Skip to main content
Gruv Logo
Proration

Plan changes without making subscribers guess.

Preview the financial impact of upgrades and downgrades before they apply. Subscribers, support, and finance see the same outcome.

Preview adjustmentsUpgrade and downgrade policiesCredit tracking
Plan changeacme-coffee.co · mid-cycle
From
Growth · $49/mo
switched · Oct 15
To
Scale · $249/mo
effective · Oct 15
Oct 1Billing periodOct 31
14 days used on Growth16 days remaining on Scale
Growth · Oct 15–31 (16 days)-$26.13
Scale · Oct 15–31 (16 days)+$128.52
Credit carried over-$12.00
Due today
$90.39

How it works

Where plan changes get expensive.

Surprise mid-cycle charges

Without a clear preview of credits and debits, a valid upgrade feels like a billing mistake.

Support calculates manually

Every plan change becomes a spreadsheet exercise. Support becomes the billing calculator.

Finance loses credits

Unused time, deferred charges, and credits need a clean trail or month-end becomes hard to reconstruct.

Policy is inconsistent

Immediate, next-renewal, or mix per plan and segment. Most teams need different rules.

Plan changes around preview and policy

Explicit proration rules, visible outcomes, and downstream invoice context. Easier to approve and explain.

  • Preview before commit

    Show subscriber or operator what the change will do before billing finalizes.

  • Upgrade policies

    Bill immediately, create an adjustment, or follow a different timing per rollout.

  • Downgrade and credit

    Track unused time and future credits cleanly so downgrades do not create accounting confusion.

Plan changes around preview and **policy**
Capabilities

What plan-change teams need

Proration preview

Financial effect visible before anyone approves it.

Upgrade handling

Control how and when mid-cycle upgrades create charges.

Downgrade handling

Keep unused-time credits easy to track and explain.

Policy controls

Immediate, deferred, or no-proration based on plan rules.

How it works

From plan change to reconciled adjustment

Proration change control

A finance operations team can preview upgrade, downgrade, and mid-cycle change math before applying credits or debits, then keep the adjustment attached to the invoice trail.

Proration change control

Frequently Asked Questions

How is proration calculated?+
Unused value on current plan plus new value on target plan in the remaining window. The credit and charge stay visible before the change applies.
Can I disable proration for certain plans?+
Yes. Different behavior per plan, segment, or policy. Immediate, deferred, or no proration are all supported.
What happens to downgrade credits?+
Tracked so they apply cleanly to future billing, not a support exception. Treatment depends on your finance policy.
Can I preview plan changes?+
Yes. That is the core goal. Internal or subscriber-facing preview makes the billing impact explicit before commit.
How does Gruv AI fit into this feature?+
Gruv AI runs payout automation, compliance gates, exception handling, and an Ask Gruv AI workspace across every product. Each feature inherits the same AI surface, so rules, holds, and reconciliation context stay consistent across the workflow.
Can I start with this feature and add more later?+
Yes. Gruv is modular, you can start with a single workflow and expand to additional modules as your requirements grow.
How do integrations work?+
Integrate via APIs and webhooks, or start with file imports/exports for a fast evaluation. Email ingestion can help with lightweight backfills when needed.
What affects coverage, methods, and timelines?+
Coverage, methods, and timelines vary by market and are subject to compliance and policy checks. Confirm your target corridors and payout methods during evaluation.
Is this tax or legal advice?+
No. Tax and compliance features vary by jurisdiction and customer configuration. This content is for informational purposes and is not tax or legal advice.

Simplify plan changes.

Preview the financial impact of upgrades and downgrades before they apply. Subscribers, support, and finance see the same outcome.

Many teams start with a narrow launch in weeks; timelines depend on scope and integrations.