Mandatory E-Invoicing in Poland

E‑invoicing in Poland 2026: Complete Guide for European Businesses

Share This Blog

Copied!

Try It Now

HubBroker iPaaS integrates effortlessly with your systems, offering the flexibility to scale and adapt. HubBroker keeps your business ahead by simplifying complexity.

Poland is rapidly modernizing tax administration and invoice processing via the Krajowy System e-Faktur (KSeF), the country’s national e-invoicing platform. KSeF has been available for voluntary use for several years and — following publication of the KSeF 2.0 technical documentation and schema — the Polish Ministry of Finance has confirmed a phased mandatory rollout under which large taxpayers will be required to use KSeF from 1 February 2026 and most other taxpayers from 1 April 2026. Businesses selling into Poland must prepare for structured, government-validated e-invoices (FA(3) schema) to remain VAT-compliant and avoid operational disruption.

HubBroker has supported hundreds of EU and UK companies through tax digitalization transitions. This guide explains how KSeF works, the confirmed mandatory timeline, the technical requirements (API / FA(3) structured invoice), and a practical implementation roadmap to help your business remain compliant and competitive.

Simplify Poland’s KSeF Transition and Integrate e-invoicing Smoothly with Your ERP

Book a Free Demo

Understanding Poland’s E‑invoicing Landscape

Current state of digitalisation

Poland introduced the National e-Invoice System (KSeF) to transform how business-to-business (B2B) and business-to-government (B2G) invoices are issued, validated, and archived in the country. The platform operates alongside the earlier SAF-T Poland (Standard Audit File for Tax). It forms a key part of the Polish tax authority’s strategy to reduce the VAT gap and increase transparency.

Timeline of implementation

  • 1 January 2022: KSeF made available voluntarily for issuing structured invoices. Comarch+1
  • 1 February 2026: Mandatory use of KSeF for large taxpayers (those with previous-year turnover above the threshold). EY
  • 1 April 2026: Mandatory use of KSeF for most remaining taxpayers.

Comparison with other EU countries

  • Germany is still in the planning phase, with a voluntary pilot expected in 2025.
  • France has announced a mandatory e‑invoicing framework for 2025, but the national platform is still under development.
  • Italy already operates the SDI system, requiring structured XML (FatturaPA) for all B2B invoices.
  • Spain uses the SII (Immediate Supply of Information) system for real‑time VAT reporting.

Key statistics and market data

Industry estimates suggest that as Poland transitions to full adoption of KSeF, the volume of e-invoices could reach over one billion annually by 2026. Additionally, survey data show a growing share of Polish enterprises already using electronic invoicing formats and preparing for KSeF integration.

KSeF System Deep Dive

What is KSeF?

The Krajowy System e-Faktur (KSeF) is Poland’s national e-invoicing platform operated by the Ministry of Finance. It serves as a central system where structured invoices are issued, received, validated, and archived. The objective is to enable a clearance-style model for VAT-relevant invoices, improve transparency, speed up VAT refunds, and reduce the tax gap.

From 1 January 2022, the system has been available voluntarily; mandatory use is scheduled from 1 February 2026 for large taxpayers and from 1 April 2026 for the majority of other businesses.

Link for document: https://ksef.podatki.gov.pl//pliki-do-pobrania-ksef-20/

Technical specifications and requirements

Invoice format: FA(3) — the structured XML schema defined by the Polish Ministry of Finance (KSeF 2.0 standard). Other formats such as UBL 2.1 or UN/CEFACT, can be converted externally but are not natively accepted by KSeF.

API architecture: RESTful API over HTTPS (TLS 1.2 or higher).

Authentication & authorisation: Token-based authentication linked to the taxpayer’s NIP and user permissions registered in KSeF. Digital certificates (QES or trusted profile) are used for user login only, not for automated submissions.

Data exchange: Invoices are uploaded to KSeF and validated in near real time. Upon acceptance, the system assigns a unique KSeF reference number and timestamp.

Archiving: Invoices are stored centrally in KSeF for 10 years from issuance, removing the need for local archival copies.

