Reconciliation of Revolut Payment Gateway Fees

Cointab helps finance teams manage Revolut payment gateway fee reconciliation with a structured workflow for comparing internal records against gateway reports, rate cards, settlement data, and bank entries. Instead of checking fees and settlements manually in Excel, teams can upload files, map fields once, run reconciliation, and review matched, partially matched, unmatched, and skipped records in one report.

What gets reconciled in Revolut payment gateway fee checks

Revolut payment gateway fee reconciliation usually involves comparing multiple finance records that need to align across the payment lifecycle.

Common reconciliation checks include:

• Transaction amount vs received amount
• Expected fee vs actual fee charged
• Tax on fees vs tax recorded in the report
• Settlement amount vs calculated settlement amount
• Settlement UTR or reference vs bank statement entry
• Internal sales or order record vs payment gateway record

A typical setup uses:

This side-based model keeps the reconciliation process clear for finance teams and makes it easier to understand what matched and what still needs review.

How the reconciliation workflow works

Cointab uses a reusable workflow that finance teams can configure once and run again for future periods.

1. Upload the required Side A and Side B files.
2. Map the key fields such as date, amount, and transaction reference.
3. Add supporting data if needed, such as a rate card, master file, or lookup table.
4. Create derived columns where calculations or cleanup are needed.
5. Run reconciliation manually or on a schedule.
6. Review the result set with clear matched, partially matched, unmatched, and skipped buckets.
7. Download the Excel reconciliation report for review, audit, or follow-up.

The workflow is designed to reduce repeat work. Once the setup is in place, finance teams do not need to rebuild the same fee reconciliation logic every month.

Fee, tax, and settlement analysis

For Revolut payment gateway reconciliation, the most important checks often go beyond a simple amount match.

Fee verification

Cointab can help compare the fee charged in the gateway report against the expected fee calculated from the rate card or agreed pricing structure.

This helps teams identify:

• Fees correctly charged
• Fees overcharged
• Fees undercharged
• Rows where fee data is missing or incomplete

Tax verification

If tax appears in the payment gateway report or supporting documents, it can be checked against the expected calculation or reference data used by the finance team.

Settlement verification

Settlement reconciliation can compare the gross transaction amount, fee, tax, and net settlement amount to identify differences before they flow into books or the bank.

Example checks may include:

• Settlement reference present in the report
• Calculated settlement amount matches the reported amount
• Settlement amount appears in the bank statement
• Settlement is missing in the bank statement
• Amount differences that need follow-up

Handling matched, partially matched, unmatched, and skipped records

Cointab separates reconciliation output into clear operational buckets so finance teams can focus on exceptions.

Fully matched

Fully matched records are those where the identifiers and values align according to the configured logic.

Partially matched

Partially matched records are linked transactions where identifiers may match, but the amounts differ. This is useful when the payment exists but fees, taxes, refunds, or deductions change the final value.

Unmatched

Unmatched records are present on one side but not found on the other. These are the items that often require follow-up with the payments team, operations team, bank, or partner.

Skipped

Skipped records are rows that were excluded because of file issues, missing fields, invalid values, or other rule-based reasons. Keeping skipped items visible helps teams understand why certain rows were not processed.

Supporting data and derived columns

Revolut fee reconciliation often depends on more than the two primary reports. Cointab supports supporting data to help finance teams prepare the records before matching.

Examples of supporting data include:

• Rate card or fee schedule
• Product or order master data
• Tax mapping file
• Settlement lookup file
• Bank reference file
• Internal mapping file for transaction references

Users can also create derived columns when the source data needs cleanup or calculation.

Examples include:

• Clean transaction reference
• Net settlement amount
• Expected fee amount
• Tax-inclusive amount
• Normalized payment identifier
• Amount after deduction

Derived columns can be created with AI-assisted formula support, which helps finance users express business logic without building formulas from scratch.

AI-assisted review for open items

After structured matching is complete, Cointab can help analyze open transactions where rules alone are not enough.

AI support can help finance teams:

• Review similar but not exact references
• Understand why a transaction may be open
• Identify whether a file may be missing
• Spot fee, refund, deduction, or timing differences
• Suggest the next action for an unresolved item

If the evidence is weak, the item stays unmatched. That keeps the reconciliation process audit-friendly and reviewable.

Manual match and missed file refresh

Finance teams often discover late files or one-off exceptions during period close. Cointab supports manual matching for cases where the business context is known but the system cannot confidently match the records.

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 useful when a Revolut report, settlement file, or bank file arrives late.

Reconciliation reports for finance and audit teams

Once the run is complete, Cointab presents a reconciliation dashboard with transaction-level detail and summary views.

The report typically includes:

• Total summary
• Fully matched summary
• Partially matched summary
• Unmatched summary
• Skipped summary
• Filters for deeper analysis
• Detailed transaction tables
• Downloadable Excel report

This makes it easier for controllers, finance managers, and audit teams to review fee differences and follow up on exceptions without recreating the analysis in spreadsheets.

Reuse and automation for recurring runs

Revolut payment gateway fee reconciliation is often a recurring finance process. Cointab is designed so the same setup can be reused every period instead of starting over.

Teams can run the same workflow for:

• Monthly reconciliation
• Quarterly review
• Year-end close
• Custom settlement periods
• Ongoing fee verification

For recurring operations, data can also be automated through email, SFTP, or API-based workflows. This helps finance teams reduce manual uploads and keep reconciliation runs on a regular schedule.

Why finance teams use a structured reconciliation engine

A structured reconciliation workflow helps teams move away from ad hoc spreadsheet checks and toward a repeatable process.

That is especially useful when the team needs to:

• Compare payment gateway reports with internal books
• Track fee and settlement differences clearly
• Keep matched and unmatched items visible
• Reuse the same setup across periods
• Maintain audit-ready reports for review and follow-up

For Revolut payment gateway fee reconciliation, that means fewer manual checks, clearer exception handling, and a more consistent process for finance operations.