How to compare a customer PO with the accepted quote

A matching total does not mean the PO matches the quote. The buyer can collapse ten quote lines into one line, add an option through an attachment, change the delivery event, replace a specification and incorporate purchasing terms that rewrite payment, warranty or liability.

The comparison must answer one business question: what would the company accept if it processed this PO as written? A field diff cannot answer that. The team needs the accepted offer, the complete incoming order, rules for matching unlike structures and a named disposition for every material change.

This method gives an industrial OEM a repeatable way to perform that review. It works for PDFs, spreadsheets, EDI orders and portal submissions, and it preserves the source behind every result.

Lock the two baselines first

Select one accepted offer and one incoming order revision before comparing anything. The offer baseline usually includes the released quote, technical proposal, option schedule, clarification record, approved commercial exceptions and submission evidence. The order baseline includes the customer PO, attachments, buyer terms, portal data and the email that delivered them.

Do not compare the PO with “the latest quote” unless the buyer accepted that revision. CRM may contain a later internal scenario, an expired draft or a revision that sales never sent. Record why the selected offer represents the customer’s acceptance: quote number, revision, email, portal event, signed proposal or other evidence.

Freeze both packages for the review. A later PO revision creates a new comparison against the current accepted order position. It does not replace the evidence from the first review.

Build a source register before extracting values

List every file and message in both packages. Include hidden workbook sheets, embedded terms, drawings, schedules, addenda and links named in the documents. A PO line that says “per specification 3017 Rev H” makes that specification part of the commercial review even when the price and quantity fields look clean.

Record the file name, document number, revision, issue date, source, received time and relationship to the transaction. Mark a document missing when the PO references it but the buyer did not supply it. Do not substitute a similarly named file from a shared drive without review.

ASME Y14.35 defines practices for identifying and recording revisions to engineering drawings and related documents. The PO comparison should respect those revision identities instead of comparing file names alone.

Normalize values without erasing what the customer wrote

Create normalized values for comparison and preserve the original text beside them. Convert dates to one format, amounts to numeric values and units to a controlled set. Resolve customer part aliases against the item master. Show the source unit, currency, date phrase and description beside the normalized value.

Normalization should support calculation, not manufacture agreement. “40 weeks ARO,” “June 15 delivery” and “required on site by June 15” may point to different start and finish events. Convert what you can and flag the unresolved meaning. Do not force them into one date field.

Apply currency and unit conversions with named rates and factors. A converted value can help compare two lines, but the team must still decide which currency, unit and rate basis govern the order.

Compare header identity and order references

Verify the legal customer, purchasing entity, sold-to account, bill-to account, ship-to site, buyer contact, seller entity, currency and customer PO identity. A familiar company name can mask a different legal entity or destination with different tax, export, credit and contract treatment.

Match the PO to the offer through explicit references first: quote number, proposal number, project name, opportunity, customer equipment tag and site. Use amount and text similarity only to find candidates. A high similarity score does not prove the buyer accepted that quote.

Check for duplicates across channels. The same order can arrive by email, EDI and portal. Use PO number, revision, customer identity, line content and source events to create one review with several receipts.

Match lines by business meaning

Line numbers rarely align. The quote may separate equipment, controls, commissioning and spares while the PO uses one lump-sum line. The buyer may use its own material code, combine options or split one quoted quantity across delivery dates. Match the commercial meaning before comparing field values.

Use a matching hierarchy: direct quote-line reference, agreed customer-to-seller item cross-reference, exact configured-product identity, unique option or service identity, then a reviewed combination of description, quantity, amount and context. Do not let a language model declare a match without showing the evidence.

X12’s purchase-order flow shows how an 850 can carry price, dates, delivery schedules and product subline detail for kits. A structured line can still represent several internal quote lines. Preserve the many-to-one or one-to-many relationship.

Compare quantity, unit, price and currency together

Compare quantity, unit of measure, unit price, extended price, currency, discount and price basis on the same row. A line can have the right total and the wrong quantity. A buyer can copy a unit price but change feet to meters. A lump-sum price can hide an option that the quote priced separately.

Recalculate extensions from normalized quantity and unit price. Compare the stated extended amount with the calculated amount and the quote. Preserve rounding rules and decimal precision. Route any unexplained difference even when it falls below a percentage threshold.

Check price validity and escalation assumptions. If the PO arrives after the quote expires, the numeric price may match while the supplier, commodity, freight or exchange-rate basis no longer holds. Expiry is a decision trigger, not a formatting difference.

Reconcile the total from the bottom up

Rebuild the quote total and PO total from their lines, discounts, freight, tax, allowances, charges, deposits and options. Then bridge one total to the other. Do not accept a matching grand total until every component has a place.

