The Operations Dashboard: The Numbers a Money Transfer Business Should Read Every Morning

In most established money transfer businesses, the first hour of the day is spent assembling a picture: a report from finance, a list of stuck transfers from operations, a note from compliance. Each person has a fragment, and decisions wait until somebody stitches them together.

This guide is for founders, general managers and operations heads who want one short, repeatable morning read. It covers the figures on the RemitSo Dashboard, what each one tells you, what to do when it moves, and how the Dashboard fits with Scout, which finds exceptions, and the Compliance Dashboard, which shows the compliance programme in one view.

The Dashboard in RemitSo's admin panel puts the business figures on one page. It does not interpret them for you: your team still decides what a movement means, who follows it up and whether anything should change.

A morning dashboard tells you, in a few minutes, whether the business is where you expected and where to look if it is not.

The RemitSo Dashboard shows:

• a monthly overview of sales, customers, volume and revenue;
• a sales overview over time;
• pending transaction actions: missing documents, payout issues and pending reviews;
• total sales and profit for the last 7 days;
• sales by destination and the top destinations;
• the customer registration trend;
• your own last sign-in time and location.

Two other screens do different jobs. Scout checks the platform every five minutes and lists what needs an operator: transfers, payouts and payments needing action, compliance decisions waiting and system health. The Compliance Dashboard brings the compliance programme into one view. The Dashboard tells you how the business is doing; Scout tells you what is stuck; the Compliance Dashboard tells you where the compliance programme stands.

The monthly overview puts four figures side by side: sales, customers, volume and revenue. Read them together, because each one on its own can mislead.

• Sales and volume moving together is normal. If sales rise but volume does not, customers are sending more often in smaller amounts; if volume rises but sales do not, fewer customers are sending larger amounts. Both are worth knowing because they change what each transfer earns.
• Revenue against volume tells you whether pricing is holding. Revenue that grows more slowly than volume usually means a shift towards cheaper corridors, a fee band customers have moved into, or an offer running longer than intended.
• Customers tells you how wide the base is this month. A month carried by the same customers sending more is less secure than one with a broad base.

Early in the month the figures are noisy. Note where they stand against the same point last month, and keep that note yourself so the trend is clear.

Remittance has a rhythm. Sending often rises around paydays, falls on particular weekdays and shifts around festivals and holidays in the countries your customers send to. After a few months of reading the sales overview, you will know your own rhythm well.

What you are looking for each morning is a break in it: a day that should have been busy and was not, or a quiet stretch that started on a specific date. A sudden drop that matches nothing in the calendar often has an operational cause: a payment method not working, a corridor paused, or a rate that stopped being competitive. When you see one, check Scout's system health and the payments needing action before assuming it is demand.

The pending transaction actions panel is the one place on the Dashboard that is about individual transfers. It groups them into three kinds, each with a different owner.

• Missing documents: transfers waiting for something from the customer. These belong to customer service or onboarding. Customers asked for an additional document are told, but a short, friendly follow-up from your team often closes the gap faster. Our guide to rescuing stalled onboarding covers how.
• Payout issues: transfers whose payout has a problem. These belong to operations, who will find the detail in Scout's payouts group and in the alerts. Our guide to finding failed payouts early covers the follow-up.
• Pending reviews: transfers waiting for a person to decide. These belong to compliance. Risky transfers wait for a person while everything else flows on its own, so this number is the size of the human queue.

The Dashboard is where a manager sees all three at once and checks that each has an owner. The work itself happens in the transaction, the customer record and Scout.

The Dashboard shows total sales and profit for the last seven days. A rolling week smooths out single-day noise and gives you a figure you can compare each Monday.

The useful reading is the relationship between the two. If sales are steady and profit falls, something about what each transfer earns has changed: a rate rule, an offer, a fee change, or a shift in the mix of corridors and payment methods. If both fall together, look at demand and at operations. If profit rises faster than sales, check that it is deliberate and not a rate that has drifted out of line with the market.

