Nothing here is verified yet. Content is migrated or drafted and has not been reviewed by a practitioner. Assertions marked like this are unchecked.
FinAtlas
Taskunverified

Revenue forecast (recognized vs billed)

Translate bookings into recognized revenue across time given contract terms, ramp schedules and recognition policy.

varies by archetype

3

The task exists in this business archetype but behaves differently. The note is the point of the edge: it must say how it differs, not merely that it does.

  • Marketplace / platformArchetypeunverified

    Take-rate businesses gross-bill the buyer and remit to the seller, so billed volume tracks GMV while recognised revenue is only the commission. Forecasting off billings overstates revenue by an order of magnitude; the forecast object is really a GMV model with a take-rate assumption on top.

  • SaaS / subscriptionArchetypeunverified

    Contracted ARR makes the base highly predictable, so the forecast reduces to renewal timing, ramp schedules and new-business landing. Deferred revenue absorbs the gap between billed and recognised, which means billings and revenue can diverge for several quarters without either being wrong.

  • Usage / consumptionArchetypeunverified

    Revenue is metered after the fact and is not contractually committed, so there is no bookings-to-revenue waterfall to build. The forecast is a consumption model with a credit burn-down, and its accuracy degrades sharply beyond one quarter because customers can simply stop using the product without churning.

produces

1

The modeling object or downloadable deliverable the task creates.

consumes

2

A canonical data object the task needs as input.

governed by

1

An accounting or regulatory standard that constrains the task.

owned by

1

The business-partner org unit accountable for the task.

runs in

1

The end-to-end shared-services process the task sits inside.

serves

1

The verb-level intent the task exists to satisfy.

Relationships pointing at this node.

depends on

1

A hard sequencing dependency: the target cannot correctly start until the source is done. The note gives the reason.

  • Bookings and pipeline forecastTaskunverified

    Recognised revenue is derived from bookings via ramp and recognition timing, so the bookings view has to land first.

performed by

1

A job title someone actually holds does this work.

Unresolved from the source registry

not yet modelled

Free-text strings from the source spreadsheet that have not been resolved to a node. Preserved verbatim so nothing is silently dropped — these are backlog, not content.

Produces: Bookings-to-revenue waterfall