​

Revenue recognition

• GET /api/v1/billing/revenue-recognition/schedule — the per-contract recognition schedule, one entry per calendar month.
• GET /api/v1/billing/revenue-recognition/summary — the rollup: recognized-to-date vs. remaining-deferred as of a reporting date, plus the recognized amount in each period.
• Dashboard → Billing → Revenue recognition — the same data, read-only.

​

1. What revenue recognition answers

• Recognized to date — the share of the contract value earned up to the reporting date, prorated straight-line across the service window.
• Deferred remaining — the share not yet earned. Still a liability; it converts to recognized revenue as the window elapses.

​

2. The two endpoints

​

2.1 Per-contract schedule

curl "https://api.orbit.devotel.io/api/v1/billing/revenue-recognition/schedule?as_of=2026-08-31" \
  -H "X-API-Key: dv_live_sk_your_key_here"

{
  "data": {
    "currency": "USD",
    "as_of": "2026-08-31T00:00:00.000Z",
    "schedules": [
      {
        "contract_id": "committed-use",
        "source": "committed_use",
        "description": "Committed-use commitment",
        "currency": "USD",
        "total_minor": 1200000,
        "total": "12000.00",
        "service_start": "2026-01-01T00:00:00.000Z",
        "service_end": "2027-01-01T00:00:00.000Z",
        "recognized_to_date_minor": 799561,
        "recognized_to_date": "7995.61",
        "deferred_minor": 400439,
        "deferred": "4004.39",
        "periods": [
          {
            "period": "2026-01",
            "period_start": "2026-01-01T00:00:00.000Z",
            "period_end": "2026-02-01T00:00:00.000Z",
            "amount_minor": 101918,
            "amount": "1019.18"
          }
        ]
      }
    ]
  }
}

​

2.2 Recognized-vs-deferred summary

curl "https://api.orbit.devotel.io/api/v1/billing/revenue-recognition/summary?as_of=2026-08-31" \
  -H "X-API-Key: dv_live_sk_your_key_here"

{
  "data": {
    "currency": "USD",
    "as_of": "2026-08-31T00:00:00.000Z",
    "contract_count": 2,
    "total_contract_value_minor": 1240000,
    "total_contract_value": "12400.00",
    "recognized_to_date_minor": 803561,
    "recognized_to_date": "8035.61",
    "deferred_remaining_minor": 436439,
    "deferred_remaining": "4364.39",
    "by_period": [
      { "period": "2026-01", "recognized_minor": 105918, "recognized": "1059.18" }
    ]
  }
}

​

3. The straight-line model

• Committed-use commitment. The total contract value is the monthly commit × the number of whole months in the contract term, recognized straight-line over the term. When the commitment carries no term dates, the schedule falls back to the current billing period — one month recognizing the monthly commit — so a schedule always exists.
• Subscription invoice lines. Each positive-amount line on a subscription invoice recognizes over the line’s own service window; when the line has none, the window falls back to the invoice’s billing period, then to the invoice-date month.

• The split is prorated to the exact reporting instant — a mid-month as_of recognizes the elapsed fraction of that month, not the whole month.
• Credit and zero-amount invoice lines do not recognize and are excluded.
• The rollup requires one currency; it reports the commitment’s currency, else the currency of the first subscription line, else USD.

​

4. Dashboard walkthrough

• Stat cards — total contract value, recognized to date, and deferred remaining across all contracts.
• Recognized by period — the cross-contract table of revenue per calendar month.
• Per-contract schedules — one card per contract with its source badge (Committed-use or Subscription), service dates, recognized/deferred split, and the month-by-month schedule table.

​

5. Finance-ops use

• Subscription history window. Subscription lines come from the most recent invoice page (up to 50 invoices). Long-lived accounts should treat the commitment as the primary multi-year source and the subscription lines as the recent-period complement.
• Commitment without a term. A commitment with no term dates recognizes the monthly commit inside the current billing period — a useful default, not a multi-year schedule. Have your Devotel account team set the term for the full picture.
• Subscription lines fail open. If the billing provider read is unavailable, the endpoints still return the committed-use schedule — the summary degrades rather than errors.
• Not a revrec ledger. The schedule is computed on demand from live contract data; renegotiating a commitment restates the whole schedule. There is no stored history to drift — the contract is the record.

​

6. Related pages

• Billing overview — the wallet, top-ups, invoices, commitments, and alerts this surface sits alongside.
• Billing API reference — endpoint-by-endpoint request/response detail.
• Committed-use contracts — the drawdown meter; revenue recognition is the deferred-revenue view of the same contract.