Back to the JournalATO & compliance

TPAR Is Due 28 August: The Contractor Data Problem Nobody Fixes Until It's Too Late

The ATO has been explicit that it is firm on the contractor reporting deadline. The lodgement itself takes minutes — assembling clean contractor data from a year of coded transactions is what takes the fortnight.

MW
Marcus Webb
Senior bookkeeper · 06 Aug 20267 min read
Last reviewed against current ATO guidance: 06 Aug 2026. Always confirm current thresholds, rates, and dates at ato.gov.au.

The taxable payments annual report is due on 28 August. The ATO has published a media release stating it is firm on the deadline for contractor reporting, which is about as clear a signal as the ATO gives.

If you have TPAR clients, you have roughly three weeks. The lodgement is the easy part. This article is about the part that actually consumes the time.

Who has to lodge

Per the ATO's guidance on working out if you need to lodge a TPAR, businesses must report if they paid contractors for:

  • building and construction services
  • cleaning services
  • courier and road freight services
  • information technology services
  • security, investigation or surveillance services

Government entities have separate and broader obligations, including reporting grants paid to entities with an ABN.

Two practical traps:

Mixed businesses. A business does not have to be in one of those industries to have an obligation. A retailer that paid couriers, or a manufacturer that engaged cleaners, can be caught depending on the proportion of income derived from those services. The test is about the payments, not the ANZSIC code on the ABN.

Paper is gone. Paper TPAR lodgments have not been accepted since 28 August 2025. If a client's process still assumes a paper form, that process is already broken.

The new pre-fill changes the stakes

The ATO introduced a new TPAR pre-fill for tax time 2026. Data reported about contractors now flows into the contractors' own returns.

Think about what that means in both directions:

  • When your client is the payer, the figures you lodge become pre-filled data in someone else's tax return. Overstating a payment creates a discrepancy in a third party's affairs.
  • When your client is the contractor, amounts reported by their customers appear pre-filled. If the client's own books say something different, that gap is now visible to the ATO before anyone has to go looking.

TPAR has quietly graduated from a compliance chore into a data-matching input. Accuracy matters more than it did two years ago.

The real bottleneck

Here is what actually happens in practice during the last week of August.

The lodgement form wants, per contractor: ABN, name, address, gross amount paid for the year including GST, and total GST. None of that is difficult to submit.

The difficulty is that the source data lives in twelve months of coded bank transactions, and the questions you have to answer are:

  1. Which payments were to contractors as opposed to suppliers of goods, employees, or reimbursements?
  2. Which contractors are the same contractor? "J Smith Plumbing", "JSMITH PLUMBING PL", "Smith Plumbing Pty Ltd" and a direct debit reference number are frequently four labels for one ABN.
  3. What is the ABN for each of them, and is it still valid?
  4. Was the payment for a reportable service, or for materials, which are treated differently?

Every one of those is a data-quality question about how the year was coded — decided months ago, usually under time pressure, by whoever was doing the coding that week.

Why bank descriptions defeat manual grouping

The single most reliable way to lose a day in late August is trying to group contractor payments by eyeballing bank descriptions.

Australian bank feeds prefix and suffix descriptions aggressively. The same contractor paid four times can appear as:

EFTPOS SMITH PLUMBING 4471
OSKO PAYMENT J SMITH PLUMBING
INTERNET BPAY SMITHPLUMB 88213
DIRECT DEBIT SMITH PLUMBING PL INV4471

Sorting a spreadsheet alphabetically does not group those. Neither does a naive text match. You end up with one contractor split across four rows, three of which fall under any sensible materiality threshold and get missed entirely.

The fix is to normalise the vendor — strip the channel prefixes (EFTPOS, OSKO, BPAY, INTERNET, DIRECT DEBIT) and the trailing reference IDs — so that all four resolve to a single vendor before you total anything. Doing that by hand across a construction client with 60 subcontractors is a full day's work. Doing it consistently across a portfolio is not realistic without tooling.

A three-week plan

Week 1 — identify and scope. List every client with a possible obligation, including the mixed-business edge cases. Do not rely on last year's list; obligations start when payment patterns change.

Week 2 — assemble and validate. For each client, pull the year's payments grouped by normalised vendor. Validate every ABN — the ABN Lookup service will confirm whether an ABN is current and whether the entity is registered for GST. An ABN that was cancelled mid-year is a conversation to have now, not in September. Where no valid ABN was quoted, check whether no-ABN withholding should have applied.

Week 3 — review and lodge. Give the client the contractor list before you lodge. They will spot the one that is actually a supplier of materials, and the one that stopped trading in November. Lodge with days to spare, not hours.

How ReconLink handles this

We built TPAR generation because this specific job — reconstructing clean contractor totals from a year of coded transactions — was the one our practice users kept describing as the worst week of their August.

ReconLink normalises the vendor on every transaction as it is imported, so the four descriptions above resolve to one vendor key automatically. Contractor payments are grouped by that key rather than by raw bank text, totals are struck for the financial year, and the report is generated with ABNs attached. Optional ABN validation runs against the Australian Business Register.

It does not remove the judgement calls — you still decide what is a reportable service and what is materials. It removes the manual grouping and the arithmetic, which is where the fortnight goes.

Frequently asked questions

When is the TPAR due? 28 August each year. The ATO has publicly stated it is firm on this deadline.

Which businesses have to lodge a TPAR? Businesses paying contractors for building and construction, cleaning, courier and road freight, information technology, or security, investigation and surveillance services. Government entities have broader reporting obligations including grants paid to ABN holders.

Can I still lodge a paper TPAR? No. Paper TPAR lodgments have not been accepted since 28 August 2025.

What if my client is not in one of the listed industries? They may still have an obligation. The test relates to payments made for the relevant services and the proportion of income derived from them, not to the industry code on the ABN. Mixed businesses are the most commonly missed category.

What happens if a contractor's ABN was cancelled during the year? Validate it before lodging. A cancelled or invalid ABN may indicate that no-ABN withholding should have been applied to those payments, which is a separate obligation worth resolving before the report goes in.

Does the new pre-fill change anything? Yes. With the TPAR pre-fill introduced for tax time 2026, reported payments appear in contractors' own returns. Discrepancies between what a payer reports and what a contractor declares are now visible without any manual review.

The short version

TPAR lodgement takes minutes. Reconstructing accurate contractor totals from a year of bank descriptions takes a fortnight — unless the vendor normalisation happened at import time, in which case it takes an afternoon. Start now; the ATO has said plainly that 28 August is firm.

Run your practice on ReconLink.

Bank reconciliation that codes itself, BAS export ready for your tool of choice, and a client portal that ends the email chain.