Skip to main content


​​​Fast, inexpensive, and safe, Electronic Data Interchange (EDI) is the application-to-application transfer of business documents such as bills of lading, invoices, purchase orders and shipping notices through a common carrier called a value-added network (VAN). EDI software supports national, international, and industry-specific EDI standards including X12 and EDIFACT.

EDI guidelines



Version 4010 214
404 ​
Version 4020 404
Version 4030 404
Version 4040 204
Version 4050 404
Version 5010 404


Canadian Pacific's EDI transactions have been developed to facilitate shipping for your business:

204 motor carrier shipment information

Sent by the customer to CP, the 204 is used as a Truck Bill of Lading or a Load Tender. As a bill of lading, it is considered an exact representation of the shipment. As a load tender, it is considered as an offer of freight to the railway and may or may not be binding.

214 intermodal status report

The 214 provides domestic intermodal customers with status and location of their containers as they move from origin to destination.

301 export booking

The 301 provides export-booking information to a CP Intermodal Terminal to release containers of a specified type and size to motor carriers for loading. CP intends to combine the information in the 301 with additional information from the IMS terminal gate (weight, seals, contents description, piece count, actual shipper/ultimate consignee) to automatically create an export waybill. When implemented, it will save ocean carriers from transmitting a 404 Bill of Lading for Export shipments and eliminate time-shipment delays due to possibly unavailable 404 information.

322 ramp activity and status report

The 322 provides ocean carriers with the status, location, and in/out terminal activity of their containers. In addition to the traditional in-gates and out-gates, CP offers other status options for the customer's information, including customs clearance, the end of free time, and current rail location and status while the shipment is on the railway network. The information will be updated on an hourly basis, 24 hours a day, and 7 days a week.

323 CP Port Operations and Intermodal Ramp Cut off Scheduler

The 323 provides CP Customers with the Vessel Schedule ETA ( Estimated Time of Arrival), can also include the ETD (Estimated Time of Departure), plus the Rail Port Cut Off and the CP Intermodal Ramp In Gate Cut Off Date/Times in order to meet the Canadian Export Vessel Departures.  Covers the itinerary for the Port of Montreal and the Port of Vancouver published currently two to three times a week.

404 bill of lading

Transmitted by customers to CP, 404's are used to transmit all information relating to rail-movement, including information required by US and Canada Customs and rating related, perishable or hazardous material information necessary to meet North American transportation requirements. Since it is the primary EDI function, most of the available transaction sets are based on information originating in the 404.

410 freight invoice

Sent by CP to the party responsible for payment of freight charges, the 410 lists invoice details and charges associated with a rail shipment. CP can provide invoice information per equipment piece (each 410 is for one railcar/trailer/container) or for a number of shipments. If possible, CP prefers to receive the 820 form (Payment Advice) as a response to transmitted 410's.

417 rail carrier waybill interchange

When used between rail carriers, it is used to provide a carrier with detailed movement instructions pertinent to a rail carrier shipment. It is used by all class 1 Railways in the United States and Canada.

417 rail carrier waybill interchange (to customers)

When used between rail carrier and customer (customer 417), it is used to provide customers with detailed waybilling instructions produced by originating rail carrier upon either a hard copy Paper Bill of Lading or an EDI 404 transaction set, which is provided by the customer. Under this scenario, the 417 generated follows the same guidelines as the 417 transaction set used between rail carriers.

810 invoice (suppliers)

EDI transaction for submitting electronic invoices from a seller to a buyer. The 810 invoice includes (but is not limited to) details such as Remit to, Bill to, and item details (ex. quantity, costs, taxes). There are two distinct 810 transactions: fuel and materials. Canadian Pacific accepts Rail Industry forum materials/ Fuel 810 (RIFMAT/ FDO) as material turn-around documents for non-PO invoices. Invoices must reference a previous 850 purchase order.

820 payment advice

Sent by the customer to CP, the 820 lists transportation Freight Charges, including over/underpayments and adjustments. If the customer wishes to continue payment by cheque, the 820 only provides details of items being paid. Another option is to use the 820 for payment of freight charges via Electronic Funds Transfer (EFT), which is done through our agreement with the Royal Bank of Canada. For customers using a different bank, the Royal Bank can connect with their bank to provide this service.

824 application acknowledgement for select transaction sets

The 824 is generated to advise that the business application has either accepted or rejected a previously submitted transaction.

850 purchase order (suppliers)

EDI transaction for submitting electronic purchase orders from a buyer to a seller. The PO includes (but is not limited to) details such as buyer, bill to, ship to, and item details (quantity, costs, taxes). Canadian Pacific utilizes the Rail Industry Forum Material (RIFMAT) EDI 850 for submitting its PO's to its vendors.

997 functional acknowledgement

Sent by the receiver for any inbound transactions sets, the 997 confirm reception of a transaction set (404, 410, 822, etc.). The 997 also provide validation for the received transaction performed by the EDI translator, and thus can identify transaction errors and rejected transactions. The 997 versions being transmitted must match the version of the transaction being acknowledged.​