Revenue Recognition
Get Revenue Recognition Waterfall
The recognition curve — revenue already recognized and revenue still scheduled — bucketed by calendar month, with totals. Read-only.
GET
Revenue recognition waterfall
Returns the tenant’s full recognized-plus-scheduled revenue curve, one bucket
per calendar month that has at least one recognition event: how much revenue
each month has already recognized and how much is still scheduled (pending)
to recognize in it. Buckets are grouped from the events themselves, so a
month with no
The statuses above are recognition-event statuses, not schedule statuses
(
recognized or pending event is simply absent — the series is
ordered but not gap-filled. Past months carry recognized; future months
carry scheduled; the current month can carry both. This is the classic
rev-rec waterfall an auditor plots to see how deferred revenue releases over
time. Read-only.
For a single month’s figures plus the still-deferred balance broken down by
currency, use the revenue recognition report.
For the ledger’s own view of the deferred balance, use the
Deferred Revenue rollforward.
Example Request
Response
Fields
Bucket Fields
A tenant with no
recognized or pending recognition events gets
"buckets": null (with both totals 0), not an empty array. Guard for
null before iterating.active, canceled). Only recognized and pending events are summed;
events in any other status (processing, failed, reversed, canceled)
are excluded from every bucket.
Amounts are a raw sum of each event’s amount across whatever currencies the
underlying schedules carry — no FX conversion is applied, so on a
multi-currency tenant the figures are not denominated in reporting_currency.
Read by_currency on the monthly report for
the native split.
Responses are cached per tenant and URL for five minutes; the
X-Cache
header reports HIT or MISS.Errors
Errors use the standard envelope — see Errors.