“Sent” and “complete” are different states
An accounting team may ask for bank statements, receipts, payroll information, identity documents, and signed forms several times a year. Clients reply across multiple threads, rename files unpredictably, or believe that one upload completed the whole request. Staff then spend time comparing inboxes with private checklists.
The underlying problem is shared visibility. The firm knows the full set of documents required, while the client sees individual requests arriving over time. Neither side has one reliable picture of what is missing, under review, or rejected for a specific reason.
A checklist can be the product
A focused first version could let the firm start from a reusable request template, set a due date, and give the client one secure page. Every item carries a plain-language description and a state: requested, submitted, accepted, or needs replacement. Staff can add a short review note instead of starting another disconnected email thread.
- Show clients only their own requests and files.
- Keep due dates and reminder history visible to staff.
- Explain why a replacement is needed without exposing internal notes.
Security comes before convenience
A real implementation needs decisions about storage location, retention, access logging, deletion, and the sensitivity of each document type. A first version should avoid collecting files that can remain in an approved existing system. It can also begin as a request-and-status layer that links to established secure storage. The measure of usefulness is simple: clients know what remains, and staff can see the same state without rebuilding it manually.
Accounting firms
This guide describes a possible starting point, not a prebuilt product. A real scope would follow a discussion of your current process.