Contract Inception Date vs. Contract Date in Revenue Recognition

Under ASC 606, contract inception date and contract date are not the same. Inception is the earlier point at which parties have committed to the contract (often before all terms are final); the contract date marks when the last condition is satisfied and the contract becomes enforceable. This gap can delay revenue recognition by weeks or months and affects revenue recognition timing in complex deals.

The conceptual distinction

ASC 606 requires that revenue be recognized when (or as) a company transfers control of promised goods or services to a customer. The first step in the five-step model is to identify the contract. But when does a contract formally exist?

A contract inception date is the point at which the parties have agreed to the core terms and have mutual commitment to the arrangement—even if some details are not yet settled. This date reflects the moment both parties believe they are bound to each other.

The contract date is the date when the contract becomes enforceable. All material terms are final, all conditions precedent are satisfied, and both parties have the right to enforce performance. This is when the legal contract truly exists.

The gap matters because ASC 606 measures contract assets, liabilities, and revenue from the contract date onward, not from inception. If a company signs a letter of intent (inception), then spends weeks negotiating final terms before signing the formal agreement (contract date), the period in between is not part of the ASC 606 accounting.

Practical examples of the gap

Software licensing deal: A software company and a customer agree in principle on pricing and scope in mid-January (inception). The company includes the deal in its backlog and commits resources to deliver. But the legal team works through data-protection clauses, indemnification terms, and service-level agreements. The contract is not fully executed until February 1 (contract date). Revenue recognition begins in February, even though the commercial commitment was made in January.

Construction contract: A builder agrees to construct a warehouse for $5 million in November (inception). The builder orders materials and schedules crews. But the project cannot start until permits are approved, expected in December (contract date). The builder’s performance obligation—measured under ASC 606 for recognizing revenue over time—begins when the permit is granted, not when the deal was agreed.

Acquisition or business combination: A buyer and seller agree to a purchase in August (inception), subject to financing approval and regulatory clearance. The “contract date” for ASC 606 purposes may not arrive until October, when the last condition is satisfied. Revenue and asset recognition for the combined entity begins at the contract date, not August.

In each case, the company must be careful to identify which date is which, because it affects when revenue recognition commences and how much of a fiscal year’s performance is captured in that period.

Why the distinction matters in practice

Period cutoff and forecasting: If a deal’s contract date falls on the last day of a fiscal quarter, the entire associated revenue may fall into that quarter. If it falls on the first day of the next quarter, the revenue is pushed forward. Accountants and controllers must verify the actual contract date, not the inception date, to draw the line correctly.

Backlog reporting: Many companies report “backlog” or “order book” as the sum of unsigned or partially signed commitments. Under ASC 606, only amounts related to contracts at or past the contract date count as enforceable commitments. Inception-stage deals are at risk of not closing; they belong in a separate “pipeline” bucket, not backlog.

Conditional arrangements: If a contract is subject to a condition precedent (financing, board approval, third-party consent), the contract date does not arrive until that condition is satisfied. For example, a manufacturer agrees to sell custom equipment to a buyer, contingent on the buyer securing bank financing. Until the financing is in place, there is no contract date. Revenue recognition waits.

Multiple elements and variable consideration: In complex deals with multiple performance obligations and variable pricing (rebates, performance bonuses, contingent fees), the contract date marks the point when the company can begin estimating total transaction price. ASC 606 requires that transaction price be estimated reliably; until the contract date, the company may lack enough information.

How to identify the contract date

The contract date is established when all of the following are true:

1. Parties have approved the contract and are committed to perform their obligations (this is inception).
2. All material terms are finalized, including price, scope, timing, and conditions.
3. Enforceable rights and obligations exist. Either the contract is executed (signed), or in some jurisdictions, it is binding even without signature if all conditions are met.
4. Conditions precedent are satisfied, if any. If the contract is conditional on third-party approval, financing, or other events, that condition must be met (or waived) before the contract date arrives.

In practice, the contract date is usually the date of the fully executed agreement. But it can be later if conditions remain unsatisfied, or, in rare cases, earlier if the parties’ actions or emails show mutual commitment to final terms before formal execution.

Distinguishing inception from contract via ASC 606 CDIs

The SEC’s Compliance and Disclosure Interpretations (CDIs) for ASC 606 clarified that inception and contract date are distinct concepts. The key CDI (1.1) states:

“A contract does not exist if the parties have not committed to perform their obligations as of the contract commencement date.”

This means that if a deal is still subject to material changes—either party can walk away without penalty, or a condition is unmet—there is no contract yet, even if inception has occurred.

Auditors and accountants use this principle to police revenue timing. A company that claims revenue on an inception date when the contract is not yet enforceable will face audit challenge.

The risk of misidentification

Companies sometimes conflate inception and contract date, especially in fast-moving markets or when sales staff are eager to book deals. Auditors have flagged cases where:

• A company recorded revenue on the date a letter of intent was signed, treating it as a contract date, when material terms were still being negotiated.
• Revenue was recognized on a handshake or verbal agreement, despite the contract not being signed.
• A deal subject to financing or regulatory approval was treated as having a contract date before the condition was satisfied.

These errors push revenue into the wrong period and can trigger restatements.

Implications for revenue forecasting and financial planning

Finance teams must track both dates in their contract database. Inception date informs the sales pipeline and backlog; contract date determines when ASC 606 accounting and revenue recognition begin.

For quarterly guidance and earnings forecasts, the company must know which deals have reached contract date and which are still in inception. A shift in deal timing—contracts being signed later than usual—directly affects the quarter’s revenue.

See also