Bank & cards
How does Mylo match receipts to card transactions?
By the Mylo team · Last updated July 1, 2026
Short answer
Mylo matches a receipt to a card charge only when the amount and date are an exact match in the same currency. There is no fuzzy tolerance, so you do not get sloppy false matches.
Matching starts with data flowing in: transactions sync from Plaid or Mercury into a unified ledger with signed amounts, so charges and credits are represented cleanly. Against that ledger, Mylo looks for a receipt whose amount and date line up with a transaction in the same currency.
The deliberate choice here is strictness. Matching is exact on both amount and date, with no tolerance and no fuzzy window. That avoids the false positives you get from approximate matching, where a slightly-off amount gets stapled to the wrong charge. The tradeoff is that a genuine gap, like a tip added later or a settlement on a different day, may stay unmatched, which is a signal worth reviewing rather than a silent guess.
A match can do more than reconcile. When a matched expense is on a corporate card, it can auto-approve if your organization enables that, since the charge itself is the proof. A matched personal charge does not get that shortcut and still needs manual approval.
How it works in Mylo
- Transactions sync from Plaid or Mercury into a unified ledger with signed amounts.
- Matching is exact on amount and date in the same currency, with no tolerance.
- Strict matching avoids sloppy false matches where an approximate amount hits the wrong charge.
- A matched corporate-card expense can auto-approve if your org enables it.
- A matched personal charge still needs manual approval.
- An expense that stays unmatched is a signal to review, not a silent guess.
Best practices
- Keep card connections active so transactions sync in the background for matching.
- Review any expense that stays unmatched, since it may be a personal charge or a timing gap.
- Mark shared cards as corporate so exact matches can auto-approve.