Revenue-Cloud-Consultant-Accredited-Professional 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 theHold Billing field toYes 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 holdcan 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 twomonths, 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

An invoice scheduler is a feature of Salesforce Revenue Cloud that allows you to automatethe creation of invoices based on predefined criteria and schedules. An invoice scheduler uses an invoice run to evaluate whether and when an order product gets invoiced. You can set up an invoice scheduler to run daily, weekly, monthly, or once, and specify the target date and time, the invoice date, and the invoice batches to include. You can also choose to automatically post the generated invoices or review them in draft status before posting. An invoice scheduler is the best option to fulfill the userstory, as it can generate invoices in draft status the same day of every month without requiring any manual intervention or custom code. 12

Triggers and apex are not the best option, as they require writing and maintaining custom code, which can be complex and error-prone. They also donot provide the flexibility and control of an invoice scheduler, as they can only check the bill now checkbox after the order status is changed to “Activated”, which may not match the desired invoicing schedule or criteria. 3

Workflow rules are also not the best option, as they have similar limitations as triggers and apex. They can only check the bill now checkbox after the order status is changed to “Activated”, and they cannot specify the invoice date, time, or batches. Workflow rules also have some restrictions and considerations, such as the number of actions per rule, the order of execution, and theimpact on performance. 4

Setting up a payment scheduler is not relevant to the user story, as it is a feature of Salesforce Revenue Cloud that allows you to automate the collection of payments from customers based on predefined criteria and schedules. A payment scheduler does not create invoices, but rather applies payments to existing invoices or payment allocations. [5]

Review Salesforce Status: The status.salesforce.com website provides real-time information about the status of Salesforce services, including maintenance windows and release schedules. By checking this site, you can find out when the new release will be available for sandboxes. This information will help you plan your testing activities.

Submit a Sandbox Refresh Request: If your sandbox is not automatically upgraded to the new release, you can request a sandbox refresh through Salesforce Support. This process will update your sandbox to the latest release, allowing you to test your implementation against the most current features and functionality.

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

INVEST is an acronym that stands for Independent, Negotiable, Valuable,Estimable, Small, and Testable12. It is a set of criteria used to assess the quality of a user story in Agile methodologies12. Here’s what each term means:

Independent: The user story should be self-contained, in a way that there is no inherent dependency on another user story12.

Negotiable: User stories, up until they are part of an iteration, can always be changed and rewritten12.

Valuable: A user story must deliver value to the end user12.

Estimable: You must always be able to estimate the size ofa user story12.

Small: User stories should not be so big as to become impossible to plan/task/prioritize with a certain level of certainty12.

Testable: The user story or its related description must provide the necessary information to make test development possible12. References: 12

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 forthe 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: C

When a customer indicates the need for customization to Salesforce CPQ due to a process in a legacy system, the first step in ensuring the requirement is accounted for in scoping is to ask follow-up questions to ensure the legacy process has a business justification. This is important because it helps to understand the business needs and requirements better, and ensures that the customization will add value to the business. It’s crucial to understand the ‘why’ behind the need for customization before proceeding with it. This approach helps in avoiding unnecessary customizations and ensures that the solution aligns with the business objectives. References: Salesforce Introduces Revenue Cloud, Starting with CPQ: 8 Most Common Reasons for Customization

According to the Salesforce Revenue Cloud CPQ documentation, users need to have the Create, Read, Edit, and Delete permissions on the Quote object in order to create and manage quotes. If users do not have the proper accessto the Quote object, they will encounter errors when trying to create quotes, even if the quotes are set as primary by default. This is because the primary quote field is a lookup field that references the Quote object, and users need to have access to the referenced object in order to populate the lookup field. Therefore, the most likely cause ofthe issue is that the users did not have the proper access to the Quote object in the production environment, and this was not detected in the sandbox environment because the users had different permissions or profiles there. References:

https://help.salesforce.com/s/articleView?id=000316738 &language=en_US&type=1

https://help.salesforce.com/s/articleView?id=000381216 &language=no&type=1

In Salesforce CPQ, ensuring that users have the proper access to the Quote object is crucialfor the smooth creation and management of quotes. The issue reported by users in the production environment, where errors occurred upon trying to create quotes for the first time, likely stemmed from insufficient permissions on the Quote object. In CPQ, setting a new quote as "primary" at the time of creation is a common practice to streamline the quoting process. However, if users lack the necessary permissions on the Quote object, they would encounter errors when attempting to create or modify quotes. It's important to note that in Salesforce CPQ, orders must be created from a primary quote, and once an order is created from a primary quote, the quote cannot be edited​​. This indicates that the underlying issue is related to access permissions on the Quote object, rather than post-installation scripts, access to the Opportunity Product object, or access to the Quote Line object.

Scoping a Revenue Cloud project involves understanding the business needs, defining the project goals, and planning the implementation strategy12. The teams that should be involved in this process are those that have a direct stake in the project’s outcome and can provide valuable input into the project’s requirements12. These teams typically include:

Accounting and Finance: This team can provide insights into the financial processes that theRevenue Cloud project will support, such as billing, revenue recognition, and financial reporting12.

Sales Operations: This team can provide insights into the sales processes that the Revenue Cloud project will support, such as quote-to-cash, contract management, and sales forecasting12.

Information Technology: This team can provide technical expertise and support for the implementation of the Revenue Cloud project, including system integration, data migration, and IT infrastructure12. References: 12

