E-Invoicing Morocco: What Is Actually Official in 2026

The essentials, without the noise. Mandatory electronic invoicing in Morocco rests on Article 145-IX of the General Tax Code (CGI), which requires taxpayers to operate an invoicing system meeting technical criteria set by the tax administration. But as of this guide's publication (July 2026) the implementing decree has still not been published. The detailed timeline you see circulating (large companies January 2026, mid-sized companies July 2026, SMEs January 2027) comes from no official document published by the DGI or in the Bulletin Officiel. This guide separates what is confirmed from what is not, and sets out what you can prepare now without depending on uncertain dates.

What is confirmed, and what is not

This is the first thing to establish, because most published content on the subject presents as settled a number of things that are not.

The draft implementing decree was submitted to the Secretariat General of the Government in April 2026. Until it is published in the Bulletin Officiel, the dates and thresholds remain assumptions, including those repeated with great confidence by many providers.

Why this matters to you: a compliance plan built on an invented date is a fragile plan. If you budget an ERP project to "be ready by 1 January 2027" and the decree sets a different deadline or different thresholds, your planning is wrong in both directions: you may have over-invested in false urgency, or fallen behind a deadline that turns out to be closer than expected.

The legal basis: Article 145-IX of the CGI

Article 145 of the General Tax Code, at paragraph IX, establishes the obligation for taxpayers to operate an IT invoicing system meeting technical criteria set by the administration.

Two things in that wording deserve attention:

1. The obligation is on the system, not just the document. This is not about emailing a PDF. The law targets your organization's technical capability to issue compliant invoices.
2. The technical criteria are delegated to the administration. That is precisely what the pending implementing decree is for, and why its absence blocks any firm timeline.

The chosen model: clearance (pre-validation)

Morocco has opted for a clearance model (also called CTC, Continuous Transaction Controls), the same principle applied in Mexico, Türkiye and Saudi Arabia.

In practice this changes the nature of invoicing itself:

• You issue the invoice from your system;
• It is transmitted to the DGI platform before being sent to the customer;
• The platform validates it;
• The invoice only has legal standing once validated.

That is a structural difference from simple after-the-fact reporting. An invoice rejected by the platform is not a late invoice: it is an invoice that does not legally exist. Your sales process becomes dependent on real-time external validation, with direct consequences for your information system.

The national platform is being built by xHub, the technology partner selected by the DGI. A free portal, fatourati.gov.ma, is planned for very small businesses with low invoice volumes.

What your invoicing system will need to do

Here is the genuinely useful part: the technical requirements are known, even though the timeline is not. You can therefore prepare your system without waiting for the decree.

Look at that list against your current setup: if you invoice today from Excel, from unmaintained software, or from a customer database where ICE is optional, none of those six requirements is met : and none of them depends on a date to be true.

What to do now, without waiting for the decree

This is the actionable part. Five workstreams hold their value whatever deadline is ultimately set:

1. Clean up your customer master data. ICE becomes blocking data. An incomplete or duplicated customer file turns into rejected invoices. This cleanup takes time, carries no risk, and is worth doing regardless of the reform.
2. Audit your current invoicing chain. Where are invoices issued? How many different systems? Is there manual entry, parallel spreadsheets? Map it before choosing a tool.
3. Check your software's technical capability. Can your current solution produce UBL 2.1 and communicate over an API? If your vendor has not publicly addressed the reform, that is a signal.
4. Sort out numbering and archiving. Clean sequences and integrity-preserving retention are good practice, not new constraints.
5. Track the decree at source. The Bulletin Officiel and official DGI communications, not provider blog posts, whose limitations this guide has just demonstrated.

None of these becomes wasted work if the timeline changes. That is exactly the test to apply: invest in what stays true regardless of the date.

Where does Odoo fit?

For most Moroccan SMEs the real question is not "which e-invoicing tool should I buy" but "will my current management system cope". Bolting an e-invoicing tool onto an ERP that does not talk to it recreates double entry, precisely what the reform is meant to eliminate.

A properly configured ERP treats electronic invoicing as a step in the sales cycle rather than a separate tool: the invoice is generated from the order, submitted for validation, and the validation status flows back into the same system as your accounting and customer records.

That is the point of our Moroccan localization work on Odoo, PCGE, CNSS, CIMR, AMO and DGI requirements handled inside the management system itself. Our complete Odoo Morocco guide sets out that approach in full.

One point of honesty to close on: until the DGI publishes the official API for its platform, no vendor (Odoo included) can claim to be "certified compliant" with Moroccan e-invoicing. What can be prepared today is technical capability: structured formats, reliable customer data, an architecture ready to connect. Treat any claim of compliance already achieved, against a standard whose final specifications are unpublished, as a warning sign.

Frequently Asked Questions

Is electronic invoicing already mandatory in Morocco?

The principle is set out in Article 145-IX of the General Tax Code, but implementation depends on a decree that, as of July 2026, has not been published in the Bulletin Officiel. The draft was submitted to the Secretariat General of the Government in April 2026. Until it appears, the entry-into-force dates by company category are not officially fixed.

Is the 2026-2027 timeline I keep seeing reliable?

Not as it stands. The frequently cited timeline (large companies on 1 January 2026, mid-sized companies on 1 July 2026, SMEs and sole traders on 1 January 2027) comes from no official document published by the DGI or in the Bulletin Officiel. The associated revenue thresholds are equally unconfirmed. These figures are repeated from one article to the next without a verifiable primary source.

What is the "clearance" model and how does it affect me?

It is a pre-validation model: the invoice is transmitted to the DGI platform before it is sent to the customer, and only acquires legal standing once validated. The practical consequence matters: a rejected invoice has not legally been issued. Your invoicing process becomes dependent on external validation, which requires a system able to handle receipts and rejections.

Will emailing a PDF be enough?

No. The chosen formats are structured XML (UBL 2.1 or CII) which allow automatic processing by the platform. A PDF, even a signed one, is not a structured format in the sense of the reform. This is where most organizations underestimate the gap they need to close.

What can I do now without waiting for the decree?

Five workstreams keep their value whatever the deadline: clean up the ICE data in your customer base, map your current invoicing chain, verify your software can produce UBL 2.1 and communicate over an API, sort out numbering and archiving, and track the decree through official sources. None of this is wasted if the timeline shifts.

Can my current software already be "compliant"?

At this stage no vendor can seriously guarantee that, since the DGI platform's official API and final specifications are unpublished. A vendor can legitimately say it has prepared its architecture and will activate the connection on publication. A claim of compliance already achieved, however, should give you pause.