Cert++
  1. Home
  3. Revenue Cloud Consultant

Revenue Cloud Consultant

Checklist progressProgress

0/242Learned

Revenue Cloud Consultant Study Checklist
  • Platform Administrator
  • Platform App Builder
  • Platform Foundations
  • Platform Developer
  • Platform Administrator II
  • Agentforce Sales Consultant
  • Agentforce Service Consultant
  • Platform Data Architect
  • Platform Development Lifecycle and Deployment Architect
  • Platform Identity and Access Management Architect
  • Platform Integration Architect
  • Platform Sharing and Visibility Architect
  • Heroku Architect
  • B2C Solution Architect
  • Experience Cloud Consultant
  • Agentforce Field Service and Operations Consultant
  • Agentforce Nonprofit Consultant
  • Data 360 Consultant
  • Omnistudio Consultant
  • CRM Analytics and Einstein Discovery Consultant
  • Platform User Experience Designer
  • Platform Strategy Designer
  • B2C Commerce Developer
  • JavaScript Developer
  • Omnistudio Developer
  • Platform Developer II
  • Marketing Cloud Engagement Administrator
  • Marketing Cloud Engagement Specialist
  • Marketing Cloud Engagement Consultant
  • Marketing Cloud Account Engagement Specialist
  • Marketing Cloud Next Consultant
  • Agentforce Sales Foundations
  • Business Analyst
  • Marketing Cloud Engagement Developer
  • Marketing Cloud Engagement Foundations
  • Agentforce Specialist
  • Agentforce Life Sciences Consultant
  • B2B Commerce Administrator AP
  • B2B Commerce Developer AP
  • Agentforce Communications AP
  • Agentforce Consumer Goods AP
  • Agentforce Financial Services AP
  • Agentforce Health AP
  • Agentforce Manufacturing AP
  • Public Sector Solutions AP
  • Revenue Cloud Consultant
  • MuleSoft Integration Foundations
  • MuleSoft Developer
  • MuleSoft Developer II
  • MuleSoft Platform Integration Architect
  • MuleSoft Platform Architect
  • Tableau Desktop Foundations
  • Tableau Data Analyst
  • Tableau Consultant
  • Tableau Server Administrator
  • Tableau Next Consultant
  • Tableau Architect
  • Slack Administrator
  • Slack Consultant
  • Slack Developer

Checklist progressProgress

0/242Learned

  • Revenue Management licenses and functional area availability
  • Permission set licenses versus permission sets for feature access
  • Profiles versus permission sets for Revenue Management users
  • Design-time versus run-time permission sets by implementation persona
  • Transaction permission sets for sales reps and operations reps
  • Revenue Management setup sequence and feature-gated permission sets
  • Extending standard permission sets with custom, muting, and group assignments
  • Revenue Management Lightning components on quote and order record pages
  • Revenue Management invocable actions in flows and integrations
  • Revenue Management components and the shared product catalog
  • Role of Context Service and context definitions in Revenue Management
  • Predefined Revenue Management context definitions and the processes they serve
  • Extending versus cloning context definitions to add custom fields
  • Decision tables versus expression sets in Business Rules Engine
  • Revenue Management features that run on Business Rules Engine
  • Omniscripts versus Flexcards for guided processes and contextual data display
  • Integration Procedures versus Data Mappers for reading and writing data
  • Omnistudio Document Generation for quote and contract documents
  • API-first headless architecture for multichannel selling
  • Choosing Revenue Management business APIs by lifecycle stage
  • Declarative configuration versus custom development and API extension
  • Native reports and dynamic dashboards for context-aware revenue KPIs
  • Revenue Management Intelligence analytics apps by functional area and persona
  • Lightning reports versus CRM Analytics versus Tableau Next for revenue KPIs
  • Product-to-cash object chain from quote to invoice
  • Catalog, category and product hierarchy objects
  • Bundle structure objects in the product catalog
  • Attribute definitions, attribute categories and product classifications
  • Product selling models and their link to price book entries
  • Salesforce Pricing adjustment, cost and derived pricing objects
  • Quote, quote line item and quote line group structure
  • Order, order item and order action records created from a quote
  • Bundle line relationships across quotes, orders and assets
  • Runtime attribute values on quote, order and asset records
  • Asset lifecycle tracking objects
  • Transaction Management Contract versus Salesforce Contracts data models
  • Billing schedule to invoice object chain
  • Credit memo, debit memo and payment application objects
  • Usage resource, grant and rate card objects for consumption-based products
  • Dynamic Revenue Orchestrator design-time versus fulfillment objects

