Why is my SaaS bill higher than the number of users times the advertised price?

Usually one of four documented reasons rather than an error. Seats may be sold in blocks, so 31 people can mean 40 purchased seats. Annual plans on some vendors bill by user tier instead of by exact headcount. An invoice covering a month in which anyone joined or left is a sum of prorated day-slices rather than a clean multiplication. And the advertised figure is normally the annual-commitment rate quoted before tax, while your account may sit on the higher month-to-month rate. Check the seat quantity on the billing page rather than the user-admin page first, because those two numbers are allowed to disagree.

Do invited users who never logged in still get billed?

On some vendors, yes. Atlassian's support documentation on users and user tiers states that additional users are "automatically counted towards billing even if they don't accept your invite or log in" (checked 18 August 2026). Slack goes the other way and publishes a Fair Billing Policy under which members who have not used Slack in over 28 days generate prorated credits. Neither behaviour is an industry default, so the answer has to come from your own vendor's billing article.

If I remove a user halfway through the month, do I get the money back?

It depends on whether the vendor prorates and, separately, on whether your plan lets the seat count drop at all. Google Workspace's billing documentation says charges are prorated per day and gives the example of adding a user on April 1 and deleting them on April 15 producing half a month of charge. But on the Annual/Fixed-Term plan the same vendor's comparison page says licences can be removed "only when you renew the contract. Until then, you pay for all purchased licenses." Prorated and reducible are two different questions.

Can I reduce seats before the renewal date on an annual plan?

Often only inside a short window straight after purchase or renewal. Microsoft's admin documentation says that on an MCA billing account you can add licences at any time but can remove them only within seven days of buying or renewing, and that a reduction made after that window appears on the first invoice following the renewal date. Microsoft's new commerce cancellation policy for partner-sold subscriptions puts the same seven calendar days on licence-based products and adds that the window "doesn't reopen until the subscription itself renews into a new term."

SaaS Pricing Page vs Your Bill: Where It Diverges

Asana's pricing page prints $10.99 per user, per month, billed annually for the Starter plan, with $13.49 as the month-to-month rate (both checked 18 August 2026). A team of 31 people multiplies the first figure out and budgets $340.69 a month. Run the seat rules published further down that same page over the same 31 people and the quantity being billed is 40 seats, or $439.60.

Nothing has gone wrong in that arithmetic. Nobody was added. The extra $98.91 a month is nine seats that do not correspond to nine people, and the rule that creates them is on the pricing page too, folded into the answer to "How can I add people to my plan?" rather than printed beside the price.

That is the general shape of the problem. The headline figure is a unit price. The invoice is a quantity multiplied by a unit price, and the quantity is not your headcount.

Seats are sold in blocks, and the blocks get bigger as you grow

Asana publishes its seat-purchasing rule as a list rather than a footnote (Asana pricing, checked 18 August 2026):

Total users	Seats are added in increments of
Between 2 and 5	1
Up to 30	5
Up to 100	10
Up to 500	25
More than 500	50

Read that as a cost curve rather than a purchasing convenience. At 26 people you buy 30 seats. At 31 people you buy 40, because crossing the 30-user line moves you into the increment-of-ten band and the first purchase inside it is a block of ten. Four unused seats becomes nine on the day one person joins.

What the page actually publishes is the increments; 30 and 40 are what those increments compose to. Confirm the number against the quantity on your own billing page before putting it in a budget.

So the real cost of the 31st hire is not $10.99 a month. It is $109.90 a month, or $1,318.80 over a year, and it stays that way until you either fill the block or drop back under the boundary.

The inverse is the part that bites during a wind-down. Losing one person out of 31 saves you nothing at all, because 30 people still sit inside the same block of forty seats until somebody resets the quantity, and the quantity can usually only be reset at one specific moment in the year.

Before any renewal, write down the block boundaries immediately above and below your headcount. Those, not your staff list, are the prices you can choose between.

Annual billing can change the unit you are counted in

The monthly-versus-annual choice gets presented as a discount. On some vendors it also changes the counting rule underneath the discount.

Atlassian's support documentation states it in two sentences: "For monthly subscriptions, we offer per-user pricing," and "Annual subscriptions are based on distinct user tiers" (Atlassian Support, checked 18 August 2026). Monthly is counted in people. Annual is counted in bands. The article stops there — it does not publish where the band edges fall or how a given headcount maps onto one, which means the annual figure is not something you can derive from the monthly one on paper. You find out what a band costs by pricing the annual subscription, and you move onto that counting rule at the same moment you accept the annual saving.

