JPK period/version mismatch: choose V7(2) or V7(3)
Fix JPK V7 period and version mismatches. Choose the correct historical schema, review monthly evidence and quarterly declarations, and keep KSeF separate.
Start with the period being corrected
JPK-PERIOD-VERSION means the selected V7 package and the header reporting month disagree. A correction created today can still concern January 2026. That period belongs to version (2), even when the correction file is generated after the February transition. Choosing a package merely from the file creation date can therefore select the wrong namespace and header variant.
MF / KAS states that V7M(3) and V7K(3) apply from 1 February 2026, while version (2) covers periods through January 2026. This validator pins the older pair to January 2022 through January 2026. Earlier version (1) files are outside the supported packages. A document from another era should be reviewed with its applicable official schema instead of being relabelled to obtain a passing result.
Keep namespace, form and variant together
The XML namespace identifies a particular published structure. KodFormularza, its kodSystemowy attribute and WariantFormularza must describe the same package. Changing only the number in WariantFormularza does not migrate the document: fields and choices can differ too. Version (3), for example, introduces the row branches NrKSeF, OFF, BFK and DI and includes K_360 in the sales-control calculation.
For a fictional monthly file with Rok 2026 and Miesiac 1, select JPK_V7M(2) and export using that complete structure. For February 2026, use JPK_V7M(3). A missing KodFormularza is a separate structural defect: our XSD-error example deliberately omits it. The independent test schema rejects that fixture at the Naglowek content sequence; it does not reproduce the full official MF contract.
Quarterly does not mean one quarterly evidence month
V7K still carries monthly evidence in Miesiac. Its quarterly declaration belongs to the final month of the appropriate quarter. The lite quarter check compares that month with Deklaracja/Naglowek/Kwartal; it does not combine three monthly files or prove that the declaration reconciles with earlier evidence. A February evidence-only V7K file is therefore different from a March file containing the first-quarter declaration.
Submission purpose is checked independently. The selected V7 packages accept purpose 1 or 2; JPK_FA(4) has a different purpose constraint and is not a V7 return. Do not infer that a document has been accepted because its purpose and period look consistent. Taxpayer status, signing, submission and UPO remain outside these checks.
Repair in the exporter and rerun each layer
Confirm the intended reporting month in the source ledger before regenerating XML. Select the matching monthly or quarterly export mode, then use the correct version as one coordinated setting. Keep a copy of the failing fictional example when integrating a fix into an ERP regression suite. A test should assert the expected rule code and location as well as the final layer state.
The default sample runs independent rules on your device and explicitly leaves XSD unexecuted. An authorised complete local schema package enables a separate schema result, including provenance and SHA256 for each supplied import. A matching root hash proves byte identity only. It does not grant usage rights or prove that all imported files are official, complete or applicable. Review the current MF download page when preparing a real filing.
Before and after
Before: independent rule fails
<Miesiac>1</Miesiac> <!-- with V7M(3): wrong period -->After: this field passes
<Miesiac>2</Miesiac> <!-- V7M(3): period boundary passes -->Fictional failing XML · Passing rule-only demo · Expected codes and locations
Primary sources and exact scope
MF / KAS JPK structures identifies current and historical V7 packages and the separate FA(4) structure. The official V7M(3) XSD and official FA(4) XSD define the factual fields used by the independent explanation. Sources rechecked 6 November 2026. No protected explanatory text or official rule pack is copied here.
The schema, independent business, plausibility and unchecked fiscal / submission layers remain separate. This page describes supported technical checks for Polish administrations; it does not create a JPK obligation in another country.
Recheck the corrected export
Poland JPK validator · Walidator JPK Polska · Related JPK repair guide