Accounting Firm Workflows: Requests, Workpapers and Review
Map client entities, reporting periods, document review and billing handoffs before adding accounting workflow software.

The practical answer
Start with one accounting handoff and an authoritative record for each fact. Separate client entities, reporting periods, received documents and reviewed work before automating the next step.
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.
For an accounting firm, a useful custom workflow often sits between client requests, workpaper preparation and review. Start by checking what your existing practice-management and accounting systems already support. Build only the missing handoff, with a clear record of the client entity and reporting period.
Example: make year-end work ready for review #
This is an illustrative design brief, not a delivered client result. It focuses on work readiness; it does not prepare accounts or make tax decisions.
- 1. Open an engagement periodResponsible: Job managerConfirm the client entity, reporting period, assigned team and current request list. Do not reuse last year’s completion state.
- 2. Request the missing informationResponsible: Client coordinatorSend a short list of outstanding items with a responsible contact. Record an assisted submission if the client cannot use the portal.
- 3. Check completenessResponsible: Assigned preparerCheck that a file belongs to the correct entity and period. A file uploaded is not automatically a requirement satisfied.
- 4. Submit for reviewResponsible: Preparer and reviewerRecord unresolved questions separately from completed work. Only the authorised reviewer changes the job to ready for the next stage.
- 5. Hand off billing informationResponsible: Job managerReview the agreed billing basis and approved work before passing it to the billing system. Retrying must not create duplicate charges.
Use entity and period as part of the identity #
| Record | Why it matters | Failure to test |
|---|---|---|
| Client person and client entity | One person may act for several companies or trusts | A person sees an entity they are no longer authorised to represent |
| Engagement and reporting period | The same document type recurs each year | Last year’s file is accepted as this year’s evidence |
| Request and review status | Received, incomplete and accepted are different states | An upload closes a request before staff check it |
| Staff assignment | Work may transfer between preparers and reviewers | Former team access remains after reassignment |
Choose a narrow first release #
Start with one service, such as year-end information collection, for a small trial group. Keep the accounting or workpaper platform authoritative for its own records. Define the identifiers and status changes the connection may exchange; avoid making a second editable copy of the entire client record.
Measure request follow-ups, incorrect-period uploads, rework and time until a job is ready for review. Include staff checking effort. Reduced chasing may create capacity; it does not automatically reduce payroll or increase billable revenue.
Keep professional review explicit #
If the workflow touches AML/CFT duties, use the firm’s assessed scope and current DIA reporting-entity guidance. A document checklist can support the process; it cannot determine that the firm has met every obligation.
Before launch, have the practice owner confirm access, retention, source systems, integration permissions and exception handling. Trial with synthetic data first, then an authorised representative set. The client document-request guide covers the customer-facing experience in more detail.
A useful companion: Workflow Mapping Worksheet.
Other articles worth reading

Adviser Portals: Application Documents and Handoffs

Custom Software for NZ Law Firms: Useful Workflows Without Pretending Software Equals Compliance

