How Procura natively integrates DGI Côte d'Ivoire's FNE framework: setup, API flow, multi-country support, and the path to production.
Procura team · May 2026 · 9 min readFNE (Facture Normalisée Électronique) is the standardized e-invoicing framework run by Côte d'Ivoire's Tax Office (DGI). Every taxpayer registered for VAT must transmit each B2B invoice in real time to the FNE platform and carry an official reference + QR-verifiable token on the printed copy. Without that signature, the invoice is no longer admissible to support a VAT deduction for the buyer or an expense write-off for the seller.
The framework is the Ivorian counterpart of Benin's MECeF, but with a markedly different technical shape. FNE uses a single-step sign API: one POST to /external/invoices/sign returns the certified reference, the NCC, a QR-verifiable token and a remaining sticker balance, there is no separate confirmation step. The DGI also issues the production base URL per-taxpayer after certification, rather than running a single shared endpoint.
The official portal is hosted at fne.dgi.gouv.ci, with a public test platform at http://54.247.95.108/ws and an interfacing procedure published by the DGI in May 2025. That procedure is the reference Procura follows for every field name and every call.
Who does what matters. The SELLER certifies its invoice and prints the QR code. The BUYER checks it: an invoice that is not certified, or certified for another company or another amount, gives the buyer no right to deduct VAT. For a purchasing platform like Procura, the FNE work is therefore mostly on the buyer's side: checking every supplier invoice before it is approved and paid.
An FNE integration in Procura is configured around five core fields. The NCC (Numéro Compte Contribuable) is your taxpayer ID, the same one that already appears on every invoice you issue, typically 8 to 14 characters depending on the regime. The API token is a Bearer secret the DGI delivers when your company is registered on the FNE portal. The point of sale and establishment are operational identifiers that ride on every transmission and can be overridden per invoice.
Two more fields complete the setup: the environment (Sandbox vs Production) and the optional production URL. Sandbox always points to the public test platform, you do not need to provide a URL there. Production requires the per-taxpayer URL the DGI hands over after certification. Procura validates this at save time: switching to Production without a production URL is rejected at the form level, so an org can never silently submit live invoices against the sandbox endpoint.
Procura also exposes a third environment, the Procura demo, which simulates the DGI so you can try the flow before contacting it. The simulation applies the field rules of the DGI procedure (required fields, item price excluding tax, B2B customer NCC, and so on) and answers in the same shape. It is a rehearsal, not a certification: only the DGI's test platform, then production, prove an integration.
None of these fields is needed to check supplier invoices. That check reads the QR code printed on the invoice and asks the DGI's public verification service, which requires no account. The API connection is only needed to certify documents in your own name, such as the purchase slip described below.
FNE uses a single-step model. The seller POSTs the invoice (invoiceType, paymentMethod, template, items, taxes, customer) to /external/invoices/sign and receives the official number, its NCC, a verification link to print as a QR code, and its remaining sticker balance. There is no separate confirmation call. A credit note goes to /external/invoices/{id}/refund, where {id} is the certified document's identifier, with the lines and quantities returned.
Templates carry meaning. B2B is for invoicing another taxpayer and requires the customer's NCC. B2C covers consumers. B2F is for foreign customers and requires the currency and its rate. B2G is for public bodies. Tax codes are TVA (18%), TVAB (9%), TVAC (0%, conventional exemption) and TVAD (0%, legal exemption).
On the buyer's side, Procura checks every invoice from an Ivorian supplier. The QR code is read from the PDF or photo of the invoice, or pasted, and Procura asks the DGI what it certified: issued by this supplier (NCC), to your company (NCC), for this amount including tax, as an invoice and not a credit note, and not already recorded on another invoice. Each result is kept on the invoice and in the audit log. The organization chooses whether a failed check only flags the invoice or blocks its approval, with an exemption that must state its reason.
The one document a buyer certifies itself is the purchase slip for farm produce (invoiceType purchase), issued when buying from a producer who has no NCC and cannot invoice. Procura issues it from the supplier invoice, reserves the invoice before calling the DGI so a double click cannot spend two stickers, and cancels it with a certified credit note when needed.
An organization that operates in both Côte d'Ivoire and Bénin, say, a group with offices in Abidjan and Cotonou, needs both FNE and MECeF active at the same time. Procura supports this natively: FNE and MECeF are two distinct module slugs in the activeModules array, and both can be enabled on the same tenant.
The Settings → Finance sidebar shows FNE (Côte d'Ivoire) and MECeF (Bénin) as two separate sections. Each holds its own credentials (NCC + token + production URL for FNE, IFU + token for MECeF), its own environment switch, and its own audit trail. Invoices issued under one regime are never confused with those issued under the other.
Provisioning a multi-country organization from the Procura platform-admin console is a single form: pick a primary country, then tick whichever module slugs apply (fne, mecef, or both). The country gate accepts ISO codes and full names in both languages, Côte d'Ivoire, Cote d'Ivoire, Ivory Coast, CI all unlock the FNE section the same way.
Behind the scenes the gating logic is countryHit OR moduleHit: a section appears whenever the org's country matches the section's accepted variants OR any of its module slugs appear in activeModules. That second branch is what lets a multi-country organization with country='Côte d'Ivoire' but activeModules=['fne','mecef'] see both regimes side by side without changing primary country.
Start with the supplier check, which needs no DGI account. Fill in your company's NCC and each Ivorian supplier's NCC, leave the rule on Flag for a few weeks, and look at which suppliers send invoices that fail. That list is the conversation to have with them before switching the rule to Block approval.
For the purchase slip, rehearse first with the Procura demo. Then register your company on the DGI test platform (http://54.247.95.108), which the procedure makes mandatory, and copy the API key shown in the Settings tab of your FNE test space into Procura, in Sandbox mode.
Issue test documents on the test platform: a purchase slip and its credit note. Send the specimens to support.fne@dgi.gouv.ci as the procedure asks. The DGI checks them, then sends the production URL and opens access to the production API key.
Paste the production key and URL, switch to Production, and issue one real slip to check the whole chain: the certified number and verification link on the invoice, the sticker balance going down, and the request and response in the audit log.