Error handling: Responses are delivered as structured XML/JSON messages with status codes (e.g., accepted, rejected, duplicate, schema error).

API integration details

The KSeF REST API allows authorised taxpayers to submit, validate, and retrieve structured e-invoices. After submission, each document is checked against the official FA(3) XML schema and assigned a unique KSeF reference number and timestamp by the Polish Ministry of Finance. 

Reference : https://ksef.podatki.gov.pl//informacje-ogolne-ksef-20/numer-ksef-i-zbiorczy-identyfikator/ 

Authentication methods

Access to the KSeF API requires a secure authentication token linked to the taxpayer’s Polish VAT ID (NIP). Tokens are generated in the KSeF portal by authorised users.

For manual portal logins, users may authenticate using a Qualified Electronic Signature (QES) or an eIDAS-compliant certificate. 
Foreign companies without a Polish NIP must use a fiscal representative or a certified service provider to issue compliant invoices.

Document formats accepted

KSeF accepts only FA(3) XML invoices. 
Other structured formats, such as UBL 2.1 or UN/CEFACT CII, can be converted into FA(3) by certified EDI providers like HubBroker, enabling seamless cross-border compliance.

Stay compliant with Poland’s upcoming e-invoicing rules through a certified PEPPOL Access Point.

Register Now on Peppol Network

Mandatory Requirements & Timeline

Current voluntary phase details

Since 1 January 2022, use of the Krajowy System e-Faktur (KSeF) has been voluntary for Polish taxpayers.
During this phase, businesses have been encouraged to integrate their ERP or e-invoicing solutions with KSeF to test FA(3) schema uploads, API connections, and internal approval flows. 

The voluntary period will remain active through 2025, providing companies time to adjust before mandatory e-invoicing begins in 2026.
The Ministry of Finance has published the KSeF 2.0 documentation and FA(3) invoice schema (June 30 2025) and launched public API test environments in September 2025 to support integration and onboarding. 

Reference: https://ksef.mf.gov.pl/

Mandatory implementation timeline 

Date  Requirement 
1 February 2026 Mandatory KSeF e-invoicing for large taxpayers (as defined by turnover thresholds under the VAT Act). 
1 April 2026 Mandatory for all remaining VAT-registered taxpayers, including SMEs and foreign entities with a Polish VAT ID (NIP).
1 January 2027 Possible inclusion of additional entity types and B2C expansions (subject to future legislation).

Who is Affected?

Domestic Businesses:

All Polish entities that issue VAT-liable invoices must transmit them through KSeF starting from their relevant phase date. 

Threshold values and exemptions

Under the latest KSeF 2.0 regulation, there are no monetary turnover limits, such as €5 million. Instead, the rollout follows a phased taxpayer classification as defined by the Polish VAT Act:

1 February 2026 → Large taxpayers (as defined by turnover and legal status in Polish VAT regulations) must begin issuing all invoices via KSeF.

1 April 2026 → All remaining VAT-registered businesses, including SMEs and foreign entities with a Polish VAT ID (NIP), become subject to the mandatory e-invoicing obligation.

After these dates, all B2B transactions subject to Polish VAT must be processed through KSeF, regardless of company size or revenue.

Exemptions

At present, the following categories remain outside the mandatory scope of KSeF:

  • B2C invoices (sales to private individuals not registered for VAT)
  • Simplified receipts under PLN 450 (~€100) or invoices marked as “simplified”
  • Flat-rate farmers’ invoices (specific agricultural exemptions)
  • Foreign suppliers without a Polish VAT ID (NIP) — these entities are not directly required to use KSeF but may comply through a Polish fiscal representative or certified EDI intermediary such as HubBroker

Penalties for non‑compliance

According to Article 106nh of the Polish VAT Act, failure to issue invoices via KSeF when required may result in: A fine of up to 100 % of the VAT amount shown on the invoice, or In standard cases, an administrative penalty of up to 30 % of the VAT due, plus interest on under-declared tax.

Enforcement Timeline

