A small tool for a clearer close

A clearer trail from payout to bank.

Bring your payout, transaction, and bank-credit CSVs together for a practical first pass. See what lines up, what needs a closer look, and where to find the source rows.

Runs on your deviceNo account or uploadUSD only

Your evidence workspace

Let's take a closer look.

Use prepared, canonical CSVs or explore with the synthetic demo.

Local preview · orders closed
01 / Choose your files

Three files. One starting point.

Use the exact case-sensitive headers below. Your files stay in this browser.

payout_id,payout_date,payout_total
Up to 10 payout rows.

No file selected

payout_id,net
Up to 5,000 transaction rows.

No file selected

posted_date,amount
Up to 2,000 bank-credit rows.

No file selected
Required columns, formats & limits
  • Payouts: payout_id,payout_date,payout_total — up to 10 data rows.
  • Transactions: payout_id,net — up to 5,000 data rows.
  • Bank credits: posted_date,amount; reference is optional — up to 2,000 data rows.
  • Headers are exact and case-sensitive. Use ISO dates (YYYY-MM-DD) and plain decimal USD amounts, with no currency symbols or thousands separators. Payout totals and bank credits must be positive; transaction nets may be negative.
  • Maximum 5 MiB per file and 100 columns. Use UTF-8 CSV, not XLSX. Comma, semicolon, and tab delimiters are detected. Matching considers equal amounts from 2 days before through 7 days after a payout date.
Processed locallyNo uploads or analytics5 MiB per file · 100 columns maxSource files unchanged · no deduplication

Need a hand preparing your files?

Get your columns into shape.

Raw Shopify and bank exports need mapping to the canonical columns before this check. Mapping is separate from the free checker. The proposed service is scoped to one store, one bank account and one selected month of USD payouts and related evidence.

Orders are not open. You can still prepare a local brief.

Explore the mapping service