Most compliance leads at a money transfer operator start the day the same way: open five pages to find out what is waiting. Identity checks for review in one place, held transfers in another, sanctions hits in a third, and the customers who worry them most in a spreadsheet someone keeps by hand. A compliance dashboard should replace that tour with one view that says what needs a decision, who it belongs to and where to go next. This guide is for MLROs, compliance managers and operations leads who either have a dashboard they do not trust or are choosing a platform that has one. Figures in the examples are illustrative.
The principle: a compliance dashboard is a worklist with numbers on top, not a wall of charts. Every figure should lead to the records behind it, and nothing should be on it that the platform cannot actually measure.
Start with the questions, not the charts
A dashboard earns its place when it answers questions the team would otherwise ask out loud. In a remittance business there are six.
| Question | What to show | Where a click should take you |
|---|---|---|
| Who is waiting on an identity decision? | Identity checks that need compliance review | The customer's profile and documents |
| Which transfers are held for us? | Transfers under review, and how long they have waited | The transfer and the checks that held it |
| Which screening hits has nobody ruled on? | Possible matches awaiting a decision, kept apart from confirmed matches | The screening record and the listed entity |
| Where is our risk concentrated? | Customers by risk band, using one set of bands everywhere | The customers in a band |
| Whose documents are running out? | Expired and soon-to-expire identity documents | The customer's documents |
| Who should we look at first? | A worklist of the highest-risk customers | Each customer's risk page, with the evidence |
If a chart does not help someone decide what to do next, it probably does not belong on the screen.
Doing it with RemitSo
RemitSo, a white label remittance platform, has a Compliance Dashboard in the admin panel that brings the compliance programme into one view. It is built on the same principles as this guide.
- Granted part by part. Each part of the Compliance Dashboard is granted separately. A screening analyst can see the screening figures without the customer worklist; a compliance manager can see both. Roles decide who sees each page and uses each button, and staff sign in with two-step sign-in.
- One set of figures. The compliance decisions waiting on Scout, the page that checks everything every 5 minutes, are the same figures as the Compliance Dashboard. The highest-risk customers on the main dashboard match it too. Nobody argues over which number is right.
- One set of risk bands. Low 1 to 25, Medium 26 to 50, High 51 to 75, Critical from 76. At or above the installation's threshold (50 unless changed), transfers stop Under Review for a person.
- Evidence behind the worklist. A customer's risk page explains each check that fired in plain language, links to the records that tripped it, and keeps the evidence.
- Possible is not confirmed. A sanctions hit is a possible match until an officer rules on it. An "Awaiting decision" filter shows the hits nobody has ruled on, and a confirmed match raises its own alert. Nothing is blocked by a match on its own.
Behind the view sit 47 ready-made risk indicators you combine into your own rules, screening of every sender and recipient against 8 sanction lists reloaded every night, and 43 alert events you can route to the right people. See the admin features.
A compliance lead's first half hour
Here is how the questions turn into a routine. The operator is mid-sized, sends to six corridors and has a compliance team of three: a lead, a screening analyst and a KYC reviewer. The figures are illustrative.
| On screen | Figure | Decision | Owner |
|---|---|---|---|
| Possible sanctions matches awaiting decision | 3 | Two are a common name with a different date of birth: ruled "not this person", so they are not flagged again. One needs more information. | Screening analyst |
| Transfers under review | 7 | Oldest has waited 20 hours. Sort by age and clear the two that will miss their payout window first. | Lead |
| Identity checks needing review | 5 | Four are clear on review. One selfie does not match; ask for a new check and record the reason. | KYC reviewer |
| Customers in High or Critical | 18 (up from 11 last week) | Open the band. Nine of the new ones share one recipient. That is a pattern, not noise. | Lead |
| Documents expired or expiring in 30 days | 26 | Nothing to do today unless a customer is mid-transfer; the platform asks for a replacement. | KYC reviewer, weekly |
The most useful line on that screen is the jump from 11 to 18 high-risk customers. A daily count would not show it, but a shared recipient across new customers is the kind of link that turns into an investigation. The lead opens each customer's risk page, sees which indicators fired, and decides whether this becomes a case. Our guide to working an AML case from alert to SAR picks up from there.
Useful test: time how long it takes your team to answer the six questions today without a dashboard. If it takes more than fifteen minutes, that is time your team spends finding work instead of doing it.
What each part should show, and what it should not
Identity verification. Show what is waiting for a person, not everyone who ever passed a check. On RemitSo, a reviewer can override a check with the reason kept, and the provider's original record and liveness recording are kept as evidence.
Held transfers. Show the count and the age of the oldest. Age matters more than count: seven transfers held for an hour is a normal morning; one held for three days is a complaint on its way. Risky transfers wait for a person; everything else flows on its own.
Sanctions screening. Keep possible matches and confirmed matches apart. They are different states, and a dashboard that adds them together overstates your exposure. Per-list counts belong inside one sanctions section, not in eight separate tiles. See how sanctions screening runs itself.
Customer risk. A distribution across bands, using the same band names as every other page. If one page says "Very High" and another says "Critical" for the same customers, filtering and reporting break.
Document expiry. Expired and expiring soon. On RemitSo expiry is checked nightly, and transfers relying on an expired document go back to asking the customer for a replacement instead of failing at the payout partner days later.
The worklist. The highest-risk customers, each one click from the evidence. This is the part that turns a reporting page into a working tool.
| Role | Sees | Does not need |
|---|---|---|
| Screening analyst | Screening figures | Customer worklist |
| KYC reviewer | Identity reviews, document expiry | Screening figures |
| Compliance manager or MLRO | Every part | Nothing hidden |
| Operations lead | Transfers held, to plan payouts | Individual customer risk |
Show what the platform knows, nothing more
It is tempting to put every metric from a requirements document on the screen: structuring detected, large cash transactions, confirmed matches, average screening time. If the platform does not record the event or its outcome, the number is a guess dressed as a fact, and it creates false confidence.
- No data, no metric. If an outcome is not recorded, leave the tile out and log the gap as a product requirement.
- Every figure is traceable. "18 possible matches" should open the 18 screening records. If it cannot, it is a reporting screen, not a compliance tool.
- Keep the dashboard read-only. Decisions happen on the customer, transfer or screening record, where the reason is kept. A dashboard that changes data quietly is an audit problem.
- Do not rewrite history. If older records never captured a value, leave them as they are. Do not fill gaps with estimates.
Watch out: a dashboard that shows confirmed sanctions matches when the system only records possible ones will be read by an examiner as a statement of fact. Show the states your platform really records.
Checklist before you rely on a dashboard
| Check | Pass if |
|---|---|
| Traceability | Every figure opens the records behind it |
| One source | The same figure on two pages always agrees |
| Bands | One set of risk bands across the platform |
| Screening states | Possible and confirmed matches are shown apart |
| Access | Each section can be granted on its own |
| Age | Held items show how long they have waited |
| Read-only | Decisions are made on the record, with a reason kept |
| No invented metrics | Nothing appears that the platform does not record |
Pair the dashboard with alerts, so the urgent items reach someone before the morning check: see alert routing for money transfer teams. To book a walk-through of the Compliance Dashboard, book a demo.
Frequently asked questions
What should a compliance dashboard for a money transfer business include?
Identity checks waiting for review, transfers held for compliance, sanctions hits awaiting a decision, customers by risk band, document expiry, and a worklist of the highest-risk customers, each linked to the records behind it.
Should every AML metric be on the dashboard?
No. Only show what the platform reliably records. A precise number built on missing data creates false confidence, which is worse than no number.
Should everyone in compliance see every section?
Not necessarily. On RemitSo each part of the Compliance Dashboard is granted separately, so a screening analyst can see screening figures without the customer worklist.
Do the dashboard figures match the rest of the platform?
On RemitSo, yes. The compliance decisions waiting on Scout are the same figures as the Compliance Dashboard, and the highest-risk customers on the main dashboard match it.
Can staff change customer or transfer data from the dashboard?
They should not. The dashboard shows what needs a decision; the decision is made on the customer, transfer or screening record, where the reason is kept.