Bewusst auf Englisch. Diese Seite enthält ausschließlich rechtliche und vertragliche Angaben. Wir übersetzen solche Inhalte nicht: eine deutsche Fassung wäre eine zweite Version desselben Rechtstextes, und sobald sie vom Vertrag abweicht, hilft sie einer Freigabe nicht mehr, sondern schadet ihr. Eine Sprache, ein Wortlaut. Rückfragen beantworten wir selbstverständlich auf Deutsch.
For supplier approval
The vendor, the scope, and the open points — on one page.
This page is written for whoever has to approve the supplier: procurement, group controlling, data protection. It carries the register data, the actual scope of the software and — the more useful part — the points that are settled only in the contract and are therefore not asserted here.
It concerns Polish reporting obligations of your Polish subsidiary, and nothing else.
Vendor profile
Every register entry can be checked in the Polish commercial register without us — one company, the same one in the contract, in the imprint and in the register.
| Contracting party | SimplyMobilePlus Sp. z o.o.A Polish company. It signs the contract and is your counterparty. |
|---|---|
| Experience | Workflow systems and tax softwareWe deliver workflow systems to large and very large organisations, with a dozen-plus references. Our KSeF product — the same mechanism as SimplyTax — runs in production at 6 customers. We do not publish customer names; we have no consents for that yet. |
| Tax number (NIP) | 7252310815 |
| Commercial register (KRS) | 0000909729 |
| Statistical number (REGON) | 389529673 |
| Registered office | ul. Prezydenta Gabriela Narutowicza 40/1, 90-135 Łódź, Poland |
| Product | SimplyTaxA submission layer, not an accounting system. |
| Deployment | Cloud or on-premiseBoth are actually delivered, not announced as a roadmap. |
| Interface languages | Polish and English, light and dark theme |
| Contact | sales@simplymobileplus.com |
What the product does — and does not
For an approval, the second column is the more useful one. It tells you which questions do not arise with this software at all.
Scope
- Builds the statutory file from what the source system can already export.
- Validates it against the Polish Ministry of Finance's official XSD schema — before submission.
- Optionally runs the whole cycle on the ministry's test gateway first, then in production.
- Receives the reference number and polls the submission status.
- Downloads the UPO — the official confirmation of receipt — and archives it with the file.
- Keeps a file history with the states generated, submitted-awaiting-UPO and accepted.
- Shows the generated XML before submission.
- Holds taxpayer master data per entity and allows switching between entities.
Explicitly not
- Not an accounting system and not an ERP module. Your Polish entity keeps the system it runs.
- No write-back into the source system. The path is one-way: out, validated, submitted.
- No statement on German tax law, and no German filings.
- No substitute for submission authorisation. The qualified signature or the UPL-1 power of attorney stays with your Polish entity.
- No tax advice. We describe obligations and cite the source; applying them to a case belongs to your adviser.
XSD validation establishes only that the structure of the file conforms to the schema. Acceptance at the gateway additionally depends on submission authorisation. We therefore show both steps separately instead of promising an outcome.
The data path
We do not ask which ERP is in use. We ask what it can export. The translator is written for the source system, not for the individual customer: a group with two hundred sites on one system needs one translator, because it reads from one source.
- source
Your system
- finance system of the
- Polish entity
- step 1
Export
- SQL · API
- storage · CSV
- SFTP · on-prem agent
- step 2
Translator
- written for your
- source system
- step 3
SimplyTax
- XSD validation
- submit · status
- UPO · archive
- target
Gateway
- Ministry of Finance PL
- National Bank of Poland
One point matters for the data-protection assessment: the platform is not a stateless relay. It stores your Polish entity's data, because it builds the file from it, keeps the history and files the UPO alongside. The journal, the general ledger, the trial balance and the fixed-asset register all pass through it.
Which Polish obligations are covered
The right-hand column is deliberately uneven. Not every structure is submitted through the platform, and that belongs in an approval.
| Structure | Subject | What the platform does |
|---|---|---|
| JPK_KR_PD | Accounting books for corporate income tax purposes | Generate, XSD validation, submit, reference number, status, UPO archived. |
| JPK_ST_KR | Fixed-asset register | Generate, XSD validation, submit, reference number, status, UPO archived. |
| JPK_V7M / JPK_V7K | VAT records with the return | Generate, XSD validation, submit, reference number, status, UPO archived. |
| VAT-UE | EC Sales List | Generate, XSD validation, submit, reference number, status, UPO archived. |
| AZ-KRH / PZ-KRH | Reporting to the National Bank of Poland | Generate. Your staff upload the file to the NBP portal themselves — we do not submit it. |
Which structures are active in a given project is recorded in writing in the offer. For the NBP reports there is no confirmation of receipt equivalent to the UPO — the evidence there is your own documentation of what was generated and uploaded, and when.
Deployment: cloud or on-premise
Cloud
We run the instance and your Polish entity works in the browser. When a ministry updates a schema, the change arrives centrally — with an obligation that changes several times a year, that is the actual argument.
On-premise
The platform runs in your own environment; the data sits where you put it. For groups with a binding data-location policy this is the normal case, and we do deliver it.
If the group already has a policy, please say so before the first call. It determines everything that follows, including the four points below.
What procurement settles in writing
This page deliberately states no figure for the four points below. A value given here that reads differently in the contract does not help your approval — it damages it. They belong in the contract, and that is where they are recorded.
- Point 1
Hosting location
For cloud operation: which country and whose data centre the instance runs in. For on-premise the question does not arise, because you determine the location yourself.
- Point 2
Sub-processors
Who besides us touches the data belongs in an annex to the contract, together with an undertaking to notify you of changes in advance.
- Point 3
Data processing agreement
Under Art. 28 GDPR, concluded before the first data transfer. Your Polish entity’s books run through this platform — that is not a peripheral procurement topic.
- Point 4
Retention and deletion
How long generated files, UPO documents and the underlying data are kept, and how deletion works. Your Polish entity’s statutory retention duties are unaffected.
How this website itself handles personal data — the processing that arises from reading this page and writing to us — is set out in the privacy policy. That is a different document from the processing agreement for the platform.
Scope of this page
What is described here are reporting obligations under Polish law that apply to your Polish subsidiary. This page makes no statement about German tax law, and the product is not intended for German filings.
The information is provided for orientation and does not constitute tax or legal advice. How a provision applies in a specific case is decided by the primary sources and by your Polish entity's adviser. We are a software vendor.
The next step
Thirty minutes with someone who actually files these, without a presentation. Useful beforehand: what the Polish entity's system can export, whether the group has a policy on cloud versus on-premise, and who in Poland is authorised to submit.
sales@simplymobileplus.com · +48 222 900 887
Schreiben Sie auf Deutsch oder Englisch — die Antwort kommt in derselben Sprache.