The same page carries the sentence that resolves most "who are all these people" questions: additional users are "automatically counted towards billing even if they don't accept your invite or log in." An invitation sent in March to a contractor who never opened it is a billable seat that appears on no list of people who have logged in.

That article also names the only route back off the count: "For a user to not count towards billing, a site admin should delete or remove the user from any synced user directory." Deleting them from the directory, in other words — not revoking a product permission somewhere downstream of it.

Google Workspace splits the same decision along a different seam. Its plan comparison page lists Business Starter at $8.40 USD per user on the Flexible plan against $7 USD per user monthly, or $84 per user yearly, on the Annual/Fixed-Term plan (Google Workspace admin help, checked 18 August 2026). The lower figure is the one that travels into budgets and comparison articles. If your account is on Flexible, your bill is twenty per cent above it and always was. Those are the US dollar rates on that page, and the page itself warns that annual payment options vary by region, so read your own currency off your own invoice.

An invoice covering a month of change is not a multiplication

The most common reason a bill refuses to reconcile is that it is not describing a whole month of anything.

Google's billing documentation says charges "are prorated per day over the billing period" and gives the arithmetic plainly: add a user on April 1 and delete them on April 15, and "we charge you for only half a month of service" (Google Workspace admin help, checked 18 August 2026).

Microsoft describes the resulting invoice structure for a MOSA billing account, which is worth quoting in full because it explains why one product appears three or four times on one page: "the previous charge for the original number of licenses is deducted on your next invoice. We add a prorated charge for the time period with the original number of licenses and add a charge for the new license count. There's also a charge for the current license count for the remainder of your billing period" (Microsoft Learn, checked 18 August 2026).

A reversal, two partial periods and a forward charge. Not one of those lines equals seats times price, and the sum of them is not meant to.

The same page adds a timing detail that hides mid-term growth from the invoice you are staring at: "Licenses added in the middle of your billing period appear on your next invoice. If you pay annually, you're invoiced within a month for these changes." The charge for the three people who started in June may simply not be on the June bill.

Which gives a rule for checking your own numbers. Never reconcile against a period in which the seat count moved. Find the first full cycle with no changes in it, and check that one. If it still does not match, the cause is structural and lives in one of the sections below.

Inactive is not the same as unbilled

Slack publishes an actual rule for this instead of leaving it to a support ticket. Under its Fair Billing Policy a member who "hasn't used Slack in over 28 days" is flagged inactive and "credits will be deposited to your Slack account for the unused portion of the billing period," with deactivated members generating credits the next day. The worked example on that page describes a workspace "on the Pro plan and you're paying monthly, $8.75 USD per member" and prices a mid-period deactivation as ($8.75 divided by 30 days) x (15 days) = $4.38. The $8.75 is the number inside Slack's own illustration, not a quotation of the current Pro rate — take the shape of the calculation from it and the rate from your own invoice (Slack help centre, checked 18 August 2026).

Now read the closing line of that policy with an exit in mind. Credits "have no currency or exchange value, are non-transferable and non-refundable, and will expire following the termination of your paid Slack plan." A team winding down over three months accrues credit for every person it switches off, and the whole balance evaporates the moment the paid plan ends. Those credits are worth something only if you spend them before you leave, which for most people leaving means they are worth nothing at all. That question belongs beside what a Slack export actually contains on your plan, because both have to be settled before the plan terminates rather than after.

There is a step people miss here that quietly costs a full term. Switching someone off inside the product and reducing the seat count on the subscription are two separate acts, and only the second one changes the invoice. Microsoft's documentation spells out the order: "You can't reduce the number of licenses for your subscription if all licenses are currently assigned to users. To reduce the number of licenses, first unassign one or more licenses from users, then remove the licenses from the subscription."

Unassigning frees the licence in the admin screen, which looks exactly like progress. It leaves the licence on the bill. The seat stays purchased until somebody opens the billing page and changes a quantity, and that screen will show a free licence for eleven months while you pay for it.

The seats you are not allowed to give back

Reducing the quantity is not always available, and the window is usually far shorter than the term.

Google's comparison page describes removing users on the Annual/Fixed-Term plan as possible "only when you renew the contract. Until then, you pay for all purchased licenses," with a minimum commitment of "1 year or more of service for licenses purchased at the start of the contract." Adding users is available at any time on both plans. That asymmetry is the entire design: the quantity ratchets upward through the term and can only fall at one moment in the year.

