Issuing invoices for Germany and Romania

POST /invoices validates the invoice, generates every requested format, checks each with the official validator and archives the documents unchangeably with SHA-256 hashes. The seller's data always comes from the seller you created; you send only the invoice.

Germany

Default formats: xrechnung-ubl, xrechnung-cii and zugferd (PDF/A-3 with embedded XML). Choose with "formats": ["xrechnung-ubl"]. Public buyers need their Leitweg-ID as buyerReference (BT-10) and usually as Peppol address with scheme 0204.

Defaults: type 380 (invoice), currency EUR, unit C62, VAT category S, payment by SEPA credit transfer to the seller's IBAN. Credit notes: "typeCode": "381" with precedingInvoices. Small businesses (§ 19 UStG): VAT category E with an exemption reason.

Romania

Sellers in Romania get ro-efactura-ubl (CIUS-RO, checked with ANAF's schematron); ro-efactura-cii on request. Rules: currency RON (or another currency with vatAccounting in RON), the number needs a digit, street and city for seller and buyer, county as ISO 3166-2:RO code in subdivision (Bucharest RO-B with SECTOR1…SECTOR6), a VAT ID or tax number for the seller, a VAT ID or registration ID for the buyer. Upload to ANAF with a delivery over channel anaf.

After issuing

Read with GET /invoices/{id}, list with GET /invoices, download with GET /invoices/{id}/document?format=… (the ETag is the SHA-256). Archived invoices cannot be changed or deleted; correct them with a credit note. Large invoices: at most 1000 lines × formats per request (invoice.too-large).