Article 145-IX of the Moroccan Tax Code — the complete e-invoicing guide for 2026.

Article 145, paragraph IX of the Moroccan General Tax Code (CGI) is the legal foundation for mandatory e-invoicing in Morocco. It requires taxpayers to operate an invoicing system meeting technical criteria set by the tax administration, with implementation details deferred to a forthcoming implementing decree — the draft of which has been transmitted to the secretariat-general of the government but not yet published in the Bulletin Officiel as of this guide's date.

The Director General of Taxes, Younès Idrissi Kaitouni, confirmed at the Grands Meetings Médias24 on 16 April 2026 that rollout would begin during 2026, starting with large enterprises (B2B transactions). Turnover thresholds, exact dates, and compliance deadlines per company size will be defined in the upcoming decree.

Adjacent legal frameworks include Law 43-20 on trust services for electronic transactions, which governs qualified electronic signatures, and Law 09-08 on personal-data protection, overseen by the CNDP. Several institutions are involved in the reform: the DGI as project owner, the Ministry of Economy and Finance as supervising authority, the DGSSI which publishes the trust-services framework under law 43-20 (a role historically held by ANRT under the previous law 53-05 regime), and xHub as the technology partner building the national platform.

Morocco has adopted a clearance model — also referred to as Continuous Transaction Controls (CTC) — as opposed to the post-audit model used in most European countries. The difference is fundamental: under post-audit, invoices flow freely between issuer and recipient, with the tax administration auditing them later. Under clearance, the administration is in the loop: no invoice has legal standing until it has been validated by the DGI platform.

The standard flow is as follows. The issuing company generates the invoice in a structured format (UBL 2.1 or CII). It is electronically signed, transmitted to the DGI national platform via a secure API, checked for compliance (format, mandatory mentions, signature, fiscal coherence), and returned with a unique validation identifier. That identifier is what gives the document legal standing. The validated invoice is then routed to the customer through the platform or directly. All parties archive the invoice for at least ten years.

The benefit for the DGI is real-time fiscal visibility — visibility that should eventually enable automatic pre-filling of VAT returns. The cost for businesses is the impossibility of issuing invoices offline, or correcting an issued invoice; any correction must go through a credit note.

The implementing decree will define exact thresholds and the detailed schedule. To date, the DGI has confirmed a phased rollout during 2026, starting with large enterprises (B2B transactions), then extending to SMEs and small businesses. B2C transactions (with consumers) will be in a later phase, after the B2B leg has stabilised.

Expected to fall in scope eventually: all corporate-tax (IS) entities, individuals subject to professional income tax keeping regular books, micro-entrepreneurs (subject to thresholds set by the decree), and public administrations (B2G).

Documents covered include sales invoices, credit notes, corrective invoices and, eventually, electronic purchase and delivery orders. Many online articles cite specific thresholds — for instance MAD 200 million in turnover for the first wave — but as of this guide none of these are sourced from an official DGI document or the Bulletin Officiel.

On the tooling side, the national platform built by xHub on a microservices architecture offers three connection modes: a free web portal (fatourati.gov.ma) announced for very small businesses, SMEs and self-employed; an EDI / REST API channel for direct integration with large-enterprise ERPs (SAP, Oracle, Sage X3); and connection via accredited dematerialisation operators for businesses that prefer to outsource the bridge to the DGI.

No e-invoicing-specific sanctions have been published yet; precise terms will be in the implementing decree. In the meantime, the CGI's general invoicing and bookkeeping sanctions apply: Article 191 bis (failure to present accounting records electronically during an audit), Article 198 ter (omission or inaccuracy of the recipient's ICE), Article 191-I (failure to present accounting records), and Article 192 (serious offences: fictitious invoices, sales without invoice).

The most material risk is probably not the administrative fine but the loss of VAT deductibility. CGI Articles 106 and 146 condition deductibility on so-called regular invoices. If regulations end up defining the platform-validated invoice as the only regular format, non-compliant invoices may be rejected for deduction during a tax audit — a financial impact far exceeding any administrative fine.

Beyond the fiscal consequences, non-compliance can lead to assessments on non-compliant exercises and a degraded fiscal-risk rating with the DGI, translating to heightened scrutiny in future audits.

The DGI requires a structured normalised format. Two are accepted: UBL 2.1 (Universal Business Language, OASIS standard widely deployed in Europe) and CII (Cross-Industry Invoice, UN/CEFACT standard). UBL 2.1 is the format favoured by the Moroccan platform. Important: a PDF emailed even with a digital signature does not constitute a compliant e-invoice — the document must be natively structured XML for automatic processing.

Mandatory mentions include: issuer's and recipient's tax IDs (IF), recipient's ICE (now indispensable), professional-tax number (TP), issue date and sequential number, precise description of goods or services, HT, VAT and TTC amounts, payment terms, and the unique identifier returned by the DGI platform after validation.

Every invoice must carry a qualified electronic signature within the meaning of Law 43-20. That implies a certificate issued by an ANRT-approved trust service provider (PSCo), and a Qualified Signature Creation Device (QSCD — typically an HSM, smart card, or secure mobile enclave). The cost of a qualified certificate is around MAD 1,200 per year. The signature is generally wrapped in XAdES.

Invoices must be archived for at least ten years, with guarantees of integrity, accessibility, traceability (secure timestamping), and recoverability in an exploitable format during audits. End-to-end traceability — issuance, DGI validation, accounting entry, archival — constitutes the reliable audit trail required by the Moroccan General Accounting Standards Code (CGNC). Archival can be on your own servers, certified cloud solutions, or via the national platform.

Three steps to run in parallel, starting now. First, audit your current state: count monthly invoices issued and received, identify the software in use, verify that all clients and suppliers have a valid ICE, and map the existing validation and archival flow.

Second, choose a technical solution. Three options will coexist: the free DGI-provided web portal fatourati.gov.ma for very small businesses and self-employed; an accredited dematerialisation operator handling conversion, signing and transmission on your behalf; or an API integration from your ERP or accounting software. Vouch fits the third category and also provides a SaaS interface for direct use.

Budget-wise, expect MAD 15,000 to 40,000 in upfront investment for an SME equipped with a compatible accounting package, plus the SaaS monthly fee, the qualified signing certificate (~MAD 1,200/year), and team training. Large enterprises with an existing ERP (SAP, Oracle, Sage X3) face costs that depend on integration complexity — request quotes from several integrators. Very small businesses and self-employed can use the free fatourati.gov.ma portal, with costs limited to the certificate and training.

Third, the organisational adjustments: update the accounting procedures manual, define the new internal validation workflows, train accounting and sales teams, and obtain qualified signing certificates from an ANRT-approved PSCo — allow several weeks for issuance.