Reconciliation Examples for Payouts, Bank Deposits, and Invoices
Concrete reconciliation walkthroughs for Shopify, Stripe, PayPal, and invoice-to-bank matching with visible review logic and unresolved cases.
Examples help when abstract guidance is not enough. A useful walkthrough shows the starting files, the review logic, the resulting match structure, and the rows that must stay open.
These examples are simplified on purpose. They are meant to teach the review path, not to impersonate real customer ledgers or promise that every difference has one automatic cause.
Try with sample files | View sample report
What these examples are designed to show
- How a payout-first workflow differs from a direct sales-to-bank comparison.
- Why matched rows, needs-review rows, and amount differences must stay separated.
- How grouped payments, refunds, fees, and timing gaps change the explanation path.
- What a reviewer can safely conclude from the exported files and what still needs manual confirmation.
Example review states
| Line item | Amount or note |
|---|
| Matched payout | Net payout and bank deposit agree |
| Needs review | Two plausible source rows support one bank row |
| Amount difference | Gap exists but exact cause is not proven |
| Unknown bank payment | No safe source explanation yet |
What these walkthroughs use
- Platform or invoice export that describes the expected cash movement.
- Bank statement export with deposit date, amount, and reference for the row under review.
- Optional support export such as balance transactions, activity detail, or review notes when the first file is not enough.
How to read the examples
- Start with the problem statement and identify the exact mismatch being reviewed.
- Check the example rows to see what evidence exists in the exported files.
- Follow the workflow section to understand why some rows are matched and others stay open.
- Use the checks and limitations sections to avoid overclaiming beyond what the files prove.
How Reconcile Locally helps
- Uses the same matched, review, unknown, unpaid, duplicate, and amount-difference language across the examples and the product output.
- Shows what the review package should look like before a client or accounting handoff.
- Lets readers compare several problem shapes before trying the browser workflow on their own exports.
What still needs manual review
- Real exports can contain weaker references, mixed periods, and more edge cases than the simplified walkthroughs on these pages.
- The examples explain review logic, not accounting approval, tax treatment, or ledger posting policy.
Frequently asked questions
Are these real customer reconciliations?
No. They are simplified educational walkthroughs built to show how exported-file evidence should be reviewed without exposing real financial data.
Do the examples replace the sample report?
No. The sample report shows the final output layout, while these pages explain the reasoning behind specific mismatch patterns.
Payout examples
Start here when the bank row is a processor or platform payout rather than a one-to-one customer payment.
Invoice and bank examples
Use these when the bank export is the starting point and invoice support is incomplete or split.
Related standards and templates
Use these when you want the terminology, report structure, or workbook behind the examples.