Annual software subscriptions: prepayment or accrual?

Short answer: If you pay for a software subscription before you use it, record a prepayment and release it to expense month by month over the service period. If you use the software before the vendor bills you, accrue the cost each month until the bill arrives.

Many annual contracts produce both at once: a prepayment for the base subscription paid at the start of the term, and an accrual for overages or extra seats billed later. This guide sets out the test, the entries, and how auto-renewals and mid-year seat true-ups change them, for finance teams at SaaS and subscription businesses reporting from Xero, QuickBooks Online or Zoho Books.

The test: when you pay versus when you use the software

The classification depends on one comparison: does the payment or invoice come before or after the month in which the software is used? The expense belongs in the months the service is received. The balance sheet holds whatever is out of step with that.

• Paid or invoiced before use. The unused part is an asset, a prepaid expense, and it is released as each month of service passes.
• Used before it is invoiced. The cost already incurred is a liability, an accrued expense, and it is cleared when the bill is entered.
• Invoiced and used in the same month. No adjustment is needed; the bill goes straight to expense.

The test looks at the service period on the invoice, not at the payment terms. A bill dated December 15, 2026 for a January to December 2027 subscription is a prepayment at December 31, 2026, whether it was paid in December or is still in accounts payable.

Paid upfront: the annual subscription as a prepayment

An annual subscription paid at the start of the term is the standard prepayment case. The bill is coded to a prepaid expenses account, and one twelfth is released to the software expense account each month.

Illustrative example: a company pays $24,000 on January 2, 2026 for a finance tool covering January 1 to December 31, 2026. The entries are set out below.

Each month carries $2,000 of software cost, which keeps monthly gross margin and operating expenses comparable. The prepaid balance at any month-end should equal the unexpired months multiplied by the monthly charge, which makes it simple to reconcile. More on setting up the schedule is in how to handle prepayments in your SaaS company.

Used before invoiced: when a software cost is an accrual

A software cost is an accrual when the service has been used but the vendor has not billed it by month-end. This happens most often in three situations:

• Usage billed in arrears. Cloud hosting, API calls or data storage billed after the month on actual consumption.
• Late first invoices. A new contract starts on the first of the month, but the vendor's invoice arrives weeks later.
• Overages above an annual commitment. Usage above the prepaid allowance, billed at quarter-end or year-end.

The accrual is an estimate of the cost incurred in the month, based on the usage report, the contract rate or the previous bill. It is cleared when the bill arrives, usually by a reversing journal dated the first day of the next month. The ScaleXP accruals page describes how accruals can be built from draft bills and purchase orders.

Auto-renewals: what changes when the term rolls over

An auto-renewal starts a new prepayment for the next term. The renewal invoice usually arrives before the renewal date, so at the month-end before the new term begins, the whole invoice is a prepayment and none of it is expense.

Three points are worth checking at each renewal:

• The new service period. Release the new prepayment over the dates on the renewal invoice, not the old schedule, as renewal dates sometimes shift.
• Price changes. A higher renewal price changes the monthly release from the first month of the new term, not before.
• Renewals you intended to cancel. If a renewal goes through by mistake and a refund is agreed, the prepayment stays on the balance sheet as a receivable from the vendor until the credit note or refund arrives, rather than being released to expense.

Keeping a list of software contracts with renewal dates and notice periods, next to the prepayment schedule, means renewals are expected rather than discovered in accounts payable.

Mid-year seat true-ups

A seat true-up is classified by the same test: compare when the extra seats are used with when they are billed.

• Seats billed in advance, prorated to the end of the term. When seats are added in July 2026 and billed immediately for July to December, the invoice is a prepayment released over those six months, alongside the original schedule.
• Seats billed in arrears at the true-up date. When the vendor counts seats at the contract anniversary and bills the excess afterward, accrue the cost each month from the month the extra seats were first used.

Illustrative example: a contract allows 50 seats, and the company uses 60 from April 2026, at $40 per seat per month, billed in arrears at year-end. The company accrues $400 a month from April, so the year-end true-up bill of $3,600 clears an accrual that already holds nine months of cost.

A decision table for software subscriptions

The table below summarizes the treatment for the common billing patterns.

Many teams set a policy threshold below which small annual subscriptions are expensed when billed. That threshold is a materiality decision for the company and its auditor, and it should be written down and applied consistently. Implementation or setup fees for software may follow separate guidance, so agree their treatment with your auditor before adding them to the subscription schedule.

How ScaleXP handles software prepayments and accruals

ScaleXP reads supplier bills and credit notes in Xero or QuickBooks, identifies prepaid expense treatment from the dates, descriptions and line items, and allocates the prepaid amount across the relevant months. Updated bills or credits, such as a prorated seat invoice, trigger controlled schedule and journal updates. For costs used before they are billed, ScaleXP builds accruals from draft bills, purchase orders and your ledger data.

In the ScaleXP demo company below, a software subscription bill is expensed at $417 a month, and the blue figures show the prepayment balance left at each month-end.

ScaleXP prepares the schedules and journals, and they are posted once finance approves them, with each schedule connected to its underlying bill. Finance remains responsible for materiality and policy decisions. See ScaleXP prepayments, how to automate prepaid expenses, and month-end close automation.

Conclusion

Annual software subscriptions are classified by comparing when the service is used with when it is billed. Paid in advance means a prepayment released over the term; used before billing means an accrual until the bill arrives. Applying that one test to renewals and seat true-ups keeps software costs in the right months and the balance sheet easy to reconcile.

Frequently asked questions