Bug fix v0.61.0
v0.61.0 — What Biurko knows, it now says
A release that followed a review of the whole tax path: twelve lenses read code that passed every test. Most of what changed is where Biurko used to stay silent — instead of computing a month from a figure nobody stated, it now says what is missing and where to fill it in. A contractor's VAT status arrived too, because the date the tax falls due under the cash method turns on it.
August 30, 2026 Taxes
- A contractor's VAT status, and the tax point under the cash method. Under the cash method, tax on a sale to a buyer who is not a registered active VAT payer arises no later than the 180th day from delivery — and a NIP does not settle that: an exempt trader has one, so does a deregistered entity. Biurko now reads the status from the Ministry's VAT register and stores it on the contractor together with the day it was read. While the status is unknown we apply the 180-day limit and say so in the register — the safe side is the one where the tax does not wait forever.
- Bad-debt relief refuses when there is no ground for it, instead of claiming it. Where the debtor is not a registered active VAT payer, relief is open only on one of the three grounds of art. 89a ust. 2a — a final judgment put into enforcement, an entry in a national debt register, or declared consumer bankruptcy. Biurko does not hold those facts, so it does not propose such a correction and says why.
- A foreign-currency invoice with no exchange rate no longer goes out. An amount without a rate used to reach the JPK converted one to one — that is, with a base lower than the real one. The file is now withheld with a named reason: art. 31a of the VAT Act says which rate applies, and the taxpayer picks it, not the program.
- A ZUS month that cannot be computed says what is missing. In place of one general "it did not work" there are now named refusals: a declared base below the statutory floor, an unstated base from another title (without it there is no telling whether the Labour Fund is owed), an unstated accident rate, a title code that contradicts the scheme the month was computed under. The month an activity starts is refused on its own: when the insurance title begins mid-month the lowest base is reduced in proportion to the days (art. 18 ust. 9 of the social-insurance act), Biurko does not compute that yet — and says so plainly instead of stating a full month.
- The April declaration asks about the annual settlement. April is the declaration the annual health-contribution settlement for the previous year is filed in. Biurko does not compute it, so the April file is written only once you state that you have nothing to settle for the year behind it — and if you do, you file April elsewhere and mark it as filed.
- A ZUS DRA korekta can be built, marked and recognised. The build button used to disappear in exactly the state where a korekta becomes possible — after the month was marked as filed; it now names the set it will build ("Build korekta no. 2"), and the mark lands on that set rather than always on the original. If the month changes after filing, the ZUS card says a korekta is needed instead of going on saying only "filed". And the printout of a contribution-holiday month is finally named for what it is — three documents, not one.
- The screens stopped saying two different things about one month. The "To pay" figure lists the ZUS contributions on their own line — they were part of the total in the heading but absent from the body beneath it. Overpaying one contribution no longer marks another as paid: the remainder is folded per contribution. And the paid-contribution dialog offers what you stated rather than what we charged — it used to put the charged amount and today's date over your own entry, which moved the deduction into another month, sometimes another year.
- The QR code on an invoice issued offline. The code now points at the address where KSeF actually verifies an invoice, and carries the full digest of the same file that reaches KSeF. The second code — the one with the certificate — is not built yet, and the document says so rather than looking complete.
- The notice of a new version of the terms reaches the people it is for. A notice sent before the day a version takes effect used to reach nobody while the program recorded that it had been sent. It now goes to everyone owed one, and tells the truth: the day it takes effect, and that the previous version binds until then.