Discussion on Compliance of Invoicing for Future Start Dates
A novice finance staff member at a SaaS company asks: if the contract start date is January 1, 2020, with annual billing, can an invoice be created in advance? Colleagues say auditors will deduct points and that invoicing must wait until 2020. This article analyzes the accounting principles for advance invoicing, pointing out that the key lies in the timing difference between revenue recognition and accounts receivable.
As a finance novice, I recently encountered a confusion: a colleague told me that for contracts with a future start date, we cannot issue invoices in advance. We are a SaaS company, and the contract stipulates a start date of January 1, 2020, with an annual billing model. My colleague insists that we must wait until 2020 to invoice, otherwise the auditors will raise objections. I have doubts about this, because creating an invoice in advance does not affect accounts receivable (AR) before 2020.
The core of this issue lies in the matching of accounting periods with revenue recognition principles. According to the accrual basis, revenue should be recognized during the period when services are provided, not at the time of invoicing. Invoicing in advance merely represents sending a bill to the customer and does not equate to revenue recognition. However, auditors are concerned with whether the financial statements accurately reflect the economic substance. If an invoice is issued before December 31, 2019, for a contract starting on January 1, 2020, the invoice amount will be included in accounts receivable for 2019, but the corresponding services have not yet been provided, which may lead to a mismatch between revenue and costs, thereby affecting the accuracy of the statements.
Specifically, if invoicing occurs in 2019, accounts receivable increases, but revenue has not yet been earned and needs to be reflected in a liability account (such as deferred revenue). Auditors may require adjustments to ensure that liabilities and assets at the balance sheet date (e.g., December 31, 2019) are truly reflected. Therefore, my colleague's statement is not unfounded, but it is not absolutely prohibited; rather, it requires proper handling in accordance with accounting standards.
From a practical perspective, many SaaS companies invoice in advance to accelerate cash flow, but they need to set up a deferred revenue account in their books. For example, if the contract start date is January 1, 2020, and the annual fee is 12,000 yuan, and invoicing occurs in December 2019, then in 2019, accounts receivable of 12,000 yuan is recognized, along with deferred revenue of 12,000 yuan; when services are provided in 2020, it is then transferred to revenue monthly or quarterly. This way, it does not affect 2019 profits and complies with audit requirements.
However, whether auditors 'deduct points' depends on the accounting policies adopted by the company and auditing standards. If the company does not correctly set up deferred accounts, auditors may issue a qualified opinion or make adjusting entries. Therefore, it is recommended to consult the company's CFO or external auditors to clarify internal policies. Additionally, contract terms may also specify invoicing timing, and it is necessary to ensure compliance with the contract.
In summary, invoicing in advance for a future start date is not impossible, but accounting recognition must be handled carefully. The key is to distinguish between the invoicing act and revenue recognition, and to ensure that the financial statements reflect the true economic transactions. For SaaS companies, it is recommended to establish standard procedures, recording deferred revenue simultaneously when invoicing, to avoid the risk of audit adjustments.
If you still have doubts, you can refer to the 'Accounting Standards for Business Enterprises No. 14 - Revenue' or the International Financial Reporting Standards (IFRS 15), which provide clear guidance on contract liabilities. Also, when communicating with peers, verify their basis to avoid spreading misinformation.