A German-owned distribution company with a Polish subsidiary received a routine invoice from its Warsaw logistics partner in early 2026. The invoice arrived as a structured XML file with a KSeF reference number. The German finance team had no idea what to do with it. That confusion – multiplied across dozens of suppliers – is the situation many German businesses now face.

Poland's National e-Invoice System – Krajowy System e-Faktur (KSeF) – became mandatory for large Polish taxpayers on 1 February 2026. Every VAT-registered Polish supplier must now issue invoices exclusively through the KSeF platform. German businesses receiving Polish invoices, or operating Polish subsidiaries, must adapt their accounts-payable and ERP workflows immediately. Failure to accept or process KSeF-format invoices can delay payment, trigger disputes, and – for Polish entities – result in penalties of up to PLN 100 per non-compliant document.

This case study draws on an anonymised matter we handled for a German industrial group with three Polish entities. It covers the background, the strategy we developed, the steps taken, and the lessons that transfer directly to any German business with Polish operations or suppliers.

What was the background to the German client's situation?

The client was a mid-sized German manufacturer with subsidiaries in Mazowieckie, Silesia, and Małopolska. Each entity had its own ERP instance and a separate local finance team. The parent company in Bavaria managed consolidation centrally but had delegated day-to-day VAT compliance to each subsidiary. When KSeF became mandatory, the subsidiaries were not ready. Two had not registered for KSeF access at all. The third had registered but had not connected its ERP system to the KSeF application programming interface (API).

The Polish subsidiaries were issuing invoices manually through the web interface. That workaround is permitted for low-volume issuers, but it creates no audit trail compatible with the parent's SAP environment. Meanwhile, the parent company was receiving KSeF-structured invoices from Polish suppliers and routing them through a standard PDF workflow – which meant the KSeF reference numbers were being discarded. Under Polish tax law, a buyer who does not correctly record the KSeF identifier risks losing the right to deduct input VAT on that transaction.

We were engaged in autumn 2025, before the mandatory date, to assess the exposure and build a compliance roadmap. The key finding: the group faced both an outbound problem (issuing) and an inbound problem (receiving), and the two required different solutions.

How did we structure the compliance strategy?

Our starting point was a gap analysis across all three Polish entities. We mapped invoice volumes, ERP configurations, and the existing VAT reporting chain – including Jednolity Plik Kontrolny (Standard Audit File for Tax, JPK) submissions to the National Tax Administration (Krajowa Administracja Skarbowa, KAS). The analysis took two weeks and produced a priority matrix. The Silesia entity, with the highest invoice volume, was treated as the pilot.

For the outbound workflow, we advised connecting the Silesia ERP to the KSeF API rather than using the manual web portal. API integration means invoices are sent to the National Court Register-linked KSeF platform automatically, receive a unique KSeF number, and are available to the buyer within seconds. The integration project was scoped at roughly 80 hours of IT work. That is a one-time cost. The alternative – manual portal entry for hundreds of invoices per month – would have required a dedicated staff member indefinitely.

For the inbound workflow at the German parent, we recommended a lighter solution. The parent was not a Polish VAT taxpayer, so it had no KSeF registration obligation. However, it needed to store KSeF reference numbers against each Polish invoice in its SAP system. We drafted a data-mapping protocol that extracted the KSeF number from the XML envelope and inserted it into a custom SAP field. This took three days to implement. We also drafted updated standard purchase-order terms requiring Polish suppliers to transmit invoices via KSeF and to include the KSeF number in any accompanying correspondence.

Transfer pricing documentation was a secondary concern. The group had intercompany service agreements between the German parent and the Polish entities. Those agreements referenced invoice procedures. We updated the relevant clauses to reflect KSeF compliance as a contractual obligation – relevant for any future KAS audit or transfer pricing review.

What did the implementation process reveal?

Three findings stood out. First, the Polish Financial Supervision Authority (Komisja Nadzoru Finansowego, KNF) has no direct role in KSeF – but several of the client's Polish entities held licences that required periodic regulatory filings. Those filings referenced VAT compliance status. A KSeF failure could therefore affect licence-renewal assessments indirectly. That risk had not been identified before our engagement.

Second, the Małopolska entity had been issuing invoices under a VAT exemption for certain intra-group services. Those invoices are outside KSeF's mandatory scope for now – but the exemption boundary is narrow. We flagged that any expansion of the service scope could bring those invoices within the mandatory perimeter, requiring immediate API integration for that entity too. We secured a reversal of an incorrectly assessed VAT surcharge of approximately PLN 180,000 for the Silesia entity during the same engagement (autumn 2025) – a separate matter that arose from a KAS spot-check triggered by the transition period.

