Getting ready for the e-invoice
Most of the time lost around e-invoicing is lost before the portal, not on it: the accountant copies an invoice over, it is rejected, the reason is hunted down, the data is fixed, and the invoice is copied again. That loop repeats several times a day.
Look closely and most rejections come from a handful of simple causes - all of which can be checked in your own system first.
The most common causes
- The company TIN is empty - by far the most frequent
- The counterparty has no TIN, or it is the wrong length
- A line has no unit of measure
- VAT rates are inconsistent across lines
- The invoice date falls in a closed period
- The numbering sequence is broken
This is a checklist, not an exhaustive list. The portal's own requirements change - for the official rules, see the tax authority's documentation.
Checking is the system's job
None of the points above should be left to human memory. The software can say whether an invoice is ready - and it should name the problem, not print a generic "error".
In ERPONA the e-invoice queue is its own screen: ready and not-ready invoices sit in one list, and each row carries a concrete problem - "the company TIN is empty", for example. The accountant sees the mistake in the system, not on the portal.
An important distinction: preparation and submission
This needs saying plainly: ERPONA does not send invoices to the portal. It prepares the invoice, checks the details and keeps the queue and the numbering - the copying itself is done by the accountant.
That is a deliberate boundary, not a limitation we are hiding. Automatic exchange is a separate agreement and integration work. Saying "everything is automatic" and then producing manual steps later is worse than stating the boundary up front.
What it buys you
- Fewer rejections and fewer re-submissions
- A bad invoice is caught when it is written, not at month end
- Numbering stays in one place
You can see the screen on the home page; the step-by-step guide is on the documentation portal.