Sign-off Pipeline: Partner, Client, Filed

The three steps

For services that require sign-off, work cannot be delivered, filed or closed until two approvals are in place, in this order: the partner approves internally, then the client approves through a secure link, and only then can the engagement be marked filed. The engagement page shows a tracker with the three steps Partner, Client and Filed, with the current message and the next button. See the Engagements article for the wider lifecycle.

Turn sign-off on for a service

Go to Practice Tools → Services and tick the Sign-off box for the service. Engagements of that service then follow the pipeline. If you try to submit an engagement whose service does not require sign-off you will see 'This service doesn't require sign-off. Turn it on under Services if you want it.'

Step 1: partner approval

• On the engagement, click 'Submit for partner approval'. The engagement moves to Review and the reviewer is notified.
• A user who can approve opens the engagement and clicks Approve ('Approve for filing', with an optional note) or Reject ('Reject sign-off', with a required reason).
• A rejection sends the engagement back to In progress and tells the preparer. Fix the work and submit again.
• Who can approve: admins by default, plus any role your organisation has granted the Approve permission for Practice.

Step 2: client approval

• After partner approval, click 'Send for client approval'.
• Optionally attach a PDF to review (upload one or paste a link) and add a message. If you attach nothing, a cover sheet is generated for the client to review.
• Click send to email and WhatsApp the client where details are on file, or 'Get link only' to copy or share the link yourself.
• The client opens the link (no login needed), reads the page 'Please approve before filing', and clicks Approve or 'Raise a query'. A query needs a note saying what must change.
• The link expires after a limited time and stops working once the client has decided. Use 'Resend link' (or 'Re-send for client approval' after a query) to issue a new one.
• The client's decision is recorded with a timestamp and their IP address in the engagement's audit trail.

Step 3: mark as filed

Once the client has approved, click 'Mark as filed'. Enter the Acknowledgement / SRN / challan no. if you have it (optional) and confirm. The engagement moves to Delivered, the linked compliance deadline is completed, and the client's status is updated. For Income Tax services a high-priority task 'E-verify return' is created, due 30 days after filing. You can then close the engagement.

The SIGNOFF_REQUIRED conflict

If you try to set an engagement to Delivered or Closed, or use Close, before the client has approved, the request is refused with a 409 conflict and the code SIGNOFF_REQUIRED. The message reads: 'Client approval is required before this can be marked delivered/filed or closed. Get partner sign-off, then send it for client approval.' Marking filed gives a similar message, 'Client approval is required before filing.' Cancelling is exempt. Related messages you may see: 'Get partner/admin sign-off before sending to the client.' if you send to the client too early.

Fixing a stuck engagement

• Read the tracker: it tells you which step is outstanding.
• Partner step pending: ask an approver to open the engagement and decide.
• Client step pending: click 'Resend link', or if the client raised a query, fix the work and send for approval again.