Poland KSeF for SAP: DRC Scope and Compliance Delivery

Poland’s Krajowy System e-Faktur (KSeF, the National e-Invoice System) makes structured electronic invoicing mandatory for VAT-registered businesses in Poland. SAP finance, tax, SD, FI, and Basis teams need a controlled way to prepare invoice data, validate mandatory fields, submit invoices to KSeF, and handle authority responses without losing traceability to SAP source documents.

How should SAP teams handle Poland KSeF compliance?

An SAP team should first confirm which Polish entities and invoice flows fall within KSeF, then verify the supported SAP scenario and prerequisites in its own release. The implementation path—SAP DRC, an SAP-native extension, a provider, or a hybrid—should follow that evidence, with lifecycle testing and authority-response monitoring before go-live.

01ScopeConfirm entities, transaction types, issuing and receiving obligations, exclusions and deadlines.

02SAP verificationCheck the exact SAP product, edition, release, components, Notes and supported country scenario.

03Architecture decisionSelect SAP DRC, an SAP-native extension, a provider or a controlled hybrid only after system evidence is available.

04Lifecycle integrationDesign FA(3) mapping, authentication, submission, receipt, corrections, KSeF identifiers and offline modes.

05TestingTest business scenarios, validation failures, authority responses, retries, outages and reconciliation.

06Production evidenceRetain decisions, test evidence, responses, exceptions and operational ownership after go-live.

SAP DRC is not automatically the correct path for every landscape. The decision depends on the customer’s SAP product, edition, release, supported scenario, document flows and operating model. See the DRC Sprint evidence workflow, implementation services and country mandate portfolio.

Evaluating Poland KSeF for your SAP landscape? In force: FA(3) mandatory

Answers to the questions most evaluation emails ask before you write one.

Landscapes assessed

SAP ECC and SAP S/4HANA; release, edition, installed components and country scenario are reviewed before any support commitment

Delivery model

Confirmed per product and landscape: an on-stack S4FN Add-on, a side-by-side S4FN extension on SAP BTP, or SAP Integration Suite connectivity

Commercial scope

Confirmed in the written proposal by country, legal entities, systems and usage scope

Engagement sequence

Scope review → landscape fit check → written implementation proposal

Get pricing and a 20-minute technical call

Your SAP releaseSAP ECC 6.0S/4HANA on-premiseS/4HANA private cloudS/4HANA public cloudMixed landscapeNot sure yet

Request pricing and a call Country: Poland (auto-filled) · We reply with the most practical next step

The Compliance Challenge in Poland

KSeF is Poland’s answer to its VAT gap: instead of exchanging invoices directly, suppliers submit structured XML invoices to a central government platform, which validates each invoice, assigns it an official KSeF number, and makes it available to the buyer. An invoice only exists legally once KSeF has accepted it, a fundamental change to how SAP billing output is treated.

The system ran as a voluntary option from January 2022 and the mandatory start was postponed several times (originally July 2024) after performance and legal concerns. Under the law as amended in 2025, the mandatory rollout is now phased (as of July 2026):

• 1 February 2026: issuing through KSeF became mandatory for large taxpayers whose 2024 gross sales exceeded PLN 200 million. From this date all businesses must be able to receive invoices through KSeF, regardless of when their issuing obligation starts.
• 1 April 2026: issuing became mandatory for all other VAT-registered businesses, including SMEs and sole proprietors.
• Temporary relief through 31 December 2026: a taxpayer whose total gross value of invoices issued in a month does not exceed PLN 10,000 may use the statutory temporary issuing relief. This is a monthly ceiling, not a blanket micro-business exemption. From 1 January 2027 the temporary relief ends; current penalty rules must be checked separately.

Receiving, Temporary Relief and Exclusions

• Receiving: in-scope taxpayers must be able to receive KSeF invoices from 1 February 2026, even where their own issuing phase began later.
• PLN 10,000 relief: the temporary rule applies by total gross invoices issued in a month and lasts only through the end of 2026.
• B2C: invoices to consumers are outside mandatory KSeF.
• Establishment: specified foreign taxpayers without a Polish establishment, or whose Polish fixed establishment does not participate in the transaction, are outside mandatory issuing.
• Special schemes: statutory exclusions include specified OSS/IOSS and EU SME-scheme cases. Apply the official scope rules to the exact taxpayer and transaction.

Technical baseline: since 1 February 2026 every invoice must conform to the FA(3) XML schema (over 300 defined fields), which fully replaced FA(2). Invoice visualisations carry a QR code so recipients can verify authenticity against KSeF.

Business continuity is part of the mandate design. The offline24 mode lets a seller issue an invoice offline (for example during a connectivity problem) and submit it to KSeF no later than the next business day; the legal issue date remains the actual issuance date. Separate offline and failure modes cover announced maintenance windows and officially declared KSeF outages, with up to 7 working days to submit after a declared failure ends. SAP teams need to decide in advance how billing, output management, and QR-code handling behave in each mode.

How S4FN Supports This in SAP

1. Reads relevant SAP invoice, tax, and master-data fields.
2. Maps required fields to the FA(3) structure, including corrective invoice logic.
3. Supports validation and error handling before submission.
4. Prepares the submission workflow and KSeF number capture.
5. Tracks authority responses, rejections, and exceptions for SAP team follow-up.

SAP Compatibility & Technical Scope

SAP ECC	To be confirmed during technical review.
SAP S/4HANA	To be confirmed during technical review.
Relevant SAP modules	FI, SD, tax configuration, master data, and Basis connectivity.
Integration method	SAP-native e-invoice workflow; exact KSeF integration points to be confirmed.
Prerequisites	SAP release, invoice scenarios, KSeF authentication (certificates/tokens), and connectivity.
Implementation considerations	FA(3) field mapping, corrective invoice process, offline24/outage handling, buyer-side invoice retrieval, and KSeF number storage for payment references.

Security & Data Handling

S4FN is designed to keep compliance processing aligned with SAP source transactions and customer-controlled workflows. Exact deployment, data residency, and authority communication flow must be confirmed during technical review.

DRC Sprint Country Compliance Pack

Poland: turn mandate scope into SAP delivery

The Poland pack connects KSeF e-invoicing requirements to system evidence, architecture decisions, implementation work and operational controls.

Requirement→Evidence→Decision→Implementation→Operation

Download the Poland Implementation Brief Assess your SAP landscape

What the pack connects

• 01Mandate controlsScope, scenarios, deadlines and exceptions
• 02SAP evidence checksRelease, component, configuration, data and process evidence
• 03Delivery assetsDecision records, test scenarios, work packages and operating controls

Poland focus: FA(3) mapping, KSeF identifiers, offline modes, response lifecycle, authentication and reconciliation.

Review Poland KSeF for Your SAP Landscape

Confirm invoice scope, FA(3) mapping, response handling, and implementation prerequisites with S4FN. Related reading: SAP integration architecture for e-invoicing and statutory reporting, and Poland SAF-T / JPK integration for SAP.

Primary Source and Verification

Verified on: 10 July 2026. Confirm taxpayer establishment, transaction exclusions, the monthly relief test and current KSeF technical package before implementation.

• Polish Ministry of Finance: scope of mandatory KSeF 2.0