Skip to content

Systems and records

Who accepted the change? A purchase order delivery exception dataset

By SourceX Editorial · Reviewed by Noah Loul ·

9 sections

Short answer

A purchase order delivery exception dataset should treat a delivery that differs from a correct order as a decision, not a receipt. Keep the approved order version untouched, record what actually arrived (a substitute, a different quantity, a drifted specification, a new carrier or route), and name who accepted the difference, under which authority, with what adjustment, and whether acceptance was explicit or happened because nobody rejected in time.

Checklist

Purchase order delivery

This page covers who accepted the change? A purchase order delivery exception dataset.Illustrative

Key takeaways

  • Receiving counts what arrived; acceptance is a separate act by someone with authority, and the record has to show both.
  • Under UCC 2-606, goods can be accepted by failing to make an effective rejection, so a dataset needs an acceptance mode as well as an acceptor.
  • FAR 46.407 ties who may accept a nonconforming delivery to its severity: critical or major cases need the contracting officer and technical concurrence.
  • An ERP tolerance is authority granted in advance; record its value and source at receipt, and flag tolerances raised after the goods arrived.
  • A carrier change can be a required substitute under UCC 2-614 rather than an exception, so establish the reason before grading the response.
  • Grade authority and severity before speed: accepting fast to keep a line running still fails if the wrong person said yes.

What does a delivery exception record need when the order itself was right?

It needs four linked states: the order as approved, the delivery as tendered and counted, the acceptance decision with its actor and authority, and the consequence, meaning any price adjustment, credit, return or downstream failure. When the order was correct, the whole exception lives between the second and third states, so a record that keeps only the receipt cannot teach a model anything about the decision.

This page covers four kinds of change that originate at the delivery: an item substituted for the one ordered, a quantity outside what the order allowed, a specification, grade or lot that drifted from the ordered one, and a carrier, route or ship-from point the order did not name. Three neighboring problems have their own pages and are left out here: a short receipt that leaves a line open or closed, a new delivery date on its own, and a change made to the order that downstream parties may not have seen.

The inclusion test is one question: could the receiving clerk truthfully have written that what came was not what the order said? If so, someone made a call about the difference, even if the call was silence. The dataset exists to recover that call and the authority behind it.

Receiving is not accepting: how the rules separate counting from saying yes

Receipt is a physical fact; acceptance is a commercial and legal act, and the two are often done at different times by different people. FAR 46.101 defines acceptance as the act of an authorized representative of the Government by which it assumes ownership of tendered supplies or approves services rendered, and FAR 46.502 makes acceptance the contracting officer's responsibility unless that duty is assigned to a contract administration office or another agency. The receiving dock appears in neither rule.

Commercial EDI draws a similar line. X12's supply chain overview says its 861 transaction was created so the receiver can notify the sender of the product actually received, answering the 856 ship notice in which the seller describes what it delivered. A dataset that stores the counted quantity as if it were the decision has merged two events the messages keep apart.

Sales law adds the hardest case. Under UCC 2-606, a buyer accepts goods when it signals, after a reasonable opportunity to inspect, that they conform or will be kept despite a defect; when it fails to make an effective rejection after that opportunity; or when it acts inconsistently with the seller's ownership. Under 2-607(3)(a), once goods are accepted, the buyer must notify the seller of a breach within a reasonable time after discovering it or be barred from any remedy. An acceptance can therefore exist with no signature at all, and a dataset that records only explicit approvals will leave those episodes mislabeled as still pending.

Four ways a delivery departs from a correct order, and what makes accepting it wrong

The matrix below is the core of the design. Each row is a change type; the columns name what the receiving record usually shows, the constraint that can make an accept-and-move-on response wrong, the role that should hold the decision and the evidence that the decision was made. It is editorial guidance built from the rules cited on this page, not a measured distribution, and a buyer should map it onto its own approval policy before labeling anything.

