Is your invoicing software ready for Morocco's DGI? A 15-point checklist

Morocco's e-invoicing reform will force every invoicing tool to evolve: a nice PDF will no longer be enough. Software will have to produce invoices in a structured format, send them to the DGI platform, handle validation, receive supplier invoices and archive everything. This 15-point checklist lets you check where your tool stands, whether it is off-the-shelf software, an ERP or an in-house build. For context and timing, read what is decided on e-invoicing in Morocco first.

Invoice data

1. Complete mandatory details: issuer identifiers (ICE, tax ID, trade register), customer identity and ICE, date, number, description, quantities, prices, VAT rate and amount.
2. Continuous, gap-free numbering generated by the software, not typed by hand, with a separate series for credit notes.
3. Clean master data: complete customer records (verified ICE), product and service catalogue with correct VAT rates.
4. Credit notes and cancellations handled as documents, never by deleting or editing an issued invoice.

Format

1. Export to a structured format cited by the reform: UBL 2.1 or UN/CEFACT CII, in XML.
2. Internal validation before sending (mandatory fields, totals, identifier formats), to avoid rejections.
3. A readable version (PDF) generated from the same data, for customers and internal use.

Transmission

1. Connection to the DGI platform via API, or through an approved service provider if that model is adopted, per the published specifications.
2. Status handling: sent, validated, rejected, with the rejection reason and the ability to fix and resend.
3. Traceability: a timestamped log of every submission and platform response.

Receiving

1. Receiving supplier e-invoices and posting them to accounting without re-keying.
2. Matching against purchase orders and goods received, for businesses that use them.

Archiving and security

1. Archiving of issued and received invoices in their original format, with validation receipts, for the legal retention period.
2. Security: named accounts, role-based permissions, backups, change log. See SaaS security and data protection.
3. Vendor commitment: a written compliance timeline, update process and support during the transition.

Reading your score

• 12 or more points covered or planned: your tool is on track. Watch for updates after the decree.
• 7 to 11 points: ask your vendor for a precise timeline and clean your data now.
• Fewer than 7, or invoices still made in Word or Excel: plan a change of tool or a significant upgrade.

Questions to ask your vendor

• Which structured formats will the software produce, and when?
• How will the connection to the DGI platform work?
• Is receiving supplier invoices planned?
• Is the update included in my subscription or billed separately?
• Where and for how long are my invoices archived?

If your software is in-house

A custom business tool that issues your invoices will have to evolve just like commercial software. It is often a chance to modernise it: clean database, APIs, archiving, and perhaps a move to SaaS if other companies in your sector have the same need. See building or adapting compliant invoicing software and turning internal software into SaaS.

Get your tool reviewed

We review and upgrade invoicing and business software: structured invoice generation, external platform connectors, archiving and security. See our SaaS and software development service. Send us a description of your tool and we will tell you what is ready and what needs to change.