If you are looking to implement McKesson as a new Trading Partner within your EDI network, this article will provide you with an understanding of the requirements, preliminary and next steps, as well as commonly used transaction types.

McKesson utilizes the following Electronic Data Interface (EDI) IDs for identification purposes. These EDI IDs are made up of a Qualifier and an ID which will be sent within their Interchange Control Header, ISA segment, on your inbound transactions. This allows Transaction Manager to be able to identify the Sender and Receiver of any EDI transaction that is sent or received.

Below is a list of the most common EDI IDs typically used by McKesson:

Before TrueCommerce is able to begin onboarding McKesson into Transaction Manager, you will need to perform the following action to kick off your Trading Partner Implementation Project:

Due to limitations in their Electronic Resource Planning (ERP) system, McKesson does not require you to complete compliance testing before Go-Live. The standard approach is to move directly into Production. However, an exception can be made for chargeback testing only and should be communicated with McKesson directly.

If your organization has previously been in Production with McKesson via a different EDI provider, and you are switching to TrueCommerce’s EDI service, you can email McKesson directly and provide the below details:

McKesson will implement the change to Production on the scheduled Go-Live date.

Please refer to the below Next Steps section for detailed instructions and expectations.

Once the purchase of the McKesson plug-in is complete, your Implementation Specialist will reach out to schedule time to complete and/or coordinate a plan for compliance testing and/or Enterprise Resource Planning (ERP) system integration testing.