Discount Approval Process: A Policy Template Sales Teams Will Follow

A discount approval process is the rule for who may approve which discount before a quote reaches the customer. It needs bands set from your own margins, an approver for each band, and one rule: the approved quote version is the one the customer sees. A CRM such as Senitix CRM keeps the request and the decision on the quote.

Most discount policies fail for reasons that have nothing to do with the numbers. The bands live in a slide nobody opens, approvals happen in chat, and the rep edits the quote after the manager says yes. The template below fixes the process and leaves the numbers to you, because your margins, not an industry average, decide what a discount costs.

What is a discount approval process?

It is the path a discount request takes from the rep who wants to offer it to the person allowed to grant it. Three terms get used interchangeably, and it helps to separate them:

• Sales discount policy: the rules. What counts as a discount, how wide each band is, and what the customer gives in return.
• Discount approval workflow: the routing. Who sees a request, in what order, and how fast they must answer.
• Deal desk: the people. A standing group, usually from sales operations, finance and sometimes legal, that reviews non-standard deals.

Pricing approval is the broader version: it covers payment terms, contract length and non-standard clauses as well as price. Every team needs a policy and a workflow. Whether it needs a deal desk is covered below.

Why does a discount need an approver at all?

Because a discount costs more than it looks. A price cut comes straight off gross profit, so the extra volume needed to make it up is larger than the discount itself:

Extra volume needed = discount ÷ (gross margin − discount)

Example, with illustrative numbers rather than a benchmark: at an 80% gross margin, a 20% discount needs 0.20 ÷ 0.60, about 33% more volume, to earn the same gross profit. At a 40% margin, the same discount needs 100% more: twice the volume.

The second cost arrives a year later. A first-year discount with no end date quietly becomes the renewal price. Example: a $48,000 annual contract discounted 25% bills $36,000 in year one. If the quote never said the discount ends, returning to list price at renewal reads to the customer as a 33% increase. The third cost is consistency: when two similar customers compare notes, the one who paid more stops trusting your price list.

The discount policy template (fill in your own numbers)

Copy this into a one-page document. The bracketed values are yours to set from your margins and deal history; nothing here is a recommended percentage.

1. Scope. This policy applies to every quote: new business, expansion and renewal.
2. What counts as a discount. Any price below the price book, measured on the whole quote over the full term. That includes line discounts, a quote-level discount, free months, extra seats at no charge, waived setup fees and payment terms longer than [standard terms].
3. Bands. Up to [A]%: the rep decides. Above [A]% and up to [B]%: sales manager approval. Above [B]% and up to [C]%: finance approval. Above [C]%: offered only as a documented exception signed off by [VP of Sales or CEO].
4. Give-get. Every discount above [A]% names what the customer gives in return: a longer term, annual prepayment, a signature date, a larger volume or a reference.
5. Duration. Every discount states whether it applies to the first term only or renews. The default is first term only.
6. The request. The rep submits the quote itself, not a summary, with the reason, the give-get, any competitor involved and the expected close date.
7. Response time. Approvers answer within [X business hours]. A request with no answer escalates to [name or role]; it is never approved by default.
8. The version rule. An approval covers one quote version. Any change to price, discount, term or payment terms after approval creates a new version that needs its own approval. Only an approved version goes to the customer.
9. The record. Requests, decisions and reasons are recorded on the quote in the CRM. An approval in chat or email does not count.
10. Review. [Owner] reviews the bands every quarter against won and lost deals.

Two lines do most of the work. Measuring the discount on the whole quote stops a rep from splitting one large discount into several small line discounts that each stay under [A]%. Counting free months and extra seats stops the discount from moving somewhere the policy does not look.

The discount approval matrix: rep, manager, finance

The matrix turns the bands into routing. Fill in your own values, and add rows for the non-price terms your team negotiates most often.

What each approver checks: a manager confirms the deal is qualified, the give-get is real and the close date is credible. Finance checks margin over the whole term, the payment terms and what renews at what price. The exception approver weighs whether the deal is worth it and what precedent it sets.

Approvals run in order: a tier-3 request goes to the manager first, then finance, so finance never reviews a deal the manager would have turned down. An approver never approves a discount on their own deal; a manager who carries accounts routes their own requests one tier up.

Response times are part of the policy, not a courtesy. When approvals take days, reps learn to ask early for more than they need, and the approved discount becomes the opening offer.

Why must the approved version be the one the customer sees?

This is the rule most discount approval processes skip, and it is the one that makes the others work. The failure it prevents is common. A manager approves a discount on Tuesday. On Thursday the buyer asks for one more concession, and the rep adds a free month to close before quarter-end. The customer signs a quote nobody approved, and the approval record shows a number that was never sent.

