Service Credits Vs Refunds In SaaS Contracts

Service credits are usually the better starting point for SaaS downtime because they compensate your customer without requiring you to hand back cash. Refunds can still make sense for more serious failures, cancelled subscriptions or situations where the Australian Consumer Law applies.

The tricky part is that you can't treat service credits as a magic shield. Your contract needs to be clear about when credits apply, how they're calculated and whether they're the customer's only remedy. It also needs to sit comfortably with Australian consumer law and unfair contract terms rules.

If you're deciding how to compensate customers for downtime or service failures, the goal is simple: give customers a fair remedy, protect your cash flow and avoid arguments when something goes wrong.

What Is The Difference Between Service Credits And Refunds?

Service credits reduce a customer's future fees, while refunds return money the customer has already paid. In SaaS customer contracts, that difference matters because it affects cash flow, customer retention and your legal risk.

A service credit is usually a dollar credit or percentage credit applied to the customer's next invoice. For example, if your platform misses its monthly uptime target, the customer might receive a 10% credit against next month's subscription fee.

A refund is a repayment. You might refund part of a monthly subscription, an unused annual subscription amount or fees paid for a feature that didn't work as promised.

For SaaS businesses, service credits are popular because they:

• keep cash in the business
• encourage the customer to continue using the platform
• create a predictable remedy for service level failures
• help avoid open-ended claims for minor outages

Refunds are more customer-friendly, but they can be harder to manage commercially. If several customers ask for refunds after the same outage, the cash impact can be much larger than a future credit.

When Should You Use A SaaS Service Credit Clause?

You should use a SaaS service credit clause when you want a clear, pre-agreed remedy for measurable service failures, especially uptime or support response failures.

A service credit clause works best where the failure can be measured objectively. That means both you and your customer can look at the same data and work out whether a credit is owed.

Common triggers include:

• monthly uptime falling below a stated percentage, such as 99.5%
• critical support tickets not receiving a response within the agreed time
• scheduled maintenance exceeding the agreed maintenance window
• failure to restore a key service within a stated recovery time

Say you run a Melbourne-based SaaS platform for allied health clinics. Your standard plan promises 99.5% monthly uptime, excluding scheduled maintenance. In one month, an infrastructure issue means uptime drops to 98.8%. Your contract could give affected customers a 10% credit on their next monthly invoice, provided they request it within 30 days and were materially affected by the outage.

That approach gives everyone a clear path. The customer doesn't need to argue about loss. You don't need to negotiate every outage from scratch.

What Should A Service Credit Clause Cover?

Your service agreement clause should explain the remedy in enough detail that your team can apply it consistently. A good clause usually covers:

• The service level: for example, 99.5% monthly uptime for the core platform.
• What counts as downtime: for example, unavailability of the production environment, not slow loading or third party login issues.
• Exclusions: for example, scheduled maintenance, customer misuse, beta features, force majeure events or failures caused by the customer's systems.
• The credit amount: for example, 5%, 10% or 25% of the monthly subscription fee for that service.
• The claim process: for example, the customer must request the credit within 30 days of the end of the month.
• Caps: for example, credits are capped at one month's fees for the affected service.
• Whether credits are the sole remedy: subject to rights that can't be excluded under law.

Templates often miss the operational details. Your clause works best when it's tailored to how your product is hosted, measured, supported and billed.

When Are Refunds Better Than Service Credits?

Refunds are better when a credit would be meaningless, unfair or unlikely to resolve the problem. This often happens when the customer is leaving, the failure is serious or the service couldn't be supplied as promised.

A credit only helps if the customer keeps using your SaaS product. If they've cancelled, lost trust or paid annually for a service they can't use, a future credit may not feel like a real remedy.

Refunds may be more suitable where:

• you can't provide the service at all
• a paid feature is materially unavailable for an extended period
• the customer paid upfront and cancels part-way through a subscription term
• you offered a satisfaction guarantee or trial with refund rights
• the Australian Consumer Law gives the customer rights that your contract can't remove

For example, imagine your Sydney SaaS business sells an annual subscription to a project management tool. A customer signs up mainly because of a promised time-tracking module. If that module is unavailable for two months and it was a key part of the deal, a small credit against a future invoice might not be enough. A partial refund or agreed cancellation right may be more practical.

