Ask AwraIQ about features, pricing, onboarding, login, integrations, security, demos, mobile apps, automation, reports, or support.
For Cameroon
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.
What actually stands between you and a paid supplier
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.
Before the goods move
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.
At the border
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.
At your gate
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.
At the bank
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.
What this costs today
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.
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.
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.
Yaoundé, Douala, Garoua and a site inland do not reconcile, counts are quarterly, and the difference is written off rather than explained.
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
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.
Operations in Cameroon
On most pages in this directory, evidence is something you produce afterwards to explain what happened. Here it comes first. The order, the domiciliation reference, the declaration, the transport documents and the receipt have to exist as a set before a payment to a foreign supplier moves — so a system that happily closes a transaction with a gap in it has not saved anybody any work, it has simply moved the assembly to the worst possible moment.
Receiving
Matching that will not close on a missing document
Order, receipt and invoice matched, with the transaction held open while a required document is absent rather than passed through for somebody to chase later. The refusal is the feature; a warning would leave the file exactly as incomplete as it was.
Documents
On the record, not in a folder named by month
Each document attached to the transaction it belongs to and retrievable by it. A folder organised by date answers a question nobody asks; the question is always about one consignment.
Evidence
Assembled as the work happens, not reconstructed
The set exists because each stage produced its part, so producing it is a retrieval. This is the difference between a file that takes an afternoon and one that takes a week and still has a hole in it.
Landed cost
Cost in XAF on the consignment, open after receipt
Freight, clearing, handling and demurrage arrive weeks after the container. The receipt stays open so they reach the unit cost rather than being discovered after the goods have been sold.
Inventory
Upcountry stock that reconciles with Douala
Yaoundé, Douala, Garoua and inland sites each a distinct position with governed transfers and counts whose variance is attributed to a place and a period — instead of accurate at head office and unknown beyond it.
Procurement
Approvals that refuse, in OHADA account classes
Thresholds that block rather than warn, posting into a chart of accounts whose classes you did not design and must use anyway. A system expecting you to invent your own numbering has made the accountant's job harder, not easier.
The limit, stated where it belongs rather than at the bottom: we do not domicile anything, submit anything, or move money through any bank. We hold the set of documents a bank and a regulator will ask for, attached to the transaction they describe. Which of them your particular payment requires is between you, your bank and your adviser — and it changes, which is precisely why we will not encode it.
Scope, stated plainly
No e-invoicing connection and no French interface. Both are real objections in this market and neither has a workaround worth pretending about.
Running in the product today
On the roadmap — and commissionable now
Not ours, by choice — and the exchange-control line is the one to hold us to
Nothing in the middle column is permanent. A DGI pipeline against a published specification, a French interface and a Cameroonian payroll engine are all ordinary builds — and Kenya's eTIMS and payroll engine exist because clients needed them and commissioned them. Ask and we will return a specification, a timeline and a price. What we will not do is name a date for an obligation whose technical detail has not been published, which is the claim this page exists to refuse.
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
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.
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.
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.
Read before you shortlist
In the CEMAC zone, paying a foreign supplier is a case you prove rather than an instruction you give. Four documents must agree, four different parties create them, and nobody owns the fact that they must match.
A hundred thousand XAF is worth exactly a hundred thousand XOF, always, by arrangement. They are still two currencies under two central banks and two sets of exchange rules — and most systems store both as one label.
Two purchases are being confused in this market. One has no published specification to build against yet, and the other you could start on this month.
A project in our system has one customer. Organisations running one programme on money from three funders need to say a single shared cost belongs to all three in different proportions — and there is no funder concept in our schema at all.
Our helpdesk was built for organizations where plenty of staff have no company login — and then the breach alarm was wired to a login. The tickets nobody had picked up were the tickets nobody was told about.
A transfer between your own warehouses is an administrative detail — until the two warehouses are the coast and somewhere landlocked, and the stock spends weeks in a state that appears in no warehouse's figure. The workflow handles it well. The reporting has a hole in exactly the wrong place.
Questions we are asked here
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. **That is on the roadmap rather than a boundary, and it is commissionable now.** Once there is a published specification to build against, a pipeline to it — issuance, retries, a failure queue and a reconciliation report — is ordinary work. Kenya's eTIMS transmission and its maintained statutory payroll engine both exist because Kenyan clients needed them and commissioned them — neither arrived on a roadmap by itself. Ask and we will scope it against the actual specification. What we will not do is name a date or describe ourselves as ready for an obligation whose technical detail has not been published, because that is the claim this page exists to refuse.
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. **This one is a boundary rather than a backlog** — it does not change with a commissioned build, and it is the most important boundary on this page. We do not domicile a contract with a bank, we do not assemble a transfer file, and nothing we sell influences whether or when a transfer is approved. Anyone suggesting software accelerates an exchange-control decision is selling something that does not exist. What we do is hold the documents against the transaction so the file is complete when it is asked for.
No. The application is English-only, and we would rather you knew it 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. **That is on the roadmap rather than a boundary, and it is commissionable now.** Interface text and document templates in French is scoped, priceable work rather than a permanent limit. Kenya's eTIMS transmission and its maintained statutory payroll engine both exist because Kenyan clients needed them and commissioned them — neither arrived on a roadmap by itself. The honest caveat: a vendor already shipping the language starts where we would be finishing, so if it is your first requirement rather than your third, buying locally is the rational move and we would rather write that sentence than lose your third month to it.
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.
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. **This one is a boundary rather than a backlog** — it does not change with a commissioned build, and it is a design decision rather than a gap we intend to fill. The plan is prescribed by OHADA law, your expert-comptable owns the presentation and signs it, and software inserting itself there puts us between you and the person accountable for the filing. We hold the operational detail underneath.
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.
Partly, and the honest split matters because this is the one obligation on this page that runs on a clock. Under the zone's exchange regulation, proceeds from an export have to be repatriated within 150 days of the effective date of the export, and the general regulation provides no exception — a percentage floor exists on top of that for extractive companies specifically, which is a different regime and not the general one. What makes it operationally awkward rather than merely administrative is where the clock starts: **not on your invoice, but on the export itself.** So the trigger is a logistics event and the obligation is a finance one, and in most organisations those two live in different systems and different heads. What runs here: the shipment exists as a consignment with its date and its documents, the receipts against it are recorded and matched to what they settled, and both sides are retrievable from the transaction rather than reconstructed. So the question "which export has money still outstanding against it, and how long has it been" is answerable from records instead of from memory. **What is not built is the clock itself** — no per-export deadline, no countdown, no alert at day 120. That is ordinary work, it is commissionable now with a written specification, a timeline and a price, and it is worth asking for, because the consequence here is not only a fine: it can include losing the right to move money through the zone's banking system for a period, which is an operational shutdown rather than a cost line. What we will not do is tell you what your particular obligation is or how a receipt should be evidenced to your bank — that is your adviser's and your banker's, and it is the same boundary the exchange-control answer above draws.
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.
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.