A few things make reconciliation go smoothly:
- Upload one file at a time — don't merge several statements into one file by hand. A single full-year PDF or CSV containing individual dated transactions is fine; a summary of category totals alone is not enough to match purchases.
- Overlap is handled. If a transaction appears in two files you upload, the deduplication logic catches it — matching on merchant + amount + date within ±1 day.
- Check date-order previews when prompted. A numeric date such as
04/05/2026can mean April 5 or May 4. Review the raw-to-readable examples, choose Day first (DD/MM/YYYY) or Month first (MM/DD/YYYY), then select Continue with this date order only when the preview matches your statement. The choice applies to this upload only. If the message says This CSV has conflicting date formats, correct or re-export the CSV, or select Choose another file; there is no safe date order to force for mixed or invalid dates. - Keep dates close. For the best matches, the expense dates in your sheet should be within a day or two of the statement's posting date — the system allows ±1 day tolerance.
- Merchant name variations are automatic. "DELTA" vs "DELTA AIR LINES 016" still match; partial-name matching is built in.
- Work the tabs in order: start with Missing Receipts (statement charges with no matching expense row), then review Credits & Refunds (money that came back to the card), and use Matched to confirm the totals line up before marking the reconciliation done.
- Near-matches live inside Missing Receipts, not in a separate tab. When the system finds a probable pair but isn't certain, the row appears in Missing Receipts with a ⚠ Needs review badge and an inline comparison of the receipt against the charge, so you confirm or reject it in place.