In this guide
Approval Plus Mortgage
Service guides

Jira and Confluence billing: review seats, profiles and the payer

A Jira administrator is not automatically the person who can pay its invoice. Identify the billing experience, account and profile first, then review the user quantities that created the charge.

Identify the Cloud billing experience you actually use

Atlassian maintains original and improved billing experiences during its transition. In the original interface, the navigation begins with Overview; the improved experience begins with Subscriptions and uses admin.atlassian.com/billing. Check the screen before following a saved procedure. This guide concerns Jira and Confluence Cloud, not a Data Center license renewal.

A billing account can contain several subscriptions. Jira and Confluence can have independent billing cycles, while applications within the Jira product family share a unified cycle for a site. Write down the exact app, site, billing account and cycle. Paying for one product should not be taken as evidence that a separately billed Confluence subscription has also been covered.

Sources & further reading: [1]

Send payment changes to a billing administrator

Check the billing role before asking someone to replace a card or download an invoice. Atlassian distinguishes billing administrators from organization and site administrators. Product or user-management access does not necessarily include payment controls. A billing administrator can manage the relevant payment information and invoice actions within the account they administer.

Make a change request specific: include the app and site, the billing account, the intended effective date and a masked reference for the replacement method. Do not include a full card number in a shared ticket. Ask the administrator to confirm the affected subscriptions before saving; this is particularly useful when several teams share the same payer.

Sources & further reading: [2]

Check every subscription attached to a billing profile

In the improved experience, a billing profile combines payment information, a sold-to address and subscriptions. A billing administrator selects the billing account, opens Billing profiles and chooses Manage for the relevant profile. Read its subscription list before editing. A card change on that profile applies to all subscriptions using it, not only the Jira page you last visited.

Address changes can have a wider reach: Atlassian says changing a sold-to address updates subscriptions using that address across billing profiles. Treat the address and payment method as separate shared settings. Record which subscriptions will inherit each change and verify company details before an invoice is generated.

Sources & further reading: [3]

Reconcile monthly quantity before comparing prices

For monthly subscriptions under maximum-quantity billing, the month begins with a billed user quantity. Increasing above that quantity creates prorated charges reflected on the following invoice. Removing users does not reduce the already billed maximum for the current period; unused capacity can be reused. The user quantity at the end of the period determines the next month’s starting quantity.

For an illustrative seat check, a team starting at 10 users, increasing to 12 and ending at 9 should not calculate the entire month as nine users. Compare the timing of the additions with the invoice’s adjustments, then check the next cycle’s starting count. This example describes quantities, not an Atlassian price or a guaranteed invoice amount.

Sources & further reading: [4]

Count product access, not only recent activity

Review access for the specific product. Atlassian’s user-billing guidance says monthly billing can include a user with product access even if that person has not accepted the invitation or logged in. An activity report is therefore not a complete billing roster. Compare invited users and granted access with the quantity shown for the app.

Annual subscriptions use user tiers, so do not apply a monthly per-user calculation to an annual quote without checking its tier. Before requesting a renewal change, record the current tier, the users who need access and any planned additions. This gives the payer an operational reason for the requested quantity instead of only a target budget.

Sources & further reading: [5]

Keep card costs and the Atlassian invoice separate

In the improved experience, use Invoices to download the document and check its status. A paid record and an invoice still awaiting payment are different evidence. Match the app or Marketplace line items, billing period and adjustments before comparing the total with the card statement.

Approval Plus Essential issuance costs US$1; Plus issuance costs US$10 and adds selection among available BINs and Visa or Mastercard options. Plus also includes replacement coverage for seven days from issuance. These card-product choices do not determine an Atlassian user tier or cancel a subscription. Include any card cost separately in your purchasing budget, then confirm the actual merchant payment against its invoice.

Sources & further reading: [6] [7]

Your questions, answered

Can a site administrator always change the billing card?

No. Check the billing-administrator role for the relevant account; product administration and billing permissions are different.

Does removing a monthly user immediately reduce the current bill?

Under maximum-quantity billing, it does not reduce the already billed maximum for that period. Review additions, prorated adjustments and the next cycle’s starting count.

Will a billing-profile card change affect only Jira?

It affects all subscriptions attached to that profile. Review its list before saving, including any other products paid through the same profile.

Sources & further reading

  1. Atlassian: identify the improved billing experience ↗Checked Nov 16, 2026
  2. Atlassian: billing permissions by role ↗Checked Nov 16, 2026
  3. Atlassian: understand billing profiles ↗Checked Nov 16, 2026
  4. Atlassian: maximum-quantity billing ↗Checked Nov 16, 2026
  5. Atlassian: manage users and user tiers ↗Checked Nov 16, 2026
  6. Atlassian: understand invoice fields and payment status ↗Checked Nov 16, 2026
  7. Approval Plus: Essential and Plus card features ↗Checked Nov 16, 2026
APPROVAL PLUS

Your next step

Account, funding and card guidance in your language.

APPROVAL PLUS

Need a hand?

Our support team can help with your account, funding and card questions.

support@approvalplusmortgage.com