Four ways a delivery departs from a correct order, and what makes accepting it wrong
Change at deliveryWhat the receipt usually showsConstraint that can make acceptance wrongWho should decideEvidence the decision happened
Item substitutedA different item number or description on the packing list, often with a supplier noteThe substitute is not on the approved alternates list, or it changes fit, safety or a customer-specified partThe requirement owner in engineering or quality, not receivingA dated approval naming the substitute, plus any price or warranty adjustment
Quantity outside the orderA counted quantity above or below the line, inside or outside toleranceOver-receipt beyond tolerance creates stock and a payable nobody approved; under-receipt can break a kit or a buildThe buyer of record within tolerance; the budget holder beyond itThe tolerance in force at receipt, or a written exception with its approver
Specification, grade or lot driftThe same item number with a different grade, revision, lot, expiry or certificateA customer or regulatory requirement depends on the ordered grade or lotQuality with technical concurrence; the contracting authority for critical or major casesA nonconformance report with severity, disposition and any price reduction
Carrier, route or ship-from changeA different carrier code, route or origin on the ship notice or bill of ladingFreight cost, risk of loss, hazardous material handling or customs status moves with the routeThe logistics owner, plus the buyer when cost or terms shiftNotice before shipment, the stated reason and any freight adjustment

Severity sets the signature: borrowing the federal acceptance ladder

Who may accept a nonconforming delivery should depend on how serious the departure is, and the federal rules supply a tested ladder. FAR 46.407 tells contracting officers to reject supplies that do not conform in all respects, ordinarily to let the contractor correct or replace them within the delivery schedule, and to accept critical or major nonconformances only after a determination based on the technical activity's advice that the item is safe and will perform, facts about the nonconformance, any contractor request, a recommendation with its rationale and the contract adjustment considered appropriate.

The same section moves smaller problems down the chain: for a minor nonconformance, the contract administration office may decide unless the contracting office withholds that authority. FAR 46.101 defines the scale. Critical means likely to create hazardous or unsafe conditions or to prevent performance of a vital mission; major means likely to cause failure or materially reduce usability; minor means not likely to materially reduce usability.

Two more rules belong in any schema. When critical or major nonconformances are accepted, FAR 46.407(f) requires a contract modification for an equitable price reduction or other consideration, while a minor one needs no modification unless the contractor's savings would exceed the cost of processing it. Under 46.407(g), rejection notices must state reasons and go out promptly, because a late notice can make acceptance implied as a matter of law. Severity, authority, consideration and notice timing are four fields, not one comment box.

These citations are to the FAR as codified through Federal Acquisition Circular 2025-06 in GSA's published FAR repository. Under the FAR overhaul, agencies are adopting rewritten Part 46 text by class deviation, and the Nuclear Regulatory Commission's memo says the definitions at 46.101 are retained. Private buyers are not bound by any of it; the ladder is simply a worked-out answer to which signature a label should require.

Tolerance settings are approvals given before the delivery arrived

Most within-limits changes are never approved by anyone at the dock, because a tolerance approved them in advance. SAP's support note on purchasing tolerances says over- and underdelivery tolerances can be set on the purchase order item's delivery tab, that no message is issued while the delivered total stays within the overdelivery tolerance, that exceeding it raises an error, that falling below the underdelivery tolerance raises a warning, and that an unlimited overdelivery indicator lets any overdelivery through without a message.

In the dataset, the tolerance is the authority, so capture it like any other approval: its value at the moment of receipt, where it came from (order item, info record or material master), who set it and when. A receipt inside tolerance with no record of the tolerance is unlabeled, not accepted.

The same documentation shows how the evidence of an exception disappears. SAP's note on error 06073, raised when the delivered quantity exceeds the ordered quantity plus tolerance, suggests increasing the overdelivery tolerance limit or setting the unlimited overdelivery flag. Either fix may be legitimate, and either turns a delivery exception into a receipt that looks routine unless the change history survives. Flag any tolerance edit dated after the goods arrived, label the episode order rewritten after receipt, and never treat the edited order as the original.

Carrier and route changes: exception, cure or required substitute?

A new carrier is not automatically a deviation to reject. UCC 2-614(1) provides that when, without fault of either party, an agreed type of carrier becomes unavailable or the agreed manner of delivery becomes commercially impracticable, a commercially reasonable substitute that is available must be tendered and accepted. In that situation the buyer has no right to refuse a reasonable substitute, so labeling it an unauthorized change would teach a model the wrong rule.

The right label therefore depends on the reason, which shipment records rarely state. A carrier switched because the agreed one stopped serving the lane is substitute performance; a switch made for the seller's convenience that shifts freight cost or risk to the buyer is a change the buyer may accept, reject or price. The packet needs the agreed carrier or method, the notice and when it came, the stated reason and any freight or risk adjustment.

