Revenue
Revenue in Tabs is the revenue recognition side of your contracts — how much revenue you earn, when you earn it, and how it maps to your ERP. Tabs separates billing from revenue recognition so you can invoice on one schedule and recognize revenue on another.
Role in Tabs
Revenue sits alongside billing in the contract lifecycle. After a contract is processed:
- Billing terms define when and how customers get invoiced
- Performance obligations define when and how revenue is recognized
- Revenue schedules translate performance obligations into specific revenue amounts recognized each month
- Close Management guides the period-end review process and generates journal entries that can be synced to your ERP
This distinction is important because billing and revenue often follow different rules. A customer may be billed monthly in arrears for usage, while revenue is recognized as the service is consumed. Similarly, a multi-element contract may require the transaction price to be allocated across multiple performance obligations under ASC 606, resulting in revenue recognition patterns that differ from the billing schedule.
Billing covers invoice generation and delivery. Revenue covers recognition schedules, SSP allocation, and month-end close. See Billing Terms & Schedules for how charges are configured, and Revenue Dates for service period configuration on products.
For the full entity hierarchy, see Tabs data model.
Explore revenue
Performance obligations, revenue schedules, categories, and billing vs revenue.
Service period start and end for revenue recognition.
ASC 606 SSP allocation across performance obligations.
Month-end close and journal entry sync to your ERP.