Cross-Border Treasury in Africa: A Guide for NGN, GHS, KES, XOF & XAF Operators

1. Map the corridors you actually operate

Start with a corridor inventory rather than a currency list. A corridor is a directional pair — NGN → GHS is a different operational problem from GHS → NGN because liquidity, cut-offs, and regulatory reporting differ at each end. For each corridor, record the counterparty banks or PSPs, the cut-off in local time, expected settlement window, and the regulatory reference (CBN, BoG, CBK, BCEAO, BEAC) you cite on filings.

The XOF and XAF zones are pegged to the Euro, which simplifies FX planning but not settlement: BCEAO (XOF) and BEAC (XAF) operate as separate clearing systems, so a payout to Côte d'Ivoire and one to Cameroon are not the same rail even though the amounts look identical on a dashboard.

2. Fund each currency ahead of demand, not on demand

The most common cross-border treasury failure is trying to source NGN or KES the same day a payout batch is due. Local liquidity windows are narrow, and interbank rates late in the day are punitive. Build a rolling seven-day forecast per currency:

• Expected collections in that currency (from your PSPs and corporate customers).
• Confirmed payouts due (payroll, supplier, tax).
• Discretionary payouts that could be rescheduled if the corridor is tight.
• Working buffer — usually 1–2 days of average payout volume.

Fund the shortfall in the morning of the previous business day. Treat "fund on the day" as an incident, not a workflow.

3. Set FX policy per corridor, not per trade

Trade-by-trade FX decisions burn desk time and produce inconsistent rates. Instead, agree a policy with the CFO:

• Passive corridors (XOF, XAF): convert at scheduled windows; the EUR peg makes intra-day timing low-value.
• Managed corridors (NGN, GHS, KES): set a reference rate each morning; auto-execute conversions within a tolerance band, escalate outside it.
• Large trades (above a per-corridor threshold): always go to a named approver — no auto-execution.

Write the policy down and version it. A treasury policy that lives in Slack is a policy no auditor will accept.

4. Enforce maker-checker on every payout

Maker-checker (four-eyes) is table stakes for regulated finance teams and increasingly expected by counterparty banks in the region. The rule is simple: the person who initiates a payout cannot be the person who releases it. Role-based access should enforce this in the system, not in policy.

Typical role split for a mid-sized operator:

• Operator — creates and edits payout batches; cannot release.
• Approver — releases batches up to a per-currency limit; cannot create.
• Treasurer — releases batches above the approver limit; can also move funds between own-account balances.
• Auditor — read-only across every corridor and action; no write access anywhere.

5. Keep an audit trail your regulator will accept

Every state change — batch created, edited, approved, released, failed, retried — needs a timestamped, user-attributed log entry that cannot be edited after the fact. The bar is not "we can reconstruct it from Slack." The bar is: a regulator asks about a specific NGN payout on a specific date and you produce, within minutes, who initiated it, who approved it, the FX rate used, the counterparty bank reference, and the final settlement status.

Store the trail in the same system that executes the payout. Reconciling logs across three tools is where audits go wrong.

6. Reconcile daily, not monthly

For each corridor, reconcile the previous day's collections and payouts against bank/PSP statements the next morning. Daily reconciliation catches routing errors while they are still recoverable; monthly reconciliation catches them after the counterparty has already closed its books.

Bringing it together

The operators who run African cross-border treasury well share a pattern: a defined corridor list, forward-funded currency positions, a written FX policy, enforced maker-checker, an append-only audit trail, and daily reconciliation. None of these are exotic — they are just consistently applied.

BorderBanc is built around this pattern: multi-currency balances across NGN, GHS, KES, XOF, and XAF, role-based approvals with maker-checker built in, and an audit trail that answers a regulator's question in one screen.