Why does your accountant keep asking for the same documents?

Compare the original request, what you supplied, and the new question before sending another copy. The accountant may be missing the file, unable to open it, working from an older version, or asking for information that the document does not contain. Each problem needs a different response.

Start with the entity, period, account, and document type. A bank transaction confirms that money moved; it may not explain the underlying purchase. A supplier invoice may identify the charge but leave an important business question unanswered. A repeated-looking request can therefore be a legitimate follow-up that was poorly explained.

AICPA Member Insurance Programs' guidance on incomplete information emphasizes identifying the missing information and its consequence precisely. Ask the provider to apply that clarity to the request: what part of the previous response was received, and what exactly is still needed?

Choose a recent request that both teams recognize. Reconstruct the sequence using the actual messages and file references. Keep the discussion factual: the purpose is to find where the information stopped being usable, not to decide which team is generally bad at communication.

The following is an illustrative request log. It shows why uploaded and resolved need separate statuses. A short record like this can prevent a document from being requested again simply because the remaining question has not been distinguished from the original request.

If the correct file was supplied but cannot be found, agree one authorized location and a consistent reference. Avoid copying sensitive documents across several inboxes just to prove they were sent. Give the recipient a secure link and check that the intended account can open it.

If the file changes, identify the version used for accounting. Microsoft documents version history for files stored in OneDrive or SharePoint Online. Where your chosen system supports an equivalent feature, use it to investigate which version was available; do not assume that a filename containing final proves the contents never changed.

Keep approvals tied to a recognizable version. If a manager approves a schedule and someone then revises the numbers, tell the accountant whether the approval still applies. A file that is easy to access can still be unsuitable evidence if nobody knows which contents were authorized.

Ask the provider to state the unresolved question in business language. Instead of requesting more support, it might ask whether equipment was ready for use, whether a customer accepted a revised amount, or which entity signed a contract. That helps the coordinator find the person who knows the answer.

Include why the answer matters and when it is needed. The company can prioritize a request more sensibly when it knows the affected report or decision. The explanation should remain proportionate and avoid demanding that a non-accountant determine the technical treatment.

If the business cannot establish the fact, say so. Ask the accountant to explain the available next steps and limitations. Repeatedly uploading the same incomplete document does not make an unsupported assumption more reliable.

Repeated requests can reveal that a new preparer did not receive the prior team's context. Ask where completed responses and standing decisions are recorded. A new employee should be able to find an accepted explanation without relying on the company to repeat every conversation.

Check whether different service teams have legitimate but overlapping needs. Tax, bookkeeping, and an external audit may require the same document for different work. Where sharing is authorized, coordinate retrieval and explain the separate purpose. Do not promise that one team's acceptance automatically satisfies another professional engagement.

If requests arrive by email, portal, and chat, nominate the record that carries the status. Other channels can alert people, but they should point back to the same item. Otherwise a resolved email question may remain overdue in the provider's task system.

For the next reporting cycle, classify repeat requests by cause: wrong period, access problem, changed version, missing fact, duplicate channel, or lost handoff. Track the avoidable repeats separately from valid follow-up questions. A lower raw request count is not a success if important questions are being suppressed.

Review the most common cause with the provider and assign one corrective action. That might be an access fix, a clearer request format, or a better staff handoff. Verify the change through an actual later request.

The useful outcome is that both sides know what was received, what remains uncertain, and what closes the item. Once those states are visible, repeated requests become specific problems that can be resolved instead of a recurring argument.