Taxable Payments Reporting (TPAR)

The Taxable Payments Annual Report (TPAR) is an ATO reporting obligation requiring certain businesses to report the total payments made to contractors and subcontractors during the financial year. The report is lodged annually by 28 August following the end of the financial year and includes the contractor's name, ABN, address, and total gross amount paid (including GST). The ATO uses TPAR data to identify contractors who have not lodged tax returns or have underreported income -- it is a cross-referencing tool that compares what businesses say they paid to contractors against what contractors report as income.

TPAR was initially introduced for the building and construction industry and has since been extended to cover cleaning services, courier services, road freight services, IT services, security, investigation and surveillance services, and mixed businesses where any of these services account for 10 percent or more of total business income. The extension of TPAR coverage is ongoing; businesses should check the current ATO guidance each year to confirm whether they are within scope rather than relying on historic coverage rules.

What AP teams need to capture for TPAR compliance

TPAR compliance is primarily an AP data capture problem. The report requires contractor ABN, name, address, and total payments (including GST, with the GST component disclosed separately). If this information is not captured consistently at the transaction level through the AP process, compiling the report at financial year-end requires manual extraction, cross-referencing, and cleanup that is time-consuming and error-prone.

Best practice is to capture TPAR-relevant supplier information at onboarding (ABN, entity name, address) and to code contractor invoices in a way that allows them to be filtered and totalled for TPAR reporting. Some businesses use a specific supplier category or expense code for TPAR-reportable payments; others rely on their AP or accounting system's built-in TPAR reporting feature (Xero and MYOB both have TPAR report generators that pull from supplier transaction data). The system-generated report is only as accurate as the underlying data -- missing ABNs, incorrect supplier names, and miscoded contractor invoices all produce TPAR errors that will require manual correction.

Penalties for TPAR non-lodgement and errors

Failure to lodge TPAR by the due date results in an administrative penalty of AU$222 for each 28-day period (or part thereof) that the report is outstanding, capped at AU$1,110 for small businesses and AU$5,550 for large businesses. Incorrect or incomplete reports that significantly misstate contractor payments can attract ATO review and, in cases of deliberate misreporting, stronger penalties. The ATO has made it clear that TPAR compliance is an enforcement priority and uses data matching to identify businesses that are within scope but have not lodged.

For industrial businesses -- construction, manufacturing, mining -- with significant contractor spend, TPAR is not a minor compliance obligation. A mining services business paying AU$5 million annually to contractors across 50 ABNs has a non-trivial data management task. Ensuring the AP system captures and tags all TPAR-reportable transactions throughout the year, rather than attempting to reconstruct the data in August, is the operationally sensible approach.