Electronic invoicing in Morocco
The electronic invoicing reform led by the DGI is changing how Moroccan businesses issue, transmit and archive their invoices. Open Vista integrates this framework into Odoo 17: formats, configuration, testing and change management, according to the DGI calendar and quoted per project.
On quotation — integration depends on your Odoo version, volumes and flows.
Electronic invoicing in Morocco: what changes
The Directorate General of Taxes (DGI) is progressively rolling out electronic invoicing in Morocco. The framework is set by the General Tax Code, in particular article 145-IX, and detailed in DGI publications. Companies concerned will have to issue, transmit and archive their invoices in structured formats, according to the DGI calendar.
Beyond the obligation, the reform is an opportunity: no more re-keying, fewer errors, faster collections and better traceability. Companies that prepare their systems early absorb the transition more calmly.
We follow the requirements published by the DGI and adapt your ERP as regulatory details are published, without anticipating deadlines that are not official.
UBL 2.1, CII, EDI: the formats to master
Your ERP must produce structured invoices readable by exchange platforms. We define the format together with your ecosystem.
UBL 2.1
An XML format widely used in B2B exchanges. We configure Odoo to generate invoices compliant with the selected profiles.
CII
A business-oriented semantic format suited to structured exchanges between ERP and platforms. We validate the structure and mandatory fields with your partners.
EDI and API
For automated flows, we set up EDI exchanges or secure APIs between Odoo and your partners or dematerialisation platforms.
PDF and archiving
Electronic invoicing does not exclude a readable PDF output. We organise generation, signing and evidential archiving of documents.
A question about integration? See our service catalogue or contact us directly.
What your ERP must produce
An electronic invoice must carry accurate data and be verifiable by exchange platforms: company identifiers (ICE), numbering, date, VAT, invoice lines, currency and customer details. We check every field and every rule before going live.
For companies running Odoo, integration covers sales invoicing, credit notes, public contracts and inter-company flows. Discover our Odoo integration in Morocco.
- Legal and tax identifiers (ICE, VAT)
- Numbering, sequence and mandatory mentions
- Invoice lines, discounts, taxes and currency
- Credit notes, down payments and recurring invoices
- Multi-company, multi-currency and public contracts
- Consistency checks before transmission
On quotation — the scope depends on your ERP and your flows.
Integrating electronic invoicing into Odoo 17 in four steps
A progressive path, tested before every go-live.
Scoping and flow analysis
We map your sales, customers and obligations, then identify the fields to complete in Odoo and the flows to send to exchange platforms. The test plan is defined at this stage.
Configuration and development
Configuration of companies, taxes and sequences, adaptation of invoice templates, development of connectors or export of UBL/CII formats according to the selected profiles.
Testing and validation
We test real cases: domestic sales, exports, credit notes, down-payment invoices and multi-company flows. Partner platforms validate the formats before cut-over.
Deployment and follow-up
Progressive go-live, team training, documented procedures and monitoring of regulatory updates published by the DGI.
For hosting and monitoring your platform, rely on our VPS servers and our Wazuh SIEM monitoring.
What are the use cases for electronic invoicing?
Commercial SMEs
Digitise your customer invoices, automate reminders and prepare for exchange obligations without increasing the administrative burden.
Multi-company groups
A common invoice template, per-company rules and end-to-end traceability across entities and currencies.
Distribution and e-commerce
High volumes, B2B and B2C flows: we make generation, formats and archiving reliable at scale.
Compliance, security and archiving
Electronic invoicing involves sensitive data and retention obligations. We implement an audit trail, access controls, backups and retention aligned with the framework published by the DGI. Exchanges are secured and logged.
- Audit trail and logging of submissions
- Access controls by company and by role
- Backups and document retention
- Documented procedures for tax audits
Who electronic invoicing integration is for
SMEs and mid-sized companies
You want to be ready before the deadline and avoid manual rework. We adapt Odoo to your business and train your teams.
Groups and multi-company setups
You need to harmonise flows across entities, currencies and systems. We frame governance and specific cases.
Experts and partners
You support your clients through the reform: we work with you on formats, testing and archiving.
Learn more: our Odoo and digital transformation services.
Frequently asked questions
Is electronic invoicing mandatory in Morocco?
The framework is set by the General Tax Code and progressively deployed by the DGI, according to the DGI calendar. Companies concerned must prepare for it; we help you anticipate the published requirements.
Can Odoo 17 produce electronic invoices?
Odoo 17 handles invoicing and can be adapted to produce structured formats (UBL, CII) and the associated flows. We develop the required connectors and validate the formats with exchange platforms.
Which formats are accepted?
Exchange formats rely on structured schemas such as UBL 2.1 or CII, supplemented by EDI or API flows. The choice depends on the selected profiles and the requirements published by the DGI.
How much does Odoo integration cost?
The budget depends on your Odoo version, number of companies, flows and the connectors to develop. We prepare a detailed quotation after a scoping workshop.
Ready to prepare your electronic invoicing?
On quotation — let's talk about your invoicing flows and timeline. Our team will propose a progressive integration path in Odoo.