Monzo Payment Gateway Fee Reconciliation
Cointab helps finance teams reconcile Monzo payment gateway fees against internal sales, settlement, and bank records using a structured, reusable workflow. Instead of checking fee calculations manually in Excel, teams can upload the required reports, map the key fields once, run reconciliation, and review matched, partially matched, unmatched, and skipped transactions in one report.
What Monzo payment gateway fee reconciliation covers
Payment gateway fee reconciliation is the process of comparing the amounts expected from internal records with the charges, taxes, and settlement values reported by the payment provider. For Monzo-related workflows, this usually means checking whether the fee charged, tax applied, and settlement received align with the business's calculation.
This type of reconciliation is useful when finance teams need to review:
- Fee charges applied to each transaction
- Tax charged on payment gateway fees
- Settlement amounts after deductions
- UTR or reference numbers linked to settlement entries
- Differences between expected and actual amounts
Cointab is designed to compare Side A and Side B data clearly:
- Side A: your internal sales, books, ERP, or payment working files
- Side B: Monzo payment reports, rate cards, settlement files, or bank records
Typical source files used in the workflow
A Monzo fee reconciliation workflow may use one or more of the following files:
- Internal sales or order report
- Payment working file
- Monzo payment report
- Monzo rate card
- Settlement report
- Bank statement
- Supporting lookup files such as order metadata, tax mapping, or fee mapping
Users can upload CSV, XLS, or XLSX files, then select the required header row, date column, amount column, and reference columns such as order ID, transaction ID, settlement ID, or UTR.
Common reconciliation scenarios
Cointab helps teams review fee and settlement differences in a structured way. Common outcomes include:
Fee correctly charged
The fee in the payment report matches the amount calculated from the rate card or internal logic.
Fee overcharged
The charged fee is higher than expected and needs review.
Fee undercharged
The charged fee is lower than expected and may indicate a reporting or calculation issue.
Tax correctly charged
The tax amount aligns with the expected calculation.
Tax overcharged
The tax amount is higher than expected and should be investigated.
Tax undercharged
The tax amount is lower than expected and may require correction.
Settlement amount match
The net amount after fee and tax deductions matches the settlement value.
Settlement amount mismatch
The settlement amount does not match the calculated amount and requires exception handling.
Settlement UTR not present
The settlement reference is missing, making it harder to tie the payment record back to the bank statement.
Settled in bank account
The settlement reference appears in the bank statement and can be marked as received.
Not settled in bank account
The settlement reference is present in Monzo data but not yet found in the bank statement.
How Cointab handles the reconciliation process
Cointab follows a practical reconciliation flow that finance teams can reuse for each period:
- Start a new reconciliation in the team workspace.
- Select a popular reconciliation or create a custom workflow.
- Upload the required files on Side A and Side B.
- Map the fields for date, amount, and identifiers.
- Add supporting files if needed for lookups or enrichment.
- Create derived columns if calculations are needed, such as net amount or cleaned reference fields.
- Run reconciliation manually or on a schedule.
- Review live processing status while the run is in progress.
- Open the reconciliation report and inspect the results.
- Download the Excel output for audit, follow-up, or internal review.
If a file was missed, users can upload it later under the same reconciliation and refresh the report.
Matching logic for fee and settlement review
Cointab's reconciliation engine applies structured matching logic to transaction data. This is useful for fee reconciliation because the same transaction may need to be checked across identifiers, amounts, and grouped totals.
The engine supports:
- One-to-one matching
- One-to-many matching
- Many-to-one matching
- Many-to-many matching
- Net-to-net matching
- Contra matching
- Partial matching
It can also work with different comparison methods, such as equal, contains, similar, and subset-based matching.
This helps teams review cases where:
- One payment maps to multiple fee lines
- Multiple fee or tax lines roll up to one settlement line
- Amounts differ because of deductions or rounding
- Reference fields are incomplete or formatted differently
- A transaction needs to be grouped before comparison
After structured matching is complete, Cointab can use AI to analyze open items that still need review. AI is conservative and audit-friendly, so weak matches are left unmatched rather than forced into a questionable result.
Reconciliation report output
Once the run is complete, finance teams can review the report dashboard and separate records into clear categories.
Fully matched
Transactions where the reference and amount align with the configured reconciliation logic.
Partially matched
Transactions where the reference matches but the amount differs. This is useful for finding fee differences, tax differences, or settlement variances.
Unmatched
Transactions present on one side but not found on the other side.
Skipped
Transactions that were excluded because of missing data, invalid values, duplicates, or other file issues.
The report also includes filters, summary totals, transaction-level detail, and a download option for audit-ready review.
Why finance teams use Cointab for payment fee reconciliation
Manual fee reconciliation in Excel can become slow and difficult to audit, especially when teams handle multiple file versions, settlement periods, and exception cases. Cointab is built to reduce that repeat work.
Key benefits include:
- Reusable reconciliation setups for future periods
- Clear handling of matched, partially matched, unmatched, and skipped records
- Faster exception review instead of checking every row manually
- Better visibility into fee, tax, and settlement differences
- Audit-friendly Excel output for internal review and follow-up
- Team workspace access so multiple users can work in one place
For recurring workflows, reconciliation can also be automated through email, SFTP, or API-based data flow. That makes it easier to keep fee reconciliation and settlement review moving without repeated manual uploads.
When manual matching is still useful
Some fee reconciliation cases still need human review. Cointab includes a manual match option for open items that the system and AI could not confidently resolve.
Manual matching is useful when:
- A reference is missing or incomplete
- A partner report is delayed or partial
- A refund or deduction explains the difference
- The totals are known to tally, but the system cannot infer the relationship safely
Manual matches remain visible in the report and can be revised later if needed.
Reuse the same setup for future runs
Once the Monzo payment gateway fee reconciliation is configured, finance teams do not need to rebuild it every month. They can reuse the same field mapping, matching logic, and supporting files for future periods.
That makes the workflow more consistent across monthly close, settlement review, audit preparation, and ongoing exception management.
What teams typically review after each run
Finance users usually review the following after reconciliation:
- Fee differences against the rate card
- Tax differences against expected calculations
- Settlement mismatches
- Missing settlement references
- Unmatched transactions that need follow-up
- Skipped rows that need file correction
- Manually matched items that require audit visibility
This gives teams a clear view of what matched, what did not match, and what needs action next.
FAQ
What is Monzo payment gateway fee reconciliation?
It is the process of comparing Monzo fee, tax, and settlement data with internal records to check whether charges and received amounts match the expected calculation.
What files are usually needed for this reconciliation?
Teams typically use internal sales or payment records, the Monzo payment report, the Monzo rate card, settlement data, and optionally the bank statement.
Can this workflow handle fee differences and partial matches?
Yes. Cointab separates fully matched, partially matched, unmatched, and skipped records so finance teams can focus on exceptions such as fee variances or settlement differences.
Can the same reconciliation setup be reused for future periods?
Yes. Once the workflow is configured, the same reconciliation can be reused for later periods without rebuilding the setup from scratch.
Can finance teams review open items manually?
Yes. Cointab supports manual matching for cases where the data is incomplete or the system cannot confidently resolve the exception.