Healthcare and Pharmaceutical integration

McKesson EDI for pharmaceutical and medical suppliers

Suppliers that stock McKesson distribution centers exchange orders, ship notices, invoices and contract data with it. This guide covers what is published and how ECOM automates the flow.

At a glance

McKesson integration, in three pictures

The industry, the document flow and the outcome for your team. Illustrations only: they show typical practice, not a specific McKesson program or a customer relationship.

Illustration of a hospital building, a pill bottle and a medical cross, representing the healthcare and pharmaceutical industry that McKesson operates in.
Industry. Healthcare and Pharmaceutical: where McKesson operates.
Workflow diagram: your ERP and distribution systems exchange documents with McKesson through ECOM. You send 855, 856, 810, 846; you receive 850, 844. Your systems ERP · distribution · finance ECOM integration map · validate · connect · monitor McKesson 855 856 810 846 855 856 810 846 850 844 850 844
Workflow. Documents in each direction. Orange: you send. Blue: you receive. Typical, not confirmed.
Comparison diagram: without integration, documents are re-keyed, files are emailed and rejections are found late; with ECOM, documents are mapped to your ERP, validated and monitored, and exceptions are visible early. Without integration Orders re-keyed by hand Files emailed or uploaded Rejections found late With ECOM Documents mapped to your ERP Every file validated and monitored Exceptions visible early
Outcome. From manual handling to a monitored flow. No figures: results depend on your setup.

Talk to an EDI/API Expert about McKesson

Tell us which documents you exchange with McKesson, which ERP you run and when you need to be live. A specialist will outline the connection, mapping and testing plan. This page is a guide based on typical practice; it does not mean ECOM works with McKesson.

  • Review of McKesson's requirements with you, once you have them
  • EDI and API integration with your ERP and distribution systems
  • Monitoring and managed service after go-live, if you want it

Prefer to call? Sales 972-836-7750 or email sales@ecom-specialist.com.

Takes about 30 seconds. Phone and note are optional.

Your request is about

Trading partner
McKesson

When should we talk?

Times are in your time zone. We use this to schedule the conversation.

We use your details only to respond to your request. See our privacy notice. Prefer to talk? Call Sales at 972-836-7750.

Integration and onboarding

How McKesson integration fits your systems

Your systemsERP, distribution and accounting
ECOMMapping, validation, connectivity and monitoringDirect EDI connection · EDI service provider
McKessonIts program, documents and requirements
  1. ConfirmConfirm your McKesson program, role and the documents it requires.
  2. MapMap each document to your ERP fields and business rules.
  3. ConnectConfigure the connection and security the program needs.
  4. TestTest against the applicable specifications and acknowledgments.
  5. Go liveGo live with monitoring, alerts and exception handling.
Typical implementation path. Exact requirements are confirmed against the applicable specifications during onboarding.

Overview

Understanding McKesson integration

Who this is for: Pharmaceutical manufacturers, medical-surgical suppliers and consumer health brands that supply McKesson distribution centers. You receive its purchase orders and send acknowledgments, ship notices and invoices.

Scope: McKesson's public EDI page covers its customer-side documents. The supplier document set, versions and testing are agreed with McKesson's onboarding team; the supplier documents below are typical practice.

If you supply McKesson, the exchange that matters is purchase order in, then acknowledgment, ship notice and invoice out, with lot and expiration data matching the shipment. McKesson is one of the largest healthcare distributors in North America, and it stocks pharmacies, health systems and other providers from its distribution centers.

McKesson does not publish a supplier EDI specification. Its public data integration page is written for pharmacy customers and lists the documents it exchanges with them: 850 purchase orders, 855 acknowledgments, 856 advance ship notices, 810 invoices and 832 price files. The supplier side of the relationship is set up through McKesson's onboarding teams, so the document set for your products is confirmed with them. Prospective vendors register on McKesson's supplier portal, STARS, which its procurement teams search; registration is not a promise of business.

Healthcare distribution adds product data and contract pricing. Lot numbers and expiration dates matter for receiving and traceability under federal DSCSA rules, and manufacturers commonly exchange sales and chargeback data with wholesalers to administer contract prices. ECOM helps map the documents to your ERP and warehouse, connect directly or through your EDI provider, test, and monitor every file after go-live.

Business scenarios

Where McKesson integration gets complicated

Typical requirements—confirm with your trading partner.

Lot and expiry data on every shipment

Distribution centers receive and rotate stock by lot and expiration date. A ship notice that does not match the physical shipment slows receiving and complicates traceability.

How ECOM helps: ECOM builds the ship notice from your warehouse and shipping data and validates product, lot and expiry fields before it is sent.

What you gain: Fewer receiving exceptions and cleaner traceability records.

Contract pricing and chargebacks

Manufacturers commonly reconcile wholesaler sales and chargeback data against contract pricing. Price differences become credits and disputes.

How ECOM helps: ECOM loads the sales and chargeback files you agree with McKesson, compares them with contract prices from your ERP and flags differences for review.

What you gain: Disputes are resolved with evidence and credits are applied against the right contract.

Orders without re-keying

McKesson sends orders for many distribution centers. Entering them by hand delays acknowledgments and invites errors.

How ECOM helps: ECOM maps each purchase order into your ERP, returns the acknowledgment and monitors for orders that are not confirmed in time.

What you gain: Orders post in minutes and unconfirmed orders are seen early.

Workflows

Typical McKesson business workflows

Typical requirements—confirm with your trading partner. Typical flows in this industry, not McKesson's published process.

Typical supplier order-to-cash

  1. 1Receive 850 purchase order
  2. 2Send 855 acknowledgment
  3. 3Ship with lot and expiry data
  4. 4Send 856 ship notice
  5. 5Send 810 invoice

