PAYG Withholding Rates 2026 Your Complete ATO Guide

You hire your first employee, run payroll, and then stare at the payslip longer than you'd like to admit. Gross wages make sense. Super makes sense. The tax withheld looks like it was pulled from thin air. That's usually the moment business owners realise PAYG withholding isn't just “take some tax out and move on”.

The problem isn't that the numbers are random. It's that the system is progressive, tied to ATO tax tables, employee declarations, pay frequency, and reporting obligations all at once. If one input is wrong, the withholding can be wrong, the payslip can be wrong, and the reporting can drift with it.

We fix these issues often. In practice, the costly mistakes rarely start with complicated tax law. They start with rushed onboarding, old payroll settings, mismatched pay cycles, or manual admin. If your team still rekeys payroll details from documents by hand, tools that eliminate manual payslip entry for HR can reduce avoidable handling errors before they become a tax problem.

PAYG withholding in Australia isn't a flat rate. It mirrors the resident income tax schedule and collects tax through the year, which is why employers need to withhold from employees, company directors, and some contractors, then report and remit those amounts through BAS or Single Touch Payroll under the ATO framework described in the ATO tax tables overview.

What You'll Learn

• That First Payslip Why Is the Tax Withheld So Complicated
• Who Needs to Withhold Tax and Why
• Decoding the ATO Tax Tables for 2026
• Beyond the Basics Withholding on Bonuses and Variations
• Putting It Into Practice Calculation Examples

Table of Contents

• That First Payslip Why Is the Tax Withheld So Complicated
• • Why the number changes when the pay pattern changes
  • Why business owners trip over it early
• Who Needs to Withhold Tax and Why
• • The legal role of the payer
  • Why the TFN declaration matters early
• Decoding the ATO Tax Tables for 2026
• • What the tables are really doing
  • A small table with a big lesson
  • What works and what doesn't
• Beyond the Basics Withholding on Bonuses and Variations
• • Irregular payments change the workflow
  • Missing TFN or ABN means the rate changes fast
• Putting It Into Practice Calculation Examples
• • Example one claiming the tax-free threshold
  • Example two not claiming the tax-free threshold
• From Calculation to Compliance Reporting via STP and BAS
• • One compliance loop not two separate jobs
  • Where businesses get caught
• Your PAYG Withholding Compliance Checklist

That First Payslip Why Is the Tax Withheld So Complicated

A first payslip usually creates two reactions. The employee wants to know whether the net pay looks right. The employer wants to know whether the tax withheld is defensible if the ATO ever asks questions.

That tension exists because PAYG withholding rates aren't designed for convenience. They're designed for collection accuracy across the year. The ATO framework uses tax tables for different pay frequencies, including weekly, fortnightly, and monthly cycles, so the amount withheld tracks the employee's pay pattern rather than using one blunt rate.

Why the number changes when the pay pattern changes

A weekly wage and a monthly salary can produce very different withholding outcomes even if the annual package sounds straightforward. Payroll software has to use the correct table for the actual pay cycle. If it doesn't, the result may still look plausible on the payslip, which is why errors often sit unnoticed.

The confusion gets worse when a business owner assumes withholding should match the employee's average tax rate. It doesn't work that way. The system follows a stepped structure, so the marginal treatment matters.

Practical rule: Don't judge withholding by gut feel. Judge it by the employee's declaration, pay frequency, and the current table loaded into payroll.

Why business owners trip over it early

New employers often focus on wages, super, and leave. Tax withholding gets treated as a software output. That's a mistake. Software only works if the setup is right, the employee data is right, and the table version is current.

Common trouble spots include:

• Wrong pay cycle: Weekly staff processed through a fortnightly or monthly setting.
• Old table settings: Payroll wasn't updated after a tax table change.
• Threshold errors: The employee's tax-free threshold status was entered incorrectly.
• Manual overrides: Someone “fixed” a figure without documenting why.

A payroll system can calculate quickly. It can't rescue bad inputs.

Why this matters: if the first payslip is wrong, the error tends to repeat across every later pay run until someone notices.

Who Needs to Withhold Tax and Why

Some business owners think PAYG withholding is something larger employers worry about. It isn't. If you're the payer, the obligation sits with you. Size doesn't change that.

