When a remittance business gets into trouble on a high-risk corridor, the corridor usually gets the blame. Look closer and the cause is nearly always inside the business: limits nobody wrote down, approvals that depend on who is on shift, rates set by feel, and exceptions handled differently every time. The corridor sets the level of risk. Your rules decide whether you control it. This guide is for compliance, operations and pricing leads at established money transfer operators who serve corridors that partners and regulators watch closely. Figures in the examples are illustrative.
The test of a rule is simple: two people applying it to the same transfer, on their own, reach the same answer. If they would not, it is still judgment.
What goes wrong when rules live in people's heads
| Area | Without a written rule | With one |
|---|---|---|
| Limits | Set by instinct; vary by who handles the case | Set per corridor, enforced by the platform, reviewed on a schedule |
| Approvals | Escalated to whoever is senior and available | Tiers by risk score and amount; each tier has an owner and a time to decide |
| Pricing | Rates and margins adjusted ad hoc; leakage nobody sees | Margin set per corridor; every change confirmed and kept in history |
| Exceptions | Each one improvised | A short list of categories, each with a set path |
| Records | "Someone made a call" | Each decision recorded with who, when and why |
The last row is the one that hurts. When an examiner or a banking partner asks why a transfer went through, what limit applied and who approved it, "someone made a call and we have no record" is not an answer. Every other row feeds this one.
Writing the rules for one corridor
Take a corridor from the UK to a payout country your risk assessment rates high: mostly cash pickup and mobile wallet, many first-time senders, and a payout country on FATF's list of jurisdictions under increased monitoring. The operator writes three sets of rules for it. The figures are illustrative; yours come from your own risk assessment.
| Rule | Setting |
|---|---|
| Per transfer | Up to 2,000 |
| Over the past 90 days | Up to 6,000 |
| Over the past year | Up to 15,000 |
| Documents as the 90-day total grows | Up to 1,000: proof of identity. Up to 3,000: plus proof of address. Up to 6,000: plus source of funds |
| Above the top tier | Cannot send until an officer raises the customer's own limit, with a reason |
| Risk band | What happens | Owner | Time to decide |
|---|---|---|---|
| Low (1 to 25) and Medium (26 to 50, below threshold) | Flows on its own | Platform | None |
| High (51 to 75) | Waits for review | Compliance analyst | 4 working hours |
| Critical (76 and above) | Waits for review; possible case | MLRO | Same working day |
| Possible sanctions match | Waits for a ruling | Screening analyst | Before payout |
Now three customers on the same morning:
- Customer A has sent 900 in the last 90 days and sends 400. The total reaches 1,300, so the platform asks for proof of address before the transfer goes. The score is Low. Once the document is approved, it flows. Nobody had to decide anything.
- Customer B signed up last week and sends 1,800 to a recipient who already receives from three other new customers. Linked transaction patterns and frequent transfers to the same recipient fire; the score is 64. It waits for an analyst, who has four working hours and a risk page that explains each trigger.
- Customer C has sent 5,700 in 90 days and tries to send 800. That would take them past 6,000, the top tier. They cannot send until an officer reviews their source of funds and decides whether to raise their own limit. The override and its reason are recorded.
Three different outcomes, each predictable from the written rules. Change the shift, and the answers stay the same. That is the point.
Write the "why" next to each number. An examiner will ask why the 90-day limit is 6,000 and not 10,000. The answer belongs in your risk assessment, dated, with the data you looked at.
Doing it with RemitSo
RemitSo, a white label remittance platform, puts these rules into the admin panel so they apply whoever is on shift.
- Limits and documents: AML rules per currency, paying country and payout country, with corridor exceptions. Policies measure each transfer or the total over a period (the past 1 day, 1 month, 90 days or 1 year), and tiers name the documents asked for as totals grow. Limits are enforced exactly as configured, a new rule applies at once, and since release 2026.10.11 only transfers a customer has paid for count. A customer at a limit is told what they can still send.
- Approval tiers: 47 ready-made risk indicators that you combine into your own rules. Risk score bands are Low 1 to 25, Medium 26 to 50, High 51 to 75 and Critical from 76; at or above your threshold (50 unless changed), transfers stop Under Review. Everything else flows on its own.
- Pricing: every standard rate shows its buy and sell rate, spread and margin, and who last changed it. Any change needs confirmation before it is saved, a zero or mistyped rate is refused, and every change is kept in the rate history.
- Exceptions: corridor exceptions in AML rules, an officer's limit raise from the customer's page, and alerts routed to the people you subscribe.
- Records: AML rule changes are reviewed before saving and kept as history with who made them and why, and every override of an AML limit is recorded in a searchable, plain-language audit log of who changed what, and when.
Your team still sets the limits, writes the rules and makes the decisions. See the admin features, our guide to handling limit overrides and exceptions, or book a demo.
Pricing is a risk control too
Rate setting is often left to treasury, apart from compliance and operations. That is a mistake. When rates are adjusted by feel, margins drift: some transfers go out at a healthy margin, others at almost nothing, and the gap shows up months later as revenue that does not match the forecast.
It is also a consumer protection issue. In the EU (PSD2, Article 45), the UK (regulation 43 of the Payment Services Regulations 2017) and the US (the Remittance Rule, 12 CFR 1005.31), the customer must be told the exchange rate before they commit. A rate changed informally, outside a controlled process, is how a transfer ends up at a rate that was not the one disclosed. Set a margin per corridor, change it only through a confirmed, recorded step, and review it on a schedule.
Exceptions: a short list with set paths
Most remittance businesses see the same handful of exceptions again and again. Name them, and give each one a path.
| Exception | Path | Owner |
|---|---|---|
| Source of funds unclear | Ask for documents in the app; hold until reviewed | KYC team |
| Possible name match | Rule on the match; record the reason | Screening analyst |
| Pattern does not fit stated purpose | Review the risk page; open a case if it does not resolve | Compliance analyst, then MLRO |
| Document expires mid-transfer | Ask for a replacement; the transfer resumes once approved | KYC team |
| Customer at the top limit tier | Review source of funds; raise their own limit or decline, with a reason | MLRO |
If a new kind of exception turns up three times in a month, it is no longer an exception. Write it a path.
Records, and a review that keeps the rules honest
FATF Recommendation 11 says transaction records must be kept for at least five years and be enough to reconstruct individual transactions; national rules build on that. A transaction log is not enough on its own. You also need the decisions: which rule held a transfer, who released it, and why.
Then review the rules on a schedule, quarterly for high-risk corridors, and whenever the corridor changes. Compare what the rules say with what actually happened: how many transfers were held, how many cleared, how long reviews took, and how many overrides there were. A rule that is overridden every week needs changing, not overriding. Record each change and the reason.
Watch out: a limit raised for one customer "just this once" with no reason recorded is exactly the decision an examiner will pick from a sample.
Sources
- The FATF Recommendations (Recommendation 11, record-keeping)
- CFPB, 12 CFR 1005.31 (Regulation E), remittance transfer disclosures
- The Payment Services Regulations 2017 (regulation 43)
- Directive (EU) 2015/2366 (PSD2) (Articles 44 and 45)
Checked October 2026. Regulations change; confirm current requirements with the regulator or your adviser.
Frequently asked questions
Should we stop serving high-risk corridors?
Not necessarily. Many operators serve them safely. What matters is that limits, approvals, pricing and exceptions on those corridors are written down, enforced by the platform and reviewed, so you can show how risk is controlled.
How do we set limits for a high-risk corridor?
Start from your risk assessment: the corridor's rating, typical customer and typical amounts. Set a per-transfer limit, period totals and document tiers, write down why, and review them quarterly or when the corridor changes.
What makes an approval tier a real rule?
Specific triggers, such as a risk band or an amount, a named owner and a time to decide. If two staff would reach different answers on the same transfer, the tier is still judgment.
Who can raise a customer's limit on RemitSo?
An officer, from the customer's page. A customer above the top tier cannot send until that happens, and every override of an AML limit is recorded in the audit log.
Does RemitSo decide which transfers to approve?
It applies your rules: transfers below your risk threshold flow on their own, and risky ones wait for a person. Your team decides what happens to the held transfers.