Cloud ERP in Poland: KSeF E-Invoicing, JPK Files, Costs and Go-Live Timelines
KSeF e-invoicing is mandatory in phases, and JPK_VAT files have to match it invoice by invoice. Here's what your ERP has to handle in Poland, how global suites compare with Comarch, and what a compliant go-live typically costs.
Why Poland Has to Be Its Own Workstream in Your ERP Plan
If your group has a Polish subsidiary, plant or warehouse, your cloud ERP Poland rollout hinges on one question: can the system issue, receive and reconcile invoices through KSeF, the national e-invoicing platform, and still produce JPK files that match? Some ERP features can wait for phase two. This one can't. Once KSeF applies to a taxpayer, a Polish B2B invoice that never went through the platform generally isn't a valid invoice. If the ERP can't issue one, the entity can't bill.
Groups usually arrive here one of three ways. A global template (SAP, Oracle, Microsoft, NetSuite) reaches Poland. A Polish business is acquired and still runs a local system. Or a mid-sized Polish company outgrows its first package. Each route ends in the same decision: localize the global suite through a partner or add-on, or run a local ERP such as Comarch and integrate it into group reporting. This guide covers what the rules require of the software, how the two approaches compare, and realistic budgets and timelines.
What follows describes how the rules generally work. The Ministry of Finance changes schemas and dates often, so confirm the current position with a Polish tax adviser before you sign a scope.
What KSeF E-Invoicing Requires From the ERP
KSeF (Krajowy System e-Faktur) is a clearance model. The ERP sends a structured XML invoice to the government platform, which validates it and assigns a unique KSeF number. That number, not the ERP document number, identifies the invoice. The rollout is phased: the largest taxpayers went first in early 2026, most other VAT taxpayers followed a couple of months later, and the smallest businesses and the penalty regime were deferred to 2027. Receiving invoices through KSeF applies more broadly than issuing does. Check which phase each of your entities falls into.
Your ERP or its connector has to cover the following:
- Generate the structured invoice (FA(3)). FA(3) is the current XML schema. It has mandatory fields for payment terms, bank accounts, GTU-relevant data, the split-payment marker and corrections. ERP master data often lacks these, especially when the template was built for another country.
- Authenticate properly. The current KSeF API relies on KSeF certificates and qualified seals or signatures, and older token methods are being phased out. Confirm the connector supports the newer method and that someone owns certificate renewal.
- Store and link the KSeF number. It has to flow back onto the AR open item and into JPK_VAT, and in some cases into payment references.
- Receive purchase invoices. The ERP must pull supplier invoices from KSeF and route them into AP matching. Most projects underestimate this side.
- Handle offline and outage modes. The rules allow offline issuance with later submission (offline24, plus modes for KSeF outages and emergencies). The ERP needs to track which invoices are pending and submit them on time.
- Process corrections. A credit note is a separate structured document that references the original KSeF number. A workflow that simply reverses and reissues won't work.
Foreign entities aren't treated alike. A company with a fixed establishment in Poland involved in the sale is generally in scope. A foreign company that is only VAT-registered in Poland, with no establishment, may be exempt from issuing through KSeF but can still receive invoices through it. This distinction drives scope for many groups, so have it confirmed for each legal entity.
JPK_VAT and the Other JPK Files Your ERP Must Produce
JPK (Jednolity Plik Kontrolny, the Standard Audit File for Tax) predates KSeF and still runs alongside it. For most ERPs the main obligation is JPK_VAT, submitted as JPK_V7M (monthly) or JPK_V7K (quarterly). It combines the VAT return with a transaction-level register. The structure now expects the KSeF number for each invoice, plus markers for invoices issued outside KSeF, such as offline or consumer documents. JPK_VAT reporting therefore has to reconcile against KSeF. If your tax engine and your e-invoicing connector disagree, an auditor will find it.
Each line also needs GTU codes for sensitive goods and services, plus procedure markings. Map these at the item and service-code level in master data. Don't leave them to manual tagging at month-end.
On-demand files matter during audits. They include JPK_FA (invoices), JPK_MAG (warehouse movements), JPK_WB (bank statements) and the accounting-books file. A further accounting-books file for corporate income tax is being phased in by company size and requires your chart of accounts to be mapped to tax categories. For a warehouse-heavy subsidiary, JPK_MAG is where global ERPs most often need custom work.
Treasury needs two adjacent checks. The ERP should verify supplier bank accounts against the VAT taxpayer "White List" before payment. It should also support the split payment mechanism (MPP), which applies above a PLN threshold to invoices covering listed goods and services.
Global Suite With Localization Partner vs. Local Vendor
ERP localization in Poland is mature, but the work sits in different places depending on the vendor. SAP S/4HANA Cloud and Oracle Fusion Cloud ERP typically connect to KSeF through their own compliance services or certified partners. Microsoft Dynamics 365 Finance offers Polish localization through its electronic invoicing features. Business Central and NetSuite usually rely on partner extensions. Middleware providers such as Pagero, Sovos, EDICOM and Comarch EDI can serve any ERP. On the local side, Comarch ERP XL and Optima, enova365, Symfonia and Asseco's products ship KSeF and JPK support as standard features, and they tend to update quickly when schemas change.
| Criterion | Global suite + localization | Local vendor (e.g., Comarch) |
|---|---|---|
| KSeF / JPK coverage | Via vendor service, partner add-on or middleware | Native, maintained by vendor |
| Speed of schema updates | Depends on partner; can lag | Usually fastest |
| Group consolidation and IFRS | Native, single template | Needs integration to group system |
| Polish payroll and HR | Often a separate local product | Usually included or tightly integrated |
| Local consultant availability | Good for SAP/Microsoft, thinner for others | Deep |
| Best fit | Poland is one of many entities on a global template | Poland is a large, autonomous operation |
Our position: if Poland is one of five or more entities on a common template, keep it on the global suite and buy localization from a partner with live Polish KSeF customers. You keep one chart of accounts and one close process. If the Polish entity is large (several hundred staff, its own manufacturing, Polish payroll), a local ERP integrated into group consolidation is often cheaper and lower-risk, because the compliance burden is heaviest there. The exception is when headquarters needs real-time operational visibility into that entity.
What Polish Compliance Adds to the Budget
The figures below are indicative 2026 market ranges in USD for the Polish workstream only. They vary by contract, partner rates and transaction volume, so confirm with vendors. Polish integrator day rates usually run below Western European rates.
| Cost item | Typical range (USD) | Main driver |
|---|---|---|
| KSeF connector or add-on subscription | $3,000-$25,000 per year | Invoice volume, number of NIPs (tax IDs) |
| Middleware e-invoicing (if multi-country) | $10,000-$60,000 per year | Countries covered, document volume |
| Localization implementation on global suite | $40,000-$200,000 one-off | Customizations, JPK_MAG, AP inbound flow |
| Local ERP (Comarch-class) licenses | $150-$900 per user per year | Edition, modules, cloud vs. hosted |
| Local ERP implementation | $30,000-$250,000 one-off | Manufacturing, WMS, payroll scope |
| Integration to group consolidation | $15,000-$80,000 one-off | Mapping depth, frequency |
| Polish tax adviser review | $5,000-$25,000 | Entity count, foreign-entity status |
Hypothetical example: say a German distributor puts its 120-person Polish subsidiary on Dynamics 365 Business Central with a partner KSeF extension. It might plan for roughly $60,000-$110,000 one-off for localization, integration and testing, and $8,000-$18,000 per year for the extension and certificate management. Those figures sit on top of base ERP licenses.
Realistic Go-Live Timelines and Red Flags
Adding KSeF to an existing, healthy ERP commonly takes 2-4 months, including testing in the Ministry's test environment. Localizing a global suite for a new Polish entity typically takes 4-7 months. A full local ERP rollout with production and warehouse often runs 6-12 months. Avoid going live on January 1 or at quarter-end, when VAT filings and year-end closes collide with cutover.
- Confirm KSeF scope per legal entity with a tax adviser, including foreign-entity status.
- Clean master data for FA(3): NIPs, bank accounts, GTU codes, payment terms.
- Build and test outbound, inbound, corrections and offline flows in the KSeF test environment.
- Run a parallel JPK_VAT reconciliation for at least one full period.
- Assign owners for certificate renewal and schema-update monitoring.
Red flags in vendor proposals:
- The partner can't name live production KSeF customers on your ERP version.
- Inbound invoices are "phase two."
- There's no committed SLA for schema updates.
- Offline mode is handled by a manual spreadsheet.
- The JPK_VAT output can't show the KSeF number for each invoice.
Before you shortlist, ask each vendor to demo a credit note against a KSeF-numbered invoice, then show the matching JPK_VAT line. If they can't do it live, they aren't ready.
Quick answers
Do foreign companies registered for VAT in Poland have to issue invoices through KSeF?
Usually only if they have a fixed establishment in Poland that takes part in the sale. A foreign company that is only VAT-registered there is generally not required to issue through KSeF, but it can still receive purchase invoices through the platform. Have a Polish tax adviser confirm this for each entity, because the answer sets your project scope.
Can we keep sending PDF invoices to Polish B2B customers?
Not as the legal invoice, once KSeF applies to you. You can still send a PDF or printout as a visual copy, but the valid document is the structured XML with its KSeF number. Invoices to consumers are handled differently and may be issued outside KSeF.
Is Comarch only suitable for Polish-only companies?
No. Comarch ERP XL and its cloud offerings serve multinational subsidiaries, and Comarch also sells EDI and e-invoicing services in other countries. The trade-off is integration. Group consolidation, intercompany flows and global reporting need a reliable interface to your headquarters system.
What happens if KSeF is down when we need to invoice?
The rules allow offline issuance during outages and in certain other cases, with submission to KSeF within set deadlines once the platform is back. Your ERP or connector has to mark these invoices, give the buyer a verification QR code and submit them automatically. Ask your vendor how it tracks pending submissions.
How does KSeF affect JPK_VAT reporting?
JPK_V7M and JPK_V7K now expect a KSeF number for each invoice, plus markers for invoices issued outside KSeF. Your VAT register therefore has to reconcile with what the platform holds. Run at least one parallel period before go-live to catch mismatches.
Written by the Freight Base System editorial team. Prices, features and rules change often - confirm details with the vendor or a licensed professional before you decide.