Canonical: https://1968labs.com/blog/bookkeeping-document-follow-ups > An original document-collection workflow for bookkeepers: track what arrived, request only missing items and leave accounting review with the team. [← All guides](https://1968labs.com/blog) Bookkeeping firms # How can a bookkeeping firm simplify document follow-ups? An original document-collection workflow for bookkeepers: track what arrived, request only missing items and leave accounting review with the team. 1968 Labs / 15 September 2026 / 3 min read Use a client-specific collection checklist and prepare follow-ups from the items still missing. An assistant can organize the request and draft the message. Received documents still need a bookkeeper’s review for the correct period, completeness and accuracy. ## Start with collection, not accounting decisions Month-end chasing is often a coordination problem: which documents were requested, which have arrived and what needs another message? A clear checklist can solve that before introducing any AI. Keep this workflow separate from reconciliation, transaction classification, payroll decisions and advice. Those tasks need their own controls and review. The narrow objective here is to give the bookkeeper a clearer handover. ## An original idea: Margin Document Desk In [Margin Document Desk](https://1968labs.com/work/margin-document-desk) , the collection list sits beside the next useful action. Mark documents received and prepare a follow-up. The message requests only what is still missing. Once all five example items are marked received, the action changes to a review handoff. It does not say the books are complete. That distinction is central to the idea: automation should describe the state it can actually establish. [![Margin document desk with a received-document checklist and a precise follow-up request.](https://1968labs.com/assets/work-margin-document-desk.webp)](https://1968labs.com/work/margin-document-desk) Explore the original concept: [Margin Document Desk ↗](https://1968labs.com/work/margin-document-desk) ## Define the checklist for each client The example includes an operating-account statement, sales summary, business-card statement, expense receipts and payroll summary. A real checklist should be set by the practice for that client and reporting period. It should also handle items that do not apply. | Record | Why it helps | | --- | --- | | Document and reporting period | Avoid asking for an ambiguous “latest statement.” | | Requested, received or reviewed | Keep collection distinct from professional review. | | Secure destination | Direct the client to the agreed portal. | | Responsible person | Make exceptions and follow-up ownership clear. | | Last request and reply | Avoid duplicate or unnecessary reminders. | ## Make the follow-up easy to act on A good message acknowledges what has arrived, lists the remaining items and explains where to provide them. Ask for clarification when an item does not apply instead of sending repeated reminders for it. Use the practice’s approved portal and communication process. Agree access and retention before connecting document systems. Do not put sensitive records into a public website demo or assume that connecting an AI tool is appropriate for every client document. ## When an assistant adds value If a checklist and scheduled template cover the work, use those. An assistant becomes more interesting when messages need to be interpreted, request wording varies by client or a person spends time assembling the same context for each follow-up. Test incorrect periods, incomplete uploads, replies that say an item does not exist and clients who have already responded. Review the drafts and state changes before enabling any automatic messages. ## What a first project could include Choose one team, one collection process and the existing portal or task system. Agree the checklist, review stages, access rules and exception owner. Track incorrect reminders and staff review time as well as how many items were collected. Explore the [Margin website concept](https://1968labs.com/work/margin-books) for the customer-facing side. Our [assistant projects start at $3,500 USD](https://1968labs.com/services/ai-agents) for one scoped workflow, with subscriptions and usage costs stated separately. Put it into practice ## Put the idea to work. Tell us which task takes up your team’s time. We’ll help define a useful first workflow. [Discuss your workflow ↗](https://1968labs.com/contact?need=ai-agents) ## Keep reading. AI & automation ### Does your small business need an AI chatbot? Decide whether clearer pages, saved replies, a simple workflow or a narrowly scoped support assistant will solve the task. Read the guide [View Does your small business need an AI chatbot?](https://1968labs.com/blog/does-small-business-need-ai-chatbot) Websites ### What should a small business website quote include? Compare website quotes using a practical checklist of scope, running costs, ownership, testing and handover. Read the guide [View What should a small business website quote include?](https://1968labs.com/blog/website-quote-checklist)