Revenue-Cloud-Consultant-Accredited-Professional Salesforce Revenue Cloud Consultant Accredited Professional (SU24) Questions and Answers

Hold Billing is a feature of Salesforce Revenue Cloud that allows businesses to control when an order product is invoiced, based on certain criteria or events. By setting the Hold Billing field to Yes on an order product, the billing process is paused for that order product and all its usage summaries. This means that no invoice lines or invoice documents are generated for the order product until the hold is released. The hold can be released by setting the Hold Billing field to No or null, either manually or automatically through a workflow or trigger. When the hold is released, Salesforce Billing will create an invoice as soon as possible, and include all the invoice lines that were accumulated during the hold period. This ensures that the customer is billed for the full amount of the order product, regardless of the hold duration. For example, if an order product has a monthly billing frequency and a hold billing period of two months, the first invoice after the hold will include three invoice lines: one for the current month and two for the previous months when the hold was active. References: 

https://help.salesforce.com/s/articleView?id=sf.blng_hold_billing.htm &language=en_US&type=5

https://trailhead.salesforce.com/users/officialblaze/trailmixes/revenue-cloud-get-started-with-billing

In a Salesforce Revenue Cloud project, the role primarily responsible for project success is the Project Manager1. The Project Manager is responsible for planning, overseeing, and leading projects from ideation through to completion2. This includes managing resources, coordinating with different teams, and ensuring that the project is completed on time and within budget2.

When an escalation happens, the Project Manager is typically the one who steps in to resolve the issue. They work closely with all stakeholders, including the Solution Architect, Technical Architect, Customer Success Manager, and Developer, to ensure that the project stays on track and meets its objectives1.

References:

• What Does a Salesforce Project Manager Do? - Salesforce Ben
• Learn About the Salesforce Admin Role - Trailhead

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.

For User Acceptance Testing (UAT) to be efficient, it's crucial to have clear and agreed-upon acceptance criteria with the customer. This ensures that both parties have a mutual understanding of what constitutes a successful test outcome. Defining these criteria upfront helps streamline the testing process, as it focuses efforts on verifying that the system meets the business requirements and expectations. While the specific document reference for this answer isn't available in the provided Salesforce Revenue Cloud documents, this approach is a widely recognized best practice in UAT planning and execution in software development and implementation projects.

In Salesforce Revenue Cloud, if a cash payment has been posted to the wrong account by mistake, the appropriate steps to correct this would be to first unallocate the payment if it has been allocated. This means that the payment is no longer linked to any particular invoice or order1. Once the payment has been unallocated, a refund should be created for the incorrect payment1. After the refund has been processed, a new payment can then be created for the correct account (Account B in this case)1. This ensures that the payment is correctly associated with the right account and invoice1. References

• Salesforce Revenue-Cloud-Consultant-Accredited-Professional Quiz 1

When a Revenue Cloud customer needs to add more items from another order to a posted invoice without using invoice batches, the recommended approach is to "Cancel and Rebill" the invoice. This process involves rolling the invoice back to its state before the most recent billing cycle, allowing corrections or additions to be made to the invoice record. This action is applicable to both draft and posted invoices and is designed to address errors or changes needed on the invoice, such as adding new order items​​. This method ensures that all necessary adjustments are made while maintaining the integrity of the invoice's audit trail and data.

 Contracted Pricing is the object that stores the negotiated prices and discounts for each account and product combination. Contracted Pricing allows sales users to create new quotes with the same pricing terms that were agreed upon in previous contracts, without having to manually adjust the prices or discounts. Contracted Pricing also enables businesses to maintain pricing consistency and accuracy across different channels and systems. To use Contracted Pricing, legacy data from accounts, contracts, and quotes need to be loaded into the Contracted Pricing object, along with the relevant price book entries and product options. 12 References:

• Contracted Pricing - Salesforce
• Migrate Legacy Data to Contracted Pricing - Salesforce

In Salesforce Revenue Cloud, if price rules are not sufficient to accurately set the quote line list price for a project, the next functionality to consider would be a Quote Calculator Plugin (QCP)1. A QCP is a JavaScript snippet that you can use to perform complex calculations and manipulations on quote lines1. It provides a way to customize the calculation sequence that happens when a quote is calculated1. This can be particularly useful when there are additional calculation steps needed that are not addressed by standard price rules1. References

• Salesforce Exam Revenue-Cloud-Consultant-Accredited-Professional Questions and Answers - Update Feb 2024

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.

 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 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 …

Cross object formula fields are fields that reference data from related objects using lookup or master-detail relationships. They can be useful to display information from parent or child objects without creating custom code or workflows. However, using too many cross object formula fields in a Revenue Cloud project can pose some risks, such as:

