Atlassian is rolling out an updated billing model, known as maximum quantity billing, for select monthly subscriptions. This significant change aims to bring more predictability to your monthly bill by basing charges on the peak usage within your billing cycle. This transition will be implemented gradually over the next few months, with all customers holding monthly subscriptions for affected apps anticipated to migrate to this new model by October 2025. This change will affect a range of popular Atlassian products, including Compass, Confluence, Guard, Jira, Jira Product Discovery, Jira Service Management, and Loom (which is already live), as well as various Marketplace apps. Further announcements are expected as additional applications transition to this new billing model, while annual subscriptions currently remain unaffected.
Historically, Atlassian calculated monthly invoices for per-user subscriptions based on the number of active users at the very end of each billing cycle. With the introduction of maximum quantity billing, this method is changing. The new approach will calculate monthly invoices based on the highest number of active seats at any point during the month. This means that if seats are added during a billing period, automatic recalculations will occur to reflect this increased usage. For example, if a team starts June with 10 seats and adds 5 more mid-month, the billable seat count for the following month (July) will be based on the total of 15 seats from the last day of June. The additional 5 seats will be billed on a prorated basis for the duration they were active, specifically, for half of that month. This shift ensures that organizations are billed for the maximum capacity utilized, offering a more consistent reflection of their usage patterns.
The new maximum quantity billing model introduces specific considerations for how adding and removing seats during a billing period will affect your invoice. Understanding these implications is crucial for managing your Atlassian costs effectively.
Adding Seats: If seats are added mid-month, your billable seat count for the current month will reflect the highest number of active seats attained during that month. The newly added seats will be prorated for the portion of the month they were active.
Removing Seats: If seats are removed during the month, these reductions will not lead to immediate deductions, refunds, or credits on your current monthly bill. Instead, the billing for these additional seats will continue until the next billing cycle. Any reductions in your seat count will only be reflected in your bill for the following month, assuming no further changes are made to your subscription during that subsequent period.
The rollout of maximum quantity billing will occur in phases over the coming months. Atlassian is committed to transparent communication throughout this transition. Customers will receive advance notification via email before their specific billing accounts transition to this new model. The company anticipates that all affected monthly subscription customers will be migrated to maximum quantity billing by October 2025. This phased approach allows Atlassian to manage the transition smoothly and provides customers with ample time to understand and prepare for the change. Organizations should monitor their email notifications closely and familiarize themselves with the updated billing FAQs and support documentation to ensure a seamless adaptation to the new model.
To prepare for the upcoming maximum quantity billing model, Atlassian Cloud users should consider several proactive steps. These actions will help ensure your team is ready for the transition and that your billing processes remain transparent and manageable.
Audit Current Usage: Regularly review your active user counts across all affected Atlassian products to gain a clear understanding of your current peak usage patterns.
Monitor Notifications: Keep a close eye on emails from Atlassian regarding the specific timeline for your account's transition to maximum quantity billing.
Familiarize Yourself with Documentation: Review the detailed Maximum Quantity Billing FAQ and support documentation provided by Atlassian to understand specific examples of how seat additions and removals impact billing.
Adjust Seat Management Strategies: If your organization frequently fluctuates in user count mid-month, consider how this new model might impact your budgeting and adjust your seat management strategies accordingly to optimize costs.
Communicate Internally: Inform relevant stakeholders, including finance teams and product administrators, about the upcoming billing changes and their implications.
Atlassian's introduction of maximum quantity billing represents a strategic move towards a more predictable and usage-based billing model for its monthly cloud subscriptions. While this change brings more clarity regarding peak usage charges, it also necessitates a proactive approach from organizations to understand its implications on budgeting and user management. By auditing current usage, staying informed through Atlassian's notifications, and adjusting internal processes, businesses can smoothly adapt to this new model. This ensures continued optimal utilization of Atlassian products while maintaining financial predictability.