Mandatory e-invoicing is no longer on the horizon in Poland. It is here.
Since 1 February 2026, every VAT-registered business in Poland has been required to receive its purchase invoices through KSeF, the National e-Invoicing System. The obligation to issue through KSeF started the same day for the largest taxpayers and extended to most remaining businesses on 1 April 2026. One deadline still remains: from 1 January 2027, the grace period ends and invoices issued outside KSeF can attract penalties of up to 100 percent of the VAT shown, assessed for each invoice separately.
That changes what an ERP system needs to do for a Polish entity. Compliance is no longer a bolt-on; it is part of the invoicing process itself, because a KSeF invoice is not treated as issued until the platform has accepted it and assigned a number. This guide explains how NetSuite handles the mandate, which parts come from Oracle and which come from a localisation package, and how it compares with the main alternative most finance teams evaluate.
Key Takeaways
- KSeF is live in both directions. Receiving through the platform has been mandatory for all VAT-registered businesses since 1 February 2026. Issuing applies to large taxpayers from the same date and to most other businesses from 1 April 2026. Penalties begin on 1 January 2027.
- Oracle supports KSeF issuing natively. The European Union Electronic Invoicing SuiteApp generates FA(3) invoices and credit memos and certifies them to KSeF directly from the transaction record, with the KSeF number and status written back. Retrieval of purchase invoices from the platform is not currently part of that native coverage and needs a separate route.
- Polish statutory reporting comes from a localisation package. JPK_V7, split payment, Whitelist checks, NBP rates, and Polish statutory documents are delivered through a maintained Polish localisation SuiteApp rather than as standard NetSuite functionality.
- One product, not a portfolio. NetSuite covers finance, inventory, full CRM, and ecommerce in a single product on one database. The Microsoft route typically combines Business Central with Dynamics 365 Sales, the Power Platform, and marketplace add-ons; each one comes as an additional licence, integration, and a potential failure point.
- FinanSys implements NetSuite for Polish entities and for international groups with Polish subsidiaries, from discovery workshop through KSeF integration to post-go-live support.
What Is KSeF and Who Does It Affect?
KSeF (Krajowy System e-Faktur) is Poland’s national e-invoicing platform, operated by the Ministry of Finance. It works on a clearance model: a B2B invoice is submitted as a structured XML file in the FA(3) schema, validated by the platform, and assigned an official KSeF number. Polish buyers collect their purchase invoices from the platform rather than receiving a PDF by email, and the date the KSeF number is assigned is the date the buyer is treated as having received the invoice.
The rollout has run in phases. Businesses with 2024 sales above PLN 200 million have been required to issue through KSeF since 1 February 2026. Most other VAT-registered businesses followed on 1 April 2026. Businesses whose invoiced sales are PLN 10,000 gross or less in a given month may continue to issue electronic or paper invoices until the end of 2026. Separately, invoicing through cash registers and simplified invoices up to PLN 450 also remain permitted until the end of 2026.
The receiving obligation is the one most often missed. It applied to everyone from 1 February 2026, with no phasing and no turnover threshold. A Polish entity that is still waiting for supplier PDFs by email is already out of step with the rules, whatever its own issuing deadline was.
Throughout 2026 the Ministry of Finance is applying a protective period: no administrative penalties for KSeF errors such as late submission or incorrect formatting. That runway closes on 31 December 2026. From 1 January 2027, issuing an invoice outside KSeF when the mandate applies can cost up to 100 percent of the VAT shown on that invoice, or up to 18.7 percent of the gross amount where no VAT is shown. The same penalty applies to an invoice issued in offline mode that is not sent to KSeF within the required time. Penalties are assessed per invoice, so a process fault repeated across a month is not one breach but as many breaches as there are invoices. In practice, the second half of 2026 is the last safe window to implement and test.
Who Is Outside the Issuing Obligation
The mandate reaches further than many international groups expect, but it does not reach everyone. A foreign company with a fixed establishment in Poland that takes part in the supply is subject to the same requirements as a Polish business. A company with no seat and no fixed establishment in Poland is outside the issuing obligation, as is a company whose Polish fixed establishment plays no part in the transaction being invoiced. The Ministry of Finance issued explanatory notes on 28 January 2026 setting out how fixed establishment is determined for KSeF purposes, and any group that is not obviously on one side of the line should read them before deciding.
Invoices to consumers are also outside the obligation, though they may be issued through KSeF voluntarily. Proforma invoices, internal documents, and credit and debit notes are not sent to KSeF at all. Correcting notes were abolished on 1 February 2026 and are no longer issued in any form.
Where NetSuite Fits In
NetSuite is a cloud ERP platform owned by Oracle and used by 43,000+ organisations worldwide. It manages finance, order-to-cash, procure-to-pay, inventory, projects, CRM, and e-commerce in a single system built on one database, which means every department works from the same live data rather than last week’s export. It is delivered entirely as software as a service: no on-premise servers, no customer-managed patches, and two automatic platform upgrades a year handled by Oracle.
For Poland, the compliance layer comes from two places. KSeF e-invoicing is now covered by Oracle’s own European Union Electronic Invoicing SuiteApp, released for Poland in the 2026.2 update. Polish statutory reporting and accounting requirements are covered by a Polish localisation SuiteApp maintained by a specialist partner and updated as regulations change. That combination, a global platform plus a maintained local compliance layer, is what makes NetSuite a realistic option both for mid-sized Polish companies and for international groups consolidating a Polish subsidiary.
How NetSuite Handles KSeF
KSeF issuing in NetSuite comes from Oracle directly, through the European Union Electronic Invoicing SuiteApp, so structured e-invoicing is part of the billing workflow rather than a separate tool. In day-to-day use, that looks like this:
- Issuing: invoices and credit memos are converted to the FA(3) XML schema and certified to KSeF directly from the transaction in NetSuite, individually or in bulk, with no re-keying into a government portal.
- Status and audit trail: after certification, the official KSeF number and QR code URL are stored on the transaction, with progress and errors visible in the e-document status and audit trail. Every invoice carries system-based evidence for tax inspections without a document hunt.
- QR codes: the KSeF verification QR code required on paper or PDF visualisations of e-invoices can be added to NetSuite invoice templates, covering offline and out-of-system delivery scenarios.
- Receiving: retrieval of purchase invoices from KSeF is not part of the SuiteApp’s current Poland coverage. Inbound is handled through a Polish localisation package with a KSeF registry function, or through a connector, and the choice is one of the first decisions to make in scoping.
Because validation happens at the platform, data quality matters more under KSeF than it ever did with PDF invoicing, and the failure modes are specific. Generation fails if a tax code is not mapped to a Polish tax category, or if a required PLN exchange rate is missing on a non-PLN transaction, and the NIP must be set correctly on both the subsidiary and the customer record. An implementation that gets this configuration right prevents most rejections before they happen.
One Detail Worth Deciding Early: Online or Offline24
If an invoice is sent to KSeF on a later date than the issue date written on the invoice itself, it counts as issued under the offline24 procedure rather than online. That is not a fault condition; offline24 is a legitimate route, and the invoice keeps the date the seller assigned to it. But it carries its own requirements, including an issuer certificate and a second QR code on any visualisation given to the buyer outside the platform, and it must reach KSeF no later than the next working day.
This matters for ERP design because a nightly batch is a very natural way to send invoices and quietly puts you in the offline24 regime. Deciding deliberately whether to certify in real time or in batch, and configuring for whichever you choose, is a better outcome than discovering the answer after go-live.
Polish Localisation Beyond KSeF
E-invoicing gets the headlines, but most of the daily compliance workload in a Polish finance team sits elsewhere. A maintained Polish localisation package covers that ground:
- VAT and JPK reporting: JPK_V7M and JPK_V7K files including corrections, split payment (mechanizm podzielonej płatności), reverse charge scenarios, and intra-EU transactions.
- Polish accounting standards: chart of accounts templates, statutory ledgers, and reporting layouts aligned with the Accounting Act (Ustawa o rachunkowości).
- Local documents and language: Polish-language interface, local date and number formats, and document types such as WZ, PZ, advance invoices, and corrections.
- NBP exchange rates: daily average rates from the National Bank of Poland retrieved automatically for VAT, currency postings, and JPK.
- Vendor verification: Whitelist (Biała Lista) bank account checks, VAT payer status, and VIES and GUS register lookups.
These capabilities come from the localisation SuiteApp rather than from core NetSuite, so the specific package matters. It is worth confirming at evaluation stage which functions are included, how quickly the vendor ships regulatory updates, and what the ongoing cost is. The localisation is maintained as regulations change, which matters in a jurisdiction where they change often, and it is the reason your compliance layer stays current without emergency custom development.
NetSuite vs Microsoft Dynamics in Poland
Both platforms serve real needs, but if you are comparing the two for a Polish entity, three structural differences tend to decide it.
One platform versus an ecosystem. NetSuite delivers finance, inventory, CRM, and e-commerce on a single unified platform. Microsoft splits functionality across Business Central, Finance & Operations, the Power Platform, and a marketplace of add-ons. Each additional component is another integration to build, licence, and maintain.
Upgrades. NetSuite upgrades are automatic and consistent for every customer, twice a year. Dynamics environments, particularly heavily customised ones, often require project work at major version changes, which carries cost and risk that rarely appears in the initial comparison spreadsheet.
Who stands behind the e-invoicing layer. Both platforms rely on localisation layers for Polish statutory reporting, so evaluate the specific package rather than the brand. The difference sits in KSeF itself: NetSuite’s issuing support ships from Oracle through the European Union Electronic Invoicing SuiteApp, while Business Central’s KSeF functionality comes from partner-built extensions. That distinction is worth testing rather than taking on trust, in either direction, by asking each vendor which flows are native, which are partner-supplied, and who commits to shipping schema updates.
For mid-market companies and multi-entity groups that want one global platform with dependable Polish compliance, NetSuite is usually the simpler and lower-risk choice. Where a business is deeply committed to the Microsoft stack and has the internal capability to manage a multi-product environment, Dynamics remains a credible alternative.
How Much Does NetSuite Cost in Poland?
The honest answer is that it depends on scope, and any partner who quotes a fixed price before understanding your business is guessing. NetSuite is licensed on a subscription basis, sized by modules and user count, with no perpetual licences and no surprise upgrade fees. Total cost of ownership has five main components: subscription licences, implementation services, data migration, integrations, and training. For a Polish entity, add the localisation package and, where a group operates e-invoicing in more than one country, the Electronic Invoicing licence that multi-country use requires.
What the cloud model removes is equally important: servers, database licences, backup infrastructure, and the upgrade project every five to ten years that on-premise systems eventually force. A meaningful estimate for a Polish deployment takes a short discovery session, which FinanSys provides free of charge together with a personalised demo and a written proposal.
How Long Does a NetSuite Implementation Take?
A focused, financials-first project covering core accounting, VAT, JPK, and KSeF integration typically takes three to six months. Multi-module and multi-subsidiary rollouts that add order management, inventory, procurement, and CRM usually run six to twelve months. The factors that can stretch timelines are predictable: complex legacy integrations, poor data quality, heavily customised business processes, and multi-country scope.
Projects follow a structured path: discovery and design, configuration, localisation including KSeF, data migration, user training, go-live, and a hypercare period. FinanSys runs implementations on a milestone basis with parallel runs and structured testing before any legacy system is switched off, so go-live is controlled rather than chaotic.
Preparing for the January 2027 Enforcement Deadline
If your Polish entity is already in scope, you are invoicing through KSeF today, penalty-free, while the protective period lasts. That makes the remainder of 2026 an implementation runway rather than a waiting room. Five steps matter most:
- Audit your current process. Map how invoices are issued and received now, and where manual steps or workarounds have crept in since April.
- Confirm the inbound route. Purchase invoices have to come out of KSeF and into NetSuite somehow. Decide whether that is the localisation package’s registry function or a connector, and make it a scoped deliverable rather than an assumption.
- Clean master data. NIP numbers, addresses, VAT settings, and tax codes must be accurate before automation can work. Bad data is the leading cause of KSeF rejections.
- Test at volume. Run representative invoice types, including corrections and advance invoices, through the integration before penalties apply.
- Train the team. AR and accounting staff need to know the exception workflow: what a rejection code means, who resolves it, and how reconciliation works when every invoice is government-validated.
Companies that treat 2026 as a test year gain operational stability before enforcement begins. Companies that wait until December will be debugging their invoicing process with penalty exposure attached.
How FinanSys Supports NetSuite in Poland
FinanSys is a specialist NetSuite partner delivering end-to-end implementations, with 27 years of ERP experience and a 94% retention rate.
The team works with Polish companies directly and with international teams that run Polish subsidiaries, which is often where compliance questions are hardest: group reporting standards on one side, KSeF, JPK, and the Accounting Act on the other. If you want to see how NetSuite could handle your specific processes, FinanSys offers a free, no-obligation demo tailored to your industry, entity structure, and regulatory priorities. Bring your current pain points and a sample invoice flow, and the session will focus on real scenarios rather than generic features.
If your group has entities in other European countries, our guide to NetSuite e-invoicing across the EU sets out the equivalent position for Belgium, France, Germany, Spain and Italy.
Frequently Asked Questions
Is NetSuite compliant with mandatory KSeF e-invoicing in Poland?
For issuing, yes. Oracle’s European Union Electronic Invoicing SuiteApp generates invoices and credit memos in the FA(3) schema, certifies them to KSeF from the transaction, and stores the official KSeF number, QR code, status, and audit trail on the record. Retrieval of purchase invoices from KSeF is handled through a Polish localisation package or a connector rather than the EU SuiteApp, so a compliant Polish deployment is usually the two together.
What is the deadline for KSeF compliance?
Receiving invoices through KSeF has been mandatory for all VAT-registered businesses since 1 February 2026. Issuing has applied to large taxpayers since 1 February 2026 and to most other VAT-registered businesses since 1 April 2026, with businesses invoicing PLN 10,000 gross or less per month able to wait until 1 January 2027. That date is also when financial penalties take effect for everyone.
What are the penalties for not using KSeF?
From 1 January 2027, issuing an invoice outside KSeF when the mandate applies can result in a penalty of up to 100 percent of the VAT amount on the invoice, or up to 18.7 percent of the gross amount where no VAT is shown. The same applies to invoices issued in offline mode and not sent to KSeF in time. Penalties are imposed by decision of the head of the tax office and assessed per invoice.
Can NetSuite run Polish and international entities in one system?
Yes. NetSuite OneWorld supports multi-company, multi-currency, and multi-language operation in a single instance. Group reporting and consolidation run centrally while each Polish entity keeps its own statutory ledgers, VAT registers, and KSeF authentication. Note that the European Union Electronic Invoicing SuiteApp requires a OneWorld account, and that e-invoicing across more than one country requires an Electronic Invoicing licence from Oracle.
Does a foreign company with a Polish subsidiary need to use KSeF?
If the entity has a registered office or fixed establishment in Poland that takes part in the supply, yes, it falls under the mandate in the same way as a domestic business. A company with no seat and no fixed establishment in Poland is outside the issuing obligation, and so is one whose Polish fixed establishment plays no part in the transaction. The Ministry of Finance published explanatory notes on fixed establishment for KSeF purposes in January 2026, and borderline cases are worth checking against them.
How long does it take to implement NetSuite with KSeF integration?
A financials-first implementation covering accounting, VAT, JPK, and KSeF typically takes three to six months. Broader rollouts with inventory, procurement, and CRM usually take six to twelve months, depending on data quality and integration complexity.
