Structuring
In short
Section titled “In short”Structuring (also called smurfing) means breaking a large amount into smaller pieces so that no single piece crosses a limit that would draw attention: a cash reporting threshold, a KYC tier limit, or an internal review limit. The person is betting that each piece looks ordinary.
Structuring is suspicious because of the intent to avoid a limit, even when the money itself turns out to be clean. Many AML laws treat deliberate structuring as an offence in its own right; confirm the position with your MLRO.
What it looks like
Section titled “What it looks like”A wallet holder in Tema makes seven cash-in deposits over four days: GHS 9,800, GHS 9,500, GHS 9,900, GHS 9,700, GHS 9,850, GHS 9,600 and GHS 9,900, through three different agents. Together that is GHS 68,250. Each deposit sits just under GHS 10,000.
Common forms:
- Just-below deposits: amounts clustered a little under a known limit.
- Spreading across agents or branches: so no single agent sees the full amount.
- Spreading across days: so no daily total stands out.
- Using other people: friends, family or paid “smurfs” deposit on the customer’s behalf.
- Many small in, one large out: collecting small deposits and withdrawing or transferring them in one go.
Which rules surface it
Section titled “Which rules surface it”| Rule | What it catches |
|---|---|
| B1 Multiple deposits just below threshold | Deposits clustered a set margin below a threshold |
| B2 Split cash-in across multiple agents | The same wallet loaded through several agents in a short window |
| B3 Many small deposits, one large withdrawal | Collect-then-withdraw |
| B4 Repeated round amounts | Many round-number transactions |
| B5 Same amount to different recipients | Spreading money out in identical pieces |
| GB1 Cash deposits split across branches | For banks: just-below cash deposits at several branches, checked every hour |
| A5 Aggregate value above tier limit | The total over a period exceeds what the customer’s KYC tier allows |
Red flags and innocent explanations
Section titled “Red flags and innocent explanations”| Red flag | Possible innocent explanation | How to tell them apart |
|---|---|---|
| Amounts consistently just under a known limit | The customer genuinely deals in amounts of that size (for example, a fixed weekly supplier payment of GHS 9,500) | Is the amount the same each time for a clear reason, or varied but always just under? Varied-but-capped is more suspicious |
| Several agents used in a short time | The customer travels for work, or uses whichever agent is nearest | Do the agent locations match where the customer lives, works or travels? Several agents on the same street on the same day is a stronger flag |
| Deposits by different people into one wallet | A family pooling money, a susu group, a small business collecting payments | Can the customer explain who the depositors are? Is it consistent with their declared use? |
| Many small deposits then one large withdrawal | Saving up for a large purchase (school fees, building materials, a vehicle) | Is the pattern a one-off with a plausible purpose, or repeated every week? |
| The customer asks about limits or changes behaviour after being told a limit | Honest curiosity | Front-line staff notes are valuable here; a customer who reshapes deposits after learning a limit is a strong flag |
How to investigate
Section titled “How to investigate”- Map the pieces. List every transaction in the pattern: date, time, amount, agent or branch, depositor if known. A simple table in your case note is enough.
- Find the limit they may be avoiding. Which threshold sits just above the amounts? A reporting threshold, the customer’s KYC tier limit, or an internal limit? Check the KYC tier and any cash reporting threshold your institution applies (confirm current figures with FIC guidance).
- Total it up. Add the pieces over the window. Would the total have crossed the limit in one go?
- Compare with the customer’s profile. Does the total fit their declared occupation and expected volume? A trader declaring GHS 5,000 a month who moves GHS 68,000 in four days needs an explanation.
- Look at where the money went next. Was it withdrawn, sent to one person, sent to many, or sent abroad? Where it goes often tells you more than how it came in.
- Check history. Is this the first time, or has it happened monthly?
- Check for linked customers. Are the same agents, devices or depositors involved with other customers showing the same pattern? That may indicate an organised group.
- Decide and document using the general method.
What to record
Section titled “What to record”- The table of transactions (date, amount, channel, agent or branch).
- The limit you believe was being avoided and why.
- The total and how it compares with the customer’s profile.
- Where the funds went afterwards.
- Any explanation found, and how you verified it.
When to escalate or report
Section titled “When to escalate or report”- Escalate when the pattern is repeated, the amounts are large relative to the profile, several people deposit for one beneficiary, or the funds move on quickly.
- Report when you have reasonable grounds to suspect deliberate avoidance of a limit, or suspect the funds themselves. Deliberate structuring can be reportable even if the source of funds looks legitimate. Confirm with your MLRO.