Payout does not match: Check fees, refunds, and chargebacks

The symptom: expected payout and bank receipt differ

You may see one of four common symptoms:

1. the payout report’s stated net amount differs from the bank receipt;
2. the report totals internally, but the prepared component total does not;
3. the bank receipt matches, but an unfamiliar component has been classified as an ordinary fee;
4. the provider changed column names, row labels, signs, or grouping, so last month’s interpretation no longer fits.

Each symptom points to a different check. A bank timing difference is not the same as a new chargeback row, and a reserve release is not the same as a current fee.

Evidence to collect before changing anything

• the original payout file in its exported format;
• the payout ID, period, currency, and provider account;
• the corresponding bank movement;
• the sales or transaction report behind the payout;
• separate invoices or notices for provider fees where available;
• refund, dispute, or chargeback evidence;
• the previous payout when a balance or reserve is carried forward;
• the owner’s factual explanation of any exceptional event.

Do not overwrite the original file or edit its rows to resemble last month. Preserve both the source and the interpretation so a reviewer can see what changed.

Worked example: one new row creates a €20 difference

The following “Harbour Studio” example is synthetic. Its payout report P-311 contains:

Last month’s controlled template knew all rows except “network adjustment.” If that row were ignored, the prepared result would be €9,750, while the bank and report both show €9,730.

The €20 is not automatically an expense merely because it closes the difference. The workflow needs three answers:

1. Does the provider documentation or separate notice explain the row?
2. Is it a current provider charge, a correction of an earlier settlement, or a balance movement?
3. Which source and period should remain connected to the prepared component?

Until those questions are resolved, the report can be mathematically reconciled but not professionally approved.

Diagnose the main component types

Fees

Fees normally explain part of the gap between gross activity and net settlement. Keep different provider charges separate when the source does. Gather the provider invoice or equivalent evidence and check the legal supplier, period, currency, and any stated tax information.

Do not infer professional treatment from the label “fee.” A platform’s wording does not decide the accounting or VAT result.

Refunds

A refund is usually connected to an earlier sale or customer charge. Identify the original transaction, whether the refund is full or partial, and whether the sales evidence was already corrected. Otherwise the same economic reduction can appear once in sales evidence and again in the payout.

Chargebacks

A chargeback starts with a reversed or disputed payment, but its final meaning can change. It may later be won, lost, corrected, or accompanied by a separate dispute fee. Keep the original sale, reversal, later outcome, and any provider charge connected rather than treating “chargeback” as a permanent account category.

Reserves and carried balances

A reserve withheld today changes the platform balance and reduces today’s cash. A reserve released today may settle an amount already carried from an earlier period. Neither movement should automatically create a new sale or cost merely because it appears in the current report.

How DeinHans handles the exception

For a known format, DeinHans can recognise the expected source structure, separate the established component types, check their sum against the stated payout, and connect the net result to the bank. If an expected column disappears or an unknown row appears, the safe behaviour is to keep the difference visible and request validation.

A controlled update should therefore produce:

• the unchanged original payout file;
• the recognised components from the existing template;
• one explicit unresolved “network adjustment” component;
• the report calculation showing the €20 difference;
• the evidence or owner answer used to resolve that row;
• the revised prepared result and the €9,730 bank match;
• a visible record that the format interpretation changed.

This workflow does not guarantee that every provider or every new layout is immediately supported. DeinHans must not silently treat an unknown column as a known fee, expose proprietary implementation rules, or turn a template match into professional approval.

Responsibility split

Release checklist for the payout

• Original report, sales evidence, and bank movement are present.
• The report period, currency, and payout ID agree.
• Every row has a known meaning or a visible question.
• Refunds and chargebacks link to the relevant earlier activity where available.
• Reserves and carried balances are not duplicated as current income or expense.
• Components add exactly to the reported net payout.
• The reported payout matches the correct bank movement or has an explained timing difference.
• The accountant can distinguish source facts, software preparation, owner answers, and professional decisions.

When those checks pass, the payout has not merely been made to balance. It has been reconstructed in a way another person can understand and review.