{
  "question_id": "Q-0020",
  "slug": "how-a-bookkeeper-can-get-clients-to-send-documents-on-time",
  "display_title": "How can a bookkeeper get clients to send documents on time?",
  "format": "article-v2",
  "applies_to": {
    "countries": [
      "US"
    ],
    "frameworks": [],
    "tax_year": null,
    "platforms": []
  },
  "general_concept": true,
  "summary": "Make the client's document duty a written engagement term: which documents, in what form, by when, and what follows if they are late. Tie each due date to a consequence the client can see, ask for named items in one bounded request, and stop requesting what you can pull through access the client has granted. Run a scheduled reminder ladder that climbs to the relationship owner, track every item, and decide deliberately when documents never arrive.",
  "body": "## Why does the chasing never stop, and what should the engagement terms say?\n\nConstant chasing usually means the client's part of the work was never agreed, and a deadline the client has not seen or accepted gives you no position to escalate from. So make supplying documents a written term of the engagement. A Journal of Accountancy article on engagement letters for tax compliance services lists, among a letter's benefits, helping to clearly communicate client responsibilities, especially those around deadlines and provision of client information.\n\nWrite the client's side of the arrangement in five parts:\n\n- **Which documents.** Name each class the client supplies for each period, such as statements for accounts you cannot see, receipts, invoices, loan statements and explanations of unusual transactions.\n- **In what form.** Say what is acceptable for each class, for example a downloaded PDF statement rather than a photo of a printout. The Journal of Accountancy article on client onboarding advises educating the client on what information is necessary, including format.\n- **By when.** Give a due date for each period, derived from a real anchor rather than your preferred close day.\n- **Who.** Name the person at the client who sends documents, the owner or manager above them, and the people at your firm who send reminders and escalate.\n- **What follows if documents are late.** State the reminder ladder, what happens to that period's deliverable, how out-of-cycle or rework effort caused by late delivery is charged, and when either side may end the engagement. A Journal of Accountancy article on CAS engagement letters advises including the circumstances under which the client and firm are unilaterally permitted to terminate the engagement, including nonpayment of fees.\n\nChasing absorbed silently into a fixed fee is invisible to both sides, so nothing pushes either to change. The Journal of Accountancy article on client onboarding advises, depending on your fee structure, discussing how client delays may affect the client's bill. Check your current letter against the five parts: wherever one is missing, the route is renegotiation, not enforcement. The wider onboarding process and its document checklist are a separate question.\n\n## What if the engagement began without written terms?\n\nA term that does not exist cannot be invoked, so add it where the arrangement is being reset anyway. The CAS engagement letter article recommends limiting the timing of an engagement to no more than one year, which makes each renewal a natural point to add document terms. The same CAS article recommends a new, separate engagement letter for significant scope changes, so a new service or a material change in the work is the other point. Until then, send the proposed terms in writing with the reason, drawn from your record of the client's late periods, and treat new dates as binding only once the client has agreed to them.\n\n## How do you set a due date the client will take seriously?\n\nA due date works when the client can see what it protects. Anchors differ in whether the client feels them:\n\n| Anchor | Does the client feel it? |\n|---|---|\n| A federal or state filing or deposit due date the client is subject to | Yes: the consequence falls on the client |\n| A reporting date in the client's loan, investor or grant agreement | Yes: the client answers to that party |\n| A payroll run, budget review or other decision the owner has scheduled | Yes: the owner's own plan slips |\n| Your firm's preferred close day or staff calendar | No, unless derived from one of the above |\n\nThe IRS's Publication 509, Tax Calendars, warns that a taxpayer who is late may have to pay a penalty as well as interest on any overdue taxes. Name the consequence of the anchor each date protects (the penalty and interest Publication 509 warns of for a tax date, or the lender's for a loan reporting date) in the terms and in each request that date governs.\n\nWhere the client faces a fixed external cycle, derive the internal date backward from it. Publication 509 sets out federal due dates in calendars, including one covering various due dates of interest to employers, and advises taking action before the listed due date whenever possible. State returns follow each state's own schedule: Washington's Department of Revenue, for example, assigns a business a monthly, quarterly or annual filing frequency and states it in the welcome letter it sends after registration, so confirm the client's own filing frequency. Count back from the external date by the working time you need to process and reconcile the period, the client's review time, the working days your ladder needs from the due date to the escalation rung, and a buffer for one round of follow-up questions. If processing takes eight working days, review three, the ladder three and the buffer two, documents are due 16 working days before the external date. The Journal of Accountancy article on client onboarding notes that clients may not understand deadlines and underestimate how much time a CPA needs to complete the work once information has been received, so show the client this arithmetic. On a year-end-only engagement the anchor is the annual return or reporting date, so start the ladder earlier and space its rungs wider.\n\n## What makes a request answerable in one go?\n\n\"Send everything for last month\" has no finish line, so the client cannot tell when they are done. A Journal of Accountancy piece on incomplete information, written about tax-return work, advises identifying exactly what information is missing and the specific date by which a response is needed, and explaining the potential consequences of a failure to respond by that date, such as penalties and/or interest for an untimely filing. The same incomplete-information piece advises making inquiries in writing and as soon as you become aware that information is incomplete.\n\nBuild each request so that one reply can complete it:\n\n- Put the client, the period and the due date in the subject line.\n- List each outstanding item by name and period, such as the statement for a named account or support for each listed transaction with its date and amount.\n- State the acceptable form for each item and the one place to send it.\n- Let the client answer \"none this period\" for any item that may not arise every period.\n- Say what happens on the due date if items are still missing.\n\nSend the period's routine request once per client on the same cycle day, not item by item, so the client can set time aside for it; but when something you have received turns out to be missing, incomplete or inconsistent, raise it in writing as soon as you find it, as the incomplete-information piece advises. The channel that carries the request is a separate question.\n\n## Which requests can you stop sending?\n\nBefore an item goes on a request, decide whether only the client holds it or whether you can retrieve it through access the client has already authorised:\n\n| If the item is | Then |\n|---|---|\n| Held only by the client, such as receipts, contracts, loan documents or an explanation of a transaction | Request it, with its form and due date |\n| Retrievable through access the client has authorised | Pull it yourself on the cycle day and leave it off the request |\n| Partly retrievable, such as transactions without the statement | Pull what you can and request only the rest |\n\nWhat is retrievable depends on each provider's own documentation. Intuit's QuickBooks Online help page on updates to the new AI-powered banking page, updated in August 2026, says pending transactions are transactions that QuickBooks downloaded from the connected bank or financial institution, so in QuickBooks Online a connected account's cleared transactions need no request. The statement may still be needed: Intuit's page on the QuickBooks Online reconcile workflow, also updated in August 2026, says reconciling needs monthly bank statements for the account. For a payroll provider, bank or card issuer, check that provider's own documentation on what an authorised accountant or view-only user can download before dropping an item. How the client grants access is a separate question.\n\n## How should the reminder and escalation ladder run?\n\nIdentical reminders teach the client that the date is soft, so each rung after the reminder must change something: the sender, the recipient or the consequence stated. Put every rung in the calendar when the request goes out, each with a named owner, so no one decides the next step from memory. A ladder for a monthly engagement might run like this:\n\n| Rung | When | From | To | What changes |\n|---|---|---|---|---|\n| Request | Cycle day 1 | Assigned bookkeeper | Named client contact | Full item list, form, due date and consequence |\n| Reminder | Two working days before the due date | Assigned bookkeeper | Named client contact | Lists only the items still missing |\n| Past due | One working day after the due date | Assigned bookkeeper | Client contact, copying the client owner | Names the deliverable now late and why |\n| Escalation | Three working days after the due date | Relationship owner at the firm | Client owner | States the consequence now in play and sets a final date |\n| Decision | While the remaining working time still covers the anchor | Relationship owner | Client owner | Records the client's choice among the paths below |\n\nSet the last rung by the anchor, not the calendar, and send every rung in writing.\n\n## How do you keep track of what is outstanding?\n\nKeep one status record per client per period, with a line for every expected document, including those you pull yourself. It turns lateness into a recorded fact and is the evidence for diagnosis and repricing. The incomplete-information piece observes that contemporaneous records are often the strongest evidence of conversations between the client and the CPA. Here is one client's month as of cycle day 9, counted in working days:\n\n| Document | Source | Requested | Due | Received | Status | Rung reached |\n|---|---|---|---|---|---|---|\n| Operating account transactions | Bank feed | Not requested | Day 1 | Day 1 | Complete | None |\n| Operating account statement | Client | Day 1 | Day 6 | Day 3 | Complete | Request |\n| Receipts for 7 listed card charges | Client | Day 1 | Day 6 | 4 on day 6, 3 on day 8 | Complete | Past due |\n| Equipment loan statement | Client | Day 1 | Day 6 | Not received | Outstanding | Escalation |\n| Payroll register | Client | Day 1 | Day 6 | Day 2 | Complete | Request |\n\nLog each request and reminder beside it, with its date, sender, recipient and the items listed. Read across periods, the record shows which clients are chronically late, on which items, and at which rung they finally deliver.\n\n## Why is this client late, and what fixes it?\n\nRepeating a reminder treats every late client alike. Read the status record for the cause, then match the remedy:\n\n| Cause and its signs | Remedy |\n|---|---|\n| **No responsible person.** Requests bounce between people, and replies come from whoever saw them. | Have the owner name one document contact and a backup in writing, and address the ladder to them. |\n| **Unusable channel.** The client says items were sent, yet they arrive in pieces by other routes. | Agree one channel the client actually uses. The Journal of Accountancy article on client onboarding advises identifying permissible and impermissible methods of communication. |\n| **Volume beyond capacity.** Statements arrive on time, but high-volume items such as receipts lag. | Pull what you can, split the batch into smaller and more frequent ones, or offer to do the gathering as a priced service. |\n| **Capability limits.** The client does not know how to download an item or which document you mean. | Walk them through it once and add an example of each item to the request. |\n| **Deliberate deprioritisation.** Everything is late, and documents arrive only at the escalation rung. | Escalate to the client owner earlier and tie each date to its anchor; if nothing changes, treat it as the engagement decision below. |\n\n## What should you do when documents still do not arrive?\n\nWhen a deadline passes with documents still outstanding, choose a path and put it in writing; once the last rung has passed, the remaining paths are engagement decisions:\n\n| Path | When it fits and what to record |\n|---|---|\n| Escalate within the ladder | A rung remains and the client owner has not yet been asked for a decision. |\n| Proceed on what is available and record the limitation | The gap can be marked clearly; the deliverable and your file state what is missing and what could not be done. |\n| Move the work to the next cycle | No external date depends on the period; tell the client in writing that its external due dates do not move. |\n| Reprice or rescope | Lateness is chronic or structural; agree the new scope or fee in writing before doing the work. |\n| Withdraw | The client will not supply what the work needs; follow the letter's termination terms and tell the client in writing which work and due dates remain theirs. |\n\nThese paths are a workflow for bookkeeping-only engagements. If the engagement also includes preparing financial statements or tax returns, check the professional standards that apply to that service before proceeding on incomplete records or withdrawing.\n\nWhatever the path, document the position. The incomplete-information piece, written about tax returns, says that if the incomplete information cannot be reasonably estimated and is still missing, you should document in writing to the client what information was requested and is still incomplete, your attempts to follow up, that the gap prevents you from timely filing the return, the potential consequences of late filing, late payment and inaccurate returns, and that remaining compliant with tax filings is the client's responsibility. For a bookkeeping period, name the missing items, the date of each request and reminder, and the deliverable affected. Without that record, it may be harder to show that the gap was the client's if the work is later questioned; the incomplete-information piece makes this point about tax filings.\n\nThe incomplete-information piece also advises considering withdrawal if the client insists on filing without the missing information or does not want to make the necessary disclosures. If you also advise on or prepare the client's tax returns, Treasury's regulation at 31 CFR 10.34(d) says a practitioner doing so may not ignore the implications of information furnished to, or actually known by, the practitioner, and must make reasonable inquiries if the information as furnished appears incorrect, inconsistent with an important fact or another factual assumption, or incomplete.\n\nWhen you reprice or rescope, the CAS engagement letter article lists ways to document a scope change in order of formality (a signed engagement letter amendment; an email with the client confirming the change and its impact on services and fees; or a change log reviewed with the client) and recommends a new, separate engagement letter for significant scope changes.",
  "sources": [
    {
      "id": "REF::1",
      "url": "https://www.journalofaccountancy.com/issues/2025/nov/blocking-and-tackling-engagement-letters-for-tax-compliance-services/",
      "title": "Blocking and tackling: Engagement letters for tax compliance services",
      "publisher": "Journal of Accountancy",
      "published": "November 1, 2025",
      "retrieved_at": "2026-09-30T20:12:04+00:00",
      "sha256": "eead87115a11da2d9a17aa24da79ac917a13d91ff43b032d35612c295cc4092e",
      "supports": [
        "C1"
      ]
    },
    {
      "id": "REF::2",
      "url": "https://www.journalofaccountancy.com/issues/2024/apr/help-reduce-risk-with-formal-client-onboarding/",
      "title": "Help reduce risk with formal client onboarding",
      "publisher": "Journal of Accountancy",
      "published": "April 1, 2024",
      "retrieved_at": "2026-09-30T20:12:05+00:00",
      "sha256": "82312d2f2e629bdf87555299441c8e6a7ca2272c49a1807efcffafc06917fa36",
      "supports": [
        "C2",
        "C10",
        "C17",
        "C32"
      ]
    },
    {
      "id": "REF::3",
      "url": "https://www.journalofaccountancy.com/issues/2026/apr/tips-for-writing-cas-engagement-letters/",
      "title": "Tips for writing CAS engagement letters",
      "publisher": "Journal of Accountancy",
      "published": "April 1, 2026",
      "retrieved_at": "2026-09-30T20:12:05+00:00",
      "sha256": "21dd748fc588468baf6192bea83a64be189b58632ee13e6089f28da320e035dc",
      "supports": [
        "C3",
        "C4",
        "C5",
        "C27",
        "C28",
        "C29",
        "C30",
        "C31"
      ]
    },
    {
      "id": "REF::4",
      "url": "https://www.irs.gov/publications/p509",
      "title": "Publication 509 (2026), Tax Calendars",
      "publisher": "Internal Revenue Service",
      "published": "Publication 509 (2026); page last reviewed 30-Apr-2026",
      "retrieved_at": "2026-09-30T20:12:04+00:00",
      "sha256": "8d545d7c740a1b8745316937cff2aa159113a4a121cd709d26251b1af83bcc73",
      "supports": [
        "C6",
        "C7",
        "C8",
        "C33"
      ]
    },
    {
      "id": "REF::5",
      "url": "https://dor.wa.gov/file-pay-taxes/filing-frequencies-due-dates",
      "title": "Filing frequencies & due dates",
      "publisher": "Washington State Department of Revenue",
      "published": "undated",
      "retrieved_at": "2026-09-30T20:12:04+00:00",
      "sha256": "682c7e980e0441e80b8e964e10c3e23ff666cc1b1f1e7ae31bf2e40ac47469f8",
      "supports": [
        "C9",
        "C34",
        "C35"
      ]
    },
    {
      "id": "REF::6",
      "url": "https://www.journalofaccountancy.com/issues/2026/sep/the-5-ws-of-incomplete-information/",
      "title": "The 5 Ws of incomplete information",
      "publisher": "Journal of Accountancy",
      "published": "September 1, 2026",
      "retrieved_at": "2026-09-30T20:12:06+00:00",
      "sha256": "d6b9649583017951ba51c27ce2487802ef1e5b0c2586e126e712c12c27b408ea",
      "supports": [
        "C11",
        "C12",
        "C13",
        "C16",
        "C18",
        "C19",
        "C20",
        "C21",
        "C22",
        "C23",
        "C24",
        "C36",
        "C37",
        "C39"
      ]
    },
    {
      "id": "REF::7",
      "url": "https://quickbooks.intuit.com/learn-support/en-us/help-article/matching-rules/learn-updates-new-ai-powered-banking-page/L0hR7A9Zf_US_en_US",
      "title": "Learn about updates to the new AI-powered banking page (QuickBooks Online)",
      "publisher": "Intuit Inc.",
      "published": "updated 8/7/2026",
      "retrieved_at": "2026-09-30T20:13:47+00:00",
      "sha256": "21b957ae11416a5c8c2f0b0ee5bf7c6a72e32eb4c69bcf6897d5985f0aa24b33",
      "supports": [
        "C14",
        "C38"
      ]
    },
    {
      "id": "REF::8",
      "url": "https://quickbooks.intuit.com/learn-support/en-us/help-article/reconciliation-reports/learn-reconcile-workflow-quickbooks/L8ZibUuVE_US_en_US",
      "title": "Learn the reconcile workflow in QuickBooks Online",
      "publisher": "Intuit Inc.",
      "published": "updated 8/24/2026",
      "retrieved_at": "2026-09-30T20:16:14+00:00",
      "sha256": "e15a16957a62712a050d9816305b35a601d71357e5c3d6f41eef4e03932cfea3",
      "supports": [
        "C15"
      ]
    },
    {
      "id": "REF::9",
      "url": "https://www.govinfo.gov/content/pkg/CFR-2025-title31-vol1/xml/CFR-2025-title31-vol1-sec10-34.xml",
      "title": "31 CFR 10.34, Standards with respect to tax returns and documents, affidavits and other papers",
      "publisher": "U.S. Government Publishing Office",
      "published": "CFR edition dated 2025-07-01",
      "retrieved_at": "2026-09-30T20:12:04+00:00",
      "sha256": "b511c7f89dc85df30ab89d1e16a48fc7947d1671b18ee2c7938c0215c5c675ab",
      "supports": [
        "C25",
        "C26"
      ]
    }
  ],
  "related": [
    {
      "question_id": "Q-0021",
      "slug": "how-a-bookkeeping-firm-can-standardize-document-intake-across-clients",
      "display_title": "How can a bookkeeping firm standardize document intake across many clients?"
    },
    {
      "question_id": "Q-2006",
      "slug": "how-a-bookkeeping-firm-can-automate-document-collection-across-clients",
      "display_title": "How can a bookkeeping firm automate document collection across many clients?"
    },
    {
      "question_id": "CG-P1B-FULL-082",
      "slug": "how-an-accountant-collects-documents-from-clients",
      "display_title": "How does an accountant collect documents from clients?"
    },
    {
      "question_id": "Q-1013",
      "slug": "a-monthly-document-workflow-a-bookkeeper-runs-for-each-client",
      "display_title": "What monthly document workflow should a bookkeeper run for each client?"
    },
    {
      "question_id": "CG-P1B-010",
      "slug": "what-a-bookkeepers-new-client-onboarding-checklist-should-include",
      "display_title": "What should a bookkeeper's new-client onboarding process and document checklist include?"
    }
  ],
  "review_class": "consequential",
  "review_class_trigger": "claim_level_review_required",
  "provenance": {
    "author_model": "claude-opus-5-5",
    "reviewer_model": "claude-opus-5-5",
    "review_verdict": "ACCEPT",
    "review_source": "closure",
    "review_verdict_on_sha256": "e7cfce2734eaaed4c12e72347054f9d55675640284a7444128ed15adddbf55eb",
    "editorial_disposition": "ACCEPT",
    "corrections": 1,
    "approved_by": null,
    "approved_at": null,
    "article_sha256": "e7cfce2734eaaed4c12e72347054f9d55675640284a7444128ed15adddbf55eb",
    "source_map_sha256": "4ea46b77945a92f2dbe701f3c26d68695bc0f9fc86a6b805d075ccdb475a89d8",
    "transform_sha256": "2faaec8988c094c1a5f3bedd8c745508d91ba97ef5c8da783d659926f1573d52"
  },
  "offer": "ask",
  "offer_id": null,
  "sample_target_id": null,
  "datePublished": "2026-10-01T20:06:59Z",
  "reviewed_at": "2026-10-01T20:06:59Z",
  "content_sha": "824af1ad595b97bc0e1660539273919bdd79b0eb76b0ceb22ec4eabd76bc38fb",
  "release": "2.14.0",
  "slug_provenance": "minted at first publication",
  "question_text": "How can a bookkeeper get clients to send documents on time?",
  "jsonld_types": [
    "Article"
  ],
  "related_question_ids": [
    "Q-0021",
    "Q-2006",
    "CG-P1B-FULL-082",
    "Q-1013",
    "CG-P1B-010"
  ],
  "aliases": [],
  "alias_provenance": []
}