Credit Burndown
Credit Burndown Definition
Credit burndown is the rate at which a customer's prepaid credits are consumed by their usage. In a credits-based billing model, the customer buys a bundle of credits up front, each unit of metered usage draws the balance down against a rate card (for example, one credit per API call or per thousand tokens), and the remaining balance determines when they need to top up, when they hit overage pricing, or when unused credits expire.
Burndown matters to finance as much as to the customer. The unconsumed credit balance is a contract liability (deferred revenue), and revenue is recognized as credits burn down, so the burndown record is also the revenue recognition record. A burndown that does not tie back to metered usage means both the customer's balance and the deferred revenue account are wrong.
Also referred to as: credit drawdown, credit consumption, prepaid credit burndown, burn rate (credits).
How credit burndown works
The lifecycle has four steps. First, a credit grant: the customer purchases or is allocated a block of credits, often with an expiry date. Second, rating: each metered event converts to credits through a rate card, which is where pricing actually lives in a credits model. Third, drawdown: rated usage reduces the active balance, oldest grants first in most designs. Fourth, resolution: the balance is topped up (manually or by auto-refill), runs to zero and shifts to overage billing, or expires with value unused.
AI products made this model mainstream. Token packs, per-agent credits, and prepaid compute bundles are all credit burndown systems: the vendor gets cash and commitment up front, and the customer gets a spending abstraction that is stable even as underlying model costs shift.
Why burndown drives deferred revenue
A credit purchase is not revenue. At purchase, the seller records deferred revenue for the full amount, and recognizes revenue only as credits are consumed. A $60,000 credit pack that is 20% consumed in a month produces $12,000 of recognized revenue that month, with $48,000 remaining as a contract liability. The deferred revenue balance in the general ledger should always tie to the value of unconsumed, unexpired credits.
Expired credits (breakage) are the judgment auditors test: expected breakage can be recognized proportionally as consumption occurs, but the estimate has to be documented and supportable, which makes clean burndown history the evidence behind the revenue number.
Where burndown tracking breaks
The common failure modes: balances tracked in a spreadsheet next to the billing system, drawdown computed from invoiced amounts instead of metered usage, negative balances nobody catches, expiry dates that are never enforced, and a deferred revenue account that cannot be tied to the sum of open credit balances. Each one either leaks revenue or misstates it.
The fix is treating credits as a reconciled subledger problem: grants, corrected usage, and balances kept per account and per metric, with the drawdown traceable from raw events through the rate card to the recognized revenue it produced.
When you'd use this
- Modeling how long a customer's prepaid credit pack will last at current usage
- Explaining why prepaid credit sales sit in deferred revenue rather than revenue
- Designing expiry, rollover, and auto-refill rules for a credits-based pricing plan
- Reconciling open credit balances to the deferred revenue account at close
Related Guides
The full model: credit packs, drawdown mechanics, expiry, and worked rev-rec journal entries.
How metered usage is rated and billed, with or without a prepaid credit layer.
How raw events become the corrected usage totals a burndown depends on.
Credit Burndown FAQ
What is the difference between credit burndown and credit drawdown?
They describe the same thing. Drawdown usually refers to the mechanical reduction of the balance as usage is rated, while burndown often refers to the rate or trajectory of that reduction over time (as in a burndown chart). In billing systems the terms are interchangeable.
How is revenue recognized on prepaid credits?
As the credits are consumed, not when they are purchased. The purchase creates deferred revenue (a contract liability), and each period's consumption converts that liability to recognized revenue. Expired credits are handled through a breakage estimate, which is a variable-consideration judgment that needs documented support.
Should credits expire?
Expiry creates urgency and limits liability tail, but it also creates breakage accounting and customer friction. Many B2B vendors use 12-month expiry with rollover on renewal, and enforce it in the billing system rather than in the contract alone, because an expiry date nobody enforces is a liability that never clears.
How do you reconcile credit balances?
Per account: active grants minus corrected lifetime usage for each metric or currency should equal the reported balance, and the sum of open balances should tie to the deferred revenue account. If drawdown is computed from anything other than metered, deduplicated usage, the reconciliation will not hold.