Every Australian accounting firm has a client who nearly missed TPAR. The taxable payments annual report lands on 28 August, a full month after the BAS deadline everyone is watching, and it applies to a subset of clients most staff have to stop and think about: building and construction, cleaning, couriers, road freight, IT and security services. It sits outside the quarterly rhythm, which is exactly why it slips.
The fix is not another wall chart. It is treating the whole ATO lodgement calendar as one automation problem: a single scheduled pulse that knows every client, every obligation and every date, instead of a dozen separate reminders living in separate heads.
The season's deadline stack
14 July: STP finalisation declarations for employer clients
28 July: Q4 BAS and June-quarter super guarantee contributions
28 August: TPAR for clients in the reportable industries
31 October: self-lodger returns, and the agent lodgement program stretching beyond
Between those markers sit the irregulars: Div 293 assessments arriving for high-income clients, instalment notices, payment plans with their own due dates. None is individually hard. Collectively they are a memory problem, and firms solve memory problems with staff time worth $160 an hour or more.
Who is actually TPAR-caught
The first automation is classification. Claude Cowork, reading the client list and each Xero file, scans the ledger for contractor and subcontractor payments in the reportable service categories and produces two lists: clients clearly caught, and edge cases where the mixed-services rules need an accountant's call. For the caught clients it assembles the reportable payee list from the ledger, ABNs and addresses included, and flags the payees with missing details while there is still time to chase them. What used to be an August scramble becomes a July checklist item.
What the contractor scan looks like in practice
Take a suburban firm with 60 clients in the trades. The agent reads each ledger for the year, isolates payments coded to subcontractors, contract labour and the accounts that behave like them even when coded creatively, then cross-checks payee ABNs against what is already on file. The output for each client is a draft TPAR payee schedule plus a short exceptions list: two payees with no ABN recorded, one with an address missing, one supplier who might be materials rather than services. A bookkeeper resolves the exceptions in minutes per client because the finding work is done. Multiply by 60 clients at roughly an hour saved each and the scan returns about $9,600 of staff time at a $160 rate, in a single deadline cycle, for one obligation type.
The cost of doing it by memory
The manual version fails quietly. A client who started using subcontractors mid-year never gets added to the TPAR list. A Div 293 assessment sits in a client's myGov inbox until the payment deadline passes and the general interest charge starts. A payment plan instalment bounces and nobody notices until the ATO letter arrives. Each miss costs an apology, unbillable remediation time and a small dent in the relationship, and none of them happens because anyone was careless. They happen because the calendar lives in too many places. Centralising it in software the firm already runs is the cheapest insurance available.
Div 293 and the letters nobody enjoys writing
Div 293 assessments arrive on their own schedule whenever a client's combined income and concessional contributions pass the $250,000 threshold, and every one triggers the same conversation: what is this, why me, do I pay from super or pocket. Claude drafts the plain-English explainer with the client's actual numbers and the election options laid out, ready for the accountant to review and send. Ten of those letters a season is half a day of senior time recovered from a task that is genuinely identical every time.
The morning deadline pulse
The piece that ties it together is a scheduled task that runs before the office opens:
Every obligation due in the next 21 days, by client, with preparation status from the folder
Anything blocked on client documents, with the chase email already drafted
New ATO correspondence spotted in the inbox, sorted by urgency
The one-line all-clear when nothing needs attention, which is the line partners learn to trust
The pulse does not lodge anything and does not talk to the ATO. It ends the version of practice management where the TPAR list lives in one manager's memory and goes on leave when they do.
Boundaries and the payoff
Lodgement stays with the registered agent, always. What the automation removes is the watching, the list-building and the identical letters. Firms running a deadline pulse report the quiet benefit is August: TPAR arrives already assembled, and the month stops being the sting in the season's tail. A fixed-fee Claude Cowork setup is $3,500 and the deadline pulse is one of the first workflows configured. Book a brainstorm call and bring your TPAR client list; it is the fastest demonstration there is.
