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.
A vendor payment that's genuinely settled shouldn't show a variance just because a processing fee was netted out, or because the confirming bank line and the remittance both mention the same cash. Ogbadu's engine gets the arithmetic right so exceptions are the ones that actually need attention.
0
hard-coded numbers in the exported reconciliation — every total is a formula
100%
recall on duplicate-payment detection in labeled test cases
The problem
When a payment nets out a fee, the amount that hits the bank is smaller than the invoice. A naive reconciliation reports that gap as an open variance even though the vendor was paid in full.
When both a remittance advice and a bank statement reference the same payment, counting both as separate cash in inflates what's actually been applied and hides the real balance.
The same invoice paid twice, or two payments for the same amount to the same vendor, are easy to miss in a spreadsheet and expensive to catch late.
How Ogbadu solves it
Ogbadu nets vendor fees into the settlement calculation automatically, so a fee-netted payment is recognized as fully applied instead of exporting as a residual variance.
When both a remittance and a bank line exist for the same payment, only the settling line's fee and amount count once — the same cash is never applied twice.
A cross-vendor coincidence or an unsourced FX conversion is never silently auto-cleared. Controls can only downgrade a match to review, never upgrade one — so authority is earned, not assumed.
Every exported reconciliation is a live workbook: every applied amount, fee, and remaining balance is a real formula tracing back to the source row, so an auditor can re-verify the numbers, not just read a static report.
Yes. Fees are netted into the settlement calculation on both the invoice side and the cash side, so a fee-netted payment reconciles as fully applied instead of showing a false residual variance.
Yes. The Excel export is formula-driven, not a static dump — every applied amount and balance is a live formula referencing the original source rows, and a separate completeness control checks that no open item from your source sheets was silently dropped.
Upload a real export and see what the AI proposes in minutes.
Evaluating tools? Compare Recon Pilot to BlackLine, FloQast & Trintech