Usage Billing Review

Accrued Expense Debit or Credit in SaaS Usage Billing

Usage billing fixes the journal entry, but estimating the amount is the hard part.

· 8 min read
Cover illustration for “Accrued Expense Debit or Credit in SaaS Usage Billing”
Accrued Revenue Accounting · November 13, 2026 · 8 min read · 1,888 words

Accrued expenses in SaaS usage billing enter as a debit to expense and a credit to accrued liabilities. The accounting direction is fixed, but the amount often is not. Variable consumption, AI workloads, non-calendar invoicing and prepaid credits make accurate period-end accounting depend on reliable metering data.

Why accrued expenses always enter as a debit to expense and a credit to a liability

Accrual accounting assigns a cost to the period in which the business received the benefit, regardless of when an invoice arrives or cash leaves. The matching principle applies under both US GAAP and IFRS. For consumed services that have not yet been invoiced, the entry debits the relevant expense account and credits accrued liabilities. The debit recognizes the cost of the service. The credit recognizes the obligation to pay for it.

For example, a company recording $5,000 of consumed but unbilled cloud hosting records a debit to Cloud Hosting Expense of $5,000 and a credit to Accrued Liabilities of $5,000. That entry reduces the period’s profit and establishes a current liability on the balance sheet. It does not move cash out of the business. Waiting for the invoice would instead leave the expense and liability out of the period that incurred them.

When the invoice arrives, the accrued liability is cleared and the unpaid bill becomes accounts payable. Payment then clears the payable and produces the cash outflow. Accrued expenses cover services received but not yet invoiced, while accounts payable covers invoices received but not yet paid. With prepaid expenses, payment comes before consumption. The rule is simple when the amount is known in advance.

How the timing gap between metering and invoicing forces an estimate into every accrual

Usage-based billing removes that certainty because the service can be consumed before its final charge is available. A company may use cloud infrastructure or API calls throughout January and get the provider’s invoice in mid-February, but need to close January before that invoice arrives. Finance must record an estimate of what the company owes before it knows the final amount.

In practice, finance teams use provider dashboards such as AWS Cost Explorer and Google Cloud Billing to obtain month-to-date charges on the last day of the period. That figure supplies a basis for the entry. It is close to the expected invoice amount, but it is not necessarily identical to it. The gap between the estimate and the eventual charge creates a variance that must be accounted for when the bill arrives. Metering and invoicing therefore affect separate stages of the same expense.

To make the two-period split concrete, suppose the January accrual is $5,000 and the actual bill is $5,150. If the accrual remains in place and the bill is paid on arrival in February, the entry debits Accrued Liabilities by $5,000, debits Cloud Hosting Expense by $150, and credits Cash by $5,150. The January expense remains the original $5,000 estimate, and February records the $150 variance. If the bill is still unpaid, the credit goes to Accounts Payable.

Another option is to use an automatic reversal and then record the actual invoice. The essential distinction is between clearing the estimated liability and recognizing the difference from the final charge. Small charges may be handled more simply under a materiality policy that is written down and applied consistently, often with a floor of a few thousand dollars below which charges are expensed right away. Such a policy is limited to immaterial amounts, while significant costs still require reliable estimates. Stable usage makes estimation manageable, but volatile consumption removes that support.

Why AI and high-velocity consumption models make the estimation problem materially worse

Token prices may fall while spending rises sharply because usage volume grows faster than the price reductions. Last month’s bill is therefore a poor anchor. A finance team using it as the current accrual may materially overstate or understate the expense, even when it understands the direction of price changes.

With a fixed subscription, the previous bill can provide the amount needed for the next accrual. With volatile AI usage, that continuity is absent. The estimate must instead use current consumption across the cost dimensions that apply, including tokens, GPU-minutes and API calls. Near-real-time metering shows how much was used in that period. Without it, finance cannot distinguish a reasonable estimate from a historical figure that no longer represents the service consumed.

Scale makes the consequence more severe. A small percentage error on a small AWS bill may be immaterial, while the same percentage error on a large AI inference bill may lead to a material misstatement. Materiality still depends on the financial statements as a whole, with the size of any one invoice considered in that context. Where an error is material, it could require an audit adjustment or restatement. Under US GAAP, missed or badly estimated accruals can also leave unrecorded liabilities that become an audit finding.

A subsequent true-up does not remove that reporting risk. Although the difference can be recorded when the invoice arrives, repeated large adjustments create P&L volatility and distort margin reporting across periods. They can also mislead investors and signal weak financial controls to auditors. Current consumption data is therefore both an accounting control and a way to make operations easier. Even when current data is reliable, it must still be split correctly when the vendor’s invoice cycle crosses the end of the buyer’s reporting period.

How mid-period invoicing and arrears billing add a second timing layer to the accrual cycle