Plan implementation readiness, including required licenses, permission sets, and prerequisite feature toggles

0/7

  • Growth, Advanced and Billing license fit for required capabilities
  • Billing feature availability under the Advanced and Billing licenses
  • Design-time versus run-time permission set licenses
  • Recommended feature permission sets by job role
  • Prerequisite feature toggles for Agentforce Revenue Management features
  • Salesforce Go initial setup and feature enablement
  • Preconfiguration sequence before Agentforce Revenue Management setup

Assign roles and responsibilities to stakeholders for cross-product project execution

0/12

Team ownership across the product-to-cash lifecycle

Learn this concept
Unseen

Product catalog admin versus product designer responsibilities

Learn this concept
Unseen

Salesforce Pricing and Rate Management persona responsibilities

Learn this concept
Unseen

Transaction Management personas for quoting and order capture

Learn this concept
Unseen

Salesforce Contracts personas and their responsibilities

Learn this concept
Unseen

Dynamic Revenue Orchestrator admin, fulfillment designer and operator roles

Learn this concept
Unseen

Invoice Management personas and their responsibilities

Learn this concept
Unseen

Internal experts and partner implementers on the implementation team

Learn this concept
Unseen

Administrator versus developer skill sets on the implementation team

Learn this concept
Unseen

Executive sponsor, steering committee and working group roles

Learn this concept
Unseen

RACI matrices for implementation responsibilities

Learn this concept
Unseen

Aligning executives, technical teams and business users on the solution

Learn this concept
Unseen

Develop an Agentforce Revenue Management scope of work and project plan

0/10

  • Requirements discovery for current and future state
  • Product-to-cash discovery questions by functional area
  • Business case built on strategic priorities and capability fit
  • Staged implementation versus full-suite scope
  • Out-of-the-box fit versus customization in the scope of work
  • Data migration and integration scope assessment
  • Scope of work boundaries, deliverables and documented decisions
  • Feature implementation sequence and interdependencies
  • Project timeline and milestone planning
  • Project risk identification and mitigation planning

Drive implementation through build, test, deployment, and adoption