The Dashboard figure is a prompt, not the books. When finance needs to explain a movement, RemitSo's double-entry accounting records every payment, payout, refund, fee and FX movement automatically, and any balance can be opened to see the transactions behind it. Our guide to double-entry accounting for remittance covers that side.

Sales by destination and the top destinations list show where your business actually goes. For most established operators, a small number of destinations carries much of the business, and that is fine as long as you know it and plan for it.

Read this panel for two things. First, concentration: if one destination carries a large share, a pause on that corridor or a problem with its payout partner affects a large share of your customers, and your contingency plans should reflect that. Second, movement: a destination climbing the list is a corridor worth reviewing for pricing and capacity, and one sliding down may have a rate or fee that has fallen behind. Our guide to payout corridor strategy covers what to do with that information.

The customer registration trend shows how many people are signing up over time. On its own it measures interest. Read next to the customers figure in the monthly overview, it tells you more.

Registrations rising after a campaign or a corridor launch is the expected result. The question is whether those people go on to send. If registrations climb while the month's customers figure does not follow over the next few weeks, sign-ups are not turning into transfers, and the place to look is onboarding: identity checks left unfinished, documents requested and not supplied. In RemitSo the ID check and selfie happen inside the first transfer rather than at sign-up, and customers can resume an unfinished check, which helps; but a stalled first transfer still needs a nudge from your team.

The Dashboard shows your last sign-in time and location. It takes a second to read and it is worth the habit: if the time or place is not one you recognise, someone may have used your account. Report it at once. Every sign-in by staff is logged in Login Sessions with time, IP address, city, country, app, operating system and whether two-step sign-in was completed, so your security lead can check the details.

Put the sections above together and you have a routine a manager can run before the first meeting. Read in this order: anything urgent first, then the business picture.

The numbers below are illustrative, chosen to show the reasoning rather than to describe any real operator.

The general manager of an established operator opens the Dashboard at 08:30.

Step 1: sign-in and pending actions

The last sign-in is Friday evening, from the office. Pending transaction actions show 14 missing documents, 3 payout issues and 9 pending reviews. Last Monday's note said 4 pending reviews. The manager asks the compliance lead whether something changed; the answer is a risk rule tightened on Thursday, and they agree to look at what it is catching.

Step 2: the week

Last-7-days sales are close to the previous week's note, but profit is down by roughly a tenth. Nothing in the calendar explains it. The pricing owner checks: a first-transfer rate for the New group was meant to end on Friday and was left running. It is stopped the same morning.

Step 3: destinations and registrations

One destination has moved from fifth to third since a corridor broadcast ten days ago, and registrations rose in the same week. The monthly customers figure has not yet followed. The manager asks customer service to contact recent sign-ups who started a first transfer but did not finish.

Step 4: hand over to Scout

The 3 payout issues are already in Scout's payouts group with alerts attached, and operations owns them. The manager does not open them; they check at the afternoon stand-up that all three are resolved.

The whole read took about ten minutes and produced three owned actions. None of them needed a report to be built.

The Dashboard opens the admin panel, with Scout and the Compliance Dashboard alongside it.

• Monthly overview: sales, customers, volume and revenue on one page, so your team starts the day with the same picture instead of assembling it.
• Sales over time: the pattern of the business at a glance, so your team spots a break early and your customers are less likely to meet a problem nobody noticed.
• Pending transaction actions: missing documents, payout issues and pending reviews counted together, which benefits both: each queue gets an owner, and customers waiting on one are not forgotten.
• Last 7 days sales and profit: a rolling week to compare each Monday, so your team catches pricing drift before month-end.
• Sales by destination and top destinations: where the business goes, so your team plans pricing and contingency around the corridors that matter most.
• Customer registration trend: sign-ups over time, so your team can see when interest is not turning into transfers.
• Last sign-in time and location: a daily check on your own account, so your team notices unrecognised access quickly.
• Scout and the Compliance Dashboard alongside: exceptions every five minutes and the compliance programme in one view, so your team works the detail where it lives.

What your team still does: read the figures, decide what a movement means, assign the follow-up and check it is done. Related reading: routing alerts to the right people and building a compliance dashboard.