Why it is free, stated plainly
The state requires you to issue e-invoices, declare goods movements and file SAF-T. You have no choice about it, and it publishes free tools of its own.
Putting a price on compelled conformity means charging someone for obeying the law. It is trivially undercut, and when the tax authority changes the format — which it does — the customer is left feeling they pay a subscription to keep up with a form.
So it is free, unlimited, including on the free plan. No invoice cap, no
submission cap. You pay for the platform, for consumption (AI, OCR, messaging)
and for resources — never for your fiscal obligations.
e-Invoicing, validated before it is sent
The invoice is converted to RO_CIUS-compliant UBL and validated before it reaches the tax portal. The reason is practical: a rejected invoice comes back with an error code that explains little, and fixing it at the authority's end is slower than fixing it at yours.
We track the state to completion — sent, processing, accepted, rejected — and surface the receipt. When something is rejected you get the reason translated into what to change on the document, not just the raw code.
Inbound invoices arrive from the portal automatically, with the partner matched by tax number and the posting already proposed.
e-Transport, tied to the document that triggers it
The movement code is requested from the delivery note or invoice that causes the transport, not from a separate screen where you retype everything. The code attaches to the document, and later changes — a different vehicle, a different route — go out from the same place.
SAF-T / D406
Generated from the actual ledger, not from an intermediate export you then adjust. The structure follows the schema in force on the reporting date, and validation runs before submission.
What happens when the rules change
They change here too, at no cost and with nothing for you to do. Fiscal formats move often; turning that into an upgrade prompt would be exactly the kind of lock-in we are trying not to build.