## TL;DR

Proration lines confuse because they show raw date math; fix it with plain-language descriptions on the invoice (what changed, for which dates, old vs new plan). Preview the upcoming invoice before the change so support can explain it proactively, and consider invoice line customization to rename the lines. Clarity here directly cuts billing support tickets.

## Steps

1. Preview the upcoming invoice for the plan change before committing.
   Expected: You see exactly the lines the customer will see.
2. Rewrite the line descriptions in plain language: plan name, date range, and whether it is a charge or credit.
   Expected: The invoice reads like an explanation, not a ledger dump.
3. Add a one-line note on the invoice or receipt summarizing the change.
   Expected: Context sits next to the confusing lines.
4. Brief support with the preview so the first ticket gets an instant answer.
   Expected: Support is proactive instead of reactive.
5. Track billing-confusion tickets per change type; simplify the worst offenders.
   Expected: The data shows which changes need better UX.

## When to use

- Customers complain about proration lines
- Plan changes generate support tickets
- You want clearer invoice descriptions

## When not to use

- You want no proration at all (use proration_behavior none)
- The lines are wrong, not just confusing (audit the math)
- The invoice is metered-usage (different line semantics)

## Compatibility

Stripe Billing; upcoming invoice preview; invoice line item descriptions customizable via API.

## Variant phrasings

### ### explain Stripe proration invoice customer

### ### proration line item description

### ### confusing partial period charge Stripe

## Root cause

Proration lines are generated by billing math (unused time credit plus used time charge at second precision), and the default descriptions expose that math raw. Customers think in plans and months, so translating the math into plan names and date ranges closes the comprehension gap.

## Edge cases

- Second-precision date ranges look odd; rounding the description dates is fine, the math stays exact
- Credit lines with negative amounts confuse more than charges; label them as credits explicitly
- Localized invoices need translated descriptions; template them per locale

## Provenance

Resolved from the public thread: https://vectle.com/posts/pst_rgoTa9Sn8Akw-yIJoLypCg