Systems and records
Supply chain partial delivery data: partial receipt vs closed order
By SourceX Editorial · Updated
9 sections
Short answer
Treat a partial delivery as a change in the order line's state, not as the end of the order. A procurement record should keep ordered, received, canceled and still-open quantities separately, and mark closure only when there is evidence for it: a delivery-completed flag, a canceled remainder with a reason, or a closed line. This guide gives the field set and outcome states that keep the two apart.
System export
Supply chain partial
Key takeaways
- A short receipt records what arrived; it does not record whether the rest is still expected.
- Closure is a recorded decision, such as a completed flag, a canceled remainder or a closed line, and needs its own evidence.
- Keep ordered, received, canceled and open quantities separately at every event and make them reconcile.
- Read state from order lines, not headers or invoices.
- Link specification, supplier approval, customer and change constraints so substitutions and waits make sense.
How should procurement records separate partial delivery from order closure?
Keep the quantity that arrived and the decision about the rest as two different facts. A receipt below the ordered quantity tells you what reached the dock; it says nothing about whether the buyer still expects the remainder, has canceled it, or has accepted the shortfall and closed the line.
The major ERP systems already model this distinction, which is why a dataset should not flatten it. In SAP, the delivery completed indicator marks a purchase order item as closed with no further goods receipt expected, and setting it reduces the open quantity to zero even when the item was only partly delivered. NetSuite reports a separate Partially Received status while items are still outstanding, and its documentation describes closing individual lines by hand when the buyer does not intend to receive the open quantity.
Microsoft Dynamics 365 Supply Chain Management handles the remainder through the Deliver remainder option on the line, where canceling the remainder quantity closes out what is still expected, and Odoo asks, at receipt validation, whether to create a backorder for the missing quantity, always creates one, or cancels the remaining products, depending on how the operation type is configured. Four systems, four mechanisms, one shared idea: the end of a line is a recorded decision, not an inference from a short receipt.
Why can't a short receipt alone tell you how the line ended?
A received quantity below the ordered quantity is consistent with at least four different futures, and a model trained on the receipt alone learns to guess between them. The remainder may be on backorder and still due, it may have been canceled, the shortfall may sit inside an agreed underdelivery tolerance, or the supplier may have shipped a substitute under a different line.
Billing makes this harder. Odoo, for example, lets a product bill on received quantities, so a draft vendor bill is built from what arrived rather than what was ordered. A fully paid bill for a partly received line therefore does not mean the order is finished; it means the received part is settled.
Automatic closure adds another trap. SAP documents that the delivery completed indicator can be set by hand or automatically at goods receipt through Inventory Management Customizing, so the same short line can close by a buyer's decision in one plant and by a configured rule in another. Record whether closure was manual or automatic and any underdelivery tolerance in force at the time, because a shortfall inside it is a normal close and the same shortfall outside it is an exception someone approved.
The practical consequence for anyone preparing procurement records for analysis or AI use is simple. Do not derive outcome labels from the last receipt, the last invoice or a status snapshot taken on export day. Derive them from the explicit state changes on the line, and record which source event supports each one.
What should the order line and outcome state dataset include?
The asset below is a field set for one purchase order line across its life. Each row names the field, what it means, where it usually comes from and why it matters for telling partial delivery from closure. Field names are suggestions; keep the system's own codes in a separate column so nothing is lost in translation.
| Field | Definition | Typical source record | Why it matters |
|---|---|---|---|
| po_line_key | Stable identifier for the order line, plus the PO number and line number it came from | PO header and line tables | Every receipt, change and closure event must join back to exactly one line |
| ordered_qty and uom | Quantity and unit of measure on the line at the time of each event, not only the latest value | PO line history or change log | Quantity changes after a change notice otherwise look like shortfalls |
| received_qty_cum | Cumulative quantity received, built from individual receipt events | Goods receipts, item receipts, receiving transactions | The partial state is measured here, never inferred from billing |
| canceled_remainder_qty | Quantity explicitly canceled, with date and actor | Deliver remainder change, line close, backorder cancellation | Separates a decision to stop from a delay |
| open_qty | Ordered minus received minus canceled, recomputed at each event | Derived | Must reconcile to the system's own open quantity or the row is flagged |
| line_state | One value from the outcome state list in the next section | Derived from events, with source event id | The label a model or analyst actually uses |
| closure_evidence | The record that justifies a closed state: completed flag, close action, cancellation, full receipt | System flag or change event | A closed state with no evidence is a modeling guess |
| supplier_ack_status | Supplier acknowledgment at line level, such as accepted, quantity changed or rejected | EDI 855 or portal confirmation | Shows whether the shortfall was announced before shipping |
| shipment_refs | Advance ship notice and carrier references tied to each receipt | EDI 856, carrier tracking | Links what was promised in transit to what was received |
| constraint_refs | Specification revision, approved supplier status, customer constraint and change notice ids that governed the line | PLM, quality, contract and sales order records | Explains why an obvious replacement was not allowed |
Which outcome state did each order line end in?
Give every line exactly one current state, and keep the history of states with timestamps. The list below is deliberately small: seven states cover most procurement histories, and anything that does not fit goes to a review queue rather than into a catch-all value.
| State | Meaning | Evidence required | Labeling rule |
|---|---|---|---|
| open_unreceived | Nothing received yet; full quantity expected | Confirmed PO line with no receipts | Default until the first receipt event |
| partial_open | Some quantity received; remainder still expected | Receipt below ordered quantity and no cancellation or completion flag | Never label closed while a backorder or open quantity exists |
| closed_complete | Full ordered quantity received | Cumulative receipts equal or exceed ordered quantity | Overdelivery beyond tolerance is flagged separately |
| closed_short_accepted | Shortfall accepted and line closed | Completion flag or remainder set to zero with date and actor | Record the shortfall quantity and the stated reason if one exists |
| closed_remainder_cancelled | Remainder canceled by buyer or supplier | Cancellation event on the line or backorder | Keep who canceled; a supplier rejection is not a buyer decision |
| superseded_by_substitute | Remainder replaced by another item or line | Change notice or new line referencing the original | Link both lines; the substitute is not a receipt against the original |
| canceled_before_receipt | Line canceled with nothing received | Cancellation event before any receipt | Distinct from closed_remainder_cancelled for reporting |
| needs_review | Events conflict or evidence is missing | Reconciliation failure or unknown status code | Excluded from training labels until resolved |
Which constraint makes the fastest replacement the wrong one?
The tempting fix for a short delivery is to buy the missing quantity from whoever can ship fastest. That choice is invalid whenever a constraint on the line rules it out, and those constraints rarely sit on the purchase order itself.
A dataset that records only the PO and the receipts will make the fast substitute look like a missed opportunity. Recording the constraints as linked references lets a reader, or a model, see why the buyer waited, split the order or canceled instead.
- Specification revision: the drawing or specification revision on the line may differ from what an alternate supplier stocks.
- Supplier approval: the item may be restricted to approved or qualified sources, so an unapproved vendor cannot fill the gap without a quality decision.
- Customer constraint: the downstream sales order may forbid partial shipments, mixing lots or substituting brands.
- Change notice: an open engineering or contract change may freeze the quantity until it is resolved.
- Alternatives on record: a documented alternate part or second source, with its own approval date, is what makes a substitution valid.
- Delivery evidence: proof of what actually arrived, including inspection results, settles disputes about whether the shortfall was real.
How does one illustrative line move from two receipts to a canceled remainder?
The figures below are illustrative counts invented for this guide, not data from any company. One purchase order line orders 400 units. The supplier acknowledges it with a quantity change to 350, ships 250, then ships 100, and the buyer cancels the last 50 after the supplier confirms it cannot make them.
- The acknowledgment at event 2 does not change the ordered quantity; it is evidence that the shortfall was announced, which is a different label from a surprise short shipment.
- Between events 3 and 5 the line is partial_open for its whole life; a snapshot taken at event 4 would wrongly look like a short close if the open quantity were ignored.
- The closing state is closed_remainder_cancelled, not closed_short_accepted, because a cancellation event exists with an actor and a reason.
| Event order | Event | Quantities after event | Line state |
|---|---|---|---|
| 1 | PO line confirmed for 400 units | ordered 400, received 0, canceled 0, open 400 | open_unreceived |
| 2 | Supplier acknowledgment: quantity changed to 350 | ordered 400, received 0, canceled 0, open 400 | open_unreceived, ack flag set |
| 3 | Receipt of 250 units against ship notice A | ordered 400, received 250, canceled 0, open 150 | partial_open |
| 4 | Receipt of 100 units against ship notice B | ordered 400, received 350, canceled 0, open 50 | partial_open |
| 5 | Buyer cancels remaining 50 with reason supplier cannot supply | ordered 400, received 350, canceled 50, open 0 | closed_remainder_cancelled |
When does a closed-looking line still have quantity in play?
Closure flags are weaker than they look, so the dataset needs reconciliation checks rather than trust in a single field. SAP notes that goods receipts for remaining quantities can still be posted after the delivery completed indicator is set, although they no longer affect on-order stock. Dynamics 365 documents that when a delivery remainder is larger than the line quantity, the order-level Cancel action removes only the line quantity and the rest stays open, and that canceling only a remainder under change management sends the order straight to a confirmed state once approved.
At a glance
When does a closed-looking line still have quantity in play
NetSuite's header status can also mislead. Its documentation says that when some lines are fully billed and at least one is closed, the transaction shows as closed, but if an open line remains, the transaction takes that open line's status. Read state from lines, not headers.
- Quantity balance: ordered equals received plus canceled plus open at every event, within the unit of measure.
- Late receipt: any receipt dated after a closure event is kept and flagged, never dropped.
- Header versus line: a header status that disagrees with the line states sends the order to needs_review.
- Orphans: receipts or ship notices that do not join to a line are counted and reported, not silently discarded.
- Status code coverage: every system status code in the export maps to one outcome state, and unmapped codes are listed.
Which order lines should wait for a procurement specialist?
Some histories should not become labeled examples until someone who knows the purchasing process has looked at them. Narrow the scope instead of forcing a label when the evidence is thin.
Hold back lines where the unit of measure changed mid-order, where consignment or vendor-managed inventory blurs the receipt event, where quality inspection rejected goods after receipt, or where a blanket order releases quantities against a contract. Each of these can make a correct line look short, or a short line look complete. A data rights reviewer should also see any field that carries negotiated supplier pricing or contract terms, because those can be confidential to the supplier relationship even when the buyer controls the system.
What changes when order-line histories go to a licensing review?
If a company is considering licensing procurement and supply chain records for AI work, the line-level states above are what make those records useful: they show decisions under constraint, not just transactions. Being able to export the data, being permitted to share it under privacy rules, owning it and holding contractual rights to license it are four separate questions, and supplier agreements may restrict some fields regardless of who runs the ERP.
Manufacturers and distributors that go ahead can bring line-level purchasing history to SourceX, which runs the rights review, contract, preparation and delivery that make chosen records a licensed dataset. Qualification is checked with a short company assessment and no ERP export, and the company approves the scope and terms and signs before a single order line is handed over.
Was the buyer entitled to take part of the order when it did?
Only if the contract allowed delivery in lots, or the parties agreed a change that did. Under UCC 2-307, unless otherwise agreed, all goods called for by a contract for sale must be tendered in a single delivery, with payment due on that tender; where either party may make or demand delivery in lots, the price can be demanded lot by lot if it can be apportioned. UCC 2-612 calls a contract that requires or authorizes delivery in separate lots, each separately accepted, an installment contract.
Scope matters as much as size. The federal Variation in Quantity clause, FAR 52.211-16, makes the contracting officer name what a permitted variation applies to, such as the total contract quantity or each quantity in the delivery schedule, so the same short lot can be inside the allowance under one contract and outside it under another.
When urgency is the reason for taking part of a delivery, the urgency needs evidence of its own. Among the factors FAR 49.402-3 lists for deciding whether to terminate a late supplier is the urgency of the need and the time needed to get the supplies elsewhere, compared with the time the delinquent contractor needs. A decision packet should hold the same comparison: the dated record of the need, the alternate source's lead time and the supplier's promised date for the rest.
What does accepting part of a delivery do to the buyer's rights over the rest?
It can preserve them or give some away, depending on what the buyer says at the time. Under UCC 2-612(3), a party facing a breach of the whole contract reinstates it by accepting a non-conforming installment without seasonably notifying cancellation, or by demanding performance of future installments. On late deliveries, FAR 49.402-3(c) tells the contracting officer that if the government did anything that might be construed as waiving the delivery date, a notice must set a new date and reserve the government's rights.
The federal default clause shows the other paths. FAR 52.249-8 allows termination in whole or in part; the government may then buy the terminated supplies elsewhere and charge excess costs, while the contractor must continue the work not terminated, and no excess costs apply when the failure arose from causes beyond the contractor's control and without its fault or negligence. FAR 49.402-6 caps the excess cost charge at the undelivered quantity terminated. Each remainder decision leaves a different record:
| Decision on the remainder | Records the packet needs | What the buyer keeps or gives up | Label if the record is missing |
|---|---|---|---|
| Still due on a new date | Notice setting the date and reserving rights, sent with the acceptance | Keeps its remedies if the new date is missed | possible_waiver |
| Reduced by agreement | Signed change lowering the quantity, with any price change | Gives up the units on the agreed terms | unagreed_reduction |
| Terminated in part and bought elsewhere | Termination notice, repurchase order and the quantity each covers | Can charge excess cost on the undelivered terminated quantity only | uncapped_cost_claim |
| Delay excused | Supplier's dated claim of a cause beyond its control and the buyer's ruling on it | No excess cost claim once the excuse is accepted | excuse_unreviewed |
| Part accepted as full performance | Written statement that the line is complete, with the reason | Gives up the missing units | unexplained_completion |
Why can a receiving system show less still owed than the supplier actually owes?
Because some systems count rejected units as received against the order. In ERPNext, each purchase receipt line carries a received quantity, an accepted quantity and a rejected quantity, and the software refuses a line unless received equals accepted plus rejected. The order line's received quantity, and the order's percent received, are then summed from the receipt lines' received quantity, so units rejected at the dock count toward the order as if they had arrived usable.
Billing can follow the same path. ERPNext's buying settings include an option to bill for rejected quantity in the purchase invoice, switched on by default, whose help text says the rejected quantity is then billed anywhere in the purchase cycle. Keep the open quantity above so it still reconciles to the system, and add these fields beside it for every partial acceptance:
- delivery_terms: single lot, installments accepted separately, or a delivery schedule, with the clause or signed change that allows lots.
- variation_basis: whether any quantity allowance applies to each scheduled lot or to the order as a whole.
- accepted_qty and rejected_qty for each receipt, with the rejection reason and the notice sent.
- owed_qty: ordered minus accepted, minus any quantity reduced by agreement or terminated, recomputed at each decision.
- need_ref, alt_lead_days and cure_days: the dated need, the alternate source's quoted lead time and the supplier's promised date for the rest.
- remainder_decision: one value from the table above, with its notice, new date or change reference and the role that decided.
What does an approved partial acceptance look like, checked field by field?
Illustrative case, every value invented: an order line for 600 units allows two lots of 300, each accepted separately. Lot 1 brings 260 units, and inspection rejects 20 damaged in transit, so 240 are accepted. A dated production order needs 200 units within four days; an approved alternate source quotes 12 days, and the supplier commits to ship the missing 40 and 20 replacements in 6. The buyer of record accepts 240, rejects 20 with reasons, and sends a notice that sets a new date for the 60 and reserves rights.
A system that counts rejections as receipts shows 260 of 600 received (43.3 percent) and 340 open, while the supplier still owes 360: the 60 from lot 1 and all of lot 2. The supplier invoices 260 and the bill is approved at 240. A script held for reviewers applies the seven checks to this case and to seven variants built to break one rule each; the approved case passes every check and each variant fails only its own.
| Check | Rule | Approved case | Variant that fails |
|---|---|---|---|
| Balance | Received equals accepted plus rejected | 260 = 240 + 20 | Rejection never recorded: 260 received, 240 accepted, 0 rejected |
| Owed | Ordered minus accepted, reduced and terminated quantities | 360 | Owed taken from received: 340 |
| Billing | Billed quantity no higher than accepted, unless a reason for billing rejects is recorded | Bill approved at 240 of the 260 invoiced | Bill approved at 260 with no reason |
| Rights | A remainder still due has a new date and a rights notice | Both on file | Remainder left open with neither |
| Urgency | Claimed urgency cites the dated need and both lead times | Production order on file; 12 days against 6 | Urgency asserted with no need record or alternate lead time |
| Cost cap | Excess cost charged on no more than the terminated quantity | Nothing terminated | 60 units terminated, excess cost charged on 100 |
| Lots | Partial acceptance under a single-lot contract cites a signed change | Contract allows lots | Single-lot order taken in part with no change on file |
Sources for this section
- UCC 2-307 provides that, unless otherwise agreed, all goods called for by a contract for sale must be tendered in a single delivery with payment due on that tender, and that where either party may make or demand delivery in lots the price can be demanded for each lot if it can be apportioned. Source
- UCC 2-612 defines an installment contract as one requiring or authorizing delivery in separate lots to be separately accepted, and provides that a party reinstates the contract by accepting a non-conforming installment without seasonably notifying cancellation or by demanding performance of future installments. Source
- FAR 52.211-16, Variation in Quantity, has the contracting officer state the permitted increase or decrease and what it applies to, such as the total contract quantity or each quantity specified in the delivery schedule. Source
- FAR 49.402-3 lists the urgency of the need and the time to obtain supplies elsewhere, compared with the time the delinquent contractor needs, among the factors in a default decision, and requires a notice setting a new date and reserving rights when the government's actions might be construed as waiving the delivery date. Source
- FAR 52.249-8 allows termination for default in whole or in part, lets the government buy terminated supplies elsewhere and charge excess costs, requires the contractor to continue the work not terminated, and excuses excess costs when the failure arose from causes beyond the contractor's control and without its fault or negligence. Source
- FAR 49.402-6 says excess cost may not be charged against the defaulting contractor for more than the undelivered quantity terminated for default, including permitted variations in quantity. Source
- ERPNext purchase receipt lines carry fields labeled Received Quantity, Accepted Quantity and Rejected Quantity. Source
- ERPNext rejects a purchase receipt line unless its received quantity equals accepted plus rejected quantity. Source
- ERPNext updates a purchase order line's received quantity and the order's percent received from the receipt lines' received quantity. Source
- ERPNext's buying settings include a Bill for rejected quantity in Purchase Invoice option, on by default, whose help text says the rejected quantity is then billed anywhere in the purchase cycle. Source
Frequently asked questions
What is a partial delivery in purchasing?
A partial delivery is a receipt of less than the ordered quantity on a purchase order line while the rest is still expected or not yet decided. The line stays open until the remainder arrives, is canceled or the shortfall is accepted and the line is closed.
Is a partially received purchase order closed?
Not by default. Systems such as NetSuite keep a Partially Received status while items are outstanding, and SAP treats an item as closed only when the full quantity arrives or the delivery completed indicator is set. A closed state needs its own evidence.
What is the difference between a backorder and a canceled remainder?
A backorder means the missing quantity is still expected and will arrive on a later receipt. A canceled remainder means someone decided it will not arrive, so the open quantity drops to zero without a receipt. Odoo, for example, can be set to create a backorder or cancel the remaining products when a partial receipt is validated.
Can the invoice tell me whether an order line is complete?
No. When a product bills on received quantities, the bill follows what arrived, so a fully paid bill can sit on a line that is still partly open. Use receipt and closure events for state, and billing only for payment status.
Which EDI documents help explain a short shipment?
The X12 855 purchase order acknowledgment lets a supplier accept, change or reject order lines before shipping, and the X12 856 ship notice lists what a shipment contains. Linking both to receipts shows whether a shortfall was announced in advance or discovered at the dock.
Sources
- SAP's delivery completed indicator marks a PO item as closed with no further goods receipt expected, sets open quantity to zero even after partial delivery, and residual receipts can still post. Source
- NetSuite lists Partially Received and Pending Billing/Partially Received purchase order statuses, and header status follows open lines when lines are mixed. Source
- NetSuite supports partially receiving a purchase order and closing lines manually when the buyer does not intend to receive the open items. Source
- In Dynamics 365, canceling only a delivery remainder on a purchase order under change management moves it directly to Confirmed once approved. Source
- Odoo's Create Backorder setting asks, always creates a backorder, or never does and cancels the remaining products at validation. Source
- Odoo's On received quantities control policy builds a draft bill from the products and quantities received. Source
- The X12 855 purchase order acknowledgment affirms a buyer's order or indicates changes to it, including line-level acceptance, change or rejection. Source
- The X12 856 ship notice/manifest lists the contents of a shipment of goods with order, product and packaging details. Source
- Dynamics 365 explains that when a delivery remainder exceeds the line quantity the order Cancel action removes only the line quantity, and canceling the remainder on the line sets it to Canceled. Source
See if your company qualifies
A short company assessment. No data uploads are needed.