AWRA OpsHub Search

For Cameroon

Your supplier is not waiting for your payment. They are waiting for your paperwork.

In the CEMAC zone, paying a foreign supplier is not a banking instruction you give — it is a case you have to prove. Since March 2019 the regional exchange regulation has required significant imports and exports to be domiciled with a bank inside the zone before they happen, the domiciliation reference to reconcile with the customs declaration, and export proceeds to come home inside a fixed period. Your bank is not being difficult. It is being audited. One thing before you read further: our interface is English-only, and in Cameroon that is a real constraint we raise on the first call rather than the last.

E-invoicing
Not connected, and no honest vendor is yet. The 2026 Finance Law creates the obligation; the specification and accreditation route were unpublished when this page was written. We are not going to print a date for you to plan against.
Exchange control
We hold the records the file is built from. We do not domicile contracts, talk to your bank, submit to BEAC, or make any transfer happen faster.
Language
The interface is English-only. In this market that is a first-call question, not a footnote — and for some organisations it is the end of the conversation.
Books
No SYSCOHADA ledger and no statutory accounts, by design and in every member state. Your expert-comptable keeps them; we build the pipe.

What actually stands between you and a paid supplier

Between "we agreed to buy" and "the supplier has the money" there is a file

Every business importing into this zone knows this sequence and almost no business has a system that models it. It gets held in a folder, in a bank relationship manager's inbox, and in the head of whichever person has done it before. That person going on leave is a genuine operational risk, and it is the plainest symptom of the problem this page describes.

  1. Before the goods move

    The order is domiciled with a bank inside the zone

    Above a threshold, the contract or order has to be registered with a CEMAC bank before the transaction proceeds, and the bank opens a file against it. From that moment the commercial relationship has a second identity — a reference number that everything downstream has to agree with. The threshold is not printed on this page on purpose; it differs by transaction type and sources disagree on the figure, so confirm yours with your bank rather than with a vendor website.

  2. At the border

    The customs declaration has to reconcile with the file

    Values, quantities, description, counterparty. A declaration that does not match the domiciled order is not a customs problem you fix at customs; it is a payment problem you discover months later, when the bank compares the two and declines to transfer. The gap between "the goods cleared" and "the payment cleared" is where almost all of the pain in this sequence lives.

  3. At your gate

    Proof that what was declared is what arrived

    The receipt evidences the transaction actually happened. This is the point where the exchange-control file and ordinary operational discipline become the same activity — a short delivery you did not record is now not only a stock error and a credit note, it is a discrepancy between your customs record and your payment file.

  4. At the bank

    The transfer is assessed against the file, not your relationship

    The bank is an agent of the exchange regulation here, not only your service provider. It has its own reporting obligation to the central bank and its own exposure if your file is incomplete. This is why a payment that "should be simple" is not, and why the answer to "when will my supplier be paid" is genuinely unknown to the person you are asking.

What happens when the file is wrong is not priced like an administrative error, and this is the part most buyers underestimate. Sanctions under the regulation include a fine set as a proportion of the amount involved and — the one that actually changes behaviour — suspension of the offender's right to transfer money through the CEMAC banking system for a period measured in months. A business that cannot make international transfers cannot import. That is not a fine, it is a stop, and it is why the finance director in Douala cares about a document trail in a way that sounds excessive to a head office elsewhere.

Five questions worth asking inside your own business, before you ask any vendor

  1. Who in your business could reconstruct a complete exchange-control file for a shipment from last quarter, and how long would it take them?
  2. When a supplier asks why they have not been paid, can anybody answer with a stage rather than an apology?
  3. Is the domiciliation reference recorded against the purchase order, or does it live in an email thread and a bank portal?
  4. How would you know today that a declaration was filed at a different value from the order it belongs to?
  5. If your longest-serving import clerk left next month, what exactly would stop working — and would you find out before or after a payment was declined?

What this costs today

Four problems that get blamed on the bank

Only one of these is genuinely the bank's. The other three are record-keeping, and they are the reason the bank's part takes as long as it does.

A payment file assembled by hand, every time

The order, the domiciliation reference, the declaration, the transport documents and the receipt exist in five places and are brought together by one person under time pressure, usually after the supplier has started chasing.

Landed cost discovered after the goods are sold

Freight, clearing, handling and demurrage arrive as invoices weeks after the container. If they never reach the unit cost, margin is being measured against a purchase price rather than against what the goods cost to have in Douala.

Stock that is accurate at head office and unknown upcountry

Yaoundé, Douala, Garoua and a site inland do not reconcile, counts are quarterly, and the difference is written off rather than explained.

