A SaaS contract is signed but starts next quarter: keep the reports clear

Record signature, contractual start, expected activation, first billing and renewal dates separately. Include conditions that must be met before service begins and any cancellation or rescheduling rights requiring legal interpretation. The sales system's closed status should link to the agreement and its effective terms, not stand in for them.

A signed agreement can be useful evidence for a commercial pipeline or commitments report. It does not by itself establish the revenue recognized in the financial statements. IFRS 15 connects recognition to satisfying the relevant performance obligations; an accountant applying your framework needs the delivery facts as well as the signature date.

If management reports future contracted value, label the measure so readers know it includes service that has not started. State how cancellation rights, usage assumptions, implementation charges and later years are treated. Keep it separate from a measure intended to describe currently active recurring subscriptions, and reconcile changes as contracts begin or are revised.

For illustration, a contract signed in November may provide a twelve-month service starting in February. The November commitments report can show that future arrangement under the company's stated definition. The active-service report should follow its own definition. Copying the full amount into both reports without explaining the overlap makes the business appear to have two independent sources of growth.

Stripe subscription schedules support future starts and phases. Where that feature is used, compare the configured start date, price, quantity and later phases with the agreement. A calendar reminder in the CRM is insufficient evidence that billing will start correctly, and an active subscription created early may produce unintended charges.

Review any upfront payment separately. Identify the invoice it settles, the period or service it covers and the approved accounting treatment. Preview the first recurring bill and confirm the customer's billing contact and purchase-order requirements. Resolve exceptions before the activation week, when implementation staff are likely to be focused on getting the customer working.

At each reporting date, show the opening list, new signed agreements, amendments, cancellations and contracts that actually began. Reconcile closing value to the underlying contract records. When a start moves, retain the original date, approved replacement and reason; overwriting the old date erases information about implementation delays.

Ask the delivery owner to confirm activation using the evidence relevant to the promise. If access is available before a formal kickoff, or a milestone delays part of the service, present those facts to accounting. Management can then distinguish an administrative schedule change from a change affecting delivery, billing or the contractual commitment.

A monthly report can show which future contracts began and whether their billed and recurring values match what had been reported. Investigate differences caused by scope reductions, delayed products, credits or mistaken data entry. This provides a practical check on the quality of the commitments report and helps sales and finance use the same account history.

Retain a link from each activated subscription back to its signed agreement and prior register entry. The next reviewer should be able to tell that the service represents delivery of an existing commitment. That connection also avoids treating a migrated or rescheduled future-start deal as a second new win when it finally enters billing.