Third, the German parent's accounts-payable team needed training. KSeF invoices are legally valid only in their XML form. A printed or PDF version is a copy for reference only. Approving a PDF and filing it as the original document – as the team had been doing – is a compliance error under Polish tax law. We ran a 90-minute remote session for the AP team in Munich and produced a one-page reference card they could keep at their desks.

The full implementation, from initial gap analysis to signed-off ERP integration and staff training, took eleven weeks. The group met the 1 February 2026 mandatory date with all three Polish entities compliant.

What are the transferable lessons for German businesses?

KSeF is not a Polish administrative curiosity. It is a structural change to how invoices exist legally in Poland. The document is not a PDF. It is a data record held on a government server. That shift has direct consequences for any German business that buys from, sells to, or owns entities in Poland.

Four lessons apply broadly:

  • Register your Polish entities for KSeF API access before you need it – not after the first compliance failure.
  • Update your purchase-order terms to require KSeF-format invoices from all Polish suppliers.
  • Train your accounts-payable team on the legal status of XML invoices versus PDF copies.
  • Review intercompany agreements for invoice-procedure clauses that may now be outdated.

German businesses with Polish operations that also use IP Box regimes or have transfer pricing arrangements should pay particular attention. KAS audits increasingly cross-reference KSeF data against JPK_CIT filings. A mismatch between invoice records and the consolidated tax return can trigger a full transfer pricing investigation. The compliance cost of prevention is a fraction of the cost of a KAS audit. For comparable situations in neighbouring markets, see our analysis of what KSeF means for your business in Slovakia and what KSeF means for your business in Sweden.

One further point on enforcement: Polish tax law gives KAS the authority to deny input VAT deductions where KSeF compliance cannot be demonstrated. That denial is not a fine – it is a permanent loss of a tax asset. It forfeits VAT already paid and cannot be recovered retroactively. For a group running significant volumes of Polish procurement, that exposure accumulates quickly. If you are also dealing with cross-border enforcement matters, our guide on enforcing a Germany judgment in Poland step by step addresses the procedural framework.

The practical checklist for a German business starting this process today:

  • Identify all Polish VAT-registered entities and their current KSeF registration status.
  • Audit invoice volumes to determine whether API integration or the web portal is appropriate.
  • Map KSeF reference numbers into your ERP or accounting system.
  • Review Polish supplier contracts for invoice-format requirements.
  • Schedule AP team training before the next Polish audit cycle.

Your specific situation – the number of Polish entities, their VAT status, and your ERP architecture – determines how much of this you can handle internally and how much requires specialist input from a tax advisor in Warsaw with direct KSeF experience.

To discuss how KSeF applies to your Polish operations, email info@kordeckipartners.com.

Frequently asked questions

Q: Does KSeF apply to German companies that only buy from Polish suppliers, without owning a Polish entity?

A: KSeF registration is an obligation for Polish VAT taxpayers, not for foreign buyers. However, a German company receiving KSeF-format invoices must handle the XML correctly. Discarding the KSeF reference number and filing only a PDF copy creates a documentation gap that can affect VAT reclaim procedures under Polish tax law. Foreign buyers should update their invoice-receipt workflows even without a Polish VAT registration.

Q: How long does KSeF API integration typically take for a mid-sized ERP system?

A: For a standard SAP or Microsoft Dynamics environment, integration typically takes between four and twelve weeks, depending on the volume of invoice types and the availability of internal IT resources. The KSeF API is publicly documented by the Polish Ministry of Finance. Many ERP vendors now offer pre-built connectors, which can reduce the timeline to two to four weeks. Budget for testing and parallel running before switching off the old workflow.

Q: Is a family foundation in Poland affected by KSeF obligations?

A: A Polish family foundation (fundacja rodzinna) that conducts permitted business activity and is registered as a VAT taxpayer falls within the KSeF mandatory scope on the same basis as any other entity. Foundations that operate solely as passive holding vehicles and are not VAT-registered are outside the mandatory perimeter for now. The boundary depends on the foundation's actual activity profile and VAT registration status – a point worth confirming with a Polish tax advisor before assuming an exemption applies.

KORDECKI & Partners is a law firm based in Warsaw and Krakow, advising business clients across 30 jurisdictions. Our team combines expertise in Polish and international law with a practical approach to tax compliance, KSeF onboarding, and cross-border advisory for German-market clients. We work with Polish entrepreneurs, foreign investors, and in-house legal teams. To discuss your situation, contact info@kordeckipartners.com.

Disclaimer: This publication is provided for informational purposes only and does not constitute legal advice. The information herein should not be relied upon as a substitute for professional legal counsel tailored to your specific circumstances. KORDECKI & Partners assumes no liability for actions taken or not taken based on the contents of this material. For advice regarding your particular situation, please contact info@kordeckipartners.com.