Maximum Quantity Billing

We bill monthly subscriptions based on the number of users at the start of each billing cycle. With maximum quantity billing, any users added mid-cycle are charged on a prorated basis for the remaining days in the cycle.

Note: No credits for users removed mid-cycle; user count resets at the start of the next billing cycle.

Maximum quantity billing will roll out gradually and be available to all customers by October of 2025.

We’ve adopted maximum quantity billing to better align with industry standards and provide a more consistent, predictable billing experience for monthly subscriptions.

No action is required on your part; your eligible subscriptions will automatically transition to this model when it is your turn to migrate, and you will receive an email in advance of your transition to maximum quantity billing.

Maximum quantity billing will apply to monthly subscriptions of Jira, Jira Product Discovery, Confluence, Compass, Atlassian Guard, Loom, and Marketplace apps.

No, maximum quantity billing will only apply to new billing periods following activation.

No, this change is not optional and cannot be delayed. All customers on monthly subscriptions will eventually be moved to the maximum quantity billing model as part of our transition to a standardized and industry-aligned billing practice.

No, this is a standard billing model for all customers and cannot be disabled.

Discounts are applicable to these billing charges as well, provided discounts are active when the invoicing is happening for these charges (typically along with the renewal for next month).

Mid-cycle user additions are prorated based on the remaining days in the billing cycle. No credits for removals mid-cycle.

Prorated charges for mid-cycle user additions appear on the next renewal invoice or as charges in arrears on the final invoice as a separate invoice line.

Maximum quantity billing does not impact invoice generation time.

For Data Center to Cloud migrations, maximum quantity billing only applies to eligible cloud subscriptions once activated.

Our support team will review disputes on a case-by-case basis. Contact us here for assistance.

Costs may increase slightly in billing cycles where users are added mid-cycle.

No, mid-cycle user removals do not reduce charges during a billing cycle, but rather free up those seats for other users until the end of the monthly billing period. Reduced user counts will only apply to your next billing cycle. 

Note: For monthly subscriptions, your bill is based on the highest number of users in the month (Maximum Quantity Billing). No credits for users removed mid-cycle; user count resets at the start of the next billing cycle.

Monthly subscriptions have no billing tiers, but you’ll be notified when adding users that impact your bill.

Yes, usage history is available in the billing console.

No, as monthly plans are auto-scaling, there’s no cap on charges for user additions.

Once activated, eligible subscriptions will incur prorated charges for mid-cycle user additions.

Deactivating users mid-cycle will not reduce your current month’s bill; rather, these seats will be freed up and available for others to use. The reduced user count will not be reflected until the next month’s renewal.

The billing console will provide new usage monitoring graphs to monitor your usage with maximum quantity billing.

Currently, usage limits or alerts for user additions are not available on monthly plans. However, you will be notified every time user addition results in additional charges.

No, there is no minimum usage threshold for maximum quantity billing.

Usage details are available in the billing console.

Contact our support team via the Atlassian Support Portal here for further assistance.