Refund and Adjustment Reconciliation - When Shortfalls Stay as Amount Differences
Explain why many payout shortfalls stay in amount-difference review until the exports prove the exact cause.
Try with sample files | View sample report
Problem statement
Many reconciliation mismatches are described as fees too early. In reality, exported files may only prove that there is an amount difference caused by some mix of refund, fee, reserve, tax, FX, or payout adjustment behavior.
Numeric example
| Line item | Amount |
|---|
| Expected source total | $1,240.00 |
| Bank or payout amount | $1,182.50 |
| Open amount difference | -$57.50 |
| Exact cause proven | Not yet |
Why the numbers do not match
- One shortfall can have several plausible causes inside the same payout or bank movement.
- Some exports label exact fee rows clearly, while others only show a net reduction.
- Refunds and adjustments can land in a different period than the original sale.
- Mixed-currency or reserve effects can look like generic deductions until another export is reviewed.
- Claim-safe wording matters when the report will be shared with accountants or clients.
What files to export
- Bank statement or payout export with the net movement under review and its available references.
- Supporting order, invoice, or processor export with rows that could narrow the difference to refund, fee, reserve, FX, or another adjustment type.
- Optional adjacent-period export when the likely cause may have landed in another cycle.
Manual workflow
- Start by recording the gap as an amount difference instead of guessing the exact cause.
- Check whether the exported files explicitly label fee, refund, reserve, or adjustment rows.
- Keep exact fee language only for rows the export truly proves.
- Leave the remaining gap in review until the support is strong enough to narrow the explanation.
- Export the final report with the difference visible rather than hiding it inside a forced category.
Common mistakes
- Calling every shortfall a fee before the export proves it.
- Blending refunds, taxes, and reserves into one unsupported explanation line.
- Removing the review state too early because the remaining amount seems small.
- Confusing payout deductions with final accounting classification.
How Reconcile Locally helps
- Supports amount-difference review without forcing an unsupported exact classification.
- Keeps the open difference visible alongside the source and bank evidence.
- Produces a report that is safer to share than a spreadsheet full of guessed fee labels.
What still needs manual review
- Some differences remain review items until another export or accounting context is available.
- This workflow helps with explanation safety; it does not prove the accounting treatment of every row.
- Leave the row in review when the files narrow the cause but still do not prove the final label.
Content review and sources
Written and reviewed by the Reconcile Locally product team. Last reviewed June 7, 2026.
Guidance is checked against current product behavior and first-party documentation where available. Reconciliation results still require human review.
Frequently asked questions
When should I say amount difference instead of fee?
Use amount difference when the exported files do not explicitly prove the exact cause. Only use fee, refund, reserve, or other exact labels when the source rows clearly support them.
Is this still useful if I already know some fees are involved?
Yes. You can keep the explicit fee rows visible and still leave the remaining unexplained gap as an amount difference until the last part is proven.