Client Document Portals for Accountants and Advisers
Design clear client requests, delegated access, controlled uploads and a review process that clients can understand.

The practical answer
A useful client request shows the correct entity and period, what is needed, review status and a help route. Staff review a submission before marking the request complete.
Discuss your business technology requirements, users and existing tools so we can define a useful website or web app scope. Discuss your website or app.
A professional-services portal should make one question easy for the client: what do you need from me, and what happens after I provide it? Begin with document requests and progress, rather than reproducing the firm’s internal system in a client interface.
Design the request, not just the upload button #
The example below is fictional. It illustrates a request card for a client who represents more than one entity. No financial or identity documents are included.
| Visible item | Example | Purpose |
|---|---|---|
| Entity and period | Example Trading Ltd — year ended 31 March 2026 | Prevents a document going against the wrong engagement |
| What is needed | The statement for the account already identified in your secure request | Describes the task without exposing unnecessary details in email |
| Status | Received — staff review pending | Does not imply an upload has been accepted |
| Question or alternative route | Ask the assigned team for help | Lets the client resolve uncertainty without guessing |
| Next step | Your coordinator will check the document and update this request | Explains what happens after submission without an unagreed response promise |
Separate the person from their authority #
Do not assume that knowing an email address proves someone may see every linked company, trust or household record. Establish who can represent each entity, what delegated access permits and how changes are reviewed. A delegated user may need to upload a file without seeing all correspondence.
Test a person with two entities, a removed representative, an expired invitation and an attempted download from another client’s request. Include files and exports, not just the visible dashboard.
Keep private detail out of notifications #
A reminder can say that a request needs attention and link to the approved sign-in route. It need not attach sensitive documents or expose their contents in an email subject. Record notification preferences and provide an assisted route for clients unable to use the portal.
Map where personal information comes from. Information provided directly and information received through a referral raise different notice questions; the Privacy Commissioner’s IPP3A guidance explains indirect collection. Have the firm’s privacy owner determine the requirements for the actual flow.
Trial the whole journey #
- A client accepts an invitation and finds the correct engagement.
- They submit a file and can see that it awaits review.
- Staff reject an incorrect file with a useful explanation.
- The client replaces it without losing the history.
- Staff confirm completion and the client sees the next step.
Measure task completion, assistance needed, incorrect submissions and repeated status emails. Do not assume that a new portal reduces communication: an unclear request can simply move the same confusion to another screen.
Keep the first release focused #
Identity, entity access, a clear request list, controlled upload, review status and help are a coherent first version. Messaging, payments, document signing or advice delivery should have their own requirements. The accounting workflow guide and adviser application guide cover distinct staff-side processes.
A useful companion: Workflow Mapping Worksheet.
Other articles worth reading

What to Include in a First Client Portal

Do You Need a Client Portal? A Practical NZ Checklist

