Contents
- Report Description
- Data Sources
- Features
- Filters
- Calculation Summary
- Revenue Recognition Behavior
- Multi-Currency Handling
- Use Cases
- FAQs
Report Description
The Revenue by Customer and Subscription Report provides a consolidated view of recognized revenue across customers and subscriptions for the selected reporting period. The report enables finance teams to analyze recognized revenue by customer, subscription, product, and accounting period while supporting financial reconciliation, reporting, and audit activities.
Note: Revenue is derived from Revenue Schedules (RSL), Billing Schedules (BSL), or Order data, depending on the configured revenue recognition method.
Purpose
Use this report to:
- Review and validate recognized revenue
- Reconcile accounting entries with operational data
- Analyze revenue contribution by customer, subscription, and product
- Support audit and financial reporting needs
Data Sources
The report derives revenue from multiple sources depending on configuration:
| Source | Usage |
| Revenue Schedules (RSL) | Primary source for deferred revenue |
| Billing Schedules (BSL) | Used for non-deferred revenue, such as revenue recognized using the Recognize on Invoicing rule. |
| Orders | Used for legacy orders that do not have revenue schedules. |
Features & Primary Benefits
- View monthly recognized revenue across customers
- Drill down into revenue by customer, subscription, plan, and product
- Supports both deferred and non-deferred revenue scenarios
- Helps validate accounting entries and revenue recognition
Filters
This report uses standard filters. Refer to Common Filters in the Recurring Revenue Reporting Framework.
Additional filters
- Revenue Customer ID / Customer Name
- Parent Customer ID / Name
- Revenue Line ID
- Revenue ID
- Period Date
- Include Non-Deferred Revenue (Yes / No)
Calculation Summary
- Revenue is calculated from Revenue Schedule Lines (RSL) for deferred revenue.
- For non-deferred revenue (Recognize on Invoicing), revenue is derived from Billing Schedule Lines (BSL).
- For legacy orders without Revenue Schedules, revenue is derived from the order amount and order date.
- Revenue is aggregated by customer and contract (Subscription ID or Order ID) for each reporting period.
Revenue Recognition Behavior
- Deferred revenue is reported based on Revenue Schedule Lines (RSL).
- For posted non-deferred revenue, the report uses the invoice date.
- For legacy orders, revenue is reported using the order amount and order date.
Multi-Currency Handling
Revenue amounts are converted to the reporting currency based on whether the revenue is deferred or non-deferred, and whether the associated records have been posted.
Deferred Revenue (Revenue Rule: Except Recognize on Invoicing)
| Scenario | Currency Conversion Logic |
| Posted Revenue Schedule Lines (RSL) | Uses the exchange rate recorded on the Journal Entry (JE). The converted revenue is calculated using the Revenue Schedule Line amount and the exchange rate applied during journal entry posting. |
| Unposted Revenue Schedule Lines (RSL) |
Uses the currency conversion method configured in the company's Revenue Schedule Currency Conversion settings. Depending on the selected rate type:
|
Non-Deferred Revenue (Revenue Rule: Recognize on Invoicing)
| Scenario | Currency Conversion Logic |
| Posted Invoice Lines | Uses the exchange rate stored on the posted Invoice, following the same currency conversion logic as the Billing Reports. |
| Unposted Invoice Lines |
Uses the company's Invoice Currency Conversion settings. Depending on the configured rate type:
|
Use Cases
Use Case 1: Review Posted Deferred Revenue
Use this report to review deferred revenue that has already been posted to the General Ledger. The report uses the exchange rate recorded on the corresponding Journal Entry (JE), ensuring that the reported revenue matches the posted accounting entries.
Use Case 2: Review Unposted Deferred Revenue
Use this report to analyze deferred revenue before posting. Revenue is converted using the company's configured Revenue Schedule Currency Conversion method, allowing you to preview how revenue will be reported.
Example
Scenario
- A subscription is billed in EUR.
- The company's reporting currency is USD.
- The revenue rule is Recognize on Invoicing.
- The invoice has not yet been posted.
- The company uses the Average Rate conversion method.
Result
The report converts the revenue from EUR to USD using the average exchange rate for the financial period corresponding to the Charge Ready Date.
Sample Report Output
Displays recognized revenue by customer and subscription across selected periods.
When to Schedule this Report
Run this report at the end of an accounting or financial reporting period to validate recognized revenue, reconcile revenue-related journal entries, and review revenue by customer and subscription. The report can also be used throughout the period to monitor recognized revenue as transactions are processed.
FAQs
What is the difference between deferred and non-deferred revenue?
| Deferred revenue is recognized over time using revenue schedules, while non-deferred revenue is recognized at invoicing. |
If a Billing Schedule Line (BSL) has been posted, how is revenue displayed?
| For posted Billing Schedule Lines, revenue is consolidated and reported based on the invoice date. If multiple Billing Schedule Lines are included in a single posted invoice, the associated revenue is displayed in the reporting period corresponding to the invoice date. |
Does this report include both revenue types?
| Yes, based on the Include Non-Deferred Revenue filter. |
Why is revenue shown in March instead of January or February?
| If multiple Billing Schedule Lines are consolidated into an invoice that is posted in March, the report displays the revenue in March based on the invoice date rather than distributing it across the earlier periods. |
Comments
0 comments
Please sign in to leave a comment.