In March 2025 someone working for an EU institution posted to OpenAI's developer forum under the title "You should notify users about expiring credit, or how I lost 400 USD." The institution had bought $400 of API credits in late 2023, the credits had lapsed unused, and the poster now had to "reimburse my institution the entire amount." The reply they quoted from OpenAI support said refunds weren't possible because "purchased credits are valid for one year from the date of issue and are non-refundable." Their complaint was mostly about the lack of notice: "it's appalling you don't even notify users by email or else about the expiration date."
A few months earlier a German developer had cited Section 307 of the German Civil Code, the clause on unfair standard terms, and asked for the remaining $500 back. Later in the same thread they reported that the credits had come back, then corrected themselves: the old balance hadn't been restored, it had been replaced with "a new amount that expires in 12 months."
The earlier posts in this series were about usage, the events that drain a balance; this one is about the balance nothing drains.
The same rule at three providers
OpenAI, Anthropic and Google all sell prepaid API credit, and all three put a one-year clock on it. OpenAI's help centre says purchased credits expire after one year and that it cannot extend the date. Anthropic's credit terms say "Usage Credits expire one calendar year from the date Anthropic sends the Confirmation Notice," that credits also lapse if the customer closes the account, and that they "are non-refundable." Google's AI Studio billing page says "Purchased credits expire after 1 year. After expiration, credits are forfeited and can't be retrieved," with one way out: if a customer switches from Prepay to Postpay, "any remaining prepaid credits are automatically refunded."
Anthropic does warn customers beforehand. A Hacker News thread titled "Anthropic expires paid credits after a year" was started by someone posting the email they'd received naming the date their organisation's credits would lapse. The commenters split two ways. One argued that the rule comes from accounting, since a vendor can't recognise credits that never expire as revenue, and said their own company had moved a contract from non-expiring credits to a three-year expiry for that reason. Another pointed out that some jurisdictions don't let prepaid balances expire at all.
The accounting point is close to the standard, if a little stronger than it. Under ASC 606-10-55-48, as quoted by PwC, a seller that expects some prepaid rights to go unused, which accountants call breakage, recognises the expected amount "as revenue in proportion to the pattern of rights exercised"; one that can't estimate it waits until "the likelihood of the customer exercising its remaining rights becomes remote." An expiry date puts that point on the calendar: whatever the vendor hasn't already estimated as breakage sits as a liability owed in usage until the date, and stops being one after it.
Modelling it, on paper
As before, this maps the published rules onto Revenue Cloud Usage Management using the public data model in the SalesforceLabs repository. It's a thought experiment, not a claim about how any of these providers bill, and the platform behaviours are the repo's account of them, not something I've run.
A credit purchase looks like a grant: a ProductUsageGrant, the included allowance, pointing at a UsageGrantRolloverPolicy that the repo describes as "unused grant rollover rules." At activation the platform writes a TransactionUsageEntitlement for the asset, and that row carries an EffectiveStartDateTime, an EffectiveEndDateTime and a lookup to the rollover policy. One year from purchase is an end date on that row, and each top-up writes another row with its own end date. So a customer who buys credit four times in a year is holding four lots in one balance, each on its own clock, and the German developer's case shows what extending one looks like from the outside: the vendor issues a new lot with a new date rather than moving the old date.
Once there are several lots, something has to decide which one a request draws from. Google publishes part of its answer: "promotional credits will be consumed first before your prepaid funds," and eligible Google Cloud credits go before the Prepay balance. Zoom, whose AI Credits run on three expiry clocks in one pooled balance (monthly for plan credits, a year for packs, the billing cycle for prepaid commitments), lists the order as the user's licence credits, then "prepaid commit credits or prepaid credit pack credits," then pay-as-you-go. That puts packs and commitments in the same step without saying which of the two is used up first, and that choice decides how much expires. A lot drawn first is less likely to lapse, so drawing the soonest-expiring lot first leaves the least breakage and drawing the newest first leaves the most. The repo records that a field named DrawdownOrder was one of four removed from TransactionUsageEntitlement between the 262 and 264 releases, so whatever the order is, the entitlement row doesn't hold it any more. Who pays for the discount covered the order between a commitment, an allowance and overage; the order between lots of the same allowance is the same kind of decision, and it's harder to see on an invoice because every lot is priced the same.
The expiry itself is the part a usage pipeline isn't built to see. Every object in the runtime layer exists because an event arrived: a TransactionJournal row lands, a summary absorbs it, a bucket decrements. Expiry is the absence of events up to a date. Nothing lands in a journal and nothing is rated, so if the design zeroes a lot on its end date the balance falls without a usage row explaining why, and finance books the forfeited amount as revenue in the period the date falls in, which may be closed by the time anyone asks about it (the close was the subject of an earlier post). The rated usage and the revenue for that period then differ by the forfeited amount, and the only record that reconciles them is whatever the design writes when the clock runs out.
Rollover is the other way to handle the date, and it brings its own condition. Snowflake's 10-K says a customer that underuses its capacity "may have the option to roll over any unused capacity to future periods, generally upon the purchase of additional capacity." It's close to what OpenAI did for the German developer, except that the contract makes a new purchase the condition for the old balance surviving.
The EU poster's complaint was about notice, which Anthropic sends before the date and which the OpenAI poster says never came. A notice like that has to come from somewhere, and the only place the date lives is the end date on each lot. If a customer holds four lots and the vendor chooses the draw order, which balance does the warning email quote, and what does the customer have to see to check it?
No comments yet