• Formula field data is not always available during CPQ quote calculation. This means that the formula fields may not reflect the latest values from the related objects when the quote is being generated or updated. This can cause inaccurate pricing, discounts, or taxes. To avoid this, it is recommended to use CPQ fields or custom fields instead of cross object formula fields for quote calculation. 12
• They are computationally expensive. This means that the formula fields require more processing power and time to evaluate and display the data from the related objects. This can affect the performance and responsiveness of the application, especially if there are multiple formula fields on the same object or page layout. To avoid this, it is recommended to limit the number and complexity of cross object formula fields, and use filters or conditions to reduce the number of records that need to be evaluated. 34
• They can easily exceed limits if not carefully designed and tested. This means that the formula fields can cause errors or warnings if they exceed the maximum length, number, or level of relationships allowed by Salesforce. For example, a formula field can only reference up to 10 unique relationships and span up to five levels of relationships. If these limits are exceeded, the formula field will not save or display correctly. To avoid this, it is recommended to review the formula field limits and best practices, and test the formula fields in different scenarios and environments. 

References:

• 1: Lookup Price Rule query considerations with Salesforce CPQ [7]
• 2: Salesforce CPQ Quote Calculation Stages [8]
• 3: What Is a Cross-Object Formula? - Salesforce [9]
• 4: Tips for Reducing Formula Size and Complexity - Salesforce [10]
• 5: Formula Field Limits - Salesforce [11]

A Flow is a scalable way to set the legal entity on the order product and order product consumption schedule because it allows you to automate complex business logic without writing code. A Flow can be triggered when a record is created and run before the record is saved, which means that you can assign the legal entity to the order product and order product consumption schedule before they are inserted into the database. This way, you can ensure that the order product and order product consumption schedule have the correct legal entity for the billing, tax, and revenue recognition treatments that are applied to them. A Flow also gives you more flexibility and control over the logic and criteria for setting the legal entity, compared to a workflow or a custom setting. A Quote Calculator Plugin (QCP) is not a scalable way to set the legal entity on the order product and order product consumption schedule because it is a custom code solution that requires development and maintenance. A QCP also runs after the order product and order product consumption schedule are created, which means that you have to update the legal entity after the record is saved, which can cause data validation issues. A workflow or a custom setting are also not scalable ways to set the legal entity on the order product and order product consumption schedule because they have limitations and drawbacks, such as:

• A workflow can only run after the record is created and saved, which means that you have to update the legal entity after the record is saved, which can cause data validation issues.
• A workflow can only execute simple logic and actions, such as field updates, email alerts, tasks, and outbound messages. It cannot perform complex logic or actions, such as loops, conditions, variables, or invocations of other processes or services.
• A custom setting is a type of custom metadata that stores data that can be accessed by formulas, validation rules, flows, Apex, and the SOAP API. However, a custom setting is not a good way to store data that changes frequently or varies by user or profile, such as the legal entity. A custom setting also requires manual configuration and maintenance, which can be error-prone and time-consuming. References:
• Legal Entities
• Automation Guidelines for Orders and Order Products
• Flow Builder

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 a Salesforce CPQ scoping session, the first type of documentation that comes into play is the Business Process Mapping. This is because before diving into the specifics of products, bundles, order management, or quote documentation, it’s crucial to understand the client’s overall business processes. Business Process Mapping provides a visual representation of the client’s business processes, which can help identify inefficiencies, redundancies, and gaps in the current process. It also helps in understanding how the Salesforce CPQ solution can be best configured to align with and optimize these processes1. References: Salesforce CPQ documentation1.

 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

Cross-object formula fields are useful for accessing data from related objects, but they also have some drawbacks and risks, especially when used excessively in a revenue cloud project. Some of the risks are:

• They can easily exceed limits if not carefully designed and tested. Cross-object formula fields count against the total number of fields allowed per object, and they also consume more resources than regular fields. If the formula is too complex or references too many objects, it can cause performance issues, errors, or failures. For example, a formula can only reference up to 10 unique relationships, and a record can only trigger up to 16 levels of cross-object formula updates. 12
• Formula field data is not always available during CPQ quote calculation. CPQ quote calculation is a process that evaluates the pricing, discounts, taxes, and other factors of a quote. During this process, some cross-object formula fields may not have the latest data or may not be accessible at all, depending on the order of execution and the timing of the updates. This can lead to inaccurate or inconsistent results, or even prevent the quote from being calculated. 3
• They are computationally expensive. Cross-object formula fields require more processing power and time than regular fields, as they need to query and calculate data from multiple objects and relationships. This can affect the overall performance and responsiveness of the revenue cloud project, especially when there are many cross-object formula fields involved. Additionally, cross-object formula fields can trigger cascading updates and validations, which can further increase the computational load and complexity. 4

References:

• 1: What Is a Cross-Object Formula? - Salesforce
• 2: Formula Operators and Functions - Salesforce
• 3: Salesforce Real Dumps Practice Exam Questions by Dumpswarp
• 4: Create Cross-Object Formulas Unit | Salesforce Trailhead

These are three documents that can help a revenue cloud consultant gain a better understanding of the client’s business model, value proposition, pricing strategy, and approval process before engaging in a scoping session.

