Braintree Payment Gateway Fee Reconciliation

Overview

Braintree payment gateway fee reconciliation helps finance teams verify that transaction fees, taxes, and settlement amounts are being charged and settled correctly. For businesses processing a high volume of online payments, even small fee or tax differences can add up quickly and make month-end review more difficult.

Cointab provides a structured reconciliation workflow for comparing your internal payment records with Braintree payment reports, rate cards, settlement data, and bank statements. Finance teams can review matched, partially matched, unmatched, and skipped records in one place, then download an audit-ready Excel report for review and follow-up.

Why Braintree fee reconciliation matters

Payment gateway reconciliation is not only about confirming that a payment was received. Finance teams also need to check:

• Whether the fee charged matches the expected rate card
• Whether tax has been calculated correctly
• Whether settlement amounts net off as expected
• Whether the settlement reference appears in the bank statement
• Whether any deductions, refunds, reversals, or timing differences explain an exception

When this is done manually in spreadsheets, the process can become repetitive and hard to audit. Reconciliation rules may differ from person to person, and large files can be difficult to review consistently.

How Cointab supports this use case

Cointab uses a Side A and Side B reconciliation model:

• Side A contains your internal records, such as sales data, payment working files, or finance books.
• Side B contains external records, such as Braintree payment reports, settlement reports, or bank statements.

Users upload the required files, map key fields such as date, amount, and reference identifiers, and run reconciliation. The platform then applies structured matching logic to compare records and separate clean matches from exceptions.

For Braintree fee reconciliation, this typically means comparing:

• Payment records against the expected fee rate card
• Settlement reports against internal payment totals
• Settlement references against bank statement entries
• Fee and tax values against calculated amounts

Typical reports used in the reconciliation

A Braintree fee reconciliation workflow may use one or more of the following inputs:

1. Braintree payment report

This report contains transaction-level payment activity and can be used to validate the amount processed, fee charged, and related payment details.

2. Braintree rate card or fee schedule

The rate card helps determine the expected fee based on payment mode, transaction type, or other configured conditions.

3. Settlement report

The settlement report is used to verify the amount that should be paid out after fees, taxes, and deductions. It can also help identify whether a settlement reference is available.

4. Bank statement

If settlement references are present in the settlement report, they can be checked against the bank statement to confirm that the funds were actually received.

Common reconciliation outcomes

Cointab separates results clearly so finance teams can focus on exceptions rather than reviewing every row manually.

Fee correctly charged

The fee charged in the payment report matches the amount calculated from the rate card.

Fee overcharged

The charged fee is higher than the expected fee. This may indicate a pricing issue, rate mismatch, or a configuration problem that needs review.

Fee undercharged

The charged fee is lower than expected. Finance teams may want to check whether the transaction was processed under a different rate or whether a data issue exists.

Tax correctly charged

The tax value matches the expected calculation based on the available fee or settlement details.

Tax overcharged or undercharged

The tax value differs from the expected calculation and should be reviewed alongside the transaction and settlement records.

Settlement UTR not present

The settlement report may not contain a UTR or similar bank reference for a transaction. This makes bank-level follow-up harder and may indicate a missing or incomplete settlement record.

Settlement amount match

After fees and taxes are deducted, the final settlement amount matches the expected calculation.

Settlement amount mismatch

The final settlement amount does not match the expected calculation. This may be caused by fees, taxes, adjustments, refunds, deductions, or file issues.

Settled in bank account

The settlement reference appears in the bank statement, confirming that the payout has been received.

Not settled in bank account

The settlement reference appears in the settlement report but not in the bank statement, which may point to a pending, delayed, or missing bank entry.

Reconciliation workflow in Cointab

A typical workflow for this use case looks like this:

1. Upload the relevant Braintree and internal finance files.
2. Map fields such as transaction date, amount, payment reference, and settlement reference.
3. Add optional supporting data if needed, such as a fee schedule or lookup file.
4. Create derived columns if a value needs to be normalized or calculated.
5. Run reconciliation manually or schedule it for recurring periods.
6. Review fully matched, partially matched, unmatched, and skipped records.
7. Use filters to inspect fee differences, settlement mismatches, or missing bank entries.
8. Download the Excel reconciliation report for audit and review.

Where supporting data can help

Supporting data is optional, but it is useful when the payment or settlement file needs to be enriched before reconciliation. For example:

• A fee rate file can help calculate the expected charge
• A mapping file can normalize partner-specific references
• A bank reference file can help connect settlement records to the bank statement
• A returns or refund report can explain differences in net settlement value

When derived columns are useful

Cointab also supports derived columns, which can be created from existing fields and recalculated every time the reconciliation runs.

For this use case, derived columns may help with:

• Cleaning transaction references
• Calculating expected fees
• Deriving settlement net amounts
• Normalizing payment mode labels
• Converting sign conventions for refunds or reversals

Users can create these using AI-assisted formula generation or by defining the formula directly.

How exceptions are handled

Not every record should be forced into a match. Cointab first applies structured reconciliation logic and then uses AI to help analyze remaining open items where rules are not enough.

This is useful for cases such as:

• Slightly different transaction descriptions
• Partial or missing references
• Complex fee or settlement adjustments
• Missing bank entries
• Refunds or reversals that explain a mismatch

If evidence is weak, the item remains unmatched so the finance team can review it manually.

Manual review and audit readiness

Finance teams often need to investigate a small number of open items after the automated run. Cointab supports manual matching for cases where the business context is clear but the system cannot confidently match the records.

The final output is designed to be reviewable and audit-friendly, with clear separation of:

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

This makes it easier to explain fee differences, track open items, and support internal review.

Reuse for recurring payment reconciliations

Once the Braintree reconciliation is configured, the same setup can be reused for future periods. Finance teams do not need to rebuild the workflow every month.

That makes it suitable for recurring reconciliation work such as:

• Daily payment reviews
• Weekly settlement checks
• Month-end close support
• Periodic bank settlement verification
• Ongoing fee and tax validation

Team-based finance operations

Cointab supports shared team workspaces, so finance, accounting, and reconciliation teams can work from one common setup instead of passing spreadsheets around. This helps keep reconciliation history, file inputs, and review activity organized in one place.

Summary

Braintree payment gateway fee reconciliation is about more than checking whether a payment went through. It also involves validating the fee charged, confirming tax treatment, matching settlement values, and checking whether payouts appear in the bank statement.

Cointab gives finance teams a structured way to manage this process with reusable workflows, clear exception handling, audit-ready reporting, and optional automation for recurring reconciliation runs.