Skip to content

docs(billing): explain the final invoice after cancellation#12203

Open
jd wants to merge 1 commit into
mainfrom
devs/jd/jd/billing-cancellation-invoice/explain-final-invoice-cancellation--51b3372e
Open

docs(billing): explain the final invoice after cancellation#12203
jd wants to merge 1 commit into
mainfrom
devs/jd/jd/billing-cancellation-invoice/explain-final-invoice-cancellation--51b3372e

Conversation

@jd

@jd jd commented Jul 25, 2026

Copy link
Copy Markdown
Member

Customers who cancel mid-period are told their subscription stays active
through the end of the period they already paid for. When their contributor
count grew during that last period, Stripe collects the accrued prorations on
the next invoice — which, for a cancelling subscription, is the final one,
dated on the very last day. Customers read that as "I cancelled and got billed
anyway" (see Plain T-4504).

The billing page documented the two invoice sections but nothing about
cancellation mechanics or this final true-up. This adds:

  • a paragraph in "Switching or Cancelling Plans" stating the subscription ends
    at period end without renewing, and warning that one last invoice may arrive
    on that final day;
  • a new "3. Final Invoice After Cancellation" subsection under "Understanding
    Your Invoice" explaining that this invoice is a proration true-up for the
    final period, not a renewal, and that nothing is charged after it.

The "Understanding Your Invoice" intro and closing sentence are adjusted since
the page no longer describes exactly two subsections.

Copilot AI review requested due to automatic review settings July 25, 2026 21:33
@mergify
mergify Bot had a problem deploying to Mergify Merge Protections July 25, 2026 21:33 Failure
@mergify

mergify Bot commented Jul 25, 2026

Copy link
Copy Markdown
Contributor

Merge Protections

🔴 2 of 6 protections blocking · waiting on 👀 reviews

Protection Waiting on
🔴 👀 Review Requirements 👀 reviews
🔴 🔎 Reviews 👀 reviews
🟢 🤖 Continuous Integration
🟢 Enforce conventional commit
🟢 📕 PR description
🟢 🚦 Auto-queue

🔴 👀 Review Requirements

Waiting for

  • #approved-reviews-by >= 2
This rule is failing.
  • any of:
    • #approved-reviews-by >= 2
    • author = dependabot[bot]
    • author = mergify-ci-bot

🔴 🔎 Reviews

Waiting for

  • #review-requested = 0
This rule is failing.
  • #review-requested = 0
  • #changes-requested-reviews-by = 0
  • #review-threads-unresolved = 0

Show 4 satisfied protections

🟢 🤖 Continuous Integration

  • all of:
    • check-success = build
    • check-success = lint
    • check-success = test
    • any of:
      • check-success = test-broken-links
      • label = ignore-broken-links
    • any of:
      • check-success=Cloudflare Pages
      • -head-repo-full-name~=^Mergifyio/

🟢 Enforce conventional commit

Make sure that we follow https://www.conventionalcommits.org/en/v1.0.0/

  • title ~= ^(fix|feat|internal|docs|style|refactor|perf|test|build|ci|chore|revert|ui)(?:\(.+\))?!?:

🟢 📕 PR description

  • body ~= (?ms:.{48,})

🟢 🚦 Auto-queue

When all merge protections are satisfied, this pull request will be queued automatically.

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR updates the billing documentation to reduce confusion when customers cancel mid-period but still receive a final (true-up) invoice at the end of the paid billing period.

Changes:

  • Adds cancellation mechanics to “Switching or Cancelling Plans”, including a warning about a possible last invoice on the final day.
  • Adds a new “Final Invoice After Cancellation” subsection under “Understanding Your Invoice”.
  • Adjusts the “Understanding Your Invoice” intro/outro to reflect the added subsection.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment thread src/content/docs/billing.mdx Outdated
@mergify
mergify Bot requested a review from a team July 25, 2026 21:35
Customers who cancel mid-period are told their subscription stays active
through the end of the period they already paid for. When their contributor
count grew during that last period, Stripe collects the accrued prorations on
the next invoice — which, for a cancelling subscription, is the final one,
dated on the very last day. Customers read that as "I cancelled and got billed
anyway" (see Plain T-4504).

The billing page documented the two invoice sections but nothing about
cancellation mechanics or this final true-up. This adds:

- a paragraph in "Switching or Cancelling Plans" stating the subscription ends
  at period end without renewing, and warning that one last invoice may arrive
  on that final day;
- a new "3. Final Invoice After Cancellation" subsection under "Understanding
  Your Invoice" explaining that this invoice is a proration true-up for the
  final period, not a renewal, and that nothing is charged after it.

The "Understanding Your Invoice" intro and closing sentence are adjusted since
the page no longer describes exactly two subsections.

Change-Id: I51b3372e5ac0708699d181f4a5f09ffdc71618b4
@jd
jd force-pushed the devs/jd/jd/billing-cancellation-invoice/explain-final-invoice-cancellation--51b3372e branch from cefb6f3 to 40ccb0c Compare July 25, 2026 21:43
@jd

jd commented Jul 25, 2026

Copy link
Copy Markdown
Member Author

Revision history

# Type Changes Reason Date
1 initial cefb6f3 2026-07-25 21:43 UTC
2 content cefb6f3 → 40ccb0c address Copilot review: reword the 'Understanding Your Invoice' intro so it no longer implies an invoice has three sections — a regular invoice has two, and cancellation produces a separate final inv… 2026-07-25 21:43 UTC

@mergify
mergify Bot had a problem deploying to Mergify Merge Protections July 25, 2026 21:44 Failure
@jd
jd marked this pull request as ready for review July 26, 2026 07:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants