Mollie Payment Gateway Fee Reconciliation

Finance teams that use Mollie often need to reconcile payment collections, gateway fees, settlements, refunds, taxes, and bank receipts across multiple reports. Doing this in spreadsheets can become slow and difficult to audit, especially when transaction volumes grow or fees vary by payment method.

Cointab helps teams reconcile Mollie-side records against internal records in a structured workflow. Users can upload files, map fields once, review matches and exceptions, and download audit-ready reports for month-end close, internal review, and partner follow-up.

What gets reconciled in a Mollie workflow

A Mollie reconciliation setup usually compares internal business records on one side with Mollie and related external records on the other side.

Side A: your records

Side A typically includes the records your business expects to be correct, such as:

• Sales or order reports
• ERP or ledger exports
• Internal payment working files
• Refund or returns data
• Customer receivable or settlement working files

Side B: external Mollie-related records

Side B typically includes the records received from Mollie or from other external sources used to verify the transaction flow, such as:

• Payment reports
• Fee or rate-card data
• Settlement reports
• Refund or adjustment records
• Bank statement entries

This makes it possible to check whether payments were received, whether fees were deducted correctly, whether settlements were complete, and whether the amounts appearing in the bank match the expected totals.

Common reconciliation checks for Mollie payments

A Mollie payment gateway reconciliation workflow can help finance teams review several types of differences.

Payment amount matching

The system checks whether the payment amount in the sales or order report matches the amount recorded in Mollie-side data.

Fee validation

Teams can verify whether the gateway fee charged matches the expected fee from the configured rate card or fee rules.

Tax validation

If tax is part of the deduction or settlement breakdown, the workflow can also help review whether tax-related amounts are consistent.

Settlement matching

Settlement totals, settlement IDs, and UTR-style references can be compared against internal records and bank-side receipts.

Bank reconciliation

The final settled amount can be compared with the bank statement to identify missing receipts, timing differences, or amount mismatches.

Refunds and deductions

Refunds, reversals, and deductions can be reviewed separately so finance teams can see whether the movement is expected or needs follow-up.

How Cointab handles Mollie fee reconciliation

Cointab is designed to make Mollie reconciliation repeatable instead of rebuilding the same logic every month.

1. Upload the required files

Users upload CSV, XLS, or XLSX files for the relevant Side A and Side B reports. Multiple files can be added if they follow the same configured structure.

2. Map the key fields

Finance users map the important columns once, such as:

• Date
• Amount
• Payment reference
• Transaction ID
• Order ID
• Settlement ID
• Bank UTR

3. Add supporting data when needed

Supporting files can be uploaded to enrich the main reports before reconciliation. For example, a team may add:

• Product master data
• Fee rate files
• Order metadata
• Mapping files
• Refund or returns data

4. Create derived columns if needed

If a reconciliation needs extra logic, users can create derived columns from existing fields. AI can help generate Excel-style formulas for tasks such as:

• Cleaning transaction references
• Calculating net amounts
• Normalizing identifiers
• Deriving fee-adjusted totals

5. Run reconciliation

Cointab applies structured matching logic to compare the two sides. The workflow can support one-to-one, one-to-many, many-to-one, and grouped matching where totals need to be netted before comparison.

6. Review the report

Once the run is complete, users can review:

• Fully matched records
• Partially matched records
• Unmatched records
• Skipped records

Exception review is clearer because finance teams can focus on the open items instead of checking every transaction manually.

Why this is better than spreadsheet-based fee checks

Manual fee validation in Excel usually depends on formulas, VLOOKUPs, and repeated file comparisons. That can work for small volumes, but it becomes fragile when reports change or multiple payment methods are involved.

Cointab helps reduce that effort by giving finance teams a reusable reconciliation workflow that is easier to audit and easier to repeat.

Benefits for finance teams

• Faster review of payment fees and settlements
• More consistent matching logic across periods
• Clear separation of matched, partially matched, unmatched, and skipped items
• Better visibility into exceptions and follow-up items
• Downloadable Excel reports for internal review and audit support
• Reusable setup for recurring reconciliation runs

Reusable and automated reconciliation for recurring operations

Once a Mollie reconciliation is configured, the same setup can be reused for future periods. Teams do not need to rebuild the workflow each month.

Cointab also supports automated data input and scheduled reconciliation runs through email, SFTP, or API-based flows where relevant. That makes it easier for finance teams to keep recurring payment and settlement checks running without starting from scratch every time.

The workflow can also be refreshed if a file was missed. Users can upload the missing file under the same reconciliation and rerun the report to update the results.

How exceptions are handled

Not every record will match immediately. Cointab separates the outcomes so finance teams can investigate the right records.

Fully matched

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

Partially matched

These are records where the reference matches, but the amounts differ. This is useful when a payment is related but needs review for fees, refunds, deductions, or rounding differences.

Unmatched

These are records found on one side but not the other. They may indicate missing files, delayed settlement, incorrect references, or internal data issues.

Skipped

These are rows excluded from reconciliation because of missing fields, invalid values, duplicates, or other data issues.

Users can also manually match items that the system could not confidently match, while keeping that action visible in the report.

Mollie reconciliation use cases finance teams often review

eCommerce and D2C payments

Match internal sales orders against Mollie payment records to check whether orders were paid, underpaid, refunded, or still open.

Settlement verification

Compare settlement reports against internal working files and bank statements to confirm that the expected net amount was received.

Fee and deduction review

Check whether gateway fees, taxes, and deductions align with the expected rate card or configured fee rules.

Month-end close support

Use reconciled reports to reduce manual back-and-forth during close and to keep finance records aligned with payment activity.

Reconciliation reporting and audit readiness

After each run, Cointab keeps reconciliation results available on the dashboard for future reference. Teams can review prior runs by period, run date, or reconciliation name.

The downloadable report supports internal review by showing the records that matched, the records that did not, and the reasons transactions were skipped or left open. That makes it easier to explain differences during finance review, partner follow-up, or audit preparation.

Frequently asked questions

What reports are typically used in Mollie reconciliation?

Teams usually reconcile internal sales, order, or ledger data against Mollie payment reports, fee or rate-card information, settlement reports, and bank statements.

Can Cointab help with fee differences and settlement differences?

Yes. The workflow can help teams compare expected fees, settlement totals, and bank receipts so differences can be reviewed in one place.

Does the reconciliation setup need to be rebuilt every month?

No. Once the reconciliation is configured, the same setup can be reused for future periods with the relevant new files.

Can users review open items manually?

Yes. Users can review unmatched or partially matched transactions, apply manual matches when appropriate, and keep those actions visible in the report.

Can reconciliation runs be automated?

Yes. Cointab supports recurring workflows that can be triggered through email, SFTP, or API-based data input, depending on the configured setup.