Overview of Revenue Recognition Events Transaction
The Revenue Recognition Event Transaction object captures data for daily consumption, delivery, and unbilled usage, supporting features like Delivery Pricing and Prepaid with Drawdown in Zuora Billing.
The Revenue Recognition Event Transaction object is available in the data source and data queryNo Content found for /db/organizations/zuora/repositories/prod-sitemap/content/documents/external_publications/billing/order_to_revenue/revenue_recognition_events_transaction_fields.dita. Revenue recognition event transactions capture data for daily consumption, daily delivery, and unbilled usage.
Revenue recognition event transactions are generated for the following features in Zuora Billing:
-
Prepaid with Drawdown
-
Minimum Commitment
-
Unbilled Usage for both termed and evergreen subscriptions
Revenue recognition events transactions are generated in the following cases:
-
When a Delivery Pricing charge is activated, a revenue recognition event transaction of the
Delivery Scheduletype is generated. For more information, see Revenue Recognition Events Transaction object fields and Data QueryNo Content found for /db/organizations/zuora/repositories/prod-sitemap/content/documents/external_publications/billing/order_to_revenue/revenue_recognition_events_transaction_fields.dita. -
When you use the Advanced Consumption Billing feature and upload usage, revenue recognition event transactions of the
Daily Rated Usagetype and theUnbilled Usagetype are generated.
For Order to Revenue customers, when the Advanced Consumption Billing feature is enabled, the preceding transactions are consumed by Zuora Revenue for revenue recognition.
When you upload usage for Prepaid with Drawdown, Zuora generates revenue recognition event transactions of the Daily Rated Usage type and the Unbilled Usage type. When you deplete a prepaid balance fund, Zuora generates a Daily Consumption Summary (DCS) event. By default, Zuora classifies the event as Daily Rated Usage. A configurable setting lets Zuora classify depletion events with the separate Deplete event type. The setting is off by default.