McKesson EDI Compliance Guide
Trade EDI with the largest pharmaceutical distributor in the US
Quick Answer
McKesson requires EDI 850 (Purchase Order), EDI 855 (PO Acknowledgment), EDI 856 (Ship Notice (ASN)), EDI 810 (Invoice), EDI 832 (Price/Sales Catalog), EDI 997 (Functional Acknowledgment) from all suppliers. Non-compliance triggers chargebacks including invoice and PO mismatches: payment deductions.
McKesson is the largest pharmaceutical distributor in the United States, supplying retail chains, independent pharmacies, hospitals, and health systems. EDI runs in both directions: manufacturers and suppliers trade purchase orders and invoices with McKesson, while pharmacy and provider customers receive order, shipment, and invoice documents from McKesson. Pharmaceutical products add DSCSA serialization and traceability requirements on top of standard EDI.
Required EDI Transactions
McKesson requires suppliers to support the following EDI transaction types. Click any transaction to view our detailed guide with segment breakdowns and examples.
McKesson-Specific Transaction Requirements
- EDI 810 (Invoice): Contract and chargeback pricing make pharma invoicing harder than retail. Invoices must reflect the contract price for the specific customer class of trade.
- EDI 832 (Price/Sales Catalog): Pharma distribution leans on the 832 catalog to keep NDC numbers, pack sizes, and contract pricing aligned between manufacturer and distributor. Catalog drift is the root cause of most invoice disputes.
- EDI 856 (Ship Notice (ASN)): Pharmaceutical ASNs carry lot, expiration, and (for serialized product) DSCSA identifiers. McKesson reconciles received product against this data.
Compliance Requirements
Here is what McKesson expects from EDI-compliant suppliers:
- EDI 850 Purchase Order processing
- EDI 855 PO Acknowledgment
- EDI 856 ASN with lot, expiry, and serialization data where required
- EDI 810 Invoice submission
- EDI 832 Price/Sales Catalog for item and pricing sync
- EDI 997 Functional Acknowledgment
- DSCSA-compliant traceability data (EPCIS) for pharmaceutical products
- GTIN and NDC product identification
Chargeback Penalties
Non-compliance with McKesson's EDI requirements can result in significant financial penalties:
Common McKesson Chargebacks
- Invoice and PO mismatches: payment deductions
- ASN errors on pharmaceutical shipments: receiving delays and disputes
- DSCSA data gaps: shipments refused or quarantined
- Contract pricing disputes: chargeback reconciliation cycles (EDI 844/849 in pharma distribution)
How to Set Up EDI with McKesson
- Get your supplier or customer agreement in place with McKesson and identify your account and class of trade.
- Contact McKesson's EDI team through your account manager to exchange identifiers and implementation guides.
- Map the document set for your relationship: 850, 855, 856, 810, and 832 are the common core.
- If you ship serialized pharmaceutical product, validate your DSCSA/EPCIS data exchange alongside EDI testing.
- Run parallel testing with McKesson before cutting over to production.
Official McKesson EDI Resources
Always verify requirements against McKesson's own documentation. These are the official resources suppliers use:
- McKesson Connect: McKesson's ordering portal for pharmacy customers. EDI replaces manual portal ordering once volume justifies it.
- McKesson: Corporate site with supplier and distribution program information.
How to Achieve McKesson EDI Compliance
Getting compliant with McKesson requires three things: an EDI platform that supports all required transaction types, automated validation that catches errors before they trigger chargebacks, and integration with your ERP so orders flow through without manual re-entry.
EDI transaction formats follow ASC X12 standards, and product identification uses GS1 GTIN and GS1-128 barcode specifications. Both are required by virtually every major US retailer.
OrderSync handles all three compliance layers. Our platform processes EDI transactions (850, 855, 856, 810, 997) alongside PDF, CSV, and email orders through a single pipeline. Automated validation checks every order against your product catalog, pricing rules, and McKesson-specific compliance requirements before syncing to your ERP.
Related Guides and Articles
Learn more about McKesson EDI requirements and compliance best practices:
Related Resources
Test Your EDI Compliance
Upload your EDI documents to our free inspector and check for compliance issues before sending to McKesson.
Open EDI InspectorFrequently Asked Questions
What EDI transactions does McKesson require?
McKesson requires EDI 850 (Purchase Order), EDI 855 (PO Acknowledgment), EDI 856 (Ship Notice (ASN)), EDI 810 (Invoice), EDI 832 (Price/Sales Catalog), EDI 997 (Functional Acknowledgment). Each transaction must meet McKesson's specific formatting and timing requirements.
What happens if I'm not EDI compliant with McKesson?
Non-compliance triggers chargebacks that can range from $200 to $5,000+ per incident depending on the violation. Repeated non-compliance can lead to supplier suspension or loss of the retail account.
Can OrderSync help with McKesson EDI compliance?
Yes. OrderSync supports all EDI transaction types required by McKesson and includes automated validation to catch compliance errors before documents are sent. Our platform processes EDI alongside PDF, CSV, and email orders through a single pipeline.
What is McKesson EDI?
McKesson EDI is the electronic document exchange McKesson runs with both sides of its distribution business. Suppliers and manufacturers receive 850 purchase orders and send back 855 acknowledgments, 856 ASNs, and 810 invoices. Pharmacy and provider customers can send 850s to McKesson and receive 855, 856, and 810 documents in return.
Does McKesson require EDI from suppliers?
High-volume pharmaceutical and medical-surgical suppliers trade with McKesson by EDI as a practical requirement. Smaller suppliers may start with portal or manual processes, but order volume and DSCSA traceability push most trading relationships onto EDI.
How does DSCSA affect EDI with McKesson?
The Drug Supply Chain Security Act requires serialized, traceable transaction data for pharmaceuticals. That data flows as EPCIS events alongside the EDI documents, and McKesson reconciles physical product against it. EDI alone does not satisfy DSCSA, but ASN accuracy and serialization data have to agree or shipments get held.