Accounting for AI SaaS Companies: Usage, Revenue and Costs
Connect customer usage, billing, revenue recognition and provider costs without confusing a credit balance, an invoice or a cash receipt with earned revenue.
Accounting for an AI SaaS company requires a traceable connection between customer contracts, product usage, billing, recognized revenue and delivery costs. Keep those records separate enough to explain timing differences, then reconcile them by customer and period. A successful API request, a credit deduction and a cash receipt can describe different events.
This becomes visible when a customer buys credits in advance, consumes them over several months, and triggers costs from more than one model provider. The product needs to know how much access remains. Finance needs to know what was sold, what was delivered, what was earned and what it cost.
Keep five records connected
Start with the identifiers that let the team trace an amount through the process. A customer may have several workspaces, and a workspace may use several models. Neither automatically identifies the legal entity that signed the contract.
| Record | What it should explain | Useful connection |
|---|---|---|
| Contract | Price, service obligations, credit terms and effective dates | Customer and contracting entity |
| Product usage | What happened, when, and whether it is billable | Workspace, customer and unique event |
| Billing | Charges, credit applications and corrections | Contract version and usage period |
| Accounting | Revenue, receivables, liabilities and cash | Invoice, service period and policy |
| Provider costs | Resources consumed and amounts billed or estimated | Workload, provider and cost period |
Retain a correction trail when usage arrives late or is reversed. If a request is retried, establish whether it created one billable customer outcome, several provider charges, or both. A retry should not become a second customer charge merely because the event was imported twice.
Separate product credits from accounting balances
Credit systems can represent prepaid purchases, promotional grants or contractual allowances. Those categories need distinct records even when the product displays one combined balance.
Stripe's explanation of billing credits distinguishes paid and promotional credits and describes applying credits to invoices. That explains a billing mechanism. The company's accounting treatment still depends on its contracts and applicable accounting framework.
For IFRS reporters, IFRS 15 links revenue recognition to satisfying performance obligations. Receiving cash or issuing credits alone does not establish that the promised service has been delivered. Contract terms, refunds, expiry rights and the nature of the service can change the analysis.
Document the chosen treatment before automating entries. Keep promotional credits, purchased credits and refunds identifiable so the accountant can assess them without reconstructing product events from a dashboard total.
A synthetic monthly example
Assume a customer pays EUR 1,000 in advance for services consumed at an agreed rate. For this simplified example, the finance team has determined that EUR 300 of service is delivered during the month and that the remaining advance relates to undelivered service. There are no refunds, promotional credits, tax or currency differences.
| Movement | Debit | Credit |
|---|---|---|
| Advance received: cash | EUR 1,000 | — |
| Advance received: contract liability | — | EUR 1,000 |
| Service delivered: contract liability | EUR 300 | — |
| Service delivered: revenue | — | EUR 300 |
The closing contract liability is EUR 700. In this deliberately simple contract, the product's remaining purchased-credit value also equals EUR 700. Real credit balances may use different units or include promotional amounts, so establish a reconciliation rather than assuming equality.
Suppose the same month's identified model-provider cost is EUR 90 and assigned hosting cost is EUR 30. Revenue less those two selected costs is EUR 180, or 60% of revenue. Label that calculation precisely: it excludes support, other delivery costs and overhead, and is not automatically the company's reported gross margin.
If the provider invoice has not arrived, preserve the usage-based estimate and reconcile it to the actual bill later. The accountant determines any accrual and subsequent adjustment under the company's policy. The estimate should not disappear when the invoice is imported, nor should both remain counted as final cost.
Explain cost allocation before comparing customers
Some provider costs can be tied directly to a customer request. Shared hosting, reserved capacity, internal experiments and idle resources may require allocation or separate reporting.
The FinOps Foundation's AI overview treats allocation and unit economics as part of understanding AI costs. For your own reports, name the unit and the included costs: cost per successful job, per customer workspace or per service period. Tokens can help explain provider consumption, but they do not by themselves measure the outcome sold to a customer.
Keep the allocation method visible. A report based on request count answers a different question from one based on measured provider consumption. Changes in the method should be identifiable so a margin movement is not mistaken for a change in operating performance.
A practical close checklist
Before accepting the month, work through the connections:
- Reconcile billable usage to invoice calculations, including corrections and excluded events.
- Reconcile purchased credits, applications and refunds to the relevant customer balances.
- Review revenue against the service delivered and the approved recognition policy.
- Reconcile provider usage estimates to invoices and explain remaining accruals.
- Separate customer delivery, internal development and shared costs using documented definitions.
- Check customer, entity, currency and period mappings before combining results.
Give each difference a reference, owner and proposed resolution. A total that ties only after an unexplained adjustment is not a finished reconciliation.
Where Arfiti fits
Arfiti provides accounting records, recurring contracts, billing workflows, dimensions and revenue or prepaid-expense schedules. Compatible assistants can inspect evidence and submit supported actions through governed tools. Recognition schedules and allocations implement configured choices; they do not decide the correct accounting policy for every AI contract.
Your product's usage collection and customer mappings still need to be designed and verified. This article does not assume that connecting Arfiti automatically imports every model provider's usage or resolves every credit arrangement.
For invoice preparation, use the billing-run review checklist. If you are evaluating a ledger change, the QuickBooks migration guide covers a separate decision: what must move and how to validate the cutover.
Request access to discuss your contract, usage and reporting workflow. Bring one representative customer period so the required evidence and boundaries are concrete.