Build a monthly bookkeeping document register

Start with the requirement, not the upload

Your team still spends the morning finding out what is missing. A single document register turns that search into a clear list of work you can start and questions you need answered.

A complete client folder still leaves someone turning supplier invoices into spreadsheet rows. That is the step ParseMill handles: upload invoice PDFs, review extracted details and line items beside the source, then download Excel. Keep document requests and engagement tracking in your existing process.

Use one row for each distinct requirement. Two bank accounts need separate rows even if the client calls both files a bank statement. Conversely, three uploaded pages might satisfy one requirement; they do not automatically become three completed items. Give each row a stable reference such as CL07-2026-09-BANK02. That reference identifies work, not a file name.

This is a suggested operating method, not a universal bookkeeping checklist. The register tracks collection and review; it does not determine accounting treatment or whether a particular document is professionally sufficient. Keep that decision with the assigned reviewer.

Set up fields that answer the next question

Create columns for item reference, client/entity, period, requirement, due date, state, evidence link, owner and next action/date. Add received-at and accepted-at fields if you need to investigate delays. Store documents in the firm's approved location and link to them; the register need not contain account numbers or copied financial details.

In Excel, Microsoft's table instructions explain how to turn a range with headers into a table. Use this for the register's rows. Excel data validation supports a list of permitted values and input/error messages. A status dropdown can therefore keep “received” and “received for review” from becoming accidental alternative labels.

Use a short, agreed vocabulary: requested, received for review, clarification needed, accepted, and withdrawn. Record a reason and approver when withdrawing a requirement. Put promised delivery dates in the next-action field rather than inventing a separate status for every client explanation. These definitions are your process choices; Excel does not decide whether a file should be accepted.

Copy this small register and adapt it

Synthetic example: Cedar Workshop is an invented client. All rows concern September 2026; the references and dates demonstrate administration, not a recommended document package. Copy the table into a spreadsheet and replace the requirements with those approved for your engagement.

This package has five requirements, two resolved rows, one internal review and two items awaiting client action. It has five uploaded files, but that file count says nothing about package completion. Only the reserve statement and card statement belong in a client follow-up; the merchant report belongs in the staff review queue.

Update the register before writing a reminder

1. Open new arrivals and check the client/entity, document type and covered period. Read enough to identify a missing page or obvious mismatch.
2. Associate each arrival with its existing requirement. If the match is unclear, retain the upload reference and assign clarification; do not guess from a similar file name.
3. Record receipt immediately. Move the row to accepted only after the designated check. Keep the reviewer and decision date visible.
4. Filter unresolved rows by their next action. Send client requests only for client actions that are due; assign internal review separately.
5. Before sending, reread the latest response and refresh the register. An afternoon upload can make a morning reminder list obsolete.

Give one person responsibility for maintaining each package, including cover during absence. A second staff member should be able to open any unresolved row and explain who acts next, what they need to do and when it will be checked.

Roll forward requirements, then check the process

At the next cycle, copy only requirements that still apply. Create new period-specific references, reset receipt and acceptance fields, and confirm changed accounts, contacts and due dates. Keep the previous cycle as its own record. Carry an unresolved old item forward by cross-reference when necessary; relabeling it as this month's item hides its age.

Trial the register with one ordinary cycle before expanding it. Check for unresolved rows without owners, accepted rows without evidence or a recorded decision, and reminders sent after receipt. Count packages returned for further collection and record the reason. Time active updating separately from days spent waiting.

The workflow audit checklist and toolkit can help record those observations. If the register exposes repeated rechecking between systems, bring that specific step and its measured workload to a document-collection workflow review; scope and any fee are agreed before further work.

Questions about this workflow