Salesforce Revenue-Cloud-Consultant-Accredited-Professional Salesforce Revenue Cloud Consultant Accredited Professional Exam Practice Test

In Salesforce Revenue Cloud, an Invoice Scheduler is used to automate the generation of invoices for billable order products. The Invoice Scheduler uses an Invoice Run to evaluate when and if an Order Product gets invoiced1.

When the Invoice Scheduler is set up with a Target Date (e.g., January 15) and Bill Usage Charges is set to False, it will generate invoice lines for Order Products with a Next Billing Date that is equal to or earlier than the Target Date1. This is because the Invoice Run is looking for eligible Order Products that match its criteria, which in this case would be Order Products with a Next Billing Date on or before the Target Date1.

It’s important to note that the Invoice Scheduler kicks off Invoice Runs when it hits the start time that you specify. For example, if you have a monthly Invoice Scheduler that runs on the 15th of every month, it will generate invoices for all Order Products with a Next Billing Date of January 15 or earlier1.

References:

• Use Invoice Scheduler to Generate Invoices - Salesforce
• Using Invoice Schedulers to Automate Invoice Creation - Salesforce

In Salesforce Revenue Cloud, when a new release is being deployed, it’s important to test the implementation against the new release before it deploys to production. This can be achieved by:

• Reviewing status.salesforce.com to determine refresh cutoff for the new release: Salesforce provides information about the refresh cutoff for the new release on status.salesforce.com. This allows you to know when the new release will be available in the sandbox for testing.
• Determining whether your sandbox is on a preview or non-preview instance: Salesforce refreshes preview sandboxes a month before each major release. Regular, non-preview sandboxes are refreshed toward the end of the release cycle. Knowing whether your sandbox is on a preview or non-preview instance can help you plan your testing schedule accordingly.

It’s worth noting that while Salesforce ensures that all sandboxes are upgraded, the timing of the upgrade can vary depending on whether the sandbox is on a preview or non-preview instance. Submitting a ticket to support when you want your sandbox updated is not a standard practice for preparing for a new release.

References

• Test New Releases in a Sandbox Unit | Salesforce Trailhead
• Salesforce Introduces Revenue Cloud to Help Businesses Accelerate …

  When scoping a Revenue Cloud project, it's essential to involve key customer teams that will be impacted by or contribute to the implementation. These teams typically include Information Technology, which will handle the technical aspects of the implementation; Sales Operations, which is responsible for the processes and strategies surrounding the sales efforts; and Accounting and Finance, which will manage billing, invoicing, and financial reporting aspects of the solution. Involving these teams ensures that all necessary requirements are captured and that the solution aligns with the organization's technical capabilities and business processes​​.

 The matching ID field is used to link usage records to usage summaries based on a common identifier. This field is especially useful when there are amendments to the order products, as it allows usage records to be uploaded to the correct usage summary without having to change the order product ID or the usage summary ID. The matching ID field can be used as an external ID to simplify usage uploads after amendments, as it can be populated by a workflow rule or a formula based on certain criteria. 12 References:

• Usage Summary and Usage Fields - Salesforce
• Differences between the ‘External ID’ field and the ‘Unique ID’ field setting - Salesforce

The correct sequence of evaluation events for a price rule, quote calculator plugin (QCP), and CPQ package pricing engine is as follows:

• Internal Initialization: This is the first step where the system prepares for the calculation process.
• On Initialization: At this stage, any price rules that are set to trigger ‘On Initialization’ are run.
• Calculate Formulas: The system evaluates formula fields.
• Before Calculate: Any price rules that are set to trigger ‘Before Calculate’ are run.
• Calculate Quantities: The system calculates quantities, for example, bundle components.
• On Calculate: Any price rules that are set to trigger ‘On Calculate’ are run.
• Price Waterfall Calculation: The system calculates out-of-the-box pricing tools such as block pricing, discount schedules, etc.
• After Calculate: Any price rules that are set to trigger ‘After Calculate’ are run1.

This sequence ensures that all calculations and price rules are applied in the correct order, providing accurate pricing information1. References: 

&language=en_US&type=5