Grace period: During early 2026, taxpayers will be permitted to correct submission errors without automatic fines.

Full enforcement: Penalties are expected to be activated from Q3 2026, once KSeF monitoring and automatic validation become fully operational.

Step‑by‑Step Implementation Guide

Pre-implementation checklist

Confirm business scope — Identify if your company is VAT-registered in Poland (has a Polish NIP). KSeF applies to all VAT-active entities under the 2026 rollout plan. → Official Portal – KSeF (Ministry of Finance)

Identify exemptions — B2C invoices, simplified receipts (< PLN 450 ≈ €100), and flat-rate farmer invoices remain outside the 2026 scope.

Select a compliance partner — Choose an e-invoicing solution certified for FA (3) mapping and KSeF API integration (e.g., HubBroker).

Prepare ERP systems — Ensure your ERP can export invoice data for conversion to FA(3) XML. Legacy formats (UBL, EDIFACT) must be transformed before submission.

Review data fields — Confirm all mandatory FA(3) elements are supported (buyer NIP, VAT codes, payment references). → FA(3) Logical Structure PDF – Polish MoF

Registration process for foreign entities

  • Obtain Polish VAT registration (NIP). Foreign suppliers without a NIP must act through a Polish fiscal representative or authorized intermediary.
  • User setup & token generation — Authorised users are created in the KSeF portal; tokens are tied to your NIP and permissions.
  • Certificates (manual logins only) — An eIDAS-compliant certificate or QES is used only for manual portal access, not API flows.

Technical integration requirements

  • HTTPS endpoint with mutual TLS authentication.
  • Message signing using a qualified certificate (QES) or the e‑IDAS profile.
  • Schema validation against the latest KSeF XSD (version 2.0).

Technical Integration Requirements

  • API architecture: REST over HTTPS (TLS 1.2+).
  • Authentication: Token-based authentication via KSeF portal; no per-invoice QES required.
  • Error handling: Responses indicate “Accepted,” “Rejected,” or “Duplicate”; store each KSeF reference ID for audit.
  • Transformation: Middleware converts foreign formats (UBL, CII, CSV) to FA(3) and validates against the official XSD.
  • Logging & Retention: Retain submission logs and KSeF IDs for 10 years (as invoices are archived centrally by KSeF).

Testing Checklist (Before Go-Live)

Perform at least three successful cycles in the KSeF sandbox: 

  1. Valid submission — FA(3) invoice accepted with KSeF ID and timestamp. 
  1. Error scenario — Submit an invoice with an invalid VAT number and review error messages. 
  1. Correction workflow — Send a corrective invoice to link to the original KSeF reference.
    Optional extras: performance tests and duplicate-handling tests. 

See official sandbox and API resources on KSeFAPI.pl Harmonogram

Go-Live Best Practices

  • Parallel run period: Run KSeF and legacy systems in parallel for 1 month to validate flows. 
  • Monitoring & alerts: Implement notifications for failed submissions, token expiry, and schema errors. 
  • Retry mechanism: Use idempotency and exponential backoff for network failures. 
  • Training: Train finance and operations teams on KSeF processes, penalties and correction rules. 
  • Audit trail: Link KSeF IDs to ERP records and bank reconciliations for compliance. 

Post Go Live Support. 

Area  Action 
Reconciliation  Match KSeF IDs with ERP and payment records. 
Compliance monitoring  Subscribe to Ministry updates on schema changes. 
Security maintenance  Rotate tokens regularly and secure API credentials. 
Vendor governance  Keep support SLA for FA(3) updates and urgent issues. 

Ensure your business is fully prepared for Poland’s 2026 e-invoicing mandate with expert guidance

Book a Free Demo

International Business Considerations

EU-based companies trading with Polish customers must: 

  • Obtain a Polish VAT number (NIP) if they have a taxable presence in Poland. 
  • Integrate via the KSeF API using token-based authentication; no separate certification layer is required for automated submissions. 
  • Ensure all invoices are converted to FA(3) (structured XML defined by the Ministry of Finance). 
  • Appoint a VAT representative only if they lack a Polish establishment or are not VAT-registered locally. 

