A Chicago-based technology company invoices its Polish subsidiary every quarter. The invoices flow smoothly through email, PDFs land in inboxes, and the accounting team reconciles everything at month-end. Then Poland's mandatory e-invoicing system goes live – and suddenly that familiar process no longer meets Polish legal requirements. The subsidiary must receive and issue invoices through a government platform. The US parent must adapt its systems, or face disruption to the entire billing relationship.

Poland's National e-Invoice System – Krajowy System e-Faktur (KSeF) – is a centralised government platform through which all VAT-registered entities in Poland must issue structured electronic invoices. Mandatory KSeF compliance applies from 1 February 2026 for large taxpayers and from 1 April 2026 for all remaining VAT payers. Any US business with a Polish subsidiary, branch, or direct VAT registration is directly affected. Non-compliance triggers financial penalties and disrupts the right to deduct input VAT.

This guide explains the KSeF framework step by step: what the system is, how it changes invoice workflows, what US businesses must do to comply, and where the most common mistakes occur. It also covers three practical business scenarios – manufacturing, technology, and cross-border investment – and answers the questions US-based finance and legal teams most frequently raise.

What is KSeF and why does it affect US businesses operating in Poland?

KSeF is the Polish tax authority's answer to the EU's push for real-time transaction reporting. Administered by the National Revenue Administration (Krajowa Administracja Skarbowa, KAS), the system requires every structured invoice – faktura ustrukturyzowana – to be submitted through a single government portal before it is considered legally issued. The Ministry of Finance (Ministerstwo Finansów) sets the technical standards. The National Court Register (Krajowy Rejestr Sądowy, KRS) holds the entity data that KSeF uses to authenticate taxpayers. A US company whose Polish entity is registered with the KRS and holds a Polish VAT number is subject to these rules from the mandatory go-live date.

The practical shift is significant. Under the old model, a US parent could email a PDF invoice to its Warsaw subsidiary and the transaction was valid. Under KSeF, that same invoice must be submitted in a structured XML format (FA(2) schema), assigned a unique KSeF identification number, and only then treated as legally issued. The buyer – the Polish entity – can only deduct input VAT from invoices that carry a valid KSeF number. An invoice without that number is, for VAT purposes, as if it were never issued.

Three categories of US businesses face the most immediate exposure. First, US multinationals with Polish subsidiaries that issue intercompany invoices to the Polish entity. Second, US companies with a direct Polish VAT registration – common in e-commerce or distribution. Third, US investors whose Polish holding or operating companies invoice Polish customers. All three must redesign their invoicing workflows before the mandatory deadline.

  • Obtain a KSeF token or authorise a qualified e-invoice service provider
  • Map all invoice flows touching the Polish VAT number
  • Convert ERP output to FA(2) XML schema
  • Test submission via the KSeF test environment (available from KAS)
  • Train finance staff on the new receipt and archiving rules

For deeper context on Polish VAT obligations and how they interact with US tax positions, see our overview of Polish tax law practice.

How does the KSeF implementation timeline work – and what are the penalties?

The mandatory KSeF timeline has two distinct phases. Large taxpayers – those whose annual turnover exceeded PLN 200 million in the preceding tax year – must comply from 1 February 2026. All other VAT-registered entities follow on 1 April 2026. A voluntary KSeF regime has been available since January 2022, giving businesses time to test integration. Most US-owned Polish entities that have not yet migrated are now in the final preparation window.

Penalties for non-compliance are structured by the Ministry of Finance regulations and can reach up to 100% of the VAT amount shown on a non-compliant invoice. That figure is not a theoretical maximum – KAS auditors apply it where deliberate circumvention is found. Even unintentional technical failures attract fines of up to PLN 4,000 per invoice. For a US technology company issuing dozens of intercompany invoices monthly, cumulative exposure can exceed PLN 100,000 within a single quarter. The right to deduct input VAT on received invoices is also suspended until the invoice is properly processed through KSeF.

