Bank of Ghana reporting for FX bureaux — a 2026 overview

[Placeholder article — the structure is real, the specific regulatory figures are not confirmed for 2026. Before publishing, a compliance reviewer at CediSync or external counsel should verify every threshold, deadline, and form name against the current BoG directives.]

Running a forex bureau in Ghana means living with Bank of Ghana returns. For a small bureau, that means one or two people spending time every month pulling numbers together, every quarter preparing a second set, and once a year sitting with an auditor to sign off the whole picture.

This is a practical overview of what BoG actually asks for — not legal advice, not a substitute for your compliance officer or counsel. It is meant to help a bureau owner or supervisor understand the shape of their reporting obligations so the calendar is less surprising.

What BoG expects from an FX bureau

At the highest level, licensed forex bureaux in Ghana operate under the Foreign Exchange Act and the supplemental directives BoG issues through the Financial Stability Department. Those directives change; the shape of the obligations is more stable:

• Monthly returns — volumes, balances, and exposures by currency.
• AML/KYC obligations — customer identification above threshold, suspicious transaction reporting, staff training records.
• Annual audited financial statements — signed off by a BoG-approved auditor.
• Record retention — a defined number of years for trade tickets, KYC records, and internal controls evidence.
• Incident and material change reporting — notifying BoG of ownership changes, new branches, significant losses, and the like.

[Placeholder — confirm exact names of each return form, reporting cadence, and the supplemental directives they derive from.]

The monthly return, in practice

The monthly return is where most bureaux spend their compliance time. It summarises:

• Opening and closing balances, in cedis, for every foreign currency you handled.
• Total volume of purchases and sales, per currency.
• Margin and spread, where applicable.
• Exceptional transactions above BoG's reporting threshold.

Submission is typically due within a few working days of month-end. Late filings attract fines — more importantly, they draw the wrong kind of attention from the supervisor.

Common mistakes on the monthly return

Three that come up repeatedly:

1. Reconciling against the wrong source. Spreadsheet totals, not the ledger. The monthly return should reflect the reconciled position, not an approximate one.
2. Missing an override. A rate override during a volatile trading day that wasn't recorded properly shows up as a variance the next month.
3. Aggregating multiple branches incorrectly. Returns are bureau-wide, but branch-level data must roll up cleanly — and cleanly means: the same customer, the same currency, counted once.

AML and KYC

AML work for a bureau is less about dramatic disclosures and more about the quiet discipline of doing the right thing on every trade: identifying customers over threshold, keeping the evidence, and reporting genuinely suspicious activity.

• Ghana Card or equivalent ID captured for every customer transacting above the relevant threshold.
• Source of funds recorded where the amount or pattern warrants it.
• Suspicious transaction reports filed with FIC — the Financial Intelligence Centre — when something doesn't add up.
• Staff training records, because BoG will ask for them.

How CediSync handles the monthly return

CediSync was built with this cycle in mind. What that means concretely:

• The monthly return template is one click — the figures come from the same ledger you already use every day, not a second set of books you maintain in parallel.
• Every rate change is logged with actor, time, old value, and new value. The audit trail is exportable.
• KYC fields attach to the trade itself — not a separate customer file. When the auditor asks to see the ID for trade T-1482, you pull it up with the trade.
• Drill-through is default — any aggregate on any report clicks through to the underlying transactions.

Compliance should be the default, not a module you remember to turn on.

This article is an overview, not legal advice. Verify every threshold and deadline against the current BoG directives or consult your compliance officer.