Bank Reconciliation Software: Rules-Based Matching
Matching bank statements to your books by hand doesn't scale past a handful of transactions a day. Yukti's reconciliation engine does the matching; you review the exceptions.
How Yukti Handles This
Statement lines match against rules you define
- Bank statements import as a file (OFX, CSV, QIF) or a live bank feed
- Reconciliation models match each line to an open invoice, bill, or journal entry
- Rules you define: exact amount, partial amount within tolerance, reference number, or a combination
- Unmatched lines sit in a queue with the closest candidate matches suggested
Reconciliation models are reusable across statements
- Set up a rule once for how a payment processor's payouts work, gross sale minus fees, batched daily
- Every future payout from that processor matches the same way without reconfiguration
Timing differences are separated from real discrepancies
- Outstanding checks, deposits in transit, or unrecorded bank fees explain most balance gaps
- Book and bank balances rarely match same-day even when both sides are correct
- Reconciliation view separates timing differences from genuine discrepancies explicitly
Matching rules scope to account and payment method
- Exact amount and reference match handles routine invoice payments
- Partial match within tolerance catches short payments, aggregated match handles bundled deposits
- Each rule scopes to its bank account or payment method, so it won't misfire elsewhere
Where This Connects to the Rest of Your Books
Reconciliation checks AR and AP against reality
- Confirms AR by matching an actual customer payment to the open invoice it settles
- Confirms AP by matching an outgoing payment to its vendor bill and payment run
- Every match posts back to the general ledger as final proof
Reusable rules keep the exception queue genuinely small
- Once a rule exists for a payout pattern, future payouts match automatically
- Exception queue holds only transactions that don't fit an existing pattern
- That's a far smaller list for a controller to review than every statement line
Where the AI agent helps
The reconciliation agent learns from every match you confirm or correct.
Picks up patterns like a payer name that never matches the customer name exactly
Proposes the same match again the next time it sees a similar pattern
Improves its suggestions the more corrections it sees over time
See What This Could Save Your Team
Bank reconciliation
You could save ~3.8 hours/month
Common Questions
What's the difference between a bank feed and importing a statement file, and does Yukti support both?
A bank feed pulls transactions automatically on a schedule through your bank's connection, while a statement import means downloading a file (OFX, CSV, or QIF) from your bank and uploading it manually. Yukti supports both, so a business without a live feed for their bank still reconciles the same way, just with a manual import step instead of an automatic pull.
How does Yukti handle an outstanding check that hasn't cleared yet when we're trying to close the period?
An outstanding check stays visible in the reconciliation view as a known, already-recorded item that simply hasn't hit the bank statement yet, so it doesn't block a period close. The reconciliation report shows it explicitly as a timing difference rather than an unexplained gap between your book balance and the bank statement balance.
Can one bank deposit that bundles several customer payments be matched against multiple invoices at once?
Yes. An aggregated matching rule handles a single deposit line that represents several smaller payments settled together, splitting it against each open invoice it actually pays, which is the common case with payment processor payouts and batch customer remittances.
What happens to a transaction that doesn't match anything, does it block the reconciliation from closing?
It doesn't post to the ledger on its own. Unmatched lines sit in a queue with the closest candidate matches suggested, and someone has to confirm or manually code them before that specific line reconciles, but that queue is scoped to genuine exceptions since routine transactions match automatically.
Do we have to rebuild our reconciliation rules every month?
No. Reconciliation models are reusable and persist once configured, so a rule built for how your payroll provider's debits work, or how a specific payment processor batches payouts, keeps applying to every future statement without reconfiguration.
See Bank Reconciliation Software: Rules-Based Matching in Yukti
Get a walkthrough of how Yukti handles your books, or compare plans to see what is included in the free community edition.