Deferred revenue is funds that are collected from a customer, or a business’s right to collect, for goods or services that have not yet been produced. As the company continues to have an obligation to perform, the amount is typically not recognized as a revenue item until the performance obligation is satisfied.
Advanced billing, subscription, milestone, or service period payments can become difficult to manually manage for Singapore businesses with multiple contracts. Billing and accounting are different systems that can cause differences in recon, late month-end closing, and revenue recognition.
The right revenue management process can link the customer contracts, billing schedules, performance obligations, revenue recognition, and accounting records. This assists finance groups to hold an even better plan of what is obtained, what is earned, and what is still to be recognised.
The data we collected from the EY Survey shows that 94% of Singapore tax leaders are focusing on data, GenAI, and technology to fuel innovation, insights, predictive analytics, and automation for reporting. This discovery underscores the increasing relevance of connected data and technology in today’s financial operations.
Find out what deferred revenue is, how it works, how it’s calculated, how it’s recorded, and the Singaporean GST treatment of deferred revenue under SFRS(I).
Key Takeaways
Deferred revenue is revenue that a business receives from a customer before its obligation to deliver goods or services. It is also referred to as unearned revenue. Under IFRS 15 and the Singaporean equivalent, it is usually classified as a contract liability when consideration is received or expected before the transfer of the goods or services in the contract.
For instance, a Singapore software business could obtain S$24,000 payment in advance for a 12-month subscription. The company does not recognize the entire S$24,000 as revenue at once when it provides the service evenly throughout the year. Rather, it takes $2,000 per month as services are rendered.
It follows a rule that revenue is the transfer of expected goods or services to the customer. According to IFRS 15, a contract liability is one that occurs when the entity receives or is owed the consideration before the transfer of the related good or service.
Deferred revenue is based on a straightforward concept, recognizing revenue after the exchange of the goods or services that are promised, but before the cash or consideration is received. The liability’s amount reduces progressively over time as the business performs its promises.
A customer may pay before receiving the full product or service. Common situations include annual software subscriptions, maintenance contracts, prepaid memberships, retainers, and service agreements that cover future periods.
The business at this point has been given economic benefit but not necessarily the revenue. The amount should therefore not be booked as recognised revenue until the performance obligation is met.
The amount of advance received is not recognised as sales revenue, but as deferred revenue or contract liability in the business records. The balance is all that has not yet been fulfilled with respect to the goods/services to be provided to the customer.
The entry typically consists of a credit to deferred revenue and a debit to cash or receivables. The liability is entered onto the balance sheet until the business is able to meet the obligation.
The business then provides the agreed goods or services as per the contract with the customer. The obligation can be fulfilled at a particular time or over time, depending on the arrangement.
The company could, for instance, fulfill this obligation on an ongoing basis by granting access to the service to its customers throughout the 12 months. For a physical product, the obligation can be fulfilled by transferring control of the product to the customer.
When the performance obligation is met, the business moves the corresponding revenue from the deferred to the recognised revenue. The quantity and timing will vary based on the contract and the manner in which the performance obligation is met.
This continues on during the service/delivery period as the complete deferred balance is recognised. The unmet obligations, then, amount to the remaining liability for consideration.
When the funds are deferred, the money is counted as a liability since it is a debt that the business still has to the customer and it must provide them with goods or services. When the payment is received, the company may not have fulfilled its contractual obligation, so the payment does not constitute revenue recognition.
A contract liability under IFRS 15 is an entity’s obligation to transfer goods or services for which an entity has received consideration, or for which consideration is due. That’s why an advance customer payment can be a liability and not a revenue item.
The liability reduces upon the performance of the related performance obligation. When the company does that, it considers that the right amount is revenue, as it delivered what the customer paid for.
Deferred revenue can be determined by looking at the amount of consideration received or due for goods or services not yet delivered. Where there are several performance obligations, variable consideration, milestones, cancellations, or alternative recognition periods, the calculation is more complex.
A simple allocation over the recognition period is appropriate for contracts that provide identical services, ensuring consistent revenue recognition across revenue streams.
First, find customer receipts or billings for goods and services to be delivered in the future. Look at the contract, invoice, payment history, and length of the services to see which payments have not yet been earned.
The business should also separate amounts that relate to already fulfilled obligations from amounts associated with future obligations. This prevents earned revenue from remaining incorrectly classified as deferred.
Determine how long the business will provide the related product or service and how the performance obligation will be satisfied. A 12-month subscription delivered evenly may use a monthly recognition pattern, while a project may use milestones or another appropriate measure of progress.
The recognition period should follow the actual contractual obligation rather than simply the date when cash was received. IFRS 15 requires revenue to reflect the transfer of promised goods or services to customers.
For a simple straight-line arrangement, divide the amount allocated to the performance obligation by the number of recognition periods.
Monthly revenue = Total revenue allocated ÷ Number of months
For example:
S$24,000 ÷ 12 months = S$2,000 per month
After three months, S$6,000 would have been recognised as revenue and S$18,000 would remain deferred, assuming the service was delivered evenly.
After each recognition period, reduce the deferred revenue balance by the amount recognised as earned revenue. Finance teams should update the schedule consistently with the actual performance of the contract.
The closing balance should represent the consideration associated with obligations that remain unsatisfied. Regular updates help finance teams reconcile the balance against contracts, invoices, payments, and revenue recognised in the general ledger.
Consider a Singapore-based software company that receives S$24,000 excluding GST for a 12-month subscription beginning on 1 January 2026. Assuming the service is delivered continuously and revenue is recognised evenly, the company recognises S$2,000 per month.
| Period | Revenue Recognised | Closing Deferred Revenue |
|---|---|---|
| Initial receipt | S$0 | S$24,000 |
| January | S$2,000 | S$22,000 |
| February | S$2,000 | S$20,000 |
| March | S$2,000 | S$18,000 |
| June | S$2,000 | S$12,000 |
| September | S$2,000 | S$6,000 |
| December | S$2,000 | S$0 |
The company initially records S$24,000 as deferred revenue because it has received consideration before providing the full subscription service. Each month, S$2,000 moves from the liability into recognised revenue as the company fulfils its service obligation.
This example simplifies the arrangement by assuming one performance obligation, equal service delivery, and no contract modifications. Actual contracts may require more detailed assessment under the applicable revenue recognition standard.
Journal entries help finance teams distinguish between the receipt of customer consideration and the point when revenue becomes earned. The exact treatment can vary depending on the contract and accounting framework.
When the customer pays before the business fulfils the related obligation, the business records the consideration as cash or a receivable and recognises a corresponding liability.
Example: S$24,000 advance payment
| Account | Debit | Credit |
|---|---|---|
| Cash | S$24,000 | – |
| Deferred Revenue / Contract Liability | – | S$24,000 |
The entry increases the company’s cash position while also recognising the remaining obligation to the customer. No S$24,000 revenue is recognised at this stage under the simplified example.
As the company provides the service, it reduces the deferred revenue balance and recognises the corresponding revenue.
Example: S$2,000 monthly revenue
| Account | Debit | Credit |
|---|---|---|
| Deferred Revenue / Contract Liability | S$2,000 | – |
| Revenue | – | S$2,000 |
The entry reduces the liability because part of the company’s obligation has been fulfilled. The revenue account increases by the amount that has become earned during the period.
Month-end adjustments may be necessary when the accounting records do not fully reflect the service delivered during the reporting period. Finance teams should compare the recognition schedule against contracts, invoices, payments, and actual performance.
For example, if S$6,000 of a service contract should have been recognised by the reporting date but only S$4,000 has been recorded, the company may need an adjustment to recognise the additional S$2,000 and reduce the contract liability accordingly. Supporting documentation should be retained so the adjustment can be explained during reconciliation or audit.
Deferred revenue and accrued revenue both involve timing differences between cash movements and revenue recognition, but they work in opposite directions.
Deferred revenue generally arises when consideration comes before the business fulfils its obligation, while accrued revenue relates to goods or services already provided before the business receives payment or has an unconditional right to consideration.
| Aspect | Deferred Revenue | Accrued Revenue |
|---|---|---|
| Meaning | Consideration received or due before the related goods or services are fully delivered. | Revenue earned from goods or services already provided but not yet received or billed as an unconditional receivable. |
| Timing | Payment or consideration comes before revenue recognition. | Revenue recognition occurs before payment or billing becomes due. |
| Balance Sheet Effect | Generally recorded as a liability or contract liability. | Generally represented by a contract asset or receivable, depending on the entity’s right to consideration. |
| Business Obligation | Business still needs to provide goods or services. | Business has already provided the related goods or services. |
| Example | Customer pays upfront for a 12-month software subscription. | Company completes a service milestone but has not yet obtained an unconditional right to payment. |
Deferred revenue and accounts receivable can both arise from customer contracts, but they represent very different positions for the business. Deferred revenue indicates that the company still owes goods or services, while accounts receivable represents an amount that the customer owes to the company.
This distinction is important when finance teams reconcile billing, cash collection, and revenue recognition. IFRS 15 specifically distinguishes an unconditional right to consideration, which is presented as a receivable, from a contract liability arising from consideration received before performance.
| Aspect | Deferred Revenue | Accounts Receivable |
|---|---|---|
| Nature | Obligation to provide future goods or services. | Right to collect payment from a customer. |
| Balance Sheet Classification | Liability or contract liability. | Asset. |
| Customer Position | Customer has provided consideration before the business fulfils the obligation. | Customer has an outstanding amount payable to the business. |
| Typical Timing | Payment or consideration occurs before fulfilment. | An unconditional right to payment exists, typically after or upon billing for the relevant supply. |
| Example | Annual service fee received before the service period begins. | Invoice issued for completed services with payment due later. |
The customer might be given a chance to consider a business before being served the product/services it provides. It is therefore critical when accounting for contracts that last for multiple months or years.
A software company might get a payment in advance for an annual subscription and record the revenue over the period of the contract. The maintenance provider can receive a 12-month payment for the maintenance services and accrue the revenue as they provide the maintenance services.
Other examples are gym memberships, prepaid training programs, annual maintenance contracts, hotel deposits, event tickets, insurance-related service agreements, and long-term service contracts. In each scenario, the business has to decide how to determine when it has performed the obligation; it is not simply when the payment is made.
Progress billings or advance payments from customers can also result in contract liabilities for construction and engineering firms. The nature of the recognition pattern is contract-specific and subject to accounting requirements.
The financial reporting framework (FRF) applicable to the entity should be taken into account by Singapore businesses in accounting for revenue. ACRA has released two SFRS(I) and FRS frameworks for annual reporting periods starting on 1 January 2026.
For entities using the SFRS(I) framework, SFRS(I) 15 is the equivalent of IFRS 15; and for entities using the FRS framework, FRS 115 is the equivalent of IFRS 15. ISCA confirms that FRS 115 is the Singapore equivalent of the revenue recognition standard and applies to revenue from contracts with customers.
It is important that the five-step model applies because no advance payment means that no income has been earned. Before recognising the revenue, the business should evaluate the contract and the performance obligations underlying the contract.
The first step will be identification of the contract with the customer, and evaluation of whether the contract complies with the relevant criteria of the applicable standard. Both finance teams need to know the contractual rights, terms of payment, goods/services to be delivered, and the obligations of the two parties.
This is needed for businesses that have numerous customers and contracts for consistent contract data. Events like renewals, amendments, canceling a contract, taking a discount, or changing the payment terms could impact the treatment of the revenue and should be reflected in the revenue process.
Then, the business outlines the unique products/services it will offer. One contract can have several performance obligations, like access to software, implementation, training, maintenance, and support.
This is a critical step as the price of the transaction could be split into different obligations. The entire advance payment might be an overstatement of revenue if certain services are still to be delivered.
The business decides what is worth the consideration that it is expecting from the transfer of the goods or services that it is promising. Fixed amounts, variable consideration, discounts, rebates, refunds, or other contract terms may have to be taken into account.
If the relevant circumstances change, the price negotiation should be considered by the finance teams. For entities to determine what the transaction price is, they must take into account the terms of the contract and relevant facts and circumstances as required by IFRS 15.
If multiple performance obligations are in a contract, the transaction price is split among the performance obligations based on the stand-alone selling price of the distinct goods or services.
This allocation is what is finally to be recognized as each obligation is completed. It can thus have an impact on the recognition period and quantity of revenue in reporting periods.
Revenue is recognized when or as the business satisfies a performance obligation by transferring control of the promised goods or services to the customer. Obligations may be satisfied at a point in time or over time. Accurate revenue recognition also helps businesses monitor cash flow and assess their burn rate to support financial planning.
This is where the liability starts to be reduced when the revenue is recognised for deferred revenue. An accounting schedule should therefore relate the originally agreed terms of the contract with the actual schedule of performance.
GST timing and accounting revenue recognition do not necessarily occur at the same point. For a GST-registered business, GST reporting follows the applicable time-of-supply rules, which can trigger output tax before the related amount is recognised as accounting revenue.
Under the general GST rule in Singapore, the time of supply for most transactions is the earlier of when an invoice is issued or when payment is received, subject to applicable exceptions. For continuous supplies of services, specific rules also apply.
If the advance payment makes the company a party to a contract with a performance obligation that has not yet been met, then the contract represents a liability for accounting purposes. The receipt of a payment can also mean the reporting of GST, however, based on the existing time of supply rules.
The finance team must not be under the impression that the deferred revenue also implies that the GST can be deferred. The accounting timeline and GST records need to be looked at individually.
For most transactions, the time of supply may commence when an invoice is issued before payment is received, and the time of supply may commence when payment is received prior to the issuance of an invoice. This means the accounting revenue for the related reporting period might not be fully recognised until the relevant GST reporting period.
The current GST rate in Singapore is 9% (but may be zero-rated, exempt or have other special treatments based on the supply). It is therefore critical for businesses to differentiate between GST reporting and deferred revenue recognition, and to keep a proper record of both.
ScaleOcean Atlas can help finance teams connect billing, accounting, revenue recognition, and GST-related records within one integrated workflow, making financial data easier to track and reconcile. Schedule a consultation with ScaleOcean to discuss your GST, deferred revenue, and financial management requirements.
Businesses should maintain a clear reconciliation between invoices, payments, GST reporting, deferred revenue balances, and recognised revenue. This helps finance teams identify situations where the GST reporting period differs from the accounting revenue recognition period.
For example, a GST-registered service company may receive an advance payment for a 12-month service contract. GST may need to be accounted for when the applicable time-of-supply event occurs, while accounting revenue is recognised progressively as the service is provided. IRAS confirms that the general time-of-supply rule can trigger output tax at the earlier of invoice issuance or payment receipt.
Deferred revenue management is especially important for businesses with numerous contracts, recurring bills, advance payments, and services provided over various durations. A formalised procedure aids in cash collection vs. earned revenue.
Deferred revenue schedules provide more accurate revenue recognition, as they make sure that the revenue is accounted for in the proper reporting period instead of the cash received. If your business has long-term contracts, services that are recurring, or payment from customers in advance, this becomes important.
Based on data our team obtained from MarketScreener, ST Engineering reported S$1.388 billion in current contract liabilities and S$1.913 billion in non-current contract liabilities at 31 December 2025. Combined, the S$3.301 billion balance represented approximately 25.2% of the group’s total liabilities of S$13.111 billion.
The example illustrates that contracts can be a big liability for a large company. ST Engineering also reported that current contract liabilities increased by S$194 million, while non-current contract liabilities increased by S$313 million, mainly due to higher progress billings and advance payments received from customers.
Deferred revenue provides finance teams with information that they have received or will receive for services that have yet to be rendered. The balance is not future cash, but the underlying contracts can offer helpful financial details on the expected revenue recognition.
A clear schedule can then enable management to differentiate between cash collected, revenue recognised, and revenue expected to be recognised in the future. This helps in better forecasting and financial planning.
Auditors should be able to understand the company’s policies on the recognition of revenue, the changes in the balances of the contracts, and the contractual evidence provided to support such balances. These relationships are easier to track if a consistent deferred revenue schedule is applied.
All the relevant contracts, invoices, payment records, recognition schedules, amendments, and supporting calculations should be retained by the business. Additionally, under IFRS 15, disclosure must be made of any changes in or balances of contracts.
Deferred revenue can help provide visibility of obligations for future service delivery. This information, combined with the values in the contract, the contract billing schedule, contract renewal information, and the expected delivery periods, will help management understand the timing of future contract revenues.
It is helpful for businesses where the subscription is recurring, the maintenance agreement is prolonged, the project is long-term, or the business engages in multiple contracts with customers. An effective schedule can assist management to plan for future known liabilities.
Manual deferred revenue management can become difficult as the number and complexity of customer contracts increase. Problems usually emerge when contract, billing, and accounting information sits in separate systems.
Billing dates, billing periods, payment terms,s and recognition dates may vary from customer to customer. Some contracts may call for recognition monthly, others based on Milestones or Delivery events.
Manual management of these schedules adds to finance staff’s reconciliation work. It can also make it more challenging to determine the balances that must be identified in a specific reporting period.
The terms of a contract may be modified even after it has been signed. Customers can increase their subscription, renew their service, terminate their contract, increase or decrease the quantity, or renegotiate new commercial terms.
Each change may impact the consideration and recognition schedule for the remaining consideration. The finance team, therefore, requires a record of amendments and their effect, and not the original contract schedule.
Billing systems might report on the invoices and payments, whereas accounting systems might report on recognised revenue and liabilities. The differences where these records do not connect can occur between the billed amount and the cash received, between revenue recognised and cash received, and between closing contract liabilities and the billed amount.
The regular reconciliation process assists in detecting these differences prior to the month-end procedures and/or audit. It also provides for finance teams to delve into discrepancies before the transaction data is lost.
Manually closing out contracts and determining the appropriate revenue recognition amounts can cause month-end closing to slow down when finance teams have to review contracts manually. This can be very difficult when hundreds or thousands of contracts have varying service periods.
If there is no regular routine, finance teams may end up having to do repetitive calculations and compare across multiple files to finalise the deferred revenue balance. This makes it time-critical and more work, in the already busy reporting period.
All deferred revenue processes should link contracts, billing, revenue schedules, and accounting records. Businesses need to also have clear policies to ensure that finance teams are following the same principles for similar transactions.
The nature of the performance obligations, the period in which they are fulfilled, the treatment of advance payments, and the accounting for changes in contracts should be identified by businesses. These policies give finance teams a reliable way to assess customer contracts.
The policy should also include details regarding exceptions. If a contract has unusual terms or involves a high degree of judgment, the relevant finance team should record the reason for the accounting treatment.
Deferred revenue balances should be identified with the contract of which they form a part and its recognition program. This allows more easily to be able to recognise the revenue for each reporting period.
The schedule should contain relevant details like contract value, payment date, period of service, performance obligations, recognised revenue, balance, and expected recognition dates. This can help to streamline month-end reconciliation.
The finance team should compare deferred revenue schedules with the general ledger, billing records, invoices, customer receipts, and contract changes. Discrepancies are likely to be identified earlier with regular reconciliation.
Additionally, businesses can check on unusual transactions, balances that are large, overdue reconciliations, and contracts that are nearing completion. These checks can guide the finance team to look into balances that need additional attention.
When billing and accounting processes operate separately, finance teams may spend considerable time transferring information, checking balances, and updating recognition schedules. Integrating these processes can allow billing events and accounting treatments to follow a more consistent workflow.
An integrated revenue management system can support automated revenue recognition, contract-based revenue tracking, integrated financial workflows, and real-time revenue reporting. ScaleOcean Atlas can provide these capabilities within a broader ERP environment, helping connect contracts, billing, accounting, and financial reporting.
Deferred revenue is consideration received or due before a business fulfils the related goods or services. Because the obligation remains outstanding, the amount is generally recorded as a liability or contract liability and gradually recognised as revenue when the relevant performance obligations are satisfied.
For Singapore businesses, managing deferred revenue can become challenging when contracts, billing, accounting, GST reporting, and recognition schedules are maintained separately. A structured process helps finance teams reduce reconciliation gaps, maintain accurate reporting, and distinguish accounting revenue recognition from GST obligations.
ScaleOcean Atlas supports revenue management by connecting contract-based revenue tracking, automated revenue recognition, billing, accounting, and financial workflows within one ERP environment. Its revenue management system can help finance teams maintain clearer recognition schedules and real-time revenue reporting. Schedule a consultation with ScaleOcean to explore how Atlas can support your deferred revenue and broader financial management requirements.
Deferred revenue is generally a liability because the business has received or is entitled to consideration while still owing the customer goods or services. The liability decreases as the business fulfils the related performance obligations.
When deferred revenue is initially recognised, it is normally recorded as a credit because it increases a liability. When the related revenue is subsequently recognised, the deferred revenue account is debited while the revenue account is credited.
Deferred revenue generally appears under liabilities, often presented as a contract liability. Depending on when the related goods or services are expected to be delivered, it may be classified as current or non-current.
Yes, the initial receipt of an advance customer payment affects cash flow because the business receives cash. However, subsequent recognition of deferred revenue as accounting revenue does not create another cash inflow because the cash was already received.
