These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Revenue Recognition
- Data model and import order
The tables behind Revenue Recognition
Revenue Recognition ships with 15 tables, grouped here by the feature that uses them. Every record your team works with lives in one of them, and you can add fields and tables in Proto.
- Tables
- 15
- Features
- 6, plus shared settings
- Change it
- Add fields and tables in Proto
How the model is organised
Revenue schedules:
Revenue schedules references Customers, Products, Organizations and People.
Billing runs:
Billing runs groups Invoices by period; invoice lines can reference revenue schedules and Products.
Payments and collections:
Payments references Customers and Invoices.
Plans and variance:
Plans belongs to an organization and owner; plan lines belongs to a plan.
Review evidence:
Review decisions references review subjects; evidence documents identifies its parent by name and ID; operation receipts records action outcomes.
Configuration:
Organizations, People, Customers, Products and Users supply reference identities.
Every table, by feature
- Revenue schedules4
- Billing runs4
- Invoices and lines6
- Payments and collections4
- Plans and variance5
- Review evidence7
- Shared and settings1
- Revenue schedules
Revenue recognition schedules with method, recognized to date and deferred balance.
Linked to Customers, Products, Organizations, People - Customers
Customer master with numbers, payment terms and billing status.
Linked to People - Products
Billable products and services with unit, list price and revenue type.
- Organizations
Business units and legal entities that own plans, revenue and billing activity.
- Billing runs
Billing cycle headers with period, invoice counts, total and validation status.
Linked to Organizations, People - Invoices
Customer invoices with issue and due dates, subtotal, tax, total and status.
Linked to Customers, Billing runs, Organizations, People - Operation receipts
Executed-operation evidence with operation type, actor, result and document URL.
Linked to People - Organizations
Business units and legal entities that own plans, revenue and billing activity.
- Invoices
Customer invoices with issue and due dates, subtotal, tax, total and status.
Linked to Customers, Billing runs, Organizations, People - Invoice lines
Invoice detail lines with product, quantity, unit price and revenue schedule link.
Linked to Invoices, Products, Revenue schedules - Customers
Customer master with numbers, payment terms and billing status.
Linked to People - Products
Billable products and services with unit, list price and revenue type.
- Revenue schedules
Revenue recognition schedules with method, recognized to date and deferred balance.
Linked to Customers, Products, Organizations, People - Billing runs
Billing cycle headers with period, invoice counts, total and validation status.
Linked to Organizations, People
- Payments
Customer payments with receipt date, amount, method, status and invoice application.
Linked to Customers, Invoices, People - Invoices
Customer invoices with issue and due dates, subtotal, tax, total and status.
Linked to Customers, Billing runs, Organizations, People - Customers
Customer master with numbers, payment terms and billing status.
Linked to People - People
People who own revenue recognition work: contract owners, recognition reviewers and billing operations staff. Each person links to their organization, role title and department.
Linked to Organizations
- Plans
Budget and forecast plan headers with period, owner, version and approval status.
Linked to Organizations, People - Plan lines
Cost center budget and forecast lines with quantity, unit rate and amount.
Linked to Plans - Organizations
Business units and legal entities that own plans, revenue and billing activity.
- Review decisions
Approval decisions on plans, billing runs, invoices and revenue schedules.
Linked to People, Plans, Billing runs, Invoices - Operation receipts
Executed-operation evidence with operation type, actor, result and document URL.
Linked to People
- Review decisions
Approval decisions on plans, billing runs, invoices and revenue schedules.
Linked to People, Plans, Billing runs, Invoices - Evidence documents
Evidence files attached to any parent record with kind, uploader and timestamp.
Linked to People - Operation receipts
Executed-operation evidence with operation type, actor, result and document URL.
Linked to People - Plans
Budget and forecast plan headers with period, owner, version and approval status.
Linked to Organizations, People - Billing runs
Billing cycle headers with period, invoice counts, total and validation status.
Linked to Organizations, People - Invoices
Customer invoices with issue and due dates, subtotal, tax, total and status.
Linked to Customers, Billing runs, Organizations, People - Revenue schedules
Revenue recognition schedules with method, recognized to date and deferred balance.
Linked to Customers, Products, Organizations, People
Keys and references
Retain stable customer, product, organization and contract identifiers. Match invoice line service periods to the linked schedule dates when reviewing billed work. Keep a billing run’s period separate from the invoice date and the schedule’s recognition window. Import review subjects with resolvable references so a later decision can be traced to the record inspected.
Migration order
- Load Organizations, People, Users, Customers and Products with stable source identifiers.
- Load revenue schedules with their customer, product, organization and owner references.
- Load Plans and plan lines by organization, period and version; reconcile planned and actual amounts.
- Load billing runs, Invoices and invoice lines, resolving any schedule references.
- Load Payments, review decisions, evidence documents and operation receipts; reconcile totals and inspect linked evidence.
Set up Revenue Recognition your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.