As a startup operating under a SaaS model, we implement an annual prepayment and invoicing system, meaning customers are required to pay for the next 12 months of service fees in advance. In this context, we need to clarify how to account for contracts. For example, in January 2016, a statement of work (SOW) with an amount of x was signed, stipulating quarterly invoicing, with services starting in February 2016. The first invoice y was issued on February 1, 2016, covering two months of the first quarter, and revenue is planned to be recognized within two months. So, should the booking amount we disclose be x or y? We look forward to your answer. Thank you.

Regarding the above question, it needs to be considered from three aspects: contract signing, invoicing, and revenue recognition. At contract signing, the SOW amount x represents the total consideration the customer has committed to pay, which is the total contract value. In the invoicing stage, the quarterly invoice y is merely the payment schedule stipulated in the contract and does not change the total contract amount. Revenue recognition follows the accrual basis, recognizing revenue monthly based on the actual period of service provision, rather than recognizing it all at once at the time of invoicing.

Therefore, in disclosing the booking amount, the total contract value x should be used. The booking amount reflects the future revenue commitment brought by signed contracts, not the amount already invoiced in the current period. The initial invoice y only represents the cash portion that has been received or is receivable, used for cash flow management, but it should not serve as the basis for measuring booking revenue. If only y were disclosed, it would underestimate the contract scale and mislead management and investors in their assessment of business growth potential.

Specifically in this example, after signing the SOW in January 2016, the contractual obligation is established, and the booking amount is determined to be x. The invoice y issued on February 1, 2016, corresponds to services for February to March (two months of Q1), and this amount should be recognized as revenue in February and March using the straight-line method or another reasonable method. Invoicing and recognition for subsequent quarters follow the same pattern until the contract expires.

To ensure compliance in accounting treatment, it is recommended to refer to ASC 606 (the revenue recognition standard under US GAAP) or IFRS 15 (International Financial Reporting Standard 15). These standards require allocating contract consideration to each performance obligation and recognizing revenue when the performance obligation is satisfied. For SaaS services, if the service is provided continuously, revenue is typically recognized over time. Additionally, attention should be paid to significant financing components in the contract; if the prepayment period exceeds one year, discounting factors may need to be adjusted, but in this case, a 12-month prepayment usually does not constitute a significant financing component.

Furthermore, in the notes to the financial statements, the changes in contract liabilities (i.e., prepaid amounts for which revenue has not yet been recognized) and the reconciliation between booking amounts and recognized revenue should be clearly disclosed. This helps external users understand the company's revenue recognition policies and future cash flow expectations.

In summary, for SaaS contracts with annual prepayments, the booking amount should be disclosed as the total contract value x, not the initial invoice y. Revenue recognition strictly follows the service period principle, ensuring that accounting information truly reflects the economic substance. If there are still doubts, it is recommended to consult professional accountants or auditors to make individualized judgments based on specific contract terms.