Rejected items follow a related rule. Under UCC 2-508, when a tender is rejected before the time for performance has run out, the seller may seasonably notify the buyer and cure within the contract time, and a seller who had reason to believe a nonconforming tender would be accepted may get a further reasonable time to substitute a conforming one. A rejected substitute followed by a conforming replacement is one episode with two tenders, and the dataset should keep both instead of only the final receipt.

The delivery exception packet: twelve fields and seven acceptance labels

Each packet covers one order line and one delivery event, assembled from order history, ship notices, receiving, quality and payables records, with people replaced by role tokens. The fields are the minimum; the seven labels in the table describe how acceptance actually happened, which is the variable a model most often gets wrong when it sees only the receipt. The list and table below make up the packet:

  • Order snapshot: the approved line as of the order date, with its version number and approver role, never the current version
  • Tender: ship notice or packing list values for item, quantity, specification or lot, carrier and origin
  • Receipt observation: counted quantity, item and lot as recorded at the dock, with the time
  • Change type: substitution, quantity, specification or lot, carrier or route; an episode can carry more than one
  • Severity: critical, major or minor, with the basis for the class
  • Standing authority: the tolerance and its source, an approved alternates entry or a contract clause in force at receipt
  • Decision: accept, conditionally accept, reject, return or accept with an adjustment
  • Decider: role, authority source and time relative to the receipt
  • Notice: whether and when the supplier was told, and the reason given
  • Consideration: price reduction, credit, replacement or none, linked to the invoice outcome
  • Downstream outcome: used, failed, returned or reworked, with the record that shows it
  • Integrity flag: any change to the order, tolerance or receipt dated after the goods arrived
The delivery exception packet: twelve fields and seven acceptance labels
Acceptance labelWhat the record must showCommon mislabel
Accepted by authorized decisionA dated approval from a role whose authority covers the change and its severityAny approval treated as valid whoever gave it
Accepted within standing toleranceA tolerance, alternates entry or clause in force at receipt that covers the changeTolerance read from today's settings instead of the receipt date
Conditionally acceptedAcceptance tied to a correction by a set date, with any amount withheldLogged as a plain acceptance once the goods were used
Accepted by inactionNo effective rejection within a reasonable time after inspection was possibleLeft open as a pending exception indefinitely
Rejected or returnedA rejection notice with reasons, its date and the dispositionA return with no notice counted as a timely rejection
Accepted without authorityAcceptance, including use of the goods, by a role whose authority did not cover the changeCounted as a valid acceptance because the goods were kept
Order rewritten after receiptThe order, tolerance or receipt edited after arrival with no acceptance recordTreated as a clean receipt with no exception at all

Fast acceptance is not a correct answer: grading one illustrative case

The strongest alternative to this design is that the business objective is throughput, so the best response to any usable delivery is to accept it quickly. That view fails whenever a constraint the dock cannot see is binding. Grade each episode first on whether the response respected the constraint and the authority, then on cost and time, never the other way round.

Illustrative case, not a real record: an order for 400 stainless fittings against a customer drawing that names grade 316 arrives complete and on time, but the certificate shows grade 304. Receiving posts all 400 within ten minutes because the count matches. On day 2 a planner issues 120 fittings to a job. On day 4 quality opens a nonconformance report and classes it major, because the customer specification depends on the ordered grade, and the requirement owner rejects the remaining 280 with a written notice. The supplier later ships a conforming replacement within the contract time and credits the 120 already used, which are scrapped and rebuilt.

A model that answers accept because the count matched and the line was waiting gets the speed right and everything else wrong. The correct labels are accepted without authority for the 120 fittings used before anyone with authority decided and rejected or returned for the 280, and the replacement is kept as a second tender in the same episode. Score the severity and authority calls as pass or fail, and record the hours from receipt to decision separately, so a fast wrong answer can never outscore a slower right one.

A swimlane timeline of the illustrative fittings case: receiving posts 400 units on day 0, a planner issues 120 on day 2, quality rejects 280 on day 4, and the supplier sends a replacement and credit later, with the acceptance labels for the 120 used (accepted without authority) and the 280 rejected (rejected or returned) and the replacement marked as a second tender.
One delivery exception, four lanes, two acceptance labels and a second tender. Illustrative case, not a real record.

