Revolut Payment Gateway Reconciliation with Cointab

Revolut payment gateway reconciliation helps finance teams match payment activity across internal records and external reports, so settlements, refunds, fees, and bank entries are accounted for correctly. Cointab supports this workflow with a structured reconciliation engine that compares Side A and Side B data, highlights discrepancies, and produces audit-ready reports.

Why Revolut payment gateway reconciliation matters

Payment gateway data rarely sits in one place. A finance team may need to compare:

• website or order reports
• internal ERP or sales exports
• Revolut settlement reports
• Revolut refund reports
• bank statements

When these records do not align, teams may see missing payments, settlement differences, cancelled orders, partial receipts, or transactions that appear in one system but not another. Reconciliation makes those differences visible and easier to review.

For finance operations, the goal is not just to find matches. It is to understand what was matched, what remains open, and what action is needed before month-end close or audit review.

Side A and Side B in a Revolut reconciliation workflow

Cointab uses a simple Side A / Side B model.

Side A: your internal records

Side A usually contains the records your business expects to be correct, such as:

• website order data
• sales reports
• ERP exports
• internal receivable or ledger data
• accounting working files

Side B: external Revolut records

Side B contains the records received from Revolut or other external sources, such as:

• settlement reports
• refund reports
• bank statements
• payout or receipt data

This structure helps finance teams clearly define what they are comparing and which fields matter for the match.

Common Revolut reconciliation scenarios

Revolut payment gateway reconciliation is often used to compare payment activity against business records in several ways.

Website vs Revolut settlement reconciliation

This workflow checks whether orders recorded on the website appear in Revolut settlement data. It helps identify:

• payments that were received but not reflected correctly on the website report
• order values that differ between the website and settlement
• cancelled transactions that should not be treated as collected revenue

ERP vs Revolut reconciliation

This workflow compares internal ERP or accounting data with Revolut reports. It is useful for identifying:

• transactions missing from the ERP export
• settlement differences caused by timing, fees, or refunds
• records that need posting or correction in books

Bank vs Revolut reconciliation

This workflow compares bank statements with Revolut-related payment activity. It helps finance teams review:

• receipts that appear in bank data but not in internal records
• settlements that have not yet landed in the bank
• timing differences between payment activity and bank postings

Refund and cancellation review

Refunds and cancellations can create confusion if they are not tracked consistently. Cointab helps teams separate these items from fully settled transactions so the report remains easy to review.

How Cointab handles Revolut reconciliation

Cointab gives finance teams a reusable workflow for recurring reconciliation runs.

1. Upload the required Side A and Side B files.
2. Map fields such as date, amount, and transaction identifiers.
3. Optionally add supporting data for lookups, merging, or enrichment.
4. Create derived columns if a clean reference or calculated value is needed.
5. Run reconciliation manually or on a schedule.
6. Review matched, partially matched, unmatched, and skipped transactions.
7. Download the Excel reconciliation report.

If the workflow is reused later, the same configuration can be applied again without rebuilding the setup from scratch.

Field mapping and supporting data

Revolut reconciliation often depends on clean identifiers. Cointab lets users map common fields such as:

• transaction date
• amount
• payment reference
• order ID
• invoice number
• settlement ID
• bank UTR

Supporting data can also be added when a finance team needs to enrich or prepare the primary reports before reconciliation. Typical examples include product masters, mapping files, order metadata, or tax-related lookup data.

This is useful when the business needs VLOOKUP-style enrichment without maintaining fragile spreadsheet logic.

Derived columns for cleaner matching

Some Revolut workflows need calculated or normalized columns before matching starts. Cointab supports derived columns on both sides of the reconciliation.

Examples include:

• clean transaction reference
• normalized order ID
• net amount after fees
• refund amount as a negative value
• combined reference field
• delivered payment amount

Users can also create derived columns with AI assistance by describing the logic in plain language. The system then helps generate an Excel-style formula that can be reused in the workflow.

Structured matching and exception handling

Cointab does not rely on a single match type. The reconciliation engine supports structured comparisons across multiple transaction patterns, including:

• one-to-one matching
• one-to-many matching
• many-to-one matching
• many-to-many matching
• net-to-net matching
• contra matching
• partial matching

This matters for payment gateway data because real finance records are often not perfectly symmetrical. One order may map to more than one record, or multiple transactions may need to be grouped before the totals match.

After deterministic rules run, remaining open items can be analyzed with AI support. If there is not enough evidence for a confident match, the transaction remains open rather than being forced into a weak match.

What the reconciliation report shows

Once the run is complete, Cointab presents a report dashboard with clear transaction status categories.

Fully matched

These are records where the identifiers and amounts align according to the configured reconciliation logic.

Partially matched

These are records where the identifiers match, but the amounts differ. This is often the most useful exception group for payment teams because it points to a related transaction that needs review.

Unmatched

These are records found on one side but not the other. They often indicate missing uploads, timing differences, or unresolved business exceptions.

Skipped

These are rows that were excluded from reconciliation because they were incomplete, invalid, duplicated, or otherwise unusable.

The report also supports filters, transaction-level drill-down, and Excel export for review, audit, and partner follow-up.

Manual match and missed file handling

Some cases cannot be matched automatically. Cointab includes a manual match option so users can pair transactions when the business context is known and the totals tally.

If a file was missed during the first run, it can be uploaded under the same reconciliation and the report can be refreshed. This is especially helpful when Revolut-related reports arrive later than expected or when a supporting file is added after initial review.

Reusable workflows and automation

A major advantage of Cointab is reuse. Once a Revolut reconciliation setup is created, finance teams can run it again for future periods without rebuilding the workflow.

Cointab also supports recurring automation through:

• email
• SFTP
• API integrations

That means a team can set up the reconciliation once, schedule the run, and let the platform handle recurring data receipt, validation, matching, and report generation. Output can also be delivered back to downstream systems through email, SFTP, or API.

Team-friendly finance operations

Cointab is designed for shared finance workspaces. That makes it easier for controllers, reconciliation analysts, accounts teams, and finance managers to work from the same reconciliation history instead of exchanging spreadsheets manually.

Shared workspaces also help with visibility into who ran a reconciliation, which files were used, and how exceptions were handled.

FAQ

What can be reconciled in a Revolut payment gateway workflow?

A Revolut workflow can reconcile website orders, ERP exports, settlement reports, refund data, and bank statements. The exact setup depends on which records your team wants to compare.

Can Cointab handle refunds, cancellations, and fee differences?

Yes. These are common exception scenarios in payment reconciliation. Cointab helps separate matched transactions from partial matches, unmatched items, and skipped rows so finance teams can review the differences clearly.

Do I need to build the workflow from scratch every month?

No. Once a reconciliation is configured, it can be reused for future periods. Teams can run the same setup again with new files or automate the data flow for recurring runs.

Can I use custom fields or calculated columns?

Yes. Cointab supports field mapping, supporting data, and derived columns so teams can prepare payment records before reconciliation starts.

How does Cointab help with open items?

Cointab first applies structured matching rules. If items remain open, AI can help analyze why they may be unmatched and suggest possible reasons or next steps. If the evidence is weak, the transaction stays unmatched for review.