0/13

  • Sandbox and org strategy for build and testing
  • User acceptance testing placement and go/no-go purpose
  • Business analyst ownership of UAT scripts, testers and sign-off
  • Promoting configuration from sandbox to production
  • Rollout approach selection for go-live
  • Data validation gate and curated quote pack for go-live
  • Handling in-flight quotes and orders at cutover
  • Go-live window, rollback criteria and hypercare planning
  • Implementation communication plan for build and cutover
  • Change management principles for user adoption
  • Stakeholder impact and change management priority by team
  • Training and enablement approach by company segment
  • Measuring and sustaining adoption after go-live
  • Role of Product Catalog Management across Agentforce Revenue Management
  • Core Product Catalog Management objects and relationships
  • Catalogs as top-level containers and Sales versus Service Process types
  • Commercial versus technical catalogs and product record types
  • Product classifications and attribute inheritance
  • Product variants versus attribute-configured single products
  • Catalog design sequence and build dependencies
  • Product Discovery browsing experience and product recommendations
  • Catalog effective start and end dates
  • Default catalog and catalog switching on the product list page
  • Category and subcategory hierarchy design within a catalog
  • Dynamic attributes, attribute picklists and attribute categories
  • Turning on and building product variants
  • Simple products versus static and configurable bundles
  • Bundle hierarchy with product component groups and nested bundles
  • Local cardinality versus group cardinality in bundles
  • Overriding component attributes and settings inside a bundle
  • Product selling models and selling model options
  • Product and category qualification and disqualification rules
  • SOQL, indexed and product field search options by catalog size
  • Configuring and rebuilding the product search index
  • Guided product selection versus faceted search in Product Discovery
  • Deep cloning products with related catalog records
  • Product catalog cache behavior and manual refresh options
  • Catalog access by persona: permission sets and record sharing
  • Enabling Product Configurator and its permission sets
  • Launching the configurator and configuring simple products
  • Configuring bundle options, quantities and child attributes at run time
  • Saving and reusing product configurations
  • Instant Pricing in the run-time configurator
  • Product Validation toggle versus on-demand Validate
  • Cloning and customizing the Default Product Configurator Flow
  • Assigning configuration flows to products and product classifications
  • Business Rules Engine versus Constraint Rules Engine for configuration logic
  • Transaction type and the rules engine used at configuration time
  • Configuration rule scope: product, bundle and transaction
  • Configuration rule actions that add, require, exclude or validate products
  • Configuration rule actions that hide, disable or set default values
  • Configuration rule sequence, status and duration
  • Configuration rule failures after product catalog changes
  • CML types, variables and relationships for modeling product structure
  • CML rules for requiring, excluding and preferring components
  • CML logical constraints and operators
  • Configuration logs for troubleshooting constraint models
  • Third-party configurator and headless configurator APIs
  • Context definitions, pricing procedures, and decision tables in the pricing flow
  • Pricing recipes and decision table setup
  • Design-time versus run-time pricing permissions
  • Pricing procedure prerequisites and creation settings
  • Cloning the default pricing procedure versus building a custom procedure
  • Transaction pricing procedure versus product discovery pricing procedure
  • Pricing Setting element and context tag mapping
  • Volume Discount versus Tier Discount elements
  • Attribute-based pricing versus the Price Adjustment Matrix
  • Bundle-based pricing versus aggregate pricing for grouped lines
  • Formula-based pricing and list operations for custom calculations
  • Quote header adjustments with Discount Distribution Service versus Manual Discount
  • Proration and Subscription elements for mid-cycle changes
  • Flow control and price compliance elements
  • Simulating and activating a pricing procedure
  • Price waterfall configuration and visibility
  • Pricing procedures by sales transaction type
  • Procedure plans for sequencing multiple pricing procedures
  • Derived pricing from another product, asset, or quote value
  • Contract-based pricing for negotiated agreements
  • Custom field pricing with context extension and Advanced Detail Line Pricing
  • Apex hooks versus declarative pricing elements
  • Pricing actions for calculating prices on any object
  • Diagnosing stale or inaccurate prices on quotes
  • Quote creation entry points and required permissions
  • Adding catalog products to quotes with Product Discovery
  • Quote document generation for customer-ready proposals
  • Revenue Quote Management agent subagents for quoting requests
  • Revenue Quote Management agent setup and licensing
  • Agent-driven initial, amendment and renewal quotes
  • Agent quoting limits on currency, line volume and channel access
  • Salesforce Contracts licenses, permission sets and enablement
  • Contract pricing and asset objects in the contract data model
  • Contract types, contract record types and contract type configs
  • Default contract lifecycle stages from Draft to Activated
  • Contract state model objects and allowed transitions
  • New Contract button versus standard Create Contract button on quotes and orders
  • Context Service mappings for Create Contract and Update Contracts actions
  • Record-triggered flow automation of contract creation from quotes and orders
  • Application usage assignment on Agentforce Revenue Management contracts
  • Capturing negotiated quote line pricing as contract item prices
  • Contract Pricing Schedule component on contract record pages
  • Line item sequencing for tiered and volume contractual discounts
  • Contract document templates and clause library
  • Microsoft 365 integration for contract collaboration and redlining
  • DocuSign e-signature integration for contract execution
  • Obligation management for post-execution contract commitments
  • Custom dynamic contract actions with Apex or OmniScript
  • Contracts AI for clause drafting and legacy contract digitization
  • Contracts Analytics dashboards versus the Contracts Console workspace
  • Order-specific objects in the order data model
  • Quote-to-order versus direct order capture
  • Converting an accepted quote into orders
  • Application usage assignment and permissions for directly created orders
  • Draft order editing versus activated order behavior
  • Submitting activated orders to Dynamic Revenue Orchestrator
  • Commercial versus technical products in order decomposition
  • Product fulfillment decomposition rule configuration
  • Orchestration plans with swimlanes and task dependencies
  • Fulfillment step types for orchestration plans
  • Fulfillment step definition scope and run-as user
  • Fulfillment scenarios for adding step groups to plans
  • SLA durations and jeopardy thresholds for fulfillment steps
  • Order fallout handling for failed fulfillment steps
  • Lifecycle requests from quote to order, fulfillment and billing
  • When to amend, renew or cancel an asset
  • Asset Actions versus Asset State Periods
  • Reviewing assets in the Managed Asset Viewer and asset record page
  • Permission sets for viewing, amending, renewing and canceling assets
  • Refresh timing of asset current-value fields
  • LIFO pricing for negative-quantity asset changes
  • Assetization through a record-triggered order flow
  • Adding the Managed Asset Viewer to account and contract pages
  • Default amend, renew and cancel flow in Revenue Settings
  • Adding assets to amendment and renewal quotes and orders
  • Quantity amendments for upsells and downsells
  • Swap, upgrade and downgrade amendments
  • Field amendments versus price amendments
  • Amending subscription start dates and termed end dates
  • Future-dated versus backdated asset changes
  • Automatic renewal versus overriding the renewal term
  • Asset renewal automation flow templates
  • Asset cancellation quotes and orders
  • Processing an asset transfer between accounts
  • Asset transfer eligibility restrictions
  • Asset Contract Relationships for contract-governed assets
  • Applying contract pricing to amendments and renewals
  • Price book and currency on amendment and renewal transactions
  • Rates, grants and proration on usage-based assets
  • Rolling back the last transaction on an asset
  • Order-to-invoice billing workflow in Agentforce Revenue Management
  • Billing policies, billing treatments and treatment selection
  • Advance versus arrears billing type and billing frequency
  • Billing profiles for customer-level invoicing preferences
  • Usage, milestone, ramp and amendment billing scenarios
  • Draft versus posted invoices and invoice tax calculation
  • Sequential invoice numbering with sequence policies
  • Credit memos, debit memos and write-offs for invoice corrections
  • Billing Central Dashboard, Billing Operations Console and invoice aging
  • BillingContext context definition and context mappings
  • Org-wide Billing Settings defaults for invoice generation
  • Invoice batch runs versus on-demand generation versus the Invoice Ingestion API
  • Invoice scheduler configuration and run frequency
  • Invoice date, target date and billing period count in invoice runs
  • On-demand invoice generation from account and order records
  • Invoice previews versus Billing Forecast
  • Invoice grouping for consolidated invoices
  • Invoice PDF document generation setup and generation modes
  • Invoice document template selection and customization
  • Invoice email delivery configuration
  • Billing Settings for negative invoice lines and credit application
  • Voiding versus deleting invoices for billing corrections
  • Suspending and resuming billing for accounts or billing schedule groups
  • Synchronous automation on Billing objects during invoice runs
  • Troubleshooting and recovering failed invoice batch runs

