Available now
Rule-based matching
Keys, tolerances, hold windows and batch sums come from configuration. The same input always gives the same result, and every run records the configuration hash that produced it. This is not AI.
AI
No AI features are in the product today: matching is rule-based and repeatable. AI match suggestions and break classification are planned for R3 (Q1 2028), and people stay in charge of every decision.
Available now in the product todayPreview screen with demo data; full workflow in the release shownR1 · Q1 2027 planned release and quarterNot offered not offered and not planned
Available now
Keys, tolerances, hold windows and batch sums come from configuration. The same input always gives the same result, and every run records the configuration hash that produced it. This is not AI.
R3 · Q1 2028
For items left unmatched, Recondora suggests likely counterparts with a confidence score. A suggestion becomes a match only through maker-checker: a maker proposes it and a different checker approves it.
R3 · Q1 2028
Each break gets its probable cause (late settlement, reversal, timeout, duplicate or fee) and is routed to the team that owns it.
R3 · Q1 2028
The exception workbench shows a suggested reason and next action for each break, for the person working the queue to accept or change.
Not offered
Not offered and not planned. Force matches, closures and write-offs always need a maker and a different checker, enforced by the server; every proposal and decision goes to the hash-chained audit log.
How AI will work in Recondora

Book a walkthrough: we load sample files from two of your rails, run them through Recondora and show you every match, break and approval.