Bank Reconciliation That Matches Itself
Bank feeds land next to your ledger, most transactions auto-match on amount, date, and payee, and you spend your reconciliation time on the handful that need a human look.
Illustrative product view
What bank reconciliation in Fintra does
Reconciliation is where sloppy books get caught - or don’t. Fintra pulls in bank feeds and matches each transaction against the corresponding ledger entry on amount, date, and payee, so a controller reviews exceptions instead of re-checking everything line by line. What is left over is exactly the set of transactions that actually need a decision.
- Bank feed import from connected accounts, refreshed automatically
- Auto-matching against ledger entries by amount, date, and payee
- Exception queue for unmatched items, duplicates, and timing differences
- Book-to-bank difference tracked to zero at close, not estimated
Core capabilities
| Capability | What it does | What it replaces |
|---|---|---|
| Bank feed import | Pulls transactions from connected bank accounts automatically | Manually downloading and uploading CSV statements |
| Auto-matching | Matches bank lines to GL entries on amount, date, and payee | Line-by-line manual matching in a spreadsheet |
| Exception queue | Surfaces unmatched, duplicate, and timing-difference items | Scrolling a full statement to find what’s wrong |
| Multi-account reconciliation | Reconciles every connected account on its own schedule | One account reconciled well, others neglected |
| Close integration | Feeds reconciliation status into the Close Board task | A separate reconciliation spreadsheet outside the close |
How it works
From bank feed to zero difference
- 1
Connect the account
Link the bank account once; transactions flow in automatically going forward.
- 2
Auto-match runs
Fintra matches bank lines to existing ledger entries on amount, date, and payee.
- 3
Clear exceptions
Review the remaining unmatched items - new transactions to record, duplicates to flag, or timing differences to note.
- 4
Confirm the balance
The book balance and bank balance should agree; anything left is investigated before moving on.
- 5
Mark reconciled
The account is marked reconciled for the period, feeding directly into close readiness.
Where AI helps and where it stops
Auto-matching is a proposal, not a posting. AI matches transactions with high confidence and leaves genuinely ambiguous items for a human, rather than forcing a low-confidence match to hit the target. Every match, override, and exception resolution is recorded in the SentriAI audit trail.
Frequently asked questions
How accurate is automatic bank matching?
Auto-matching relies on amount, date, and payee agreement between a bank transaction and a ledger entry, and only matches when confidence is high. Ambiguous transactions - a split payment, a delayed deposit - are left in the exception queue for a human to resolve rather than force-matched.
What happens to transactions that don’t match?
They land in an exception queue categorized as unmatched, duplicate, or timing difference. You can create the missing ledger entry, flag a duplicate for investigation, or note a timing difference that will clear next period - each with a reason recorded for the audit trail.
Can I reconcile more than one bank account?
Yes. Every connected account reconciles independently on its own schedule, and reconciliation status for all accounts rolls up into the Close Board so nothing gets skipped when there are multiple operating, savings, or entity-specific accounts.
Does reconciliation status affect the close?
Directly. Bank reconciliation is one of the standard tasks on the Close Board, and an unreconciled account lowers your close readiness score - so the close process itself won’t let a reconciliation gap go unnoticed until it’s too late.
Stay in the loop
One practical finance briefing a week - new guides, checklists, and benchmarks.
Reconcile in minutes, not days
Start free, no card required. Connect a bank account and watch most of it match itself.
Talk to us