Prepare for the Exam

Play Today's Certle

Study Community

Ask questions and get the latest info from other Revenue Cloud Consultant studiers.

Go to Discord
  1. Revenue Cloud Consultant Checklist
  3. Implementation Readiness

RACI matrices for implementation responsibilities

Explainer

Learn More

Practice Question

Studying for this exam?

This is one of 242 concepts on the Salesforce Revenue Cloud Consultant exam.

Looking for practice exams? Click below to try one!

Keep going

Next conceptAligning executives, technical teams and business users on the solution

Checklist progress

0/242 (0%)

0 of 242 concepts learned

Tip: You can filter concepts by status.

Prepare for the Exam

Play Today's Certle

Study Community

Ask questions and get the latest info from other Revenue Cloud Consultant studiers.

Go to Discord
Close
  1. Revenue Cloud Consultant Checklist
  3. Implementation Readiness
RACI matrices for implementation responsibilities

Explainer

Learn More

Practice Question

Studying for this exam?

This is one of 242 concepts on the Salesforce Revenue Cloud Consultant exam.

Looking for practice exams? Click below to try one!

Keep going

Next conceptAligning executives, technical teams and business users on the solution

Explainer

A RACI matrix is a table that lists project tasks or decisions against the people or roles on a project. It marks each role as Responsible, Accountable, Consulted, or Informed for each task. An Agentforce Revenue Management implementation spans many teams and personas, from product catalog and pricing to contracts, fulfillment, and billing, so writing down who owns what keeps unstated assumptions from causing misunderstandings, gaps, and delays.
Core information
  • RACI stands for responsible, accountable, consulted, and informed. A RACI chart is a matrix of a project's activities or decision-making authorities, set against all the people or roles involved. A letter in each cell shows how that role relates to that task.
More details and nuances
  • Responsible and Accountable are each one person per task, while Consulted and Informed can be several people.

Explainer

A RACI matrix is a table that lists project tasks or decisions against the people or roles on a project. It marks each role as Responsible, Accountable, Consulted, or Informed for each task. An Agentforce Revenue Management implementation spans many teams and personas, from product catalog and pricing to contracts, fulfillment, and billing, so writing down who owns what keeps unstated assumptions from causing misunderstandings, gaps, and delays.
Core information
  • RACI stands for responsible, accountable, consulted, and informed. A RACI chart is a matrix of a project's activities or decision-making authorities, set against all the people or roles involved. A letter in each cell shows how that role relates to that task.
More details and nuances
  • Responsible and Accountable are each one person per task, while Consulted and Informed can be several people.