Rev-Con-201 study plan

Sequence the product-to-cash stages and name the record type that carries each stage from catalog through cash application.

Draw the data model linking product definition, price book entry, quote line, order line, contract, subscription, asset, billing schedule, invoice line, and payment.

Configure a starter catalog containing at least one good and one service product, each with a distinct selling model.

Trace one subscription record through its full status progression and annotate which stage of the lifecycle each status represents.

Build price book entries so the same product carries different prices in two price books and verify which price a quote pulls by default.

Create discount schedules and price rules, then compute the expected evaluated price for each combination before running it.

Model a bundle with required and optional components and set the constraints that govern selecting and deselecting components.

Configure configuration attributes so that one attribute choice filters which components remain selectable.

Test pricing precedence by stacking a list-price override, a volume discount, and a manual line discount on one quote line.

Generate quotes from opportunities and add standalone, bundle, and service lines without breaking price resolution.

Group quote lines into logical sections and confirm group-level rollups match the sum of their lines.

Configure a ramped quote line set where quantity or price steps up across periods, and predict the resulting billing spread.

Set proration behavior on a mid-period line and verify the partial-period amount against a manual calculation.

Produce a customer-facing quote document template that shows line detail, discounts, and totals.

Convert an accepted quote into an order and contract, then confirm the resulting subscription and asset records match the quoted terms.

Execute an amendment that changes quantity mid-term and record the proration outcome.

Execute a renewal and a cancellation on the same subscription family and contrast how each affects the term and the billing schedule.

Design an approval workflow triggered by discount threshold and document the routing conditions.

Sit a 60-question timed assessment across domains 1 through 3 and classify every missed item by root cause.

Generate billing schedules from active subscriptions and verify period boundaries, amounts, and any proration at term edges.

Run an invoice generation cycle and reconcile every invoice line back to its source billing schedule row.

Apply tax treatment and confirm tax lines appear correctly on the invoice and in totals.

Record payments against invoices, including one partial payment, and observe how invoice balance and status change.

Issue a credit memo and trace how it reduces the outstanding balance.

Configure a usage-based charge and confirm rated usage flows into the correct invoice line for the period.

Handle a failed payment end to end, including retry and dunning step, and document each state change.

Identify performance obligations in a multi-element contract and allocate transaction price using standalone selling prices.

Build a revenue recognition schedule for that contract and compute the recognized amount for each period.

Produce the journal entries for one period, balancing contract asset or liability against recognized revenue.

Report on subscription health by building views for active subscriptions, upcoming renewals, and churn within the next 90 days.

Reconcile billed versus recognized revenue for the quarter and explain every variance line.

Analyze amendment and cancellation impact on recurring revenue using a period-over-period comparison.

Build a dashboard that surfaces at least five metrics a finance stakeholder would act on.

Audit your own data model for reporting gaps, such as missing dates or unlinked records, and list fixes.

Re-run every weak-area item from weeks 4 and 6 and confirm each is now answered correctly with reasoning.

Sit two full-length timed mock exams and compare section-level scores between them.

Re-derive the end-to-end lifecycle from memory and mark any stage you cannot explain in one sentence.

Close remaining knowledge gaps by rebuilding the two configurations you found hardest, without notes.