1. CPQ for Data Center Infrastructure
  2. Features
  3. Evidence and reconciliation
Feature · Evidence and reconciliation

Evidence and reconciliation

Connect quote decisions to supporting files and investigate uncertain operation results.

OverviewOperation Exceptions
CPQ for Data Center Infrastructure · Evidence and reconciliation

Operation Exceptions

Operation receipts

New
ParentActionOperation keyExpected revisionResult stateOccurred at
QTS-61950ACT-605OK-765830Pending15 Oct
QTS-71113ACT-998OK-905110Failed11 Oct
QTS-21468ACT-916OK-316510Needs review04 Oct
QTS-85015ACT-434OK-716810Pending09 Oct
QTS-22870ACT-486OK-434200Failed03 Oct
6 of 6 records
ACT-605Operation receipts · OR-10557
Pending
ParentQTS-61950
Operation keyOK-765
Expected revision830
Occurred at15 Oct
Failure reasonCut to length
Example screen with sample data

What you can do

Keep the explanation with the quote

A Pricing Reviewer may return to an offer after the original customer conversation has ended. Quote attachments retain a title, evidence type and uploaded file, together with the uploader and visibility setting. Use those records for customer requirements, pricing support and acceptance evidence so the next reader can find the material behind a decision.

Operation receipts provide a separate record of attempted work. Each receipt identifies its parent quote, expected revision and action, with a stable operation key and result state. When a result needs attention, compare the receipt with the quote lines and review decisions. Operations Overview brings quote value, lifecycle mix and operational exceptions into the team’s daily discussion.

How the work is organized

  • Supporting files. The Quote Specialist attaches material to the intended quote and gives it a useful title. Check Internal or Shared visibility before using the document in the next handoff.
  • Review evidence. A decision records the source revision and reviewer’s reason. Open it alongside the current quote when explaining why an earlier offer was approved, rejected or returned.
  • Result investigation. Pending, Failed and Needs review results require examination of the recorded effects. Retain a concrete failure reason when the evidence does not support completion.

What to agree during setup

Agree which documents are appropriate for Shared visibility and who may change that setting. Test document access with the normal accounts that will read the evidence. Keep sensitive pricing support within the access rules the team establishes, and check how any customer-facing delivery uses the shared files.

Assign responsibility for investigating each operation result. Decide how the reviewer compares the expected revision with the actual quote and decision evidence. A completed result needs a real effect reference or other matching support. Define how an investigator handles an uncertain handoff response without editing the earlier receipt into a success that the downstream system cannot confirm.

Check the handoff on an actual case

Attach the rack requirement sheet and pricing explanation to the expansion quote. Give each document a title that distinguishes its purpose, then check its visibility and uploader. Ask the Pricing Reviewer to locate the material using normal review access and explain which quote revision received the decision.

Next, inspect a handoff receipt with a Pending or Failed result. Compare its expected revision and operation key with the accepted quote. Check the external reference against the configured order connection before deciding whether the handoff completed. Rehearse a discrepancy where the receipt’s claim does not match the local decision evidence; the investigator should record a clear reason for further review and leave the accepted quote’s evidence intact.

What your team sees

  • Operation Exceptions — Investigate Pending, Failed and Needs review action results.
  • Quote Evidence — Find supporting files and check their visibility and uploader.
  • My Review Decisions — Read the judgments associated with the signed-in reviewer.

Follow the work through

Follow operation reconciliation and agree the connection responsibilities under integrations.

What it keeps track of

Data model
Record attachments
Supporting evidence files attached to a quote.
Review decisions
Independent reviewer decisions recorded against a quote revision.
Operation receipts
Idempotent operation receipts recording persisted effects and outcomes.
Quotes
Versioned quotes prepared, reviewed, approved and accepted for customers.
Quote lines
Priced lines belonging to a quote, frozen by revision.
Team members
Team members with organization membership and role scope.

Who uses it

Permissions
Quote Specialist
, Pricing Reviewer, Auditor, Admin.
Auditor
Reads authorized evidence; the operational team investigates and resolves the result.

Set up CPQ for Data Center Infrastructure your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

How to get started