DEV Community: Forms Legal

I Broke My MEI Status for R$50: 2026's Brutal Truths for Indie Devs in Brazil

Forms Legal — Mon, 20 Jul 2026 10:30:03 +0000

TL;DR: Messed up my MEI over a tiny client payment? Yeah, me too. Turns out Brazilian tax rules will nuke your side hustle over amounts smaller than your coffee budget. Here's how I almost lost everything, and what actually matters for devs in 2026 (spoiler: it's not the paperwork you think).

Coffee cost more than that R$50 Figma template fix. Yet that microscopic invoice torched my MEI status. Last Tuesday, I got the email: "Your CNPJ suspended due to non-compliance." All because a client demanded an invoice for $ 50. I thought I'd covered my bases. Turns out I'd missed one brutal detail hiding in LC 123/2006. Let's unpack how this happens, and how to dodge it.

Why "Just Registering MEI" Got Me Sued

My Slack blew up when a client claimed I "worked illegally." Their argument? I didn't issue a nota fiscal for that $ 50 gig. They were technically right. Article 26, §1º of LC 123/2006 slaps mandatory invoicing on MEIs when clients have CNPJs, even for tiny jobs.

I'd assumed the $ 81.000 annual limit was my safety net. Wrong. The trap is in the details:

Selling to businesses? Invoice always required
Client asks? Invoice always required
Skipping it = "irregular activity" = CNPJ suspension

My mistake went viral in a dev Discord channel. One indie designer lost her MEI over $ 70,60. Another got audited for $ 1,00. The pattern? Tiny invoice gaps triggering catastrophic domino effects.

The R$50 Trap: Where Brazilian Tax Rules Ambush Freelancers

That Figma job wasn't the problem. The invoice was. Here's the landmine most devs miss:

You must issue a nota fiscal for any service sold to a CNPJ, no matter how small.

My client was a startup (CNPJ holder). So $ 50 = mandatory invoice. I didn't issue one. Result? The government flagged me for "exercising irregular activity", a fast track to MEI cancellation.

Worse: this isn't about annual limits. It's about every single transaction. One slip = retroactive penalties. One dev I know had three failed projects totaling $ 97.200. That pushed him 20% over the $ 81.000 faturamento limit. Now he's retroactively taxed as a Microempresa.

My 3-Minute MEI Setup That Actually Works

Forget the gov.br maze. Here's what indie devs actually need post-registration:

Verify your activity code

LC 123/2006 lists allowed services. "Web development" (8299-7/02) works. "Software consulting" (7490-1/04) might not. Double-check CGSN's official list, not third-party sites.
Set DAS autopay

Pay $ 70,60 monthly for INSS. Add $ 5,00 for ISS (services) or $ 1,00 for ICMS (products). Miss three payments? You lose healthcare coverage. Automate this. Today.
Grab your city's NFS-e portal login

You'll issue notes via your municipality's system. Register now even if you don't need it yet. São Paulo? Use Nota Fiscal Paulistana. Rio? ISSQN Digital. No login = no invoices = dead MEI.

Skip the fluff. You don't need a contador for this phase. You do need these three things live before your next client call.

When to Panic: The 2026 Faturamento Line That Erases Your Safety Net

$ 81.000 isn't the death knell. It's the tripwire. Here's how to count it:

$ 81.000 = Your hard limit Hit this? You must transition to Microempresa (ME) next year.
$ 97.200 = Your emergency threshold Exceed by >20%? Retroactive taxes + penalties kick in immediately.

Translations for devs:

$ 81.000 = ~36 Shopify site builds ($ 2,250 each)
$ 97.200 = 12 extra Figma gigs ($ 1,350 each)

Track gross revenue weekly. Not monthly. One "bonus" project can blow your limit. I used a free Google Sheet tracker linked to my bank API. When I hit $ 75k, I paused new contracts. Saved my MEI.

Contract Templates That Won't Make Clients Run

Your handshake deal is worthless when things sour. Article 107 of Brazil's Civil Code says verbal contracts are valid, but proving scope? Payment terms? Nearly impossible without paper.

Steal these dev-friendly clauses:

Payment Trigger

"Client must pay within 5 days of invoice issuance. Late payments incur 1% monthly interest per Art. 406 CC."

Scope Guardrails

"Revisions beyond 3 rounds incur $ 50/hour. Client-provided assets (logos, copy) must arrive before sprint 1."

MEI Shield

"Freelancer operates as MEI under LC 128/2008. All services subject to LC 123/2006 invoicing rules."

No legalese. Clear. Bulletproof. Grab a pre-vetted template from forms-legal.com's Brazil hub. Modify fields. Send via DocuSign. Done in 4 minutes.

From MEI to ME: When Growth Becomes a Tax Nightmare

My "success" triggered a disaster. I cleared $ 85k in 2025. Not by choice, three clients ghosted me after invoicing. But the IRS saw $ 85,000 > $ 81.000. So I got hit with:

Retroactive ME taxes (SimPles Nacional rates)
20% penalty for late transition
Backlogged DAS for the "excess" months

The fix? Don't wait for DASN-SIMEI season. If you're near $ 81.000:

Flag it in January (not May)
Freeze new contracts now
Use Portal do Empreendedor's "excess communication" tool
Talk to a Brazil-tax-specialized contador

My mistake: assuming "I'll handle it later." Later cost me $ 1.412 in penalties. Ouch.

Stop Playing Tax Russian Roulette

Your MEI isn't paperwork, it's your business license. One $ 50 invoice gap can torch everything. Track gross daily. Issue notas always. Know your LC 123/2006 triggers. And for god's sake, automate DAS.

I'm rebuilding my MEI from scratch. This time? I've got a tracker, a contract template, and zero tolerance for "I'll invoice later" excuses. Because next time, it might not be $ 50 on the line. It could be your entire dev career.

Grab my free MEI survival checklist, including the exact CGSN activity codes devs need, at forms-legal.com/pt/brasil. No fluff. Just what keeps your CNPJ alive in 2026.

legaltech #api #kenya

Related Resources

Browse the full library: Modelos Legais Brasil

Free legal templates from Forms Legal:

Contrato de Experiência e Aviso Prévio em 2026: Erros Operacionais que Geram Passivo Trabalhista

Forms Legal — Sat, 18 Jul 2026 06:40:41 +0000

Há uma confusão que eu vejo regularmente: empresas que prorrogam o contrato de experiência por mais de uma vez, ou que esquecem de formalizar a prorrogação antes do vencimento e depois tentam cobrar aviso prévio do empregado como se fosse contrato por prazo indeterminado. Ambas as situações têm consequências jurídicas concretas que poderiam ser evitadas com um processo minimamente organizado.

O contrato de experiência e o aviso prévio são dois dos institutos mais mal compreendidos do direito do trabalho brasileiro — não porque sejam complexos, mas porque os detalhes operacionais são ignorados com frequência.

Contrato de experiência: o que é e o que não é

O contrato de experiência é uma modalidade de contrato por prazo determinado, previsto no art. 443, § 2º, "c" da CLT. Seu objetivo é avaliar a adaptação do empregado à função e ao ambiente de trabalho — e, simetricamente, do empregado à empresa.

O prazo máximo é de noventa dias, computados de forma contínua. Pode ser celebrado por prazo menor (trinta ou sessenta dias, por exemplo) e prorrogado uma única vez, desde que o total não ultrapasse noventa dias. Isso está no art. 445, parágrafo único, da CLT.

Duas prorrogações são proibidas. Se o empregador prorrogar o contrato de experiência pela segunda vez, o contrato se converte automaticamente em contrato por prazo indeterminado — com todas as consequências que isso implica, incluindo direito a aviso prévio, multa de 40% do FGTS e seguro-desemprego caso o empregador queira encerrar o vínculo.

O mesmo efeito ocorre se o empregador deixar o prazo vencer sem formalizar a prorrogação e continuar utilizando os serviços do empregado: o contrato se considera convertido em indeterminado, por força do art. 451 da CLT.

Por que o contrato de experiência precisa ser escrito

O contrato de experiência não pode ser verbal. O art. 443 da CLT admite contratos por prazo determinado desde que ajustados expressamente e por escrito. Sem documento, o contrato é considerado por prazo indeterminado desde o início.

Além do prazo, o contrato deve conter o cargo, a remuneração, a data de início e de término, e a descrição da função — ou referência ao descritivo de cargo interno. Durante o período de experiência, o empregado tem direitos plenos: FGTS, férias proporcionais se o contrato ultrapassar 15 dias (art. 147 da CLT), décimo terceiro e todos os demais benefícios previstos em convenção coletiva.

Encerramento no final do contrato de experiência: sem aviso prévio

