Menu

Blog — Vedron

Poland’s e-Sprawozdanie is the structured XML format for annual financial statements, submitted to the KRS (National Court Register) e-Sprawozdania system. Getting the data into the correct XML is most of the work. It is not the whole process, and we are clear about where automation stops.

What a real e-Sprawozdanie requires

Correctly structured XML matching the current schema version, built from your actual ledger data. Balance sheet, profit and loss, supporting notes — all reconciling with your books rather than looking plausible.

And a qualified electronic signature (XAdES) has to be applied to the document, and the signed file has to be submitted to KRS.

What runs today in Vedron

Vedron generates the e-Sprawozdanie XML directly from your ledger, matching the schema Poland’s filing system expects. You are not building the document by hand or reconciling it against your books after the fact.

Direct about scope: the XML this produces is unsigned by design. Applying the qualified electronic signature and submitting the signed file to KRS remain manual steps today, performed by your tax advisor or signatory. That is the correct split under current Polish rules: the preparation is automated, the attestation is human.

Common questions

Does this submit my filing to KRS automatically? No. It generates the correctly structured XML; the qualified signature and submission are manual steps.

What schema version does this target? The current e-Sprawozdania XML schema. Schemas get updated, so confirm your build matches the current filing year’s requirements.

Does this work for Polish companies on UOR? Yes. It is built against the same UOR-based ledger your Polish reporting already uses.

Talk to us about your setup

Book a short call. Beta clients get two months of custom setup on us.

All posts

Poland's e-Sprawozdanie — what Vedron prepares and what your accountant signs

28. Juli 20262 min read
Poland's e-Sprawozdanie — what Vedron prepares and what your accountant signs

Poland’s e-Sprawozdanie is the structured XML format for annual financial statements, submitted to the KRS (National Court Register) e-Sprawozdania system. Getting the data into the correct XML is most of the work. It is not the whole process, and we are clear about where automation stops.

What a real e-Sprawozdanie requires

Correctly structured XML matching the current schema version, built from your actual ledger data. Balance sheet, profit and loss, supporting notes — all reconciling with your books rather than looking plausible.

And a qualified electronic signature (XAdES) has to be applied to the document, and the signed file has to be submitted to KRS.

What runs today in Vedron

Vedron generates the e-Sprawozdanie XML directly from your ledger, matching the schema Poland’s filing system expects. You are not building the document by hand or reconciling it against your books after the fact.

Direct about scope: the XML this produces is unsigned by design. Applying the qualified electronic signature and submitting the signed file to KRS remain manual steps today, performed by your tax advisor or signatory. That is the correct split under current Polish rules: the preparation is automated, the attestation is human.

Common questions

Does this submit my filing to KRS automatically? No. It generates the correctly structured XML; the qualified signature and submission are manual steps.

What schema version does this target? The current e-Sprawozdania XML schema. Schemas get updated, so confirm your build matches the current filing year’s requirements.

Does this work for Polish companies on UOR? Yes. It is built against the same UOR-based ledger your Polish reporting already uses.

Talk to us about your setup

Book a short call. Beta clients get two months of custom setup on us.

Did you enjoy this article?