Doculane
A monthly bookkeeping document checklist should identify the statements, sales records, expense evidence and other reports needed for a specific client and period. Request only what the engagement requires, name each account separately, and explain what counts as a complete upload. Track receipt separately from the bookkeeper’s review of the contents.
Monthly documents to request
Start with the client’s actual accounts and services. A solo consultant and an online retailer should not receive an identical request. Remove items already available through an authorized connection or another agreed process, unless you need a separate source document.
The table below is an adaptable collection template, not a universal accounting or tax requirement. The bookkeeper responsible for the engagement should decide which records are needed. For US businesses, the IRS describes supporting business records such as invoices, receipts and account statements; the specific checklist still depends on the business and the work being performed.
| Document group | What to ask the client for | Add it when | What to check on receipt |
|---|---|---|---|
| Bank statements | A statement for each named business account and requested period | The statement is needed for the engagement | Correct account, dates and all relevant pages |
| Credit card statements | A statement for each named business card | The business uses that card and you need its statement | Card identity, billing period and complete document |
| Sales records | The agreed sales report or invoice export for the period | Sales records are not already available to the team | Source system and reporting dates are identifiable |
| Payment processor reports | The agreed payout or transaction report | The client uses a processor whose activity you need | Processor, business and reporting dates are identifiable |
| Expense evidence | Receipts, bills or invoices for the requested expenses | Your process requires those records or a specific transaction needs clarification | Supplier, date and transaction can be identified |
| Payroll reports | The agreed payroll summary for the period | Payroll is included in the engagement | Correct business and pay periods; avoid unrelated personal information |
| Loan or finance records | Relevant statement or new agreement | A balance, payment or new financing arrangement needs support | Lender, period and document are identifiable |
| Changes and exceptions | Relevant documents for a new account, asset or unusual transaction | Something changed during the period | The client explains which event the document relates to |
Receipt checks establish whether a usable-looking document arrived. They do not establish that the transaction has been reconciled or that the accounting treatment is correct.
Clear client requests
Write each requirement as document + source + period + completion condition. This is Doculane’s suggested request-writing pattern, not an accounting standard.
Compare “bank statements” with “Operating account ending 2048 — October statement — upload the complete PDF, including any blank or continuation pages.” The second instruction makes the requested account and period explicit. Use only the identifying details needed to distinguish accounts; a full account number is usually unnecessary in the request title.
Build a request using these fields:
- Client or business name.
- Period covered by the work.
- A separate checklist item for each required account or report.
- Brief instructions describing the document you expect.
- An agreed submission date, distinct from any statutory deadline.
- One submission destination and a person to contact with questions.
A document request works best when the client can tell which item a file is meant to satisfy before uploading it.
A request-ready example
This fictional example is for Northstar Studio. It demonstrates request wording and tracking, not a customer result or a complete month-end close.
| Checklist item | Client instruction | Example collection state | Internal next step |
|---|---|---|---|
| Operating account — October | Send the October statement for the account ending 2048 | Received | Check account and period |
| Reserve account — October | Send the October statement for the account ending 7712 | Received | Check account and period |
| Business card — October billing period | Send the card statement covering the agreed billing period | Missing | Follow up on this item only |
| Equipment purchase invoice | Send the invoice for the purchase listed in our request | Received | Review with the transaction record |
Three of four items have files in this example. That does not mean three items have been reviewed or that the books are ready to close. A collection count measures receipt, not accounting completion. Keep internal review notes in your accounting process rather than treating an upload indicator as approval.
Missing and incomplete files
Classify the problem before sending another reminder. A client who has no statement to provide needs a different reply from a client who uploaded the wrong month.
| Situation | Useful next message | What to record internally |
|---|---|---|
| Nothing uploaded | Name the outstanding document and repeat the submission link | Missing item and follow-up owner |
| Wrong period | Identify the period received and the period still needed | Replacement requested |
| Incomplete document | Explain which pages or details are absent | What must be checked on replacement |
| Item does not apply | Ask the client to explain why | Whether the responsible bookkeeper accepts the explanation |
| Document is not available yet | Ask when it is expected | Agreed next contact date |
These are working labels for a team tracker, not a promise that a particular tool implements each label. Do not silently mark an irrelevant item as received. Record the explanation and let the responsible person decide how to handle it.
For wording you can adapt, use the client document request email templates. Change the reminder to reflect the current missing items rather than repeating the original request in full.
The Doculane workflow
Doculane is document collection software for teams that need a client checklist, a submission link and a view of what has arrived. A bookkeeper can create a request, add item instructions, set a due date and schedule email reminders. Clients verify their email with a one-time code rather than creating a Doculane account, subject to the workspace’s sender access settings.
Clients can send documents in stages while the request remains active. Your team can inspect the received originals and keep files associated with the contact. Optional Google Drive copies are one-way; they are not two-way document synchronization.
Save a checklist as a template if it will be useful again. For the next month, create a new request from that template and update the period, items and deadline. Scheduled reminders do not automatically create next month’s request.
Doculane fits the collection step. It does not reconcile transactions, replace bookkeeping software or provide a QuickBooks/Xero accounting integration. If you need a recurring close workflow, client payments or accounting automation in the same system, include those requirements when comparing tools.
Frequently asked questions
Should every client send every document every month?
No. Tailor the list to the engagement, the client’s accounts and information already available to the team. Ask for additional evidence when a specific transaction or change requires it.
Is a bank statement the same as a receipt?
No. A statement and a receipt provide different information. The IRS notes that a combination of supporting documents can be needed. The responsible professional should decide what evidence is appropriate; this collection checklist does not determine deductibility or retention periods.
Does uploading every required file mean the bookkeeping is finished?
No. Receiving documents and completing their review are separate steps. A team still needs to check the files and perform the bookkeeping work.
Can a client upload the remaining files later in Doculane?
Yes, while the request is active and the sender is allowed by the workspace’s access settings. A due date supports reminder and overdue tracking; it is not, by itself, an automatic upload cutoff.
Get started
Choose one client, remove irrelevant rows and write account-specific instructions for the next period. Agree who will review the received files before treating the collection as complete.