Offshore BookkeepersPowered by StealthAgentsPlan my role

Bookkeeping Operations

Client document request trackers: a method note for bookkeeping teams

A method note on tracking document requests from clients, covering the request log, the reminder cadence, and the limits of a completion measure.

A method note on tracking document requests from clients, covering the request log, the reminder cadence, and the limits of a completion measure.
Table of contents

Key takeaways

  • Record the document, the period, the request date, and the owner before the first reminder.
  • Separate a document that was received from one that was reviewed and accepted.
  • Report the age of open requests and the clients with repeated delays.
  • Use the pattern to change the request process, not to rank clients.

A bookkeeper sends a document request to twelve clients. Six reply the same week, three reply after a reminder, and three are still silent at month end. The close slips, and nobody can say which document is missing from which client.

A document request tracker makes the waiting visible. This method note describes what to record, how to review it, and what the tracker cannot prove.

Start with the request list

Build the request list from the close checklist: bank statements, credit card statements, invoices, payroll reports, and loan statements. Each line needs the client, the period, and the document.

Send the list as one request rather than a series of messages. A single list is easier for the client to action and easier for the team to track.

Record the request date

Record when the request was sent and the channel used. A request sent to the wrong address is not a client delay.

Keep the channel in the record. If the client says they never received it, the team can check rather than argue.

Separate received from accepted

A file can arrive and still be unusable: the wrong period, a partial statement, or a screenshot instead of a download. Record the review state separately.

Accepted means the bookkeeper checked the document against the request. The distinction is the difference between a full inbox and a ready close.

Set a reminder cadence

Agree the cadence with the client: a reminder at the due date, a second after three days, and an escalation after a week. Record each attempt.

Do not send daily reminders. A predictable cadence is easier to follow and less likely to damage the relationship.

What the tracker can show

The tracker can show which documents are missing, how long they have been outstanding, and which clients are consistently late.

It can show the team's response time as well: how quickly a received document was reviewed and accepted. That is the part the team controls.

What the tracker cannot show

The tracker cannot show why a client is late. The cause may be a system issue, a staffing change, or a misunderstanding about what was requested.

It cannot show whether the document is accurate. A bank statement can be complete and still contain an error that requires a question.

It also cannot prove that the close is on time. The tracker shows the requests; the close depends on the review and the accounting work.

Methodology and limits

This note is an operating design informed by public guidance on internal control, recordkeeping, and client operations. It does not report an empirical study or establish a service level.

The fields were tested against common cases: a missing statement, a partial file, a document for the wrong period, and a client who changed contacts. The design keeps those cases distinguishable.

Review cadence

Review the open requests weekly and the pattern monthly. The weekly pass sends the reminders; the monthly pass looks for repeated causes.

Keep the same definitions across reviews. A tracker that changes shape cannot show whether the process improved.

Reminder templates

Write two reminder templates: one before the due date and one after. Keep them short and specific about the document and the impact on the close.

Record which template was sent. A generic reminder is easy to ignore, and the record shows whether the team escalated appropriately.

Portal versus email

Record the channel the client prefers and use it consistently. A portal request may be more secure but slower if the client does not log in.

Where the client uses a portal, check the upload state rather than assuming the request was seen. The tracker should reflect the actual channel.

Client changes

When a client changes bookkeeper, email, or portal access, the open requests need a new owner. Record the change and re-send the open list to the new contact.

A request that was sent to a departed employee is not a client delay. The tracker should show the re-send date.

A worked example

A client has three open requests at the due date. One is a bank statement that arrived but was for the wrong month, one is a payroll report, and one is a loan statement.

The first is re-requested with the correct period, the second is escalated to the client's accountant, and the third arrives after a reminder. The tracker shows the review state for each, not only the arrival.

Client communication

Tell the client what is still outstanding and what it affects. A short list with the close impact is more useful than a generic reminder.

Thank the client when the documents arrive. The relationship matters more than the individual request, and the next close will depend on it.

Client education

Tell new clients what documents are needed and when. A short welcome note with the list prevents the first close from becoming a scavenger hunt.

Record that the note was sent and to whom. A client who received the list cannot claim ignorance later, and the record ends the argument.

Measuring team response

Track the time from receipt to acceptance, not only from request to receipt. The team controls the review time, and it is the part most likely to delay the close.

Record the median and the slowest cases. A slow review with fast client replies is a capacity finding, not a client issue.

Weekly review

Review the open requests every week with the close owner. The meeting is short: what is outstanding, who is chasing, and what is blocking the close.

Record the decisions. A review without a decision becomes a status update that repeats the same list.

Conclusion

A document request tracker makes the waiting visible and the review state explicit. It shows what is missing, how long it has been missing, and who is responsible for the next step. It does not show why the client is late or whether the document is accurate, and it should not be presented as if it does.

Listed sources

  1. U.S. GAO, Standards for Internal Control in the Federal Government
  2. IRS, Recordkeeping
  3. U.S. Small Business Administration, Manage your business

Related research