How to run BAS season as a Kanban pipeline

Most agents I talk to run BAS quarter the same way. There is a list of clients somewhere (spreadsheet, accounting software dashboard, sticky notes). There is a vague idea of who is ahead and who is behind. The “oh god which BAS is overdue” moment hits in the third week and the rest of the quarter is reactive.

Reactive isn’t the same as inefficient. You can lodge twenty BAS reactively and still come in under the deadline. But it costs you cycle time you can’t see. The fix is to make the work visible.

Why kanban for BAS

BAS is a workflow with discrete states. A given client’s BAS for a given quarter is in exactly one of these states at any moment:

1. Backlog: quarter exists, no work started.
2. In progress: statements imported, categorisation underway.
3. Review: figures computed, awaiting agent review.
4. Approved: agent has signed off, client email sent, awaiting lodgement.
5. Lodged: submitted to the ATO.

Five states. Each BAS moves through them once per quarter. That is exactly the shape kanban was designed for. The reason most agents don’t use it is they have never seen it set up for tax work; kanban gets associated with software teams, not professional practices.

How the columns work in practice

Backlog to In progress

A BAS enters In progress the moment a statement gets uploaded for that quarter. No manual “mark started” step. The system knows because the data is there. If a quarter has no statement, the card stays in Backlog and the “overdue” counter starts ticking when the due date approaches.

In progress to Review

Review starts when categorisation is complete: every transaction has a category, no Suspense rows, the GST treatments make sense. The pipeline card shows the figures (1A, 1B, Net) computed from the categorised data. You can scan a column of cards and see what each client owes the ATO this quarter, in order, without opening anything.

Review to Approved

Approval is the agent’s signature. After this, the BAS is locked. No more edits to the categorised transactions for that quarter. This is where the “send the cover email” prompt fires. You move to Approved, the system asks if you would like to draft the email to the client, you say yes, you edit and send.

Approved to Lodged

Lodgement happens via the practitioner portal (or SBR2 when that ships). You come back to Jazhi, mark Lodged, the date stamps automatically, and the card moves out of the active queue.

What you watch on the board

• Overdue cards: anything in In progress or Review past the due date. Bright red. These are the fires.
• Cards in Review for more than five business days. Partial fires. The agent (you) is the bottleneck.
• Cards in Approved waiting on lodgement. The cheap wins. Five clicks each, knock them out in a batch.
• Backlog count: the work you have not started. If this is non-zero in week three, something is wrong.

What goes wrong if you don’t

I ran my practice on a spreadsheet for years. The two failure modes:

1. Lost cards. A client’s quarter never gets started. Three weeks before the due date you discover it because their accountant emails asking. Too late to do well.
2. Bottleneck blindness. You think you are behind on data import. You are actually behind on review. Three BAS have been waiting on you to look at them for a week. Without the pipeline view, you cannot tell which is true.

How Jazhi shows this

The Dashboard in Jazhi is exactly this pipeline. Five columns plus Lodged below. Cards drag manually only if you need to override; otherwise they advance themselves based on the underlying data state. Filter pills at the top show only Overdue, only Due This Week, only Due This Month. Performance metrics show your average cycle time and your bottleneck stage so you know where to focus.

If you are running BAS season any other way, give the kanban shape a quarter. Worst case you go back to spreadsheets and learnt a thing. Best case you get one day a quarter back.