ReconFiles

Drag and drop your two files onto the upload areas, or click to browse. Both files must be in CSV format (.csv). If your data is in Excel, save each sheet as a CSV first via File → Save As → CSV.

Common use cases include matching a Stripe or GoCardless payout export against a Salesforce or Xero report, or reconciling a bank statement against an internal ledger. Any two CSV files with a shared reference column will work.

Once both files load, ReconFiles immediately scans the column values and suggests the best match key and amount columns — you usually won't need to change anything.

The auto-detect feature scans the actual values in each column — not just the column names — to find the best matching pair. This is especially useful when the same reference is called Description in one file and Asperato Reference in another.

It detects two things:

• Match key — the column whose values appear in both files (e.g. a payment reference like 9364-A143842077). Shows the percentage overlap found.
• Amount column — the numeric column to compare between files. ReconFiles checks that per-key totals broadly agree before recommending a pair.

You can override any suggestion using the dropdowns in Step 2.

When two systems convert the same foreign currency payment to GBP, they often use slightly different exchange rates — producing a small difference that isn't really a mismatch. The two tolerance fields let you absorb this noise.

• Ignore below £ — absolute floor. Any difference smaller than this (e.g. £0.01) is ignored.
• … and below % — percentage floor. Any difference smaller than this percentage of the amount (e.g. 0.5%) is also ignored.

A row is only flagged as a mismatch when the difference exceeds both thresholds. This means small rounding differences on large amounts pass through cleanly, while genuine discrepancies on any amount are still caught.

Click Reconcile files → to run the match. Results appear across four tabs:

• Matched — references found in both files, with all File A columns preserved and reconciliation summary columns appended.
• Only in A — references in File A with no match in File B. You can tick individual rows to exclude them from the Excel export.
• Only in B — references in File B with no match in File A.
• Amount mismatches — matched references whose summed amounts differ beyond your tolerance thresholds.

Each tab has a search/filter box and shows the row count. You can re-run at any time by changing the column settings and clicking Reconcile again.

Click ↓ Export to Excel to download a .xlsx workbook. It contains up to five sheets:

• File A sheet — your original data with a Match column (VLOOKUP formula) and a Difference (A − B) column (SUMIF formula) inserted after the key column, mirroring a typical manual reconciliation layout.
• File B sheet — same structure, looking up into File A.
• Only in A — unmatched rows from File A (excluding any you ticked for exclusion).
• Only in B — unmatched rows from File B.
• Summary — a metadata sheet recording which files were used, the match key, tolerances, and result counts.

Amount columns in the export are written as real Excel numbers, not text — so you can select any amount column and see the sum in Excel's status bar immediately.

If you reconcile the same two systems every month, save your settings as a named mapping. Click ＋ Save current as… in the Saved mappings bar, give it a name (e.g. Stripe ↔ Salesforce), and it's stored in your browser.

Next month, load the same files and select the mapping from the dropdown — all column selections and tolerance settings are applied in one click. Mappings are marked with ✓ (fully compatible), ◐ (partial), or ✗ (incompatible with the current files) so you always know what to expect.