Skip to main content
← All posts
By Abhay Muttreja, Founder, SolvTreeAI

Who can change a quoted price after the customer says yes?

How to control price changes after a quote is accepted: quote versions, authorisation limits, invoice matching and an exception trail.

·4 min read
  • Quote Management
  • Approval Workflows
  • Invoice Controls

The short answer

After a customer accepts a quote, nobody should be able to change the price without creating a new version, recording a reason and getting approval from someone with the authority for that amount. The invoice should then be checked against the latest approved version, not against whatever is in someone’s inbox. You need a small, strict record to do this. You need a full ERP only when quoting, purchasing, project costing and invoicing all depend on each other.

Key points

  • An accepted quote is a commitment. Changes to it are commercial decisions, not edits.
  • Every change needs a new version number, a reason, the person who requested it and the person who approved it.
  • Approval limits should depend on the size of the change, not on who happens to be in the office.
  • The invoice must match the latest approved version. Any difference is an exception that someone reviews.
  • Start with the minimum record. Move to a connected system only when the work genuinely spans several departments.

Why prices move after yes

In quote-led businesses, the accepted price rarely survives untouched. Scope grows. Material costs move. The customer asks for a substitution. A site condition turns out to be different from the survey. Some of these changes are legitimate and some are mistakes, and without a record the two look identical on the invoice.

The risk runs both ways. If prices change without approval, margin leaks quietly. If nobody can change anything without the owner’s personal sign-off, jobs stall and customers wait.

An illustrative example: a fit-out contractor in Dubai

Consider a hypothetical interior fit-out contractor in Dubai working on a 2,000 square foot office. All figures below are illustrative.

  1. Version 1, quote issued. The estimator prices the job at AED 310,000, including partitions, ceilings, flooring, lighting and joinery. The client accepts in writing.

  2. Change request. During works, the client asks to upgrade the flooring in the meeting rooms to engineered wood. The site manager agrees verbally on site and tells the estimator by phone.

  3. Version 2, drafted. The estimator adds AED 18,500 for the flooring upgrade. They also notice the original quote under-priced the glass partitions by AED 6,000 and quietly add that too, since “we are revising anyway”.

  4. Approval. The contractor’s rule says changes under AED 10,000 can be approved by the project manager, and anything above needs the commercial manager. The total change is AED 24,500, so it goes to the commercial manager, who approves the flooring as a client-requested variation but rejects the partition correction. The original price was accepted; correcting the contractor’s own error after acceptance is a commercial conversation with the client, not a silent addition.

  5. Version 3, approved. The quote becomes AED 328,500. The client receives the variation for signature.

  6. Invoice. Accounts prepares the final invoice from the project file, which still holds Version 2 at AED 334,500. Because the invoice is checked against the latest approved version, the AED 6,000 difference is flagged as an exception before it reaches the client.

Without versioning, step 3 would have reached the client as a single revised figure, the partition correction would have been buried, and a dispute would have followed at final account.

The minimum record

For each quote, keep one record that holds:

  • Quote number that stays the same across versions.

  • Version number, incremented on every change after acceptance.

  • Line items with prices for each version, so differences can be compared line by line.

  • Change reason for each modified line: client request, site condition, cost change, error correction.

  • Requested by, with date.

  • Approved by, with date, and the approval limit that applied.

  • Client acceptance of each version that changes the price, with a copy of the signed variation.

  • Invoice reference linked to the approved version it bills against.

This can live in a well-controlled spreadsheet with locked versions, a quoting tool, or a small custom component. The format matters less than two rules: versions cannot be overwritten, and invoices are matched against them.

Approval and exception rules to write down

Before choosing any software, agree these:

  1. Who can request a change to an accepted quote.

  2. Approval limits by amount or percentage, and by type (a client variation may follow different rules from an internal error correction).

  3. Whether a price can ever go up without the client signing a variation. Most businesses should answer no; check your contract terms with an adviser.

  4. What happens when the invoice and the approved version differ: who reviews, within what time, and who can release it.

  5. Who can see margin on each version, and who can see only the selling price.

Then test them. Create a synthetic quote, make three changes of different sizes and types, and check that each one routes to the right approver, that no version can be edited after approval, and that a mismatched invoice is caught.

When a connected system is justified

A versioned quote record solves the price-change problem on its own. A fuller system becomes worth it when the same job also needs purchase orders matched to quote lines, subcontractor costs tracked against budget, progress billing against milestones, and live margin visible to the commercial team. At that point, keeping each piece in a separate tool creates more reconciliation work than it saves. For more on what that looks like, see our post on the AI-native ERP.

Where SolvTree fits

This maps to our custom systems and AI-native ERP work: from a single quote-versioning and approval component to a connected system covering quotes, procurement, job costing and invoicing. We start with one approval-heavy workflow and build the smallest system that controls it.

Next step: Bring one approval-heavy workflow to a free 30-minute operational audit and find its smallest useful system with us. The report is yours to keep.

Frequently asked questions

What should happen when an accepted quote changes?
Create a new version with line-level changes, reasons, requester and authorised approver. Record the customer’s acceptance of price-changing variations and preserve earlier versions.
Which quote version should an invoice match?
Match the invoice to the latest approved and customer-accepted version it bills against. Route any price or quantity difference to a named reviewer before releasing the invoice.