Understand the improved Atlassian billing experience
What is the improved Atlassian billing experience?
We’re replacing our existing billing infrastructure with a new billing engine to provide a unified billing and invoicing experience across all Atlassian cloud products. It includes an improved invoicing and administration model, which will give you enhanced flexibility to group and pay for subscriptions in the way that best suits your business needs. We’re developing the experience incrementally and will release enhanced capabilities over time.
How do you know which experience you’re viewing?
To check the difference in the user interface:
Go to Atlassian Administration.
Select your organization if you have more than one.
Select Billing. The Billing preview page appears.
Select Manage corresponding to the required product.
The following screenshots indicate how the interface of the two billing experiences differs.
Original experience | Improved experience |
|---|---|
In the original billing experience, the first option on the left is Overview.
| In the improved billing experience, Subscriptions is the first option on the left. |
What are the key differences?
We’ve introduced a number of changes in the improved billing experience. Each billing experience has a different functionality and interface.
Parameter | Original billing experience | Improved billing experience |
|---|---|---|
Billing interface | On the original system, you can manage your bills in two places:
| The improved experience doesn’t use my.atlassian.com – we’ve unified all billing functions in Atlassian administration and can be navigated using either of the ways:
|
Account model | Contact-based model. As a billing or technical contact, you can administer multiple licenses. We invoice you on a site-by-site basis. Payment details are managed at the site level. | Account-based model. We’ve introduced billing accounts, which can have one or many billing admins. Each account can be associated with a billing profile, which has a group of product subscriptions linked to a sold-to address and a payment method. |
Roles | The original system had two billing roles:
As a billing contact on the original experience, your subscriptions are managed through my.atlassian.com. Note: You may have product subscriptions on one or both systems. | We’ve introduced a new, expanded role that replaces billing and technical contacts:
If you’re a billing admin with products that are on the improved experience, they’re now managed through a new interface at admin.atlassian.com/billing. Note: You may have product subscriptions on one or both systems. |
Subscription ID | The original system uses the Support Entitlement Number (SEN). Example: SEN-123456 | The improved experience uses an alpha-numeric Entitlement Number, starting with an 'E'. Example: E-12A-C34-DEF-GHI |
Billing interface
For products managed on the original billing experience, you can do different billing in two different places:
With the improved billing experience, we’ve created a unified experience with a new interface that can be navigated using any one of the following ways:
Go to admin.atlassian.com/billing. Select your billing account if you have more than one.
Go to Atlassian Administration. Select your organization if you have more than one. Select Billing.
It’s important to note that some products – Jira Align, Opsgenie, and Trello – are managed on separate billing systems.
Account model
In our original billing system, customers are billed on a site-by-site basis. In the improved billing experience, all cloud product subscriptions live under a customer billing account. This account model gives you more flexibility and allows you to:
have multiple subscriptions split between billing accounts
have multiple billing profiles with different sold-to addresses and payment methods for a group of subscriptions. Read more about billing profiles
move subscriptions from one billing account to another
decouple Confluence and Jira billing – in other words, Confluence and its related apps can be on a different billing cycle and terms than Jira on the same site
Read more about billing accounts
Roles
Your admin roles also impact how and where you manage your subscriptions.
To simplify administration, we’ve created a new administrative role called a billing admin, which replaces the technical contact and billing contact in the original system.
Primary billing contacts, secondary billing contacts, and technical contacts will all be converted to billing admins in the new experience.
As an org or site admin, you can perform some billing tasks within admin.atlassian.com. You may have product subscriptions managed on one or both systems.
Read more about billing administration
Which products and plans are supported?
Eventually, the new experience will support all cloud products. However, the Data Center products will remain in the original experience for now.
We support all plans for the products in the following table:
| Currently supported | Not yet supported |
|---|---|---|
Products |
|
|
How and when will customers be moved to the new experience?
To smoothly transition customers from the current system to the improved billing experience, we’re conducting a site migration. Customers' sites and data will migrate to the new billing engine in different groups at different times.
We’ve built sophisticated migration tooling, which uses end-to-end encryption to keep your billing data secure and protect your privacy during the move.
You’ll receive an email with 30 days' notice when your sites are scheduled to be migrated. You won’t need to do anything—we’ll do the work in the background, so you don’t have any downtime.
Was this helpful?