01
Merchant names that look nothing like the vendor
A card statement shows a processor descriptor, a city and a terminal number instead of the vendor you know. Fuzzy payee matching and saved rules connect the descriptor to the vendor, and the next month it happens automatically.
02
Charges recorded in another currency
A hotel bill entered in euros and charged in dollars never matches exactly. The pair is matched within tolerance and the conversion difference is labeled on its own.
03
Posting date versus transaction date
Card statements carry two dates and your expense entries carry a third. Date windows keep these together and flag only real gaps.
04
Missing expense entries
A charge with no entry in your books is the most common card exception. It goes to the queue as unmatched, with merchant, cardholder and amount, ready to be chased.
05
Split and recurring charges
One charge recorded as two expense lines is matched as a group. Recurring subscriptions can be paired by a saved rule, the same way automated reconciliation software handles routine matches.