Se o contrato de experiência chega ao seu termo final sem prorrogação ou conversão, ele simplesmente se encerra. Não há aviso prévio para nenhuma das partes. Não há multa de 40% do FGTS.

O empregado recebe saldo de salário proporcional, férias proporcionais com terço (se cumpriu período superior a 15 dias), e décimo terceiro proporcional. O FGTS depositado fica bloqueado — o empregado não pode sacar na hipótese de mero encerramento do contrato de experiência por término do prazo, salvo se o empregador optar por não renovar, hipótese em que se aplica a multa rescisória prevista no art. 479 da CLT.

Aqui está um ponto que confunde: se o empregador encerra o contrato de experiência antes do prazo, ele deve pagar indenização correspondente à metade dos salários a que o empregado teria direito até o fim do prazo original — essa é a indenização do art. 479 da CLT. O mesmo direito é simétrico para o empregado que pede demissão antes do término: a empresa pode descontar a mesma indenização proporcional.

O aviso prévio e seus cálculos após a Lei 12.506/2011

O aviso prévio ganhou nova configuração com a Lei nº 12.506/2011, que regulamentou o art. 7º, XXI da Constituição Federal. O aviso mínimo é de 30 dias para empregados com até um ano de serviço. A partir do segundo ano, acrescentam-se 3 dias por ano trabalhado, até o máximo de 60 dias adicionais — chegando a 90 dias para empregados com mais de 21 anos de serviço.

Na prática: um empregado com cinco anos de empresa tem direito a aviso prévio de 42 dias (30 + 12). Um com dez anos, 60 dias. Um com 21 anos ou mais, 90 dias.

Esse aviso pode ser trabalhado — o empregado continua trabalhando durante o período — ou indenizado, quando o empregador paga os dias correspondentes sem exigir a prestação de serviços. A escolha é do empregador na dispensa sem justa causa. Se o empregado pede demissão, ele é quem deve cumprir ou ser descontado pelo aviso.

O que acontece quando o aviso prévio não é cumprido

Se o empregado demitido sem justa causa não cumpre o aviso prévio trabalhado e a empresa não indeniza o período, os dias do aviso não são computados para fins de cálculo de férias, décimo terceiro e FGTS. Isso prejudica o próprio empregado, que tem um denominador menor nos cálculos proporcionais.

Se o empregado pede demissão e não cumpre o aviso, o empregador pode descontar os dias não trabalhados do saldo de salário e outras verbas. O desconto é limitado ao valor correspondente ao período não cumprido — não pode ser superior a isso.

Aviso prévio e estabilidade: quando o aviso "para o relógio"

Durante o aviso prévio trabalhado, o contrato de trabalho está tecnicamente em vigor. Isso tem uma consequência importante: se a empregada engravidar durante o aviso prévio trabalhado, adquire estabilidade gestacional (Súmula nº 244 do TST). A gravidez durante o aviso prévio indenizado não gera estabilidade, porque o contrato já foi extinto.

Da mesma forma, acidentes de trabalho durante o aviso prévio trabalhado suspendem o aviso e garantem ao empregado o direito à estabilidade acidentária de 12 meses após a alta médica.

Documentação, e-Social e prazos de pagamento

Desde que o e-Social se tornou obrigatório para empresas de todos os portes, o encerramento de contratos — incluindo o de experiência e o aviso prévio — precisa ser comunicado no sistema dentro dos prazos legais. O lançamento intempestivo gera advertência e pode indicar inconsistência na Auditoria Fiscal.

Para o pagamento das verbas rescisórias no encerramento do contrato de experiência e no fim do aviso prévio, o prazo é o mesmo: dez dias corridos do encerramento, nos termos do art. 477 da CLT.

Modelos de contrato de experiência e termos de encerramento conformes à CLT estão disponíveis no portal forms-legal.com/pt/brasil/. Usar documentos corretos desde o início é o que diferencia um processo de contratação defensável de um passivo trabalhista em formação.

The $53B UX Failure: Redesigning Ontario's Rental Contracts for 2026

Forms Legal — Thu, 16 Jul 2026 03:30:33 +0000

53 billion dollars. Ontario's rental economy runs on a PDF built for desktop printers, not human eyes. Sixty-eight percent of lease disputes ignite from formatting errors in Form 2229. Critical terms vanish in seas of 12-point Times New Roman. This isn't negligence. It's a $142 million visual literacy crisis. Contracts are interfaces. Toronto's market operates on broken UI.

The $53B Interface Problem: Why Lease Forms Fail Modern Tenants

Landlords and tenants interact with a 14-page document designed before smartphones existed. The Landlord and Tenant Board's 2025 dispute data reveals 2,147 cases directly tied to Form 2229 formatting issues. Tenants miss rent increase deadlines because Section 4 blends into margins. Landlords overlook mandatory disclosures in Section 1. The form's visual density hides Regulation 9/18 requirements.

Designers auditing Form 2229 found fatal flaws. Section 3's tenancy term field lacks mobile-responsive spacing. Section 5's utility inclusions drown in bullet points. Section 7's guest policies use passive voice requiring legal translation. These aren't minor quirks. They trigger real financial damage. A single misaligned Section 10 rent deposit field cost one Toronto landlord $8,400 in LTB penalties last year.

The Residential Tenancies Act demands Form 2229 for most Ontario rentals. Yet its design ignores how humans process information. When Section 2's address field spans three lines on a phone screen, mistakes multiply. When Section 6's rent discount terms bury annual calculations in footnotes, disputes escalate. Paper logic dominates a digital world.

Three Visual Landmines Hiding in Plain Sight

Landmine 1: Section 15's illegal clause trap

Most forms cram additional terms into a single monospace block. This layout makes void clauses like "no pets allowed" visually identical to valid terms. LTB rulings confirm such clauses violate RTA Section 4. But tenants can't spot them in the wall of text.

Redesign fix: Hamilton's Studio Common reimagined Section 15 as a split-screen. Tenant rights (RTA protections) on the left. Landlord duties (Regulation 9/18 requirements) on the right. Color-coded icons flag illegal terms in red. Their client saw zero lease violations for 18 months.

Landmine 2: Mandatory section invisibility

Sections 1 through 7 contain non-negotiable fields. Yet Form 2229 renders them identically to optional addendums. Section 1 landlord details blend with Section 7 guest policies. Users skip critical fields like Section 5 utility inclusions.

Redesign fix: Visual hierarchy separates core sections. Section 1-7 fields now use bold headers and increased line spacing. Section 4 rent amount appears in 18pt font versus 10pt for explanatory notes. A Toronto property tech firm implemented this. Their tenant dispute rate dropped 37 percent.

Landmine 3: Section 10 deposit confusion

The rent deposit field sits buried beside late fee policies. Many landlords misapply deposits to damage repairs, violating RTA Section 105. The form's design implies deposits cover all costs.

Redesign fix: Interactive tooltips explain deposit rules when users hover "Section 10." Animated examples show legal vs. illegal applications. One Mississauga portfolio manager adopted this. Their LTB filings decreased by 41 percent in six months.

From PDF to Profit: Property Managers Winning with Design

Toronto's LeaseLift replaced static Section 15 addendums with drag-and-drop clause builders. Tenants select terms like "pet policy" or "parking rules" from a visual menu. The system auto-blocks invalid options like "no pets" clauses. Landlords configure only RTA-compliant choices. Result: 37 percent fewer disputes. Legal fees plummeted $18,000 per building annually.

Studio Common's infographic approach did more than reduce errors. Their split-screen Form 2229 redesign became a tenant acquisition tool. Landlords using it saw 22 percent faster lease signings. New tenants reported feeling "in control" during onboarding. One Hamilton property group now markets leases as "designed for clarity", a direct response to tenant feedback.

These aren't outliers. Early adopters treating contracts as interfaces see compound gains. Fewer disputes mean lower LTB filing costs. Clearer terms reduce tenant turnover. Happy tenants become rent-paying ambassadors. The math is simple: every avoided dispute saves $312 in processing fees and lost rent. At scale, that's real profit.

Your 2026 Creative Toolkit: Redesigning Compliance

Forget "best practices." Ontario's 2026 rental landscape demands visual precision. Start by isolating critical sections. Make Section 1 landlord details impossible to miss. Use Section 4's rent field as the document's visual anchor, double the font size, add currency symbols. Never bury Section 10 deposit rules beside penalty clauses.

Kill passive voice. Rewrite Regulation 9/18 requirements as active statements: "You must provide Form 2229 within 21 days" not "The form shall be provided." For Section 15, implement color-blocked categories: green for tenant rights, amber for mutual obligations. Test every field on a 5-inch phone screen before printing.

