In this article

Five accounts owe nothing this month. One has no work scheduled, one is using its free allowance, another is consuming prepaid credit, a fourth has a broken billing feed, and the last has left for a competitor. A report that labels all five as churned creates five very different operational mistakes.

For a usage-priced product, inspect the path from customer work to consumption to billing. A zero amount due is an observation about one point in that path. To understand retention, the team needs to know what happened before it and what the account is expected to do next.

Keep three records that can be reconciled

The service record describes work performed: a completed analysis, stored document or processed request. The usage record translates that work into the units the commercial agreement counts. The billing record applies allowances, prices and credits, then determines what is owed.

These records will not always have identical totals. An attempt that fails before completion might be excluded from billed usage under your policy. Several product actions might form one billable unit. A prepaid customer can consume units without making a new payment during the same month.

Write the mapping explicitly. For each account and service period, preserve successful work, billable units before allowances, allowance consumed, charges before credits, credits applied and remaining amount due. Keep cash collection in its own field. This is an operational view; it should not be presented as a substitute for the business’s accounting policy.

Read the five zero balances

The following example is invented. Assume a simple service that charges $0.01 per billable unit, with no tax, fixed subscription fee, discounts or other adjustments. The allowance account receives 1,000 included units. The prepaid account has enough eligible credit to cover its $40 charge. “Reported due” means the amount produced from the usage that reached billing.

AccountService units this monthBilling explanationReported dueUseful classification
Seasonal0No units consumed$0Quiet; next expected job needs checking
Allowance800All units inside its 1,000-unit allowance$0Active within included usage
Prepaid4,000$40 charge covered by $40 credit$0Active; consuming prepaid balance
Meter failure1,500No units reached billing$0Usage reconciliation incident
Departed0Customer confirms it stopped using the service$0Known departure

The meter-failure account performed work worth $15 under the stated rate, but that amount is not yet a valid final invoice. Reconcile the missing events and apply the actual billing policy before changing the balance. The table’s purpose is to expose the inconsistency, not to authorize a charge from an analytics report.

The other distinction is just as important: Seasonal and Departed have identical observed unit counts. The confirmed departure supplies information the number cannot. Keep the quiet account unresolved until its cadence or customer context supports a stronger conclusion.

Treat credit consumption as activity

Stripe’s billing-credit documentation describes prepaid and promotional grants that can cover eligible metered charges. Eligibility depends on conditions including the credit’s timing, currency and available balance. A credit-covered invoice therefore needs to be read alongside the underlying consumption.

For the illustrative prepaid account, the customer received service and used part of an existing commercial balance. Sending a “we miss you” message because this month’s cash collection is zero would be poorly targeted. A more relevant product question is whether consumption follows the expected pattern and whether the remaining balance is enough for upcoming work.

Keep prepaid and promotional credits distinct in analysis. Both can reduce the immediate amount due, but they represent different commercial histories. Consumption funded by a free grant does not demonstrate that the customer will buy more when the grant ends. Record the credit’s source and remaining usable balance without treating either as a retention verdict.

Check the meter before contacting the customer

Compare the service record with the usage submitted to billing for the same account and period. Investigate missing events, mismatched account identifiers, duplicate submissions and events assigned to the wrong time window. Use known service completion as the starting point; a quiet usage table alone cannot show whether work stopped.

Stripe’s meter-event API requires a configured event name and a payload containing the meter’s customer and value fields. It also supports an event identifier and timestamp. Those fields illustrate the information needed to trace a product action into billing, although your own reconciliation must account for your implementation and retry policy.

Record a measurement-status field alongside the account classification. “No recorded consumption; reporting incomplete” is more useful than a confident churn label. Keep affected accounts visible in aggregate reporting rather than quietly excluding them and improving the apparent result.

When the pipeline is repaired, revise the affected periods under a documented correction policy. Preserve the earlier operational alert so the team can distinguish a customer returning from data finally arriving.

Give low-frequency customers a relevant clock

A monthly snapshot is convenient for reporting, but the customer’s work may be quarterly, seasonal or triggered by an external event. Establish an expected next-use window from the product job and available customer context. Avoid declaring a universal number of quiet days after which every account has left.

For Seasonal, the next known batch might be due after a quarterly planning meeting. Before that window, no consumption may be ordinary. After the window passes, inspect whether the customer postponed the job, moved it elsewhere or hit a product problem. If the next-use date is unknown, keep that uncertainty visible.

Use the service-level view to assess whether the product remains part of the customer’s work, and the consumption view to assess how much of that work it handles. A customer can remain active while moving a large share elsewhere. A binary active label would miss that contraction.

Route each state to a different decision

The allowance account may need no intervention. The prepaid account may need a balance forecast. The meter-failure account needs an internal fix. Seasonal needs a cadence-aware check, while Departed belongs in departure analysis with the customer’s stated reason preserved.

Review movement between these states over time. An allowance user beginning paid consumption is different from a prepaid user purchasing another balance. Neither should be called a reactivation merely because cash reappears. The account may have been using the product throughout.

Choose the retention denominator around the customer relationship you want to track, and document how credits and allowances affect it. For deciding what usage should represent commercially, see choosing a pricing metric. Before either discussion, reconcile what the customer did, what the meter counted and why the invoice says zero.

Sources

Something we should clarify?

Suggest a correction