Summary
- Poland has released version 5.5.1.v1 of its e-invoicing technical specification, refining the KSeF API interface.
- Error code 99 for HTTP 400 (Bad Request) responses has been removed, and “kwota przychodu” (revenue amount) is now available as an authorisation parameter in selected schemas.
- No new invoicing obligations are introduced, but software providers and API integrators must adapt their integrations.
Article
Article The Polish Ministry of Finance has published an updated version of the JPK services interface specification (v5.5.1.v1), continuing the incremental refinement of the KSeF technical framework ahead of the mandatory e-invoicing rollout. The update is technical in nature and does not modify the underlying legal obligations for taxpayers.
Two changes stand out. First, error code 99 for HTTP 400 (Bad Request) responses is withdrawn, aligning error handling with the actual behaviour of the API. Second, taxpayers may now use the revenue amount (“kwota przychodu”) as an authorisation element in selected schemas — a change welcomed by natural persons and micro-entities that do not rely on qualified signatures or ZAW-FA authorisations. While the update is transparent for end-users, ERP vendors, invoicing software providers and integrators should update their KSeF connectors accordingly.
Source














