Software Development Agreement (Australia)

A Software Development Agreement in Australia is a legally binding written instrument.

Under section 35(6) of the Copyright Act 1968 (Cth), copyright in software created by an independent contractor — including computer programs, source code, object code, and related documentation — belongs to the contractor by default, not to the client who commissioned and paid for the work. This default position surprises many clients and is a frequent source of disputes in the Federal Court of Australia. To transfer copyright ownership to the client, the parties must execute a written assignment that complies with section 196 of the Copyright Act 1968 (Cth), which requires the assignment to be in writing and signed by the assignor. An oral agreement or informal understanding is insufficient. The forms-legal.com Software Development Agreement (Australia) template includes an express copyright assignment clause so the client obtains full ownership upon payment of the agreed fee.

Patent rights in any novel technical inventions arising from the software development project are governed by the Patents Act 1990 (Cth), administered by IP Australia. Where the development may give rise to a patentable invention — for example, a novel algorithm, data processing method, or technical process — the agreement should address whether the patent rights are assigned to the client or retained by the developer under a licensing arrangement.

The Australian Consumer Law (ACL), being Schedule 2 to the Competition and Consumer Act 2010 (Cth) and enforced by the Australian Competition and Consumer Commission (ACCC), imposes mandatory consumer guarantees on software development services. Under section 60 of the ACL, there is a guarantee that services will be rendered with due care and skill. Under section 61, there is a guarantee that services will be fit for the particular purpose disclosed by the client. These guarantees cannot be excluded, restricted, or modified by a contract term under section 64 of the ACL. Since November 2023, the unfair contract terms regime under sections 23 to 28 of the ACL also applies to standard form software development contracts with small businesses.

Privacy obligations under the Privacy Act 1988 (Cth) and the Australian Privacy Principles (APPs), enforced by the Office of the Australian Information Commissioner (OAIC), apply where the software project involves personal information about individuals. APP 11 requires reasonable security safeguards, and APP 8 governs cross-border disclosure. GST applies to software development services under the A New Tax System (Goods and Services Tax) Act 1999 (Cth), and payment terms should specify whether prices are inclusive or exclusive of GST. The agreement uses Australian business conventions including ABN identification, AUD pricing, DD/MM/YYYY date formatting, and governing law of the relevant Australian state or territory. Section 127 of the Corporations Act 2001 (Cth) governs execution of documents by companies, and the agreement should specify whether each party will execute under section 127 or under a power of attorney. The Australian Taxation Office (ATO) administers GST under the A New Tax System (Goods and Services Tax) Act 1999 (Cth), and milestone invoices must be valid tax invoices to enable the recipient to claim input tax credits. The Federal Court of Australia and the Supreme Courts of each state have jurisdiction over IP and contractual disputes arising from software development projects.

A Software Development Agreement should be signed before any development work commences whenever a business commissions bespoke software from an independent developer or software house in Australia. The agreement is equally important whether the developer is a sole trader, a small studio, or a large Pty Ltd company.

Without a written agreement, the default position under section 35(6) of the Copyright Act 1968 (Cth) means the developer owns all IP in the software — even software the client has paid for in full. The client would then have no right to modify, resell, or sublicence the software without the developer's consent. Resolving these disputes before the Federal Court of Australia or the state Supreme Courts is costly and disruptive. A written agreement eliminates this risk by specifying ownership upfront.

The agreement is particularly important where the software will handle personal information subject to the Privacy Act 1988 (Cth). In that case, the developer will be handling personal information on behalf of the client during the development process, triggering obligations under the Australian Privacy Principles. The agreement should require the developer to handle personal information in accordance with APP 11 (security), APP 8 (cross-border disclosure for offshore developers), and to notify the client immediately of any suspected data breach. Where the software is for a financial services business regulated by the Australian Securities and Investments Commission (ASIC) under the Corporations Act 2001 (Cth), or for a healthcare provider regulated under the Health Practitioner Regulation National Law, additional sector-specific data handling and security requirements will apply.

The agreement should also be signed when engaging offshore developers, as Australian law — including the Copyright Act 1968 (Cth) and the ACL — can still apply to the transaction where the client is based in Australia. APP 8 of the Privacy Act 1988 (Cth) requires the client to take reasonable steps to ensure any offshore developer who handles personal information treats it in a manner consistent with the APPs. Where the offshore developer cannot satisfy this requirement, the client remains accountable to the OAIC for any privacy breach by the offshore party.

For software projects that will be commercially significant — for example, a SaaS platform, a mobile application distributed through the Apple App Store or Google Play, or an enterprise system — the agreement should also address resale rights, sublicensing terms, and whether the developer is permitted to reuse any elements of the software in projects for other clients. The distinction between Background IP (pre-existing developer tools and frameworks) and Project IP (bespoke code created for the client) is critical in this context and must be clearly defined.

A legally sound Australian Software Development Agreement must include the following elements to protect both the client and the developer under the Copyright Act 1968 (Cth), the ACL, and the Privacy Act 1988 (Cth).

Parties and project description: Full legal names and ABNs of both the client and the developer; a precise description of the software to be developed including the platform (web, mobile, desktop, embedded), technology stack, and any third-party integrations; and a project timeline with key milestones.

IP ownership and assignment: A clear statement that the developer assigns all Project IP — including copyright in source code under section 196 of the Copyright Act 1968 (Cth), any patentable inventions under the Patents Act 1990 (Cth), and all related documentation — to the client upon payment of the project fee. An alternative perpetual licence option where the developer retains ownership. Background IP protection preserving the developer's pre-existing tools, frameworks, and libraries, with a perpetual royalty-free licence to the client to use Background IP to the extent necessary to operate the finished software.

Milestone-based payment: Payment in AUD tied to defined delivery milestones — for example, 30% on signing, 40% on design approval, 30% on final acceptance — to protect both parties. GST provisions compliant with the A New Tax System (Goods and Services Tax) Act 1999 (Cth). The developer's right to suspend work for non-payment and to charge interest on overdue invoices.

Acceptance testing: A formal user acceptance testing (UAT) process with defined acceptance criteria, a testing period, a mechanism for the client to raise defects, and a remedy period for the developer to correct them. Deeming acceptance where the client fails to respond within the testing period protects the developer against clients who unreasonably withhold sign-off.

Scope change control: A requirement that all scope variations be documented in a written change order signed by both parties before additional work commences, with agreed additional fees. This prevents scope creep disputes, which are among the most frequently litigated issues in Australian software project disputes.

Privacy and data security: The developer's obligation to handle any personal information encountered during the project in accordance with the APPs under the Privacy Act 1988 (Cth); APP 11 security safeguards; APP 8 cross-border disclosure controls; breach notification obligations under the Notifiable Data Breaches scheme, enforced by the OAIC; and data return or deletion on project completion.

ACL compliance and limitation of liability: An acknowledgment that sections 60 to 62 consumer guarantees cannot be excluded; a limitation of liability clause compliant with section 64A of the ACL; and mutual indemnities for IP infringement. The forms-legal.com Software Development Agreement (Australia) template includes all these elements, drafted for use by Australian businesses engaging developers across all states and territories.