&language=en_US&type=1

 The Salesforce CPQ (Configure, Price, Quote) system allows for the creation of custom fields on the Opportunity Line Item object, such as ARR c, to capture recurring revenue. This can be used in conjunction with a price rule to copy the value from the corresponding field (ARR c) on the SBQQ QuoteLine__c object. This solution is efficient as it leverages the existing structure and functionality of Salesforce CPQ, allowing for the seamless integration of recurring revenue data into existing pipeline reports. References:

• Salesforce Revenue Cloud documents and learning resources
• Salesforce Introduces Revenue Cloud to Help Businesses Accelerate Revenue Growth Across Any Channel
• Get Started with Revenue Intelligence
• Introduction to Revenue Intelligence for Sales Cloud
• Getting Started: Revenue Cloud: Salesforce Billing
• CPQ Object Relationships - Salesforce
• Object Reference for the Salesforce Platform
• Salesforce CPQ Clone with Related Button to clone Quotes to a new …
• Troubleshoot Salesforce CPQ Opportunity and Quote sync issues
• Bundle configuration errors ‘does not belong to SObject Type’ or …
• Salesforce Revenue-Cloud-Consultant-Accredited-Professional Quiz 1 …

RASIC is an acronym used in project management to define the roles and responsibilities of each person who interacts with the project. Each letter represents a designated role in a task’s completion:

• R (Responsible): This is the task lead – the individual who is ultimately responsible for getting the job done. There should only be one person responsible.
• A (Accountable): This is the person, or people, who will approve or deny the task once it’s complete. The person responsible can also play this role, but it can also be a technical expert or stakeholder.
• S (Supporting): The individual(s) in this role actively work on the task and help the person responsible.
• I (Informed): The individual(s) in this role need to be informed of the task’s progress and any decisions being made. These are the people who need to know when the task is complete.
• C (Consulted): People in this role offer advice or guidance but do not actively work on the task. These are often subject matter experts who offer guidance or one-time technical reviews1.

References

• Defining Roles and Responsibilities on a Project (RASIC) - Nexight Group

In Salesforce Revenue Cloud, if a cash payment has been posted to the wrong account by mistake, the recommended steps to correct this are as follows:

• Allocate the Payment: If the payment has been allocated, the first step is to allocate the payment. This means assigning the payment to the specific invoice it was intended for.
• Create a Refund: Once the payment has been allocated, the next step is to create a refund. This will effectively reverse the payment that was made in error.
• Create a New Payment for Account B: After the refund has been created, a new payment can be made for the correct account (Account B in this case). This payment should be allocated to the correct invoice on Account B.

It’s important to note that these steps ensure that the payment records are accurate and reflect the correct allocation of funds. This is crucial for accurate financial reporting and for maintaining the integrity of the account’s payment history.

References:

• Use Payments to Correct Errors on Posted Refunds - Salesforce
• Make a Payment on an Invoice - Salesforce
• Payments and Credits - Salesforce

Multi Dimensional Quoting (MDQ) is a pricing functionality in Salesforce CPQ that allows you to break a long subscription into smaller segments, such as months, quarters, or years, and apply different quantities, discounts, or uplifts to each segment. This way, you can offer flexible and customized pricing to your customers based on their needs and preferences. For example, if you sell boxes based on size, you can use MDQ to create a quote with different prices for different dimensions of the boxes, such as length, width, and height. You can also adjust the prices for each dimension based on the duration of the subscription, such as offering a lower price for the first year and a higher price for the second year. MDQ helps you to create complex and dynamic quotes with ease and accuracy, and increase customer satisfaction and loyalty. References:

• Create a Multidimensional Quote
• Revenue Management Platform & CPQ Solution
• Explain Multi Dimensional Quoting (Price Dimension) in Salesforce CPQ

 The ‘safe harbor’ slide at the beginning of every Salesforce presentation is a legal disclaimer that informs the audience that the presentation may contain forward-looking statements about the company’s future products, features, capabilities, performance, and financial results. These statements are based on the company’s current expectations, assumptions, and projections, and are subject to risks, uncertainties, and changes that may cause the actual results to differ materially from the statements. Therefore, the audience should not rely on these statements as guarantees or promises of future performance or availability, and should make their own independent decisions based on the current and available capabilities of the company. The ‘safe harbor’ slide also directs the audience to the company’s website, where they can find more information about the factors that may affect the forward-looking statements, as well as the company’s most recent financial reports and filings. 12

