Revvly
Docs
Customers

Subscription Variable Usage

The live counter for one meter on one subscription.

Overview

Whenever a Variable Component is part of a Subscription, Revvly maintains a counter row that tracks current and cumulative usage, peak values, rollover units, and (for commission components) GMV / transaction counts. The counters drive overage charges, true-up invoices, and limit enforcement. Counters reset according to the Variable Component's limit period configuration. For a component whose quantity resets each period, the counter is not the last word: when the period closes Revvly captures the accumulated total as a Usage Reading before the counter resets, and the invoice for that period waits until the reading is sealed or waived. That is what stops a metered period being billed on a number nobody looked at, and it is why an integration that goes quiet holds an invoice rather than quietly billing zero — see the Capture metered usage guide.

How it connects

This concept highlighted in context. Click a peer to navigate.

Subscription Variable Usage
  • One per (Subscription, Meter) pair
  • Updated by the Event Ingestion API
  • Closes into a Usage Reading each period on components that reset
  • Drives Variable Invoice Lines

Key fields

What you’ll see when creating or editing a Subscription Variable Usage.

Subscription + Meter
What this counter belongs to
Reset behaviour
Carries forward / Resets each period
Billed value
Highest observed / Total over the period / Value at period end
Capture mode
API (an integration increments it) / Manual (an operator enters it)
Current / cumulative
Live counters
Peak count + reached at
For peak-mode metrics
Rollover units
Unspent quota carried into next period
Period start / end
Billing-period bounds
Commission counters
GMV, transaction count, refunded amount (commission components)

Example

Acme · seats
Current15 seats
Peak this period17 seats
ModePeak