> ## Documentation Index
> Fetch the complete documentation index at: https://docs2.zenskar.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Revenue lifecycle

## Overview

Revenue recognition is rarely a straight line. Contracts evolve, usage fluctuates, and accounting standards demand both rigor and flexibility. **Zenskar** manages the entire revenue lifecycle, from distribution to adjustments, in a way that is both compliant with **ASC 606 / IFRS 15** and practical for day-to-day operations.

```mermaid theme={null}
---
config:
  theme: redux
---
flowchart TD
    Start[Contract Execution] --> Identify{Identify Performance Pattern}
    Identify --> TimeBased[Over Time]
    Identify --> EventBased[At a Point in Time]
    EventBased --> Immediate[Recognize Upon Delivery]

    %% Revenue Distribution
    subgraph Distribution[Revenue Distribution]
        direction LR
        TimeBased --> SelectDist{Select Distribution Method}
        SelectDist --> StraightLine[Straight-line]
        SelectDist --> UsageBased[Usage-based]
        SelectDist --> Entitlement[Entitlement-based]
        StraightLine --> CreateSchedule[Create Revenue Schedule]
        UsageBased --> CreateSchedule
        Entitlement --> CreateSchedule
    end

    CreateSchedule --> Monitor[Monitor Performance]
    Monitor --> Change{Change in Contract?}

    Change -- No --> Recognize[Recognize Revenue as Scheduled]

    %% Revenue Adjustment
    subgraph Adjustment[Revenue Adjustment]
        direction LR
        Change -- Yes --> SelectAdjust{Select Adjustment Method}
        SelectAdjust --> FrontLoad[Front-load]
        SelectAdjust --> StraightLineAdjust[Straight-line]
        SelectAdjust --> BackLoad[Back-load]
        FrontLoad --> RevisedSchedule[Create Revised Schedule]
        StraightLineAdjust --> RevisedSchedule
        BackLoad --> RevisedSchedule
    end

    RevisedSchedule --> Recognize

```

***

## 1. From contract to baseline schedule

When a contract is signed, the first task is to identify how obligations are delivered:

* **Over time** (subscriptions, managed services)
* **At a point in time** (product delivery, milestone completion)

For over-time obligations, Zenskar applies the appropriate **distribution method** to create the **baseline revenue schedule**:

* **Straight-line** → evenly across periods for predictable services.
* **Usage-based** → tied directly to consumption metrics.
* **Entitlement-based** → aligned with credits, milestones, or features.

This operationalizes **Steps 3–5 of ASC 606 / IFRS 15**: allocating the transaction price and recognizing revenue in proportion to performance.

***

## 2. Continuous monitoring

Once a schedule is created, Zenskar continuously monitors performance. This is critical because reality often diverges from plan:

* Customers expand or modify scope.
* Usage overshoots or undershoots forecasts.
* Variable consideration (bonuses, penalties) becomes determinable.
* Exchange rates or calculation precision introduce variances.

Zenskar detects these variances as they occur, ensuring revenue reporting reflects *current contractual and operational truth*.

***

## 3. Adjustments for real-world changes

When variances arise, the baseline schedule must be revised. Zenskar applies one of three **adjustment methods**, depending on materiality and certainty:

* **Front-load** → immediate recognition in the next open period (required for material adjustments >5%).
* **Straight-line adjustment** → evenly distributed across remaining periods.
* **Back-load** → deferred until the final period, when outcomes are certain.

Each adjustment is **documented with rationale, approval workflow, and audit trail**, ensuring compliance with both ASC 606 and IFRS 15.

***

## 4. Recognition and compliance

Revenue is ultimately recognized either:

* According to the original schedule (if unchanged), or
* According to the revised schedule (if adjustments apply).

In either case, Zenskar ensures:

* **Faithful representation** of revenue.
* **Consistency** in applying methods.
* **Compliance** with disclosure and documentation standards.
* **Audit readiness**, with complete histories of distribution and adjustment decisions.

***

## Why this matters

Without an integrated approach, finance teams often treat distribution and adjustment as separate processes — leading to inconsistencies, missed compliance requirements, or late surprises at close.

Zenskar unifies the two into one **continuous lifecycle**:

1. **Baseline scheduling** aligns with contractual performance.
2. **Continuous monitoring** detects divergences.
3. **Adjustments** realign recognition with actuals.
4. **Recognition** is always compliant, documented, and audit-ready.

In short, Zenskar ensures that revenue recognition is **accurate, compliant, and adaptive** — turning what is usually a manual, error-prone process into a controlled, transparent system.