Deferred revenue arises when a business receives customer consideration before it has recognized the related revenue.
For companies applying IFRS 15 Revenue from Contracts with Customers, this amount is generally presented as a contract liability when the customer pays—or payment becomes due—before the business transfers the promised goods or services.
“Deferred revenue” and “unearned revenue” are still widely used business and accounting terms, but contract liability is the more precise IFRS 15 terminology for this situation.
Revenue recognition then depends on the underlying contract.
Under IFRS 15, a business:
This means receiving cash does not automatically create revenue.
For example, if a customer prepays for a service that will be delivered over the following 12 months, the initial receipt may create a contract liability. That liability is then reduced as the related performance obligation is satisfied and revenue is recognized.
Common situations include subscriptions, memberships, maintenance contracts, service retainers, and other customer advance payments. To better understand unearned revenue, let’s look at some real-world examples.
Suppose a customer pays SAR 12,000 upfront for a 12-month service that is transferred evenly throughout the year.
The business initially records a contract liability and may recognize SAR 1,000 per month if recognizing revenue evenly faithfully reflects the transfer of the service.
However, equal monthly recognition should not be applied automatically to every annual contract. The recognition pattern must reflect how the relevant performance obligation is satisfied under IFRS 15.
If a customer pays for equipment in advance but control of the equipment has not yet transferred, the seller generally records the advance as a contract liability rather than revenue.
Revenue is recognized when the applicable performance obligation is satisfied.
A customer may pay upfront for support available throughout a contract period.
The business must determine whether the service represents a performance obligation satisfied over time and select an appropriate measure of progress.
When a business sells a gift card redeemable for its own goods or services, it normally has an obligation to provide future goods or services rather than immediate revenue.
However, gift-card accounting can become more complex where cards expire, customers are expected not to exercise all rights, or third parties are involved. It should therefore not be reduced to a universal “recognize everything only when redeemed” rule without considering the specific arrangement.
Deferred revenue separates cash collection from revenue recognition.
A business may already have the customer's cash but still have an obligation to transfer goods or services.
Recording that amount as a liability helps the financial statements show both facts correctly.
Revenue should reflect the transfer of promised goods or services rather than simply the timing of customer payment.
Under IFRS 15, revenue is recognized when or as a performance obligation is satisfied.
Until the business satisfies the relevant obligation, the advance payment represents an obligation to the customer.
This is why IFRS 15 uses the concept of a contract liability for consideration received or due before the related good or service is transferred.
If a full annual subscription were recognized as revenue immediately even though the related service will be provided throughout the year, revenue could be reported in the wrong periods.
Deferred revenue also highlights an important distinction:
Cash received is not necessarily revenue recognized.
The cash can already be available to the business even though some or all of the corresponding accounting revenue remains to be recognized.
For Saudi companies, the precise accounting treatment should follow the entity’s applicable SOCPA-endorsed financial-reporting framework rather than assuming that every entity follows exactly the same version of full IFRS.
Now, let’s explore how deferred revenue differs from deferred expenses, another important concept that may impact your finances.
Accounting concepts are quite complex. When you understand the differences between Deferred Revenue and Expenses, you’ll have a clearer picture of how to manage both in your business. Here’s how they differ:
To better understand how unearned revenue impacts your finances, let’s find out why it is considered a liability and how it affects your accounting records.
Under IFRS 15, where a customer pays consideration—or an unconditional amount becomes due—before the business transfers the promised goods or services, the transaction is generally presented as a contract liability.
The liability reflects the business’s outstanding obligation to provide the customer with the promised goods or services.
As those obligations are satisfied, the corresponding portion of the contract liability is reduced and revenue is recognized.
Do not apply a simple rule that every balance expected to remain for more than 12 months is automatically non-current.
Current/non-current presentation also considers the entity’s normal operating cycle and the applicable presentation requirements. The 12-month test remains important, but it is not the only classification principle under IFRS.
The timing of revenue recognition for accounting purposes does not automatically determine when Saudi VAT becomes due.
This distinction is critical for customer advances.
ZATCA’s VAT rules specifically recognize situations where consideration is received before the taxable supply occurs, and the applicable invoicing and VAT timing rules can therefore arise before the business recognizes accounting revenue.
For continuous supplies, ZATCA also provides specific timing rules based on events such as the payment due date, actual payment, or invoice issuance.
Businesses should therefore maintain separate logic for:
IFRS revenue recognition → contract liability → Saudi VAT date of supply and invoicing
rather than assuming all three occur on the same date.
Deferred revenue becomes actual revenue when the business fulfills its part of the deal—i.e., when the product is delivered or the service is performed.
This follows the revenue recognition principle under accrual accounting, which states that revenue should be recognized when it is earned, not when cash is received. For example, if your business sells a 12-month subscription and receives full payment at the start, only a portion of the payment is recognized as revenue each month.
Now, let’s look at a detailed example of how a company records and then recognizes deferred revenue.
Assume a customer pays SAR 24,000 on January 1 for a 12-month service beginning immediately, and the service is transferred evenly over the contract period.
The business has received cash, but the related service has not yet been fully provided.
If the performance obligation is satisfied evenly throughout the 12-month period:
SAR 24,000 ÷ 12 = SAR 2,000 per month
After January, the remaining contract liability would be SAR 22,000, assuming no other changes.
The same recognition pattern would continue only if it appropriately reflects how the service is transferred to the customer. IFRS 15 requires an appropriate measure of progress for performance obligations satisfied over time.
Understanding how this revenue is recorded helps us see its impact on financial statements. Let’s explore how it affects your balance sheet and income statement.
When an advance payment creates a contract liability, cash increases and the corresponding liability is recorded until the related performance obligation is satisfied.
The customer payment does not automatically become revenue when cash is received.
Revenue is recognized when or as the relevant performance obligation is satisfied under IFRS 15.
The cash can be received before accounting revenue appears in profit or loss.
This is why a business can have strong customer cash collections while still reporting a substantial contract-liability balance.
Contract liabilities can affect working-capital and liquidity measures.
A large deferred-revenue balance is not automatically positive or negative: it means the business has received consideration while still having obligations to customers.
Accounting deferral does not necessarily defer VAT.
ZATCA rules can require VAT accounting and invoicing when advance consideration is received, depending on the supply and transaction type.
Finance teams therefore need to reconcile:
These balances may move on different timelines.
Properly managing deferred revenue helps maintain financial accuracy and supports long-term business growth. Let’s now explore the best ways to track and manage it effectively.
Maintain a clear record of:
Do not recognize revenue merely because a month has passed.
Determine whether the performance obligation is satisfied:
For obligations satisfied over time, use an appropriate measure of progress in accordance with IFRS 15.
Periodically reconcile:
Opening liability + new advances − revenue recognized ± adjustments = closing contract liability
This helps identify customer advances that have been omitted, duplicated, or recognized incorrectly.
Cancellations, refunds, upgrades, extensions, price changes, and other contract modifications can affect both the remaining liability and future revenue recognition.
Customer advances should be reviewed for both:
The dates will not necessarily match.
Accounting or ERP systems can help record customer advances, invoices, recurring transactions, journal entries, and related ledger activity.
However, businesses should verify whether a system provides true IFRS 15 revenue-recognition automation rather than assuming recurring billing and revenue recognition are the same thing.
By staying organized and using the right tools, you can manage unearned revenue and stay compliant. However, even the most diligent businesses can fall into common traps when it comes to this type of revenue. Let’s explore these pitfalls and how to avoid them to keep your finances on track.
Receiving cash does not automatically mean the business has satisfied its performance obligation.
Fix: Analyze the contract under the applicable revenue-recognition framework before recording revenue.
Straight-line monthly recognition is not correct merely because the contract lasts 12 months.
Fix: Determine whether the service is transferred evenly over time and select an appropriate measure of progress.
A contract can contain more than one distinct promised good or service.
Fix: Identify the separate performance obligations and allocate the transaction price appropriately under IFRS 15.
This can cause Saudi VAT errors when advance payments create tax obligations before accounting revenue is recognized.
Fix: Maintain separate revenue-recognition and VAT schedules.
Refunds, cancellations, upgrades, scope changes, and other modifications can change the amount or timing of revenue.
Fix: Review modified contracts instead of continuing the original recognition schedule automatically.
Unreconciled advances can remain indefinitely in liability accounts or be recognized twice.
Fix: Reconcile customer-level balances to the contract-liability ledger regularly.
HAL provides several workflows that are relevant to businesses managing payments received in advance.
HAL’s Customer Advance workflow allows businesses to record advance payments received from customers and link them to relevant transactions where applicable.
HAL’s current support guidance also confirms an important accounting distinction: customer advances can affect the Tax Report without affecting the Income Statement, because the advance does not initially post to the income ledger.
That is directly relevant to the difference between advance-payment tax treatment and accounting revenue.
HAL’s Subscription Module supports subscription plans, billing frequencies, renewals, cancellations, and automatic generation of recurring invoices.
HAL Invoicing also supports standard, recurring, and milestone invoice workflows.
HAL Accounting provides automated journal entries, ledger control, reconciliation, and financial reporting functionality.
These features can support the operational process around advances, subscriptions, invoicing, and accounting.
However, HAL should not be described publicly as automatically applying IFRS 15 performance-obligation analysis or determining the correct revenue-recognition schedule unless the product team can provide current documentation confirming that capability.
Finance teams remain responsible for determining the appropriate contract liability and revenue treatment. Businesses can request a HAL ERP demo to test how their specific advance-payment and subscription workflows would be configured.
Deferred revenue is consideration received before the related revenue has been recognized.
Under IFRS 15, a customer payment received before the related promised goods or services are transferred is generally presented as a contract liability.
It is generally a liability because the business still has an obligation to provide the customer with promised goods or services.
As the obligation is satisfied, the liability decreases and revenue is recognized.
No.
Cash is an asset already received by the company. Deferred revenue or a contract liability represents the corresponding obligation that remains to the customer.
Under IFRS 15, revenue is recognized when or as a performance obligation is satisfied by transferring the promised good or service to the customer.
No.
Equal monthly recognition can be appropriate when the service is transferred evenly over the year, but the business must assess the actual performance obligation and recognition pattern.
No.
Saudi VAT timing is governed by separate VAT rules. Advance consideration can create VAT and invoicing obligations before the related accounting revenue is recognized.
Deferred revenue involves consideration received before revenue is recognized, creating a liability.
Unbilled revenue generally involves revenue already recognized before the customer has been invoiced and may result in a contract asset or receivable depending on the contractual rights.
Yes.
HAL currently documents a dedicated Customer Advance workflow for advance payments received from customers.