The legal role of the payer

In practice, the payer is the entity making the payment and carrying the withholding responsibility. That often means an employer paying wages, but it can also extend to payments to company directors and some contractors depending on the arrangement.

The job starts before the first processed pay run. Registration, setup, and the correct withholding framework need to be in place early. If you need the administrative starting point, this guide to registering your business with the ATO under the PAYG withholding tax scheme covers the setup sequence clearly.

Why the TFN declaration matters early

The TFN declaration drives several payroll decisions. It tells payroll whether the employee is claiming the tax-free threshold and gives the employer the information needed to apply the right table treatment. If that form is delayed, guessed, or entered badly, the withholding result can go off course from the first pay.

We tell clients to treat the TFN declaration like a control document, not a filing form. It affects how the pay run behaves. That makes it operational, not just administrative.

Worker classification mistakes are ugly because they rarely stay small. A business might treat someone as an independent contractor, skip withholding, and then spend months cleaning up payroll, reporting, and back-pay issues if that classification doesn't hold.

Common Pitfall

A worker can call themselves a contractor and still be treated differently under withholding rules depending on the facts. Labels don't fix risk. Neither does copying whatever another business in the industry does. Good compliance starts with reviewing the arrangement itself, then setting payroll treatment to match.

A solid process usually includes:

• Collect documents first: Get the TFN declaration and onboarding paperwork before the first live pay.
• Review the engagement: Check whether the worker's engagement falls outside employee treatment.
• Lock the payroll settings: Once verified, stop ad hoc changes by untrained staff.
• Keep evidence: If the ATO asks, memory won't help. Records will.

Why this matters: the cleanest payroll file usually comes from disciplined onboarding, not from fixing errors later.

Decoding the ATO Tax Tables for 2026

Many users open an ATO tax table, see formulas, thresholds, and notes, then hand the whole job to software. Fair enough. But if you don't understand what the table is doing, you won't know when the software is wrong.

What the tables are really doing

The tables tell payers how much to withhold for a particular pay cycle. That means the weekly table applies to weekly payroll, the fortnightly table applies to fortnightly payroll, and so on. The ATO builds them as administrative tools linked to the underlying income tax scale, not as a separate tax system.

That link matters. When income tax policy changes, payroll settings must change too. A useful reminder came in 2016, when the 32.5% bracket threshold increased from $80,000 to $87,000, which required employers to update payroll systems to the new withholding tables, as noted in this explanation of the new PAYG withholding rates.

The lesson is simple. Never assume last year's settings are close enough.

A small table with a big lesson

The point of a tax table isn't to memorise every line. It's to understand the structure and know what to check.

Sample 2026 Weekly Tax Table (Claiming Tax-Free Threshold)Tax to Withhold

Over $3,400

$968 plus 39 cents for each dollar over $3,400

Over $3,652

$1,067 plus 47 cents for each dollar over $3,652

That stepped design is why withholding can jump once earnings cross a bracket line. It also explains why payroll teams should care about gross pay timing, one-off payments, and whether the employee is claiming the threshold.

If you want a cleaner grasp of how the underlying scale works, this AWTS guide on what is marginal tax rate in Australia is worth reading alongside the ATO tables.

The businesses that handle PAYG well don't try to outsmart the table. They make sure the right table is being used, then they test edge cases before payroll goes live.

What works and what doesn't

What works:

• Using the current ATO table loaded into payroll.
• Testing odd pay amounts before the first production run.
• Checking threshold settings against employee declarations.

What doesn't:

• Relying on memory from prior years.
• Applying annual tax logic to a weekly or fortnightly payroll problem.
• Treating the table as static after a federal change.

Why this matters: tax tables look mechanical, but every payroll error tied to them still comes back to human setup decisions.

Beyond the Basics Withholding on Bonuses and Variations

Ordinary wages are the easy part. Payroll stress usually appears when the payment is irregular, larger than usual, or missing the supporting details payroll needs.

Irregular payments change the workflow

Bonuses, commissions, and other non-routine amounts force payroll to slow down. That's where rushed teams make poor choices. They either process the amount like ordinary salary without checking the ATO method, or they override the result because the withholding “looks too high”.

