What McKesson expects in the 997
McKesson trades on X12 4010 over VAN. McKesson's 997 follows the standard X12 layout — no partner-specific companion-guide quirks are curated for this document yet. The certified base map covers the standard requirements, and validation still runs against the 997 spec before anything transmits.
How EDISQ maps it
The certified McKesson 997 map loads when you enable the partner — fields auto-map from NetSuite, QuickBooks, Dynamics, and 33 other systems, validation runs against McKesson's spec before transmission, and the sandbox replays McKesson test scenarios until everything passes.
Common rejection reasons
Nearly all 997 rejections trace to reference data, not syntax: identifiers that don't match McKesson's cross-references, echoed fields dropped from the original PO, or timing that misses the program window. EDISQ flags each before McKesson ever sees the document.
Sample McKesson 997
A representative 997 interchange addressed to McKesson — envelope, body segments, and control totals:
1ISA*00* *00* *ZZ*ACMESUPPLY *ZZ*MCKESSON *260101*1200*U*00401*000000001*0*P*>~ 2GS*FA*ACMESUPPLY*MCKESSON*20260101*1200*1*X*004010~ 3ST*997*0001~ 4AK1*PO*1~ 5AK2*850*0001~ 6AK5*A~ 7AK9*A*1*1*1~ 8SE*6*0001~ 9GE*1*1~ 10IEA*1*000000001~
FAQ
Which 997 version does McKesson use?
X12 4010, delivered over VAN. The certified map tracks McKesson's current companion guide.
How do I test a McKesson 997?
The sandbox generates realistic McKesson 997 scenarios against your live mapping — free, unlimited, invisible to McKesson.
What does it cost?
Per document only: first 25/month free, then from $0.50, decreasing with volume. No partner or mapping fees.