TPAR: getting the taxable payments annual report right
Which clients need to lodge a taxable payments annual report, what it captures, and how to collect contractor payment data through the year rather than in a rush.
The taxable payments annual report is easy to forget precisely because it only comes around once a year and only affects certain industries. But for clients who pay contractors, TPAR is a genuine obligation with its own deadline, and the data it needs is far easier to assemble across the year than in a single frantic effort after year end.
Who has to lodge
TPAR applies to businesses in specific industries that make payments to contractors. Building and construction is the best-known, but the requirement also extends to industries such as cleaning, courier and road freight, information technology, and security services. A client who has recently moved into one of these areas, or who has started using subcontractors, may have a new TPAR obligation they are not aware of.
The full list of affected industries and the reporting requirements are maintained by the ATO, and it is worth confirming each year whether a client's activities bring them into scope.
What the report captures
The report sets out the total payments made to each contractor during the year, along with their details such as name, address, and ABN. The ATO uses this to check that contractors are declaring their income. For the practice, the task is really a data-collection exercise: pulling together, per contractor, the total paid across the year.
- Contractor identity: name, address, and ABN.
- Total payments: the gross amount paid during the year.
- GST: the GST component where relevant.
Collect the data as you go
The difference between a smooth TPAR and a painful one is whether contractor payments were coded consistently through the year. If subcontractor payments are recorded against the right accounts and suppliers as they happen, the report is largely a matter of running a summary. If they are scattered or miscoded, the year-end clean-up can be substantial.
This is where good bookkeeping discipline pays off directly. Coding contractor payments correctly at the point of entry, and reviewing them periodically, means the annual report almost writes itself.
Track it as a recurring obligation
Because TPAR repeats every year for the same clients, it belongs on your recurring compliance calendar. In Finye you can flag your TPAR-liable clients and generate an annual job with the right due date, so the report is never the obligation that gets remembered a week before it is due. Having every TPAR client on one board also makes it easy to confirm scope each year. You can see how firms structure recurring compliance work in Finye's guides.
Confirm ABNs during the year
One of the most common TPAR headaches is a contractor whose ABN is missing or invalid, which is far easier to fix when the work is done than a year later when the report is due. Building an ABN check into supplier onboarding, and reviewing contractor records periodically, means the details are clean by the time the report is prepared. It also protects the client, since payments to a contractor who has not quoted a valid ABN can raise withholding questions of their own.
Review before lodging
A quick review before lodgement catches the common problems: contractors with missing ABNs, payments that belong to employees rather than contractors, and totals that look out of step with the prior year. Once the report is confirmed, lodge it and record the lodgement against the client. TPAR is not a difficult obligation, but it is an easy one to overlook. Confirm scope every year, keep the contractor coding clean as you go, and track it as recurring work, and it becomes a routine annual job rather than a scramble.