Revolut Payment Gateway Reconciliation

Finance teams that use Revolut as part of their payment flow still need to reconcile settlements, refunds, website orders, ERP exports, and bank statements. Cointab helps you compare the records you expect to be correct with the records received from Revolut and other systems, then review matched, partially matched, unmatched, and skipped transactions in one workflow.

How Revolut payment gateway reconciliation works

Cointab follows a structured Side A and Side B model:

• Side A: your internal records, such as website sales, ERP exports, order reports, ledger data, or other source-of-truth files.
• Side B: external records, such as Revolut settlement reports, refund reports, bank statements, or other partner files.

A typical workflow looks like this:

1. Upload the required files for Side A and Side B.
2. Map fields such as date, amount, and transaction identifiers.
3. Add supporting data if needed, such as order metadata, fee files, or mapping files.
4. Create derived columns when a field needs to be cleaned, combined, or calculated.
5. Run reconciliation manually or on a schedule.
6. Review the report for matched, partially matched, unmatched, and skipped items.
7. Download the Excel report for review, follow-up, or audit preparation.

This approach makes Revolut reconciliation easier to repeat for daily, weekly, monthly, or period-end finance work.

Reports commonly used in Revolut reconciliation

Different teams may reconcile Revolut against different internal and external records depending on how payments are collected and settled.

Revolut settlement reports

Settlement reports are often the main external source used to confirm what Revolut settled, when the settlement happened, and what amounts were involved.

Revolut refund reports

Refund reports help finance teams track reversed payments, cancelled orders, and refund timing differences.

Website or order reports

Website reports show the internal record of orders placed, paid, cancelled, or refunded. These are useful when comparing actual sales activity with payment gateway records.

ERP or books reports

ERP exports and ledger reports help teams reconcile gateway activity against internal accounting records.

Bank statements

Bank statements are used when the objective is to reconcile Revolut settlements or payout receipts with actual cash movement in the bank.

What finance teams usually reconcile

Revolut payment gateway reconciliation often involves more than just one-to-one transaction matching. Finance teams may need to review:

• Order or payment references
• Transaction IDs
• Settlement IDs
• Refund references
• Payment amounts and fees
• Net settlement values
• Currency or conversion differences
• Missing transactions
• Duplicate entries
• Cancelled or reversed orders
• Timing differences between sale date and settlement date

Cointab is designed to handle these patterns in a controlled, reviewable way rather than relying on fragile spreadsheet formulas.

Common differences found in Revolut reconciliation

Payment gateway reconciliation usually surfaces a predictable set of exceptions. Cointab helps you separate them clearly so the team can focus on what needs action.

Fully matched transactions

These are records where the identifier and amount match according to the configured logic.

Partially matched transactions

These are records where the identifier matches, but the amount does not fully match. This is useful when you need to investigate fees, refunds, deductions, rounding, or split settlements.

Unmatched transactions

These are records present on one side but not found on the other. Common examples include sales that did not appear in the settlement file or settlement rows that do not map back to internal records.

Skipped transactions

These are rows excluded from reconciliation because of missing data, invalid values, duplicates, or file issues. Skipped records remain visible so the team knows what was ignored and why.

How Cointab helps with Revolut payment gateway reconciliation

Cointab gives finance teams a reusable reconciliation setup instead of a one-off spreadsheet exercise.

Flexible file upload and field mapping

Upload CSV, XLS, or XLSX files and map the required fields once. If a file does not match the configured format, the system can reject it with a clear error so users know what needs to be fixed.

Supporting data for richer matching

If your Revolut reconciliation depends on additional context, you can upload supporting data such as product masters, mapping files, fee files, tax files, or order metadata. Supporting data helps enrich the primary reports before reconciliation runs.

Derived columns for finance logic

Users can create calculated fields from existing columns. For example, a team may want to clean references, normalize transaction IDs, combine identifiers, or calculate net values before matching.

Structured matching engine

Cointab supports one-to-one, one-to-many, many-to-one, many-to-many, net-to-net, partial matching, and contra matching scenarios. This is useful when Revolut data needs to be compared with grouped orders, combined payments, or settlement-level entries.

AI-assisted open-item analysis

After structured matching is complete, AI can help review open items, explain likely causes of exceptions, and support finance users when identifiers or descriptions are incomplete. If evidence is weak, the item remains unmatched for manual review.

Manual match where needed

When business context is known but automated logic is not enough, users can manually match transactions and keep the action auditable.

Audit-ready reporting

Once the run is complete, teams can download Excel reports with matched, partially matched, unmatched, and skipped rows for internal review, follow-up, or audit preparation.

Reuse the same Revolut workflow for future periods

A major advantage of Cointab is reuse. Once the Revolut reconciliation is configured, the same setup can be used again for the next period without rebuilding the workflow from scratch.

Teams can also automate recurring runs using email, SFTP, or API-based data flow. That means Revolut reports can be received, validated, reconciled, and reported with less manual effort.

If a file arrives late, users can upload the missed file into the same reconciliation and refresh the report instead of starting over.

Why this matters for finance teams

Revolut payment gateway reconciliation is rarely just about matching totals. Finance teams also need to understand exceptions, identify timing differences, explain missing items, and keep reports consistent across periods.

Cointab supports that process by giving teams:

• A structured reconciliation workflow
• Consistent matching logic
• Clear exception visibility
• Reusable setup for recurring runs
• Reviewable output for audit and close
• Less dependency on manual Excel checks

That makes it easier to keep payment, settlement, refund, and bank records aligned without losing control over the underlying logic.

FAQ

What data can be used in Revolut payment gateway reconciliation?

You can reconcile Revolut settlement reports, refund reports, website or order reports, ERP exports, and bank statements, depending on the workflow you need to review.

Can Revolut reconciliation handle partial matches?

Yes. Cointab separates fully matched and partially matched transactions so finance teams can investigate amount differences, deductions, refunds, fees, or split settlements.

Can the same reconciliation be reused every month?

Yes. Once the workflow is configured, it can be reused for future periods instead of being rebuilt each month.

Can reconciliation be automated?

Yes. Cointab supports recurring data flow and scheduled reconciliation runs using email, SFTP, or API-based automation where required.

What happens if a file is missing?

If a required file arrives later, users can upload it into the same reconciliation and refresh the report so the workflow reflects the complete data set.