Neither approach is sound. Irregular payments need the correct payroll treatment, clear documentation, and a review before lodgement. If bonus withholding is part of your payroll cycle, this AWTS article on tax on bonus payments is a practical starting point.

Pro-Tip

For larger variable payments, run a test calculation before the live pay run and show the employee the expected withholding outcome in advance. That doesn't change the legal calculation, but it prevents arguments after net pay lands lower than expected.

Missing TFN or ABN means the rate changes fast

Identity-status withholding catches more businesses than bracket issues do. If an employee doesn't provide a TFN, employers must withhold at 47% for Australian residents. If a supplier doesn't quote an ABN on an invoice over $75, the business must also withhold at 47%, based on the compliance summary in Rippling's explanation of what PAYG withholding is.

That's not a subtle change. It's a blunt compliance tool.

Businesses usually create this problem themselves by allowing onboarding to lag behind payment timing. Someone starts quickly, the paperwork follows later, and payroll proceeds anyway. Then cash flow gets distorted and the clean-up begins.

A better way to handle variations is to separate them into decision buckets:

• Routine salary changes: Update the employee record before the pay run.
• One-off additions: Review the withholding method before approval.
• Missing identifiers: Stop and fix the TFN or ABN issue before payment where possible.
• Formal variations: Follow the ATO-approved variation process rather than inventing your own rate.

Why this matters: the expensive withholding errors usually don't come from complexity alone. They come from speed, weak onboarding, and undocumented exceptions.

Putting It Into Practice Calculation Examples

Once you've seen the logic, the table stops looking mysterious. The fastest way to build confidence is to run a couple of practical checks yourself.

The examples below use the ATO weekly table formula effective from 1 July 2024. For an employee claiming the tax-free threshold, withholding on weekly earnings over $3,400 is $968 plus 39 cents for each dollar over that amount. If the threshold isn't claimed, withholding is $1,111 plus 47 cents for each dollar over $3,400, according to the ATO's weekly tax table.

Example one claiming the tax-free threshold

Take a weekly wage of $3,500 where the employee is claiming the tax-free threshold.

The amount over $3,400 is $100.
The formula says $968 plus 39 cents for each dollar over $3,400.
So the extra withholding component is 39 cents x 100.
That is $39.

Add that to $968, and the withholding comes to $1,007 before the usual payroll rounding and system handling rules are applied.

That example matters because it shows the table is formula-based, not guess-based. If payroll produces a number far outside that range, something in the setup needs attention.

If you want a quicker way to sense-check routine figures, an Australia payroll calculator can be useful as a secondary review tool before finalising a pay run.

Example two not claiming the tax-free threshold

Now take the same weekly wage of $3,500, but this time the employee is not claiming the tax-free threshold.

The amount over $3,400 is still $100.
The formula changes to $1,111 plus 47 cents for each dollar over $3,400.
So the extra withholding component is 47 cents x 100.
That is $47.

Add that to $1,111, and the withholding comes to $1,158 before the payroll system applies the final table handling.

That's a sharp difference from the first example. Same wage. Different declaration setting. Different result.

If a withholding figure surprises you, don't start by questioning the tax rate. Start by checking whether the employee is marked as claiming the tax-free threshold and whether the weekly table is the one actually in use.

A short explainer can help if you're training internal staff on payroll reviews:

Why this matters: once you can verify one or two edge calculations by hand, you're far less likely to miss a payroll setup error.

From Calculation to Compliance Reporting via STP and BAS

Correct withholding is only half the job. The other half is reporting it properly and paying it on time. Businesses that separate those tasks in their minds usually create reconciliation problems.

One compliance loop not two separate jobs

PAYG withholding moves through a connected chain. Payroll calculates the withholding. STP reports the wage and withholding data. BAS captures the payable amount for remittance. Then the business pays the ATO.

If one part of that chain is wrong, the error doesn't stay isolated. It spreads. That's why we treat payroll processing and reporting as one compliance loop.

For businesses refining their reporting discipline more broadly, practical finance governance material such as 2025 financial reporting advice for sponsors can be useful for strengthening review habits around reconciliations and reporting controls. The same mindset helps in payroll compliance.

