Committed ARR

TL;DR

• Committed ARR (CARR), also known as Contracted ARR, represents recurring revenue that has been secured through signed customer contracts, even if it is not yet active or recognized.
• Unlike ARR, which reflects recurring revenue currently in effect, CARR includes future contractual commitments such as multi-year agreements, scheduled expansions, and contracted AI features.
• In the context of AI ARR vs ARR, CARR helps finance teams distinguish between revenue that is already monetized and revenue that is contractually guaranteed but will materialize later.
• Under ASC 606, revenue is recognized as services are delivered. This means committed revenue contributes to CARR today but becomes recognized revenue only over time.
• Under ASC 340, related contract acquisition costs (like sales commissions) are capitalized and amortized over the customer lifecycle.

Understanding Committed ARR and its role in SaaS revenue models

Committed ARR is a forward-looking measure of recurring revenue based on signed contractual agreements. In SaaS businesses, contracts often extend beyond the current billing period and may include future subscriptions, upgrades, or product modules scheduled to activate later. These commitments create revenue certainty that does not yet appear in active billing systems.

The simplest way to express the relationship: CARR = ARR + Contracted but not yet active ARR. ARR reflects revenue already live and being delivered. CARR reflects revenue contractually secured but not yet operational. The gap between them is itself a planning metric: it shows how much future ARR growth is already committed before a single new booking is required.

As SaaS products evolve to include AI capabilities, this distinction becomes more layered. Finance teams now track three dimensions of the same revenue base: ARR as the current baseline, AI ARR as the portion attributable to AI-powered functionality, and CARR as the total recurring value already secured through contracts. When a customer signs a contract including AI automation that activates in a later deployment phase, ARR and AI ARR may not change at signing. CARR increases immediately. AI ARR shows realized AI monetization. CARR shows committed AI monetization. Together, they help finance teams assess whether projected AI revenue depends on future adoption or is already contractually guaranteed.

When Does Each Metric Move?

The relationship between CARR and revenue recognition under ASC 606

Understanding CARR requires separating contractual commitment from recognized revenue.

ASC 606, the revenue recognition standard, requires companies to recognize revenue when performance obligations are satisfied. In SaaS enterprises, this typically means recognizing revenue over time as services are delivered rather than when contracts are signed.

When a customer signs a long-term subscription agreement, the total recurring value becomes part of CARR because the obligation exists. However, ASC 606 prevents companies from recognizing that value as revenue until the service is provided.

For example:

A three-year subscription agreement may guarantee recurring payments over the duration of the contract. When this agreement commits to an AI module that activates in month 7, CARR and AI ARR apply, but ASC 606 is not triggered until the service is provided. 

From a commitment perspective, the entire recurring value contributes to CARR. From an accounting perspective, revenue is recognized gradually as the company fulfills its obligation to deliver access to the software.

This means:

• CARR reflects certainty
• ARR reflects activation
• Recognized revenue as per ASC 606 reflects delivery

The separation ensures financial reporting remains aligned with service performance rather than contractual timing. This distinction becomes even more relevant in AI-enabled offerings where:

• Deployment timelines vary
• Feature activation can be changed over time
• Consumption ramps over time

In such cases, the difference between commitment and recognition becomes more pronounced.

There is also a balance sheet implication under ASC 340. Incremental sales commissions tied to CARR contracts must be capitalised and amortised over the expected customer benefit period. As CARR grows, so does this deferred cost asset on the balance sheet, making it a dimension finance teams should track alongside CARR, especially in high-growth periods.

How committed revenue transitions into ARR

CARR is not static. Over time, committed revenue moves into ARR as contracted services become active. This transition typically occurs through events such as subscription start dates, phased implementation, or scheduled feature activation.

For example, a customer may sign a contract that includes advanced AI capabilities beginning six months after deployment. At contract execution, the future value contributes to CARR. When the feature becomes operational, that value begins contributing to ARR. 

The movement from CARR to ARR reflects the shift from contractual certainty to active delivery. This transition is important because it provides visibility into how much of future ARR growth is already secured versus how much depends on new bookings.

Why finance teams track CARR

CARR provides insight into revenue predictability. Since it is based on signed agreements, it offers a clearer view of future stability than ARR alone. Committed ARR offers a forward-looking perspective grounded in contractual certainty and bridges the gap between signed agreements and realized recurring revenue.

Tracking CARR helps finance teams understand committed growth, evaluate long-term stability, and separate realized revenue from secured revenue. 

In the context of AI investments, this becomes particularly valuable because AI monetization often involves a staged rollout, usage ramp-up, and future module activation. Without tracking CARR, finance teams may underestimate the level of revenue certainty already in place.

For instance, ARR may show modest AI contribution today. However, CARR may reveal that significant AI revenue is already committed through enterprise agreements. This provides a more balanced understanding of growth potential.

With platforms like Zenskar, finance teams can:

• Track contracted revenue across customer segments
• Distinguish between committed recurring revenue and recognizable revenue as per ASC 606 
• Align contractual commitments with revenue forecasts