← All memos
Jun 15, 2026financeplatformResponded

Weekly revenue recognition grouping for finance-mart

Expects responseYes
Response byJun 17, 2026
Tagsfinance-mart, weekly-recognition, mart

Weekly revenue recognition grouping for finance-mart

Why

Finance needs a weekly revenue recognition view in the Finance app. QuickBooks is now useful for bank reconciliation, OPEX classification, founder contributions, and cash bookkeeping, but it is not the authoritative source for earned revenue. Weekly earned revenue should stay tied to Revenue's recognition ledger through the Platform-served finance mart.

The current Finance app can show monthly recognized revenue from groupings.pnl and monthly revenue recognition from groupings.revenue_recognition. It can also read cohort_summary, but that sub-section is cumulative by cohort and current week, not weekly-period recognized revenue. Platform's current compute emits only one cohort_summary observation per cohort for the requested period, so Finance cannot derive a clean weekly recognition report by subtracting consecutive current-week rows.

What

Finance is preparing the app to consume an additive weekly grouping named revenue_recognition_weekly. The requested row shape keeps the existing monthly rows unchanged and gives Finance a business reporting view over Revenue's source-backed recognition rows.

Proposed grouping:

  • groupings.revenue_recognition_weekly
  • Grain: one row per recognition_week × organization_id × org_market_id, plus an organization or portfolio rollup if Platform's finance-mart conventions prefer one.
  • recognition_week: ISO week key, preferably IYYY-"W"IW, aligned to Revenue recognition timing.
  • reporting_period_grain: week.
  • recognized_revenue_cents: net recognized revenue.
  • gross_recognized_revenue_cents: gross non-contra recognition amount.
  • contra_revenue_cents: contra recognition amount as positive contra.
  • recognition_count, exception_recognition_count, exception_revenue_cents, has_exception: same semantics as the existing revenue-recognition rollup.
  • as_of: materialization timestamp.

Composition should read Revenue's silver recognition face, not Revenue bronze. The net-revenue policy should match contracts/finance-mart/revenue-recognition-rollup.md: recognized revenue reflects only revenue earned from customers who paid, and adjustment/service-recovery rows without a Purchase Credit ledger entry produce no recognized revenue.

Asks

Platform, please confirm the additive grouping path and wire revenue_recognition_weekly in GET /api/mart/sections/finance.

The Finance app now has a weekly recognition page ready to consume this grouping. Until the grouping is served, it will show a pending state rather than deriving a misleading weekly figure from cumulative cohort data.

Analytics questions

  1. What earned revenue did the business recognize each week? Answered by recognition_week plus recognized_revenue_cents.
  2. Which organization or org-market recognized the revenue? Answered by organization_id, organization_slug, and org_market_id.
  3. Are there recognition exceptions that should qualify the weekly number? Answered by exception_recognition_count, exception_revenue_cents, and has_exception.

References

  • contracts/finance-mart/revenue-recognition-rollup.md
  • contracts/finance-mart/cohort-summary.md
  • Platform compute: lib/mart/sections/finance.ts

Thread (3 memos)

Jun 15financeWeekly gross margin field for finance-mart weekly recognitionJun 15platformPlatform accepts the additive weekly revenue-recognition grouping path for finance-mart

View source on GitHub