A vendor that bills on the 15th of each month for the prior period creates two distinct obligations at a January 31 close. The January 15 invoice covers December 15–January 14. If that invoice remains unpaid, it belongs in accounts payable. Consumption from January 15–31 has occurred, but its invoice has not yet arrived. That portion belongs in accrued liabilities, even though both amounts are owed to the same vendor.

The January 15 invoice crosses the December and January accounting boundary, while the next invoice will include usage after January 31. Finance needs the consumption dates to assign costs to the right month, as well as the invoice status to classify the obligation. The total owed to a vendor alone does not show either split.

The general ledger must therefore keep the payable and the accrued liability separate. Posting the unbilled portion into accounts payable overstates AP and understates accrued liabilities, even if the combined liability remains unchanged. AP aging reports can then include amounts that do not correspond to received invoices, and cash flow forecasts can be distorted.

A fixed monthly subscription invoiced at the start of the period does not create this particular split. It leads to a prepaid or immediate expense entry, while non-calendar usage billing in arrears leads to payable and accrual entries at the same time. A monthly rule such as dividing annual value by 12 cannot show where to put the usage cutoff. The calculation must follow the actual days of consumption within the accounting period and the usage attributable to them. For audit cutoff testing, finance must be able to show which consumption days belong in each period and whether an accrual or payable covers them.

How prepaid credit wallets flip the accrual direction and create a deferred revenue liability instead

Prepaid credits reverse the buyer’s timing problem because cash leaves before the service is consumed. At purchase, the buyer records a debit to Prepaid Asset and a credit to Cash. As credits are drawn down, it records a debit to Expense and a credit to Prepaid Asset. No accrued expense liability arises from that prepaid purchase. The accounting task shifts from estimating an unpaid obligation to measuring how much of a paid-for resource has been used.

The distinction becomes important when a vendor offers both postpaid usage and prepaid capacity. A buyer may then hold a prepaid asset and an accrued liability for the same underlying vendor at the same time. The general ledger must keep these different positions separate so that consumption reduces the appropriate prepaid asset or contributes to the appropriate accrued expense. Treating all usage as postpaid would hide the asset the buyer has already paid for.

Many SaaS companies also sell AI-powered products, so they face the vendor-side pattern as well. When a customer buys credits, the seller records a debit to Cash and a credit to Deferred Revenue. As the customer consumes those credits, the seller debits Deferred Revenue and credits Revenue. The liability shrinks as the service is delivered. Under ASC 606, sold credits are not all revenue on day one, and unused-credit breakage must follow the constraint on variable consideration.

Volatility also affects the seller’s forecast of when deferred revenue will convert to recognized revenue. That projection depends on the pace of consumption, which can be as uncertain as the buyer’s postpaid accrual estimate. Actual recognition, however, depends on the record of what was consumed. Every drawdown must be recorded against the wallet balance in real time to support accurate deferred revenue accounting for the seller and prepaid asset accounting for the buyer. The same event-level evidence connects the two sides, even though their journal entries differ.

What the accrual cycle demands from billing and metering infrastructure at period-end

To meet these accounting requirements, finance needs a complete consumption record that is accurate across all cost dimensions whenever it closes, as well as when billing generates an invoice. A dashboard is useful only if its underlying data is timely and trustworthy. Delays in event ingestion, duplicate events and records that arrive late can all make the estimate it shows less reliable. Real-time ingestion must support an accurate record of the consumption belonging to the period.

Idempotency and late-arrival handling are therefore accounting controls as well as engineering requirements. Counting an event twice overstates consumption, while assigning a late-arriving event to the wrong period breaks the expense cutoff. Both errors flow into the accrual estimate. A trustworthy metering layer must preserve the relationship between the consumption event and its period of use. Otherwise, the finance team's task becomes reconciling defects in the record, a separate problem from estimating a genuinely uncertain charge.

The system must also report usage by exact date range, as well as by invoice cycle. For the mid-period example, finance needs to distinguish January 15–31 consumption from the December 15–January 14 invoice period. Credit wallets impose an additional requirement for an event-level drawdown ledger. Each credit consumption event must have a timestamp, fall in the correct period and be available to query by date range. End-of-cycle aggregation alone cannot provide that accounting evidence.

When engineering owns the metering system and finance must ask for reports, the close depends on when another team is available. Finance-accessible consumption data removes that reporting bottleneck. A unified metering and billing system also removes the separate reconciliation step between event ingestion and invoice generation. Assembling those functions separately leaves a seam where data gaps can become accrual errors.

The operational cost appears when finance spends the first week of every month reconciling billing data before it can close the books. That work reflects a billing stack that was not designed to produce period-accurate consumption records. Correct journal-entry direction cannot compensate for missing or misallocated usage. From the finance team’s perspective, accrual accuracy is achievable when the billing system was designed to support it.

More in Accrued Revenue Accounting