A supplier ledger nobody trusts

When payments are delayed by a process outside your control, ageing stops being a measure of your behaviour and becomes noise — so people stop reading it, and a genuine dispute hides in the same column as an administrative wait.

A small fact that software gets confidently wrong

Two CFA francs, one peg, and most systems think they are the same currency

The Central African CFA franc (XAF) and the West African CFA franc (XOF) are pegged to the euro at exactly the same rate. A hundred thousand of one is worth precisely a hundred thousand of the other, always, by arrangement. They are still two separate currencies, issued by two separate central banks, under two separate sets of exchange rules, and they are not interchangeable. Douala to Abidjan is a cross-border, cross-currency transaction between two currencies that never move against each other — which is exactly the sort of thing software gets confidently wrong.

A balance labelled "CFA" tells you nothing 01

What happens

What happens: a chart of accounts, a price list or a spreadsheet says CFA and everybody knows what they mean until the day they do not. A payable in Libreville and a payable in Lomé net to zero on a report and are, in fact, two obligations in two banking systems that cannot settle each other.

What helps

What helps: storing the actual currency code on the transaction — XAF or XOF, never a shared label — so a report can be right rather than only arithmetically consistent.

The rate is fixed. The permission is not. 02

What happens

What happens: because the euro peg does not move, teams conclude there is no currency risk here and stop paying attention. The exposure in this zone was never the rate. It is administrative — whether and when a transfer is allowed to happen — and no exchange-rate hedge addresses it.

What helps

What helps: tracking the elapsed time and the stage a payment is sitting at, because in this zone the useful metric is delay, not rate movement.

Inside the "CFA zone" can still be outside CEMAC 03

What happens

What happens: a transfer from Cameroon to Senegal feels domestic in every way that matters commercially, and is a transfer out of the CEMAC monetary area for the purposes of the regulation. It needs the same treatment as a payment to Rotterdam.

What helps

What helps: the exchange-control file being driven by the counterparty's zone rather than by whether the currency looks familiar — a rule, applied consistently, instead of a judgement made per transaction.

Group reporting that quietly merges the two 04

What happens

What happens: a group with operations either side of the boundary consolidates on the assumption that CFA is CFA. The consolidated number is arithmetically correct and operationally useless, because it hides which half of the group is holding the cash and which half can actually spend it.

What helps

What helps: entities and locations holding their own positions in their own currency, reportable separately and together, so the consolidation is a view rather than an assumption baked into the data.

None of this is exotic and none of it requires special software to understand. It requires a system that refuses to let two things be labelled the same when they are not — which is the same discipline that makes stock counts and supplier balances trustworthy, applied to a currency code.

Scope, stated plainly

Two of these decide whether we are worth a meeting

No e-invoicing connection and no French interface. Both are real objections in this market and neither has a workaround worth pretending about.

Scope in Cameroon, stated before the demo

Running in the product today

  • Purchase orders, receipts and invoices matched, with discrepancies raised rather than absorbed, and supporting documents held against the transaction.
  • Landed cost on the consignment, so clearing, freight, duty and demurrage reach the unit cost rather than a general expense line.
  • Multi-site stock with per-location positions, transfers that require confirmation at the receiving end, and counts that produce a variance with a name on it.
  • Multi-currency held at the rate actually applied, with XAF and XOF treated as the two distinct currencies they are.
  • Approvals that block above a threshold, per site, with a full audit trail of who changed what and when.
  • Mobile capture for sites with poor connectivity, so a receipt upcountry is recorded when it happens rather than when somebody reaches a desk.

Not built — and the first two decide whether we are worth a meeting

  • No DGI e-invoicing connection, and nobody honestly has one yet. The 2026 Finance Law creates a real-time issuance obligation through an approved platform. When this page was written the technical specification, the accreditation route and the rollout timetable had not been published. We are not accredited, we do not transmit, and we would treat any vendor currently claiming Cameroon e-invoicing readiness as describing an intention rather than a product.
  • No French interface. The application is English-only. In a market where the administration, the banks and most finance floors work in French, that is a serious objection and not a roadmap footnote. The anglophone regions make it survivable for some organisations and irrelevant for others; it is a first-call question, not a last-call one.
  • No SYSCOHADA ledger and no statutory accounts. We do not ship a numbered OHADA chart of accounts or produce statutory financial statements, in any member state. Your expert-comptable keeps the books; we would build the export that feeds them.
  • We are not part of your exchange-control process. We do not domicile contracts, communicate with your bank, submit anything to BEAC, or make a transfer happen faster. What we hold is the record the file is built from.
  • No Cameroonian payroll. No income tax bands, no CNPS contributions, no statutory schedules. Our maintained payroll engine covers Kenya only.
  • No local office and no implementation partner in the zone. Onboarding and support are remote from Nairobi, in English.

