Afternoon logoAfternoon

Accounting for AI tokens and prepaid credits

Updated 2026-09-24

Tokens measure usage. Credits describe a balance or unit defined by the seller. Neither term, by itself, tells you how to record the transaction.

For accounting, start with the contract: what did the buyer pay for, when did the seller provide it, and what rights remain? Then separate the buyer's expense from the seller's revenue.

This guide uses illustrative accrual-accounting entries. A contract's terms and your accounting framework can change the treatment.

Credits you buy vs. credits you sell

EventBuyerSeller
Payment for future serviceMay record a prepaid assetGenerally records a contract liability for service still owed
Service consumedRecords expense or another qualifying costRecognizes revenue as required by the contract and accounting rules
Unused balance expiresReviews the remaining asset and any lossReviews breakage rules and legal obligations
Cash paymentChanges cash and the related balanceChanges cash and the related balance

A balance shown in a vendor dashboard is useful evidence, but it is not a complete accounting policy. Check whether it represents paid credits, a promotion, a commitment, or an amount already billed.

For the pricing distinction, see AI credits vs. tokens.

Match the records to the payment model

Payment modelWhat to track
Usage billed in arrearsService consumed, accrued cost, later invoice, and payment
Prepaid balanceEach purchase, usage deduction, refund, and expiry
Subscription with an allowanceSubscription period, included units, and any overage charge
Automatic reloadEach new cash purchase as well as the usage that triggered it

Calculate a token charge using the applicable input and output rates, plus any other priced categories such as cached inputs. Save the model, rate version, units, and service period. A combined token count is not enough when the categories use different rates.

Keep a subscription purchase separate from API credits unless the contract says the subscription includes those rights. Check current vendor terms instead of relying on an old model price or credit expiry rule.

Buyer example: Prepaid API usage

Assume you pay $1,000 for future API service and consume $250 during the month. Assume the remaining rights meet the criteria for a recoverable prepaid asset.

At purchase:

AccountDebitCredit
Prepaid API services$1,000
Cash$1,000

When you consume the service:

AccountDebitCredit
API expense$250
Prepaid API services$250

The closing prepaid balance is $750.

Classify the cost by its use. API calls that deliver your customer product may belong in cost of revenue. Calls for internal research or administration may belong elsewhere. Apply a consistent policy; the vendor name does not determine the account.

If a balance expires or becomes unusable, review whether you still have an asset. Do not keep an expired balance on the books merely because the original payment was called a credit purchase.

Buyer example: Usage billed after month-end

Assume $250 of API service was consumed in the month, qualifies as a current expense, and has not yet been invoiced. These amounts are illustrative.

EventDebitCredit
Record the month's usageAPI expense $250Accrued expenses $250
Receive the matching invoiceAccrued expenses $250Accounts payable $250
Pay the invoiceAccounts payable $250Cash $250

Match the invoice to the accrual and resolve any difference. Do not expense the same usage again when the bill arrives.

If the $750 remaining in the prepaid example later expires with no refund or usable rights, the illustrative write-off is a $750 debit to loss on unused credits and a $750 credit to prepaid API services. Review recoverability before expiry too, rather than waiting for a dashboard balance to reach zero.

Seller example: Customer prepayment

Assume a customer pays $1,000 for future service and earns no separate benefit at purchase. Under the example's recognition policy, $250 of that service is delivered during the month.

At purchase:

AccountDebitCredit
Cash$1,000
Deferred revenue$1,000

As the service is delivered:

AccountDebitCredit
Deferred revenue$250
Usage revenue$250

The remaining $750 reflects service still owed. Do not record the cash receipt and later usage as two separate sales.

These entries assume usage measures the service transferred under the contract. Minimum commitments, distinct services, and other terms can change the analysis. See usage-based revenue recognition.

How to handle free credits

A promotional grant is not the same as receiving cash for future service. Do not automatically debit marketing expense and credit deferred revenue for the face value of every free credit.

Review whether the offer is a discount, a customer right tied to a paid contract, or a separate promotion. Record the actual costs of providing the service under your expense policy. A paid contract that includes free units may require allocation of its transaction price.

Track promotional grants separately so they do not inflate cash-funded balances or paid consumption. For a buyer, keep no-cost promotional units separate from purchased credits. Do not assign them a prepaid cost merely because the dashboard shows a face value. Review offers tied to a paid contract under that contract's terms.

How to handle unused credits and breakage

Expiry alone does not always permit immediate revenue recognition. Consider the customer's rights, whether the company expects to be entitled to an unused amount, the applicable recognition constraints, and unclaimed-property obligations.

Deloitte's discussion of ASC 606 breakage explains why the answer depends on the facts. Keep the estimate and supporting evidence with the close records.

Do not recognize an expected unused amount and then recognize the same balance again when it expires.

What to reconcile each month

For purchased credits, reconcile opening balance, purchases, usage, refunds, and expiry with the vendor statement.

For customer credits, reconcile the credit ledger with payment receipts, usage charges, refunds, promotions, and the general ledger. Investigate negative balances and late usage rather than forcing the ledger to equal cash.

Keep these records:

  • The contract and price version.
  • Paid and promotional credit lots.
  • Usage by customer and service period.
  • Refunds, adjustments, and expiry.
  • The method used to translate usage into revenue and cost.

Use a SaaS chart of accounts that keeps prepaid assets separate from customer liabilities.

Keep different AI services and costs visible

ServiceUsage or contract detail to retain
Text generationModel and separately priced input, output, or cached units
Image, audio, or video workThe billed unit, such as image count or processed duration, and the applicable rate
Fine-tuning or trainingTraining charges, related project, rights obtained, and later hosting or inference charges
Embeddings and storageProcessing charges separately from ongoing storage or access fees

The unit changes the calculation, not the need to assess what was delivered. A plan to use a trained model for a long time does not, by itself, justify capitalizing training costs. Apply the relevant development or software-cost rules with your accountant.

Tag shared vendor spending by team, project, and product. Review budget alerts and unusual usage during the month, then reconcile the provider statement with those records at close. A spending alert does not guarantee a hard cap.

For buyers, useful measures include total spend, cost per project, cost per completed task, and paid credits left unused. For sellers, review revenue and delivery cost by model or service, credit use by purchase group, refunds, and expired rights. Keep promotional use separate and define the unit and period before comparing a cost-per-token or utilization measure.

Do tax rules follow these entries?

Not necessarily. Tax treatment depends on the taxpayer's method, applicable advance-payment and prepaid-expense rules, and other facts. A book deferral does not by itself defer taxable income, and a cash payment does not always create an immediate deduction.

For U.S. prepaid expenses, the 12-month rule addresses certain rights or benefits that end by the earlier of twelve months after they begin or the end of the tax year after payment. It is not a blanket deduction for every short-lived credit balance; other deduction and accounting-method rules still matter.

For sellers, qualifying advance payments may allow limited tax deferral under an eligible method. That does not mean all prepaid credits stay outside taxable income until customers use them.

The IRS accounting methods guide describes these rules. Review the tax treatment separately with the preparer rather than copying book entries into the return.

Does a prepaid balance guarantee a hard spending cap?

No. That is a system behavior, not an accounting property. Your records must include usage incurred during any delay in enforcement. For implementation, see how to build prepaid AI credits.