If you need the reporting side explained in payroll terms, this AWTS guide on Single Touch Reporting STP gives the right operational overview.

Where businesses get caught

The common issue isn't that businesses never lodge. It's that the figures across payroll, STP, and BAS don't line up cleanly.

Common Pitfall

A mismatch between STP totals and BAS figures is one of the most avoidable compliance problems in small and medium business payroll. It often starts with manual journal entries, late payroll adjustments, or a corrected pay run that wasn't reflected everywhere else.

A practical monthly review should include:

• Payroll register check: Confirm the wage and withholding totals from the payroll file.
• STP review: Make sure the submitted figures match the finalised payroll data.
• BAS preparation check: Reconcile the payable amount to the same source totals.
• Payment control: Confirm the remittance matches the lodged obligation.

Clean reconciliation is what keeps PAYG withholding defensible. If the numbers don't agree across payroll, STP, and BAS, the ATO won't care that the original payslip looked reasonable.

Why this matters: withholding compliance isn't finished when the payslip is issued. It's finished when the reporting and payment trail agrees from start to finish.

Your PAYG Withholding Compliance Checklist

PAYG problems don't usually come from one dramatic failure. They build from small process gaps that repeat every pay cycle. The fix is a tighter system.

Use this checklist as a working standard, not a once-a-year exercise.

• Confirm current payroll settings: Check that your software is using the right pay frequency and the current ATO table version.
• Verify employee declarations: Make sure TFN declarations are on file and correctly entered before live payroll runs.
• Review threshold treatment: Test whether employees claiming or not claiming the tax-free threshold are coded correctly.
• Flag exceptions early: Separate ordinary wages from bonuses, commissions, and other irregular payments before processing.
• Control onboarding: Don't let missing TFNs or supplier ABN issues drift into payment runs without review.
• Reconcile each cycle: Match payroll totals to STP submissions and BAS figures, not just bank payments.
• Keep an audit trail: Save calculation notes, override reasons, and correction records where staff can retrieve them.
• Schedule compliance dates: BAS and remittance deadlines shouldn't live in someone's memory.
• Review after changes: New software, new payroll staff, or a restructure should trigger a payroll control check.
• Get help when the process feels fragile: If your payroll only works because one person knows where everything sits, the system isn't stable.

The businesses that stay out of trouble don't rely on luck. They build controls that make the right result more likely every time.

What is PAYG withholding and who must do it?

PAYG withholding is the system by which employers deduct tax from payments before remitting the net amount to the payee. Any business that employs staff, engages contractors under a voluntary agreement, or pays certain investment income must register for PAYG withholding and remit withheld amounts to the ATO.

How do I calculate PAYG withholding for an employee?

Use the ATO's tax withheld calculator or the published tax tables. The amount depends on the employee's earnings, pay frequency, tax-free threshold claim, and any HELP debt. Enter the gross weekly or fortnightly pay into the relevant ATO table and withhold the corresponding amount. Update calculations whenever the employee's circumstances change.

What happens if I withhold the wrong amount of PAYG tax?

Under-withholding means the employee may owe tax at year end and the employer may face a shortfall penalty. Over-withholding creates a refund for the employee. Correct errors promptly by adjusting future pay runs and reporting corrections via Single Touch Payroll finalisation at year end.

When must PAYG withholding amounts be paid to the ATO?

Payment frequency depends on withholder category. Large withholders (over $1 million annually) pay electronically by the next business day. Medium withholders ($25,000–$1 million) pay monthly. Small withholders (under $25,000) pay quarterly with the BAS. All withholders must report through STP on or before each payday.

What is a TFN declaration and why does it matter for PAYG withholding?

A TFN declaration is completed by employees when they start work. It records the TFN, tax-free threshold claim, and HELP debt status. Without a declaration, employers must withhold at 47%. An incorrect declaration affects withholding accuracy for the entire employment period.

If your payroll records are messy, your BAS is behind, or your PAYG withholding process feels more improvised than controlled, get advice before the problem compounds. Australia Wide Tax Solutions helps businesses clean up payroll compliance, align STP and BAS reporting, and keep withholding obligations accurate from setup through lodgement.