Who it's for: anyone who posts supplier invoices, runs the prepayments schedule or reviews software spend in a SaaS or tech finance team.
What you'll get: when a software subscription is a prepayment, how to build and reconcile the schedule, worked journals for annual, mid-term and overseas subscriptions, and a one-slide pitch for getting software spend under control.
Reading time: about 10 minutes. Long enough to find three tools nobody uses any more.
Why software prepayments deserve their own process
SaaS companies buy a lot of SaaS. Annual subscriptions for CRM, engineering tools, security, design and data are often paid upfront, on company cards, by people outside finance. Book them straight to the P&L and one month takes a huge hit while the other eleven look cheap.
A tidy prepayments process spreads each cost over the months it covers, catches renewals before they happen, and gives you a live list of what the company is paying for. That last part is often worth more than the accounting.
Key terms
- Prepayment: a cost paid before the period it relates to. It sits on the balance sheet as an asset and is released to the P&L month by month.
- Release (or amortisation) of a prepayment: the monthly journal that moves the right slice of cost to the P&L.
- Service period: the dates the subscription covers, which may not match the invoice date.
- Reverse charge: a VAT mechanism for services bought from overseas suppliers, where the UK buyer accounts for the VAT itself rather than the supplier charging it.
- Materiality threshold: the amount below which a team chooses to expense a cost straight away rather than prepay it, to save effort.
When is a software subscription a prepayment?
Under FRS 102 and IFRS, a cost paid in advance for services you'll receive in future months is typically recorded as a prepayment and expensed as the service is received. For software subscriptions, that means:
| Situation | Common treatment |
|---|---|
| Monthly subscription, billed monthly | Expense in the month. No prepayment needed. |
| Annual subscription paid upfront, above your threshold | Prepayment, released evenly over the service period |
| Annual subscription below your threshold | Many teams expense it immediately, as a documented policy |
| Multi-year subscription paid upfront | Prepayment; the part beyond 12 months is often shown as a non-current asset |
| Usage-based or overage charges | Expense as used; accrue if the invoice comes later |
| Implementation or setup fees for cloud software | Usually expensed, or prepaid if they relate to a distinct future service. Capitalising them as an intangible is rare for cloud software you don't control, so check your policy |
Set a written threshold, for example "annual software under £1,000 is expensed". It saves hours of tiny releases and it's an easy decision to defend at audit, as long as it's applied consistently.
Step by step: the monthly prepayments routine
| Task | What "done" looks like | |
|---|---|---|
| ☐ | Review the month's supplier invoices and card spend for software | Every annual or multi-month software charge identified |
| ☐ | Check each invoice for the service period, not just the invoice date | Start and end dates recorded for each |
| ☐ | Post new prepayments to the balance sheet | Cost coded to prepayments, not the P&L |
| ☐ | Add each one to the prepayments schedule | Supplier, amount, dates, monthly release, P&L code, owner |
| ☐ | Post the month's releases | Release journal agrees to the schedule total |
| ☐ | Reconcile the schedule to the ledger | Schedule closing balance = prepayments balance in the ledger |
| ☐ | Check upcoming renewals in the next 60 to 90 days | Owners asked to confirm renew, resize or cancel |
Many accounting systems, including Xero, QuickBooks, Sage and NetSuite, can set up scheduled or recurring journals for prepayments, either built in or through add-ons. They save posting time, but the schedule still needs reconciling every month.
AI shortcut: give an approved AI tool the month's purchase ledger and card transaction export and ask it to list every software charge that looks annual or multi-month (large one-off amounts from subscription suppliers, or wording like "annual" or "12 months" on the invoice). It's a first pass; a person checks the invoices and decides what gets prepaid.
Worked example 1: an annual subscription paid upfront
MonthEndClub Co Ltd, a fictional UK SaaS company, buys an annual CRM subscription from a UK supplier. The invoice is dated 1 October and covers 1 October to 30 September next year. Price £18,000 plus VAT of £3,600. Paid by bank transfer.
October: post the invoice to prepayments.
| Account | Dr | Cr |
|---|---|---|
| Prepayments | £18,000 | |
| VAT input tax | £3,600 | |
| Trade creditors | £21,600 |
Each month, October to September: release one-twelfth. £18,000 ÷ 12 = £1,500.
| Account | Dr | Cr |
|---|---|---|
| Software subscriptions (P&L, sales and marketing) | £1,500 | |
| Prepayments | £1,500 |
At 31 October, the prepayment balance is £18,000 − £1,500 = £16,500, covering the 11 months still to come.
Worked example 2: a mid-month start and an add-on
On 15 November, MonthEndClub Co Ltd buys an annual engineering tool for £7,300 (ignore VAT for simplicity), covering 15 November to 14 November next year. Many teams release by days for accuracy, or by whole months for simplicity. Both are fine if the policy is consistent.
By days: £7,300 ÷ 365 = £20 per day. November covers 16 days (15 to 30 November), so the November release is 16 × £20 = £320. A full 31-day month is £620, and a 30-day month is £600.
By months: £7,300 ÷ 12 = £608.33 a month, with a common rule that a start on or before the 15th counts as a full month.
In March, the team adds seats, invoiced at £2,400 for the period 1 March to 14 November (8.5 months). Treat it as a separate line on the schedule with its own dates: monthly release £2,400 ÷ 8.5 = £282.35, with half a month in November (£141.20 after rounding, so the total is exactly £2,400). Keeping add-ons as separate lines makes the schedule much easier to follow.
Worked example 3: an overseas supplier and the reverse charge
MonthEndClub Co Ltd buys an annual analytics subscription from a US supplier for £12,000. No VAT is shown on the invoice. As a UK VAT-registered business buying services from overseas, the company typically accounts for VAT under the reverse charge: it declares output VAT and claims the same amount as input VAT on the same return. For a fully taxable business, the net VAT effect is nil. The rules have conditions, so check HMRC's guidance on the reverse charge for services.
| Account | Dr | Cr |
|---|---|---|
| Prepayments | £12,000 | |
| Trade creditors | £12,000 | |
| VAT input tax (reverse charge, 20%) | £2,400 | |
| VAT output tax (reverse charge, 20%) | £2,400 |
The monthly release is £12,000 ÷ 12 = £1,000. If the invoice is in US dollars, the prepayment is typically recorded at the exchange rate on the transaction date and isn't revalued later, because a prepayment is a non-monetary item. The creditor, until paid, is revalued.
Reconciling the prepayments schedule
| Prepayments roll-forward, October | £ |
|---|---|
| Opening balance, 30 September | 42,000 |
| Add: new prepayments in October (CRM) | 18,000 |
| Less: releases in October (all items, including CRM £1,500) | (6,800) |
| Closing balance, 31 October | 53,200 |
The closing £53,200 should agree to the ledger. If it doesn't, the usual causes are an invoice posted to prepayments but not added to the schedule, a release posted twice, or a cancelled subscription still on the schedule. Also check for "zombie" lines: items with a balance after their end date.
AI shortcut: give an approved AI tool the prepayments schedule and the ledger detail for the prepayments account, and ask it to list any ledger postings not on the schedule, any schedule lines past their end date with a balance left, and any releases that don't equal amount ÷ months. A person investigates each item.
If you report under US GAAP (ASC 606)
ASC 606 is about revenue, so it doesn't change how you account for software you buy. Under US GAAP, prepaid expenses work the same way in practice. Implementation costs for cloud computing arrangements have specific guidance (ASC 350-40), which can require some of them to be deferred and expensed over the subscription term. If you're part of a US group, check its policy.
Common mistakes and audit watch-outs
- Using the invoice date instead of the service period. A December invoice for a January start shouldn't release anything in December.
- Annual card spend expensed in full. Card transactions skip the purchase ledger review. Check card spend for annual charges every month.
- Cancelled subscriptions left on the schedule. If a tool is cancelled early and there's no refund, the remaining balance is typically written off.
- No threshold, or an inconsistent one. Decide, write it down, apply it.
- Forgetting the reverse charge on overseas software. It's a common VAT return error.
- Letting AI decide what's a prepayment. AI can misread service dates or miss a credit note. It suggests; a person decides.
Tools that can help
Accounting systems such as Xero, QuickBooks, Sage and NetSuite handle scheduled releases through built-in features or add-ons. Spend management tools such as Pleo capture card receipts and can flag recurring software charges. A simple schedule in Excel or Google Sheets works well for most smaller teams. Tools post the journals; they don't replace the reconciliation or the renewal review.
Take it to your boss: one slide
Getting software spend under control
The problem: annual software is bought on cards by many teams. Costs land in the wrong months, renewals happen automatically and nobody has a full list.
Three changes
- One schedule: every annual tool on the prepayments schedule, with an owner and renewal date.
- A 90-day renewal check: owners confirm renew, resize or cancel before the date.
- AI first pass on card spend: flag annual and duplicate subscriptions each month, reviewed by finance.
| Risk | Control |
|---|---|
| Costs in the wrong month | Schedule reconciled to the ledger monthly |
| Unwanted auto-renewals | Renewal list reviewed 90 days ahead |
| Duplicate tools | Quarterly review of the schedule by category |
| AI misreads an invoice | Approved tools only; finance checks every flag |
How we'll measure it: unreconciled prepayment balance (target zero), renewals reviewed before the date, and annual saving from cancelled or resized tools.
Rates, thresholds and rules in this guide
Figures were checked against the pages below in October 2026. They change regularly (often each April or at Budget time), and we can't guarantee they're still current or right for your situation. Always check the official page before relying on them.
- VAT on services from abroad (GOV.UK): how the reverse charge works for services bought from overseas
- VAT rates (GOV.UK): the 20% standard rate used in the examples
Key takeaways
- Annual software paid upfront is typically a prepayment, released over the service period.
- Use the service dates, not the invoice date.
- Set and document a threshold below which you expense straight away.
- Reconcile the schedule to the ledger every month and clear zombie lines.
- Use the schedule to manage renewals; it's often where the real savings are.
- AI is good at spotting annual charges in card and ledger data; a person decides and signs off.
FAQs
Should a prepaid software licence be capitalised as an intangible asset?
Usually not for cloud subscriptions, where you're paying for access to the supplier's software rather than controlling an asset. Perpetual licences you own and control may be different. Check your accounting policy.
Release by days or by months?
Either works if you're consistent. Days are more accurate for mid-month starts; months are simpler and are what many teams use for smaller items.
Can AI build the prepayments schedule for us?
It can draft one from invoices and card data, including service dates and monthly releases. Someone still checks each line against the invoice and reconciles the total to the ledger before it's relied on.
Related guides
- Accruals and Prepayments: A Practical Guide with Examples
- Cloud Hosting Costs: Accruing, Allocating, and COGS vs Opex
- Balance Sheet Reconciliations: What Good Looks Like
- Month-End FX Revaluation, Step by Step
More in Costs and Accruals guides.
From the Club
Released evenly over twelve months of month-ends. The Team Mug · The Triple Tick Bag
Join the Club. New guides, early access and members-only batches. Join here.
This guide is general information about common practice. It isn't tailored to any business, and standards, tax rules and figures change. Check your own circumstances, the latest rules and, where needed, a qualified professional before acting.
Last reviewed: October 2026.