Purchase order and fulfilment

In the Peppol post-award ordering grammar, the act that concludes the contract is the seller's Order Response, not the buyer's issuance of the Order.

The strongest thing against it C-009. In the Dynamics 365 vendor collaboration model the supplier's acceptance does not confirm the order; see CL-02.

What may not be said from this Never 'the supplier's acknowledgement is what binds a purchase order'. The finding is grammar-specific and this area found a counterexample in the same collection.

In the Dynamics 365 Supply Chain Management vendor collaboration model, a supplier's acceptance does not confirm the purchase order — the customer's confirmation does — and the supplier cannot change price at all.

The strongest thing against it C-005 and the Norwegian EHF ordering specification, where the seller's confirmation is the accepting act.

What may not be said from this Never 'ERP systems do not let suppliers bind an order'. One system, one workspace, one set of documents.

Across the order grammars inspected in this area, the same named object — the supplier's response to an order — carries the binding act in some and not in others.

The strongest thing against it None was found. The four grammars differ, and none of the four states that the object's name settles the question.

What may not be said from this Never 'order confirmation means different things across the market'. No prevalence, share or representativeness claim is available from four grammars.

In the Peppol Advanced Ordering grammar, the buyer's power to cancel or change an order ends at a physical state — the order being prepared for delivery — rather than at the counterparty's acceptance.

The strongest thing against it The same specification gives the seller a symmetrical power — 'The seller may cancel the order because of lack of delivery capacity or other reasons' — so the asymmetry is in the trigger, not in which party may act.

What may not be said from this Never 'buyers can cancel purchase orders until shipment'. The evidenced boundary is 'prepared for delivery' in one specification, and who judges it is unestablished.

In the Italian NSO grammar a supplier may issue the order itself, and without a prior authorisation from the buyer that order has no legal effect.

The strongest thing against it None was found. The same guidelines state that in the simple ordering process every change to the order is the buyer's to make — 'ogni modifica all'Ordine e a carico del Cliente' — so composition authority is process-dependent within the same transaction infrastructure.

What may not be said from this Never 'suppliers create the buyer's purchase orders'. The evidenced case is one national process, bounded by a pre-authorisation without which the object is void.

A state institution's validation state of an order is a stated ground on which the supplier's invoice may be rejected, and in March 2025 that institution moved one rule from a recommendation to a blocking error.

The strongest thing against it None was found. No inspected artifact states any route by which an order not validated by NSO nonetheless supports a payable invoice, other than the operator's own Ordine di convalida remedy.

What may not be said from this Never 'institutions control whether suppliers get paid'. One transaction infrastructure, one member state, one public sector, and the area's boundary ends at the entitlement, not at the payment.

One inspected vendor artifact requires a non-person integration user to hold Purchase Order Management privileges, and states that purchase documents are created by a scheduled job after an award is approved.

The strongest thing against it The same artifact recommends a human: 'Set the negotiation owner as the first-level approver in both negotiation and award approvals to ensure a human reviews the autonomously created negotiations and awards.' It recommends; it does not require.

What may not be said from this Never 'an AI agent issues purchase orders'. The document type is unstated, the status is unstated, and the privilege grant is a configuration requirement, not an observed act.

That any capability inspected in this area performs the act that binds an order object without a human act.

The strongest thing against it C-003 is the nearest thing to one: a scheduled job creates purchase documents under a non-person identity. It falls short because no inspected passage states that the created document binds the buyer.

What may not be said from this Never 'no agent can bind a purchase order' and never 'agents do not execute orders'. Absence of retrieved evidence is not absence of a capability, and the contract's unsupported_claims 4 forbids the inversion.

In this area every institutional and standards artifact retrieved carried a page-visible date, while every vendor PRODUCT-DOCUMENTATION artifact retrieved carried none; the only dated vendor artifacts were release-plan pages.

The strongest thing against it The Microsoft release-plan feature pages, which carry 'Public preview: Apr 25, 2025' and 'Public preview: Apr 24, 2026' in a visible table.

What may not be said from this Never 'vendors do not date their documentation'. Twelve vendor artifacts in one area, with a named exception.

That any party answerable for an order object — other than the actor, the authority holder, the actor, system or institution that makes the outcome official or the holder of the object — is named in any artifact inspected in this area.

The strongest thing against it The nearest approach is NSO, where a state institution's validation state conditions the supplier's entitlement to be paid — but no inspected artifact names NSO or MEF as ANSWERABLE to anyone for an order, and conditioning an entitlement is not answerability.

What may not be said from this Never 'nobody is answerable for a purchase order'. The claim is about what inspected artifacts name, and vendor-operated hosts blocked four retrievals.

One network carrying orders states that it performs no business checks on the order, only formal checks for correct addressing.

The strongest thing against it NSO, which blocks an order on business rules and whose validation state conditions invoice rejection (CL-06). The two are the area's structural contrast and neither generalises to the other.

What may not be said from this Never 'EDI networks do not validate orders'. One network, one subset, one statement about itself.

One unit in this area constructs a purchase order and transmits it into systems it does not hold, and names both the object it constructs and the systems that hold it.

The strongest thing against it None was found for the non-holding relationship. The counterexample to any autonomy reading is inside the same artifact: 'The supplier reviews the recommendations ... The supplier then creates a purchase order'.

What may not be said from this Never 'the network issues purchase orders on the buyer's behalf autonomously'. Construction and transmission are evidenced; the deciding act is evidenced as the supplier's.

The party that defines the permissible form of an order is more than one party, and the layers are dated and divergent by jurisdiction.

The strongest thing against it None was found. Even the counterexample grammar (C-009) has a layer above the buyer's configuration, in the vendor's product limits, though this area did not code that layer.

What may not be said from this Never 'order standards are controlled by institutions'. T-08 refuses 'controls' without a named object, and the evidenced relation is form-defining, not controlling.