Documents and APIs

McKesson documents by program

General guidance. We could not verify McKesson's EDI requirements from a published source, so these are documents commonly exchanged in this industry, not McKesson's confirmed requirements. Confirm the list, versions and programs with McKesson.

DocumentNameDirectionProgramStatusPurpose
850 Purchase Order From McKesson Not stated General guidance McKesson orders products for its distribution centers. Commonly the first document in the supplier cycle.
855 Purchase Order Acknowledgment To McKesson Not stated General guidance The supplier confirms or adjusts the order.
856 Advance Ship Notice To McKesson Not stated General guidance Describes shipment contents, including lot and expiration data.
810 Invoice To McKesson Not stated General guidance Bills McKesson for shipped products.
846 Inventory Inquiry/Advice To McKesson Not stated General guidance Commonly used to share inventory availability where a program calls for it.
844 Product Transfer Account Adjustment From McKesson Not stated General guidance Commonly used by wholesalers to claim contract-price chargebacks.
849 Response to Product Transfer Account Adjustment To McKesson Not stated General guidance Commonly used by the manufacturer to accept or reject each chargeback line.

Connectivity

How companies connect

  • Direct EDI connection

    Suppliers can connect directly using details from McKesson's onboarding team.

    General guidance

  • EDI service provider

    Many suppliers exchange documents through an EDI provider that manages the connection.

    General guidance

Challenges

Common integration challenges

  • Product data accuracy

    Lot, expiration and product identifiers must be correct for receiving and traceability.

  • Program-specific requirements

    Document sets vary by program and product type, so they are agreed during onboarding.

  • Contract pricing data

    Sales and chargeback data must reconcile with contracts.

Automation options for McKesson suppliers

Four ways to automate. One foundation.

ECOM helps you automate them, meet McKesson's labeling and ship notice requirements, and see what needs action. McKesson sets its program's rules; ECOM confirms which options fit yours.

PRISM Supply Chain Automation Foundation

One platform beneath every option. Use one, or combine them for different partners and documents.

Compliance and actionable visibility

Connect order processing, shipping documentation, trading partner requirements, and performance monitoring through one coordinated workflow. These capabilities help teams improve shipment accuracy, reduce manual work, address compliance risks, and respond to exceptions before they affect customers.

Discuss Your Trading Partner Requirements

Connect McKesson documents to your ERP

ECOM integrates McKesson documents with ERP and warehouse systems so lot and expiry data flows from shipping into ship notices, and orders and invoices post without re-keying.

Industry

Pharmaceuticals

See how ECOM supports pharmaceutical distribution EDI.

Product

PRISM-SCV

Monitor McKesson acknowledgments, ship notices and invoice exceptions.

General EDI flow

How EDI with McKesson typically works

The documents, their order and the timing are McKesson's to set; this is the general sequence most programs of this kind follow.

  1. 850 Purchase Order

    From McKesson to you

    McKesson orders products for its distribution centers. Commonly the first document in the supplier cycle.

  2. 855 Purchase Order Acknowledgment

    From you to McKesson

    The supplier confirms or adjusts the order.

  3. 856 Advance Ship Notice

    From you to McKesson

    Describes shipment contents, including lot and expiration data.

  4. 810 Invoice

    From you to McKesson

    Bills McKesson for shipped products.

  5. 846 Inventory Inquiry/Advice

    From you to McKesson

    Commonly used to share inventory availability where a program calls for it.

  6. 844 Product Transfer Account Adjustment

    From McKesson to you

    Commonly used by wholesalers to claim contract-price chargebacks.

  7. 849 Response to Product Transfer Account Adjustment

    From you to McKesson

    Commonly used by the manufacturer to accept or reject each chargeback line.

Need help with the specification?

Tell ECOM which program you are in and what the partner has given you. We help you read it, confirm the applicable requirements, map them to your systems and test against them. Do not send passwords or EDI identifiers with your request.

Next step

Get help with your McKesson program

Each request goes to an ECOM EDI specialist with McKesson's name attached, so the reply starts from your program.

  • Review McKesson's requirements

    Send us McKesson's guide or your program details; we explain the documents, rules and options for meeting them.

    Request a requirements review
  • Connect McKesson to your ERP

    The documents you exchange, in and out of the ERP and operating systems you already run.

    Discuss ERP integration
  • Testing and certification

    Build, test and certify each McKesson document, then go live with monitoring from the first file.

    Plan testing and certification
  • Shipping labels and ASNs

    Labels and ship notices that match McKesson's rules, to help avoid receiving problems and compliance deductions.

    Review shipping compliance

McKesson integration FAQs

Which EDI documents does McKesson publish?

Its public data integration page lists 850 purchase orders, 855 acknowledgments, 856 advance ship notices, 810 invoices and 832 price files, as exchanged with pharmacy customers. Supplier documents are set during onboarding.

Why do lot and expiration dates matter in ship notices?

They support accurate receiving, inventory rotation and product traceability, which are critical in healthcare distribution.

Can ECOM support pharmaceutical serialization data?

ECOM can integrate serialization and traceability data flows with your systems and partners. Compliance responsibilities stay with you and follow the DSCSA and McKesson's requirements.

Is ECOM a McKesson partner?

This is an independent integration guide. It does not indicate an endorsement, partnership or approval by McKesson.

Sources and accuracy

This guide summarizes publicly available information as of November 2026. McKesson sets its own requirements and can change them at any time; your McKesson implementation guide, supplier portal or account contact is the authoritative source for your program.

Request McKesson integration assistance

Tell us about your McKesson program, documents and ERP. We will outline the connection, mapping and testing plan.