How it works
Follow one payment from order to ledger.
Tuesday, 21:14. A customer pays €59.95 for an order. By the next morning, three systems have recorded that payment: your order system, Adyen and your bank. Each one uses its own format and its own timing. This page follows it through Actuals until it is one line in your General Ledger.

€59.95Tue 13 Oct 2026 · 21:14
- Order systemorder.status: paid
- AdyenSettled, fee 0.29
- BankPayout, three days later
Three systems, three formats. Nothing tied together yet.
The route
Six stops, one payment. See what Actuals makes of it at each one.
Press Next stop or pick a stop on the route. The record on the right changes into what Actuals holds at that stop.
Illustrative example, simplified. Every amount comes from the same order of €59.95.
When it doesn’t match
Most payments match by themselves. Pick what goes wrong with this one.
Matching only tells you matched or unmatched. What saves the time is knowing why, the day it happens.
Choose a problem. The rows, the balance pattern and the status change with it. Then press the button under the result.
Orders
Total 0.00
Adyen payments
Total 0.00
- Balance pattern
- 1-0
- Difference
- 59.95
- Matching percentage
- 0%
- Status
- Unmatched
Illustrative. Actuals adds up the amounts per transaction id on each side and compares the totals.
What it tells you
In practice: when the PSP payout doesn’t equal revenueAfter the journal
October closes. The line stays where it is.
Once a financial period is closed, the transactions in it are read-only. A correction never overwrites what came in. It is a new entry, with its own reference.

Close October, then try to change the revenue line. Add a correction to see what Actuals does instead.
October is open. Lines in an open period can still be edited.
- Source
- Manual entries (general journal entries)
- Date
- 2 Nov 2026
- Period
- November 2026 · open
- Currency
- EUR
Illustrative correction: the fee moves to another account. The original lines in October are not touched.
And back again
Your auditor points at October revenue. Walk it back to Tuesday night.
“An auditor does not test a spreadsheet in isolation. They test whether a transaction can be followed from source to report, whether the same answer comes back when the question is asked again, and whether each change leaves a trail.”
Peter Engel, Founder & CEO of Actuals
“We use Actuals to track all transactions from initiation to our general ledger, ensuring they match with supplier invoices and remain balanced.”
Patrick Roozeman, CEO of MultiTankCard
Press One level down. Each level opens the one below it, until you reach the line that came in.
- General LedgerRevenue · October 2026includes 49.55 from this order
- JournalDaily total · 13 Oct 2026Balanced, debit = credit
- Transaction48213 · Orders ↔ AdyenMatched · balance pattern 1-1
- Raw line · Order system
{"order_id":"48213","status":"paid","total":"59,95","created":"2026-10-13 21:14"}Exactly as it arrived on Tuesday night
Illustrative. Actuals keeps the raw data next to the transactions it made from it. The trail is the same every time you ask.
Where to go next
You followed one payment. Now look at your own chain.
Six factors decide whether your numbers hold
Find the first link in your own chain that breaks, in six questions.
Find your weakest linkHow your data gets into Actuals
Connectors, database access, SFTP or the API, and which one fits your sources.
Read the docs
The whole layer between payments and your ERP
What it does in day-to-day finance, and the two phases to start with.
See the productWant to follow one of your own payments? Talk to the team about your sources, your matching and your ledger.