Microsoft draws the line by days instead of by term, and which line you are standing on depends on a piece of account plumbing most admins have never looked at. Its buy-or-remove-licenses article opens by telling you to find out what type of billing account you have, then splits into separate instructions for the two types. Do that lookup first; the rest of this section is unusable without the answer.

On an MCA billing account you can buy licences whenever you like, "however, you can only remove licenses from your subscription if it's within seven days of buying or renewing your subscription," and mid-term purchases carry their own window: "If you buy licenses in the middle of your billing period, you have seven days from when you buy them to reduce the number of licenses you bought." Miss it, and the reduction "appears on the first invoice you receive after the subscription renewal date." The unassignment step quoted in the previous section has to happen before any of this, on either account type.

The MOSA section of that article publishes no equivalent deadline. It gives a single set of steps covering both directions, where you type the total you want into the Total licenses box and save, and the consequence lands as the four-line invoice quoted earlier: a deduction, two partial periods and a forward charge. So a MOSA account is not governed by the seven days at all, and reading that rule as though it applied is a way to talk yourself out of a reduction you were allowed to make. The constraint on MOSA is the assignment check and the invoice lag, not a window.

If the subscription came through a reseller rather than direct, the equivalent rule lives in Microsoft's new commerce cancellation policy, which grants licence-based products a prorated refund within seven calendar days of purchase and then shuts: the cancellation window "doesn't reopen until the subscription itself renews into a new term" (Microsoft Learn, checked 18 August 2026). That table is headed "Self-serve cancellation window in Partner Center", and Partner Center is the reseller's console rather than yours. The seven days are real; the person who can act inside them is your account manager. So the request goes out in writing on the day of purchase or renewal, not when somebody gets around to it.

No vendor sends a reminder for a window that short, and it falls in the week when everyone is relieved the renewal went through. It belongs on the same page as your notice period, which is why it sits in the first block of the 30-day switch runbook rather than somewhere near the end. It is also why a seat count set during one busy quarter can outlive the people it was bought for by eleven months.

Reconciling one invoice, line by line

Twenty minutes, once, before any decision about renewal.

Start on the billing page, not the user-admin page. The seat quantity you are being charged for is held there, in a different place from the list of people, and the whole gap described above lives between those two numbers.
Find out which rate the account is actually set to. Monthly and annual figures sit side by side on every pricing page, the smaller one is the one that gets remembered, and the account may be on the other one — Google Workspace Business Starter splits $8.40 against $7 on exactly that line, at the rates quoted earlier.
Divide the invoice total by the seat quantity. If the answer is not the published rate, you are looking at a proration month, a tier band, or tax. Pricing pages generally quote before VAT.
Add-ons are billed on their own terms and have to be listed separately. Per-seat add-ons, marketplace apps and one-time onboarding fees each have a different basis, and an add-on priced per user may be counted against your purchased seat quantity rather than your active people — Slack, for one, says credit calculations for its add-ons work the same way as for members. Check each add-on's own billing article; this is not consistent between vendors.
The last thing to write down is a date rather than a decision: the next day on which the quantity is allowed to fall. For most vendors that is the renewal date, or a fixed number of days after it.

The figure that decides your bill is not how many people work here. It is a quantity on a billing page nobody has opened since the last time someone joined, governed by plan rules that decide when that quantity may move. Both are knowable in an afternoon. Neither changes because you deactivated an account in the user list.

Verified against Asana, Atlassian, Google, Microsoft and Slack documentation on 18 August 2026. The seat-increment table comes from Asana's pricing page. The per-user versus per-tier distinction and the invite-counting sentence come from Atlassian's users and user tiers article. The proration rule and plan comparison come from Google Workspace's bills and charges and plan comparison pages. The invoice structure and the seven-day windows come from Microsoft's buy or remove licenses and new commerce cancellation policy articles. The credit formula and the expiry wording come from Slack's Fair Billing Policy.

Prices move and billing articles get edited without announcement, so treat every figure above as the value on the date in bold, not as a current quote. The rules are the durable part; the dollar amounts are not. Five vendors are named because their billing mechanics are published in their own words, not because any of them is being recommended or ranked. If a quotation here has stopped matching its source, the contact page reaches me and the claim gets re-read against it.