When a contract says that something "will be treated as" something else, it is doing more than describing reality. It is creating an agreed fiction: the parties are deciding, between themselves, how a fact, event or amount is to be classified for the purposes of their agreement, even where that classification would not apply outside the contract. A late payment can be "treated as" a material breach. Information can be "treated as" confidential whether or not it is marked as such. An overpayment can be "treated as" a credit against future invoices.
These clauses are common in Australian business contracts, and they matter because the classification they impose usually unlocks something: a right to suspend services, a duty of confidentiality, a set-off, or a termination right. This guide covers:
- What the clause does: how a "treated as" provision operates as a rule of classification inside the contract.
- Its parts: the trigger, the deemed character and the consequence, and why the consequence is where the risk sits.
- Its limits: where the fiction stops, including consumer law, employment law and tax.
- The misconceptions: the assumptions that cause the most trouble in practice.
What a "Treated As" Clause Does
A "treated as" clause, sometimes called a deeming clause, is a rule of classification that the parties agree will apply within the four corners of their contract. The older drafting habit uses the word "deem", but "treated as", "taken to be" and "for the purposes of this agreement" all do the same work. The clause takes an event, amount or piece of information and gives it a status the parties have chosen, rather than the status it would otherwise have.
Courts give effect to this agreed fiction when the wording is clear, because Australian contract law starts from the proposition that parties are free to allocate risk and consequences between themselves as they see fit. That is how a contract can say that a payment arriving three days late "is" a material breach, or that unmarked information "is" confidential, and have those statements operate as agreed. The fiction binds the parties to each other.
Two boundaries apply. First, the clause is read in the context of the whole contract, so it must work with the definitions, payment terms, termination clause and remedies around it. Second, the parties cannot contract out of mandatory law. A clause can reclassify an event between the parties, but it cannot change what the law itself requires, which is a point that comes back repeatedly below.
The Three Parts of a "Treated As" Clause
Every workable "treated as" clause has three parts, and it pays to identify each one when you read a contract.
The Trigger
The trigger is the fact, event, amount or information being classified: a late invoice, an overpayment, information disclosed during negotiations, an absence from work. If the trigger is vague, for example "any delay", the clause is hard to apply and easier to dispute. The more precisely the trigger is described, the less room there is for argument about whether the clause has been engaged at all.
The Deemed Character
The deemed character is the label or status the parties attach: "material breach", "confidential information", "a credit", "paid leave". The label is the bridge between the trigger and the consequences. It is also the point where drafting choices are easiest to copy from one contract to another without thinking about what the label actually means in this agreement.
The Consequence
The consequence is what the label unlocks. A "material breach" label typically engages the termination and remedies clauses. A "confidential" label creates obligations about storage, access and disclosure. A "credit" label changes how money moves between the parties, and a "paid leave" label changes what an employee is entitled to.
The consequence is where the risk lives. Two contracts can use identical trigger and label language and produce very different outcomes, because everything depends on what the rest of the contract does with the label. That is why a "treated as" clause can never be read in isolation. The right question is not "what does the clause say" but "what does it unlock for each party".
The Scope of the Fiction: Between the Parties Only
A "treated as" clause binds the parties to each other. It does not bind the Australian Taxation Office, a court, a regulator or anyone else who is not a party to the agreement. This is the boundary that catches businesses out.
Under the Australian Consumer Law (ACL), which is Schedule 2 of the Competition and Consumer Act 2010 (Cth), a term of a contract is void to the extent that it purports to exclude, restrict or modify the consumer guarantees (s 64 of the ACL). A clause that says a faulty product will be "treated as" sold with all faults cannot displace the guarantees that apply when goods are supplied to consumers. In the same schedule, an unfair term in a standard form consumer contract or small business contract is void, and proposing, applying or relying on one can now attract a pecuniary penalty (s 23 of the ACL). Labelling a refund as "a gesture of goodwill" in the contract does not stop those provisions applying.
The same logic runs through employment law. The National Employment Standards under the Fair Work Act 2009 (Cth) are minimum standards that cannot be excluded by a modern award or enterprise agreement (s 55), and the standards themselves cannot be displaced (s 61). If an employment document says an amount will be "treated as" a deduction from wages, the deduction still has to satisfy the permitted deductions rules in s 324 of the Fair Work Act 2009 (Cth), which require, among other things, written authorisation that is principally for the employee's benefit.
Tax operates the same way. The parties can agree how a payment will be treated between themselves, but the character of a payment for tax purposes is decided by legislation and the substance of the arrangement, not by a label in a contract. If a clause touches tax or GST, the practical answer comes from the tax law and the specific facts, and it is worth checking with an accountant before relying on the wording.
A Worked Example: The Design Studio and the Late-Paying Client
Take a Melbourne design studio that signs a services agreement with a retailer. The agreement contains three "treated as" clauses. The first says any invoice not paid within 30 days "will be treated as a material breach". The second says all information disclosed during the project "will be treated as confidential, whether or not marked as confidential". The third says any overpayment "will be treated as a credit against future invoices".
The first clause looks powerful for the studio, but its real effect depends on the termination clause. If the termination clause allows termination for a material breach only after written notice and a 14 day cure period, then the deeming clause does not let the studio walk away on the day the payment becomes late. It simply classifies the lateness so that the termination machinery can start. If the two clauses do not fit together, the studio may believe it has a right to terminate that the contract never actually gave it. That mismatch is where disputes begin.
The second clause works both ways. It protects the studio's own concepts and price lists, but it also means the studio must store and handle the retailer's information as confidential, with all the practical obligations that come with that duty. The third clause changes cash flow: the studio forgives the overpayment in favour of future credit, which is workable only if the studio's invoicing system can track and apply credits reliably.
None of these clauses changes what the law itself requires. If the retailer is a consumer, the studio's obligations under the consumer guarantees continue to apply regardless of how the agreement classifies delays or defects. The clauses allocate consequences between the two businesses, and that is their only job.
Common Misconceptions
Three assumptions cause most of the trouble in practice:
-
"If the contract says it, the law treats it that way": This is wrong. Contractual classification works between the parties, and only where the law allows. Consumer guarantees cannot be excluded (s 64 of the ACL), unfair terms in standard form contracts are void (s 23 of the ACL), and National Employment Standards cannot be displaced (s 55 of the Fair Work Act 2009 (Cth)). A clause that re-labels a legal obligation does not remove the obligation. At most it allocates the agreed consequences between the parties, and sometimes it is simply void.
-
"Deeming something a material breach means we can terminate immediately": At common law, a breach entitles the innocent party to terminate only where it is serious enough to deprive them of substantially the whole benefit of the contract (Koompahtoo Local Aboriginal Land Council v Sanpine Pty Ltd [2007] HCA 61). A "treated as material breach" clause can elevate a lesser breach for the purposes of the agreement, but it operates through the contract's own termination machinery, including any notice and cure steps. And in a standard form consumer or small business contract, a clause that brands almost any conduct a material breach may itself be vulnerable as an unfair term under s 23 of the ACL, because it can create a significant imbalance in the parties' rights.
-
"The label decides how a court or the ATO treats the payment": Courts look at substance. A stipulated sum labelled "liquidated damages" is still a penalty, and unenforceable beyond the actual loss, if it is extravagant or unconscionable compared with the greatest loss that could conceivably be proved (Andrews v Australia and New Zealand Banking Group Ltd [2012] HCA 30). The label is a starting point, not a guarantee. The same is true for tax character, which follows the legislation and the substance of the arrangement rather than the words the parties chose.
When a "Treated As" Clause Needs a Lawyer's Eye
A contract lawyer reviewing treatment language does not stop at the clause itself. They trace each "treated as" through the rest of the document: does the definition of "material breach" line up with the termination clause, including any notice and cure steps? Does the confidentiality clause carry carve-outs for information that is already public or independently developed? Does the credit mechanism sit consistently with the set-off clause and the invoicing process? Does any of the treatment language collide with mandatory law under the ACL, the Fair Work system, privacy law or tax?
The value for a business is practical. A short review before signing is far cheaper than a dispute after a trigger fires. Where treatment language is complex or the agreement is high value, a focused review can identify cash flow surprises, unintended confidentiality obligations and termination rights that are not what they first appear. A lawyer can also propose qualifiers and carve-outs, such as "unless otherwise agreed in writing", that keep a rigid treatment clause from producing an outcome nobody intended.
The Question to Ask Before You Sign
The most expensive misconception in this area is the assumption that the label is the outcome. A clause that says late payment "will be treated as a material breach" does not, by itself, tell you what the other party can do next. What matters is what the termination clause, the remedies clause and the law actually deliver when the trigger fires.
So when you next review a contract, ask a single question about every "treated as" clause: what does each party gain when this trigger occurs, and can my business deliver that? If the clause unlocks a termination right for the other party, know the notice and cure steps that apply. If it imposes a confidentiality duty on you, know what you must actually do. If it changes how money moves, check that your systems can track it. If you cannot trace a "treated as" clause to a clear consequence, tighten the wording before you sign, because the contract will not read itself more generously later.