Skip to content

From a document request to a filed document

How a request for documents reaches the client portal, how the client's upload is reviewed and how it ends up filed in documents with its retention.

Collecting documents through the app keeps a record of what was asked, what arrived and which version was used.

1. Ask

Issue a Document request pack on the engagement: a ready-made list of what that kind of work needs. Each item becomes a Document request in Requests. The client's portal contacts are told.

2. The client uploads

The client opens the Client portal with a Magic link, goes to Requests and adds a file for each item, or answers "not applicable" or "not available": see Send documents your CA team asked for. The client sees only requests and documents shared with them, never internal threads.

3. Review

Depending on the firm's setting, a clean upload is accepted straight away or waits for a member of staff to accept it. If something is wrong, Return the request with a reason the client can see; the request opens again and the earlier file stays filed. When the client says an item is not available, staff decide whether to waive it on the pack.

If the file is data the app can read, such as a Form 26AS or a register, it is passed to Imports as an Import batch. A rejected import does not reopen the request; the batch shows what to fix.

4. Filed in documents

The accepted file is filed in Documents under the client and engagement, as a Document version. It gets a Retention class, and a Legal hold applies while a proceeding for that period is open. Documents that show an Aadhaar number are kept encrypted and shown masked: see Masking.

5. Approval of the result

When the work is ready, send the draft back to the client for Client approval. The approval is tied to the exact version the client saw.

Last reviewed 27 October 2026