A statement conversion tracker is a grid with one row per client account and one column per month. Each cell holds a status: arrived, converted, balanced or exported. At a glance it shows which statements are still missing, which failed a check and which are done, so nothing waits unnoticed between collecting a statement and posting it.
What does a statement conversion tracker record?
A statement conversion tracker records where every expected statement stands, not the transactions inside it. Each row is one account for one client, and each column is one statement period. The cell tells you the last step that statement completed. The tracker answers "what is left?" without opening a single file.
The rows need enough detail to tell accounts apart:
- Client name, as it appears in your practice's client list.
- Bank or institution, since one client may bank in two places.
- Account type and ending, such as "Checking 2208" or "Card 0456".
- Statement cycle, such as "calendar month" or "closes on the 20th", because a card that closes mid-month is due later than a checking statement.
- Who owns the account's work, if more than one person handles the client.
The columns hold the months. For a monthly practice, twelve month columns plus a notes column is enough. For catch-up work, add as many months as the backlog covers.
Six statuses cover the whole path. Keep them short, so a full row fits on a screen:
| Code | Status | Means |
|---|---|---|
| – | Expected | The statement period has ended, but nothing has arrived |
| A | Arrived | The statement file is in the client's folder |
| C | Converted | The batch has turned it into transaction rows |
| B | Balanced | The balance check passed and review is clear |
| E | Exported | The file has been delivered to the client's books |
| F | Flagged | A check failed or a question is open; see notes |
A statement conversion tracker template to copy
The template below is a working example for three made-up clients over four months. Copy the shape into a spreadsheet, replace the rows with your own accounts, and add a column per month. Statuses use the codes from the table above.
| Client | Account | Cycle | Jan | Feb | Mar | Apr | Notes |
|---|---|---|---|---|---|---|---|
| Example Bakery | Checking 2208 | Calendar | E | E | E | B | |
| Example Bakery | Card 0456 | Closes 20th | E | E | F | A | Mar: page 3 missing, asked client 4/3 |
| Example Plumbing | Checking 1190 | Calendar | E | E | E | C | |
| Example Plumbing | Savings 7731 | Quarterly | – | – | E | – | Quarterly statement, next due Jun |
| Example Studio | Checking 5560 | Calendar | E | E | B | – | Apr not yet received |
| Example Studio | Card 3304 | Closes 5th | E | E | E | E |
Three conventions keep a tracker readable:
- One cell, one status. If a statement is both converted and flagged, mark it F and explain in the notes. The worst status wins.
- Dates go in the notes, not the cell. "Asked client 4/3" tells the next person when to chase again.
- Non-monthly accounts are marked, not left blank. The quarterly savings account above shows "–" in months with no statement due, and the note says so. A blank cell should always mean "not done yet".
Put the tracker somewhere the whole team can open: a shared spreadsheet is enough. The row and column layout also works well when converted lines go to Excel, as the guide on how to extract data from multiple PDF files to Excel describes, since the same account and period columns appear in both.
Tracker statuses from arrived to exported
A tracker status moves forward only when a specific condition is met, and each condition is something you can check. Statuses describe facts, not intentions. "Converted" means the rows exist. "Balanced" means the check passed and review is clear. Setting a status early, because it will probably be fine, defeats the tracker.
The conditions for each move:
- Expected to Arrived. The statement file is saved in the client's folder with its standard name. An email saying "sent!" with no file is not an arrival.
- Arrived to Converted. The batch has read the statement and produced its transaction rows. If the file came inside an archive, it counts as arrived only after it is extracted and checked, which the guide on how to upload a zip of bank statements walks through.
- Converted to Balanced. The statement's opening balance plus its transactions equals its closing balance, and the lines in review have been cleared.
- Balanced to Exported. The export file for that client and period has been delivered to the client's books.
- Any status to Flagged. A check failed, a page is missing, or a question to the client is open. Write the reason in the notes.
A flagged cell returns to its previous status when the problem is fixed. A statement that failed its balance check because of a missing page goes from F back to A when the replacement arrives, then forward again through the batch.
Balanced does not mean every line is coded the way the client expects. A statement can balance with a line coded wrongly, such as an owner's personal withdrawal booked as an expense. Coding questions belong in review, and the guide to recording owner draws covers the line that most often needs a second look.
Updating the conversion tracker during a batch run
The conversion tracker is updated at three points in a batch run: when files arrive, when the batch finishes, and when exports go out. Updating at fixed points, rather than whenever someone remembers, keeps the grid accurate without turning it into a chore. One person owns each update, even on a team.
A practical rhythm:
- On arrival. Whoever files incoming statements marks each one A as it is saved. If statements are forwarded by email or dropped in a shared folder, mark them during a daily intake pass.
- After the batch. Once the run finishes, mark every converted statement C, then move each to B or F as review clears. A batch tool that reports passed and failed statements makes this a short job.
- After export. When a client's files are delivered, mark the period E for every account in that client's row.
AutoBankConvert holds back any statement whose balance check fails, puts uncertain lines in a review queue, and exports per client or per batch. Those three outputs map straight onto the tracker's C, B or F, and E. The tracker is still yours to keep. It covers the parts no converter can see, such as a statement the client has not sent yet.
For runs that go to CSV rather than straight into accounting software, the same rhythm applies, and the guide to batch converting bank statements to CSV covers what each output file should contain.
Which conversion tracker cells need attention at month end?
At month end, the conversion tracker cells that need attention are the ones that have not moved. A cell stuck on Expected past its usual arrival date, a cell on Converted that never reached Balanced, and any cell marked Flagged with an old date in the notes all point to work that will stall the close.
Scan the grid for these patterns:
- A dash in the latest column, past the date the statement usually arrives. Chase the client now.
- A whole row lagging, such as one account still on January while the rest of the client is on March. Usually one account was forgotten in the collection request.
- An F with a note older than a week. Either the question was never sent or the answer never came back.
- Converted with no Balanced for more than a few days. Review is backing up.
- Balanced with no Exported across many clients. Delivery is the bottleneck, not conversion.
The last two patterns say something about the practice, not about any one client. If statements pile up at the same status every month, that step needs more time or a different owner.
A quick month-end count helps: for the column just closed, count cells at each status. If most of the column is E and only two cells are F, the month is nearly done. If a third of the column still shows a dash, the close depends on statement collection, not on conversion.
Closed and new accounts on a conversion tracker
Closed and new accounts are the rows that cause false alarms in a conversion tracker. A closed account keeps showing Expected for months that will never come. A new account appears in the books before its row exists on the tracker, so its first statements are never chased. Both need to be marked when the change happens.
For a closed account:
- Mark the final statement month as usual.
- Mark every later month with a status that means "none due", such as "–" plus a note: "closed, final statement Mar".
- Keep the row until the end of the fiscal year, so the history stays in one place.
For a new account:
- Add the row on the day you learn the account exists, not when its first statement arrives.
- Mark months before the account opened as "–" with a note: "opened Apr".
- Ask for the first statement right away, because the first one shows the opening balance the books start from.
The first statement of a new account is also where the balance chain starts. Its opening balance is usually zero, and its first deposit is often a transfer from another of the client's accounts, which should match a withdrawal on that account's statement.
When is a conversion tracker more than a client needs?
A conversion tracker is more than a client needs when there are so few statements that you can see every one in your head. A client with one checking account and a dozen transactions a month does not need a row of statuses. A note in the client file saying which month was last exported does the same job.
The tracker earns its place when any of these are true:
- The client has three or more accounts, so one can go missing without being noticed.
- More than one person works on the client, so status has to be visible without asking.
- Statement cycles differ, such as a card that closes mid-month next to a calendar-month checking account.
- You are catching up a backlog, where the grid is the plan as well as the record.
For a practice, the tracker usually makes sense across all clients even if a few rows are short. One sheet, one row per account, is easier to keep than several systems. A small client's row simply fills quickly. If you want a batch run that reports the converted, balanced and flagged results your tracker needs, AutoBankConvert shows how a month of statements moves through those steps.