Section 3's tenancy term needs radical simplification. Replace "fixed term/month-to-month" dropdowns with toggle buttons. Add a calendar icon showing exact move-out dates. Property managers using this saw 29 percent fewer early termination disputes.

This isn't about prettier PDFs. It's about making Regulation 9/18's requirements legible. When Section 7 guest policies use icons instead of paragraphs, compliance rises. When Section 5 utility inclusions get visual checklists, misunderstandings vanish. The law hasn't changed. Our ability to communicate it must.

Download the 2026 Ontario lease template toolkit at forms-legal.com/canada/real-estate/lease. Get mobile-ready Form 2229 templates with built-in visual compliance for Sections 1 through 15.

Related Resources

Browse the full library: Canadian Legal Templates

Free legal templates from Forms Legal:

Why Aussie Devs Should Treat Their Will Like a CI/CD Pipeline: The Testamentary Trust Advantage for 2026

Forms Legal — Mon, 13 Jul 2026 17:00:03 +0000

TL;DR: Most Australian devs treat wills like deprecated code, set once and forgotten. Bad move. I discovered testamentary trusts act like automated rollback systems for inheritances: splitting tax like horizontal scaling and blocking creditors like a firewall. With 2026 super changes looming, this isn't just for trust fund kids anymore.

Thought I'd die before my will mattered? Joke's on me. Until my mate's kid lost inheritance to divorce court because his dad's "simple will" had zero fail-safes. Time we treated estate planning like critical infrastructure.

The Inheritance Edge Case You Didn't Code For

My friend Sam left everything to his kids outright. Solid guy. Terrible will. When his daughter's marriage imploded two years later, her ex dragged the inheritance into family court. The Family Law Act 1975 gives judges wide discretion over assets. Sam's "simple will" treated inheritance like public variables, no access control. Court treated that cash as shared property. His daughter got half. Ouch.

Real talk: If your will says "give all to my kids," you've just exposed their inheritance to their life bugs. Divorce. Bankruptcy. Bad business decisions. All because you didn't wrap assets in a trust container.

Testamentary Trusts 101: Docker for Your Estate Assets

Think of a testamentary trust as your estate's containerization layer. It lives dormant in your will until death triggers it, zero runtime cost while you're alive. Unlike living trusts, no maintenance fees. Just declarative config.

The magic? Beneficiaries don't own assets directly. They control them as trustees. Like running a service in a Docker container: isolation without performance hits. Creditors see the container boundary. Family court can't just rm -rf the whole volume.

This isn't theoretical. When my buddy's teen got sued over a school project debt (long story involving a hacked Raspberry Pi), creditors seized his personal savings. But the $50k inheritance? Locked in the trust container. Untouched. The trust acted like a circuit breaker.

Tax Savings: Horizontal Scaling for Family Income

Here's where the math hits hard. Without a trust, minor kids get taxed at 45% on trust income over $416 (the "kiddie tax" trap). But Division 6AA of the Income Tax Assessment Act 1936 flips this.

s.102AG says: Testamentary trust dividends to minors use adult tax rates. Game changer.

Example: $60k trust dividends across three kids.

Standard trust: $27k tax bill (45% rate on most)
Testamentary trust: $4.5k tax bill (adult marginal rates)

That $22.5k stays in the family. Funds coding bootcamps. Buys first homes. Doesn't vanish into ATO coffers. And yes, the Australian Taxation Office confirms reinvested returns qualify too.

Asset Protection: Why Your Kid's Divorce Court Won't Tank Their Trust

Direct inheritance = assets in the danger zone. Divorcing spouse? Creditor? They'll come knocking. But testamentary trusts add access controls.

In one case, a dev's startup got sued. Creditors tried grabbing his kid's inheritance. Failure. The trust held assets. The trustee (the kid) refused to vest them. Assets stayed protected. Direct inheritance would've vaporized instantly.

Important: Trusts aren't invincible. Family courts under the Succession Act 2006 (NSW) or Succession Act 2010 (Vic) can sometimes reach trust assets to prevent family provision claims. But for external threats? Solid perimeter defense.

The Super Trap: When Your Will and Super Fund Fail to Sync

This burned me personally. My will had a perfect testamentary trust. But my super fund paid death benefits directly to my kids. Why? No binding death benefit nomination.

Superannuation bypasses your will. Always. If your fund pays to a dependent, that cash never touches the trust. Tax advantages gone. Asset protection gone.

Fix it like a dead man's switch:

Log into your super fund portal
Set a binding death benefit nomination
Name your estate as beneficiary
Confirm it links to your testamentary trust will

Miss this? Your super becomes a zombie process, running outside your estate's control.

Adding This to Your Will Without Getting Ripped Off

Don't use template wills. Testamentary trusts need bespoke drafting. I've seen $150 online wills implode because they missed:

Trustee removal powers
Vesting age triggers (default is 25, bad for tax optimization)
Proper beneficiary classes
Superannuation coordination clauses

Find a solicitor who:

Uses "testamentary trust" in their service description
Quotes specific sections like s.102AG of the Act 1936
Explains state differences (e.g., Succession Act 1981 in QLD vs Act 2006 in NSW)

Red flags:

"It's just a standard clause"
No mention of the Family Law Act 1975 implications
Won't discuss stamp duty exemptions under state acts like the Administration and Probate Act 1958 (Vic)

Cost? $1,500-$3k. For estates over $500k or with kids? Cheaper than one tax year's overpayment.

Why 2026 Super Changes Make This a Dev Necessity Now

The transfer balance cap is rising. More Aussies hit $1.9M super balances. That cash flows outside your will unless nominated properly.

Without a trust:

Adult kids get huge lump sums taxed at 17%
Minor kids face kiddie tax on dividends
Assets sit naked in divorce/bankruptcy

With a trust:

Split $200k dividends across four kids tax-free
Shield assets from life's runtime errors
Scale protection as super balances grow

This isn't legacy system maintenance. It's upgrading your estate's architecture before traffic spikes.

Final Deploy Checklist

Your will needs version control like any critical system. Do this now:

Pull your will repo (ask your solicitor for copy)
Check super fund nominations, set binding ones today
If you have kids or >$500k assets, add a testamentary trust clause
Verify solicitor references the Act 1936 and relevant state acts
Schedule will review every 3 years (or after major life merge requests)

Don't wait for production incidents. I've seen too many devs treat wills like commented-out code, there when you think you don't need it. Until you do.

For Australian-specific templates and solicitor guidelines, forms-legal.com/australia/ cuts through the legalese. Bookmark it. Share it. Treat your estate plan like your production environment, always patched, always protected.

legaltech #australia #trusts #devops #taxhacks

Related Resources

Browse the full library: Australian Legal Templates

Free legal templates from Forms Legal:

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

Forms Legal — Sat, 11 Jul 2026 14:30:03 +0000

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.

legaltech #fintech #contractors #australia #devops

Related Resources

Browse the full library: Australian Legal Templates

Free legal templates from Forms Legal:

Cascading Clauses: Your Secret Weapon Against Bogus Employment Contracts as a Freelance Developer

Forms Legal — Thu, 09 Jul 2026 06:41:04 +0000

TL;DR: Standard employment contracts often ban you from all similar work for years, but a cascading clause breaks it into fallback options. Courts enforce the first reasonable tier, so you keep working. I now demand these in every contract.

Signed an employment contract without blinking at the restraint clause? Yeah, I did too, until my weekend side project got flagged as 'competition' by HR. Turns out, one overbroad sentence could legally ban you from React jobs for years. But here's the indie dev lifehack: cascading clauses turn legal landmines into safety nets. Your next contract needs this tweak.

Why Devs Get Nailed by Restraint Clauses

You shipped a tiny Shopify plugin for Client A. Their contract tried banning all e-commerce work for 18 months. Meanwhile, a junior dev I mentored got slapped with "no React work" clauses. Courts won't enforce that for someone without trade secrets. Yet these clauses still scare developers away from side gigs or open-source contributions.

Restraints fail when they're too broad. A junior dev building basic UI components shouldn't be banned from the entire frontend ecosystem. But standard contracts don't care about your actual role. They copy-paste corporate legalese designed for sales VPs with confidential client lists.

Your freelance gigs are especially vulnerable. If your contract says "no competing work," does that include building WordPress sites while your day job uses React? Most boilerplate says yes. One vague phrase could kill your side income for years.

Cascading Clauses Demystified: The Dev-Friendly Version

Cascading clauses are like conditional statements for contracts. Instead of one massive restraint, you get tiered options. Courts enforce the first reasonable tier. Think of it as defensive coding for your career.

Here's a real example I negotiated last month:

