Set True Up Billing Rules for Changing MSP Seat Counts

Define the Count Behind the Invoice

Write down what the recurring line covers and how its quantity is established. Identify the system or record used for the count, the person who confirms changes, and how exceptions are handled. User, device, license, and managed-service seat should not be treated as interchangeable labels without an agreed definition.

Keep the previous invoiced quantity as the starting record. Compare it with the verified billable quantity for the same period. A device inventory is useful input, but first check how the agreement treats inactive devices, shared equipment, and other exceptions relevant to your service.

For a worked example, assume the model's 20-seat client at $225 per seat each month, with no separate additions, credits, or other charges. The full-period managed fee is 20 multiplied by $225, or $4,500. That result depends on the agreed quantity and rate both being correct.

Keep those inputs beside the invoice line. If the verified count changes, recalculate quantity using the agreed effective date. If the price changes, show the new rate separately. Combining them into a single unexplained adjustment makes the calculation harder to check.

Choose Effective Dates for Additions and Removals

Decide when an added seat becomes billable. Possible arrangements include the approved service start or another expressly agreed billing point. Choose the policy you can administer and fund, then put it in the agreement rather than letting the first invoice establish it by accident.

Make the removal rule equally explicit. State what confirms that the billable service has ended, who approves it, and which date the invoice uses. Keep a requested removal separate from the evidence that the relevant work and commercial changes have been completed.

Don't assume additions and reductions must use the same mechanism. Test the proposed treatment against your service work and supplier commitments. Have the client-facing wording and the billing configuration reviewed together before relying on the policy.

A leaver request can also require account, device, and license decisions. Give each its own task where needed. Closing an access task shouldn't silently tell finance which recurring lines to remove.

Write the Proration Calculation

Proration means charging part of a period according to the method the agreement specifies. If you use it, state the period basis, the effective-date convention, and the rounding treatment. The model supplies no universal mid-period billing rule to copy.

The calculation needs the agreed unit price, the verified quantity change, and the part of the period that is billable. Calculate the quantity change multiplied by the unit price, then apply that agreed fraction. Keep the date evidence with the calculation.

At the example's $225 unit price, the full-month amount for an additional billable seat is $225. A part-month amount depends on the agreed fraction; don't manufacture a daily charge from an unstated convention. The same discipline applies to any credit the policy permits.

If your policy instead adjusts at an agreed period boundary, show that rule and the resulting date. Don't call a full-period charge prorated. The client and billing owner should be able to reproduce the same result from the record.

Keep Supplier Commitments Beside the Client Rule

Check the upstream subscription or tool commitment before promising flexibility in the downstream fee. Record which charges can change, which remain committed, and when any permitted change takes effect. Use the supplier's current terms and your actual order record.

On MSP Mastery, Tas Gray describes bundling Microsoft licensing into his monthly per-user service while choosing monthly upstream commitments so client seat counts can flex. He gives administrative simplicity and flexibility as his reasons. That is his commercial design, not a rule that every MSP's existing supplier commitments work the same way.

Keep the managed-service seat line separate internally from product commitments even when the client sees a bundle. A smaller user count doesn't itself establish which supplier charges have stopped. Finance needs the actual commitment record to cost the policy.

Separate the Annual Increase From the Count Change

The model calls for a fixed annual increase written into the contract and communicated in advance. Its step is 5%. That changes the rate, while a seat adjustment changes the quantity. Give each its own explanation on the billing record.

Hold the example's count at 20 seats and apply the 5% step to $225. The new unit price is $225 multiplied by 1.05, or $236.25. The full-period fee becomes 20 multiplied by $236.25, or $4,725. No seat increase is assumed in that calculation.

If quantity also changes, use the rate applicable to each relevant part of the period under the agreement. Keep the price-effective date and quantity-effective date distinct. Don't apply the annual step again inside an unexplained true-up amount.

Reconcile Before Sending the Adjustment

Give the recurring reconciliation a date that fits the billing process and enough time to resolve differences before invoicing. Add change-driven work when a user, device, or service event requires it. The routine needs an owner and a backup, rather than a reminder with no recipient.

• The service or request owner records the approved addition or removal, its relevant service result, and the effective-date evidence.
• The billing owner compares the verified billable count with the quantity already invoiced for the same period.
• The licensing owner confirms separate product changes and any commitments that remain.
• The billing reviewer checks the rate, dates, proration method, and rounding against the agreement.
• The account lead explains a material change before the client receives a surprising invoice and routes any disputed input for correction.

Keep corrections identifiable. Show the period corrected, the previous charge, the reason for the change, and the revised calculation. An unexplained credit may settle the immediate amount while leaving the same input error in place for the next invoice.

Take a client whose seat count changed and reproduce the next invoice from the agreement and change record. If you need an unwritten decision to finish the calculation, settle that decision and update the policy before sending the adjustment.