Software keeps most Australian businesses running - from point-of-sale systems and payroll tools to project management and creative apps. But installing an app doesn’t automatically make its use legal for business. You also need the right licence, and you need to use the software within the limits of that licence.
If that sounds daunting, don’t stress. With a bit of upfront knowledge (and a simple process to keep records tidy), you can stay compliant, control costs and avoid the scramble of a vendor audit. This guide explains what software licensing is, why it matters in Australia, and the practical steps to get your business set up the right way.
What Is Software Licensing?
A software licence is a contract that sets the rules for how you can use a particular program or service. When you “buy” or subscribe to software, you’re usually purchasing permission to use it on specific terms - not owning the software outright.
Licences typically cover things like:
- How many users or devices can access the software
- Whether you can copy, modify, or redistribute it
- Where it can be used (e.g. one location vs multiple sites)
- Usage limits (for example, API calls or storage caps in cloud products)
- What happens if terms are breached (suspension, termination, audit rights)
Because a licence is a contract, breaching it can lead to contractual remedies (like paying for overuse, audit costs, or termination). If the breach involves copyright (for example, using unlicensed copies), it can also lead to copyright infringement claims.
Why Software Licensing Matters For Australian Businesses
Getting licensing right isn’t just a “nice to have”. It supports your operations and reduces risk in several ways:
- Compliance and risk management: Using unlicensed or over-deployed software can trigger infringement claims or contractual action. It’s far cheaper to stay compliant than to “true-up” under pressure after an audit.
- Business continuity: Vendors can suspend access under their terms if there’s a serious breach, which can disrupt your team’s ability to work.
- Security and support: Access to patches, updates and support generally depends on having a current, valid licence - which is critical for cyber security.
- Budget control: Understanding licence metrics helps you pay for what you actually need (and avoid paying for seats or add-ons you don’t).
- Professional reputation: Clean, well-managed licensing demonstrates good governance to clients, partners and potential investors.
Common Licence Types (And What They Mean)
There isn’t one universal licensing model. You’ll typically encounter a mix of the following:
- Subscription (SaaS) licences: You pay monthly or annually to access cloud-based software. Terms often appear in SaaS Terms and may include usage caps, uptime commitments and data handling rules.
- Perpetual licences: A one‑off fee for the right to use a specific version indefinitely. Support and upgrades are usually separate and time‑limited.
- User- or device-based licences: Pricing depends on “named users” or installed devices. Sharing logins or exceeding activation limits typically breaches the licence.
- Volume or site licences: Discounted arrangements for multiple seats or locations, often with audit rights and reporting requirements.
- Proprietary licences: The most common for commercial tools from large vendors. Terms are restrictive - you generally can’t modify, reverse engineer, or redistribute without permission.
- Open source licences: These allow use (including commercial use) under specific conditions. Some are “permissive” (e.g. MIT, Apache) and mainly require attribution. Others are “copyleft” (e.g. GPL), which may require you to make source code available if you distribute derivative works. The key is understanding your obligations before you incorporate open source into a product or internal build.
- Freeware and freemium: Free tiers can be great for trials and small teams, but look closely for limits on features, seat counts or commercial use in the fine print.
When you supply software yourself (for example, your own app or platform), you set the terms users must accept, commonly in an EULA for installed software or a Terms of Use for web or mobile apps.
How To Stay Compliant: A Practical Step-By-Step
1) Map What You Use (And Who Uses It)
Create a simple inventory of all software in your business. Include vendor names, licence type (subscription, perpetual, etc.), how many seats you have, who uses them, and key dates (renewals, true-up windows). Don’t forget plugins, mobile apps, and “shadow IT” installed by enthusiastic team members.
2) Reconcile Licences Against Actual Usage
Pull the contracts, order forms and invoices for each product. Check whether your deployment matches the licence metrics (users, devices, instances, environments). For cloud services, compare billing portals against your internal list. If you’re over the limit, plan a tidy correction rather than waiting for an audit.
3) Choose Licensing Models That Fit Your Team
When purchasing or renewing, look beyond headline price. Consider:
- Seat vs device vs consumption-based pricing (which aligns with how your team works?)
- Growth plans (will you need more users or advanced features within 12 months?)
- Data location and compliance needs (does the plan support them?)
- Contract length (multi‑year discounts vs flexibility)
4) Educate Your Team On The “House Rules”
Most breaches are accidental. Explain simple do’s and don’ts: no sharing logins, no installing personal copies on work devices without approval, and no “trial” downloads on production machines. Short refreshers during onboarding go a long way.
5) Calendar Renewals And Budget For Audits
Vendors commonly reserve the right to audit or request usage reports. Keep purchase records accessible, set reminders for true‑ups, and assign someone to own renewals. Planning beats scrambling to fix issues under time pressure.
6) Build A Lightweight Approval Process
Before anyone adds a new tool, run a quick check: is there an existing licence we can use, does the new licence conflict with other terms, and does the product handle data in line with our privacy and security requirements?
7) Get Expert Help For Complex Deals Or New Products
Large enterprise orders, international contracts, or launching your own software product often call for tailored terms. Having a lawyer review the order form and core terms can reduce risk and clarify practical points like data security, uptime and exit rights. If you need hands-on support, consider speaking with a contract lawyer before you sign.
Essential Documents To Put In Place
- Software Licence Agreement and EULA: If you supply software (installed or downloadable), you’ll set the rules in a Software Licence Agreement or an EULA. For packaged solutions, many businesses use a combined Software Licence Agreement and EULA.
- SaaS Terms: If you run a cloud platform, your service terms (your SaaS Terms) cover subscriptions, acceptable use, uptime, support, data handling and termination.
- Service Level Agreement (SLA): For B2B customers, an SLA sets performance targets (like uptime and response times) and what happens if you miss them.
- Reseller or Channel Agreements: If you resell software or distribute licences, a clear Reseller Agreement should set territory, pricing, marketing rights and compliance obligations.
- Website Terms and Conditions: If users interact through your site or app, your Website Terms and Conditions set the rules of use and limit your liability where appropriate.
- Privacy Policy: If you collect personal information (for example, through sign‑ups or analytics), a compliant Privacy Policy explains what data you collect and how you handle it.
Protecting Your IP When You Build Or Buy Software
Copyright in software arises automatically when the code is created. You don’t “register” copyright in Australia, but you can and should protect your brand and other IP. Consider registering your name or logo as a trade mark via register your trade mark. For product design and inventions, you may also look at designs or patents (specialist IP advice is recommended).
When engaging developers or contractors, make sure your contract clearly states who owns the code, whether open source components can be used, and your rights to modify and commercialise the finished product. Clear ownership clauses prevent disputes later.
Common Pitfalls To Avoid
- License creep: Quietly adding seats or tools without adjusting licences leads to expensive true‑ups.
- Mismatched metrics: Buying device licences for a remote workforce that actually needs named‑user licences (or vice versa).
- Open source misunderstandings: Open source generally permits commercial use, but copyleft obligations can apply if you distribute modified code. Know the specific licence terms.
- Unclear internal rules: Without a simple policy, staff may share logins or install unapproved apps.
- No exit plan: Forgetting to look at data export, transition assistance, or IP clauses before you commit to a long subscription.
What Laws Apply To Software Licensing In Australia?
Several Australian laws (and sometimes overseas laws, depending on the vendor and chosen jurisdiction) can affect your rights and obligations. At a minimum, be aware of the following:
- Copyright Act 1968 (Cth): Software is protected as a “literary work”. Using or copying software without permission can infringe copyright, separate to any contractual breach.
- Australian Consumer Law (ACL): If you supply software or digital services, consumer guarantees, rules around misleading or deceptive conduct, and the unfair contract terms regime can apply - including for many small business customers using standard form contracts.
- Privacy Act 1988 (Cth): Many organisations handling personal information must comply with the Australian Privacy Principles. The Act generally applies to “APP entities” (typically businesses with an annual turnover of more than $3 million), but there are important exceptions that capture smaller businesses (for example, health data, handling Tax File Numbers, or providing certain services). Even where the Act doesn’t strictly apply, customers increasingly expect a clear and practical Privacy Policy.
- Contract law: Your licence terms and order forms are contracts. Pay attention to licence scope, audit rights, payment triggers, data ownership, liability caps and termination clauses.
- Data and security obligations: Industry standards, customer SLAs and security commitments in your terms can create enforceable obligations - make sure they are realistic and aligned with your technical capability.
If you license or purchase from overseas vendors, governing law and jurisdiction clauses may point to another country. It’s a good idea to review those terms through an Australian lens so you understand how they interact with your local obligations.
Key Takeaways
- Software licensing is a contract: you’re buying permission to use software on specific terms, not ownership of the software itself.
- Compliance protects your business: it reduces legal risk, avoids audit surprises, and keeps your security patches and support on track.
- Choose licence models that fit how your team works, and keep a simple inventory that matches licences to actual usage.
- Open source generally permits commercial use, but different licences come with different obligations (like attribution or sharing modifications).
- Core Australian laws to be mindful of include copyright, the ACL and the Privacy Act; your terms and order forms also create contractual obligations.
- If you supply software, have clear customer-facing documents such as SaaS Terms, an EULA, an SLA, Website Terms and Conditions and a Privacy Policy.
- When you build software, lock in ownership and licensing rights in your developer contracts and consider trade mark protection for your brand.
If you would like a consultation on software licensing for your business, you can reach us at 1800 730 617 or team@sprintlaw.com.au for a free, no-obligations chat.