When encountering a Salesforce Sales Cloud implementation with multiple triggers, workflow, and flow processes applied to the Opportunity object, it is advisable to recommend consolidating these automations intoa single type. This approach is recommended to optimize performance and maintainability, reducing complexity and potential conflicts between different automation types. Consolidating automations into one trigger, process builder, or flow ensures a more streamlined and efficient execution of business logic, contributing to better system performance and easier troubleshooting and maintenance​​.

Reducing processing times during quote document generation in Salesforce CPQ can be achieved through various optimizations. One effective method is using compressed image formats for image files included in the quote document. This reduces the file size of the images,leading to faster loading and processing times when generating quote documents. While the specific reference to this practice is not directly available in the provided Salesforce Revenue Cloud documents, it isa widely recognized optimization technique in document generation processes to enhance performance and reduce loading times​​.

 During User Acceptance Testing (UAT), when an incident is submitted due to a discrepancy in the invoice total, the following information should be included in the description of the incident for aquick resolution:

BQuote number, order number, or invoice number: This information is crucial as it helps identify the specific transaction that has caused the issue1.

D. Steps to reproduce the issue: Providing a clear and detailed step-by-step process to reproduce the issue is essential. This allows the team to understand the exact scenario under which the issue occurs, making it easier to diagnose and resolve1.

E. Expected results: Clearly stating what the expected results should be provides a benchmark against which the actual results can be compared. This helps in understanding the deviation and the impact of the issue1.

References

Learn About User Acceptance Testing Unit | Salesforce Trailhead

User Acceptance Testing Strategies for Large Data Volume Scenarios | Salesforce Education

Resolve an Incident - Salesforce

Steps to Implement IncidentManagement in Your Salesforce Org

QUESTON NO:62

A Revenue Cloud customer has posted an invoice and now wants to add on more items from another order associated to that account. Without using invoice batches, how can this be accomplished?

A. Credit theinvoice, add the new order and run an invoice scheduler to pick all the

orders up.

B. use bill now on the new order and reparent the new invoice lines to the existing invoice

C. Cancel and Rebill the invoice,add the new Order and run an invoice scheduler to pick

all the order up.

D. Use bill now on the new Order and consolidate the invoices

Answer: A

In Salesforce Revenue Cloud, particularly within Salesforce Billing, when an invoice has already been posted and there's a need to add more items from anotherorder associated with that account, one effective approach is to use credit and debit notes. This method allows for adjustments to the invoice's balance while maintaining the availability of the original invoice and invoice line records for reference. This process can be particularly useful in scenarios where a mistake, such as an incorrect account address leading to an incorrect tax calculation, needs to be corrected after the invoice has already been posted​​.

To migrate legacy install base into Salesforce CPQ along with the contract, the Revenue Cloud Consultant needs to populate the Assets and Subscriptions objects. These objects store the information about the products and services that the customer has purchased and are associated with the contract. The Assets object tracks the physical products, such as hardware and software licenses, that have been delivered or activated for the customer. The Subscriptions object tracks the recurring products, such as software subscriptions or maintenance plans, that have a defined billing frequency and term. By populating these objects, the Revenue Cloud Consultant can preserve the history of the customer’s purchases and enable the features of Salesforce CPQ, such as renewals, amendments, and co-termination. References:

Migrate Legacy Data to Salesforce CPQ

[Assets]

[Subscriptions]

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.

 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 unpaidinvoice 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 linesmay still be pending for payment, and if they are not resolved before the amendment order is contracted, thefuture invoices may not accurately reflect the changes made in the amendment order2.

C. Having a subscription on the Contract be linked to an OrderProduct 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 besubject to changes. If these changes are not finalized before the amendment order is contracted, the future invoices may not accurately reflect thechanges made in the amendment order2.

Order Product: The status of the Order Product is updated when the corresponding Invoice Line is posted. The fields such as ‘InvoiceRun Processing Status’, ‘Next Billing Date’, ‘Next Charge Date’, and ‘Last Charge To Date’ are updated for the next period1.

Invoice Line: The Invoice Line objectis updated when an invoice is posted. This includes locking the Invoice Line from further changes and finalizing the agreement represented by the invoice2.

Invoice: The Invoice object itself is updated when an invoice is posted. This includes changing the status of the invoice from ‘Draft’ to ‘Posted’, which locks the invoice from further changes and makes it ready for revenue recognition reporting2.

It’s important to note that posting an invoice finalizes the agreement and prevents deletion of the invoice or any of its invoice lines. This ensures that your organization always has a record for legal and bookkeeping purposes2.

 To implement the user story of rewarding loyal customers with bulk discounts based on previously purchased quantities, the design of the solution should include the following components:

Contracts, Subscriptions and Assets should be populated with historical data. This is necessary to track the customer’s purchase history and determine the appropriate discount tier for each product or service. Contracts, Subscriptions and Assets are the core objects of Revenue Cloud that store the information about the customer’s agreements, recurring charges, and entitlements. By migrating the historical data from the legacy system to these objects, the customer can leverage the Revenue Cloud features such as renewal management, usage-based pricing, and revenue recognition. 123

Discount schedules with Cross Orders checked. This is the feature that enables the bulk discounts based on previously purchased quantities. A discount schedule is a set of discount tiers that apply to a product or a product option based on the quantity or amount ordered. By checking the Cross Orders option, the discount schedule will consider the quantities from all the orders associated with the same account, contract, or subscription. This way, the customer can reward their loyal customers with lower prices for higher volumes. 45

For a Revenue Cloud project where aproduct's taxability depends on a custom field that holds industry information, the appropriate solution is touse automation to set the Tax Rule based on the value of the custom field. This approach allows for dynamic application of tax rules to productsbased 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 thatthe 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.