Opayo Payment Gateway Fee Reconciliation Software
Cointab helps UK finance teams reconcile Opayo payment gateway fees by comparing payment data, rate cards, settlement reports, bank statements, and internal records in one structured workflow. Instead of checking spreadsheet formulas and row-level differences manually, teams can map fields once, run reconciliation, and review matched, partially matched, unmatched, and skipped records in an audit-ready report.
Why Opayo fee reconciliation becomes difficult in spreadsheets
Opayo-related reconciliation often involves more than just matching transactions. Finance teams may need to verify:
- Payment amounts processed through Opayo
- Gateway fees charged against the expected rate card
- Tax or other charge components where applicable
- Net settlement amounts after deductions
- References that must tie back to a bank statement or ledger entry
- Refunds, reversals, or missing settlements that create open items
When these records arrive in separate files, spreadsheet-based checks can become repetitive and hard to audit. A single reconciliation may need multiple reports, several matching rules, and careful review of exceptions.
Common records used in an Opayo reconciliation
| Record type | Typical role in the workflow |
|---|---|
| Internal sales or order report | Side A source of truth for expected transactions |
| Opayo payment report | Side B record for processed payments and payment references |
| Opayo rate card | Supporting data for expected fee calculation |
| Settlement report | Side B record for net settlement values and references |
| Bank statement | Final record for confirming the money received |
| ERP or books export | Internal accounting view for tie-back to the ledger |
Supporting files such as refund reports, mapping files, or fee reference sheets can also be added when they help enrich or prepare the primary data before reconciliation.
How Cointab structures the reconciliation workflow
Cointab uses a Side A and Side B model so finance teams can clearly define what they expect to receive and what they actually receive.
Side A: your records
Side A usually contains the business records that should be correct, such as:
- Sales report
- Books export
- ERP data
- Internal order report
- Ledger or settlement working file
Side B: external records
Side B usually contains records received from Opayo or related external systems, such as:
- Payment report
- Settlement report
- Bank statement
- Fee or rate card file
- Refund or reversal report
Typical workflow
- Upload CSV, XLS, or XLSX files.
- Select header rows and map required fields such as date, amount, and identifiers.
- Add supporting data where needed for lookups, merging, or enrichment.
- Create derived columns using AI-generated Excel-style formulas when values need to be cleaned or calculated.
- Run reconciliation manually or on a schedule.
- Review live progress while the reconciliation runs.
- Open the completed report and inspect matched, partially matched, unmatched, and skipped records.
- Download the Excel report or deliver output through email, SFTP, or API where automation is configured.
What the reconciliation engine checks
Cointab applies structured matching logic to compare records across both sides. For an Opayo fee reconciliation, that can help teams identify:
- Fee correctly charged, where the fee matches the expected value
- Fee overcharged, where the actual fee is higher than expected
- Fee undercharged, where the actual fee is lower than expected
- Settlement amount match, where the net settlement aligns with the calculation
- Settlement amount mismatch, where the settled amount differs from the expected amount
- Settlement UTR present or missing in the bank statement
- Open items that need review because identifiers or values do not align cleanly
The platform separates results clearly so finance teams can focus on exceptions rather than scanning every line item manually.
How exceptions are handled
Not every item should be forced into a match. Cointab keeps the reconciliation audit-friendly by showing what was matched and what still needs attention.
Fully matched
Transactions where the expected identifiers and amounts align with the reconciliation logic.
Partially matched
Transactions where identifiers may match but the amounts do not. This is useful for catching small fee differences, settlement shortfalls, or amount mismatches that still need review.
Unmatched
Transactions present on one side but not found on the other. In an Opayo workflow, this might indicate a missing settlement, an unrecorded fee, or an item that needs follow-up.
Skipped
Records that were not included in reconciliation because they were incomplete, invalid, duplicated, or excluded by rule. Skipped items remain visible so the team understands what was ignored and why.
Why finance teams use Cointab for recurring reconciliation
Opayo fee reconciliation is usually not a one-time task. It is part of monthly close, settlement review, and cash control.
Cointab supports recurring work by allowing teams to:
- Reuse the same reconciliation setup for future periods
- Use manual match when business context is known but rules are not enough
- Refresh the report if a file was missed and later received
- Collaborate in a shared team workspace with roles and access control
- Keep a history of runs and report outputs on the dashboard
- Export audit-ready Excel reports for internal review or follow-up
This makes the workflow easier to repeat across periods without rebuilding the same spreadsheet logic each time.
Where automation helps most
Once an Opayo reconciliation has been configured, Cointab can automate recurring input and output flows. That is useful when teams receive reports daily, weekly, or monthly and want reconciliation to run without repeated manual uploads.
Automation can support:
- File receipt through email or SFTP
- Scheduled reconciliation runs
- Output delivery back to internal systems through email, SFTP, or API
- Ongoing visibility into when a run happened and which files were used
For finance teams, this turns reconciliation from a manual spreadsheet task into a repeatable operational workflow.
AI support for finance teams
Cointab also uses AI in a conservative, reviewable way.
For Opayo fee reconciliation, AI can help with:
- Creating derived columns from plain-language instructions
- Analyzing open transactions where references are inconsistent
- Suggesting possible reasons for unresolved differences
- Highlighting whether a missing file, fee variance, or settlement delay may explain the open item
AI is used to support finance review, not replace it. If there is not enough evidence, the transaction should remain unmatched.
A practical fit for payment gateway fee review
Opayo fee reconciliation is most useful when finance teams need a clear view of how payment activity translates into fees, settlements, and bank movements. Cointab brings those records into one workflow so teams can map once, reconcile repeatedly, and review the exceptions that matter most.
Frequently asked questions
What data can be used for Opayo payment gateway fee reconciliation?
Finance teams typically use an internal sales or order report on Side A and Opayo payment, settlement, rate card, and bank files on Side B. Supporting files can be added when they help with enrichment or lookups.
Can Cointab handle fee, settlement, and bank differences in the same workflow?
Yes. Cointab can compare related payment, settlement, and bank records in one reconciliation setup so teams can review fee differences, settlement mismatches, and missing references together.
Can the same Opayo reconciliation be reused for future periods?
Yes. Once configured, the reconciliation can be reused for future periods so teams do not need to rebuild the setup every month.
What happens if a file was missed during reconciliation?
The missed file can be uploaded under the same reconciliation and the report can be refreshed so the new data is included in the updated run.
Can users manually match items that were not resolved automatically?
Yes. If the system and AI do not confidently match a transaction, users can manually match items when the business context supports it, and the manual action remains visible in the report.