Our solution for PSP and payment gateway reconciliation

Match sales, PSP transactions, and bank settlements end to end

PSP reconciliation connects three layers: the order from your system, the transaction from Stripe, Adyen, PayPal or Redsys, and the net deposit in your bank. Embat ingests all three, cross-references them automatically, and ensures every euro is accounted for from checkout to cash.

Ingest sales orders from any source, wherever they live

Sales orders rarely live in the ERP. They sit in your own systems: a marketplace backend, a delivery platform, a ticketing admin. Embat's public API connects to wherever your orders are and brings them into the reconciliation flow alongside PSP and bank data.

psp reconciliation

Break down every settlement into its real components

A single PSP deposit bundles hundreds of sales minus fees, retentions, tips, and chargebacks. Embat unpacks each settlement and posts every component to the right GL account: gross revenue, provider commission, retained balance, net deposit. Precise analytical accounting from day one.

PSP reconciliation with Embat

Automatic ID-based matching that eliminates manual pairing

Every PSP transaction carries a unique ID that corresponds to a sales order ID. The automatching engine pairs them instantly and groups the results into daily reconciliation bundles. Your team focuses only on the exceptions that remain unmatched.

automated reconciliation PSP

Daily reconciliation bundles with clear status tracking

Each day's reconciliation activity is consolidated into a single bundle showing matched transactions, outstanding items, and posting readiness. Bundles marked as complete are ready to post; incomplete bundles show exactly how many transactions and orders remain pending, so nothing slips through.

Post reconciled bundles to your ERP and clear the bridge account in one step

Once a bundle is ready to be posted, posting it clears the customer debt account and recognises the reconciled amount in your general ledger. The system logs who validated each bundle and when, ensuring full traceability from original sale to ERP entry.

Full visibility from checkout to bank account, including money in transit

Money in transit visibility

Refund and chargeback traceability

Accounting-ready PSP data

Checkout-to-GL audit trail

The tangible impact of automated PSP reconciliation

5-day faster close

5-day faster close

Commission transparency with fees control gateway

Commission transparency

Scalable operations with PSP gateways

Scalable operations

Accurate cash position with money in transit forecasting

Accurate cash position

One reconciliation flow,
every gateway

Seamless integration with leading PSPs.

Stripe

PayPal

Adyen

Square

Klarna

Shopify

Mercado Pago

Checkout

Worldpay

American Express

Nuvei

Dlocal

Ready to see what an Intelligent Treasury can do for you?

Frequently Asked Questions (FAQ)

PSP reconciliation is the process of matching three layers of payment data: the original sale from your business system, the transaction recorded by the payment gateway (Stripe, Adyen, PayPal, Redsys), and the net deposit that arrives in your bank account. Unlike bank reconciliation — which matches two layers (bank vs GL) — PSP reconciliation adds the sales order as a third layer and must also deconstruct aggregated settlements into their individual components: gross amounts, fees, retentions, tips, and chargebacks. Embat ingests data from all three layers, cross-references them automatically, and posts each component to the correct GL account. Discrepancies and missing transactions are flagged for review, while the matched majority flows straight into your accounting workflow.

Embat integrates with major payment gateways including Stripe, Adyen, PayPal, Redsys, Worldpay, Mercadopago, Checkout, FB500, Nuvei & Amex through its connectivity module.

PSP transactions are ingested automatically — no manual downloads or CSV uploads. For sales order data, Embat provides a public API that connects to your proprietary systems regardless of where your order data lives — whether that's a custom admin platform, a POS system, or a marketplace backend.

Absolutely. Embat normalises all transactions into a single reporting currency (e.g., GBP or EUR) using real-time exchange rates, while still allowing you to drill down into the original currency for detailed FX risk analysis.

Payment gateways typically bundle hundreds or thousands of individual transactions into a single bank deposit after deducting fees, retentions, and chargebacks. Embat deconstructs each settlement into its components — matching individual sales to PSP transactions, segregating fees by type, calculating rounding differences and tips, and reconciling the net amount against the bank deposit. Discrepancies and missing transactions are flagged automatically for review.

Yes — PSP reconciliation is a pre-accounting process that feeds into Embat's accounting module. Once sales, PSP transactions, and bank settlements are matched, Embat generates reconciliation bundles with the full breakdown (gross, fees, retentions, net). These bundles flow into the accounting module for GL posting, where the standard closed-loop process applies: entries post to your ERP, the confirmation returns to Embat, and bank and GL balances stay aligned. Think of PSP reconciliation as the layer that prepares payment gateway data before it enters your accounting workflow.