In this article
Key takeaways
- Keep the new file and a previously checked report.
- Separate a layout change from a new financial event.
- Matching the bank does not explain an unfamiliar deduction.
- Reuse a changed template only after its interpretation is checked.
A new €37.50 row changes the payout
In this fictional report, the known rows explain €7,412.50. A new row reduces the payout to €7,375.
| Component | Amount |
|---|---|
| Activity | €9,000 |
| Fees | −€1,100 |
| Refunds | −€250 |
| Chargebacks | −€180 |
| Reserve held | −€57.50 |
| Total of known rows | €7,412.50 |
| New “balance correction” | −€37.50 |
| Reported payout and bank receipt | €7,375 |
The calculation works. The explanation is incomplete. The €37.50 could concern an earlier balance, a corrected fee or another event. Those possibilities are not interchangeable.
Keep the new row with its original label and request the supporting statement. Do not put it into fees simply to finish the payout.
Compare meaning, not only column names
| Previously checked field | New field | What to establish |
|---|---|---|
| service_fee | service_fees | Does it still include the same charges? |
| reserve_hold, negative | retained_balance, positive | Is this a new hold or the closing balance? |
| No equivalent | balance correction | Which event explains the €37.50? |
| payout_total | net_transfer | Does it agree with the identified bank receipt? |
These field names are invented, not a documented change by a named provider. The reserve row illustrates the main risk: a closing balance must not be deducted again as if it were a new hold.
Check the changed report in five steps
- Preserve the original. Keep the downloaded file unchanged, together with account, payout ID, currency and download date.
- Compare one reliable earlier file. Identify added rows, changed signs, subtotals and date ranges. Check for duplicate transactions too.
- Recalculate what is understood. Show which rows still explain the payout and the exact amount that remains unclear.
- Get the missing explanation. Ask for the provider notice, detailed transaction or reserve statement. The owner can supply business facts; the accountant reviews the treatment.
- Test before reuse. Check the revised interpretation against representative files and their bank receipts. Keep the earlier version and the date from which the new one applies.
A format update should not silently reinterpret older months. If the previous interpretation affected accepted books, the firm decides the correction separately.
What Hans prepares for the reviewer
For a supported report, Hans can retain the source, identify the mismatch and separate known components from the unexplained part. The useful output is a specific case: “What does this €37.50 correction refer to?” with the relevant row and payout attached.
Once the meaning and template are validated through the supported process, later matching files can reuse that work. Coverage still depends on the provider and format; a changed file is a reason to check, not a promise of universal compatibility.
For a complete payout example, use the P-204 evidence pack. For reserve movements, read fees, refunds and retained balances.
Sources
Sources were checked on 21 July 2026. This article provides orientation and is not tax, legal, or accounting advice.
- German Commercial Code section 238 – bookkeeping duty
- German Fiscal Code section 146 – bookkeeping requirements
- Published