What monthly document workflow should a bookkeeper run for each client?

What are the stages, and what starts and ends each one?

The cycle belongs to the client's period, not to the day someone opens the file: every date in it is set from the client's period end, and it ends only when a sign-off record exists. Written down, it can be checked; run from memory, it changes with the month and the person. Request, completeness check and sign-off are dated gates, in that order; processing, queries and filing start with the first document or question, run alongside them and must all be finished before sign-off starts.

Stage names, order, conditions, logs, naming rule and sign-off record are constant across the portfolio; the right-hand column is per-client data. The accounting tasks of closing the month have their own checklist and run alongside.

Where a client's period does not end on the last day of a calendar month, or the engagement is quarterly or on another cadence, keep the same stages and conditions, set the dates from that client's period end at that client's frequency, and state each expected-set line per period: for a quarterly cycle, every statement for each account and the payroll register for every pay period in the quarter; for a period that ends off the calendar month, the statements that cover its last day. A quarterly client with two monthly-statement bank accounts and biweekly payroll, for example, expects six statements and six or seven payroll registers. The completeness check then counts against that per-period list.

What belongs in each client's expected document set?

Keep a standing list per client, held as data in the client's record. Each line names one document, who produces it, how it arrives, when it normally exists and whether its absence blocks the period. Re-deciding the list each month removes the fixed point that completeness is checked against. The first version comes from onboarding.

The IRS's record-keeping page tells businesses that the business they are in affects the type of records they need for federal tax purposes, and that for most small businesses the business checking account is the main source for entries in the books. It adds that purchases, sales, payroll and other transactions generate supporting documents, such as sales slips, paid bills, invoices, receipts, deposit slips and canceled checks. The engagement scope then shapes the list:

The IRS page notes that a combination of supporting documents may be needed to substantiate all elements of a purchase, so a bill and its proof of payment can be separate lines. AccountingTools defines a payroll register as a report that details all payments made to employees during a specific pay period. For a client paid through Stripe with automatic payouts, Stripe's undated payout reconciliation documentation says its report helps match the payouts received in the bank account with the batches of payments and other transactions they relate to. The same page says the report is available only where automatic payouts are enabled, points users on manual payouts to the Balance report instead, and says Stripe can't identify which transactions are included in an instant payout, so record in the client's expected set which report applies.

Change the list only when the client's business changes, such as a new account, a new processor, payroll starting or a new scope, and date each change with its reason. At each sign-off, add anything that appeared this period that the list did not expect and that will recur, dated with its reason; one-off documents stay in that period's intake log only.

When should the completeness check run, and what if something is missing?

Set each client's check date late enough that the slowest regular item normally exists, and early enough that a chased document can still arrive before the sign-off target. Some items lag the period: Stripe's undated payout reconciliation documentation notes that report data follows a separate processing schedule, so a payout might arrive before its reconciliation data is ready.

Compare received against expected line by line and raise a query for each gap that day. The Journal of Accountancy's article on incomplete client information says inquiries should be made in writing and as soon as you become aware of the incomplete information, and that a follow-up should identify exactly what is missing and the specific date by which a response is needed. Getting clients to send documents on time is a separate question.

Decide the outcome by a rule written in advance, so it does not depend on who does the work:

Where it is not practical to obtain the missing document and a reasonable estimate stands in for it, the incomplete-information article, written about tax work, lists what to document in writing: why the exact data was unavailable, what methodology was used to develop the estimate, client approval to use the estimate, and the client's understanding and acceptance of potential consequences.

What happens to documents that arrive late or by another route?

Give each client one intake channel (a portal, a dedicated mailbox or a shared folder) and record it in the client's data; documents taken through whatever route a client prefers that month leave no single place where the period's documents are known to be. Log every arrival with the date received, the route, the period it belongs to and the period in which it was processed, so a document belonging to an earlier period stays visible as such. Nothing is refused for arriving the wrong way, and nothing skips the cycle:

• Out of channel. Move it into the client's channel, delete the copy left where it arrived, log the route it came by and process it from there. For anything said by phone or in a meeting, the Journal of Accountancy's article on right-sizing risk management advises following up verbal discussions with a quick email summary saved in the client file.
• Late, period still open. Log it against the period it belongs to and process it in the current cycle.
• Late, period signed off. Log it against its own period, flag it as received after sign-off and open a query that day for any change it requires. Handle any change as in step 4 of the correction steps, never by editing the signed record.
• Resent. Treat it as a possible duplicate and test it as described next.

How do you catch duplicates and let corrections replace originals?

Before processing, test every arrival against the intake log. Same issuer, same document number and identical content, or an identical file: log it as a duplicate, link it to the original and do not process it. Same issuer, date and amount on a document with no number: treat it as a possible duplicate, open a query asking the client whether it is a second transaction, and do not discard it until the client answers. A document with the same issuer and document number as one already logged but any difference in content, or one the client marks or describes as corrected, revised or replacing an earlier document, is a correction, never a duplicate or a new document. A corrected document supersedes the original rather than joining it. When a correction arrives, handle it in this order:

1. Save it under the original's name with the next version number, in the original's period folder.
2. Mark the original as superseded and keep it; never overwrite it.
3. If the original was not yet processed, process only the new version.
4. If it was, open a query to correct the entry in the period the document belongs to. If that period is already signed off, decide instead under the practice's month-end close procedure whether the correction is posted in that period or in the current open one, record the choice and the reason as a dated addendum to that period's sign-off record, and tell the client if figures they have already received change.

