An unmatched transaction is an entry in one financial file that has no corresponding entry in the file it is being reconciled against.
An unmatched transaction is an entry that could not be paired with any candidate from the other file during the reconciliation process — even using fuzzy matching, date proximity, and tolerance rules. It represents the most severe form of reconciliation exception: there is no corresponding record at all, which may indicate a missing entry, an error in one file, a transaction not yet recorded, or a payment that requires investigation.
Unmatched transactions require the most attention during reconciliation review. They may represent legitimate timing differences, posting errors, missing ledger entries, or — in some cases — transactions that never occurred in one system. Each one must be investigated before the reconciliation can be finalized.
A bank statement shows a $12,000 debit that appears in no corresponding payables ledger entry. Investigation reveals the payment was processed by the bank but not recorded in the accounting system. A manual journal entry needs to be created.
Certanexa surfaces unmatched transactions as high-priority exceptions, shows what nearest candidates were reviewed, and uses PowerBot to help explain possible causes and suggest next investigation steps.
Safe boundary: Certanexa surfaces unmatched entries for review — it does not determine whether an entry represents an error, a missing record, or another issue. Finance teams make that determination.
Certanexa is in early access for modern finance teams. Join to explore exception review, PowerBot investigation, and audit-ready workflows.