Retire a closed account from recurring document requests

Retire the recurring request, not the history

Retire the request with its closure evidence so the next cycle starts with an accurate list.

A complete client folder still leaves someone turning supplier invoices into spreadsheet rows. That is the step ParseMill handles: upload invoice PDFs, review extracted details and line items beside the source, then download Excel. Keep document requests and engagement tracking in your existing process.

Ask the reviewer responsible for the engagement to define the final evidence needed. This guide concerns collection control; it does not decide how to treat remaining balances or whether any particular document is professionally sufficient.

Separate final evidence from future requests

Create a closure note with entity, account reference, reported closure date, supporting source, final-period coverage and reviewer. Link any remaining exception to its own task. Record the first future period for which the recurring statement request should no longer be generated.

For US firms, TaxDome: Document checklists permits changes to sent checklist items. TaxDome: Request list distinguishes request progress states. Those controls can support administration, but stopping a recurrence and resolving a current request are different decisions. Check both places in your own process. A future reminder can continue even when a current item has been archived, depending on how the next cycle is created.

Work through a closing account

Synthetic example: Willow Trading closes savings account S3 on September 12. September intake already includes an ordinary monthly requirement.

This creates one clear final package without concealing the balance question. The unresolved question should remain visible even if the statement itself is accepted. Conversely, keeping that question open should not cause another generic monthly statement request to be sent.

Test awkward cases before stopping follow-up

An account reported as closed may still have a later correction, fee or final communication. Record what the firm has actually confirmed, and keep a route for later evidence to reopen the relevant review. Do not assume that absence of activity proves closure. A dormant account and a formally closed account may require different collection decisions.

If the client withdraws or corrects the closure report, update the effective-date record and tell whoever maintains recurring requests. Preserve the earlier statement as a superseded report rather than rewriting it as if the firm had always known the correct position.

Verify the next generated checklist

Inspect the next cycle before sending it. Confirm that S3 is absent from ordinary recurring requests, that final-period evidence remains accessible, and that the separate unresolved question has an owner and review date. Search both manual reminder lists and any native portal scheduling settings used by the team.

A useful acceptance test is simple: a colleague should explain why the account is no longer requested while still finding its last accepted evidence and any remaining decision. the related workflow guide provides the overall collection method. Record closure-related duplicate requests in the workflow audit checklist to see whether a clearer change process is working.