Prepaid AI Credits and Rollover: How to Separate Cash, Grants and Consumed Units

Three balances, three rules

An API vendor may issue trial credit on account creation, reset a plan’s recurring allowance every billing month, and separately accept purchased prepaid credit. A trial may have an expiry date unrelated to account creation; a subscription allotment may roll over conditionally; purchased credit may have its own expiry and permitted-service restrictions. The first step in a credit ledger is to store a source-backed balance_type field for every grant and purchase. A single aggregate “remaining credits” counter is insufficient when one pool expires next week and another can be spent next quarter.

A first-party example with explicit expiry terms

ElevenLabs’ October 9, 2026 terms discuss prepaid credit purchases and state that, unless otherwise specified, those prepaid credits expire twelve months after purchase or issuance. They also describe non-transferability and nonrefundability subject to applicable law. That is a term for a defined ElevenLabs credit product—not a general rule covering every AI subscription. Other vendors vary materially: Udio’s 2026 documentation distinguishes monthly subscription limits from purchased à-la-carte credits and a one-time promotional grant. Store each rule with the original legal document, checked date and jurisdiction.

Credit valuation is different from credit count

A USD purchase can be recorded as currency cash, while the wallet’s spend events are counted in a proprietary unit. If a hypothetical buyer purchases 50,000 credits for a documented, account-specific USD amount, the effective cost per unit is purchase amount divided by 50,000 before any relevant fees. Do not reuse a conversion rate from another provider or from an introductory discount. If the wallet is replenished with multiple purchase batches, FIFO or other supported accounting allocation may matter for determining which expiry date and acquisition price apply. Financial recognition is jurisdiction- and policy-specific and may require professional advice.

Forecast expiry losses separately

A low advertised unit cost is not economical if prepaid credit expires before enough eligible work arrives. Calculate expected burn from real output volumes, then stress-test a lower-usage month, project pauses and rejected generations. Treat free credit as a separate promotional subsidy and do not convert an uncertain future grant into guaranteed cash savings. Likewise, never infer that “unlimited” plan marketing applies to all fast jobs, output types and queue tiers. A finance reviewer needs transaction-level provenance, not an averaged credit number detached from its source.

Implementation and user decisions

The archive’s pricing calculator should accept purchase date, grant source, quantity, currency, expiration date, eligible meters, monthly reset and application priority. Unknown expiry or redemption order should remain null and be flagged. Alert staff before spendable balances vanish and prevent the calculator from summing vendor A’s credits with vendor B’s. When the contract changes, add a new dated rule rather than rewriting historical spend, preserving both the old policy and the source that governed it.

Decision checklist and limitations

Before purchase or deployment, retain the literal model or plan identifier, payer/merchant, country or cloud region, billing currency, exact usage meter, source URL, checked date, effective date if explicitly supported, and any plan commitment or promotional eligibility. Recalculate from the companion price and quota snapshots rather than assuming that a remembered list tariff will remain unchanged. A credit allowance, maximum input length, published token rate and confirmed billed currency answer different questions; never add them as if they were the same quantity.

When comparing another provider or route, use the same input/output distribution and acceptable result definition. Include unsuccessful attempts, optional tools, storage, tax, payment and human review only when those components are actually measured or supported by an explicit source. Vendor marketing and documentation are not independent product tests. This article makes no claim to have personally tested paid endpoints, purchased plans, or checked account-specific taxes or availability.