What Is Payment Reconciliation

Payment reconciliation is the operational backbone of any ISV that touches money. It’s unglamorous, rarely discussed in pitch decks, and absolutely critical to running a payments business.

Why Reconciliation Exists

Every payment transaction creates records in multiple systems that should agree but often don’t:

• Your application database records what the customer was charged
• The payment gateway records what was authorized
• The payment processor records what was settled
• The merchant’s bank records what was deposited

Reconciliation is the process of matching these records and finding the gaps.

When everything works, the numbers match. When they don’t — and they frequently don’t — reconciliation is how you find out before your merchants do.

The Three-Way Match

Professional payment reconciliation uses a three-way matching process:

Match 1: Application ↔ Gateway/Processor

Compare your internal transaction records against the processor’s settlement report. Every transaction your app recorded should appear in the settlement file, with matching amounts (minus fees).

Common discrepancies:

• Transactions your app shows as “completed” that the processor shows as “declined” (race conditions)
• Amount mismatches due to currency conversion or dynamic pricing
• Missing transactions from network timeouts where your app didn’t receive the response

Match 2: Processor ↔ Bank Statement

Compare the processor’s settlement report against actual bank deposits. The net settlement amount should match the deposit minus any holdbacks or reserves.

Common discrepancies:

• Timing differences (settlement processed Friday, deposit hits Monday)
• Chargeback deductions that appear in the bank before the processor’s chargeback report
• Reserve holdbacks for new merchants or high-risk transactions

Match 3: Application ↔ Bank Statement

The end-to-end check. Your application’s expected revenue should reconcile to what actually arrived in the bank, accounting for fees, chargebacks, refunds, and reserves.

Why ISVs Can’t Ignore Reconciliation

Regulatory Requirements

If you operate as a PayFac or handle sub-merchant funds, regulators (and your sponsoring bank) require you to demonstrate accurate fund segregation and distribution. Reconciliation is how you prove it.

Merchant Trust

When a merchant’s deposit doesn’t match their expectations, they contact your support team — not the payment processor. If you can’t explain the discrepancy quickly, you lose credibility and eventually lose the merchant.

Financial Accuracy

Unreconciled transactions mean your own financial reporting is wrong. Revenue recognition, fee calculations, and tax obligations all depend on accurate transaction data.

Fraud Detection

Reconciliation surfaces anomalies — duplicate charges, unauthorized refunds, split-transaction patterns — that are early indicators of fraud. Without it, fraudulent activity compounds silently.

Reconciliation for ISV Platforms

ISVs operating embedded payments face unique reconciliation challenges:

Split Settlement

When your platform splits payments between the merchant and your take rate, reconciliation must verify both sides: the merchant received the correct amount, and your platform earned the correct fee.

Multi-Merchant Aggregation

A single settlement batch from your processor may contain transactions for hundreds of merchants. Reconciliation must disaggregate the batch, match each transaction to the correct merchant, and verify individual merchant-level accuracy.

Chargeback Attribution

When a chargeback hits your master merchant account (payment facilitator model), you need to attribute it to the correct sub-merchant and debit their balance — not absorb it at the platform level.

Cross-Currency Transactions

If your merchants accept payments in multiple currencies, reconciliation must account for exchange rates at the time of authorization vs. settlement. These rates differ, creating predictable but trackable discrepancies.

Building vs. Buying Reconciliation

Approach	Pros	Cons	Best For
Manual (spreadsheets)	No cost, immediate	Doesn’t scale past ~100 transactions/day	Pre-launch testing
Built-in (your own system)	Full control, customized to your model	Engineering investment, maintenance burden	ISVs with unique settlement models
Third-party tool	Fast to deploy, handles edge cases	Monthly cost, dependency on vendor	Most ISVs processing $1M-$100M
Payment provider’s dashboard	Included with processing	Limited customization, no app integration	ISVs just starting with integrated payments

Key Metrics to Track

• Reconciliation rate — Percentage of transactions that auto-match without manual intervention. Target: >99.5%
• Exception resolution time — How long discrepancies take to resolve. Target: <24 hours
• Unreconciled balance — Dollar value of transactions that haven’t been matched. Should trend toward zero.
• Chargeback detection latency — Time between chargeback occurrence and platform awareness. Target: same-day.