The tables behind CPQ & Quote-to-Cash

The catalog of record: every SKU that can be sold, configured, priced, quoted and billed, with the cost the margin on a quote line is measured against.

A named set of choices on a configurable product (edition tier, support level, term, warranty), with whether the rep must choose and how many values may be chosen.

The values inside an option group, each with the price delta it adds to the unit price when chosen.

What a product of Type = Bundle is made of: the required and optional component products, their quantities and whether each is priced inside the bundle or as its own line.

Header of a configuration rule: a named, typed rule that runs against every quote line on save.

The “if” clauses of a rule. Conditions on one rule are AND-combined; an OR is a second rule.

The “then” clauses of a rule. Every action fires when all the rule’s conditions match the cart.

Append-only configuration evaluation evidence, including rejected draft attempts, so failed saves and warnings remain reportable.

One product on a quote with its quantity, the list and net unit prices the recompute resolved, and any line discount. Component lines of a bundle nest under the bundle line through parent line.

The options chosen on a configured line, one row per option, with the price delta frozen at selection time.

The open deal a quote is written for. Synced from the CRM; stage is read here and worked there, and the primary quote’s total is synced back to Amount.

Staged CRM product payload with required mapping before any valid quote line is created.

Versioned activation evidence for catalog/rules, pricing, tax, templates and approval policy; effective records are immutable.

A versioned price book. Several may be active at once (standard list, enterprise, partner, a promotion); a quote picks exactly one. Inactive books stay referenceable by historical quotes.

Per-product prices inside a book, with volume breaks and a floor. A missing book entry uses base price only when the reviewed policy permits that fallback; missing floor/cost coverage still requires review.

Automatic combination pricing. When the qualifying products all appear on a quote, the bundle recompute applies the discount as a quote discounts row with Reason = Bundle. Bundle rows are excluded from the discount percent that is routed for approval.

The products that must all be on a quote for the bundle discount to qualify, one row per product.

Reviewed configured tax cases by jurisdiction, with explicit taxable scope and exemption evidence. Accounting-owned final tax is an alternative; complete US tax coverage is not claimed.

The quote header: one per proposal to a buyer, whether for new business, a renewal or an amendment of a contract. Submission creates the immutable quote versions authority; controlled withdrawal creates a fresh revision before any unaccepted change.

One product on a quote with its quantity, the list and net unit prices the recompute resolved, and any line discount. Component lines of a bundle nest under the bundle line through parent line.

Header-level discounts on a quote, with the rep’s reason and justification. Rows with Reason = Bundle are written by the bundle recompute and are excluded from the routed percent.

Frozen allocation of each full-term header discount to eligible commercial lines; exact sums and provenance prevent lost discounts or false automatic bands.

Complete submitted commercial snapshots, retained through approval, sending and acceptance; later revisions cannot rewrite their prices, configuration, terms or signature authority.

Immutable commercial authority for each submitted and accepted configured line; retained even when a later draft changes or removes the working line.

Versioned activation evidence for catalog/rules, pricing, tax, templates and approval policy; effective records are immutable.

The quote header: one per proposal to a buyer, whether for new business, a renewal or an amendment of a contract. Submission creates the immutable quote versions authority; controlled withdrawal creates a fresh revision before any unaccepted change.

One product on a quote with its quantity, the list and net unit prices the recompute resolved, and any line discount. Component lines of a bundle nest under the bundle line through parent line.

The options chosen on a configured line, one row per option, with the price delta frozen at selection time.

Header-level discounts on a quote, with the rep’s reason and justification. Rows with Reason = Bundle are written by the bundle recompute and are excluded from the routed percent.

The named milestones a Milestone-billed quote is invoiced on, with the share or amount of each and the event that makes it billable.

Complete submitted commercial snapshots, retained through approval, sending and acceptance; later revisions cannot rewrite their prices, configuration, terms or signature authority.

Immutable commercial authority for each submitted and accepted configured line; retained even when a later draft changes or removes the working line.

The document a quote is rendered to: layout, cover text, terms and conditions, and what the buyer sees of the discounting.

The agreement documents a contract is generated from, with the default term, renewal behaviour and uplift each one carries.

One e-signature envelope per document sent for signature: a quote sent for signature, or a contract generated from a quote that was sent for review. Status is updated by inbound provider webhooks.

Event log from the e-signature provider, one row per inbound webhook event.

The customer master as this system needs it: who is sold to, who signs, who is billed, and the credit position an order is confirmed against. Synced from the CRM and extended with billing and credit fields.

The people at an account: who receives the quote, who signs the order form, who gets the invoice. Synced from the CRM with the account.

The open deal a quote is written for. Synced from the CRM; stage is read here and worked there, and the primary quote’s total is synced back to Amount.

Staged CRM product payload with required mapping before any valid quote line is created.

Durable local business-event inbox/outbox and atomic effect key. This is a required implementation contract, not a claim that integrations are live.

Per-destination delivery attempts and acknowledgments separate local issue/release from external posting or provisioning.

Tiered approval thresholds. Approval routing reads this on quote submit to pick the tier for the quote’s discount percent. Active rows must not have overlapping percent ranges.

Header-level discounts on a quote, with the rep’s reason and justification. Rows with Reason = Bundle are written by the bundle recompute and are excluded from the routed percent.

Frozen allocation of each full-term header discount to eligible commercial lines; exact sums and provenance prevent lost discounts or false automatic bands.

The audit trail of a routing decision: one row per approver action on a submitted quote, created by approval routing from the matrix tier, the floor check or the terms check.