References:

• Salesforce - Safe Harbor
• Salesforce Announces Record Fourth Quarter and Full Year Fiscal 2022 Results - Salesforce Earnings

 Salesforce Revenue Cloud’s CPQ (Configure, Price, Quote) solution allows for the creation of price rules that can be used to perform calculations on quote lines. In this scenario, the CPQ admin has created three separate price rules, each using a summary variable to add the net total for quote lines belonging to a particular product family. While this solution works, it may not be the most optimal from a performance standpoint.

Option D suggests using a single price rule with three price actions. This would be more efficient because it reduces the number of price rules that need to be evaluated. Each price rule evaluation can consume system resources and potentially slow down the quote calculation process. By consolidating the three price rules into a single one with multiple actions, the system only needs to evaluate one rule, which can improve performance.

It’s important to note that summary variables in Salesforce CPQ allow you to perform a math function on the collected values of a number field on the quote line, product option, subscription, or asset1. You can also create filters so that the summary variable evaluates only fields on records that match the filter values1. This functionality would still be available with a single price rule with multiple actions.

References

• Summary Variable Fields - Salesforce
• Revenue Management Platform & CPQ Solution - Salesforce.com US
• Quote Line Groups - Salesforce

To design a multi-leveled approval matrix for controlling discounts on quotes, Universal Containers should consider the following:

• Identify backup approvers in case the primary approver is out of the office. This will ensure that the approval process is not delayed or stalled due to the unavailability of the primary approver. Backup approvers can be assigned using the Delegated Approver feature in Salesforce, which allows users to delegate their approval authority to another user for a specific period of time. 1
• Define the discount threshold or limit allowed for the sales reps. This will help to enforce the pricing policies and prevent excessive or unauthorized discounts. The discount threshold or limit can be defined using the Approval Thresholds feature in Salesforce CPQ, which allows setting up different approval rules based on the discount percentage, amount, or margin. 2
• Document the discount approval levels for each approver. This will help to clarify the roles and responsibilities of each approver and the criteria for approving or rejecting a quote. The discount approval levels can be documented using the Approval Processes feature in Salesforce, which allows creating a sequence of steps and actions that an approval request must go through. 3

References:

• Approval Thresholds
• Approval Processes
• Delegated Approver

In Salesforce CPQ, the Order Management plugin functionality provides flexibility in customizing the default package behavior, including the ability to set the activation date for orders. This feature allows for greater control over the order management process, enabling organizations to align the activation dates of their orders with their specific business requirements. By overriding the default behavior, businesses can ensure that the activation dates are set in a manner that is consistent with their operational workflows, contractual obligations, or customer agreements. This capability is part of Salesforce CPQ's broader set of features designed to provide customizable solutions to complex quoting and order management challenges​​.

QUESITON NO:51

Our customer is headquartered in the US but has operations in Germany. The Germanoperation has CPQ installed in their own EU instance of salesforce. Which service regionshould be defined for the Europeans instance of CPQ in order to optimize calculationperformance?

A. North America

B. japan

C. Europe

D. Australia

E. Server region has no performance impact

Answer: E

 Incorrect future invoicing for an amended order product might be caused by the following scenarios:

A. Not contracting the Amendment Order: If the amendment order is not contracted, the changes made in the amendment order will not be reflected in the future invoices. This is because the contract is the legal agreement that specifies the terms of the sale, including the products, quantities, and prices. If the amendment order is not contracted, the original terms of the sale remain in effect, which may result in incorrect future invoicing1.

B. Having a subscription on the Contract be linked to an Order Product with one or more unpaid invoice lines: If there are unpaid invoice lines linked to the order product, it may cause discrepancies in the future invoices. This is because the unpaid invoice lines may still be pending for payment, and if they are not resolved before the amendment order is contracted, the future invoices may not accurately reflect the changes made in the amendment order2.