Requesting delivery exception episodes, and where this design stops

A buyer asking SourceX for this kind of dataset should state the change types it needs, the systems that hold order history and change logs, the minimum share of episodes that must carry a named decision role and authority, and the acceptance test it will run on a sample. SourceX looks for a dataset only after a buyer's request arrives, sourcing it from U.S. businesses, so the request should also carry the volume, language and format wanted, the timing and the license the model work needs. Whether a particular company's archive holds complete episodes is established during sourcing, not assumed.

The legal rules cited here are general information, not legal advice: the UCC applies as each state enacted it, the FAR governs federal contracting rather than private buyers, and counsel should review any specific acceptance or rejection question. Receiving notes often hold employee names and negotiated prices, so packets should use role tokens and treat supplier pricing as confidential before any licensing review.

The design cannot recover a decision nobody recorded. If an order was edited after receipt and the change log is gone, the honest label is order rewritten after receipt, and those episodes belong in an uncertainty bucket for evaluation, not in training data as clean acceptances.

Frequently asked questions

What is a purchase order delivery exception dataset?

A set of order-line episodes in which a correct purchase order met a delivery that differed from it, each recording the approved order version, what arrived, who accepted or rejected the difference, under which authority and with what adjustment. It is built to teach or test the acceptance decision, not the receiving count.

Is a goods receipt the same as acceptance?

No. A goods receipt records what was counted; acceptance is an act by someone with authority, and under UCC 2-606 it can also happen when a buyer fails to make an effective rejection after a reasonable chance to inspect. In federal contracts, FAR 46.502 places acceptance with the contracting officer, not the receiving dock.

Does a delivery inside the ERP tolerance need an approval?

It already has one: the tolerance, set in advance by whoever owns the order or the master data. Record the tolerance value and its source as of the receipt date, and flag any tolerance raised after the goods arrived, since SAP's own note on error 06073 suggests raising the tolerance to clear an overdelivery error.

How is this different from a partial delivery or late delivery record?

A partial delivery record tracks open, received and canceled quantities on a line, and a date-change record tracks a new promised date. This design starts where the order was correct and something else changed at delivery: the item, a quantity outside tolerance, the specification or lot, or the carrier or route.

Should a carrier change be labeled an exception?

Only once the reason is known. Under UCC 2-614, if the agreed carrier becomes unavailable without either party's fault, a commercially reasonable substitute must be tendered and accepted, so the change is substitute performance. A switch for the seller's convenience that moves cost or risk to the buyer is a change the buyer may accept, reject or price.

Sources

  • FAR 46.101 (as codified through FAC 2025-06) defines acceptance, conditional acceptance and critical, major and minor nonconformance. Source
  • FAR 46.407 sets when contracting officers reject, allow correction, or accept nonconforming supplies, who decides minor cases, the price reduction rule and prompt rejection notices. Source
  • FAR 46.502 makes acceptance the contracting officer's responsibility unless assigned to a contract administration office or another agency. Source
  • The Nuclear Regulatory Commission's FAR overhaul class deviation for Part 46 states that all definitions at 46.101 are retained. Source
  • UCC 2-606 sets out what constitutes acceptance of goods, including failure to make an effective rejection after a reasonable opportunity to inspect. Source
  • UCC 2-607(3)(a) requires a buyer who has accepted goods to notify the seller of breach within a reasonable time or be barred from any remedy. Source
  • UCC 2-614(1) requires a commercially reasonable substitute to be tendered and accepted when the agreed carrier becomes unavailable without either party's fault. Source
  • UCC 2-508 lets a seller cure a rejected tender within the contract time, or substitute a conforming tender in a further reasonable time, after seasonable notice. Source
  • SAP's support note explains under- and overdelivery tolerances on purchase order items, the messages they trigger and the unlimited overdelivery indicator. Source
  • SAP's note on error 06073 suggests increasing the overdelivery tolerance limit or setting unlimited overdelivery when a receipt exceeds order quantity plus tolerance. Source
  • X12's supply chain transaction flow describes the 856 ship notice and the 861 receiving advice that lets the receiver report the product actually received. Source

Tell us what data you need

Share scope, volume, format, timing and licensing needs. Datasets are sourced on request.

See if your company qualifies