As more organizations accelerate their shift from on‑premises to cloud‑based SaaS solutions, Atlassian is no exception. 

Particularly for Jira and Confluence, where billing is tied directly to per‑user pricing, every additional user immediately affects costs.

Big Changes Are Coming to Atlassian Cloud Billing

If your team uses Jira, Confluence, or any Atlassian Cloud products, there’s a major billing change headed your way, and it might catch you off guard if you’re not ready.

Starting July 14, 2025, Atlassian is rolling out something called Maximum Quantity Billing for monthly subscriptions. In plain terms, you’ll be charged based on the highest number of active users during the month, even if you remove people later.

That means one quick login from a dormant account or a short-term guest could end up inflating your costs.

Let’s break it down and talk about what you can do to stay in control.

So, What Exactly Is Maximum Quantity Billing?

Here’s how the new billing model works:

• Billing is based on peak user count. Even if someone logs in just once, they count for the whole month.
• Adding users mid-month? You’ll see pro-rated charges immediately.
• Removing users? That won’t reduce your bill for the current month.

This change affects monthly subscriptions for most Atlassian Cloud products, including Jira, Confluence, JSM, Compass, Guard, Jira Product Discovery, Loom, and many Marketplace apps.

👉 Here’s Atlassian’s full breakdown.

Why It Matters: Real Costs for Real-World Scenarios

You used to be able to deactivate a user before the end of the month and avoid being billed. Not anymore. Now, if someone logs in even for a second, they’re counted. That’s a big deal if:

• You have users who were onboarded but never used their account

• External collaborators jump into a project for a day or two

• Employees go on leave, sabbatical, or switch roles

To manage this manually, you’d need to keep tabs on your user list every single day. That’s neither scalable nor efficient.

What Can You Do About It?

Good news, there are smart ways to stay ahead of this.

Option 1: Switch to Annual Billing

If your user base is relatively stable, switching to annual billing could save you around 20% and help you avoid monthly usage spikes.

You’ll get:

• Predictable costs

• Fewer surprises from short-term user activity

• Simpler budget planning

It’s a straightforward way to reduce risk and save money.

Option 2: Automate User and License Management

This is where the real value kicks in.

Tools like Flexible User License help you stay on top of usage without constantly checking admin panels.

You’ll get:

• Real-time visibility into who’s actually using their license

• Automated rules to pause or remove inactive accounts

• Dashboards that show seat allocation, usage peaks, and available capacity

It’s like putting your Atlassian admin on autopilot, so you only pay for what you truly need.

🚀 Check it out in the Atlassian Marketplace

Don’t Let Surprise Costs Derail You

Atlassian’s new billing model is designed to simplify billing on their end, but it puts more responsibility on your side to actively manage users.

Take action now so your next invoice doesn’t catch you off guard:

• Go annual if your team size stays relatively stable

• Automate license management if your user base changes 

You already have plenty to focus on. License management shouldn’t be another daily task, and now it doesn’t have to be.

Want help figuring out the best approach for your team?
We can show you exactly how Flexible User License can save you time, money, and unnecessary hassle.

📅 Book a quick demo