Industry News & Expert Tips
Cloud Computing Services: Business Model, Audit Issues and Evidence
Industry-specific audit considerations, tailored procedures, and evidence points for Hong Kong audit teams.
Industry Overview
Last updated: 16 September 2026
Cloud computing providers commonly earn recurring fees for software, platform or infrastructure capacity, together with usage-based charges for computing, storage, data transfer, support and implementation. The commercial model may combine direct subscriptions, reseller or marketplace routes, prepaid credits, consumption commitments and third-party infrastructure. Auditors need a clear view of what is promised to customers, who controls the promised service, how consumption is captured and how contract changes feed the financial-reporting process.
For Hong Kong entities applying HKFRS, the timing and measurement of revenue from customer contracts require careful analysis under the principles of HKFRS 15, particularly where arrangements contain multiple services, variable usage fees or incentives. The audit response should be tailored to the entity's product architecture, billing data flow, reliance on service providers and estimates, with sufficient evidence to support the conclusion rather than a generic check of invoices.
Key Audit Issues
Service promises, contract changes and revenue timing
Cloud arrangements can combine access to a hosted application, platform functionality, infrastructure capacity, implementation, support and optional features. The accounting analysis may be affected by whether these are distinct promised services, the period over which the customer receives the benefit, contract modifications, prepaid commitments and non-refundable upfront amounts. A documented understanding of the commercial terms and the basis for the entity's revenue policy is important.
Completeness and accuracy of usage-based billing
For IaaS, PaaS and consumption-priced SaaS, revenue often originates in automated metering records rather than a manually prepared invoice. Risks arise where usage events are lost, duplicated, changed after capture, mapped to the wrong customer or rate plan, or excluded by an interface failure. The integrity of the metering-to-billing-to-ledger data flow is therefore central to both completeness and accuracy.
Principal-versus-agent and variable consideration judgements
A provider may bundle third-party cloud capacity, licences, marketplace offerings or managed services with its own service. Judgement may be needed over the nature of the promised service and whether revenue is reported on a gross or net basis. Credits, service-level rebates, usage discounts, refunds and sales incentives can also affect the transaction price and the adequacy of related estimates.
Capitalised development expenditure and impairment indicators
Cloud businesses may incur significant expenditure on internally developed software, implementation capability, acquired technology and data-centre or network assets. The classification of expenditure, useful-life assumptions, amortisation and assessment of indicators of impairment can be judgemental, especially where customer churn, price pressure, product obsolescence or a failed deployment changes expected economic benefits.
IT dependency, cybersecurity events and third-party operations
Financial information may depend on identity and access management, release management, system interfaces, cloud-hosting providers and automated logs. An outage, security incident or uncontrolled production change may affect service delivery, billing completeness, customer claims or the reliability of information used in the financial statements. The audit team should understand relevant IT and third-party dependencies without assuming that a vendor report alone resolves all risks.
Tailored Audit Procedures
Map the revenue architecture and perform walkthroughs
Obtain an understanding of each material revenue stream, including direct subscription, usage, implementation, support and reseller channels. Walk selected transactions from customer onboarding and pricing approval through metering, billing, revenue recognition, cash collection and the general ledger; identify relevant applications, interfaces, manual adjustments and responsible personnel.
Inspect representative customer arrangements
Select contracts and material amendments across the principal service models and inspect the promised services, pricing, renewal and termination clauses, usage commitments, credits, acceptance provisions and reseller terms. Evaluate whether management's documented revenue analysis is consistent with the contract and with the high-level HKFRS 15 principles applied by the entity.
Test the meter-to-bill-to-ledger data lineage
For selected periods and customers, trace billed and recognised revenue to underlying immutable or controlled usage records, approved rate cards and customer master data; recalculate charges where practicable. Test both directions, from usage to the ledger for completeness and from the ledger to usage and contracts for occurrence, and investigate reconciling items.
Perform focused cut-off and analytical testing
Test transactions and usage records around period end, including delayed billing, credits, reversals and post-period adjustments. Compare recurring revenue, active customer counts, consumption volumes, average pricing, churn and deferred revenue movements with prior periods, budgets and other operational information, and obtain explanations and corroboration for unusual relationships.
Assess gross-versus-net presentation and variable amounts
For material third-party capacity, marketplace or reseller arrangements, inspect the commercial agreements and evaluate management's assessment of the promised service and presentation. Test selected credits, rebates, refunds and discount calculations to source records, and evaluate whether estimates and related disclosures are supported by current experience and contractual terms.
Evaluate development-cost accounting and related estimates
Inspect a risk-based sample of development and technology expenditure, project approvals, timesheets or other cost records, and management's capitalisation analysis. Assess the consistency of useful-life and amortisation assumptions with product roadmaps and actual use, and consider whether operational or market evidence identifies a need for further impairment analysis.
Controls and Evidence to Consider
Approved contract, product and price catalogue
Maintain executed customer agreements, approved amendments, a controlled product catalogue and effective-dated price tables. Evidence of independent approval of non-standard terms, discounts, credits and changes supports the link between the commercial arrangement and the accounting treatment.
Metering and billing reconciliations
Perform and retain periodic reconciliations from source usage events to rating, invoices, deferred-revenue schedules and the general ledger. Exception reports should identify rejected events, duplicate records, unmatched customers, manual overrides and late postings, with documented investigation and resolution.
Access, change and interface controls
Use role-based access, periodic access reviews and approved production-change processes for systems that capture usage, maintain rate tables or post billing entries. Retain change tickets, testing or release evidence, interface monitoring and logs of privileged or manual changes relevant to financial reporting.
Third-party assurance and operational incident records
Retain vendor contracts, relevant service-organisation reports where available, management's review of complementary controls, service-level monitoring and records of significant outages or security incidents. These records help management and auditors assess the effect of third-party operations on billing data, service obligations and financial-reporting estimates.
Related Reading
Apply Industry Insight to Your Audit Workflow
EQC can discuss audit-quality priorities, documentation, inspection readiness, and Audit Program 4.1 (AP4.1) workflow support relevant to your practice.