📘 References: KSeF Portal – MoF | FA(3) Structure PDF

UK Companies (Post-Brexit)

Following Brexit, UK suppliers are treated as non-EU entities:

  • Must register for Polish VAT (NIP) if issuing invoices subject to Polish VAT.
  • Can authenticate using eIDAS-compliant certificates or through an authorised Polish representative; a QES issued in the EU is optional, not mandatory.
  • May use a local intermediary (HubBroker) to convert and submit FA(3) invoices to KSeF on their behalf.

📘 References: EY Update – KSeF 2.0

Non-EU Businesses

Non-EU companies (e.g., US, Switzerland) follow the same approach as UK entities: 

  • Must register for Polish VAT or appoint a VAT representative. 
  • KSeF API submission is handled through the same secure endpoints used by domestic and EU taxpayers. 

Cross-Border Transactions

KSeF supports both domestic and cross-border invoice flows through the same API: 

  • Supplier and buyer VAT IDs must conform to VIES validation standards. 
  • All invoices are transmitted in FA(3) XML and stored centrally. 
  • Foreign suppliers remain responsible for VAT compliance and record-keeping. 

📘 References: Sovos – KSeF 2.0 Implementation Guide

VAT Representative Requirements 

If a company has no registered office or NIP in Poland, it must appoint a Polish VAT representative who will: 

  • File VAT returns and manage correspondence with the Polish Tax Authority.
  • Maintain ongoing compliance for KSeF submissions and corrections.
Country  System  Mandatory  Format  API Access  Key Date 
Italy  SDI  Yes  FatturaPA (XML)  REST/SOAP  Active since 2019 
France  PDP/Chorus Pro  Phased 2026 onwards  XML/PDF  API  2026 (revised) 
Germany  Planned  No (2025 pilot)  XRechnung (XML)  API  2025 pilot 
Spain  SII  Yes (2018)  XML  SOAP  Ongoing 
Romania  RO e-Invoice  Yes (2022)  XML  API  Ongoing 
Hungary  Online Invoice  Yes (2021)  XML  API  Ongoing 
Portugal  e-Factura  Yes (2021)  XML  API  Ongoing 
Poland  KSeF 2.0  Yes (2026)  FA(3) (XML)  REST API  1 Feb 2026 / 1 Apr 2026 

Get ready for Poland 2026 with secure, compliant PEPPOL e-invoicing

Register for PEPPOL E-Invoicing

Benefits & ROI

Cost‑savings analysis

Automating invoice generation and submission reduces paper, postage, and storage costs by up to 40 %, and lowers rejection rates from ~12 % to under 2 %.

Efficiency improvements

Real-time submission to KSeF shortens invoice-to-approval cycles from days to seconds and improves DSO by 5–7 days.

Reduced VAT gap impact

Real-time VAT validation helps Poland recover an estimated €2 billion annually, while early adopters enjoy faster refunds and lower audit risk.

Automation opportunities

Full ERP integration (SAP, Microsoft Dynamics) enables: 
Invoice creation → Validation → KSeF submission → Confirmation → Archiving.

Real‑time reporting advantages 

With KSeF, finance teams have instant visibility into VAT positions, enabling more accurate forecasting and faster response to tax‑authority queries.

Common Challenges & Solutions

Technical integration hurdles

Many companies struggle with the complex XML schemas required by KSeF. HubBroker’s drag‑and‑drop mapping tool lets you connect your existing ERP fields to the required KSeF elements without writing code. 

Language barriers

The Polish tax authority’s documentation is primarily in Polish. Our multilingual support team provides English‑language guidance and translated reference materials, ensuring you never miss a critical detail. 

Legal compliance complexities

Keeping up with evolving deadlines and thresholds can be daunting. HubBroker’s compliance calendar automatically alerts you to upcoming changes, such as the 2025 mandatory deadline, so you can plan proactively. 

Multi‑country operations management