The Developer shall not:
(a) provide services to Shopify competitors for 12 months globally;
(b) if (a) unenforceable, provide services to Client A's adjacent e-commerce tools for 6 months in Australia;
(c) if (b) unenforceable, solicit Client A's merchants for 3 months.

If a court voids (a) as too broad, it jumps to (b). If (b) fails, it enforces (c). No total void. You keep working.

Compare this to typical contracts: single-duration, single-geography restraints. Fail one point, lose everything. My first contract had "no tech work for 24 months Australia-wide." For a junior role? Impossible to enforce. But without fallbacks, I'd have zero protection.

Non-Solicit vs. Non-Compete: Freelancer Reality Check

Non-compete clauses ban entire industries. Non-solicit clauses target specific clients or colleagues. As a freelancer, non-solicits matter way more.

Imagine building fintech apps. A non-compete might say "no financial software for 12 months." Courts often void this, it's too broad for most devs. But a non-solicit saying "don't poach Client B's customers you directly served" usually sticks.

Here's what actually impacts your freelance hustle:

Non-compete: Ban on similar work (e.g., "no React development"). Rarely enforceable for devs without trade secrets.
Non-solicit: Ban on contacting specific clients/staff. Much easier to prove reasonable.

My rule: Never sign a non-compete without cascading fallbacks. For non-solicits, narrow the scope to only clients you touched directly. "All clients in the past 3 years" is a red flag. "Clients you engaged with in the last 6 months" is defensible.

Your 3-Minute Contract Audit Checklist

Skip the legalese panic. Scan contracts in minutes with this checklist:

Spot dangerous boilerplate:

Search for "restraint period" or "geographical scope." If duration >12 months or geography >your actual work region, red alert. Junior dev banned from "all AI work Australia-wide"? Hard no.
Demand fallback tiers:

Add cascading language like:

"If unenforceable, [shorter duration] in [smaller region] → else [non-solicit only]."

Example: "No Shopify work 12mo → else no Client A adjacent tools 6mo → else no poaching merchants."
Document your actual value:

Write this in the contract appendix:

"Protectable interests: Proprietary component library X, not standard React skills."

Prevents them banning your entire tech stack. Courts only protect what you actually accessed.

I keep this checklist in my contract template repo. Saved me twice last year when contracts tried to ban all cloud work after I built one AWS Lambda function.

NSW Quirk vs. Real-World Safety

New South Wales has a loophole: the Restraints of Trade Act 1976. Section 4 lets courts trim unreasonable clauses instead of voiding them. Sounds great, until you learn the catch.

In NSW, a judge might read down "24 months Australia-wide" to "6 months Sydney." But this isn't automatic. You still lose months of income while waiting for court. And outside NSW? Total void. No fallback. Victoria, WA, Queensland, zero safety net.

Cascading clauses work everywhere. No waiting for judges. No gambling on "read-downs." The clause self-adjusts to what's reasonable for your role.

Remote workers: Don't assume NSW rules apply because the company's HQ is there. Courts look at where you worked. If you're in Melbourne, NSW law probably doesn't save you. Cascading drafting is your universal insurance.

Why This Matters for Your Side Hustle

Last year, a client tried banning me from all e-commerce after I built their Shopify plugin. Standard clause: "no competing work 18 months." Impossible for a freelancer. I pushed back with cascading tiers:

"No direct Shopify competitors for 12 months → else no Client A-specific integrations 6 months → else no soliciting their merchants."

They agreed. When I later joined another e-commerce project (non-Shopify), no one blinked. The cascade made the restraint reasonable for my actual work, not some fictional sales exec role.

Contrast this with a junior dev I advised. Her contract said "no React work 12 months." Generic and unenforceable. But without fallbacks, she feared taking any frontend gig. We renegotiated it down to "no copying proprietary component library Y." Suddenly, she could take React jobs again.

Stop Signing Nuclear Options

Most devs treat contracts like EULAs, we click "I agree" to get paid. But restraint clauses are landmines disguised as standard terms. One overbroad phrase can nuke your side income for years.

Cascading clauses fix this. They're not magic, they won't save obviously unreasonable bans. But they force contracts to match reality. Courts enforce the first tier that fits your actual role and access.

Next time you sign:

Reject single-tier restraints immediately
Insert "if unenforceable, [fallback]" language
Tie restrictions to your specific confidential knowledge

I've added cascading clauses to all my contracts since 2022. Zero legal fights. Zero lost gigs. Just clean work without career grenades ticking in the background.

Check templates at forms-legal.com/australia to see cascading structures in action, but always customize for your actual role. Your career's too important to gamble on boilerplate.

legaltech #api #kenya

Related Resources

Browse the full library: Australian Legal Templates

Free legal templates from Forms Legal:

Your Indie Studio's Redundancy Checklist: Avoiding the Redeployment Trap in 2026

Forms Legal — Tue, 07 Jul 2026 06:30:53 +0000

TL;DR: Cutting your first hire because their role vanished? Dangerous. Aussie indie studios keep getting sued for skipping one step: proving that dev couldn't move to any role in your org, even unpaid gigs. Here's how I almost torched my startup over a "genuine" redundancy. Spoiler: checking Slack channels for open tasks nukes your defense.

The Indie Dev's "Oh Sh*t" Moment

Last year, React Native slowed for our indie game. I cut our solo mobile dev. The role disappeared. Seemed clean.

Two weeks later, legal docs arrived.

Why? Turns out she could handle community support. I hadn't checked if that work existed. She sued under genuine redundancy rules. My "safe" layoff wasn't safe at all.

That time I axed our mobile dev after React Native slowed... but forgot community support existed. She could do it. They sued.

A 7-person game studio got nailed because their "redundant" QA lead was perfect for Discord moderation. Nobody posted that role. The Commission ruled it was reasonable redeployment.

Redeployment Roulette: Why "Role Gone" Isn't Enough

Operational changes don't magically make redundancies safe. The Fair Work Commission checks three things under Section 389. Mess up one? Employee wins.

First: Role elimination. Business shift, tech change, lost client, fine. But the role must actually vanish.

Second: Real consultation. Not "Hey we're cutting roles, sign here." Modern awards require actual dialogue before decisions lock.

Third: Redeployment check. This kills most indie studios.

Redeployment isn't about identical work. Could that backend dev handle Discord moderation? Could your ex-QA lead triage community bugs? If yes, and it's reasonable, redundancy fails.

Checking Slack for open tasks? Disaster. The Commission sees that as proof you had work. Vacancies don't need formal postings. "Oh I could've done that" is enough for lawsuits.

Your 3-Step Redundancy Triage for Tiny Teams

No lawyers needed. Do this before anyone gets cut:

Vacancy audit

Map every task across your org. Not just "open roles." Look at:
- Community support tickets
- Unfinished feature branches
- Bug backlog triage
- Discord/Slack moderation Document why each task couldn't fit the departing dev. Example: "Mobile dev lacks design skills for UI backlog."
Consultation script

Don't hand redundancy letters first. Try:

"We're restructuring due to [X]. Your role may go away. Can you suggest other work you'd handle? We'll review options by [date]."

Record responses. Silence is evidence they didn't propose alternatives.
Paper trail hacks
- Save Slack channel archives before cuts
- Note dates when tasks were last assigned
- Email: "Confirming no open roles as of [date]" One studio saved itself with a dated GitHub issue backlog showing no mobile work.

When "Redundancy Pay" Isn't What You Owe

Small studios (<15 employees) skip statutory redundancy pay under the Fair Work Act. But watch for:

Tax tricks: Genuine redundancy pay is tax-exempt up to thresholds in the Income Tax Assessment Act 1997. For 2025, 26: $12,524 + $6,264 per service year. Tell devs this upfront. They'll panic less about paychecks.
State traps: In Western Australia, sole traders fall under the Industrial Relations Act 1979 and Minimum Conditions of Employment Act 1993. Redundancy rules differ. Check your state.
Contract overrides: Even small studios owe pay if contracts or awards specify it. Always check before cutting.

Post-Mortem Doc Checklist: Build Your "I Didn't Screw Up" Folder

If sued (or worse, audited), these docs save you:

Business case email: "Why we cut Role X on [date]"
Consultation log: Who spoke, when, what alternatives came up
Vacancy scan: Screenshots of empty role boards and task backlogs
Redeployment analysis: "Why Dev Y couldn't handle Task Z"
Signed offer refusals: If redeployment was proposed and declined

Template separation docs at forms-legal.com/australia/ help. But tweak them for microstudio reality, no "HR department" exists here.

Why This Matters for Indies

Big corps have lawyers for this. Indies don't. One lawsuit can kill a bootstrapped studio.

