RevRec brainstorm · Start · Start · Brainstorm overview
00 — Brainstorm overview (start here)
What this is: Raw working notes from a ramp-up / design brainstorm on Chargebee RevRec — current evidence in the product, what an optimal ASC 606 subledger should look like, and how that compares to Zuora-class outcomes. Not a finished PRD; not legal advice; not an implementation backlog with dates.
Tone: Internal, candid, incomplete on purpose where we don’t know yet.
Read order (short)
- This page
- Capability master — ASC 606 × Zuora × our RevRec (the useful table)
- ASC scenario catalog + priority cards
- Domain model + Architecture from model
- Direction alignment — choices we already locked in conversation
- Supporting depth (product aims, events, use cases, research)
Current vs optimal (one picture)
| Current RevRec (evidence) | Optimal Next (direction) | |
|---|---|---|
| Truth | Warehouse / sync-job outcomes; many behaviors proven in smoke | Contract → PO → schedule → recognize (ASC 606 write model) |
| Correctness bar | Golden sheets / accounting rows in tests | ASC 606 + audit + close; accounting equality |
| North star | Chargebee RevRec + AC Premium | Zuora-class outcomes, Chargebee-native upstream |
| Tests | ~317 smoke cases + gaps/cypress notes | A606 scenario ids → engine goldens; smoke as evidence |
How to read the capability master
Each row asks:
| Column | Meaning |
|---|---|
| Definition | What the capability is (plus Zuora/ASC links when we have them) |
| ASC / A606 | Standard hook + our scenario id if any |
| Zuora | Named surface in Zuora Revenue research |
| RevRec today | in_product / partial / evidence_only / not_in_product / n_a |
| Evidence | Paths under revanu/.../cases/…, tags, cypress/gap notes |
| Next build | ready (domain clear) / needs_design / out |
| CB facts | Does Billing need to supply this? from_billing / from_catalog / derived_in_revrec / ac_only / not_applicable |
“Evidence” ≠ “we should clone the implementation.” It only means: we already exercise something like this in today’s corpus.
What we are not doing here
- Cloning Zuora RevPro internals
- Declaring sprint plans
- Treating smoke sheet shapes as ASC definition
- Handing AC the job of calculating revenue (AC journals amounts RevRec calculates)
Deploy / share
Static site under site/. Regenerated from markdown. Intended for Cloudflare Pages as a living brainstorm doc.