RevRec brainstorm · Research · Zuora scope tiers
12 — Scope from Zuora Revenue (north star)
Status: draft decision aid
Date: 2026-07-29
North-star product: Zuora Revenue
Capability inventory (sourced): research/zuora-revenue-capability-map.md
Our product aims: 00-product.md
Chargebee public positioning (overlap): chargebee.com/revenue-recognition-software
0. How to use this doc
You said you don’t know in/out of scope yet. This doc turns Zuora Revenue into a capability backlog with proposed tiers, so we can decide deliberately.
| Column | Meaning |
|---|---|
| Zuora capability | What the category leader sells |
| CB markets today | Chargebee RevRec marketing already claims it |
| Our design today | Covered in RevRec Next docs (MVP or later) |
| Proposed tier | MVP / Next / Later / Out for this redesign |
| Notes | Why |
Rule: We are not cloning Zuora architecture (RevPro staging / RC grouping templates / Workbench). We are cloning the product outcomes finance buys — ASC 606 subledger, close, reports, audit — with Chargebee Billing as the native upstream advantage.
1. What Zuora Revenue is (one picture)
Upstream (Billing / Orders / Invoices / Events / ERP)
↓
Staging → group into Revenue Contracts
↓
ASC 606 engine:
identify contract → identify POBs → TP (+ VC)
→ SSP allocate → release / recognize
↓
Journals → GL
Reports / waterfalls / disclosures / close dashboard
Audit trail + holds + approvals
Source: Zuora Overview — full inventory in the research doc.
Chargebee equivalent shape (ours):
Chargebee facts → extract → normalize → apply API
open / amend / bill / pay / credit / recognize / post_journals
↓
Ops DB (contracts, POs, schedules, AR) → close → journals → reports
Same product class. Cleaner internal model. See 02, 09.
2. Proposed scope tiers (decide these)
| Tier | Intent | Who it’s for |
|---|---|---|
| MVP | Working product outcome: single-PO ratable SaaS from Chargebee, close, JE export, waterfall, audit trail | Majority of CB merchants; proves the thesis |
| Next | What Chargebee marketing already promises that MVP doesn’t fully cover | Growth / mid-market complexity |
| Later | Enterprise Zuora parity (usage deep, multi-book, LT/ST, cost, full SOX pack) | Large / public / multi-entity |
| Out | Not this product (or not this redesign) | ERP-as-RevRec, Hotglue CSV parity, Catalyst/ERP sync |
These tiers are proposals. Lock via ADR when you agree.
3. Capability → tier map
3.1 Core ASC 606 engine
| Zuora capability | CB markets today | Our design | Proposed tier |
|---|---|---|---|
| Five-step ASC 606 / IFRS 15 | Yes | Yes (01, 08) | MVP |
| Revenue contract + POB model | Yes (subledger / SO language) | Yes (Contract, PO) |
MVP |
| Touchless recognition (rules, exceptions only) | Yes | Yes (apply loop) | MVP |
| Configurable policies | Yes | Yes (11) | MVP (thin set) |
| RC grouping templates (complex) | Implicit | Explicit contract from sub — not Zuora grouping engine | Out as architecture; outcome in MVP |
| POB bundles / consolidated POBs | Yes (multi-PO) | Deferred multi-PO | Next |
| Variable consideration engine | Partial (usage/credits) | Later | Later |
| SSP formula + relative allocation | Yes (SSP library) | Single-PO 100% in MVP; multi-PO next | MVP degenerate / Next real |
| SSP Analyzer / historical / AI SSP | No strong claim | — | Later |
| Residual SSP | — | — | Later |
3.2 Recognition methods & triggers
| Zuora capability | CB markets today | Our design | Proposed tier |
|---|---|---|---|
| Over-time ratable (contract / monthly / daily) | Yes | Yes (ratable) |
MVP |
| Point-in-time | Yes | Listed in 11 | Next |
| Booking-based / upon booking | Implicit | Prefer open from subscription (booking-ish) | MVP |
| Billing-based recognition | Yes | record_billing sibling; recognition not invented from invoice |
MVP (billing as AR); billing-as-trigger optional Next |
| Events / delivery / milestones / PS | Yes (delivery-based) | record_delivery later |
Next (PIT+delivery) / Later (full PS) |
| Usage / consumption revenue | Yes (usage-based) | Later scenarios S07 | Next (basic) / Later (PayGo, drawdown, unbilled usage suite) |
| Ramp contracts | Yes | Later | Next |
| User-defined / milestone schedules | — | — | Later |
3.3 Contract modifications
| Zuora capability | CB markets today | Our design | Proposed tier |
|---|---|---|---|
| Upsell / downsell / cancel / returns | Yes | Yes (03, 11) | MVP (prospective + cancel + CN default) |
| Prospective allocation | Yes | Yes (S03) | MVP |
| Retrospective / cumulative catch-up | Implied | Explicitly deferred | Next |
| Retro-prospective / impairment | — | — | Later |
| Configurable mod rule matrix | Yes | Named policies | MVP thin / Next rich |
3.4 Close, journals, reconciliation
| Zuora capability | CB markets today | Our design | Proposed tier |
|---|---|---|---|
| Period close workflow | Yes | Yes (F3 in 10) | MVP |
| Continuous / daily recognition | Claimed (Zuora); CB “as events occur” | Period recognize + optional frequent runs |
MVP period; continuous Next |
| Journal entry generation → GL | Yes | post_journals |
MVP (export) |
| Pre-built ERP GL connectors (NS/Workday/D365) | CB: NS, Intacct, QBO, Xero | Keep as integration layer | Next (reuse existing connectors where possible) |
| Close dashboard + anomaly detection | Partial | Pre-close checks | MVP thin / Next dashboard |
| Automated report reconciliation matrix | — | Waterfall tie-out | Next |
| CA/CL netting | Disclosure-ish | Deferred waterfall + unbilled | Next |
| LT/ST reclass | — | — | Later |
| Manual journal entries + approvals | — | — | Later |
| Revenue holds / transfer holds | Period lock | Period lock MVP; holds Next | MVP lock / Next holds |
3.5 Audit & controls
| Zuora capability | CB markets today | Our design | Proposed tier |
|---|---|---|---|
| Immutable audit trail (event → balance) | Yes | AppliedEvent + raw lake (10 F5) | MVP |
| Role-based access / SoD | Implied | Platform | Next (harden) |
| Full SOX report pack | — | — | Later |
| 7-year retention | — | Policy | Later (ops requirement) |
| Approvals on release/MJE | — | — | Later |
3.6 Reporting & disclosures
| Zuora capability | CB markets today | Our design | Proposed tier |
|---|---|---|---|
| Deferred / revenue waterfall | Yes | Yes (A5/A6, F6) | MVP |
| RC / billing / unbilled rollforwards | Partial | Deferred + unbilled | Next |
| Trial balance | — | — | Next |
| ASC 606 disclosures (CA/CL, satisfied POBs) | Partial | RPO aim A5 | Next |
| Unsatisfied POB / RPO | Implied | Explicit aim | Next |
| ARR / NRR / bookings / billings | Yes | Aim A6 | Next (MVP can ship recognized + deferred only) |
| Forecast revenue | Claimed | — | Later |
| VC / cost / consumption waterfalls | — | — | Later |
| Multi-currency FX waterfalls | — | Multi-currency aim A8 | Later |
3.7 AR / cash (sibling)
| Zuora capability | CB markets today | Our design | Proposed tier |
|---|---|---|---|
| Invoices, payments, CNs in subledger | Yes (AR complete view) | AR projector / AC Premium | Next (MVP: bill/pay/credit events feed revenue; full AR UI later) |
| AR aging / roll-forward | Yes | Aim A7 | Next |
| Tax position in subledger | Claimed by CB | — | Later / clarify with product |
3.8 Integrations
| Zuora capability | CB markets today | Our design | Proposed tier |
|---|---|---|---|
| Native Billing ↔ Revenue | Yes (Chargebee advantage) | Chargebee SourceAdapter first | MVP |
| Other billing (Stripe, …) | Yes | Adapters later | Later |
| CRM / CPQ upstream | Yes (ecosystem) | Not day-one | Later |
| File upload (non-integrated) | Manual path exists today | Optional | Next (migration / edge) |
| Hotglue CSV / OrderDetails parity | Internal today | Explicitly not the bar | Out |
3.9 Advanced enterprise (default Later / Out)
| Zuora capability | Proposed tier |
|---|---|
| Multi-book (GAAP vs IFRS vs local) | Later |
| Cost capitalization (commissions, COGS, rebates) | Later / possibly Out of RevRec core |
| Significant financing component | Later |
| Quote-impact simulations / GTM AI | Later (nice; not subledger core) |
| Dedicated shard / managed services packaging | Out of product design (ops) |
| Cloning Zuora Workbench UX literally | Out — design our UX from use cases (10) |
4. Recommended MVP (working product outcome)
If we freeze nothing else, freeze this:
MVP = a Chargebee-native Zuora-Revenue-class thin slice:
- Ingest Chargebee: customers, subscriptions (+ term), catalog, invoices, credit notes, transactions
- Open one PO ratable contract from subscription
- Bill / pay / credit without inventing POs from invoices
- Amend prospective; terminate with named cancel policy; one CN policy
- Recognize(period) + deferred waterfall
- Post journals (summarized export)
- Audit drill-down event → schedule → raw
- Close/lock period
MVP is successful when a finance user can close a Chargebee SaaS tenant and explain every recognized dollar — without Hotglue, without OrderDetails manufacturing.
Mapped to existing specs: 08-mvp-spec.md + S01–S05 in 04 + flows F1–F5 in 10.
5. Already claimed by Chargebee marketing → backlog pressure
These are public promises; they pull items out of “nice later” into Next unless product explicitly walks them back:
| Claim (CB site) | Tier pressure |
|---|---|
| Usage / hybrid / credits / ramps | Next |
| Multi-PO + SSP library | Next |
| Amendments (upsell, co-term, CN, early renewals) | MVP core + Next richer |
| Full AR view + aging | Next |
| Automated close + JE to GL | MVP |
| Waterfalls + ARR/NRR dashboards | Waterfall MVP; ARR/NRR Next |
| Audit trail contract → JE | MVP |
| Multi-billing connectors (Stripe, …) | Later |
6. What we explicitly do not take from Zuora
| Leave behind | Why |
|---|---|
| Invoice/SO → RC via complex grouping as the only contract path | Chargebee subscription is the contract signal |
| Reconstructing POs from billing time-series | Already rejected (0002) |
| RevPro-style mandatory BRD / template sprawl as day-one UX | Start with opinionated SaaS defaults + few policies |
| Boiling the ocean to match every Zuora report on day one | Ship waterfall + close; expand reports with demand |
| Hotglue / Camunda / sheet spine | Accidental; not the product |
7. Decision checklist (for you / product)
Answer these to lock scope. Each becomes an ADR when decided.
- MVP merchant: Chargebee-only SaaS, single-PO ratable — yes/no?
- Is multi-PO + SSP in v1.0 or v1.x? (CB markets it → pressure for Next soon)
- Usage recognition: Next vs Later?
- Retrospective mods: Next vs Later?
- AR Premium: same product UI in Next, or separate track?
- Disclosures/RPO: required for first GA or post-GA?
- GL connectors: export-only MVP OK?
- Any Zuora capability we will never chase? (cost amortization? multi-book? financing?)
8. Related docs
| Doc | Role |
|---|---|
| research/zuora-revenue-capability-map.md | Sourced Zuora inventory |
| 00-product.md | Aims |
| 08-mvp-spec.md | Normative MVP |
| 10-use-cases-and-flows.md | End-user flows |
| 11-rules-reference.md | Policy catalog |
| decisions/ | Lock answers from §7 here |