Multi-PSP reconciliation
Adyen, Stripe, PayPal.Three report formats, one truth?
Actuals normalizes transaction data across PSPs, banks, and platforms. All pulled via native APIs and normalised into one validated financial layer. Daily.
- Merchant Reference
- 12345
- Gross Credit (GC)
- 100.00
- Commission (NC)
- 2.50
- metadata.order_id
- 12346
- amount
- 80.00
- fee
- 1.90
- Invoice ID
- INV-12347
- Gross
- 45.00
- Fee
- −1.66
| Order | PSP | Gross | Fee | Net | |
|---|---|---|---|---|---|
| 12345 | Adyen | €100.00 | −€2.50 | €97.50 | ✓ |
| 12346 | Stripe | €80.00 | −€1.90 | €78.10 | ✓ |
| 12347 | PayPal | €45.00 | −€1.66 | €43.34 | ✓ |
Sound familiar?
A new payment provider should be a small change. In a fragile architecture it is a project.
It needs a new mapping, a new script, and a person who understands the rules well enough to keep them running.
Try it: add your payment providers one by one. 0 of 5 added
All integrations are pre-built and centrally maintained by Actuals. When an API changes, we update it. Your team does nothing.
The first provider is manageable. The fifth one is where the close starts to slip.
The manual process doesn’t scale. Actuals does.
What breaks
When the stack is fragile, small changes create large consequences.
A new payment method adds fields the ERP does not expect.
The order system assigns one reference, the payment provider another, the ERP a third.
Refunds aren’t labeled the same way in Stripe and PayPal.
Each change breaks matching logic and generates exceptions your team resolves manually, until the next change arrives.
PSP APIs change several times per year. When Adyen or Stripe updates their API, your script breaks. Someone has to fix it. That someone is usually the person building the core product.
How Actuals handles it
You never rebuild a PSP connector because a vendor made a change.
- Every source in one layerAdyen, Stripe, Mollie, PayPal, Shopify, marketplaces, bank feeds. All pulled via native APIs and normalised into one validated financial layer. Daily.
- We maintain every connectorAdyen changes their settlement format. Stripe adds a field. We absorb it. You never rebuild a PSP connector because a vendor made a change.
- Switch a PSP or ERPWe absorb the change. You never rebuild financial plumbing.
Live within weeks. No IT project required.
Customer stories
One source of truth, across every provider.

With ActualsPSP statements, transaction data and bank settlements are matched automatically. The team only resolves the outstanding issues.
“Actuals provides us with the comfort of control and is also scalable towards the future.”Freddy Dijkman, CFO, Recharge.com
StripeCatawiki chose Actuals to create a single source of truth between Stripe and their internal systems. Within two days, a proof of concept was live.
Read the story“Without Actuals, reconciliation would be extremely labour-intensive and simply not scalable.”CFO, FlowbirdRead the story
Questions
What finance teams ask about multiple PSPs.

What is reconciliation when it comes to payments?
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.
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.
When don’t I need a multi-PSP layer yet?
If one processor handles all your payments and its reporting already answers your questions, you do not need a multi-PSP layer yet. If your only problem is matching bank lines to invoices, with no fee or FX complexity, a simpler bank reconciliation solution will do the job. And if you are a regulated financial firm looking for client money or safeguarding controls, start with tools built for that work.
What should I ask a multi-PSP reconciliation vendor?
Use these questions with any vendor, including us:
- Can you trace one transaction from the original order to the ledger entry, live, on our data?
- Which fees and FX differences do you calculate per transaction, and where do they land?
- What happens to an unexplained difference? Is it a flagged item with an owner, or a balance that grows?
- Which of our processors are out of the box, and how long does a new one take?
- What is your match rate, how is it measured, and on what kind of data?
- What does your audit trail record, and how long is it kept?
- Does the ERP receive journals, or raw events?
If a vendor cannot answer these with examples, the feature list does not matter.
Can Stripe payments be traced to the ledger?
Almost every product can match a settlement total to a bank line. That is not the hard part. The hard part is what happens to one transaction when it moves through several processors, a refund, a fee and a currency conversion. Where did the money come from, what did each step cost, and which journal did it land in? If a tool cannot answer that for one transaction, it will not answer it for a million.
What happens when a PSP changes its API?
PSP APIs change several times per year. A purpose-built platform absorbs those changes centrally. A custom tool breaks and waits for an engineer to fix it.
All integrations are pre-built and centrally maintained by Actuals. When an API changes, we update it. Your team does nothing.
Which PSPs and ERPs does Actuals connect to?
PSPs: Adyen, Stripe, PayPal, Klarna, Nuvei, Mollie, Buckaroo, Braintree, Checkout.com, Worldline, Worldpay, and others.
ERPs and accounting systems: SAP (S/4HANA and earlier), NetSuite, Xero, Exact, Microsoft Dynamics 365 Business Central, and others.




