PSP payout reconciliation

Your PSP payout never equals your revenue.Can you explain every cent?

Refunds, fees, chargebacks, and settlements don’t line up across systems. Actuals detects and resolves mismatches across all of them as they happen.

Connected to AdyenStripePayPalMollieBraintreeand others
Order 12345PSP A · card · EUR
Expected€77.80
Received€77.30
Difference−€0.50
?Where?
  1. Order event€100.00
  2. Payment captured at PSP A€100.00
  3. Processing fee−€2.50
  4. Expected settlement€97.50
  5. Refund to customer−€20.00
  6. Fee returned by PSP A+€0.30
  7. Expected after refund€77.80
  8. Bank received€77.30
  9. €0.50 unexplainedFlagged against this transaction ID and this journal, not netted into a suspense balance that nobody owns.−€0.50
Illustrative example from the Actuals blog, not a customer case.

Sound familiar?

Monday morning. The downloads begin.

  1. Someone opens Adyen. Downloads the settlement report.
  2. Opens Stripe. Downloads that one too.
  3. Then Mollie. Then PayPal.
  4. Four tabs, four exports, four slightly different formats.

It’s 9am and nothing has been reconciled yet.

That’s not a process — that’s a risk that grows with every new channel you add.

The PSP black box

On the left, what your customers pay. On the right, what lands in your bank. In between, a lot can happen.

Bram van Kessel, Actuals, at the order-to-cash break-out of Finance Unlocked 2026

How Actuals handles it

Not just a number that doesn’t match. A flagged exception with the reason.

  • All PSP sources connected via native API
  • Every transaction matched to settlement and bank statement
  • Exceptions flagged with root cause

Live within weeks. No IT project required.

Customer stories

Differences stopped hiding inside totals. They became visible immediately.

Stripe

BeforeStripe data and the internal platform told different stories. Finance was closing the books with doubt instead of certainty.

With ActualsActuals connected Stripe and the internal platform to the data warehouse, automated journal entries and made mismatches visible on a daily basis.

“When I joined, the accuracy of the data simply wasn’t there. Actuals fixed that. Now the data is accurate and that changes everything.”VP Finance, Catawiki
2 daysto a live proof of conceptRead the story
PayPal and more
“At Recharge we do millions of transactions, each containing multiple variables, making things really complex. Actuals provides us with the comfort of control and is also scalable towards the future.”Freddy Dijkman, Recharge
Read the story
Adyen

Actuals automated the daily processing of Adyen settlement batches, allowing the finance team to track which orders had been invoiced and whether those invoices were recorded in NetSuite.

Read the story
Orders, payments, refunds

Issues surfaced early. Audits became easier. Month end became calmer.

Read the story

Questions

What finance teams ask about PSP payouts.

Still a question?Talk to Peter Engel, founder of Actuals.Book a 30-minute call
What is payment reconciliation?

Transaction reconciliation matches financial records across systems: order management, PSP, bank settlement, and ledger system. The goal is to ensure they agree. Without it, downstream processes such as close, audit, and reporting operate on data that may not be correct. At scale, manual reconciliation in Excel becomes unsustainable. Automated platforms like Actuals match continuously as transactions occur, surfacing mismatches within hours rather than at month-end, when they are harder to fix.

Why doesn’t my PSP payout match my revenue?

Each payment provider reports settlements in its own way. Some include fees inline and others report them separately. Some group by merchant and others by batch. Cut-off times, currency conversion and reference identifiers all vary. The same customer payment can arrive in three different shapes from three providers, on three schedules.

Matching aggregated amounts can hide offsetting errors. A duplicate and an omission of similar value will cancel each other out in a total, leaving both errors undetected.

How does Actuals handle refunds, chargebacks, and fees?

Refunds are reconciled against the originating transaction, with correct timing and revenue reversal. For prior-period refunds, adjustments are handled automatically without reopening closed books.

Chargebacks are tracked back to the originating transaction even when they arrive weeks or months later. Period adjustments are automatic.

Fees are recognised separately from transaction revenue, reconciled to PSP settlement data, and booked to the correct expense accounts and periods.

Multi-currency transactions are converted at the correct exchange rate for the transaction date. FX differences between transaction date and settlement date are calculated and posted automatically to the correct accounts.

All of the above maintain a complete audit trail from operational event to journal entry. Every number is traceable. Every period is clean.

Which PSPs does Actuals connect to?

PSPs: Adyen, Stripe, PayPal, Klarna, Nuvei, Mollie, Buckaroo, Braintree, Checkout.com, Worldline, Worldpay, and others.

All integrations are pre-built and centrally maintained by Actuals. When an API changes, we update it. Your team does nothing.

Can I use AI or Python to reconcile my payouts?

For low volumes or internal tools, AI-generated code or Python scripts can get the job done. For enterprise financial operations, they have four critical limitations: no certification, no audit trail, no maintained integrations and no revenue recognition logic.

A script that works at 10,000 transactions often fails at 100,000. Race conditions, timezone drift, partial settlements, late chargebacks. Each one is a separate incident, discovered at the worst possible moment.

Do I need a sub-ledger?

You likely need one if: you process 50,000 or more transactions per month, you operate across multiple PSPs, you spend days each month on reconciliation, or you have audit traceability concerns.

If two or more of these are true, the spreadsheet is not the problem. The missing infrastructure is.

How long does implementation take?

A typical implementation ranges from a few weeks for straightforward configurations to several months for complex multi-entity, multi-currency environments.

The technical integrations are pre-built. No custom coding is required.