E‑Invoicing in Benin: Facture Normalisée Rules & DGI Rules
Benin’s facture normalisée: DGI-approved e‑invoicing via MECeF and e‑MECeF, covering business and public-sector transactions with invoice archiving requirements.
August 14, 2026•
General
Benin’s facture normalisée: DGI-approved e‑invoicing via MECeF and e‑MECeF, covering business and public-sector transactions with invoice archiving requirements.
Facture Normalisée
e‑MECeF / SYGMEF
DGI
DGI-certified MECeF model
In scope for covered suppliers
In scope for covered suppliers
In scope for covered suppliers
10-year retention
E‑invoicing in Benin is already mandatory for most formal businesses: under Article 481 of the General Tax Code, anyone subject to corporate income tax, business profits tax, the synthetic business tax or VAT must issue a facture normalisée, unless the DGI has granted a specific exemption.
Covered invoices must be issued through a DGI‑approved system or the MECeF or the e‑MECeF tax portal and finalised with required security elements, including the NIM, date and time, electronic signature, electronic code and QR code. A PDF created outside this workflow is not, by itself, a compliant, normalised facture.
From 20 July 2026, the DGI introduced two-factor authentication for access to the SYGMEF platform through which normalised electronic invoices are issued.
The legal scope of mandatory e-invoicing remains broad under the 2026 General Tax Code. No official announcement of a new phased B2B, B2C, or B2G rollout for 2026. Therefore, the existing normalised electronic invoicing obligation continues to apply according to the supplier’s tax status and the type of transaction.
Businesses can issue normalised invoices through the MECeF or online e‑MECeF portal, provided the workflow meets DGI requirements.
The format is defined by required invoice data rather than a Peppol or EN 16931 XML standard: supplier and buyer details, IFUs where applicable, transaction details, pricing and VAT must be combined with DGI security data, the NIM, issue date and time, electronic signature and QR code. Finalisation adds the DGI security elements that make the document a normalised invoice.
e‑MECeF supports domestic and export sales, credit invoices and copies; corrections must be issued as linked credit invoices using the original MECeF/DGI code, rather than editing the original.
Any software that creates invoices for businesses in Benin, including ERP, POS or billing platforms, should confirm directly with the DGI that the system is approved and that its integration, validation controls, and archive meet local requirements. Keep the finalised invoice, security information, and all linked correction records for the statutory retention period.
.webp&w=1920&q=75)
March 2018: Ministerial Order No. 711‑C defined facture normalisée content and DGI security elements.
2021–2022: Law No. 2021‑15 and Articles 481–482 made DGI‑certified e‑invoicing mandatory for covered taxpayers, unless expressly exempted.
2022: The DGI issued the e‑MECeF manual, confirming that an invoice becomes normalised only after finalisation with DGI security elements.
2026: The framework remains in force; SYGMEF introduced two‑factor authentication from 20 July 2026.
The official DGI materials describe one facture normalisée framework rather than separate B2B, B2C and B2G invoice networks or formats. So businesses should confirm their tax status, applicable tax treatment and any exemption directly with the DGI.
Before deciding that e‑invoicing is mandatory or voluntary for your business, confirm:
Suppliers to public bodies use a DGI‑approved MECeF or e‑MECeF workflow and must apply the correct customer details and tax group. The DGI guide notes that a Taxe Professionnelle Synthétique (TPS) billing a state entity may need to use taxable Group B where the authority withholds VAT; confirm the applicable treatment with the DGI or contracting authority before invoicing.
No separate government B2G format or exchange network is identified in the official sources reviewed. The invoice must still contain the required facture normalisée data and DGI security elements; Article 502 penalties may apply where covered suppliers fail to comply.
For covered B2B suppliers, each sale or service must be invoiced through an approved MECeF system or the e‑MECeF portal. The invoice records both parties’ identities and IFUs, goods or services, prices, taxes, NIM, signature and QR code.
e‑MECeF supports domestic sales invoices, export invoices and credit invoices. Do not edit or delete a finalised invoice: corrections or cancellations must use a linked credit invoice that references the original MECeF/DGI code. For internal ERP, billing and subscription platforms, verify DGI approval requirements before production use.
Consumer sales use the same standardised invoice model. An invoice must be finalised in MECeF or e‑MECeF; the issuer can create it without full customer details but can add the customer’s name, contact details and IFU when needed. When an IFU is provided, e‑MECeF validates it before accepting the invoice.
For businesses using retail, online checkout or other billing software, confirm with the DGI that the system is authorised and supports the required invoice fields and finalisation process. A PDF or receipt produced outside the approved workflow is not, on its own, a facture normalisée.
Under Article 502 of Benin’s 2026 General Tax Code, a covered business that fails to issue a facture normalisée can be fined five times the uninvoiced amount, with a minimum of CFA 500,000 per missing invoice.
For repeat breaches, the penalty rises to ten times the uninvoiced amount, with a CFA 1 million minimum per invoice and possible three‑month administrative closure.
The Code also penalises invoice understatement, unauthorised system changes and fraudulent invoices. Software vendors or businesses using an e‑invoicing system without DGI approval can face CFA 5 million for a first breach and CFA 10 million for a repeat breach. Before relying on an exemption or treating e‑invoicing as voluntary, confirm your tax status, system approval and exact obligations directly with the DGI.
In Benin, compliance is about more than creating an invoice: each facture normalisée must follow the correct workflow, document type, tax treatment, security elements and archiving rules.
Before launch, always confirm directly with the DGI that your business is in scope and that the proposed system or integration meets local approval requirements.
DDD Invoices provides a unified API‑first compliance layer for ERP, POS, billing, e‑commerce and subscription platforms. Send standardised invoice data through one REST API while we handle local invoice validation, domestic and export document workflows, credit‑invoice links and secure archiving behind the scenes. Our solution can be embedded or white‑labelled, so customers can stay within your existing application while you scale across markets.
Still have questions?
In the 30min free call we will discuss:
Yes. Unless an express exemption has been granted, transactions carried out by persons subject to corporate income tax, business profits tax, the synthetic business tax, or VAT must result in a normalised invoice or an accepted equivalent document.
It is an invoice containing standard commercial information together with DGI security elements such as the system identification number, date and time, electronic signature, electronic code, and QR code.
Yes, but the invoicing system must meet the DGI’s technical specifications and be approved before use in Benin. A system that has not yet been approved must be adapted to communicate with e-MECeF through the DGI-approved API.
Copies of invoices and related accounting documents are required to be kept for 10 years by the Code.
%2520(1)-1.webp&w=1920&q=75)
-1.webp&w=1920&q=75)
-1.webp&w=1920&q=75)
-1.webp&w=1920&q=75)