• A sample proposal the client provides to their customers: This document can help the consultant understand how the client presents their products and services to their customers, what kind of information they include, how they structure their pricing and discounts, and what terms and conditions they apply. This can help the consultant design a solution that meets the client’s needs and expectations, as well as aligns with their branding and messaging. 1
• Brochures that provided detail to the products and services the client offers: This document can help the consultant understand the features and benefits of the client’s products and services, how they differentiate themselves from their competitors, and what kind of value they deliver to their customers. This can help the consultant configure the product catalog, pricing rules, and quote templates that reflect the client’s offerings and value proposition. 2
• An approval matrix documentation that describe the approvals needed before a quote is sent to the customer: This document can help the consultant understand the client’s internal governance and compliance requirements, as well as the roles and responsibilities of the stakeholders involved in the quote-to-cash process. This can help the consultant set up the approval workflows, notifications, and permissions that ensure the accuracy and validity of the quotes and contracts. 3

References:

• 1: This article explains how to create a professional proposal for customers using Salesforce CPQ.
• 2: This article explains how to create and manage product catalogs and pricing in Salesforce Revenue Cloud.
• 3: This article explains how to create and manage approval processes in Salesforce Revenue Cloud.

The three design examples that will negatively impact the scale and performance of the Revenue Cloud implementation are:

A. Multiple automation types (trigger/workflows,flows) on a single object: Having multiple automation types on a single object can lead to complex and inefficient processes. This can slow down the system and negatively impact the performance and scalability of the Revenue Cloud implementation1.

B. External API calls within the pricing sequence: Making external API calls within the pricing sequence can introduce latency and potential points of failure. This can slow down the pricing process and negatively impact the performance and scalability of the Revenue Cloud implementation1.

C. Extensive use of quote line custom fields: Using a large number of custom fields can increase the complexity and size of the data model. This can slow down queries and negatively impact the performance and scalability of the Revenue Cloud implementation1.

References: 1

https://trailhead.salesforce.com/content/learn/modules/scalability-with-salesforce/understand-scalability-at-salesforce

Design examples that can negatively impact the scale and performance of the Revenue Cloud implementation include using multiple automation types on a single object, making external API calls within the pricing sequence, and extensively using custom fields on quote lines. Multiple automations on a single object can lead to complex logic processing and increased execution times, impacting overall system performance. External API calls within pricing sequences can introduce latency and potential points of failure, affecting the responsiveness and reliability of pricing calculations. Additionally, an excessive number of custom fields on quote lines can increase the data load and processing time during quote generation and manipulation, further degrading system performance. These design considerations are critical for maintaining optimal performance and scalability in Revenue Cloud implementations.

 In a Salesforce CPQ Scoping Session, the first topic of discussion is typically Business Process Mapping. This involves understanding the current business processes and identifying areas where Salesforce CPQ can provide improvements. It’s an essential step in the scoping process as it helps to define the project’s scope and identify potential challenges early on. The other topics like Quote Document and e-signature, Order Management, and Products and Bundles are also important but they usually come after the business processes have been mapped and understood.

References

• Get Started with Salesforce CPQ Unit | Salesforce Trailhead
• CPQ Scoping Questionaire? : r/salesforce - Reddit
• How To: Salesforce CPQ: Build a Bundle

 A project manager is the role that is primarily responsible for project success, especially when an escalation on a Revenue Cloud project happens. A project manager oversees the end-to-end delivery of a Salesforce project, ensuring that the project is delivered within scope, budget, and timeline. A project manager also coordinates the communication and collaboration among the project team, the customer, and other stakeholders, as well as manages the risks, issues, and changes that may arise during the project lifecycle. A project manager is the first point of contact for any escalation on a Revenue Cloud project, and is expected to resolve the escalation promptly and effectively, by applying the appropriate escalation management process and involving the relevant parties. A project manager also monitors and reports on the project progress, quality, and satisfaction, and ensures that the project meets the customer’s expectations and business objectives. 1234 References:

• 1: Your Guide to Salesforce Roles & Responsibilities
• 2: Salesforce Introduces Revenue Cloud to Help Businesses Accelerate Revenue Growth Across Any Channel
• 3: Marketing Cloud Consultant Job Description
• 4: What Is Salesforce Revenue Cloud?

In Salesforce Revenue Cloud, usage records are a key component of the usage-based pricing model. They track the consumption of a product or service over a predefined time period1.

The required fields on the usage record to load and rate the usage are:

• Start Date Time: This field represents the start of the usage period1.
• End Date Time: This field represents the end of the usage period1.
• Matching ID: Salesforce Billing uploads usage only to usage summaries with matching IDs1.
• Matching Attribute: Usages are rated against usage summaries where the Matching ID, Matching Attribute, and Unit of Measure fields all match1.
• Unit of Measure: This field represents the unit in which the usage is measured1.
• Quantity: This field represents the amount of usage1.

These fields are essential for accurately tracking and billing usage-based products or services. They allow Salesforce Revenue Cloud to calculate charges based on the actual consumption of a product or service, which can be more flexible and customer-friendly than flat-rate pricing2.

References

• Usage Summary and Usage Fields - Salesforce
• Usage-Based Products - Salesforce