Key-based, order-independent matching
Reports sorted by date on one side and by payout batch on the other still reconcile correctly, because matching runs on the order ID you map — not row position.
All use cases
Every order should have a payment. Prove it.
The store says 1,184 orders. The processor's payout report says 1,179 charges. Finding the five missing — and the refunds, retries, and fee differences hiding in between — is what reconciliation actually means. CSV Power Editor compares both exports by order ID and gives you a reviewable exception list, with financial data never leaving your Mac.
Workflow
Two reports to an exception list.
- 1
Export both sides
Pull the orders export from your store or ERP and the transactions/payout report from the processor (Stripe, PayPal, Square — anything that exports CSV).
- 2
Open both and normalize the key
Open one file, import the other as a tab, and Trim Spaces on the order ID columns. If one system prefixes IDs (like #1001 vs 1001), use Find & Replace to strip the prefix first.
- 3
Compare keyed by order ID
Run Compare Files and map the order ID columns from each report as the key. Row order and column layout don't need to match.
- 4
Review the exceptions
The compare workbook identifies orders with no matching charge and charges with no matching order, and for matched rows shows both files' values — including amounts — side by side with audit columns.
- 5
Export the follow-up list
Filter the compare workbook to the rows that need action and Save Filtered to hand finance a short, concrete exception list instead of two raw exports.
Why it works
Reconciliation is a matching problem.
Missing rows on both sides
Unpaid orders and orphan charges both surface by key. That asymmetry — present here, absent there — is precisely what manual scanning gets wrong at volume.
Amounts visible side by side
Matched rows show each report's amount columns next to each other in the output workbook, so fee deductions, partial refunds, and currency rounding stand out on inspection.
Financial data stays local
Transaction exports contain customer names, amounts, and card metadata. Everything is processed on your Mac with no uploads and no outbound connections.
FAQ
Common questions.
The order IDs are formatted differently in each report. Can I still match?
Yes. Normalize first — Trim Spaces removes whitespace, and Find & Replace (with regex support) strips prefixes like '#' or 'ORD-' — then compare on the cleaned key.
Does it automatically flag amount mismatches with a tolerance?
It shows both reports' values side by side for every matched order in the compare workbook, so differences are visible on review. There are no automatic tolerance rules — you decide what counts as a discrepancy.
My payouts come in multiple files. Can I reconcile against all of them?
Yes. Merge the payout files into one sheet first (import as tabs, then Merge Files), then run the compare against the combined sheet.
Can I get just the problem rows as a file?
Yes. Filter the compare workbook to the exceptions and use Save Filtered to export only those rows as a CSV for follow-up.
Is any of this uploaded to a server?
No. The app runs entirely on your Mac and makes no outbound network connections — appropriate for financial exports.
Keep going
Related guides.
Compare Two CSV Files on Mac
Get a reviewable compare workbook with matched keys, changed columns, and missing rows.
Merge CSV Files into One
Combine multiple CSV or Excel exports into one workbook, dedupe the result, and export.
Reconcile CRM and Ecommerce Customer Data
Match customer lists from your CRM and store by email, find missing records, and build one master list.