There is a narrow grace period built into the regulations. During the first three months after the mandatory start date, KAS has indicated it will apply a reduced enforcement posture for good-faith technical failures – but this does not suspend the penalty framework. It simply affects the likelihood of immediate audit action. US businesses should treat this as a buffer for resolving integration bugs, not as permission to delay preparation.

We secured a reversal of a VAT surcharge exceeding PLN 2.4 million for a US-owned manufacturing client in the Mazowieckie region (autumn 2025). The surcharge arose from a predecessor invoicing system that failed to meet earlier structured invoice requirements. Early remediation – before the mandatory KSeF deadline – would have avoided the dispute entirely.

What steps must a US business take to achieve KSeF compliance?

Compliance is a five-stage process. Each stage has a defined output. Missing any stage creates downstream failure – the system will reject submissions, and rejected submissions are not legally issued invoices.

Stage 1 – Entity authentication. The Polish entity must be authenticated in the KSeF portal. Authentication is tied to the entity's NIP (tax identification number) and requires either a qualified electronic signature, a trusted profile (Profil Zaufany), or a KSeF token. US-based signatories who are not Polish residents typically use the token route, which requires advance registration through KAS. Allow at least 10 business days for token issuance.

Stage 2 – ERP and billing system adaptation. The FA(2) XML schema has over 300 mandatory and optional fields. Most US ERP systems – SAP, Oracle, Microsoft Dynamics – have KSeF connectors available, but configuration requires localisation expertise. The schema must capture Polish-specific fields including the buyer's NIP, the seller's NIP, the invoice type code, and the VAT rate breakdown. A mismatch in any mandatory field causes immediate rejection.

Stage 3 – API integration or service provider engagement. KSeF operates via a REST API. Large entities typically integrate directly. Smaller Polish entities often use a certified e-invoice service provider (dostawca usług KSeF). For US businesses managing this remotely, the service provider route reduces technical risk, but the US parent must grant formal authorisation in the KSeF portal – a step that requires a Polish-language legal instrument.

Stage 4 – Testing. KAS provides a test environment that mirrors production. Run at least 30 test submissions across different invoice types before go-live. Pay particular attention to credit notes (faktury korygujące) and advance invoices, which have distinct schema requirements.

Stage 5 – Archiving. KSeF stores invoices for 10 years. The Polish entity retains the right to download its own invoice archive. US parents should ensure their document retention policies align with this 10-year obligation under Polish tax law.

How does KSeF interact with transfer pricing and intercompany structures for US groups?

This is where KSeF moves from an IT project to a legal and tax strategy question. US multinationals operating in Poland routinely use intercompany invoices for management fees, IP royalties, shared services, and intragroup financing. All of these, if issued by or to a Polish VAT-registered entity, must flow through KSeF from the mandatory date. The interaction with transfer pricing documentation creates a new compliance layer.

Under Polish tax law, intercompany transactions exceeding PLN 10 million per year require a local transfer pricing file. That file must now reference KSeF invoice numbers for the documented transactions. A mismatch between the transfer pricing documentation and the KSeF invoice record – for example, a management fee described differently in each – can trigger a KAS audit. The audit scope typically expands to include the full intercompany structure, not just the invoicing discrepancy.

IP Box regimes add another dimension. A US group using a Polish entity to hold intellectual property and benefit from the Polish IP Box regime (5% CIT rate on qualifying IP income) must ensure that royalty invoices issued under the IP Box structure meet KSeF requirements. An IP Box claim supported by non-KSeF-compliant invoices is vulnerable to challenge. The Polish tax authority has indicated that invoice integrity is a prerequisite for preferential regime claims.

For US investors considering restructuring their Polish holding structure to optimise both KSeF compliance and tax efficiency, our analysis of restructuring options for US-market entities provides a useful framework. Transfer pricing alignment and KSeF readiness should be addressed in parallel, not sequentially.

Our team obtained interim protection of a transfer pricing dispute for a US technology group with operations in Lower Silesia (spring 2026). The dispute centred on royalty invoices that predated KSeF but were being reviewed under the new audit framework. Early KSeF alignment of the post-2026 invoice series materially strengthened the group's compliance position.

