August 9, 2026
Service Contracts, Variable Consideration & Customer Prepayments - Part 2 of 5
- IFRS 15
- Business Central
By Shailesh Apte, Chartered Accountant and Business Central Solution Architect
Performance bonuses, penalty clauses, advance payments and billing schedules that never quite match revenue, worked through on Vantage Facilities Management in Business Central’s Subscription module.
“A £2.4 million, three-year contract sounds straightforward, until you read the small print: up to £120,000 a year of performance bonus if the KPIs are hit, a £60,000 penalty if they slip. Quarterly billing in advance, and an annual CPI uplift. So how much revenue do you recognise in month one?” |
Recap from Part 1: one contract, many documents in Business Central
Before we get to that number, one point from Part 1 is worth restating, because everything in this series builds on it. Part 1’s central claim was never really about revenue timing. It was architectural. A single contract splits across three documents: a Sales Order for the goods or services, a Project for the implementation, and Subscription Billing for the recurring services. Business Central posts where the work actually happens, on each document, then uses a single tag running through every posting (the CONTRACT dimension) to reunite them into one IFRS 15 contract. |
Sales Order | Project (Jobs) | Subscription Billing |
Goods or service Point in time The perpetual licence and the hardware. Billed at quoted price, recognised at a point in time when control transfers. | Implementation Over time The professional-services element. Planning lines and WIP, recognised over time on percentage-of-completion. | Recurring services Over time Support and any ongoing service. Billed and deferred, released pro rata across the term. |
That is the idea the whole series stands on: Business Central lets one contract span many documents and still report as one.
And the SSP allocation? It sits on none of the three. The calculation is recognition-only. It is posted by journal to a balance-sheet contract-control account, tagged with the CONTRACT dimension, and never appears as a field on any order. Each document keeps billing at its quoted price; the allocation is the practitioner’s overlay.
With that foundation in place, Part 2 goes deeper into the one step Part 1 kept deliberately clean: Step 3, the transaction price, and what happens when the money arrives before the work does.
THE RUNNING CASE Company: TechCo Ltd (from the D365PPUG stage) Customer: RetailCo UK Ltd Contract value: £150,000 Framework: IFRS 15 and UK FRS 102 Section 23
→ TechCo’s transaction price is a clean £150,000. No variable consideration, no financing element. That is the easy case. The deeper example below, Vantage Facilities Management, is the opposite: bonuses, penalties and CPI steps on a single contract. |
DEEPER EXAMPLE Company: Vantage Facilities Management Customer: NHS Trust Services: Cleaning & Maintenance Contract value: £2,400,000 (base annual value £800,000 for 3 years) Billing: Quarterly in advance Performance bonus £120,000 / yr if average KPI score across sites is above 95% £60,000 / yr if average KPI score across sites is 90% to 95% Nothing if average KPI score is between 85% and 90% Penalty clause £60,000 / yr if average KPI score across sites falls below 85%, deducted in the final-quarter payment. All KPIs are measured quarterly and reported to the NHS Trust. CPI escalation: Annual (each January)
* SSPs equal contract price here, so there is no discount to allocate (contrast Post 1’s Meridian bundle). The bonus and penalty are variable consideration, assessed separately under Step 3. |
Step 3 deep-dive: variable consideration
The bonus and penalty are variable consideration. IFRS 15 requires Vantage to estimate the amount it expects, then apply the constraint: include variable consideration only to the extent that it is highly probable a significant revenue reversal will not occur when the uncertainty resolves. When in doubt, leave it out until it is highly probable.
Two estimation methods
Expected value | Most likely amount |
Probability-weighted The probability-weighted sum of outcomes. Best where a range of partial outcomes is possible, for example where the KPI can land in several bands. This is the method Vantage uses. | Single outcome The single most likely outcome. Best for binary results, for example where the bonus is either earned or not. Suited to a straight pass or fail clause. |
Expected value: Year 1
Vantage reviews KPI performance on comparable NHS contracts over the last three years and assigns the following probabilities:
Scenario | KPI band | Bonus/(Penalty) | Probability | Weighted (£) |
|---|---|---|---|---|
Full bonus | ≥ 95% | 120,000 | 55% | 66,000 |
Partial bonus (50%) | 90-95% | 60,000 | 30% | 18,000 |
No bonus, no penalty | 85-90% | 0 | 10% | 0 |
Penalty applied | < 85% | (60,000) | 5% | (3,000) |
Expected value of variable consideration | 100% | 81,000 |
Applying the constraint to Vantage’s estimate
The expected value comes to £81,000, but the constraint asks a different question: is it highly probable that including this amount will not lead to a reversal later?
Vantage concludes that it is highly probable it will earn at least the 50% partial bonus of £60,000. The step up to the full £120,000 bonus, however, carries real reversal risk from factors outside its control (for e.g. site access and emergency lockdowns among them), so that portion stays outside the estimate entirely.
This leaves the constrained variable consideration for Year 1 at £60,000, with nothing recognised incrementally beyond that. At year-end, the outcome resolves directly to one of the four contractual bands: £(60,000), £0, £60,000, or £120,000.
Year 1 transaction price = £800,000 base + £60,000 constrained bonus = £860,000. |
Configuration in Business Central: a two-track structure
Track 1 Base fee (£800,000): Subscription Billing in Business Central
• This is Business Central’s standard Subscription Billing module, with deferral working as designed. No manual journal is needed for this piece.
Customer Subscription Contract CUC000003 · NHS Trust, with cleaning and planned-maintenance lines.
• Billed quarterly in advance via Recurring Billing: £200,000 × 4 = £800,000
Account Type | Account Head | Debit (£) | Credit (£) |
|---|---|---|---|
Customer | NHS Trust | 200,000 | |
General Ledger | Contract Liability (Deferred Revenue) | 200,000 |
• Recognised monthly via deferral release: £800,000 ÷ 12 = £66,667 / month (60% cleaning + 40% maintenance split), released from the contract liability as service is performed.
Account Type | Account Head | Debit (£) | Credit (£) |
|---|---|---|---|
General Ledger | Contract Liability (Deferred Revenue) | 66,667 | |
General Ledger | Revenue: Cleaning | 40,000 | |
General Ledger | Revenue: Maintenance | 26,667 |
A detailed, screen-by-screen walkthrough of setting up the Subscription Contract, the Recurring Billing lines, the Billing Proposal, and the deferral release schedule in Business Central will be covered in Blog Post 3. |
Track 2 Constrained bonus (£60,000): General Journal
• Not billed monthly: there is nothing to invoice until the KPI outcome is confirmed.
• Recognised monthly via the IFRS15-VAR journal: £60,000 ÷ 12 = £5,000 / month.
Account Type | Account Head | Debit (£) | Credit (£) |
|---|---|---|---|
General Ledger | Contract Asset | 5,000 | |
General Ledger | Revenue (Variable) | 5,000 |
• At year-end, when the estimate matches the outcome, a Sales Invoice for £60,000 is raised.
Account Type | Account Head | Debit (£) | Credit (£) |
|---|---|---|---|
Customer | NHS Trust | 60,000 | |
General Ledger | Contract Asset | 60,000 |
THE PROFESSIONAL PATTERN: A DEDICATED VARIABLE-CONSIDERATION JOURNAL Variable consideration is an accounting judgement, not a billing mechanic, so it is right that Business Central does not try to automate it. The robust setup is a standalone IFRS15-VAR journal, dimensioned to CONTRACT, that carries the constrained estimate and absorbs the true-up when the KPI or outcome is confirmed. This keeps billing and recognition cleanly separated and fully auditable. Build the journal structure at contract inception; do not wait for the first estimate to force the decision. |
Year 2: CPI escalation is a price change, not a modification
On 1 January 2027 the CPI clause lifts the base fee by 3.5%, from £800,000 to £828,000. Because the clause was in the original contract, this is a change in transaction price and not a contract modification. It is applied
prospectively:
Year 2 transaction price | Amount (£) |
|---|---|
Base fee post-CPI (£800,000 × 1.035) | 828,000 |
Constrained variable consideration | 60,000 |
Total Year 2 transaction price | 888,000 |
Monthly recognition rises to £888,000 ÷ 12 = £74,000. Update the Business Central service contract’s annual amount and re-run the revenue schedule to regenerate the remaining deferral entries.
UP NEXT · POST 3 Subscription Billing & Recognising Revenue Pro Rata Over Time Cloud Axis SaaS Ltd bills annual subscriptions upfront and releases them month by month. We build Business Central’s Subscription Billing deferral template end to end: the setup, the schedule, and every posting across hundreds of subscription lines. |
📝 This post reflects the author’s professional views and is for informational purposes only. It does not constitute legal, financial, or accounting advice. |