Key takeaways
- PSP reconciliation confirms that every transaction recorded in a business's ledger was processed by its payment service provider, at the same amount and status.
- It works at transaction level, while settlement reconciliation works at payout level.
- Businesses using several processors face different file formats, references and cut-off times for each.
- Status mismatches, such as a payment the ledger shows as complete but the processor shows as failed, are the most damaging breaks because they create balances that do not exist.
What PSP reconciliation is
A payment service provider, or PSP, is the company that processes payments on a business's behalf, such as a card processor, a wallet provider or a bank transfer provider. Each PSP keeps its own record of every transaction it handled. PSP reconciliation matches that record, line by line, with the business's own ledger.
Where settlement reconciliation checks that the right total arrived in the bank, PSP reconciliation checks that the right transactions sit behind that total. Both are needed. A settlement can agree in total while containing one payment recorded twice and another missing.
The multi-PSP problem
Most payment businesses of any size use more than one PSP, for cost, coverage or resilience. Each PSP reports differently. Transaction references follow different formats. Time stamps are recorded in different time zones. Fees appear per transaction in one report and as a daily total in another. Currency conversion happens at different points.
The result is that a matching rule written for one PSP rarely works for the next. Teams that reconcile in spreadsheets often end up maintaining a different workbook for each processor, and the reconciliation slows down every time a new processor is added.
The breaks that matter most
Not every difference carries the same risk. The table ranks the common PSP breaks by the damage they do if left open.
| Break | What it means | Risk if left open |
|---|---|---|
| Status mismatch | Ledger shows complete, PSP shows failed or reversed | High: customer balance credited with money never received |
| Missing in ledger | PSP processed a transaction the ledger never recorded | High: customer money held but not owed to anyone on the books |
| Missing at PSP | Ledger recorded a transaction the PSP never processed | High: balance created without funds |
| Amount difference | Same transaction, different amount | Medium: often fees or currency conversion |
| Timing difference | Same transaction, recorded on different days | Low if it clears the next day |
Worked example
A wallet provider reconciles 48,210 transactions from its main card processor for one day. 48,196 match on reference, amount and status. Of the 14 that do not, 9 are timing differences that appear in the next day's file, 3 are refunds the ledger recorded at the original rather than the converted amount, and 2 are payments the ledger shows as successful but the processor shows as declined.
The 2 declined payments are the urgent items. Two customers have been credited with $1,140.00 that never arrived. The provider reverses the credits, investigates why its system accepted a success message before the processor's final status, and fixes the rule. A match rate of 99.97% looked healthy, but the two breaks that mattered were in the remaining 0.03%.
How to do it well
Normalise every PSP's report into one common structure before matching, so one set of rules covers all processors. Match on the PSP's own transaction reference wherever possible. Treat status mismatches as the highest priority, ahead of amount differences. Keep a record of every break, its cause and its resolution. For regulated firms, link the result to the daily customer-money position, because a PSP break often changes what is owed to customers.
Safeheld normalises processor files into a single structure, matches across processors, ledgers and banks, and ranks breaks by risk. See three-way reconciliation and Safeheld reconciliation.
Frequently asked questions
What is PSP reconciliation?
Matching a payment service provider's transaction records with a business's own ledger, transaction by transaction.
How is PSP reconciliation different from settlement reconciliation?
PSP reconciliation works at transaction level; settlement reconciliation checks the net payout received in the bank.
Which PSP breaks are most serious?
Status mismatches and transactions missing from one side, because they create customer balances with no matching funds.
How do you reconcile several PSPs at once?
Convert every PSP's report into one common structure first, then apply one set of matching rules.
References
- FCA Handbook, CASS 15.8 Records, accounts and reconciliations
- Massachusetts General Laws c.169B §9: permissible investments
- Bank of Canada, Retail payment supervision
About Safeheld
Safeheld reconciles client money every day, resolves every difference and prepares every regulatory return for sign-off, for regulated firms in the United States, the United Kingdom, the European Union, Canada, Australia, Singapore and Hong Kong. To discuss your operations, contact us at safeheld.com/contact.
This article is for general information and does not constitute legal or regulatory advice.