C. Having a subscription on the Contract be linked to an Order Product with one or more invoice lines in draft: If there are invoice lines in draft status linked to the order product, it may cause inaccuracies in the future invoices. This is because the draft invoice lines have not yet been finalized and may still be subject to changes. If these changes are not finalized before the amendment order is contracted, the future invoices may not accurately reflect the changes made in the amendment order2.

References: Salesforce Revenue Cloud documents12

For a Revenue Cloud project where a product's taxability depends on a custom field that holds industry information, the appropriate solution is to use automation to set the Tax Rule based on the value of the custom field. This approach allows for dynamic application of tax rules to products based on industry-specific requirements, ensuring that the correct tax treatment is applied during the quoting and invoicing processes. Automation could involve using Process Builder, Flow, or Apex to update the tax rule assignments on products or quote lines based on the specified industry criteria. This ensures that products are taxed correctly according to the industry-specific regulations captured in the custom field.

The steps that an implementation team should take to integrate Revenue Cloud with another system are:

• B. Complete a source to target mapping of the fields that will integrate between systems: This step involves defining how data fields in Revenue Cloud correspond to data fields in the external system. It is crucial for ensuring accurate data flow and integration functionality between the systems.
• D. Design an architecture view of how data integrates and flows between systems: This involves creating a detailed architectural blueprint that outlines how data will be transferred and managed between Revenue Cloud and the external system. It helps in identifying potential integration challenges and ensuring that the integration supports the business processes effectively.

These steps are based on best practices in systems integration, focusing on data consistency and integrity, along with a structured approach to designing integration flows.

Customer Asset LifeCycle Management (CALM) is a feature of Salesforce Revenue Cloud that enables businesses to manage the entire lifecycle of their customer assets, from creation to renewal to termination. Customer assets are the goods and services that customers have purchased or subscribed to, and they can be tracked and updated on a single platform. CALM provides an aggregated view of the current customer assets on a contract, as well as their history, status, and future changes. CALM also allows businesses to automate the creation and activation of orders, amendments, and renewals based on the customer asset data. With CALM, businesses can gain visibility and control over their revenue streams, optimize their customer relationships, and reduce manual errors and inefficiencies. References:

These are three features that are not natively supported by Salesforce Revenue Cloud, but can be added by using an AppExchange Solution.

• Contract Redlining: This is the process of comparing and editing different versions of a contract document, usually with track changes and comments. This can help to negotiate and finalize the terms and conditions of a contract with customers or partners. 1
• Electronic Signature: This is the digital equivalent of a handwritten signature, which can be used to sign and validate a contract document electronically. This can help to speed up the contract approval process and reduce paper usage. 2
• Attachments: This is the ability to add additional files or documents to a contract document, such as supporting evidence, product specifications, or legal disclosures. This can help to provide more information and clarity to the contract parties. 3

References:

• 1: This article explains the benefits and challenges of contract redlining and how to use an AppExchange Solution to enable it in Salesforce.
• 2: This article explains the benefits and best practices of electronic signature and how to use an AppExchange Solution to integrate it with Salesforce.
• 3: This article explains how to use an AppExchange Solution to add attachments to a contract document in Salesforce.

To improve the performance of Salesforce CPQ, enabling sales reps to quickly generate and send quotes, an admin can undertake the following steps:

• C. Ensure Salesforce CPQ is upgraded to the latest release: Keeping the CPQ software up to date ensures that users benefit from the latest performance enhancements and bug fixes, which can significantly improve the overall efficiency of the system.
• D. Reuse referenced fields across the UI and rules: By reusing fields and minimizing the number of unique calculations or data fetch operations, system load is reduced, which can improve response times and overall performance.
• E. Rules that have a narrower evaluation scope will lead to better performance: Configuring rules to operate within a narrower scope means that fewer calculations are necessary during each transaction, which speeds up the quote generation process.

