FinSuite · Module
PTAS FinSuite Bank Reconciliation
Statement lines parsed from any bank format, payments tied back to bills and ledger entries, and breaks surfaced with their likely cause.
What the agent does
Statements Read, Not Retyped
Reconciliation is rarely hard. It is repetitive, it is monthly, and it is where the close quietly loses its days.
Input
Any bank format
PDF, scan or export: the statement is read on its structure, so there is no per-bank template to build and maintain.
Input
Continuity checks
Opening and closing balances are carried page to page, so a missing page or a truncated export is caught immediately.
Matching
Payment to bill
Transactions are tied back to the invoices they settled, including part payments and one transfer covering many bills.
Matching
Narration parsing
Reference numbers, UTRs and vendor names are pulled out of free-text narrations that were never meant to be machine-read.
Breaks
Likely cause
Unmatched items arrive with a reason attached: timing, bank charge, part payment, or genuinely missing.
Breaks
Ageing
How long each break has been open, so the old ones stop hiding behind this month's new ones.
Breaks
Unmatched, With a Reason
A list of exceptions is not much use on its own. What saves the afternoon is knowing which are timing, which are fees, and which need chasing.
Break list — 5 open on this account · Illustrative example
Ageing is what stops the old breaks hiding behind this month's new ones. Three explain themselves; two do not.
Batch payments
One transfer settling thirty invoices, split back out.
Bank charges
Fees and FX differences recognised, not left as breaks.
Timing differences
In transit at period end, flagged rather than chased.
Inputs
However Your Bank Sends It
PDF statement
Downloaded from the bank
Scanned statement
Posted or filed copies
CSV / XLS
Exports of any column order
MT940
Standard bank messaging
Bank API feed
Direct connection where offered
Custom format
Whatever your bank sends
FAQ
Questions Teams Ask
Which banks do you support?
All of them, because there is no per-bank template to support. The agent reads a statement on its structure (columns, running balance, narration block) rather than on a layout defined in advance, so a bank you have never mentioned works the same as one we have seen a thousand times.
Can it handle one payment that settles many invoices?
Yes, and the reverse: one invoice settled by several payments. Batch transfers are split back across the bills they cover, and part payments leave the remaining balance open against the original invoice rather than closing it.
What happens to transactions it cannot match?
They go to a break list, each with a likely cause and an age rather than a bare flag. Most breaks are timing, a bank charge or a part payment, and saying which is what turns an afternoon of investigation into a short review.
Does it post to the ledger?
Cleared items are written back to your system of record with the bank transaction linked to the entry, so the audit trail runs from statement line to ledger posting to the original invoice without anyone assembling it by hand.
Keep reading
Related Capabilities
AP Automation
The payables side of the ledger these payments are clearing.
Read more →Procure-to-Pay
Where payment sits in the full commitment cycle.
Read more →Bank Statement Processing
The DocPro agent that reads the statement itself.
Read more →FinSuite
The full finance workflow this capability feeds.
Read more →Bank Reconciliation Automation
Statement lines matched to the ledger, with every break explained rather than parked.
Read more →Next step
Close Without the Reconciliation Week
Run last month again through FinSuite and compare the break list with what your team found by hand.