Poland Standard Audit File for Tax (SAF-T / JPK) Integration for SAP
Poland Standard Audit File for Tax (SAF-T), handled through the JPK (Jednolity Plik Kontrolny) file family, requires structured statutory data in defined XML formats, some filed periodically, some on demand, and, since 2025, accounting ledgers filed annually. SAP finance and tax teams need controlled data selection, mapping, validation, and traceability from accounting and VAT records to required file output.
Key dates
31 Jul 2026
First JPK_CIT filing deadline for large CIT payers
Tax years from 2026
JPK_CIT extends to other JPK_V7 filers (tax years after 31 Dec 2025)
Tax years from 2027
JPK_CIT extends to all remaining CIT payers (tax years after 31 Dec 2026)
At a glance
- Mandate: JPK VAT + SAF-T reporting (periodic, on-demand, and annual JPK_CIT)
- Platform / channel: Ministry of Finance JPK gateway
- Authority: Ministry of Finance / KAS
- SAP scope: FI, SD, MM, tax config, master data + Basis
Evaluating Poland SAF-T / JPK for your SAP landscape? In force: scope expanding
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
The Compliance Challenge in Poland
Poland runs one of Europe’s broadest SAF-T programs, and the obligation is growing in layers rather than being replaced (as of July 2026):
- JPK_V7M/V7K: the combined VAT register and return, filed monthly or quarterly by all VAT-registered businesses, the recurring workload.
- On-demand structures (accounting books, bank statements, warehouse, invoices): submitted when the authority requests them during a control, so mapping readiness matters even between requests.
- JPK_CIT, the new layer: for tax years starting after 31 December 2024, tax capital groups and CIT taxpayers whose prior-year revenue exceeded EUR 50 million enter the first phase. Their first JPK_KR_PD files are submitted in 2026; JPK_ST_KR is voluntary only for their 2025 period. Other monthly JPK_VAT filers enter for years starting after 31 December 2025, followed by remaining taxpayers for years starting after 31 December 2026. A February 2026 regulation extends the first wave’s accounting-book deadline to the end of the seventh month after year-end only for the entities and periods covered by its wording.
- Data scope tightens over time: from 2026 tax years, JPK_CIT data expands to include counterparty tax IDs, KSeF invoice numbers, and detailed accounting-to-tax difference categories, tying the accounting file directly to the e-invoicing system.
The SAP implication: JPK is no longer a VAT-only topic. Ledger design, fixed-asset data quality, and tax-difference categorisation in FI now feed statutory files, and inconsistencies between JPK_V7, JPK_CIT, and KSeF data become visible to the authority across systems.
How S4FN Supports This in SAP
- Reads relevant SAP FI, SD, MM, tax, and master-data fields where relevant.
- Maps required fields to the applicable JPK structures.
- Supports validation and error handling before filing.
- Prepares file generation for periodic, on-demand, and annual reporting workflows.
- Tracks responses and follow-up where applicable.
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, MM, tax configuration, master data, and Basis. |
| Integration method | SAP-native SAF-T / JPK reporting workflow; exact integration points to be confirmed. |
| Prerequisites | SAP release, accounting scope, tax data scope, file requirements, and authority workflow. |
| Implementation considerations | JPK_V7 correction workflow, JPK_CIT ledger and fixed-asset mapping, KSeF number capture for 2026+ data scope, and mapping-change governance. |
Security & Data Handling
S4FN is designed to keep compliance processing aligned with SAP source transactions and customer-controlled workflows. Exact deployment, data residency, and file handling must be confirmed during technical review.
DRC Sprint Country Compliance Pack
Poland SAF-T and JPK: connect requirements to SAP delivery
This pack connects SAF-T and JPK reporting requirements to system evidence, architecture decisions, implementation work and operational controls.
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 SAF-T and JPK focus: JPK structures, source ledgers, tax mappings, file generation, validation, submission and corrections.
Review Poland SAF-T / JPK for Your SAP Landscape
Confirm source data, file scope, validation workflow, and implementation prerequisites with S4FN. Related reading: Poland SAF-T readiness guide for SAP and what SAF-T is and how it works in SAP.
Primary Sources and Verification
Verified on: 10 July 2026. Confirm entity classification, tax year, current logical schemas and any transitional deadline before filing.
