E-Invoicing
E-Invoicing on Odoo
Native e-invoicing for India (GST), Italy (FatturaPA), Saudi Arabia (ZATCA), and other regulatory regimes. IRN registration, e-way bill, statutory reports, and audit-ready archives — all inside Odoo.
Last reviewed:
What it is
Country-specific e-invoicing flows wired natively into Odoo's accounting module. For India: IRN registration with the GSTN portal, e-way bill generation, JSON format compliance. For Italy: FatturaPA XML generation and SDI submission. For Saudi Arabia: ZATCA Phase 2 cryptographic stamps. For each regime: real-time submission, status tracking, archive retention per regulatory requirement.
Why it matters
E-invoicing mandates are spreading globally and are non-negotiable: you can't bill GST B2B in India above the threshold without IRN; you can't bill in Italy without FatturaPA; you can't bill in Saudi Arabia without ZATCA. Bolt-on third-party compliance tools work but add cost, integration friction, and another vendor relationship. Native e-invoicing inside Odoo means one system of record and audit-ready archives without extra plumbing.
Features
-
India GST e-invoicing
IRN registration, e-way bill generation, JSON format per GSTN spec, real-time submission, IRN/QR code printing on invoice.
-
Italy FatturaPA
Italian e-invoice XML generation per FatturaPA spec, SDI portal submission, customer/supplier validation, and status tracking.
-
Saudi Arabia ZATCA
ZATCA Phase 2 cryptographic stamping, QR code generation, real-time submission to ZATCA portal, archive retention.
-
Mexico CFDI
CFDI 4.0 XML generation, SAT submission via PAC integration, complement support (Carta Porte, Pagos).
-
EU EN 16931
Pan-European e-invoice standard support for Peppol BIS Billing 3.0. Used in France (Chorus Pro), Belgium, and others adopting EN 16931.
-
Audit-ready archives
Statutory archive retention per regime. India: 8 years. Italy: 10 years. Saudi: 6 years. Documents retrievable on regulator request.
-
Status reconciliation
Real-time status tracking — submitted, accepted, rejected, cancelled — with auto-retry on transient failures and human escalation on persistent ones.
-
Multi-entity multi-country
Run multiple legal entities across multiple countries in one Odoo instance. Each entity uses the right e-invoicing flow per its country's mandate.
How it works
-
Regime audit
We catalog the e-invoicing mandates that apply to your business based on country, entity structure, and B2B vs. B2C transaction types. Output: written compliance roadmap.
-
Provisioning
Government portal credentials, PAC accounts (Mexico), digital signatures, and cryptographic certificates set up per regime. Setup time varies by country (1–4 weeks).
-
Odoo configuration
Country-specific e-invoicing modules activated. Tax codes, invoice templates, and submission workflows configured per entity.
-
Testing
Test transactions submitted to government test/sandbox environments. Validation, error-handling, and edge-case behavior verified before production.
-
Production go-live
Phased — start with one entity / country, expand. Status reports during the first 30 days flag any submission issues for proactive resolution.
Deployment timeline
Single-country rollout (India only, or Italy only): 4–6 weeks. Multi-country (e.g. India + Saudi Arabia): 8–10 weeks. The bottleneck per country is provisioning — government portal credentials, PAC accounts, and digital certificates each take 1–4 weeks to obtain depending on the country.
Best for
Any business operating in countries with e-invoicing mandates above transaction thresholds: India B2B GST (above GST registration threshold), Italy (all B2B/B2C), Saudi Arabia (Phase 2 — all B2B/B2C above threshold), Mexico, France, Belgium, and the growing list of countries adopting Peppol/EN 16931. Especially valuable for multi-country operators consolidating compliance into one ERP.
Frequently asked questions
-
Is Odoo e-invoicing certified by tax authorities?
Odoo e-invoicing modules are designed to comply with each regime's spec, but 'certification' isn't a thing in most regimes — it's about whether your submissions are accepted by the government portal. We test against each portal's sandbox environment before production and have shipped Odoo e-invoicing for India, Italy, Saudi Arabia, and Mexico without rejection issues. For India specifically, we use IRP (Invoice Reference Portal) APIs directly.
-
What about multi-country operations?
Multi-company multi-currency is native to Odoo. Each entity uses the e-invoicing flow appropriate to its country. One Odoo instance can simultaneously generate IRN-stamped invoices for India, FatturaPA XML for Italy, and ZATCA-stamped QR codes for Saudi Arabia — depending on which entity issues each invoice.
-
Does it handle e-way bills (India)?
Yes — e-way bill generation is integrated with the GSTN portal. Triggered automatically on goods movements above the threshold; cancellable per regulatory rules; tracked through delivery for audit.
-
What about ZATCA Phase 2 (Saudi Arabia)?
Yes — Phase 2 cryptographic stamping is supported. Each invoice is signed with the ZATCA-issued certificate; submitted to the ZATCA portal in real time; QR code generated for the printed invoice. We've shipped this for Saudi Arabia clients during the rolling Phase 2 rollout.
-
How are errors and rejections handled?
Real-time submission means errors surface within seconds. Rejections route to a triage queue with regulator's error message attached. Most rejections are validation issues (tax code mismatch, missing fields) that auto-route to the responsible team. Auto-retry handles transient failures; persistent ones escalate.
-
Do you handle the digital certificate / DSC issuance?
We don't issue certificates ourselves (that's the regulator's job), but we coordinate with you and the certificate authority (eMudhra, NSDL, IdenTrust, etc.) to get them issued and installed in Odoo. We also handle annual renewals during ongoing support engagements.
-
What about archive retention?
Statutory archive retention per regime. Documents retrievable for the required period (8 years India, 10 years Italy, 6 years Saudi). Archive search and retrieval supported for regulator audits — we've supported Indian GST and Italian Agenzia delle Entrate audits with Odoo as the system of record.
-
Implementation timeline?
Single-country: 4–6 weeks. Multi-country: 8–10 weeks. Bottleneck is provisioning — government credentials, PAC accounts, and digital signatures take 1–4 weeks per country. Existing Odoo customers can start provisioning in parallel with other configuration to compress timelines.