From Checkout to Reconciliation: How topropay Unifies Payment Data Across Every Acquirer

If your company's monthly close drags into the second week of every month, the bottleneck is rarely accounting. It is payments. The finance team is matching settlement files from four or five acquirers against captures in your order system, reconciling fees that show up in three different formats, and chasing chargeback adjustments that landed in the wrong reporting period. Multiply that by every market and every payment method, and the close becomes a multi-day reconstruction exercise.

topropay collapses that work into a single ledger. Every capture, settlement, fee, chargeback, and payout — across every acquirer in your stack — is ingested, normalized, and reconciled inside one feed. The teams that adopt it tend to describe the same outcome: the close becomes routine, and the data finally tells one consistent story. The reconciliation and reporting page covers the matching logic and export targets in more detail.

The rest of this piece walks through what unified reconciliation actually means at the data layer, and why it matters once your payments stack outgrows a single PSP.

The reconciliation problem nobody plans for

Every merchant that adds a second acquirer for the right reasons — better approval rates, lower fees, market coverage — inherits a hidden cost: a second reconciliation pipeline. By the time a third or fourth acquirer is in production, that hidden cost is one of the biggest line items on the finance team's calendar.

The typical pain points stack up quickly:

•        Each acquirer ships settlement data in a different file format (CSV, XML, MT940, custom JSON)

•        Fee schedules are itemized differently — some bundled, some per-line, some only summarized

•        Chargeback adjustments land days or weeks after the original transaction and have to be matched back manually

•        FX conversions happen at different rates and different times depending on the acquirer

•        Refund timings differ; some net out at settlement, some post separately

•        Payouts batch differently — daily for one acquirer, T+2 for another, weekly for a third

The finance team is doing the same conceptual work — match capture to settlement, account for fees, reconcile to bank — but doing it once per acquirer, in once per format. The error rate goes up, the close gets longer, and the audit trail gets harder to defend.

What topropay actually ingests

topropay sits above the acquirers and pulls in the raw operational data from each one automatically. The ingestion layer covers:

•        Settlement files in whatever native format the acquirer ships

•        Per-transaction fee breakdowns (interchange, scheme, acquirer markup, processing)

•        Chargeback notifications, representments, and final outcomes

•        Refund events and their settlement timing

•        Payout batches and bank credit confirmations

•        FX rates applied per transaction at authorization time

Everything is normalized to a single schema before it hits the ledger. That schema is the same whether the underlying acquirer is Adyen, Worldpay, Checkout.com, Stripe, Nuvei, Worldline, or any of the others in the topropay connector catalog. Your reconciliation team queries one data model instead of five.

How matching works inside topropay

The matching engine inside topropay handles the four most expensive reconciliation tasks automatically:

1. Capture-to-settlement matching — every captured payment is linked to the settlement line that funded it, even when the acquirer batches them differently than the order timestamp would suggest
2. Fee itemization per transaction — interchange, scheme, acquirer markup, and topropay's own fee are broken out per payment, so true cost-of-payment is visible at the row level
3. Chargeback lifecycle tracking — the initial dispute, the representment, the final outcome, and the corresponding ledger adjustments are all stitched back to the original transaction
4. Payout-to-bank reconciliation — settled batches are matched against actual bank credits, so unmatched amounts surface immediately instead of at month-end

Mismatches do not get silently absorbed. They get flagged in the dashboard with the specific reason — missing settlement line, fee discrepancy, FX rounding, late-arriving chargeback — and queued for review.

One ledger, in real time

The output of all that ingestion and matching is a single unified ledger that the finance team works against. Inside topropay, that ledger is live — every event updates it in near real time rather than at end-of-day batch.

Practical implications:

•        A finance lead can see today's processing across every acquirer at any time without exporting anything

•        Discrepancies surface within hours, not at the next month-end close

•        Period-end exports are a one-click operation rather than a multi-day data assembly

•        Auditors get one canonical source for every payment, fee, and adjustment

Exporting where your finance stack lives

Reconciliation data is only useful where the rest of the financial workflow happens. topropay pushes the normalized ledger out to wherever you need it:

•        ERP systems — NetSuite, SAP, Microsoft Dynamics, Oracle

•        Data warehouses — Snowflake, BigQuery, Redshift

•        Accounting platforms — Xero, QuickBooks for smaller setups

•        Custom destinations — via webhook and API

The push is configurable. You choose the cadence, the granularity, and the field mapping. Most finance teams set it up once and never touch the integration again.

What changes for the team

The before-and-after pattern looks roughly the same across merchants that move onto topropay:

•        Monthly close compresses from 5–10 days to 1–2 days — finance is reviewing one reconciled ledger instead of stitching five sources together

•        Engineering effort on payment reporting drops to near zero — no more custom ETL pipelines per acquirer

•        Cost-of-payment becomes visible per transaction — pricing decisions and PSP renegotiations get sharper

•        Audit prep takes hours instead of weeks — the topropay ledger is the canonical source

•        FP&A models become more accurate — payments revenue is reconciled to bank, not estimated from gateway data

The compounding benefit is that finance and engineering stop arguing about whose numbers are correct. There is one set of numbers.

Multi-currency and cross-border specifics

For merchants operating in multiple European markets, the reconciliation surface area grows non-linearly. Each additional currency introduces FX timing, multi-leg settlement, and cross-border fee structures.

topropay handles the multi-currency case as a first-class feature:

•        FX rates are captured per transaction at the point of authorization

•        Settlement currency, presentment currency, and bank deposit currency are all tracked separately

•        Cross-border scheme fees are itemized and matched to the originating transaction

•        Per-country regulatory levies, where applicable, are broken out in the ledger

For a merchant with EUR, GBP, PLN, SEK, and CHF exposure, that level of detail is the difference between a defensible quarterly close and an ongoing reconciliation backlog.

The takeaway

Reconciliation is one of those problems that does not look serious until it is. A single acquirer is manageable. Two is irritating. Three or more is a structural drain on finance and engineering, and the only way out is to move the data layer above the acquirers.

topropay is that data layer. One ingestion pipeline. One normalized schema. One ledger. One export to your ERP or warehouse. The work that took five days every month becomes the work that takes one — and the data finally agrees with itself.

A short discovery call with the topropay team will model what unified reconciliation looks like against your actual acquirer mix and close timeline. The exercise usually surfaces a few line items the finance team already suspected were wrong.