Revenue dashboards can show successful payments while the bank receives a smaller, later, or differently denominated amount. The gap usually comes from settlement timing, fees, refunds, reserves, currency conversion, or a reconciliation failure that no one owns end to end.
At 8:12 on a Tuesday, Maya, the composite finance operator in this example, had a board deck open on one screen and three payment-provider dashboards on the other. Her company had sold subscriptions in the UK, the US, and Singapore over the weekend. Each dashboard showed green success notifications. The revenue slide looked strong.
The bank balance did not.
She had 48 minutes before the board meeting. If the cash figure was wrong, the runway forecast was wrong too. A payment marked successful can mean a customer was charged. It does not guarantee that the company can spend that money today, or that it will arrive in the expected account at the expected amount.
A successful payment starts the cash journey
The first error is treating authorization, capture, settlement, and bank receipt as one event. They are separate events with separate timestamps.
A customer’s card may be authorized on Friday, captured on Saturday, and paid out to the company on Tuesday. A marketplace or payment provider may hold funds until a payout threshold is met. Cross-border payments can enter a conversion process before they reach the operating account. A charge can also succeed and later reverse through a refund, dispute, or failed settlement.
Maya’s weekend total was real as a sales signal. It was not yet a cash number.
That distinction matters most when a company is growing across markets. The finance team may see gross transaction value in one tool, recognized revenue in another, and bank deposits in a third. Each number can be correct for its purpose. Using one as a substitute for another creates a forecast that looks precise until payroll, vendor payments, or a board question exposes the difference.
A useful starting point is to label every dashboard by what it actually measures: customer payment attempts, successful captures, settled funds, available balance, or cash received. “Revenue” should not become the catch-all label for all five.
Reconciliation needs a path for every transaction
Maya stopped comparing dashboard totals to the bank’s total. She started tracing individual transactions.
For each market, she needed a clear path:
- What did the customer pay, and in which currency?
- Which provider processed the payment?
- What fees, taxes, reserves, or refunds reduced the payout?
- When did the provider mark the funds as available?
- Which bank account received the payout, and on what date?
That work reveals the common traps. One provider may pay out net of fees while another deposits gross revenue and invoices fees later. A US payout may land on a different schedule from a UK payout. A reserve can sit in the provider balance for weeks without appearing in the operating account. Currency conversion can make a local-currency total look close enough until a few percentage points compound across hundreds of transactions.
The goal is not a prettier spreadsheet. It is an auditable bridge between customer payments and cash. A board member should be able to ask why the bank received less than the payment dashboard showed and get an answer that separates timing differences from permanent deductions.
The dangerous gap is the unexplained one
Some differences are expected. A two-day payout delay is a timing item. Processor fees are a cost. A documented reserve is restricted cash. A refund is a reversal.
The risk begins when the team cannot classify the gap.
Maya found that one market’s payout report had been filtered by transaction date, while the bank export used settlement date. Another provider had routed funds to an older account set up during launch. Neither problem changed the customer-facing product. Both changed the cash picture presented to the board.
This is where ownership matters. Revenue operations may own payment configuration. Finance may own close. Treasury may own bank accounts. Customer support may process refunds. If no one owns the reconciliation across those boundaries, the company gets a set of accurate local reports and an unreliable global answer.
The operating rhythm should match the company’s exposure. A startup processing meaningful daily volume needs daily exception checks, even if the formal close remains monthly. Flag payouts that are late, deposits that lack a source report, large fee changes, reserve movements, and transactions that remain successful in the payment tool but never reach settlement.
For a related example of how operational ambiguity spreads when accountability is split, see Friday, 4:47 PM: The Accountability Split.
Build the board number from cash backward
Before the meeting, Maya replaced a single “revenue received” line with three numbers: customer payments captured, funds pending settlement, and cash received in bank accounts. The first number showed demand. The second showed short-term exposure. The third supported the runway forecast.
That presentation created a more useful conversation. The board could see that the business had collected demand across three markets, while finance still needed to resolve a routing issue and confirm payout timing. No one had to guess whether a green payment notification meant cash was available for next week’s obligations.
The practical discipline is simple: reconcile by transaction or payout batch, preserve the provider report with the bank record, and assign an owner to every unmatched item. Do it before the deck is due. The next morning’s cash forecast should begin with money the bank can actually see.
Comments
No comments yet.