DGI E-Invoicing Compliance

The scheme covers companies subject to corporate tax, professional income tax or VAT. The most widely cited calendar sets the obligation at 1 January 2026 for large corporate-tax entities, 1 July 2026 for companies with revenue between MAD 10 and 200 million, then 1 January 2027 for SMEs and very small businesses above MAD 500,000 of annual revenue. Those thresholds and dates are still set by the implementing decree, which was in validation at the time of writing, so we recommend checking the version in force on tax.gov.ma and having it confirmed by your tax adviser before committing a budget.

Rarely. A recent ERP with a dedicated Moroccan module can generate the structured format natively, but that remains the exception. In most cases your system already exposes the data through an API or a file feed, and it is enough to add a transformation layer that produces compliant XML and then handles the platform's acknowledgements. Replacing the ERP to achieve compliance stretches the timeline and moves the difficulty rather than solving it.

The rules require a structured XML format, either UBL 2.1 or CII. These standards are not interchangeable with a PDF or CSV export, because they impose a precise tag structure for every mandatory field, notably tax identifiers, per-line VAT and the invoice's unique reference. Morocco has also adopted a clearance model, which means an invoice must pass through the DGI platform and be validated there before it counts as legally issued.

This is the half of the problem most projects leave aside. Your main suppliers will switch over too, so your procurement module has to read a UBL or CII file and reconcile automatically. Continuing to re-key PDFs cancels the traceability benefit of the reform and multiplies the risk of error. Once inbound volume picks up, an accounting module that cannot parse the format blocks reconciliation, and that is usually when the subject becomes urgent.

The right answer is to design the integration so you do not have to build it twice. Three things are not yet settled: the choice between a four-corner and a five-corner model, the exact revenue thresholds per wave, and the final list of accredited providers. An integration hard-wired around a single assumption will have to be reworked as soon as the decree specifies the chosen architecture. So we build the transformation layer and the connector to stay isolable, which makes switching platform or provider a configuration change rather than new development.