If you operate in several European markets, managing different e‑invoicing standards can become fragmented. HubBroker’s Unified E‑Invoicing Hub centralises all formats—FA(2), UBL, XRechnung, FatturaPA—into a single dashboard, simplifying reporting and audit trails. 

How HubBroker addresses these challenges

  • Pre‑configured KSeF connector reduces implementation time from months to weeks. 
  • Continuous schema updates keep your invoices compliant with the latest Polish requirements. 
  • Multilingual support removes language obstacles. 
  • Unified dashboard handles multiple European e‑invoicing standards, giving you a single source of truth for compliance across borders.

Conclusion & Next Steps

Poland’s move to mandatory e-invoicing (KSeF 2.0) is both a compliance requirement and a digital advantage.
By adopting an automated solution like HubBroker, you can: 

  • Meet the 2026 deadlines with minimal disruption. 
  • Reduce operational costs and speed up cash flow. 
  • Gain a compliance edge across the EU, UK, and beyond. 

Next Steps 

  1. Schedule a KSeF Readiness Assessment with our experts. 
  1. Explore our sandbox environment for end-to-end test submission. 
  1. Sign up for a 30-day trial to experience automated FA(3) compliance. 

Don’t wait for penalties—lead the digital tax transformation with HubBroker.

FAQ (Updated 2026) 

Q1. Is e-invoicing mandatory in Poland?
A: Yes. KSeF becomes mandatory from 1 February 2026 for large taxpayers and from 1 April 2026 for all other VAT-registered entities.
EY Tax Alert 2025 

Q2. Which formats are accepted by KSeF?
A: Only the FA(3) XML format defined by the Polish Ministry of Finance is accepted.
Other standards (UBL 2.1, UN/CEFACT CII) must be converted before submission.
FA(3) Logical Structure PDF – MoF 

Q3. Can UK companies use KSeF after Brexit?
A: Yes. UK companies can authenticate via an eIDAS-compliant certificate or use an authorised intermediary.
A Polish VAT registration (NIP) is required for all suppliers issuing VAT invoices in Poland.
Sovos KSeF 2.0 Documentation 

Q4. What happens if an invoice fails validation?
A: The KSeF API returns a structured error message identifying the issue.
HubBroker’s system automatically flags the error and enables instant correction and resubmission. 

Q5. Do I need a VAT representative in Poland?
A: Yes, if your business has no registered office or Polish VAT ID (NIP).
A local VAT representative will handle VAT filings and ensure KSeF compliance. 

Q6. How does HubBroker maintain ongoing compliance?
A: HubBroker continuously monitors Ministry of Finance updates and automatically adjusts to new FA(3) validation rules and API schema changes, ensuring full alignment at all times.
KSeF Portal – MoF 

Q7. Can I receive the Official Confirmation of Receipt (UPO) and status updates for invoices submitted via HubBroker KSeF? 

Yes. HubBroker’s KSeF integration automatically returns every Official Confirmation of Receipt (UPO) and related status code received from the Polish Ministry of Finance. All responses are visible directly inside the HubBroker Dashboard, as well as in your Tracking and Archive modules, ensuring full traceability for every FA(3) invoice submitted through our platform.

Q8 Does HubBroker KSeF handle only EDI invoices, or all B2B invoices subject to the mandate? 

HubBroker’s solution covers all B2B invoices that fall under the KSeF mandate, not just those sent through traditional EDI channels.
Whether your data originates from an ERP system, CSV export, or API feed, HubBroker automatically transforms it into the required FA(3) XML format and submits it securely to KSeF for clearance.

  1. How can we verify that the HubBroker KSeF solution fits our business needs?

You can request a personalized KSeF demo from HubBroker to see the platform in action.
Our team will walk you through test submissions in the KSeF sandbox environment, show how validation and UPO tracking work, and demonstrate how easily our interface connects with your ERP system.

HubBroker has supported hundreds of European and global companies through their e-invoicing transformation. As regulations evolve, we continuously update our KSeF connector and validation rules to guarantee ongoing compliance. 

📅 Book your free demo

Continue Reading