Why electronic invoices exist
A PDF is made for people to read. An electronic invoice is structured data, so accounting software or a public authority can read the numbers without retyping them. Several countries and sectors now require or encourage this, and the rules differ.
The two formats Mavri exports
- UBL 2.1 is a widely used XML syntax for business documents. Mavri’s UBL export follows Peppol BIS 3.0.
- XRechnung is a German standard for invoices to public bodies, also XML. Mavri exports XRechnung 3.0.
How to get one in Mavri
- Open an invoice.
- Choose UBL XML or XRechnung XML.
- If something required is missing, Mavri says which field, instead of producing a half-empty file.
Electronic invoices need more identity data than a PDF. In the guide’s words, add the country code, tax ID and e-invoice address to the business, and the address, tax ID and country code to the customer, plus a buyer reference if the customer requires one. In a test run on a bare invoice, Mavri also asked for a due date or payment terms and for the issuer’s email and phone. Through the API, the same problem shows up as a 422 einvoice_incomplete response that lists what is missing.
What an export does not do
- It does not transmit invoices over the Peppol network or to a government portal. You deliver the file yourself.
- Whether a recipient accepts the file depends on their system and on your data being correct.
- Before relying on e-invoices for a mandate, ask your tax adviser or the recipient what they require and test with their validator.
A sensible first run
Fill in the identity fields for one business and one customer, export both formats from a test invoice, and open the XML in the validator your recipient or country recommends. Fix anything it flags in your records, then repeat.
Sources
- Mavri guide – Businesses and customers
- Mavri API reference – e-invoice route
- Peppol BIS Billing 3.0
- XRechnung standard (KoSIT)