Reconcile a subscription change with its proration preview

Freeze the proposed change before calculating

Stripe’s Prorations documentation, checked 7 November 2026, distinguishes a preview from a subscription change, a credit from an automatic refund and a debit from immediate collection. Confirm the account’s billing mode and original invoice status.

Write a change brief using invented subscription details: existing plan, proposed plan, quantity, current service period and intended effective instant. State whether the request preserves the current renewal boundary or proposes a different one. Separate the customer’s requested outcome from the configuration someone thinks will implement it. A request to add capacity today does not by itself authorize replacing the billing period or changing another product.

Build a component bridge rather than one total

Create a worksheet with the old service allocation, unused-service credit, new service allocation, debit and other invoice components kept on separate lines. Identify which amount comes from the provider preview and which is an independently calculated reasonableness check. Do not substitute a simple daily estimate for documented provider arithmetic when the configured calculation uses another basis.

Attach the original period’s payment status and relevant price history. An unpaid invoice can make a credit look like money being returned when no corresponding cash was collected. Mark uncertain inputs as unresolved rather than choosing the rate that gives the customer or seller the more attractive answer. Finance owns the approved treatment of those cases.

Bind the preview to its assumptions

Record the preview’s timestamp, proposed effective instant, price identifiers, quantities, currency and relevant configuration version in the synthetic acceptance packet. Keep tax, discount and balance components visible when they appear in the supplied output, but do not invent their treatment. The point is to compare like with like, not to reproduce the entire billing engine in a marketing spreadsheet.

Define what invalidates the preview: a changed quantity, later effective instant, different discount, altered original invoice or a revised billing configuration. If the assumptions change, request a new authorized preview rather than presenting the old figure as guaranteed. When reviewing a supplied final result, compare each component with the frozen proposal and explain differences. A matching net amount alone can conceal an incorrect credit offset by an incorrect debit.

Explain the financial consequence precisely

Prepare separate plain-language statements for the service change, invoice adjustment and payment event. Say whether the evidence describes a preview, a pending adjustment, an invoice or a completed payment. Avoid refund language unless an actual refund is the approved and verified outcome. Likewise, do not promise that a positive adjustment will be collected immediately simply because it appears in the calculation.

Close the exercise with a component bridge, assumption list and unresolved decision owner. Any real modification or financial communication needs its normal authorization; the worksheet itself grants none. Preserve a redacted or synthetic calculation record suitable for future support questions without copying account secrets or payment identifiers. Acceptance means the proposed change is explainable on its own terms, not that it has been applied or that the customer has agreed to it.

Make the reasoning concrete.

A fictional design-software service proposes adding seats midway through a service period. A supplied preview contains an unused-service credit and a new debit, while the original invoice is still unpaid. The account team wants to call the credit a refund.

The team holds the refund wording and creates a component-level review packet. No subscription, invoice, refund or customer message is changed.

Take the questions into your next brief.

Use these prompts in your own notes. Nothing is submitted from this page.

1. Change

   What exact plan, quantity and effective instant are proposed?

2. Basis

   Which original service period, price history and payment status support the credit?

3. Bridge

   How do separate components reconcile to the preview amount?

4. Validity

   Which changed assumption requires a new preview?

5. Meaning

   What is calculated, invoiced, collected or still unresolved?

Watch for the wrong conclusion.

• Calling an unused-service credit a completed refund.
• Comparing totals while ignoring different effective times.
• Treating an unpaid original invoice as settled cash.

Sources & scope

Workflows, fixtures, worksheets and examples are original editorial analysis. Sources support the narrow attributed statements, not measured business results. Platform guidance is scoped to the documented implementation and date checked. Synthetic offline planning only; no real financial action or account change is performed.

• Prorations →Primary platform documentation · Supports: Supports the attributed preview, credit and collection distinctions.