New feature v0.60.0
v0.60.0 — The ZUS DRA declaration, ready to file
The previous version computed the contributions, but the declaration itself had to be made elsewhere. From this version Biurko prepares the ZUS DRA: a KEDU file in the KEDU_5_7 schema, or a printout on the official form, together with the steps the eZUS import takes. There is still no sending to ZUS — you file it yourself, and Biurko records that the period was filed.
August 30, 2026 Taxes
- A KEDU file for the month, in the version ZUS accepts today. The declaration is written in the KEDU_5_7 schema (specification EWD 2.27, in force since 25 April 2026) from the figures the contributions screen already shows — not from a second, separate calculation. The schema version is read from the document's namespace, because the “version” attribute inside a ZUS schema file can say something else than the file is.
- A printout on the official form, because that is the second lawful way. A payer settling contributions for no more than five people may file the declaration as a printout — Biurko draws it after the pattern in the ZUS specification: two A4 pages, with the producer, the program and its version on the margins, as the pattern requires.
- A month of contribution holidays is a set of three documents. The law then requires the declaration and two named ZUS RCA reports — one for what the state budget financed, one for what you still paid yourself. The file carries all three, and so does the printout: six pages instead of two.
- The import checklist names the sections of eZUS. Eight steps, including the one easiest to miss: the import wizard creates registration documents of its own that you never sent, and they have to be deleted before you submit.
- Marking the period filed keeps the file. Recording “filed in eZUS” with its date silences the reminders and closes the month, but it does not take away the document you filed with — you can still download and print it afterwards.
- A correction knows which number to introduce itself by. The next set for the same month takes the next declaration identifier from the ZUS dictionary, and two deadlines are computed rather than held as a date: five years from the day the contributions for that month were due, and, for the health part, the end of the second month after the annual tax return was due.
- A declaration does not outlive the month it was built from. If the month changes after the file was built — the scheme, the revenue, the contributions paid — Biurko names the divergence and asks for a rebuild instead of handing out a document that states something no longer true.
- The insured person's details are stated once and kept encrypted. The PESEL (or the type and number of an identity document) and the six-character insurance title code, in exactly the form eZUS shows it. The file and the printout are handed only to someone permitted to state those details.
- The AI assistant can build the declaration. A new MCP tool prepares the file for a given month and answers with a fact — the period, the set number, whether the file is ready — never with the contents of the document.
- What is not there. Biurko does not send the declaration to ZUS, does not sign it and has no access to your eZUS account — you file it yourself, by file or by printout. The annual health-contribution settlement, filed together with the declaration for April, is not computed yet: the April month says so plainly instead of handing out an incomplete document.