e-MECeF — Benin e-invoicing

Invoicerr does not support Benin

No Benin data file exists anywhere in this repository — no country policy, no identifiers, no tax system, no transmission channel. Nothing on this page is implemented. It is here so that someone who wants Benin support knows what adding it would involve. The countries Invoicerr does cover are listed in the country directory.

Benin's e-invoicing runs through e-MECeF, the Système dématérialisé des Machines Électroniques Certifiées de Facturation, administered by the DGI, the Direction Générale des Impôts. It works through certified electronic billing machines rather than a pure B2B invoice flow.

What supporting Benin would involve

System	e-MECeF — Système dématérialisé des Machines Électroniques Certifiées de Facturation
Authority	DGI — Direction Générale des Impôts
Format	A national XML schema, generated by a certified electronic billing machine or software. No provider in backend/src/modules/documents/formats/ builds it today.
Transmission	Submission through the e-MECeF API. No transport in backend/src/modules/documents/transports/ talks to it today.

Inherited, unverified

Carried over from an earlier research pass in this repository's own history, and never checked against a primary source. Leads, not facts — confirm every line before writing it into a data file.

• Mandatory for all VAT-registered businesses from 2020, with continuous real-time transmission.
• Described as a clearance model: invoices are validated through e-MECeF.
• Requires a certified electronic billing machine or certified software, not just any invoicing tool.

Which catalogues a contributor would add

Adding a country is data, not code. Adding a country is the procedure and the contract each file has to satisfy; this is only the shopping list for Benin.

• country-policy/data/bj.json — which document actions Benin allows. Start here: without this file every action is refused with a 403, naming the country.
• country-identifiers/data/bj.json — which national identifier a party must carry.
• tax/tax-systems/data/bj.json and vat-rates/data/bj.json — the tax kind, and the rate ladder offered on an invoice line.
• correction-routes/data/bj.json — all eleven canonical correction routes, unverified where unresearched, never omitted.
• b2g-routing/data/bj.json — the channel and format a Beninese public buyer requires.
• transports/channel-policy/data/bj.json — whether a channel is legally required of a seller established in Benin, and from what date.
• archive/retention/data/bj.json — how long an archived document is kept, and what the duration is counted from.

Add mentions/, content-requirements/, country-fields/, reporting/ and domestic-reverse-charge/ only where the law actually gives them content.

Data alone will not finish the job here: the e-MECeF platform is a transmission channel this repository does not implement, and its XML schema has no format provider. Both are code, not a JSON file — see When a country needs more than a file.

Want Benin supported?

Check the open compliance issues first. If there is no issue for Benin, open one and name which of the files above you need — a request that names one mechanism is far more actionable than "please add Benin".