Subscription plan-change disputes: seats, proration, and invoices

A disputed subscription upgrade, downgrade, or seat change needs three answers: what the customer approved, when the service changed, and how that change affected the bill. Those events do not have to happen together. An adjustment can be collected immediately, carried to renewal, or recorded as a credit rather than returned to the card.

For B2B and B2C SaaS teams, the useful investigation connects the personal account or company workspace to each of those records. A second invoice is not enough to establish a duplicate charge. Fewer active users are not enough to establish that the billed seat quantity was reduced.

Establish the change before explaining the amount

Find the original request and the terms shown at that time. Record the old and new plan, quantity, price, currency, billing interval, and affected account. Preserve the confirmation or preview the customer actually received, rather than reconstructing it from today's pricing page.

For a company workspace, identify the actor who requested the change and the billing authority they held then. Today's administrator list does not establish historic permission. A product event attributed to a member also does not, by itself, establish cardholder authorization.

Keep requested, processed, and effective times separate. A reduction requested on Friday may have been scheduled for renewal; an accepted request may also have failed during processing. The customer activity timeline guide explains how to retain those distinctions without treating missing events as proof that nothing happened.

If the complaint is actually that the whole subscription should have ended, follow the cancellation investigation. Removing an add-on and canceling the subscription are different requests. Paddle explicitly distinguishes removing recurring items from ending the entire subscription.

Check when the adjustment was meant to be billed

Proration means adjusting a charge for part of a billing period. It does not, on its own, specify when money is collected or returned. Check the provider's recorded configuration for this change.

Paddle documents five modes: prorated or full billing now, prorated or full billing at renewal, and no billing for the change. Lemon Squeezy's plan-change guide describes adding a prorated amount to the next renewal by default, with options to invoice immediately or disable proration. These are provider-specific behaviors, not interchangeable defaults.

For each change, compare the selected behavior with the confirmation and resulting records. Was the customer shown an immediate payment, a renewal adjustment, or no additional charge? Did support later promise something different? A billing setting can explain the calculation without settling whether the customer received the promised treatment.

Reconcile invoice lines and actual money separately

Read the line items before comparing invoice totals. Identify the service interval, quantity, price, debit or credit, discounts, taxes, and any previous balance applied. Then connect the invoice to actual collection and refund records. Do not count an unpaid invoice or a failed payment attempt as money received.

Paddle's refund guidance adds an important balance detail: refunding a transaction that created credit reduces the associated balance, while the original credit-issued display remains historical. Check the current balance as well as the original transaction. Do not count the historical credit and a later refund as two independent benefits without reconciling their relationship.

Worked example: an extra payment followed by a credit

Fictional example. A company workspace has six seats at €30 each for November 1–30. For this example only, the agreed calculation uses a 30-day period, changes take effect at midnight UTC, and amounts exclude tax and discounts. This is not a universal formula or a reproduction of a provider's calculation.

On November 11, an authorized billing administrator adds three seats. The recorded choice collects the remaining-period adjustment immediately: 3 × €30 × 20/30 = €60. On November 21, the administrator removes those three seats. This change creates a credit for the remaining ten days: 3 × €30 × 10/30 = €30, to be applied at renewal.

The November payments cover different obligations: the original six seats and the additional seats for part of the month. That explains why two collections exist. The downgrade produced a €30 credit, not a €30 card refund.

Now read the support conversation. If an agent promised “€30 back to your card today,” the billing history does not fulfill that promise. The case needs an owner to reconcile the commitment with the available refund route. If the customer instead disputes the administrator's authority, the arithmetic does not answer that complaint either.

Compare billed quantity with the service actually available

Check what a seat means in the applicable agreement: a purchased allowance, an assigned member, or another defined unit. Use that definition when comparing billing and product history. Do not silently substitute the number of recent logins for the purchased quantity.

Then look for genuine mismatches. Did billing increase while access remained on the old plan? Did a confirmed reduction leave the previous quantity on renewal? Was an access failure acknowledged by support? Preserve these contradictions alongside the records supporting the charge.

Paddle's change workflow supports previews of immediate and next transactions. A saved preview can help explain what was presented. It still needs to be matched to the applied change and final transaction; a preview is not proof of collection.

Turn the investigation into a precise answer

Give support or the dispute owner a short finding: the approved change, effective period, adjustment, collected amount, current credit or refund, and unresolved issue. Correct a confirmed mismatch through the appropriate billing process. Where the record supports the charge, explain it with the relevant lines rather than sending an unexplained invoice total.

For a formal card dispute, select the records that address the actual allegation using the chargeback evidence guide. If the question remains whether two payments settled the same obligation, use the duplicate-charge investigation.

Evidenz is being built for this history problem in B2B and B2C SaaS. A personal plan upgrade may need the confirmation beside the invoice; a company seat reduction may also need the requesting member, workspace, and support commitment. Its intended approach brings those relationships into the investigation so the explanation follows the customer history, rather than starting and ending with a payment amount. That is especially useful when finance's credit record and support's refund promise describe different things.

Follow-up questions

Does a downgrade automatically produce a cash refund?

No. Establish the configured adjustment and the actual records. The change may create credit against later billing, and a separate refund may require another action. A specific refund promise still needs resolution. For missing money already promised, follow the refund-not-received guide.

Can two invoices exist without two successful payments?

Yes. An invoice and a collected payment are different records. Check the payment linked to each invoice and its current outcome. Explain only verified collections, and keep pending or failed attempts separate.