A quote is a promise with arithmetic attached. When a line item carries the wrong price, the wrong unit, or a discount nobody approved, the error travels into the order, the invoice, and the revenue report. By then the buyer has a copy and the correction costs a conversation.
Line item source verification fixes the problem at the smallest unit of the quote. Each line gets a source, an owner, and a check before the document is sent. This guide describes the fields and the review routine, with the goal that any reviewer can explain a single line without opening four systems.
Add a source column to the quote line
Most quote templates show description, quantity, unit price, and total. Add a source reference for each line. The reference should point to the price book entry, contract clause, or vendor quote that authorises the value, along with the version and effective date.
The column is internal. Buyers do not need to see it, but the preparer and reviewer do. A line without a source is not automatically wrong, but unverified lines should not pass without a named approver.
Use a controlled list of source types rather than free text. Price book, customer contract, partner cost sheet, vendor quote, approved exception, and manual override cover most cases.
Tie price to a versioned price book
Price books change, and quotes outlive the change. Record the price book identifier and version on the quote, not just the resolved price. When a buyer challenges a number six weeks later, the version tells you which list was in force when the document was created.
| Line check | Authoritative source | Owner | Fail action |
|---|---|---|---|
| List price | Price book version and effective date | Sales operations | Hold and reprice |
| Discount | Approval record with approver and limit | Sales manager | Return to requester |
| Quantity | Buyer request or signed order form | Account executive | Confirm in writing |
| Unit of measure | Product catalogue | Sales operations | Correct before send |
| Term and start date | Contract or order form | Deal desk | Route to legal review |
| Tax code | Tax determination system | Finance | Hold for tax review |
If the price book has an expiry date, the quote should inherit it. A quote that references an expired list should fail validation even when the arithmetic is correct, because the authorisation no longer exists.
Verify quantity, unit of measure, and term
Price errors get attention; unit errors cause quiet losses. A line sold in cases but quoted in units, or a subscription quoted per month but billed annually, can pass a total check while being wrong by a factor of twelve. Compare the requested quantity with the quoted quantity and the unit of measure in the catalogue.
Term start and end dates deserve the same treatment. Check that the start date matches the requested service date, that the term length matches the contract, and that any co-termination with an existing agreement is documented. The NIST SP 800-53 control catalogue treats audit logging as a control family for a reason: the record of who changed what is part of the control, not an afterthought.
Freight, installation, and professional services often sit outside the main price book. Give them their own source line and owner. A services line copied from a previous quote is a common source of margin leakage.
Route discounts and nonstandard terms
Discounts should not be editable by the person preparing the quote unless the approval is attached. The approval record needs the approver, the limit approved, the reason, and the expiry. A discount that exceeds the delegated limit should route to the next level automatically rather than relying on a reminder.
Nonstandard terms follow the same path. Payment terms longer than the standard, custom cancellation, extended warranties, and data processing amendments all change the risk profile of the deal. Route them to the owner who can accept that risk, and record the response on the quote.
Keep the approval visible to the reviewer but out of the buyer-facing document. The buyer sees the commercial result; the internal record shows how the team earned the right to offer it.
Compare the quote to the order before booking
A quote that is correct can still become an incorrect order. Before booking, compare the order form to the accepted quote line by line: part number, description, quantity, unit, price, discount, term, and start date. Differences are not always errors, but each one needs a reason.
Build a variance list rather than a pass or fail. The list should show the quoted value, the ordered value, the difference, the reason, and the approver. A short variance list is a healthy sign that the comparison is real.
Record the comparison result on the opportunity. When finance later asks why the booked amount differs from the quoted amount, the answer is already attached to the deal instead of buried in an email thread.
Keep revision lineage beyond the file name
Quote revisions multiply quickly. Rev7_final_v2 is not a version control system. Give every revision an identifier, a creation timestamp, the author, the reason for the revision, and a link to the previous revision. The current revision should be obvious from the record, not from the file name.
When a revision changes a price or a term, record which line changed and why. The line-level checks pair with the quote request intake boundaries; if the review standard needs a second owner, book a free consultation. That lineage lets a reviewer reconstruct the sequence without comparing PDFs by eye. It also supports the quote revision analysis described in our research on reconstructing quote revision cycles.
Run a ten-minute pre-send review
The review does not need to be long. Check that every line has a source, that the price book version is current, that discounts have approvals, that units and terms match the request, and that the total arithmetic is correct. Then check the buyer-facing document for the correct logo, entity, currency, and validity date.
Assign the review to someone other than the preparer. The preparer has already convinced themselves the quote is right; a second set of eyes catches the copy-paste error that survived three checks. For small teams, the reviewer can be the sales operations lead, but the role should be named.
Log the review result with the quote identifier. A review that leaves no trace cannot be distinguished from no review at all, and the next auditor will have to trust the memory of whoever was on shift.
Frequently asked questions
Who owns quote line verification?
The preparer owns the first pass, and sales operations owns the review standard. Pricing, finance, and legal own the exceptions in their areas. A single named reviewer should sign off before the quote leaves the building.
Should every quote line have a price book reference?
Every line should have a source reference. Most will point to a price book entry, but contract lines, services, and approved exceptions will point elsewhere. The important rule is that the source is identifiable and the reviewer can open it.
How do we handle a quote that must go out before approval arrives?
Send it as a draft with an explicit expiry and do not accept a purchase order against unapproved terms. If the buyer needs a same-day document, escalate the approval rather than removing the gate. A fast quote with an unapproved discount is a slower problem later.
Related articles
Map a Fallback Owner for Every Lead Routing Rule
Build a lead routing map with a named fallback owner for every branch, a dwell limit, replayable routing events, and a weekly exception review.
Sales OperationsBuild a No-Show Recovery Queue With Named Ownership
Define a no-show, start recovery the same day, cap attempts, and measure recovered meetings without double-booking the calendar.
Sales OperationsRequire Evidence Before a Pipeline Stage Changes
Define observable stage exit criteria, attach evidence, log backward moves, and sample changes monthly so the pipeline reflects real buyer progress.