Revenue Schedule
A Revenue Schedule in Salesforce Products and Pricing is a configuration on a Product (or Opportunity Product) that defines how the total revenue from selling that product will be recognized over time, distributing the total across multiple installments rather than recording all of it at the closing date.
Definition
A Revenue Schedule in Salesforce Products and Pricing is a configuration on a Product (or Opportunity Product) that defines how the total revenue from selling that product will be recognized over time, distributing the total across multiple installments rather than recording all of it at the closing date. The schedule is used for products whose revenue is earned over time: annual subscriptions, multi-year service contracts, deferred licenses, professional services delivered over weeks or months. The Revenue Schedule sits alongside the Quantity Schedule (which describes when quantity is delivered) as one of the two scheduling concepts on the standard Product model.
Revenue Schedules matter because for many products the revenue recognition does not match the close date. A twelve-month software subscription closes once but recognizes revenue monthly for twelve months. Without Revenue Schedules, the Opportunity's total amount sits in a single point on the close date, which misrepresents the actual revenue timing. With Revenue Schedules, the Opportunity Product creates a series of OpportunityLineItemSchedule records that capture the monthly recognition installments, providing more accurate revenue forecasting and reporting.
How Revenue Schedules work in Salesforce
Default Revenue Schedule on the Product
Each Product can have a default Revenue Schedule defined on its detail page: the schedule type (Divide, Repeat, or none), the schedule installment period (Daily, Weekly, Monthly, Quarterly, Yearly), and the number of installments. The Divide schedule splits the total revenue across N installments (a 12,000 dollar subscription divided into 12 monthly installments of 1,000). The Repeat schedule repeats the same amount across N installments (a recurring 1,000-per-month charge for 12 months totaling 12,000). When an Opportunity Product is added with the default schedule, the schedule applies automatically and creates the installment records.
Schedule overrides per Opportunity
The default schedule on the Product is a starting point. On any specific Opportunity Product, the schedule can be overridden: different period, different number of installments, custom installment amounts. The override is useful for non-standard deals where the customer has negotiated different recognition timing. The platform creates OpportunityLineItemSchedule records reflecting the overridden schedule. These per-Opportunity overrides are the most common use of Revenue Schedules in real-world implementations because every significant deal has unique commercial terms.
Revenue versus Quantity Schedules
Salesforce supports both Revenue Schedules and Quantity Schedules. Revenue Schedules describe when the revenue is recognized. Quantity Schedules describe when the product is delivered (or how the quantity is split over time). For most products, the two schedules are aligned: a 12-month subscription delivers value monthly and recognizes revenue monthly. But for some products, the two diverge: an upfront license fee with deferred delivery, or a quantity that ships in batches but is recognized as revenue all at once. Salesforce supports both schedule types independently, and the admin chooses which one (or both) applies per Product.
Forecast and pipeline implications
Revenue Schedules affect Opportunity-based reporting and forecasting. Without schedules, the Opportunity amount is a single value at the close date. With schedules, the Opportunity has visible recognition over multiple future periods, which makes forecasting more accurate for subscription businesses. Custom reports against OpportunityLineItemSchedule provide period-by-period revenue projections, supporting the FP&A team's revenue forecast. Collaborative Forecasting Type configurations can be set to use the schedules rather than the raw amount, which is the right setting for subscription-heavy businesses but requires explicit configuration.
Integration with billing and finance systems
Revenue Schedules in Salesforce do not directly produce invoices or general-ledger entries. They are forecast representations of expected recognition. The actual recognition flows through finance systems (NetSuite, SAP, Oracle, Workday). The integration between Salesforce Revenue Schedules and the finance system typically synchronizes the planned recognition timing for budget and forecast purposes, with the finance system holding the actual booked revenue. Misalignment between the two systems is a common audit issue: Salesforce shows planned recognition, the finance system shows actual booked revenue, and the variance becomes a reconciliation conversation.
Salesforce CPQ and Revenue Cloud
For complex revenue recognition scenarios (multi-element arrangements, ASC 606 compliance, deferred revenue recognition), standard Revenue Schedules are limited. Salesforce CPQ and the broader Revenue Cloud product handle these scenarios with much richer recognition logic: contract-based recognition, performance obligation tracking, accounting standards compliance. Customers with these requirements should evaluate whether standard Revenue Schedules are sufficient or whether CPQ or Revenue Cloud features are needed. Most subscription businesses with simple recognition can use Revenue Schedules; complex enterprise sales motions typically outgrow them within a year or two.
Reporting on Revenue Schedules
Reports on OpportunityLineItemSchedule are the foundation for period-by-period revenue projections. Useful reports include: future revenue by month for the next 24 months, recognition schedules per region or product family, deferred revenue projections, churn impact from scheduled revenue at risk. Custom dashboards built from these reports support FP&A and finance leadership conversations about future revenue visibility. CRM Analytics extends the analysis with cohort views and predictive analytics specific to subscription metrics. The reporting is what makes Revenue Schedules operationally valuable beyond just data capture.
Schedules in modern subscription businesses
Standard Revenue Schedules made sense in a world where most Salesforce deals were perpetual licenses with simple recognition. Modern subscription businesses face requirements that exceed what standard Revenue Schedules can express: contract-based renewal logic, mid-term upgrades and amendments, multi-currency billing for global accounts, deferred revenue accounting compliant with ASC 606 and IFRS 15. For these scenarios, the platform expects customers to adopt Salesforce CPQ for the quoting side and Revenue Cloud (or a third-party revenue recognition tool like Zuora, NetSuite Advanced Revenue Management, or Sage Intacct) for the recognition side. The standard Revenue Schedule on Products and Opportunity Products becomes a forecast input rather than the source of truth. For smaller subscription businesses (one product line, simple renewal terms, single-currency), the standard schedules can still work as the primary recognition tool. The boundary between standard schedules being sufficient versus needing CPQ or Revenue Cloud usually sits at around 100 customers and a single product line; beyond that scale, the operational pain of managing complex recognition through standard schedules typically exceeds the cost of adopting the broader tooling. Customers approaching that scale should evaluate the upgrade proactively rather than waiting for the operational pain to force the conversation.
Practical implementation patterns and pitfalls
Three patterns recur in real-world Revenue Schedule deployments. The matching-default pattern: most Products use the default schedule, with overrides reserved for genuine commercial exceptions. The matching-default keeps the data clean and the reporting consistent. The everyone-overrides pattern: reps override schedules on every Opportunity Product because the default never quite matches the actual deal terms. The override-noise undermines reporting and produces a soup of inconsistent recognition logic that finance cannot trust. The lazy pattern: schedules are enabled but never overridden, producing data that always reflects the default rather than actual deal terms. Each pattern has its own data quality story. The healthy state is matching-default with disciplined override authority for specific commercial exceptions. Achieving that state requires deliberate training, audit, and incentive alignment over multiple quarters. Programs that get this right report dramatically better revenue forecasting accuracy than programs that treat schedules as administrative noise to ignore.
Configure and use Revenue Schedules
Setting up Revenue Schedules involves enabling the feature, configuring default schedules on Products, and training the sales team on how to handle schedule overrides per deal. The workflow below covers the standard sequence for a subscription business adopting Revenue Schedules.
- Enable Revenue Schedules
From Setup, navigate to Product Schedules Setup and enable Revenue Schedules (and optionally Quantity Schedules). The feature applies org-wide. Save the enablement. Confirm the Product detail page now shows the Revenue Schedule configuration section. The feature is now available for any Product to use, but no Products are automatically scheduled until each one is configured.
- Configure default schedules per Product
For each Product that needs Revenue Schedule support, edit the Product record. Set the Revenue Schedule fields: Schedule Type (Divide or Repeat), Installment Period (Monthly, Quarterly, etc.), Number of Installments. Save. The default applies to new Opportunity Products that reference this product. Existing Opportunity Products are not retroactively updated; the default only applies going forward.
- Train the sales team on schedule overrides
Train sales reps and ops on how to view and override Revenue Schedules on Opportunity Products. Walk through the standard case (default schedule applies) and the override case (custom schedule for a non-standard deal). Document the override decision authority: which roles can change schedules, what approvals are required, how variances from the default are reviewed. Without training, reps either ignore the schedules or override inconsistently, both of which undermine the reporting.
- Build the reporting and integrate with finance
Build the OpportunityLineItemSchedule reports that FP&A needs: future revenue by period, recognition schedules per product family, deferred revenue projections. Schedule these reports for monthly review with finance leadership. Integrate with the finance system to synchronize planned recognition timing into the budget and forecast tools. Reconcile periodically between the Salesforce planned recognition and the finance-system booked revenue to catch drift early.
- Existing Opportunity Products are not retroactively scheduled. Default schedule applies only to new Opportunity Products going forward.
- Schedule data lives in OpportunityLineItemSchedule. Custom reports need this object specifically, not just Opportunity Product.
- Salesforce Revenue Schedules are forecast representations, not actual booked revenue. Reconciliation with the finance system is essential.
- Complex recognition scenarios (ASC 606, multi-element arrangements) exceed standard Revenue Schedule capabilities. Salesforce CPQ or Revenue Cloud are the right tools.
- Inconsistent override behavior across reps undermines reporting. Train on override authority and document the decision rules.
Trust & references
Straight from the source - Salesforce's reference material on Revenue Schedule.
- Revenue and Quantity SchedulesSalesforce Help
- ProductsSalesforce Help
About the Author
Dipojjal Chakrabarti is a B2C Solution Architect with 29 Salesforce certifications and over 13 years in the Salesforce ecosystem. He runs salesforcedictionary.com to help admins, developers, architects, and cert/interview candidates sharpen their fundamentals. More about Dipojjal.
Test your knowledge
Q1. What is a Revenue Schedule?
Q2. When are revenue schedules valuable?
Q3. What pairs with revenue schedules?
Discussion
Loading discussion…