Should Refunds Be Automatic?

Refunds don't always need to be automatic, but your contract should clearly say when they're available. If you leave this vague, your support team may end up making inconsistent calls.

You might say:

• monthly subscription fees are generally non-refundable once a billing period starts
• unused prepaid fees are refundable only where your contract allows cancellation for your breach
• setup, onboarding or customisation fees are non-refundable once the work has started
• nothing in the clause limits rights under the Australian Consumer Law

This gives you a commercial position while leaving room for legal rights that can't be contracted out of.

Can You Make Service Credits The Customer's Only Remedy?

You can often make service credits the customer's only contractual remedy for specific service level failures, but you can't exclude rights that the customer has under the Australian Consumer Law or other laws.

This is where SaaS contracts need careful wording. A clause that says service credits are the customer's sole and exclusive remedy may be useful for routine uptime misses, but it shouldn't try to remove non-excludable rights.

Under the Australian Consumer Law, which sits in Schedule 2 to the Competition and Consumer Act 2010, consumer guarantees can apply to business customers in some cases. For example, services costing $100,000 or less are generally covered, and some higher-value services may also be covered if they're ordinarily acquired for personal, domestic or household use.

For services, the guarantees include that services will be provided with due care and skill, be fit for a disclosed purpose and be supplied within a reasonable time where no time is agreed.

You can't simply write those guarantees out of your SaaS terms. For services that aren't ordinarily acquired for personal, domestic or household use, you may be able to limit liability in certain ways, such as supplying the services again or paying the cost of having them supplied again, but only where the law allows and the limitation is fair and reasonable.

A safer approach is to say that service credits are the customer's sole remedy for the relevant service level failure, except for any rights or remedies that can't be excluded, restricted or modified under law.

How Do Australian Uptime Remedies Usually Work?

Australian SaaS uptime remedies usually work through a service level agreement, often called an SLA, that sets an uptime target and a credit if you miss it. The SLA can sit in your main customer terms, an order form or a separate service level agreement schedule.

The key is to make your uptime promise realistic. If your hosting provider only commits to 99.9% availability, promising every customer 99.99% uptime may expose you to credits you can't control.

Common Uptime Credit Structures

Many SaaS businesses use a stepped credit structure. For example:

• 99.0% to 99.49% uptime: 5% credit of the monthly fee
• 98.0% to 98.99% uptime: 10% credit of the monthly fee
• below 98.0% uptime: 25% credit of the monthly fee

Those numbers aren't legally required. They're commercial choices. The right structure depends on your product, customer base, pricing and how critical the software is to your customers' operations.

If your software is business-critical, customers may expect stronger remedies. If it's a lower-cost tool used for convenience, a smaller credit may be reasonable.

How To Define Uptime Clearly

Your SLA should define uptime in a way your systems can actually measure. Consider spelling out:

• whether uptime is measured monthly, quarterly or annually
• which parts of the platform are included
• whether partial degradation counts as downtime
• whose monitoring system is the source of truth
• how scheduled maintenance is notified and excluded
• how third party outages are treated, such as cloud hosting, payment gateways or integrations

Without clear definitions, customers may count every glitch as downtime. You may then spend more time debating the numbers than fixing the problem.

What Should Your Software Subscription Refund Clause Say?

Your software subscription refund clause should say when fees are refundable, when they're not and how the clause interacts with legal rights that can't be excluded. Clear refund wording helps your sales, accounts and support teams apply the same rules.

For SaaS, your refund clause should cover the main payment situations in your business. That may include monthly subscriptions, annual subscriptions, upgrades, downgrades, onboarding fees and usage-based fees.

Useful points to cover include:

• Billing periods: whether fees are charged monthly, annually or on another cycle.
• Cancellation timing: whether cancellation takes effect immediately or at the end of the current billing period.
• Prepaid fees: whether unused prepaid fees are refundable, credited or forfeited.
• Trials: when a free trial becomes a paid subscription and whether reminders are sent.
• Downgrades: whether downgrades create a credit or only reduce future invoices.
• Setup fees: whether implementation, onboarding or migration fees are refundable.
• Legal carve-out: a statement preserving non-excludable rights under the Australian Consumer Law.

