Sending a BAS for sign-off

/practice/bas shows every BAS approval across your practice grouped by status: awaiting client sign-off, approved (ready to lodge), lodged, rejected, drafts.

The send flow

Click + Send for sign-off at the top.

1. Pick a client. Active clients only.
2. Pick a BAS period. The dropdown shows existing BAS periods on that client's account (with payable / refund label). If the client hasn't created any periods yet, you'll see a "+ Create a new BAS draft for this client" toggle — fill in period start, end, optional label, click Create draft. The new draft is auto-selected.
3. Optional declaration text. Empty falls back to your saved practice default (Settings → Branding → "Default BAS declaration text") or the built-in TPB declaration if you haven't set one.
4. Click Send. Client gets a branded email link, reviews the figures + declaration in-app, signs (timestamp + IP captured), status flips to approved.

Marking as lodged

After you've lodged via ATO Online Services for Agents, click Mark lodged on the approved BAS row. Optionally enter the ATO receipt reference — surfaces under the row for the audit trail.

Frank does not lodge to the ATO directly. Lodgement happens via Online Services for Agents; the "Lodged" marker is a record-keeping flag.

TASA / TPB compliance

Every client sign-off is recorded with timestamp + IP for the 5-year retention requirement (TASA s30-35). The client_signoff_events table is append-only with UPDATE/DELETE blocked at the trigger level — if a signature is ever disputed, you can replay the immutable event log.

Drafts vs sent

A draft BAS is one that exists on the client's account but hasn't been sent yet. Sending creates the bas_drafts row and emits a sent event into client_signoffs. From there it transitions through sent_for_review → approved → lodged (or rejected).