What are the three most common mistakes US businesses make with KSeF?

Complexity produces predictable failure patterns. Three mistakes account for the majority of KSeF compliance failures among US-owned Polish entities.

Mistake 1 – Treating KSeF as an IT project only. Finance teams hand the project to IT, IT integrates the API, and no one reviews whether the invoice content meets Polish VAT law. KSeF rejects structurally invalid XML, but it does not validate substantive content. An invoice with the wrong VAT rate, a missing NIP, or an incorrect transaction description will be accepted by the system but will still be legally defective. The error surfaces only during a KAS audit – typically 12 to 36 months later.

Mistake 2 – Ignoring the authorisation chain. KSeF requires explicit authorisation for each person or system that submits or receives invoices on behalf of the Polish entity. US-based CFOs who sign Polish tax returns often assume their existing authority covers KSeF. It does not. A separate KSeF authorisation must be registered in the portal. Submissions made without valid authorisation are treated as null – the invoice is not legally issued, and no VAT deduction is available.

Mistake 3 – Overlooking the family foundation interaction. US founders who have established a Polish fundacja rodzinna (family foundation) and use it as a holding vehicle may find that the foundation's transactions with operating subsidiaries require KSeF compliance. Polish family foundations established since May 2023 can conduct limited business activity. Where that activity generates VAT-able transactions, KSeF applies. Many foundation administrators have not yet addressed this.

A practical self-assessment: if your Polish entity issued more than 50 invoices in the past 12 months, or if it receives intercompany invoices from a US parent, KSeF compliance is not optional preparation – it is an immediate legal requirement from the go-live date. For a broader view of how Polish and US tax treaty positions interact, see our analysis of the double tax treaty key provisions.

To receive an expert assessment of your Polish entity's KSeF readiness, contact info@kordeckipartners.com.

Frequently asked questions

Q: Does KSeF apply to a US company that is not VAT-registered in Poland but invoices a Polish customer?

A: KSeF applies to entities registered for VAT in Poland. A US company without a Polish VAT registration is not directly required to submit invoices through KSeF. However, the Polish customer – if VAT-registered – can only deduct input VAT from invoices that carry a KSeF number. In practice, Polish buyers are beginning to require KSeF-compliant invoices from all suppliers, regardless of origin. US exporters to Poland should monitor this commercial pressure even if they have no direct legal obligation.

Q: How long does KSeF implementation take for a mid-sized US-owned Polish subsidiary?

A: A mid-sized entity with an established ERP system typically requires between 8 and 14 weeks for full KSeF implementation – covering entity authentication, schema configuration, API integration, testing, and staff training. Entities using legacy billing systems or manual invoicing may require 16 to 20 weeks. The single most common cause of delay is obtaining the KSeF token for a US-based signatory, which requires advance coordination with KAS and should be initiated at least six weeks before the target go-live date.

Q: Is the tax advisor Warsaw market well-equipped to assist US businesses with KSeF?

A: Warsaw-based tax advisory practices with international client bases have developed significant KSeF expertise since the voluntary regime launched in 2022. The key differentiator is whether the advisor can bridge Polish VAT law, ERP configuration, and US group reporting requirements simultaneously. US businesses should look for advisors with experience in both KSeF technical implementation and transfer pricing documentation, since the two compliance streams interact directly. A tax advisor Warsaw engagement that covers only one stream creates gaps that surface during audit.

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 structuring. We work with Polish entrepreneurs, foreign investors, and in-house legal teams. To discuss your situation, contact info@kordeckipartners.com.

Katarzyna leads the firm's tax practice. She spent nine years in a Big Four tax department. Her practice spans CIT/PIT/VAT advisory, KSeF onboarding, JPK_CIT, Pillar Two, IP Box, transfer pricing, KAS audits, and tax-court litigation (WSA/NSA). She has structured eight family foundations since May 2023.

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.