How should the query log work without holding up the period?

Keep one query log per client, carried from period to period. Each entry records the following:

• The period and the document or transaction affected
• The question, worded so the client can answer it without context
• Who raised it, when, and the reply-by date
• What was assumed or recorded meanwhile
• The answer, the date cleared and who cleared it

A query's age is the time since it was raised. Review the log on fixed days each cycle and chase the oldest first.

A query holds only its own item, unless it is for an expected item marked blocking, which holds the period at stage 2 under the completeness rule. Otherwise the rest of the period moves on, the item is handled on the basis the log states, and an unanswered query carries into the next period's log with its original date, so its age keeps counting. A period closed with open queries and no record of them hides which figures rest on unconfirmed assumptions, so the sign-off record lists them.

Intuit's help for QuickBooks Online Accountant, updated 8/7/2026, describes, within Intuit Accountant Suite, an Ask client action whose request form fills in the request for missing transaction-level details; the client can open each request to explain what they bought and why, and a Books review column shows which tasks are finished or open. The request form lets you edit the due date for the client's response, but the same page notes that client requests with due dates set for a future year won't appear in the Books review tab; those are found in the client's QuickBooks Online company, in the My accountant tab. Keep the query log as the record of what is open, especially across a year-end. Wherever a platform's request lacks the reply-by date or the assumption used, keep them in the log.

What should sign-off show, and who signs?

Sign-off is what separates a reviewed period from a processed one. The Journal of Accountancy's article on telling a story with documentation, written about professional liability claims against CPAs, says that in such a claim the engagement documentation will be the primary method used to evaluate whether the CPA dutifully performed the agreed-to services, and its list of what to include covers the relevant client records received, client assertions relied upon by the CPA, and relevant dates. The sign-off record for each client and period holds the following:

• The expected set against what was received, with every exception and hold
• The queries open at sign-off, with their ages and the assumption used for each
• What the client confirmed that the period relies on, such as approval of an estimate
• What the reviewer checked, the preparer's and reviewer's names and the date

The reviewer checks the evidence, not the preparer's summary of it: compare the period folder with the expected set, read the open items in the query log, and trace a sample of processed documents into the books. Where staffing allows, the reviewer is not the preparer. In a one-person practice they are the same person; say so in the record, and review in a separate pass against the expected set and the log, not from memory.

Once saved, the record is not edited; later documents and corrections become dated addenda. The documentation article warns that changes to documentation after the engagement was completed can signal carelessness.

How should documents be filed and named?

File every document under the period it belongs to, never the date it arrived; filing by receipt date scatters a period across folders and puts late documents in the wrong one. The IRS's record-keeping page tells businesses to keep supporting documents in an orderly fashion and in a safe place, organized for instance by year and type of income or expense. A practice applies the same idea with folders by client, year, period and category, and file names built from client code, period, category, issuer, document date, the document's own number (or a running sequence where it has none) and version, such as ACME_2026-09_Payables_Supplier_2026-09-14_INV4471_v1. Anyone who knows the rule can then find a period's documents without asking who filed them.

Custody changes what the file must show:

• The practice holds the documents. Keep a register of originals in the practice's custody: what they are, since when, where they are kept and when they went back.
• The client keeps the originals. File the copy or export you worked from and note where the original is held, so the period can be rebuilt without access you may later lose.

How do you run one cycle across a whole portfolio?

Write the cycle once and hold every difference in a client register: period end and cadence, request, check and sign-off dates, intake channel, expected set, custody model, preparer and reviewer. A client with more documents, more sources or a wider scope gets a longer expected set, not its own process, with dates set by the same rules and its documents processed as they arrive; separate workflows per client cannot be supervised or handed over. Then plan the period-end peak from the register:

• Put every client's check date and sign-off target on one calendar and count the work due each week.
• Stagger check dates by when each client's documents normally exist, rather than giving every client the same day.
• Process high-volume clients' documents as they arrive, so their check date leaves only the gaps.
• Reserve reviewer time for sign-offs, which bunch at the end of the peak.

What must be written down so someone else can run it?

A colleague or successor needs these, kept with the practice's files rather than in one person's notes:

• The cycle definition, with the stages table, the completeness rule and the naming rule
• The client register, with each client's expected set and dates
• Each client's intake log, query log and sign-off records
• Client notes on whom to contact, how documents usually arrive and anything unusual in the records

Test it now and then: ask someone who did not do the work to find a given period's documents and say what is still open. Whatever they have to ask belongs in the register or the notes.

How do you keep client documents access-controlled during the cycle?

The Federal Trade Commission's guide Protecting Personal Information advises limiting access to personal information to employees with a need to know, and requiring that files containing personally identifiable information be kept in locked file cabinets except when an employee is working on the file. Within the cycle, that means the following:

• Give access to a client's folders and logs only to the people assigned to that client. Remove it the moment they stop working on the client, and have the client remove any user they hold on the client's systems at the same moment.
• Keep paper originals locked away except while someone is working on them.
• Move documents that arrive by personal email, text message or by hand into the controlled store, delete the copy from the personal mailbox, phone or message thread once it is stored, and log how they arrived and that the copy was deleted.
• On a client's own systems, work through a user set up for you with the narrowest rights the work needs, never the client's own sign-in.

The practice's wider data-security obligations are a separate question.