The Taxable Payments Annual Report — TPAR — is a report that certain Australian businesses lodge with the ATO each year. It lists every contractor your business paid for services during the financial year, along with their ABN, the gross amount paid, and the GST included in those payments.
The ATO uses TPAR data to cross-match what businesses report paying contractors against what those contractors declare as income. It is a data matching exercise, and if the numbers do not line up, the ATO follows up — with the contractor, with your business, or both.
Who needs to lodge a TPAR?
You need to lodge a TPAR if your business makes payments to contractors for services in any of these industries:
- Building and construction — including trades, civil works, and project management
- Cleaning
- Courier and delivery
- Road freight
- Information technology (IT)
- Security, investigation, and surveillance
It does not matter whether your business is in one of those industries itself. What matters is the nature of the services you are paying for. A property management company that pays a plumber to fix a pipe at a rental property is making a payment for building and construction services — and needs to report it.
Government entities also need to lodge a TPAR for payments to contractors across all industries, not just the ones listed above.
What the TPAR covers
For each contractor you paid during the financial year (1 July to 30 June), you need to report:
| Field | What to include |
|---|---|
| ABN | The contractor’s Australian Business Number. If they did not provide one, you report that — and you may have been required to withhold from the payment. |
| Name | The contractor’s business or trading name as it appears on their invoices. |
| Address | Their business address. |
| Gross amount paid | The total of all payments made during the year, including GST. |
| GST included | The GST component of those payments. |
| Tax withheld | Any amounts withheld where no ABN was quoted. |
You do not need to report payments for materials only — TPAR covers payments for services, or for a mix of labour and materials where the labour component is not separately identified.
When is the TPAR due?
The TPAR is due by 28 August each year, covering the financial year that ended on 30 June.
If you lodge through a registered tax agent, you may be eligible for an extended lodgement date. Check with your agent or the ATO for the current schedule.
How to lodge
There are three main ways to lodge your TPAR:
-
Through your accounting software — Both Xero and MYOB have TPAR reporting built in. The software generates the report from your contractor payment records and lets you lodge directly with the ATO via Standard Business Reporting (SBR).
-
Through your tax agent or BAS agent — Your accountant or bookkeeper can prepare and lodge on your behalf.
-
Through ATO online services — You can lodge via the ATO’s Business Portal or through myGov if you are a sole trader.
Where TPAR goes wrong
The lodgement itself is straightforward — Xero and MYOB both generate the report in a few clicks. The problem is almost always the data that goes into it.
Missing ABNs
If a contractor did not provide their ABN when they invoiced you, you were required to withhold 47% from the payment (the no-ABN withholding rate). Most businesses do not actually withhold — they pay the invoice, move on, and then scramble to collect ABNs in August when the TPAR is due.
Missing ABNs create two problems: you cannot accurately report the payment, and you may have a withholding obligation you did not meet. The ATO takes no-ABN withholding seriously — it is one of the most common TPAR compliance issues.
Incorrect GST status
If you recorded a contractor as GST-registered when they are not (or vice versa), the GST component in your TPAR will not match the contractor’s own BAS reporting. The ATO’s data matching picks this up, and it can trigger a review of both parties.
The fix is not to check GST registration once a year before lodgement — it is to validate it when you first receive an invoice from a contractor.
Inconsistent contractor records
Over 12 months, the same contractor might appear in your records under slightly different names, different ABNs (if they operate through multiple entities), or different addresses. When Xero or MYOB generates the TPAR, it may split one contractor into multiple entries or miss payments because the records do not match.
Payments recorded against the wrong contact
If an invoice from a subcontractor was accidentally coded to a different supplier, the payment will not appear in the TPAR under the correct contractor — or will not appear at all. This is especially common when invoices are manually entered and supplier names are selected from a dropdown.
How Pulsify prevents TPAR pain
Pulsify does not generate or lodge the TPAR — your accounting software handles that. What Pulsify does is make sure the contractor data flowing into Xero or MYOB is clean from the start, so when August arrives, there is nothing to chase.
ABN validation at the point of invoice processing
Every contractor invoice processed through Pulsify is checked against the Australian Business Register (ABR). The contractor’s ABN is validated automatically — confirming it exists, is active, and matches the entity name on the invoice. If the ABN is invalid, cancelled, or does not match, the invoice is flagged before it reaches your accounting software.
This means you never post a bill to Xero or MYOB with a missing or incorrect ABN. When the TPAR report is generated, every contractor has a validated ABN attached to their payment records.
GST registration status verified against the ABR
As part of the same ABR lookup, Pulsify checks whether the contractor is registered for GST. If an invoice includes GST but the contractor is not GST-registered (or vice versa), the discrepancy is flagged during the approval process.
This catches the mismatches that otherwise surface as ATO queries after TPAR lodgement — mismatches between the GST you reported paying a contractor and the GST they reported collecting.
Consistent contractor records
Because Pulsify matches incoming invoices to existing supplier records using ABN and entity name, the same contractor does not end up as three different entries in your ledger. Payments are consolidated under the correct contact, so the TPAR report in Xero or MYOB is accurate without manual cleanup.
The result at TPAR time
When your bookkeeper or accountant runs the TPAR report in Xero or MYOB, the data is already correct:
- Every contractor has a validated ABN
- GST status matches ATO records
- Payments are attributed to the right contacts
- No withholding gaps from missing ABNs
There is no August scramble. No spreadsheets of missing ABNs to chase. No line-by-line reconciliation of contractor records. The TPAR generates cleanly because the data was validated at the point each invoice was processed — not 12 months after the fact.
TPAR checklist
Use this as a quick reference before lodgement:
- Confirm your business is required to lodge (payments for services in a covered industry)
- Review contractor records for missing or invalid ABNs
- Verify GST registration status for each contractor
- Check for duplicate or inconsistent contractor entries
- Confirm gross payment amounts include GST
- Reconcile withheld amounts where no ABN was quoted
- Generate the TPAR report in Xero or MYOB
- Review the report for obvious gaps or anomalies
- Lodge by 28 August
Get started
If you are processing contractor invoices manually and TPAR season is a recurring headache, start a free 30-day trial and see what validated contractor data looks like from day one. Or book a demo and we will walk through how Pulsify handles ABN validation, GST verification, and contractor record management for businesses in construction, cleaning, IT, and other TPAR-reportable industries.