v0.83.0 — KSeF in full: offline regimes, certificates, permissions, attachments

Offline deadlines counted the way the act counts them. When KSeF is unavailable, an invoice issued offline has a filing deadline in working days (art. 106nda, 106nh, 106nf), not "24 hours". Biurko used to count fixed days — that is, stricter than the law. The deadline is stored at the moment of issue, so a change of rules does not move the deadline of a document that already has one. A fourth regime was added too: during a declared total failure the duty to file does not run at all.
A free KSeF certificate as a third way to connect. Beside a Trusted Profile and a purchased qualified signature, you can now order your own certificate from KSeF and connect the company with it — without buying a signature. Applications and their statuses live on their own screen, and the private key never leaves the product.
The second QR code on a printed offline invoice. An invoice issued offline now carries both codes the Ministry requires: the one for checking the document and the one that proves the issuer (captioned "CERTYFIKAT"). The Ministry's own verifier accepted both.
KSeF permissions are visible and manageable. A new screen shows who may act in KSeF on the company's behalf, and lets you grant or withdraw a permission. The gateway acknowledges the request and settles it moments later — the product says so plainly instead of pretending the matter is closed.
An attachment to an invoice. An invoice sent to KSeF can now carry an attachment — once the consent is enabled in KSeF, and only through the batch route, because the gateway itself accepts it no other way. The screen says what is missing before you try.
A wide import arrives in one download. A window holding thousands of invoices now comes as one package instead of a call per document (measured: 4 476 invoices in 1.78 MB in about 100 seconds, where fetching by number would take tens of hours). The automatic pull remembers the gateway's high-water mark — the moment KSeF guarantees completeness to — so the next window does not begin past documents the gateway has not recorded yet.
Batch sending with its own UPO and visible limits. Larger batches go as one session, whose own receipt is stored page by page. The KSeF limits (calls per hour, invoices per batch) are asked of the gateway and shown before you act, not after a refusal.
One number instead of a list of invoices. Several invoices from the same seller can be joined in KSeF under one collective identifier — a single transfer then names the whole set. The ceiling (today 500 invoices) is the gateway's to state, and a set cannot be broken up, so the dialog asks before creating one.
A KSeF number can be read out of the UPO. If an invoice's number was lost or arrived in an unlawful form, the invoice card now offers "Read from the UPO": the value comes from the signed receipt we already hold rather than from retyping it.
The screen shows the gateway the invoices actually go to. The KSeF address used to be written down separately in the product and did not agree with where documents went. The screen now asks the layer that does the sending — and shows the address of this company's environment, not the default one's.

Cookies