Practice workspace / Documents and chasing

Request documents and follow up on missing records

Staff request named documents and reviewers check uploads, while clients see what they still need to send.

S SecureWire Workflow illustration
Example workflow

Documents and chasing

Example
Example clientExample steps
Request documentsIn progress
JL
Client uploads in the portalNot started
SK
Accept or reject with a reasonNot started
AM
Client replaces rejected filesNot started
JL
Request documents01 / 04
Illustrative workflow and sample data. Register interest to discuss your requirements.
How this supports your work

Reviewers see which uploads need checking and staff can leave scheduled reminders to chase missing documents instead of sending each follow-up by hand.

Staff document requests showing uploaded and accepted records
Shown with an invented demo practice.

How it works

  1. Request documents
  2. Client uploads in the portal
  3. Accept or reject with a reason
  4. Client replaces rejected files
01

Review each upload

Requests move from Requested to Uploaded to Accepted or Rejected. A rejection includes a reason and opens a fresh request. Work, Review lists waiting uploads oldest first.

Client uploads in the portal
02

Set the chasing schedule

Reminders go out on days 3, 7 and 10 by default. On day 14 chasing stops and the case passes to a named person at the practice. Change or pause the schedule per template or engagement.

Accept or reject with a reason
03

Use secure links

Clients upload against a request through the portal. Secure links expire, by default within 30 days. Staff can upload on a client’s behalf, and previews are recorded in History.

Client replaces rejected files
Prepare for the launch

Tell us what your team needs from accounting software

Register interest in SecureWire and ask us about the modules you need.