Read those two lists together before deciding. If what you need is a compliance product for Cameroon, we are not it and we are not close. If what you need is for the operational record underneath the compliance — what was ordered, what arrived, what it cost landed, and which documents exist — to stop being assembled by hand under pressure, that is a real and specific thing we do, and it happens to be the layer the exchange-control file is built from.

How this starts

Three moves, and the first two need no vendor at all

01

Pick one import from last quarter and rebuild its file

Order, domiciliation reference, declaration, transport documents, receipt, payment. Time it, and count the systems and people involved. Almost every business that does this exercise is surprised by the answer, and the number it produces is a better basis for a software decision than any demo.

02

Ask what the landed cost of that shipment actually was

Not the supplier invoice — the cost of having the goods in your warehouse, including clearing, transport and any demurrage. If the answer is unavailable, or arrives as a number somebody assembled for the question, your margin reporting is running on purchase prices.

03

Then decide which problem you are buying for

E-invoicing readiness is coming and will be a real purchase, from somebody who is accredited, once there is a specification to be accredited against. Operational record-keeping is a purchase you can make today and it is a different purchase. Businesses that wait for the first and neglect the second usually end up doing both badly, in a hurry.

Questions we are asked here

Answered in full, including the ones that lose us the deal

Do you connect to the DGI e-invoicing platform?

No. The 2026 Finance Law introduces a real-time issuance obligation through an approved platform or an accredited service provider, and when this page was written the technical specification, the accreditation route and the phased timetable had not been published. We are not accredited and we do not transmit. We are also not going to print a go-live date here for you to plan against, because dates in this position move and a reader who plans against a vendor's guess is worse off than one who asks the DGI. What we would say to anybody currently being sold Cameroon e-invoicing readiness: ask which specification version the product is built against, and see whether a version number comes back.

Can you handle the exchange-control paperwork for us?

No, and it is important to be exact about the boundary. We do not domicile a contract with a bank, we do not correspond with your bank, we do not submit anything to BEAC, and nothing about using us makes a transfer approved sooner. What we do is hold the underlying records the file is assembled from — the order, the receipt, the values, the documents, the reference numbers — on the transaction rather than across five places. That turns an assembly job into a retrieval job. Your bank relationship and your compliance obligation remain entirely yours.

Is the interface available in French?

No. The application is English-only, and we would rather lose the deal on the first call than the fourth. Whether that is workable depends on your specific organisation — some Cameroonian businesses run an English-speaking finance and operations function comfortably, particularly ones with anglophone or regional-group roots, and many do not. Documents you send to customers and suppliers are templated and can carry your own wording; the application itself is not translated, and we are not going to describe a translation as imminent.

Do you treat XAF and XOF as the same currency?

No. They are pegged to the euro at the same rate, so a hundred thousand of one converts to a hundred thousand of the other, but they are separate currencies issued by separate central banks under separate exchange rules, and we store the actual code on the transaction. This matters more than it sounds: a group operating either side of that boundary can produce a consolidated CFA figure that is arithmetically perfect and tells you nothing about which entity can actually spend the money.

Do you produce SYSCOHADA accounts?

No, and this is a deliberate design decision rather than a gap we intend to fill. We do not ship a numbered OHADA chart of accounts and we do not produce statutory financial statements in any member state. The statutory ledger belongs with your expert-comptable, who is accountable for it and who will be the one signing. What we would build is the pipe: a defined monthly export mapped to their chart of accounts, so the operational detail arrives in a shape they can post rather than as a request for a spreadsheet.

What about MTN MoMo and Orange Money?

Not integrated today. Mobile money is a serious collection rail in Cameroon and a settlement feed into the Payments Register is a realistic build rather than a fantasy — it is the same shape as work already done for other markets. Today it would be reconciled from a statement rather than matched automatically, and you should price that manual step into any comparison.

Where does support come from, and does the time difference matter?

Nairobi, remote, in English. Cameroon is UTC+1 and Nairobi is UTC+3, so two hours — the smallest gap of any market outside East Africa and effectively a non-issue for a working day. There is no Cameroon office and no local implementation partner, which is a fair objection. The working week and public holidays are configured rather than assumed.

Rebuild one import file and time it

One shipment from last quarter: order, domiciliation reference, customs declaration, transport documents, receipt, payment. How long, how many systems, how many people. You do not need us to run that exercise, and the number it produces will tell you whether this page is describing your business.