Forms Legal

Posted on Jul 11

Why That 'Contractor' Gig Could Cost You $80k in Back Pay (A Dev's Reality Check)

#legal #startup #contracts

TL;DR: An ABN on your invoice won't save you when the Fair Work Ombudsman sees you working like an employee. I've watched devs get hit with $94k back-pay bills because they thought invoicing made them contractors. Reality check: your daily standups and Jira access destroy your contractor status. Here's how to actually protect yourself.

When 'Contractor' Isn't Enough (Real Dev Horror Story)

My React dev mate invoiced a Sydney startup for two years. He used their Jira board 24/7, sat in daily standups, and had zero other clients. No uniforms or business cards, but he might as well have worn a company badge. Then the Fair Work Ombudsman dropped a bomb. They ruled him an employee retroactively. Suddenly he was owed $94k in unpaid annual leave, super, and penalties. His ABN? Meaningless. The client called every shot, he coded when they said, where they said, how they said. Invoicing didn't change the reality.

This isn't hypothetical. The CFMMEU v Personnel Contracting case reshaped Australian law in 2022. Courts now ignore fancy contract labels if your actual work screams "employee." If your client controls your hours, tools, and workflow? You're staff. Period. That invoice number won't save you when the Ombudsman audits.

The 3 Clauses That Actually Protect You (Not Your ABN)

Your ABN is just tax paperwork. Real protection lives in your contract. I almost signed one last month requiring daily standups at the client's office. That single clause would've voided my contractor status under 2026 rulings. Here's what saved me, and what you need:

Explicit right to subcontract

Must state: "Contractor may appoint a qualified substitute without client approval." No wiggle room. If they can veto your sub, you're locked in like an employee. I added this to a gig last week, the client pushed back until I showed them Section 357 consequences.
Result-focused payment terms

Kill hourly billing. Payment triggers must tie to deliverables: "Payment issued within 14 days of approved feature deployment." Not "Payment for 40 hours/week." The Superannuation Guarantee (Administration) Act 1992 treats hourly-paid "contractors" as employees for super. If you're paid for labour, not outcomes, you lose.
Financial risk allocation

Include: "Contractor bears cost overruns if timeline extends beyond agreed scope." Real contractors eat delays. Employees don't. When a Melbourne dev friend added this clause, his client balked, they wanted free overtime. Red flag.

These aren't negotiable fluff. They're legal tripwires. Without them, your "contractor" label is tissue paper.

Why Your Daily Standup Invitation Is a Red Flag

That Slack DM asking you to join standups at 9 AM sharp? It's a death sentence for contractor status. Here's why devs get trapped:

Tool dependencies = Control

Using the client's Jira, Slack, or GitHub? You're integrated into their business. My React friend lived in their Jira board. Courts see that as employment evidence under the Fair Work Act 2009. True contractors use their own tools.
Mandated hours = Supervision

"Be online 9-5 for standups" destroys independence. The Act 2016 in Queensland explicitly flags fixed hours as an employee trait. I rejected a gig over this, they wanted me in-office Tuesdays for "culture."
Exclusive focus = Economic dependence

One client = zero leverage. If 95% of your income comes from them (like my mate's two-year gig), you're economically dependent. The WIRC Act in Victoria treats this as employment evidence.

If your workflow mirrors their staff, you are staff. No contract clause can fix that reality.

My Pre-Signing Checklist for Gigs

Run this 5-point audit before accepting any "contractor" role. I do it in under 2 minutes:

Sub test: Can I legally send a junior dev to handle this sprint? If "no," walk away.
Tool test: Do I own the IDE, laptop, and repos? If they provision GitHub seats, you're on thin ice.
Rate test: Was this rate actually negotiated? Or did they say "take it or leave it"?
Client test: Am I allowed to pitch other clients this week? True contractors hustle.
Scope test: Is payment tied to features shipped, not hours logged? Check your invoice template.

I failed point 4 on a fintech gig last year. They demanded full exclusivity. Nixed it, and avoided a potential Act 1987 workers' comp nightmare.

What Happens If You Get Caught? (Spoiler: It's Ugly)

Think back pay only hits the client? Wrong. As the "contractor," you get handed a tax bomb. Here's the math:

Back-pay avalanche: Unpaid annual leave (4 weeks/year), personal leave (10 days/year), super (11.5%). For a $120k "contractor" role? $25k+ in owed entitlements.
Penalties: Section 357 violations cost corporations $82,500 per contravention. But the Ombudsman will claw back unpaid super from you via the Act 1992.
Your side-hustle implodes: That cash you "saved" on super? Now it's due, with interest. I know a dev who paid $18k after a 3-year gig. His side project became a debt trap.

The Fair Work Ombudsman's 2024 "Closing Loopholes" push means they audit harder. They're scraping ABN databases for devs with one client. If your work pattern matches staff, you lose.

Where to Get a Dev-Safe Contract Template

Generic templates are landmines. That "independent contractor agreement" from Google? Likely missing state-specific traps. Queensland's Act 2003 and NSW's Act 1987 have different workers' comp tests. Victoria's WIRC Act 2013 adds more layers. One template won't cover all.

I use forms-legal.com as a starting point. Their Australia hub breaks down clauses for dev gigs, especially the subcontracting rights and scope language that actually hold up. But never just download and sign. Tailor every line to your real work pattern. If your gig involves client tools or fixed hours, those sections must reflect controlled access, not blanket permission.

Last month I tweaked their template with a "tools clause": "Contractor may access client Jira only during agreed sprint windows. All code commits use contractor-owned GitHub account." The client accepted it because it reduced their risk too.

Don't Let Invoicing Fool You

Your ABN isn't armor. It's just paperwork. The courts look at what you actually do, not what your invoice says. If you're glued to their Jira board, taking mandatory standups, and coding to their clock? You're staff. And that $80k back-pay bill will find you.

I audit my gigs quarterly now. Can I send a sub? Do I own my tools? Is payment tied to shipped code? If not, I renegotiate or walk. It's saved me twice.

Your move: Next contract gig, run the 5-point checklist. Make them accept real subcontracting rights. Pay for a lawyer if needed, cheaper than $94k. I link to forms-legal.com's Australia hub because their templates bake in Section 357 safeguards. But remember: your behavior must match the contract. Or the Ombudsman will make you pay for the gap.

DEV Community