Reconciliation software for accountants has to handle many clients at once, keep each client's files apart, record who prepared and who reviewed each reconciliation, and log every edit. A controller needs speed on one set of books. A firm needs evidence it can show a reviewer, a partner or a regulator.
What accountants need from reconciliation software that controllers don't
Accountants need reconciliation software that separates clients, records review and proves what changed, because they answer to a reviewer and to the client. A controller reconciles one company's books and owns the result. A firm reconciles many companies' statements, often as support for an opinion or a report.
Where the two jobs differ
A controller's questions are internal: are all accounts reconciled this close, and who is late? A firm's questions are external: can I show support for this client's cash balance, and who signed it? That difference changes what a tool must provide.
- Many entities, few accounts each. A firm may see forty clients with two or three accounts apiece. A controller may see one entity with fifty accounts. Tools built for the second case organize by account. A firm organizes by client and period.
- Statements arrive from outside. Clients send PDFs, photos and scans in mixed layouts. The firm does not control the format, so extraction quality matters more than integration.
- The file is the product. What the firm hands over, or keeps for its own file, is the workpaper. Exports and references matter as much as the matching.
- Someone else reviews. A manager or partner reads the work. The tool should make their review quick and leave a record of it.
- Confidentiality sits with the firm. Client statements carry account numbers and payee names. Where they are stored and who can open them is a professional duty, not an IT detail.
A short list of tests
When you evaluate a product, ask five things. Can I keep each client's statements in a separate space? Can I give a reviewer access without giving them everything? Does the report show the footing result and the exceptions? Is every edit recorded? Can I export the support in a format my file accepts? A product that answers yes to all five is built for firms. One that answers yes to the first only is built for a single company.
Engagement folders, seats and reviewer sign-off
Firms organize reconciliation work by engagement: a folder for each client and period that holds the statements, the reconciliation and the exceptions. A seat is one named user, and reviewer sign-off is a recorded approval by someone other than the preparer.
Engagement folders
An engagement folder keeps everything about one assignment together, so a reviewer opens one place. It also contains risk. If one client's statements sit in a shared pool, a mistaken click can put them into another client's report. Ask whether folders are a real boundary in the tool or only a label.
Seats
A seat is a login for one person. Count the seats you need by role, not by headcount. A solo practitioner needs one. A team that prepares and reviews needs at least two, plus a seat for anyone who only reads. A larger firm may also want roles, so that a junior can prepare but not sign, and a partner can read every engagement. Shared logins defeat the purpose, because the log then cannot say who did what.
Reviewer sign-off
Sign-off means a second person has looked at the work and approved it. For the record to carry weight, it should show who signed, when, and what the report looked like at that moment. Three rules help:
- The preparer cannot sign their own work. The tool should enforce this, not leave it to habit.
- Sign-off freezes the report. If something changes afterward, the approval is cleared or the change is logged.
- The reviewer can send items back. A comment on a specific exception is more useful than a general rejection.
How firms use these together
A typical flow is simple. A preparer uploads a client's statements into the engagement folder and runs the checks. They clear the exceptions they can explain and note the rest. The reviewer opens the folder, reads the exception list, samples the lines the tool flagged as low confidence, and signs. The folder is then the file. For how an auditor tests what a client hands over, audit procedures for bank reconciliation, with a program covers the procedures a reviewer would apply.
Is audit software for accountants the same as reconciliation software?
Audit software for accountants and reconciliation software overlap but are not the same. Reconciliation software proves that records agree: statement to ledger, or statement to its own arithmetic. Audit software covers planning, sampling, workpapers and opinions across the whole engagement. A reconciliation tool is one input to an audit, not the audit.
Where they overlap
Both produce evidence. An auditor testing cash wants the footing result, the list of reconciling items and the support for each. A reconciliation tool that produces those items in a workpaper-ready form is doing part of the auditor's job. The overlap is largest in cash and bank procedures.
Where they part
- Scope. An audit platform plans the whole engagement and tracks risks, sampling and conclusions. A reconciliation tool deals with one kind of evidence.
- Judgment. An audit platform records the auditor's conclusions. A reconciliation tool records tests and results, and leaves the conclusions to the person.
- Opinion. Neither produces an opinion by itself. PreciseBankFlow's own FAQ says it does not give an audit opinion: it does the extraction, footing and exception testing, and the conclusions and sign-off stay with you.
Which one to buy first
If your pain is the volume of statements and the time spent footing and matching them, start with reconciliation software. If your pain is engagement management, such as sampling, review notes and file assembly, you need audit management software, and reconciliation output will feed into it. Many firms need both, bought separately.
Edit logs: proving what changed in a reconciliation file
An edit log is a record of every change made to a reconciliation after the tool first produced it: who changed a line, when, and from what value to what value. It matters because a reconciliation that can be edited without a trace cannot be relied on as evidence.
Why edits happen
Edits are normal. A line is misread and a preparer corrects it. A date is moved to the right period. A duplicate is confirmed and removed from the total. None of this is wrong. The problem is an edit nobody can see.
What a useful log records
- Who made the change, by name and not by a shared account.
- When, with date and time.
- What, meaning the field, the old value and the new value.
- Why, as a note, at least for changes to amounts.
- Against what, so the line can be traced to the source page.
How a reviewer uses it
A reviewer who sees the extract and the log together can answer a question that is otherwise unanswerable: was this number read from the statement, or typed in? A statement that foots only after three amount edits tells a different story from one that foots untouched. The log lets the reviewer decide whether those edits were sound corrections, or adjustments made to reach a result.
An example
Suppose a preparer changes a withdrawal from 1,580.00 to 1,850.00 after seeing the original page, and the statement then foots. The log shows the old and new value, the preparer and the time. A reviewer opens page 3, confirms the printed figure is 1,850.00, and accepts the edit. Without the log, the same result would look like a plug. The values here are an example only.
The Team plan on the PreciseBankFlow homepage lists a log of every edit to the extract. The product is in early access, so check what the log shows against the list above.
How should accountants size reconciliation software: pages or accounts?
Size reconciliation software by statement pages per month, because pages are what the tool reads and what drives the work. Accounts are a poor measure: one account with a hundred-page credit card statement costs more to process than ten quiet accounts with one page each.
Count your pages
Add up the statement pages you handle in a busy month, not an average one. Include scans and multi-page card statements. Add some room for the month-end and year-end rush, when more clients send documents and pages per statement rise. If a plan limit is close to your busy month, choose the next size up, and ask the vendor what happens when you go over.
Count your seats
Count the people who prepare, review or only read. Then ask how many may be added later and at what price.
The sizing table
The table shows how needs change from a solo practitioner to a firm. PreciseBankFlow's early pricing sits in the last column as one reference point; prices may change before general release.
| Need | Solo | Team | Firm | PreciseBankFlow early pricing |
|---|---|---|---|---|
| Seats | 1 | 2 to 3 | 4 to 10 | 1 seat; 3 seats; 10 seats with roles |
| Monthly pages | Low hundreds | Around a thousand | Thousands | Up to 300; up to 1,200; up to 4,000 |
| Reviewer sign-off | Self-review only | Needed | Needed, by role | Listed on the Team plan; Firm lists roles |
| Edit log | Helpful | Needed | Needed | Listed on the Team plan |
| Folders per engagement | Optional | Needed | Needed, across engagements | Listed on the Team plan; Firm lists exports across engagements |
| Early price a month | $49 Professional; $99 Team; $199 Firm |
The seat, page and price figures come from the homepage's early pricing. The "solo, team, firm" bands in the first three columns are example sizes, not product limits.
When to move up a size
Move up when you hit the page limit in two months out of three, or when a second person starts reviewing. A reviewer working in the same tool changes the need from convenience to control.
When not to let reconciliation software decide: accountant judgment
Reconciliation software must not decide anything that needs professional judgment: whether a difference is material, whether an unusual item is an error or a fraud, and whether the reconciliation supports the conclusion. The tool finds and lists items. The accountant decides what they mean.
What the tool decides, and what it must not
A tool can reasonably decide that a statement does not foot, that two lines look identical, or that a check number is missing from a sequence. It must not decide that a duplicate is an error, because some repeats are legitimate, such as two identical rent payments split across a month end. It must not decide that a difference is immaterial, because materiality depends on the client, the account and the engagement.
Four judgments to keep
- Materiality. What size of difference matters for this client and this purpose.
- Cause. Whether an unexplained item is timing, error or something worse.
- Reliance. Whether the statement itself can be trusted, particularly if it came from the client and not from the bank.
- Conclusion. Whether the evidence supports the figure being reported.
Why this matters for software choice
A tool that offers to "resolve" exceptions automatically is selling the opposite of what a firm needs. Prefer tools that list and explain over tools that close and hide. A good report makes your judgment faster and leaves a record of it.
Where to go next
To decide whether a tool is worth the move at all, read manual bank reconciliation versus software and the volume where it tips. Client statements are sensitive, so before you upload any, read about encryption in transit and at rest for online bank reconciliation. To try the product on an engagement of your own, request a place in early access.