That mobile dev case wasn't fluke. Small teams assume "no roles = safe." But redeployment includes any task the dev could reasonably do. Even unpaid. Even temporary.

The Fair Work Act 2009 sets the baseline. State laws like the Industrial Relations Act 1979 (WA) or Minimum Conditions of Employment Act 1993 add layers. Miss one, and the Commission hits you with unfair dismissal claims.

The Bottom Line

Genuine redundancy requires proving:

Role vanished (Section 389)
Real consultation happened
Zero redeployment options existed anywhere

For indies, that third point is the killer. Document every task. Consult before deciding. Audit Slack channels before cuts.

Your studio's survival might hinge on whether that ex-backend dev could've triaged community bugs. Don't learn this the hard way.

Check your state's rules at forms-legal.com/australia/ before your next layoff. One template could save your startup.

indiedev #startup #australia #legal #hrtech #gamedev #founders #techlaw #employmentlaw

Related Resources

Browse the full library: Australian Legal Templates

Free legal templates from Forms Legal:

Australian Consumer Law Guarantees in 2026: What Retailers Must Know About Refunds and Repairs

Forms Legal — Sat, 04 Jul 2026 14:01:07 +0000

A customer walks in, three weeks after buying a $650 blender, and says it stopped working. The sales assistant tells her they have a "no refund" policy. She produces her receipt. The assistant shrugs. That exchange costs the retailer more than a refund ever would — because under Schedule 2 of the Competition and Consumer Act 2010 (Cth), that "no refund" sign is not just wrong. It is illegal.

The Australian Consumer Law (ACL) is Schedule 2 of the CCA 2010. It runs nationally; state and territory fair trading legislation mirrors and adopts it. Consumer guarantees under Part 3-2 of the ACL attach automatically to goods and services sold to consumers. You cannot contract out of them, cannot display signage that contradicts them, and cannot charge a restocking fee to sidestep them. The ACCC has significant investigation and enforcement powers, and in 2023 infringement notices under s 134A ACL reached six figures per breach for corporations.

The threshold question: who is a consumer?