The buyer may remove a quoted freight line and add the same amount to equipment, include tax that the quote excluded, or net a deposit against the order total. Those structures affect invoicing and revenue even when the payable amount appears unchanged.

Use a suspense row for unexplained value. Never force the difference into a generic adjustment to make the totals tie. The business finishes the comparison after it can explain the entire bridge.

Compare scope, options, assumptions and exclusions

Read the words that define what the company will deliver. Compare the base scope, selected options, alternates, quantities, services, documentation, training, installation, commissioning, spares and freight. Then compare assumptions, customer responsibilities and exclusions that shaped the price and schedule.

A buyer can add scope without adding a line. “Per specification” may pull in tests or documents that the proposal excluded. “Complete system” may conflict with a quoted battery limit. A PO note can include every option while the amount covers only the base offer.

Map each scope difference to the cost, schedule, configuration and proposal decision it affects. The reviewer needs the business effect, not a redlined sentence alone.

Compare every technical document by revision

Build a document matrix for drawings, specifications, data sheets, standards and customer procedures. Compare the document number and revision in the accepted proposal with the PO package. Mark added, removed, superseded and missing documents.

Then compare the changed requirements inside the new revision. A revision bump can alter materials, voltage, hazardous-area classification, test requirements, documentation or cybersecurity. Route the affected requirements to engineering and show the downstream cost and schedule records that depend on them.

Do not let a newer file automatically win. The customer may have attached an obsolete drawing by mistake or issued a later revision after the quote. The team must identify the intended governing set and price any change before acceptance.

Define what every date means

Compare the event, date, start condition and dependency. Quote language such as “42 weeks from receipt of order and approved drawings” does not match a PO that requires arrival on site 40 weeks after its issue date. Shipment, arrival, installation complete and site acceptance are different commitments.

Compare delivery terms and named places with the schedule. A move from FCA seller plant to DDP customer site changes freight, customs, tax, risk, timing and logistics responsibility. The date comparison must include that commercial basis.

Check each line schedule as well as the header. A customer can split one quantity across dates or add a required-on-site date in a portal field. The review should show requested, quoted and currently supportable dates together.

Compare payment and billing mechanics

Compare payment amounts, percentages, trigger events, invoice timing, due dates, currency, retainage, deposits, security instruments and customer setoff language. “Net 60” tells only part of the story. Net 60 from invoice differs from net 60 after site acceptance.

Reconcile milestone percentages and fixed amounts to the order total. Check whether the PO moved a milestone, made customer approval discretionary or added documentation that the seller must submit before invoicing. Calculate the cash effect and funding gap when the terms change.

Link each accepted billing trigger to evidence the project can produce. If the PO requires a signed FAT certificate, the order handover should create that deliverable. A term buried in the comparison should not surprise finance at invoice time.

Compare the terms that sit outside the line table

Review warranty, acceptance, performance guarantees, delay damages, liability, indemnity, insurance, cancellation, termination, intellectual property, confidentiality, governing law and dispute terms. Include buyer terms incorporated by reference and portal click-through terms that apply to the order.

In the United States, UCC 2-207 addresses additional or different terms in an acceptance or written confirmation, including material alterations and objections. The legal result depends on the documents, parties, governing law and conduct. Counsel should define the company’s review and response rules. The comparison should find and explain the changed language.

Compare obligations by meaning. A quote may state a 12-month warranty in the commercial schedule while the PO incorporates a 24-month warranty through buyer terms. A paragraph-number comparison would miss it. The review should show duration, start event, coverage and remedy together.

Classify each difference by its business effect

A text diff shows that words changed. The review must show what the change does. Classify each difference as identity, scope, configuration, price, cost, schedule, payment, legal, quality, tax, logistics or data. One difference can carry several effects.

Give the difference a source on each side, materiality, owner, due date and disposition. Link related differences into one issue. A new material specification may change engineering, supplier price, lead time, selling price and warranty. Five isolated red rows will not help the team decide it.

State the release impact. Some differences block the whole order. Some block one option, purchase package or billing event. Some need a customer correction. Some fit an approved tolerance and can clear automatically.

Use tolerances only where the company has made a policy decision

Create tolerances for differences the business has chosen to accept: rounding, approved customer aliases, date format, address punctuation or a small tax calculation that the tax system will recompute. Name the rule, scope, owner and effective date.

Do not use a broad percentage threshold for price, quantity or schedule. A $100 change can add an unsupported service. A two-day move can trigger delay damages. A one-character drawing revision can change the product. Materiality depends on meaning.

Log every auto-clear with its rule and source values. Sample cleared rows and measure later corrections. If reviewers repeatedly override a rule, revise the policy instead of teaching users to ignore the result.

