POLAND · JPK · LOCAL LITE / BYO

Poland JPK validator

Catch an export mismatch before another correction round. Separate V7 returns and FA invoice records, built for Polish accounting offices and ERP teams.

Runs on this device. No XML upload. Independent rules demo; XSD not executed.

Polski · English

Check your JPK export

One file free. Existing Pro / Team limits: up to 25 / 100 files per batch, 50 MB total. Selected files take precedence over pasted XML. No ZIP.

XSD · authorised local package

Official schemas import external type and code-list files. No complete official package is redistributed. Supply every required XSD locally only with sufficient processing and modification rights; public access, BYO and matching hashes do not grant rights. No automatic downloads.

Official MF / KAS downloads · Provenance and rights boundary

For every file: path, HTTPS source, publisher, version / validity period, acquisition date, concrete rights and notices. Replace the example and add one record for each import. SHA256 is calculated locally. Original absolute import URLs are mapped only to explicitly supplied matching namespaces. Absolute includes need an exact supplied source-URL match; relative paths stay inside the local package. Limits: 1 MB per XSD, 10 MB total; no ZIP, DTD, entity expansion or implicit fetch.

XML, identifiers and amounts stay in this tab. Reports use file indices. Only the last profile and sample choice are remembered locally; analytics receives fixed events only.

Ready · no checks executed.

Five pinned versions, two separate packages

Verified with MF / KAS on 6 November 2026: V7M(3) and V7K(3) apply from February 2026; V7M(2) and V7K(2) cover January 2022 through January 2026. Corrections follow the reporting period, not the date you run this tool. V7K evidence is monthly; a quarterly declaration belongs to the final month of the matching quarter.

JPK_FA(4) is a separate invoice-data export. It is not KSeF FA(3), and a KSeF invoice cannot replace a JPK return. This tool does not cover other JPK types.

Read each layer separately

No proof of correct fiscal qualification, VAT liability, taxpayer registration, successful submission or UPO. Full declaration formulas and cross-month quarter reconciliation are unchecked. Unknown profiles never receive a complete green result.

Fictional examples with known outcomes

The primary action runs the selected package sample. These independently authored rule-only files are not filing templates and have no established official XSD validity. Each package has a passing rule demo, a control-total error and a missing KodFormularza XSD-error fixture. The latter is executed against our own MIT test subset, clearly distinct from MF.

All five packages: expected codes / locations · V7M(3) demo · V7K(3) demo · FA(4) demo · Independent test XSD · not MF

Repair the export at the right layer

JPK period / version mismatch · JPK control totals and FP rows

Primary sources and notices

MF / KAS · Struktury JPK · JPK_V7M(3) XSD · JPK_V7K(3) XSD · JPK_FA(4) XSD · MF reuse conditions · Artifact and engine notices

MF reuse conditions require source, production/acquisition time, changes and known author. The gov.pl text footer is not treated as a licence for each schema/import. Unresolved imported type/code-list rights remain a separate open decision; no protected rule pack, Schematron or new engine/plugin is shipped.

One client file, then the batch

One local check is free. Pro / Team uses existing batch access, limits and checkout. Each file gets its own outcome; CSV / JSON records versions, scope and schema provenance. No new client-account model. Local checks consume no server validation quota.

Pro / Team plans · API / CLI scope · KSeF FA(3)