I'mBoardDocs
Board OntologyFinance

Services / Implementation Revenue

Recognized non-recurring revenue from implementation, onboarding, or professional services for the period. Kept separate from recurring revenue because it is lower-margin and does not compound — a services-heavy quarter can grow total revenue while ARR stays flat. — Finance KPI, I'mBoard-authored (editorial tier).

I'mBoard-authored (editorial tier)

No public third-party standard anchors this KPI yet, so I'mBoard authors and maintains the definition — transparently labeled as editorial tier. See the ontology methodology for the published vs editorial tier system and the back-attribution workstream.

Rogue ID: finance.services_revenue Type: Currency Domain: Finance

Definition

Recognized non-recurring revenue from implementation, onboarding, or professional services for the period. Kept separate from recurring revenue because it is lower-margin and does not compound — a services-heavy quarter can grow total revenue while ARR stays flat.

Formula

Recognized professional-services / implementation revenue for the period.

Why it matters

Separating services keeps recurring revenue clean and exposes margin dilution from delivery-heavy periods.

How to interpret

A rising services share of total revenue often pressures blended gross margin — read against finance.gross_margin_pct.

Calculation policy

How an AI agent should compute this KPI from messy company data. Free-text rules consumed at reasoning time — not a deterministic DSL. The most common ways to get this wrong are listed under Common miscomputations.

Inclusion rules

  • Recognized non-recurring implementation, onboarding, or professional-services revenue, recognized as delivered (milestone or percentage-of-completion).

Exclusion rules

  • Recurring subscription and usage revenue.
  • Services billed but not yet delivered (deferred until the performance obligation is satisfied).
  • Services bundled with the subscription that are NOT a distinct performance obligation under ASC 606 — those stay in subscription revenue.

Required inputs

  • SOW / project recognition schedule and delivery milestones.

Data-source priority

  • PSA / project-tracking system.
  • Revenue-recognition subledger for the services component.

Edge cases

  • Services bundled with a subscription must be split per the ASC 606 distinct-obligation test.
  • Fixed-fee vs time-and-materials engagements recognize differently (percentage-of-completion vs as-delivered).

Validation checks

  • Pair with finance.services_delivery_costs to read services margin.
  • A rising services share of total revenue pressures blended gross margin — read against finance.gross_margin_pct.

Common miscomputations

  • Recognizing services at billing or signing instead of delivery.
  • Leaving non-distinct bundled services in this line instead of subscription.
  • finance.total_revenue
  • finance.services_delivery_costs

Source

I'mBoard editorial — authored and maintained by I'mBoard, first published 2026-04-01. No third-party standard is cited for this KPI; when one emerges, the definition is back-attributed and promoted to the published tier (a minor version bump). Read the ontology methodology for the published vs editorial tier system, attribution rules, and dispute process.

Stage relevance

Company stagePriority
Series ARecommended
Series BRecommended
Series C+Recommended
PublicRecommended

Suggested for stages: Series A, Series B, Series C+, Public.

Default owning functions

  • Finance

Machine-readable

On this page