How-to · 23 Oct
How-to · 3 min read
How to tell if an EDI purchase order was really accepted
Buyers and integration teams who send purchase orders over EDI often see a 997 come back and assume the supplier has accepted the order. The dashboard turns green, the order moves on, and nobody looks again until the shipment is short or the invoice price is different. Then someone has to dig through AS2 receipts, 997s and an 855 to work out what the supplier actually agreed to. During trading-partner onboarding, that confusion gets built straight into the status logic.
- Published
- 17 Nov 2026
- Delivery
- No. 12
- Topic
- Work and office
- Evidence
- 9 claims quoted from ariftly.io
01
Why it's hard
Each acknowledgment answers a different question. An AS2 MDN says the message arrived, a 997 says the document passed syntax checks, and only an 855 carries the seller's response to the order, which can confirm it, change it or reject it. Many integrations fold all of these into one status field, because one field is easier to show on a screen. The keys that tie them together differ as well: an MDN refers to a message, a 997 can cover a whole group of transactions, and an 855 refers to a single purchase order. Join them on the wrong key and a valid acknowledgment ends up attached to the wrong order.
This part describes the usual way. It makes no claims about Ariftly, so nothing is quoted here.
02
How Ariftly does it
Ariftly, which builds AI-assisted enterprise workflows with human approval, has published a research guide on this exact boundary, comparing the MDN, the 997 and the 855 and what each one does and does not prove. Its answer is plain: a 997 is a syntax acknowledgment, not commercial acceptance. EDI and trading-partner onboarding is listed as a future workflow direction, built around message, acknowledgement and business-rule checks, with integration owners resolving partner-specific exceptions. It is not a self-serve tool today, since work is scoped and quoted per workflow after a discovery call, so the guide is the first useful thing you can take from them.
No. An X12 997 acknowledges the results of syntactic checks on EDI documents, not a seller's commercial acceptance of a purchase order.Quoted from ariftly.io
Message, acknowledgement and business-rule checksQuoted from ariftly.io
Integration owners resolve partner-specific exceptionsQuoted from ariftly.io
03
Step by step
- 1List every acknowledgment your partner agreement requires, such as the MDN, the 997 or 999, and the 855.
- 2Store each one as its own record instead of overwriting a single order status.
- 3Match each acknowledgment at its real scope: message, functional group, transaction or purchase order.
- 4Mark an order as accepted only when an 855 confirms it, and keep accepted with changes as a separate state.
- 5Test the failure cases before go-live, including missing, late or duplicate acknowledgments and changed quantities or prices.
- 6If you want help scoping one partner flow, book a discovery call and bring the partner guide and sample messages.
04
Tips
Never treat an HTTP 200 as proof of receipt. A plain 200, an MDN arriving and a correctly verified signed MDN are three different events, and your logs should keep them apart.
Do not label an HTTP 200 response, an MDN's arrival and a verified signed MDN as the same event.Quoted from ariftly.io
Read every 855 for what it says, not for the fact that it arrived. A response can accept the order while changing price, quantity or dates, and a header-level acknowledgment should not be stretched into line-level proof.
The seller's PO response, which may affirm, change or reject the orderQuoted from ariftly.io
Keep the green status honest. If one indicator hides whether the order was commercially accepted, unresolved orders slip through until a short shipment or a wrong invoice exposes them.
Collapsing those stages into one green status can hide a commercially unresolved order.Quoted from ariftly.io
Check the partner guide before you hard-code anything. Some partners require a 999 instead of a 997, and the meaning of a response depends on your agreement, not on a generic table you found online.
Verify the applicable partner agreement and order state.Quoted from ariftly.io
05
Questions
Does an EDI 997 mean the order was accepted?
No. A 997 acknowledges syntax checks on the EDI document, not the seller's commercial acceptance of the purchase order.
No. An X12 997 acknowledges the results of syntactic checks on EDI documents, not a seller's commercial acceptance of a purchase order.Quoted from ariftly.io
Can I use Ariftly for EDI onboarding today?
Not as a finished product. EDI onboarding is listed as a future workflow direction, and the current concrete example is a local Oracle SQL to Snowflake workflow.
A direction is an example of scope, not a finished product.Quoted from ariftly.io
How is Ariftly priced?
Per workflow. Each deployment is scoped and quoted instead of sold at a public seat price.
we scope and quote the work rather than publish a generic seat price.Quoted from ariftly.io