Complete submitted commercial snapshots, retained through approval, sending and acceptance; later revisions cannot rewrite their prices, configuration, terms or signature authority.

Immutable commercial authority for each submitted and accepted configured line; retained even when a later draft changes or removes the working line.

Reviewed, time-bounded named-user grants; delegation never changes the meaning of an approval decision or permits self-approval.

Versioned activation evidence for catalog/rules, pricing, tax, templates and approval policy; effective records are immutable.

People who use the system, with the role that decides their screens, the approver tier they can sign for, and the delegate who covers them when they are away.

The agreement documents a contract is generated from, with the default term, renewal behaviour and uplift each one carries.

The commercial agreement behind an accepted quote: term, renewal behaviour, signed document and value. Created already signed when the quote itself was the signed order form.

Effective signed commercial history for original terms, amendments and renewals; replace/cancel entries supersede only their approved future scope.

The quote header: one per proposal to a buyer, whether for new business, a renewal or an amendment of a contract. Submission creates the immutable quote versions authority; controlled withdrawal creates a fresh revision before any unaccepted change.

Complete submitted commercial snapshots, retained through approval, sending and acceptance; later revisions cannot rewrite their prices, configuration, terms or signature authority.

Immutable commercial authority for each submitted and accepted configured line; retained even when a later draft changes or removes the working line.

One e-signature envelope per document sent for signature: a quote sent for signature, or a contract generated from a quote that was sent for review. Status is updated by inbound provider webhooks.

Event log from the e-signature provider, one row per inbound webhook event.

One controlled decision per expiring contract term. Records explicit notice/nonrenewal and the exact signed pricing authority used for either automatic or manual renewal.

Versioned activation evidence for catalog/rules, pricing, tax, templates and approval policy; effective records are immutable.

The customer master as this system needs it: who is sold to, who signs, who is billed, and the credit position an order is confirmed against. Synced from the CRM and extended with billing and credit fields.

The people at an account: who receives the quote, who signs the order form, who gets the invoice. Synced from the CRM with the account.

The order created from an accepted quote and handed to fulfilment or provisioning once deal desk confirms it against the PO, the credit position and the contract.

Staged order lines allocated from immutable accepted quote lines, retaining net term amounts, service periods, configured options and evidenced fulfillment.

Reserves a portion of an accepted line for one staged order, carrying the exact accepted value and periods through billing.

The quote header: one per proposal to a buyer, whether for new business, a renewal or an amendment of a contract. Submission creates the immutable quote versions authority; controlled withdrawal creates a fresh revision before any unaccepted change.

Complete submitted commercial snapshots, retained through approval, sending and acceptance; later revisions cannot rewrite their prices, configuration, terms or signature authority.

Immutable commercial authority for each submitted and accepted configured line; retained even when a later draft changes or removes the working line.

The named milestones a Milestone-billed quote is invoiced on, with the share or amount of each and the event that makes it billable.

The commercial agreement behind an accepted quote: term, renewal behaviour, signed document and value. Created already signed when the quote itself was the signed order form.

Effective signed commercial history for original terms, amendments and renewals; replace/cancel entries supersede only their approved future scope.

Immutable fulfillment evidence received from a configured ERP/provisioning/acceptance source, separate from invoice generation.

The customer master as this system needs it: who is sold to, who signs, who is billed, and the credit position an order is confirmed against. Synced from the CRM and extended with billing and credit fields.

Durable local business-event inbox/outbox and atomic effect key. This is a required implementation contract, not a claim that integrations are live.

Per-destination delivery attempts and acknowledgments separate local issue/release from external posting or provisioning.

The billing schedule for an order: when each amount is invoiced, built from the order’s billing method and its lines’ frequencies, timing and terms.

One planned invoice amount, tied to the order line or milestone it bills and, once issued, to the invoice. A milestone line waits as Pending without a date until its trigger fires.

The locally issued invoice, delivered separately to accounting, settled by effective payment/credit applications and corrected through immutable credit evidence.

What the invoice charges for, one row per product and service period.

A credit raised against a posted invoice for a pricing error, a service credit, a dispute, a write-off or a cancellation. Independently approved above the requester’s captured limit, issued, delivered to accounting and allocated between outstanding invoice balance and account credit.

Original invoice-line allocations bound the creditable net/tax value, including fully paid invoices.

Money received from an account, applied across one or more invoices through payment applications.

How much of a payment settled which invoice: one row per invoice a payment touches, so a wire covering three invoices or a short pay is recorded as it happened.

Controlled immutable payment/application reversal, returned-cash and refund effects. A requested or uncertain bank refund has no confirmed money effect.

Spends a credit memo surplus once, on an invoice or a confirmed refund, while preserving the source invoice historical payment trail.

The order created from an accepted quote and handed to fulfilment or provisioning once deal desk confirms it against the PO, the credit position and the contract.

Reserves a portion of an accepted line for one staged order, carrying the exact accepted value and periods through billing.

Immutable fulfillment evidence received from a configured ERP/provisioning/acceptance source, separate from invoice generation.

The customer master as this system needs it: who is sold to, who signs, who is billed, and the credit position an order is confirmed against. Synced from the CRM and extended with billing and credit fields.

Durable local business-event inbox/outbox and atomic effect key. This is a required implementation contract, not a claim that integrations are live.

Per-destination delivery attempts and acknowledgments separate local issue/release from external posting or provisioning.

Reviewed historical import and cutover boundary with stable source keys, staged references and live-trigger suppression.