A mid-term upsell is not automatically a new contract

A customer on a 24-month subscription adds fifty seats in month 14. Sales books it, billing invoices it, and the revenue schedule needs to reflect it from the date the seats went live.

There are two defensible ways to record that, and they produce different numbers for the remaining ten months. Which one applies is a question about the added seats, not about the size of the deal.

The question is distinctness and price

If the additional seats are distinct from what was already promised, and they are priced at their standalone selling price, the addition stands on its own. The original schedule continues untouched and the new seats get their own.

If either condition fails, meaning the seats are not separable from the existing promise or they were sold at a discount that only makes sense in the context of the original deal, the addition is a modification of the arrangement that already exists. Then the remaining consideration is reallocated across the remaining obligations, and recognised over the remaining term.

Same commercial event. Two schedules, two deferred revenue balances, two sets of journals.

The arithmetic is not the hard part

It is worth being precise about where this actually breaks, because the common version of this argument is wrong.

NetSuite's revenue management does handle contract modification. Combined Revenue Arrangements and Prospective Merges exist for exactly this, including carve-in and carve-out after billing has already happened. Acumatica, with its ASC 606 feature enabled, builds a reallocation pool and allocates across obligations in proportion to fair value price. Neither platform is helpless here, and anyone selling you the opposite is one documentation link away from being corrected in front of your team.

The gap is upstream of the arithmetic.

In both systems the arrangement is assembled from transactions. Sales orders, invoices, billing schedules. That is a reasonable place to start, and it works cleanly when a commercial change arrives as a billing change on the same day.

It works less cleanly the rest of the time. An amendment is signed in March with an effective date in May. A term extension is agreed and the billing schedule is not updated until the next cycle. A partial cancellation is negotiated verbally, confirmed by email, and reaches the ERP when someone raises the credit. In each case the contract changed before the transaction did, and the schedule is correct only from the point the system found out.

What that costs at the population level

One late modification is a correction. The reason this becomes a quarterly exercise is that modifications do not arrive alone, and they do not arrive on a schedule.

By the time someone is reconciling deferred revenue at quarter end, the question is no longer "what does this contract say". It is "which of the four hundred active contracts changed since the last close, and did anything downstream reflect it". That question is answered by asking around, and it is answered again three months later.

The three things that make it answerable are unglamorous:

Contract terms enter as terms. The executed document is the source of the obligations, with its own effective dates, rather than being inferred from whatever was billed.

Every schedule change records its trigger. An amendment, a clause firing, a judgement revisited. "Why did this schedule change in March" becomes a lookup instead of an investigation.

Modifications are worked as a population. Which contracts changed in the period, what the change was, and what it did to the schedule. As a list, before close, rather than as forty separate discoveries during it.

What stays with your team

The judgements. Whether an added promise is distinct. Whether the price reflects standalone value or deal-level discounting. Whether a change is a modification of one arrangement or the start of another. Those are decisions for your accountants, tested by your auditors, and no system should be making them.

What the system owes you is that once the judgement is made, it is applied consistently, from the right date, across every affected contract, and that the evidence for it is still there when someone asks in eighteen months.