What makes a special pricing agreement exception?
A special pricing agreement is routine until a price is used outside its terms: after the end date, for the wrong customer, above the approved quantity or on a product the supplier never covered. The exception is the gap between what the system allowed and what the agreement allowed, and the work is finding it, arguing it with the supplier and fixing both the transaction and the rule that let it through.
Pricing systems make this easy to miss. In SAP, pricing condition records carry a validity period, and a new record can partially overlap an existing one, for example a special price valid for one month; a partial overlap adjusts the older record's dates without a message. In Microsoft Dynamics 365, each sales trade agreement price line has a From date and a To date, and when two agreements cover overlapping periods the one with the lowest price is selected when order lines are created. Neither behavior is a fault. Both mean that the price on an order can look correct while the agreement behind it has expired or been replaced, which is why the dates matter as much as the number.
SAP
Microsoft Dynamics 365Work through one exception: an expired approval reused on a new order
Illustrative worked example: a fictional 275-person electrical distributor, not a real case or a completed deal.
- Request, January 8. An inside salesperson asks a lighting manufacturer for a special price on LED fixtures for a hospital project, quoting the contractor and the expected quantity. Record: pricing request in the CPQ tool, with the project name.
- Approval, January 15. The manufacturer approves the price for that project, valid through March 31. Record: approval number and dates loaded as a price condition in the ERP; the approval letter saved in a shared folder.
- First orders, February and March. Orders priced under the approval; claims filed and paid. Record: order lines carrying the approval number; claim submissions and credits.
- The exception, April 12. The contractor places a follow-on order. The quote is copied from the March quote, approval number and price included. Nothing in the quote warns that the approval has expired. Record: order line with an approval number outside its validity dates.
- Rejection, May 3. The manufacturer rejects the claim for the April order as outside the agreement period. Record: rejection notice in the supplier's claim portal or email.
- Repair, May 10. The pricing desk asks for an extension; the manufacturer re-approves the same price from April 1 to September 30. Record: new approval, linked to the old one by project, and a resubmitted claim.
- Checked result, June. The resubmitted claim is paid, and the CPQ team adds a rule that blocks copying an approval past its end date. Record: claim credit, change request for the rule.
Steps 4 and 5 are what turn a price history into an explained exception. They show a system accepting something it should have refused, a counterparty catching it, and people repairing both the transaction and the process. The deal desk approval data type covers the internal approval side of the same pattern.
Which record proves each part of the exception?
Each stage of the case needs its own record. If one is missing, the story breaks at that point.
| Part of the case | Record | Typical home | What it proves |
|---|---|---|---|
| The initial problem | Order line with an approval number past its end date | ERP order history | The system priced an order the agreement no longer covered |
| The authority that existed | Supplier approval with validity dates | ERP price conditions and the approval letter | What was actually approved, for whom and until when |
| The catch | Claim rejection with its reason | Supplier claim portal or email | A counterparty applied the agreement terms |
| The authorized action | Extension request and re-approval | Email and the new price condition | Who asked, who approved and the new dates |
| The checked result | Paid resubmitted claim | Accounts receivable or claim ledger | The repair worked financially |
| The process fix | CPQ rule change request | Change log or ticket system | The company stopped the same error recurring |
Pricing requests, supplier approvals and order outcomes are the core. The claim and change records turn them from a price list into a decision history. Note that this table describes record classes. It does not assume any particular export from any vendor's tool; what each system can actually produce is confirmed later, with the company.
What to ask the pricing director about coverage and rights
Keep every question at metadata level. You are learning what exists, not collecting it.
- How many years of special pricing approvals are held, and in which systems?
- Are rejected and resubmitted claims kept with the original claim, or only the final credit?
- Do order lines carry the approval number in a field, or only in free-text notes?
- Roughly how many claims a year are rejected, and is the reason recorded?
- Do supplier program terms restrict how approval letters or claim data may be disclosed?
- Who in the company can authorize a discussion about licensing these records?
Supplier confidentiality is the usual sticking point; the question on distributor price file confidentiality covers it, and why data rights matter explains why SourceX reviews rights before anything else.
Does the company qualify, and what stays unknown?
The introduced company needs 50+ full-time employees at peak (contractors excluded), a documented operating history, rights to license the records, and an authorized contact. Companies in the U.S., Canada and the EU qualify, as do companies in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia when at least 90% of the data is in English. See who qualifies, the industries hub, wholesale distribution and specialty distribution.
Until SourceX reviews it, nobody knows whether buyers want this history, what rights review concludes about supplier and customer terms, how much de-identification is needed, or whether an offer follows. Partners sign the Channel Partner Agreement before submitting introductions; the first valid introduction within the 90-day window is credited when the company submits a verified application.
Go deeper on special pricing agreement exceptions
- Special pricing exception records across systems: a field map of the keys that join CPQ, ERP and claim records.
- Who can license special pricing exception records: a short answer on which decision-maker to introduce.
- Preserving special pricing exception history: an inventory checklist for before a pricing transformation.
- Special pricing exception referral brief template: a fill-in template for the introduction itself.
Next step
Refer a company. Earn up to $100,000. Default reward: 25% of Actual Supplier Payout, capped at $100,000 cumulatively per referred company. Eligibility and payment conditions apply, and a signed Schedule A or addendum can differ. A lead, meeting or signature alone does not trigger payment.
If a distributor can trace its rejected and repaired special pricing claims from request to paid credit, register as a partner, check the company against who qualifies, and read the program terms before you introduce the pricing director.