Resolve differences with explicit dispositions

Route each issue to the person who can commit the company. Sales operations owns transaction identity. Engineering owns technical scope. Estimating and sourcing own cost. Operations owns supportable dates. Finance owns cash and credit. Legal or an authorized commercial owner handles contract language. One order-release owner closes the package.

Use a controlled disposition: accept as ordered, accept under an approved tolerance, reprice, reschedule, request customer correction, issue a qualified acknowledgment, reject, or hold. Record the decision, reason, authority, conditions and affected order revision.

Resolve dependencies in order. Engineering must define the technical effect before estimating can price it. Sourcing may need to refresh a supplier quote before operations can commit a date. Run independent decisions together, but do not ask finance to approve margin on an unknown cost.

Turn the comparison into a customer response

Prepare a concise variance schedule or order acknowledgment from the approved dispositions. Reference the customer PO and revision, seller quote and revision, affected lines, agreed price, dates and qualifications. State what the customer must change or accept.

GS1’s purchase-order response specification supports acceptance, proposed amendment or rejection for all or part of an order. The structure reflects the real business decision: the seller may accept some lines while changing or rejecting others.

When the buyer issues a revised PO, compare it with the seller’s current accepted position and the prior PO. Confirm that the revision resolves the open items and did not introduce new ones. Close each issue with evidence before sales-order release.

Worked example: one conveyor-system PO hides eleven changes

A bulk-material equipment maker issues Quote Rev 5 for a conveyor and dust-control system. The $3.18 million base price includes conveyors, controls, FAT and commissioning. A corrosion-resistant package costs another $145,000. The offer promises shipment 42 weeks after advance payment and approved layout drawings, FCA the seller’s plant. Payment is 30% at order, 60% before shipment and 10% after site acceptance. Warranty runs 12 months after commissioning with an 18-month shipment limit.

The customer sends PO Rev 0 for one $3.18 million line and references the quote. The total matches. The attachments and terms do not. The PO includes the corrosion package, references Process Specification Rev H instead of quoted Rev F, requires delivery to site in 40 weeks from the PO date, changes freight to DDP, moves payment to net 90 after SAT, extends warranty to 24 months after SAT and adds delay damages of 0.5% per week with a 10% cap.

The comparison registers the PO, buyer terms and four technical attachments. It maps the lump-sum line to the three base quote lines and the unselected option. It finds eleven material differences across scope, document revision, schedule, delivery, payment, warranty, damages and customer responsibilities. A matching-total rule would have cleared the order.

Engineering compares Rev H with Rev F and finds a new washdown requirement, stainless cable tray and a changed dust classification. Estimating adds $85,000. The corrosion package adds $145,000. Logistics prices DDP at $67,000. Operations can commit shipment in 46 weeks after approved layouts. Finance rejects net 90 after SAT. Legal rejects the damages and 24-month post-SAT warranty.

The seller returns a variance schedule and Quote Rev 6 for $3.477 million. The customer issues PO Rev 1 for that amount, selects the corrosion package, accepts the Rev H technical additions and DDP freight, restores 30/60/10 payment, accepts 46-week shipment from layout approval, returns to the original warranty and removes delay damages. The second comparison closes all eleven issues and releases the order.

Use one comparison record through release

The final record should contain the two baselines, source register, line mapping, field and clause differences, linked issues, decisions, customer responses and release result. Do not export a redline, email it around and rebuild the answer in ERP.

Create the sales-order draft from the accepted quote, then apply the approved differences. Link the PO, proposal, comparison and acknowledgment to the order. Send the released technical sources and remaining owned work into engineering handover.

Retain the comparison after release. When a dispute, change request or margin problem appears, the team can see what the buyer sent, what the seller offered, who approved the difference and what entered execution.

How Bourne compares the PO with the quote

Bourne identifies the accepted quote and proposal, captures the customer PO and attachments, and builds a source register for both packages. It maps unlike line structures, normalizes units and dates, and shows each comparison beside the original evidence.

The review covers customer identity, items, quantities, price, options, technical documents, delivery, payment, warranty and other terms. Each material difference shows its business effect, owner, dependent decisions and allowed dispositions. A changed specification can reopen configuration, supplier, cost and schedule work in the same case.

Approved results update the customer response and sales-order draft. Unresolved material differences block only the work they affect. After release, Bourne links the comparison to the ERP order and passes the current technical and commercial baseline into sales-to-engineering handover.

Buğra Gündüz

Buğra Gündüz is the co-founder and CEO of Bourne and co-founder of HockeyStack. He built HockeyStack into an eight-figure AI business. At Bourne, he works with entrepreneurs and established companies to create AI products and services.