Sample reconciliation report

This page shows a visible sample summary, category-level proof rows, and an interactive subset of the live report UI. The goal is to make the output inspectable before you open the workspace.

Reconcile Locally does not force unsafe matches. Uncertain rows stay in review. The cards and tables below show matched rows, needs-review cases, unpaid orders, unknown bank payments, amount differences, possible duplicates, and possible grouped payments in crawlable HTML.

Try with sample files | View sample report

Sample report summary

These counts come from the same interactive sample below. Review categories can overlap, so one unresolved row can appear in both the broader review queue and a narrower category such as amount differences or grouped payments.

Matched: 1 Rows with clear bank, payout, or invoice support.
Needs review: 5 Rows that still need a reviewer decision before export.
Unpaid invoices/orders: 1 Source rows still waiting for a supporting payment.
Unknown bank payments: 1 Bank movements that still need a source explanation.
Amount differences: 2 Review rows where the cash gap still needs a business explanation.
Possible duplicates: 1 Candidates that should not be forced into one payment trail.
Possible grouped payments: 1 One bank row likely supports several source rows.

Matched payments

These rows have enough support to be accepted without more review.

Example row	Amount	What it shows
Stripe payout PO_4201 matched to bank deposit	$1,284.20	Amount, date, and payout reference align across the files.

Needs review

These rows look related, but the explanation is not strong enough to auto-accept.

Example row	Amount	What it shows
Card settlement batch vs Order #8821-A	$120.00	The date and amount are close, but there is not enough reference evidence to auto-confirm the match.
Invoice INV-401 vs split transfer batch	$800.00	Two bank rows may settle one invoice, but manual confirmation is still required.

Unpaid invoices/orders

These source rows are still open because no supported payment was found in the current file set.

Example row	Amount	What it shows
Order #8821	$120.00	The source row is still waiting for a matching payment.

Unknown bank payments

These bank rows still need a source explanation or a manual classification.

Example row	Amount	What it shows
Unknown incoming transfer	$240.00	No supporting order, invoice, or payout row was found.

Amount differences

These rows stay open until the business explanation is confirmed from the exports.

Example row	Amount	What it shows
Stripe payout PO_4319	$42.18 difference	Possible reason: fee, refund, tax, timing difference, or payout adjustment. Needs review.
Grouped card settlement for INV-201 and INV-202	$250.00 difference	One deposit may support several invoices, but the open remainder still needs review.

Possible duplicates

These rows share the same amount or date signals strongly enough to stay open for duplicate review.

Example row	Amount	What it shows
Order #1048 duplicate candidate	$89.00	Two source rows could explain the same bank movement, so neither is forced into a final match.

Possible grouped payments

These rows show one bank movement that likely covers several source rows.

Example row	Amount	What it shows
Grouped card settlement for INV-201 and INV-202	$1,000.00 vs $1,250.00	One deposit may support several invoices, but the open remainder still needs review.

What this report does not claim

This sample report does not claim to fully explain every payout, fee, refund, tax, FX, or adjustment case.
The wording stays conservative when the files only prove an amount difference instead of an exact fee breakdown.
Some grouped payments and weak-reference matches still require manual review before export.

Try the same workflow with sample files

Open the browser workspace to review matched rows, amount differences, grouped payments, and unknown bank deposits locally with the sample dataset.