If you sell to both businesses and consumers, be especially careful with refund language. A blanket statement like all fees are non-refundable in all circumstances can create problems if it suggests customers don't have rights the law gives them.

Your refund policy should also match what you say on your website, checkout page, order form and sales emails. If your marketing promises easy cancellation but your terms say no refunds, customers may challenge the inconsistency.

What Contract Risks Should Australian SaaS Businesses Watch For?

The main risks are overpromising service levels, trying to exclude rights you can't exclude and using standard terms that may be unfair. Each risk can be managed with careful drafting.

Unfair Contract Terms

Australia's unfair contract terms regime can apply to standard form contracts with consumers and small businesses. Since 9 November 2023, unfair contract terms aren't just void - using, proposing or relying on them can attract penalties.

For small business contracts, the regime can apply where at least one party has fewer than 100 employees or annual turnover of less than $10 million. Maximum penalties under the Competition and Consumer Act can be significant, including up to $50 million for companies, three times the benefit obtained, or 30% of adjusted turnover during the relevant period where the benefit can't be determined.

For SaaS terms, watch clauses that:

• let you change service levels, pricing or features without a fair process
• give you broad rights to suspend access without notice or a reasonable trigger
• make customers pay even where you haven't provided the service
• exclude all liability in every circumstance
• make service credits the only remedy even for serious or repeated failures

That doesn't mean you can't protect your business. It means your protections should be balanced, transparent and connected to a genuine business need.

Misleading Or Inconsistent Promises

If your website says guaranteed 99.99% uptime, your contract shouldn't quietly water that down to a much lower standard. Claims in sales decks, onboarding materials and product pages can matter, not just the fine print.

If you're not ready to make a hard guarantee, use softer and more accurate wording. For example, you might say you target a certain uptime level and set out the remedy if you don't meet it.

Third Party Dependencies

Most SaaS products rely on third party services: hosting, analytics, payments, authentication, email, SMS or AI tools. Your IT services agreement should explain how failures in those services affect your SLA.

You may decide that third party outages are excluded from downtime if they're outside your reasonable control. If a third party is central to your product, customers may push back and ask you to take more responsibility. The right balance depends on your pricing, bargaining position and the criticality of the service.

How Should You Draft A Fair Service Level Remedy?

You should start with the customer's real problem, then choose a remedy that's clear, proportionate and workable for your business. A fair remedy is easier to enforce and easier to explain when a customer is frustrated.

A practical drafting process looks like this:

1. Map the failure types: list the failures that matter most, such as downtime, data access issues, slow support or failed integrations.
2. Choose measurable standards: avoid vague promises like best possible uptime. Use measurable targets where you can.
3. Set proportionate credits: match the credit to the seriousness of the failure and the fees paid for the affected service.
4. Cap the exposure: consider a monthly cap, such as credits not exceeding the monthly fee for the affected service.
5. Keep evidence simple: decide what logs, monitoring reports or support tickets will be used.
6. Add a claim deadline: many businesses use 30 days after the relevant month, but choose a period that your customers can reasonably meet.
7. Preserve legal rights: make clear that nothing limits rights that can't be excluded under law.

You can also separate routine failures from serious failures. For example, a minor uptime miss might trigger a credit, while repeated serious outages might give the customer a right to terminate and receive a pro-rata refund of unused prepaid fees.

This kind of structure helps you avoid two extremes: offering nothing, which can frustrate customers, or promising unlimited refunds and liability, which can put the business under unnecessary pressure.

Key Takeaways

• Service credits are often a better fit for routine SaaS downtime because they protect cash flow and keep the customer relationship going.
• Refunds may be more appropriate for serious failures, cancelled subscriptions, unused prepaid fees or situations where a future credit won't help.
• Your SLA should clearly define uptime, downtime, exclusions, credit amounts, caps and the claim process.
• You can't contract out of non-excludable rights under the Australian Consumer Law, so your clauses need a clear legal carve-out.
• Unfair contract terms rules can apply to standard SaaS terms, especially where you sell to consumers or small businesses.
• The best remedy is one your business can actually honour and your customer can easily understand.

If you'd like help with your SaaS customer terms, service level agreement, refund wording or Australian Consumer Law compliance, you can reach us at 1800 730 617 or team@sprintlaw.com.au for a free, no-obligations chat.