Use case · Knowing where you stand daily
Do you know today what came in yesterday?
If you only look at close, you know nothing for a month and then everything at once. By then the oldest difference is weeks old, and nobody remembers the order behind it.
“Reconciliation shifted from a monthly firefight to a daily control.”
Drag through October, then switch how often you check. The two numbers show what you know on that day.
Illustrative month for a high-volume webshop. The numbers are an example.

Why yesterday is hard
Sold yesterday. Paid out days later.
What came in yesterday is not what you sold yesterday. Each payment method settles on its own clock, so a daily position needs every sale matched to the payout it ends up in.
Pick a payment method. The row shows the day of the sale and the window in which the money can arrive.
Sources: Adyen Help Center, What is settlement delay (1 to 45 days depending on the method, cards up to 7, iDEAL up to 4); Stripe Docs, Payout reconciliation report (with instant payouts Stripe cannot say which transactions a payout contains).
This morning’s list
1,240 differences are not 1,240 problems.
“Not every mismatch is an error. Some are timing differences that will resolve in the next settlement cycle. Others are known exceptions, such as cancelled orders, that can be explained and categorized.” From the Actuals blog
Each dot is two differences from yesterday. Press the button to sort them by cause.
- Settled after the cut-offTiming. Resolves with the next payout.1,104
- Fee charged on the batch, not per orderKnown pattern. Split per order, then matched.90
- Refund in a later batchKnown pattern. Linked to its original order.36
- True exceptionsPaid at the provider but missing in the backend, or a different amount. Each one gets an owner today.10
Illustrative morning. Actuals on its product page: “Clear separation between bulk issues and true exceptions”.
How Actuals handles it
Open the app. See if today’s numbers can be used.
“A key thing we wanted to include is not just which reports are available but also if you can use them at all. If something is wrong, you can work on the fix first instead of working with incorrect or incomplete data in your reports.”
The overview shows which periods are open and which are closed, with the monitoring events in one place. What used to be called unmatched transactions is now called exceptions.
Reports for yesterday
Click a report to see whether you can use it this morning.
Illustrative overview, after the description of the new interface by Peter Lem on the Actuals blog.
From the customer files
Three teams that moved from the month to the day.
Switch between Before and Now. Each card shows its own story, in the words of the case.
Travel · Interrail“Reconciliation did not scale. It lived in Excel, took weeks at month end.”
“Differences stopped hiding inside totals and became visible immediately.”
Read the Interrail story
Online marketplace · Catawiki“Stripe data and the internal platform told different stories.”
“Actuals connected Stripe and the internal platform to the data warehouse, automated journal entries and made mismatches visible on a daily basis.”
Read the Catawiki story
“The finance team was tasked with reconciling vast amounts of data every month.”
“Actuals automated the daily processing of Adyen settlement batches.”
Read the Helloprint storyRelated moments
What a daily position makes easier.
Want to know where you stand tomorrow morning? The 15-minute Actuals scan shows which of your sources you can already match every day.


