Answer first

PSP settlement reconciliation proves whether a payment service provider settled the correct net amount for the eligible transactions in a settlement period.

Reconcile eligible transaction value to the PSP's expected net settlement before comparing anything with the bank.

Keep fee, FX, refund, reserve, and timing logic explicit and versioned.

Treat every unresolved difference as a case with calculation evidence, not merely an unmatched row.

What is PSP settlement reconciliation?

PSP settlement reconciliation compares a company's internal transaction records with the settlement report produced by its payment service provider. Its purpose is to prove which transactions were eligible, how gross value became net settlement, and whether the provider-reported result follows the agreed commercial rules.

This is the first stage of a complete payment reconciliation. It answers whether the PSP settlement is correct. A separate bank-receipt stage answers whether that settlement actually reached the bank and became available on time.

Core calculationExpected net settlement

Eligible gross transactions βˆ’ refunds βˆ’ provider fees Β± FX adjustments Β± contractual adjustments = expected PSP settlement.

The source records you need

A reliable result starts with complete, attributable source data. Internal transactions establish what the business believes occurred. The PSP report establishes what the provider accepted into a settlement cycle and how it calculated the payout.

SourceMinimum useful fieldsControl question
Internal transactionExternal ID, reference, amount, currency, status, occurred atWas this transaction eligible for settlement?
PSP settlementSettlement reference, gross, fee, net, currency, settlement dateHow did the PSP calculate the net amount?
Commercial rulesFee schedule, FX rule, reserve rule, settlement calendarWhich version applied at the time?

Match deterministically before investigating

Matching should begin with deterministic identifiers and calculations: exact references, composite keys, settlement batches, currency, amount tolerance, and expected date windows. Probabilistic or AI-assisted methods can help investigate incomplete references, but should not silently rewrite the financial result.

Batch settlements often create many-to-one relationships. A single PSP payout may contain thousands of transactions, refunds, and adjustments. The control therefore needs both record-level lineage and a batch-level proof of gross-to-net arithmetic.

  • Preserve the matching-rule version used by each run.
  • Separate exact matches, tolerance matches, composite matches, and manual overrides.
  • Run data-quality checks before matching so missing source data does not become a false settlement exception.

The exceptions that matter

An unmatched record is a symptom, not a root cause. The operational queue should classify the financial condition and preserve the amount affected, age, evidence, confidence, and owner.

ExceptionWhat it meansEvidence to inspect
Missing settlementAn eligible transaction has no PSP settlement relationshipEligibility status, cutoff, batch membership, provider status
Amount mismatchProvider-reported value differs from expected valueSource amount, refunds, adjustments, calculation
Fee mismatchCharged fee differs from the applicable fee ruleFee schedule, pricing tier, fee line items
FX differenceConversion result differs from the expected FX ruleRate source, spread, quote time, settlement currency
Settlement delayThe PSP settlement missed its expected windowSLA, calendar, actual availability time, source health

Close with evidence, not a status change

A resolution should retain the source records, rule version, calculation, investigation, recommendation, human decision, actor, and timestamp. This makes a case replayable and keeps an AI recommendation separate from the financial truth established by deterministic records and controls.

The practical operating rule is simple: rules calculate, AI investigates, and authorized people control the outcome. No evidence means no automatic resolution.

Control principleEvidence first. Recommendation second.

AI may explain the most likely cause and organize supporting records. It does not move money, alter source data, or become the financial system of record.

PSP reconciliation readiness checklist

Before automating the daily process, confirm that the team can answer the following questions consistently.

  • Which transaction statuses are settlement-eligible?
  • Which timezone, cutoff, weekend, and holiday calendar applies?
  • How are fees, FX, refunds, reserves, and adjustments represented?
  • Can every PSP batch be traced back to its internal transactions?
  • Who may override a match, approve a resolution, and sign off a run?
Prepared byTraqvera Product & Controls

This guide explains operational payment reconciliation controls. It is not legal, accounting, audit, treasury, credit, or investment advice.

Settlement Leakage Audit

Turn a reconciliation question into a measured baseline.

Start with a free 30–45 minute fit assessment. Do not send production financial data through the website or ordinary email.

Request free assessment