DE_XRECHNUNG_UBLSA_ZATCAPEPPOL_BIS3
Odoo ERP to XRechnung 3.0, ZATCA Phase 2 & Peppol BIS 3.0
Offload brittle EDI/XML maintenance from your Odoo modules to a dedicated, integer-cent accurate REST microservice.
Covers Germany Jan 1, 2027, Poland/UAE Jan 1, 2027, and Saudi Wave 25 Feb 1, 2027.
3-Step Integration Flow
- Trigger an Odoo automated action on account.move post.
- Call POST /v1/einvoice/issue with Odoo move name as Idempotency-Key.
- Store the returned xmlSha256 and ZATCA UUID/ICV back on the Odoo record.
Odoo -> Invora REST
import requests
r = requests.post(
"https://api.invora.dev/v1/einvoice/issue",
headers={"Authorization": "Bearer tb_live_your_key", "Idempotency-Key": move.name},
json=odoo_to_invora_payload(move),
timeout=15,
)Frequently Asked Questions
Does Invora guarantee sequential ZATCA ICV/PIH under concurrent Odoo workers?
Yes. Every ZATCA issuance locks the EGS CSID row in PostgreSQL with SELECT ... FOR UPDATE.
Ship Odoo E-Invoicing Today
Starts at $79/mo for 1,500 invoices. No sales call required.