The haystack problem: finding a mismatch is the easy part

Finding a mismatch is the easy part. Knowing why it is there is what takes the time. Where a mismatch starts, from the first order to the journal entry, and how MultiTankcard stopped searching.

Peter EngelFounder & CEO · 3 min read

A chargeback comes in on a Tuesday. Nobody records it. The payout that week is a little lower than expected, but it falls within the usual noise.

Three weeks later, at month end, the PSP balance does not tie out. Someone opens the order export, the PSP report and the bank statement, and starts looking for one transaction among thousands.

That is the haystack problem. And the hard part is not finding the needle. It is knowing why it is there.

Why mismatches cost more the longer they sit

Every payment, refund, chargeback and settlement should match across your systems. In practice, finance teams run into the same four things.

  • Mismatches that go unnoticed for weeks, so small errors pile up.
  • Investigations by hand, tracing one difference across several systems.
  • Revenue that leaks away, because an unresolved difference is often money that never arrives.
  • Reporting that does not line up, which adds compliance risk.

Each of these gets worse with time. A difference you see the next morning has one cause and the evidence is still fresh. The same difference at month end is mixed in with all the others.

From the first order to the journal entry: where a mismatch starts

A mismatch rarely starts in the ERP. It starts somewhere in the chain before it.

  1. The data comes in. Orders from your platform, payments, refunds, chargebacks and fees from each PSP, payouts from the bank. A chargeback that never reaches finance is the first gap.
  2. The data is put into one format. Each source uses its own IDs and dates. If they are not translated into one structure, the same event looks like two different ones.
  3. Every transaction is matched. Order, payment, settlement and payout are linked. This is where a mismatch shows up, and where it should get its reason: a fee, a refund, a chargeback, a currency conversion, or a payment that simply has not arrived yet.
  4. Balances are calculated. With every transaction matched, you can see on any day what each PSP still owes you.
  5. Period, revenue and VAT rules are applied. A settlement that lands a day late should still count in the month it belongs to.
  6. The journal entries are made and posted. Only matched, explained totals go to the ERP. Anything still open stays visible until someone resolves it.

When steps 1 to 3 happen in spreadsheets at month end, every mismatch is a search. When they happen every day, most mismatches arrive with their reason already attached. Your team only has to look at the ones that are still unexplained.

What that looks like in practice

MultiTankcard issues mobility cards that work across fuel networks, service providers and banks. Its finance team dealt with unrecorded chargebacks, delayed settlements and transactions that did not match.

With Actuals, mismatches are detected and explained automatically. Chargebacks are resolved faster, so less revenue is lost. Settlements line up with what was expected, which also makes forecasting more accurate. And all transaction data now sits in one source of truth, instead of being pieced together at month end.

Does it take more work to check every day?

It takes less. Searching is what takes time, and a daily check leaves almost nothing to search for. A difference that is one day old takes minutes to explain. The same difference four weeks later can take an afternoon, or end up in a suspense account.

The work that remains is the part that needs a person: deciding what an unexplained difference means and who should act on it.

The question to ask

How long does a mismatch sit in your books before someone knows why it is there? If the answer is "until month end", you are still searching haystacks.

The Actuals scan takes 15 minutes and shows where your payouts and your orders first stop matching.

In practiceHow many days of your close go to explaining differences?

Written by

Peter EngelFounder & CEO