The fix is mechanical. Every revision is a new numbered version of the quote, never an edit to the one that was approved. An approval attaches to one version, and when the version changes, the approval does not carry over. The approver also sees the whole quote, including term, payment terms and every line, not a one-line message that says “20% for the Denver deal.” For how a quote should show list price, discount and total so the buyer reads it correctly, see what to include in a sales quote.

Do you need a deal desk?

A deal desk earns its cost when non-standard deals are frequent enough that one manager cannot review them well. On a small team, a named approver and a response time usually do the same job.

A deal desk is probably overkill if:

• one sales manager can clear every tier-2 request the same day;
• you sell from one price book on standard terms, and most deals use them;
• legal redlines are the exception, not the norm;
• finance can answer tier-3 requests without a meeting.

You probably need one if:

• non-standard payment terms, service levels or contract clauses come up every week;
• you sell several products, in several currencies or through partners, each with its own price list;
• finance and legal are involved in most deals, not a few;
• deals slip because nobody knows who decides.

Illustrative scenario, not a real company: a 12-rep B2B SaaS team in Austin sells from one price book on standard annual terms. Instead of a deal desk, the sales manager clears tier-2 requests daily, and the controller holds a 15-minute review twice a week for tier-3 requests and exceptions. When the team adds a partner channel with its own price list, that review becomes a deal desk, and managing more than one price book becomes the next problem to solve.

What are the most common discount approval mistakes?

• Bands per line instead of per quote. Several small line discounts add up to a large one nobody approved.
• Approvals that never expire. An approval should end with the quote’s validity date. A price approved in March is not approved in June.
• No give-get. A discount with nothing in return teaches the buyer that asking works.
• Approval by timeout. It rewards slow approvers and makes the policy optional.
• A quarter-end exception tier. If the bands loosen in the last two weeks of a quarter, buyers learn to wait for them.
• Hiding the discount. A net price with no list price and no discount line leaves the renewal conversation nowhere to start.

How do you know the policy is working?

Report on won deals each quarter, and read the trend rather than a single month:

• Average effective discount, by rep and by band, on the whole quote over the full term.
• Share of quotes that needed approval. If nearly every quote needs one, the bands are too tight or the price book is wrong.
• Approval turnaround, from request to decision, by approver.
• Win rate with and without a discount. If discounted deals do not win more often, the discount is not what closes them.
• Price at renewal against the first term, to check that first-term discounts end when the policy says they do.

How to run discount approvals in Senitix CRM

Quotes in Senitix CRM are built from the product catalog and price books, with line items, discounts and totals. Each revision is kept as a numbered version, and quote templates produce the PDF the buyer receives, so the record shows exactly which version went out. The quotes and products features cover the detail.

Approval processes add the routing. Each process has its own steps and approvers, and its entry criteria decide which quotes it covers, such as a discount above your tier-2 band. A step can name a specific person, a role or the quote owner’s manager, so a request goes to the sales manager first and finance second. By default, a quote that needs approval cannot be marked as sent until it is approved, and if the values it was approved on, such as the discount, change afterward, it has to be approved again before it can be. Automations and approvals sit together in the feature catalog. Field permissions can keep a cost or margin field visible only to the roles that approve.

Two boundaries. A workspace without approval processes handles the manager’s review outside the CRM, with the version history as the record of what was sent (plan availability is on the pricing page). And volume discount schedules and customer-specific contracted prices are not available yet: the rep enters the discount on the quote, and your policy decides whether it stands.

To put the policy to work on your own quotes, compare plans or talk to the sales team.

Frequently asked questions

How long should a discount approval take?

Set a response time for each tier and publish it with the policy. A manager-level request should get an answer the same business day, and a finance-level request within one business day, because a quote that waits loses momentum. If an approver misses the window, the request escalates to a named backup. It should never be approved automatically, or the slowest approver sets your discount policy.

Should the discount be visible on the quote?

Yes. Show the list price, the discount as its own line and the net total, and say whether the discount applies to the first term only. A visible discount tells the buyer what they received, and it gives the renewal conversation a starting point. A quote that shows only a net price turns that price into the new list price in the customer’s mind.

How do you handle discount requests at the end of the quarter?

Apply the same bands and the same approvers as any other week. What changes at quarter-end is the give-get: a signature date inside the quarter is something the customer can give in return, and it belongs in the request. If you relax the bands in the final weeks instead, buyers learn the calendar and hold their signatures until you do.

How often should you change the discount bands?

Review them each quarter and change them rarely. Look at the discount on won and lost deals, the share of quotes that needed approval and the turnaround time. If most requests land in one tier, move the band rather than approving the same exception again. A policy that changes every month is a policy reps stop reading.