Practice Free AP-223 CPQ and Billing Consultant Accredited Professional Exam Questions Answers With Explanation

Scenario:

A payment is posted on the wrong Account

It must be applied to an invoice on a different Account

Payment is already posted

Salesforce Billing rules:

A posted payment cannot be reparented

A payment allocated to an invoice cannot simply be moved

Correct process is:

? B — If allocated, create a refund, then create a new payment on the correct accountDetailed steps:

Reverse (refund) the incorrect payment

Create a new payment on the correct account

Allocate that payment to the correct invoice

This ensures:

Proper audit trail

Compliance with financial controls

Correct ledger entries

Why the other options are wrongOption

Why Incorrect

A. Allocate payment to Account B invoice

Not allowed: payment is tied to Account A.

C. Reparent payment to Account B

Posted payments cannot be reparented.

D. Cancel the payment

Cancelling alone does not reverse ledger impact; refund process is required.

Thus B is correct.

For multi-level discount approvals in CPQ:

A – Identify backup approvers: Required because Salesforce Approval Processes must account for out-of-office or unavailable approvers.

D – Define discount thresholds for sales reps: Mandatory so the system knows when to trigger approvals.

E – Document approval levels: Ensures clear governance and reduces ambiguity.

Incorrect options:

B printing approval matrices is not a Salesforce implementation requirement.

C contradicts the purpose of approval controls.

Thus the correct answers are A, D, E.

When dealing with large quotes, Salesforce CPQ may hit platform governor limits (CPU time, SOQL limits, etc.) during save and recalculation.

Salesforce CPQ provides the Large Quote Threshold setting, which instructs CPQ to switch to a more efficient calculation mode once the quote line count exceeds the threshold.

The Salesforce documentation states:

Large Quote Threshold should be set to a number below the volume that triggers governor limits during testing.

It is not set arbitrarily; it must be based on empirical volume testing results.

This avoids synchronous processing of too many quote lines and forces CPQ to optimize its calculation path.

Therefore, option D is the correct implementation.

When a Salesforce CPQ user logs into production for the first time, CPQ requires running the Post-Install Script. This script:

Creates default settings

Ensures CPQ-managed fields are initialized

Grants required permissions

Creates default Primary Quote logic metadata

Updates field values such as IsPrimary, quote calculation settings, etc.

Why the issue happenedThe customer implemented automation that automatically sets a new quote as Primary at creation.

If a user has not executed the CPQ Post-Install Script on their first login, then Salesforce CPQ has not yet initialized several objects and fields that are required for the Primary Quote creation process.

Therefore, the “first time users tried to create quotes” ? they encountered errors, because:

Their user-specific CPQ installation metadata was not initialized

CPQ could not run its internal logic that depends on Primary Quote setup

Salesforce’s installation documentation explicitly states:

Each CPQ user must run the Post-Install Script after first login, or they may encounter errors when creating quotes, setting a quote primary, or performing calculations.

Thus the correct answer is A, and it is consistent with CPQ installation best practices.

Scenario:

A customer has:

A posted invoice

A new order for the same account

Wants to add items without using invoice batches

The correct approach:

? D — Use Bill Now on the new order and consolidate invoicesSteps:

Run Bill Now on the new order ? generates a new invoice immediately.

Enable Invoice Consolidation (Billing settings / Account level).

Combine invoice lines from the new invoice into the already posted invoice.

Salesforce Billing supports invoice consolidation even after one invoice is posted.

Why the other options are wrongOption

Why Incorrect

A — Credit then Bill

Unnecessary; original invoice is correct and should remain posted.

B — Bill Now + reparent invoice lines

Reparenting posted invoice lines is NOT supported.

C — Cancel and Rebill

Only used to correct errors, not to add new order items.

Thus D is the correct solution.

Universal Containers wants:

ARR__c on Opportunity Line Item (Opportunity Product)

But ARR is currently on SBQQ__QuoteLine__c

They want ARR captured in pipeline reports without adding automation.

Salesforce CPQ Behavior:During Quote ? Opportunity sync, CPQ automatically maps fields only if:

The same API name exists on both objects

The field types match

The field-level security is correct

If these conditions are met, CPQ automatically handles field synchronization.

Therefore:

? C. Create ARR__c on Opportunity Line Item with matching field configurationThis leverages native CPQ field mapping, requires zero automation, and is the recommended Salesforce approach.

Why the other options are incorrect:Option

Why Incorrect

A. Price Rule to copy value

Price rules do not run on Opportunity Products; rules run only on Quote Line Editor.

B. Flow

Extra overhead and maintenance—unnecessary when CPQ already supports native field sync.

D. Cross-object formula

Opportunity Line Item cannot reference Quote Line fields (different object trees). Salesforce prevents this.

Thus, C is the only correct and efficient solution.

The requirement:

One Order Product must invoice 2 months of charges on the next invoice, without affecting the other 4 Order Products.

To do this, you must tell Billing to:

Skip 1 billing cycle

Jump ahead to a future billing date

Without impacting other Order Products

Without modifying invoicing schedule globally

The correct way is to set:

? Override Next Billing Date? This forces the next invoice line to include charges up to the new date, resulting in multiple periods billed together.

Why others are wrong:Option

Explanation

B — Hold Billing

Pauses billing entirely; does NOT create multi-month invoices.

C — Target Date

Controls invoice run date, not multi-period billing.

D — Bill Through Date Override

Controls end date of a prorated period, not the number of periods billed.

E — Bill Now

Generates an immediate invoice but still only bills 1 period unless dates are overridden.

Thus A (Override Next Billing Date) is correct.

Revenue Cloud implementations should NOT replicate outdated legacy CPQ logic.

Instead, Salesforce best practices require business transformation:

Understand current and future-state processes

Challenge legacy limitations

Use standard functionality wherever possible

Remove unnecessary customizations

? Correct Answer: COptions A, B, and D represent anti-patterns:

Option

Why Incorrect

A — Map legacy CPQ logic

Leads to replicating outdated processes rather than improvement.

B — Customize UI to mimic legacy

Increases technical debt and destroys scalability.

D — Keep legacy CPQ

Two CPQ systems create conflicts and are not recommended.

Thus C is correct.

When Price Rules are insufficient for complex pricing logic, Salesforce CPQ documentation directs consultants to the Quote Calculator Plugin (QCP) as the next escalation point.

QCP enables custom JavaScript logic executed inside the CPQ Quote Calculator, allowing manipulation of:

List price

Net price

Quantity

Custom logic loops

Conditional calculations beyond standard rule capabilities

Flows or Apex should not manipulate pricing during calculation because they run outside the CPQ calculator, causing inconsistent pricing results.

Hence the correct next step is QCP.

SKU rationalization reduces catalog complexity and improves CPQ performance by merging duplicate or similar products.

? A — Same product names with different attribute valuesUse Product Options, Attributes, or Configuration Attributes instead of separate SKUs.

? C — Same product names with different bulk discount levelsUse Discount Schedules instead of duplicating products.

? E — Same product names commonly found in the same bundleUse one product with options/rules, rather than multiple redundant SKUs.

Why others are incorrect:Option

Why Wrong

B — Same products with different serial numbers

Serial numbers belong on Assets, not separate products.

D — Same names with different terms

Use Subscription Term or Term picklist, not separate SKUs.

Thus A, C, E is correct.

Requirement:

Product may be taxable or tax-exempt depending on a custom field (Industry).

In Salesforce Billing:

Tax rules determine whether a product line is taxable or exempt.

Tax rules can be driven by custom logic using:

Custom fields

Flow

Apex

Determination scripts

Therefore:

? C. Use automation to set the Tax Rule based on the custom field.Why not the others?Option

Why Incorrect

A. Tax Treatment

Outputs tax result, but the rule determining taxability is the Tax Rule, not Tax Treatment.

B. Billing Rule

Controls invoice schedule, NOT taxability.

D. Revenue Recognition Rule

Controls revenue, not tax.

Thus C is the only valid solution.

Efficient UAT requires:

B – Define acceptance criteria upfront

D – Train UAT testers on new Revenue Cloud processes and CPQ/Billing functionality

E – Finalize test plans before build phase completes to ensure readiness

Options A and C are incorrect:

Consultants should NOT execute tests for the customer (UAT = customer validation).

Not every issue in UAT is a change request; many are defects that must be fixed.

All answers you provided are confirmed correct based on Salesforce CPQ & Billing documentation and implementation methodology.

Send the next set whenever you're ready!

The user story states that sales users should inherit previously negotiated pricing when quoting for existing customers.

In Salesforce CPQ, the object that stores account-specific negotiated prices is:

Contracted Pricing (SBQQ__ContractedPrice__c)

This object overrides standard list prices during quoting based on:

Account

Product

Pricebook

Contract linkage

Therefore, in addition to migrating Accounts, Contracts, and Quotes, the missing legacy pricing data must be loaded into Contracted Pricing.

To correctly load and rate Usage in Salesforce Billing, a Usage Record must contain the minimum required fields that allow the Billing Engine to:

Identify which subscription/order product the usage belongs to

Determine the billing period

Retrieve the correct rating method (per unit, tiered, etc.)

Apply account-level and billing-level context

Roll up usage into a Usage Summary for invoicing

Salesforce Billing documentation specifies that the following fields are required for rating:

Required Fields for Usage RatingField

Why it is required

Order Product (SBQQB__OrderProduct__c)

Links usage to the billable product and its pricing model

Start Date/Time

Used to determine billing period & usage summary matching

(End Date/Time)

Optional, depending on rating model

Quantity

Required for rating calculation

Unit of Measure

Required to match usage with the product's usage rate

Usage Summary Lookup (optional but required for import batching)

Groups usage records for processing

Account

Required for Billing Context

Option B is the only choice that correctly includes:

Order Product (mandatory for rating)

Start Date/Time

Quantity

Unit of Measure

Usage Summary Lookup

Account

This matches Salesforce Billing’s usage rating prerequisites.

? Why other options are incorrect:A – Missing Order Product IDUsage cannot be rated without knowing which subscription/order product it belongs to.

So A is invalid.

“Matching ID” and “Matching Attribute” are not standard required fields for usage rating.

Overly broad and mixes irrelevant fields.

C – Includes fields that Salesforce does not require

D – Only includes UOM + QuantityInsufficient. Missing the essential contextual fields (Order Product, Date/Time, Account).

? Final Confirmed AnswerB. lookup start date time, order product ID, unit of measure, quantity, usage summary lookup, account

The consultant discovers:

Multiple triggers

Workflows

Flows

Possibly recursion or conflicting automations… on the Opportunity, which is foundational for CPQ.

Salesforce Revenue Cloud Best Practice:Use one automation type (preferably Flow) to avoid conflicts, recursion, performance issues, and unpredictable ordering.

Too many automation types cause issues with:

CPQ Quote Sync

Opportunity ? Quote event handling

Performance and CPU limits

Unpredictable execution order

Therefore:

? A — Recommend using a single automation type for best performanceThis aligns with:

Salesforce Well-Architected Framework

Salesforce CPQ implementation guidelines

General platform automation best practices

Why other options are incorrect:Option

Why Not Correct

B

Large Quote Threshold affects calculator performance, not Opportunity automation.

C

Multiple automation types is the problem, not the solution.

D

Accepting the current messy automation is not recommended before CPQ implementation.

Thus A is correct.

The Order Management Plugin (OrderPlugin2) in Salesforce CPQ allows architects to override the default behavior of CPQ when generating Orders from Quotes.

According to CPQ developer documentation, the plugin can override:

Order start date

Order end date logic (in limited ways)

Order product behaviors

The key supported override is specifically:

Setting the Order Start Date programmatically

Invoice Scheduler Settings:

Target Date = Jan 15

Bill Usage Charges = FALSE

This means:

The scheduler will generate invoice lines for Order Products only, not usage summaries.Thus the correct rule is:

? A — Order Products with Next Billing Date equal to or earlier than January 15

Why the other options are wrong:Option

Why Incorrect

B — Usage Summaries

Ignored because Bill Usage Charges = False.

C — Next Billing Date equal to or after

Billing only generates lines for dates <= Target Date.

D — Next Charge Date

Not used by Invoice Scheduler.

Thus A is correct.

User Story“As a pricing manager, bulk discounts must include previously purchased quantities for pricing calculations on the quote to reward loyal customers.”

This refers to historical purchases influencing tiered or volume discounts.

In Salesforce CPQ, the only native feature that supports “include prior purchases when calculating discount tiers” is:

? Discount Schedules with Cross Orders enabledThis setting tells CPQ to:

Look at existing subscriptions, assets, orders, and previous quote lines

Aggregate prior quantities

Apply tiered volume discount based on the total owned quantity + new quantity

But for Cross Orders functionality to work…

? Historical Subscriptions / Assets must existSo you must migrate historical:

Contracts

Subscriptions

Assets (if asset-based ordering)

Without that data, CPQ cannot aggregate historical quantities.

Correct answer: B and E? B — Populate Contracts, Subscriptions, and Assets with historical dataCPQ needs these to calculate previously purchased quantities.

? E — Discount Schedules with Cross Orders checkedThis is the actual feature that uses prior purchased amounts to determine discount tiers.

Why the other options are not correct:Option

Why Incorrect

A — Custom Action

Unnecessary. CPQ has native Cross Orders behavior.

C — Summary Variable

Summary variables do not summarize external historical purchases.

D — Migrate Orders & Invoices

Not required for CPQ pricing. Only Subscriptions/Assets matter.

A partner leading a Revenue Cloud Scoping session requires:

? A — Strong communication skillsEssential for facilitating workshops, documenting requirements, and aligning stakeholders.

? B — Effective at planning, monitoring, reviewingScoping is structured, requires:

Agenda control

Risk identification

Note capture

Validation cycles

? E — Understanding design pitfalls & mitigationCritical in CPQ + Billing, where poor scoping leads to:

Wrong pricing model

Incorrect renewal logic

Billing edge cases

Data migration problems

A good partner surfaces these risks early.

Why the wrong answers are incorrect:Option

Why Incorrect

C — Knowledge of competitor products

Not relevant to scoping Salesforce Revenue Cloud.

D — Experience with quota-carrying sales roles

Helpful but not foundational to scoping complex CPQ + Billing architecture.

Final answer for Q49 = A, B, E

Requirement:

Provide an aggregated view of current goods and services on a contract.

This refers to consolidating all active entitlements, subscriptions, assets, and amendments.

Salesforce Revenue Cloud feature for this:? E. Customer Asset Lifecycle Management (CALM)CALM provides:

A unified, aggregated view of:

Active assets

Entitlements

Subscriptions

Amendments

Renewed services

Tracks lifecycle changes from:

Orders

Amendments

Cancellations

Upgrades

Represents the source of truth for what the customer owns today.

Why not the others?Option

Why Incorrect

A. Amendments

These modify contracts but do NOT aggregate current products.

B. Orders

Represent transactions, not current state.

C. Subscriptions

Only subscription items, not full lifecycle items or non-subscription goods.

D. Renewals

Only track renewal processes, not aggregated state.

Only CALM provides an aggregated, contract-aligned view of all customer entitlements.

When users log in to Salesforce CPQ for the first time, the Post-Install Script must run.

This script:

Initializes CPQ user settings

Creates required calculation metadata

Ensures Quote + Quote Line permissions and defaults work

Enables Primary Quote logic

If an automation tries to set a new Quote as Primary, but the user has not run the CPQ post-install script, CPQ raises errors because internal references and fields are not yet initialized for that user.

This is a documented CPQ requirement.

Thus, A is correct, and all other options point to permission issues that do NOT cause this specific failure pattern.

The Salesforce CPQ calculation sequence includes:

Internal Initialization

QCP: onInitialization()

CPQ: Calculate Formulas (pre-calculation)

Price Rule Evaluation: Before Calculate

QCP: onCalculate()

Price Waterfall (Pricing Engine)

QCP: AfterCalculate()

Option D matches this exact order:

internal initialization ? on Initialization ? calculate formulas ? Before Calculate ? calculate quantities ? On Calculate ? Price Waterfall ? After Calculate