Loading your page
Most pages open in under 3 seconds. Larger reconciliations can take a little longer.
Loading your page
Most pages open in under 3 seconds. Larger reconciliations can take a little longer.
Most "unmatched" bank items aren't errors, they're timing: a check that hasn't cleared, a deposit in transit. Ogbadu's AI separates genuine timing gaps from items that need real investigation, so your reviewer's attention goes where it matters.
100%
recall on labeled timing/duplicate/reversal test scenarios
0.74
confidence cap on any FX-converted pair — never auto-cleared
The problem
A transaction posted in the GL a day before it clears the bank isn't a discrepancy, it's normal timing. Treating every one as an exception trains reviewers to ignore the exception queue.
An FX-converted pair can look like a match at an undated, unsourced exchange rate while the actual booked rate is different — a real accuracy risk hiding behind a clean-looking reconciliation.
A remittance advice alone tells you what should have been paid; only the bank statement confirms what actually moved. Treating the two as equally strong evidence overstates confidence.
How Ogbadu solves it
During setup, Ogbadu asks whether you expect timing gaps between periods, then reframes unmatched orphans that fall inside a data-relative timing window — without ever hiding a genuine mismatch behind that framing.
A currency-converted pair is disclosed with its proposed rate but capped below the auto-clear confidence threshold and routed to review by default — an unsourced rate table never silently authorizes a match.
The engine treats a bank line as confirmation of cash actually moving, separate from remittance advice, and reports explicitly when cash could not be independently confirmed.
When two different subsets of transactions could equally explain a deposit, that's surfaced as a genuine judgment call for a reviewer, not silently resolved by picking the first one found.
It asks during setup whether you expect timing differences, then reframes only genuinely unmatched, one-sided items that fall inside a data-relative timing window. A matched item with a real problem — like a duplicate or an overpayment — is never reframed as timing.
No. Cross-currency matches are disclosed with the proposed rate but capped below the confidence threshold required for automatic clearing, and routed to a reviewer by default, since the underlying rate table isn't a dated, sourced feed.
Upload a real export and see what the AI proposes in minutes.
Evaluating tools? Compare Recon Pilot to BlackLine, FloQast & Trintech