Contract renewals: prepare the next invoice from approved terms

A renewal date is not automatically permission to continue billing on the same terms. The next cycle should be prepared from an approved commercial decision, including price, scope, dates, entity and any cancellation condition.

When renewal work stays in a sales calendar while billing repeats an old schedule, both teams can act correctly inside their own systems and still produce the wrong invoice.

Name the renewal event

Record the contract end date, notice period, renewal type and person responsible for the decision.

Distinguish automatic renewal terms from an internal expectation that the customer will continue.

Compare old and new terms

Make pricing, quantity, currency, tax context, service period and customer entity visible side by side.

A no-change renewal still needs a confirmed owner and effective date.

Route commercial exceptions

Price changes, negotiated extensions, credits and scope adjustments need explicit authority.

Do not hide an exception inside a recurring line that appears unchanged to later reviewers.

Update the schedule deliberately

Create or revise the billing schedule only after the approved renewal record exists.

Keep the previous schedule, new schedule and effective boundary available for audit and customer questions.

Run a first-cycle review

Treat the first renewed invoice as a controlled exception even when later cycles can follow a standard path.

Check the period, amount, entity, customer reference and delivery route before sending.

Treat renewal as an effective-dated commercial decision

A contract renewal becomes billable only when the organisation can identify the customer, entity, renewed scope, amount or rate basis, currency, service period, billing schedule, effective date and approving authority. A sales forecast, unsigned proposal or reminder that a term is ending is not automatically a supported renewal charge.

Define which renewal states can prepare billing and which must remain held. Auto-renewal, customer-confirmed renewal, negotiated amendment, notice of non-renewal and unresolved renewal should not collapse into one active flag. Preserve the evidence and rule that moved the contract into its current state.

Open the renewal workflow before the billing cut-off

Calculate a review date from the notice period, negotiation needs and first invoice cut-off. Notify the commercial owner with the current terms, upcoming effective date, customer contacts and outstanding exceptions. A useful renewal queue shows the decision required, not merely days remaining until expiry.

Keep overdue decisions visible. Do not let the existing schedule continue indefinitely because nobody changed it, and do not stop a supported auto-renewal because a task was not marked complete. Apply the documented contract rule and route uncertainty to an authorised owner with a named checkpoint.

Version renewed terms and schedules

Create a new effective-dated term version for changes to price, quantity, currency, frequency, minimums, caps, payment terms, entity or delivery instructions. Preserve the prior version and its service period. The renewal should never rewrite the evidence behind invoices already prepared or issued.

Generate or update the billing schedule from the approved version. Reconcile the first renewed charge to the agreed period and prevent overlap with the ending schedule. Proration, credits or transition treatment must follow the authorised commercial and finance rule rather than an improvised calculation at invoice time.

Work a renewal with a price and entity change

Assume a customer renews on 1 October at $12,000 per month, replacing a $10,000 schedule, and moves to a different issuing entity. Preserve the old schedule through 30 September. Create the new term version with its customer entity, currency, payment terms, authority and first billing date.

Do not edit the September invoice or move its receivable to the new entity. Prepare the October invoice from the new schedule after entity and customer data checks. If the entity change remains under review, hold the new charge with an owner and date rather than defaulting it to the former billing account.

Handle late agreement and retrospective changes

When renewal evidence arrives after the intended effective date, record the actual approval time, requested effective date and affected service or invoices. Route retrospective treatment through the approved commercial, accounting and specialist process. Do not backdate the decision record to make the workflow appear timely.

Identify charges already issued under prior terms and preserve them. If a correction is authorised, use the governed document path and link it to the renewal version. Keep customer communication and resulting balances visible so collections does not continue against a superseded unsupported amount.

Connect renewal to delivery and collections

Verify the renewed billing contact, purchase reference, portal access and required delivery channel before the first invoice. A commercial renewal can succeed while invoice delivery fails because the customer's operating contacts changed. Treat destination readiness as a separate controlled checkpoint.

Carry open disputes, credits, promises and unapplied receipts forward as linked receivable context rather than mixing them into the new schedule amount. A renewed contract does not close the prior balance. Give collections the contract version and customer communication needed to distinguish old and new obligations.

Close the renewal hand-off

Record the prior and renewed versions, decision evidence, effective date, schedule transition, first prepared invoice, outgoing approval, delivery readiness and accounting mapping. Name every held issue and next action. The hand-off closes only when another authorised person can explain why the first renewed charge belongs in its period.

Review missed decisions, overlapping schedules, defaulted entities, late corrections and delivery failures by stable cause. Repair renewal lead times and ownership without publishing unsupported performance claims. The control should make the true decision state visible, not manufacture administrative completion.

Decision summary

• Require an effective-dated renewal decision before billing.

• Version renewed terms and prevent schedule overlap.

• Hold uncertain entity, rate or scope changes visibly.

• Keep prior receivables separate from the renewed schedule.

• Reproduce the first renewed charge from approved evidence.

Verify the first renewed cycle

At the first renewed billing checkpoint, compare the issued candidate with the approved renewed version, prior schedule end, effective customer data and expected period. Check that no old schedule produced a duplicate and no new term was applied to service outside its authorised scope.

Retain the reviewer, comparison and outcome. If the first charge is held or corrected, feed the result back to the renewal record and schedule rather than applying a one-off invoice edit. The second cycle should inherit a repaired rule, not depend on someone remembering the first-cycle exception.

Confirm that customer-facing renewal communication names the effective terms, first billing period and route for a discrepancy. Keep the communication with the renewed version so later collection activity does not depend on a salesperson's private message history.

Put the control into practice

Select the next renewal due and follow it from contract decision to prepared invoice. If the schedule changes before the terms are approved, reverse that dependency.

Run the review on a real case

A contract renews with a price change effective next quarter. Retain the renewal decision, old and new terms, currency, scope, effective date and approver before changing the recurring schedule. Review the first renewed invoice as a controlled exception.

Compare the previous agreement and approved renewal side by side. Finance should be able to identify which cycles use each term and why the schedule changed.

Case-review checklist

• Renewal event is confirmed

• Old and new terms are preserved

• Effective boundary is explicit

• Commercial exceptions are approved

• First renewed cycle is reviewed

An expected continuation is not authority to invoice. The signed or otherwise approved renewal record and applicable contract process remain the source of the billing change.