You spent Tuesday clearing out 15 people who left months ago. A few weeks later the invoice arrives, and it’s exactly the same. Finance asks what the clean-up was for.

Nothing went wrong. The removal worked, it just hasn’t reached the bill yet. Removing a person and lowering the invoice are two separate events, and how far apart they are depends on your plan.

Monthly plan: you pay for the highest count

Monthly Jira subscriptions use what Atlassian calls maximum quantity billing. Your bill is based on the most users you had during the billing period. Remove someone on day 5 and that period’s bill doesn’t move. Atlassian is plain about it: no deductions, refunds or credits.

What you do get is a spare seat until the period ends. Give it to the next new starter and you won’t pay extra for them.

The saving arrives one step later, because the next period starts from your count on the last day.

Next billing period

People with Jira

38

You pay for

38

Saving starts here

Day 1: 40 people, 40 seats billed. On a monthly plan the bill follows the highest count in the period.

Day 10: you remove 5. You still pay for 40. Their seats sit empty but paid until the period ends.

Day 20: 3 new starters take spare seats. No extra cost, because you used seats you already pay for.

Next period: you pay for 38. The count on the last day sets the next bill.

Sample numbers · monthly subscription

So on a monthly plan, one habit pays for itself: remove first, then add. Add the new starters first and you can push the maximum up, and then you pay a prorated cost for the extra seats too.

Annual plan: you already bought the tier

Annual subscriptions are sold in user tiers, not per person. You paid up front for a band of users, and Atlassian’s licensing page says annual user tiers can’t be altered or changed. Removing 15 people from a 100-user tier doesn’t bring money back.

The clean-up still counts, in two ways. You stay inside the tier you bought, so you won’t need a prorated upgrade quote when you hire. And when renewal comes round, the quote starts from fewer people.

So the deadline to watch is your renewal, not your next invoice. Annual customers usually get a renewal quote automatically about 90 days before the subscription ends, so do the clean-up before then and check which tier the quote uses.

The next bill still didn’t fall?

Then those people are probably still counted. This is the part worth checking, because it’s real money and it won’t fix itself.

They still have Jira through another group. Taking someone out of one group often isn’t enough. Another group can give them Jira too, or the default group can. Open the person in Atlassian Administration and look at their Apps tab. If Jira is still listed, they’re still counted. Our article on why removing a user from a group didn’t remove Jira access goes through every path.

A sync or a default group put them back. An identity provider can add people again on its next sync, and so can an approved domain or a default group. Check the count again a day or two after your clean-up, not just the minute after.

You’re looking at a different app. Jira, Jira Service Management and Confluence are billed one by one. Removing someone from Jira doesn’t touch their Confluence seat.

Your plan is at organization level. Enterprise plans are billed annually on a user tier for the whole organization, so they won’t show on the site bill at all.

How to see where you stand

Go to admin.atlassian.com, then Billing, find the subscription and select Manage. On the subscription details page, the Billed user tab shows your billed quantity, the user changes and your next bill estimate. That’s the number to show finance, because it tells you what’s coming instead of what already happened.

If your screen looks different, you may be on the original billing experience, where it’s under Manage subscriptions. Atlassian is still rolling out the newer one.

What to tell finance

Keep the two facts apart, with a date on each:

☐ We removed 15 people on 3 November. ☐ The bill follows on the next billing date (monthly) or at renewal (annual). ☐ The Billed user tab shows the new estimate.

Where Seatwise fits

Seatwise shows who costs a Jira seat without having worked in Jira lately, and which groups give each person that seat, so you can catch the “still in another group” case before the invoice does. You see a preview before anything changes, and you have 30 days to undo it. It only covers Jira seats, so it won’t help with Confluence or Atlassian Guard counts, and it can’t change how Atlassian bills you.

Sources: Atlassian: how maximum quantity billing works, Atlassian: manage users and user tiers, Atlassian: cloud licensing. Checked 2 November 2026.