Staff cleaned and categorized transactions
Different bank formats, descriptions, and account lists made each monthly run a fresh spreadsheet exercise.
EXAMPLE · BOOKKEEPING
Bookkeeping Classification and Review
The system takes bank statements and transaction files through parsing, duplicate checks, classification, review, learning, and export. The bookkeeping team approves the final work. It works with QuickBooks, Xero, and the tools the firm already uses.
Based on a Calyer bookkeeping build. Names, volumes, dates, and results are illustrative.BEFORE THE BUILD
The close kept waitingon transaction cleanup.
Before review could start, staff had to clean each export, find duplicates and transfers, and apply the client's chart of accounts by hand.
Review waited for a prepared file
The reviewer could not start until every date, amount, description, and account column was ready.
Duplicates and transfers surfaced late
The same movement could appear in two accounts and get noticed only during reconciliation.
app.calyer.ai/bookkeeping/august-close
AUGUST CLOSE
86 NEED REVIEWTransaction review
Transactions1,248
Ready1,162
Staff review86
Files uploaded
PDF, CSV, or spreadsheet
Rows prepared
Dates, amounts, duplicates, and transfers checked
Transactions reviewed
86 exceptions need a decision
Final export
Ready after team approval
ILLUSTRATIVE BEFORE AND AFTER
What changes across1,248 sample transactions.
Illustrative comparison based on the workflow shown above. Times are rounded.
- Source
- Based on a Calyer bookkeeping build.
- Scope
- Illustrative set: 1,248 transactions.
- Comparison
- The before and after values compare the manual bookkeeping path with the system path shown on this page.
- Limits
- Names, volumes, dates, and results are illustrative. They are not client outcomes or a promise. This example does not measure accounting accuracy or close quality.
- Review date
- Reviewed August 2026.
Staff time per run
BEFOREAbout 26 hours
AFTERAbout 7 hours
Most staff time moves from row cleanup to review and approval.Time to first review
BEFORE2 business days
AFTERUnder 2 hours
Parsing and classification run after upload while the team works elsewhere.Rows checked by hand
BEFORE1,248 rows
AFTER86 exceptions
Rules, prior decisions, and policy decide which rows need attention.Reviewer corrections
BEFORERepeated next month
AFTERSaved as client rules
Approved merchant and account decisions can guide later statements.HOW THE TEAM USES IT
One workspace for the team.
Client dashboard
Every statement run, its current state, and the work still waiting on review.
Transaction review
Suggested account, vendor, confidence, policy, and source detail on each row.
Learning review
Reviewer corrections that can become client rules for the next statement.
INSIDE THE BUILD
What the bookkeepingsystem covers
The build carries a client from setup through an approved export while keeping the bookkeeper in control of every final decision.
Set up the client
Add the chart of accounts, policies, export format, and past classifications.
Prepare the rows
Parse files, normalize fields, and flag duplicate or matching transfers.
Classify
Use client rules, prior decisions, and AI to suggest an account and vendor.
Review and learn
Approve or change each exception and save useful corrections for later runs.
Export
Create the client's file format or post approved work to QuickBooks.
ONE PROCESS