Prepare an annual SaaS seat true-up from historical usage

An annual seat adjustment might use a maximum count, an average, a specified measurement date or additions during the term. Read the actual agreement and amendments. Record the initial committed seats, measurement period, allowed reductions and rates for incremental seats. A year-end snapshot cannot establish a historical maximum or an average across the year.

Identify any provisions for temporary access, mergers or contractor accounts. Resolve unclear language with the commercial owner while the customer can still review the evidence. The billing team's task is to apply the agreed method consistently, not select whichever historical report produces the easiest total. Preserve the approved interpretation with the calculation.

Collect the opening register and subsequent additions, removals and transfers. Reconcile the history to periodic snapshots and the final directory. Stripe models per-seat charges through quantities; your supporting record must explain how the contractual measurement produces the quantity or adjustment submitted to billing.

Check missing periods and corrections to user identities before calculating the charge. A user renamed during the year should not automatically become an additional seat. If only partial history is available, state the gap and obtain an approved resolution rather than presenting a reconstructed estimate as a complete observed record.

List interim seat invoices and credits against the annual commitment. Identify the periods they cover and whether they were permanent additions or temporary adjustments. Stripe's proration documentation illustrates why quantity changes can create separate billing effects. The final true-up must account for those effects before another invoice is issued.

For illustration, an agreement might require an additional $4,800 for the year under its stated measurement rule, while $3,000 of eligible interim additions has already been billed. The remaining adjustment is $1,800 if the agreement permits that offset. Preserve the mapping from each interim invoice to the calculation instead of subtracting every invoice with the word seats in its description.

If the contract uses a maximum seat count, inspect the events that produced the maximum. A temporary onboarding overlap, duplicate identity or emergency access grant may explain the peak, but its chargeability still depends on the agreed definition. Preserve the evidence and approved treatment instead of smoothing the history because the highest count looks unusual.

If the contract instead uses an average, document the weighting and intervals used. A hypothetical count of 40 seats for one day and 20 for the remaining 29 days should not be averaged as two equally weighted snapshots. Retain the dated history and calculation so the reviewer can reproduce the result and distinguish a genuine temporary increase from a data error.

Share the applicable measurement dates, quantities, rate and prior-billing deductions in a clear statement. Use customer-approved identifiers where supporting detail is needed. Allow the account owner to resolve genuine data disputes before finalizing the bill. Keep a record of accepted corrections and the authority for any negotiated concession.

After issue, reconcile the invoice to the approved calculation and provide accounting with the service periods and any earlier accrual. Set the next term's opening quantity explicitly; an annual adjustment does not automatically define the renewal commitment. Store the history and calculation together so a later account manager can explain the adjustment without rebuilding a year's user changes.