Zenith Core Systems: Allocating a Bundled Banking Platform Contract Under IFRS 15
Zenith Core Systems (Pvt) Ltd (ZCS) signs a three-year contract with a commercial bank on 1 October 2025 with fixed consideration of Rs 240 million, plus a per-transaction fee of Rs 0.40 for volumes above 5 million transactions a year, capped at Rs 30 million. ZCS will (i) license its core banking platform, (ii) customise it to the bank's product set over nine months, and (iii) provide three years of support. The licence cannot be used without the customisation, and the customisation significantly changes the platform's functionality. ZCS's normal standalone prices are Rs 210 million for the combined licence-and-customisation deliverable and Rs 30 million for support. ZCS also resells a third-party data-warehouse appliance for Rs 45 million; it buys it from the vendor for Rs 41 million, the vendor's contract names the bank as customer, and the vendor is responsible for specification compliance. The finance director has recognised the full Rs 240 million as licence revenue on signature, treated the appliance as revenue of Rs 45 million against cost of Rs 41 million, and ignored the transaction fee until billed. Profit before tax is Rs 90 million; materiality is Rs 12 million.
1. Identify the performance obligations in the platform contract and compute the revenue that should be recognised for the year ended 31 December 2025. Explain the effect on reported profit and materiality.
Read the worked answer
Step 1 - Identify performance obligations (IFRS 15.22-30). The licence and the customisation are not distinct. The bank cannot benefit from the licence without the customisation (capable of being distinct), and ZCS is providing a significant integration service because the customisation significantly changes functionality (distinct within the context of the contract). They therefore form a single combined performance obligation. Support is distinct: the bank benefits from it with the platform and it is separately identifiable.
Step 2 - Allocate the fixed consideration on relative standalone selling prices. Combined deliverable: 240 x 210/240 = Rs 210 million. Support: 240 x 30/240 = Rs 30 million.
Step 3 - Recognise the combined obligation over time. The bank receives and consumes benefits as customisation progresses, so an input measure (labour hours or months) is appropriate. At 31 December 2025 three of nine months are complete: 210 x 3/9 = Rs 70 million. Support is straight-line: 30 x 3/36 = Rs 2.5 million.
Step 4 - Effect on profit. Revenue recognised rises to Rs 72.5 million, not Rs 240 million. Total revenue becomes Rs 76.5 million and cost of sales for the appliance falls to nil (see principal/agent point). Reported revenue of Rs 285 million is overstated by Rs 208.5 million; reported profit before tax of Rs 90 million becomes a loss of about Rs 77.5 million, an overstatement of Rs 167.5 million. That is roughly 14 times materiality, so the misstatement is material and pervasive to the revenue line. The contract is also a multi-year arrangement, so the deferred revenue of Rs 137.5 million must be presented as a contract liability.
2. Should ZCS recognise the data-warehouse appliance gross at Rs 45 million or net as a commission? Set out the indicators you would apply and quantify the effect.
Read the worked answer
Framework. IFRS 15. B34-B38 requires an assessment of whether ZCS controls the appliance before transfer - i.e. whether it is principal or agent. No single indicator is decisive; weigh them together.
Indicators against control (agency):
- Primary responsibility for fulfilment rests with the vendor: the vendor's contract names the bank as customer and the vendor is responsible for specification compliance.
- Inventory risk is largely absent - ZCS buys to order at Rs 41 million and the bank's payment is not contingent on resale, so ZCS bears little obsolescence or price risk.
- Pricing discretion is thin: a fixed Rs 4 million spread on a Rs 45 million item suggests a fee, not a margin set by ZCS.
Indicators for control (principal): the legal form is buy-sell, and ZCS may carry credit risk. These are outweighed here.
Conclusion. ZCS is an agent. It should recognise revenue of Rs 4 million (its commission) and no cost of sales, not gross revenue of Rs 45 million with a cost of Rs 41 million.
Effect. Gross profit is unchanged at Rs 4 million, but revenue is overstated by Rs 41 million and cost of sales by Rs 41 million. Rs 41 million is more than three times materiality. Because users assess growth and margin on revenue, and because the misstatement conceals the low-margin, pass-through nature of the business, it is material even though profit is unaffected. It also distorts the gross margin percentage from roughly 8.9% to a meaningless blend when combined with the platform revenue.
3. How should the per-transaction fee be treated, and what disclosures and controls should accompany it? Draft the correcting judgement the finance director should apply.
Read the worked answer
Analysis. The fee is variable consideration (IFRS 15.50-59). The sales-and-usage royalty exception in IFRS 15. B63 applies only to a licence of intellectual property that is a distinct performance obligation. Here the licence is part of a combined obligation that includes a significant integration service, so the exception is not available and the general variable consideration model applies.
Applying the model. Estimate the expected fee and apply the constraint in IFRS 15.56 - recognise only to the extent it is highly probable there will not be a significant revenue reversal. Two factors push toward a constrained estimate: the volume is entirely outside ZCS's control, and the Rs 30 million cap means the fee is a narrow band rather than a reliable expectation. Given the absence of historical volume data at signature date, the recognition should be as usage occurs, in the period the transactions take place, with any minimum fee assessed separately. No amount should be recognised at 1 October 2025.
Allocation. The variable fee relates specifically to the processing service provided after go-live; where the terms relate only to a specific part of the contract, allocate it to that obligation rather than to the combined deliverable (IFRS 15.84-85).
Disclosure. IFRS 15.110-129: disaggregation of revenue, contract liabilities, the method used to measure progress, and the judgement that the licence and customisation are a single obligation. IAS 1.122 requires disclosure of the judgements with the most significant effect.
Control recommendation. The underlying failure is at contract inception - the accounting team was not involved before signature and no checklist forced a five-step analysis. Require accounting review of all non-standard contracts above Rs 25 million, a documented standalone selling price register, and quarterly review of variable consideration estimates against actual volumes.