Log Every Pricing Exception Before Discount Drift Becomes the Price

The Signal

A customer emails asking why their invoice total does not match the quote from six weeks earlier. A finance lead pulls the CRM record and the order form and finds two different unit prices, both technically "approved," neither matching what the customer actually agreed to pay. Nobody committed fraud. Someone applied a discount verbally on a call, someone else applied a different one in writing, and the system recorded whichever one was typed in last.

That is the signal: pricing exceptions are not the problem. Untracked pricing exceptions are the problem. Every business grants discounts, waives fees, and negotiates custom terms — that is normal commercial behavior. What breaks the business is when those exceptions exist only in an email thread, a verbal agreement, or one salesperson's memory, with no record of who approved them, why, or for how long.

A pricing-exception log closes that gap. It is a single record of every deviation from list price or standard terms, with the customer, the exception, the business reason, the approver, the expiration or review date, and whether it was ever meant to be permanent.

Why this matters now

Discounting tends to accumulate rather than reset. A customer gets a temporary reduction during a rough quarter, and the reduction quietly becomes their permanent price because nobody scheduled a review. A new sales rep, unaware of the informal exception, offers a different discount to the same account, and now two conflicting terms exist for one customer.

Corporate Finance Institute's overview of price discrimination describes how deliberate price variation is meant to function as a bounded tool tied to a specific business objective — segmenting willingness to pay, clearing inventory, winning a competitive deal — not as permanent, untracked drift in the price book. Reference: https://corporatefinanceinstitute.com/resources/accounting/price-discrimination/

Without a log, the business cannot answer basic questions during a renewal, an audit, or a margin review: how many customers are on exception pricing, what those exceptions are costing in aggregate, and which ones were supposed to end months ago. The exceptions become the default, and the list price becomes the number nobody actually charges.

The mistake to avoid

The mistake is approving exceptions verbally and recording only the outcome — the final number in the invoicing system — without recording the reasoning or the expiration. A price with no attached reason cannot be evaluated later; nobody can tell whether it still serves the original purpose or whether the situation that justified it ended a year ago.

A related mistake is letting exception approval bypass any owner. If any salesperson can grant any discount without a named approver, the business has no way to see the pattern until margin erodes across dozens of accounts at once. The individual exceptions might each be defensible; the aggregate is often not.

Do not confuse a pricing-exception log with a punitive audit trail. The goal is not to prevent reasonable flexibility. It is to make every exception visible, time-bound, and reviewable, so flexibility stays a deliberate choice instead of an accumulating default.

Build the exception log

Create one record for every customer currently paying, or receiving terms, outside the standard price book. For each entry, capture the customer, the specific deviation, the stated business reason, the approver, the date granted, and a review or expiration date — even a generous one is better than none.

Separate structural exceptions, such as a negotiated enterprise contract with its own term, from informal ones granted mid-conversation to save a deal or address a complaint. The informal category is where drift accumulates fastest and deserves the tightest review cadence.

Assign someone to run a quarterly pass: pull every exception nearing its review date, confirm whether the original reason still applies, and either renew it deliberately, adjust it, or let it expire back to standard pricing.

What stays protected

Protect the sales relationship by not treating every exception as a mistake to reverse. Some exceptions are the right call and should stay in place — the log exists to make that a documented decision, not an accident.

Protect margin visibility by keeping the log connected to actual invoiced amounts, not just the terms someone believes are in effect. A log that drifts from what billing systems actually charge is as unreliable as no log at all.

Protect the approver's judgment by requiring a stated reason for every entry. A reason forces a real business justification instead of a reflexive yes to whichever customer pushed hardest.

The first move

Pull the last twelve months of invoices for your ten highest-revenue accounts and compare the price actually charged against your current list price or standard terms. Note every deviation, however small, and check whether anyone can produce the original reason it was granted.

The move this week

Build the exception log for every customer currently outside standard pricing. Assign an approver and a review date to each entry, and flag the ones with no documented reason at all — those are the exceptions most likely to be quietly costing margin with nobody watching.