These steps are aligned with best practices in system optimization, focusing on maintaining up-to-date software, efficient use of system resources, and strategic rule configuration to enhance performance.

 A Salesforce CPQ implementation can suffer from poor performance due to a large number of active price rules supporting complex pricing requirements. To improve performance in this area, a Revenue Cloud Consultant can consider the following tactics:

• Implement lookup price rules where applicable (Option B): Lookup price rules in Salesforce CPQ allow for the mapping of data points on a quote line to data in a custom object, finding a matching record with the same values, and retrieving an associated field value from the matched record1. This can help reduce the number of price rules needed, thereby improving performance1.
• Implement Quote Calculator Plugin where possible to replace price rules (Option C): The Quote Calculator Plugin in Salesforce CPQ allows for the addition of extra functionality to the quote line editor with custom JavaScript code2. This can change how calculations are performed and manage page-level security such as field visibility2. By replacing some price rules with functionalities in the Quote Calculator Plugin, the number of price rules can be reduced, leading to improved performance2.

References:

• Salesforce CPQ Lookup Price Rules
• Salesforce CPQ Quote Calculator Plugin

Salesforce Revenue Cloud allows businesses to automate key processes related to recurring revenue models1. The ‘Renewal Forecasted’ field should be checked as early as possible to allow for accurate forecasting and planning. This helps businesses anticipate future revenue and make informed decisions about resource allocation and strategy. On the other hand, the ‘Renewal Quoted’ field should be checked closer to the Contract End Date. This is because the quote for renewal is typically generated and sent to the customer near the end of the contract term, allowing for any changes in pricing, terms, or services to be included21. References

• Revenue Cycle Management Software by Revenue Cloud - Salesforce
• Salesforce Introduces Revenue Cloud to Help Businesses Accelerate Revenue Growth Across Any Channel - Salesforce Sales
• Manage Contracts and Renewals Unit | Salesforce Trailhead
• A Guide to Recurring Revenue Enablement with Salesforce

The Large Quote Experience is a feature of Salesforce Revenue Cloud that allows businesses to handle quotes with a large number of quote line items more efficiently and avoid platform governor limit issues. The Large Quote Experience optimizes the performance of the Quote Line Editor and the Quote Calculator by using asynchronous processing, caching, and pagination. By enabling the Large Quote Experience, businesses can improve the user experience and reduce the risk of hitting CPU time, heap size, or SOQL query limits when saving or calculating large quotes. The Large Quote Experience can be enabled by setting the CPQ Package setting for “Large Quote Experience” to True. The Large Quote Experience also requires the CPQ Package setting for “Quote Batch Size” to be set to a value between 50 and 200, which determines the number of quote line items processed in each batch. The optimal value for this setting depends on the complexity and configuration of the quote line items

In Salesforce Revenue Cloud, the “Billing Day of Month” field can affect whether an invoice line is generated for an order product1. The system evaluates several fields to calculate an order product’s next billing date1. If the order product is billed in advance, Salesforce evaluates the order’s billing day of month to choose the nearest date on or before the order product’s start date1. If the order product is billed in arrears, Salesforce evaluates the order’s billing day of month to choose the nearest date after the order product’s start date1. Therefore, if the “Billing Day of Month” does not match with the next billing date of the order product, it might prevent the generation of an invoice line1. References

• Understanding Next Billing Date - Salesforce

Having the customer's Executive sponsors participate in the kickoff of a Revenue Cloud implementation is crucial for several reasons:

• A. To endorse project plan and timelines of the transformation efforts: Executive sponsorship is essential for endorsing and supporting the project plan and timelines. Their backing ensures that the project aligns with broader organizational goals and gets the necessary resources and attention.
• C. To assure project objectives are being met: Executive sponsors help in assuring that the project objectives align with the business’s strategic goals. Their presence in the kickoff meeting reinforces the importance of these objectives and ensures they are clearly communicated and understood by all stakeholders.
• E. To provide finality in escalations paths: Involving executive sponsors in the kickoff provides a clear escalation path for addressing issues that might arise during the implementation. This setup helps in resolving conflicts or challenges swiftly, ensuring the project stays on track.

Executive involvement from the beginning underscores the strategic importance of the project, facilitates alignment on expectations and resources, and establishes a clear governance structure.