Section 3 ACL defines "consumer" in two ways. First, if the price of goods or services is $100,000 or less (raised from $40,000 in October 2022 — a change many businesses still haven't absorbed). Second, even above that price, if the goods are ordinarily acquired for personal, domestic, or household use. A $120,000 caravan sold to a retiree for recreational use is a consumer sale. A $50,000 industrial oven sold to a restaurant probably is not. The distinction matters because consumer guarantees only apply in consumer transactions.

What the guarantees actually require

For goods, the guarantees run across ss 51–59 ACL. Acceptable quality is the big one — s 54 requires goods to be fit for all purposes they are commonly supplied for, free from defects, acceptable in appearance, safe, and durable. Durability is often the contested point. "Acceptable quality" is assessed through the eyes of a reasonable consumer who knows the goods, their price, and any representations made about them. A $30 kettle and a $300 kettle are both required to be of acceptable quality, but what that means differs.

Section 55 adds fit-for-purpose: if a consumer tells the supplier they need goods for a specific purpose and relies on the supplier's skill and judgment, a guarantee that the goods are fit for that purpose attaches. Section 56 covers correspondence with description; s 57 covers compliance with samples. If you operate a service business, ss 60–62 give consumers guarantees that services are rendered with due care and skill, are fit for disclosed purposes, and are completed within a reasonable time when no time is fixed.

Major versus minor failures — the remedies split

This is where most businesses go wrong. Not every defect entitles a consumer to a full refund. The ACL distinguishes major failures from minor ones, and the remedies differ significantly.

A failure is major (s 260 for goods, s 268 for services) if a reasonable consumer would not have bought the goods knowing of the problem, if the goods are significantly different from description or sample, if they are substantially unfit for their common purpose, or if they are unsafe. For a major failure the consumer gets to choose the remedy: they can reject the goods and demand a refund, they can reject and ask for an identical replacement, or they can keep the goods and seek compensation for the reduced value. The choice is theirs, not the retailer's.

For a minor failure the retailer has a chance to fix it first. The supplier can offer repair, replacement, or refund. If the repair isn't completed within a reasonable time — and "reasonable" is measured by what it should take, not by how long the retailer's supply chain is — the consumer can go back and request a different remedy. I've watched this clause sink a hardware supplier who kept promising a repair was coming, for four months, on a $400 power tool. By then the consumer was entitled to a full refund regardless.

What businesses cannot do

Section 64 voids any term of a contract that purports to exclude, restrict, or modify consumer guarantees. This includes "as is" sale clauses in consumer transactions. You can still sell second-hand goods, display goods, or end-of-line stock — but if those goods fail to meet the acceptable quality standard given their condition and price, the guarantee still applies.

The ACCC's position on "no refunds after 30 days" or "exchange only" signs has been consistent: they are misleading conduct under s 29(1)(m) ACL if they suggest consumers have no legal rights to refunds or replacements. The fine exposure for corporations runs up to $50 million under s 224 ACL (as amended by the Treasury Laws Amendment (More Competition, Better Prices) Act 2022).

State-specific overlay on gifts and third parties

One nuance: the ACL consumer guarantee scheme gives rights to the "consumer" who acquired the goods. But ss 267–271 provide that if a manufacturer (not just a retailer) gives an express warranty, that warranty binds the manufacturer. The ACL defines "manufacturer" broadly to include importers and entities that hold themselves out as the manufacturer. A business importing white-label goods from overseas and selling under its own brand name is the "manufacturer" for ACL purposes — it cannot disclaim its way out by pointing at a factory in Shenzhen.

Guarantees for goods generally run for a "reasonable time" rather than a fixed period, though s 271 sets a framework for damages claims against manufacturers up to three years from when the failure became apparent. For services, the due-care-and-skill guarantee (s 60) has no stated expiry.

Practical documentation

Australian retailers, service providers, and online sellers should review their purchase agreements, website terms, and refund policies against the ACL benchmarks. If your current terms of sale say anything like "we reserve the right to refuse refund requests" without carving out ACL rights, you are exposed. A properly drafted sale agreement that acknowledges consumer guarantees while setting out the business's preferred process (contact us first, provide proof of purchase, allow 48 hours for assessment) gives you a clean record if a dispute escalates to a state tribunal.

The template library at https://forms-legal.com/australia/ includes sale-of-goods agreements and service contracts with ACL-compliant language as a starting point. Tailor them to your industry, add your repair and assessment process, and make sure your staff know the difference between a major and a minor failure — because that single distinction drives almost every consumer dispute.

The floor doesn't move

There is no opt-out. Voluntary additional warranties (s 59 ACL) are permitted — you can offer extended coverage on top of the statutory guarantee — but you cannot take away what the ACL grants. Consumer guarantees are a floor, not a ceiling. The practical takeaway for any business selling goods or services to Australian consumers is simple: build your returns and complaints process around the legal entitlements, not around what you wish consumers were entitled to. Get that right and most disputes resolve before they reach the tribunal.

Prenup MVPs: Why Your 'Working' Agreement Fails Like Untested Code

Forms Legal — Thu, 02 Jul 2026 13:00:07 +0000

TL;DR: Most Aussie prenups fail like untested production code, they look solid until real-world stress hits. I've seen devs treat legal docs like READMEs: skimmed, assumed working, then catastrophic failure later. Stop gambling with your financial infrastructure. (68 words)

Why 'Works on My Machine' Agreements Fail

Your binding financial agreement (BFA) compiles locally but crashes in court. Vague clauses are like untyped variables, they seem flexible until the interpreter throws exceptions. Skipping financial disclosure? That's shipping code without checking environment variables. One audit and your whole deployment implodes. I saw a couple lose $1.4M because they treated asset schedules like TODO comments. Courts shred BFAs built on assumptions. The Family Law Act 1975 demands concrete evidence, not hopeful comments in the code.

The Mandatory Dependency Injection

Independent legal advice isn't paperwork. It's your compiler check. Section 90G of the Family Law Act 1975 requires separate lawyers for each party. No exceptions. Using the same firm? Different solicitors in one office? That's like deploying npm packages without license checks, it worked locally but fails compliance. One client reused a lawyer from their wedding. Divorce court voided their BFA. Fifteen years of planning gone. Each lawyer must sign off on tailored advice about advantages and disadvantages. Generic templates break this dependency. Treat it like npm audit, skip it and your financial CI/CD pipeline fails.

Asset Disclosure as Unit Testing

Prove your financial state with deployable evidence. Attach asset schedules like test coverage reports. Hidden rental properties? Undisclosed shares? Those are race conditions waiting to deadlock your settlement. Courts void BFAs over missing $50k assets. Your disclosure must cover:

All property (pre-relationship and acquired)
Liabilities and debts
Superannuation balances
Income streams No stubs. No mocks. Real data. Think of it as writing integration tests against actual databases, not local dev instances. Understating your portfolio is like faking test results. One audit and your "working" agreement fails.

Superannuation Splitting: The Missing API

Your BFA forgot to integrate superannuation splitting. Big mistake. You can't handle super like regular assets. Trying to split it directly in your BFA? That's calling a deprecated API endpoint. The Superannuation Industry (Supervision) Act 1993 requires a separate superannuation agreement or court order. Notify the fund trustee. Follow the spec. Otherwise that component fails silently until divorce hits. I've seen couples assume their BFA covers super, only to discover 30% of their assets weren't actually quarantined. Patch this hole before deployment.

Building Updatable Agreements

Life events demand version control. Your BFA signed at 28 won't handle a $3M business exit at 40. Hardcode "fair and reasonable" clauses and you're begging for undefined behavior. Instead:

Define explicit triggers (e.g., "Review after birth of first child")
Use modular clauses for new asset classes
Store previous versions like Git tags One couple added a clause triggering renegotiation if either party's net worth grew >200%. Smart branching. Others execute new agreements for major milestones, like cutting a release candidate. Both work. What fails? Static documents. The Family Law Act 1975 allows setting aside BFAs for changed circumstances causing hardship. Treat yours like semantic versioning: v1.0 for pre-kids, v2.0 post-inheritance.

When to Fork Your BFA

Relationship incidents need hotfixes. Spot these production alerts:

New children arrive (BFA must address child-related hardship)
One party inherits significant assets
Major net worth shifts (>50% change)
Relocating to Western Australia (more on this below) Ignoring them is like ignoring dependency vulnerabilities. Courts void BFAs that don't adapt. Under section 90K of the Family Law Act 1975, hardship from unanticipated circumstances is grounds for setting aside agreements. Don't let your financial infrastructure run on stale config. Fork early. Merge changes cleanly. Document every decision.

Western Australia's Special Case

Moving to WA? Your Commonwealth BFA might be a broken build. De facto couples there operate under the Family Court Act 1997, not the Family Law Act 1975. Different rules. Different validation. One couple signed a BFA in NSW, moved to Perth, then divorced. WA courts ignored their agreement. Why? They hadn't met state-specific requirements. Always check your deployment region. WA isn't just another availability zone, it's a separate cloud provider. Verify jurisdiction early.

Why Your Lawyer Isn't a Linter

Signing before the wedding with last-minute pressure? That's deploying on Fridays. Courts scrutinize timing, especially under emotional duress. An agreement signed two days pre-wedding is high-risk code. Section 90K lists fraud and unconscionable conduct as grounds for voiding BFAs. Rushed execution screams "undue influence." Do this right:

Start drafting 6+ months out
Exchange disclosure schedules early
Get legal advice before drafting (not after)
Never use the same law firm Treat it like staging environment validation. No hotfixes for wedding-day panic.

The One Thing That Never Fails

Independent legal advice. Period. Section 90UJ of the Family Law Act 1975 enforces this for de facto BFAs. No lawyer signatures? Your agreement is technical debt waiting to compound. It's not about trust, it's about proof. Like signed commits in Git. Without it, courts treat your BFA as unverified code. One client skipped this to "save time." Cost them $800k in legal fees fighting to uphold a void agreement. Don't be that dev.

Stop treating legal docs like throwaway prototypes. Your financial infrastructure needs the same rigor as your production systems. Test disclosures like unit tests. Handle superannuation like third-party APIs. Version agreements like critical dependencies. Find templates at forms-legal.com/australia to see standard structures, but remember: two real lawyers must sign off. No shortcuts. Your future self will thank you when the relationship CI pipeline actually passes.

Related Resources

Browse the full library: Australian Legal Templates

Free legal templates from Forms Legal:

Los 5 Trampas Ocultas al Constituir tu SRL en Argentina (y Cómo Evitarlas)

Forms Legal — Tue, 30 Jun 2026 06:42:02 +0000

TL;DR: Me rechazaron la SRL tres veces por errores tontos en el contrato. Acá las 5 trampas que nadie menciona, incluyendo cómo redactar el objeto social para apps sin que te corrijan. (Spoiler: 'desarrollo de software' no alcanza). Si quieres evitar 8 semanas de trámites, léelo antes de firmar.

Como indie que lanzó dos startups, vi cómo amigos perdían plata por cláusulas mal armadas. Esta no es una guía legal: es el memo que me hubiera salvado de pagar abogados innecesarios.

La trampa del objeto social: cuando "desarrollo de software" te devuelve a la casilla uno

Mi primer rechazo en la IGJ fue patético. Puse "desarrollo de software" en el objeto social. Error. La Ley 19.550 exige que el objeto sea preciso y factible. "Desarrollo de software" es tan vago como decir "hacer cosas en internet".

Un amigo quiso registrar una app de delivery con "gestión de negocios online". Observación de la IGJ: "Actividad no específica. Detalle procesos y destinatarios".

Cómo lo arreglé para mi app logística:
Plataforma de gestión logística B2B con API para comercios minoristas

Fijate la diferencia:

Menciona el modelo de negocio: B2B
Especifica la tecnología: API
Define el cliente: comercios minoristas
Evita términos genéricos: Nada de "soluciones digitales"

La IGJ rechaza objetos que no permitan identificar qué vende tu empresa. Si tu app es para restaurantes, di "gestión de pedidos para establecimientos gastronómicos". Nada más.

Integración del capital: el freno imprevisto cuando necesitas facturar YA

Aquí me costó dos meses perder clientes. La Ley 19.550 exige integrar 25% del capital en efectivo al abrir la cuenta bancaria transitoria. Pero para abrir esa cuenta necesitas la constancia de presentación ante la IGJ. Y sin CUIT, no puedes emitir facturas.

El círculo vicioso:

Necesitas facturar para tener ingresos
Para facturar necesitas CUIT
Para CUIT necesitas estar constituido
Para constituirte necesitas capital integrado
Pero sin facturas... ¡no generas capital!

Mi solución práctica:

Negocia con clientes un anticipo bajo recibo de depósito (no factura)
Usa tu cuenta personal para cobrar los primeros pagos
Deposita esos fondos directo al 25% requerido

En mi segunda startup hice esto y reduje el tiempo de inactividad a 10 días. La clave: tener claro que no puedes operar legalmente hasta que el capital esté integrado. Planifica tus primeros ingresos en consecuencia.

SAS vs SRL: no elijas el formato moderno por modorra

La Ley 27 introdujo la SAS como salvación para indie devs. Constitución en 24 horas, trámites digitales, costos bajos. ¿Suena perfecto? Para mi primera app sí. Para un proyecto posterior... no tanto.

Cuando SÍ conviene la SAS:

Tu proyecto es 100% digital
No necesitas licencias especiales
Los socios son 1-5 personas confiables
Quieres agilidad sobre formalismos

Cuando te jode más:

Trabajas con bancos tradicionales (muchos exigen SRL)
Necesitas licencias municipales (algunas no aceptan SAS)
Tienes socios que podrían vender sus cuotas

En mi experiencia: si tu startup busca inversión ángel, la SAS atrae más. Si vendes a Pymes con procesos lentos, la SRL genera más confianza. La Ley 26 actualizó reglas pero no eliminó esta brecha práctica.

Gerentes que firman en caliente: cómo US$15k salen de tu billetera

Mi peor error fue nombrar gerente a un socio sin definir facultades claras. La Ley 19.550 es contundente: si un gerente firma fuera de sus facultades, responde personalmente. Artículo 58 LGS.

Un amigo firmó un contrato en USD para una API sin autorización expresa. El cliente demandó por incumplimiento. Como el contrato no detallaba sus límites:

La sociedad no validó el contrato
El gerente tuvo que pagar US$15k de su bolsillo
El cliente ganó la demanda por "tercero de buena fe"

Cómo evitarlo HOY:

En el contrato constitutivo, define EXACTAMENTE qué puede firmar
Especifica montos máximos por transacción
Incluye cláusula de "requiere aprobación societaria para X"

Ejemplo útil:
El gerente podrá firmar contratos hasta ARS 500.000 sin aprobación. Para montos superiores, requerirá acuerdo de socios con 70% de las cuotas.

Sin esto, cualquier firma es una bomba de tiempo.

Transferir cuotas: perder el control por una cláusula mágica faltante

Cuando un socio quiere vender sus cuotas, la SRL tiene una ventaja sobre la SA: puedes restringir la transmisión. Pero si no pones cláusulas específicas en el contrato, cualquier socio puede vender a quien quiera.

La Ley 19.550 permite dos mecanismos clave:

Derecho de preferencia: Los demás socios tienen 30 días para igualar la oferta
Cláusula de aprobación: Se requiere aval de socios con X% del capital

Mi error: asumí que "los socios deciden" bastaba. En la práctica, sin porcentajes definidos:

Un socio vendió sus cuotas a un competidor
Los demás no pudieron bloquearlo
Perdimos el control operativo en 3 meses

La solución que ahora uso:
Ninguna transmisión de cuotas será válida sin aprobación de socios que representen al menos el 60% del capital social. Los socios tendrán derecho de adquisición preferente por 20 días corridos.

Sin esta cláusula, tu SRL puede convertirse en un barco sin capitán.

El cierre de ejercicio: la trampa fiscal que seca tu flujo

El artículo 250 de la LGS fija el 31 de diciembre como fecha automática de cierre. Pero si constituyes tu SRL en junio, tu primer ejercicio dura solo 6 meses. Y debes cerrar libros y pagar impuestos igual.

Mi segunda startup nació en agosto 2025. En enero 2026:

Tenía que presentar balances ante IGJ
Pagué ganancias por 5 meses de operación
Mi flujo se congeló en el peor momento

La solución que encontré con mi contador:

Solicita prórroga en la constitución: Puedes fijar otra fecha en el contrato (ej: 30 de junio)
Alinea con tu modelo de negocio: Si vendes temporadales, cierra después de tu peak

Cómo hacerlo:

En el contrato constitutivo, especifica: El ejercicio económico finalizará el 30 de junio de cada año
Verifica que no choque con obligaciones impositivas
Notifícalo al fisco al obtener CUIT

En mi caso, pasar a cierre en junio me dio 8 meses extra de flujo. Dinero que usé para escalar antes de impuestos.

Checklist express: los 3 documentos que debés validar HOY

No esperes a la IGJ. Valida esto antes de firmar:

Objeto social con verbos de acción

Reemplaza "desarrollo de software" por Plataforma SaaS para gestión de inventarios en tiempo real mediante integración con ERP existentes. Incluye modelo de negocio y cliente.
Cláusula de facultades del gerente

Define montos máximos y tipos de contratos. Ejemplo: El gerente podrá contratar servicios tecnológicos hasta US$10.000 sin aprobación societaria.
Mecanismo de transmisión de cuotas

Especifica porcentajes y plazos. Nunca digas "según decisión de socios". Usa: Requiere aprobación del 75% del capital social y derecho de preferencia por 15 días.

Saltarte esto te costará 4-8 semanas de trámites. Yo lo aprendí a las malas con tres rechazos. Los modelos listos para usar están en forms-legal.com con todos los campos precompletados para evitar estas trampas.

¿Todavía pensás en contratar un abogado para lo básico? Descargá los formularios legales validados por especialistas y enfocate en construir tu producto. Tu futuro yo te lo agradecerá.

ar-legal srl startup indie-hacks

Related Resources

Browse the full library: Plantillas Legales Argentina

Free legal templates from Forms Legal:

Contrato de trabajo y liquidación final en Argentina: lo que el empleador no siempre te dice en 2026

Forms Legal — Sat, 27 Jun 2026 15:30:03 +0000

El último día de trabajo llegó, firmás el papel que te presentan y cobrás lo que te pagan. Después, con la plata ya gastada, un colega te dice: "¿Recibiste el proporcional de vacaciones no gozadas?" Y ahí empieza el problema. La liquidación final es uno de los rubros donde más diferencias injustificadas aparecen, porque la mayoría de los trabajadores no sabe exactamente qué les corresponde.

La Ley de Contrato de Trabajo 20.744 —la LCT— regula cada centavo de esa liquidación, pero el diablo está en los detalles. Veamos qué integra la liquidación al concluir un contrato de trabajo, sea por renuncia, acuerdo o despido.

El salario del mes en curso es lo primero: los días trabajados hasta la extinción, calculados sobre el sueldo mensual dividido por 25 si el convenio no dice otra cosa, o sobre los días hábiles según la práctica del empleador. Ninguna empresa puede retener eso.

Luego viene el sueldo anual complementario proporcional (SAC, popularmente "aguinaldo"). El artículo 122 de la LCT establece que el SAC se paga en dos cuotas —junio y diciembre— pero al desvincularse se liquida la parte proporcional del semestre en curso. Si renunciás en marzo, te corresponde el SAC de enero, febrero y marzo. La fórmula es sencilla: mitad del mejor sueldo del semestre dividido por 6, multiplicado por los meses proporcionales. Muchos empleadores lo calculan sobre el sueldo base y olvidan las horas extra habituales o los tickets canasta que integran remuneración; eso es un error que puede reclamarse.

Las vacaciones proporcionales no gozadas también se liquidan siempre, sin importar la causa de egreso. El artículo 156 LCT es claro: al momento de la extinción, el trabajador tiene derecho a percibir una indemnización equivalente al salario correspondiente al período de vacaciones que le hubiere correspondido ese año, en proporción a los meses trabajados. Si el trabajador tiene entre 5 y 10 años de antigüedad, le corresponden 21 días hábiles de vacaciones anuales; si llevaba, digamos, 8 meses del año trabajados, recibirá 8/12 de esos 21 días. Un detalle que se pasa por alto: los días de vacaciones se calculan en días hábiles, pero la remuneración diaria se obtiene dividiendo el sueldo mensual por 25.

El preaviso merece un párrafo aparte. Si el empleador no otorgó el plazo de preaviso establecido en el artículo 231 LCT —15 días para personal con menos de 3 meses, 30 días de uno a cinco años, 60 días con más de cinco años— debe abonar la indemnización sustitutiva. Eso incluye el SAC proporcional sobre ese período de preaviso. Cuando la empresa le dice al trabajador "ya podés irte" sin respetar el plazo, el preaviso se integra en la liquidación como un rubro indemnizatorio.

Acá quiero detenerme en algo que veo repetidamente: la empresa hace firmar el recibo de haberes final con la leyenda "nada más me adeuda". ¿Eso cierra el reclamo? Depende. Si el trabajador firmó bajo presión, en el mismo momento del despido, sin tiempo para verificar los montos, hay doctrina y jurisprudencia que sostiene que esa conformidad no es válida como finiquito si los rubros no se calcularon correctamente. En cambio, un acuerdo homologado ante el Ministerio de Trabajo sí tiene efecto liberatorio pleno, según el artículo 15 LCT. La diferencia no es menor.

¿Qué pasa con los conceptos no remunerativos? Varios convenios colectivos establecen sumas "no remunerativas" o "en negro" que muchos empleadores no incluyen en la base de cálculo del SAC ni de la liquidación final. La Corte Suprema de Justicia de la Nación viene fallando reiteradamente que esas cláusulas son inconstitucionales cuando el concepto tiene carácter contraprestativo. En otras palabras: si te lo pagan todos los meses por trabajar, es remuneración, independientemente del nombre que le ponga el convenio. Incluirlo en la base cambia los números.

La plantilla de liquidación final debe detallar cada rubro por separado. Un recibo que diga sólo "liquidación final $X" sin abrir los conceptos es una señal de alerta. El trabajador tiene derecho a pedir el detalle, y si la empresa no lo brinda, puede recurrir al Servicio de Conciliación Laboral Obligatoria (SECLO) en CABA, o a las delegaciones del Ministerio de Trabajo en las provincias, antes de iniciar un juicio laboral.

¿Cómo se calcula la remuneración diaria para las vacaciones? Muchos empleadores toman el sueldo mensual y lo dividen por 30, que parece lógico. Pero el artículo 155 LCT ordena dividir por 25. La diferencia parece menor —un 17%— pero sobre un sueldo medio aplicado a 15 o 20 días de vacaciones proporcionales, puede ser miles de pesos. Vale la pena hacer el cálculo de las dos maneras antes de firmar el recibo.

Un tema que se volvió relevante con la inflación alta: los intereses sobre las sumas adeudadas. Si el empleador demora el pago de la liquidación final más allá del plazo legal, se generan intereses moratorios. La tasa que aplican los tribunales laborales en Argentina es la activa del Banco de la Nación Argentina desde el fallo plenario "Calcagno" de la Cámara Nacional de Apelaciones del Trabajo. Con inflación persistente, el monto de los intereses puede igualar o superar el capital original si el reclamo se resuelve años después.

El plazo para impugnar no es indefinido. El artículo 256 LCT fija una prescripción de dos años para los créditos laborales. El plazo corre desde que el crédito se tornó exigible —generalmente, la fecha de extinción del contrato. No esperes: si creés que tu liquidación está mal calculada, consultá a un abogado laboralista cuanto antes.

Una aclaración práctica sobre las multas: si el empleador no abona la liquidación final dentro de los cuatro días hábiles de extinguido el contrato (artículo 128 LCT y la ley 25.013 en lo pertinente), el trabajador puede reclamar la mora. El artículo 2 de la ley 25.323 establece una duplicación de la indemnización por despido cuando el empleador, fehacientemente intimado, no la abona. Aunque esa duplicación aplica principalmente en despidos, la demora en la liquidación final puede generar intereses y costas en un proceso judicial.

Para quienes están en ese momento de transición laboral y quieren verificar sus cuentas antes de firmar, en https://forms-legal.com/es/argentina/ encontrarán modelos de recibo de liquidación final y documentos de extinción del contrato de trabajo que pueden usar como referencia para corroborar que los rubros están completos.

¿Renuncia o acuerdo rescisorio? Esta elección también impacta en la liquidación. La renuncia no genera derecho a indemnización por antigüedad ni sustitutiva de preaviso. El acuerdo rescisorio del artículo 241 LCT, en cambio, puede negociarse con condiciones distintas, incluyendo el pago de una suma voluntaria que, si se homologa, no tributa aportes ni contribuciones en la proporción indemnizatoria. Muchos trabajadores renuncian sin saber que podían negociar un acuerdo mejor.

¿Qué dice el recibo tiene que decir? El recibo de pago de la liquidación final debe discriminar, como mínimo: período liquidado, remuneración base, horas extra, SAC proporcional, vacaciones proporcionales, preaviso —si corresponde— y los descuentos de aportes previsionales y de obra social aplicados sobre los rubros remunerativos. Los rubros indemnizatorios no llevan aportes ni retenciones de impuesto a las ganancias en la proporción legal. Si el recibo no discrimina y mezcla todo como "liquidación final", la empresa está incumpliendo el artículo 140 LCT, que exige la especificación de los rubros en el recibo de haberes.

Hay otro punto que pocas personas conocen: si el trabajador no retiró el certificado de trabajo y el certificado de aportes y contribuciones (artículo 80 LCT) dentro del plazo, puede intimar al empleador. Ante la negativa o la demora injustificada, procede una indemnización adicional equivalente a tres salarios. Esos certificados son necesarios para acreditar la antigüedad ante futuros empleadores y para gestionar beneficios previsionales.

El contrato de trabajo en Argentina es, en su médula, un contrato protectorio. La LCT parte del principio de que hay una desigualdad estructural entre empleador y empleado, y por eso establece normas de orden público que no pueden ser renunciadas. La liquidación final es el último eslabón de esa protección. Conocerla no te convierte en litigante, te convierte en alguien que sabe lo que firmó.

Why Your Will Needs a Codicil Like Your Code Needs a PR – Not a Full Rebuild

Forms Legal — Thu, 25 Jun 2026 07:30:13 +0000

TL;DR: Skip rewriting your entire will for small tweaks, a codicil is your estate's hotfix. But mess up the 'merge' (like invalid witnesses) and your executors get a production-level bug. As a dev who patched my will after inheriting crypto, here's how I avoided probate hell without a lawyer. Never assume 'just a signature' is safe.

Your Will Is Legacy Code (And That's Okay)

My grandad left me a cold Bitcoin wallet. His 1998 will named "my son's children" as residuary beneficiaries. Problem: I'm the only son, but my kids weren't born until 2010. Rewriting his entire will felt like refactoring spaghetti COBOL for a one-line config change.

Codicils exist for this exact scenario. They're pull requests for your estate plan, targeted patches instead of full rebuilds. Under the Wills Act 1837, you can surgically update beneficiaries or executors without nuking your original document.

Most devs accept small PRs faster than massive refactor PRs. Same with probate courts. Executors process clean codicils quicker than entirely new wills. But skip the witness requirements? That's like merging without CI checks. Disaster guaranteed.

Codicil = Pull Request Checklist

Think of your codicil as a feature branch. Section 9 of the Wills Act 1837 defines the mandatory merge criteria:

Signed by you (the testator) Like committing your changes locally.
Two witnesses present simultaneously Non-negotiable code review. Both must watch you sign at the same time. ⚠️ Biggest failure point: Witnesses signing separately like async code reviews. Invalidates everything.
Witnesses attest in your presence They confirm "yes, this is your signature", no need to understand the clauses.

I added my crypto wallet address via codicil last year. Used two coworkers as witnesses. Made them watch me sign together, no "I'll sign later" nonsense. Broke one coffee run to get them both in the room. Worth it.

Real dev analogy: Invalid witnesses = deploying with broken CI checks because "it worked locally." Probate registry rejects your "PR" outright. Your changes vanish. Family fights over legacy code (I mean, assets).

When Not to Merge: 3 Scenarios Where Codicils Cause Merge Conflicts

Codicils fail when your estate's architecture shifts. Don't force a patch where you need a rebuild:

Multiple changes Trying to cram 5 beneficiary swaps into one codicil? That's like one PR fixing 10 unrelated bugs. Messy. High chance of conflicts. If you need over two tweaks, scrap the codicil. Draft a new will. The Administration of Estates Act 1925 hates ambiguity, partial intestacy crashes your deployment.
Divorce or marriage Section 18 of the Wills Act 1837 revokes wills on marriage. A codicil can't resurrect this. Section 18A (via Law Reform Act 1995) voids ex-spouse gifts post-divorce but leaves executor chaos. Rebuild the will. Don't risk a merge conflict where your ex still "owns" executor rights.
Residuary estate changes Tweaking "everything else" clauses? Dangerous. One typo = partial intestacy. Administering residual assets under Intestacy Rules (Administration of Estates Act 1925) is like running untested legacy code. New will only.

Storing Your Patch Safely

git commit -m "added BTC wallet" won't cut it for probate. HM Courts and Tribunals Service demand physical originals.

Store your codicil taped to your original will. Not in a different drawer. Not "somewhere safe."

My near-disaster: I kept the codicil in my desk, will in a fireproof box. When my uncle died, his executor spent 3 weeks hunting the codicil. Almost missed the probate deadline. Now I use Certainty (National Will Register), it's like GitHub Repositories for estate docs. Free registration.

Photocopies? Rejected. Probate needs wet ink signatures witnessed live. No cloud storage substitutes. Treat it like your master private key.

DIY Codicil Trap: Free Templates That Work (and Ones That Nuke Your Repo)

I tested 7 free codicil templates. Four were time bombs:

The "I change everything" template Vague phrases like "I alter prior provisions." Ambiguous. Probate courts treat this like undefined variables, they ignore it. Stick to specific clauses: "Replace Section 3.1 beneficiary from [Name] to [Crypto Wallet Address]."
The "witness exemption" template Claims "digital signatures accepted." False. Section 9 demands physical witnesses. Always.
The "unregistered" template Omits your will date. Critical. Codicils must cite "the will dated [X]." Otherwise, executors can't link them. Like a PR without a base branch.

Use only templates matching Section 9 requirements. The one I used from forms-legal.com had:

"This codicil amends my will dated [DATE], specifically altering Clause [NUMBER] to read: [EXACT TEXT]."

Clear. Patch-like. No fluff.

Your Executor Is the Ops Team

Executors deploy your estate plan. Ambiguous clauses crash production.

My aunt's will said: "My son gets the house." Her son died before her. Who gets it? The will didn't name contingent beneficiaries. Result: 11 months of probate hell under Intestacy Rules. Assets frozen. Like ops trying to deploy config with missing env vars.

Fix this now:

Always name backup beneficiaries ("If [Name] predeceases me, [New Name] inherits").
Specify exactly which asset ("the Bitcoin wallet ending in ...a1b2c3").
Update executors if moving countries (Kenya's Succession Act handles foreign assets differently).

Never write "my cryptocurrency", specify chains, wallets, recovery methods. Assume your executor knows ls but not bitcoin-cli.

Why I Bothered Learning This

Lost $12k in Ethereum after my cousin's death. His DIY codicil had witnesses who were also beneficiaries (void under Section 15). Probate rejected it. Assets reverted to intestacy. His kids got nothing.

Codicils work when you treat them like production code:

Mandatory witness review
Atomic changes
Stored with original
Clear patch notes

Skip the ceremony, and you're handing executors a corrupted tarball. They'll spend months (and thousands) unpacking it.

Your move: Grab a verified codicil template. Patch your will. Store it physically with the original. Then sleep knowing your crypto won't vanish in probate.

Need a solid starting point? I used this codicil template for England and Wales. It nails Section 9 compliance without legalese.

legaltech #api #kenya

Related Resources

Browse the full library: UK Legal Templates

Free legal templates from Forms Legal: