Salesforce AP-223 - CPQ and Billing Consultant Accredited Professional

Salesforce Billing’s Hold Billing field on Order Product works exactly as follows:

When Hold Billing = Yes, Salesforce Billing does not generate invoice lines for that Order Product.

Once the user sets Hold Billing back to No, Billing:

Calculates the missed invoice periods

Creates catch-up invoice lines so billing is not lost

Correct Behavior (per Documentation)This means:

✔ Invoicing is suspended

✔ Catch-up invoice lines are created for the entire period Hold Billing was active

Thus, C is the correct and documented behavior.

Why the other answers are incorrectOption

Description

Why Incorrect

A

Prevents invoice document generation and emails

Misleading: the function specifically stops invoice line creation for the order product; it does not manage email notifications.

B

Hold Billing auto-resets on activation

False. Hold Billing is a manual field and does not auto-clear.

D

Only invoices after Hold Billing is set to No are created

Incorrect—Billing creates catch-up invoices for missed time.

Thus, C is completely aligned with Salesforce Billing behavior.

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.

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.

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.

Amendments in Salesforce Billing must maintain clean financial continuity. Any financial artifact still in an incomplete or unsettled state breaks future invoicing, because Billing cannot prorate, advance, or reconcile future periods correctly.

✔ B — Subscription linked to Order Product with unpaid invoice linesUnpaid invoice lines cause:

Billing to treat the subscription as financially “not settled”

Block future billing for that subscription

Incorrect Next Billing Dates

This is a documented reason for missed or incorrect invoice generation.

✔ C — Subscription linked to Order Product with draft invoice linesDraft invoice lines mean the invoice is not posted, so:

Revenue and billing are not finalized

Billing engine cannot determine the next billing boundary

Amendments generate incorrect billing periods

This absolutely causes incorrect future invoicing.

✔ D — Subscription linked to an unallocated paymentUnallocated payments interfere with:

Aging

Balance-based billing logic

Proper allocation of future charges

Billing expects charges and payments to be reconciled.

Why A and E are not correct:Option

Reason

A — Not contracting the amendment order

You must contract an amendment order, but failure to do so stops renewal/amendment flow, not future invoicing behavior.

E — Contracting from amended opportunity

This is the correct and expected process, not a problem.

Thus B, C, D are correct.

Revenue Cloud Billing does not allow reparenting or reallocating payments across accounts.

To correct a misapplied payment:

Un-allocate the payment if already applied

Refund the payment

Create a new payment under the correct account (Account B)

Allocate it to the appropriate invoice

This follows Billing best practices for financial audit integrity.

RASIC is a well-known responsibility matrix used in Salesforce projects.

✔ Correct definition:R — Responsible

A — Accountable

S — Supporting

I — Informed

C — Consulted

INVEST criteria is a standard Agile user story quality framework.

Correct breakdown:

I — Independent

N — Negotiable

V — Valuable

E — Estimable

S — Small

T — Testable

Thus D is the correct choice.