Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash...

455
Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical Standards Work Group Foodservice Date: March 2012 Publication Version: 1.0

Transcript of Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash...

Page 1: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Foodservice EDI Transaction Sets

Order to Cash

Business Process Flow Information With Implementation Guidelines

Prepared by: Technical Standards Work Group Foodservice Date: March 2012 Publication Version: 1.0

Page 2: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

2012 GS1 Canada – Technical Standards Work Group - Foodservice EDI Page 2 of 57

Technical Standards Work Group – Foodservice Foodservice Business Process and EDI (GS1C11-513)

Table of Contents Disclaimer ....................................................................................................................................................... 4

DOCUMENT HISTORY ........................................................................................................................... 5

DOCUMENT CONTRIBUTION ................................................................................................................ 5

Change Request - GS1C11-513 - Foodservice EDI Transaction Sets for Order-To-Cash ............................ 6

EXECUTIVE SUMMARY ......................................................................................................................... 7

BUSINESS PROCESS ANALYSIS .......................................................................................................... 8

MISSION .................................................................................................................................................... 8

SCOPE ........................................................................................................................................................ 8

AUDIENCE .................................................................................................................................................. 8

KEY PRINCIPALS AND RULES ...................................................................................................................... 8

GENERAL DEFINITIONS .............................................................................................................................. 9

Initial Challenges ............................................................................................................................................ 9 Dependancies/References ............................................................................................................................. 9 How to Read This Document .......................................................................................................................... 9

BUSINESS PROCESS OVERVIEW ...................................................................................................... 10

Figure 0 – Order to Payment Process ........................................................................................................... 10 Initial order-to-cash process: .................................................................................................................. 11

The Actors: .............................................................................................................................................. 11

PROCESS: PURCHASE ORDER ......................................................................................................... 12

Definition/Rational ....................................................................................................................................... 12 Actors ........................................................................................................................................................... 12 Process ......................................................................................................................................................... 12 EDI Transaction Set(s) to support business process: .................................................................................... 13 Figure 1 – Purchase Order Process Flow ...................................................................................................... 13

PROCESS: PURCHASE ORDER CHANGE ......................................................................................... 14

Definition/Rational ....................................................................................................................................... 14 Actors ........................................................................................................................................................... 14 Process ......................................................................................................................................................... 14 EDI Transaction Set(s) to support business process: .................................................................................... 15 Figure 2 – Purchase Order Change – Purchasing Organization Initiated ..................................................... 15 EDI Transaction Set(s) to support business process: .................................................................................... 17 Figure 2a – Purchase Order Change – Selling Organization Initiated ........................................................... 17

PROCESS: SHIPPING .......................................................................................................................... 18

Definition/Rational ....................................................................................................................................... 18 Actors ........................................................................................................................................................... 18 Process ......................................................................................................................................................... 18 EDI Transaction Set(s) to support business process: .................................................................................... 19 Figure 3 – Shipping Process from Selling Organization ................................................................................ 19

Page 3: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

2012 GS1 Canada – Technical Standards Work Group - Foodservice EDI Page 3 of 57

Technical Standards Work Group – Foodservice Foodservice Business Process and EDI (GS1C11-513)

PROCESS: RECEIVING ........................................................................................................................ 20

Definition/Rational ....................................................................................................................................... 20 Actors ........................................................................................................................................................... 20 Process ......................................................................................................................................................... 20 EDI Transaction Set(s) to support business process: .................................................................................... 21 Figure 4 - Receiving Process to Purchasing Organization ............................................................................. 21

PROCESS: INVOICE ............................................................................................................................. 22

Definition/Rational ....................................................................................................................................... 22 Actors ........................................................................................................................................................... 22 Process ......................................................................................................................................................... 22 EDI Transaction Set(s) to support business process: .................................................................................... 23 Figure 5 - Invoice Process from Selling Organization ................................................................................... 23

PROCESS: PAYMENT (REMITTANCE) ............................................................................................... 24

Definition/Rational ....................................................................................................................................... 24 Actors ........................................................................................................................................................... 24 Process ......................................................................................................................................................... 24 EDI Transaction Set(s) to support business process: .................................................................................... 25 Figure 6 - Payment Remittance by Purchasing Organization ....................................................................... 25

APPENDIX 1: TRANSACTION SETS AND MAINTENANCE SUBMISSION ........................................ 26

APPENDIX 1: MAINTENANCE SUBMISSION FORM COMPLETED ................................................... 28

APPENDIX 2: BUSINESS EXAMPLES ................................................................................................. 30

Business Examples A .................................................................................................................................... 30 Business Examples B .................................................................................................................................... 39

Document 850 – Purchase Order ............................................................................................................ 39

Document 856 – Ship Notice/Manifest ................................................................................................... 41

Document 810 – Invoice .......................................................................................................................... 44

Document 820 –Remittance Advice ........................................................................................................ 46

APPENDIX 4: EDI OVERVIEW.............................................................................................................. 47

INTRODUCTION TO ELECTRONIC DATA INTERCHANGE (EDI) ...................................................... 47

INTRODUCTION ....................................................................................................................................... 47

EDI: THE CONCEPT ................................................................................................................................... 47

BENEFITS OF EDI ...................................................................................................................................... 47

EDI IMPLEMENTATION CONSIDERATIONS ....................................................................................... 49

Problems to avoid ................................................................................................................................... 49

Implementation Checklist ....................................................................................................................... 50

APPENDIX 5: GLOSSARY .................................................................................................................... 56

APPENDIX 6: INDUSTRY IMPLEMENTATION ROAD MAP WITH TIMELINES .................................. 57

Page 4: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

2012 GS1 Canada – Technical Standards Work Group - Foodservice EDI Page 4 of 57

Technical Standards Work Group – Foodservice Foodservice Business Process and EDI (GS1C11-513)

Disclaimer GS1 Canada is providing this voluntary standard as a service to the Canadian healthcare industry. This voluntary standard guideline was developed through a consensus process of industry participants . Although efforts have been made to assure that the standard guideline is correct, reliable, and technically accurate, GS1 Canada makes no warranty or representation, express or implied, that this standard is correct, will not require modification as experience and technological advances dictate, or will be suitable for any purpose or workable in any application, or otherwise. Use of the standard is with the understanding that GS1 Canada has no liability for any claim to the contrary, or for any damage or loss of any kind or nature. If a user perceives a need for a change to the standard, they should contact GS1 Canada. Users are cautioned that this is a voluntary healthcare industry standard. Should it conflict with government laws or regulations, the legal requirements supersede the standard.

Page 5: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

2012 GS1 Canada – Technical Standards Work Group - Foodservice EDI Page 5 of 57

Technical Standards Work Group – Foodservice Foodservice Business Process and EDI (GS1C11-513)

DOCUMENT HISTORY

Version No. Actions Author

1.0

Date

Initial Publication Technical Work Group - Foodservice March 2012

DOCUMENT CONTRIBUTION

Company Representative

ARAMARK Canada Ltd.

Title

Larysa Ihnatowycz Sr. Director of Distribution Cadbury Adams Canada Inc. Rose DeLuca GDS Operations Gateway Grocer Stephane Cadieux Food Safety Manager Flanagan Foodservice Inc. Ernest Krawetz V.P. Information Technology Gordon Food Service Kathryn Moore Item Data Integrity / EDI Administrator Gourmet Baker Inc. King Kho QA & Food Safety Supervisor H.J. Heinz of Canada Ltd. Richard McTavish Systems Analysis - EDI/Sales Holt Renfrew Chris Ford EDI Specialist I-D Foods Corporation Gabrielle Litschauer Procedures/Data integrity coordinator Kraft Canada Inc. Bill Powell eBusiness Analyst Lassonde Industries Guy Vezina eCommerce specialist McCormick Canada Kim Chalk Business Analyst - Electronic Data Nestle Canada Inc. Sean Byrne Data Manager Parmalat Canada Shani Williams Packaging Technician Saputo Inc. Curtis Aikens Corporate Business Analyst Smucker Foods of Canada Paula Mandel Senior Business Analyst Sysco Canada Karen Hurley Manager, Healthcare Sysco Canada Xenia Di Natale Manager, Supply Chain Services Tannis Food Distributors Fadi Swayty Project Manager The Overwaitea Food Group Cindy McLean Sr. Business Analyst Thomas, Large & Singer Inc. Debi McOuat EDI & Database Services Manager Weston Bakeries Hong Tran Category Manager, Food Service Zast Foods Corporation Jayne Hughes V.P. Operations GS1 Canada Rita Laur Director Standards GS1 Canada Nicole Golestani Implementation Manager GS1 US Steven Rosenberg Director, Electronic Commerce

Page 6: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

2012 GS1 Canada – Technical Standards Work Group - Foodservice EDI Page 6 of 57

Technical Standards Work Group – Foodservice Foodservice Business Process and EDI (GS1C11-513)

Change Request - GS1C11-513 - Foodservice EDI Transaction Sets for Order-To-Cash Submitter - Food Service Sector Board B: PROPOSED ACTION List specific changes needed, if known, to be implementation guidelines to satisfy the business need. If necessary, attach additional documentation.

Establish a working group to review existing Order-To-Cash transactions, revise, approve and publish a Foodservice Implementation Guideline for EDI. Transactions to be included are: • 850 Purchase Order • 855 Purchase Order Acknowledgment • 856 Ship Notice / Manifest (ASN Advance Ship Notice) • 810 Invoice • 997 Functional Acknowledgment Establish the version for all Foodservice Industry to use.

C: EXPECTED BENEFITS, OPPORTUNITIES AND EARLY ADOPTERS Explain what business benefits or opportunities can be realized by this request and list those organizations, apart from the submitters, who will benefit from the resulting global solution. If necessary, attach additional documentation.

Reasons for implementing EDI fall increasingly within the tactical rather than the strategic category. Standardize electronic communication for the order-to-cash process will improve the efficiency and accuracy of information. Listed below are some of the major benefits identified by many companies already involved in EDI: • Improved accuracy • Increased customer service • Increased improvement in patient safety • Reduced manual data entry • Reduced postage and handling cost • Reduced printing cost of forms • Reduced mail time • Reduced labour processing cost • Reduced order cycle time • Reduced lead times • Reduced filing of paperwork • Reduced inventory carrying cost

Attachments: There are no attachments associated with this request. D: BUSINESS FUNCTION/PURPOSE Explain, in detail, the business function, operation or problem that will be satisfied by the change, I.e., what is the change accomplishing from a business or carrier performance perspective. Use additional pages if necessary.

Modify electronic communication systems to send and receive the order – to – cash EDI transactions between trading partners.

Page 7: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

2012 GS1 Canada – Technical Standards Work Group - Foodservice EDI Page 7 of 57

Technical Standards Work Group – Foodservice Foodservice Business Process and EDI (GS1C11-513)

EXECUTIVE SUMMARY This document was created to provide a path for Foodservice companies to achieve efficiencies in their operations by adopting the use of electronic messaging for business documents that are exchanged between trading partners.

Current business processes rely on paper based exchange between trading paprtners via fax, mail or email, and are manually entered into internal systems. This adds time and may cause data entry errors in the business processes. Implementing electronic messages allows the business to re-engineer those processes to take advantage of the increased speed and accuracy of the data exchanged.

A team of cross-industry experts assembled this document to describe the key areas affected in the current business processes and the electronic messages that can be implemented to support them. The business processes covered are:

• PURCHASE ORDER

• PURCHASE ORDER CHANGE

• SHIPPING

• RECEIVING

• INVOICE

• PAYMENT

EDI (Electronic Data Interchange) is the method for electronic messaging used in Canada. This document recommends the use of the GS1 Canada Food Service VICS Implementation Guideline for EDI which is based on the voluntary use of the EDI X12 standards.

Page 8: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

2012 GS1 Canada – Technical Standards Work Group - Foodservice EDI Page 8 of 57

Technical Standards Work Group – Foodservice Foodservice Business Process and EDI (GS1C11-513)

BUSINESS PROCESS ANALYSIS

MISSION Establish a working group to review existing Order-To-Cash transactions, revise, approve and publish a Foodservice Business Process Analysis with an Implementation Guideline for EDI. Transactions included: Purchase Order, Purchase Order Acknowledgment, Purchase Order Change, Advance Ship Notice, Invoice and Payment Remittance / Payment Advice. Establish the EDI version for all Foodservice Industry to use.

SCOPE To document the order-to-cash processes and to establish industry best practice for electonic communication in Food Service.

• Business process timelines as they are part of the trading partner agreement. Out of scope

• Receiving exception process • Payment dispute resolution • Back order process • Carrier processing • Carrier selection • Discrepancy resolution • Product activity reporting • Vendor managed inventory (VMI) • Rebate processing • Substitutions

AUDIENCE The different sections of this document have been written for different audiences; ranging from the General Manager who will be faced with the decision to implement the EDI project with all of the attendant business considerations, to the technicians who will perform the data requirements and the programming efforts.

KEY PRINCIPALS AND RULES The business intention is to develop standards to aid the communication of order to cash for the Food Service sector.

1. All foodservice communication is goverened by local regualtions, policy and guidelines. 2. Establish trading partner agreements/contracts. 3. Each trade item must be referenced using an unique identifier. 4. Each trading partners address and contact information must be established. 5. Each transaction must be uniquly identified and clearly state it’s purpose. 6. Trading partners must synchronize product data prior to transactional communication. 7. Transaction recipients must acknowledge the receipt of the transaction. 8. One invoice per shipment. 9. Include established audit trails for each business process.

Page 9: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

2012 GS1 Canada – Technical Standards Work Group - Foodservice EDI Page 9 of 57

Technical Standards Work Group – Foodservice Foodservice Business Process and EDI (GS1C11-513)

GENERAL DEFINITIONS

Initial Challenges As organizations recognize a need to improve the efficiency of their business processes, some of the major challenges are:

• Manual data entry effort • Data entry errors • Warehouse inefficiencies • Cost increases in manual operations • Large amounts of paperwork and requisite storage Assumptions

GS1 Canada Food Service VICS Implementation Guideline for EDI is based on the voluntary use of X12 standards.

Dependancies/References

Reference Name Description

X12 EDI standards Message Transaction Sets • Purchase Order (850) • Purchase Order Change (860) • Purchase Order Acknowledgment (855) • Ship Notice / Manifest (ASN Advance Ship Notice) (856) • Invoice (810) • Remittance Advice (820) • Functional Acknowledgment (997)* NOTE: A functional acknowledgment is sent after each transmission. This is to confirm the transaction was received by the trading partner.

Canadian VICS EDI Guideline Canadian Food & Drug Retail and Foodservice Implementation Guideline for EDI Published 1998 (v4010)

GS1 General Specification Barcode Standards and Allocation Rules

How to Read This Document 1. Each business process has steps identified alpha numerically. This alpha numeric is matched to the process flow

diagram for the specific step. 2. Each diagram has respective actor swim lanes. Within the diagram message is in lower case as the step is not an

actor.

Page 10: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

2012 GS1 Canada – Technical Standards Work Group - Foodservice EDI Page 10 of 57

Technical Standards Work Group – Foodservice Foodservice Business Process and EDI (GS1C11-513)

BUSINESS PROCESS OVERVIEW Figure 0 – Order to Payment Process

Note: see Key Principals

PurchaseOrder

Purchasing Organization

Messages

Selling Organization

Payment

Shipping

PurchaseOrder

Change

Invoice

PurchaseOrder

Payment

Receiving

PurchaseOrder

Change

Invoice

Purchase Order (850)

Purchase Order Acknowledgement (855)

Purchase Order Change (860)

Advanced Ship Notice (856)

Invoice (810)

Remittance/ Payment Advice (820)

Page 11: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

2012 GS1 Canada – Technical Standards Work Group - Foodservice EDI Page 11 of 57

Technical Standards Work Group – Foodservice Foodservice Business Process and EDI (GS1C11-513)

Initial order-to-cash process:

1. Purchase Order 2. Purchase Order Change (Optional) 3. Shipping 4. Receiving 5. Invoice 6. Payment

The Actors:

Accounts Payable Position paying the invoice at the purchasing organization

Accounts Receivable Position issuing invoice and receiving payment at the selling organization

Bill-to Organization Organization receiving invoices on behalf of the purchasing organization

Buyer Position purchasing the product at the purchasing organization

Carrier Organization handling the delivery of shipment(s)

Customer Service Position processing the purchase order at the selling organization

Purchasing Organization The Operator/Distributor/Provider that is purchasing product

Selling Organization The Supplier/Manufacturer/Vendor/Broker that is selling the product

Shipper Individual/Department responsible for preparing the shipment at the selling organization

Receiver Organization handling the receipt of shipment(s)

Page 12: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

2012 GS1 Canada – Technical Standards Work Group - Foodservice EDI Page 12 of 57

Technical Standards Work Group – Foodservice Foodservice Business Process and EDI (GS1C11-513)

PROCESS: PURCHASE ORDER

Definition/Rational A buyer authorizes a request for goods or services. When accepted by the seller, it becomes a contract binding on both parties.

Actors Purchasing Organization The Operator/Distributor/Provider that is purchasing product Selling Organization The Supplier/Manufacturer/Vendor/Broker that is selling the product Buyer Position purchasing the product at the purchasing organization Customer Service Position processing the purchase order at the selling organization

Process

None Pre-requisite process

A1. Purchase Order creation (Purchasing Organization - Buyer)

The buyer for the purchasing organization has identified the need to purchase a product. The buyer enters the details into the purchasing system and creates a purchase order. The purchase order is communicated to the selling organization.

A2. Purchase Order receipt confirmation (Selling Organization – Customer Service) The selling organization optionally sends a communication back to the purchasing organization that the purchase order was received. This communication purely is to communicate that the purchase order was received and does not confirm that the purchase order will be shipped.

A3. Purchase Order review (Selling Organization – Customer Service)

Customer service will review the purchase order and confirm the contents. This confirmation includes checking of the following on the purchase order:

• Product GTIN • Product quantities – variable or catch weight • Delivery/pickup/appointment (date and time)/cancellation date • Shipping instructions

Method Specific arrival window (time)

• Shipping locations • Pricing/currency • Billing information • Special instructions

Marked pricing on product • Freight on board (FOB)

A4. Acceptance of Purchase Order (Selling Organization – Customer Service)

When the purchase order is accepted without changes, the selling organization acknowledges confirmation to the buying organization (as agreed by trading partners).

A5. Any rejections or changes to the purchase order will be addressed in the purchase order change process.

Page 13: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

2012 GS1 Canada – Technical Standards Work Group - Foodservice EDI Page 13 of 57

Technical Standards Work Group – Foodservice Foodservice Business Process and EDI (GS1C11-513)

EDI Transaction Set(s) to support business process: • Purchase Order (850) • Purchase Order Acknowledgment (855)

Figure 1 – Purchase Order Process Flow

Purchase Order

messages Customer Service RepresentativeBuyer

Purchase Order Creation

Purchase Order Purchase Order Received

Purchase Order Receipt

Confirmation

Purchase Order Review

Accept Purchase

Order?

Purchase Order Acknowledgement

- Approval

Purchase Order Acknowledgement - Change/Rejection

Optional

Yes

No

Start

Purchase Order Approval Received

Confirmation Received

See Purchase Order Change

Process

A1

A3

A2

A4

A5

Page 14: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

2012 GS1 Canada – Technical Standards Work Group - Foodservice EDI Page 14 of 57

Technical Standards Work Group – Foodservice Foodservice Business Process and EDI (GS1C11-513)

PROCESS: PURCHASE ORDER CHANGE

Definition/Rational A change to an existing Purchase Order. It can be initiated by the Purchasing Organization or the Selling Organization

Actors Purchasing Organization The Operator/Distributor/Provider that is purchasing product Selling Organization The Supplier/Manufacturer/Vendor/Broker that is selling the product Buyer Position purchasing the product at the purchasing organization Customer Service Position processing the purchase order at the selling organization

Process

1. Purchase Order Pre-requisite processes:

Purchase Order Change initiated by the Purchasing Organization

B1. Purchase Order Change initiated by Purchasing Organization The Buyer determines that a change needs to be made to an existing Purchase Order. A change could take one of the following forms:

B2. A change to the existing Purchase Order under the existing Purchase Order number B3. The original Purchase Order is cancelled and a new Purchase Order is issued. In this situation the change

being communicated is the cancel and the process starts over from scratch with a new Purchase Order and new Purchase

A change to a Purchase Order could affect any of the following:

• Product/quantities • Delivery/pickup/appointment/cancellation date • Shipping method • Shipping locations • Pricing/currency • Billing information • Special instructions

Once finalized, the Buyer sends the Purchase Order Change to the Selling Organization. The Change could re-issue the entire Purchase Order, or just communicate the changes.

B4. Customer service receives the purchase order change and puts the new version of the purchase order through the

same review processes as described for the purchase order in the section above.

Customer service then communicates the acceptance or rejection of the changes back to the purchasing organization.

Page 15: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

2012 GS1 Canada – Technical Standards Work Group - Foodservice EDI Page 15 of 57

Technical Standards Work Group – Foodservice Foodservice Business Process and EDI (GS1C11-513)

EDI Transaction Set(s) to support business process: • Purchase Order Change (860)

Figure 2 – Purchase Order Change – Purchasing Organization Initiated

PO Change – Purchasing Organization Initiated

Customer Service RepresentativemessagesBuyer

Reason for Purchase Order

Change Identified

Start

Cancel or Revision

Purchase Order Change

Purchase Order Cancel

Purchase Order Change Review

End

Cancellation of Purchase Order in

Sellers system

See Purchase Order Process

Revision

Cancel

B1

B2

B3

B4

Page 16: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

2012 GS1 Canada – Technical Standards Work Group - Foodservice EDI Page 16 of 57

Technical Standards Work Group – Foodservice Foodservice Business Process and EDI (GS1C11-513)

Purchase Order Change initiated by the Selling Organization

C1. Purchase Order Change initiated by the Selling Organization after the Purchase Order was accepted Selling organization identifies that a purchase order which has been received and accepted cannot be fulfilled as agreed and requires a change. Changes could affect the following:

• Product/quantities • Delivery/pickup/appointment/cancellation date • Shipping method • Shipping locations • Pricing/currency • Billing information • Special instructions

Customer Service communicates the change to the buyer.

C2. The buyer can accept, revise, and reject a purchase order change. An additional option is to cancel the purchase

order. C3. Customer service is notified of the changed purchase order and puts the new version of the purchase order

through the same review process.

Customer service communicates a final confirmation of the acceptance or rejection of the changes back to the buyer.

Page 17: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

2012 GS1 Canada – Technical Standards Work Group - Foodservice EDI Page 17 of 57

Technical Standards Work Group – Foodservice Foodservice Business Process and EDI (GS1C11-513)

EDI Transaction Set(s) to support business process: • Purchase Order Change (860)

Figure 2a – Purchase Order Change – Selling Organization Initiated

PO Change – Selling Organization Initiated

Customer Service RepresentativemessagesBuyer

Reason for Purchase Order

Change Identified

Start

Purchase Order Change RequestPurchase Order

change review

Purchase Order Change

accepted?

Purchase Order Change

Additional revisions to the Purchase Order Change or Cancel?

Purchase Order Cancel

Revisions

Yes

No

Cancel

Purchase Order Change Review

See Purchase Order Process

Cancellation of Purchase Order in

Sellers system

End

C1C2

C3

C3

Page 18: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

2012 GS1 Canada – Technical Standards Work Group - Foodservice EDI Page 18 of 57

Technical Standards Work Group – Foodservice Foodservice Business Process and EDI (GS1C11-513)

PROCESS: SHIPPING

Definition/Rational The shipping process is the logistics process of transferring of goods from the selling organization to the purchasing organization.

Actors

Customer Service Position processing the purchase order at the selling organization Purchasing Organization The Operator/Distributor/Provider that is purchasing product Selling Organization The Supplier/Manufacturer/Vendor/Broker that is selling the product Shipper Individual/Department responsible for preparing the shipment at the selling

organization Carrier Organization handling the delivery of shipment(s)

Process

1. Purchase Order Pre-requisite processes:

2. Purchase Order Change (Optional)

Shipping Process from Selling Organization

D1. The selling organization shipping department receives the purchase order from the selling organizations customer service.

D2. A carrier and shipping route is then determined (out of scope) and assigned to the purchase order. D3. The product is then picked from the warehouse, staged for shipping and loaded with the appropriate labels and

machine readable bar code. The Bill of Lading and/or Packing Slip is generated and included with the shipment (mandatory minimum of one).

D4. The bill of lading and/or packing slip contains the following information:

• Bill of lading/Packing slip date (mandatory) • Delivery date and time (mandatory) • PO number (s) (mandatory) • Bill of lading number and/or Packing slip number (mandatory) • Master bill of lading (optional) • Ship to (ID Number, Name and address) (mandatory) • Product identification (Description and GTIN) (mandatory) • Product quantities – variable or catch weight (mandatory) • Special instructions (optional) • Gross weight (mandatory) • Cube (optional) • Number of pallets/shipping units (optional) • Type of pallets (optional) • Product information may include

1. batch or lot codes, 2. dates such as best before, expiry, pack, etc 3. subject to regulatory and industry standards

• Selling organization tracking identification (tracking and tracing/traceability) (optional)

Page 19: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

2012 GS1 Canada – Technical Standards Work Group - Foodservice EDI Page 19 of 57

Technical Standards Work Group – Foodservice Foodservice Business Process and EDI (GS1C11-513)

D5. Once loaded the Carrier signs for the load and departs for the Purchasing Organization’s ship to location. D6. Optionally, the Advanced Ship Notice is generated by the Selling Organization and sent to the buying organization. The

Advanced Ship Notice includes the information on the Bill of Lading or Packing Slip plus: • Routing information (mandatory) • Pallet/Shipping Unit Label tag numbers (mandatory) • Packaging hierarchy with quantities (mandatory)

EDI Transaction Set(s) to support business process: • Shipping Notice / Manifest (856) (Advance Ship Notice –ASN)

Figure 3 – Shipping Process from Selling Organization

Shipping

messages Buying OrganizationShippingCustomer Service

Representative Carrier

Bill of Lading/Packing Slip

Purchase Order sent to shipping

Advanced Ship Notice(Optional)

Start

End

Shipping Route is determined

Product is picked and staged for

shipping

Product is loaded

Carrier signs for Load

See Receiving Process

D1 D2

D3 D4

D5

D6

Page 20: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

2012 GS1 Canada – Technical Standards Work Group - Foodservice EDI Page 20 of 57

Technical Standards Work Group – Foodservice Foodservice Business Process and EDI (GS1C11-513)

PROCESS: RECEIVING

Definition/Rational The receiving process is the logistics process of accepting delivery of goods from the carrier. Actors

Accounts Payable Position paying the invoice at the purchasing organization Carrier Organization handling the delivery of shipment(s) Purchasing Organization The Operator/Distributor/Provider that is purchasing product Receiver Organization handling the receipt of shipment(s) Selling Organization The Supplier/Manufacturer/Vendor/Broker that is selling the product

Process

1. Purchase Order Pre-requisite processes:

2. Purchase Order Change (Optional) 3. Shipping

Receiving Process to Purchasing Organization

E1. The Purchasing Organization optionally receives the Advanced Ship Notice. E2. The delivery arrives at the Purchasing Organizations ship to location. The delivery is then validated by the Receiver by

comparing the delivery/receiving schedule against the paperwork for the delivery. This validation checks the purchase order number, the delivery address, etc.

E3. Once passed the validation, the delivery arrives at the receiving dock. E4. The Receiver conducts a load inspection of

the inbound carrier prior to unloading to ensure: • clean, sanitary, pest-free, damage-free conditions • all hazardous chemicals and non-food products are kept separately from food products • that the carrier is capable of maintaining the proper temperature throughout the phases of travel

E5. Once passed the load inspection, the delivery is unloaded and verified.

For purchasing organizations that use

• Receive the ASN and compare against the requirements of the order

the Advanced Ship Notice the following validations are conducted (in no particular order):

• Approve condition of order (Inspect the conditions of the pallets, cases with food, products, or materials for signs of damage, pests, appropriate expiration dates, appropriate placement (e.g. off the floor) and signs of temperature abuse (e.g. wet packages))

• Scan each pallet bar code • Confirm that the number of pallets match the Advanced Ship Notice • An optional random audit comparing each detail on the Advanced Ship Notice against the shipment. A

scorecard for the Supplying Organization is maintained with these audits.

For purchasing organizations that do not use

• Confirm number of pallets, configuration and types of pallets

the Advanced Ship Notice the following validations are conducted (in no particular order): (all confirmations below are manual checks)

Page 21: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

2012 GS1 Canada – Technical Standards Work Group - Foodservice EDI Page 21 of 57

Technical Standards Work Group – Foodservice Foodservice Business Process and EDI (GS1C11-513)

• Approve condition of order (Inspect the conditions of the pallets, cases with food, products, or materials for signs of damage, pests, appropriate expiration dates, appropriate placement (e.g. off the floor) and signs of temperature abuse (e.g. wet packages))

• Confirm and record number of cases per item • Scan the case bar code • Confirm and record code dates • Confirm pack size • Confirm that the above matches the requirements of the order to the internal system.

Once the validations have been conducted, the product is accepted or declined. Refused product is held and arrangements are made to return them to the selling organization. Discrepancies are noted and can trigger an exception process (out of scope).

E6. The accepted product generates a receipt verification document (internal document) which is sent to Purchasing

Organization - Accounts Payable and then is put away or cross docked.

EDI Transaction Set(s) to support business process: • Shipping Notice / Manifest (856) (Advance Ship Notice –ASN)

Figure 4 - Receiving Process to Purchasing Organization

Receiving

messagesReceiving Accounts PayableCarriermessages

Start

Bill of Lading/Packing Slip

Carrier arrives at location with load

End

Advanced Ship Notice

(Optional)

Carrier brings load to dock

Delivery Validation

Delivery Contents Validation

Receipt VerificationLoad is put away

or cross docked

See Invoice Process

E1

E2

E3

E3

E5

E6

Load Inspection

E4

Page 22: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

2012 GS1 Canada – Technical Standards Work Group - Foodservice EDI Page 22 of 57

Technical Standards Work Group – Foodservice Foodservice Business Process and EDI (GS1C11-513)

PROCESS: INVOICE

Definition/Rational The invoice process includes the generating and issuing of the invoice by a selling organization to a bill-to organization. Actors

Accounts Payable Position paying the invoice at the purchasing organization Accounts Receivable Position issuing invoice and receiving payment at the selling organization Bill-to Organization Organization receiving invoices on behalf of the purchasing organization Purchasing Organization The Operator/Distributor/Provider that is purchasing product Selling Organization The Supplier/Manufacturer/Vendor/Broker that is selling the product

Process

1. Purchase Order Pre-requisite processes:

2. Purchase Order Change (Optional) 3. Shipping 4. Receiving

F1. Once the product is shipped an invoice is generated by the Selling Organization and sent to the Bill-To Organization. Invoice Process from Selling Organization

The invoice will contain the following information: • Invoice Date (mandatory) • Invoice Number (mandatory) • Purchasing Organization internal account number (optional) • Purchase Order Number(s) – Purchasing Organization (mandatory)

Note: Direct Store Delivery (DSD) or Direct Delivery may not have a purchase order number (out of scope) • Purchase Order Date(s) (optional) • Delivery/Pick up Date (optional) • Bill to and/or Sold to (ID Number, Name, Address and Telephone) (mandatory) • Ship to (ID Number, Name, Address and Telephone) (mandatory) • Remit to and/or Selling Organization (ID Number, Name, Address and Telephone) (mandatory) • Payment Terms (optional) • Carrier Delivery Information (freight on board – pre-paid or collect) (optional) • Taxes (Registration Numbers and tax amounts, levies and surcharges) (optional) • Special instructions (optional) • Total Invoice Amount Due (mandatory) • Total Invoice Weight (optional) • Total Invoice Piece Count (optional) • Product Information – line item level

1. Quantities (invoiced (mandatory), ordered or shipped (optional)) • Catch weight (mandatory when applicable)

2. Item description (optional) 3. Product GTIN (mandatory) 4. Unit Price (mandatory) 5. Extended Price (optional) 6. Pack Size (optional) 7. Rebates and allowances or charges (optional) 8. Taxes (registration numbers and tax amounts, levies and surcharges) (optional) 9. Deposit (bottle, barrels, crates, etc.) (optional)

Page 23: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

2012 GS1 Canada – Technical Standards Work Group - Foodservice EDI Page 23 of 57

Technical Standards Work Group – Foodservice Foodservice Business Process and EDI (GS1C11-513)

Invoice process from Purchasing Organization

F2. The bill-to organization receives the invoice and reconciles the invoice against the purchase order and the receipt verification document. The invoice can then be acknowledged (accepted, rejected or contact for clarification). If accepted, Accounts Payable is notified that the invoice is approved to pay.

EDI Transaction Set(s) to support business process: • Invoice (810)

Figure 5 - Invoice Process from Selling Organization

Invoice

messagesBill To Organization Accounts PayablemessagesSelling Organization

Invoice Document is created

Invoice

Start

Invoice Review Acceptance

messageSee Payment

Process

F1 F2

Page 24: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

2012 GS1 Canada – Technical Standards Work Group - Foodservice EDI Page 24 of 57

Technical Standards Work Group – Foodservice Foodservice Business Process and EDI (GS1C11-513)

PROCESS: PAYMENT (Remittance)

Definition/Rational The payment process provides reconciliation of the invoice to the payment by the purchasing organization to the selling organization.

Actors Accounts Payable Position paying the invoice at the purchasing organization Accounts Receivable Position issuing invoice and receiving payment at the selling organization Purchasing Organization The Operator/Distributor/Provider that is purchasing product Selling Organization The Supplier/Manufacturer/Vendor/Broker that is selling the product

Process

1. Purchase Order Pre-requisite processes:

2. Purchase Order Change (Optional) 3. Shipping 4. Receiving 5. Invoice

G1. The Accounts Payable group generates a payment transfer and confirms payment to the Bank and Selling Organization. Alternatively, a cheque may be issued by accounts payable. Remittance advice is transmitted to accounts receivable - selling organization.

Payment Remittance by Purchasing Organization

The remittance advice will contain the following information:

• Payment Remittance Date (mandatory) • Payment / Cheque Number (mandatory) • Remit to and/or Selling Organization (ID Number, Name, Address and Telephone) (mandatory) • Purchase Order Number(s) – Purchasing Organization (optional) • Bill to and/or Sold to (ID Number, Name, Address and Telephone) (mandatory) • Total Remittance Amount Paid (mandatory)

Note: may cover multiple invoices • Remittance Detail –

1. Invoice Number (mandatory) line item level

2. Invoice Total Amount (mandatory) 3. Invoice Payment Amount (mandatory)

Remittance Process by Selling Organization

G2. Accounts Receivable will receive the remittance advice. The remittance is reconciled against the bank statement or cheque.

G3. The payment is applied to the Purchasing Organizations buying account. Any discrepancies are resolved (out of scope)

Page 25: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

2012 GS1 Canada – Technical Standards Work Group - Foodservice EDI Page 25 of 57

Technical Standards Work Group – Foodservice Foodservice Business Process and EDI (GS1C11-513)

EDI Transaction Set(s) to support business process: • Payment Order / Remittance Advice (820)

Figure 6 - Payment Remittance by Purchasing Organization

Payment

Accounts ReceivablemessagesAccounts Payable

Remittance

End

Start

Payment transfer or cheque is generated

Reconcile Payment and Remittance

Payment/cheque

Payment applied to account

G1 G2

G3

Page 26: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

2012 GS1 Canada – Technical Standards Work Group - Foodservice EDI Page 26 of 57

Technical Standards Work Group – Foodservice Foodservice Business Process and EDI (GS1C11-513)

APPENDIX 1: TRANSACTION SETS AND MAINTENANCE SUBMISSION The following transactions will be used for reference.

• 810 Invoice

Version 4010 Updated 2012:

• 820 Remittance Advice • 850 Purchase Order • 855 Purchase Order Acknowledgment • 856 Ship Notice / Manifest (ASN Advance Ship Notice) • 860 Purchase Order Change – Buyer Initiated • 997 Functional Acknowledgment

As business processes change, the EDI transactions supporting them may require modification.

Maintenance Submission Information

The following working sheet contains the data you need to submit in the online GS1 Canada Standards Requirement Request System. Note: This worksheet is to assist in the collection of information from your various departments. To submit a Standards Requirements Request to GS1 Canada for industry review, the following is required:

1. Submitting organization must be a GS1 Canada member in good standing. 2. This form is to be used as a worksheet to collect and record information. 3. Final Change Request must be completed in full and submitted online. Go to

http://www.gs1ca.org/page.asp?LSM=1&intNodeID=944&intPageID=733. a. Select the EDI change request form.

For more information about the maintenance process contact:

Rita Laur Director, Standards GS1 Canada 1500 Don Mills Road, Suite 800 Toronto, Ontario M3B 3L1 Email : [email protected] Phone: (416) 380-2509 Fax: (416) 510-1916 Website: www.gs1ca.org

Page 27: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

2012 GS1 Canada – Technical Standards Work Group - Foodservice EDI Page 27 of 57

Technical Standards Work Group – Foodservice Foodservice Business Process and EDI (GS1C11-513)

GS1 Canada Requirement Request Work Sheet A – SUBMITTER

Submission Date _____________________

Submitter Name _____________________

Representing Company:

_____________________ Title: _____________________________

Address: _____________________ Phone: ( ) -

E-mail: ______________________________________________________________

Industry Sector – Healthcare, General Merchandise, Hardlines, Grocery, Foodservice, Rx, Other.

Industry Type: Provider, Supplier/Manufacturer, Retailer/Distributor, Broker, Other.

B – PROPOSED ACTION List specific addition(s) or change(s) required, if known, to be included in the standard and implementation guidelines that satisfy the business need. (If necessary, attach additional documentation.)

C – EXPECTED BENEFITS, OPPORTUNITIES FOR EARLY ADOPTION Explain what business benefits or opportunities may be realized by this request and list those organizations, apart from the submitters, who will benefit from the resulting solution. (If necessary, attach additional documentation.)

D – BUSINESS FUNCTION/PURPOSE Explain, in detail, the business function, operation or problem that will be satisfied by the request. (I.e. what is the request accomplishing from a business or carrier performance perspective?) (If necessary, attach additional documentation.)

EDI

E – RAMIFICATIONS

List only those areas that will be used by the business function

Transaction Set(s) ID and Name:

Other:

Segment(s) ID and Other:

Data Elements:

Architecture Guide:

Business Example:

Functional Profiles:

Requires ASC X12 Change:

F – STANDARDS MAINTENANCE COMMITTEE ACTION

Internal use only, used for submitter status and tracking

Approved Approved as Modified Deferred

Disapproved Referred to Task Group Withdrawn by Submitter

Comments:

Signature: Date: On behalf of the company or industry group identified above, the submitter warrants that he/she has the right to submit the above material for changes to editing, or development of new, standards. By submitting the material above, you warrant that either the material is not copyrighted or that the owner of any copyrighted material hereby gives a royalty-free license to GS1 to use the submitted material in a GS1 standard. GS1 standards are open and available for use. Our standards are copyrighted to prevent misuse of the standard. GS1 will freely grant any legitimate request for use of its standards.

Page 28: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

2012 GS1 Canada – Technical Standards Work Group - Foodservice EDI Page 28 of 57

Technical Standards Work Group – Foodservice Foodservice Business Process and EDI (GS1C11-513)

APPENDIX 1: MAINTENANCE SUBMISSION Form completed

GS1 Canada Requirement Request Work Sheet A – SUBMITTER

Submission Date January 27, 2012

Submitter Name Full Name

Representing Company: Organization Name Title: Submitter’s Title

Address: 123 Street, City, Province Postal

Phone: (123) 234-5678

E-mail: [email protected]

Industry Sector – Foodservice

Industry Type: Provider, Supplier/Manufacturer, Retailer/Distributor, Broker, Other.

B – PROPOSED ACTION List specific addition(s) or change(s) required, if known, to be included in the standard and implementation guidelines that satisfy the business need. (If necessary, attach additional documentation.)

• ADD segment W6 – Special Handling Information to both the EDI Purchase Order (850) and Purchase Order Acknowledgment (855)

• In the Header at position 1/0300 • With W601 Data Element 152 Special Handling Code • Code Value – RO Rush Order

C – EXPECTED BENEFITS, OPPORTUNITIES FOR EARLY ADOPTION Explain what business benefits or opportunities may be realized by this request and list those organizations, apart from the submitters, who will benefit from the resulting solution. (If necessary, attach additional documentation.)

We have identified that a Rush Order is not an order type but rather a handling requirement of an order and needs to be identified in the header of the communication.

D – BUSINESS FUNCTION/PURPOSE Explain, in detail, the business function, operation or problem that will be satisfied by the request. (I.e. what is the request accomplishing from a business or carrier performance perspective?) (If necessary, attach additional documentation.)

By modifying the existing standards the implementation guideline would allow businesses to have a standard way to communicate the urgency needed to handle the order

Page 29: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

2012 GS1 Canada – Technical Standards Work Group - Foodservice EDI Page 29 of 57

Technical Standards Work Group – Foodservice Foodservice Business Process and EDI (GS1C11-513)

GS1 Canada Requirement Request Work Sheet X EDI

E – RAMIFICATIONS

List only those areas that will be used by the business function

Transaction Set(s) ID and Name: 850 Purchase Order and 855 Purchase Order Acknowledgment

Other:

Segment(s) ID and Other: W6 Special Handling Information

Data Elements: W601 Data Element 152 Special Handling Code

Architecture Guide:

Business Example:

Functional Profiles: Canadian FOODSERVICE v4010-2012

Requires ASC X12 Change:

F – STANDARDS MAINTENANCE COMMITTEE ACTION Internal use only, used for submitter status and tracking

Approved Approved as Modified Deferred

Disapproved Referred to Task Group Withdrawn by Submitter

Comments:

Signature: Date:

On behalf of the Company or Industry Group identified above, the submitter warrants that he/she has the right to submit the above material for changes to exiting, or development of new, standards. By submitting the material above, you warrant that either the material is not copyrighted or that the owner of any copyrighted material hereby gives a royalty free license to GS1 to use the submitted material in a GS1 standard. GS1 standards are open and available for use. Our standards are copyrighted to prevent misuse of the standard. GS1 will freely grant any legitimate request for use of its standards.

Page 30: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

2012 GS1 Canada – Technical Standards Work Group - Foodservice EDI Page 30 of 57

Technical Standards Work Group – Foodservice Foodservice Business Process and EDI (GS1C11-513)

APPENDIX 2: BUSINESS EXAMPLES

Business Examples A The following suite of foodservice business examples marked Suite A. These business process only includes 4 tranaction sets covering from the purchase order to the invoice. Note: A functional acknowlegment (997) is communicated as a response to each transaction sent. For outbound transactions the expectation is to receive a 997 acknowledgment. For inbound the 997 is sent immediately upon receipt of the inbound transaction.

EDI TRANSMISSION DATA EXPLANATION

850 – Purchase Order Customer sending a Purchase order to the Vendor requesting 4 materials be delivered Jan 16, 2012

855 – Purchase Order Acknowledgment

Transaction from Vendor to Customer confirming receipt of PO and confirming timing, quantities and pricing.

860 – Purchase Order Change Purchase order change requesting the removal of line item 00030, and quantity adjustment of line item 00040

810 - Invoice Invoice from Vendor to Customer summarizing product shipped, referencing the Customer’s purchase order and providing quantities, pricing and codes for the materials shipped.

The following purchase order covers a new order. Identifies the appropriate contacts, how the payment terms will be conducted, and the expected delivery dates while identifying where the product is being shipped to and in this case the bill to is different. There are 4 products being ordered showing quanities, price, GTINs and description. Also, for one of the items a contract number is being used as a reference, this will be used in the invoice when matching product for payment. The other 3 products do not have a reference to a contract.

EDI TRANSMISSION DATA EXPLANATION

ST*850*0001

Start of the transaction set 850 - Transaction Set Identifier Code for the PO Transaction Set 0001 - Transaction Set Control Number

BEG*00*NE*4500876263**20111221 Beginning of a PO transaction set; transmits identifying numbers and dates 00 –Transaction Set Purpose Code, indicating this is an original purchase order NE - PO Type Code, indicating this is a New Order 4500876263 - PO Number 20111221 - PO Date (December 21, 2011)

PER*BD*Jane Smith*TE*504-555-2398*EM*[email protected]

Identifying information BD - Reference Number Qualifier, indicating the buyer/department placing the order Jane Smith - Buyer/department name TE - Telephone number will follow 504-555-2398 - Telephone number EM - Email to follow [email protected] - Email address

PER*IC*John Doe Identifying information IC – Information Contact

Page 31: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

2012 GS1 Canada – Technical Standards Work Group - Foodservice EDI Page 31 of 57

Technical Standards Work Group – Foodservice Foodservice Business Process and EDI (GS1C11-513)

EDI TRANSMISSION DATA EXPLANATION

John Doe – Order contact name FOB*PP*DE

FOB Related Information PP – Prepaid (by seller) DE – Destination (shipping)

ITD*08*3*2**10**30 Terms of sale 08 - Terms Type Code, indicating the terms as Basic Discount Offered 3 - Terms Basis Date Code, indicating the Invoice Date as the beginning of the terms period 2 - Terms Discount Percent available to the purchaser if an invoice is paid on or before the Terms Discount Days Due 10 - Terms Discount Days Due 30 - Terms Net Days

DTM*002*20120116

Date / Time Reference 002 – Requested Delivery 20120116 – Jan 16, 2012

N1*BT**UL*0012345000015 Party by type of organization, name, and code BT - Entity Identifier Code indicating the Bill To Party UL - Identification Code Qualifier, indicating that the following identification code is the Global Location Number (GLN) 0012345000015 - 13-digit GLN

N1*ST*Customer Ship to*UL*0012345023008

Party by type of organization, name, and code ST - Entity Identifier Code, indicating this N1 segment identifies the Ship To location Customer Ship to - Name of the Ship To Location UL - Identification Code Qualifier, indicating that the following Identification code is the GLN 0012345023008 - 13-digit GLN

N3*82 1st street Street address of the Ship To Location 82 1st street - Delivery street address

N4*Toronto*ON*A1B 2C3 Address (including city/town, province/state and postal code/zip code) of the Ship To Location Toronto - City portion of the delivery address ON - Two-character province code A1B 2C3 - Postal Code

N1*VN*VENDOR ABC*UL*0011234530235

Party by type of organization, name, and code VN - Entity Identifier Code, indicating this N1 segment identifies the Vendor UL - Identification Code Qualifier, indicating that the following Identification code is the GLN 0011234530235 - 13-digit GLN

PO1*00010*67200*EA*33.33**UK*000666666123459

Basic line item data 00010 - Number of the line item 67200 - Quantity ordered EA - UOM code, indicating Each 33.33 - Unit Price of the product ($33.33) UK - Following value is a SCC14 (UCC/EAN-14 Shipping Container Code (1-2-5-5-1)) 00066666123459 - 14-digit GTIN

PID*F****CRAB BOIL 3KG Description of the product being ordered F – Free form CRAB BOIL 3KG – Description of the Product

REF*CT*4600092394 Reference identification

Page 32: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

2012 GS1 Canada – Technical Standards Work Group - Foodservice EDI Page 32 of 57

Technical Standards Work Group – Foodservice Foodservice Business Process and EDI (GS1C11-513)

EDI TRANSMISSION DATA EXPLANATION

CT – Contract number will follow 4600092394 – Contract number

PO1*00020*86400*EA*74.02**UK*00066666000026

Basic line item data 00020 - Number of the line item 86400 - Quantity ordered EA - UOM code, indicating Each 74.02 - Unit Price of the product ($74.02) UK - Following value is a SCC14 (UCC/EAN-14 Shipping Container Code (1-2-5-5-1)) 00066666000026 - 14-digit GTIN

PID*F****JAMBALAYA PASTA 6.7 KG

Description of the product being ordered F – Free form JAMBALAYA PASTA 6.7 KG - Description of the product

PO1*00030*14400*EA*74.02**UK*00066666000037

Basic line item data 00030 - Number of the line item 14400 - Quantity ordered EA - UOM code, indicating Each 74.02 - Unit Price of the product ($74.02) UK - Following value is a SCC14 (UCC/EAN-14 Shipping Container Code (1-2-5-5-1)) 00066666000037 - 14-digit GTIN

PID*F****GUMBO PASTA 5.5KG Description of the product being ordered F – Free form GUMBO PASTA 5.5KG - Description of the product

PO1*00040*14400*EA*74.02**UK*00066666000048

Basic line item data 00040 - Number of the line item 14400 - Quantity ordered EA - UOM code, indicating Each 74.02- Unit Price of the product ($74.02) UK - Following value is a SCC14 (UCC/EAN-14 Shipping Container Code (1-2-5-5-1)) 00066666000048 - 14-digit GTIN

PID*F****SOUTHERN STROGANOFF PASTA 6.5 KG

Description of the product being ordered F – Free form SOUTHERN STROGANOFF PASTA 6.5 KG - Description of the product

SUMMARY CTT*4 Transmits the total number of line items

4 - Number of line items (PO1 segments) present in this transaction set

SE*22*0001 Shows the end of the transaction set. 22 - Number of Included Segments in this transaction set, including the ST and SE segments 0001 - Transaction Set Control Number (value must match the ST segment (ST02) of the transaction set)

Page 33: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

2012 GS1 Canada – Technical Standards Work Group - Foodservice EDI Page 33 of 57

Technical Standards Work Group – Foodservice Foodservice Business Process and EDI (GS1C11-513)

The supplier in the following purchase order acknowledgment has confirmed receipt of the purchase order and acknowledging “with detailing, no change” The detail includes confirmation of the payment terms, requested delivery date for all the items. Confirming each trade item, quantity, price and GTIN Note: the single product ordered with a contract number does not return the contract number – it will appear in the invoice.

EDI TRANSMISSION DATA EXPLANATION

ST*855*0001 Start of the transaction set 855 - Transaction Set Identifier Code for the PO Transaction Set 0001 - Transaction Set Control Number

BAK*00*AD*4500876263*20111221 Transaction Set Purpose Code 00 - Original AD - Acknowledge - With Detail, No Change 4500876263 – Purchase Order Number 20111221 – Purchase Order Date

ITD*08*3*2**10**30 Terms of sale 08 - Terms Type Code, indicating the terms as Basic Discount Offered 3 - Terms Basis Date Code, indicating the Invoice Date as the beginning of the terms period 2 - Terms Discount Percent available to the purchaser if an invoice is paid on or before the Terms Discount Days Due 10 - Terms Discount Days Due 30 - Terms Net Days

DTM*002*20120116 Date / Time Reference 002 – Requested Delivery 20120116 – Jan 16, 2012

PO1*00010*67200*EA*33.33**UK*00066666123459

Basic line item data 00010 - Number of the line item 67200 - Quantity ordered EA - UOM code, indicating Each 33.33 - Unit Price of the product ($33.33) UK - Following value is a SCC14 (UCC/EAN-14 Shipping Container Code (1-2-5-5-1)) 00066666123459 - 14-digit GTIN

PO1*00020*86400*EA*74.02**UK*00066666000026

Basic line item data 00020 - Number of the line item 86400 - Quantity ordered EA - UOM code, indicating Each 74.02 - Unit Price of the product ($74.02) UK - Following value is a SCC14 (UCC/EAN-14 Shipping Container Code (1-2-5-5-1)) 00066666000026 - 14-digit GTIN

PO1*00030*14400*EA*74.02**UK*00066666000037

Basic line item data 00030 - Number of the line item 14400 - Quantity ordered EA - UOM code, indicating Each 74.02 - Unit Price of the product ($74.02) UK - Following value is a SCC14 (UCC/EAN-14 Shipping Container Code (1-2-5-5-1)) 00066666000037 - 14-digit GTIN

PO1*00040*14400*EA*74.02**UK*00066666000048

Basic line item data 00040 - Number of the line item 14400 - Quantity ordered

Page 34: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

2012 GS1 Canada – Technical Standards Work Group - Foodservice EDI Page 34 of 57

Technical Standards Work Group – Foodservice Foodservice Business Process and EDI (GS1C11-513)

EDI TRANSMISSION DATA EXPLANATION EA - UOM code, indicating Each 74.02- Unit Price of the product ($74.02) UK - Following value is a SCC14 (UCC/EAN-14 Shipping Container Code (1-2-5-5-1)) 00066666000048 - 14-digit GTIN

CTT*4 Transmits the total number of line items 4 - Number of line items (PO1 segments) present in this transaction set

SE*10*0001 Shows the end of the transaction set. 13 - Number of Included Segments in this transaction set, including the ST and SE segments 0001 - Transaction Set Control Number (value must match the ST segment (ST02) of the transaction set)

Page 35: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

2012 GS1 Canada – Technical Standards Work Group - Foodservice EDI Page 35 of 57

Technical Standards Work Group – Foodservice Foodservice Business Process and EDI (GS1C11-513)

The buyer has initiated a change to an earlier purchase order to their supplier. The changes include a cancellation / deletion of one product and a quantity change to another. For the product that has quantity change, the GTIN, Price and quantity are included. This transaction has included a total dollar amount for reference. The total is the full amount of the revised purchase order. Note: header information is always repeated to ensure accurate, consistent information is being communicated.

EDI TRANSMISSION DATA EXPLANATION

ST*860*0001

Start of the transaction set 860 - Transaction Set Identifier Code for the PO Transaction Set 0001 - Transaction Set Control Number

BCH*04*SA*4500876263***20111221*****20120106

Beginning Segment for Purchase Order Change 04 – Represents this is a change request SA – Stand-alone Order 4500876263 – Purchase Order Number 20111221 – Purchase Order date 20120106 – Purchase Order Change Request Date

PER*BD*Jane Smith*TE*504-555-2398*EM*[email protected]

Identifying information BD - Reference Number Qualifier, indicating the buyer/department placing the order Jane Smith - Buyer/department name TE - Telephone number will follow 504-555-2398 - Telephone number EM - Email to follow [email protected] - Email address

PER*IC*John Doe Identifying information IC – Information Contact John Doe – Order contact name

FOB*PP*DE FOB Related Information PP – Prepaid (by seller) DE – Destination (shipping)

ITD*08*3*2**10**30 Terms of sale 08 - Terms Type Code, indicating the terms as Basic Discount Offered 3 - Terms Basis Date Code, indicating the Invoice Date as the beginning of the terms period 2 - Terms Discount Percent available to the purchaser if an invoice is paid on or before the Terms Discount Days Due 10 - Terms Discount Days Due 30 - Terms Net Days

N1*VN**UL*0011234530235 Party by type of organization, name, and code VN - Entity Identifier Code, indicating this N1 segment identifies the Vendor UL - Identification Code Qualifier, indicating that the following identification code is the Global Location Number (GLN) 0011234530235 - 13-digit GLN

N1*BT**UL*0012345000015 Party by type of organization, name, and code BT - Entity Identifier Code indicating the Bill To Party UL - Identification Code Qualifier, indicating that the following identification code is the Global Location Number (GLN) 0012345000015 - 13-digit GLN

N1*ST*Customer Ship Party by type of organization, name, and code

Page 36: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

2012 GS1 Canada – Technical Standards Work Group - Foodservice EDI Page 36 of 57

Technical Standards Work Group – Foodservice Foodservice Business Process and EDI (GS1C11-513)

EDI TRANSMISSION DATA EXPLANATION

to*UL*0012345023008 ST - Entity Identifier Code, indicating this N1 segment identifies the Ship To location Customer Ship to - Name of the Ship To Location UL - Identification Code Qualifier, indicating that the following Identification code is the GLN 0012345023008 - 13-digit GLN

N3*82 1st street Street address of the Ship To Location 82 1st street - Delivery street address

N4*Toronto*ON*A1B 2C3 Address (including city/town, province/state and postal code/zip code) of the Ship To Location Toronto - City portion of the delivery address ON - Two-character province code A1B 2C3 - Postal Code

POC*00030*DI******UK*00066666000037

Line Item Change 00030 – Number of the line item DI – Delete Item from the purchase order UK - Following value is a SCC14 (UCC/EAN-14 Shipping Container Code (1-2-5-5-1)) 00066666000037 – 14 digit GTIN

PID*F****GUMBO PASTA 5.5 KG Product Item Description F - Free Form GUMBO PASTA 5.5 KG – Product description

POC*00040*RZ*11200*0*EA*74.02**UK*00066666000048

Line Item Change 00040 – Number of the line item RZ – Replace All Values 11200 – New order quantity 0 – Quantity left to receive EA – unit of measure 74.02 – Price UK - Following value is a SCC14 (UCC/EAN-14 Shipping Container Code (1-2-5-5-1)) 00066666000048 – 14 digit GTIN

PID*F****SOUTHERN STROGANOFF PASTA 6.5 KG

Product Item Description F - Free Form SOUTHERN STROGANOFF PASTA 6.5 KG - Product description

CTT*2*25600 Transmits the total number of line items 2 - Number of line items (PO1 segments) present in this transaction set

SE*16*0001 Shows the end of the transaction set. 16 - Number of Included Segments in this transaction set, including the ST and SE segments 0001 - Transaction Set Control Number (value must match the ST segment (ST02) of the transaction set)

Page 37: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

2012 GS1 Canada – Technical Standards Work Group - Foodservice EDI Page 37 of 57

Technical Standards Work Group – Foodservice Foodservice Business Process and EDI (GS1C11-513)

The fourth transaction used in this suite of examples in the invoice. It contains the Invoice Date, Number, the original purchase order date and number as well as the suppliers’ location identification number (GLN). Additional information included is the address of buyer organization – bill to, street address of the ship to location, the city and postal. The Terms of Sale for each line item with the quantity, price, GTIN and the vendor material number with description.

The dollar total is included with the number line items.

EDI TRANSMISSION DATA EXPLANATION

ST*810*0001 Start of the transaction set 810 - Transaction Set Identifier Code for the PO Transaction Set 0001 - Transaction Set Control Number

BIG*20120116*2320155674*20110902*4500876263

Beginning Segment of the Invoice 20120116 - Invoice date 2320155674 – Invoice number 20110902 – Original PO date 4500876263 – Original PO number

N1*VN*VENDOR ABC*UL*0011234530235

Party by type of organization, name, and code VN - Entity Identifier Code, indicating this N1 segment identifies the Vendor UL - Identification Code Qualifier, indicating that the following Identification code is the GLN 0011234530235 - 13-digit GLN

N1*BS*CUSTOMER ABC*UL*0012345000015

Party by type of organization, name, and code BS – Bill and Ship To CUSTOMER ABC – Customer name UL - Identification Code Qualifier, indicating that the following Identification code is the GLN 0012345000015 - 13-digit GLN

N3*PO BOX 168*ATTN ACCOUNTS PAYABLE

Street address of the Ship To Location PO BOX 168 – Address information ATTN ACCOUNTS PAYABLE – Additional address information

N4*TORONTO*ON*A1B 2C3 Address (including city/town, province/state and postal code/zip code) of the Ship To Location Toronto - City portion of the delivery address ON - Two-character province code A1B 2C3 - Postal Code

ITD*14**1**10**30*****1% 10, NET 30 D

Terms of sale 14 – Previously Agreed Upon 1 – 1% discount 10 – Terms Discount Days Due 30 – Terms Net Days 1% 10, NET 30 D - Free form description

IT1*00010*67200*EA*33.3* *UK*00066666123459

Line Item details 00010 – Number of the line item 67200 - Quantity EA – Unit of Measure 33.3 - Price UK - Following value is a SCC14 (UCC/EAN-14 Shipping Container Code (1-2-5-5-1)) 00066666123459 – 14 digit GTIN

PID*F****CRAB BOIL Description of the product being ordered F – Free Form CRAB BOIL - Description of the product

Page 38: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

2012 GS1 Canada – Technical Standards Work Group - Foodservice EDI Page 38 of 57

Technical Standards Work Group – Foodservice Foodservice Business Process and EDI (GS1C11-513)

EDI TRANSMISSION DATA EXPLANATION

IT1*00020*86400*EA*74.02* *UK*00066666000026

Line Item details 00020 – Number of the line item 86400 - Quantity EA – Unit of Measure 74.02 - Price UK - Following value is a SCC14 (UCC/EAN-14 Shipping Container Code (1-2-5-5-1)) 00066666000026 – 14 digit GTIN

PID*F****JAMBALAYA PAST Description of the product being ordered F – Free form JAMBALAYA PAST - Description of the product

IT1*00040*11200*EA*74.02* *UK*00066666000048

Line Item details 00040 – Number of the line item 11200 - Quantity EA – Unit of Measure 74.02 - Price UK - Following value is a SCC14 (UCC/EAN-14 Shipping Container Code (1-2-5-5-1)) 00066666000048 – 14 digit GTIN

PID*F****STROGANOFF PAS Description of the product being ordered F – Free form STROGANOFF PAS - Description of the product

TDS*2822867*2822867 Total Monetary Value Summary 2822867 - $28228.67 2822867 - Discount based on $28228.67

CTT*3 Transmits the total number of line items 3 - Number of line items (PO1 segments) present in this transaction set

SE*17*0001 Shows the end of the transaction set. 17 - Number of Included Segments in this transaction set, including the ST and SE segments 0001 - Transaction Set Control Number (value must match the ST segment (ST02) of the transaction set)

Page 39: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

2012 GS1 Canada – Technical Standards Work Group - Foodservice EDI Page 39 of 57

Technical Standards Work Group – Foodservice Foodservice Business Process and EDI (GS1C11-513)

Business Examples B

Document 850 – Purchase Order A foodservice supply company in Red Deer, AB – Korner Café – wishes to acquire 8 cases of Neilson Ultimate Chocolate 500 ml drink and 6 cases of Nestle Coffee Crisop Milkshake 473 ml drinks. While it requires the physical products, its Accounts Payable is handled at its head office – Super Cafes – located in Gimli, MB. The supplier/vendor of the product is Prods R Us of Herzog, BC. The EDI Purchase Order below identifies the purchasing entity (Korner Kafe), the paying entity (Super Cafes) and the supplying entity (Prods R Us) in the header. In the details it identifies the desired products, the anticipated price and provides descriptive information to assure the product information is interpreted correctly (both product descriptions and the case size) along with their specific GTINs.

EDI TRANSMISSION DATA EXPLANATION

ST*850*0001 ST – Start of the Transaction Set (Document) 850 - Transaction Set Identifier Code for the PO Transaction Set 0001- Transaction Set Control Number

BEG*00*SA*549044-57**20110930 BEG – Beginning Segment for Purchase Order 00 - Transaction Set Purpose Code, indicating this is an original purchase order SA - PO Type Code, indicating this is a Stand Alone PO 549044-57 - PO Number 20110930 - PO Date (September 30, 2011)

FOB*PP FOB – FOB Related Instructions PP – Shipment Prepaid by Seller

DTM*002*20111013*0500 DTM – Date/Time Reference 002 - Qualifier - Requested Delivery Date 20111013 - Date (October 13, 2011) 0500 – 05:00 local time (24-hour clock)

N9*AH*549044-57 N9 – Reference Identification AH – Agreement Number 549044-57 – number of the agreement (PO number)

MSG*DELIVER TO BACK DOOR MSG – Message Text DELIVER TO… - Freeform text message

N1*SU*PRODS R US *UL*1234567890123

N1 – Name SU - Entity ID Code – Supplier Information PRODS R US - Name of the Supplier UL – ID Qualifier - Global Location Number (GLN) 1234567890123 - 13-digit Supplier GLN

N1*BT*SUPER CAFES*UL*3210123456789

N1 – Name BT - Entity ID Code – Bill-To Information SUPER CAFES - Name of the Bill-To Entity UL – ID Qualifier - Global Location Number (GLN) 3210123456789 - 13-digit Bill-To Entity GLN

N3*1324 GROSVENOR BLVD N3 – Address Information (referring to last N1) 1324… - Address line (maybe repeated if multiple lines required)

N4*GIMLI*MB*R2Y 5S5*CA N4 – Geographic Location (referring to last N1) GIMLI – City MB – Province R2Y 5S5 – Postal Code CA - Country Code

N1*ST*KORNER CAFÉ*UL*6780123456789

N1 – Name ST - Entity ID Code – Ship-To Information

Page 40: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

2012 GS1 Canada – Technical Standards Work Group - Foodservice EDI Page 40 of 57

Technical Standards Work Group – Foodservice Foodservice Business Process and EDI (GS1C11-513)

EDI TRANSMISSION DATA EXPLANATION

KORNER CAFÉ - Name of the Ship-To Entity UL – ID Qualifier - Global Location Number (GLN) 6780123456789- 13-digit Ship-To Entity GLN

N3*UNIT 12 FLOOR 17 N3 – Address Information (referring to last N1) UNIT 12… - Address line (maybe repeated if multiple lines required)

N3*15 STREET WEST N3 – Address Information (referring to last N1) 15 STREET… - Address line (maybe repeated if multiple lines required)

N4*RED DEER*AB*T4N 3X1*CA N4 – Geographic Location (referring to last N1) RED DEER – City AB – Province T4N 3X1 – Postal Code CA - Country Code

PO1**8*CA*23.1**UK*10066800025510

PO1 - Basic Line Item Data 8 - Quantity ordered CA - UOM code, indicating Case 23.1 - Unit Price of the product ($23.10) UK - Following value is a SCC14 (UCC/EAN-14 Shipping Container Code (1-2-5-5-1)) 10066800025510 - 14-digit GTIN

PID*F****NEILSON ULTIMATE CHOC 500 ML

PID – Product/Item Description F – Description Type – Free-Form NEILSON… - Product Description

PO4*12 PO4 – Item Physical Details 12 – Pack - 12-Pack

PO1**6*CA*23.31**UK*10066800020249

PO1 - Basic Line Item Data 6 - Quantity ordered CA - UOM code, indicating Case 23.21 - Unit Price of the product ($23.21) UK - Following value is a SCC14 (UCC/EAN-14 Shipping Container Code (1-2-5-5-1)) 10066800020249 - 14-digit GTIN

PID*F****NESTLE COFFEE CRISP MILKSHAKE 473 ML

PID – Product/Item Description F – Description Type – Free-Form NESTLE… - Product Description

PO4*12 PO4 – Item Physical Details 12 – Pack - 12-Pack

CTT*2 CTT – Transaction Totals 2 – Two Line Items

SE*21*564310003 End of the transaction set. 21 - Number of Included Segments in this transaction set, including the ST and SE segments 564310003- Transaction Set Control Number (value must match the ST segment (ST02) of the transaction set)

Page 41: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

2012 GS1 Canada – Technical Standards Work Group - Foodservice EDI Page 41 of 57

Technical Standards Work Group – Foodservice Foodservice Business Process and EDI (GS1C11-513)

Document 856 – Ship Notice/Manifest Having received the PO and prepared shipment, Prods R Us sends a Ship Notice back to Korner Kafe to provide warning as to what products have been shipped, by which method it has been shipped, who is performing the shipping and what pallets/container identification has been attached to the load. An association is also provided between the purchase order and physical shipment for traceability purposes. If appropriate, multiple orders may be detailed in a single load manifest. There will be one ship notice per physical load to the receiving location, although each manifest may contain multiple orders (each will be appropriately referenced in the document).

EDI TRANSMISSION DATA EXPLANATION

ST*856*1004 ST – Start of the Transaction Set (Document) 856 - Transaction Set Identifier Code for the Ship Notice 1004 - Transaction Set Control Number

BSN*00*06*20111005*1127*0001 BEG – Beginning Segment for Ship Notice 00 - Transaction Set Purpose Code – Original Notice 06 – Shipment Identification Number 20111005 – Date 1127 – Time 0001 – Hierarchal Structure Code – Shipment, Order, Packaging, Item

HL*1**S HL – Hierarchical Level 1 – Hierarchical ID Number S – Hierarchical Level Code - Shipment

TD1*PLT94*500****G*103.0*KG TD1 – Carrier Details (Quantity & Weight) PLT94 – Packing Code – Wooden Pallet G – Weight Qualifier – Gross Weight 103.0 – Weight KG – Weight Unit of Measure

TD5*B***M*TRANSX RAIL*CC TD5 – Carrier Details (Routing Sequence/Transit Time) B – Routing Sequence Code – Origin/Delivery Carrier M – Transportation Method/Type Code – Motor (Common Carrier) TRANSX RAIL – Routing CC – Shipment Status Code – Shipment Complete

TD3*TL TD3 – Carrier Details (Equipment) TL – Equipment Description Code – Trailer

REF*BM*INV5948591 REF – Reference Identification BM – Reference ID Qualifier – Bill of Lading Number INV5948591 – Reference Identification

DTM*011*20111005 DTM – Date/Time Reference 011 - Qualifier - Shipped 20111013 - Date (October 05, 2011)

N1*ST*KORNER CAFÉ*UL*6780123456789

N1 – Name ST - Entity ID Code – Ship-To Information KORNER CAFÉ - Name of the Ship-To Entity UL – ID Qualifier - Global Location Number (GLN) 6780123456789- 13-digit Ship-To Entity GLN

N3*UNIT 12 FLOOR 17 N3 – Address Information (referring to last N1) UNIT 12… - Address line (maybe repeated if multiple lines required)

N3*15 STREET WEST N3 – Address Information (referring to last N1) 15 STREET… - Address line (maybe repeated if multiple lines required)

Page 42: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

2012 GS1 Canada – Technical Standards Work Group - Foodservice EDI Page 42 of 57

Technical Standards Work Group – Foodservice Foodservice Business Process and EDI (GS1C11-513)

EDI TRANSMISSION DATA EXPLANATION

N4*RED DEER*AB*T4N 3X1*CA N4 – Geographic Location (referring to last N1) RED DEER – City AB – Province T4N 3X1 – Postal Code CA - Country Code

N1*SF*PRODS R US *UL*1234567890123

N1 – Name SF - Entity ID Code – Shipped From PRODS R US - Name of the Supplier UL – ID Qualifier - Global Location Number (GLN) 1234567890123 - 13-digit Supplier GLN

N3*15 Sellers Lane N3 – Address Information (referring to last N1) 15 SELLERS… - Address line (maybe repeated if multiple lines required)

N4*Yonkers*SK*S4K 1U2*CAN N4 – Geographic Location (referring to last N1) Yonkers – City SK – Province S4K 1U2 – Postal Code CA - Country Code

HL*2**O HL – Hierarchical Level 2 – Hierarchical ID Number O – Hierarchical Level Code - Order

PRF*549044-57 PRF – Purchase Order Reference 549044-57 – Purchase Order Number

TD1*PLT94*14****G*70*KG TD1 – Carrier Details (Quantity & Weight) PLT94 – Packing Code – Wooden Pallet 14 – Lading Quantity G – Weight Qualifier – Gross Weight 70 – Weight KG – Weight Unit of Measure

HL*3**T HL – Hierarchical Level 3 – Hierarchical ID Number T – Hierarchical Level Code – Shipping Tare

MAN*GM*00100103590000000580 MAN – Marks & Numbers GM – Qualifier – EAN-128 Serial Shipping Container Code (SSCC) 00100103590000000580 – SSCC Number

HL*4**I HL – Hierarchical Level 4 – Hierarchical ID Number I – Hierarchical Level Code - Item

LIN**UK*10066800025510 LIN – Item Identification UK – Following value is a SCC14 (UCC/EAN-14 Shipping Container Code (1-2-5-5-1)) 10066800025510 – 14-digit GTIN

SN1**8*CA SN1 – Item Detail (Shipment) 8 – Number of Units Shipped CA – Unit of Measure - Cases

PO4*12*****40.0*KG PO4 – Item Physical Details 12 – Pack - 12-Pack 40.0 – Gross Weight KG – Weight Qualifier

PID*F*08***NLS 12x500ML ULTIM CHOC MILK

PID – Product/Item Description F – Description Type – Free-Form 08 – Product Characteristic Code - Product

Page 43: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

2012 GS1 Canada – Technical Standards Work Group - Foodservice EDI Page 43 of 57

Technical Standards Work Group – Foodservice Foodservice Business Process and EDI (GS1C11-513)

EDI TRANSMISSION DATA EXPLANATION

NLS 12X500ML… - Product Description HL*5**T HL – Hierarchical Level

5 – Hierarchical ID Number T – Hierarchical Level Code – Shipping Tare

MAN*GM*00100103590000000658 MAN – Marks & Numbers GM – Qualifier – EAN-128 Serial Shipping Container Code (SSCC) 00100103590000000658– SSCC Number

HL*6**I HL – Hierarchical Level 6 – Hierarchical ID Number I – Hierarchical Level Code - Item

LIN**UK*10066800020249 LIN – Item Identification UK – Following value is a SCC14 (UCC/EAN-14 Shipping Container Code (1-2-5-5-1)) 10066800020249– 14-digit GTIN

SN1**6*CA SN1 – Item Detail (Shipment) 6 – Number of Units Shipped CA – Unit of Measure - Cases

PO4*12*****30.0*KG PO4 – Item Physical Details 12 – Pack - 12-Pack 30.0 – Gross Weight KG – Weight Qualifier

PID*F*08***NST 12x473ML COFFEE CRISP MLKS

PID – Product/Item Description F – Description Type – Free-Form 08 – Product Characteristic Code - Product NST 12X473… - Product Description

CTT*2 CTT – Transaction Totals 2 – Two Line Items

SE*34*1004 End of the Transaction Set. 34 - Number of Included Segments in this transaction set, including the ST and SE segments 1004 - Transaction Set Control Number (value must match the ST segment (ST02) of the transaction set)

Page 44: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

2012 GS1 Canada – Technical Standards Work Group - Foodservice EDI Page 44 of 57

Technical Standards Work Group – Foodservice Foodservice Business Process and EDI (GS1C11-513)

Document 810 – Invoice With the product en route to the customer, the invoice is prepared. It details all of the standard financial transaction information surrounding the invoice process and associates to the original Purchase Order. The number of orders addressed in the manifest (above) bears no relevance in this invoice document. The relationship is 1:1 between the Purchase Order and the Invoice (in most circumstances) however multiple invoices may address a specific Purchase Order (incomplete shipments and/or Standing Purchase Orders). These circumstances will not be considered the de facto standard and so must be discussed between the participating entities prior to making use of the practice.

EDI TRANSMISSION DATA EXPLANATION

ST*810*453160027 ST – Start of the Transaction Set (Document) 810 - Transaction Set Identifier Code for the Invoice 453160027 - Transaction Set Control Number

BIG*20111005*4008798063*20110930*549044-57

BIG – Beginning Segment for Invoice 20111005 – Date – Invoice Issue Date 4008798063 – Invoice Number 20110930 – Date – Purchase Order Date 549044-57 – Purchase Order Number

N1*BT*SUPER CAFES*UL*3210123456789

N1 – Name BT - Entity ID Code – Bill-To Information SUPER CAFES - Name of the Bill-To Entity UL – ID Qualifier - Global Location Number (GLN) 3210123456789 - 13-digit Bill-To Entity GLN

N3*1324 GROSVENOR BLVD N3 – Address Information (referring to last N1) 1324… - Address line (maybe repeated if multiple lines required)

N4*GIMLI*MB*R2Y 5S5*CA N4 – Geographic Location (referring to last N1) GIMLI – City MB – Province R2Y 5S5 – Postal Code CA - Country Code

N1*ST*KORNER CAFÉ*UL*6780123456789

N1 – Name ST - Entity ID Code – Ship-To Information KORNER CAFÉ - Name of the Ship-To Entity UL – ID Qualifier - Global Location Number (GLN) 6780123456789- 13-digit Ship-To Entity GLN

N3*UNIT 12 FLOOR 17 N3 – Address Information (referring to last N1) UNIT 12… - Address line (maybe repeated if multiple lines required)

N3*15 STREET WEST N3 – Address Information (referring to last N1) 15 STREET… - Address line (maybe repeated if multiple lines required)

N4*RED DEER*AB*T4N 3X1*CA N4 – Geographic Location (referring to last N1) RED DEER – City AB – Province T4N 3X1 – Postal Code CA - Country Code

N1*VN*PRODS R US *UL*1234567890123

N1 – Name VN - Entity ID Code – Vendor Information PRODS R US - Name of the Vendor UL – ID Qualifier - Global Location Number (GLN) 1234567890123 - 13-digit Supplier GLN

N3*P.O. BOX 367 N3 – Address Information (referring to last N1) P.O. BOX… - Address Information

N4*Herzog*BC*T5J 2J8*CA N4 – Geographic Location (referring to last N1) Herzog – City BC - Province

Page 45: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

2012 GS1 Canada – Technical Standards Work Group - Foodservice EDI Page 45 of 57

Technical Standards Work Group – Foodservice Foodservice Business Process and EDI (GS1C11-513)

EDI TRANSMISSION DATA EXPLANATION

T5J 2J8 – Postal Code CA - Country

ITD*01*3****20111102*28 ITD – Terms of Sale 01 – Terms Type Code – Basic Terms 3 – Terms Basis Date Code – Invoice Date 20111102 – Terms Net Due Date (November 02, 2011) 28 – Terms Net Days

DTM*011*20111005 DTM – Date/Time Reference 011 - Qualifier - Shipped 20111013 - Date (October 05, 2011)

IT1**8*CA*23.1**UK*10066800025510 IT1 – Baseline Item Data (Invoice) 8 – Quantity Invoiced CA – Unit of Measure 23.10 – Unit Price UK - Following value is a SCC14 (UCC/EAN-14 Shipping Container Code (1-2-5-5-1)) 10066800025510- 14-digit GTIN

PID*F****NLS 12x500ML ULTIM CHOC MILK

PID – Product/Item Description F – Description Type – Free-Form NLS 12X500ML… - Product Description

PO4*12*500*GR PO4 – Item Physical Details 12 – Pack - 12-Pack 500 – Size GR – Unit of Measurement (Grams)

IT1**6*CA*23.31**UK*10066800020249

IT1 – Baseline Item Data (Invoice) 6 – Quantity Invoiced CA – Unit of Measure 23.23 – Unit Price UK - Following value is a SCC14 (UCC/EAN-14 Shipping Container Code (1-2-5-5-1)) 10066800020249 - 14-digit GTIN

PID*F****NST 12x473ML COFFEE CRISP MLKS

PID – Product/Item Description F – Description Type – Free-Form NST 12X473… - Product Description

PO4*12*473*GR PO4 – Item Physical Details 12 – Pack - 12-Pack 473 – Size GR – Unit of Measurement (Grams)

TDS*32466 TDS – Total Monetary Value Summary 32466 – Amount - $324.66

ISS*14*CA*70*KG ISS – Invoice Shipment Summary 14 – Number of Units Shipped CA – Unit of Measure 70 – Weight KG – Unit of Measure

CTT*2 CTT – Transaction Totals 2 – Two Line Items

SE*24*453160027 End of the Transaction Set. 24 - Number of Included Segments in this transaction set, including the ST and SE segments 453160027- Transaction Set Control Number (value must match the ST segment (ST02) of the transaction set)

Page 46: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

2012 GS1 Canada – Technical Standards Work Group - Foodservice EDI Page 46 of 57

Technical Standards Work Group – Foodservice Foodservice Business Process and EDI (GS1C11-513)

Document 820 –Remittance Advice Having received the shipping manifest, then the product itself, the invoice for the product and finally internal confirmation of receipt from Korner Kafe, the Accounts Payable department of Super Cafes will authorize a cheque or financial transfer via their banking protocol and provide remittance advice information to Prods R Us so that the money transferred may be applied correctly to the Super Cafes account. This document will be transmitted once per cash movement and may contain many transactions – each detailing the amount of cash to apply and/or credits taken on the specific invoices. The total of the Remittance Advice must match the total of moneys moved in a single transaction (i.e. cheque or fund transfer must reconcile to this figure).

EDI TRANSMISSION DATA EXPLANATION

ST*820*0001 ST – Start of the Transaction Set (Document) 820 - Transaction Set Identifier Code for the Remittance Advice 0001- Transaction Set Control Number

BPR*I*324.66*C*CHK*PBC*****SUPER CAFES******20111025

BPR – Beginning Segment for Remittance Advice I – Transaction Handling Code – Remittance Information Only 324.66 – Monetary Amount – Total Remittance Amount C – Credit/Debit Flag Code - Credit CHK – Payment Method Code - Cheque PBC – Payment Format Code – Commercial/Corporate Cheque SUPER… – Originating Company Identifier 20111025 – Date

REF*CK*3192690 REF – Reference Identification CK – Reference ID Qualifier – Cheque Number 3192690 – Reference Identification

DTM*007*20111025 DTM – Date/Time Reference 007 - Qualifier – Effective Date 20111025 - Date (October 25, 2011)

N1*PR*SUPER CAFES*UL*3210123456789

N1 – Name PR - Entité ID Code – Payer SUPER CAFES - Name of the Bill-To Entity UL – ID Qualifier - Global Location Number (GLN) 3210123456789 - 13-digit Bill-To Entity GLN

ENT*1 ENT – Entity 1 – Assigned Number – Remittance Line Number

RMR*IV*4008798063*PO*324.66 RMR – Remittance Advice A/R Open Item Reference IV – Reference ID Qualifier – Invoice Number 4008798063 – Reference Identification PO – Payment Action Code – Payment on Account 324.66 – Monetary Amount

SE*08*0001 End of the Transaction Set. 08 - Number of Included Segments in this transaction set, including the ST and SE segments 0001 - Transaction Set Control Number (value must match the ST segment (ST02) of the transaction set)

Page 47: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

2012 GS1 Canada – Technical Standards Work Group - Foodservice EDI Page 47 of 57

Technical Standards Work Group – Foodservice Foodservice Business Process and EDI (GS1C11-513)

APPENDIX 4: EDI OVERVIEW

Introduction to Electronic Data Interchange (EDI) INTRODUCTION The intent of this publication is to assist companies in implementing EDI, using the Canadian VICS EDI Foodservice Implementation Guidelines. The different sections of this document have been written for different audiences; ranging from the General Manager who will be faced with the decision to implement the EDI project with all of the attendant business considerations, to the technicians who will perform the data requirements and the programming efforts. Many companies are already using computers to send business documents instead of mailing paper documents. Since computerized transmission of business data will ultimately replace traditional paper based systems, it is important for the Canadian Foodservice industry to establish and maintain guidelines for these activities. This publication has been developed through the cooperative efforts of representatives from involved industry in Canada under the umbrella of GS1 Canada. Any comments or questions concerning this publication may be directed to the Council by telephone at: (416) 510-8039 or by email at [email protected].

EDI: THE CONCEPT In order to evaluate the decision to implement EDI, let’s first review the general concept of electronic data interchange. EDI is simply the means to communicate between companies from one computer to another. In 1979 the American National Standards Institute (ANSI) formed the Accredited Standards Committee (ASC) X12 to eliminate the confusion in electronic communication between trading partners. The ASC X12 standards are recognized by the United Nations as the standard for North America. The VICS (Voluntary Inter-Industry Commerce Solutions) EDI Retail and Foodservice Industry format for EDI follow the ASC X12 standards.

BENEFITS OF EDI Why should foodservice distributors/retailers and suppliers establish EDI links? The reasons for implementing EDI fall increasingly within the tactical rather than the strategic category. Competitive position within the marketplace is driving the decision more than any strategic considerations. Listed below are some of the major benefits identified by many companies using EDI:

• Improved accuracy • Increased customer service • Increased sales • Reduced manual data entry • Reduced postage and handling cost • Reduced printing cost of forms • Reduced mail time • Reduced labour processing cost • Reduced order cycle time • Reduced lead times

Page 48: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

2012 GS1 Canada – Technical Standards Work Group - Foodservice EDI Page 48 of 57

Technical Standards Work Group – Foodservice Foodservice Business Process and EDI (GS1C11-513)

• Reduced filing of paperwork • Reduced inventory carrying cost • Improved warehouse management

What Are The Benefits Of Implementing The Ship Notice/Manifest? (VICS Guidelines): • Eliminates the need for paper based communications, • Ensures accuracy between product shipped and product received, • Reduces off-loading time at receiving dock, • Reduces check-in time from receipt to selling floor, • Facilitates the cross docking process, • Allows for advance order allocation, • Facilitates mechanized receiving, • Allows for integration of data to multiple systems without multiple data entry, • Allows for resource scheduling by the receiver, and • Smooth the payment process by facilitating accurate matching.

Additional ASN advantages: • No more paper packing slips • Advanced warning of gaps in shipped product versus ordered product – gives receiving party the

chance to resolve difference before receiving product • When using GS1-128, there is no need to open shipping units received; scan only • More than just the inventory counts can be included on ASN data – carrier codes, shipping units

measurements • Inventory counts not required (manually written or scanned) as shipping units were scanned • Inventory counts can be loaded to receiver’s system (Financial Stock Ledger) instead of manually

keying • Can further utilize the GS1-128 sent from supplier in your own internal supply chain: shipping dock

at initial point of receipt (warehouse / distribution centre), and at final point of receipt (store/restaurant/etc.)

• Should lead to auditing ASN quality/accuracy at initial point of receipts – can develop supplier classifications based on success/failure rates on previously audited ASN shipments

• ASN quality/accuracy tracking KPIs can lead to vendor/supplier score carding • Facilitates cross-docking at warehouses/DCs • Reduction in employee headcount – less processing time at all points of receipt • Reduction in lead times – ordered product reaches destination quicker • Will ultimately improve shipment, order, and inventory accuracy • Improved inventory accuracy decreases shrink • Could lead to ERS

The most compelling reason to implement EDI is in response to major trading partners requesting the establishment of links in order to realize the benefits listed above. How much is it going to cost? The cost to implement EDI can and will vary widely among companies. The skills of the business and technical personnel, the design and condition of existing computer systems, but most importantly, the ability of the organization to absorb and adapt to change, will determine the cost of this effort. The companies that have implemented EDI have done so because they have realized that the benefits are tangible, that the benefits outweigh the costs, and that EDI has become the accepted practice for conducting business – referred to as “Best Practices”. Following is the EDI Implementation Considerations and Checklist, which provides a guideline for implementing the EDI project, and will provide assistance in identifying the costs and benefits of the project.

Page 49: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

2012 GS1 Canada – Technical Standards Work Group - Foodservice EDI Page 49 of 57

Technical Standards Work Group – Foodservice Foodservice Business Process and EDI (GS1C11-513)

EDI IMPLEMENTATION CONSIDERATIONS Implementation Introduction The purpose of this section is to provide a guideline for the successful implementation of EDI in your organization. EDI impacts many areas of a company’s structure. The management of the company must be involved in the approval phases of the project to ensure the commitment of needed personnel, resources and cross-functional cooperation. While the requirements for implementation vary from one business or organization to another, the following information is intended to present major areas for consideration within your implementation strategy.

Problems to avoid • Deviating from the published standards Without exception AVOID

any deviations from the published Canadian VICS EDI Industry Conventions and Implementation Guidelines. Deviations will cause unnecessary customization to your system, which will complicate adding new trading partners and increase time and costs.

• Too much too soon Do not begin your EDI implementation prematurely. Provide adequate time for education and exposure to the relevant business issues and standards. Talk to potential trading partners and other companies who have already implemented similar EDI functions to learn from their experiences. For additional educational opportunities, contact the GS1 Canada at (416) 510-8039 or by email [email protected] • Be certain that the systems interfacing with EDI are working properly EDI is not a cure for the problems you may have in your existing systems. These problems may be accentuated by the EDI method of transmitting and receiving data for these systems. • Communication Guidelines This publication does not define a single communication standard. Instead, these guidelines describe the most commonly used methods for communicating between trading partners. The communication of the message syntax is accomplished in one of two ways:

The commercial network acts as an intermediary for information passing between trading partners. The network’s data management function can be thought of as a large mailbox, where each user has an assigned slot. The network accepts messages from all participants and stores them in the appropriate slots, where only the assigned users may access them. This simplifies EDI for the trading partners, who only need to interface with their mailbox slot on the network, instead of with each individual trading partner. This service is provided by “solution providers” who may be referred to as “VANs (Value Added Networks)” or a “Service Bureau”.

Commercial network interface (VAN (Value Added Network))

Direct Communication is a trading partner specific electronic communication link. No other organization is involved with the transmission and management of the EDI message. This method of communicating eliminates the ongoing expense of a commercial network (this means no VANS or Service Bureau intervention). However, direct communication with trading partners may require an in-house communication system and resources capable of providing the required business services.

Direct trading partner interface

A direct communication such as AS2 allows for secure, trading partner to trading partner communication over the Internet.

Page 50: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

2012 GS1 Canada – Technical Standards Work Group - Foodservice EDI Page 50 of 57

Technical Standards Work Group – Foodservice Foodservice Business Process and EDI (GS1C11-513)

Implementation Checklist These steps highlight the critical considerations for the successful completion of your EDI Implementation Project. Each of the steps listed is then detailed.

1. Obtain commitment from management 2. Identify business ownership to the project 3. Establish a plan 4. Education 5. Establish project team and define responsibilities 6. Designate EDI business contacts 7. Designate EDI technical contacts 8. Review internal system and business procedures 9. Secure the appropriate reference materials 10. Establish Trading Partner Contact 11. Conduct an EDI survey with trading partners 12. Review data contained in the documents to be exchanged 13. Determine what product information will be provided 14. Determine what partnership identification scheme will be used 15. Develop an overall systems design 16. Decide on translation software strategy 17. Decide on communication solution 18. Code and test the interface to in-house systems 19. Finalize network provider’s optional services 20. Implement the translation software 21. Conduct system test with translation and network 22. Conduct system test with your trading partner 23. Establish production cutover date criteria 24. Implementation 25. Re-Evaluate the checklist for future implementations

Page 51: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

2012 GS1 Canada – Technical Standards Work Group - Foodservice EDI Page 51 of 57

Technical Standards Work Group – Foodservice Foodservice Business Process and EDI (GS1C11-513)

1. Obtain commitment from management

Identify and obtain Key Management commitment and support for this EDI project. Involve all the departments that will be impacted by the implementation (e.g., accounts payable and receivables, merchandising and order processing, information technology, sales and marketing, shipping and receiving etc.). Each department should be included in the analysis, testing, and implementation to insure the accuracy of the test results and promote the support of these groups.

2. Identify business ownership to the project

Although this project is technical in nature, this is a business process re-engineering project and requires owners to be identified and responsible for each component area. It is recommended that you try to avoid this becoming purely an information technology (IT) project.

3. Establish a plan

I. Identify Project – Purpose, Scope (and out of scope) components II. Identify which business documents are be traded III. Develop a work plan IV. Identify as many of the tasks as possible V. Provide cursory estimates to each task VI. Define current document process costs to facilitate cost benefit analysis to be included in the project post

mortem. 4. Education

Take the time to learn what other companies are doing with EDI. This may help you to avoid the pitfalls that other companies have experienced. Education efforts should focus on: software, network/communication topics, and the adjustments to business practices by similar companies. One of the best opportunities to refine a basic understanding of EDI is to participate in the user groups and standards setting bodies for the industry. Contact GS1 Canada at (416) 510-8039 or by email [email protected].

5. Establish project team and define responsibilities

Construct a Project Plan. This will help determine if enough resources have been identified to accomplish the EDI Implementation Project and its on-going maintenance. You should be specific about the deliverables expected from each task. Ensure communication and acceptance of Project and the Defined Responsibilities are signed off.

6. Designate EDI business contacts

The core of the EDI Implementation Project Team should be from within your organization. Additional project personnel may be supplemented by contracting external experts who have previously participated in other successful EDI implementations. Identify and list people who will be primary and secondary contacts for all areas. This list should have complete contact information with major responsibilities clearly defined and signed off.

7. Designate EDI technical contacts

Page 52: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

2012 GS1 Canada – Technical Standards Work Group - Foodservice EDI Page 52 of 57

Technical Standards Work Group – Foodservice Foodservice Business Process and EDI (GS1C11-513)

As with business contacts this group should include representatives from each trading partner, as well as your own internal staff. A contact list should be established with names, contact information and major responsibilities. Industry groups (e.g. GS1 Canada), network providers and other retailers and vendors are a good source to provide direction to your in-house staff.

8. Review internal system and business procedures

A thorough current system analysis should be undertaken. The present process that creates the business documents and the flow of the documents should be recorded. Rules or procedures that affect its life as a document need to be included.

I. Determine how EDI should be integrated into existing systems II. Develop a preliminary scope of the effort to achieve integration

9. Secure the appropriate reference materials

Your list should include: • Canadian VICS EDI Implementation Guidelines • EDI Architecture Guides • Internal systems documentation

For additional information or questions contact the GS1 Canada (416) 510-8039 or send an email to [email protected]

10. Establish Trading Partner Contacts

This will serve to initially establish the contacts within each trading partner organization for both business and communication related requirements. For each contact, the following information should be obtained:

• Name of contact and position (includes email, phone and address) • What their responsibilities are in relation to EDI • How they may be contacted

11. Conduct an EDI survey with trading partners

Survey your trading partners to identify their EDI capabilities including: • EDI Transactions (current and future) • EDI Standards and Versions • Communication methods (e.g. Commercial Network / Direct Connection)

12. Review data contained in the documents to be exchanged

A thorough review of the data mapping requirements for each business document should be performed against the Canadian VICS EDI Implementation Guidelines for Foodservice. Through this process you will be able to determine whether your internal system documents contain all of the required/mandatory data elements. Optional data elements can be identified and discussed with each trading partner to determine applicability. All outstanding issues should be identified and addressed with each trading partner.

Page 53: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

2012 GS1 Canada – Technical Standards Work Group - Foodservice EDI Page 53 of 57

Technical Standards Work Group – Foodservice Foodservice Business Process and EDI (GS1C11-513)

13. Determine what product information will be provided

Product information/identification does vary widely from one distributor/retailer or supplier to another. Whether a unique product code structure or any of the existing options will be used must be identified.

14. Determine what partnership identification scheme will be used

A unique trading partner identifier needs to be established for each trading division of your organization. (Example: GLN or DUNS+4 – see glossary).

15. Develop an overall systems design

Some of the elements likely to be included: • General systems narrative • System data flow diagram • Functional analysis • Inputs/outputs • Processing • Controls/Audits • Backup/restart specifications • Program descriptions • Impact on facilities • Detailed specifications of the computer programs • Specifications of the data formats and data mappings • Specifications of the communications mechanisms • Specifications of billing procedures and any back up statistical reports • Details of security procedures • Operational procedures • Documentation of all processes and programs • Business training materials • Document business process changes as required

16. Decide on translation software strategy

There are two options to handle this. Purchase translation software or outsource the services to a third party solution provider.

Factors for either Purchasing or Outsourcing that should be used considered are:

• Estimated Transaction Volume • Current technology infrastructure • Internal resource availability • Analyze the costs and maintenance for initial and future development • Integration to existing systems

17. Decide on communication solution

The results of your EDI Survey with your trading partners will influence your choice of communication solution. The timing of this decision should be made very early, as it will influence many of the future decisions you will have to make. VAN Solution Providers have standard cost contracts and commercial price lists, all of which should be reviewed before making your decision.

Page 54: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

2012 GS1 Canada – Technical Standards Work Group - Foodservice EDI Page 54 of 57

Technical Standards Work Group – Foodservice Foodservice Business Process and EDI (GS1C11-513)

Direct connection, such as AS2, is an alternative to using commercial networks (VANS). This decision requires the trading partners to accept the burden of maintaining the connection, coordinating the polling schedule (if applicable), providing audit reports, and generating invoices if the costs (if any) are to be shared and related responsibilities.

18. Code and test the interface to in-house systems

It will be necessary to develop programs, which interface between your internal applications and files generated by translation software, in order to process the business information. It is also important to test that these programs are functioning properly.

19. Finalize network provider’s optional services

Compliance checking is one of many types of services that are offered. Various reports that could be useful to determine the status of transmissions can be made available. Be sure to establish the cost of the optional services — they are not always offered for free!

20. Implement the translation software

Whether you purchased your translation software or have outsourced to a third party solution provider you should first use whatever education support is available to prepare your staff to use the software or to understand how to work with the third party provider. If you purchased your software make sure you have determined the amount of time required to implement the software and configured it to be ready for use. With a third party solution, they should provide a timeline to tell you how long it will take for them to prepare their system for you. For both solutions you will need to prepare and implement the network connectivity to allow you to exchange your transactions.

21. Conduct system test with translation and network

The purpose of this will be to verify the following capabilities: Sending Documents

• Generate the data from the internal system • Translate the data into the EDI document format • Send document to the network • If applicable, receive functional acknowledgement

Receiving Documents

• Receive transmission from the network • Translate the document into your data files • Interface data into internal system • If applicable, generate and send a functional acknowledgment

Determine cost associated with testing.

22. Conduct system test with your trading partner

The purpose of this test is to be able to verify the following capabilities:

Page 55: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

2012 GS1 Canada – Technical Standards Work Group - Foodservice EDI Page 55 of 57

Technical Standards Work Group – Foodservice Foodservice Business Process and EDI (GS1C11-513)

• Send and receive transmission to and from your trading partner through your selected communication provider and process functional acknowledgment

• For received documents, translate into internal file and interface with your systems • For sent documents, receive data from the internal systems and translate into required document formats • Validate received or sent documents were successfully transmitted • Validate the content of the documents against the specific business event such as: order, invoice, etc. • Send paper documents in parallel to your trading partner for validation of the documents sent electronically.

You may wish to extend this practice for some pre-determined period following your EDI implementation.

Extensive system testing should be done prior to implementation. 23. Establish production cutover date criteria

Develop a signoff document that includes all the participants (Example: internal departments and all external trading partners) in the EDI Implementation Project. Following the testing and resolution of all outstanding issues, the cutover date can be defined. Cutover consideration needs to be taken into account for business documents communicated before the cutover date. Example Can EDI invoices be processed for orders issued prior to the cutoff date?

24. Implementation

One document transmitted successfully will be more rewarding than hundreds with problems. Selecting your initial trading partner for piloting will be critical to the overall success of the project. It is recommended that you collect data during the first few months for use in a post mortem review of the project. This information will be useful for your management and new or potential trading partners.

25. Re-Evaluate the checklist for future implementations

Eliminate unnecessary tasks and simplify the process of establishing new trading relationships. This is also a good time to review whether assumptions about the benefits have been realized (e.g. reductions in data entry/data validation/data corrections, lower inventory levels etc).

Page 56: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

2012 GS1 Canada – Technical Standards Work Group - Foodservice EDI Page 56 of 57

Technical Standards Work Group – Foodservice Foodservice Business Process and EDI (GS1C11-513)

APPENDIX 5: GLOSSARY Expression

Adjustment Amount

Expression Description

Cash Discount Bill to Purchasing Organization address the invoice should be sent to by the Selling

Organization Billing information Billing information is use to create invoice Delivery/pickup/appointment (date and time)/cancellation date

Delivery date: Date of the shipment should be delivered. Pickup date: Date at which Purchasing Organization is picking up the shipment. Appointment date & time: Selling Organization needs to book an appointment date and time from customer to deliver the shipment to their store or warehouse. Cancellation Date: Customer will not accept shipment after cancellation date.

DUNS+4 DUNS+4- is a 13-digit number to identify allocation. the Duns +4 has two components; a 9-digit number assigned by Dun & Bradstreet to identify a company or a subset of a company (DUNS) and a 4-digit number assigned by the company or subset to uniquely identify a location within their own domain.

Freight on board (FOB) The Selling Organization/Vendor is responsible for all freight expense GLN The GLN is a 13-digit number used to uniquely identify a location. (Any legal,

functional or physical location within a business or organizational entity. The GLN components are An EAN.UCC/ECCC Company Prefix A location reference and A check digit

Gross Amount / 850 List Price Gross paid /820 Amount Paid after discount GTIN Product GTIN The Global Trade Item Number (GTIN) is the new term for the

14-digit data structure to uniquely identify trade items(products and services) within the EAN.UCC system

Marked pricing on product Product marked price is the price marked by the store on the good; the people who come into the store and pay

Net / 850 List Price less any off invoices. Net payment / 820 Net is Invoice Cost Pricing/currency Unit price. Shipping instructions Added information which helps Selling Organization shipper's to transport the

load. Shipping locations Purchasing Organization address from where shipment will ship by the Selling

Organization Sold To Purchasing Organization address the shipment should be sent to by the Selling

Organization Special instructions Special shipment delivery instruction Specific arrival window (time) Range of dates in which shipment needs to arrive

Page 57: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Appendix 6: Industry Implementation Road Map with Timelines

Foodservice EDI Implementation Timeline for Order to Cash - 7 Transaction Sets

Months

Transaction Name (TS)

Year

TS# 1 2 3 4 5 6 7 8 9 10 11 12 12 month span

Purchase Order 850 Internal Preparation Community Implementation

Purchase Order Acknowledgment

855 Internal Preparation Community Implementation

Purchase Order Change 860 Internal Preparation Community Implementation

Advance Ship Notice 856 Internal Preparation Community Implementation

Invoice 810 Internal Preparation Community Implementation

Payment 820 Internal Preparation Community Implementation

Functional Acknowledgment 997 Internal Preparation Community Implementation

Page 58: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Foodservice EDI Change Summary

Version 4010-2012

Table of Contents

Section 1: Change Summary 4010 to 4010-2012 .................................................................................................. 2 Section 2: Data Elements and Position Identification ......................................................................................... 22 Section 2A: Data Element 355 Unit or Basis for Measurement ............................................................................ 54 Section 3: Data Element 1300 Service, Promotion, Allowance or Charge .......................................................... 58

This Foodservice Implementation Guideline for EDI document reflects information for the following Transaction Sets:

• 850 Purchase Order

• 855 Purchase Order Acknowledgment

• 860 Purchase Order Change Request- Buyer Initiated

• 856 Ship Notice / Manifest (ASN Advance Ship Notice)

• 810 Invoice

• 820 Payment Order/Remittance Advice

• 997 Functional Acknowledgment

Page 59: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

GS1 Canada – Industry Relations Standards Page 2 of 81

Foodservice EDI Change Summary Version 4010 to 4010-2012

Section 1: Change Summary 4010 to 4010-2012

810 INV 850 PO 855 POA 856 ASN 997 FA Segment &

Element Position Data Element Code and Expression

Action in Foodservice EDI Version 4010-2012

(All changes below from CR GS1C11-513)

- - - - - - - - - REMOVED TS852 Product Activity Data from Foodservice EDI Transactions Order to Cash

- - - - - - - - -

ADDED TS820 Payment Order/Remittance Advice in Foodservice EDI Transactions Order to Cash

- - - - - - - - -

ADDED TS860 Purchase Order Change Request- Buyer Initiated FS in Foodservice EDI Transactions Order to Cash

BEG02 1/0200 92- Purchase Order Type Code

- BE Blanket Order/Estimated Quantities (Not firm Commitment)

ADDED one code in TS850 BEG02 92- Purchase Order Type Code position 1/0200

BEG04 BEG04 1/0200 328- Release Number OPENED BEG04 DE 328 Release

Number in TS850 position 1/0200

AK101 AK101 1/0200 479- Functional Identifier Code

- IN Invoice Information (810,819) - PC Purchase Order Change Request - Buyer Initiated (860) - PO Purchase Order (850) - PR Purchase Order Acknowledgement (855) - RA Payment Order/Remittance Advice (820) - SH Ship Notice/Manifest (856)

ADDED 6 codes in TS977 AK101 DE 479 position 1/0200

Page 60: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

GS1 Canada – Industry Relations Standards Page 3 of 81

Foodservice EDI Change Summary Version 4010 to 4010-2012

810 INV 850 PO 855 POA 856 ASN 997 FA Segment &

Element Position Data Element Code and Expression

Action in Foodservice EDI Version 4010-2012

(All changes below from CR GS1C11-513)

AK201 AK201 1/0300 143- Transaction Set Identifier Code

- 810 Invoice - 820 Payment Order/Remittance Advice - 850 Purchase Order - 855 Purchase Order Acknowledgment - 856 Ship Notice/Manifest - 860 Purchase Order Change Request - Buyer Initiated

ADDED 6 codes in TS977 AK201 DE 143 position 1/0300

REF REF REF 1/0500 Reference Identification

REMOVED Syntax Notes 2 & 3 from TS850 and TS855: 2 If either C04003 or C04004 is present, then the other is required. 3 If either C04005 or C04006 is present, then the other is required.

REF01 REF01 1/0500 128- Reference

Identification Qualifier -CT Contract Number ADDED one code in TS850 REF01 DE

128 position 1/0500

REF01 REF01 REF01 1/0500 128- Reference Identification Qualifier

- D3 National Association of Boards of Pharmacy Number

REMOVED code D3 National Association of Boards of Pharmacy Number in TS850 and TS855 REF01 DE 128 position 1/0500

REF01 REF01 1/0500 128- Reference Identification Qualifier

- IV Seller's Invoice Number - VN Vendor Order Number

ADDED 2 codes in TS855 REF01 DE 128 position 1/0500

AK503,504,505,506

AK503,504,505,506

1/0600 718 Transaction Set Syntax Error Code

- 1 Transaction Set Not Supported - 2 Transaction Set Trailer Missing - 3 Transaction Set Control Number in Header and Trailer Do Not Match - 4 Number of Included

ADDED 5 codes in TS977 AK503,504,505,506 DE 718 position 1/0600

Page 61: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

GS1 Canada – Industry Relations Standards Page 4 of 81

Foodservice EDI Change Summary Version 4010 to 4010-2012

810 INV 850 PO 855 POA 856 ASN 997 FA Segment &

Element Position Data Element Code and Expression

Action in Foodservice EDI Version 4010-2012

(All changes below from CR GS1C11-513)

Segments Does Not Match Actual Count - 5 One or More Segments in Error

PER03 PER03 PER03 1/0600 365-Communication Number Qualifier

- EM Electronic Mail ADDED one code in TS810 and TS850 PER03 DE 365 Position 1/0600

PER05 PER05 PER05 1/0600 365 Communication Number Qualifier

- EM Electronic Mail -TE Telephone

OPENED PER05 DE 365 Communication Number Qualifier Code including 2 codes in TS810 and TS850 position 1/0600

PER06 PER06 PER06 1/0600 364 Communication Number

OPENED PER06 DE 365 Communication Number Qualifier Code including 2 codes in TS810 and TS850 position 1/0600

AK906,907,908,909

AK906,907,908,909

1/0700 716- Functional Group Syntax Error Code

- 1 Functional Group Not Supported - 2 Functional Group Version Not Supported - 3 Functional Group Trailer Missing - 4 Group Control Number in the Functional Group Header and Trailer Do Not Agree - 5 Number of Included Transaction Sets Does Not Match Actual Count

ADDED 5 codes in TS977 AK906,907,908,909 DE 716 position 1/0700

N101 N101 1/0700 98 Entity Identifier Code

Only codes BO, BS, BT, RI, SF, ST, SU and VN

See Data Element 98 in List

N103 N103 1/0700 66- Identification Code Qualifier

- 1 D-U-N-S Number, Dun & Bradstreet - 91 Assigned by Seller or Seller's Agent - 92 Assigned by Buyer

REMOVED 3 codes from TS810 N103 DE66 position 1/0700

Page 62: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

GS1 Canada – Industry Relations Standards Page 5 of 81

Foodservice EDI Change Summary Version 4010 to 4010-2012

810 INV 850 PO 855 POA 856 ASN 997 FA Segment &

Element Position Data Element Code and Expression

Action in Foodservice EDI Version 4010-2012

(All changes below from CR GS1C11-513)

or Buyer's Agent

SAC02 SAC02 1/1200 1300- Service, Promotion, Allowance, or Charge Code

- D350 Goods and Services Credit Allowance - D360 Goods and Services Tax Charge - H490 Subject To Tax On Resale - H770 Tax - State Tax - H806 Tax Credit

ADDED 5 codes in TS850 SAC02 DE 1300 position 1/1200

SAC09 SAC09 1/1200 355- Unit or Basis for Measurement Code

- BG Bag - BR Barrel - CA Case - DR Drum - EA Each - GA Gallon - KG Kilogram - LB Pound - LT Liter - PA Pail - PL Pallet/Unit Load - TE Tote

ADDED 12 codes in TS850 SAC09 DE 355 position 1/1200

ITD01 ITD01 1/1300 336- Terms Type Code - 01 Basic with note - 04 Deferred or Installment with note

REMOVED 2 codes from TS810 ITD01 366 position 1/1300

ITD01 ITD01 1/1300 336- Terms Type Code - 01 Basic - 02 End of Month (EOM) - 03 Fixed Date - 04 Deferred or Installment - 06 Mixed - 07 Extended - 10 Instant - 11 Elective - 12 10 Days After End

REMOVED 9 codes from TS850 ITD01 366 position 1/1300

Page 63: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

GS1 Canada – Industry Relations Standards Page 6 of 81

Foodservice EDI Change Summary Version 4010 to 4010-2012

810 INV 850 PO 855 POA 856 ASN 997 FA Segment &

Element Position Data Element Code and Expression

Action in Foodservice EDI Version 4010-2012

(All changes below from CR GS1C11-513)

of Month

ITD02 ITD02 1/1300 333- Terms Basis Date Code

- 8 Invoice Transmission Date

REMOVED one code from TS850 DE ITD02 333 position 1/1300

ITD09 ITD09 1/1300 388- Terms Deferred Due Date

REMOVED ITD09 DE 388 from TS810 position 1/1300

ITD10 ITD10 1/1300 389- Deferred Amount Due

REMOVED ITD10 DE 389 from TS810 position 1/1300

ITD11 ITD11 1/1300 342- Percent of Invoice Payable

REMOVED ITD11 DE 342 from TS810 position 1/1300

ITD12 ITD12 1/1300 352 Description REMOVED ITD12 DE 352 from TS810 position 1/1300

DTM01 DTM01 1/1500 374- Date/Time Qualifier

-118 Requested Pickup REMOVED one code from TS855 DTM01 DE 374 position 1/1500

N101 N101 1/3000 98- Entity Identifier Code

- FR Message From - MA Party for whom Item is Ultimately Intended Ultimate receiver - OB Ordered By Customer of retailer - TO Message To

REMOVED 4 codes from TS855 N101 DE 98 position 1/3000

N101 N101 1/3000 98- Entity Identifier Code

- BO Broker or Sales Office - SU Supplier/Manufacturer - VN Vendor

ADDED 3 codes in TS855 N101 DE 98 position 1/3000

N103 N103 1/3000 66- Identification Code Qualifier

- 1 D-U-N-S Number, Dun & Bradstreet - 91 Assigned by Seller or Seller's Agent - 92 Assigned by Buyer or Buyer's Agent

REMOVED 3 codes fromTS855 N103 DE 66 position 1/3000

Page 64: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

GS1 Canada – Industry Relations Standards Page 7 of 81

Foodservice EDI Change Summary Version 4010 to 4010-2012

810 INV 850 PO 855 POA 856 ASN 997 FA Segment &

Element Position Data Element Code and Expression

Action in Foodservice EDI Version 4010-2012

(All changes below from CR GS1C11-513)

N101 N101 1/3100 98- Entity Identifier Code

- AG Agent/Agency - BL Party to Receive Bill of Lading - CB Customs Broker - CN Consignee - CS Consolidator - CT Country of Origin - EX Exporter - FR Message From - FW Forwarder - H9 Designer - MA Party for whom Item is Ultimately Intended Ultimate receiver - MF Manufacturer of Goods - NP Notify Party for Shipper's Order - OB Ordered By - TO Message To - Z7 Mark-for Party

REMOVED 16 codes from TS850 N101 DE 98 position 1/3100

N101 N101 1/3100 98- Entity Identifier Code

-VN Vendor ADDED one code in TS850 N101 DE 98 position 1/3000

N103 N103 1/3100 66- Identification Code Qualifier

- 1 D-U-N-S Number, Dun & Bradstreet - 91 Assigned by Seller or Seller's Agent - 92 Assigned by Buyer or Buyer's Agent

REMOVED 3 codes fromTS850 N103 DE 66 position 1/3100

Page 65: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

GS1 Canada – Industry Relations Standards Page 8 of 81

Foodservice EDI Change Summary Version 4010 to 4010-2012

810 INV 850 PO 855 POA 856 ASN 997 FA Segment &

Element Position Data Element Code and Expression

Action in Foodservice EDI Version 4010-2012

(All changes below from CR GS1C11-513)

IT103 IT103 2/0100 355 Unit or Basis for Measurement Code

- BG Bag - BR Barrel - DR Drum - GA Gallon - KG Kilogram - LB Pound - LT Liter - PA Pail - TE Tote

ADDED 9 codes in TS810 IT103 355 position 2/0100

IT106 IT106 2/0100 235- Product/Service ID Qualifier

- EN European Article Number (EAN) (2-5- 5-1) - IN Buyer's Item Number - UA U.P.C./EAN Case Code (2-5-5) - UN U.P.C. Case Code Number (1- 1-5-5) - UP U.P.C. Consumer Package Code (1-5-5-1) - VN Vendor's (Seller's) Item Number

REMOVED 6 codes from TS810 IT106 235 position 2/0100

IT108,110, 112,114,

116

IT108,110,112,114,11

6

2/0100 235- Product/Service ID Qualifier

Closed IT108,110,112,114,116 DE 235 from TS810 position 2/0100

IT109,111, 113,115

IT107, 09,111,113

,115

2/0100 234- Product/Service ID

Closed IT109,111,113,115 DE 234 from TS810 position 2/0100

PO103 PO103 2/0100 355-Unit or Basis for Measurement Code

- BA Bale - BO Bottle - BX Box - CN Can - CT Carton - DS Display - DZ Dozen - PK Package - RL Roll

REMOVED 9 codes in TS850 PO103 DE 355 position 2/0100

Page 66: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

GS1 Canada – Industry Relations Standards Page 9 of 81

Foodservice EDI Change Summary Version 4010 to 4010-2012

810 INV 850 PO 855 POA 856 ASN 997 FA Segment &

Element Position Data Element Code and Expression

Action in Foodservice EDI Version 4010-2012

(All changes below from CR GS1C11-513)

PO103 PO103 2/0100 355-Unit or Basis for Measurement Code

- DR Drum - GA Gallon - KG Kilogram - LB Pound - LT Liter - PA Pail - TE Tote

ADDED 7 codes in TS850 PO103 DE 355 position 2/0100

PO103 PO103 2/0100 355-Unit or Basis for Measurement Code

- BG Bag - BR Barrel - DR Drum - GA Gallon - KG Kilogram - LB Pound - LT Liter - PA Pail - TE Tote

ADDED 9 codes in TS855 PO103 DE 355 position 2/0100

PO104 PO104 2/0100 212- Unit Price CLOSED PO104 DE 212 from TS850 position 2/0100

PO106 PO106 2/0100 235- Product/Service ID Qualifier

- EN European Article Number (EAN) (2-5- 5-1) - IN Buyer's Item Number - UA U.P.C./EAN Case Code (2-5-5) - UN U.P.C. Case Code Number (1-1-5-5) - UP U.P.C. Consumer Package Code (1-5-5-1) - VN Vendor's (Seller's)Item Number

REMOVED 6 codes in TS850 PO106 DE 235 position 2/0100

PO106 PO106 2/0100 235- Product/Service ID Qualifier

- EN European Article Number (EAN) (2-5- 5-1) - UA U.P.C./EAN Case Code (2-5-5)

REMOVED 4 codes from TS855 PO106 DE 235 position 2/0100

Page 67: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

GS1 Canada – Industry Relations Standards Page 10 of 81

Foodservice EDI Change Summary Version 4010 to 4010-2012

810 INV 850 PO 855 POA 856 ASN 997 FA Segment &

Element Position Data Element Code and Expression

Action in Foodservice EDI Version 4010-2012

(All changes below from CR GS1C11-513)

- UN U.P.C. Case Code Number (1-1-5-5) - UP U.P.C. Consumer Package Code (1-5-5-1)

PO108, 110,112,11

4,116

PO108, 110,112,11

4,116

PO108, 110,112,11

4,116

2/0100 235- Product/Service ID Qualifier

CLOSED PO108, 110,112,114,116 DE 235 from TS850 and TS 855 position 2/0100

PO109,111,113,115,

117

PO109,111,113,115,

117

PO109,111,113,115,1

17

2/0100 234- Product/Service ID

CLOSED PO109,111,113,115,117 DE 234 from TS850 and TS 855 position 2/0100

CTP01 CTP01 2/0400 687- Class of Trade Code

- AG Agent - BG Buying Group - DE Dealer - DI Distributor - RS Resale

OPENED in TS855 CTP01 DE 687 position 2/0400 including 5 codes

CTP02 CTP02 2/0400 236- Price Identifier Code

- ALT Alternate Price - CAT Catalog Price - MSR Manufacturer's Suggested Retail - PRP Promotional price - RES Resale

ADDED 5 codes in TS855 CTP02 DE 236 position 2/0400

CTP02 CTP02 2/0400 236- Price Identifier Code

- OPP Original Purchase Order Price

REMOVED one code from TS855 CTP02 DE 236 position 2/0400

Page 68: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

GS1 Canada – Industry Relations Standards Page 11 of 81

Foodservice EDI Change Summary Version 4010 to 4010-2012

810 INV 850 PO 855 POA 856 ASN 997 FA Segment &

Element Position Data Element Code and Expression

Action in Foodservice EDI Version 4010-2012

(All changes below from CR GS1C11-513)

CTP05- 01 CTP05 2/0400 355- Unit or Basis for Measurement Code

- BG Bag - BR Barrel - CA Case - CC Cubic Centimeter - CF Cubic Feet - CI Cubic Inches - CR Cubic Meter - DB Dry Pounds - DR Drum - EA Each - FT Foot - FZ Fluid Ounce (Imperial) - GA Gallon - GI Imperial Gallons - GR Gram - IN Inch - KG Kilogram - LB Pound - LT Liter - ML Milliliter - PA Pail - PL Pallet/Unit Load - PT Pint - PX Pint, Imperial - TE Tote - YD Yard

ADDED 26 codes in TS855 position 2/0400

CTP11 CTP11 2/0400 289- Multiple Price Quantity

OPENED CTP11 DE 289 inTS855 position 2/0400

CTP04 CTP04 2/0400 380- Quantity CLOSED CTP04 DE 380 from TS850 position 2/0400

CTP05 CTP05 2/0400 C001- Composite Unit of Measure

CLOSED CTP05 DE C001 from TS850 position 2/0400

CTP05 C00101

CTP05 C00101

2/0400 355- Unit or Basis for Measurement Code

CLOSED CTP05 C00101 DE 355 from TS850 position 2/0400

Page 69: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

GS1 Canada – Industry Relations Standards Page 12 of 81

Foodservice EDI Change Summary Version 4010 to 4010-2012

810 INV 850 PO 855 POA 856 ASN 997 FA Segment &

Element Position Data Element Code and Expression

Action in Foodservice EDI Version 4010-2012

(All changes below from CR GS1C11-513)

CTP09 CTP09 2/0400 639 Basis of Unit Price Code

CLOSED CTP09 DE 639 (NT Net, and PE Price per Each) from TS850 position 2/0400

CTP04 CTP04 2/0500 380- Quantity CLOSED CTP04 DE 380 from TS810 position 2/0500

CTP05 CTP05 2/0500 C001- Composite Unit of Measure

CLOSED CTP05 DE C001 from TS810 position 2/0500

CTP05 C00101

CTP05 C00101

2/0500 355- Unit or Basis for Measurement Code

CLOSED CTP05 C00101 DE 355 from TS810 position 2/0500

CTP09 CTP09 2/0500 639 Basis of Unit Price Code

CLOSED CTP09 DE 639 (NT Net, and PE Price per Each) from TS810 position 2/0500

PID PID 2/0500 Product/Item Description

ADDED PID Product /Item Description segment in TS855 position 2/0500

PO402 PO402 2/0900 357- Size CLOSED PO402 DE 357 from TS855 position 2/0900

PO403 PO403 2/0900 355- Unit or Basis for Measurement Code

CLOSED PO403 DE 355 from TS855 position 2/0900

PO403 PO403 2/0900 355- Unit or Basis for Measurement Code

- BG Bag - BR Barrel - CA Case - DR Drum - EA Each - GA Gallon - KG Kilogram - LB Pound - LT Liter - PA Pail - PL Pallet/Unit Load - TE Tote

ADDED 12 codes in TS850 PO403 355 position 2/0900

PO406 PO406 2/0900 384 Gross Weight per Pack

OPENED PO406 DE 384 in TS855 position 2/0900

Page 70: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

GS1 Canada – Industry Relations Standards Page 13 of 81

Foodservice EDI Change Summary Version 4010 to 4010-2012

810 INV 850 PO 855 POA 856 ASN 997 FA Segment &

Element Position Data Element Code and Expression

Action in Foodservice EDI Version 4010-2012

(All changes below from CR GS1C11-513)

PO407 PO407 2/0900 355- Unit or Basis for Measurement Code

-KG Kilogram - LB Pound

OPENED PO407 DE 355 including 2 codes inTS855 position 2/0900

PO408 PO408 2/0900 385- Gross Volume per Pack

OPENED PO408 DE 385 in TS855 position 2/0900

PO409 PO409 2/0900 355- Unit or Basis for Measurement Code

- CC Cubic Centimeter - CF Cubic Feet - CI Cubic Inches - CR Cubic Meter - GA Gallon - GI Imperial Gallons - LT Liter - ML Milliliter - PT Pint - PX Pint, Imperial

OPENED PO409 DE 355 including 10 codes inTS855 position 2/0900

PO403 PO403 2/1000 355- Unit or Basis for Measurement Code

- BG Bag - BR Barrel - CA Case - DR Drum - EA Each - GA Gallon - KG Kilogram - LB Pound - LT Liter - PA Pail - PL Pallet/Unit Load - TE Tote

ADDED 12 codes in TS810 PO403 355 position 2/1000

TD103 Shipment

TD1103 Shipment

2/1100 23- Commodity Code Qualifier

CLOSED TD103 DE 23 from TS856 segment TD1 -Shipment, position 2/1100

TD104 Shipment

TD1 04 Shipment

2/1100 22- Commodity Code CLOSED TD104 DE 22 from TS856 segment TD1 -Shipment, position 2/1100

TD105 Shipment

TD1 05 Shipment

2/1100 79- Lading Description CLOSED TD104 DE 79 from TS856 segment TD1 -Shipment, position 2/1100

Page 71: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

GS1 Canada – Industry Relations Standards Page 14 of 81

Foodservice EDI Change Summary Version 4010 to 4010-2012

810 INV 850 PO 855 POA 856 ASN 997 FA Segment &

Element Position Data Element Code and Expression

Action in Foodservice EDI Version 4010-2012

(All changes below from CR GS1C11-513)

TD110 Shipment

TD110 Shipment

2/1100 355- Unit or Basis for Measurement Code

- CC Cubic Centimeter - CF Cubic Feet - CI Cubic Inches - CR Cubic Meter - GA Gallon - GI Imperial Gallons - LT Liter - ML Milliliter - PT Pint - PX Pint, Imperial

ADDED TD110 HL SHIPMENT DE 355 including 10 codes inTS856 position 2/1100

TD502 Shipment

TD502 Shipment

2/1200 66- Identification Code Qualifier

- 91 Assigned by Seller or Seller's Agent - 92 Assigned by Buyer or Buyer's Agent

REMOVED 2 codes from TS856 segment TD5 - Shipment, TD502 DE 66 position 2/1200

SAC SAC 2/1300 Service, Promotion, Allowance, or Charge

Information

ADDED to Semantics in TS855 position 2/1300: 8. SAC14 is used in conjunction with SAC13 to identify an option when there is more than one option of the promotion. 9. SAC16 is used to identify the language being used in SAC15.

SAC02 SAC02 2/1300 1300- Service, Promotion, Allowance, or Charge Code

- D350 Goods and Services Credit Allowance - D360 Goods and Services Tax Charge - H490 Subject To Tax On Resale - H770 Tax - State Tax - H806 Tax Credit

ADDED 5 codes in TS855 SAC02 DE 1300 position 2/1300

Page 72: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

GS1 Canada – Industry Relations Standards Page 15 of 81

Foodservice EDI Change Summary Version 4010 to 4010-2012

810 INV 850 PO 855 POA 856 ASN 997 FA Segment &

Element Position Data Element Code and Expression

Action in Foodservice EDI Version 4010-2012

(All changes below from CR GS1C11-513)

SAC09 SAC09 SAC09 2/1300 355- Unit or Basis for Measurement Code

- BG Bag - BR Barrel - DR Drum - GA Gallon - KG Kilogram - LB Pound - LT Liter - PA Pail - TE Tote

ADDED 9 codes in TS850 and TS 855 SAC09 355 position 2/1300

SAC11 SAC11 2/1300 380- Quantity OPENED SAC11 DE 380 in TS855 position 2/1300

SAC14 SAC14 2/1300 770- Option Number OPENED SAC14 DE 770 in TS855 position 2/1300

SDQ SDQ 2/1400 Destination Quantity Closed SDQ Segment from TS810 position 2/1400

REF Shipment

REF Shipment

2/1500 Reference Identification

REMOVED Syntax in TS856 segment REF- Shipment, position 2/1500: 2 If either C04003 or C04004 is present, then the other is required. 3 If either C04005 or C04006 is present, then the other is required.

PER03 Shipment

PER03 Shipment

2/1510 365-Communication Number Qualifier

- EM Electronic Mail ADDED one code in TS856 PER03 DE 365 Position 2/1510

PER05 Shipment

PER05 Shipment

2/1510 365 Communication Number Qualifier

- EM Electronic Mail -TE Telephone

OPENED PER05 and ADDED the 2 codes in TS856 segment PER - Shipment, position 2/1510

PER06 Shipment

PER06 Shipment

2/1510 364- Communication Number

OPENED PER06 in TS856 segment PER - Shipment, position 12/1510

SAC SAC 2/1800 Service, Promotion, Allowance, or Charge

Information

ADDED to Semantics in TS810 position 2/1800: 8. SAC14 is used in conjunction with SAC13 to identify an option when there is more than one option of the promotion. 9. SAC16 is used to identify the

Page 73: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

GS1 Canada – Industry Relations Standards Page 16 of 81

Foodservice EDI Change Summary Version 4010 to 4010-2012

810 INV 850 PO 855 POA 856 ASN 997 FA Segment &

Element Position Data Element Code and Expression

Action in Foodservice EDI Version 4010-2012

(All changes below from CR GS1C11-513)

language being used in SAC15.

SAC09 SAC09 2/1800 355- Unit or Basis for Measurement Code

- BG Bag - BR Barrel - CA Case - DR Drum - EA Each - GA Gallon - KG Kilogram - LB Pound - LT Liter - PA Pail - PL Pallet/Unit Load - TE Tote

ADDED 12 codes in TS810 SAC09 355 position 2/1800

SAC14 SAC014 2/1800 770- Option Number OPENED 770 Option Number in TS810 position2/1800

SDQ SDQ SDQ 2/1900 Destination Quantity REMOVED Segment SDQ from TS850 and TS855 position 2/1900

N101 Shipment

N101 Shipment

2/2200 98- Entity Identifier Code

- BS Bill and Ship To - CS Consolidator - FR Message From - LP Loading Party - MA Party for whom Item is Ultimately Intended - OB Order By Customer of Retailer - TO Message To - UP Unloading Party - YW Discharge Point

REMOVED 9 codes from TS856 segment N1 - Shipment, N101 DE 98 position 2/2200

N103 Shipment

N103 Shipment

2/2200 66- Identification Code Qualifier

- 1 D-U-N-S Number, Dun & Bradstreet - 91 Assigned by Seller or Seller's Agent

REMOVED 3 codes from TS856 segment N1 -Shipment, N103 DE 66 position 2/2200

Page 74: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

GS1 Canada – Industry Relations Standards Page 17 of 81

Foodservice EDI Change Summary Version 4010 to 4010-2012

810 INV 850 PO 855 POA 856 ASN 997 FA Segment &

Element Position Data Element Code and Expression

Action in Foodservice EDI Version 4010-2012

(All changes below from CR GS1C11-513)

- 92 Assigned by Buyer or Buyer's Agent

N103 Shipment

N103 Shipment

2/2200 66- Identification Code Qualifier

- UL UCC/EAN Location Code

ADDED one code to TS856 segment N1 -Shipment, N103 DE 66 position 2/2200

TD108 Order

TD108 Order

2/1100 355- Unit or Basis for Measurement Code

- GR Gram - KG Kilogram

ADDED 2 codes in TS856 segment TD1 - Order, TD108 DE 355 position 2/1100

REF01 Order

REF01 Order

2/1500 128- Reference Identification Qualifier

- UCB UCC Bill of Lading Number (17 Digits) - UCM UCC Master Bill of Lading Number (17 Digits)

REMOVED 2 codes in TS856 segment REF- Order, REF01 DE 128 position 2/1500

N101 Order

N101 Order

2/2200 98- Entity Identifier Code

- MA Party for whom Item is Ultimately Intended

REMOVED one code from TS856 segment N1 - Order, N101 DE 98 position 2/2200

N103 (Order

N103 Order

2/2200 66- Identification Code Qualifier

- 1 D-U-N-S Number, Dun & Bradstreet - 91 Assigned by Seller or Seller's Agent - 92 Assigned by Buyer or Buyer's Agent

REMOVED 3 codes from TS856 segment N1 -Order, N103 DE 66 position 2/2200

LIN02 Pack

LIN02 Pack 2/0200 235- Product/Service ID Qualifier

- UA U.P.C./EAN Case Code (2-5-5)

REMOVED one code from TS856 segment LIN - Pack, LIN02 DE 235 position 2/0200

LIN04 Pack

LIN04 Pack 2/0200 235- Product/Service ID Qualifier

- LT Lot Number - UK U.P.C./EAN Shipping Container Code (1-2-5-5-1)

ADDED 2 codes in TS856 Segment LIN - Pack, LIN04 DE 235 position 2/0200

LIN06 Pack

LIN06 Pack 2/0200 235- Product/Service ID Qualifier

CLOSED LIN06 DE 235 from TS856 segment - Pack, position 2/0200

LIN07 Pack

LIN07 Pack 2/0200 234- Product/Service ID

CLOSED LIN07 DE 234 from TS856 segment - Pack, position 2/0200

Page 75: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

GS1 Canada – Industry Relations Standards Page 18 of 81

Foodservice EDI Change Summary Version 4010 to 4010-2012

810 INV 850 PO 855 POA 856 ASN 997 FA Segment &

Element Position Data Element Code and Expression

Action in Foodservice EDI Version 4010-2012

(All changes below from CR GS1C11-513)

SN103 Pack

SN103 Pack

2/0300 355-Unit or Basis for Measurement Code

- BG Bag - BR Barrel - DR Drum - EA Each - GA Gallon - KG Kilogram - LB Pound - LT Liter - PA Pail - PL Pallet/Unit Load - TE Tote

ADDED 11 codes in TS856 segment SN- Pack, SN103 DE 355 position 2/0300

MAN01 Pack

MAN01 Pack

2/1900 88- Marks and Numbers Qualifier

- UC U.P.C. Shipping Container Code

REMOVED one Code from TS856 segment MAN- Pack, MAN01 DE 88 position 2/1900

MAN04 Pack

MAN04 Pack

2/1900 88- Marks and Numbers Qualifier

- GM SSCC-18 and Application Identifier - UP U.P.C. Consumer Package Code (1-5-5-1)

OPENED MAN04 DE 88 including 2 codes in TS856 Segment - MAN- Pack, position 2/1900

MAN05 Pack

MAN05 Pack

2/1900 87- Marks and Numbers

OPENED MAN05 DE 87 for use with MAN04 in TS856 Segment - MAN- Pack, position 2/1900

LIN02 Item

LIN02 Item 2/0200 235- Product/Service ID Qualifier

- EN European Article Number (EAN) (2-5-5-1) - IT Buyer's Style Number - LT Lot Number - UA U.P.C./EAN Case Code (2-5-5) - UN U.P.C. Case Code Number (1-2-5-5) - UP U.P.C. Consumer Package Code (1-5-5-1)

REMOVED 6 codes from TS856 segment LIN - Item, LIN02 DE 235 position 2/0200

LIN04,06,08,10,12,14,16

Item

LIN04,06,08,10,12,14,

16 Item

2/0200 235- Product/Service ID Qualifier

CLOSED LIN04,6,08,10,12,14,16 DE 235 from TS856 segment LIN - Item, position 2/0200

Page 76: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

GS1 Canada – Industry Relations Standards Page 19 of 81

Foodservice EDI Change Summary Version 4010 to 4010-2012

810 INV 850 PO 855 POA 856 ASN 997 FA Segment &

Element Position Data Element Code and Expression

Action in Foodservice EDI Version 4010-2012

(All changes below from CR GS1C11-513)

LIN05,07,09,11,13,15,17

Item

LIN05,07,09,11,13,15,

17 Item

2/0200 234- Product/Service ID

CLOSED LIN05,07,09,11,13,15,17 DE 234 from TS856 segment LIN - Item, position 2/0200

SN103 Item

SN103 Item

2/0300 355-Unit or Basis for Measurement Code

- BG Bag - BR Barrel - CA Case - DR Drum - EA Each - GA Gallon - KG Kilogram - LB Pound - LT Liter - PA Pail - PL Pallet/Unit Load - TE Tote

ADDED 12 codes in TS856 segment SN- Item, SN103 DE 355 position 2/0300

PO406 Item

PO406 Item

2/0600 384- Gross Weight per Pack

CLOSED PO406 DE 384 from TS856 segment PO4-Item, position 2/0600

PO407,09 Item

PO407,09 Item

2/0600 355- Unit or Basis for Measurement Code

CLOSED PO407,09 DE 2/0600 from TS856 segment PO4-Item, position 2/0600 (

PO408 Item

PO408 Item

2/0600 385- Gross Volume per Pack

CLOSED PO408 DE 385 from TS856 segment PO4-Item, position 2/0600

PID03 Item

PID03 Item

2/0700 559- Agency Qualifier Code

CLOSED PID03 DE 559 from TS856 segment PID -Item, position 2/0700

PID04 Item

PID04 Item

2/0700 751- Product Description Code

CLOSED PID04 DE 751 from TS856 segment PID -Item, position 2/0700

TD4 Item

TD4 Item 2/1400 Carrier Details (Special Handling, or

Hazardous Materials, or Both)

REMOVED TD4 HL-ITEM Segment from TS856 position 2/1400

Page 77: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

GS1 Canada – Industry Relations Standards Page 20 of 81

Foodservice EDI Change Summary Version 4010 to 4010-2012

810 INV 850 PO 855 POA 856 ASN 997 FA Segment &

Element Position Data Element Code and Expression

Action in Foodservice EDI Version 4010-2012

(All changes below from CR GS1C11-513)

ACK03 ACK03 2/2700 355- Unit or Basis for Measurement Code

- BG Bag - BR Barrel - DR Drum - GA Gallon - KG Kilogram - LB Pound - LT Liter - PA Pail - TE Tote

ADDED 9 codes in TS855 ACK03355 position 2/2700

CTT02 CTT02 3/0100 347- Hash Total CLOSED CTT02 DE 347 from TS850 position 3/0100

CTT03 CTT03 3/0100 81- Weight CLOSED CTT03 DE 81 from TS850 position 3/0100

CTT04,06 CTT04,06 3/0100 355- Unit or Basis for Measurement Code

CLOSED CTT06 DE 355 from TS850 position 3/0100

CTT05 CTT05 3/0100 183- Volume CLOSED from TS850 position 3/0100

CTT07 CTT07 3/0100 352- Description CLOSED CTT07 DE 3/0100 from TS850 position 3/0100

SAC SAC 3/0400 Service, Promotion, Allowance, or Charge

Information

ADDED to Semantics in TS810 position 3/0400: 8. SAC14 is used in conjunction with SAC13 to identify an option when there is more than one option of the promotion. 9. SAC16 is used to identify the language being used in SAC15.

Page 78: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

GS1 Canada – Industry Relations Standards Page 21 of 81

Foodservice EDI Change Summary Version 4010 to 4010-2012

810 INV 850 PO 855 POA 856 ASN 997 FA Segment &

Element Position Data Element Code and Expression

Action in Foodservice EDI Version 4010-2012

(All changes below from CR GS1C11-513)

SAC09 SAC009 3/0400 355- Unit or Basis for Measurement Code

- BG Bag - BR Barrel - CA Case - DR Drum - EA Each - GA Gallon - KG Kilogram - LB Pound - LT Liter - PA Pail - PL Pallet/Unit Load - TE Tote

ADDED 12 codes in n TS810 SAC09 355 position 3/0400

ISS02 ISS02 3/0600 355- Unit or Basis for Measurement Code

- BG Bag - BR Barrel - CA Case - DR Drum - EA Each - GA Gallon - KG Kilogram - LB Pound - LT Liter - PA Pail - PL Pallet/Unit Load - TE Tote

ADDED 12 codes in TS810 ISS02 355 position 3/0600

ISS04 ISS04 3/0600 355- Unit or Basis for Measurement Code

- KG Kilogram - LB Pound

ADDED 2 codes in TS810 SAC09 355 position 3/0600

SLN SLN Subline Item Detail CLOSED SLN segment from TS855

Page 79: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

GS1 Canada – Industry Relations Standards Page 22 of 81

Foodservice EDI Change Summary Version 4010 to 4010-2012

Section 2: Data Elements and Position Identification

Data Element # and Name Codes 810 820 850 855 856 860 997

100 Currency Code 1/0400 CUR02 Yes 1/0400 CUR02, 05

1005 Hierarchical Structure Code

Yes

1005 Hierarchical Structure Code

0001 Shipment, Order, Packaging, Item

1/0200 BSN05

100 Currency Code Yes Yes

100 Currency Code CAD - Canadian 1/0400 CUR02 1/0400 CUR02

100 Currency Code USD - United States 1/0400 CUR02 1/0400 CUR02

103 Packaging Code Yes

103 - Packaging Code BAG - Bag 2/1100 TD101 Shipment

2/1100 TD101 Order

103 - Packaging Code CTN - Carton 2/1100 TD101 Shipment

2/1100 TD101 Order

103 - Packaging Code MIX Mixed Container Types

2/1100 TD101 Shipment

103 - Packaging Code PLT - Pallet 2/1100 TD101 Shipment

2/1100 TD101 Order

103 - Packaging Code SLP- Slip Sheet 2/1100 TD101 Shipment

103 - Packaging Code SRW - Shrink Wrap 2/1100 TD101 Shipment

103 - Packaging Code 01 - Aluminum 2/1100 TD101 Shipment

2/1100 TD101 Order

Page 80: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

GS1 Canada – Industry Relations Standards Page 23 of 81

Foodservice EDI Change Summary Version 4010 to 4010-2012

Data Element # and Name Codes 810 820 850 855 856 860 997

103 - Packaging Code 25 - Corrugated or Solid 2/1100 TD101 Shipment

2/1100 TD101 Order

103 - Packaging Code 31- Fibre 2/1100 TD101 Shipment

2/1100 TD101 Order

103 - Packaging Code 58 - Metal 2/1100 TD101 Shipment

103 - Packaging Code 71 Not Otherwise Specified

2/1100 TD101 Shipment

103 - Packaging Code 76 - Paper 2/1100 TD101 Shipment

2/1100 TD101 Order

103 - Packaging Code 79 - Plastic 2/1100 TD101 Shipment

2/1100 TD101 Order

103 - Packaging Code 91 - Stainless Steel 2/1100 TD101 Shipment

103 - Packaging Code 94 - Wood 2/1100 TD101 Shipment

2/1100 TD101 Order

116 Postal Code 1/100 N403 1/1000 N403 1/3400 N403 1/3300 N403 2/2500 N403 Shipment

2/2500 N403 Order

1/3300 N403

118 Rate 2/1800 SAC08 1/1200 SAC08 2/1300 SAC08

2/1300 SAC08 1/1200 SAC08 2/1300 SAC08

123 Number of Received Transaction Sets

1/0700 AK903

Page 81: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

GS1 Canada – Industry Relations Standards Page 24 of 81

Foodservice EDI Change Summary Version 4010 to 4010-2012

Data Element # and Name Codes 810 820 850 855 856 860 997

127 Reference Identification 1/0500 REF02 2/1800 SAC13

1/0350 TRN02 1/0500 REF02 2/0800 ADX04 2/1100 REF02

2/1500 RMR02 2/2100 ADX04

1/0500 REF02 1/1200 SAC13 1/2950 N902 1/3500 REF02 2/1300 SAC13

1/0500 REF02 '2/1300 SAC13

2/1500 REF02 Shipment

2/1500 REF02 Order

2/1500 REF02 Item

1/0500 REF02 1/1200 SAC13 1/2850 N902 1/3400 REF02 2/1300 SAC13

128 Reference Identification Qualifier

Yes Yes Yes Yes Yes Yes

128 - Reference Identification Qualifier

6B- U.S. Customs Service (USCS) Entry Number

2/1500 REF01 Order

128 - Reference Identification Qualifier

AH- Agreement Number

1/2950 N901 1/2850 N901

128 - Reference Identification Qualifier

BM - Bill of Lading Number

2/1500 REF01 Shipment

2/1500 REF01 Order

128 - Reference Identification Qualifier

BT- Batch Number 2/1500 REF01 Order

128 - Reference Identification Qualifier

CH- Customer catalog number

2/1500 REF01 Order

128 - Reference Identification Qualifier

CK- Check Number 1/0500 REF01

128 - Reference Identification Qualifier

CL- Seller's Credit Memo

2/1100 REF01

128 - Reference Identification Qualifier

CM- Buyer's Credit Memo

2/0800 ADX03 2/2100 ADX03

128 - Reference Identification Qualifier

CN - Carrier's Reference Number (PRO/Invoice)

2/1500 REF01 Shipment

128 - Reference Identification Qualifier

CO- Customer Order Number

2/1500 REF01 Order

2/1500 REF01 Item

128 - Reference Identification Qualifier

CT - Contract Number 1/0500 REF01

Page 82: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

GS1 Canada – Industry Relations Standards Page 25 of 81

Foodservice EDI Change Summary Version 4010 to 4010-2012

Data Element # and Name Codes 810 820 850 855 856 860 997

128 - Reference Identification Qualifier

D3- National Association of Boards of Pharmacy Number

128 - Reference Identification Qualifier

DB- Buyer's Debit Memo

2/0800 ADX03 2/1100 REF01 2/2100 ADX03

128 - Reference Identification Qualifier

DK- Dock Number 1/3500 REF01 1/3400 REF01

128 - Reference Identification Qualifier

DP - Department Number

1/0500 REF01 1/0500 REF01 1/0500 REF01 2/1500 REF01 Order

1/0500 REF01

128 - Reference Identification Qualifier

HB- Bill & Hold Invoice Number

2/1500 REF01 Order

128 - Reference Identification Qualifier

IA- Internal Vendor Number

1/0500 REF01 1/0500 REF01 1/0500 REF01 2/1500 REF01 Order

1/0500 REF01

128 - Reference Identification Qualifier

IT - Internal Customer Number

1/0500 REF01 1/0500 REF01 1/0500 REF01 2/1500 REF01 Order

1/0500 REF01

128 - Reference Identification Qualifier

IV - Seller's Invoice Number

2/1500 RMR01 1/0500 REF01 2/1500 REF01 Order

128 - Reference Identification Qualifier

LT- Lot Number 2/1500 REF01 Item

128 - Reference Identification Qualifier

MB- Master Bill of Lading

2/1500 REF01 Shipment

128 - Reference Identification Qualifier

MR- Merchandise Type Code

2/1500 REF01 Order

128 - Reference Identification Qualifier

PD Promotion/Deal Number

1/0500 REF01 2/1500 REF01 Order

1/0500 REF01

128 - Reference Identification Qualifier

QC- Product Specification Document Number

2/1500 REF01 Order

128 - Reference Identification Qualifier

SB- Sales Region Number

2/1500 REF01 Order

128 - Reference Identification Qualifier

SE- Serial Number 2/1500 REF01 Item

Page 83: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

GS1 Canada – Industry Relations Standards Page 26 of 81

Foodservice EDI Change Summary Version 4010 to 4010-2012

Data Element # and Name Codes 810 820 850 855 856 860 997

128 - Reference Identification Qualifier

VN - Vendor Order Number

1/0500 REF01 2/1500 REF01 Order

1300 Service, Promotion Charge Code

Yes Yes Yes

1300 Service, Promotion Charge Code

D350- Goods and Services Credit Allowance

2/1800 SAC02 3/0400 SAC02

1/1200 SAC02 2/1300 SAC02 1/1200 SAC02 2/1300 SAC02

1300 Service, Promotion Charge Code

D360 -Goods and Services Tax Charge

2/1800 SAC02 3/0400 SAC02

1/1200 SAC02 2/1300 SAC02 1/1200 SAC02 2/1300 SAC02

1300 Service, Promotion Charge Code

H490- Subject To Tax On Resale

2/1800 SAC02 3/0400 SAC02

1/1200 SAC02 2/1300 SAC02 1/1200 SAC02 2/1300 SAC02

1300 Service, Promotion Charge Code

H770- Tax - State Tax 2/1800 SAC02 3/0400 SAC02

1/1200 SAC02 2/1300 SAC02 1/1200 SAC02 2/1300 SAC02

1300 Service, Promotion Charge Code

H806- Tax Credit 2/1800 SAC02 3/0400 SAC02

1/1200 SAC02 2/1300 SAC02 1/1200 SAC02 2/1300 SAC02

1301 Agency Service, Promotion, Allowance, or Charge Code

2/1800 SAC04 1/1200 SAC04 2/1300 SAC04

'2/1300 1301 1/1200 SAC04

133 Routing Sequence Code Yes Yes Yes

133 Routing Sequence Code 1- 1st Carrier after Origin Carrier

1/2400 TD501 2/1200 TD501 Shipment

1/2400 TD501

133 Routing Sequence Code 2-2nd Carrier after Origin Carrier

1/2400 TD501 2/1200 TD501 Shipment

1/2400 TD501

133 Routing Sequence Code 3- 3rd Carrier after Origin Carrier

1/2400 TD501 2/1200 TD501 Shipment

1/2400 TD501

133 Routing Sequence Code 4- 4th Carrier after Origin Carrier

1/2400 TD501 2/1200 TD501 Shipment

1/2400 TD501

133 Routing Sequence Code 5- 5th Carrier after Origin Carrier

1/2400 TD501 2/1200 TD501 Shipment

1/2400 TD501

133 Routing Sequence Code 6- 6th Carrier after Origin Carrier

1/2400 TD501 2/1200 TD501 Shipment

1/2400 TD501

133 Routing Sequence Code 7- 7th Carrier after 1/2400 TD501 2/1200 TD501 1/2400 TD501

Page 84: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

GS1 Canada – Industry Relations Standards Page 27 of 81

Foodservice EDI Change Summary Version 4010 to 4010-2012

Data Element # and Name Codes 810 820 850 855 856 860 997

Origin Carrier Shipment

133 Routing Sequence Code 8- 8th Carrier after Origin Carrier

1/2400 TD501 2/1200 TD501 Shipment

1/2400 TD501

133 Routing Sequence Code 9- 9th Carrier after Origin Carrier

1/2400 TD501 2/1200 TD501 Shipment

1/2400 TD501

133 Routing Sequence Code A -Origin Carrier, Agent's Routing (Rail)

1/2400 TD501 2/1200 TD501 Shipment

1/2400 TD501

133 Routing Sequence Code B- Origin/Delivery Carrier (Any Mode)

1/2400 TD501 2/1200 TD501 Shipment

1/2400 TD501

133 Routing Sequence Code O- Origin Carrier (Air, Motor, or Ocean)

1/2400 TD501 2/1200 TD501 Shipment

1/2400 TD501

133 Routing Sequence Code S- Origin Carrier, Shipper's Routing (Rail)

1/2400 TD501 2/1200 TD501 Shipment

1/2400 TD501

143 Transaction Set ID Yes Yes Yes Yes Yes Yes Yes

143 Transaction Set ID 810 Invoice 1/0100 ST01 01/0300 AK201

143 Transaction Set ID 820 Payment Order/Remittance Advice

1/0100 ST01 01/0300 AK201

143 Transaction Set ID 850 Purchase Order 01/0100 ST01 01/0300 AK201

143 Transaction Set ID 855 Purchase Order Acknowledgment

01/0100 ST01 01/0300 AK201

143 Transaction Set ID 856 Ship Notice/Manifest

01/0100 ST01 01/0300 AK201

143 Transaction Set ID 860 Purchase Order Change Request - Buyer Initiated

1/0100 ST01 01/0300 AK201

143 Transaction Set ID 997 Functional Acknowledgment

01/0100 ST01

146 Shipment Method of Payment

Yes Yes Yes

146 Shipment Method of Payment

CC- Collect 1/1500 FOB01 1/0800 FOB01 1/0800 FOB01

Page 85: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

GS1 Canada – Industry Relations Standards Page 28 of 81

Foodservice EDI Change Summary Version 4010 to 4010-2012

Data Element # and Name Codes 810 820 850 855 856 860 997

146 Shipment Method of Payment

PB- Customer Pick-up/Backhaul

1/1500 FOB01 1/0800 FOB01 1/0800 FOB01

146 Shipment Method of Payment

PP- Prepaid (by Seller) 1/1500 FOB01 1/0800 FOB01 1/0800 FOB01

152 Special Handling Code Yes

152 Special Handling Code CC- Container, Consolidator Load

2/1400 TD401 Shipment

152 Special Handling Code CF-Container, Factory Load

2/1400 TD401 Shipment

152 Special Handling Code LN- Less Than Container, Consolidator Load

2/1400 TD401 Shipment

152 Special Handling Code LR- Less Than Container, Factory Load

2/1400 TD401 Shipment

152 Special Handling Code TC- Trailer, Consolidator Load

2/1400 TD401 Shipment

152 Special Handling Code TF-Trailer, Factory Load 2/1400 TD401 Shipment

156 State or Province 1/0100 N402 1/1000 N402 1/3400 N402 1/3200 N402 2/2500 N402 Shipment

1/3300 N402

166 Address Information 1/0900 N301, 02

1/0900 N301, 02

1/3300 N301, 02

1/3200 N301, 02

2/2400 N301, 02 Shipment 2/2400 N301,

02 Order 2/2500 N402

Order

1/3200 N301, 302

183 Volume 2/1100 TD109

187 Weight Qualifier Yes

187 - Weight Qualifier G - Gross Weight 2/1100 TD106 Shipment

2/1100 TD106 Order

19 City Name 1/0100 N401 1/1000 N401 1/3400 N401 1/3300 N401 2/2500 N401 Shipment

2/2500 N401 Order

1/3300 N401

Page 86: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

GS1 Canada – Industry Relations Standards Page 29 of 81

Foodservice EDI Change Summary Version 4010 to 4010-2012

Data Element # and Name Codes 810 820 850 855 856 860 997

2 Number of Accepted Transaction Sets

1/0700 AK904

206 Equipment Initial 2/1300 TD302 Shipment

207 Equipment Number 2/1300 TD307 Shipment

212 Unit Price 2/0100 ITD104 2/0500 CTP03

0/0400 CTP03 2/0100 PO104 2/0400 CT03

2/0100 POC06 2/0400 CTP03

234 Product/Service ID 2/0100 P0107 2/0100 PO107 2/0200 LIN03, 05 Pack

2/0200 LIN03 Item

2/0100 POC09

235 Product/Service ID Qualifier

Yes Yes Yes Yes Yes

235 Product/Service ID Qualifier

LT- Lot Number 2/0200 LIN02, 04 Pack

235 Product/Service ID Qualifier

UK - GTIN 14-digit Data Structure

2/0100 IT106 2/0100 PO106 20100/PO106 2/0200 LIN02, 04 Pack

2/0200 LIN02 Item

2/0100 POC08

236 Price Identifier Code Yes Yes Yes Yes

236 Price Identifier Code ALT- Alternate Price 2/0400 CTP02

236 Price Identifier Code CAT - Catalog Price 2/0400 CTP02

236 Price Identifier Code MSR- Manufacturer's Suggested Retail

2/0400 CTP02

236 Price Identifier Code PRP- Promotional price 2/0400 CTP02

236 Price Identifier Code RES- Resale 2/0400 CTP02

236 Price Identifier Code UCP - Unit cost price 2/0500 CTP02 2/0400 CTP02 2/0400 CTP02 2/0400 CTP02

248 Allowance or Charge Indicator

Yes Yes Yes Yes

248 Allowance or Charge Indicator

A - Allowance 2/1800 SAC01 3/0400 SAC01

1/1200 SAC01 2/1300 SAC01

2/1300 SAC01 1/1200 SAC01 2/1300 SAC01

248 Allowance or Charge Indicator

C - Charge 2/1800 SAC01 3/0400 SAC01

1/1200 SAC01 2/1300 SAC01

2/1300 SAC01 1/1200 SAC01 2/1300 SAC01

Page 87: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

GS1 Canada – Industry Relations Standards Page 30 of 81

Foodservice EDI Change Summary Version 4010 to 4010-2012

Data Element # and Name Codes 810 820 850 855 856 860 997

248 Allowance or Charge Indicator

N - No Allowance or Charge

2/1800 SAC01 3/0400 SAC01

1/1200 SAC01 2/1300 SAC01

2/1300 SAC01 1/1200 SAC01 2/1300 SAC01

248 Allowance or Charge Indicator

R- Allowance Request 2/1800 SAC01 3/0400 SAC01

1/1200 SAC01 2/1300 SAC01

2/1300 SAC01 1/1200 SAC01 2/1300 SAC01

26 Country Code Code defining international

Yes YES Yes Yes 2/2500 N404 Shipment

2/2500 N404 Order

Yes

26 Country Code CA- Canada 1/0100 N404 1/1000 N404 1/3400 N404 1/3300 N404 1/3300 N404

26 Country Code MX-Mexico 1/0100 N404 1/1000 N404 1/3400 N404 1/3300 N404 1/3300 N404

26 Country Code US-United States 1/0100 N404 1/1000 N404 1/3400 N404 1/3300 N404 1/3300 N404

28 Group Control Number 1/0200 AK102

280 Exchange Rate 1/0400 CUR03

289 Multiple Price Quantity 2/0400 CTP11

305 Transaction Handling Code Yes

305 Transaction Handling Code I- Remittance Information Only

1/0200 BPR01

309 Location Qualifier Yes Yes Yes Yes

309 Location Qualifier D- Census Schedule D 2/2500 N405 Shipment

309 Location Qualifier DE - Destination (Shipping)

1/1500 FOB02 1/0800 FOB02 1/0800 PFB02

309 Location Qualifier IA- International Air Transport Association (IATA) Location Qualifier

2/2500 N405 Shipment

309 Location Qualifier K- Census Schedule K 2/2500 N405 Shipment

309 Location Qualifier OR - Origin ( Shipping Point)

1/1500 FOB02 1/0800 FOB02 1/0800 PFB02

309 Location Qualifier W- Worldwide Geographic Location Code

2/2500 N405 Shipment

310 Location Identifier 2/2500 N406

Page 88: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

GS1 Canada – Industry Relations Standards Page 31 of 81

Foodservice EDI Change Summary Version 4010 to 4010-2012

Data Element # and Name Codes 810 820 850 855 856 860 997 Shipment

324 Purchase Order Number 1/0200 BIG04 1/0200 BEG03 1/0200 BAK03 2/0500 PRF01 Order

1/0200 BCH03

326 Request Reference Number

1/0200 BCH07

328 Release Number 1/0200 BEG04 1/0200 BCH04

329 Transaction Set Control Number

1/0100 ST02 3/0800 SE02

01/0100 ST02 3/0100 SE02

1/0100 ST02 3/0300 SE02

1/0100 ST02 3/0300 SE02

1/0100 ST02 3/0200 SE02

1/0100 ST02 3/0300 SE02

1/0100 ST02 1/0300 AK202

330 Quantity Ordered 2/0100 PO102 2/010 PO102 2/0100 POC03

331 Allowance or Charge Method of Handling Code

Yes Yes Yes Yes

331 Allowance or Charge Method of Handling Code

01- Bill Back 2/1800 SAC12 3/0400 SAC12

1/1200 SAC12 2/1300 SAC012

2/1300 SAC12 1/1200 SAC12 2/1300 SAC12

331 Allowance or Charge Method of Handling Code

02- Off Invoice 2/1800 SAC12 3/0400 SAC12

1/1200 SAC12 2/1300 SAC012

2/1300 SAC12 1/1200 SAC12 2/1300 SAC12

331 Allowance or Charge Method of Handling Code

03- Vendor Check to Customer

2/1800 SAC12 3/0400 SAC12

1/1200 SAC12 2/1300 SAC012

2/1300 SAC12 1/1200 SAC12 2/1300 SAC12

331 Allowance or Charge Method of Handling Code

04- Credit Customer Account

2/1800 SAC12 3/0400 SAC12

1/1200 SAC12 2/1300 SAC012

2/1300 SAC12 1/1200 SAC12 2/1300 SAC12

331 Allowance or Charge Method of Handling Code

05- Charge to be Paid by Vendor

2/1800 SAC12 3/0400 SAC12

1/1200 SAC12 2/1300 SAC012

2/1300 SAC12 1/1200 SAC12 2/1300 SAC12

331 Allowance or Charge Method of Handling Code

06- Charge to be Paid by Customer

2/1800 SAC12 3/0400 SAC12

1/1200 SAC12 2/1300 SAC012

2/1300 SAC12 1/1200 SAC12 2/1300 SAC12

332 Percent 2/1800 SAC07 1/1200 SAC07 2/1300 SAC07

2/1300 SAC07 1/1200 SAC07 2/1300 SAC07

333 Terms Basis Date Code Yes Yes Yes

333 Terms Basis Date Code 1 - Ship Date 1/1300 ITD02 1/1300 ITD02

333 Terms Basis Date Code 2 - Delivery Date 1/1300 ITD02 1/1300 ITD02 1/1300 ITD02

333 Terms Basis Date Code 3 - Invoice date 1/1300 ITD02 1/1300 ITD02 1/1300 ITD02

333 Terms Basis Date Code 4- Specified Date 1/1300 ITD02 1/1300 ITD02 1/1300 ITD02

333 Terms Basis Date Code 7 - Effective Date 1/1300 ITD02 1/1300 ITD02

333 Terms Basis Date Code 15 - Receipt of Goods 1/1300 ITD02 1/1300 ITD02 1/1300 ITD02

336 Terms Type Code Yes Yes Yes Yes

Page 89: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

GS1 Canada – Industry Relations Standards Page 32 of 81

Foodservice EDI Change Summary Version 4010 to 4010-2012

Data Element # and Name Codes 810 820 850 855 856 860 997

336 Terms Type Code 05 - Discount Not Applicable

01/1300 ITD01 1/1300 ITD01 1/1300 ITD01

336 Terms Type Code 08 - Basic Discount Offered

01/1300 ITD01 1/1300 ITD01 1/1300 ITD01

336 Terms Type Code 09 - Proximo 01/1300 ITD01 1/1300 ITD01 1/1300 ITD01

336 Terms Type Code 14 - Previously agreed upon

01/1300 ITD01 1/1300 ITD01 1/1300 ITD01

336 Terms Type Code DI-Delivery Instructions Contact

2/1510 PER01 Shipment

337 Time 1/1500 DTM03 1/0200 BSN04 2/2000 DTM03

Shipment

1/1500 DTM03

338 Terms Discount Percent 01/1300 ITD03 1/1300 ITD03 1/1300 ITD03

349 Item Description Type Yes YES YES Yes Yes

349 Item Description Type F - Free-form 2/0600 PID01 2/0500 PID01 2/0500 PID01 2/0700 PID01 Item

2/0500 PID01

349 Item Description Type S- Structured (From Industry Code List)

2/0500 PID01

349 Item Description Type X- Semi-structured (Code and Text)

2/0500 PID01

350 Assigned Identification 2/0100 POC01

351 Terms Discount Days Due 1/1300 ITD05 1/1300 ITD05 1/1300 ITD05

352 Description 1/1500 FOB03 2/0600 PID05 2/1800 SAC 15

2/1100 REF03 1/0800 FOB03 1/1200 SAC15 2/0500 PID05 2/1300 SAC15

2/0500 PID05 '2/1300 SAC15

2/0700 PID02 Item

1/0800 FOB02 1/1200 SAC15 2/0500 PID05 2/1300 SAC15

353 Transaction Set Purpose Code

Yes Yes Yes Yes

353 - Transaction Set Purpose Code

00 - Original 1/0200 BEG01 1/0200 BAK01 1/0200 BSN01

353 - Transaction Set Purpose Code

01 - Cancellation 1/0200 BAK01 1/0200 BCH01

353 - Transaction Set Purpose Code

04 - Change 1/0200 BCH01

Page 90: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

GS1 Canada – Industry Relations Standards Page 33 of 81

Foodservice EDI Change Summary Version 4010 to 4010-2012

Data Element # and Name Codes 810 820 850 855 856 860 997

353 - Transaction Set Purpose Code

05 - Replace 1/0200 BAK01

353 - Transaction Set Purpose Code

06 - Confirmation 1/0200 BEG01

353 - Transaction Set Purpose Code

07 - Duplicate 1/0200 BSN01

353 - Transaction Set Purpose Code

16- Proposed 1/0200 BAK01

353 - Transaction Set Purpose Code

19- Seller initiated change

1/0200 BAK01

353 - Transaction Set Purpose Code

22 - Information Copy 1/0200 BEG01

353 - Transaction Set Purpose Code

CO - Corrected

354 Number of Line items 3/0700 CTT01 3/0100 CTT01 3/0100 CTT01 3/0100 CTT01 3/0100 CTT01

355 Unit or Basis for Measure Code

Yes Yes Yes Yes Yes

355 Unit of Measure Code BG - Bag 2/0100 IT103 2/1000 PO403 2/1800 SAC09 3/0400 SAC09 3/0600 ISS02

1/1200 SAC09 2/0100 PO103 2/0900 PO403 2/1300 SAC09

2/0100 PO103 2/0400 CTP05-

01 2/1300 SAC09 2/2700 ACK03

2/0300 SN103 Pack

2/0300 SN103 Item

1/1200 SAC09 2/0100 POC05-

01 2/0900 PO403 2/1300 SAC09

355 Unit of Measure Code BR- Barrel 2/0100 IT103 2/1000 PO403 2/1800 SAC09 3/0400 SAC09 3/0600 ISS02

1/1200 SAC09 2/0100 PO103 2/0900 PO403 2/1300 SAC09

2/0100 PO103 2/0400 CTP05-

01 2/1300 SAC09 2/2700 ACK03

2/0300 SN103 Pack

2/0300 SN103 Item

1/1200 SAC09 2/0100 POC05-

01 2/0900 PO403 2/1300 SAC09

355 Unit of Measure Code CA - Case 2/0100 IT103 2/1000 PO403 2/1800 SAC09 3/0400 SAC09 3/0600 ISS02

1/1200 SAC09 2/0100 PO103 2/0900 PO403 2/1300 SAC09

2/0100 PO103 2/0400 CTP05-

01 2/1300 SAC09 2/2700 ACK03

2/0300 SN103 Pack

2/0300 SN103 Item

1/1200 SAC09 2/0100 POC05-

01 2/0900 PO403 2/1300 SAC09

Page 91: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

GS1 Canada – Industry Relations Standards Page 34 of 81

Foodservice EDI Change Summary Version 4010 to 4010-2012

Data Element # and Name Codes 810 820 850 855 856 860 997

355 Unit of Measure Code CC - Cubic Centimeter 2/0400 CTP05-01

2/0900 PO409

2/1100 TD110 Shipment

355 Unit of Measure Code CF-Cubic Feet 2/0400 CTP05-01

2/0900 PO409

2/1100 TD110 Shipment

355 Unit of Measure Code CI- CubicInches 2/0400 CTP05-01

2/0900 PO409

2/1100 TD110 Shipment

355 Unit of Measure Code CR - Cubic Meter 2/0400 CTP05-01

2/0900 PO409

2/1100 TD110 Shipment

355 Unit of Measure Code DR - Drum 2/0100 IT103 2/1000 PO403 2/1800 SAC09 3/0400 SAC09 3/0600 ISS02

1/1200 SAC09 2/0100 PO103 2/0900 PO403 2/1300 SAC09

2/0100 PO103 2/0400 CTP05-

01 2/1300 SAC09 2/2700 ACK03

2/0300 SN103 Pack

2/0300 SN103 Item

1/1200 SAC09 2/0100 POC05-

01 2/0900 PO403 2/1300 SAC09

355 Unit of Measure Code EA - Each 2/0100 IT103 2/1000 PO403 2/1800 SAC09 3/0400 SAC09 3/0600 ISS02

1/1200 SAC09 2/0100 PO103 2/0900 PO403 2/1300 SAC09

2/0100 PO103 2/0400 CTP05-

01 2/1300 SAC09 2/2700 ACK03

2/0300 SN103 Pack

2/0300 SN103 Item

1/1200 SAC09 2/0100 POC05-

01 2/0900 PO403 2/1300 SAC09

355 Unit of Measure Code FT-Foot 2/0400 CTP05-01

355 Unit of Measure Code FZ-Fluid Ounce (Imperial)

2/0400 CTP05-01

355 Unit of Measure Code GA - Gallon 2/0100 IT103 2/1000 PO403 2/1800 SAC09 3/0400 SAC09 3/0600 ISS02

1/1200 SAC09 2/0100 PO103 2/0900 PO403 2/1300 SAC09

2/0100 PO103 2/0400 CTP05-

01 2/0900 PO409 2/1300 SAC09 2/2700 ACK03

2/1100 TD110 Shipment

2/0300 SN103 Pack

2/0300 SN103 Item

1/1200 SAC09 2/0100 POC05-

01 2/0900 PO403 2/1300 SAC09

355 Unit of Measure Code GI- Imperial Gallons 2/0400 CTP05-01

2/0900 PO409

2/1100 TD110 Shipment

Page 92: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

GS1 Canada – Industry Relations Standards Page 35 of 81

Foodservice EDI Change Summary Version 4010 to 4010-2012

Data Element # and Name Codes 810 820 850 855 856 860 997

355 Unit of Measure Code GR - Gram 2/0400 CTP05-01

355 Unit of Measure Code IN-Inch 2/0400 CTP05-01

355 Unit of Measure Code KG - Kilogram 2/0100 IT103 2/1000 PO403 2/1800 SAC09 3/0400 SAC09 3/0600 ISS02 3/0600 ISS04

1/1200 SAC09 2/0100 PO103 2/0900 PO403 2/1300 SAC09

2/0100 PO103 2/0400 CTP05-

01 2/0900 PO407 2/1300 SAC09 2/2700 ACK03

2/0300 SN103 Pack

2/0300 SN103 Item

2/1100 TD108 Shipment

2/1100 TD108 Order

1/1200 SAC09 2/0100 POC05-

01 2/0900 PO403 2/1300 SAC09

355 Unit of Measure Code LB - Pound 2/0100 IT103 2/1000 PO403 2/1800 SAC09 3/0400 SAC09 3/0600 ISS02 3/0600 ISS04

1/1200 SAC09 2/0100 PO103 2/0900 PO403 2/1300 SAC09

2/0100 PO103 2/0400 CTP05-

01 2/0900 PO407 2/1300 SAC09 2/2700 ACK03

2/0300 SN103 Pack

2/0300 SN103 Item

2/1100 TD108 Shipment

2/1100 TD108 Order

1/1200 SAC09 2/0100 POC05-

01 2/0900 PO403 2/1300 SAC09

355 Unit of Measure Code LT - Liter 2/0100 IT103 2/1000 PO403 2/1800 SAC09 3/0400 SAC09 3/0600 ISS02

1/1200 SAC09 2/0100 PO103 2/0900 PO403 2/1300 SAC09

2/0100 PO103 2/0400 CTP05-

01 2/0900 PO409 2/1300 SAC09

2/1100 TD110 Shipment

2/0300 SN103 Pack

2/0300 SN103 Item

1/1200 SAC09 2/0100 POC05-

01 2/0900 PO403 2/1300 SAC09

355 Unit of Measure Code ML - Milliliter 2/0400 CTP05-01

2/0900 PO409

2/1100 TD110 Shipment

PA-Pail 2/0100 IT103 2/1000 PO403 2/1800 SAC09 3/0400 SAC09 3/0600 ISS02

1/1200 SAC09 2/0100 PO103 2/0900 PO403 2/1300 SAC09

2/0100 PO103 2/0400 CTP05-

01 2/1300 SAC09 2/2700 ACK03

2/0300 SN103 Pack

2/0300 SN103 Item

1/1200 SAC09 2/0100 POC05-

01 2/0900 PO403 2/1300 SAC09

Page 93: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

GS1 Canada – Industry Relations Standards Page 36 of 81

Foodservice EDI Change Summary Version 4010 to 4010-2012

Data Element # and Name Codes 810 820 850 855 856 860 997

355 Unit of Measure Code PL- Pallet/Unit Load 2/0100 IT103 2/1000 PO403 2/1800 SAC09 3/0400 SAC09 3/0600 ISS02

1/1200 SAC09 2/0100 PO103 2/0900 PO403 2/1300 SAC09

2/0100 PO103 2/0400 CTP05-

01 2/1300 SAC09 2/2700 ACK03

2/0300 SN103 Pack

2/0300 SN103 Item

1/1200 SAC09 2/0100 POC05-

01 2/0900 PO403 2/1300 SAC09

355 Unit of Measure Code PT- Pint 2/0400 CTP05-01

2/0900 PO409

2/1100 TD110 Shipment

355 Unit of Measure Code PX- Pint, Imperial 2/0400 CTP05-01

2/0900 PO409

2/1100 TD110 Shipment

355 Unit of Measure Code TE-Tote 2/0100 IT103 2/1000 PO403 2/1800 SAC09 3/0400 SAC09 3/0600 ISS02

1/1200 SAC09 2/0100 PO103 2/0900 PO403 2/1300 SAC09

2/0100 PO103 2/0400 CTP05-

01 2/1300 SAC09 2/2700 ACK03

2/0300 SN103 Pack

2/0300 SN103 Item

1/1200 SAC09 2/0100 POC05-

01 2/0900 PO403 2/1300 SAC09

355 Unit of Measure Code YD - Yard 2/0400 CTP05-01

356 Pack 2/1000 PO401 2/0900 PO401 2/0900 PO401 2/2150 PAL03 Shipping Tare 2/0600 Item

2/0900 PO401

357 Size 2/1000 PO402 2/0900 PO402 2/0900 PO402

358 Quantity Invoiced 2/0100 IT102

362 Terms Discount Amount 1/1300 ITD08 1/1300 ITD08 1/1300 ITD08

364 Communication Number 1/0600 PER04, 06

1/0600 PER04, 06

1/1510 PER04, 06 Shipment

1/0600 PER04, 06

365 Communication Number Qualifier

Yes Yes Yes Yes

365 Communication Number Qualifier

EM - Electronic Mail 1/0600 PER03, 05

1/0600 PER03, 05

2/1510 PER03, 05 Shipment

1/0600 PER03, 05

365 Communication Number Qualifier

TE - Telephone 1/0600 PER03, 05

1/0600 PER03, 05

2/1510 PER0, 05 Shipment

1/0600 PER03, 05

366 Contact Function Code Yes Yes Yes Yes

Page 94: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

GS1 Canada – Industry Relations Standards Page 37 of 81

Foodservice EDI Change Summary Version 4010 to 4010-2012

Data Element # and Name Codes 810 820 850 855 856 860 997

366 - Contact Function Code BD - Buyer Name / Department

1/0600 PER01 1/0600 PER01

366 - Contact Function Code CR - Customer Relations

1/0900 PER01

366 - Contact Function Code IC- Information Contact

1/0600 PER01

1/0600 PER01

366 - Contact Function Code DI- Delivery Instructions Contact

1/1510 PER01 Shipment

366 - Contact Function Code SR - Sales Representative or Department

1/0900 PER01

367 Contract Number 1/0200 BCH07

368 Shipment/Order Status Code

Yes

368 Shipment/Order Status Code

CC - Shipment Complete on (Date)

2/1200 TD506 Shipment

370 Terms Discount Due Date 1/1300 ITD04 1/1300 ITD04

373 Date 1/1400 DTM02 1/0200 BIG01,

03

1/0600 DTM02 2/1800 DTM02 1/0200 BPR16

1/0200 BEG05 1/1500 DTM02

1/0200 BAK04 1/1500 DTM02 2/2700 ACK05

1/0200 BSN03 2/2000 DTM02

Shipment 2/2000 DTM02

Item

1/0200 BCH06, 11

1/1500 DTM02

374 Date/Time Qualifier Yes Yes YES Yes Yes Yes

374 Date/Time Qualifier 001- Cancel After 1/1500 DTM01

374 Date/Time Qualifier 002 - Delivery Requested

1/1400 DTM01 1/1500 DTM01 1/1500 DTM01 1/1500 DTM01

374 Date/Time Qualifier 003- Invoice 2/1800 DTM01

374 Date/Time Qualifier 007 - Effective 1/0600 DTM01

374 Date/Time Qualifier 010- Requested Ship 1/1500 DTM01

374 Date/Time Qualifier 011 - Shipped 1/1400 DTM01 2/2000 DTM01 Shipment

374 Date/Time Qualifier 017 - Estimated Delivery

2/2000 DTM01 Shipment

Page 95: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

GS1 Canada – Industry Relations Standards Page 38 of 81

Foodservice EDI Change Summary Version 4010 to 4010-2012

Data Element # and Name Codes 810 820 850 855 856 860 997

374 Date/Time Qualifier 118- Requested Pick-up 1/1500 DTM01 1/1500 DTM01

374 Date/Time Qualifier 036 - Expiration 2/2000 DTM01 Item

374 Date/Time Qualifier 067 - current schedule delivery

2/2000 DTM01 Shipment

374 Date/Time Qualifier 068 Current Schedule Ship

1/1500 DTM01 2/2700 ACK04

2/2000 DTM01 Shipment

374 Date/Time Qualifier 086 Scheduled for Shipment (Week of)

1/1500 DTM01

374 Date/Time Qualifier 100 - No Shipping Schedule Established as of

2/2700 ACK04

374 Date/Time Qualifier AA1- Estimated Point of Arrival

2/2000 DTM01 Shipment

374 Date/Time Qualifier AA2- Estimated Point of Discharge

2/2000 DTM01 Shipment

378 Allowance/Charge Percent Qualifier

Yes Yes Yes Yes

378 Allowance/Charge Percent Qualifier

1- Item List Cost 2/1800 SAC06 3/0400 SAC06

1/1200 SAC06 2/1300 SAC06

2/1300 SAC06 1/1200 SAC06 2/1300 SAC06

378 Allowance/Charge Percent Qualifier

2- Item Net Cost 2/1800 SAC06 3/0400 SAC06

1/1200 SAC06 2/1300 SAC06

2/1300 SAC06 1/1200 SAC06 2/1300 SAC06

378 Allowance/Charge Percent Qualifier

3- Discount/Gross 2/1800 SAC06 3/0400 SAC06

1/1200 SAC06 2/1300 SAC06

2/1300 SAC06 1/1200 SAC06 2/1300 SAC06

378 Allowance/Charge Percent Qualifier

4 -Discount/Net 2/1800 SAC06 3/0400 SAC06

1/1200 SAC06 2/1300 SAC06

2/1300 SAC06 1/1200 SAC06 2/1300 SAC06

378 Allowance/Charge Percent Qualifier

5- Base Price per Unit 2/1800 SAC06 3/0400 SAC06

1/1200 SAC06 2/1300 SAC06

2/1300 SAC06 1/1200 SAC06 2/1300 SAC06

378 Allowance/Charge Percent Qualifier

6- Base Price Amount 2/1800 SAC06 3/0400 SAC06

1/1200 SAC06 2/1300 SAC06

2/1300 SAC06 1/1200 SAC06 2/1300 SAC06

378 Allowance/Charge Percent Qualifier

7-Base Price Amount Less Previous Discount

2/1800 SAC06 3/0400 SAC06

1/1200 SAC06 2/1300 SAC06

2/1300 SAC06 1/1200 SAC06 2/1300 SAC06

Page 96: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

GS1 Canada – Industry Relations Standards Page 39 of 81

Foodservice EDI Change Summary Version 4010 to 4010-2012

Data Element # and Name Codes 810 820 850 855 856 860 997

380 Quantity 2/1800 SAC10 1/1200 SAC10 2/1300 SAC10

2/0400 CT04 '2/1300 SAC11 2/270 ACK02

1/1200 SAC10, 11

2/1300 SAC10, 11

382 Number of Units Shipped

3/0600 ISS01 2/0300 SN102 Pack

2/0300 SN102 Item

384 Gross Weight per Pack 2/0900 PO406

385 Gross Volume per Pack 2/0900 PO408

386 Terms Net Days 1/1300 ITD07 1/1300 ITD07 1/1300 ITD07

387 Routing 1/2400 TD505 1/2400 TD505

396 Shipment Identification 1/0200 BSN02 2/1200 TD505

399 Pallet Exchange Code Yes

1- No Exchange/No Return

2/2150 PAL15 Shipping Tare

399 Pallet Exchange Code 2- Exchange Pallets 2/2150 PAL15 Shipping Tare

399 Pallet Exchange Code 3- Return Pallets 2/2150 PAL15 Shipping Tare

399 Pallet Exchange Code 4- Pallets to be Purchased by Customer

2/2150 PAL15 Shipping Tare

399 Pallet Exchange Code 5- Third-Party Pallet Exchange

2/2150 PAL15 Shipping Tare

40 Equipment Description Code

Yes Yes Yes

40 Equipment Description Code

CN- Container 2/1300 TD301 Unit or Lot

40 Equipment Description Code

CV- Closed Van 1/2500 TD301 2/1300 TD301 Shipment

1/2500 TD301

40 Equipment Description Code

CZ- Refrigerated Container

2/1300 TD301 Unit or Lot

40 Equipment Description FT- Flat Bed Trailer 1/2500 TD301 2/1300 TD301 1/2500 TD301

Page 97: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

GS1 Canada – Industry Relations Standards Page 40 of 81

Foodservice EDI Change Summary Version 4010 to 4010-2012

Data Element # and Name Codes 810 820 850 855 856 860 997

Code Shipment

40 Equipment Description Code

RT- Controlled Temperature Trailer (Reefer)

1/2500 TD301 2/1300 TD301 Shipment

1/2500 TD301

40 Equipment Description Code

TL- Trailer (not otherwise specified)

1/2500 TD301 2/1300 TD301 Shipment

1/2500 TD301

40 Equipment Description Code

20- 20 ft. IL Container (Open Top)

2/1300 TD301 Unit or Lot

40 Equipment Description Code

2B- 20 ft. IL Container (Closed Top)

2/1300 TD301 Unit or Lot

40 Equipment Description Code

40- 40 ft. IL Container (Open Top)

2/1300 TD301 Unit or Lot

40 Equipment Description Code

4B- 40 ft. IL Container (Closed Top)

2/1300 TD301 Unit or Lot

426 Adjustment Reason Code Yes

426 Adjustment Reason Code 01- Pricing Error 2/0800 ADX02 2/2100 ADX02

426 Adjustment Reason Code 04- Item Not Accepted - Damaged

2/0800 ADX02 2/2100 ADX02

426 Adjustment Reason Code 06- Quantity Contested 2/0800 ADX02 2/2100 ADX02

426 Adjustment Reason Code 07- Incorrect Product 2/0800 ADX02 2/2100 ADX02

426 Adjustment Reason Code 11- Returns - Damage 2/0800 ADX02 2/2100 ADX02

426 Adjustment Reason Code 30- Delivery Charge Incorrect

2/0800 ADX02 2/2100 ADX02

426 Adjustment Reason Code 52- Credit for Overpayment

2/0800 ADX02 2/2100 ADX02

426 Adjustment Reason Code 53 -Remittance for 2/0800 ADX02 2/2100 ADX02

426 Adjustment Reason Code 55- Tax Deducted 2/0800 ADX02 2/2100 ADX02

Page 98: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

GS1 Canada – Industry Relations Standards Page 41 of 81

Foodservice EDI Change Summary Version 4010 to 4010-2012

Data Element # and Name Codes 810 820 850 855 856 860 997

446 Terms Net Due Date 1/1300 ITD06 1/1300 ITD06

447 Loop Identifier Codet 1/0400 AK303

478 Credit/Debit Flag Code Yes

478 Credit/Debit Flag Code C- Credit 1/0200 BPR03

478 Credit/Debit Flag Code D- Debit 1/0200 BPR03

479 Functional Identifier Code Yes

479 Functional Identifier Code IN - Invoice Information (810)

1/0200 AK101

479 Functional Identifier Code PC Purchase Order Change Request - Buyer Initiated (860)

1/0200 AK101

479 Functional Identifier Code PO Purchase Order (850)

1/0200 AK101

479 Functional Identifier Code PR Purchase Order Acknowledgement (855)

1/0200 AK101

479 Functional Identifier Code RA Payment Order/Remittance Advice (820)

1/0200 AK101

479 Functional Identifier Code SH Ship Notice/Manifest (856)

1/0200 AK101

481 Trace Type Code Yes

481 Trace Type Code 1- Current Transaction Trace Numbers

1/0350 TRN01

482 Payment Action Code Yes

482 Payment Action Code AJ Adjustment 2/1500 RMR03

482 Payment Action Code ER Evaluated Receipts Settlement

2/1500 RMR03

482 Payment Action Code FL Final 2/1500 RMR03

482 Payment Action Code NS Not Specified (Unknown as to Type of Payment)

2/1500 RMR03

482 Payment Action Code PA Payment in Advance 2/1500 RMR03

Page 99: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

GS1 Canada – Industry Relations Standards Page 42 of 81

Foodservice EDI Change Summary Version 4010 to 4010-2012

Data Element # and Name Codes 810 820 850 855 856 860 997

482 Payment Action Code PI Pay Item 2/1500 RMR03

482 Payment Action Code PO Payment on Account

2/1500 RMR03

482 Payment Action Code PP Partial Payment 2/1500 RMR03

482 Payment Action Code PR Progress Payment 2/1500 RMR03

506 (DFI) ID Number Qualifier Yes

506 (DFI) ID Number Qualifier 01- ABA Transit Routing Number Including Check Digits (9 digits)

1/0200 BPR06, 12

506 (DFI) ID Number Qualifier 02- Swift Identification (8 or 11 characters)

1/0200 BPR06, 12

506 (DFI) ID Number Qualifier 03- CHIPS (3 or 4 digits) 1/0200 BPR06, 12

506 (DFI) ID Number Qualifier 04- Canadian Bank Branch and Institution Number

1/0200 BPR06, 12

507 (DFI) Identification Number

1/0200 BPR07, 13

508 Account Number 1/0200 BPR09, 15

509 Originating Company Identifier

1/0200 BPR10

554 Assigned Number 2/0100 ENT01

559 Agency Qualifier Code Yes Yes Yes Yes

559 Agency Qualifier Code VI- Voluntary Inter-Industry Commerce Standard (VICS) EDI

2/1800 SAC03 3/0400 SAC03

1/1200 SAC03 2/1300 SAC03

2/0500 PID03 2/1300 SAC03

1/1200 SAC03 2/1300 SAC03

569 Account Number Qualifier Yes

569 Account Number Qualifier DA- Demand Deposit 1/0200 BPR08, 14

587 Acknowledgment Type Yes

587 Acknowledgment Type AC - Acknowledge - With Detail and Change

1/0200 BAK02

587 Acknowledgment Type AD- Acknowledge - 1/0200 BAK02

Page 100: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

GS1 Canada – Industry Relations Standards Page 43 of 81

Foodservice EDI Change Summary Version 4010 to 4010-2012

Data Element # and Name Codes 810 820 850 855 856 860 997

With Detail, No Change 587 Acknowledgment Type AE - Acknowledge -

With Exception Detail Only

1/0200 BAK02

587 Acknowledgment Type AK - Acknowledge - No Detail or Change

1/0200 BAK02

587 Acknowledgment Type AP- Acknowledge - Product Replenishment

1/0200 BAK02

587 Acknowledgment Type RJ - Rejected - No Detail

1/0200 BAK02

591 Payment Method Code Yes

591 Payment Method Code CHK- Check 1/0200 PBR04

610 Amount 2/1800 SAC05 2/1300 SAC05 1/1200 SAC05 '2/1300 SAC05

1/1200 SAC05 2/1300 SAC05

628 Hierarchical ID Number 2/0100 HL01 Shipment

2/0100 HL01 Unit or Lot

2/0100 HL01 Order

2/0100 HL01 Shipping Tare 2/0100 HL01

Pack 2/0100 HL01

Item

639 Basis of Unit Price Code Yes Yes

639 Basis of Unit Price Code LD Catalog Price per Dozen

2/0100 PO105 1/0100 POC07

639 Basis of Unit Price Code LE Catalog Price per Each

2/0100 PO105 1/0100 POC07

639 Basis of Unit Price Code NC No Charge 2/0100 PO105 1/0100 POC07

639 Basis of Unit Price Code PO Price per Ounce 2/0100 PO105 1/0100 POC07

639 Basis of Unit Price Code PP Price per Pound 2/0100 PO105 1/0100 POC07

639 Basis of Unit Price Code PR Promotion 2/0100 PO105 1/0100 POC07

Page 101: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

GS1 Canada – Industry Relations Standards Page 44 of 81

Foodservice EDI Change Summary Version 4010 to 4010-2012

Data Element # and Name Codes 810 820 850 855 856 860 997

639 Basis of Unit Price Code QT Quoted 2/0100 PO105 1/0100 POC07

639 Basis of Unit Price Code RD Retail Price per Dozen

2/0100 PO105 1/0100 POC07

639 Basis of Unit Price Code RE Retail Price per Each 2/0100 PO105 1/0100 POC07

639 Basis of Unit Price Code TD Contract Price per Dozen

2/0100 PO105 1/0100 POC07

639 Basis of Unit Price Code TE Contract Price per Each

2/0100 PO105 1/0100 POC07

639 Basis of Unit Price Code WD Wholesale Price per Dozen

2/0100 PO105 1/0100 POC07

639 Basis of Unit Price Code WE Wholesale Price per Each

2/0100 PO105 1/0100 POC07

66 Identification Code Qualifier

Yes Yes Yes Yes Yes Yes

66 Identification Code Qualifier 2 - Standard Carrier Alpha Code (SCAC)

1/2400 TD502 2/1200 TD502 Shipment

1/2400 TD502

66 Identification Code Qualifier 9 D-U-N-S+4, D-U-N-S Number with Four Character Suffix

1/0700 N103 1/3100 N103 1/3000 N103 2/2200 N103 Shipment

2/2200 N103 Order

1/3000 N103

66 Identification Code Qualifier 91 - Assigned by seller 1/2400 TD502 1/2400 TD502

66 Identification Code Qualifier 92 - Assigned by Buyer or Agent

1/0700 N103 1/2400 TD502 1/2400 TD502

66 Identification Code Qualifier UL - UCC/EAN Location Code

1/0700 N103 1/0700 N103 1/3100 N103 1/3000 N103 2/2200 N103 Shipment

2/2200 N103 Order

1/3000 N103

67 Identification Code 1/0700 N104 1/0700 N104 1/3100 N104 1/2400 TD503

1/3000 N104 2/1200 TD503 Shipment

2/2200 N104 Shipment

2/2200 N104 Order

1/2400 TD503 1/3000 N104

668 line Item status code Yes

Page 102: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

GS1 Canada – Industry Relations Standards Page 45 of 81

Foodservice EDI Change Summary Version 4010 to 4010-2012

Data Element # and Name Codes 810 820 850 855 856 860 997

668 line Item status code IA - Item Accepted 2/2700 ACK01

668 line Item status code IC - Item Accepted - Changes Made

2/2700 ACK01

668 line Item status code ID - Item Deleted 2/2700 ACK01

670 Change or Response Type Code

Yes

670 Change or Response Type Code

AI- Add Additional Item(s)

2/0100 POC02

670 Change or Response Type Code

CE- Changes To Item Level Allowance/Charges

2/0100 POC02

670 Change or Response Type Code

CT- Change of Dates 2/0100 POC02

670 Change or Response Type Code

DI- Delete Item(s) 2/0100 POC02

670 Change or Response Type Code

PC- Price Change 2/0100 POC02

670 Change or Response Type Code

QD- Quantity Decrease 2/0100 POC02

670 Change or Response Type Code

QI- Quantity Increase 2/0100 POC02

671 Quantity Left to Receive 2/0100 POC04

687 Class of Trade Code Yes

687 Class of Trade Code AG - Agent 2/0400 CTP01

687 Class of Trade Code BG - Buying Group 2/0400 CTP01

687 Class of Trade Code DE - Dealer 2/0400 CTP01

687 Class of Trade Code DF - Doctors' Offices

687 Class of Trade Code DI - Distributor 2/0400 CTP01

687 Class of Trade Code RS- Resale 2/0400 CTP01

715 Functional Group Acknowledge Code

Yes

715 Functional Group Acknowledge Code

A - Accepted 1/0700 AK901

Page 103: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

GS1 Canada – Industry Relations Standards Page 46 of 81

Foodservice EDI Change Summary Version 4010 to 4010-2012

Data Element # and Name Codes 810 820 850 855 856 860 997

715 Functional Group Acknowledge Code

E - Accepted But Errors Were Noted

1/0700 AK901

715 Functional Group Acknowledge Code

P - At least 1 transaction set rejected

1/0700 AK901

715 Functional Group Acknowledge Code

R - Rejected 1/0700 AK901

716 Functional Group Syntax Error Code

Yes

716 Functional Group Syntax Error Code

1 - Functional Group Not Supported

1/0700 AK905, 06, 07, 08 , 09

716 Functional Group Syntax Error Code

2 - Functional Group Version Not Supported

1/0700 AK905, 06, 07, 08 , 09

716 Functional Group Syntax Error Code

3 - Functional Group Trailer Missing

1/0700 AK905, 06, 07, 08 , 09

716 Functional Group Syntax Error Code

4 - Group Control Number in the Functional Group Header and Trailer Do Not Agree

1/0700 AK905, 06, 07, 08 , 09

716 Functional Group Syntax Error Code

5 - Number of Included Transaction Sets Does Not Match Actual Count

1/0700 AK905, 06, 07, 08 , 09

717 Transaction Set Acknowledgment Code

Yes

717 Transaction Set Acknowledgment Code

A - Accepted 1/0600 AK502

717 Transaction Set Acknowledgment Code

E - Accepted But Errors Were Noted

1/0600 AK502

717 Transaction Set Acknowledgment Code

R - Rejected 1/0600 AK502

718 Transaction Set Syntax Error Code

Yes

Page 104: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

GS1 Canada – Industry Relations Standards Page 47 of 81

Foodservice EDI Change Summary Version 4010 to 4010-2012

Data Element # and Name Codes 810 820 850 855 856 860 997

718 Transaction Set Syntax Error Code

1 - Transaction Set Not Supported

1/0600 AK502, 03, 04; 05, 06

718 Transaction Set Syntax Error Code

2 - Transaction Set Trailer Missing

1/0600 AK502, 03, 04, 05, 06

718 Transaction Set Syntax Error Code

3 - Transaction Set Control Number in Header and Trailer Do Not Match

1/0600 AK502, 03, 04, 05, 06

718 Transaction Set Syntax Error Code

4 - Number of Included Segments Does Not Match Actual Count

1/0600 AK502, 03, 04, 05, 06

718 Transaction Set Syntax Error Code

5 - One or More Segments in Error

1/0600 AK502, 03, 04, 05, 06

719 Segment Position in Transaction Set

1/0400 AK301

720 Segment Syntax Error Code

Yes

720 Segment Syntax Error Code 1 - Unrecognized segment ID

1/0400 AK304

720 Segment Syntax Error Code 2 - Unexpected segment

1/0400 AK304

720 Segment Syntax Error Code 3 - Mandatory segment missing

1/0400 AK304

721 Segment ID Code 1/0400 AK301

722 Element Position in Segment

1/0500 AK401-01

723 Data Element Syntax Error Code

Yes

724 Copy of Bad Data Element 1 Mandatory data element missing

1/0500 AK403

724 Copy of Bad Data Element 2 Conditional required data element missing.

1/0500 AK403

Page 105: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

GS1 Canada – Industry Relations Standards Page 48 of 81

Foodservice EDI Change Summary Version 4010 to 4010-2012

Data Element # and Name Codes 810 820 850 855 856 860 997

724 Copy of Bad Data Element 3 Too many data elements.

1/0500 AK403

724 Copy of Bad Data Element 4 Data element too short.

1/0500 AK403

724 Copy of Bad Data Element 5 Data element too long.

1/0500 AK403

724 Copy of Bad Data Element 6 Invalid character in data element.

1/0500 AK403

724 Copy of Bad Data Element 7 Invalid code value. 1/0500 AK403

724 Copy of Bad Data Element 1/0200 AK404

725 Data Element Reference Number

1/0500 AK402

734 Hierarchical Parent ID Number

2/0100 HL02 Unit or Lot

2/0100 HL02 Order

2/0100 HL02 Shiping Tare 2/0100 HO02

Pack 2/0100 HL02

Item

735 Hierarchical Level Code Yes

735 Hierarchical Level Code I- Item 2/0100 HL03 Item

735 Hierarchical Level Code O- Order 2/0100 HL03 Order

735 Hierarchical Level Code P- Pack 2/0100 HL03 Pack

735 Hierarchical Level Code UT- Unit or Lot 2/0100 HL03 Unit or Lot

735 Hierarchical Level Code S - Shipment 2/0100 HL03 Shipment

735 Hierarchical Level Code T- Shipping Tare 2/0100 HL03 Shipping Tare

750 Product/Process Yes Yes Yes Yes Yes

Page 106: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

GS1 Canada – Industry Relations Standards Page 49 of 81

Foodservice EDI Change Summary Version 4010 to 4010-2012

Data Element # and Name Codes 810 820 850 855 856 860 997

Characteristic Code 750 Product/Process

Characteristic Code 08- Product 2/0600 PID02 2/0500 PID02 2/0500 PID02 2/0700 PID02

Item 2/0500 PID02

750 Product/Process Characteristic Code

73- Vendor color description

2/0500 PID02 2/0500 PID02

750 Product/Process Characteristic Code

74- Vendor size description

2/0500 PID02 2/0500 PID02

750 Product/Process Characteristic Code

75- Buyer's Color Description

2/0500 PID02 2/0500 PID02

750 Product/Process Characteristic Code

91- Buyer's Item Size Description

2/0500 PID02 2/0500 PID02

751 Product Description Code 2/0500 PID04

752 Surface/Layer/Position Code

Yes

752 Surface/Layer/Position Code

R0- Relative Position 10 2/0500 PID06

752 Surface/Layer/Position Code

R1- Relative Position 1 2/0500 PID06

752 Surface/Layer/Position Code

R2- Relative Position 2 2/0500 PID06

752 Surface/Layer/Position Code

R3- Relative Position 3 2/0500 PID06

752 Surface/Layer/Position Code

R4- Relative Position 4 2/0500 PID06

752 Surface/Layer/Position Code

R5- Relative Position 5 2/0500 PID06

752 Surface/Layer/Position Code

R6- Relative Position 6 2/0500 PID06

752 Surface/Layer/Position Code

R7- Relative Position 7 2/0500 PID06

752 Surface/Layer/Position Code

R8- Relative Position 8 2/0500 PID06

752 Surface/Layer/Position Code

R9- Relative Position 9 2/0500 PID06

Page 107: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

GS1 Canada – Industry Relations Standards Page 50 of 81

Foodservice EDI Change Summary Version 4010 to 4010-2012

Data Element # and Name Codes 810 820 850 855 856 860 997

752 Surface/Layer/Position Code

RA- Relative Position 11 2/0500 PID06

752 Surface/Layer/Position Code

RB- Relative Position 12 2/0500 PID06

76 Invoice Number 1/20200 BIG02

770 Option Number 2/1800 SAC14 1/1200 SAC14 2/1300 SAC14 1/1200 SAC14 2/1300 SAC14

782 Monetary Amount 1/0200 BPR02 2/0800 ADX01 2/1500 RM04,

04, 05, 06 2/2100 ADX01

80 Lading Quantity 2/1100 TD102 Shipment

2/1100 TD102 Order

81 Weight 3/0600 ISS03 2/1100 TD107 Shipment

2/1100 TD107 Order

810 Inner Pack 2/1000 PO414 2/0900 PO414 2/0900 PO414 2/0600 PO414 Item

2/0900 PO414

812 Payment Format Code Yes

812 Payment Format Code PBC - Commerical / Corporate Check

1/0200 BPR05

819 Language Code 2/1800 SAC16 1/1200 SAC16 2/1300 SAC16

2/0500 PID09 '2/1300 SAC16

1/1200 SAC16 2/1300 SAC16

87 Marks and Numbers 2/1900 UNIt or Lot

2/1900 MAN02

Shipping Tare 2/1900

MAN02, 05 Pack

88 Marks and Numbers Yes

Page 108: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

GS1 Canada – Industry Relations Standards Page 51 of 81

Foodservice EDI Change Summary Version 4010 to 4010-2012

Data Element # and Name Codes 810 820 850 855 856 860 997

Qualifier 88 Marks and Numbers

Qualifier GM -SSCC-18 and Application Identifier

2/1900 MAN01 Unit or

Lot 2/1900 MAN01

Shipping Tare 2/1900

MAN01 , 04 Pack

88 Marks and Numbers Qualifier

UP- U.P.C. Consumer Package Code (1-5-5-1)

2/1900 MAN01, 04

Pack

883 Pallet Type Code Yes

883 Pallet Type Code 1 -Aluminum 2/2150 PAL01 Shipping Tare

883 Pallet Type Code 2-As Specified by the Department of Transportation (DOT)

2/2150 PAL01 Shipping Tare

883 Pallet Type Code 3- Metal 2/2150 PAL01 Shipping Tare

883 Pallet Type Code 4- Standard 2/2150 PAL01 Shipping Tare

883 Pallet Type Code 5- Steel 2/2150 PAL01 Shipping Tare

883 Pallet Type Code 6- Wood 2/2150 PAL01 Shipping Tare

883 Pallet Type Code 7- Slip sheet 2/2150 PAL01 Shipping Tare

884 Pallet Tiers 2/215 PAL02 Shipping Tare

885 Pallet Blocks 2/215 PAL03 Shipping Tare

91 Transportation Method/Type Code

Yes Yes Yes

Page 109: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

GS1 Canada – Industry Relations Standards Page 52 of 81

Foodservice EDI Change Summary Version 4010 to 4010-2012

Data Element # and Name Codes 810 820 850 855 856 860 997

91 Transportation Method/Type Code

H - Customer Pickup 1/2400 TD504 2/1200 TD504 Shipment

1/2400 TD504

91 Transportation Method/Type Code

L- Contract Carrier

91 Transportation Method/Type Code

M - Motor (Common Carrier)

1/2400 TD504 2/1200 TD504 Shipment

1/2400 TD504

91 Transportation Method/Type Code

R - Rail 2/1200 TD504 Shipment

92 Purchase Order Type Code Yes Yes

92 Purchase Order Type Code BE- Blanket Order/Estimated Quantities (Not firm Commitment)

1/0200 BEG02

92 Purchase Order Type Code BK - Blanket Order (Quantity Firm)

1/0200 BEG02 1/0200 BCH02

92 Purchase Order Type Code RE-Reorder 1/0200 BCH02

92 Purchase Order Type Code RL - Release or Delivery Order

1/0200 BCH02

92 Purchase Order Type Code SA - Stand-alone Order 1/0200 BEG02

92 Purchase Order Type Code ST - Standing Order 1/0200 BCH02

92 Purchase Order Type Code RL- Release or Delivery Order

1/0200 BEG02

93 Name 1/0600 PER02 1/0700 N102 1/080 N201,

02

1/0700 N102 1/0800 N201,

3

1/0600 PER02 1/3100 N102 1/3200 N201,

02

1/3000 N102 1/3100 N201,

02

1/1510 PER02 Shipment

2/2200 N102 Shipment

2/2300 N201, 02 Shipment 2/2200 N102

Order 2/2300 N201,

02 Order

1/0600 PER02 1/300 N102

1/3100 N201, 02

933 Free-Form Message Text 1/3000 MSG01 1/2900 MSG01

96 Number of Included Segments

3/0800 SE01 3/0100 SE01 3/0300 SE01 3/0300 SE01 3/0200 SE01 3/0300 SE01 1/0800 SE01

Page 110: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

GS1 Canada – Industry Relations Standards Page 53 of 81

Foodservice EDI Change Summary Version 4010 to 4010-2012

Data Element # and Name Codes 810 820 850 855 856 860 997

97 Number of Transaction Sets Included

1/0700 AK902

98 Entity Identifier Code Yes Yes Yes Yes Yes Yes

98 Entity Identifier Code BO- Broker or Sales Office

1/0700 N101 1/3100 N101 1/3000 N101 1/3000 N101

98 Entity Identifier Code BS- Bill and Ship To 1/0700 N101 1/3100 N101 1/3000 N101

98 Entity Identifier Code BT - Bill To Party 1/0700 N101 1/3100 N101 1/3000 N101 1/3000 N101

98 Entity Identifier Code BY - Buying Party 1/0400 CUR01 1/0400 CUR01 1/3100 N101

1/3000 N101 2/2200 N101 Order

1/0400 CUR01 1/3000 N101

98 Entity Identifier Code PR- Payer 1/0400 CUR01 1/0700 N101

98 Entity Identifier Code RI - Remit To 1/0700 N101

98 Entity Identifier Code SE - Selling Party 1/0400 CUR04

98 Entity Identifier Code SF - Ship From 1/0700 N101 1/3100 N101 1/3000 N101 2/2200 N101 Shipment

1/3000 N101

98 Entity Identifier Code ST - Ship To 1/0700 N101 1/3100 N101 1/3000 N101 2/2200 N101 Shipment

1/3000 N101

98 Entity Identifier Code SU - Supplier/Manufacturer

1/0700 N101 1/3100 N101 1/3000 N101 1/3000 N101

98 Entity Identifier Code VN - Vendor 1/0700 N101 1/3100 N101 1/3000 N101 1/3000 N101

C001 Composite Unit of Measure

2/0400 CTP05

2/0100 POC05

C030 Position in Segment

1/0500 AK401

Page 111: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

GS1 Canada – Industry Relations Standards Page 54 of 81

Foodservice EDI Change Summary Version 4010 to 4010-2012

Section 2A: Data Element 355 Unit or Basis for Measurement

NOTE: 820 Payment Order/Remittance Advice is not reflected below as no elements of this data element are required.

355 - Unit or Basis for Measurement 810 850 855 856 860 Weight Dimension

Ordering Unit

Volume Product

Size

Code Code Expression Position

BG BG Bag 2/0100 IT103 1/1200 SAC09 2/0100 PO103 2/0300 SN103 Pack

1/1200 SAC09 x

2/1000 PO403 2/0100 PO103 2/0400 CTP05 2/0300 SN103 Item

2/0100 POC05

2/1800 SAC09 2/0900 PO403 2/1300 SAC09 2/0900 PO403

3/0400 SAC09 2/1300 SAC09 2/2700 ACK03 2/1300 SAC09

3/0600 ISS02

BR BR Barrel 2/0100 IT103 1/1200 SAC09 2/0100 PO103 2/0300 SN103 Pack

1/1200 SAC09 x

2/1000 PO403 2/0100 PO103 2/0400 CTP05 2/0300 SN103 Item

2/0100 POC05

2/1800 SAC09 2/0900 PO403 2/1300 SAC09 2/0900 PO403

3/0400 SAC09 2/1300 SAC09 2/2700 ACK03 2/1300 SAC09

3/0600 ISS02

CA CA Case 2/0100 IT103 1/1200 SAC09 2/0100 PO103 2/0300 SN103 Pack

1/1200 SAC09 x

2/1000 PO403 2/0100 PO103 2/0400 CTP05-01

2/0300 SN103 Item

2/0100 POC05

2/1800 SAC09 2/0900 PO403 2/1300 SAC09 2/0900 PO403

3/0400 SAC09 2/1300 SAC09 2/2700 ACK03 2/1300 SAC09

3/0600 ISS02

CC CC Cubic Centimeter 2/0400 CTP05 2/1100 TD110 Shipment

x

2/0900 PO409

CF CF Cubic Feet 2/0400 CTP05 2/1100 TD110 Shipment

x

2/0900 PO409

CI CI Cubic Inches 2/0400 CTP05 2/1100 TD110 Shipment

x

2/0900 PO409

CR CR Cubic Meter 2/0400 CTP05 2/1100 TD110 x

Page 112: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

GS1 Canada – Industry Relations Standards Page 55 of 81

Foodservice EDI Change Summary Version 4010 to 4010-2012

355 - Unit or Basis for Measurement 810 850 855 856 860 Weight Dimension

Ordering Unit

Volume Product

Size

Code Code Expression Position

2/0900 PO409 Shipment

DB DB Dry Pounds 2/0400 CTP05 x

DR DR Drum 2/0100 IT103 1/1200 SAC09 2/0100 PO103 2/0300 SN103 Pack

1/1200 SAC09 x

2/1000 PO403 2/0100 PO103 2/0400 CTP05 2/0300 SN103 Item

2/0100 POC05

2/1800 SAC09 2/0900 PO403 2/1300 SAC09 2/0900 PO403

3/0400 SAC09 2/1300 SAC09 2/2700 ACK03 2/1300 SAC09

3/0600 ISS02

EA EA Each 2/0100 IT103 1/1200 SAC09 2/0100 PO103 2/0300 SN103 Pack

1/1200 SAC09 x

2/1000 PO403 2/0100 PO103 2/0400 CTP05 2/0300 SN103 Item

2/0100 POC05

2/1800 SAC09 2/0900 PO403 2/1300 SAC09 2/0900 PO403

3/0400 SAC09 2/1300 SAC09 2/2700 ACK03 2/1300 SAC09

3/0600 ISS02

FT FT Foot User Note 1: Feet

2/0400 CTP05 x

FZ FZ Fluid Ounce (Imperial)

2/0400 CTP05 x

GA GA Gallon 2/0100 IT103 1/1200 SAC09 2/0100 PO103 2/1100 TD110 Shipment

1/1200 SAC09 x x x

2/1000 PO403 2/0100 PO103 2/0400 CTP05 2/0300 SN103 Pack

2/0100 POC05

2/1800 SAC09 2/0900 PO403 2/0900 PO409 2/0300 SN103 Item

2/0900 PO403

3/0400 SAC09 2/1300 SAC09 2/1300 SAC09 2/1300 SAC09

3/0600 ISS02 2/2700 ACK03

GI GI Imperial Gallons 2/0400 CTP05 2/1100 TD110 Shipment

x x x

2/0900 PO409

GR GR Gram 2/0400 CTP05 2/1100 TD108 Order

x

Page 113: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

GS1 Canada – Industry Relations Standards Page 56 of 81

Foodservice EDI Change Summary Version 4010 to 4010-2012

355 - Unit or Basis for Measurement 810 850 855 856 860 Weight Dimension

Ordering Unit

Volume Product

Size

Code Code Expression Position

IN IN Inch 2/0400 CTP05 x

KG KG Kilogram 2/0100 IT103 1/1200 SAC09 2/0100 PO103 2/1100 TD108 Shipment

1/1200 SAC09 x

2/1000 PO403 2/0100 PO103 2/0400 CTP05 2/1100 TD108 Order

2/0100 POC05

2/1800 SAC09 2/0900 PO403 2/0900 PO407 2/0300 SN103 Pack

2/0900 PO403

3/0400 SAC09 2/1300 SAC09 2/1300 SAC09 2/0300 SN103 Item

2/1300 SAC09

3/0600 ISS02 2/2700 ACK03

3/0600 ISS04

LB LB Pound 2/0100 IT103 1/1200 SAC09 2/0100 PO103 2/1100 TD108 Shipment

1/1200 SAC09 x

2/1000 PO403 2/0100 PO103 2/0400 CTP05 2/0300 SN103 Pack

2/0100 POC05

2/1800 SAC09 2/0900 PO403 2/0900 PO407 2/0300 SN103 Item

2/0900 PO403

3/0400 SAC09 2/1300 SAC09 2/1300 SAC09 2/1300 SAC09

3/0600 ISS02 2/2700 ACK03

3/0600 ISS04

LT LT Liter 2/0100 IT103 1/1200 SAC09 2/0100 PO103 2/1100 TD110 Shipment

1/1200 SAC09 x x x

2/1000 PO403 2/0100 PO103 2/0400 CTP05 2/0300 SN103 Pack

2/0100 POC05

2/1800 SAC09 2/0900 PO403 2/0900 PO409 2/0300 SN103 Item

2/0900 PO403

3/0400 SAC09 2/1300 SAC09 2/1300 SAC09 2/1300 SAC09

3/0600 ISS02 2/2700 ACK03

ML ML Milliliter 2/0400 CTP05 2/1100 TD110 Shipment

x x x

2/0900 PO409

PA PA Pail 2/0100 IT103 1/1200 SAC09 2/0100 PO103 2/0300 SN103 Pack

1/1200 SAC09 x

Page 114: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

GS1 Canada – Industry Relations Standards Page 57 of 81

Foodservice EDI Change Summary Version 4010 to 4010-2012

355 - Unit or Basis for Measurement 810 850 855 856 860 Weight Dimension

Ordering Unit

Volume Product

Size

Code Code Expression Position

2/1000 PO403 2/0100 PO103 2/0400 CTP05 2/0300 SN103 Item

2/0100 POC05

2/1800 SAC09 2/0900 PO403 2/1300 SAC09 2/0900 PO403

3/0400 SAC09 2/1300 SAC09 2/2700 ACK03 2/1300 SAC09

3/0600 ISS02

PL PL Pallet/Unit Load 2/0100 IT103 1/1200 SAC09 2/0100 PO103 2/0300 SN103 Pack

1/1200 SAC09 x

2/1000 PO403 2/0100 PO103 2/0400 CTP05 2/0300 SN103 Item

2/0100 POC05

2/1800 SAC09 2/0900 PO403 2/1300 SAC09 2/0900 PO403

3/0400 SAC09 2/1300 SAC09 2/2700 ACK03 2/1300 SAC09

3/0600 ISS02

PT PT Pint 2/0400 CTP05 2/1100 TD110 Shipment

x x x

2/0400 CTP05

2/0900 PO409

PX PX Pint, Imperial 2/0900 PO409 2/1100 TD110 Shipment

x x x

TE TE Tote 2/0100 IT103 1/1200 SAC09 2/0100 PO103 2/0300 SN103 Pack

1/1200 SAC09 x

2/1000 PO403 2/0100 PO103 2/0400 CTP05 2/0300 SN103 Item

2/0100 POC05

2/1800 SAC09 2/0900 PO403 2/1300 SAC09 2/0900 PO403

3/0400 SAC09 2/1300 SAC09 2/2700 ACK03 2/1300 SAC09

3/0600 ISS02

YD YD Yard 2/0400 CTP05 x

Page 115: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

GS1 Canada – Industry Relations Standards Page 58 of 81

Foodservice EDI Change Summary Version 4010 to 4010-2012

Section 3: Data Element 1300 Service, Promotion, Allowance or Charge

The following two transactions sets can have additional codes available in DE 1300

• 850 Position 2/1300 SAC02 • 860 Positions 1/1200 and 2/1300 SAC02

DE 1300

Code Name

A010 Absolute Minimum Charge A020 Access Charge - Federal A030 Access Charge - State A040 Access Charges A050 Account Number Correction Charge A060 Acid (Battery) A070 Acknowledgment of Delivery Fee (AOD) A080 Activation of Carnet A090 Ad Valorem A100 Add on - Destination A110 Add on - Origin A112 Add to Make Market Value A120 Additional Copies of Freight Bill A121 Additional Commercial Invoices A122 Additional Tariff Classifications A130 Additional Material A140 Address Correction A150 Adjustment for Maximum Charges Billing A160 Adjustment for Minimum Average Time Requirement Billing A170 Adjustments A172 Administrative A180 Advance Charges Handling A190 Advance Destination Amount A200 Advance Destination Fee A210 Advance Fee A220 Advance Lading Charge A230 Advance Origin Amount A240 Advance Origin Fee A250 Advances A260 Advertising Allowance A270 Affidavit A280 Agent Disbursement - Destination A290 Agent Disbursement - Origin A300 Air Export Certificate A310 Air Express Charge A320 Air Transportation Charge A330 Aircraft On Ground (AOG) A340 Airline Opening Fee A350 Airport Terminal Handling Charge A360 Alcoholic Beverage Report Charge A370 Allegheny County, PA Delivery Charge

Page 116: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

810 InvoiceFoodservice EDI

Version: 4010-2012 FS Final

Author: Technical StandardsWork Group -Foodservice

Publication: 7/1/2012 Notes: For Implementation

December 2012

Page 117: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Invoice Foodservice - 810

July 2012 [V004010-2012 FS] iCopyright 2012 - GS1 Canada

Table of Contents

810 Invoice Foodservice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>ST Transaction Set Header . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>BIG Beginning Segment for Invoice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>CUR Currency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>REF Reference Identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>PER Administrative Communications Contact . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>N1 Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>N2 Additional Name Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>N3 Address Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>N4 Geographic Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>ITD Terms of Sale/Deferred Terms of Sale . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>DTM Date/Time Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>FOB F.O.B. Related Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>IT1 Baseline Item Data (Invoice) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>CTP Pricing Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>PID Product/Item Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>PO4 Item Physical Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>SAC Service, Promotion, Allowance, or Charge Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>TDS Total Monetary Value Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>SAC Service, Promotion, Allowance, or Charge Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>ISS Invoice Shipment Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>CTT Transaction Totals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>SE Transaction Set Trailer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>

. . . . . 1. . . . . 3. . . . . 4. . . . . 5. . . . . 6. . . . . 7. . . . . 9. . . . 11. . . . 12. . . . 13. . . . 14. . . . 16. . . . 17. . . . 18. . . . 20. . . . 21. . . . 23. . . . 25. . . . 30. . . . 31. . . . 36. . . . 38. . . . 39

Page 118: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Invoice Foodservice - 810

July 2012 [V004010-2012 FS] 1Copyright 2012 - GS1 Canada

810 Invoice FoodserviceFunctional Group=IN

Purpose: This Draft Standard for Trial Use contains the format and establishes the data contents of the InvoiceTransaction Set (810) for use within the context of an Electronic Data Interchange (EDI) environment. Thetransaction set can be used to provide for customary and established business and industry practice relative to thebilling for goods and services provided.

Heading:Pos Id Segment Name Req Max Use Repeat Notes Usage010 ST Transaction Set Header M 1 Must use020 BIG Beginning Segment for

InvoiceM 1 Must use

040 CUR Currency O 1 Used050 REF Reference Identification O 12 Used060 PER Administrative

Communications ContactO 3 Used

LOOP ID - N1 200 LOOP ID - N1 200

070 N1 Name O 1 Used080 N2 Additional Name

InformationO 2 Used

090 N3 Address Information O 2 Used100 N4 Geographic Location O 1 Used130 ITD Terms of Sale/Deferred

Terms of SaleO >1 Used

140 DTM Date/Time Reference O 10 Used150 FOB F.O.B. Related Instructions O 1 Used

Detail:Pos Id Segment Name Req Max Use Repeat Notes Usage

LOOP ID - IT1 200000 LOOP ID - IT1 200000

010 IT1 Baseline Item Data(Invoice)

O 1 Used

050 CTP Pricing Information O 25 Used LOOP ID - PID 1000 LOOP ID - PID 1000

060 PID Product/Item Description O 1 Used100 PO4 Item Physical Details O 1 Used

LOOP ID - SAC 25 LOOP ID - SAC 25

180 SAC Service, Promotion,Allowance, or ChargeInformation

O 1 Used

Summary:Pos Id Segment Name Req Max Use Repeat Notes Usage010 TDS Total Monetary Value

SummaryM 1 Must use

LOOP ID - SAC 25 LOOP ID - SAC 25

040 SAC Service, Promotion, O 1 Used

Page 119: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Invoice Foodservice - 810

Pos Id Segment Name Req Max Use Repeat Notes Usage

July 2012 [V004010-2012 FS] 2Copyright 2012 - GS1 Canada

Allowance, or ChargeInformation

LOOP ID - ISS >1 LOOP ID - ISS >1

060 ISS Invoice Shipment Summary O 1 Used070 CTT Transaction Totals O 1 N3/070 Used080 SE Transaction Set Trailer M 1 Must use

Notes: 3/070 Number of line items (CTT01) is the accumulation of the number of IT1 segments. If used, hash total

(CTT02) is the sum of the value of quantities invoiced (IT102) for each IT1 segment.

Page 120: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Invoice Foodservice - 810

July 2012 [V004010-2012 FS] 3Copyright 2012 - GS1 Canada

ST Transaction Set Header Pos: 010 Max: 1Heading - Mandatory

Loop: N/A Elements: 2

User Option (Usage): Must usePurpose: To indicate the start of a transaction set and to assign a control number

Element Summary: Ref Id Element Name Req Type Min/Max UsageST01 143 Transaction Set Identifier Code

Description: Code uniquely identifying aTransaction Set

M ID 3/3 Must use

CodeList Summary (Total Codes: 298, Included: 1)Code Name810 Invoice

ST02 329 Transaction Set Control Number

Description: Identifying control numberthat must be unique within the transactionset functional group assigned by theoriginator for a transaction setUser Note 1: The number is sequentiallyassigned by the sender, starting with onewithin each functional group. For eachfunctional group, the first transaction setcontrol number will be 0001 and incrementedby one for each additional transaction setwithin the group.

User Note 1: The number is sequentiallyassigned by the sender, starting with onewithin each functional group. For eachfunctional group, the first transaction setcontrol number will be 0001 and incrementedby one for each additional transaction setwithin the group.

M AN 4/9 Must use

Semantics: 1. The transaction set identifier (ST01) used by the translation routines of the interchange partners to select the

appropriate transaction set definition (e.g., 810 selects the Invoice Transaction Set).

Page 121: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Invoice Foodservice - 810

July 2012 [V004010-2012 FS] 4Copyright 2012 - GS1 Canada

BIG Beginning Segment forInvoice

Pos: 020 Max: 1Heading - Mandatory

Loop: N/A Elements: 4

User Option (Usage): Must usePurpose: To indicate the beginning of an invoice transaction set and transmit identifying numbers and dates

Element Summary: Ref Id Element Name Req Type Min/Max UsageBIG01 373 Date

Description: Date expressed asCCYYMMDD

M DT 8/8 Must use

BIG02 76 Invoice Number

Description: Identifying number assignedby issuer

M AN 1/22 Must use

BIG03 373 Date

Description: Date expressed asCCYYMMDDUser Note 1: Purchasing Organization'soriginal purchase order dateUser Note 1: Purchasing Organization'soriginal purchase order date

O DT 8/8 Used

BIG04 324 Purchase Order Number

Description: Identifying number forPurchase Order assigned by theorderer/purchaserUser Note 1: Purchasing Organization'soriginal purchase order numberUser Note 1: Purchasing Organization'soriginal purchase order number

O AN 1/22 Used

Semantics: 1. BIG01 is the invoice issue date.2. BIG03 is the date assigned by the purchaser to purchase order.3. BIG10 indicates the consolidated invoice number. When BIG07 contains code CI, BIG10 is not used.

Comments: 1. BIG07 is used only to further define the type of invoice when needed.

Page 122: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Invoice Foodservice - 810

July 2012 [V004010-2012 FS] 5Copyright 2012 - GS1 Canada

CUR Currency Pos: 040 Max: 1Heading - Optional

Loop: N/A Elements: 2

User Option (Usage): UsedPurpose: To specify the currency (dollars, pounds, francs, etc.) used in a transaction

Element Summary: Ref Id Element Name Req Type Min/Max UsageCUR01 98 Entity Identifier Code

Description: Code identifying anorganizational entity, a physical location,property or an individual

M ID 2/3 Must use

CodeList Summary (Total Codes: 1312, Included: 1)Code NameBY Buying Party (Purchaser)

CUR02 100 Currency Code

Description: Code (Standard ISO) forcountry in whose currency the chargesare specifiedUser Note 1: CAD CanadianUSD United StatesUser Note 1: CAD CanadianUSD United States

M ID 3/3 Must use

Syntax Rules: 1. C0807 - If CUR08 is present, then CUR07 is required.2. C0907 - If CUR09 is present, then CUR07 is required.3. L101112 - If CUR10 is present, then at least one of CUR11 or CUR12 is required.4. C1110 - If CUR11 is present, then CUR10 is required.5. C1210 - If CUR12 is present, then CUR10 is required.6. L131415 - If CUR13 is present, then at least one of CUR14 or CUR15 is required.7. C1413 - If CUR14 is present, then CUR13 is required.8. C1513 - If CUR15 is present, then CUR13 is required.9. L161718 - If CUR16 is present, then at least one of CUR17 or CUR18 is required.

10. C1716 - If CUR17 is present, then CUR16 is required.11. C1816 - If CUR18 is present, then CUR16 is required.12. L192021 - If CUR19 is present, then at least one of CUR20 or CUR21 is required.13. C2019 - If CUR20 is present, then CUR19 is required.14. C2119 - If CUR21 is present, then CUR19 is required.

Comments: 1. See Figures Appendix for examples detailing the use of the CUR segment.

Page 123: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Invoice Foodservice - 810

July 2012 [V004010-2012 FS] 6Copyright 2012 - GS1 Canada

REF Reference Identification Pos: 050 Max: 12Heading - Optional

Loop: N/A Elements: 2

User Option (Usage): UsedPurpose: To specify identifying information

Element Summary: Ref Id Element Name Req Type Min/Max UsageREF01 128 Reference Identification Qualifier

Description: Code qualifying theReference Identification

M ID 2/3 Must use

CodeList Summary (Total Codes: 1503, Included: 3)Code NameDP Department NumberIA Internal Vendor Number

User Note 1:User Note 1:Identification number assigned to the Selling Organization, by the Purchasing Organizationfor use within the Purchasing Organization's systemIdentification number assigned to the Selling Organization, by the Purchasing Organizationfor use within the Purchasing Organization's system

IT Internal Customer NumberUser Note 1:User Note 1:

Identification number assigned to the Purchasing Organization, by the SellingOrganization, for use within the Selling Organization's systemIdentification number assigned to the Purchasing Organization, by the SellingOrganization, for use within the Selling Organization's system

REF02 127 Reference Identification

Description: Reference information asdefined for a particular Transaction Set oras specified by the ReferenceIdentification Qualifier

C AN 1/30 Must use

Syntax Rules: 1. R0203 - At least one of REF02 or REF03 is required.

Semantics: 1. REF04 contains data relating to the value cited in REF02.

Page 124: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Invoice Foodservice - 810

July 2012 [V004010-2012 FS] 7Copyright 2012 - GS1 Canada

PER AdministrativeCommunications Contact

Pos: 060 Max: 3Heading - Optional

Loop: N/A Elements: 6

User Option (Usage): UsedPurpose: To identify a person or office to whom administrative communications should be directed

Element Summary: Ref Id Element Name Req Type Min/Max UsagePER01 366 Contact Function Code

Description: Code identifying the majorduty or responsibility of the person orgroup named

M ID 2/2 Must use

CodeList Summary (Total Codes: 230, Included: 2)Code NameCR Customer Relations

User Note 1:User Note 1:Customer service representativeCustomer service representative

SR Sales Representative or Department

PER02 93 Name

Description: Free-form name

O AN 1/60 Used

PER03 365 Communication Number Qualifier

Description: Code identifying the type ofcommunication number

C ID 2/2 Used

CodeList Summary (Total Codes: 40, Included: 2)Code NameEM Electronic MailTE Telephone

PER04 364 Communication Number

Description: Complete communicationsnumber including country or area codewhen applicable

C AN 1/80 Used

PER05 365 Communication Number Qualifier

Description: Code identifying the type ofcommunication number

C ID 2/2 Used

CodeList Summary (Total Codes: 40, Included: 2)Code NameEM Electronic MailTE Telephone

PER06 364 Communication Number

Description: Complete communicationsnumber including country or area codewhen applicable

C AN 1/80 Used

Page 125: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Invoice Foodservice - 810

Ref Id Element Name Req Type Min/Max Usage

July 2012 [V004010-2012 FS] 8Copyright 2012 - GS1 Canada

Syntax Rules: 1. P0304 - If either PER03 or PER04 is present, then the other is required.2. P0506 - If either PER05 or PER06 is present, then the other is required.3. P0708 - If either PER07 or PER08 is present, then the other is required.

Page 126: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Invoice Foodservice - 810

July 2012 [V004010-2012 FS] 9Copyright 2012 - GS1 Canada

N1 Name Pos: 070 Max: 1Heading - Optional

Loop: N1 Elements: 4

User Option (Usage): UsedPurpose: To identify a party by type of organization, name, and code

Element Summary: Ref Id Element Name Req Type Min/Max UsageN101 98 Entity Identifier Code

Description: Code identifying anorganizational entity, a physical location,property or an individual

M ID 2/3 Must use

CodeList Summary (Total Codes: 1312, Included: 8)Code NameBO Broker or Sales Office

User Note 1:User Note 1:For a domestic purchase order, this is the manufacturer's sales office. For an importpurchase order this is the sales office that interacts with the manufacturer's/buyer's agent.For a domestic purchase order, this is the manufacturer's sales office. For an importpurchase order this is the sales office that interacts with the manufacturer's/buyer's agent.

BS Bill and Ship ToBT Bill-to-PartyRI Remit ToSF Ship FromST Ship ToSU Supplier/Manufacturer

User Note 1:User Note 1:Supplier may or may not be the manufacturerSupplier may or may not be the manufacturer

VN VendorUser Note 1:User Note 1:

Party supplying the products being maintainedParty supplying the products being maintained

N102 93 Name

Description: Free-form name

C AN 1/60 Used

N103 66 Identification Code Qualifier

Description: Code designating thesystem/method of code structure used forIdentification Code (67)

C ID 1/2 Used

CodeList Summary (Total Codes: 215, Included: 2)Code Name9 D-U-N-S+4, D-U-N-S Number with Four Character SuffixUL UCC/EAN Location Code

Description: Global Location Number (GLN) (Revised name) A globally unique 13 digit code used for the identification of any physical or legal locationthat needs to be uniquely identified for use in the supply chain. A GS1 identification key SEE CODE SOURCE 583

N104 67 Identification Code C AN 2/80 Used

Page 127: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Invoice Foodservice - 810

Ref Id Element Name Req Type Min/Max Usage

July 2012 [V004010-2012 FS] 10Copyright 2012 - GS1 Canada

Description: Code identifying a party orother code

Syntax Rules: 1. R0203 - At least one of N102 or N103 is required.2. P0304 - If either N103 or N104 is present, then the other is required.

Comments: 1. This segment, used alone, provides the most efficient method of providing organizational identification. To

obtain this efficiency the "ID Code" (N104) must provide a key to the table maintained by the transactionprocessing party.

2. N105 and N106 further define the type of entity in N101.

Page 128: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Invoice Foodservice - 810

July 2012 [V004010-2012 FS] 11Copyright 2012 - GS1 Canada

N2 Additional Name Information Pos: 080 Max: 2Heading - Optional

Loop: N1 Elements: 2

User Option (Usage): UsedPurpose: To specify additional names or those longer than 35 characters in length

Element Summary: Ref Id Element Name Req Type Min/Max UsageN201 93 Name

Description: Free-form name

M AN 1/60 Must use

N202 93 Name

Description: Free-form name

O AN 1/60 Used

Page 129: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Invoice Foodservice - 810

July 2012 [V004010-2012 FS] 12Copyright 2012 - GS1 Canada

N3 Address Information Pos: 090 Max: 2Heading - Optional

Loop: N1 Elements: 2

User Option (Usage): UsedPurpose: To specify the location of the named party

Element Summary: Ref Id Element Name Req Type Min/Max UsageN301 166 Address Information

Description: Address information

M AN 1/55 Must use

N302 166 Address Information

Description: Address information

O AN 1/55 Used

Page 130: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Invoice Foodservice - 810

July 2012 [V004010-2012 FS] 13Copyright 2012 - GS1 Canada

N4 Geographic Location Pos: 100 Max: 1Heading - Optional

Loop: N1 Elements: 4

User Option (Usage): UsedPurpose: To specify the geographic place of the named party

Element Summary: Ref Id Element Name Req Type Min/Max UsageN401 19 City Name

Description: Free-form text for city name

O AN 2/30 Used

N402 156 State or Province Code

Description: Code (StandardState/Province) as defined by appropriategovernment agency

O ID 2/2 Used

N403 116 Postal Code

Description: Code defining internationalpostal zone code excluding punctuationand blanks (zip code for United States)

O ID 3/15 Used

N404 26 Country Code

Description: Code identifying the countryUser Note 1: CA CanadaMX MexicoUS United States

User Note 1: CA CanadaMX MexicoUS United States

O ID 2/3 Used

Syntax Rules: 1. C0605 - If N406 is present, then N405 is required.

Comments: 1. A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location.2. N402 is required only if city name (N401) is in the U.S. or Canada.

Page 131: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Invoice Foodservice - 810

July 2012 [V004010-2012 FS] 14Copyright 2012 - GS1 Canada

ITD Terms of Sale/Deferred Termsof Sale

Pos: 130 Max: >1Heading - Optional

Loop: N/A Elements: 8

User Option (Usage): UsedPurpose: To specify terms of sale

Element Summary: Ref Id Element Name Req Type Min/Max UsageITD01 336 Terms Type Code

Description: Code identifying type ofpayment terms

O ID 2/2 Used

CodeList Summary (Total Codes: 65, Included: 4)Code Name05 Discount Not Applicable08 Basic Discount Offered09 Proximo14 Previously agreed upon

ITD02 333 Terms Basis Date Code

Description: Code identifying thebeginning of the terms period

O ID 1/2 Used

CodeList Summary (Total Codes: 17, Included: 4)Code Name2 Delivery Date3 Invoice Date4 Specified Date15 Receipt of Goods

ITD03 338 Terms Discount Percent

Description: Terms discount percentage,expressed as a percent, available to thepurchaser if an invoice is paid on orbefore the Terms Discount Due DateUser Note 1: The percent is sent with adecimal point only when needed, e.g., 10.5%is sent as ``10.5'', and 2% is sent as ``2''.

User Note 1: The percent is sent with adecimal point only when needed, e.g., 10.5%is sent as ``10.5'', and 2% is sent as ``2''.

O R 1/6 Used

ITD04 370 Terms Discount Due Date

Description: Date payment is due ifdiscount is to be earned expressed informat CCYYMMDD

C DT 8/8 Used

ITD05 351 Terms Discount Days Due

Description: Number of days in the termsdiscount period by which payment is dueif terms discount is earnedUser Note 1: The end of the term period isderived by adding this value to the beginningUser Note 1: The end of the term period isderived by adding this value to the beginning

C N0 1/3 Used

Page 132: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Invoice Foodservice - 810

Ref Id Element Name Req Type Min/Max Usage

July 2012 [V004010-2012 FS] 15Copyright 2012 - GS1 Canada

of the term period, as qualified by ITD02.of the term period, as qualified by ITD02.

ITD06 446 Terms Net Due Date

Description: Date when total invoiceamount becomes due expressed in formatCCYYMMDD

O DT 8/8 Used

ITD07 386 Terms Net Days

Description: Number of days until totalinvoice amount is due (discount notapplicable)User Note 1: The end of the term period isderived by adding this value to the beginningof the term period, as qualified by ITD02.

User Note 1: The end of the term period isderived by adding this value to the beginningof the term period, as qualified by ITD02.

O N0 1/3 Used

ITD08 362 Terms Discount Amount

Description: Total amount of termsdiscount

O N2 1/10 Used

Syntax Rules: 1. L03040513 - If ITD03 is present, then at least one of ITD04, ITD05 or ITD13 is required.2. L08040513 - If ITD08 is present, then at least one of ITD04, ITD05 or ITD13 is required.3. L091011 - If ITD09 is present, then at least one of ITD10 or ITD11 is required.

Semantics: 1. ITD15 is the percentage applied to a base amount used to determine a late payment charge.

Comments: 1. If the code in ITD01 is "04", then ITD07 or ITD09 is required and either ITD10 or ITD11 is required; if the code

in ITD01 is "05", then ITD06 or ITD07 is required.

Page 133: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Invoice Foodservice - 810

July 2012 [V004010-2012 FS] 16Copyright 2012 - GS1 Canada

DTM Date/Time Reference Pos: 140 Max: 10Heading - Optional

Loop: N/A Elements: 2

User Option (Usage): UsedPurpose: To specify pertinent dates and times

Element Summary: Ref Id Element Name Req Type Min/Max UsageDTM01 374 Date/Time Qualifier

Description: Code specifying type of dateor time, or both date and time

M ID 3/3 Must use

CodeList Summary (Total Codes: 1112, Included: 2)Code Name002 Delivery Requested011 Shipped

DTM02 373 Date

Description: Date expressed asCCYYMMDD

C DT 8/8 Must use

Syntax Rules: 1. R020305 - At least one of DTM02, DTM03 or DTM05 is required.2. C0403 - If DTM04 is present, then DTM03 is required.3. P0506 - If either DTM05 or DTM06 is present, then the other is required.

Page 134: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Invoice Foodservice - 810

July 2012 [V004010-2012 FS] 17Copyright 2012 - GS1 Canada

FOB F.O.B. Related Instructions Pos: 150 Max: 1Heading - Optional

Loop: N/A Elements: 3

User Option (Usage): UsedPurpose: To specify transportation instructions relating to shipment

Element Summary: Ref Id Element Name Req Type Min/Max UsageFOB01 146 Shipment Method of Payment

Description: Code identifying paymentterms for transportation charges

M ID 2/2 Must use

CodeList Summary (Total Codes: 28, Included: 3)Code NameCC CollectPB Customer Pick-up/BackhaulPP Prepaid (by Seller)

FOB02 309 Location Qualifier

Description: Code identifying type oflocation

C ID 1/2 Used

CodeList Summary (Total Codes: 172, Included: 2)Code NameDE Destination (Shipping)OR Origin (Shipping Point)

FOB03 352 Description

Description: A free-form description toclarify the related data elements and theircontentUser Note 1: Free-form name oftransportation responsibility locationUser Note 1: Free-form name oftransportation responsibility location

O AN 1/80 Used

Syntax Rules: 1. C0302 - If FOB03 is present, then FOB02 is required.2. C0405 - If FOB04 is present, then FOB05 is required.3. C0706 - If FOB07 is present, then FOB06 is required.4. C0809 - If FOB08 is present, then FOB09 is required.

Semantics: 1. FOB01 indicates which party will pay the carrier.2. FOB02 is the code specifying transportation responsibility location.3. FOB06 is the code specifying the title passage location.4. FOB08 is the code specifying the point at which the risk of loss transfers. This may be different than the

location specified in FOB02/FOB03 and FOB06/FOB07.

Page 135: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Invoice Foodservice - 810

July 2012 [V004010-2012 FS] 18Copyright 2012 - GS1 Canada

IT1 Baseline Item Data (Invoice) Pos: 010 Max: 1Detail - Optional

Loop: IT1 Elements: 5

User Option (Usage): UsedPurpose: To specify the basic and most frequently used line item data for the invoice and related transactions

Element Summary: Ref Id Element Name Req Type Min/Max UsageIT102 358 Quantity Invoiced

Description: Number of units invoiced(supplier units)

C R 1/10 Must use

IT103 355 Unit or Basis for Measurement Code

Description: Code specifying the units inwhich a value is being expressed, ormanner in which a measurement hasbeen taken

C ID 2/2 Must use

CodeList Summary (Total Codes: 794, Included: 12)Code NameBG BagBR BarrelCA CaseDR DrumEA EachGA GallonKG KilogramLB PoundLT LiterPA PailPL Pallet/Unit LoadTE Tote

IT104 212 Unit Price

Description: Price per unit of product,service, commodity, etc.User Note 1: The price is sent with adecimal point only when needed, e.g., $15.95would be sent as ``15.95'', and $29.00 wouldbe sent as ``29''.

To indicate free goods, use a single zero (0)with code NC as the value in IT105.

User Note 1: The price is sent with adecimal point only when needed, e.g., $15.95would be sent as ``15.95'', and $29.00 wouldbe sent as ``29''.

To indicate free goods, use a single zero (0)with code NC as the value in IT105.

C R 1/17 Must use

IT106 235 Product/Service ID Qualifier

Description: Code identifying thetype/source of the descriptive numberused in Product/Service ID (234)

C ID 2/2 Used

CodeList Summary (Total Codes: 477, Included: 1)

Page 136: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Invoice Foodservice - 810

July 2012 [V004010-2012 FS] 19Copyright 2012 - GS1 Canada

Code NameUK U.P.C./EAN Shipping Container Code (1-2-5-5-1)

Description: GTIN-14 A 14-digit GS1 Identification Key composed of an Indicator Digit, GS1 Company Prefix, ItemReference and Check Digit used to identify trade items SEE CODE SOURCE 41

IT107 234 Product/Service ID

Description: Identifying number for aproduct or service

C AN 1/48 Used

Syntax Rules: 1. P020304 - If either IT102, IT103 or IT104 are present, then the others are required.2. P0607 - If either IT106 or IT107 is present, then the other is required.3. P0809 - If either IT108 or IT109 is present, then the other is required.4. P1011 - If either IT110 or IT111 is present, then the other is required.5. P1213 - If either IT112 or IT113 is present, then the other is required.6. P1415 - If either IT114 or IT115 is present, then the other is required.7. P1617 - If either IT116 or IT117 is present, then the other is required.8. P1819 - If either IT118 or IT119 is present, then the other is required.9. P2021 - If either IT120 or IT121 is present, then the other is required.

10. P2223 - If either IT122 or IT123 is present, then the other is required.11. P2425 - If either IT124 or IT125 is present, then the other is required.

Semantics: 1. IT101 is the purchase order line item identification.

Comments: 1. Element 235/234 combinations should be interpreted to include products and/or services. See the Data

Dictionary for a complete list of IDs.2. IT106 through IT125 provide for ten different product/service IDs for each item. For example: Case, Color,

Drawing No., U.P.C. No., ISBN No., Model No., or SKU.

Page 137: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Invoice Foodservice - 810

July 2012 [V004010-2012 FS] 20Copyright 2012 - GS1 Canada

CTP Pricing Information Pos: 050 Max: 25Detail - Optional

Loop: IT1 Elements: 2

User Option (Usage): UsedPurpose: To specify pricing information

Element Summary: Ref Id Element Name Req Type Min/Max UsageCTP02 236 Price Identifier Code

Description: Code identifying pricingspecification

C ID 3/3 Must use

CodeList Summary (Total Codes: 164, Included: 1)Code NameUCP Unit cost price

User Note 1:User Note 1:Item list costItem list cost

CTP03 212 Unit Price

Description: Price per unit of product,service, commodity, etc.User Note 1: The price is sent with adecimal point only when needed, e.g., $15.95would be sent as ``15.95'', and $29.00 wouldbe sent as ``29''.

User Note 1: The price is sent with adecimal point only when needed, e.g., $15.95would be sent as ``15.95'', and $29.00 wouldbe sent as ``29''.

C R 1/17 Must use

Syntax Rules: 1. P0405 - If either CTP04 or CTP05 is present, then the other is required.2. C0607 - If CTP06 is present, then CTP07 is required.3. C0902 - If CTP09 is present, then CTP02 is required.4. C1002 - If CTP10 is present, then CTP02 is required.5. C1103 - If CTP11 is present, then CTP03 is required.

Semantics: 1. CTP07 is a multiplier factor to arrive at a final discounted price. A multiplier of .90 would be the factor if a 10%

discount is given.2. CTP08 is the rebate amount.

Comments: 1. See Figures Appendix for an example detailing the use of CTP03 and CTP04.2. See Figures Appendix for an example detailing the use of CTP03, CTP04 and CTP07.

Page 138: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Invoice Foodservice - 810

July 2012 [V004010-2012 FS] 21Copyright 2012 - GS1 Canada

PID Product/Item Description Pos: 060 Max: 1Detail - Optional

Loop: PID Elements: 3

User Option (Usage): UsedPurpose: To describe a product or process in coded or free-form format

Element Summary: Ref Id Element Name Req Type Min/Max UsagePID01 349 Item Description Type

Description: Code indicating the formatof a description

M ID 1/1 Must use

CodeList Summary (Total Codes: 3, Included: 1)Code NameF Free-form

User Note 1:User Note 1:The description will be found in PID05.The description will be found in PID05.

PID02 750 Product/Process Characteristic Code

Description: Code identifying the generalclass of a product or processcharacteristic

O ID 2/3 Used

CodeList Summary (Total Codes: 217, Included: 1)Code Name08 Product

PID05 352 Description

Description: A free-form description toclarify the related data elements and theircontent

C AN 1/80 Used

Syntax Rules: 1. C0403 - If PID04 is present, then PID03 is required.2. R0405 - At least one of PID04 or PID05 is required.3. C0703 - If PID07 is present, then PID03 is required.4. C0804 - If PID08 is present, then PID04 is required.5. C0905 - If PID09 is present, then PID05 is required.

Semantics: 1. Use PID03 to indicate the organization that publishes the code list being referred to.2. PID04 should be used for industry-specific product description codes.3. PID08 describes the physical characteristics of the product identified in PID04. A "Y" indicates that the

specified attribute applies to this item; an "N" indicates it does not apply. Any other value is indeterminate.4. PID09 is used to identify the language being used in PID05.

Comments: 1. If PID01 equals "F", then PID05 is used. If PID01 equals "S", then PID04 is used. If PID01 equals "X", then

both PID04 and PID05 are used.

Page 139: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Invoice Foodservice - 810

July 2012 [V004010-2012 FS] 22Copyright 2012 - GS1 Canada

2. Use PID06 when necessary to refer to the product surface or layer being described in the segment.3. PID07 specifies the individual code list of the agency specified in PID03.

Page 140: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Invoice Foodservice - 810

July 2012 [V004010-2012 FS] 23Copyright 2012 - GS1 Canada

PO4 Item Physical Details Pos: 100 Max: 1Detail - Optional

Loop: IT1 Elements: 4

User Option (Usage): UsedPurpose: To specify the physical qualities, packaging, weights, and dimensions relating to the item

Element Summary: Ref Id Element Name Req Type Min/Max UsagePO401 356 Pack

Description: The number of innercontainers, or number of eaches if thereare no inner containers, per outercontainer

O N0 1/6 Used

PO402 357 Size

Description: Size of supplier units inpack

C R 1/8 Used

PO403 355 Unit or Basis for Measurement Code

Description: Code specifying the units inwhich a value is being expressed, ormanner in which a measurement hasbeen taken

C ID 2/2 Used

CodeList Summary (Total Codes: 794, Included: 12)Code NameBG BagBR BarrelCA CaseDR DrumEA EachGA GallonKG KilogramLB PoundLT LiterPA PailPL Pallet/Unit LoadTE Tote

PO414 810 Inner Pack

Description: The number of eaches perinner container

O N0 1/6 Used

Syntax Rules: 1. P0203 - If either PO402 or PO403 is present, then the other is required.2. C0506 - If PO405 is present, then PO406 is required.3. P0607 - If either PO406 or PO407 is present, then the other is required.4. P0809 - If either PO408 or PO409 is present, then the other is required.5. C1013 - If PO410 is present, then PO413 is required.

Page 141: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Invoice Foodservice - 810

July 2012 [V004010-2012 FS] 24Copyright 2012 - GS1 Canada

6. C1113 - If PO411 is present, then PO413 is required.7. C1213 - If PO412 is present, then PO413 is required.8. L13101112 - If PO413 is present, then at least one of PO410, PO411 or PO412 is required.9. C1716 - If PO417 is present, then PO416 is required.

10. C1804 - If PO418 is present, then PO404 is required.

Semantics: 1. PO415 is used to indicate the relative layer of this package or range of packages within the layers of

packaging. Relative Position 1 (value R1) is the innermost package.2. PO416 is the package identifier or the beginning package identifier in a range of identifiers.3. PO417 is the ending package identifier in a range of identifiers.4. PO418 is the number of packages in this layer.

Comments: 1. PO403 - The "Unit or Basis for Measure Code" in this segment position is for purposes of defining the pack

(PO401) /size (PO402) measure which indicates the quantity in the inner pack unit. For example: If the cartoncontains 24 12-Ounce packages, it would be described as follows: Data element 356 = "24"; Data element357 = "12"; Data element 355 = "OZ".

2. PO413 defines the unit of measure for PO410, PO411, and PO412.

User Note 1:User Note 1:This segment is used to specify the packaging of the item in the case or carton. There may be two levels of packagingspecified. The first level is always specified by using PO401 (Pack). The first level may be actual items, e.g., consumer units,or it may be the number of smaller containers within the case. The second level, specified using PO414 (Inner Pack), is thenumber of eaches in each inner container when PO401 is the number of smaller containers within the case.

This segment can be used also to specify the weight and/or volume (cube) for the item by using PO406 and PO407, and/orPO408 and PO409.

This segment is used to specify the packaging of the item in the case or carton. There may be two levels of packagingspecified. The first level is always specified by using PO401 (Pack). The first level may be actual items, e.g., consumer units,or it may be the number of smaller containers within the case. The second level, specified using PO414 (Inner Pack), is thenumber of eaches in each inner container when PO401 is the number of smaller containers within the case.

This segment can be used also to specify the weight and/or volume (cube) for the item by using PO406 and PO407, and/orPO408 and PO409.

Page 142: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Invoice Foodservice - 810

July 2012 [V004010-2012 FS] 25Copyright 2012 - GS1 Canada

SAC Service, Promotion,Allowance, or ChargeInformation

Pos: 180 Max: 1Detail - Optional

Loop: SAC Elements: 15

User Option (Usage): UsedPurpose: To request or identify a service, promotion, allowance, or charge; to specify the amount or percentage forthe service, promotion, allowance, or charge

Element Summary: Ref Id Element Name Req Type Min/Max UsageSAC01 248 Allowance or Charge Indicator

Description: Code which indicates anallowance or charge for the servicespecified

M ID 1/1 Must use

CodeList Summary (Total Codes: 7, Included: 4)Code NameA AllowanceC ChargeN No Allowance or ChargeR Allowance Request

SAC02 1300 Service, Promotion, Allowance, orCharge Code

Description: Code identifying the service,promotion, allowance, or chargeUser Note 1: See FoodserviceImplementation Guidelines Appendix - DataElements

User Note 1: See FoodserviceImplementation Guidelines Appendix - DataElements

C ID 4/4 Used

CodeList Summary (Total Codes: 1053, Included: 5)Code NameD350 Goods and Services Credit AllowanceD360 Goods and Services Tax Charge

User Note 1:User Note 1:Provincal Tobacco Tax.Provincal Tobacco Tax.

H490 Subject To Tax On ResaleH770 Tax - State TaxH806 Tax Credit

User Note 1:User Note 1:Provincial Tax Credit.Provincial Tax Credit.

SAC03 559 Agency Qualifier Code

Description: Code identifying the agencyassigning the code values

C ID 2/2 Used

CodeList Summary (Total Codes: 176, Included: 1)

Page 143: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Invoice Foodservice - 810

July 2012 [V004010-2012 FS] 26Copyright 2012 - GS1 Canada

Code NameVI Voluntary Inter-Industry Commerce Standard (VICS) EDI

SAC04 1301 Agency Service, Promotion, Allowance,or Charge Code

Description: Agency maintained codeidentifying the service, promotion,allowance, or chargeUser Note 1: See FoodserviceImplementation Guidelines Appendix - DataElements

User Note 1: See FoodserviceImplementation Guidelines Appendix - DataElements

C AN 1/10 Used

SAC05 610 Amount

Description: Monetary amountUser Note 1: When SAC01 contains code Aor code C, then this data element is required.This will resolve any differences between thesender's and receiver's system calculations ofamounts, i.e., rounding errors whenallowances or charges are expressed inpercentages or rates.

User Note 1: When SAC01 contains code Aor code C, then this data element is required.This will resolve any differences between thesender's and receiver's system calculations ofamounts, i.e., rounding errors whenallowances or charges are expressed inpercentages or rates.

O N2 1/15 Used

SAC06 378 Allowance/Charge Percent Qualifier

Description: Code indicating on whatbasis allowance or charge percent iscalculated

C ID 1/1 Used

CodeList Summary (Total Codes: 11, Included: 7)Code Name1 Item List Cost2 Item Net Cost3 Discount/Gross

User Note 1:User Note 1:All allowances are off the gross price including cash discount.All allowances are off the gross price including cash discount.

4 Discount/NetUser Note 1:User Note 1:

All allowances are off the gross price. Cash discounts are off the net.All allowances are off the gross price. Cash discounts are off the net.

5 Base Price per UnitUser Note 1:User Note 1:

Line item discountLine item discount

6 Base Price Amount7 Base Price Amount Less Previous Discount

User Note 1:User Note 1:Declining balance methodDeclining balance method

SAC07 332 Percent

Description: Percent expressed as apercentUser Note 1: The percent is sent with adecimal point only when needed, e.g., 10.5%is sent as ``10.5'', and 2% is sent as ``2''.

User Note 1: The percent is sent with adecimal point only when needed, e.g., 10.5%is sent as ``10.5'', and 2% is sent as ``2''.

C R 1/6 Used

Page 144: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Invoice Foodservice - 810

Ref Id Element Name Req Type Min/Max Usage

July 2012 [V004010-2012 FS] 27Copyright 2012 - GS1 Canada

SAC08 118 Rate

Description: Rate expressed in thestandard monetary denomination for thecurrency specified

O R 1/9 Used

SAC09 355 Unit or Basis for Measurement Code

Description: Code specifying the units inwhich a value is being expressed, ormanner in which a measurement hasbeen taken

C ID 2/2 Used

CodeList Summary (Total Codes: 794, Included: 12)Code NameBG BagBR BarrelCA CaseDR DrumEA EachGA GallonKG KilogramLB PoundLT LiterPA PailPL Pallet/Unit LoadTE Tote

SAC10 380 Quantity

Description: Numeric value of quantity

C R 1/15 Used

SAC12 331 Allowance or Charge Method ofHandling Code

Description: Code indicating method ofhandling for an allowance or charge

O ID 2/2 Used

CodeList Summary (Total Codes: 22, Included: 6)Code Name01 Bill Back

User Note 1:User Note 1:The allowance or charge amount will be adjudicated as a separate item, i.e., a debit/creditmemo or a separate invoice. The amount will not be reflected in the invoice total amount.The allowance or charge amount will be adjudicated as a separate item, i.e., a debit/creditmemo or a separate invoice. The amount will not be reflected in the invoice total amount.

02 Off InvoiceUser Note 1:User Note 1:

The allowance or charge amount will be reflected in the total transaction amount, e.g.,Total Invoice Amount = Merchandise Price + Charges - Allowances.The allowance or charge amount will be reflected in the total transaction amount, e.g.,Total Invoice Amount = Merchandise Price + Charges - Allowances.

03 Vendor Check to CustomerUser Note 1:User Note 1:

The vendor will issue a check directly to the customer of the retailer, or end consumer, forthe allowance or charge amount. The amount is not reflected in the total invoice amount.The vendor will issue a check directly to the customer of the retailer, or end consumer, forthe allowance or charge amount. The amount is not reflected in the total invoice amount.

04 Credit Customer Account

Page 145: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Invoice Foodservice - 810

Code Name

July 2012 [V004010-2012 FS] 28Copyright 2012 - GS1 Canada

User Note 1:User Note 1:The retailer's account will be credited for the amount of the allowance or charge. Theamount is not reflected in the total invoice amount.The retailer's account will be credited for the amount of the allowance or charge. Theamount is not reflected in the total invoice amount.

05 Charge to be Paid by VendorUser Note 1:User Note 1:

The vendor is responsible for the allowance or charge amount. The exact method ofadjudication has been agreed to by the trading partners. The amount will not be reflectedin the total invoice amount.

The vendor is responsible for the allowance or charge amount. The exact method ofadjudication has been agreed to by the trading partners. The amount will not be reflectedin the total invoice amount.

06 Charge to be Paid by CustomerUser Note 1:User Note 1:

When the order/item is a direct ship to the customer, or end consumer of the retailer, theallowance or charge amount is the responsibility of the customer or end consumer. If it isnot a drop ship to the customer of the retailer, then the allowance or charge amount is theresponsibility of the retailer. The exact method of adjudication has been agreed to by thetrading partners. The amount will not be reflected in the total invoice amou

When the order/item is a direct ship to the customer, or end consumer of the retailer, theallowance or charge amount is the responsibility of the customer or end consumer. If it isnot a drop ship to the customer of the retailer, then the allowance or charge amount is theresponsibility of the retailer. The exact method of adjudication has been agreed to by thetrading partners. The amount will not be reflected in the total invoice amou

SAC13 127 Reference Identification

Description: Reference information asdefined for a particular Transaction Set oras specified by the ReferenceIdentification QualifierUser Note 1: Used for tax registrationnumber.User Note 1: Used for tax registrationnumber.

C AN 1/30 Used

SAC14 770 Option Number

Description: A unique number identifyingavailable promotion or allowance optionswhen more than one is offered

O AN 1/20 Used

SAC15 352 Description

Description: A free-form description toclarify the related data elements and theircontent

C AN 1/80 Used

SAC16 819 Language Code

Description: Code designating thelanguage used in text, from a standardcode list maintained by the InternationalStandards Organization (ISO 639)

O ID 2/3 Used

Syntax Rules: 1. R0203 - At least one of SAC02 or SAC03 is required.2. P0304 - If either SAC03 or SAC04 is present, then the other is required.3. P0607 - If either SAC06 or SAC07 is present, then the other is required.4. P0910 - If either SAC09 or SAC10 is present, then the other is required.5. C1110 - If SAC11 is present, then SAC10 is required.6. L130204 - If SAC13 is present, then at least one of SAC02 or SAC04 is required.7. C1413 - If SAC14 is present, then SAC13 is required.8. C1615 - If SAC16 is present, then SAC15 is required.

Semantics:

Page 146: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Invoice Foodservice - 810

July 2012 [V004010-2012 FS] 29Copyright 2012 - GS1 Canada

1. If SAC01 is "A" or "C", then at least one of SAC05, SAC07, or SAC08 is required.2. SAC05 is the total amount for the service, promotion, allowance, or charge.3. If SAC05 is present with SAC07 or SAC08, then SAC05 takes precedence.4. SAC08 is the allowance or charge rate per unit. 5. SAC10 and SAC11 is the quantity basis when the allowance or charge quantity is different from the purchase

order or invoice quantity.6. SAC10 and SAC11 used together indicate a quantity range, which could be a dollar amount, that is applicable

to service, promotion, allowance, or charge.7. SAC13 is used in conjunction with SAC02 or SAC04 to provide a specific reference number as identified by

the code used.8. SAC14 is used in conjunction with SAC13 to identify an option when there is more than one option of the

promotion.9. SAC16 is used to identify the language being used in SAC15.

Comments: 1. SAC04 may be used to uniquely identify the service, promotion, allowance, or charge. In addition, it may be

used in conjunction to further the code in SAC02.2. In some business applications, it is necessary to advise the trading partner of the actual dollar amount that a

particular allowance, charge, or promotion was based on to reduce ambiguity. This amount is commonlyreferred to as "Dollar Basis Amount". It is represented in the SAC segment in SAC10 using the qualifier "DO" -Dollars in SAC09.

Page 147: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Invoice Foodservice - 810

July 2012 [V004010-2012 FS] 30Copyright 2012 - GS1 Canada

TDS Total Monetary ValueSummary

Pos: 010 Max: 1Summary - Mandatory

Loop: N/A Elements: 4

User Option (Usage): Must usePurpose: To specify the total invoice discounts and amounts

Element Summary: Ref Id Element Name Req Type Min/Max UsageTDS01 610 Amount

Description: Monetary amount

M N2 1/15 Must use

TDS02 610 Amount

Description: Monetary amount

O N2 1/15 Used

TDS03 610 Amount

Description: Monetary amount

O N2 1/15 Used

TDS04 610 Amount

Description: Monetary amount

O N2 1/15 Used

Semantics: 1. TDS01 is the total amount of invoice (including charges, less allowances) before terms discount (if discount is

applicable).2. TDS02 indicates the amount upon which the terms discount amount is calculated.3. TDS03 is the amount of invoice due if paid by terms discount due date (total invoice or installment amount

less cash discount). 4. TDS04 indicates the total amount of terms discount.

Comments: 1. TDS02 is required if the dollar value subject to discount is not equal to the dollar value of TDS01.

Page 148: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Invoice Foodservice - 810

July 2012 [V004010-2012 FS] 31Copyright 2012 - GS1 Canada

SAC Service, Promotion,Allowance, or ChargeInformation

Pos: 040 Max: 1Summary - Optional

Loop: SAC Elements: 15

User Option (Usage): UsedPurpose: To request or identify a service, promotion, allowance, or charge; to specify the amount or percentage forthe service, promotion, allowance, or charge

Element Summary: Ref Id Element Name Req Type Min/Max UsageSAC01 248 Allowance or Charge Indicator

Description: Code which indicates anallowance or charge for the servicespecified

M ID 1/1 Must use

CodeList Summary (Total Codes: 7, Included: 4)Code NameA AllowanceC ChargeN No Allowance or ChargeR Allowance Request

SAC02 1300 Service, Promotion, Allowance, orCharge Code

Description: Code identifying the service,promotion, allowance, or chargeUser Note 1: See FoodserviceImplementation Guidelines Appendix - DataElements

User Note 1: See FoodserviceImplementation Guidelines Appendix - DataElements

C ID 4/4 Used

CodeList Summary (Total Codes: 1053, Included: 5)Code NameD350 Goods and Services Credit AllowanceD360 Goods and Services Tax Charge

User Note 1:User Note 1:Provincal Tobacco Tax.Provincal Tobacco Tax.

H490 Subject To Tax On ResaleH770 Tax - State TaxH806 Tax Credit

User Note 1:User Note 1:Provincial Tax Credit.Provincial Tax Credit.

SAC03 559 Agency Qualifier Code

Description: Code identifying the agencyassigning the code values

C ID 2/2 Used

CodeList Summary (Total Codes: 176, Included: 1)

Page 149: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Invoice Foodservice - 810

July 2012 [V004010-2012 FS] 32Copyright 2012 - GS1 Canada

Code NameVI Voluntary Inter-Industry Commerce Standard (VICS) EDI

SAC04 1301 Agency Service, Promotion, Allowance,or Charge Code

Description: Agency maintained codeidentifying the service, promotion,allowance, or charge

C AN 1/10 Used

SAC05 610 Amount

Description: Monetary amountUser Note 1: When SAC01 contains code Aor code C, then this data element is required.This will resolve any differences between thesender's and receiver's system calculations ofamounts, i.e., rounding errors whenallowances or charges are expressed inpercentages or rates.

User Note 1: When SAC01 contains code Aor code C, then this data element is required.This will resolve any differences between thesender's and receiver's system calculations ofamounts, i.e., rounding errors whenallowances or charges are expressed inpercentages or rates.

O N2 1/15 Used

SAC06 378 Allowance/Charge Percent Qualifier

Description: Code indicating on whatbasis allowance or charge percent iscalculated

C ID 1/1 Used

CodeList Summary (Total Codes: 11, Included: 6)Code Name1 Item List Cost2 Item Net Cost3 Discount/Gross

User Note 1:User Note 1:All allowances are off the gross price including cash discount.All allowances are off the gross price including cash discount.

4 Discount/NetUser Note 1:User Note 1:

All allowances are off the gross price. Cash discounts are off the net.All allowances are off the gross price. Cash discounts are off the net.

5 Base Price per UnitUser Note 1:User Note 1:

Line item discountLine item discount

7 Base Price Amount Less Previous DiscountUser Note 1:User Note 1:

Declining balance methodDeclining balance method

SAC07 332 Percent

Description: Percent expressed as apercentUser Note 1: The percent is sent with adecimal point only when needed, e.g., 10.5%is sent as ``10.5'', and 2% is sent as ``2''.

User Note 1: The percent is sent with adecimal point only when needed, e.g., 10.5%is sent as ``10.5'', and 2% is sent as ``2''.

C R 1/6 Used

SAC08 118 Rate

Description: Rate expressed in thestandard monetary denomination for the

O R 1/9 Used

Page 150: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Invoice Foodservice - 810

Ref Id Element Name Req Type Min/Max Usage

July 2012 [V004010-2012 FS] 33Copyright 2012 - GS1 Canada

currency specified

SAC09 355 Unit or Basis for Measurement Code

Description: Code specifying the units inwhich a value is being expressed, ormanner in which a measurement hasbeen taken

C ID 2/2 Used

CodeList Summary (Total Codes: 794, Included: 12)Code NameBG BagBR BarrelCA CaseDR DrumEA EachGA GallonKG KilogramLB PoundLT LiterPA PailPL Pallet/Unit LoadTE Tote

SAC10 380 Quantity

Description: Numeric value of quantity

C R 1/15 Used

SAC12 331 Allowance or Charge Method ofHandling Code

Description: Code indicating method ofhandling for an allowance or charge

O ID 2/2 Used

CodeList Summary (Total Codes: 22, Included: 6)Code Name01 Bill Back

User Note 1:User Note 1:The allowance or charge amount will be adjudicated as a separate item, i.e., a debit/creditmemo or a separate invoice. The amount will not be reflected in the invoice total amount.The allowance or charge amount will be adjudicated as a separate item, i.e., a debit/creditmemo or a separate invoice. The amount will not be reflected in the invoice total amount.

02 Off InvoiceUser Note 1:User Note 1:

The allowance or charge amount will be reflected in the total transaction amount, e.g.,Total Invoice Amount = Merchandise Price + Charges - Allowances.The allowance or charge amount will be reflected in the total transaction amount, e.g.,Total Invoice Amount = Merchandise Price + Charges - Allowances.

03 Vendor Check to CustomerUser Note 1:User Note 1:

The vendor will issue a check directly to the customer of the retailer, or end consumer, forthe allowance or charge amount. The amount is not reflected in the total invoice amount.The vendor will issue a check directly to the customer of the retailer, or end consumer, forthe allowance or charge amount. The amount is not reflected in the total invoice amount.

04 Credit Customer AccountUser Note 1:User Note 1:

The retailer's account will be credited for the amount of the allowance or charge. Theamount is not reflected in the total invoice amount.The retailer's account will be credited for the amount of the allowance or charge. Theamount is not reflected in the total invoice amount.

Page 151: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Invoice Foodservice - 810

Code Name

July 2012 [V004010-2012 FS] 34Copyright 2012 - GS1 Canada

05 Charge to be Paid by VendorUser Note 1:User Note 1:

The vendor is responsible for the allowance or charge amount. The exact method ofadjudication has been agreed to by the trading partners. The amount will not be reflectedin the total invoice amount.

The vendor is responsible for the allowance or charge amount. The exact method ofadjudication has been agreed to by the trading partners. The amount will not be reflectedin the total invoice amount.

06 Charge to be Paid by CustomerUser Note 1:User Note 1:

When the order/item is a direct ship to the customer, or end consumer of the retailer, theallowance or charge amount is the responsibility of the customer or end consumer. If it isnot a drop ship to the customer of the retailer, then the allowance or charge amount is theresponsibility of the retailer. The exact method of adjudication has been agreed to by thetrading partners. The amount will not be reflected in the total invoice amou

When the order/item is a direct ship to the customer, or end consumer of the retailer, theallowance or charge amount is the responsibility of the customer or end consumer. If it isnot a drop ship to the customer of the retailer, then the allowance or charge amount is theresponsibility of the retailer. The exact method of adjudication has been agreed to by thetrading partners. The amount will not be reflected in the total invoice amou

SAC13 127 Reference Identification

Description: Reference information asdefined for a particular Transaction Set oras specified by the ReferenceIdentification QualifierUser Note 1: Used for tax registration.User Note 1: Used for tax registration.

C AN 1/30 Used

SAC14 770 Option Number

Description: A unique number identifyingavailable promotion or allowance optionswhen more than one is offered

O AN 1/20 Used

SAC15 352 Description

Description: A free-form description toclarify the related data elements and theircontent

C AN 1/80 Used

SAC16 819 Language Code

Description: Code designating thelanguage used in text, from a standardcode list maintained by the InternationalStandards Organization (ISO 639)

O ID 2/3 Used

Syntax Rules: 1. R0203 - At least one of SAC02 or SAC03 is required.2. P0304 - If either SAC03 or SAC04 is present, then the other is required.3. P0607 - If either SAC06 or SAC07 is present, then the other is required.4. P0910 - If either SAC09 or SAC10 is present, then the other is required.5. C1110 - If SAC11 is present, then SAC10 is required.6. L130204 - If SAC13 is present, then at least one of SAC02 or SAC04 is required.7. C1413 - If SAC14 is present, then SAC13 is required.8. C1615 - If SAC16 is present, then SAC15 is required.

Semantics: 1. If SAC01 is "A" or "C", then at least one of SAC05, SAC07, or SAC08 is required.2. SAC05 is the total amount for the service, promotion, allowance, or charge.3. If SAC05 is present with SAC07 or SAC08, then SAC05 takes precedence.

Page 152: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Invoice Foodservice - 810

July 2012 [V004010-2012 FS] 35Copyright 2012 - GS1 Canada

4. SAC08 is the allowance or charge rate per unit. 5. SAC10 and SAC11 is the quantity basis when the allowance or charge quantity is different from the purchase

order or invoice quantity.6. SAC10 and SAC11 used together indicate a quantity range, which could be a dollar amount, that is applicable

to service, promotion, allowance, or charge.7. SAC13 is used in conjunction with SAC02 or SAC04 to provide a specific reference number as identified by

the code used.8. SAC14 is used in conjunction with SAC13 to identify an option when there is more than one option of the

promotion.9. SAC16 is used to identify the language being used in SAC15.

Comments: 1. SAC04 may be used to uniquely identify the service, promotion, allowance, or charge. In addition, it may be

used in conjunction to further the code in SAC02.2. In some business applications, it is necessary to advise the trading partner of the actual dollar amount that a

particular allowance, charge, or promotion was based on to reduce ambiguity. This amount is commonlyreferred to as "Dollar Basis Amount". It is represented in the SAC segment in SAC10 using the qualifier "DO" -Dollars in SAC09.

Page 153: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Invoice Foodservice - 810

July 2012 [V004010-2012 FS] 36Copyright 2012 - GS1 Canada

ISS Invoice Shipment Summary Pos: 060 Max: 1Summary - Optional

Loop: ISS Elements: 4

User Option (Usage): UsedPurpose: To specify summary details of total items shipped in terms of quantity, weight, and volume

Element Summary: Ref Id Element Name Req Type Min/Max UsageISS01 382 Number of Units Shipped

Description: Numeric value of unitsshipped in manufacturer's shipping unitsfor a line item or transaction set

C R 1/10 Used

ISS02 355 Unit or Basis for Measurement Code

Description: Code specifying the units inwhich a value is being expressed, ormanner in which a measurement hasbeen taken

C ID 2/2 Used

CodeList Summary (Total Codes: 794, Included: 12)Code NameBG BagBR BarrelCA CaseDR DrumEA EachGA GallonKG KilogramLB PoundLT LiterPA PailPL Pallet/Unit LoadTE Tote

ISS03 81 Weight

Description: Numeric value of weight

C R 1/10 Used

ISS04 355 Unit or Basis for Measurement Code

Description: Code specifying the units inwhich a value is being expressed, ormanner in which a measurement hasbeen takenUser Note 1: See Section III for code list.User Note 1: See Section III for code list.

C ID 2/2 Used

CodeList Summary (Total Codes: 794, Included: 2)Code NameKG KilogramLB Pound

Syntax Rules:

Page 154: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Invoice Foodservice - 810

July 2012 [V004010-2012 FS] 37Copyright 2012 - GS1 Canada

1. R010305 - At least one of ISS01, ISS03 or ISS05 is required.2. P0102 - If either ISS01 or ISS02 is present, then the other is required.3. P0304 - If either ISS03 or ISS04 is present, then the other is required.4. P0506 - If either ISS05 or ISS06 is present, then the other is required.

Semantics: 1. ISS07 is the quantity of third party pallets.2. ISS08 is the gross weight of third party pallets in pounds.

Page 155: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Invoice Foodservice - 810

July 2012 [V004010-2012 FS] 38Copyright 2012 - GS1 Canada

CTT Transaction Totals Pos: 070 Max: 1Summary - Optional

Loop: N/A Elements: 1

User Option (Usage): UsedPurpose: To transmit a hash total for a specific element in the transaction set

Element Summary: Ref Id Element Name Req Type Min/Max UsageCTT01 354 Number of Line Items

Description: Total number of line items inthe transaction setUser Note 1: The number of IT1 segmentspresent in the transaction setUser Note 1: The number of IT1 segmentspresent in the transaction set

M N0 1/6 Must use

Syntax Rules: 1. P0304 - If either CTT03 or CTT04 is present, then the other is required.2. P0506 - If either CTT05 or CTT06 is present, then the other is required.

Comments: 1. This segment is intended to provide hash totals to validate transaction completeness and correctness.

Page 156: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Invoice Foodservice - 810

July 2012 [V004010-2012 FS] 39Copyright 2012 - GS1 Canada

SE Transaction Set Trailer Pos: 080 Max: 1Summary - Mandatory

Loop: N/A Elements: 2

User Option (Usage): Must usePurpose: To indicate the end of the transaction set and provide the count of the transmitted segments (including thebeginning (ST) and ending (SE) segments)

Element Summary: Ref Id Element Name Req Type Min/Max UsageSE01 96 Number of Included Segments

Description: Total number of segmentsincluded in a transaction set including STand SE segments

M N0 1/10 Must use

SE02 329 Transaction Set Control Number

Description: Identifying control numberthat must be unique within the transactionset functional group assigned by theoriginator for a transaction setUser Note 1: This must be the same numberas is in the ST segment (ST02) for thetransaction set.

User Note 1: This must be the same numberas is in the ST segment (ST02) for thetransaction set.

M AN 4/9 Must use

Comments: 1. SE is the last segment of each transaction set.

Page 157: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

GS1 Canada – Industry Relations Standards Page 59 of 81

Foodservice EDI Change Summary Version 4010 to 4010-2012

DE 1300 Code

Name

A380 Allowance Advance A390 Allowance for Consignment Merchandise A400 Allowance Non-performance A410 "Alterations" A420 Amending Export Documentation A430 Anneal/Heat (Steel or Glass Treatment) A440 Anodizing Charge A445 Anti-dumping Duty A450 Appointment (Notification) A460 Arbitrary (In Addition to Through Rates and Charges) A470 Art Work A480 Assembly A485 Assist Amount A490 Attachments to Bill of Lading Charge A500 Bad Debt A510 Banking Drafts A520 Base Charge A530 Basic Reorder Allowance A540 Beaming Charge A550 Bedding/Feeding/Disinfecting A555 Beef Fee A560 Beyond Charge A570 Beyond Freight Charges A580 Bill and Hold A590 Bill of Lading Attendancy A600 Bill of Lading Charge A610 Billed Demand A620 Black Lung Tax A630 Blocking and Bracing Charge A640 Blower Charge A650 Bobtail Charges A658 Bond Amount A660 Bond Charge A670 Bordeaux Arbitraries A680 Both-Flat A690 Break Bulk Surface Charge A691 Breakbulk Services A700 Bridge Toll A710 Broken Lot A720 Broken Package Charge A721 Brokerage A730 Brokerage or Duty A740 Bunker Surcharge A750 Burning A760 Buyer Hand Carry A770 Buyers Car Allowance A780 Cable Pressurization

Page 158: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

GS1 Canada – Industry Relations Standards Page 60 of 81

Foodservice EDI Change Summary Version 4010 to 4010-2012

DE 1300 Code

Name

A790 Cables (sending of) A800 Call Tag A810 Camp Arbitrary A820 Canada Great Lakes Additionals A830 Canadian C.Q.Customs Clearance A840 Canadian Currency Exchange A850 Canadian Import Termination Fee A860 Canadian Reconsignment Fee A870 Canadian Remanifest Fee A880 Cancellation Charge A890 Cancelled Order, Heavy Duty Flatcar A900 Capping A910 Car Loading A920 Car Rental A930 Carrier Credit Allowance A940 Carrier Debit Allowance A950 Carrier Notification Charge A960 Carrier A970 Cartage Charge A980 Cartage A990 Cataloging Services ADOW Payroll Additives, Overtime Labor ADRW Payroll Additives, Straight Time Labor AFEE Fee

Description: Percentage or fixed fee an organization charges for services

ALPT Port Changes B000 Central Buy B010 Cents Off B015 Bop Sheet

Description: A cardboard pallet B020 Certificate of Conformance B030 Certificate of Origin B040 Certificate of Registration B050 Certification B060 Chain and Binders B070 Chamber of Commerce Service Charge B080 Change of Airbill - Service Fee B090 Charges Forward/Advance Charge B091 Charter Services B100 Chassis Transfer B110 Chemical Milling Charge B120 Chicago Loop Charge B130 Cigarette Stamping B140 City Delivery B150 City maintenance fee B160 City Pickup

Page 159: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

GS1 Canada – Industry Relations Standards Page 61 of 81

Foodservice EDI Change Summary Version 4010 to 4010-2012

DE 1300 Code

Name

B170 City Terminal Charge B180 Cleaning Charge B190 Closing & Sealing B200 Co-manufacturing Discount B210 Co-op Credit B220 Coating (Dip, Rustproof, EDP) B230 COD Amount B240 COD Charges B250 Collect on Delivery Alteration Charge B260 Collect on Delivery Deletion Charge B270 Collect Surcharge B280 Combination Performance and Non-performance B290 Combination B300 Combine All Same Day Shipment B310 Commission Amount B320 Competitive Allowance B330 Competitive Car Allowance B340 Competitive Price B350 Compressor Charge B360 Concession Credit B370 Concession Money B380 Congestion Surcharge B390 Connect Charge B400 Conservation research fee B500 Consignee Unload B510 Consolidation B520 Constant Surveillance Service - Armed B530 Constant Surveillance Service B540 Consular Legalization Service B550 Consularization Fee B551 Consulting Service B555 Consumer Service Provider Charge B560 Container Allowance B570 Container Deposits B580 Container Destuffing B581 Container Discount B590 Container Leasing B600 Container Service Charge UK/EUR B610 Container Service Charge USA/Canada B620 Container Stuffing B630 Container/Trailer Allowance B650 Continuous Mileage B660 Contract Allowance B670 Contract Escalation B680 Contract Service Charge B690 Controlled Atmosphere B700 Converting

Page 160: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

GS1 Canada – Industry Relations Standards Page 62 of 81

Foodservice EDI Change Summary Version 4010 to 4010-2012

DE 1300 Code

Name

B720 Cooperative Advertising/Merchandising Allowance (Performance)

B730 Copy of Bill of Lading Charge B740 Copy of Delivery Receipt Charge B742 Copying B750 Core Charge B760 Cost Recovery Factor B770 Cost recovery/adjustment B775 Cotton Fee B780 Count and Recount B785 Coupon Reimbursement B787 Countervailing Duty B790 Crafting B791 Crating B800 Credit B801 Credit Card Processing Fee B802 Credit Card Processing Fee - Automated Dial-up Line B803 Credit Card Processing Fee - Leased Line B804 Credit Card Processing Fee - Fleet Cards B810 Currency Adjustment Factor B820 Currency Adjustment B830 Currency Discount B840 Customer Account Identification B850 Customer Equipment Allowance B860 Customs Broker Fee B870 Customs Charge B872 Customs Duty B880 Customs Entry B881 Customs Exam B890 Customs Formalities B900 Customs Invoice - Additional Page B910 Customs Invoice B911 Customs Penalty B920 Cut and Parallel B930 Cut B940 Cutting Charge B950 Damaged Merchandise B960 Data/Drawing Charge B970 De-Installation B980 Deadhead Mileage Charge B990 Deaf and Disabled Surcharge B992 Declared Value for Carriage B994 Declared Value for Customs B996 Declared Value for Insurance B998 Deduct to Make Market Value BU2T Bunker Adjustment - 20 Foot Container BU4T Bunker Adjustment - 40 Foot Container

Page 161: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

GS1 Canada – Industry Relations Standards Page 63 of 81

Foodservice EDI Change Summary Version 4010 to 4010-2012

DE 1300 Code

Name

BUAT Bunker Adjustment BURD Burden, Overhead, or Allowance for Indirect Costs C000 Defective Allowance C010 Deficit Freight C020 Delay Furnishing Destination Weights C030 Delivery Surcharge C040 Delivery C050 Demand charge C060 Demurrage - Average Agreement C070 Demurrage - Special C080 Demurrage C090 Deposit Charges C100 Deposit in Lieu of Order C110 Deposit C120 Deramping C130 Derrick Charge C140 Designated Supplier Inspection C150 Destination Charge C160 Detention - Special Type Flat Car C170 Detention Loading C180 Detention of Power Units C190 Detention of Trailers C200 Detention Unloading C210 Determined Freight C220 Development Charge C230 Die Service Charge C231 Disbursement C240 Disconnect Charge C250 Discount - Drop Box/Convenience Ctr. C260 Discount - Incentive C270 Discount - Multiple Shipment C280 Discount - Service Option (Delivery) C290 Discount - Service Option (Pickup) C300 Discount - Special C310 Discount C320 Display Allowance C330 Distribution Fee C340 Distribution Service C350 Distributor Discount/Allowance C360 Diversion and Reconsignment C370 Diversion Charge C380 Diversion to Air Charge C390 Dockage - Boat Detention C400 Documentation Charge C401 Document Handling C402 Door-to-Door C410 Dowel Pin Charge

Page 162: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

GS1 Canada – Industry Relations Standards Page 64 of 81

Foodservice EDI Change Summary Version 4010 to 4010-2012

DE 1300 Code

Name

C420 Drayage C430 Drayage/Line Haul C440 Driver Assisted Unloading C450 Driver's Wages C460 Drop Dock C470 Drop Yard C480 Drum Cost C490 Drum Deposit C500 Drum Up Charge C510 Dry Ice C520 Dryer Charge C530 Duty Charge C531 Duty Drawback C540 Early Buy Allowance C550 Early Payment Allowance C560 Early Ship Allowance C570 Emergency Port Charge C580 Emergency Service C590 Emergency Surcharge C600 Empty Weighing Charge C610 Enclosure C630 Endorsement Fee C640 Energy charge C650 Energy Surcharge (Fuel Adjustment Factor) C660 Engineering Charge C670 Engraving C675 Entered Value C680 Environmental Protection Service C690 Escalation C700 Escort Service C710 Eur1 Presentation Fee C720 European Port Charges C730 Excess Mileage Charge C740 Excess Periods C750 Excess Value Fee C760 Excess Weight C770 Excessive Value Charge C780 Exchange Access Credit C790 Exclusive Use Of Equipment C800 Exclusive Use C810 Exhibition Delivery Charge C820 Exhibition Pickup Charge C830 Expanded Service C840 Expedited One Day Consular Service C850 Expedited Service Charge C860 Expedited Shipments C870 Expediting Fee

Page 163: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

GS1 Canada – Industry Relations Standards Page 65 of 81

Foodservice EDI Change Summary Version 4010 to 4010-2012

DE 1300 Code

Name

C880 Expediting Premium C890 Export Customs Clearance C900 Export Declarations - Automated C910 Export Declarations - U.S. Shippers C920 Export License Application C930 Export Shipping Charge C940 Export/Import Charge C950 Extra Copies and Mailings C960 Extra Labor (Helper Service) C970 Extra Length C980 Extra Service - Counter-to-Counter C990 Fabrication Charge CA2T Currency Adjustment - 20 Foot Container CA4T Currency Adjustment - 40 Foot Container CFCT Customs Fees - Container Level CFLT Customs Fees - Lift Level CGTT Cargo Taxes CLDT Container Loss/Damage COMM Communications Charges CONC Container Charge CRLT Container Lease CUFT Currency Adjustment - Break Bulk D000 Facsimile Charges - Additional Pages D010 Facsimile Charges D015 Dunnage

Description: Loose materials used around a cargo to prevent damage or padding in a shipping container to protect contents against breakage

D020 Failed Lamp Panel Charge D025 Fax Pre-alert D030 Federal Transfer Surcharge D040 Finance Charge D050 First Article Charge D060 First Flight Out D070 Flat Rate D080 Floor Stock Protection D100 Food and Lodging D101 Foreign Office Advance D103 Foreign Customs Duty D110 Foreign Military Sales (FMS) Rental D120 Foreign Military Sales (FMS) Special Charge D130 Forwarding Agent Commission D140 Forwarding Charge D141 Forward Coupons D142 Capture Additional Data D143 Provide Name and Address D144 Provide Household Identifier

Page 164: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

GS1 Canada – Industry Relations Standards Page 66 of 81

Foodservice EDI Change Summary Version 4010 to 4010-2012

DE 1300 Code

Name

D150 Franchise fee D160 Free Domicile Shipment Processing D170 Free Goods D180 Freight Based on Dollar Minimum D190 Freight Charges to Border D200 Freight Charges to Destination D210 Freight Equalization D220 Freight Passthrough D230 Freight Surcharge D240 Freight D242 Freight, International D244 Freight, International, U.S. Dollars D246 Freight, International, Non-U.S. Dollars D250 Freshness/Leaker Allowance D260 Fuel Charge D270 Fuel Surcharge D280 Full Service D290 Full Truckload Allowance D292 Fumigation D300 Garment District D301 Gateway Fee D310 Gas Pressure D320 Glaze D330 Gold Factor D340 Goods and Services Charge D350 Goods and Services Credit Allowance D360 Goods and Services Tax Charge D370 Government Inspection D380 Government Warehouse Fee - Destination D390 Government Warehouse Fee - Origin D400 Grain Doors D410 Grain Flow Charge D420 Grinding D430 Gross Receipts Surcharge D440 Groupage Discount D450 Grouped Items

Description: Indicates the pricing for this line is related to the pricing of some other item either in this transaction or some prior transaction(s)

D460 Guaranteed Inspection Technical Service D470 Gulf Port Delivery Charge D480 Handling Charges on Distribution Freight Forwarded Beyond D490 Handling Freight At Positions Not Immediately Adjacent To

Vehicle Charge D500 Handling D501 Harbor Maintenance Report D502 Harbor Maintenance Fee

Page 165: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

GS1 Canada – Industry Relations Standards Page 67 of 81

Foodservice EDI Change Summary Version 4010 to 4010-2012

DE 1300 Code

Name

D510 Hauling and Hoisting to be Direct Billed D520 Hauling and Hoisting D530 Hazardous Cargo Charge D540 Hazardous Materials Handling Fee - Domestic D550 Hazardous Materials Handling Fee - International D560 Hazardous Storage D570 Heat in Transit Charges D580 Heat Treat Charge D590 Heavy Duty Flat Car Charge D600 Heavy Lift D610 High Security Red In-bond Seal Charge D620 Highway Interchange D630 Hointins and Hauling D640 Holding Charge D650 Home Line Freight Charge D655 Honey Fee D660 Hook-up charge D670 Hose Charge Special D680 Hose Charge D690 Household Goods Pickup or Delivery D700 IATA Airbill Preparation D701 International Air Transport Association (IATA) Commission D710 IATA Fee D711 International Air Transport Association (IATA) Markup D720 Identification D730 Import Service Fee D740 In Transit Price Protection D750 Inbound Freight Charges D760 Income Freight (Manufacturing to Shipping Point) D770 Incorrect Billing Account Charge D780 Industry Price Allowance D790 Initial License Fee D800 Inland Transportation D810 Inside Cable Connectors D820 Inside Delivery D830 Inside Pickup D840 Inspect at Destination D850 Inspect at Origin D870 Inspection D880 Installation & Warranty D890 Installation and Training D900 Installation D910 Insulated Tank Charge D920 Insurance Fee D930 Insurance Placement Cost Charge D940 Insurance Premium D950 Insurance Provided by Lessee

Page 166: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

GS1 Canada – Industry Relations Standards Page 68 of 81

Foodservice EDI Change Summary Version 4010 to 4010-2012

DE 1300 Code

Name

D960 Insurance Provided by Lessor D970 Insurance Surcharge D980 Insurance D990 Interdivision Profit D995 Interest Amount DCET Damage to Carrier Equipment DCVT Damage to Carrier Vessel DDZT Drayage at Port of Debarkation (Rate Zone) DEZT Drayage at Port of Embarkation (Rate Zone) DFDT Keep From Freezing Percent Differential DGET Damage to Government Equipment DOVT Container Diversion DPDT Drayage at Port of Debarkation DPET Drayage at Port of Embarkation E000 Interest on refund E010 Interest on Security Deposit E020 Interim Use Permitted at Special Rate E022 International Courier E030 International Door-to-Door Handling Fee E040 Interplant Charge E050 Interstate/Highway Toll E060 Intra-plant Charge E063 Invoice Additional Amount E065 Invoice Adjustment E067 Invoice At-Cost Amount E068 Invoice Delivery Terms Amount E069 Invoice No-Charge Amount E070 Invoice Services E080 Invoice with Goods E090 Irish Arbitraries E100 Island Delivery Charge E110 Island Pickup Charge E120 Italian Release Charge E130 Item Percentage E140 Item-Unit E150 Koshering E160 Label Allowance E170 Labeling E180 Labor (Repair and Return Orders) E190 Labor Charges E191 Labor, Straight-time E192 Labor, Overtime E193 Labor, Premium Overtime E200 Labor Cost of Removal E210 Labor Service E220 Labor, Modify E230 Labor, No Trouble Found

Page 167: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

GS1 Canada – Industry Relations Standards Page 69 of 81

Foodservice EDI Change Summary Version 4010 to 4010-2012

DE 1300 Code

Name

E240 Labor, Test and Calibrate E250 Lading Adjustment Charge E260 Lashing E270 Late Order Charge E280 Late Payment Charge E290 Layout/Design E300 Layover Charges E310 Lead Factor E320 Leaking Underground Storage Tax (LUST) E330 Lease Shortfall Consideration E340 Less Than Truckload (LTL) Charge E350 Letter of Credit Processing E360 License and Title E370 Lifeline Surcharge E380 Lift Gate (Truck) or Forklift Service at Pickup/Delivery E381 Lime Fee E382 Liquidation Anti-Dumping Duty E384 Liquidation Countervailing Duty E386 Liquidation Tax Amount E388 Liquidation Total Due U.S. Customs and Border Protection

(CBP) E389 Liquidation Total Fees E390 Load Weighing Charge E400 Loading (Labor Charges) E410 Loading E420 Loan Fee E430 Local Delivery/Drayage E440 Locomotive Delayed in Switching Service E450 Locomotive Under Own Power E460 Lot Charge E470 Lump Sum E480 Machining Charge E485 Mail Fee E490 Mail Invoice to Each Location E500 Mail Invoice E510 Mailing - Postage Cost E520 Mailing - Service Fee E530 Manifest Charge E540 Manufacturing E550 Market Development Funds E560 Marking or Tagging Charge E565 Markdown Allowance E570 Marriage Rule E580 Memo Returnable Container E585 Merchandise Processing Fee E590 Message Charge E600 Message Rate Adjustment

Page 168: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

GS1 Canada – Industry Relations Standards Page 70 of 81

Foodservice EDI Change Summary Version 4010 to 4010-2012

DE 1300 Code

Name

E610 Messenger Service E620 Metals Surcharge E630 Meter Charge E640 Mileage Fee (For Repair and Return) E650 Mileage or Travel E660 Monthly Rental E670 Mount/Demount E680 Mounting E690 Municipal Surcharge E695 Mushroom Fee E700 N.H.D. Wharfage E710 New Discount E720 New Distribution Allowance E730 New Item Allowance E740 New Store Allowance E750 New Store Discount E760 New Warehouse Discount E770 New Warehouse E780 New York Delivery Charge E790 New York Pickup Charge E800 No Return Credit Allowance E805 Non-Dutiable Charges E810 Non Generated Freight E820 Non-returnable Containers E830 Normal Pump Charge E840 Notarized Affidavit E850 Notify Consignee Before Delivery E860 Notify Consignee E870 Nozzle Charge E880 Ocean Charges - Hazardous E890 Ocean Freight E900 Offshore - Alaska/Hawaii E910 On Carriage E920 On Hand Service E930 One - Day Service E940 One Time Engineering Charge E950 One-Time License Fee E960 One-Time-Only Charge E970 Onetime Tooling E980 Operator Credit E990 Option Charge (Color Fabric Office Furniture) ENGA Engineering Supplies EXLT Extra Length Surcharge F000 Optional Charge F010 Optional Software Support for Operational Support Systems F020 Optional Software Support for Switching Systems F030 Order Notify Charge

Page 169: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

GS1 Canada – Industry Relations Standards Page 71 of 81

Foodservice EDI Change Summary Version 4010 to 4010-2012

DE 1300 Code

Name

F040 Order-Flat F050 Other (See related description) F060 Other Accessorial Service Charge F061 Other Advances F062 Other Export Charges F063 Other Government Agency Declaration F065 Other Government Agency Exam F067 Other Import Charge F070 Out of Route Miles F080 Out of Zone Pickup or Delivery F090 Outside Cable Connectors F100 Over Dimension F110 Overrun Charge F120 Oversized Premium F130 Overtime Loading F140 Pack Invoice with Shipment F150 Packaging Service F155 Packaging F160 Painting (Primer or Finish) F170 Pallet Exchange Charge F180 Pallet F190 Palletizing F200 Paralleling F210 Parish/County Sales Tax (only) F220 Passing Shippers Export Entry F225 Pecan Fee F230 Penalty Charge F240 Per Item Charge F250 Per Order Charge F260 Per Pound Charge F270 Percent of Product F271 Percent of Shipped Quantity that is Returnable F272 Percent of Shipment Value that is Returnable F280 Performance Allowance F290 Performance Award F300 Permit Charge F310 Permits Bonds Escort Attendant F320 Phosphatizing (Steel Treatment) F330 Pickup and Delivery F340 Pick/Up F350 Pickle and Oil F360 Pickup - Out of Area F370 Pickup Surcharge F380 Pier Charges - Wharfage F390 Pier Charges Other Than Wharfage F400 Pier Pickup and/or Delivery F401 Pier Unloading

Page 170: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

GS1 Canada – Industry Relations Standards Page 72 of 81

Foodservice EDI Change Summary Version 4010 to 4010-2012

DE 1300 Code

Name

F410 Pilot Inspection F420 Placement and/or Removal Charge F430 Plating F440 Pole, Wood-service Charge F445 Pork Fee F450 Positioning at Origin F460 Postage F465 Potato Fee F470 Power Factor Adjustment F480 Pre-carriage Excess F490 Pre-carriage F500 Pre-Positioned Inventory Service F510 Precious Metal Content F520 Preloading Charge F530 Prelodge Charge F540 Premise Use F550 Premium Charge F560 Premium Transportation F570 Prepaid Usage Allowance F580 Preparation and Delivery F590 Preparation of Air Waybill - Origin F600 Preparation of Canadian Customs Invoice F610 Preparation of Commercial Invoice F620 Preparation of Export Entry F630 Preparation of Insurance Certificate F640 Preparation of U.S. Export Documentation F650 Preparation F660 Previous Billing F670 Price and Marketing Allowance F680 Price Deviation F690 Prior Balance F700 Prior Billing Amount F710 Prior Delivery Of Bill Charge F720 Prior Month Credit F730 Priority Service F740 Process in Transit Privilege F750 Processing Charge F760 Processing F765 Procurement Charge F770 Professional Fees F780 Proforma Invoice F790 Progress Payment Requirement F800 Promotional Allowance F810 Promotional Discount F820 Proof & Composition F830 Proof of Delivery F840 Protective Service - Cold

Page 171: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

GS1 Canada – Industry Relations Standards Page 73 of 81

Foodservice EDI Change Summary Version 4010 to 4010-2012

DE 1300 Code

Name

F850 Protective Service - Heat F860 Protective Service Charge F870 Pulling Eyes F880 Pump Air Charge F890 Pump Charge F900 Purchase Option F910 Quantity Discount F920 Quantity Surcharge F930 Equipment Manufacturer Restoration Audit F940 Ramping F950 Rate Code F955 Rate Reduction Bond F960 Re-Bill Charge F970 Rebate F980 Rebilled Drayage - Destination F990 Rebilled Drayage - Origin F991 Receiving FAKT Barge Freight All Kinds Service FLST Flatrack Surcharge G000 Recipient Address Correction G010 Reclamation, Federal G020 Reclamation, State G025 Reconciliation G030 Reconnect charge G040 Reconsign Consignee Charge G050 Reconsign Delivery Charge G060 Reconsignment Charge G070 Recoopering (at Owner's or Shipper's Expense) G080 Record/Filing G090 Recovery Fee G100 Recovery G110 Recrating/Recoopering - Destination G120 Recrating/Recoopering - Origin G130 Recurring Hardware Maintenance Charge G140 Recurring License Fee G150 Recurring Software Maintenance Charge G160 Redelivery G170 Redistribution Allowance G180 Reduction Prepalletized Cargo G190 Reel Cable G200 Reel Deposit G210 Reel G220 Refrigeration G230 Refrigeration/Mechanical Detention G240 Refund G250 Refurbishing Charge G260 Regain

Page 172: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

GS1 Canada – Industry Relations Standards Page 74 of 81

Foodservice EDI Change Summary Version 4010 to 4010-2012

DE 1300 Code

Name

G270 Registration of Export for Reentry G280 Registration of Export Shipments G290 Regulatory Fee G300 Regulatory required refund G310 Reliability Charge G320 Relinquishment Charge G322 Reliquidation Anti-Dumping Duty G324 Reliquidation Countervailing Duty G326 Reliquidation Tax Amount G328 Reliquidation Total Due U.S. Customs and Border Protection

(CBP) G329 Reliquidation Total Fees G330 Rental Charge G340 Rental Deduction G350 Rents and Leases G360 Repack Charge G370 Repair at Buyers Expense Charge G380 Repair at Customer Expense Charge G390 Repair at Government Expense Charge G400 Repair G410 Repickup G420 Request Via Canada G430 Research & Development Fee G440 Resellers Discount G450 Residential Delivery G460 Residential Pickup G470 Restocking Charge G480 Restricted Article Fee G490 Retainer G500 Return Cargo Charge G510 Returnable Container G520 Returned Load G530 Rework G540 Riding Attendant Charge G550 Rocky Mountain Bureau 583 Item 1100 Arbitrary Charge G560 Roll Out Adjustment G570 Roll Rebate G580 Royalties G590 Salvage G600 Same - Day Service G610 Saturday Delivery G620 Saturday Pickup or Delivery Charge G630 Saturday Pickup G640 Scale Charge Unloading G650 Scale Charge G660 Scrap Allowance G670 Security Signature Service

Page 173: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

GS1 Canada – Industry Relations Standards Page 75 of 81

Foodservice EDI Change Summary Version 4010 to 4010-2012

DE 1300 Code

Name

G680 Segregating (Sorting) G690 Select Charge G700 Self Unloader G710 Seller Hand Carry G720 Service Assistance Program Surcharge G730 Service Charge (with Cash Discount) G740 Service Charge G750 Service Upgrade G760 Set-up G770 Shearing G775 Sheep Fee G780 Ship to Stock Quality Audit G790 Shipper Load and Count G800 Shipper Load Carrier Count G810 Shipper Load Consignee Unload G820 Shipper Load G821 Shipping G830 Shipping and Handling G840 Shipside Pickup G850 Shotblasting G860 Shrink Allowance G870 Shrink-Wrap Charge G880 Shrinkage Allowance G890 Single Invoice Allowance G900 Single Pickup G910 Single Shipment Fee G920 Sleeving G930 Slip Sheet Unloading Allowance G940 Slip Sheet, Rail G950 Slip Sheet, Truck G960 Slotting Allowance G970 Small Order Charge G980 Software Support Service G990 Source Inspection GMST Garment Surcharge H000 Special Allowance H010 Special Buy H020 Special Circus Trains H030 Special Credit H040 Special Delivery H050 Special Detention Charge H060 Special Equipment Charge H070 Special Finish Charge H080 Special Freight Supplements H090 Special Handling H100 Special Mileage Movements H110 Special Packaging

Page 174: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

GS1 Canada – Industry Relations Standards Page 76 of 81

Foodservice EDI Change Summary Version 4010 to 4010-2012

DE 1300 Code

Name

H120 Special Permits H130 Special Pickup H140 Special Pump Charge H150 Special Seal Charge H151 Special Services H160 Special Test Equipment Charge H170 Special Tooling Charge H180 Special Tooling rework charge H190 Special Train Movement H200 Special Use H210 Special Vehicle Rent H215 Specific Duty H220 Specification Review H230 Split Delivery H240 Split Pickup at Pier Charge H250 Split Pickup H260 Spool Charge H270 Spotting of Trailer H280 Spreader Charge H290 Stamp Fee H300 Stamping H310 Standby Charge H320 State Motor Fuel H330 State Sales Charge H340 State Surcharge H350 State/Metropolitan Transit Authority Surcharge H360 Steaming Charge H370 Stenciling Charge H380 Stop-off at Pier Charge H390 Stop-off Charge H400 Stopcharge H410 Stopping in Transit H420 Storage in Transit H430 Storage H440 Straightening Charge H450 Strapping H460 Street lamps charge H470 Stripping, Sorting, and Consolidation H480 Subject to Cooperative Advertising Allowance H490 Subject To Tax On Resale H500 Sufferance Warehouse Charge (Export or Import) H505 Sugar Fee H507 Sum of Adds and Deducts to Make Market Value H510 Sunday or Holiday Pickup or Delivery H520 Super Bag Charge H530 Supervisor Charge H535 Supplemental Duty

Page 175: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

GS1 Canada – Industry Relations Standards Page 77 of 81

Foodservice EDI Change Summary Version 4010 to 4010-2012

DE 1300 Code

Name

H540 Supplemental Items H550 Surcharge H551 Surety Bond H560 Swell H570 Switch Charge H580 Switching Charge H590 Tank Car Allowance H600 Tank Rental H605 Tarping H610 Tax - Airport Tax, Destination H620 Tax - Airport Tax, Origin H625 Tax - Beverage Tax H630 Tax - City Sales Tax (Only) H640 Tax - Excise Tax - Destination H650 Tax - Excise Tax - Origin H660 Tax - Federal Excise Tax, FET H670 Tax - Federal Excise Tax, FET, on Tires H680 Tax - Governmental H690 Tax - Handling Charge Tax H700 Tax - Local Tax H710 Tax - Metropolitan Transit Tax H720 Tax - Regulatory Tax H730 Tax - Local Sales Tax

Description: All applicable sales taxes by taxing authorities below the State level

H740 Tax - Sales and Use H750 Tax - Sales Tax (State and Local) H760 Tax - State Hazardous Substance H770 Tax - State Tax H780 Tax - Super Fund Excise Tax H790 Tax - Use Tax H800 Tax - Value Added Tax (VAT) H806 Tax Credit H810 Tax Liability - Amortized H820 Tax Liability - One Time H830 Tax on Miscellaneous Charges H840 Tax on Transportation H850 Tax H855 Tea Fee H860 Technology Exchange H870 Telegram Chargeback H880 Telephone - Destination H890 Telephone - Origin H900 Telephone Charge H910 Temperature Protection H920 Temporary Allowance H930 Temporary Voluntary Allowance

Page 176: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

GS1 Canada – Industry Relations Standards Page 78 of 81

Foodservice EDI Change Summary Version 4010 to 4010-2012

DE 1300 Code

Name

H935 Tendered as Truckload H940 Terminal Charge H950 Terminal Differential H960 Terminal Service Fee H970 Terms Allowance H980 Test/Qualification Charge H990 Testing Services Charge HZDT Hazardous Cargo on Deck I000 Testing I010 Third Party Allowance I020 Third Party Pallets I030 Throughput Allowance I040 Throughput Container Charge I050 Thruway Charge I060 Ticketing Service I070 Tobacco Products Report Charge I080 TOFC Service Charge I090 Tool Charge I100 Tooling Rework Charge I110 Tooling I120 Tools for Printing I130 Total Assessorial Charges I131 Total Fees I132 Total Invoice Amount I133 Total Due U.S. Customs and Border Protection (CBP) I134 Total Invoice Amount, U.S. Dollars I136 Total Invoice Amount, Non-U.S. Dollars I138 Total Material Invoice Amount I140 Tracing Inbound Via Other Carriers I150 Tracing Service Fee I160 Track Storage I170 Trade Discount I180 Trade In I190 Trailer Rental Charge I200 Transfer Charge I210 Transfer of Lading Charge I220 Transferred Charges I230 Transit I235 Transmission Charge I240 Transportation And Setup I250 Transportation Charge (Minimum Rate) I260 Transportation Direct Billing I270 Transportation Third Party Billing I280 Transportation Vendor Provided I290 Trimming Charge I300 Truck Detention I310 Truckload Discount

Page 177: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

GS1 Canada – Industry Relations Standards Page 79 of 81

Foodservice EDI Change Summary Version 4010 to 4010-2012

DE 1300 Code

Name

I320 Turning Charge I330 Two - Day Service I340 Two Door Pickup I350 U.S. Vehicles I360 Unabsorbed Switching I370 Unitized I380 Unloading (Labor Charges) I390 Unloading I400 Unloading/Reloading Charge I410 Unsaleable Merchandise Allowance I411 Unscheduled Fee I420 Up Charge I430 Usage Plan Detail Charge I431 U.S. Customs and Border Protection (CBP) Flat Assist

Amount I432 U.S. Customs and Border Protection (CBP) Maximum Assist

Amount I440 USDA Inspected, Stamping Certification I450 Use - Special Type Flat Car I460 Use Charge Tooling/Personnel I470 Valuation Fee I480 Vehicle Ordered but Not Used I490 Vehicle Prep Charge (Courtesy Delivery) I495 Vehicle Road Charge I500 Vendor Freight I510 Venting Instructions I520 Virgin Island Transfer Charge I530 Volume Discount I540 Voluntary Contribution Charge I550 Waiting Time I560 War Risk Surcharge I570 Warehouse I580 Warehousing I590 Warranties I595 Watermelon Fee I600 Waybill and Invoice Distribution I610 Weather Protection I620 Weight Verification Charge I630 Wharfage & Handling I640 Wharfage Charge I650 Wide Area Telephone Service (WATS) Usage Credit I660 Will Call Charge I670 Written Proof of Delivery I680 X-ray Charge I690 Gratuity I700 Escrow I710 Payment

Page 178: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

GS1 Canada – Industry Relations Standards Page 80 of 81

Foodservice EDI Change Summary Version 4010 to 4010-2012

DE 1300 Code

Name

I720 Direct Product Handling (DPC) I730 Price Adjustment Percent (PCT) I740 Post Damaged Handling (PDC) I750 Reclamation Center Handling (Chute) I760 Reclamation Shared Responsibility (SRS) I770 Mid-Tier Lottery Winners I780 Mid-Tier Lottery Cashing Bonus I790 Lottery Cross Redeemed I800 Low-Tier Lottery Winners I810 Low-Tier Lottery Cashing Bonus I820 Lottery Charge Back I830 Tote I840 Extra Hour Charges I850 Refused Delivery Charge I860 Reimbursement for Online Cashing Bonus I870 Reimbursement for Online Winners I880 Online Sales Bonus I890 Instant Sales Bonus IDCT Improper Documentation LC2T Land Currency Adjustment Factor - 20 Foot Container LC4T Land Currency Adjustment Factor - 40 Foot Container LCLT Percent Differential - Less Than Container LECT Less Than Container LFDT Linehaul from Port of Debarkation LMDT Liner Terms at Port of Embarkation LNDT Liner Terms at Port of Debarkation LPDT Linehaul Percent Differential LQDT Liquidated Damages LTET Linehaul to Port of Embarkation MATT Modified Atmosphere OCNT Over Height Container OFFA Office Supplies OODT On Deck Break Bulk Differential OTHR Other Miscellaneous Earning or Additive OWCT Over Width Container PFCH Prepared Food Charge PRST Stuffing Charge PTAX Payroll Taxes PVPT Private Owned Vehicle Processing R020 Personal Property, Member R030 Personal Property, Spouse R040 Port Handling and Unloading R060 Packing, Crating, and Handling Charge R080 Packing, Crating, Handling, and Transportation Charge RDHT Railhead Handling RFEE Recycling Fee RFMT Reefer Maintenance

Page 179: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

GS1 Canada – Industry Relations Standards Page 81 of 81

Foodservice EDI Change Summary Version 4010 to 4010-2012

DE 1300 Code

Name

RPDT Reefer Cargo Percent Differential RSTT Respotting SFBT Single Factor Origination/Destination SFDT Single Factor Origination/Port of Debarkation SFET Single Factor Port of Embarkation/Destination SSCT Stripping, Sorting and Consolidation SSUT Pole Lashing Equipment (PLE) Surcharge STDT Stop-off at Destination STFT Stuffing STOT Stop-off at Origination TERT Terminal Handling Charges VCLT Van Cleaning WBBT Wharfage - Breakbulk WCFT Wharfage - Container WFTT Wasted/Futile Trip WRBT War Risk Crew Insurance WRIT War Risk Insurance X001 Auto Towing X002 Late Return X003 One Way/Drop Off X004 Passenger Facility Charge X005 Lodging X006 Business Center X007 Gift Shop X008 Health Club X009 Laundry/Dry Cleaning X010 In-room Movie X011 In-room Mini-bar X012 Meals X013 Parking X014 Prepaid Amount X015 Liquor Charge ZZZZ Mutually Defined

Page 180: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

810 InvoiceFoodservice EDI

Version: 4010-2012 FS Final

Author: Technical StandardsWork Group -Foodservice

Publication: 7/1/2012 Notes: For Implementation

December 2012

Page 181: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Invoice Foodservice - 810

July 2012 [V004010-2012 FS] iCopyright 2012 - GS1 Canada

Table of Contents

810 Invoice Foodservice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>ST Transaction Set Header . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>BIG Beginning Segment for Invoice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>CUR Currency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>REF Reference Identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>PER Administrative Communications Contact . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>N1 Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>N2 Additional Name Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>N3 Address Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>N4 Geographic Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>ITD Terms of Sale/Deferred Terms of Sale . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>DTM Date/Time Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>FOB F.O.B. Related Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>IT1 Baseline Item Data (Invoice) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>CTP Pricing Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>PID Product/Item Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>PO4 Item Physical Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>SAC Service, Promotion, Allowance, or Charge Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>TDS Total Monetary Value Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>SAC Service, Promotion, Allowance, or Charge Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>ISS Invoice Shipment Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>CTT Transaction Totals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>SE Transaction Set Trailer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>

. . . . . 1. . . . . 3. . . . . 4. . . . . 5. . . . . 6. . . . . 7. . . . . 9. . . . 11. . . . 12. . . . 13. . . . 14. . . . 16. . . . 17. . . . 18. . . . 20. . . . 21. . . . 23. . . . 25. . . . 30. . . . 31. . . . 36. . . . 38. . . . 39

Page 182: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Invoice Foodservice - 810

July 2012 [V004010-2012 FS] 1Copyright 2012 - GS1 Canada

810 Invoice FoodserviceFunctional Group=IN

Purpose: This Draft Standard for Trial Use contains the format and establishes the data contents of the InvoiceTransaction Set (810) for use within the context of an Electronic Data Interchange (EDI) environment. Thetransaction set can be used to provide for customary and established business and industry practice relative to thebilling for goods and services provided.

Heading:Pos Id Segment Name Req Max Use Repeat Notes Usage010 ST Transaction Set Header M 1 Must use020 BIG Beginning Segment for

InvoiceM 1 Must use

040 CUR Currency O 1 Used050 REF Reference Identification O 12 Used060 PER Administrative

Communications ContactO 3 Used

LOOP ID - N1 200 LOOP ID - N1 200

070 N1 Name O 1 Used080 N2 Additional Name

InformationO 2 Used

090 N3 Address Information O 2 Used100 N4 Geographic Location O 1 Used130 ITD Terms of Sale/Deferred

Terms of SaleO >1 Used

140 DTM Date/Time Reference O 10 Used150 FOB F.O.B. Related Instructions O 1 Used

Detail:Pos Id Segment Name Req Max Use Repeat Notes Usage

LOOP ID - IT1 200000 LOOP ID - IT1 200000

010 IT1 Baseline Item Data(Invoice)

O 1 Used

050 CTP Pricing Information O 25 Used LOOP ID - PID 1000 LOOP ID - PID 1000

060 PID Product/Item Description O 1 Used100 PO4 Item Physical Details O 1 Used

LOOP ID - SAC 25 LOOP ID - SAC 25

180 SAC Service, Promotion,Allowance, or ChargeInformation

O 1 Used

Summary:Pos Id Segment Name Req Max Use Repeat Notes Usage010 TDS Total Monetary Value

SummaryM 1 Must use

LOOP ID - SAC 25 LOOP ID - SAC 25

040 SAC Service, Promotion, O 1 Used

Page 183: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Invoice Foodservice - 810

Pos Id Segment Name Req Max Use Repeat Notes Usage

July 2012 [V004010-2012 FS] 2Copyright 2012 - GS1 Canada

Allowance, or ChargeInformation

LOOP ID - ISS >1 LOOP ID - ISS >1

060 ISS Invoice Shipment Summary O 1 Used070 CTT Transaction Totals O 1 N3/070 Used080 SE Transaction Set Trailer M 1 Must use

Notes: 3/070 Number of line items (CTT01) is the accumulation of the number of IT1 segments. If used, hash total

(CTT02) is the sum of the value of quantities invoiced (IT102) for each IT1 segment.

Page 184: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Invoice Foodservice - 810

July 2012 [V004010-2012 FS] 3Copyright 2012 - GS1 Canada

ST Transaction Set Header Pos: 010 Max: 1Heading - Mandatory

Loop: N/A Elements: 2

User Option (Usage): Must usePurpose: To indicate the start of a transaction set and to assign a control number

Element Summary: Ref Id Element Name Req Type Min/Max UsageST01 143 Transaction Set Identifier Code

Description: Code uniquely identifying aTransaction Set

M ID 3/3 Must use

CodeList Summary (Total Codes: 298, Included: 1)Code Name810 Invoice

ST02 329 Transaction Set Control Number

Description: Identifying control numberthat must be unique within the transactionset functional group assigned by theoriginator for a transaction setUser Note 1: The number is sequentiallyassigned by the sender, starting with onewithin each functional group. For eachfunctional group, the first transaction setcontrol number will be 0001 and incrementedby one for each additional transaction setwithin the group.

User Note 1: The number is sequentiallyassigned by the sender, starting with onewithin each functional group. For eachfunctional group, the first transaction setcontrol number will be 0001 and incrementedby one for each additional transaction setwithin the group.

M AN 4/9 Must use

Semantics: 1. The transaction set identifier (ST01) used by the translation routines of the interchange partners to select the

appropriate transaction set definition (e.g., 810 selects the Invoice Transaction Set).

Page 185: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Invoice Foodservice - 810

July 2012 [V004010-2012 FS] 4Copyright 2012 - GS1 Canada

BIG Beginning Segment forInvoice

Pos: 020 Max: 1Heading - Mandatory

Loop: N/A Elements: 4

User Option (Usage): Must usePurpose: To indicate the beginning of an invoice transaction set and transmit identifying numbers and dates

Element Summary: Ref Id Element Name Req Type Min/Max UsageBIG01 373 Date

Description: Date expressed asCCYYMMDD

M DT 8/8 Must use

BIG02 76 Invoice Number

Description: Identifying number assignedby issuer

M AN 1/22 Must use

BIG03 373 Date

Description: Date expressed asCCYYMMDDUser Note 1: Purchasing Organization'soriginal purchase order dateUser Note 1: Purchasing Organization'soriginal purchase order date

O DT 8/8 Used

BIG04 324 Purchase Order Number

Description: Identifying number forPurchase Order assigned by theorderer/purchaserUser Note 1: Purchasing Organization'soriginal purchase order numberUser Note 1: Purchasing Organization'soriginal purchase order number

O AN 1/22 Used

Semantics: 1. BIG01 is the invoice issue date.2. BIG03 is the date assigned by the purchaser to purchase order.3. BIG10 indicates the consolidated invoice number. When BIG07 contains code CI, BIG10 is not used.

Comments: 1. BIG07 is used only to further define the type of invoice when needed.

Page 186: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Invoice Foodservice - 810

July 2012 [V004010-2012 FS] 5Copyright 2012 - GS1 Canada

CUR Currency Pos: 040 Max: 1Heading - Optional

Loop: N/A Elements: 2

User Option (Usage): UsedPurpose: To specify the currency (dollars, pounds, francs, etc.) used in a transaction

Element Summary: Ref Id Element Name Req Type Min/Max UsageCUR01 98 Entity Identifier Code

Description: Code identifying anorganizational entity, a physical location,property or an individual

M ID 2/3 Must use

CodeList Summary (Total Codes: 1312, Included: 1)Code NameBY Buying Party (Purchaser)

CUR02 100 Currency Code

Description: Code (Standard ISO) forcountry in whose currency the chargesare specifiedUser Note 1: CAD CanadianUSD United StatesUser Note 1: CAD CanadianUSD United States

M ID 3/3 Must use

Syntax Rules: 1. C0807 - If CUR08 is present, then CUR07 is required.2. C0907 - If CUR09 is present, then CUR07 is required.3. L101112 - If CUR10 is present, then at least one of CUR11 or CUR12 is required.4. C1110 - If CUR11 is present, then CUR10 is required.5. C1210 - If CUR12 is present, then CUR10 is required.6. L131415 - If CUR13 is present, then at least one of CUR14 or CUR15 is required.7. C1413 - If CUR14 is present, then CUR13 is required.8. C1513 - If CUR15 is present, then CUR13 is required.9. L161718 - If CUR16 is present, then at least one of CUR17 or CUR18 is required.

10. C1716 - If CUR17 is present, then CUR16 is required.11. C1816 - If CUR18 is present, then CUR16 is required.12. L192021 - If CUR19 is present, then at least one of CUR20 or CUR21 is required.13. C2019 - If CUR20 is present, then CUR19 is required.14. C2119 - If CUR21 is present, then CUR19 is required.

Comments: 1. See Figures Appendix for examples detailing the use of the CUR segment.

Page 187: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Invoice Foodservice - 810

July 2012 [V004010-2012 FS] 6Copyright 2012 - GS1 Canada

REF Reference Identification Pos: 050 Max: 12Heading - Optional

Loop: N/A Elements: 2

User Option (Usage): UsedPurpose: To specify identifying information

Element Summary: Ref Id Element Name Req Type Min/Max UsageREF01 128 Reference Identification Qualifier

Description: Code qualifying theReference Identification

M ID 2/3 Must use

CodeList Summary (Total Codes: 1503, Included: 3)Code NameDP Department NumberIA Internal Vendor Number

User Note 1:User Note 1:Identification number assigned to the Selling Organization, by the Purchasing Organizationfor use within the Purchasing Organization's systemIdentification number assigned to the Selling Organization, by the Purchasing Organizationfor use within the Purchasing Organization's system

IT Internal Customer NumberUser Note 1:User Note 1:

Identification number assigned to the Purchasing Organization, by the SellingOrganization, for use within the Selling Organization's systemIdentification number assigned to the Purchasing Organization, by the SellingOrganization, for use within the Selling Organization's system

REF02 127 Reference Identification

Description: Reference information asdefined for a particular Transaction Set oras specified by the ReferenceIdentification Qualifier

C AN 1/30 Must use

Syntax Rules: 1. R0203 - At least one of REF02 or REF03 is required.

Semantics: 1. REF04 contains data relating to the value cited in REF02.

Page 188: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Invoice Foodservice - 810

July 2012 [V004010-2012 FS] 7Copyright 2012 - GS1 Canada

PER AdministrativeCommunications Contact

Pos: 060 Max: 3Heading - Optional

Loop: N/A Elements: 6

User Option (Usage): UsedPurpose: To identify a person or office to whom administrative communications should be directed

Element Summary: Ref Id Element Name Req Type Min/Max UsagePER01 366 Contact Function Code

Description: Code identifying the majorduty or responsibility of the person orgroup named

M ID 2/2 Must use

CodeList Summary (Total Codes: 230, Included: 2)Code NameCR Customer Relations

User Note 1:User Note 1:Customer service representativeCustomer service representative

SR Sales Representative or Department

PER02 93 Name

Description: Free-form name

O AN 1/60 Used

PER03 365 Communication Number Qualifier

Description: Code identifying the type ofcommunication number

C ID 2/2 Used

CodeList Summary (Total Codes: 40, Included: 2)Code NameEM Electronic MailTE Telephone

PER04 364 Communication Number

Description: Complete communicationsnumber including country or area codewhen applicable

C AN 1/80 Used

PER05 365 Communication Number Qualifier

Description: Code identifying the type ofcommunication number

C ID 2/2 Used

CodeList Summary (Total Codes: 40, Included: 2)Code NameEM Electronic MailTE Telephone

PER06 364 Communication Number

Description: Complete communicationsnumber including country or area codewhen applicable

C AN 1/80 Used

Page 189: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Invoice Foodservice - 810

Ref Id Element Name Req Type Min/Max Usage

July 2012 [V004010-2012 FS] 8Copyright 2012 - GS1 Canada

Syntax Rules: 1. P0304 - If either PER03 or PER04 is present, then the other is required.2. P0506 - If either PER05 or PER06 is present, then the other is required.3. P0708 - If either PER07 or PER08 is present, then the other is required.

Page 190: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Invoice Foodservice - 810

July 2012 [V004010-2012 FS] 9Copyright 2012 - GS1 Canada

N1 Name Pos: 070 Max: 1Heading - Optional

Loop: N1 Elements: 4

User Option (Usage): UsedPurpose: To identify a party by type of organization, name, and code

Element Summary: Ref Id Element Name Req Type Min/Max UsageN101 98 Entity Identifier Code

Description: Code identifying anorganizational entity, a physical location,property or an individual

M ID 2/3 Must use

CodeList Summary (Total Codes: 1312, Included: 8)Code NameBO Broker or Sales Office

User Note 1:User Note 1:For a domestic purchase order, this is the manufacturer's sales office. For an importpurchase order this is the sales office that interacts with the manufacturer's/buyer's agent.For a domestic purchase order, this is the manufacturer's sales office. For an importpurchase order this is the sales office that interacts with the manufacturer's/buyer's agent.

BS Bill and Ship ToBT Bill-to-PartyRI Remit ToSF Ship FromST Ship ToSU Supplier/Manufacturer

User Note 1:User Note 1:Supplier may or may not be the manufacturerSupplier may or may not be the manufacturer

VN VendorUser Note 1:User Note 1:

Party supplying the products being maintainedParty supplying the products being maintained

N102 93 Name

Description: Free-form name

C AN 1/60 Used

N103 66 Identification Code Qualifier

Description: Code designating thesystem/method of code structure used forIdentification Code (67)

C ID 1/2 Used

CodeList Summary (Total Codes: 215, Included: 2)Code Name9 D-U-N-S+4, D-U-N-S Number with Four Character SuffixUL UCC/EAN Location Code

Description: Global Location Number (GLN) (Revised name) A globally unique 13 digit code used for the identification of any physical or legal locationthat needs to be uniquely identified for use in the supply chain. A GS1 identification key SEE CODE SOURCE 583

N104 67 Identification Code C AN 2/80 Used

Page 191: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Invoice Foodservice - 810

Ref Id Element Name Req Type Min/Max Usage

July 2012 [V004010-2012 FS] 10Copyright 2012 - GS1 Canada

Description: Code identifying a party orother code

Syntax Rules: 1. R0203 - At least one of N102 or N103 is required.2. P0304 - If either N103 or N104 is present, then the other is required.

Comments: 1. This segment, used alone, provides the most efficient method of providing organizational identification. To

obtain this efficiency the "ID Code" (N104) must provide a key to the table maintained by the transactionprocessing party.

2. N105 and N106 further define the type of entity in N101.

Page 192: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Invoice Foodservice - 810

July 2012 [V004010-2012 FS] 11Copyright 2012 - GS1 Canada

N2 Additional Name Information Pos: 080 Max: 2Heading - Optional

Loop: N1 Elements: 2

User Option (Usage): UsedPurpose: To specify additional names or those longer than 35 characters in length

Element Summary: Ref Id Element Name Req Type Min/Max UsageN201 93 Name

Description: Free-form name

M AN 1/60 Must use

N202 93 Name

Description: Free-form name

O AN 1/60 Used

Page 193: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Invoice Foodservice - 810

July 2012 [V004010-2012 FS] 12Copyright 2012 - GS1 Canada

N3 Address Information Pos: 090 Max: 2Heading - Optional

Loop: N1 Elements: 2

User Option (Usage): UsedPurpose: To specify the location of the named party

Element Summary: Ref Id Element Name Req Type Min/Max UsageN301 166 Address Information

Description: Address information

M AN 1/55 Must use

N302 166 Address Information

Description: Address information

O AN 1/55 Used

Page 194: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Invoice Foodservice - 810

July 2012 [V004010-2012 FS] 13Copyright 2012 - GS1 Canada

N4 Geographic Location Pos: 100 Max: 1Heading - Optional

Loop: N1 Elements: 4

User Option (Usage): UsedPurpose: To specify the geographic place of the named party

Element Summary: Ref Id Element Name Req Type Min/Max UsageN401 19 City Name

Description: Free-form text for city name

O AN 2/30 Used

N402 156 State or Province Code

Description: Code (StandardState/Province) as defined by appropriategovernment agency

O ID 2/2 Used

N403 116 Postal Code

Description: Code defining internationalpostal zone code excluding punctuationand blanks (zip code for United States)

O ID 3/15 Used

N404 26 Country Code

Description: Code identifying the countryUser Note 1: CA CanadaMX MexicoUS United States

User Note 1: CA CanadaMX MexicoUS United States

O ID 2/3 Used

Syntax Rules: 1. C0605 - If N406 is present, then N405 is required.

Comments: 1. A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location.2. N402 is required only if city name (N401) is in the U.S. or Canada.

Page 195: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Invoice Foodservice - 810

July 2012 [V004010-2012 FS] 14Copyright 2012 - GS1 Canada

ITD Terms of Sale/Deferred Termsof Sale

Pos: 130 Max: >1Heading - Optional

Loop: N/A Elements: 8

User Option (Usage): UsedPurpose: To specify terms of sale

Element Summary: Ref Id Element Name Req Type Min/Max UsageITD01 336 Terms Type Code

Description: Code identifying type ofpayment terms

O ID 2/2 Used

CodeList Summary (Total Codes: 65, Included: 4)Code Name05 Discount Not Applicable08 Basic Discount Offered09 Proximo14 Previously agreed upon

ITD02 333 Terms Basis Date Code

Description: Code identifying thebeginning of the terms period

O ID 1/2 Used

CodeList Summary (Total Codes: 17, Included: 4)Code Name2 Delivery Date3 Invoice Date4 Specified Date15 Receipt of Goods

ITD03 338 Terms Discount Percent

Description: Terms discount percentage,expressed as a percent, available to thepurchaser if an invoice is paid on orbefore the Terms Discount Due DateUser Note 1: The percent is sent with adecimal point only when needed, e.g., 10.5%is sent as ``10.5'', and 2% is sent as ``2''.

User Note 1: The percent is sent with adecimal point only when needed, e.g., 10.5%is sent as ``10.5'', and 2% is sent as ``2''.

O R 1/6 Used

ITD04 370 Terms Discount Due Date

Description: Date payment is due ifdiscount is to be earned expressed informat CCYYMMDD

C DT 8/8 Used

ITD05 351 Terms Discount Days Due

Description: Number of days in the termsdiscount period by which payment is dueif terms discount is earnedUser Note 1: The end of the term period isderived by adding this value to the beginningUser Note 1: The end of the term period isderived by adding this value to the beginning

C N0 1/3 Used

Page 196: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Invoice Foodservice - 810

Ref Id Element Name Req Type Min/Max Usage

July 2012 [V004010-2012 FS] 15Copyright 2012 - GS1 Canada

of the term period, as qualified by ITD02.of the term period, as qualified by ITD02.

ITD06 446 Terms Net Due Date

Description: Date when total invoiceamount becomes due expressed in formatCCYYMMDD

O DT 8/8 Used

ITD07 386 Terms Net Days

Description: Number of days until totalinvoice amount is due (discount notapplicable)User Note 1: The end of the term period isderived by adding this value to the beginningof the term period, as qualified by ITD02.

User Note 1: The end of the term period isderived by adding this value to the beginningof the term period, as qualified by ITD02.

O N0 1/3 Used

ITD08 362 Terms Discount Amount

Description: Total amount of termsdiscount

O N2 1/10 Used

Syntax Rules: 1. L03040513 - If ITD03 is present, then at least one of ITD04, ITD05 or ITD13 is required.2. L08040513 - If ITD08 is present, then at least one of ITD04, ITD05 or ITD13 is required.3. L091011 - If ITD09 is present, then at least one of ITD10 or ITD11 is required.

Semantics: 1. ITD15 is the percentage applied to a base amount used to determine a late payment charge.

Comments: 1. If the code in ITD01 is "04", then ITD07 or ITD09 is required and either ITD10 or ITD11 is required; if the code

in ITD01 is "05", then ITD06 or ITD07 is required.

Page 197: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Invoice Foodservice - 810

July 2012 [V004010-2012 FS] 16Copyright 2012 - GS1 Canada

DTM Date/Time Reference Pos: 140 Max: 10Heading - Optional

Loop: N/A Elements: 2

User Option (Usage): UsedPurpose: To specify pertinent dates and times

Element Summary: Ref Id Element Name Req Type Min/Max UsageDTM01 374 Date/Time Qualifier

Description: Code specifying type of dateor time, or both date and time

M ID 3/3 Must use

CodeList Summary (Total Codes: 1112, Included: 2)Code Name002 Delivery Requested011 Shipped

DTM02 373 Date

Description: Date expressed asCCYYMMDD

C DT 8/8 Must use

Syntax Rules: 1. R020305 - At least one of DTM02, DTM03 or DTM05 is required.2. C0403 - If DTM04 is present, then DTM03 is required.3. P0506 - If either DTM05 or DTM06 is present, then the other is required.

Page 198: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Invoice Foodservice - 810

July 2012 [V004010-2012 FS] 17Copyright 2012 - GS1 Canada

FOB F.O.B. Related Instructions Pos: 150 Max: 1Heading - Optional

Loop: N/A Elements: 3

User Option (Usage): UsedPurpose: To specify transportation instructions relating to shipment

Element Summary: Ref Id Element Name Req Type Min/Max UsageFOB01 146 Shipment Method of Payment

Description: Code identifying paymentterms for transportation charges

M ID 2/2 Must use

CodeList Summary (Total Codes: 28, Included: 3)Code NameCC CollectPB Customer Pick-up/BackhaulPP Prepaid (by Seller)

FOB02 309 Location Qualifier

Description: Code identifying type oflocation

C ID 1/2 Used

CodeList Summary (Total Codes: 172, Included: 2)Code NameDE Destination (Shipping)OR Origin (Shipping Point)

FOB03 352 Description

Description: A free-form description toclarify the related data elements and theircontentUser Note 1: Free-form name oftransportation responsibility locationUser Note 1: Free-form name oftransportation responsibility location

O AN 1/80 Used

Syntax Rules: 1. C0302 - If FOB03 is present, then FOB02 is required.2. C0405 - If FOB04 is present, then FOB05 is required.3. C0706 - If FOB07 is present, then FOB06 is required.4. C0809 - If FOB08 is present, then FOB09 is required.

Semantics: 1. FOB01 indicates which party will pay the carrier.2. FOB02 is the code specifying transportation responsibility location.3. FOB06 is the code specifying the title passage location.4. FOB08 is the code specifying the point at which the risk of loss transfers. This may be different than the

location specified in FOB02/FOB03 and FOB06/FOB07.

Page 199: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Invoice Foodservice - 810

July 2012 [V004010-2012 FS] 18Copyright 2012 - GS1 Canada

IT1 Baseline Item Data (Invoice) Pos: 010 Max: 1Detail - Optional

Loop: IT1 Elements: 5

User Option (Usage): UsedPurpose: To specify the basic and most frequently used line item data for the invoice and related transactions

Element Summary: Ref Id Element Name Req Type Min/Max UsageIT102 358 Quantity Invoiced

Description: Number of units invoiced(supplier units)

C R 1/10 Must use

IT103 355 Unit or Basis for Measurement Code

Description: Code specifying the units inwhich a value is being expressed, ormanner in which a measurement hasbeen taken

C ID 2/2 Must use

CodeList Summary (Total Codes: 794, Included: 12)Code NameBG BagBR BarrelCA CaseDR DrumEA EachGA GallonKG KilogramLB PoundLT LiterPA PailPL Pallet/Unit LoadTE Tote

IT104 212 Unit Price

Description: Price per unit of product,service, commodity, etc.User Note 1: The price is sent with adecimal point only when needed, e.g., $15.95would be sent as ``15.95'', and $29.00 wouldbe sent as ``29''.

To indicate free goods, use a single zero (0)with code NC as the value in IT105.

User Note 1: The price is sent with adecimal point only when needed, e.g., $15.95would be sent as ``15.95'', and $29.00 wouldbe sent as ``29''.

To indicate free goods, use a single zero (0)with code NC as the value in IT105.

C R 1/17 Must use

IT106 235 Product/Service ID Qualifier

Description: Code identifying thetype/source of the descriptive numberused in Product/Service ID (234)

C ID 2/2 Used

CodeList Summary (Total Codes: 477, Included: 1)

Page 200: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Invoice Foodservice - 810

July 2012 [V004010-2012 FS] 19Copyright 2012 - GS1 Canada

Code NameUK U.P.C./EAN Shipping Container Code (1-2-5-5-1)

Description: GTIN-14 A 14-digit GS1 Identification Key composed of an Indicator Digit, GS1 Company Prefix, ItemReference and Check Digit used to identify trade items SEE CODE SOURCE 41

IT107 234 Product/Service ID

Description: Identifying number for aproduct or service

C AN 1/48 Used

Syntax Rules: 1. P020304 - If either IT102, IT103 or IT104 are present, then the others are required.2. P0607 - If either IT106 or IT107 is present, then the other is required.3. P0809 - If either IT108 or IT109 is present, then the other is required.4. P1011 - If either IT110 or IT111 is present, then the other is required.5. P1213 - If either IT112 or IT113 is present, then the other is required.6. P1415 - If either IT114 or IT115 is present, then the other is required.7. P1617 - If either IT116 or IT117 is present, then the other is required.8. P1819 - If either IT118 or IT119 is present, then the other is required.9. P2021 - If either IT120 or IT121 is present, then the other is required.

10. P2223 - If either IT122 or IT123 is present, then the other is required.11. P2425 - If either IT124 or IT125 is present, then the other is required.

Semantics: 1. IT101 is the purchase order line item identification.

Comments: 1. Element 235/234 combinations should be interpreted to include products and/or services. See the Data

Dictionary for a complete list of IDs.2. IT106 through IT125 provide for ten different product/service IDs for each item. For example: Case, Color,

Drawing No., U.P.C. No., ISBN No., Model No., or SKU.

Page 201: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Invoice Foodservice - 810

July 2012 [V004010-2012 FS] 20Copyright 2012 - GS1 Canada

CTP Pricing Information Pos: 050 Max: 25Detail - Optional

Loop: IT1 Elements: 2

User Option (Usage): UsedPurpose: To specify pricing information

Element Summary: Ref Id Element Name Req Type Min/Max UsageCTP02 236 Price Identifier Code

Description: Code identifying pricingspecification

C ID 3/3 Must use

CodeList Summary (Total Codes: 164, Included: 1)Code NameUCP Unit cost price

User Note 1:User Note 1:Item list costItem list cost

CTP03 212 Unit Price

Description: Price per unit of product,service, commodity, etc.User Note 1: The price is sent with adecimal point only when needed, e.g., $15.95would be sent as ``15.95'', and $29.00 wouldbe sent as ``29''.

User Note 1: The price is sent with adecimal point only when needed, e.g., $15.95would be sent as ``15.95'', and $29.00 wouldbe sent as ``29''.

C R 1/17 Must use

Syntax Rules: 1. P0405 - If either CTP04 or CTP05 is present, then the other is required.2. C0607 - If CTP06 is present, then CTP07 is required.3. C0902 - If CTP09 is present, then CTP02 is required.4. C1002 - If CTP10 is present, then CTP02 is required.5. C1103 - If CTP11 is present, then CTP03 is required.

Semantics: 1. CTP07 is a multiplier factor to arrive at a final discounted price. A multiplier of .90 would be the factor if a 10%

discount is given.2. CTP08 is the rebate amount.

Comments: 1. See Figures Appendix for an example detailing the use of CTP03 and CTP04.2. See Figures Appendix for an example detailing the use of CTP03, CTP04 and CTP07.

Page 202: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Invoice Foodservice - 810

July 2012 [V004010-2012 FS] 21Copyright 2012 - GS1 Canada

PID Product/Item Description Pos: 060 Max: 1Detail - Optional

Loop: PID Elements: 3

User Option (Usage): UsedPurpose: To describe a product or process in coded or free-form format

Element Summary: Ref Id Element Name Req Type Min/Max UsagePID01 349 Item Description Type

Description: Code indicating the formatof a description

M ID 1/1 Must use

CodeList Summary (Total Codes: 3, Included: 1)Code NameF Free-form

User Note 1:User Note 1:The description will be found in PID05.The description will be found in PID05.

PID02 750 Product/Process Characteristic Code

Description: Code identifying the generalclass of a product or processcharacteristic

O ID 2/3 Used

CodeList Summary (Total Codes: 217, Included: 1)Code Name08 Product

PID05 352 Description

Description: A free-form description toclarify the related data elements and theircontent

C AN 1/80 Used

Syntax Rules: 1. C0403 - If PID04 is present, then PID03 is required.2. R0405 - At least one of PID04 or PID05 is required.3. C0703 - If PID07 is present, then PID03 is required.4. C0804 - If PID08 is present, then PID04 is required.5. C0905 - If PID09 is present, then PID05 is required.

Semantics: 1. Use PID03 to indicate the organization that publishes the code list being referred to.2. PID04 should be used for industry-specific product description codes.3. PID08 describes the physical characteristics of the product identified in PID04. A "Y" indicates that the

specified attribute applies to this item; an "N" indicates it does not apply. Any other value is indeterminate.4. PID09 is used to identify the language being used in PID05.

Comments: 1. If PID01 equals "F", then PID05 is used. If PID01 equals "S", then PID04 is used. If PID01 equals "X", then

both PID04 and PID05 are used.

Page 203: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Invoice Foodservice - 810

July 2012 [V004010-2012 FS] 22Copyright 2012 - GS1 Canada

2. Use PID06 when necessary to refer to the product surface or layer being described in the segment.3. PID07 specifies the individual code list of the agency specified in PID03.

Page 204: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Invoice Foodservice - 810

July 2012 [V004010-2012 FS] 23Copyright 2012 - GS1 Canada

PO4 Item Physical Details Pos: 100 Max: 1Detail - Optional

Loop: IT1 Elements: 4

User Option (Usage): UsedPurpose: To specify the physical qualities, packaging, weights, and dimensions relating to the item

Element Summary: Ref Id Element Name Req Type Min/Max UsagePO401 356 Pack

Description: The number of innercontainers, or number of eaches if thereare no inner containers, per outercontainer

O N0 1/6 Used

PO402 357 Size

Description: Size of supplier units inpack

C R 1/8 Used

PO403 355 Unit or Basis for Measurement Code

Description: Code specifying the units inwhich a value is being expressed, ormanner in which a measurement hasbeen taken

C ID 2/2 Used

CodeList Summary (Total Codes: 794, Included: 12)Code NameBG BagBR BarrelCA CaseDR DrumEA EachGA GallonKG KilogramLB PoundLT LiterPA PailPL Pallet/Unit LoadTE Tote

PO414 810 Inner Pack

Description: The number of eaches perinner container

O N0 1/6 Used

Syntax Rules: 1. P0203 - If either PO402 or PO403 is present, then the other is required.2. C0506 - If PO405 is present, then PO406 is required.3. P0607 - If either PO406 or PO407 is present, then the other is required.4. P0809 - If either PO408 or PO409 is present, then the other is required.5. C1013 - If PO410 is present, then PO413 is required.

Page 205: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Invoice Foodservice - 810

July 2012 [V004010-2012 FS] 24Copyright 2012 - GS1 Canada

6. C1113 - If PO411 is present, then PO413 is required.7. C1213 - If PO412 is present, then PO413 is required.8. L13101112 - If PO413 is present, then at least one of PO410, PO411 or PO412 is required.9. C1716 - If PO417 is present, then PO416 is required.

10. C1804 - If PO418 is present, then PO404 is required.

Semantics: 1. PO415 is used to indicate the relative layer of this package or range of packages within the layers of

packaging. Relative Position 1 (value R1) is the innermost package.2. PO416 is the package identifier or the beginning package identifier in a range of identifiers.3. PO417 is the ending package identifier in a range of identifiers.4. PO418 is the number of packages in this layer.

Comments: 1. PO403 - The "Unit or Basis for Measure Code" in this segment position is for purposes of defining the pack

(PO401) /size (PO402) measure which indicates the quantity in the inner pack unit. For example: If the cartoncontains 24 12-Ounce packages, it would be described as follows: Data element 356 = "24"; Data element357 = "12"; Data element 355 = "OZ".

2. PO413 defines the unit of measure for PO410, PO411, and PO412.

User Note 1:User Note 1:This segment is used to specify the packaging of the item in the case or carton. There may be two levels of packagingspecified. The first level is always specified by using PO401 (Pack). The first level may be actual items, e.g., consumer units,or it may be the number of smaller containers within the case. The second level, specified using PO414 (Inner Pack), is thenumber of eaches in each inner container when PO401 is the number of smaller containers within the case.

This segment can be used also to specify the weight and/or volume (cube) for the item by using PO406 and PO407, and/orPO408 and PO409.

This segment is used to specify the packaging of the item in the case or carton. There may be two levels of packagingspecified. The first level is always specified by using PO401 (Pack). The first level may be actual items, e.g., consumer units,or it may be the number of smaller containers within the case. The second level, specified using PO414 (Inner Pack), is thenumber of eaches in each inner container when PO401 is the number of smaller containers within the case.

This segment can be used also to specify the weight and/or volume (cube) for the item by using PO406 and PO407, and/orPO408 and PO409.

Page 206: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Invoice Foodservice - 810

July 2012 [V004010-2012 FS] 25Copyright 2012 - GS1 Canada

SAC Service, Promotion,Allowance, or ChargeInformation

Pos: 180 Max: 1Detail - Optional

Loop: SAC Elements: 15

User Option (Usage): UsedPurpose: To request or identify a service, promotion, allowance, or charge; to specify the amount or percentage forthe service, promotion, allowance, or charge

Element Summary: Ref Id Element Name Req Type Min/Max UsageSAC01 248 Allowance or Charge Indicator

Description: Code which indicates anallowance or charge for the servicespecified

M ID 1/1 Must use

CodeList Summary (Total Codes: 7, Included: 4)Code NameA AllowanceC ChargeN No Allowance or ChargeR Allowance Request

SAC02 1300 Service, Promotion, Allowance, orCharge Code

Description: Code identifying the service,promotion, allowance, or chargeUser Note 1: See FoodserviceImplementation Guidelines Appendix - DataElements

User Note 1: See FoodserviceImplementation Guidelines Appendix - DataElements

C ID 4/4 Used

CodeList Summary (Total Codes: 1053, Included: 5)Code NameD350 Goods and Services Credit AllowanceD360 Goods and Services Tax Charge

User Note 1:User Note 1:Provincal Tobacco Tax.Provincal Tobacco Tax.

H490 Subject To Tax On ResaleH770 Tax - State TaxH806 Tax Credit

User Note 1:User Note 1:Provincial Tax Credit.Provincial Tax Credit.

SAC03 559 Agency Qualifier Code

Description: Code identifying the agencyassigning the code values

C ID 2/2 Used

CodeList Summary (Total Codes: 176, Included: 1)

Page 207: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Invoice Foodservice - 810

July 2012 [V004010-2012 FS] 26Copyright 2012 - GS1 Canada

Code NameVI Voluntary Inter-Industry Commerce Standard (VICS) EDI

SAC04 1301 Agency Service, Promotion, Allowance,or Charge Code

Description: Agency maintained codeidentifying the service, promotion,allowance, or chargeUser Note 1: See FoodserviceImplementation Guidelines Appendix - DataElements

User Note 1: See FoodserviceImplementation Guidelines Appendix - DataElements

C AN 1/10 Used

SAC05 610 Amount

Description: Monetary amountUser Note 1: When SAC01 contains code Aor code C, then this data element is required.This will resolve any differences between thesender's and receiver's system calculations ofamounts, i.e., rounding errors whenallowances or charges are expressed inpercentages or rates.

User Note 1: When SAC01 contains code Aor code C, then this data element is required.This will resolve any differences between thesender's and receiver's system calculations ofamounts, i.e., rounding errors whenallowances or charges are expressed inpercentages or rates.

O N2 1/15 Used

SAC06 378 Allowance/Charge Percent Qualifier

Description: Code indicating on whatbasis allowance or charge percent iscalculated

C ID 1/1 Used

CodeList Summary (Total Codes: 11, Included: 7)Code Name1 Item List Cost2 Item Net Cost3 Discount/Gross

User Note 1:User Note 1:All allowances are off the gross price including cash discount.All allowances are off the gross price including cash discount.

4 Discount/NetUser Note 1:User Note 1:

All allowances are off the gross price. Cash discounts are off the net.All allowances are off the gross price. Cash discounts are off the net.

5 Base Price per UnitUser Note 1:User Note 1:

Line item discountLine item discount

6 Base Price Amount7 Base Price Amount Less Previous Discount

User Note 1:User Note 1:Declining balance methodDeclining balance method

SAC07 332 Percent

Description: Percent expressed as apercentUser Note 1: The percent is sent with adecimal point only when needed, e.g., 10.5%is sent as ``10.5'', and 2% is sent as ``2''.

User Note 1: The percent is sent with adecimal point only when needed, e.g., 10.5%is sent as ``10.5'', and 2% is sent as ``2''.

C R 1/6 Used

Page 208: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Invoice Foodservice - 810

Ref Id Element Name Req Type Min/Max Usage

July 2012 [V004010-2012 FS] 27Copyright 2012 - GS1 Canada

SAC08 118 Rate

Description: Rate expressed in thestandard monetary denomination for thecurrency specified

O R 1/9 Used

SAC09 355 Unit or Basis for Measurement Code

Description: Code specifying the units inwhich a value is being expressed, ormanner in which a measurement hasbeen taken

C ID 2/2 Used

CodeList Summary (Total Codes: 794, Included: 12)Code NameBG BagBR BarrelCA CaseDR DrumEA EachGA GallonKG KilogramLB PoundLT LiterPA PailPL Pallet/Unit LoadTE Tote

SAC10 380 Quantity

Description: Numeric value of quantity

C R 1/15 Used

SAC12 331 Allowance or Charge Method ofHandling Code

Description: Code indicating method ofhandling for an allowance or charge

O ID 2/2 Used

CodeList Summary (Total Codes: 22, Included: 6)Code Name01 Bill Back

User Note 1:User Note 1:The allowance or charge amount will be adjudicated as a separate item, i.e., a debit/creditmemo or a separate invoice. The amount will not be reflected in the invoice total amount.The allowance or charge amount will be adjudicated as a separate item, i.e., a debit/creditmemo or a separate invoice. The amount will not be reflected in the invoice total amount.

02 Off InvoiceUser Note 1:User Note 1:

The allowance or charge amount will be reflected in the total transaction amount, e.g.,Total Invoice Amount = Merchandise Price + Charges - Allowances.The allowance or charge amount will be reflected in the total transaction amount, e.g.,Total Invoice Amount = Merchandise Price + Charges - Allowances.

03 Vendor Check to CustomerUser Note 1:User Note 1:

The vendor will issue a check directly to the customer of the retailer, or end consumer, forthe allowance or charge amount. The amount is not reflected in the total invoice amount.The vendor will issue a check directly to the customer of the retailer, or end consumer, forthe allowance or charge amount. The amount is not reflected in the total invoice amount.

04 Credit Customer Account

Page 209: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Invoice Foodservice - 810

Code Name

July 2012 [V004010-2012 FS] 28Copyright 2012 - GS1 Canada

User Note 1:User Note 1:The retailer's account will be credited for the amount of the allowance or charge. Theamount is not reflected in the total invoice amount.The retailer's account will be credited for the amount of the allowance or charge. Theamount is not reflected in the total invoice amount.

05 Charge to be Paid by VendorUser Note 1:User Note 1:

The vendor is responsible for the allowance or charge amount. The exact method ofadjudication has been agreed to by the trading partners. The amount will not be reflectedin the total invoice amount.

The vendor is responsible for the allowance or charge amount. The exact method ofadjudication has been agreed to by the trading partners. The amount will not be reflectedin the total invoice amount.

06 Charge to be Paid by CustomerUser Note 1:User Note 1:

When the order/item is a direct ship to the customer, or end consumer of the retailer, theallowance or charge amount is the responsibility of the customer or end consumer. If it isnot a drop ship to the customer of the retailer, then the allowance or charge amount is theresponsibility of the retailer. The exact method of adjudication has been agreed to by thetrading partners. The amount will not be reflected in the total invoice amou

When the order/item is a direct ship to the customer, or end consumer of the retailer, theallowance or charge amount is the responsibility of the customer or end consumer. If it isnot a drop ship to the customer of the retailer, then the allowance or charge amount is theresponsibility of the retailer. The exact method of adjudication has been agreed to by thetrading partners. The amount will not be reflected in the total invoice amou

SAC13 127 Reference Identification

Description: Reference information asdefined for a particular Transaction Set oras specified by the ReferenceIdentification QualifierUser Note 1: Used for tax registrationnumber.User Note 1: Used for tax registrationnumber.

C AN 1/30 Used

SAC14 770 Option Number

Description: A unique number identifyingavailable promotion or allowance optionswhen more than one is offered

O AN 1/20 Used

SAC15 352 Description

Description: A free-form description toclarify the related data elements and theircontent

C AN 1/80 Used

SAC16 819 Language Code

Description: Code designating thelanguage used in text, from a standardcode list maintained by the InternationalStandards Organization (ISO 639)

O ID 2/3 Used

Syntax Rules: 1. R0203 - At least one of SAC02 or SAC03 is required.2. P0304 - If either SAC03 or SAC04 is present, then the other is required.3. P0607 - If either SAC06 or SAC07 is present, then the other is required.4. P0910 - If either SAC09 or SAC10 is present, then the other is required.5. C1110 - If SAC11 is present, then SAC10 is required.6. L130204 - If SAC13 is present, then at least one of SAC02 or SAC04 is required.7. C1413 - If SAC14 is present, then SAC13 is required.8. C1615 - If SAC16 is present, then SAC15 is required.

Semantics:

Page 210: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Invoice Foodservice - 810

July 2012 [V004010-2012 FS] 29Copyright 2012 - GS1 Canada

1. If SAC01 is "A" or "C", then at least one of SAC05, SAC07, or SAC08 is required.2. SAC05 is the total amount for the service, promotion, allowance, or charge.3. If SAC05 is present with SAC07 or SAC08, then SAC05 takes precedence.4. SAC08 is the allowance or charge rate per unit. 5. SAC10 and SAC11 is the quantity basis when the allowance or charge quantity is different from the purchase

order or invoice quantity.6. SAC10 and SAC11 used together indicate a quantity range, which could be a dollar amount, that is applicable

to service, promotion, allowance, or charge.7. SAC13 is used in conjunction with SAC02 or SAC04 to provide a specific reference number as identified by

the code used.8. SAC14 is used in conjunction with SAC13 to identify an option when there is more than one option of the

promotion.9. SAC16 is used to identify the language being used in SAC15.

Comments: 1. SAC04 may be used to uniquely identify the service, promotion, allowance, or charge. In addition, it may be

used in conjunction to further the code in SAC02.2. In some business applications, it is necessary to advise the trading partner of the actual dollar amount that a

particular allowance, charge, or promotion was based on to reduce ambiguity. This amount is commonlyreferred to as "Dollar Basis Amount". It is represented in the SAC segment in SAC10 using the qualifier "DO" -Dollars in SAC09.

Page 211: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Invoice Foodservice - 810

July 2012 [V004010-2012 FS] 30Copyright 2012 - GS1 Canada

TDS Total Monetary ValueSummary

Pos: 010 Max: 1Summary - Mandatory

Loop: N/A Elements: 4

User Option (Usage): Must usePurpose: To specify the total invoice discounts and amounts

Element Summary: Ref Id Element Name Req Type Min/Max UsageTDS01 610 Amount

Description: Monetary amount

M N2 1/15 Must use

TDS02 610 Amount

Description: Monetary amount

O N2 1/15 Used

TDS03 610 Amount

Description: Monetary amount

O N2 1/15 Used

TDS04 610 Amount

Description: Monetary amount

O N2 1/15 Used

Semantics: 1. TDS01 is the total amount of invoice (including charges, less allowances) before terms discount (if discount is

applicable).2. TDS02 indicates the amount upon which the terms discount amount is calculated.3. TDS03 is the amount of invoice due if paid by terms discount due date (total invoice or installment amount

less cash discount). 4. TDS04 indicates the total amount of terms discount.

Comments: 1. TDS02 is required if the dollar value subject to discount is not equal to the dollar value of TDS01.

Page 212: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Invoice Foodservice - 810

July 2012 [V004010-2012 FS] 31Copyright 2012 - GS1 Canada

SAC Service, Promotion,Allowance, or ChargeInformation

Pos: 040 Max: 1Summary - Optional

Loop: SAC Elements: 15

User Option (Usage): UsedPurpose: To request or identify a service, promotion, allowance, or charge; to specify the amount or percentage forthe service, promotion, allowance, or charge

Element Summary: Ref Id Element Name Req Type Min/Max UsageSAC01 248 Allowance or Charge Indicator

Description: Code which indicates anallowance or charge for the servicespecified

M ID 1/1 Must use

CodeList Summary (Total Codes: 7, Included: 4)Code NameA AllowanceC ChargeN No Allowance or ChargeR Allowance Request

SAC02 1300 Service, Promotion, Allowance, orCharge Code

Description: Code identifying the service,promotion, allowance, or chargeUser Note 1: See FoodserviceImplementation Guidelines Appendix - DataElements

User Note 1: See FoodserviceImplementation Guidelines Appendix - DataElements

C ID 4/4 Used

CodeList Summary (Total Codes: 1053, Included: 5)Code NameD350 Goods and Services Credit AllowanceD360 Goods and Services Tax Charge

User Note 1:User Note 1:Provincal Tobacco Tax.Provincal Tobacco Tax.

H490 Subject To Tax On ResaleH770 Tax - State TaxH806 Tax Credit

User Note 1:User Note 1:Provincial Tax Credit.Provincial Tax Credit.

SAC03 559 Agency Qualifier Code

Description: Code identifying the agencyassigning the code values

C ID 2/2 Used

CodeList Summary (Total Codes: 176, Included: 1)

Page 213: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Invoice Foodservice - 810

July 2012 [V004010-2012 FS] 32Copyright 2012 - GS1 Canada

Code NameVI Voluntary Inter-Industry Commerce Standard (VICS) EDI

SAC04 1301 Agency Service, Promotion, Allowance,or Charge Code

Description: Agency maintained codeidentifying the service, promotion,allowance, or charge

C AN 1/10 Used

SAC05 610 Amount

Description: Monetary amountUser Note 1: When SAC01 contains code Aor code C, then this data element is required.This will resolve any differences between thesender's and receiver's system calculations ofamounts, i.e., rounding errors whenallowances or charges are expressed inpercentages or rates.

User Note 1: When SAC01 contains code Aor code C, then this data element is required.This will resolve any differences between thesender's and receiver's system calculations ofamounts, i.e., rounding errors whenallowances or charges are expressed inpercentages or rates.

O N2 1/15 Used

SAC06 378 Allowance/Charge Percent Qualifier

Description: Code indicating on whatbasis allowance or charge percent iscalculated

C ID 1/1 Used

CodeList Summary (Total Codes: 11, Included: 6)Code Name1 Item List Cost2 Item Net Cost3 Discount/Gross

User Note 1:User Note 1:All allowances are off the gross price including cash discount.All allowances are off the gross price including cash discount.

4 Discount/NetUser Note 1:User Note 1:

All allowances are off the gross price. Cash discounts are off the net.All allowances are off the gross price. Cash discounts are off the net.

5 Base Price per UnitUser Note 1:User Note 1:

Line item discountLine item discount

7 Base Price Amount Less Previous DiscountUser Note 1:User Note 1:

Declining balance methodDeclining balance method

SAC07 332 Percent

Description: Percent expressed as apercentUser Note 1: The percent is sent with adecimal point only when needed, e.g., 10.5%is sent as ``10.5'', and 2% is sent as ``2''.

User Note 1: The percent is sent with adecimal point only when needed, e.g., 10.5%is sent as ``10.5'', and 2% is sent as ``2''.

C R 1/6 Used

SAC08 118 Rate

Description: Rate expressed in thestandard monetary denomination for the

O R 1/9 Used

Page 214: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Invoice Foodservice - 810

Ref Id Element Name Req Type Min/Max Usage

July 2012 [V004010-2012 FS] 33Copyright 2012 - GS1 Canada

currency specified

SAC09 355 Unit or Basis for Measurement Code

Description: Code specifying the units inwhich a value is being expressed, ormanner in which a measurement hasbeen taken

C ID 2/2 Used

CodeList Summary (Total Codes: 794, Included: 12)Code NameBG BagBR BarrelCA CaseDR DrumEA EachGA GallonKG KilogramLB PoundLT LiterPA PailPL Pallet/Unit LoadTE Tote

SAC10 380 Quantity

Description: Numeric value of quantity

C R 1/15 Used

SAC12 331 Allowance or Charge Method ofHandling Code

Description: Code indicating method ofhandling for an allowance or charge

O ID 2/2 Used

CodeList Summary (Total Codes: 22, Included: 6)Code Name01 Bill Back

User Note 1:User Note 1:The allowance or charge amount will be adjudicated as a separate item, i.e., a debit/creditmemo or a separate invoice. The amount will not be reflected in the invoice total amount.The allowance or charge amount will be adjudicated as a separate item, i.e., a debit/creditmemo or a separate invoice. The amount will not be reflected in the invoice total amount.

02 Off InvoiceUser Note 1:User Note 1:

The allowance or charge amount will be reflected in the total transaction amount, e.g.,Total Invoice Amount = Merchandise Price + Charges - Allowances.The allowance or charge amount will be reflected in the total transaction amount, e.g.,Total Invoice Amount = Merchandise Price + Charges - Allowances.

03 Vendor Check to CustomerUser Note 1:User Note 1:

The vendor will issue a check directly to the customer of the retailer, or end consumer, forthe allowance or charge amount. The amount is not reflected in the total invoice amount.The vendor will issue a check directly to the customer of the retailer, or end consumer, forthe allowance or charge amount. The amount is not reflected in the total invoice amount.

04 Credit Customer AccountUser Note 1:User Note 1:

The retailer's account will be credited for the amount of the allowance or charge. Theamount is not reflected in the total invoice amount.The retailer's account will be credited for the amount of the allowance or charge. Theamount is not reflected in the total invoice amount.

Page 215: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Invoice Foodservice - 810

Code Name

July 2012 [V004010-2012 FS] 34Copyright 2012 - GS1 Canada

05 Charge to be Paid by VendorUser Note 1:User Note 1:

The vendor is responsible for the allowance or charge amount. The exact method ofadjudication has been agreed to by the trading partners. The amount will not be reflectedin the total invoice amount.

The vendor is responsible for the allowance or charge amount. The exact method ofadjudication has been agreed to by the trading partners. The amount will not be reflectedin the total invoice amount.

06 Charge to be Paid by CustomerUser Note 1:User Note 1:

When the order/item is a direct ship to the customer, or end consumer of the retailer, theallowance or charge amount is the responsibility of the customer or end consumer. If it isnot a drop ship to the customer of the retailer, then the allowance or charge amount is theresponsibility of the retailer. The exact method of adjudication has been agreed to by thetrading partners. The amount will not be reflected in the total invoice amou

When the order/item is a direct ship to the customer, or end consumer of the retailer, theallowance or charge amount is the responsibility of the customer or end consumer. If it isnot a drop ship to the customer of the retailer, then the allowance or charge amount is theresponsibility of the retailer. The exact method of adjudication has been agreed to by thetrading partners. The amount will not be reflected in the total invoice amou

SAC13 127 Reference Identification

Description: Reference information asdefined for a particular Transaction Set oras specified by the ReferenceIdentification QualifierUser Note 1: Used for tax registration.User Note 1: Used for tax registration.

C AN 1/30 Used

SAC14 770 Option Number

Description: A unique number identifyingavailable promotion or allowance optionswhen more than one is offered

O AN 1/20 Used

SAC15 352 Description

Description: A free-form description toclarify the related data elements and theircontent

C AN 1/80 Used

SAC16 819 Language Code

Description: Code designating thelanguage used in text, from a standardcode list maintained by the InternationalStandards Organization (ISO 639)

O ID 2/3 Used

Syntax Rules: 1. R0203 - At least one of SAC02 or SAC03 is required.2. P0304 - If either SAC03 or SAC04 is present, then the other is required.3. P0607 - If either SAC06 or SAC07 is present, then the other is required.4. P0910 - If either SAC09 or SAC10 is present, then the other is required.5. C1110 - If SAC11 is present, then SAC10 is required.6. L130204 - If SAC13 is present, then at least one of SAC02 or SAC04 is required.7. C1413 - If SAC14 is present, then SAC13 is required.8. C1615 - If SAC16 is present, then SAC15 is required.

Semantics: 1. If SAC01 is "A" or "C", then at least one of SAC05, SAC07, or SAC08 is required.2. SAC05 is the total amount for the service, promotion, allowance, or charge.3. If SAC05 is present with SAC07 or SAC08, then SAC05 takes precedence.

Page 216: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Invoice Foodservice - 810

July 2012 [V004010-2012 FS] 35Copyright 2012 - GS1 Canada

4. SAC08 is the allowance or charge rate per unit. 5. SAC10 and SAC11 is the quantity basis when the allowance or charge quantity is different from the purchase

order or invoice quantity.6. SAC10 and SAC11 used together indicate a quantity range, which could be a dollar amount, that is applicable

to service, promotion, allowance, or charge.7. SAC13 is used in conjunction with SAC02 or SAC04 to provide a specific reference number as identified by

the code used.8. SAC14 is used in conjunction with SAC13 to identify an option when there is more than one option of the

promotion.9. SAC16 is used to identify the language being used in SAC15.

Comments: 1. SAC04 may be used to uniquely identify the service, promotion, allowance, or charge. In addition, it may be

used in conjunction to further the code in SAC02.2. In some business applications, it is necessary to advise the trading partner of the actual dollar amount that a

particular allowance, charge, or promotion was based on to reduce ambiguity. This amount is commonlyreferred to as "Dollar Basis Amount". It is represented in the SAC segment in SAC10 using the qualifier "DO" -Dollars in SAC09.

Page 217: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Invoice Foodservice - 810

July 2012 [V004010-2012 FS] 36Copyright 2012 - GS1 Canada

ISS Invoice Shipment Summary Pos: 060 Max: 1Summary - Optional

Loop: ISS Elements: 4

User Option (Usage): UsedPurpose: To specify summary details of total items shipped in terms of quantity, weight, and volume

Element Summary: Ref Id Element Name Req Type Min/Max UsageISS01 382 Number of Units Shipped

Description: Numeric value of unitsshipped in manufacturer's shipping unitsfor a line item or transaction set

C R 1/10 Used

ISS02 355 Unit or Basis for Measurement Code

Description: Code specifying the units inwhich a value is being expressed, ormanner in which a measurement hasbeen taken

C ID 2/2 Used

CodeList Summary (Total Codes: 794, Included: 12)Code NameBG BagBR BarrelCA CaseDR DrumEA EachGA GallonKG KilogramLB PoundLT LiterPA PailPL Pallet/Unit LoadTE Tote

ISS03 81 Weight

Description: Numeric value of weight

C R 1/10 Used

ISS04 355 Unit or Basis for Measurement Code

Description: Code specifying the units inwhich a value is being expressed, ormanner in which a measurement hasbeen takenUser Note 1: See Section III for code list.User Note 1: See Section III for code list.

C ID 2/2 Used

CodeList Summary (Total Codes: 794, Included: 2)Code NameKG KilogramLB Pound

Syntax Rules:

Page 218: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Invoice Foodservice - 810

July 2012 [V004010-2012 FS] 37Copyright 2012 - GS1 Canada

1. R010305 - At least one of ISS01, ISS03 or ISS05 is required.2. P0102 - If either ISS01 or ISS02 is present, then the other is required.3. P0304 - If either ISS03 or ISS04 is present, then the other is required.4. P0506 - If either ISS05 or ISS06 is present, then the other is required.

Semantics: 1. ISS07 is the quantity of third party pallets.2. ISS08 is the gross weight of third party pallets in pounds.

Page 219: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Invoice Foodservice - 810

July 2012 [V004010-2012 FS] 38Copyright 2012 - GS1 Canada

CTT Transaction Totals Pos: 070 Max: 1Summary - Optional

Loop: N/A Elements: 1

User Option (Usage): UsedPurpose: To transmit a hash total for a specific element in the transaction set

Element Summary: Ref Id Element Name Req Type Min/Max UsageCTT01 354 Number of Line Items

Description: Total number of line items inthe transaction setUser Note 1: The number of IT1 segmentspresent in the transaction setUser Note 1: The number of IT1 segmentspresent in the transaction set

M N0 1/6 Must use

Syntax Rules: 1. P0304 - If either CTT03 or CTT04 is present, then the other is required.2. P0506 - If either CTT05 or CTT06 is present, then the other is required.

Comments: 1. This segment is intended to provide hash totals to validate transaction completeness and correctness.

Page 220: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Invoice Foodservice - 810

July 2012 [V004010-2012 FS] 39Copyright 2012 - GS1 Canada

SE Transaction Set Trailer Pos: 080 Max: 1Summary - Mandatory

Loop: N/A Elements: 2

User Option (Usage): Must usePurpose: To indicate the end of the transaction set and provide the count of the transmitted segments (including thebeginning (ST) and ending (SE) segments)

Element Summary: Ref Id Element Name Req Type Min/Max UsageSE01 96 Number of Included Segments

Description: Total number of segmentsincluded in a transaction set including STand SE segments

M N0 1/10 Must use

SE02 329 Transaction Set Control Number

Description: Identifying control numberthat must be unique within the transactionset functional group assigned by theoriginator for a transaction setUser Note 1: This must be the same numberas is in the ST segment (ST02) for thetransaction set.

User Note 1: This must be the same numberas is in the ST segment (ST02) for thetransaction set.

M AN 4/9 Must use

Comments: 1. SE is the last segment of each transaction set.

Page 221: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

820 PaymentOrder/Remittance Advice

Foodservice Foodservice EDI

Version: 4010-2012 FS Final

Author: GS1 Canada TechnicalStandards Work GroupFoodservice

Publication: 7/1/2012 Notes: For Implementation

December 2012

Page 222: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Payment Order/Remittance AdviceFoodservice - 820

July 2012 [V004010-2012 FS] iCopyright 2012 - GS1 Canada

Table of Contents

820 Payment Order/Remittance Advice Foodservice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>ST Transaction Set Header . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>BPR Beginning Segment for Payment Order/Remittance Advice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>TRN Trace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>CUR Currency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>REF Reference Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>DTM Date/Time Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>N1 Party Identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>N2 Additional Name Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>N3 Party Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>N4 Geographic Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>ENT Entity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>ADX Adjustment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>REF Reference Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>RMR Remittance Advice Accounts Receivable Open Item Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>DTM Date/Time Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>ADX Adjustment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>SE Transaction Set Trailer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>

. . . . . 1. . . . . 3. . . . . 4. . . . . 7. . . . . 8. . . . . 9. . . . 10. . . . 11. . . . 12. . . . 13. . . . 14. . . . 15. . . . 16. . . . 18. . . . 19. . . . 21. . . . 22. . . . 24

Page 223: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Payment Order/Remittance AdviceFoodservice - 820

July 2012 [V004010-2012 FS] 1Copyright 2012 - GS1 Canada

820 Payment Order/Remittance AdviceFoodserviceFunctional Group=RA

Purpose: This X12 Transaction Set contains the format and establishes the data contents of the PaymentOrder/Remittance Advice Transaction Set (820) for use within the context of an Electronic Data Interchange (EDI)environment. The transaction set can be used to make a payment, send a remittance advice, or make a paymentand send a remittance advice.This transaction set can be an order to a financial institution to make a payment to apayee. It can also be a remittance advice identifying the detail needed to perform cash application to the payee'saccounts receivable system. The remittance advice can go directly from payer to payee, through a financialinstitution, or through a third party agent.

Heading:Pos Id Segment Name Req Max Use Repeat Notes Usage0100 ST Transaction Set Header M 1 Must use0200 BPR Beginning Segment for

Payment Order/RemittanceAdvice

M 1 Must use

0350 TRN Trace O 1 C1/0350 Used0400 CUR Currency O 1 C1/0400 Used0500 REF Reference Information O >1 Used0600 DTM Date/Time Reference O >1 Used

LOOP ID - N1 >1 C1/0700L LOOP ID - N1 >1 C1/0700L

0700 N1 Party Identification O 1 C1/0700 Used0800 N2 Additional Name

InformationO >1 Used

0900 N3 Party Location O >1 Used1000 N4 Geographic Location O 1 Used

Detail:Pos Id Segment Name Req Max Use Repeat Notes Usage

LOOP ID - ENT >1 CN2/0100L

LOOP ID - ENT >1 CN2/0100L

0100 ENT Entity O 1 CN2/0100 Used LOOP ID - ADX >1 C2/0800L LOOP ID - ADX >1 C2/0800L

0800 ADX Adjustment O 1 C2/0800 Used LOOP ID - REF >1 LOOP ID - REF >1

1100 REF Reference Information O 1 Used

LOOP ID - RMR >1 C2/1500L LOOP ID - RMR >1 C2/1500L

1500 RMR Remittance AdviceAccounts Receivable OpenItem Reference

O 1 C2/1500 Used

1800 DTM Date/Time Reference O >1 Used LOOP ID - ADX >1 C2/2100L LOOP ID - ADX >1 C2/2100L

2100 ADX Adjustment O 1 C2/2100 Used

Summary:

Page 224: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Payment Order/Remittance AdviceFoodservice - 820

July 2012 [V004010-2012 FS] 2Copyright 2012 - GS1 Canada

Pos Id Segment Name Req Max Use Repeat Notes Usage0100 SE Transaction Set Trailer M 1 Must use

Notes: 2/0100L The ENT loop is for vendor or consumer third party consolidated payments.2/0100 The ENT loop is for vendor or consumer third party consolidated payments.

Comments: 1/0350 The TRN segment is used to uniquely identify a payment order/remittance advice.1/0400 The CUR segment does not initiate a foreign exchange transaction.1/0700L The N1 loop allows for name/address information for the payer and payee which would be utilized to

address remittance(s) for delivery.1/0700 The N1 loop allows for name/address information for the payer and payee which would be utilized to

address remittance(s) for delivery.2/0100L ENT09 may contain the payee's accounts receivable customer number.2/0100 ENT09 may contain the payee's accounts receivable customer number.2/0800L This ADX loop contains adjustment items which are not netted to an RMR segment in this transaction

set.2/0800 This ADX loop contains adjustment items which are not netted to an RMR segment in this transaction

set.2/1500L Loop RMR is for open items being referenced or for payment on account.2/1500 Loop RMR is for open items being referenced or for payment on account.2/2100L This ADX loop can only contain adjustment information for the immediately preceding RMR segment and

affects the amount (RMR04) calculation. If this adjustment amount is not netted to the immediatelypreceding RMR, use the outer ADX loop (position 080).

2/2100 This ADX loop can only contain adjustment information for the immediately preceding RMR segment andaffects the amount (RMR04) calculation. If this adjustment amount is not netted to the immediatelypreceding RMR, use the outer ADX loop (position 080).

Page 225: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Payment Order/Remittance AdviceFoodservice - 820

July 2012 [V004010-2012 FS] 3Copyright 2012 - GS1 Canada

ST Transaction Set Header Pos: 0100 Max: 1Heading - Mandatory

Loop: N/A Elements: 2

User Option (Usage): Must usePurpose: To indicate the start of a transaction set and to assign a control number

Element Summary: Ref Id Element Name Req Type Min/Max UsageST01 143 Transaction Set Identifier Code

Description: Code uniquely identifying aTransaction Set

M ID 3/3 Must use

CodeList Summary (Total Codes: 319, Included: 1)Code Name820 Payment Order/Remittance Advice

ST02 329 Transaction Set Control Number

Description: Identifying control numberthat must be unique within the transactionset functional group assigned by theoriginator for a transaction set

M AN 4/9 Must use

Semantics: 1. The transaction set identifier (ST01) is used by the translation routines of the interchange partners to select

the appropriate transaction set definition (e.g., 810 selects the Invoice Transaction Set).2. The implementation convention reference (ST03) is used by the translation routines of the interchange

partners to select the appropriate implementation convention to match the transaction set definition. Whenused, this implementation convention reference takes precedence over the implementation referencespecified in the GS08.

Page 226: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Payment Order/Remittance AdviceFoodservice - 820

July 2012 [V004010-2012 FS] 4Copyright 2012 - GS1 Canada

BPR Beginning Segment forPayment Order/RemittanceAdvice

Pos: 0200 Max: 1Heading - Mandatory

Loop: N/A Elements: 15

User Option (Usage): Must usePurpose: To indicate the beginning of a Payment Order/Remittance Advice Transaction Set and total paymentamount, or to enable related transfer of funds and/or information from payer to payee to occur

Element Summary: Ref Id Element Name Req Type Min/Max UsageBPR01 305 Transaction Handling Code

Description: Code designating the actionto be taken by all parties

M ID 1/2 Must use

CodeList Summary (Total Codes: 23, Included: 1)Code NameI Remittance Information Only

BPR02 782 Monetary Amount

Description: Monetary amount

M R 1/18 Must use

BPR03 478 Credit/Debit Flag Code

Description: Code indicating whetheramount is a credit or debit

M ID 1/1 Must use

CodeList Summary (Total Codes: 2, Included: 2)Code NameC CreditD Debit

BPR04 591 Payment Method Code

Description: Code identifying the methodfor the movement of payment instructions

M ID 3/3 Must use

CodeList Summary (Total Codes: 54, Included: 1)Code NameCHK Check

BPR05 812 Payment Format Code

Description: Code identifying thepayment format to be used

O ID 1/10 Used

CodeList Summary (Total Codes: 29, Included: 1)Code NamePBC Commercial/Corporate Check

BPR06 506 (DFI) ID Number Qualifier

Description: Code identifying the type ofidentification number of Depository

X ID 2/2 Used

Page 227: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Payment Order/Remittance AdviceFoodservice - 820

Ref Id Element Name Req Type Min/Max Usage

July 2012 [V004010-2012 FS] 5Copyright 2012 - GS1 Canada

Financial Institution (DFI)

CodeList Summary (Total Codes: 5, Included: 4)Code Name01 ABA Transit Routing Number Including Check Digits (9 digits)02 Swift Identification (8 or 11 characters)03 CHIPS (3 or 4 digits)04 Canadian Bank Branch and Institution Number

BPR07 507 (DFI) Identification Number

Description: Depository FinancialInstitution (DFI) identification number

X AN 3/12 Used

BPR08 569 Account Number Qualifier

Description: Code indicating the type ofaccount

O ID 1/3 Used

CodeList Summary (Total Codes: 48, Included: 1)Code NameDA Demand Deposit

BPR09 508 Account Number

Description: Account number assigned

X AN 1/35 Used

BPR10 509 Originating Company Identifier

Description: A unique identifierdesignating the company initiating thefunds transfer instructions, businesstransaction or assigning trackingreference identification.User Note 1: Use GS1 Global LocationNumber (GLN) 13 digitsUser Note 1: Use GS1 Global LocationNumber (GLN) 13 digits

O AN 10/10 Used

BPR12 506 (DFI) ID Number Qualifier

Description: Code identifying the type ofidentification number of DepositoryFinancial Institution (DFI)

X ID 2/2 Used

CodeList Summary (Total Codes: 5, Included: 4)Code Name01 ABA Transit Routing Number Including Check Digits (9 digits)02 Swift Identification (8 or 11 characters)03 CHIPS (3 or 4 digits)04 Canadian Bank Branch and Institution Number

BPR13 507 (DFI) Identification Number

Description: Depository FinancialInstitution (DFI) identification number

X AN 3/12 Used

BPR14 569 Account Number Qualifier

Description: Code indicating the type ofaccount

O ID 1/3 Used

Page 228: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Payment Order/Remittance AdviceFoodservice - 820

Ref Id Element Name Req Type Min/Max Usage

July 2012 [V004010-2012 FS] 6Copyright 2012 - GS1 Canada

CodeList Summary (Total Codes: 48, Included: 1)Code NameDA Demand Deposit

BPR15 508 Account Number

Description: Account number assigned

X AN 1/35 Used

BPR16 373 Date

Description: Date expressed asCCYYMMDD where CC represents thefirst two digits of the calendar year

O DT 8/8 Used

Syntax Rules: 1. P0607 - If either BPR06 or BPR07 is present, then the other is required.2. C0809 - If BPR08 is present, then BPR09 is required.3. P1213 - If either BPR12 or BPR13 is present, then the other is required.4. C1415 - If BPR14 is present, then BPR15 is required.5. P1819 - If either BPR18 or BPR19 is present, then the other is required.6. C2021 - If BPR20 is present, then BPR21 is required.

Semantics: 1. BPR02 specifies the payment amount.2. When using this transaction set to initiate a payment, all or some of BPR06 through BPR16 may be required,

depending on the conventions of the specific financial channel being used.3. BPR06 and BPR07 relate to the originating depository financial institution (ODFI).4. BPR08 is a code identifying the type of bank account or other financial asset. 5. BPR09 is the account of the company originating the payment. This account may be debited or credited

depending on the type of payment order.6. BPR10 shall be mutually established between the originating depository financial institution (ODFI) and the

company originating the payment.7. BPR12 and BPR13 relate to the receiving depository financial institution (RDFI).8. BPR14 is a code identifying the type of bank account or other financial asset.9. BPR15 is the account number of the receiving company to be debited or credited with the payment order.

10. BPR16 is the date the originating company intends for the transaction to be settled (i.e., Payment EffectiveDate).

11. BPR17 is a code identifying the business reason for this payment.12. BPR18, BPR19, BPR20 and BPR21, if used, identify a third bank identification number and account to be

used for return items only.13. BPR20 is a code identifying the type of bank account or other financial asset.

Page 229: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Payment Order/Remittance AdviceFoodservice - 820

July 2012 [V004010-2012 FS] 7Copyright 2012 - GS1 Canada

TRN Trace Pos: 0350 Max: 1Heading - Optional

Loop: N/A Elements: 2

User Option (Usage): UsedPurpose: To uniquely identify a transaction to an application

Element Summary: Ref Id Element Name Req Type Min/Max UsageTRN01 481 Trace Type Code

Description: Code identifying whichtransaction is being referenced

M ID 1/2 Must use

CodeList Summary (Total Codes: 3, Included: 1)Code Name1 Current Transaction Trace Numbers

TRN02 127 Reference Identification

Description: Reference information asdefined for a particular Transaction Set oras specified by the ReferenceIdentification Qualifier

M AN 1/80 Must use

Semantics: 1. TRN02 provides unique identification for the transaction.2. TRN03 identifies an organization.3. TRN04 identifies a further subdivision within the organization.

Page 230: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Payment Order/Remittance AdviceFoodservice - 820

July 2012 [V004010-2012 FS] 8Copyright 2012 - GS1 Canada

CUR Currency Pos: 0400 Max: 1Heading - Optional

Loop: N/A Elements: 2

User Option (Usage): UsedPurpose: To specify the currency (dollars, pounds, francs, etc.) used in a transaction

Element Summary: Ref Id Element Name Req Type Min/Max UsageCUR01 98 Entity Identifier Code

Description: Code identifying anorganizational entity, a physical location,property or an individual

M ID 2/3 Must use

CodeList Summary (Total Codes: 1524, Included: 1)Code NamePR Payer

CUR02 100 Currency Code

Description: Code (Standard ISO) forcountry in whose currency the chargesare specified

M ID 3/3 Must use

Syntax Rules: 1. C0807 - If CUR08 is present, then CUR07 is required.2. C0907 - If CUR09 is present, then CUR07 is required.3. L101112 - If CUR10 is present, then at least one of CUR11 or CUR12 is required.4. C1110 - If CUR11 is present, then CUR10 is required.5. C1210 - If CUR12 is present, then CUR10 is required.6. L131415 - If CUR13 is present, then at least one of CUR14 or CUR15 is required.7. C1413 - If CUR14 is present, then CUR13 is required.8. C1513 - If CUR15 is present, then CUR13 is required.9. L161718 - If CUR16 is present, then at least one of CUR17 or CUR18 is required.

10. C1716 - If CUR17 is present, then CUR16 is required.11. C1816 - If CUR18 is present, then CUR16 is required.12. L192021 - If CUR19 is present, then at least one of CUR20 or CUR21 is required.13. C2019 - If CUR20 is present, then CUR19 is required.14. C2119 - If CUR21 is present, then CUR19 is required.

Comments: 1. See Figures Appendix for examples detailing the use of the CUR segment.

Page 231: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Payment Order/Remittance AdviceFoodservice - 820

July 2012 [V004010-2012 FS] 9Copyright 2012 - GS1 Canada

REF Reference Information Pos: 0500 Max: >1Heading - Optional

Loop: N/A Elements: 2

User Option (Usage): UsedPurpose: To specify identifying information

Element Summary: Ref Id Element Name Req Type Min/Max UsageREF01 128 Reference Identification Qualifier

Description: Code qualifying theReference Identification

M ID 2/3 Must use

CodeList Summary (Total Codes: 1813, Included: 1)Code NameCK Check Number

REF02 127 Reference Identification

Description: Reference information asdefined for a particular Transaction Set oras specified by the ReferenceIdentification Qualifier

X AN 1/80 Used

Syntax Rules: 1. R0203 - At least one of REF02 or REF03 is required.

Semantics: 1. REF04 contains data relating to the value cited in REF02.

Page 232: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Payment Order/Remittance AdviceFoodservice - 820

July 2012 [V004010-2012 FS] 10Copyright 2012 - GS1 Canada

DTM Date/Time Reference Pos: 0600 Max: >1Heading - Optional

Loop: N/A Elements: 2

User Option (Usage): UsedPurpose: To specify pertinent dates and times

Element Summary: Ref Id Element Name Req Type Min/Max UsageDTM01 374 Date/Time Qualifier

Description: Code specifying type of dateor time, or both date and time

M ID 3/3 Must use

CodeList Summary (Total Codes: 1307, Included: 1)Code Name007 Effective

DTM02 373 Date

Description: Date expressed asCCYYMMDD where CC represents thefirst two digits of the calendar year

X DT 8/8 Used

Syntax Rules: 1. R020305 - At least one of DTM02, DTM03 or DTM05 is required.2. C0403 - If DTM04 is present, then DTM03 is required.3. P0506 - If either DTM05 or DTM06 is present, then the other is required.

Page 233: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Payment Order/Remittance AdviceFoodservice - 820

July 2012 [V004010-2012 FS] 11Copyright 2012 - GS1 Canada

N1 Party Identification Pos: 0700 Max: 1Heading - Optional

Loop: N1 Elements: 4

User Option (Usage): UsedPurpose: To identify a party by type of organization, name, and code

Element Summary: Ref Id Element Name Req Type Min/Max UsageN101 98 Entity Identifier Code

Description: Code identifying anorganizational entity, a physical location,property or an individual

M ID 2/3 Must use

CodeList Summary (Total Codes: 1524, Included: 1)Code NamePR Payer

N102 93 Name

Description: Free-form name

X AN 1/60 Used

N103 66 Identification Code Qualifier

Description: Code designating thesystem/method of code structure used forIdentification Code (67)

X ID 1/2 Used

CodeList Summary (Total Codes: 254, Included: 2)Code Name9 D-U-N-S+4, D-U-N-S Number with Four Character SuffixUL Global Location Number (GLN)

Description: Global Location Number (GLN) (Revised name)

A globally unique 13 digit code used for the identification of any physical or legal locationthat needs to be uniquely identified for use in the supply chain. A GS1 identification key

SEE CODE SOURCE 583

N104 67 Identification Code

Description: Code identifying a party orother code

X AN 2/80 Used

Syntax Rules: 1. R0203 - At least one of N102 or N103 is required.2. P0304 - If either N103 or N104 is present, then the other is required.

Comments: 1. This segment, used alone, provides the most efficient method of providing organizational identification. To

obtain this efficiency the "ID Code" (N104) must provide a key to the table maintained by the transactionprocessing party.

2. N105 and N106 further define the type of entity in N101.

Page 234: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Payment Order/Remittance AdviceFoodservice - 820

July 2012 [V004010-2012 FS] 12Copyright 2012 - GS1 Canada

N2 Additional Name Information Pos: 0800 Max: >1Heading - Optional

Loop: N1 Elements: 2

User Option (Usage): UsedPurpose: To specify additional names

Element Summary: Ref Id Element Name Req Type Min/Max UsageN201 93 Name

Description: Free-form name

M AN 1/60 Must use

N202 93 Name

Description: Free-form name

O AN 1/60 Used

Page 235: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Payment Order/Remittance AdviceFoodservice - 820

July 2012 [V004010-2012 FS] 13Copyright 2012 - GS1 Canada

N3 Party Location Pos: 0900 Max: >1Heading - Optional

Loop: N1 Elements: 2

User Option (Usage): UsedPurpose: To specify the location of the named party

Element Summary: Ref Id Element Name Req Type Min/Max UsageN301 166 Address Information

Description: Address information

M AN 1/55 Must use

N302 166 Address Information

Description: Address information

O AN 1/55 Used

Page 236: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Payment Order/Remittance AdviceFoodservice - 820

July 2012 [V004010-2012 FS] 14Copyright 2012 - GS1 Canada

N4 Geographic Location Pos: 1000 Max: 1Heading - Optional

Loop: N1 Elements: 4

User Option (Usage): UsedPurpose: To specify the geographic place of the named party

Element Summary: Ref Id Element Name Req Type Min/Max UsageN401 19 City Name

Description: Free-form text for city name

O AN 2/30 Used

N402 156 State or Province Code

Description: Code (StandardState/Province) as defined by appropriategovernment agency

X ID 2/2 Used

N403 116 Postal Code

Description: Code defining internationalpostal zone code excluding punctuationand blanks (zip code for United States)

O ID 3/15 Used

N404 26 Country Code

Description: Code identifying the countryUser Note 1: CA Canada

MX Mexico

US United States

User Note 1: CA Canada

MX Mexico

US United States

X ID 2/3 Used

Syntax Rules: 1. E0207 - Only one of N402 or N407 may be present.2. C0605 - If N406 is present, then N405 is required.3. C0704 - If N407 is present, then N404 is required.

Comments: 1. A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location.

Page 237: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Payment Order/Remittance AdviceFoodservice - 820

July 2012 [V004010-2012 FS] 15Copyright 2012 - GS1 Canada

ENT Entity Pos: 0100 Max: 1Detail - Optional

Loop: ENT Elements: 1

User Option (Usage): UsedPurpose: To designate the entities which are parties to a transaction and specify a reference meaningful to thoseentities

Element Summary: Ref Id Element Name Req Type Min/Max UsageENT01 554 Assigned Number

Description: Number assigned fordifferentiation within a transaction set

O N0 1/6 Used

Syntax Rules: 1. P020304 - If either ENT02, ENT03 or ENT04 are present, then the others are required.2. P050607 - If either ENT05, ENT06 or ENT07 are present, then the others are required.3. P0809 - If either ENT08 or ENT09 is present, then the other is required.

Comments: 1. This segment allows for the grouping of data by entity/entities at or within a master/masters. A master (e.g., an

organization) can be comprised of numerous subgroups (e.g., entities). This master may send grouped datato another master (e.g., an organization) which is comprised of one or more entities. Groupings are as follows:

2. (1) Single/Single: Only ENT01 is necessary, because there is a single entity (the sending master)communicating with a single entity (the receiving master).

3. (2) Single/Multiple: ENT05, ENT06, and ENT07 would be used to identify the entities within the receivingmaster. The sending master is a single entity, so no other data elements need be used.

4. (3) Multiple/Single: ENT02, ENT03, and ENT04 would be used to identify the entities within the sendingmaster. The receiving master is a single entity, so no other data elements need be used.

5. (4) Multiple/Multiple: ENT02, ENT03, and ENT04 would be used to identify the entities within the sendingmaster. ENT05, ENT06, and ENT07 would be used to identify the entities within the receiving master.

6. This segment also allows for the transmission of a unique reference number that is meaningful between theentities.

Page 238: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Payment Order/Remittance AdviceFoodservice - 820

July 2012 [V004010-2012 FS] 16Copyright 2012 - GS1 Canada

ADX Adjustment Pos: 0800 Max: 1Detail - Optional

Loop: ADX Elements: 4

User Option (Usage): UsedPurpose: To convey accounts-payable adjustment information for the purpose of cash application, includingpayer-generated debit/credit memos

Element Summary: Ref Id Element Name Req Type Min/Max UsageADX01 782 Monetary Amount

Description: Monetary amount

M R 1/18 Must use

ADX02 426 Adjustment Reason Code

Description: Code indicating reason fordebit or credit memo or adjustment toinvoice, debit or credit memo, or payment

M ID 2/2 Must use

CodeList Summary (Total Codes: 628, Included: 9)Code Name01 Pricing Error04 Item Not Accepted - Damaged06 Quantity Contested07 Incorrect Product11 Returns - Damage30 Delivery Charge Incorrect52 Credit for Overpayment53 Remittance for Previous Underpayment55 Tax Deducted

ADX03 128 Reference Identification Qualifier

Description: Code qualifying theReference Identification

X ID 2/3 Used

CodeList Summary (Total Codes: 1813, Included: 2)Code NameCM Buyer's Credit MemoDB Buyer's Debit Memo

ADX04 127 Reference Identification

Description: Reference information asdefined for a particular Transaction Set oras specified by the ReferenceIdentification Qualifier

X AN 1/80 Used

Syntax Rules: 1. P0304 - If either ADX03 or ADX04 is present, then the other is required.

Semantics: 1. ADX01 specifies the amount of the adjustment and must be signed if negative. If negative, it reduces the

payment amount; if positive, it increases the payment amount.

Page 239: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Payment Order/Remittance AdviceFoodservice - 820

July 2012 [V004010-2012 FS] 17Copyright 2012 - GS1 Canada

2. ADX02 specifies the reason for claiming the adjustment.3. ADX03 and ADX04 specify the identification of the adjustment.

Page 240: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Payment Order/Remittance AdviceFoodservice - 820

July 2012 [V004010-2012 FS] 18Copyright 2012 - GS1 Canada

REF Reference Information Pos: 1100 Max: 1Detail - Optional

Loop: REF Elements: 3

User Option (Usage): UsedPurpose: To specify identifying information

Element Summary: Ref Id Element Name Req Type Min/Max UsageREF01 128 Reference Identification Qualifier

Description: Code qualifying theReference Identification

M ID 2/3 Must use

CodeList Summary (Total Codes: 1813, Included: 2)Code NameCL Seller's Credit MemoDB Buyer's Debit Memo

REF02 127 Reference Identification

Description: Reference information asdefined for a particular Transaction Set oras specified by the ReferenceIdentification Qualifier

X AN 1/80 Used

REF03 352 Description

Description: A free-form description toclarify the related data elements and theircontent

X AN 1/80 Used

Syntax Rules: 1. R0203 - At least one of REF02 or REF03 is required.

Semantics: 1. REF04 contains data relating to the value cited in REF02.

Page 241: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Payment Order/Remittance AdviceFoodservice - 820

July 2012 [V004010-2012 FS] 19Copyright 2012 - GS1 Canada

RMR Remittance AdviceAccounts Receivable OpenItem Reference

Pos: 1500 Max: 1Detail - Optional

Loop: RMR Elements: 6

User Option (Usage): UsedPurpose: To specify the accounts receivable open item(s) to be included in the cash application and to convey theappropriate detail

Element Summary: Ref Id Element Name Req Type Min/Max UsageRMR01 128 Reference Identification Qualifier

Description: Code qualifying theReference Identification

X ID 2/3 Used

CodeList Summary (Total Codes: 1813, Included: 1)Code NameIV Seller's Invoice Number

RMR02 127 Reference Identification

Description: Reference information asdefined for a particular Transaction Set oras specified by the ReferenceIdentification Qualifier

X AN 1/80 Used

RMR03 482 Payment Action Code

Description: Code specifying theaccounts receivable open item(s), if any,to be included in the cash application.

O ID 2/2 Used

CodeList Summary (Total Codes: 9, Included: 9)Code NameAJ AdjustmentER Evaluated Receipts SettlementFL FinalNS Not Specified (Unknown as to Type of Payment)PA Payment in AdvancePI Pay ItemPO Payment on AccountPP Partial PaymentPR Progress Payment

RMR04 782 Monetary Amount

Description: Monetary amountUser Note 1: Amount paid by buyer to seller.

User Note 1: Amount paid by buyer to seller.

O R 1/18 Used

RMR05 782 Monetary Amount

Description: Monetary amount

O R 1/18 Used

Page 242: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Payment Order/Remittance AdviceFoodservice - 820

Ref Id Element Name Req Type Min/Max Usage

July 2012 [V004010-2012 FS] 20Copyright 2012 - GS1 Canada

User Note 1: Amount of the invoice (including charges, lessallowance) before terms discount (if discountis applicable) or debit amount or creditamount of referenced items.

User Note 1: Amount of the invoice (including charges, lessallowance) before terms discount (if discountis applicable) or debit amount or creditamount of referenced items.

RMR06 782 Monetary Amount

Description: Monetary amountUser Note 1: The amount of discount taken.

User Note 1: The amount of discount taken.

O R 1/18 Used

Syntax Rules: 1. P0102 - If either RMR01 or RMR02 is present, then the other is required.2. P0708 - If either RMR07 or RMR08 is present, then the other is required.

Semantics: 1. If RMR03 is present, it specifies how the cash is to be applied.2. RMR04 is the amount paid.3. RMR05 is the amount of invoice (including charges, less allowance) before terms discount (if discount is

applicable) or debit amount or credit amount of referenced items. 4. RMR06 is the amount of discount taken.5. RMR08, if present, represents an interest penalty payment, amount late interest paid, or amount anticipation.

Comments: 1. Parties using this segment should agree on the content of RMR01 and RMR02 prior to initiating

communication.2. If RMR03 is not present, this is a payment for an open item. If paying an open item, RMR02 must be present.

If not paying a specific open item, RMR04 must be present.3. RMR05 may be needed by some payees to distinguish between duplicate reference numbers.

Page 243: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Payment Order/Remittance AdviceFoodservice - 820

July 2012 [V004010-2012 FS] 21Copyright 2012 - GS1 Canada

DTM Date/Time Reference Pos: 1800 Max: >1Detail - Optional

Loop: RMR Elements: 2

User Option (Usage): UsedPurpose: To specify pertinent dates and times

Element Summary: Ref Id Element Name Req Type Min/Max UsageDTM01 374 Date/Time Qualifier

Description: Code specifying type of dateor time, or both date and time

M ID 3/3 Must use

CodeList Summary (Total Codes: 1307, Included: 1)Code Name003 Invoice

DTM02 373 Date

Description: Date expressed asCCYYMMDD where CC represents thefirst two digits of the calendar year

X DT 8/8 Used

Syntax Rules: 1. R020305 - At least one of DTM02, DTM03 or DTM05 is required.2. C0403 - If DTM04 is present, then DTM03 is required.3. P0506 - If either DTM05 or DTM06 is present, then the other is required.

Page 244: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Payment Order/Remittance AdviceFoodservice - 820

July 2012 [V004010-2012 FS] 22Copyright 2012 - GS1 Canada

ADX Adjustment Pos: 2100 Max: 1Detail - Optional

Loop: ADX Elements: 4

User Option (Usage): UsedPurpose: To convey accounts-payable adjustment information for the purpose of cash application, includingpayer-generated debit/credit memos

Element Summary: Ref Id Element Name Req Type Min/Max UsageADX01 782 Monetary Amount

Description: Monetary amount

M R 1/18 Must use

ADX02 426 Adjustment Reason Code

Description: Code indicating reason fordebit or credit memo or adjustment toinvoice, debit or credit memo, or payment

M ID 2/2 Must use

CodeList Summary (Total Codes: 628, Included: 9)Code Name01 Pricing Error04 Item Not Accepted - Damaged06 Quantity Contested07 Incorrect Product11 Returns - Damage30 Delivery Charge Incorrect52 Credit for Overpayment53 Remittance for Previous Underpayment55 Tax Deducted

ADX03 128 Reference Identification Qualifier

Description: Code qualifying theReference Identification

X ID 2/3 Used

CodeList Summary (Total Codes: 1813, Included: 2)Code NameCM Buyer's Credit MemoDB Buyer's Debit Memo

ADX04 127 Reference Identification

Description: Reference information asdefined for a particular Transaction Set oras specified by the ReferenceIdentification Qualifier

X AN 1/80 Used

Syntax Rules: 1. P0304 - If either ADX03 or ADX04 is present, then the other is required.

Semantics: 1. ADX01 specifies the amount of the adjustment and must be signed if negative. If negative, it reduces the

payment amount; if positive, it increases the payment amount.

Page 245: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Payment Order/Remittance AdviceFoodservice - 820

July 2012 [V004010-2012 FS] 23Copyright 2012 - GS1 Canada

2. ADX02 specifies the reason for claiming the adjustment.3. ADX03 and ADX04 specify the identification of the adjustment.

Page 246: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Payment Order/Remittance AdviceFoodservice - 820

July 2012 [V004010-2012 FS] 24Copyright 2012 - GS1 Canada

SE Transaction Set Trailer Pos: 0100 Max: 1Summary - Mandatory

Loop: N/A Elements: 2

User Option (Usage): Must usePurpose: To indicate the end of the transaction set and provide the count of the transmitted segments (including thebeginning (ST) and ending (SE) segments)

Element Summary: Ref Id Element Name Req Type Min/Max UsageSE01 96 Number of Included Segments

Description: Total number of segmentsincluded in a transaction set including STand SE segments

M N0 1/10 Must use

SE02 329 Transaction Set Control Number

Description: Identifying control numberthat must be unique within the transactionset functional group assigned by theoriginator for a transaction set

M AN 4/9 Must use

Comments: 1. SE is the last segment of each transaction set.

Page 247: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

850 Purchase Order FSFoodservice EDI

Version: 4010-2012 FS Final

Author: GS1 Canada -Foodservice TechnicalStandards Work Group

Publication: 7/1/2012 Notes: For Implementation

December 2012

Page 248: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Purchase Order - Foodservice - 850

July 2012 [V004010-2012 FS] iCopyright 2012 - GS1 Canada

Table of Contents

850 Purchase Order - Foodservice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>ST Transaction Set Header . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>BEG Beginning Segment for Purchase Order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>CUR Currency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>REF Reference Identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>PER Administrative Communications Contact . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>FOB F.O.B. Related Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>SAC Service, Promotion, Allowance, or Charge Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>ITD Terms of Sale/Deferred Terms of Sale . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>DTM Date/Time Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>TD5 Carrier Details (Routing Sequence/Transit Time) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>TD3 Carrier Details (Equipment) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>N9 Reference Identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>MSG Message Text . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>N1 Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>N2 Additional Name Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>N3 Address Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>N4 Geographic Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>REF Reference Identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>PO1 Baseline Item Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>CTP Pricing Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>PID Product/Item Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>PO4 Item Physical Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>SAC Service, Promotion, Allowance, or Charge Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>CTT Transaction Totals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>SE Transaction Set Trailer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>

. . . . . 1. . . . . 3. . . . . 4. . . . . 6. . . . . 7. . . . . 8. . . . 10. . . . 11. . . . 16. . . . 18. . . . 19. . . . 21. . . . 22. . . . 23. . . . 24. . . . 26. . . . 27. . . . 28. . . . 29. . . . 30. . . . 32. . . . 33. . . . 35. . . . 37. . . . 42. . . . 43

Page 249: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Purchase Order - Foodservice - 850

July 2012 [V004010-2012 FS] 1Copyright 2012 - GS1 Canada

850 Purchase Order - FoodserviceFunctional Group=PO

Purpose: This Draft Standard for Trial Use contains the format and establishes the data contents of the PurchaseOrder Transaction Set (850) for use within the context of an Electronic Data Interchange (EDI) environment. Thetransaction set can be used to provide for customary and established business and industry practice relative to theplacement of purchase orders for goods and services. This transaction set should not be used to convey purchaseorder changes or purchase order acknowledgment information.

Heading:Pos Id Segment Name Req Max Use Repeat Notes Usage010 ST Transaction Set Header M 1 Must use020 BEG Beginning Segment for

Purchase OrderM 1 Must use

040 CUR Currency O 1 Used050 REF Reference Identification O >1 Used060 PER Administrative

Communications ContactO 3 Used

080 FOB F.O.B. Related Instructions O >1 Used LOOP ID - SAC 25 LOOP ID - SAC 25

120 SAC Service, Promotion,Allowance, or ChargeInformation

O 1 Used

130 ITD Terms of Sale/DeferredTerms of Sale

O >1 Used

150 DTM Date/Time Reference O 10 Used240 TD5 Carrier Details (Routing

Sequence/Transit Time)O 12 Used

250 TD3 Carrier Details (Equipment) O 12 Used LOOP ID - N9 1000 LOOP ID - N9 1000

295 N9 Reference Identification O 1 Used300 MSG Message Text O 1000 Used

LOOP ID - N1 200 LOOP ID - N1 200

310 N1 Name O 1 Used320 N2 Additional Name

InformationO 2 Used

330 N3 Address Information O 2 Used340 N4 Geographic Location O >1 Used350 REF Reference Identification O 12 Used

Detail:Pos Id Segment Name Req Max Use Repeat Notes Usage

LOOP ID - PO1 100000 N2/010L LOOP ID - PO1 100000 N2/010L

010 PO1 Baseline Item Data M 1 N2/010 Must use LOOP ID - CTP >1 LOOP ID - CTP >1

040 CTP Pricing Information O 1 Used

LOOP ID - PID 1000 LOOP ID - PID 1000

Page 250: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Purchase Order - Foodservice - 850

Pos Id Segment Name Req Max Use Repeat Notes Usage

July 2012 [V004010-2012 FS] 2Copyright 2012 - GS1 Canada

050 PID Product/Item Description O 1 Used090 PO4 Item Physical Details O >1 Used

LOOP ID - SAC 25 LOOP ID - SAC 25

130 SAC Service, Promotion,Allowance, or ChargeInformation

O 1 Used

Summary:Pos Id Segment Name Req Max Use Repeat Notes Usage

LOOP ID - CTT 1 N3/010L LOOP ID - CTT 1 N3/010L

010 CTT Transaction Totals O 1 N3/010 Used030 SE Transaction Set Trailer M 1 Must use

Notes: 2/010L PO102 is required.2/010 PO102 is required.3/010L The number of line items (CTT01) is the accumulation of the number of PO1 segments. If used, hash total

(CTT02) is the sum of the value of quantities ordered (PO102) for each PO1 segment.3/010 The number of line items (CTT01) is the accumulation of the number of PO1 segments. If used, hash total

(CTT02) is the sum of the value of quantities ordered (PO102) for each PO1 segment.

Page 251: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Purchase Order - Foodservice - 850

July 2012 [V004010-2012 FS] 3Copyright 2012 - GS1 Canada

ST Transaction Set Header Pos: 010 Max: 1Heading - Mandatory

Loop: N/A Elements: 2

User Option (Usage): Must usePurpose: To indicate the start of a transaction set and to assign a control number

Element Summary: Ref Id Element Name Req Type Min/Max UsageST01 143 Transaction Set Identifier Code

Description: Code uniquely identifying aTransaction Set

M ID 3/3 Must use

CodeList Summary (Total Codes: 298, Included: 1)Code Name850 Purchase Order

ST02 329 Transaction Set Control Number

Description: Identifying control numberthat must be unique within the transactionset functional group assigned by theoriginator for a transaction setUser Note 1: The number is sequentiallyassigned by the sender, starting with onewithin each functional group. For eachfunctional group, the first transaction setcontrol number will be 0001 and incrementedby one for each additional transaction setwithin the group.

User Note 1: The number is sequentiallyassigned by the sender, starting with onewithin each functional group. For eachfunctional group, the first transaction setcontrol number will be 0001 and incrementedby one for each additional transaction setwithin the group.

M AN 4/9 Must use

Semantics: 1. The transaction set identifier (ST01) used by the translation routines of the interchange partners to select the

appropriate transaction set definition (e.g., 810 selects the Invoice Transaction Set).

Page 252: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Purchase Order - Foodservice - 850

July 2012 [V004010-2012 FS] 4Copyright 2012 - GS1 Canada

BEG Beginning Segment forPurchase Order

Pos: 020 Max: 1Heading - Mandatory

Loop: N/A Elements: 5

User Option (Usage): Must usePurpose: To indicate the beginning of the Purchase Order Transaction Set and transmit identifying numbers anddates

Element Summary: Ref Id Element Name Req Type Min/Max UsageBEG01 353 Transaction Set Purpose Code

Description: Code identifying purpose oftransaction set

M ID 2/2 Must use

CodeList Summary (Total Codes: 65, Included: 3)Code Name00 Original06 Confirmation22 Information Copy

User Note 1:User Note 1:This code is used to notify anyone other than the seller about this order.This code is used to notify anyone other than the seller about this order.

BEG02 92 Purchase Order Type Code

Description: Code specifying the type ofPurchase Order

M ID 2/2 Must use

CodeList Summary (Total Codes: 69, Included: 4)Code NameBE Blanket Order/Estimated Quantities (Not firm Commitment)BK Blanket Order (Quantity Firm)RL Release or Delivery Order

Description: An order for goods and services placed against a pre-existing contract orblanket order

SA Stand-alone Order

BEG03 324 Purchase Order Number

Description: Identifying number forPurchase Order assigned by theorderer/purchaserUser Note 1: Purchasing Organization'soriginal purchase order numberUser Note 1: Purchasing Organization'soriginal purchase order number

M AN 1/22 Must use

BEG04 328 Release Number

Description: Number identifying arelease against a Purchase Orderpreviously placed by the parties involvedin the transactionUser Note 1: Purchasing Organization'srelease against the purchase order, if usedUser Note 1: Purchasing Organization'srelease against the purchase order, if used

O AN 1/30 Used

BEG05 373 Date M DT 8/8 Must use

Page 253: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Purchase Order - Foodservice - 850

Ref Id Element Name Req Type Min/Max Usage

July 2012 [V004010-2012 FS] 5Copyright 2012 - GS1 Canada

Description: Date expressed asCCYYMMDDUser Note 1: Purchasing Organization'soriginal purchase order dateUser Note 1: Purchasing Organization'soriginal purchase order date

Semantics: 1. BEG05 is the date assigned by the purchaser to purchase order.

User Note 1:User Note 1:If BEG02 contains code RL, then BEG04 is required. BEG03 contains the blanket purchase order number which is beingreleased against and BEG04 contains the release number.If BEG02 contains code RL, then BEG04 is required. BEG03 contains the blanket purchase order number which is beingreleased against and BEG04 contains the release number.

Page 254: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Purchase Order - Foodservice - 850

July 2012 [V004010-2012 FS] 6Copyright 2012 - GS1 Canada

CUR Currency Pos: 040 Max: 1Heading - Optional

Loop: N/A Elements: 2

User Option (Usage): UsedPurpose: To specify the currency (dollars, pounds, francs, etc.) used in a transaction

Element Summary: Ref Id Element Name Req Type Min/Max UsageCUR01 98 Entity Identifier Code

Description: Code identifying anorganizational entity, a physical location,property or an individual

M ID 2/3 Must use

CodeList Summary (Total Codes: 1312, Included: 1)Code NameBY Buying Party (Purchaser)

CUR02 100 Currency Code

Description: Code (Standard ISO) forcountry in whose currency the chargesare specifiedUser Note 1: CAD CanadianUSD United StatesUser Note 1: CAD CanadianUSD United States

M ID 3/3 Must use

Syntax Rules: 1. C0807 - If CUR08 is present, then CUR07 is required.2. C0907 - If CUR09 is present, then CUR07 is required.3. L101112 - If CUR10 is present, then at least one of CUR11 or CUR12 is required.4. C1110 - If CUR11 is present, then CUR10 is required.5. C1210 - If CUR12 is present, then CUR10 is required.6. L131415 - If CUR13 is present, then at least one of CUR14 or CUR15 is required.7. C1413 - If CUR14 is present, then CUR13 is required.8. C1513 - If CUR15 is present, then CUR13 is required.9. L161718 - If CUR16 is present, then at least one of CUR17 or CUR18 is required.

10. C1716 - If CUR17 is present, then CUR16 is required.11. C1816 - If CUR18 is present, then CUR16 is required.12. L192021 - If CUR19 is present, then at least one of CUR20 or CUR21 is required.13. C2019 - If CUR20 is present, then CUR19 is required.14. C2119 - If CUR21 is present, then CUR19 is required.

Comments: 1. See Figures Appendix for examples detailing the use of the CUR segment.

Page 255: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Purchase Order - Foodservice - 850

July 2012 [V004010-2012 FS] 7Copyright 2012 - GS1 Canada

REF Reference Identification Pos: 050 Max: >1Heading - Optional

Loop: N/A Elements: 2

User Option (Usage): UsedPurpose: To specify identifying information

Element Summary: Ref Id Element Name Req Type Min/Max UsageREF01 128 Reference Identification Qualifier

Description: Code qualifying theReference Identification

M ID 2/3 Must use

CodeList Summary (Total Codes: 1503, Included: 5)Code NameCT Contract NumberDP Department Number

User Note 1:User Note 1:This code may be used in the header area or the detail area, but not both.This code may be used in the header area or the detail area, but not both.

IA Internal Vendor NumberUser Note 1:User Note 1:

Identification number assigned to the Selling Organization, by the Purchasing Organizationfor use within the Purchasing Organization's systemIdentification number assigned to the Selling Organization, by the Purchasing Organizationfor use within the Purchasing Organization's system

IT Internal Customer NumberUser Note 1:User Note 1:

Identification number assigned to the Purchasing Organization, by the SellingOrganization, for use within the Selling Organization's systemIdentification number assigned to the Purchasing Organization, by the SellingOrganization, for use within the Selling Organization's system

PD Promotion/Deal Number

REF02 127 Reference Identification

Description: Reference information asdefined for a particular Transaction Set oras specified by the ReferenceIdentification Qualifier

C AN 1/30 Must use

Syntax Rules: 1. R0203 - At least one of REF02 or REF03 is required.

Semantics: 1. REF04 contains data relating to the value cited in REF02.

Page 256: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Purchase Order - Foodservice - 850

July 2012 [V004010-2012 FS] 8Copyright 2012 - GS1 Canada

PER AdministrativeCommunications Contact

Pos: 060 Max: 3Heading - Optional

Loop: N/A Elements: 6

User Option (Usage): UsedPurpose: To identify a person or office to whom administrative communications should be directed

Element Summary: Ref Id Element Name Req Type Min/Max UsagePER01 366 Contact Function Code

Description: Code identifying the majorduty or responsibility of the person orgroup named

M ID 2/2 Must use

CodeList Summary (Total Codes: 230, Included: 2)Code NameBD Buyer Name or DepartmentIC Information Contact

PER02 93 Name

Description: Free-form name

O AN 1/60 Used

PER03 365 Communication Number Qualifier

Description: Code identifying the type ofcommunication number

C ID 2/2 Used

CodeList Summary (Total Codes: 40, Included: 2)Code NameEM Electronic MailTE Telephone

PER04 364 Communication Number

Description: Complete communicationsnumber including country or area codewhen applicable

C AN 1/80 Used

PER05 365 Communication Number Qualifier

Description: Code identifying the type ofcommunication number

C ID 2/2 Used

CodeList Summary (Total Codes: 40, Included: 2)Code NameEM Electronic MailTE Telephone

PER06 364 Communication Number

Description: Complete communicationsnumber including country or area codewhen applicable

C AN 1/80 Used

Syntax Rules:

Page 257: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Purchase Order - Foodservice - 850

July 2012 [V004010-2012 FS] 9Copyright 2012 - GS1 Canada

1. P0304 - If either PER03 or PER04 is present, then the other is required.2. P0506 - If either PER05 or PER06 is present, then the other is required.3. P0708 - If either PER07 or PER08 is present, then the other is required.

Page 258: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Purchase Order - Foodservice - 850

July 2012 [V004010-2012 FS] 10Copyright 2012 - GS1 Canada

FOB F.O.B. Related Instructions Pos: 080 Max: >1Heading - Optional

Loop: N/A Elements: 3

User Option (Usage): UsedPurpose: To specify transportation instructions relating to shipment

Element Summary: Ref Id Element Name Req Type Min/Max UsageFOB01 146 Shipment Method of Payment

Description: Code identifying paymentterms for transportation charges

M ID 2/2 Must use

CodeList Summary (Total Codes: 28, Included: 3)Code NameCC CollectPB Customer Pick-up/BackhaulPP Prepaid (by Seller)

FOB02 309 Location Qualifier

Description: Code identifying type oflocation

C ID 1/2 Used

CodeList Summary (Total Codes: 172, Included: 2)Code NameDE Destination (Shipping)OR Origin (Shipping Point)

FOB03 352 Description

Description: A free-form description toclarify the related data elements and theircontent

O AN 1/80 Used

Syntax Rules: 1. C0302 - If FOB03 is present, then FOB02 is required.2. C0405 - If FOB04 is present, then FOB05 is required.3. C0706 - If FOB07 is present, then FOB06 is required.4. C0809 - If FOB08 is present, then FOB09 is required.

Semantics: 1. FOB01 indicates which party will pay the carrier.2. FOB02 is the code specifying transportation responsibility location.3. FOB06 is the code specifying the title passage location.4. FOB08 is the code specifying the point at which the risk of loss transfers. This may be different than the

location specified in FOB02/FOB03 and FOB06/FOB07.

Page 259: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Purchase Order - Foodservice - 850

July 2012 [V004010-2012 FS] 11Copyright 2012 - GS1 Canada

SAC Service, Promotion,Allowance, or ChargeInformation

Pos: 120 Max: 1Heading - Optional

Loop: SAC Elements: 15

User Option (Usage): UsedPurpose: To request or identify a service, promotion, allowance, or charge; to specify the amount or percentage forthe service, promotion, allowance, or charge

Element Summary: Ref Id Element Name Req Type Min/Max UsageSAC01 248 Allowance or Charge Indicator

Description: Code which indicates anallowance or charge for the servicespecified

M ID 1/1 Must use

CodeList Summary (Total Codes: 7, Included: 4)Code NameA AllowanceC ChargeN No Allowance or ChargeR Allowance Request

SAC02 1300 Service, Promotion, Allowance, orCharge Code

Description: Code identifying the service,promotion, allowance, or chargeUser Note 1: See FoodserviceImplementation Guidelines Appendix - DataElements

User Note 1: See FoodserviceImplementation Guidelines Appendix - DataElements

C ID 4/4 Used

CodeList Summary (Total Codes: 1053, Included: 5)Code NameD350 Goods and Services Credit AllowanceD360 Goods and Services Tax Charge

User Note 1:User Note 1:Provincal Tobacco Tax.Provincal Tobacco Tax.

H490 Subject To Tax On ResaleH770 Tax - State TaxH806 Tax Credit

User Note 1:User Note 1:Provincial Tax Credit.Provincial Tax Credit.

SAC03 559 Agency Qualifier Code

Description: Code identifying the agencyassigning the code values

C ID 2/2 Used

CodeList Summary (Total Codes: 176, Included: 1)

Page 260: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Purchase Order - Foodservice - 850

July 2012 [V004010-2012 FS] 12Copyright 2012 - GS1 Canada

Code NameVI Voluntary Inter-Industry Commerce Standard (VICS) EDI

SAC04 1301 Agency Service, Promotion, Allowance,or Charge Code

Description: Agency maintained codeidentifying the service, promotion,allowance, or chargeUser Note 1: See FoodserviceImplementation Guidelines Appendix - DataElements

User Note 1: See FoodserviceImplementation Guidelines Appendix - DataElements

C AN 1/10 Used

SAC05 610 Amount

Description: Monetary amountUser Note 1: When SAC01 contains code Aor code C, then this data element is required.This will resolve any differences between thesender's and receiver's system calculations ofamounts, i.e., rounding errors whenallowances or charges are expressed inpercentages or rates.

User Note 1: When SAC01 contains code Aor code C, then this data element is required.This will resolve any differences between thesender's and receiver's system calculations ofamounts, i.e., rounding errors whenallowances or charges are expressed inpercentages or rates.

O N2 1/15 Used

SAC06 378 Allowance/Charge Percent Qualifier

Description: Code indicating on whatbasis allowance or charge percent iscalculated

C ID 1/1 Used

CodeList Summary (Total Codes: 11, Included: 7)Code Name1 Item List Cost2 Item Net Cost3 Discount/Gross

User Note 1:User Note 1:All allowances are off the gross price including cash discount.All allowances are off the gross price including cash discount.

4 Discount/NetUser Note 1:User Note 1:

All allowances are off the gross price. Cash discounts are off the net.All allowances are off the gross price. Cash discounts are off the net.

5 Base Price per UnitUser Note 1:User Note 1:

Line item discountLine item discount

6 Base Price Amount7 Base Price Amount Less Previous Discount

User Note 1:User Note 1:Declining balance methodDeclining balance method

SAC07 332 Percent

Description: Percent expressed as apercentUser Note 1: The percent is sent with adecimal point only when needed, e.g., 10.5%is sent as ``10.5'', and 2% is sent as ``2''.

User Note 1: The percent is sent with adecimal point only when needed, e.g., 10.5%is sent as ``10.5'', and 2% is sent as ``2''.

C R 1/6 Used

Page 261: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Purchase Order - Foodservice - 850

Ref Id Element Name Req Type Min/Max Usage

July 2012 [V004010-2012 FS] 13Copyright 2012 - GS1 Canada

SAC08 118 Rate

Description: Rate expressed in thestandard monetary denomination for thecurrency specified

O R 1/9 Used

SAC09 355 Unit or Basis for Measurement Code

Description: Code specifying the units inwhich a value is being expressed, ormanner in which a measurement hasbeen taken

C ID 2/2 Used

CodeList Summary (Total Codes: 794, Included: 12)Code NameBG BagBR BarrelCA CaseDR DrumEA EachGA GallonKG KilogramLB PoundLT LiterPA PailPL Pallet/Unit LoadTE Tote

SAC10 380 Quantity

Description: Numeric value of quantity

C R 1/15 Used

SAC12 331 Allowance or Charge Method ofHandling Code

Description: Code indicating method ofhandling for an allowance or charge

O ID 2/2 Used

CodeList Summary (Total Codes: 22, Included: 6)Code Name01 Bill Back

User Note 1:User Note 1:The allowance or charge amount will be adjudicated as a separate item, i.e., a debit/creditmemo or a separate invoice. The amount will not be reflected in the invoice total amount.The allowance or charge amount will be adjudicated as a separate item, i.e., a debit/creditmemo or a separate invoice. The amount will not be reflected in the invoice total amount.

02 Off InvoiceUser Note 1:User Note 1:

The allowance or charge amount will be reflected in the total transaction amount, e.g.,Total Invoice Amount = Merchandise Price + Charges - Allowances.The allowance or charge amount will be reflected in the total transaction amount, e.g.,Total Invoice Amount = Merchandise Price + Charges - Allowances.

03 Vendor Check to CustomerUser Note 1:User Note 1:

The vendor will issue a check directly to the customer of the retailer, or end consumer, forthe allowance or charge amount. The amount is not reflected in the total invoice amount.The vendor will issue a check directly to the customer of the retailer, or end consumer, forthe allowance or charge amount. The amount is not reflected in the total invoice amount.

04 Credit Customer Account

Page 262: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Purchase Order - Foodservice - 850

Code Name

July 2012 [V004010-2012 FS] 14Copyright 2012 - GS1 Canada

User Note 1:User Note 1:The retailer's account will be credited for the amount of the allowance or charge. Theamount is not reflected in the total invoice amount.The retailer's account will be credited for the amount of the allowance or charge. Theamount is not reflected in the total invoice amount.

05 Charge to be Paid by VendorUser Note 1:User Note 1:

The vendor is responsible for the allowance or charge amount. The exact method ofadjudication has been agreed to by the trading partners. The amount will not be reflectedin the total invoice amount.

The vendor is responsible for the allowance or charge amount. The exact method ofadjudication has been agreed to by the trading partners. The amount will not be reflectedin the total invoice amount.

06 Charge to be Paid by CustomerUser Note 1:User Note 1:

When the order/item is a direct ship to the customer, or end consumer of the retailer, theallowance or charge amount is the responsibility of the customer or end consumer. If it isnot a drop ship to the customer of the retailer, then the allowance or charge amount is theresponsibility of the retailer. The exact method of adjudication has been agreed to by thetrading partners. The amount will not be reflected in the total invoice amou

When the order/item is a direct ship to the customer, or end consumer of the retailer, theallowance or charge amount is the responsibility of the customer or end consumer. If it isnot a drop ship to the customer of the retailer, then the allowance or charge amount is theresponsibility of the retailer. The exact method of adjudication has been agreed to by thetrading partners. The amount will not be reflected in the total invoice amou

SAC13 127 Reference Identification

Description: Reference information asdefined for a particular Transaction Set oras specified by the ReferenceIdentification QualifierUser Note 1: This is used to provide the TaxRegistration NumberUser Note 1: This is used to provide the TaxRegistration Number

C AN 1/30 Used

SAC14 770 Option Number

Description: A unique number identifyingavailable promotion or allowance optionswhen more than one is offered

O AN 1/20 Used

SAC15 352 Description

Description: A free-form description toclarify the related data elements and theircontent

C AN 1/80 Used

SAC16 819 Language Code

Description: Code designating thelanguage used in text, from a standardcode list maintained by the InternationalStandards Organization (ISO 639)

O ID 2/3 Used

Syntax Rules: 1. R0203 - At least one of SAC02 or SAC03 is required.2. P0304 - If either SAC03 or SAC04 is present, then the other is required.3. P0607 - If either SAC06 or SAC07 is present, then the other is required.4. P0910 - If either SAC09 or SAC10 is present, then the other is required.5. C1110 - If SAC11 is present, then SAC10 is required.6. L130204 - If SAC13 is present, then at least one of SAC02 or SAC04 is required.7. C1413 - If SAC14 is present, then SAC13 is required.8. C1615 - If SAC16 is present, then SAC15 is required.

Semantics:

Page 263: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Purchase Order - Foodservice - 850

July 2012 [V004010-2012 FS] 15Copyright 2012 - GS1 Canada

1. If SAC01 is "A" or "C", then at least one of SAC05, SAC07, or SAC08 is required.2. SAC05 is the total amount for the service, promotion, allowance, or charge.3. If SAC05 is present with SAC07 or SAC08, then SAC05 takes precedence.4. SAC08 is the allowance or charge rate per unit. 5. SAC10 and SAC11 is the quantity basis when the allowance or charge quantity is different from the purchase

order or invoice quantity.6. SAC10 and SAC11 used together indicate a quantity range, which could be a dollar amount, that is applicable

to service, promotion, allowance, or charge.7. SAC13 is used in conjunction with SAC02 or SAC04 to provide a specific reference number as identified by

the code used.8. SAC14 is used in conjunction with SAC13 to identify an option when there is more than one option of the

promotion.9. SAC16 is used to identify the language being used in SAC15.

Comments: 1. SAC04 may be used to uniquely identify the service, promotion, allowance, or charge. In addition, it may be

used in conjunction to further the code in SAC02.2. In some business applications, it is necessary to advise the trading partner of the actual dollar amount that a

particular allowance, charge, or promotion was based on to reduce ambiguity. This amount is commonlyreferred to as "Dollar Basis Amount". It is represented in the SAC segment in SAC10 using the qualifier "DO" -Dollars in SAC09.

Page 264: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Purchase Order - Foodservice - 850

July 2012 [V004010-2012 FS] 16Copyright 2012 - GS1 Canada

ITD Terms of Sale/Deferred Termsof Sale

Pos: 130 Max: >1Heading - Optional

Loop: N/A Elements: 6

User Option (Usage): UsedPurpose: To specify terms of sale

Element Summary: Ref Id Element Name Req Type Min/Max UsageITD01 336 Terms Type Code

Description: Code identifying type ofpayment terms

O ID 2/2 Used

CodeList Summary (Total Codes: 65, Included: 4)Code Name05 Discount Not Applicable08 Basic Discount Offered09 Proximo14 Previously agreed upon

ITD02 333 Terms Basis Date Code

Description: Code identifying thebeginning of the terms period

O ID 1/2 Used

CodeList Summary (Total Codes: 17, Included: 6)Code Name1 Ship Date2 Delivery Date3 Invoice Date4 Specified Date7 Effective Date15 Receipt of Goods

ITD03 338 Terms Discount Percent

Description: Terms discount percentage,expressed as a percent, available to thepurchaser if an invoice is paid on orbefore the Terms Discount Due DateUser Note 1: The percent is sent with adecimal point only when needed, e.g., 10.5%is sent as ``10.5'', and 2% is sent as ``2''.

User Note 1: The percent is sent with adecimal point only when needed, e.g., 10.5%is sent as ``10.5'', and 2% is sent as ``2''.

O R 1/6 Used

ITD05 351 Terms Discount Days Due

Description: Number of days in the termsdiscount period by which payment is dueif terms discount is earnedUser Note 1: The end of the term period isderived by adding this value to the beginningof the term period, as qualified by ITD02.

User Note 1: The end of the term period isderived by adding this value to the beginningof the term period, as qualified by ITD02.

C N0 1/3 Used

ITD07 386 Terms Net Days O N0 1/3 Used

Page 265: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Purchase Order - Foodservice - 850

Ref Id Element Name Req Type Min/Max Usage

July 2012 [V004010-2012 FS] 17Copyright 2012 - GS1 Canada

Description: Number of days until totalinvoice amount is due (discount notapplicable)User Note 1: The end of the term period isderived by adding this value to the beginningof the term period, as qualified by ITD02.

User Note 1: The end of the term period isderived by adding this value to the beginningof the term period, as qualified by ITD02.

ITD08 362 Terms Discount Amount

Description: Total amount of termsdiscount

O N2 1/10 Used

Syntax Rules: 1. L03040513 - If ITD03 is present, then at least one of ITD04, ITD05 or ITD13 is required.2. L08040513 - If ITD08 is present, then at least one of ITD04, ITD05 or ITD13 is required.3. L091011 - If ITD09 is present, then at least one of ITD10 or ITD11 is required.

Semantics: 1. ITD15 is the percentage applied to a base amount used to determine a late payment charge.

Comments: 1. If the code in ITD01 is "04", then ITD07 or ITD09 is required and either ITD10 or ITD11 is required; if the code

in ITD01 is "05", then ITD06 or ITD07 is required.

Page 266: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Purchase Order - Foodservice - 850

July 2012 [V004010-2012 FS] 18Copyright 2012 - GS1 Canada

DTM Date/Time Reference Pos: 150 Max: 10Heading - Optional

Loop: N/A Elements: 3

User Option (Usage): UsedPurpose: To specify pertinent dates and times

Element Summary: Ref Id Element Name Req Type Min/Max UsageDTM01 374 Date/Time Qualifier

Description: Code specifying type of dateor time, or both date and time

M ID 3/3 Must use

CodeList Summary (Total Codes: 1112, Included: 2)Code Name002 Delivery Requested118 Requested Pick-up

DTM02 373 Date

Description: Date expressed asCCYYMMDD

C DT 8/8 Must use

DTM03 337 Time

Description: Time expressed in 24-hourclock time as follows: HHMM, orHHMMSS, or HHMMSSD, orHHMMSSDD, where H = hours (00-23), M= minutes (00-59), S = integer seconds(00-59) and DD = decimal seconds;decimal seconds are expressed asfollows: D = tenths (0-9) and DD =hundredths (00-99)

C TM 4/8 Used

Syntax Rules: 1. R020305 - At least one of DTM02, DTM03 or DTM05 is required.2. C0403 - If DTM04 is present, then DTM03 is required.3. P0506 - If either DTM05 or DTM06 is present, then the other is required.

Page 267: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Purchase Order - Foodservice - 850

July 2012 [V004010-2012 FS] 19Copyright 2012 - GS1 Canada

TD5 Carrier Details (RoutingSequence/Transit Time)

Pos: 240 Max: 12Heading - Optional

Loop: N/A Elements: 5

User Option (Usage): UsedPurpose: To specify the carrier and sequence of routing and provide transit time information

Element Summary: Ref Id Element Name Req Type Min/Max UsageTD501 133 Routing Sequence Code

Description: Code describing therelationship of a carrier to a specificshipment movement

O ID 1/2 Used

CodeList Summary (Total Codes: 23, Included: 13)Code Name1 1st Carrier after Origin Carrier2 2nd Carrier after Origin Carrier3 3rd Carrier after Origin Carrier4 4th Carrier after Origin Carrier5 5th Carrier after Origin Carrier6 6th Carrier after Origin Carrier7 7th Carrier after Origin Carrier8 8th Carrier after Origin Carrier9 9th Carrier after Origin CarrierA Origin Carrier, Agent's Routing (Rail)B Origin/Delivery Carrier (Any Mode)O Origin Carrier (Air, Motor, or Ocean)S Origin Carrier, Shipper's Routing (Rail)

TD502 66 Identification Code Qualifier

Description: Code designating thesystem/method of code structure used forIdentification Code (67)

C ID 1/2 Used

CodeList Summary (Total Codes: 215, Included: 3)Code Name2 Standard Carrier Alpha Code (SCAC)91 Assigned by Seller or Seller's Agent92 Assigned by Buyer or Buyer's Agent

TD503 67 Identification Code

Description: Code identifying a party orother code

C AN 2/80 Used

TD504 91 Transportation Method/Type Code

Description: Code specifying the methodor type of transportation for the shipment

C ID 1/2 Used

CodeList Summary (Total Codes: 71, Included: 2)

Page 268: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Purchase Order - Foodservice - 850

July 2012 [V004010-2012 FS] 20Copyright 2012 - GS1 Canada

Code NameH Customer PickupM Motor (Common Carrier)

TD505 387 Routing

Description: Free-form description of therouting or requested routing for shipment,or the originating carrier's identity

C AN 1/35 Used

Syntax Rules: 1. R0204050612 - At least one of TD502, TD504, TD505, TD506 or TD512 is required.2. C0203 - If TD502 is present, then TD503 is required.3. C0708 - If TD507 is present, then TD508 is required.4. C1011 - If TD510 is present, then TD511 is required.5. C1312 - If TD513 is present, then TD512 is required.6. C1413 - If TD514 is present, then TD513 is required.7. C1512 - If TD515 is present, then TD512 is required.

Semantics: 1. TD515 is the country where the service is to be performed.

Comments: 1. When specifying a routing sequence to be used for the shipment movement in lieu of specifying each carrier

within the movement, use TD502 to identify the party responsible for defining the routing sequence, and useTD503 to identify the actual routing sequence, specified by the party identified in TD502.

User Note 1:User Note 1:This segment is used to specify every carrier in the routing sequence or a specific routing sequence that has been previouslyidentified (usually from a routing guide). The segment can also be used to indicate estimated transit time in days. Only useTD501 if needed for clarity; this is not a requirement in most retail applications. When referring to a pre-established routingguide, use code 91 or 92 in TD502, and identify the routing sequence, from the routing guide, in TD503. To identify a specificprivate parcel service, TD502 will contain code 2, and TD503 will contain the corresponding SCAC. TD510 and TD511 are usedto specify transit time.

This segment is used to specify every carrier in the routing sequence or a specific routing sequence that has been previouslyidentified (usually from a routing guide). The segment can also be used to indicate estimated transit time in days. Only useTD501 if needed for clarity; this is not a requirement in most retail applications. When referring to a pre-established routingguide, use code 91 or 92 in TD502, and identify the routing sequence, from the routing guide, in TD503. To identify a specificprivate parcel service, TD502 will contain code 2, and TD503 will contain the corresponding SCAC. TD510 and TD511 are usedto specify transit time.

Page 269: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Purchase Order - Foodservice - 850

July 2012 [V004010-2012 FS] 21Copyright 2012 - GS1 Canada

TD3 Carrier Details (Equipment) Pos: 250 Max: 12Heading - Optional

Loop: N/A Elements: 1

User Option (Usage): UsedPurpose: To specify transportation details relating to the equipment used by the carrier

Element Summary: Ref Id Element Name Req Type Min/Max UsageTD301 40 Equipment Description Code

Description: Code identifying type ofequipment used for shipment

C ID 2/2 Must use

CodeList Summary (Total Codes: 134, Included: 4)Code NameCV Closed VanFT Flat Bed TrailerRT Controlled Temperature Trailer (Reefer)TL Trailer (not otherwise specified)

Syntax Rules: 1. E0110 - Only one of TD301 or TD310 may be present.2. C0203 - If TD302 is present, then TD303 is required.3. C0405 - If TD304 is present, then TD305 is required.4. P0506 - If either TD305 or TD306 is present, then the other is required.

Page 270: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Purchase Order - Foodservice - 850

July 2012 [V004010-2012 FS] 22Copyright 2012 - GS1 Canada

N9 Reference Identification Pos: 295 Max: 1Heading - Optional

Loop: N9 Elements: 2

User Option (Usage): UsedPurpose: To transmit identifying information as specified by the Reference Identification Qualifier

Element Summary: Ref Id Element Name Req Type Min/Max UsageN901 128 Reference Identification Qualifier

Description: Code qualifying theReference Identification

M ID 2/3 Must use

CodeList Summary (Total Codes: 1503, Included: 1)Code NameAH Agreement Number

N902 127 Reference Identification

Description: Reference information asdefined for a particular Transaction Set oras specified by the ReferenceIdentification Qualifier

C AN 1/30 Must use

Syntax Rules: 1. R0203 - At least one of N902 or N903 is required.2. C0605 - If N906 is present, then N905 is required.

Semantics: 1. N906 reflects the time zone which the time reflects.2. N907 contains data relating to the value cited in N902.

Page 271: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Purchase Order - Foodservice - 850

July 2012 [V004010-2012 FS] 23Copyright 2012 - GS1 Canada

MSG Message Text Pos: 300 Max: 1000Heading - Optional

Loop: N9 Elements: 1

User Option (Usage): UsedPurpose: To provide a free-form format that allows the transmission of text information

Element Summary: Ref Id Element Name Req Type Min/Max UsageMSG01 933 Free-Form Message Text

Description: Free-form message text

M AN 1/264 Must use

Syntax Rules: 1. C0302 - If MSG03 is present, then MSG02 is required.

Semantics: 1. MSG03 is the number of lines to advance before printing.

Comments: 1. MSG02 is not related to the specific characteristics of a printer, but identifies top of page, advance a line, etc.2. If MSG02 is "AA - Advance the specified number of lines before print" then MSG03 is required.

User Note 1:User Note 1:This segment will contain any text clauses for the agreement referenced in the previous N9 segment.This segment will contain any text clauses for the agreement referenced in the previous N9 segment.

Page 272: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Purchase Order - Foodservice - 850

July 2012 [V004010-2012 FS] 24Copyright 2012 - GS1 Canada

N1 Name Pos: 310 Max: 1Heading - Optional

Loop: N1 Elements: 4

User Option (Usage): UsedPurpose: To identify a party by type of organization, name, and code

Element Summary: Ref Id Element Name Req Type Min/Max UsageN101 98 Entity Identifier Code

Description: Code identifying anorganizational entity, a physical location,property or an individual

M ID 2/3 Must use

CodeList Summary (Total Codes: 1312, Included: 8)Code NameBO Broker or Sales OfficeBS Bill and Ship ToBT Bill-to-PartyBY Buying Party (Purchaser)SF Ship FromST Ship ToSU Supplier/Manufacturer

User Note 1:User Note 1:Supplier may or may not be the manufacturerSupplier may or may not be the manufacturer

VN VendorUser Note 1:User Note 1:Party supplying the products being maintainedParty supplying the products being maintained

N102 93 Name

Description: Free-form name

C AN 1/60 Used

N103 66 Identification Code Qualifier

Description: Code designating thesystem/method of code structure used forIdentification Code (67)

C ID 1/2 Used

CodeList Summary (Total Codes: 215, Included: 2)Code Name9 D-U-N-S+4, D-U-N-S Number with Four Character SuffixUL UCC/EAN Location Code

Description: Global Location Number (GLN) (Revised name) A globally unique 13 digit code used for the identification of any physical or legal locationthat needs to be uniquely identified for use in the supply chain. A GS1 identification key SEE CODE SOURCE 583

N104 67 Identification Code

Description: Code identifying a party orother code

C AN 2/80 Used

Page 273: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Purchase Order - Foodservice - 850

July 2012 [V004010-2012 FS] 25Copyright 2012 - GS1 Canada

Syntax Rules: 1. R0203 - At least one of N102 or N103 is required.2. P0304 - If either N103 or N104 is present, then the other is required.

Comments: 1. This segment, used alone, provides the most efficient method of providing organizational identification. To

obtain this efficiency the "ID Code" (N104) must provide a key to the table maintained by the transactionprocessing party.

2. N105 and N106 further define the type of entity in N101.

Page 274: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Purchase Order - Foodservice - 850

July 2012 [V004010-2012 FS] 26Copyright 2012 - GS1 Canada

N2 Additional Name Information Pos: 320 Max: 2Heading - Optional

Loop: N1 Elements: 2

User Option (Usage): UsedPurpose: To specify additional names or those longer than 35 characters in length

Element Summary: Ref Id Element Name Req Type Min/Max UsageN201 93 Name

Description: Free-form name

M AN 1/60 Must use

N202 93 Name

Description: Free-form name

O AN 1/60 Used

Page 275: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Purchase Order - Foodservice - 850

July 2012 [V004010-2012 FS] 27Copyright 2012 - GS1 Canada

N3 Address Information Pos: 330 Max: 2Heading - Optional

Loop: N1 Elements: 2

User Option (Usage): UsedPurpose: To specify the location of the named party

Element Summary: Ref Id Element Name Req Type Min/Max UsageN301 166 Address Information

Description: Address information

M AN 1/55 Must use

N302 166 Address Information

Description: Address information

O AN 1/55 Used

Page 276: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Purchase Order - Foodservice - 850

July 2012 [V004010-2012 FS] 28Copyright 2012 - GS1 Canada

N4 Geographic Location Pos: 340 Max: >1Heading - Optional

Loop: N1 Elements: 4

User Option (Usage): UsedPurpose: To specify the geographic place of the named party

Element Summary: Ref Id Element Name Req Type Min/Max UsageN401 19 City Name

Description: Free-form text for city name

O AN 2/30 Used

N402 156 State or Province Code

Description: Code (StandardState/Province) as defined by appropriategovernment agency

O ID 2/2 Used

N403 116 Postal Code

Description: Code defining internationalpostal zone code excluding punctuationand blanks (zip code for United States)

O ID 3/15 Used

N404 26 Country Code

Description: Code identifying the countryUser Note 1: CA CanadaMX MexicoUS United States

User Note 1: CA CanadaMX MexicoUS United States

O ID 2/3 Used

Syntax Rules: 1. C0605 - If N406 is present, then N405 is required.

Comments: 1. A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location.2. N402 is required only if city name (N401) is in the U.S. or Canada.

Page 277: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Purchase Order - Foodservice - 850

July 2012 [V004010-2012 FS] 29Copyright 2012 - GS1 Canada

REF Reference Identification Pos: 350 Max: 12Heading - Optional

Loop: N1 Elements: 2

User Option (Usage): UsedPurpose: To specify identifying information

Element Summary: Ref Id Element Name Req Type Min/Max UsageREF01 128 Reference Identification Qualifier

Description: Code qualifying theReference Identification

M ID 2/3 Must use

CodeList Summary (Total Codes: 1503, Included: 1)Code NameDK Dock Number

REF02 127 Reference Identification

Description: Reference information asdefined for a particular Transaction Set oras specified by the ReferenceIdentification Qualifier

C AN 1/30 Must use

Syntax Rules: 1. R0203 - At least one of REF02 or REF03 is required.

Semantics: 1. REF04 contains data relating to the value cited in REF02.

Page 278: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Purchase Order - Foodservice - 850

July 2012 [V004010-2012 FS] 30Copyright 2012 - GS1 Canada

PO1 Baseline Item Data Pos: 010 Max: 1Detail - Mandatory

Loop: PO1 Elements: 4

User Option (Usage): Must usePurpose: To specify basic and most frequently used line item data

Element Summary: Ref Id Element Name Req Type Min/Max UsagePO102 330 Quantity Ordered

Description: Quantity ordered

C R 1/15 Must use

PO103 355 Unit or Basis for Measurement Code

Description: Code specifying the units inwhich a value is being expressed, ormanner in which a measurement hasbeen taken

O ID 2/2 Must use

CodeList Summary (Total Codes: 794, Included: 12)Code NameBG BagBR BarrelCA CaseDR DrumEA EachGA GallonKG KilogramLB PoundLT LiterPA PailPL Pallet/Unit LoadTE Tote

PO106 235 Product/Service ID Qualifier

Description: Code identifying thetype/source of the descriptive numberused in Product/Service ID (234)

C ID 2/2 Used

CodeList Summary (Total Codes: 477, Included: 1)Code NameUK U.P.C./EAN Shipping Container Code (1-2-5-5-1)

Description: GTIN-14 A 14-digit GS1 Identification Key composed of an Indicator Digit, GS1 Company Prefix, ItemReference and Check Digit used to identify trade items SEE CODE SOURCE 41

PO107 234 Product/Service ID

Description: Identifying number for aproduct or service

C AN 1/48 Used

Syntax Rules:

Page 279: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Purchase Order - Foodservice - 850

July 2012 [V004010-2012 FS] 31Copyright 2012 - GS1 Canada

1. C0302 - If PO103 is present, then PO102 is required.2. C0504 - If PO105 is present, then PO104 is required.3. P0607 - If either PO106 or PO107 is present, then the other is required.4. P0809 - If either PO108 or PO109 is present, then the other is required.5. P1011 - If either PO110 or PO111 is present, then the other is required.6. P1213 - If either PO112 or PO113 is present, then the other is required.7. P1415 - If either PO114 or PO115 is present, then the other is required.8. P1617 - If either PO116 or PO117 is present, then the other is required.9. P1819 - If either PO118 or PO119 is present, then the other is required.

10. P2021 - If either PO120 or PO121 is present, then the other is required.11. P2223 - If either PO122 or PO123 is present, then the other is required.12. P2425 - If either PO124 or PO125 is present, then the other is required.

Comments: 1. See the Data Element Dictionary for a complete list of IDs.2. PO101 is the line item identification.3. PO106 through PO125 provide for ten different product/service IDs per each item. For example: Case, Color,

Drawing No., U.P.C. No., ISBN No., Model No., or SKU.

Page 280: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Purchase Order - Foodservice - 850

July 2012 [V004010-2012 FS] 32Copyright 2012 - GS1 Canada

CTP Pricing Information Pos: 040 Max: 1Detail - Optional

Loop: CTP Elements: 2

User Option (Usage): UsedPurpose: To specify pricing information

Element Summary: Ref Id Element Name Req Type Min/Max UsageCTP02 236 Price Identifier Code

Description: Code identifying pricingspecification

C ID 3/3 Must use

CodeList Summary (Total Codes: 164, Included: 1)Code NameUCP Unit cost price

User Note 1:User Note 1:Item list costItem list cost

CTP03 212 Unit Price

Description: Price per unit of product,service, commodity, etc.User Note 1: The price is sent with adecimal point only when needed, e.g., $15.95would be sent as ``15.95'', and $29.00 wouldbe sent as ``29''.

User Note 1: The price is sent with adecimal point only when needed, e.g., $15.95would be sent as ``15.95'', and $29.00 wouldbe sent as ``29''.

C R 1/17 Must use

Syntax Rules: 1. P0405 - If either CTP04 or CTP05 is present, then the other is required.2. C0607 - If CTP06 is present, then CTP07 is required.3. C0902 - If CTP09 is present, then CTP02 is required.4. C1002 - If CTP10 is present, then CTP02 is required.5. C1103 - If CTP11 is present, then CTP03 is required.

Semantics: 1. CTP07 is a multiplier factor to arrive at a final discounted price. A multiplier of .90 would be the factor if a 10%

discount is given.2. CTP08 is the rebate amount.

Comments: 1. See Figures Appendix for an example detailing the use of CTP03 and CTP04.2. See Figures Appendix for an example detailing the use of CTP03, CTP04 and CTP07.

Page 281: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Purchase Order - Foodservice - 850

July 2012 [V004010-2012 FS] 33Copyright 2012 - GS1 Canada

PID Product/Item Description Pos: 050 Max: 1Detail - Optional

Loop: PID Elements: 3

User Option (Usage): UsedPurpose: To describe a product or process in coded or free-form format

Element Summary: Ref Id Element Name Req Type Min/Max UsagePID01 349 Item Description Type

Description: Code indicating the formatof a description

M ID 1/1 Must use

CodeList Summary (Total Codes: 3, Included: 1)Code NameF Free-form

User Note 1:User Note 1:The description will be found in PID05.The description will be found in PID05.

PID02 750 Product/Process Characteristic Code

Description: Code identifying the generalclass of a product or processcharacteristic

O ID 2/3 Used

CodeList Summary (Total Codes: 217, Included: 1)Code Name08 Product

PID05 352 Description

Description: A free-form description toclarify the related data elements and theircontent

C AN 1/80 Used

Syntax Rules: 1. C0403 - If PID04 is present, then PID03 is required.2. R0405 - At least one of PID04 or PID05 is required.3. C0703 - If PID07 is present, then PID03 is required.4. C0804 - If PID08 is present, then PID04 is required.5. C0905 - If PID09 is present, then PID05 is required.

Semantics: 1. Use PID03 to indicate the organization that publishes the code list being referred to.2. PID04 should be used for industry-specific product description codes.3. PID08 describes the physical characteristics of the product identified in PID04. A "Y" indicates that the

specified attribute applies to this item; an "N" indicates it does not apply. Any other value is indeterminate.4. PID09 is used to identify the language being used in PID05.

Comments: 1. If PID01 equals "F", then PID05 is used. If PID01 equals "S", then PID04 is used. If PID01 equals "X", then

both PID04 and PID05 are used.

Page 282: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Purchase Order - Foodservice - 850

July 2012 [V004010-2012 FS] 34Copyright 2012 - GS1 Canada

2. Use PID06 when necessary to refer to the product surface or layer being described in the segment.3. PID07 specifies the individual code list of the agency specified in PID03.

Page 283: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Purchase Order - Foodservice - 850

July 2012 [V004010-2012 FS] 35Copyright 2012 - GS1 Canada

PO4 Item Physical Details Pos: 090 Max: >1Detail - Optional

Loop: PO1 Elements: 4

User Option (Usage): UsedPurpose: To specify the physical qualities, packaging, weights, and dimensions relating to the item

Element Summary: Ref Id Element Name Req Type Min/Max UsagePO401 356 Pack

Description: The number of innercontainers, or number of eaches if thereare no inner containers, per outercontainer

O N0 1/6 Used

PO402 357 Size

Description: Size of supplier units inpack

C R 1/8 Used

PO403 355 Unit or Basis for Measurement Code

Description: Code specifying the units inwhich a value is being expressed, ormanner in which a measurement hasbeen taken

C ID 2/2 Used

CodeList Summary (Total Codes: 794, Included: 12)Code NameBG BagBR BarrelCA CaseDR DrumEA EachGA GallonKG KilogramLB PoundLT LiterPA PailPL Pallet/Unit LoadTE Tote

PO414 810 Inner Pack

Description: The number of eaches perinner container

O N0 1/6 Used

Syntax Rules: 1. P0203 - If either PO402 or PO403 is present, then the other is required.2. C0506 - If PO405 is present, then PO406 is required.3. P0607 - If either PO406 or PO407 is present, then the other is required.4. P0809 - If either PO408 or PO409 is present, then the other is required.5. C1013 - If PO410 is present, then PO413 is required.

Page 284: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Purchase Order - Foodservice - 850

July 2012 [V004010-2012 FS] 36Copyright 2012 - GS1 Canada

6. C1113 - If PO411 is present, then PO413 is required.7. C1213 - If PO412 is present, then PO413 is required.8. L13101112 - If PO413 is present, then at least one of PO410, PO411 or PO412 is required.9. C1716 - If PO417 is present, then PO416 is required.

10. C1804 - If PO418 is present, then PO404 is required.

Semantics: 1. PO415 is used to indicate the relative layer of this package or range of packages within the layers of

packaging. Relative Position 1 (value R1) is the innermost package.2. PO416 is the package identifier or the beginning package identifier in a range of identifiers.3. PO417 is the ending package identifier in a range of identifiers.4. PO418 is the number of packages in this layer.

Comments: 1. PO403 - The "Unit or Basis for Measure Code" in this segment position is for purposes of defining the pack

(PO401) /size (PO402) measure which indicates the quantity in the inner pack unit. For example: If the cartoncontains 24 12-Ounce packages, it would be described as follows: Data element 356 = "24"; Data element357 = "12"; Data element 355 = "OZ".

2. PO413 defines the unit of measure for PO410, PO411, and PO412.

User Note 1:User Note 1:This segment is used to specify the packaging of the item in the case or carton. There may be two levels of packagingspecified. The first level is always specified by using PO401 (Pack). The first level may be actual items, e.g., consumer units,or it may be the number of smaller containers within the case. The second level, specified using PO414 (Inner Pack), is thenumber of eaches in each inner container when PO401 is the number of smaller containers within the case. See Section V(Pack/Inner Pack Usage) for usage examples.

This segment can be used also to specify the weight and/or volume (cube) for the item by using PO406 and PO407, and/orPO408 and PO409.

This segment is used to specify the packaging of the item in the case or carton. There may be two levels of packagingspecified. The first level is always specified by using PO401 (Pack). The first level may be actual items, e.g., consumer units,or it may be the number of smaller containers within the case. The second level, specified using PO414 (Inner Pack), is thenumber of eaches in each inner container when PO401 is the number of smaller containers within the case. See Section V(Pack/Inner Pack Usage) for usage examples.

This segment can be used also to specify the weight and/or volume (cube) for the item by using PO406 and PO407, and/orPO408 and PO409.

Page 285: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Purchase Order - Foodservice - 850

July 2012 [V004010-2012 FS] 37Copyright 2012 - GS1 Canada

SAC Service, Promotion,Allowance, or ChargeInformation

Pos: 130 Max: 1Detail - Optional

Loop: SAC Elements: 14

User Option (Usage): UsedPurpose: To request or identify a service, promotion, allowance, or charge; to specify the amount or percentage forthe service, promotion, allowance, or charge

Element Summary: Ref Id Element Name Req Type Min/Max UsageSAC01 248 Allowance or Charge Indicator

Description: Code which indicates anallowance or charge for the servicespecified

M ID 1/1 Must use

CodeList Summary (Total Codes: 7, Included: 4)Code NameA AllowanceC ChargeN No Allowance or ChargeR Allowance Request

SAC02 1300 Service, Promotion, Allowance, orCharge Code

Description: Code identifying the service,promotion, allowance, or chargeUser Note 1: See FoodserviceImplementation Guidelines Appendix - DataElements

User Note 1: See FoodserviceImplementation Guidelines Appendix - DataElements

C ID 4/4 Used

SAC03 559 Agency Qualifier Code

Description: Code identifying the agencyassigning the code values

C ID 2/2 Used

CodeList Summary (Total Codes: 176, Included: 1)Code NameVI Voluntary Inter-Industry Commerce Standard (VICS) EDI

SAC04 1301 Agency Service, Promotion, Allowance,or Charge Code

Description: Agency maintained codeidentifying the service, promotion,allowance, or chargeUser Note 1: See FoodserviceImplementation Guidelines Appendix - DataElements

User Note 1: See FoodserviceImplementation Guidelines Appendix - DataElements

C AN 1/10 Used

SAC05 610 Amount

Description: Monetary amount

O N2 1/15 Used

Page 286: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Purchase Order - Foodservice - 850

Ref Id Element Name Req Type Min/Max Usage

July 2012 [V004010-2012 FS] 38Copyright 2012 - GS1 Canada

User Note 1: When SAC01 contains code Aor code C, then this data element is required.This will resolve any differences between thesender's and receiver's system calculations ofamounts, i.e., rounding errors whenallowances or charges are expressed inpercentages or rates.

User Note 1: When SAC01 contains code Aor code C, then this data element is required.This will resolve any differences between thesender's and receiver's system calculations ofamounts, i.e., rounding errors whenallowances or charges are expressed inpercentages or rates.

SAC06 378 Allowance/Charge Percent Qualifier

Description: Code indicating on whatbasis allowance or charge percent iscalculated

C ID 1/1 Used

CodeList Summary (Total Codes: 11, Included: 7)Code Name1 Item List Cost2 Item Net Cost3 Discount/Gross

User Note 1:User Note 1:All allowances are off the gross price including cash discount.All allowances are off the gross price including cash discount.

4 Discount/NetUser Note 1:User Note 1:

All allowances are off the gross price. Cash discounts are off the net.All allowances are off the gross price. Cash discounts are off the net.

5 Base Price per UnitUser Note 1:User Note 1:

Line item discountLine item discount

6 Base Price Amount7 Base Price Amount Less Previous Discount

User Note 1:User Note 1:Declining balance methodDeclining balance method

SAC07 332 Percent

Description: Percent expressed as apercentUser Note 1: The percent is sent with adecimal point only when needed, e.g., 10.5%is sent as ``10.5'', and 2% is sent as ``2''.

User Note 1: The percent is sent with adecimal point only when needed, e.g., 10.5%is sent as ``10.5'', and 2% is sent as ``2''.

C R 1/6 Used

SAC08 118 Rate

Description: Rate expressed in thestandard monetary denomination for thecurrency specified

O R 1/9 Used

SAC09 355 Unit or Basis for Measurement Code

Description: Code specifying the units inwhich a value is being expressed, ormanner in which a measurement hasbeen taken

C ID 2/2 Used

CodeList Summary (Total Codes: 794, Included: 12)

Page 287: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Purchase Order - Foodservice - 850

July 2012 [V004010-2012 FS] 39Copyright 2012 - GS1 Canada

Code NameBG BagBR BarrelCA CaseDR DrumEA EachGA GallonKG KilogramLB PoundLT LiterPA PailPL Pallet/Unit LoadTE Tote

SAC10 380 Quantity

Description: Numeric value of quantity

C R 1/15 Used

SAC12 331 Allowance or Charge Method ofHandling Code

Description: Code indicating method ofhandling for an allowance or charge

O ID 2/2 Used

CodeList Summary (Total Codes: 22, Included: 6)Code Name01 Bill Back

User Note 1:User Note 1:The allowance or charge amount will be adjudicated as a separate item, i.e., a debit/creditmemo or a separate invoice. The amount will not be reflected in the invoice total amount.The allowance or charge amount will be adjudicated as a separate item, i.e., a debit/creditmemo or a separate invoice. The amount will not be reflected in the invoice total amount.

02 Off InvoiceUser Note 1:User Note 1:

The allowance or charge amount will be reflected in the total transaction amount, e.g.,Total Invoice Amount = Merchandise Price + Charges - Allowances.The allowance or charge amount will be reflected in the total transaction amount, e.g.,Total Invoice Amount = Merchandise Price + Charges - Allowances.

03 Vendor Check to CustomerUser Note 1:User Note 1:

The vendor will issue a check directly to the customer of the retailer, or end consumer, forthe allowance or charge amount. The amount is not reflected in the total invoice amount.The vendor will issue a check directly to the customer of the retailer, or end consumer, forthe allowance or charge amount. The amount is not reflected in the total invoice amount.

04 Credit Customer AccountUser Note 1:User Note 1:

The retailer's account will be credited for the amount of the allowance or charge. Theamount is not reflected in the total invoice amount.The retailer's account will be credited for the amount of the allowance or charge. Theamount is not reflected in the total invoice amount.

05 Charge to be Paid by VendorUser Note 1:User Note 1:

The vendor is responsible for the allowance or charge amount. The exact method ofadjudication has been agreed to by the trading partners. The amount will not be reflectedin the total invoice amount.

The vendor is responsible for the allowance or charge amount. The exact method ofadjudication has been agreed to by the trading partners. The amount will not be reflectedin the total invoice amount.

06 Charge to be Paid by CustomerUser Note 1:User Note 1:

When the order/item is a direct ship to the customer, or end consumer of the retailer, theallowance or charge amount is the responsibility of the customer or end consumer. If it isnot a drop ship to the customer of the retailer, then the allowance or charge amount is the

When the order/item is a direct ship to the customer, or end consumer of the retailer, theallowance or charge amount is the responsibility of the customer or end consumer. If it isnot a drop ship to the customer of the retailer, then the allowance or charge amount is the

Page 288: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Purchase Order - Foodservice - 850

Code Name

July 2012 [V004010-2012 FS] 40Copyright 2012 - GS1 Canada

responsibility of the retailer. The exact method of adjudication has been agreed to by thetrading partners. The amount will not be reflected in the total invoice amouresponsibility of the retailer. The exact method of adjudication has been agreed to by thetrading partners. The amount will not be reflected in the total invoice amou

SAC13 127 Reference Identification

Description: Reference information asdefined for a particular Transaction Set oras specified by the ReferenceIdentification QualifierUser Note 1: This is used to provide the TaxRegistration NumberUser Note 1: This is used to provide the TaxRegistration Number

C AN 1/30 Used

SAC15 352 Description

Description: A free-form description toclarify the related data elements and theircontent

C AN 1/80 Used

SAC16 819 Language Code

Description: Code designating thelanguage used in text, from a standardcode list maintained by the InternationalStandards Organization (ISO 639)

O ID 2/3 Used

Syntax Rules: 1. R0203 - At least one of SAC02 or SAC03 is required.2. P0304 - If either SAC03 or SAC04 is present, then the other is required.3. P0607 - If either SAC06 or SAC07 is present, then the other is required.4. P0910 - If either SAC09 or SAC10 is present, then the other is required.5. C1110 - If SAC11 is present, then SAC10 is required.6. L130204 - If SAC13 is present, then at least one of SAC02 or SAC04 is required.7. C1413 - If SAC14 is present, then SAC13 is required.8. C1615 - If SAC16 is present, then SAC15 is required.

Semantics: 1. If SAC01 is "A" or "C", then at least one of SAC05, SAC07, or SAC08 is required.2. SAC05 is the total amount for the service, promotion, allowance, or charge.3. If SAC05 is present with SAC07 or SAC08, then SAC05 takes precedence.4. SAC08 is the allowance or charge rate per unit. 5. SAC10 and SAC11 is the quantity basis when the allowance or charge quantity is different from the purchase

order or invoice quantity.6. SAC10 and SAC11 used together indicate a quantity range, which could be a dollar amount, that is applicable

to service, promotion, allowance, or charge.7. SAC13 is used in conjunction with SAC02 or SAC04 to provide a specific reference number as identified by

the code used.8. SAC14 is used in conjunction with SAC13 to identify an option when there is more than one option of the

promotion.9. SAC16 is used to identify the language being used in SAC15.

Comments: 1. SAC04 may be used to uniquely identify the service, promotion, allowance, or charge. In addition, it may be

used in conjunction to further the code in SAC02.2. In some business applications, it is necessary to advise the trading partner of the actual dollar amount that a

Page 289: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Purchase Order - Foodservice - 850

July 2012 [V004010-2012 FS] 41Copyright 2012 - GS1 Canada

particular allowance, charge, or promotion was based on to reduce ambiguity. This amount is commonlyreferred to as "Dollar Basis Amount". It is represented in the SAC segment in SAC10 using the qualifier "DO" -Dollars in SAC09.

Page 290: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Purchase Order - Foodservice - 850

July 2012 [V004010-2012 FS] 42Copyright 2012 - GS1 Canada

CTT Transaction Totals Pos: 010 Max: 1Summary - Optional

Loop: CTT Elements: 1

User Option (Usage): UsedPurpose: To transmit a hash total for a specific element in the transaction set

Element Summary: Ref Id Element Name Req Type Min/Max UsageCTT01 354 Number of Line Items

Description: Total number of line items inthe transaction setUser Note 1: The number of PO1 segmentspresent in the transaction setUser Note 1: The number of PO1 segmentspresent in the transaction set

M N0 1/6 Must use

Syntax Rules: 1. P0304 - If either CTT03 or CTT04 is present, then the other is required.2. P0506 - If either CTT05 or CTT06 is present, then the other is required.

Comments: 1. This segment is intended to provide hash totals to validate transaction completeness and correctness.

Page 291: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Purchase Order - Foodservice - 850

July 2012 [V004010-2012 FS] 43Copyright 2012 - GS1 Canada

SE Transaction Set Trailer Pos: 030 Max: 1Summary - Mandatory

Loop: N/A Elements: 2

User Option (Usage): Must usePurpose: To indicate the end of the transaction set and provide the count of the transmitted segments (including thebeginning (ST) and ending (SE) segments)

Element Summary: Ref Id Element Name Req Type Min/Max UsageSE01 96 Number of Included Segments

Description: Total number of segmentsincluded in a transaction set including STand SE segments

M N0 1/10 Must use

SE02 329 Transaction Set Control Number

Description: Identifying control numberthat must be unique within the transactionset functional group assigned by theoriginator for a transaction setUser Note 1: This must be the same numberas is in the ST segment (ST02) for thetransaction set.

User Note 1: This must be the same numberas is in the ST segment (ST02) for thetransaction set.

M AN 4/9 Must use

Comments: 1. SE is the last segment of each transaction set.

Page 292: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

855 Purchase OrderAcknowledgment FS

Foodservice EDI

Version: 4010-2012 FS Final

Author: GS1 Canada -Foodservice TechnicalStandards Work Group

Publication: 7/1/2012 Notes: For Implementation

December 2012

Page 293: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Purchase Order Acknowledgment -Foodservice - 855

July 2012 [V004010-2012 FS] iCopyright 2012 - GS1 Canada

Table of Contents

855 Purchase Order Acknowledgment - Foodservice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>ST Transaction Set Header . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>BAK Beginning Segment for Purchase Order Acknowledgment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>REF Reference Identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>DTM Date/Time Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>N1 Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>N2 Additional Name Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>N3 Address Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>N4 Geographic Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>PO1 Baseline Item Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>CTP Pricing Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>PID Product/Item Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>PO4 Item Physical Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>SAC Service, Promotion, Allowance, or Charge Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>ACK Line Item Acknowledgment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>CTT Transaction Totals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>SE Transaction Set Trailer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>

. . . . . 1. . . . . 3. . . . . 4. . . . . 6. . . . . 7. . . . . 8. . . . 10. . . . 11. . . . 12. . . . 13. . . . 16. . . . 19. . . . 22. . . . 24. . . . 29. . . . 31. . . . 32

Page 294: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Purchase Order Acknowledgment -Foodservice - 855

July 2012 [V004010-2012 FS] 1Copyright 2012 - GS1 Canada

855 Purchase Order Acknowledgment -FoodserviceFunctional Group=PR

Purpose: This Draft Standard for Trial Use contains the format and establishes the data contents of the PurchaseOrder Acknowledgment Transaction Set (855) for use within the context of an Electronic Data Interchange (EDI)environment. The transaction set can be used to provide for customary and established business and industrypractice relative to a seller's acknowledgment of a buyer's purchase order. This transaction set can also be used asnotification of a vendor generated order. This usage advises a buyer that a vendor has or will ship merchandise asprearranged in their partnership.

Heading:Pos Id Segment Name Req Max Use Repeat Notes Usage010 ST Transaction Set Header M 1 Must use020 BAK Beginning Segment for

Purchase OrderAcknowledgment

M 1 Must use

050 REF Reference Identification O >1 Used150 DTM Date/Time Reference O 10 Used

LOOP ID - N1 200 LOOP ID - N1 200

300 N1 Name O 1 Used310 N2 Additional Name

InformationO 2 Used

320 N3 Address Information O 2 Used330 N4 Geographic Location O 1 Used

Detail:Pos Id Segment Name Req Max Use Repeat Notes Usage

LOOP ID - PO1 100000 N2/010L LOOP ID - PO1 100000 N2/010L

010 PO1 Baseline Item Data O 1 N2/010 Used040 CTP Pricing Information O >1 Used

LOOP ID - PID 1000 LOOP ID - PID 1000

050 PID Product/Item Description O 1 Used090 PO4 Item Physical Details O >1 Used

LOOP ID - SAC 25 LOOP ID - SAC 25

130 SAC Service, Promotion,Allowance, or ChargeInformation

O 1 Used

LOOP ID - ACK 104 LOOP ID - ACK 104

270 ACK Line Item Acknowledgment O 1 Used

Summary:Pos Id Segment Name Req Max Use Repeat Notes Usage

LOOP ID - CTT 1 N3/010L LOOP ID - CTT 1 N3/010L

010 CTT Transaction Totals O 1 N3/010 Used030 SE Transaction Set Trailer M 1 Must use

Page 295: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Purchase Order Acknowledgment -Foodservice - 855

July 2012 [V004010-2012 FS] 2Copyright 2012 - GS1 Canada

Notes: 2/010L PO102 is required.2/010 PO102 is required.3/010L The number of line items (CTT01) is the accumulation of the number of PO1 segments. If used, hash total

(CTT02) is the sum of the value of quantities ordered (PO102) for each PO1 segment.3/010 The number of line items (CTT01) is the accumulation of the number of PO1 segments. If used, hash total

(CTT02) is the sum of the value of quantities ordered (PO102) for each PO1 segment.

Page 296: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Purchase Order Acknowledgment -Foodservice - 855

July 2012 [V004010-2012 FS] 3Copyright 2012 - GS1 Canada

ST Transaction Set Header Pos: 010 Max: 1Heading - Mandatory

Loop: N/A Elements: 2

User Option (Usage): Must usePurpose: To indicate the start of a transaction set and to assign a control number

Element Summary: Ref Id Element Name Req Type Min/Max UsageST01 143 Transaction Set Identifier Code

Description: Code uniquely identifying aTransaction Set

M ID 3/3 Must use

CodeList Summary (Total Codes: 298, Included: 1)Code Name855 Purchase Order Acknowledgment

ST02 329 Transaction Set Control Number

Description: Identifying control numberthat must be unique within the transactionset functional group assigned by theoriginator for a transaction setUser Note 1: The number is sequentiallyassigned by the sender, starting with onewithin each functional group. For eachfunctional group, the first transaction setcontrol number will be 0001 and incrementedby one for each additional transaction setwithin the group.

User Note 1: The number is sequentiallyassigned by the sender, starting with onewithin each functional group. For eachfunctional group, the first transaction setcontrol number will be 0001 and incrementedby one for each additional transaction setwithin the group.

M AN 4/9 Must use

Semantics: 1. The transaction set identifier (ST01) used by the translation routines of the interchange partners to select the

appropriate transaction set definition (e.g., 810 selects the Invoice Transaction Set).

Page 297: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Purchase Order Acknowledgment -Foodservice - 855

July 2012 [V004010-2012 FS] 4Copyright 2012 - GS1 Canada

BAK Beginning Segment forPurchase OrderAcknowledgment

Pos: 020 Max: 1Heading - Mandatory

Loop: N/A Elements: 4

User Option (Usage): Must usePurpose: To indicate the beginning of the Purchase Order Acknowledgment Transaction Set and transmit identifyingnumbers and dates

Element Summary: Ref Id Element Name Req Type Min/Max UsageBAK01 353 Transaction Set Purpose Code

Description: Code identifying purpose oftransaction set

M ID 2/2 Must use

CodeList Summary (Total Codes: 65, Included: 5)Code Name00 Original

User Note 1:User Note 1:ACKNOWLEDGMENT: This is the original acknowledgment.ACKNOWLEDGMENT: This is the original acknowledgment.

01 CancellationUser Note 1:User Note 1:

ACKNOWLEDGMENT: Cancels the the purchasing organization's purchase order.ACKNOWLEDGMENT: Cancels the the purchasing organization's purchase order.

05 ReplaceUser Note 1:User Note 1:

ACKNOWLEDGMENT: This code is not valid for regular acknowledgments.ACKNOWLEDGMENT: This code is not valid for regular acknowledgments.

16 ProposedUser Note 1:User Note 1:

ACKNOWLEDGMENT: This code is not valid for regular acknowledgments.ACKNOWLEDGMENT: This code is not valid for regular acknowledgments.

19 Seller initiated changeUser Note 1:User Note 1:

ACKNOWLEDGMENT: Change the the purchasing organization's purchase order.ACKNOWLEDGMENT: Change the the purchasing organization's purchase order.

BAK02 587 Acknowledgment Type

Description: Code specifying the type ofacknowledgment

M ID 2/2 Must use

CodeList Summary (Total Codes: 15, Included: 6)Code NameAC Acknowledge - With Detail and Change

User Note 1:User Note 1:Full purchase order detail must be transmittedFull purchase order detail must be transmitted

AD Acknowledge - With Detail, No ChangeAE Acknowledge - With Exception Detail Only

User Note 1:User Note 1:Only transmit details of changeOnly transmit details of change

AK Acknowledge - No Detail or Change

Page 298: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Purchase Order Acknowledgment -Foodservice - 855

Code Name

July 2012 [V004010-2012 FS] 5Copyright 2012 - GS1 Canada

AP Acknowledge - Product ReplenishmentRJ Rejected - No Detail

BAK03 324 Purchase Order Number

Description: Identifying number forPurchase Order assigned by theorderer/purchaser

M AN 1/22 Must use

BAK04 373 Date

Description: Date expressed asCCYYMMDD

M DT 8/8 Must use

Semantics: 1. BAK04 is the date assigned by the purchaser to purchase order.2. BAK08 is the seller's order number.3. BAK09 is the date assigned by the sender to the acknowledgment.

Page 299: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Purchase Order Acknowledgment -Foodservice - 855

July 2012 [V004010-2012 FS] 6Copyright 2012 - GS1 Canada

REF Reference Identification Pos: 050 Max: >1Heading - Optional

Loop: N/A Elements: 2

User Option (Usage): UsedPurpose: To specify identifying information

Element Summary: Ref Id Element Name Req Type Min/Max UsageREF01 128 Reference Identification Qualifier

Description: Code qualifying theReference Identification

M ID 2/3 Must use

CodeList Summary (Total Codes: 1503, Included: 5)Code NameDP Department NumberIA Internal Vendor Number

User Note 1:User Note 1:Identification number assigned to the vendor, by the purchasing organization, for usewithin the purchasing organization's systemIdentification number assigned to the vendor, by the purchasing organization, for usewithin the purchasing organization's system

IT Internal Customer NumberUser Note 1:User Note 1:

Identification number assigned to the retailer, by the selling organization, for use withinthe selling organization's systemIdentification number assigned to the retailer, by the selling organization, for use withinthe selling organization's system

IV Seller's Invoice NumberVN Vendor Order Number

REF02 127 Reference Identification

Description: Reference information asdefined for a particular Transaction Set oras specified by the ReferenceIdentification Qualifier

C AN 1/30 Must use

Syntax Rules: 1. R0203 - At least one of REF02 or REF03 is required.

Semantics: 1. REF04 contains data relating to the value cited in REF02.

Page 300: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Purchase Order Acknowledgment -Foodservice - 855

July 2012 [V004010-2012 FS] 7Copyright 2012 - GS1 Canada

DTM Date/Time Reference Pos: 150 Max: 10Heading - Optional

Loop: N/A Elements: 2

User Option (Usage): UsedPurpose: To specify pertinent dates and times

Element Summary: Ref Id Element Name Req Type Min/Max UsageDTM01 374 Date/Time Qualifier

Description: Code specifying type of dateor time, or both date and time

M ID 3/3 Must use

CodeList Summary (Total Codes: 1112, Included: 5)Code Name001 Cancel After

User Note 1:User Note 1:If the order has not been shipped by this date, the order is considered canceledIf the order has not been shipped by this date, the order is considered canceled

002 Delivery Requested010 Requested Ship068 Current Schedule Ship086 Scheduled for Shipment (Week of)

DTM02 373 Date

Description: Date expressed asCCYYMMDD

C DT 8/8 Must use

Syntax Rules: 1. R020305 - At least one of DTM02, DTM03 or DTM05 is required.2. C0403 - If DTM04 is present, then DTM03 is required.3. P0506 - If either DTM05 or DTM06 is present, then the other is required.

Page 301: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Purchase Order Acknowledgment -Foodservice - 855

July 2012 [V004010-2012 FS] 8Copyright 2012 - GS1 Canada

N1 Name Pos: 300 Max: 1Heading - Optional

Loop: N1 Elements: 4

User Option (Usage): UsedPurpose: To identify a party by type of organization, name, and code

Element Summary: Ref Id Element Name Req Type Min/Max UsageN101 98 Entity Identifier Code

Description: Code identifying anorganizational entity, a physical location,property or an individual

M ID 2/3 Must use

CodeList Summary (Total Codes: 1312, Included: 8)Code NameBO Broker or Sales OfficeBS Bill and Ship ToBT Bill-to-PartyBY Buying Party (Purchaser)SF Ship FromST Ship ToSU Supplier/Manufacturer

User Note 1:User Note 1:Supplier may or may not be the manufacturerSupplier may or may not be the manufacturer

VN VendorUser Note 1:User Note 1:Party supplying the products being maintainedParty supplying the products being maintained

N102 93 Name

Description: Free-form name

C AN 1/60 Used

N103 66 Identification Code Qualifier

Description: Code designating thesystem/method of code structure used forIdentification Code (67)

C ID 1/2 Used

CodeList Summary (Total Codes: 215, Included: 2)Code Name9 D-U-N-S+4, D-U-N-S Number with Four Character SuffixUL UCC/EAN Location Code

Description: Global Location Number (GLN) (Revised name)A globally unique 13 digit code used for the identification of any physical or legal locationthat needs to be uniquely identified for use in the supply chain. A GS1 identification key SEE CODE SOURCE 583

N104 67 Identification Code

Description: Code identifying a party orother code

C AN 2/80 Used

Page 302: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Purchase Order Acknowledgment -Foodservice - 855

July 2012 [V004010-2012 FS] 9Copyright 2012 - GS1 Canada

Syntax Rules: 1. R0203 - At least one of N102 or N103 is required.2. P0304 - If either N103 or N104 is present, then the other is required.

Comments: 1. This segment, used alone, provides the most efficient method of providing organizational identification. To

obtain this efficiency the "ID Code" (N104) must provide a key to the table maintained by the transactionprocessing party.

2. N105 and N106 further define the type of entity in N101.

Page 303: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Purchase Order Acknowledgment -Foodservice - 855

July 2012 [V004010-2012 FS] 10Copyright 2012 - GS1 Canada

N2 Additional Name Information Pos: 310 Max: 2Heading - Optional

Loop: N1 Elements: 2

User Option (Usage): UsedPurpose: To specify additional names or those longer than 35 characters in length

Element Summary: Ref Id Element Name Req Type Min/Max UsageN201 93 Name

Description: Free-form name

M AN 1/60 Must use

N202 93 Name

Description: Free-form name

O AN 1/60 Used

Page 304: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Purchase Order Acknowledgment -Foodservice - 855

July 2012 [V004010-2012 FS] 11Copyright 2012 - GS1 Canada

N3 Address Information Pos: 320 Max: 2Heading - Optional

Loop: N1 Elements: 2

User Option (Usage): UsedPurpose: To specify the location of the named party

Element Summary: Ref Id Element Name Req Type Min/Max UsageN301 166 Address Information

Description: Address information

M AN 1/55 Must use

N302 166 Address Information

Description: Address information

O AN 1/55 Used

Page 305: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Purchase Order Acknowledgment -Foodservice - 855

July 2012 [V004010-2012 FS] 12Copyright 2012 - GS1 Canada

N4 Geographic Location Pos: 330 Max: 1Heading - Optional

Loop: N1 Elements: 4

User Option (Usage): UsedPurpose: To specify the geographic place of the named party

Element Summary: Ref Id Element Name Req Type Min/Max UsageN401 19 City Name

Description: Free-form text for city name

O AN 2/30 Used

N402 156 State or Province Code

Description: Code (StandardState/Province) as defined by appropriategovernment agency

O ID 2/2 Used

N403 116 Postal Code

Description: Code defining internationalpostal zone code excluding punctuationand blanks (zip code for United States)

O ID 3/15 Used

N404 26 Country Code

Description: Code identifying the countryUser Note 1: CA CanadaMX MexicoUS United States

User Note 1: CA CanadaMX MexicoUS United States

O ID 2/3 Used

Syntax Rules: 1. C0605 - If N406 is present, then N405 is required.

Comments: 1. A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location.2. N402 is required only if city name (N401) is in the U.S. or Canada.

Page 306: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Purchase Order Acknowledgment -Foodservice - 855

July 2012 [V004010-2012 FS] 13Copyright 2012 - GS1 Canada

PO1 Baseline Item Data Pos: 010 Max: 1Detail - Optional

Loop: PO1 Elements: 6

User Option (Usage): UsedPurpose: To specify basic and most frequently used line item data

Element Summary: Ref Id Element Name Req Type Min/Max UsagePO102 330 Quantity Ordered

Description: Quantity ordered

C R 1/15 Must use

PO103 355 Unit or Basis for Measurement Code

Description: Code specifying the units inwhich a value is being expressed, ormanner in which a measurement hasbeen takenUser Note 1: See Section III for code list.User Note 1: See Section III for code list.

O ID 2/2 Must use

CodeList Summary (Total Codes: 794, Included: 12)Code NameBG BagBR BarrelCA CaseDR DrumEA EachGA GallonKG KilogramLB PoundLT LiterPA PailPL Pallet/Unit LoadTE Tote

PO104 212 Unit Price

Description: Price per unit of product,service, commodity, etc.User Note 1: The price is sent with adecimal point only when needed, e.g., $15.95would be sent as ``15.95'', and $29.00 wouldbe sent as ``29''.

To indicate free goods, use a single zero (0) inPO104 and code NC in PO105.

User Note 1: The price is sent with adecimal point only when needed, e.g., $15.95would be sent as ``15.95'', and $29.00 wouldbe sent as ``29''.

To indicate free goods, use a single zero (0) inPO104 and code NC in PO105.

C R 1/17 Used

PO105 639 Basis of Unit Price Code

Description: Code identifying the type ofunit price for an itemUser Note 1: This data element is used toclarify or alter the basis of unit price. The unitUser Note 1: This data element is used toclarify or alter the basis of unit price. The unit

O ID 2/2 Used

Page 307: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Purchase Order Acknowledgment -Foodservice - 855

Ref Id Element Name Req Type Min/Max Usage

July 2012 [V004010-2012 FS] 14Copyright 2012 - GS1 Canada

price expressed in PO104 is always in thesame terms as the unit of measure in PO103,unless otherwise specified in PO105.

price expressed in PO104 is always in thesame terms as the unit of measure in PO103,unless otherwise specified in PO105.

CodeList Summary (Total Codes: 91, Included: 13)Code NameLD Catalog Price per DozenLE Catalog Price per EachNC No ChargePO Price per OuncePP Price per PoundPR PromotionQT QuotedRD Retail Price per DozenRE Retail Price per EachTD Contract Price per DozenTE Contract Price per EachWD Wholesale Price per DozenWE Wholesale Price per Each

PO106 235 Product/Service ID Qualifier

Description: Code identifying thetype/source of the descriptive numberused in Product/Service ID (234)

C ID 2/2 Used

CodeList Summary (Total Codes: 477, Included: 1)Code NameUK U.P.C./EAN Shipping Container Code (1-2-5-5-1)

Description: GTIN-14 A 14-digit GS1 Identification Key composed of an Indicator Digit, GS1 Company Prefix, ItemReference and Check Digit used to identify trade items SEE CODE SOURCE 41

PO107 234 Product/Service ID

Description: Identifying number for aproduct or service

C AN 1/48 Used

Syntax Rules: 1. C0302 - If PO103 is present, then PO102 is required.2. C0504 - If PO105 is present, then PO104 is required.3. P0607 - If either PO106 or PO107 is present, then the other is required.4. P0809 - If either PO108 or PO109 is present, then the other is required.5. P1011 - If either PO110 or PO111 is present, then the other is required.6. P1213 - If either PO112 or PO113 is present, then the other is required.7. P1415 - If either PO114 or PO115 is present, then the other is required.8. P1617 - If either PO116 or PO117 is present, then the other is required.9. P1819 - If either PO118 or PO119 is present, then the other is required.

10. P2021 - If either PO120 or PO121 is present, then the other is required.11. P2223 - If either PO122 or PO123 is present, then the other is required.12. P2425 - If either PO124 or PO125 is present, then the other is required.

Page 308: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Purchase Order Acknowledgment -Foodservice - 855

July 2012 [V004010-2012 FS] 15Copyright 2012 - GS1 Canada

Comments: 1. PO101 is the line item identification.2. PO106 through PO125 provide for ten different product/service IDs per each item. For example: Case, Color,

Drawing No., U.P.C. No., ISBN No., Model No., or SKU.

Page 309: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Purchase Order Acknowledgment -Foodservice - 855

July 2012 [V004010-2012 FS] 16Copyright 2012 - GS1 Canada

CTP Pricing Information Pos: 040 Max: >1Detail - Optional

Loop: PO1 Elements: 6

User Option (Usage): UsedPurpose: To specify pricing information

Element Summary: Ref Id Element Name Req Type Min/Max UsageCTP01 687 Class of Trade Code

Description: Code indicating class oftrade

O ID 2/2 Used

CodeList Summary (Total Codes: 52, Included: 5)Code NameAG AgentBG Buying GroupDE DealerDI DistributorRS Resale

CTP02 236 Price Identifier Code

Description: Code identifying pricingspecification

C ID 3/3 Must use

CodeList Summary (Total Codes: 164, Included: 6)Code NameALT Alternate PriceCAT Catalog PriceMSR Manufacturer's Suggested RetailPRP Promotional price

User Note 1:User Note 1:Promotion/EventPromotion/Event

RES ResaleUser Note 1:User Note 1:

Retail priceRetail price

UCP Unit cost priceUser Note 1:User Note 1:

Item list costItem list cost

CTP03 212 Unit Price

Description: Price per unit of product,service, commodity, etc.User Note 1: The price is sent with adecimal point only when needed, e.g., $15.95would be sent as ``15.95'', and $29.00 wouldbe sent as ``29''.

User Note 1: The price is sent with adecimal point only when needed, e.g., $15.95would be sent as ``15.95'', and $29.00 wouldbe sent as ``29''.

C R 1/17 Must use

CTP04 380 Quantity

C R 1/15 Used

Page 310: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Purchase Order Acknowledgment -Foodservice - 855

Ref Id Element Name Req Type Min/Max Usage

July 2012 [V004010-2012 FS] 17Copyright 2012 - GS1 Canada

Description: Numeric value of quantity

CTP05 C001 Composite Unit of Measure

Description: To identify a composite unitof measure(See Figures Appendix forexamples of use)

C Comp Used

CTP05-01 355 Unit or Basis for Measurement Code

Description: Code specifying the units inwhich a value is being expressed, ormanner in which a measurement hasbeen taken

M ID 2/2 Must use

CodeList Summary (Total Codes: 794, Included: 26)Code NameBG BagBR BarrelCA CaseCC Cubic CentimeterCF Cubic FeetCI Cubic InchesCR Cubic MeterDB Dry PoundsDR DrumEA EachFT Foot

User Note 1:User Note 1:FeetFeet

FZ Fluid Ounce (Imperial)Description: A liquid unit of measure equal to 1/20 (.05) pint (Imperial), 28.416 cubiccentimeters, or 28.416 milliliters

GA GallonGI Imperial GallonsGR GramIN InchKG KilogramLB PoundLT LiterML MilliliterPA PailPL Pallet/Unit LoadPT PintPX Pint, ImperialTE ToteYD Yard

CTP11 289 Multiple Price Quantity

Description: Quantity of units for a givenprice, e.g., 3 for $10.00

O N0 1/2 Used

Page 311: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Purchase Order Acknowledgment -Foodservice - 855

Ref Id Element Name Req Type Min/Max Usage

July 2012 [V004010-2012 FS] 18Copyright 2012 - GS1 Canada

User Note 1: This is the quantity containedin a multipack for the retail selling pricespecified in CTP03, e.g., 3 for $10.00, whenthe product will be sold as a multipack.

User Note 1: This is the quantity containedin a multipack for the retail selling pricespecified in CTP03, e.g., 3 for $10.00, whenthe product will be sold as a multipack.

Syntax Rules: 1. P0405 - If either CTP04 or CTP05 is present, then the other is required.2. C0607 - If CTP06 is present, then CTP07 is required.3. C0902 - If CTP09 is present, then CTP02 is required.4. C1002 - If CTP10 is present, then CTP02 is required.5. C1103 - If CTP11 is present, then CTP03 is required.

Semantics: 1. CTP07 is a multiplier factor to arrive at a final discounted price. A multiplier of .90 would be the factor if a 10%

discount is given.2. CTP08 is the rebate amount.

Comments: 1.

Page 312: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Purchase Order Acknowledgment -Foodservice - 855

July 2012 [V004010-2012 FS] 19Copyright 2012 - GS1 Canada

PID Product/Item Description Pos: 050 Max: 1Detail - Optional

Loop: PID Elements: 7

User Option (Usage): UsedPurpose: To describe a product or process in coded or free-form format

Element Summary: Ref Id Element Name Req Type Min/Max UsagePID01 349 Item Description Type

Description: Code indicating the formatof a description

M ID 1/1 Must use

CodeList Summary (Total Codes: 3, Included: 3)Code NameF Free-form

User Note 1:User Note 1:The description will be found in PID05.The description will be found in PID05.

S Structured (From Industry Code List)User Note 1:User Note 1:

The description will be found in PID03 and PID04.The description will be found in PID03 and PID04.

X Semi-structured (Code and Text)User Note 1:User Note 1:

The description will be found in PID03 and PID04, and PID05.The description will be found in PID03 and PID04, and PID05.

PID02 750 Product/Process Characteristic Code

Description: Code identifying the generalclass of a product or processcharacteristic

O ID 2/3 Used

CodeList Summary (Total Codes: 217, Included: 5)Code Name08 Product73 Vendor color description74 Vendor size description75 Buyer's Color Description91 Buyer's Item Size Description

PID03 559 Agency Qualifier Code

Description: Code identifying the agencyassigning the code values

C ID 2/2 Used

CodeList Summary (Total Codes: 176, Included: 1)Code NameVI Voluntary Inter-Industry Commerce Standard (VICS) EDI

PID04 751 Product Description Code

Description: A code from an industrycode list which provides specific dataabout a product characteristic

C AN 1/12 Used

Page 313: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Purchase Order Acknowledgment -Foodservice - 855

Ref Id Element Name Req Type Min/Max Usage

July 2012 [V004010-2012 FS] 20Copyright 2012 - GS1 Canada

PID05 352 Description

Description: A free-form description toclarify the related data elements and theircontent

C AN 1/80 Used

PID06 752 Surface/Layer/Position Code

Description: Code indicating the productsurface, layer or position that is beingdescribedUser Note 1: This data element is used todescribe the relative sequence of the itemwithin the product, e.g., sequence ofbirthstones within a mother's birthstone ring.The ring is specified in the PO1 segment andthe stones in the PID segment.

User Note 1: This data element is used todescribe the relative sequence of the itemwithin the product, e.g., sequence ofbirthstones within a mother's birthstone ring.The ring is specified in the PO1 segment andthe stones in the PID segment.

O ID 2/2 Used

CodeList Summary (Total Codes: 101, Included: 12)Code NameR0 Relative Position 10R1 Relative Position 1R2 Relative Position 2R3 Relative Position 3R4 Relative Position 4R5 Relative Position 5R6 Relative Position 6R7 Relative Position 7R8 Relative Position 8R9 Relative Position 9RA Relative Position 11RB Relative Position 12

PID09 819 Language Code

Description: Code designating thelanguage used in text, from a standardcode list maintained by the InternationalStandards Organization (ISO 639)

O ID 2/3 Used

Syntax Rules: 1. C0403 - If PID04 is present, then PID03 is required.2. R0405 - At least one of PID04 or PID05 is required.3. C0703 - If PID07 is present, then PID03 is required.4. C0804 - If PID08 is present, then PID04 is required.5. C0905 - If PID09 is present, then PID05 is required.

Semantics: 1. Use PID03 to indicate the organization that publishes the code list being referred to.2. PID04 should be used for industry-specific product description codes.3. PID08 describes the physical characteristics of the product identified in PID04. A "Y" indicates that the

specified attribute applies to this item; an "N" indicates it does not apply. Any other value is indeterminate.

Page 314: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Purchase Order Acknowledgment -Foodservice - 855

July 2012 [V004010-2012 FS] 21Copyright 2012 - GS1 Canada

4. PID09 is used to identify the language being used in PID05.

Comments: 1. If PID01 equals "F", then PID05 is used. If PID01 equals "S", then PID04 is used. If PID01 equals "X", then

both PID04 and PID05 are used.2. Use PID06 when necessary to refer to the product surface or layer being described in the segment.3. PID07 specifies the individual code list of the agency specified in PID03.

User Note 1:User Note 1:The PID segment is used to provide product/item descriptions in text and or coded formats. The codes in PID04 aremaintained by the VICS EDI SMC and are only printed in this guideline.

This segment may be used to transmit semi-custom product descriptions, such as made-to-order window coverings, jewelry,furniture, apparel, automotive parts, and other customer specific products. When used for this purpose, PID04 will containthe multi-part VICS EDI Semi-Custom Product Description Code. The complete code list is contained in Section III. In additionto the VICS EDI Semi-Custom Product Description Code, PID05 may be used for text descriptions, PID06 for relativeplacement, and additional MEA segment(s) for actual measurement values.

The PID segment is used to provide product/item descriptions in text and or coded formats. The codes in PID04 aremaintained by the VICS EDI SMC and are only printed in this guideline.

This segment may be used to transmit semi-custom product descriptions, such as made-to-order window coverings, jewelry,furniture, apparel, automotive parts, and other customer specific products. When used for this purpose, PID04 will containthe multi-part VICS EDI Semi-Custom Product Description Code. The complete code list is contained in Section III. In additionto the VICS EDI Semi-Custom Product Description Code, PID05 may be used for text descriptions, PID06 for relativeplacement, and additional MEA segment(s) for actual measurement values.

Page 315: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Purchase Order Acknowledgment -Foodservice - 855

July 2012 [V004010-2012 FS] 22Copyright 2012 - GS1 Canada

PO4 Item Physical Details Pos: 090 Max: >1Detail - Optional

Loop: PO1 Elements: 6

User Option (Usage): UsedPurpose: To specify the physical qualities, packaging, weights, and dimensions relating to the item

Element Summary: Ref Id Element Name Req Type Min/Max UsagePO401 356 Pack

Description: The number of innercontainers, or number of eaches if thereare no inner containers, per outercontainer

O N0 1/6 Used

PO406 384 Gross Weight per Pack

Description: Numeric value of grossweight per pack

C R 1/9 Used

PO407 355 Unit or Basis for Measurement Code

Description: Code specifying the units inwhich a value is being expressed, ormanner in which a measurement hasbeen taken

C ID 2/2 Used

CodeList Summary (Total Codes: 794, Included: 2)Code NameKG KilogramLB Pound

PO408 385 Gross Volume per Pack

Description: Numeric value of grossvolume per pack

C R 1/9 Used

PO409 355 Unit or Basis for Measurement Code

Description: Code specifying the units inwhich a value is being expressed, ormanner in which a measurement hasbeen taken

C ID 2/2 Used

CodeList Summary (Total Codes: 794, Included: 10)Code NameCC Cubic CentimeterCF Cubic FeetCI Cubic InchesCR Cubic MeterGA GallonGI Imperial GallonsLT LiterML MilliliterPT Pint

Page 316: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Purchase Order Acknowledgment -Foodservice - 855

Code Name

July 2012 [V004010-2012 FS] 23Copyright 2012 - GS1 Canada

PX Pint, Imperial

PO414 810 Inner Pack

Description: The number of eaches perinner container

O N0 1/6 Used

Syntax Rules: 1. P0203 - If either PO402 or PO403 is present, then the other is required.2. C0506 - If PO405 is present, then PO406 is required.3. P0607 - If either PO406 or PO407 is present, then the other is required.4. P0809 - If either PO408 or PO409 is present, then the other is required.5. C1013 - If PO410 is present, then PO413 is required.6. C1113 - If PO411 is present, then PO413 is required.7. C1213 - If PO412 is present, then PO413 is required.8. L13101112 - If PO413 is present, then at least one of PO410, PO411 or PO412 is required.9. C1716 - If PO417 is present, then PO416 is required.

10. C1804 - If PO418 is present, then PO404 is required.

Semantics: 1. PO415 is used to indicate the relative layer of this package or range of packages within the layers of

packaging. Relative Position 1 (value R1) is the innermost package.2. PO416 is the package identifier or the beginning package identifier in a range of identifiers.3. PO417 is the ending package identifier in a range of identifiers.4. PO418 is the number of packages in this layer.

Comments: 1. PO403 - The "Unit or Basis for Measure Code" in this segment position is for purposes of defining the pack

(PO401) /size (PO402) measure which indicates the quantity in the inner pack unit. For example: If the cartoncontains 24 12-Ounce packages, it would be described as follows: Data element 356 = "24"; Data element357 = "12"; Data element 355 = "OZ".

2. PO413 defines the unit of measure for PO410, PO411, and PO412.

Page 317: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Purchase Order Acknowledgment -Foodservice - 855

July 2012 [V004010-2012 FS] 24Copyright 2012 - GS1 Canada

SAC Service, Promotion,Allowance, or ChargeInformation

Pos: 130 Max: 1Detail - Optional

Loop: SAC Elements: 16

User Option (Usage): UsedPurpose: To request or identify a service, promotion, allowance, or charge; to specify the amount or percentage forthe service, promotion, allowance, or charge

Element Summary: Ref Id Element Name Req Type Min/Max UsageSAC01 248 Allowance or Charge Indicator

Description: Code which indicates anallowance or charge for the servicespecified

M ID 1/1 Must use

CodeList Summary (Total Codes: 7, Included: 4)Code NameA AllowanceC ChargeN No Allowance or ChargeR Allowance Request

SAC02 1300 Service, Promotion, Allowance, orCharge Code

Description: Code identifying the service,promotion, allowance, or chargeUser Note 1: See FoodserviceImplementation Guidelines Appendix - DataElements

User Note 1: See FoodserviceImplementation Guidelines Appendix - DataElements

C ID 4/4 Used

CodeList Summary (Total Codes: 1053, Included: 5)Code NameD350 Goods and Services Credit AllowanceD360 Goods and Services Tax Charge

User Note 1:User Note 1:Provincal Tobacco Tax.Provincal Tobacco Tax.

H490 Subject To Tax On ResaleH770 Tax - State TaxH806 Tax Credit

User Note 1:User Note 1:Provincial Tax Credit.Provincial Tax Credit.

SAC03 559 Agency Qualifier Code

Description: Code identifying the agencyassigning the code values

C ID 2/2 Used

CodeList Summary (Total Codes: 176, Included: 1)

Page 318: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Purchase Order Acknowledgment -Foodservice - 855

July 2012 [V004010-2012 FS] 25Copyright 2012 - GS1 Canada

Code NameVI Voluntary Inter-Industry Commerce Standard (VICS) EDI

SAC04 1301 Agency Service, Promotion, Allowance,or Charge Code

Description: Agency maintained codeidentifying the service, promotion,allowance, or charge

C AN 1/10 Used

SAC05 610 Amount

Description: Monetary amountUser Note 1: When SAC01 contains code Aor code C, then this data element is required.This will resolve any differences between thesender's and receiver's system calculations ofamounts, i.e., rounding errors whenallowances or charges are expressed inpercentages or rates.

User Note 1: When SAC01 contains code Aor code C, then this data element is required.This will resolve any differences between thesender's and receiver's system calculations ofamounts, i.e., rounding errors whenallowances or charges are expressed inpercentages or rates.

O N2 1/15 Used

SAC06 378 Allowance/Charge Percent Qualifier

Description: Code indicating on whatbasis allowance or charge percent iscalculated

C ID 1/1 Used

CodeList Summary (Total Codes: 11, Included: 7)Code Name1 Item List Cost2 Item Net Cost3 Discount/Gross

User Note 1:User Note 1:All allowances are off the gross price including cash discount.All allowances are off the gross price including cash discount.

4 Discount/NetUser Note 1:User Note 1:

All allowances are off the gross price. Cash discounts are off the net.All allowances are off the gross price. Cash discounts are off the net.

5 Base Price per UnitUser Note 1:User Note 1:

Line item discountLine item discount

6 Base Price Amount7 Base Price Amount Less Previous Discount

User Note 1:User Note 1:Declining balance methodDeclining balance method

SAC07 332 Percent

Description: Percent expressed as apercentUser Note 1: The percent is sent with adecimal point only when needed, e.g., 10.5%is sent as ``10.5'', and 2% is sent as ``2''.

User Note 1: The percent is sent with adecimal point only when needed, e.g., 10.5%is sent as ``10.5'', and 2% is sent as ``2''.

C R 1/6 Used

SAC08 118 Rate

Description: Rate expressed in the

O R 1/9 Used

Page 319: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Purchase Order Acknowledgment -Foodservice - 855

Ref Id Element Name Req Type Min/Max Usage

July 2012 [V004010-2012 FS] 26Copyright 2012 - GS1 Canada

standard monetary denomination for thecurrency specified

SAC09 355 Unit or Basis for Measurement Code

Description: Code specifying the units inwhich a value is being expressed, ormanner in which a measurement hasbeen taken

C ID 2/2 Used

CodeList Summary (Total Codes: 794, Included: 12)Code NameBG BagBR BarrelCA CaseDR DrumEA EachGA GallonKG KilogramLB PoundLT LiterPA PailPL Pallet/Unit LoadTE Tote

SAC10 380 Quantity

Description: Numeric value of quantityUser Note 1: When SAC02 contains codeD170, this data element is required and willcontain the quantity of free goods. The unit ofmeasure is in SAC09.

SAC10 alone is used to indicate a specificquantity which could be a dollar amount, thatis applicable to the service, promotion,allowance, or charge.

User Note 1: When SAC02 contains codeD170, this data element is required and willcontain the quantity of free goods. The unit ofmeasure is in SAC09.

SAC10 alone is used to indicate a specificquantity which could be a dollar amount, thatis applicable to the service, promotion,allowance, or charge.

C R 1/15 Used

SAC11 380 Quantity

Description: Numeric value of quantity

O R 1/15 Used

SAC12 331 Allowance or Charge Method ofHandling Code

Description: Code indicating method ofhandling for an allowance or charge

O ID 2/2 Used

CodeList Summary (Total Codes: 22, Included: 6)Code Name01 Bill Back

User Note 1:User Note 1:The allowance or charge amount will be adjudicated as a separate item, i.e., a debit/creditmemo or a separate invoice. The amount will not be reflected in the invoice total amount.The allowance or charge amount will be adjudicated as a separate item, i.e., a debit/creditmemo or a separate invoice. The amount will not be reflected in the invoice total amount.

Page 320: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Purchase Order Acknowledgment -Foodservice - 855

Code Name

July 2012 [V004010-2012 FS] 27Copyright 2012 - GS1 Canada

02 Off InvoiceUser Note 1:User Note 1:

The allowance or charge amount will be reflected in the total transaction amount, e.g.,Total Invoice Amount = Merchandise Price + Charges - Allowances.The allowance or charge amount will be reflected in the total transaction amount, e.g.,Total Invoice Amount = Merchandise Price + Charges - Allowances.

03 Vendor Check to CustomerUser Note 1:User Note 1:

The vendor will issue a check directly to the customer of the retailer, or end consumer, forthe allowance or charge amount. The amount is not reflected in the total invoice amount.The vendor will issue a check directly to the customer of the retailer, or end consumer, forthe allowance or charge amount. The amount is not reflected in the total invoice amount.

04 Credit Customer AccountUser Note 1:User Note 1:

The retailer's account will be credited for the amount of the allowance or charge. Theamount is not reflected in the total invoice amount.The retailer's account will be credited for the amount of the allowance or charge. Theamount is not reflected in the total invoice amount.

05 Charge to be Paid by VendorUser Note 1:User Note 1:

The vendor is responsible for the allowance or charge amount. The exact method ofadjudication has been agreed to by the trading partners. The amount will not be reflectedin the total invoice amount.

The vendor is responsible for the allowance or charge amount. The exact method ofadjudication has been agreed to by the trading partners. The amount will not be reflectedin the total invoice amount.

06 Charge to be Paid by CustomerUser Note 1:User Note 1:

When the order/item is a direct ship to the customer, or end consumer of the retailer, theallowance or charge amount is the responsibility of the customer or end consumer. If it isnot a drop ship to the customer of the retailer, then the allowance or charge amount is theresponsibility of the retailer. The exact method of adjudication has been agreed to by thetrading partners. The amount will not be reflected in the total invoice amount.

When the order/item is a direct ship to the customer, or end consumer of the retailer, theallowance or charge amount is the responsibility of the customer or end consumer. If it isnot a drop ship to the customer of the retailer, then the allowance or charge amount is theresponsibility of the retailer. The exact method of adjudication has been agreed to by thetrading partners. The amount will not be reflected in the total invoice amount.

SAC13 127 Reference Identification

Description: Reference information asdefined for a particular Transaction Set oras specified by the ReferenceIdentification Qualifier

C AN 1/30 Used

SAC14 770 Option Number

Description: A unique number identifyingavailable promotion or allowance optionswhen more than one is offered

O AN 1/20 Used

SAC15 352 Description

Description: A free-form description toclarify the related data elements and theircontent

C AN 1/80 Used

SAC16 819 Language Code

Description: Code designating thelanguage used in text, from a standardcode list maintained by the InternationalStandards Organization (ISO 639)

O ID 2/3 Used

Syntax Rules: 1. R0203 - At least one of SAC02 or SAC03 is required.2. P0304 - If either SAC03 or SAC04 is present, then the other is required.3. P0607 - If either SAC06 or SAC07 is present, then the other is required.

Page 321: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Purchase Order Acknowledgment -Foodservice - 855

July 2012 [V004010-2012 FS] 28Copyright 2012 - GS1 Canada

4. P0910 - If either SAC09 or SAC10 is present, then the other is required.5. C1110 - If SAC11 is present, then SAC10 is required.6. L130204 - If SAC13 is present, then at least one of SAC02 or SAC04 is required.7. C1413 - If SAC14 is present, then SAC13 is required.8. C1615 - If SAC16 is present, then SAC15 is required.

Semantics: 1. If SAC01 is "A" or "C", then at least one of SAC05, SAC07, or SAC08 is required.2. SAC05 is the total amount for the service, promotion, allowance, or charge.3. If SAC05 is present with SAC07 or SAC08, then SAC05 takes precedence.4. SAC08 is the allowance or charge rate per unit. 5. SAC10 and SAC11 is the quantity basis when the allowance or charge quantity is different from the purchase

order or invoice quantity.6. SAC10 and SAC11 used together indicate a quantity range, which could be a dollar amount, that is applicable

to service, promotion, allowance, or charge.7. SAC13 is used in conjunction with SAC02 or SAC04 to provide a specific reference number as identified by

the code used.8. SAC14 is used in conjunction with SAC13 to identify an option when there is more than one option of the

promotion.9. SAC16 is used to identify the language being used in SAC15.

Comments: 1. SAC04 may be used to uniquely identify the service, promotion, allowance, or charge. In addition, it may be

used in conjunction to further the code in SAC02.2. In some business applications, it is necessary to advise the trading partner of the actual dollar amount that a

particular allowance, charge, or promotion was based on to reduce ambiguity. This amount is commonlyreferred to as "Dollar Basis Amount". It is represented in the SAC segment in SAC10 using the qualifier "DO" -Dollars in SAC09.

User Note 1:User Note 1:There is one segment for each Allowance, Charge, Service, or Promotion being specified. If this segment appears in theheader area of the transaction set, the data applies to the entire transaction set. If this segment appears in the detail areaof the transaction set, the data applies only to that line item. The data specified in the header area is exclusive of the dataspecified in the detail area; it is not the sum of the data in the detail area, i.e., allowances or charges.

There is one segment for each Allowance, Charge, Service, or Promotion being specified. If this segment appears in theheader area of the transaction set, the data applies to the entire transaction set. If this segment appears in the detail areaof the transaction set, the data applies only to that line item. The data specified in the header area is exclusive of the dataspecified in the detail area; it is not the sum of the data in the detail area, i.e., allowances or charges.

Page 322: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Purchase Order Acknowledgment -Foodservice - 855

July 2012 [V004010-2012 FS] 29Copyright 2012 - GS1 Canada

ACK Line Item Acknowledgment Pos: 270 Max: 1Detail - Optional

Loop: ACK Elements: 5

User Option (Usage): UsedPurpose: To acknowledge the ordered quantities and specify the ready date for a specific line item

Element Summary: Ref Id Element Name Req Type Min/Max UsageACK01 668 Line Item Status Code

Description: Code specifying the actiontaken by the seller on a line itemrequested by the buyer

M ID 2/2 Must use

CodeList Summary (Total Codes: 26, Included: 3)Code NameIA Item AcceptedIC Item Accepted - Changes MadeID Item Deleted

User Note 1:User Note 1:Cancellation of a line itemCancellation of a line item

ACK02 380 Quantity

Description: Numeric value of quantityUser Note 1: Quantity which the changeaffects, i.e., the quantity that applies to thedates sent in ACK04 and ACK05

User Note 1: Quantity which the changeaffects, i.e., the quantity that applies to thedates sent in ACK04 and ACK05

C R 1/15 Used

ACK03 355 Unit or Basis for Measurement Code

Description: Code specifying the units inwhich a value is being expressed, ormanner in which a measurement hasbeen takenUser Note 1: See Section III for code list.User Note 1: See Section III for code list.

C ID 2/2 Used

CodeList Summary (Total Codes: 794, Included: 12)Code NameBG BagBR BarrelCA CaseDR DrumEA EachGA GallonKG KilogramLB PoundLT LiterPA PailPL Pallet/Unit LoadTE Tote

Page 323: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Purchase Order Acknowledgment -Foodservice - 855

Ref Id Element Name Req Type Min/Max Usage

July 2012 [V004010-2012 FS] 30Copyright 2012 - GS1 Canada

ACK04 374 Date/Time Qualifier

Description: Code specifying type of dateor time, or both date and time

O ID 3/3 Used

CodeList Summary (Total Codes: 1112, Included: 2)Code Name068 Current Schedule Ship100 No Shipping Schedule Established as of

ACK05 373 Date

Description: Date expressed asCCYYMMDD

C DT 8/8 Used

Syntax Rules: 1. P0203 - If either ACK02 or ACK03 is present, then the other is required.2. C0405 - If ACK04 is present, then ACK05 is required.3. P0708 - If either ACK07 or ACK08 is present, then the other is required.4. P0910 - If either ACK09 or ACK10 is present, then the other is required.5. P1112 - If either ACK11 or ACK12 is present, then the other is required.6. P1314 - If either ACK13 or ACK14 is present, then the other is required.7. P1516 - If either ACK15 or ACK16 is present, then the other is required.8. P1718 - If either ACK17 or ACK18 is present, then the other is required.9. P1920 - If either ACK19 or ACK20 is present, then the other is required.

10. P2122 - If either ACK21 or ACK22 is present, then the other is required.11. P2324 - If either ACK23 or ACK24 is present, then the other is required.12. P2526 - If either ACK25 or ACK26 is present, then the other is required.13. P2728 - If either ACK27 or ACK28 is present, then the other is required.14. C282729 - If ACK28 is present, then ACK27 and ACK29 are required.

Semantics: 1. ACK29 Industry Reason Code may be used to identify the item status. In addition, it may be used in

conjunction with ACK01 to further clarify the status.

User Note 1:User Note 1:This segment may be used to indicate that a line item has been accepted, deleted, or changed. Some product productioncycles, such as furniture, are long and may have different ship dates than the original purchase order. This segment may beused to inform the originator of the current ship date or that no ship date has been scheduled.

This segment may be used to indicate that a line item has been accepted, deleted, or changed. Some product productioncycles, such as furniture, are long and may have different ship dates than the original purchase order. This segment may beused to inform the originator of the current ship date or that no ship date has been scheduled.

Page 324: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Purchase Order Acknowledgment -Foodservice - 855

July 2012 [V004010-2012 FS] 31Copyright 2012 - GS1 Canada

CTT Transaction Totals Pos: 010 Max: 1Summary - Optional

Loop: CTT Elements: 1

User Option (Usage): UsedPurpose: To transmit a hash total for a specific element in the transaction set

Element Summary: Ref Id Element Name Req Type Min/Max UsageCTT01 354 Number of Line Items

Description: Total number of line items inthe transaction setUser Note 1: The number of PO1 segmentspresent in the transaction setUser Note 1: The number of PO1 segmentspresent in the transaction set

M N0 1/6 Must use

Syntax Rules: 1. P0304 - If either CTT03 or CTT04 is present, then the other is required.2. P0506 - If either CTT05 or CTT06 is present, then the other is required.

Comments: 1. This segment is intended to provide hash totals to validate transaction completeness and correctness.

Page 325: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Purchase Order Acknowledgment -Foodservice - 855

July 2012 [V004010-2012 FS] 32Copyright 2012 - GS1 Canada

SE Transaction Set Trailer Pos: 030 Max: 1Summary - Mandatory

Loop: N/A Elements: 2

User Option (Usage): Must usePurpose: To indicate the end of the transaction set and provide the count of the transmitted segments (including thebeginning (ST) and ending (SE) segments)

Element Summary: Ref Id Element Name Req Type Min/Max UsageSE01 96 Number of Included Segments

Description: Total number of segmentsincluded in a transaction set including STand SE segments

M N0 1/10 Must use

SE02 329 Transaction Set Control Number

Description: Identifying control numberthat must be unique within the transactionset functional group assigned by theoriginator for a transaction setUser Note 1: This must be the same numberas is in the ST segment (ST02) for thetransaction set.

User Note 1: This must be the same numberas is in the ST segment (ST02) for thetransaction set.

M AN 4/9 Must use

Comments: 1. SE is the last segment of each transaction set.

Page 326: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

856 Ship Notice/ManifestFS

Foodservice EDI

Version: 4010-2012 Final

Author: GS1 Canada -Foodservice TechnicalStandards Work Group

Publication: 7/1/2012 Notes: For Implementation

December2012

Page 327: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Ship Notice/Manifest - Foodservice - 856

July 2012 [V004010-2012 FS] iCopyright 2012 - GS1 Canada

Table of Contents

856 Ship Notice/Manifest - Foodservice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>ST Transaction Set Header . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>BSN Beginning Segment for Ship Notice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>HL Hierarchical Level - Shipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>TD1 Carrier Details (Quantity and Weight) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>TD5 Carrier Details (Routing Sequence/Transit Time) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>TD3 Carrier Details (Equipment) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>TD4 Carrier Details (Special Handling, or Hazardous Materials, or Both) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>REF Reference Identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>PER Administrative Communications Contact . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>DTM Date/Time Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>N1 Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>N2 Additional Name Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>N3 Address Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>N4 Geographic Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>HL Hierarchical Level - Unit or Lot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>TD3 Carrier Details (Equipment) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>MAN Marks and Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>HL Hierarchical Level - Order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>PRF Purchase Order Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>TD1 Carrier Details (Quantity and Weight) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>REF Reference Identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>N1 Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>N2 Additional Name Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>N3 Address Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>N4 Geographic Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>HL Hierarchical Level - Shipping Tare . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>MAN Marks and Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>PAL Pallet Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>HL Hierarchical Level - Pack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>LIN Item Identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>SN1 Item Detail (Shipment) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>MAN Marks and Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>HL Hierarchical Level - Item . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>LIN Item Identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>SN1 Item Detail (Shipment) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>PO4 Item Physical Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>PID Product/Item Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>REF Reference Identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>

. . . . . 1. . . . . 4. . . . . 5. . . . . 7. . . . . 8. . . . 11. . . . 13. . . . 14. . . . 15. . . . 16. . . . 18. . . . 19. . . . 21. . . . 22. . . . 23. . . . 24. . . . 26. . . . 27. . . . 28. . . . 30. . . . 31. . . . 33. . . . 35. . . . 37. . . . 38. . . . 39. . . . 40. . . . 42. . . . 43. . . . 45. . . . 47. . . . 49. . . . 50. . . . 52. . . . 54. . . . 56. . . . 57. . . . 59. . . . 61

Page 328: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Ship Notice/Manifest - Foodservice - 856

July 2012 [V004010-2012 FS] iiCopyright 2012 - GS1 Canada

DTM Date/Time Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>CTT Transaction Totals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>SE Transaction Set Trailer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>

. . . . 62

. . . . 63

. . . . 64

Page 329: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Ship Notice/Manifest - Foodservice - 856

July 2012 [V004010-2012 FS] 1Copyright 2012 - GS1 Canada

856 Ship Notice/Manifest - FoodserviceFunctional Group=SH

Purpose: This Draft Standard for Trial Use contains the format and establishes the data contents of the ShipNotice/Manifest Transaction Set (856) for use within the context of an Electronic Data Interchange (EDI)environment. The transaction set can be used to list the contents of a shipment of goods as well as additionalinformation relating to the shipment, such as order information, product description, physical characteristics, type ofpackaging, marking, carrier information, and configuration of goods within the transportation equipment. Thetransaction set enables the sender to describe the contents and configuration of a shipment in various levels of detailand provides an ordered flexibility to convey information.The sender of this transaction is the organizationresponsible for detailing and communicating the contents of a shipment, or shipments, to one or more receivers ofthe transaction set. The receiver of this transaction set can be any organization having an interest in the contents ofa shipment or information about the contents of a shipment.

Heading:Pos Id Segment Name Req Max Use Repeat Notes Usage010 ST Transaction Set Header M 1 Must use020 BSN Beginning Segment for Ship

NoticeM 1 Must use

Detail:Pos Id Segment Name Req Max Use Repeat Notes Usage

LOOP ID - HL 200000 C2/010L LOOP ID - HL 200000 C2/010L

010 HL Hierarchical Level -Shipment

M 1 C2/010 Must use

110 TD1 Carrier Details (Quantityand Weight)

O 20 Used

120 TD5 Carrier Details (RoutingSequence/Transit Time)

O 12 Used

130 TD3 Carrier Details (Equipment) O 12 Used140 TD4 Carrier Details (Special

Handling, or HazardousMaterials, or Both)

O 5 Used

150 REF Reference Identification O >1 Used151 PER Administrative

Communications ContactO 3 Used

200 DTM Date/Time Reference O 10 Used LOOP ID - N1 200 LOOP ID - N1 200

220 N1 Name O 1 Used230 N2 Additional Name

InformationO 2 Used

240 N3 Address Information O 2 Used250 N4 Geographic Location O 1 Used

LOOP ID - HL 200000 C2/010L LOOP ID - HL 200000 C2/010L

010 HL Hierarchical Level - Unit orLot

M 1 C2/010 Must use

130 TD3 Carrier Details (Equipment) O 12 Used190 MAN Marks and Numbers O >1 Used

LOOP ID - HL 200000 C2/010L LOOP ID - HL 200000 C2/010L

010 HL Hierarchical Level - Order M 1 C2/010 Must use

Page 330: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Ship Notice/Manifest - Foodservice - 856

Pos Id Segment Name Req Max Use Repeat Notes Usage

July 2012 [V004010-2012 FS] 2Copyright 2012 - GS1 Canada

050 PRF Purchase Order Reference O 1 Used110 TD1 Carrier Details (Quantity

and Weight)O 20 Used

150 REF Reference Identification O >1 Used LOOP ID - N1 200 LOOP ID - N1 200

220 N1 Name O 1 Used230 N2 Additional Name

InformationO 2 Used

240 N3 Address Information O 2 Used250 N4 Geographic Location O 1 Used

LOOP ID - HL 200000 C2/010L LOOP ID - HL 200000 C2/010L

010 HL Hierarchical Level -Shipping Tare

M 1 C2/010 Must use

190 MAN Marks and Numbers O >1 Used215 PAL Pallet Information O 1 Used

LOOP ID - HL 200000 C2/010L LOOP ID - HL 200000 C2/010L

010 HL Hierarchical Level - Pack M 1 C2/010 Must use020 LIN Item Identification O 1 Used030 SN1 Item Detail (Shipment) O 1 Used190 MAN Marks and Numbers O >1 Used

LOOP ID - HL 200000 C2/010L LOOP ID - HL 200000 C2/010L

010 HL Hierarchical Level - Item M 1 C2/010 Must use020 LIN Item Identification O 1 Used030 SN1 Item Detail (Shipment) O 1 Used060 PO4 Item Physical Details O 1 Used070 PID Product/Item Description O 200 Used150 REF Reference Identification O >1 Used200 DTM Date/Time Reference O 10 Used

Summary:Pos Id Segment Name Req Max Use Repeat Notes Usage010 CTT Transaction Totals O 1 N3/010 Used020 SE Transaction Set Trailer M 1 Must use

Notes: 3/010 Number of line items (CTT01) is the accumulation of the number of HL segments. If used, hash total

(CTT02) is the sum of the value of units shipped (SN102) for each SN1 segment.

Comments: 2/010L The HL segment is the only mandatory segment within the HL loop, and by itself, the HL segment has no

meaning.2/010 The HL segment is the only mandatory segment within the HL loop, and by itself, the HL segment has no

meaning.2/010L The HL segment is the only mandatory segment within the HL loop, and by itself, the HL segment has no

meaning.2/010 The HL segment is the only mandatory segment within the HL loop, and by itself, the HL segment has no

meaning.

Page 331: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Ship Notice/Manifest - Foodservice - 856

July 2012 [V004010-2012 FS] 3Copyright 2012 - GS1 Canada

2/010L The HL segment is the only mandatory segment within the HL loop, and by itself, the HL segment has nomeaning.

2/010 The HL segment is the only mandatory segment within the HL loop, and by itself, the HL segment has nomeaning.

2/010L The HL segment is the only mandatory segment within the HL loop, and by itself, the HL segment has nomeaning.

2/010 The HL segment is the only mandatory segment within the HL loop, and by itself, the HL segment has nomeaning.

2/010L The HL segment is the only mandatory segment within the HL loop, and by itself, the HL segment has nomeaning.

2/010 The HL segment is the only mandatory segment within the HL loop, and by itself, the HL segment has nomeaning.

2/010L The HL segment is the only mandatory segment within the HL loop, and by itself, the HL segment has nomeaning.

2/010 The HL segment is the only mandatory segment within the HL loop, and by itself, the HL segment has nomeaning.

Page 332: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Ship Notice/Manifest - Foodservice - 856

July 2012 [V004010-2012 FS] 4Copyright 2012 - GS1 Canada

ST Transaction Set Header Pos: 010 Max: 1Heading - Mandatory

Loop: N/A Elements: 2

User Option (Usage): Must usePurpose: To indicate the start of a transaction set and to assign a control number

Element Summary: Ref Id Element Name Req Type Min/Max UsageST01 143 Transaction Set Identifier Code

Description: Code uniquely identifying aTransaction Set

M ID 3/3 Must use

CodeList Summary (Total Codes: 298, Included: 1)Code Name856 Ship Notice/Manifest

ST02 329 Transaction Set Control Number

Description: Identifying control numberthat must be unique within the transactionset functional group assigned by theoriginator for a transaction setUser Note 1: The number is sequentiallyassigned by the sender, starting with onewithin each functional group. For eachfunctional group, the first transaction setcontrol number will be 0001 and incrementedby one for each additional transaction setwithin the group.

User Note 1: The number is sequentiallyassigned by the sender, starting with onewithin each functional group. For eachfunctional group, the first transaction setcontrol number will be 0001 and incrementedby one for each additional transaction setwithin the group.

M AN 4/9 Must use

Semantics: 1. The transaction set identifier (ST01) used by the translation routines of the interchange partners to select the

appropriate transaction set definition (e.g., 810 selects the Invoice Transaction Set).

Page 333: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Ship Notice/Manifest - Foodservice - 856

July 2012 [V004010-2012 FS] 5Copyright 2012 - GS1 Canada

BSN Beginning Segment for ShipNotice

Pos: 020 Max: 1Heading - Mandatory

Loop: N/A Elements: 5

User Option (Usage): Must usePurpose: To transmit identifying numbers, dates, and other basic data relating to the transaction set

Element Summary: Ref Id Element Name Req Type Min/Max UsageBSN01 353 Transaction Set Purpose Code

Description: Code identifying purpose oftransaction set

M ID 2/2 Must use

CodeList Summary (Total Codes: 65, Included: 2)Code Name00 Original07 Duplicate

BSN02 396 Shipment Identification

Description: A unique control numberassigned by the original shipper to identifya specific shipment

M AN 2/30 Must use

BSN03 373 Date

Description: Date expressed asCCYYMMDD

M DT 8/8 Must use

BSN04 337 Time

Description: Time expressed in 24-hourclock time as follows: HHMM, orHHMMSS, or HHMMSSD, orHHMMSSDD, where H = hours (00-23), M= minutes (00-59), S = integer seconds(00-59) and DD = decimal seconds;decimal seconds are expressed asfollows: D = tenths (0-9) and DD =hundredths (00-99)

M TM 4/8 Must use

BSN05 1005 Hierarchical Structure Code

Description: Code indicating thehierarchical application structure of atransaction set that utilizes the HLsegment to define the structure of thetransaction set

O ID 4/4 Must use

CodeList Summary (Total Codes: 61, Included: 1)Code Name0001 Shipment, Order, Packaging, Item

User Note 1:User Note 1:Pick and Pack StructurePick and Pack Structure

Syntax Rules:

Page 334: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Ship Notice/Manifest - Foodservice - 856

July 2012 [V004010-2012 FS] 6Copyright 2012 - GS1 Canada

1. C0706 - If BSN07 is present, then BSN06 is required.

Semantics: 1. BSN03 is the date the shipment transaction set is created.2. BSN04 is the time the shipment transaction set is created.3. BSN06 is limited to shipment related codes.

Comments: 1. BSN06 and BSN07 differentiate the functionality of use for the transaction set.

User Note 1:User Note 1:In some implementations, it may be appropriate to omit the unit load level and packaging levels, i.e., tare and pack, from thetransaction set. Depending on the retailer's receiving systems, carton identification may not be required. Code 0004 in BSN05indicates the use of a hierarchical structure that does not include a unit load level or any packaging levels.

In some implementations, it may be appropriate to omit the unit load level and packaging levels, i.e., tare and pack, from thetransaction set. Depending on the retailer's receiving systems, carton identification may not be required. Code 0004 in BSN05indicates the use of a hierarchical structure that does not include a unit load level or any packaging levels.

Page 335: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Ship Notice/Manifest - Foodservice - 856

July 2012 [V004010-2012 FS] 7Copyright 2012 - GS1 Canada

HL Hierarchical Level - Shipment Pos: 010 Max: 1Detail - Mandatory

Loop: HL Elements: 2

User Option (Usage): Must usePurpose: To identify dependencies among and the content of hierarchically related groups of data segments

Element Summary: Ref Id Element Name Req Type Min/Max UsageHL01 628 Hierarchical ID Number

Description: A unique number assignedby the sender to identify a particular datasegment in a hierarchical structureUser Note 1: The value for this level(shipment) is 1.User Note 1: The value for this level(shipment) is 1.

M AN 1/12 Must use

HL03 735 Hierarchical Level Code

Description: Code defining thecharacteristic of a level in a hierarchicalstructure

M ID 1/2 Must use

CodeList Summary (Total Codes: 170, Included: 1)Code NameS Shipment

Comments: 1. The HL segment is used to identify levels of detail information using a hierarchical structure, such as relating

line-item data to shipment data, and packaging data to line-item data.2. The HL segment defines a top-down/left-right ordered structure.3. HL01 shall contain a unique alphanumeric number for each occurrence of the HL segment in the transaction

set. For example, HL01 could be used to indicate the number of occurrences of the HL segment, in whichcase the value of HL01 would be "1" for the initial HL segment and would be incremented by one in eachsubsequent HL segment within the transaction.

4. HL02 identifies the hierarchical ID number of the HL segment to which the current HL segment is subordinate.5. HL03 indicates the context of the series of segments following the current HL segment up to the next

occurrence of an HL segment in the transaction. For example, HL03 is used to indicate that subsequentsegments in the HL loop form a logical grouping of data referring to shipment, order, or item-level information.

6. HL04 indicates whether or not there are subordinate (or child) HL segments related to the current HLsegment.

User Note 1:User Note 1:The HL segment is used to identify levels of detail information using a hierarchical structure.

HL01 shall contain a unique number for each occurrence of the HL segment within the transaction set. The value assigned tothe first HL segment will be 1, and is incremented by one for each subsequent HL segment within the transaction set.

HL02 identifies the hierarchical ID of the HL segment to which it is subordinate (child of). HL02 will be omitted for the firstoccurrence of the HL segment in the transaction set, since it has no parent. HL03 identifies the application content of theseries of segments following the current HL segment up to the next occurrence of an HL segment, or the CTT or SE segment,e.g., Shipment, Unit Load, Order, Tare, Pack and Item.

The HL segment is used to identify levels of detail information using a hierarchical structure.

HL01 shall contain a unique number for each occurrence of the HL segment within the transaction set. The value assigned tothe first HL segment will be 1, and is incremented by one for each subsequent HL segment within the transaction set.

HL02 identifies the hierarchical ID of the HL segment to which it is subordinate (child of). HL02 will be omitted for the firstoccurrence of the HL segment in the transaction set, since it has no parent. HL03 identifies the application content of theseries of segments following the current HL segment up to the next occurrence of an HL segment, or the CTT or SE segment,e.g., Shipment, Unit Load, Order, Tare, Pack and Item.

Page 336: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Ship Notice/Manifest - Foodservice - 856

July 2012 [V004010-2012 FS] 8Copyright 2012 - GS1 Canada

TD1 Carrier Details (Quantity andWeight)

Pos: 110 Max: 20Detail - Optional

Loop: HL Elements: 7

User Option (Usage): UsedPurpose: To specify the transportation details relative to commodity, weight, and quantity

Element Summary: Ref Id Element Name Req Type Min/Max UsageTD101 103 Packaging Code

Description: Code identifying the type ofpackaging; Part 1: Packaging Form, Part2: Packaging Material; if the Data Elementis used, then Part 1 is always required

O AN 3/5 Used

CodeList Summary (Total Codes: 148, Included: 6)Code NameBAG BagCTN CartonMIX Mixed Container Types

Description: More than one type of container is included in a shipment (shipment couldconsist of 3 pieces that include 1 box, 1 crate, and 1 basket)

User Note 1:User Note 1:Can be used only with code 71 in Part 2Can be used only with code 71 in Part 2

PLT PalletSLP Slip Sheet

Description: Shipping containers utilizing slip sheets, which are cardboard platforms usedto hold product for storage or transportation

SRW Shrink WrapDescription: In packaging, a method of securing a unit load by placing a large "bag" ofplastic film over the components and applying heat to induce shrinkage and cause the bagto tighten around the contents

CodeList Summary (Total Codes: 55, Included: 9)Code Name01 Aluminum25 Corrugated or Solid31 Fibre58 Metal71 Not Otherwise Specified76 Paper79 Plastic91 Stainless Steel94 Wood

TD102 80 Lading Quantity

Description: Number of units (pieces) ofthe lading commodityUser Note 1: The number of packages in theshipment as described in TD101User Note 1: The number of packages in theshipment as described in TD101

C N0 1/7 Used

Page 337: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Ship Notice/Manifest - Foodservice - 856

Ref Id Element Name Req Type Min/Max Usage

July 2012 [V004010-2012 FS] 9Copyright 2012 - GS1 Canada

TD106 187 Weight Qualifier

Description: Code defining the type ofweight

O ID 1/2 Used

CodeList Summary (Total Codes: 51, Included: 1)Code NameG Gross Weight

TD107 81 Weight

Description: Numeric value of weight

C R 1/10 Used

TD108 355 Unit or Basis for Measurement Code

Description: Code specifying the units inwhich a value is being expressed, ormanner in which a measurement hasbeen taken

C ID 2/2 Used

CodeList Summary (Total Codes: 794, Included: 2)Code NameKG KilogramLB Pound

TD109 183 Volume

Description: Value of volumetricmeasureUser Note 1: Gross volumeUser Note 1: Gross volume

C R 1/8 Used

TD110 355 Unit or Basis for Measurement Code

Description: Code specifying the units inwhich a value is being expressed, ormanner in which a measurement hasbeen taken

C ID 2/2 Used

CodeList Summary (Total Codes: 794, Included: 10)Code NameCC Cubic CentimeterCF Cubic FeetCI Cubic InchesCR Cubic MeterGA GallonGI Imperial GallonsLT LiterML MilliliterPT PintPX Pint, Imperial

Syntax Rules: 1. C0102 - If TD101 is present, then TD102 is required.2. C0304 - If TD103 is present, then TD104 is required.3. C0607 - If TD106 is present, then TD107 is required.

Page 338: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Ship Notice/Manifest - Foodservice - 856

July 2012 [V004010-2012 FS] 10Copyright 2012 - GS1 Canada

4. P0708 - If either TD107 or TD108 is present, then the other is required.5. P0910 - If either TD109 or TD110 is present, then the other is required.

User Note 1:User Note 1:This segment, at the shipment level, is used to specify total containers and gross weight of the shipment.This segment, at the shipment level, is used to specify total containers and gross weight of the shipment.

Page 339: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Ship Notice/Manifest - Foodservice - 856

July 2012 [V004010-2012 FS] 11Copyright 2012 - GS1 Canada

TD5 Carrier Details (RoutingSequence/Transit Time)

Pos: 120 Max: 12Detail - Optional

Loop: HL Elements: 6

User Option (Usage): UsedPurpose: To specify the carrier and sequence of routing and provide transit time information

Element Summary: Ref Id Element Name Req Type Min/Max UsageTD501 133 Routing Sequence Code

Description: Code describing therelationship of a carrier to a specificshipment movement

O ID 1/2 Used

CodeList Summary (Total Codes: 23, Included: 13)Code Name1 1st Carrier after Origin Carrier2 2nd Carrier after Origin Carrier3 3rd Carrier after Origin Carrier4 4th Carrier after Origin Carrier5 5th Carrier after Origin Carrier6 6th Carrier after Origin Carrier7 7th Carrier after Origin Carrier8 8th Carrier after Origin Carrier9 9th Carrier after Origin CarrierA Origin Carrier, Agent's Routing (Rail)B Origin/Delivery Carrier (Any Mode)O Origin Carrier (Air, Motor, or Ocean)S Origin Carrier, Shipper's Routing (Rail)

TD502 66 Identification Code Qualifier

Description: Code designating thesystem/method of code structure used forIdentification Code (67)

C ID 1/2 Used

CodeList Summary (Total Codes: 215, Included: 1)Code Name2 Standard Carrier Alpha Code (SCAC)

TD503 67 Identification Code

Description: Code identifying a party orother code

C AN 2/80 Used

TD504 91 Transportation Method/Type Code

Description: Code specifying the methodor type of transportation for the shipment

C ID 1/2 Used

CodeList Summary (Total Codes: 71, Included: 3)Code NameH Customer Pickup

Page 340: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Ship Notice/Manifest - Foodservice - 856

Code Name

July 2012 [V004010-2012 FS] 12Copyright 2012 - GS1 Canada

M Motor (Common Carrier)R Rail

TD505 387 Routing

Description: Free-form description of therouting or requested routing for shipment,or the originating carrier's identity

C AN 1/35 Used

TD506 368 Shipment/Order Status Code

Description: Code indicating the statusof an order or shipment or the dispositionof any difference between the quantityordered and the quantity shipped for a lineitem or transaction

C ID 2/2 Used

CodeList Summary (Total Codes: 102, Included: 1)Code NameCC Shipment Complete on (Date)

Syntax Rules: 1. R0204050612 - At least one of TD502, TD504, TD505, TD506 or TD512 is required.2. C0203 - If TD502 is present, then TD503 is required.3. C0708 - If TD507 is present, then TD508 is required.4. C1011 - If TD510 is present, then TD511 is required.5. C1312 - If TD513 is present, then TD512 is required.6. C1413 - If TD514 is present, then TD513 is required.7. C1512 - If TD515 is present, then TD512 is required.

Semantics: 1. TD515 is the country where the service is to be performed.

Comments: 1. When specifying a routing sequence to be used for the shipment movement in lieu of specifying each carrier

within the movement, use TD502 to identify the party responsible for defining the routing sequence, and useTD503 to identify the actual routing sequence, specified by the party identified in TD502.

User Note 1:User Note 1:This segment is used to specify every carrier in the routing sequence or a specific routing sequence that has been previouslyidentified (usually from a routing guide). The segment can also be used to indicate estimated transit time in days. Only useTD501 if needed for clarity; this is not a requirement in most retail applications. When referring to a pre-established routingguide, use code 91 or 92 in TD502 and identify the routing sequence, from the routing guide, in TD503. To identify a specificprivate parcel service, TD502 will contain code 2 and TD503 will contain the corresponding SCAC. TD510 and TD511 are usedto specify transit time.

When using a small package service provider as the carrier, TD502 will contain code 2, TD503 will contain the carrier's SCAC,and TD504 will contain code U to inform the receiver of a small package service shipment.

This segment is used to specify every carrier in the routing sequence or a specific routing sequence that has been previouslyidentified (usually from a routing guide). The segment can also be used to indicate estimated transit time in days. Only useTD501 if needed for clarity; this is not a requirement in most retail applications. When referring to a pre-established routingguide, use code 91 or 92 in TD502 and identify the routing sequence, from the routing guide, in TD503. To identify a specificprivate parcel service, TD502 will contain code 2 and TD503 will contain the corresponding SCAC. TD510 and TD511 are usedto specify transit time.

When using a small package service provider as the carrier, TD502 will contain code 2, TD503 will contain the carrier's SCAC,and TD504 will contain code U to inform the receiver of a small package service shipment.

Page 341: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Ship Notice/Manifest - Foodservice - 856

July 2012 [V004010-2012 FS] 13Copyright 2012 - GS1 Canada

TD3 Carrier Details (Equipment) Pos: 130 Max: 12Detail - Optional

Loop: HL Elements: 3

User Option (Usage): UsedPurpose: To specify transportation details relating to the equipment used by the carrier

Element Summary: Ref Id Element Name Req Type Min/Max UsageTD301 40 Equipment Description Code

Description: Code identifying type ofequipment used for shipment

C ID 2/2 Must use

CodeList Summary (Total Codes: 134, Included: 4)Code NameCV Closed VanFT Flat Bed TrailerRT Controlled Temperature Trailer (Reefer)TL Trailer (not otherwise specified)

TD302 206 Equipment Initial

Description: Prefix or alphabetic part ofan equipment unit's identifying number

O AN 1/4 Used

TD303 207 Equipment Number

Description: Sequencing or serial part ofan equipment unit's identifying number(pure numeric form for equipment numberis preferred)

C AN 1/10 Used

Syntax Rules: 1. E0110 - Only one of TD301 or TD310 may be present.2. C0203 - If TD302 is present, then TD303 is required.3. C0405 - If TD304 is present, then TD305 is required.4. P0506 - If either TD305 or TD306 is present, then the other is required.

User Note 1:User Note 1:This segment is used to specify the trailer number for a truckload shipment.This segment is used to specify the trailer number for a truckload shipment.

Page 342: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Ship Notice/Manifest - Foodservice - 856

July 2012 [V004010-2012 FS] 14Copyright 2012 - GS1 Canada

TD4 Carrier Details (SpecialHandling, or HazardousMaterials, or Both)

Pos: 140 Max: 5Detail - Optional

Loop: HL Elements: 1

User Option (Usage): UsedPurpose: To specify transportation special handling requirements, or hazardous materials information, or both

Element Summary: Ref Id Element Name Req Type Min/Max UsageTD401 152 Special Handling Code

Description: Code specifying specialtransportation handling instructions

C ID 2/3 Must use

CodeList Summary (Total Codes: 526, Included: 6)Code NameCC Container, Consolidator Load

Description: Full container

CF Container, Factory LoadDescription: Full container, not to be opened for consolidation

LN Less Than Container, Consolidator LoadLR Less Than Container, Factory LoadTC Trailer, Consolidator Load

Description: Full trailer

TF Trailer, Factory LoadDescription: Full trailer, not to be opened for consolidation

Syntax Rules: 1. R010204 - At least one of TD401, TD402 or TD404 is required.2. C0203 - If TD402 is present, then TD403 is required.

Semantics: 1. TD405 identifies if a Material Safety Data Sheet (MSDS) exists for this product. A "Y" indicates an MSDS

exists for this product; an "N" indicates an MSDS does not exist for this product.

Page 343: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Ship Notice/Manifest - Foodservice - 856

July 2012 [V004010-2012 FS] 15Copyright 2012 - GS1 Canada

REF Reference Identification Pos: 150 Max: >1Detail - Optional

Loop: HL Elements: 2

User Option (Usage): UsedPurpose: To specify identifying information

Element Summary: Ref Id Element Name Req Type Min/Max UsageREF01 128 Reference Identification Qualifier

Description: Code qualifying theReference Identification

M ID 2/3 Must use

CodeList Summary (Total Codes: 1503, Included: 3)Code NameBM Bill of Lading NumberCN Carrier's Reference Number (PRO/Invoice)MB Master Bill of Lading

REF02 127 Reference Identification

Description: Reference information asdefined for a particular Transaction Set oras specified by the ReferenceIdentification Qualifier

C AN 1/30 Must use

Syntax Rules: 1. R0203 - At least one of REF02 or REF03 is required.

Semantics: 1. REF04 contains data relating to the value cited in REF02.

User Note 1:User Note 1:In some cases, individual shipments with bill of lading may be grouped under a Master Bill of Lading. Under thiscircumstance, specifying both the bill of lading and the associated Master Bill of Lading Number will facilitate tracking.In some cases, individual shipments with bill of lading may be grouped under a Master Bill of Lading. Under thiscircumstance, specifying both the bill of lading and the associated Master Bill of Lading Number will facilitate tracking.

Page 344: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Ship Notice/Manifest - Foodservice - 856

July 2012 [V004010-2012 FS] 16Copyright 2012 - GS1 Canada

PER AdministrativeCommunications Contact

Pos: 151 Max: 3Detail - Optional

Loop: HL Elements: 6

User Option (Usage): UsedPurpose: To identify a person or office to whom administrative communications should be directed

Element Summary: Ref Id Element Name Req Type Min/Max UsagePER01 366 Contact Function Code

Description: Code identifying the majorduty or responsibility of the person orgroup named

M ID 2/2 Must use

CodeList Summary (Total Codes: 230, Included: 1)Code NameDI Delivery Instructions Contact

PER02 93 Name

Description: Free-form name

O AN 1/60 Used

PER03 365 Communication Number Qualifier

Description: Code identifying the type ofcommunication number

C ID 2/2 Used

CodeList Summary (Total Codes: 40, Included: 2)Code NameEM Electronic MailTE Telephone

PER04 364 Communication Number

Description: Complete communicationsnumber including country or area codewhen applicable

C AN 1/80 Used

PER05 365 Communication Number Qualifier

Description: Code identifying the type ofcommunication number

C ID 2/2 Used

CodeList Summary (Total Codes: 40, Included: 2)Code NameEM Electronic MailTE Telephone

PER06 364 Communication Number

Description: Complete communicationsnumber including country or area codewhen applicable

C AN 1/80 Used

Syntax Rules: 1. P0304 - If either PER03 or PER04 is present, then the other is required.

Page 345: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Ship Notice/Manifest - Foodservice - 856

July 2012 [V004010-2012 FS] 17Copyright 2012 - GS1 Canada

2. P0506 - If either PER05 or PER06 is present, then the other is required.3. P0708 - If either PER07 or PER08 is present, then the other is required.

Page 346: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Ship Notice/Manifest - Foodservice - 856

July 2012 [V004010-2012 FS] 18Copyright 2012 - GS1 Canada

DTM Date/Time Reference Pos: 200 Max: 10Detail - Optional

Loop: HL Elements: 3

User Option (Usage): UsedPurpose: To specify pertinent dates and times

Element Summary: Ref Id Element Name Req Type Min/Max UsageDTM01 374 Date/Time Qualifier

Description: Code specifying type of dateor time, or both date and time

M ID 3/3 Must use

CodeList Summary (Total Codes: 1112, Included: 6)Code Name011 Shipped017 Estimated Delivery067 Current Schedule Delivery068 Current Schedule ShipAA1 Estimated Point of ArrivalAA2 Estimated Point of Discharge

DTM02 373 Date

Description: Date expressed asCCYYMMDD

C DT 8/8 Must use

DTM03 337 Time

Description: Time expressed in 24-hourclock time as follows: HHMM, orHHMMSS, or HHMMSSD, orHHMMSSDD, where H = hours (00-23), M= minutes (00-59), S = integer seconds(00-59) and DD = decimal seconds;decimal seconds are expressed asfollows: D = tenths (0-9) and DD =hundredths (00-99)

C TM 4/8 Used

Syntax Rules: 1. R020305 - At least one of DTM02, DTM03 or DTM05 is required.2. C0403 - If DTM04 is present, then DTM03 is required.3. P0506 - If either DTM05 or DTM06 is present, then the other is required.

Page 347: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Ship Notice/Manifest - Foodservice - 856

July 2012 [V004010-2012 FS] 19Copyright 2012 - GS1 Canada

N1 Name Pos: 220 Max: 1Detail - Optional

Loop: N1 Elements: 4

User Option (Usage): UsedPurpose: To identify a party by type of organization, name, and code

Element Summary: Ref Id Element Name Req Type Min/Max UsageN101 98 Entity Identifier Code

Description: Code identifying anorganizational entity, a physical location,property or an individual

M ID 2/3 Must use

CodeList Summary (Total Codes: 1312, Included: 2)Code NameSF Ship FromST Ship To

N102 93 Name

Description: Free-form name

C AN 1/60 Used

N103 66 Identification Code Qualifier

Description: Code designating thesystem/method of code structure used forIdentification Code (67)

C ID 1/2 Used

CodeList Summary (Total Codes: 215, Included: 2)Code Name9 D-U-N-S+4, D-U-N-S Number with Four Character SuffixUL UCC/EAN Location Code

Description: Global Location Number (GLN) (Revised name) A globally unique 13 digit code used for the identification of any physical or legal locationthat needs to be uniquely identified for use in the supply chain. A GS1 identification key SEE CODE SOURCE 583

N104 67 Identification Code

Description: Code identifying a party orother code

C AN 2/80 Used

Syntax Rules: 1. R0203 - At least one of N102 or N103 is required.2. P0304 - If either N103 or N104 is present, then the other is required.

Comments: 1. This segment, used alone, provides the most efficient method of providing organizational identification. To

obtain this efficiency the "ID Code" (N104) must provide a key to the table maintained by the transactionprocessing party.

2. N105 and N106 further define the type of entity in N101.

User Note 1:User Note 1:

Page 348: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Ship Notice/Manifest - Foodservice - 856

July 2012 [V004010-2012 FS] 20Copyright 2012 - GS1 Canada

N103 and N104 are required except when N101 contains code MA or OB.

When the ship to is the end consumer (customer of retailer), N103 and N104 are not required.

In some EDI implementations, it may be necessary to identify the sender and/or receiver of the transaction set within eachtransaction set. To identify the sender of the transaction set, N101 will contain code FR, N103 will contain code 93, and N104will contain the actual identification number. To identify the receiver of the transaction set, N101 will contain code TO, N103will contain code 94, and N104 will contain the actual identification number. These four codes may be used only in thecombination listed above and may be used only to identify the sender and/or receiver of the transaction set.

N103 and N104 are required except when N101 contains code MA or OB.

When the ship to is the end consumer (customer of retailer), N103 and N104 are not required.

In some EDI implementations, it may be necessary to identify the sender and/or receiver of the transaction set within eachtransaction set. To identify the sender of the transaction set, N101 will contain code FR, N103 will contain code 93, and N104will contain the actual identification number. To identify the receiver of the transaction set, N101 will contain code TO, N103will contain code 94, and N104 will contain the actual identification number. These four codes may be used only in thecombination listed above and may be used only to identify the sender and/or receiver of the transaction set.

Page 349: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Ship Notice/Manifest - Foodservice - 856

July 2012 [V004010-2012 FS] 21Copyright 2012 - GS1 Canada

N2 Additional Name Information Pos: 230 Max: 2Detail - Optional

Loop: N1 Elements: 2

User Option (Usage): UsedPurpose: To specify additional names or those longer than 35 characters in length

Element Summary: Ref Id Element Name Req Type Min/Max UsageN201 93 Name

Description: Free-form name

M AN 1/60 Must use

N202 93 Name

Description: Free-form name

O AN 1/60 Used

Page 350: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Ship Notice/Manifest - Foodservice - 856

July 2012 [V004010-2012 FS] 22Copyright 2012 - GS1 Canada

N3 Address Information Pos: 240 Max: 2Detail - Optional

Loop: N1 Elements: 2

User Option (Usage): UsedPurpose: To specify the location of the named party

Element Summary: Ref Id Element Name Req Type Min/Max UsageN301 166 Address Information

Description: Address information

M AN 1/55 Must use

N302 166 Address Information

Description: Address information

O AN 1/55 Used

Page 351: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Ship Notice/Manifest - Foodservice - 856

July 2012 [V004010-2012 FS] 23Copyright 2012 - GS1 Canada

N4 Geographic Location Pos: 250 Max: 1Detail - Optional

Loop: N1 Elements: 6

User Option (Usage): UsedPurpose: To specify the geographic place of the named party

Element Summary: Ref Id Element Name Req Type Min/Max UsageN401 19 City Name

Description: Free-form text for city name

O AN 2/30 Used

N402 156 State or Province Code

Description: Code (StandardState/Province) as defined by appropriategovernment agency

O ID 2/2 Used

N403 116 Postal Code

Description: Code defining internationalpostal zone code excluding punctuationand blanks (zip code for United States)

O ID 3/15 Used

N404 26 Country Code

Description: Code identifying the country

O ID 2/3 Used

N405 309 Location Qualifier

Description: Code identifying type oflocation

C ID 1/2 Used

CodeList Summary (Total Codes: 172, Included: 4)Code NameD Census Schedule DK Census Schedule KW Worldwide Geographic Location CodeIA International Air Transport Association (IATA) Location Qualifier

N406 310 Location Identifier

Description: Code which identifies aspecific location

O AN 1/30 Used

Syntax Rules: 1. C0605 - If N406 is present, then N405 is required.

Comments: 1. A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location.2. N402 is required only if city name (N401) is in the U.S. or Canada.

Page 352: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Ship Notice/Manifest - Foodservice - 856

July 2012 [V004010-2012 FS] 24Copyright 2012 - GS1 Canada

HL Hierarchical Level - Unit or Lot Pos: 010 Max: 1Detail - Mandatory

Loop: HL Elements: 3

User Option (Usage): Must usePurpose: To identify dependencies among and the content of hierarchically related groups of data segments

Element Summary: Ref Id Element Name Req Type Min/Max UsageHL01 628 Hierarchical ID Number

Description: A unique number assignedby the sender to identify a particular datasegment in a hierarchical structure

M AN 1/12 Must use

HL02 734 Hierarchical Parent ID Number

Description: Identification number of thenext higher hierarchical data segment thatthe data segment being described issubordinate to

O AN 1/12 Must use

HL03 735 Hierarchical Level Code

Description: Code defining thecharacteristic of a level in a hierarchicalstructure

M ID 1/2 Must use

CodeList Summary (Total Codes: 170, Included: 1)Code NameUT Unit or Lot

User Note 1:User Note 1:Unit loadUnit load

Comments: 1. The HL segment is used to identify levels of detail information using a hierarchical structure, such as relating

line-item data to shipment data, and packaging data to line-item data.2. The HL segment defines a top-down/left-right ordered structure.3. HL01 shall contain a unique alphanumeric number for each occurrence of the HL segment in the transaction

set. For example, HL01 could be used to indicate the number of occurrences of the HL segment, in whichcase the value of HL01 would be "1" for the initial HL segment and would be incremented by one in eachsubsequent HL segment within the transaction.

4. HL02 identifies the hierarchical ID number of the HL segment to which the current HL segment is subordinate.5. HL03 indicates the context of the series of segments following the current HL segment up to the next

occurrence of an HL segment in the transaction. For example, HL03 is used to indicate that subsequentsegments in the HL loop form a logical grouping of data referring to shipment, order, or item-level information.

6. HL04 indicates whether or not there are subordinate (or child) HL segments related to the current HLsegment.

User Note 1:User Note 1:The HL segment is used to identify levels of detail information using a hierarchical structure.

HL01 shall contain a unique number for each occurrence of the HL segment within the transaction set. The value assigned tothe first HL segment will be 1, and is incremented by one for each subsequent HL segment within the transaction set.

The HL segment is used to identify levels of detail information using a hierarchical structure.

HL01 shall contain a unique number for each occurrence of the HL segment within the transaction set. The value assigned tothe first HL segment will be 1, and is incremented by one for each subsequent HL segment within the transaction set.

Page 353: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Ship Notice/Manifest - Foodservice - 856

July 2012 [V004010-2012 FS] 25Copyright 2012 - GS1 Canada

HL02 identifies the hierarchical ID of the HL segment to which it is subordinate (child of). HL02 will be omitted for the firstoccurrence of the HL segment in the transaction set, since it has no parent. HL03 identifies the application content of theseries of segments following the current HL segment up to the next occurrence of an HL segment, or the CTT or SE segment,e.g., Shipment, Unit Load, Order, Tare, Pack and Item.

HL02 identifies the hierarchical ID of the HL segment to which it is subordinate (child of). HL02 will be omitted for the firstoccurrence of the HL segment in the transaction set, since it has no parent. HL03 identifies the application content of theseries of segments following the current HL segment up to the next occurrence of an HL segment, or the CTT or SE segment,e.g., Shipment, Unit Load, Order, Tare, Pack and Item.

Page 354: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Ship Notice/Manifest - Foodservice - 856

July 2012 [V004010-2012 FS] 26Copyright 2012 - GS1 Canada

TD3 Carrier Details (Equipment) Pos: 130 Max: 12Detail - Optional

Loop: HL Elements: 1

User Option (Usage): UsedPurpose: To specify transportation details relating to the equipment used by the carrier

Element Summary: Ref Id Element Name Req Type Min/Max UsageTD301 40 Equipment Description Code

Description: Code identifying type ofequipment used for shipment

C ID 2/2 Must use

CodeList Summary (Total Codes: 134, Included: 6)Code Name20 20 ft. IL Container (Open Top)2B 20 ft. IL Container (Closed Top)40 40 ft. IL Container (Open Top)4B 40 ft. IL Container (Closed Top)CN ContainerCZ Refrigerated Container

Syntax Rules: 1. E0110 - Only one of TD301 or TD310 may be present.2. C0203 - If TD302 is present, then TD303 is required.3. C0405 - If TD304 is present, then TD305 is required.4. P0506 - If either TD305 or TD306 is present, then the other is required.

Page 355: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Ship Notice/Manifest - Foodservice - 856

July 2012 [V004010-2012 FS] 27Copyright 2012 - GS1 Canada

MAN Marks and Numbers Pos: 190 Max: >1Detail - Optional

Loop: HL Elements: 2

User Option (Usage): UsedPurpose: To indicate identifying marks and numbers for shipping containers

Element Summary: Ref Id Element Name Req Type Min/Max UsageMAN01 88 Marks and Numbers Qualifier

Description: Code specifying theapplication or source of Marks andNumbers (87)

M ID 1/2 Must use

CodeList Summary (Total Codes: 20, Included: 1)Code NameGM SSCC-18 and Application Identifier

User Note 1:User Note 1:This is a twenty-character UCC/EAN-128 Serial Shipping Container Code (SSCC-18) thatincludes the two digit application identifier. The symbology code and the modulo 103check digit are not included.

This is a twenty-character UCC/EAN-128 Serial Shipping Container Code (SSCC-18) thatincludes the two digit application identifier. The symbology code and the modulo 103check digit are not included.

MAN02 87 Marks and Numbers

Description: Marks and numbers used toidentify a shipment or parts of a shipment

M AN 1/48 Must use

Syntax Rules: 1. P0405 - If either MAN04 or MAN05 is present, then the other is required.2. C0605 - If MAN06 is present, then MAN05 is required.

Semantics: 1. MAN01/MAN02 and MAN04/MAN05 may be used to identify two different marks and numbers assigned to the

same physical container.2. When both MAN02 and MAN03 are used, MAN02 is the starting number of a sequential range and MAN03 is

the ending number of that range.3. When both MAN05 and MAN06 are used, MAN05 is the starting number of a sequential range, and MAN06 is

the ending number of that range.

Comments: 1. When MAN01 contains code "UC" (U.P.C. Shipping Container Code) and MAN05/MAN06 contain a range of

ID numbers, MAN03 is not used. The reason for this is that the U.P.C. Shipping Container code is the sameon every carton that is represented in the range in MAN05/MAN06.

2. MAN03 and/or MAN06 are only used when sending a range(s) of ID numbers.3. When both MAN02/MAN03 and MAN05/MAN06 are used to send ranges of ID numbers, the integrity of the

two ID numbers must be maintained.

User Note 1:User Note 1:This segment, at the unit load level, is used to specify the identification number for the unit load.This segment, at the unit load level, is used to specify the identification number for the unit load.

Page 356: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Ship Notice/Manifest - Foodservice - 856

July 2012 [V004010-2012 FS] 28Copyright 2012 - GS1 Canada

HL Hierarchical Level - Order Pos: 010 Max: 1Detail - Mandatory

Loop: HL Elements: 3

User Option (Usage): Must usePurpose: To identify dependencies among and the content of hierarchically related groups of data segments

Element Summary: Ref Id Element Name Req Type Min/Max UsageHL01 628 Hierarchical ID Number

Description: A unique number assignedby the sender to identify a particular datasegment in a hierarchical structure

M AN 1/12 Must use

HL02 734 Hierarchical Parent ID Number

Description: Identification number of thenext higher hierarchical data segment thatthe data segment being described issubordinate to

O AN 1/12 Must use

HL03 735 Hierarchical Level Code

Description: Code defining thecharacteristic of a level in a hierarchicalstructure

M ID 1/2 Must use

CodeList Summary (Total Codes: 170, Included: 1)Code NameO Order

Comments: 1. The HL segment is used to identify levels of detail information using a hierarchical structure, such as relating

line-item data to shipment data, and packaging data to line-item data.2. The HL segment defines a top-down/left-right ordered structure.3. HL01 shall contain a unique alphanumeric number for each occurrence of the HL segment in the transaction

set. For example, HL01 could be used to indicate the number of occurrences of the HL segment, in whichcase the value of HL01 would be "1" for the initial HL segment and would be incremented by one in eachsubsequent HL segment within the transaction.

4. HL02 identifies the hierarchical ID number of the HL segment to which the current HL segment is subordinate.5. HL03 indicates the context of the series of segments following the current HL segment up to the next

occurrence of an HL segment in the transaction. For example, HL03 is used to indicate that subsequentsegments in the HL loop form a logical grouping of data referring to shipment, order, or item-level information.

6. HL04 indicates whether or not there are subordinate (or child) HL segments related to the current HLsegment.

User Note 1:User Note 1:The HL segment is used to identify levels of detail information using a hierarchical structure.

HL01 shall contain a unique number for each occurrence of the HL segment within the transaction set. The value assigned tothe first HL segment will be 1, and is incremented by one for each subsequent HL segment within the transaction set.

HL02 identifies the hierarchical ID of the HL segment to which it is subordinate (child of). HL02 will be omitted for the firstoccurrence of the HL segment in the transaction set, since it has no parent. HL03 identifies the application content of theseries of segments following the current HL segment up to the next occurrence of an HL segment, or the CTT or SE segment,

The HL segment is used to identify levels of detail information using a hierarchical structure.

HL01 shall contain a unique number for each occurrence of the HL segment within the transaction set. The value assigned tothe first HL segment will be 1, and is incremented by one for each subsequent HL segment within the transaction set.

HL02 identifies the hierarchical ID of the HL segment to which it is subordinate (child of). HL02 will be omitted for the firstoccurrence of the HL segment in the transaction set, since it has no parent. HL03 identifies the application content of theseries of segments following the current HL segment up to the next occurrence of an HL segment, or the CTT or SE segment,

Page 357: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Ship Notice/Manifest - Foodservice - 856

July 2012 [V004010-2012 FS] 29Copyright 2012 - GS1 Canada

e.g., Shipment, Unit Load, Order, Tare, Pack and Item.e.g., Shipment, Unit Load, Order, Tare, Pack and Item.

Page 358: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Ship Notice/Manifest - Foodservice - 856

July 2012 [V004010-2012 FS] 30Copyright 2012 - GS1 Canada

PRF Purchase Order Reference Pos: 050 Max: 1Detail - Optional

Loop: HL Elements: 1

User Option (Usage): UsedPurpose: To provide reference to a specific purchase order

Element Summary: Ref Id Element Name Req Type Min/Max UsagePRF01 324 Purchase Order Number

Description: Identifying number forPurchase Order assigned by theorderer/purchaser

M AN 1/22 Must use

Semantics: 1. PRF04 is the date assigned by the purchaser to purchase order.

Page 359: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Ship Notice/Manifest - Foodservice - 856

July 2012 [V004010-2012 FS] 31Copyright 2012 - GS1 Canada

TD1 Carrier Details (Quantity andWeight)

Pos: 110 Max: 20Detail - Optional

Loop: HL Elements: 5

User Option (Usage): UsedPurpose: To specify the transportation details relative to commodity, weight, and quantity

Element Summary: Ref Id Element Name Req Type Min/Max UsageTD101 103 Packaging Code

Description: Code identifying the type ofpackaging; Part 1: Packaging Form, Part2: Packaging Material; if the Data Elementis used, then Part 1 is always required

O AN 3/5 Used

CodeList Summary (Total Codes: 148, Included: 3)Code NameBAG BagCTN CartonPLT Pallet

CodeList Summary (Total Codes: 55, Included: 6)Code Name01 Aluminum25 Corrugated or Solid31 Fibre76 Paper79 Plastic94 Wood

TD102 80 Lading Quantity

Description: Number of units (pieces) ofthe lading commodity

C N0 1/7 Used

TD106 187 Weight Qualifier

Description: Code defining the type ofweight

O ID 1/2 Used

CodeList Summary (Total Codes: 51, Included: 1)Code NameG Gross Weight

TD107 81 Weight

Description: Numeric value of weight

C R 1/10 Used

TD108 355 Unit or Basis for Measurement Code

Description: Code specifying the units inwhich a value is being expressed, ormanner in which a measurement hasbeen taken

C ID 2/2 Used

CodeList Summary (Total Codes: 794, Included: 2)

Page 360: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Ship Notice/Manifest - Foodservice - 856

July 2012 [V004010-2012 FS] 32Copyright 2012 - GS1 Canada

Code NameGR GramKG Kilogram

Syntax Rules: 1. C0102 - If TD101 is present, then TD102 is required.2. C0304 - If TD103 is present, then TD104 is required.3. C0607 - If TD106 is present, then TD107 is required.4. P0708 - If either TD107 or TD108 is present, then the other is required.5. P0910 - If either TD109 or TD110 is present, then the other is required.

User Note 1:User Note 1:This segment, at the order level, is used to specify the number and type of shipping containers in the order.This segment, at the order level, is used to specify the number and type of shipping containers in the order.

Page 361: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Ship Notice/Manifest - Foodservice - 856

July 2012 [V004010-2012 FS] 33Copyright 2012 - GS1 Canada

REF Reference Identification Pos: 150 Max: >1Detail - Optional

Loop: HL Elements: 2

User Option (Usage): UsedPurpose: To specify identifying information

Element Summary: Ref Id Element Name Req Type Min/Max UsageREF01 128 Reference Identification Qualifier

Description: Code qualifying theReference Identification

M ID 2/3 Must use

CodeList Summary (Total Codes: 1503, Included: 15)Code Name6B U.S. Customs Service (USCS) Entry Number

User Note 1:User Note 1:Customs entry numberCustoms entry number

BM Bill of Lading NumberBT Batch NumberCH Customer catalog numberCO Customer Order Number

User Note 1:User Note 1:Customer of retailerCustomer of retailer

DP Department NumberHB Bill & Hold Invoice NumberIA Internal Vendor Number

User Note 1:User Note 1:Identification number assigned to the vendor, by the retailer, for use within the retailer'ssystemIdentification number assigned to the vendor, by the retailer, for use within the retailer'ssystem

IT Internal Customer NumberUser Note 1:User Note 1:

Identification number assigned to the retailer, by the vendor, for use within the vendor'ssystemIdentification number assigned to the retailer, by the vendor, for use within the vendor'ssystem

IV Seller's Invoice NumberMR Merchandise Type CodePD Promotion/Deal NumberQC Product Specification Document Number

Description: Model designation of replacement component

User Note 1:User Note 1:Schematic reference numberSchematic reference number

SB Sales Region NumberVN Vendor Order Number

REF02 127 Reference Identification

Description: Reference information asdefined for a particular Transaction Set oras specified by the Reference

C AN 1/30 Must use

Page 362: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Ship Notice/Manifest - Foodservice - 856

Ref Id Element Name Req Type Min/Max Usage

July 2012 [V004010-2012 FS] 34Copyright 2012 - GS1 Canada

Identification Qualifier

Syntax Rules: 1. R0203 - At least one of REF02 or REF03 is required.

Semantics: 1. REF04 contains data relating to the value cited in REF02.

Page 363: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Ship Notice/Manifest - Foodservice - 856

July 2012 [V004010-2012 FS] 35Copyright 2012 - GS1 Canada

N1 Name Pos: 220 Max: 1Detail - Optional

Loop: N1 Elements: 4

User Option (Usage): UsedPurpose: To identify a party by type of organization, name, and code

Element Summary: Ref Id Element Name Req Type Min/Max UsageN101 98 Entity Identifier Code

Description: Code identifying anorganizational entity, a physical location,property or an individual

M ID 2/3 Must use

CodeList Summary (Total Codes: 1312, Included: 1)Code NameBY Buying Party (Purchaser)

N102 93 Name

Description: Free-form name

C AN 1/60 Used

N103 66 Identification Code Qualifier

Description: Code designating thesystem/method of code structure used forIdentification Code (67)

C ID 1/2 Used

CodeList Summary (Total Codes: 215, Included: 2)Code Name9 D-U-N-S+4, D-U-N-S Number with Four Character SuffixUL UCC/EAN Location Code

Description: Global Location Number (GLN) (Revised name) A globally unique 13 digit code used for the identification of any physical or legal locationthat needs to be uniquely identified for use in the supply chain. A GS1 identification key SEE CODE SOURCE 583

N104 67 Identification Code

Description: Code identifying a party orother codeUser Note 1: This is the location code asdefined by N103. The location code may be aformal number, e.g., DUNS, or it may beassigned by either the buyer or seller. Thelocation refers to a store, warehouse,distribution center, plant, etc. Location codesare used to alleviate the need to sendcomplete names and addresses.

User Note 1: This is the location code asdefined by N103. The location code may be aformal number, e.g., DUNS, or it may beassigned by either the buyer or seller. Thelocation refers to a store, warehouse,distribution center, plant, etc. Location codesare used to alleviate the need to sendcomplete names and addresses.

C AN 2/80 Used

Syntax Rules: 1. R0203 - At least one of N102 or N103 is required.2. P0304 - If either N103 or N104 is present, then the other is required.

Page 364: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Ship Notice/Manifest - Foodservice - 856

July 2012 [V004010-2012 FS] 36Copyright 2012 - GS1 Canada

Comments: 1. This segment, used alone, provides the most efficient method of providing organizational identification. To

obtain this efficiency the "ID Code" (N104) must provide a key to the table maintained by the transactionprocessing party.

2. N105 and N106 further define the type of entity in N101.

User Note 1:User Note 1:There will be at least one occurrence, of this segment, to identify the buying party by using code BY in N101.

N103 and N104 are required except when N101 contains code CT, MA or OB.

There will be at least one occurrence, of this segment, to identify the buying party by using code BY in N101.

N103 and N104 are required except when N101 contains code CT, MA or OB.

Page 365: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Ship Notice/Manifest - Foodservice - 856

July 2012 [V004010-2012 FS] 37Copyright 2012 - GS1 Canada

N2 Additional Name Information Pos: 230 Max: 2Detail - Optional

Loop: N1 Elements: 2

User Option (Usage): UsedPurpose: To specify additional names or those longer than 35 characters in length

Element Summary: Ref Id Element Name Req Type Min/Max UsageN201 93 Name

Description: Free-form name

M AN 1/60 Must use

N202 93 Name

Description: Free-form name

O AN 1/60 Used

Page 366: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Ship Notice/Manifest - Foodservice - 856

July 2012 [V004010-2012 FS] 38Copyright 2012 - GS1 Canada

N3 Address Information Pos: 240 Max: 2Detail - Optional

Loop: N1 Elements: 2

User Option (Usage): UsedPurpose: To specify the location of the named party

Element Summary: Ref Id Element Name Req Type Min/Max UsageN301 166 Address Information

Description: Address information

M AN 1/55 Must use

N302 166 Address Information

Description: Address information

O AN 1/55 Used

Page 367: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Ship Notice/Manifest - Foodservice - 856

July 2012 [V004010-2012 FS] 39Copyright 2012 - GS1 Canada

N4 Geographic Location Pos: 250 Max: 1Detail - Optional

Loop: N1 Elements: 4

User Option (Usage): UsedPurpose: To specify the geographic place of the named party

Element Summary: Ref Id Element Name Req Type Min/Max UsageN401 19 City Name

Description: Free-form text for city name

O AN 2/30 Used

N402 156 State or Province Code

Description: Code (StandardState/Province) as defined by appropriategovernment agency

O ID 2/2 Used

N403 116 Postal Code

Description: Code defining internationalpostal zone code excluding punctuationand blanks (zip code for United States)

O ID 3/15 Used

N404 26 Country Code

Description: Code identifying the country

O ID 2/3 Used

Syntax Rules: 1. C0605 - If N406 is present, then N405 is required.

Comments: 1. A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location.2. N402 is required only if city name (N401) is in the U.S. or Canada.

Page 368: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Ship Notice/Manifest - Foodservice - 856

July 2012 [V004010-2012 FS] 40Copyright 2012 - GS1 Canada

HL Hierarchical Level - ShippingTare

Pos: 010 Max: 1Detail - Mandatory

Loop: HL Elements: 3

User Option (Usage): Must usePurpose: To identify dependencies among and the content of hierarchically related groups of data segments

Element Summary: Ref Id Element Name Req Type Min/Max UsageHL01 628 Hierarchical ID Number

Description: A unique number assignedby the sender to identify a particular datasegment in a hierarchical structure

M AN 1/12 Must use

HL02 734 Hierarchical Parent ID Number

Description: Identification number of thenext higher hierarchical data segment thatthe data segment being described issubordinate to

O AN 1/12 Must use

HL03 735 Hierarchical Level Code

Description: Code defining thecharacteristic of a level in a hierarchicalstructure

M ID 1/2 Must use

CodeList Summary (Total Codes: 170, Included: 1)Code NameT Shipping Tare

Comments: 1. The HL segment is used to identify levels of detail information using a hierarchical structure, such as relating

line-item data to shipment data, and packaging data to line-item data.2. The HL segment defines a top-down/left-right ordered structure.3. HL01 shall contain a unique alphanumeric number for each occurrence of the HL segment in the transaction

set. For example, HL01 could be used to indicate the number of occurrences of the HL segment, in whichcase the value of HL01 would be "1" for the initial HL segment and would be incremented by one in eachsubsequent HL segment within the transaction.

4. HL02 identifies the hierarchical ID number of the HL segment to which the current HL segment is subordinate.5. HL03 indicates the context of the series of segments following the current HL segment up to the next

occurrence of an HL segment in the transaction. For example, HL03 is used to indicate that subsequentsegments in the HL loop form a logical grouping of data referring to shipment, order, or item-level information.

6. HL04 indicates whether or not there are subordinate (or child) HL segments related to the current HLsegment.

User Note 1:User Note 1:The HL segment is used to identify levels of detail information using a hierarchical structure.

HL01 shall contain a unique number for each occurrence of the HL segment within the transaction set. The value assigned tothe first HL segment will be 1, and is incremented by one for each subsequent HL segment within the transaction set.

HL02 identifies the hierarchical ID of the HL segment to which it is subordinate (child of). HL02 will be omitted for the firstoccurrence of the HL segment in the transaction set, since it has no parent. HL03 identifies the application content of theseries of segments following the current HL segment up to the next occurrence of an HL segment, or the CTT or SE segment,

The HL segment is used to identify levels of detail information using a hierarchical structure.

HL01 shall contain a unique number for each occurrence of the HL segment within the transaction set. The value assigned tothe first HL segment will be 1, and is incremented by one for each subsequent HL segment within the transaction set.

HL02 identifies the hierarchical ID of the HL segment to which it is subordinate (child of). HL02 will be omitted for the firstoccurrence of the HL segment in the transaction set, since it has no parent. HL03 identifies the application content of theseries of segments following the current HL segment up to the next occurrence of an HL segment, or the CTT or SE segment,

Page 369: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Ship Notice/Manifest - Foodservice - 856

July 2012 [V004010-2012 FS] 41Copyright 2012 - GS1 Canada

e.g., Shipment, Unit Load, Order, Tare, Pack and Item.e.g., Shipment, Unit Load, Order, Tare, Pack and Item.

Page 370: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Ship Notice/Manifest - Foodservice - 856

July 2012 [V004010-2012 FS] 42Copyright 2012 - GS1 Canada

MAN Marks and Numbers Pos: 190 Max: >1Detail - Optional

Loop: HL Elements: 2

User Option (Usage): UsedPurpose: To indicate identifying marks and numbers for shipping containers

Element Summary: Ref Id Element Name Req Type Min/Max UsageMAN01 88 Marks and Numbers Qualifier

Description: Code specifying theapplication or source of Marks andNumbers (87)

M ID 1/2 Must use

CodeList Summary (Total Codes: 20, Included: 1)Code NameGM SSCC-18 and Application Identifier

User Note 1:User Note 1:EAN.UCC Serial Shipping Container Code (SSCC) and Application Identifier

SEE CODE SOURCE 98

EAN.UCC Serial Shipping Container Code (SSCC) and Application Identifier

SEE CODE SOURCE 98

MAN02 87 Marks and Numbers

Description: Marks and numbers used toidentify a shipment or parts of a shipment

M AN 1/48 Must use

Syntax Rules: 1. P0405 - If either MAN04 or MAN05 is present, then the other is required.2. C0605 - If MAN06 is present, then MAN05 is required.

Semantics: 1. MAN01/MAN02 and MAN04/MAN05 may be used to identify two different marks and numbers assigned to the

same physical container.2. When both MAN02 and MAN03 are used, MAN02 is the starting number of a sequential range and MAN03 is

the ending number of that range.3. When both MAN05 and MAN06 are used, MAN05 is the starting number of a sequential range, and MAN06 is

the ending number of that range.

Comments: 1. When MAN01 contains code "UC" (U.P.C. Shipping Container Code) and MAN05/MAN06 contain a range of

ID numbers, MAN03 is not used. The reason for this is that the U.P.C. Shipping Container code is the sameon every carton that is represented in the range in MAN05/MAN06.

2. MAN03 and/or MAN06 are only used when sending a range(s) of ID numbers.3. When both MAN02/MAN03 and MAN05/MAN06 are used to send ranges of ID numbers, the integrity of the

two ID numbers must be maintained.

User Note 1:User Note 1:This segment, at the tare level, is used to specify the identification numbers for the pallet.;This segment, at the tare level, is used to specify the identification numbers for the pallet.;

Page 371: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Ship Notice/Manifest - Foodservice - 856

July 2012 [V004010-2012 FS] 43Copyright 2012 - GS1 Canada

PAL Pallet Information Pos: 215 Max: 1Detail - Optional

Loop: HL Elements: 5

User Option (Usage): UsedPurpose: To identify the type and physical attributes of the pallet, and, gross weight, gross volume, and height of theload and the pallet

Element Summary: Ref Id Element Name Req Type Min/Max UsagePAL01 883 Pallet Type Code

Description: Code indicating the type ofpallet

O ID 1/2 Used

CodeList Summary (Total Codes: 7, Included: 7)Code Name1 Aluminum2 As Specified by the Department of Transportation (DOT)3 Metal4 Standard5 Steel6 Wood7 Slip sheet

Description: Typically cardboard or plastic sheets used to hold product for storage ortransportation

PAL02 884 Pallet Tiers

Description: The number of layers perpallet

O N0 1/3 Used

PAL03 885 Pallet Blocks

Description: The number of pieces(cartons) per layer on the pallet

O N0 1/3 Used

PAL04 356 Pack

Description: The number of innercontainers, or number of eaches if thereare no inner containers, per outercontainer

O N0 1/6 Used

PAL15 399 Pallet Exchange Code

Description: Code specifying palletexchange instructions

O ID 1/1 Used

CodeList Summary (Total Codes: 5, Included: 5)Code Name1 No Exchange/No Return2 Exchange Pallets3 Return Pallets4 Pallets to be Purchased by Customer5 Third-Party Pallet Exchange

Page 372: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Ship Notice/Manifest - Foodservice - 856

July 2012 [V004010-2012 FS] 44Copyright 2012 - GS1 Canada

Syntax Rules: 1. P0506 - If either PAL05 or PAL06 is present, then the other is required.2. C0710 - If PAL07 is present, then PAL10 is required.3. C0810 - If PAL08 is present, then PAL10 is required.4. C0910 - If PAL09 is present, then PAL10 is required.5. L10070809 - If PAL10 is present, then at least one of PAL07, PAL08 or PAL09 is required.6. P1112 - If either PAL11 or PAL12 is present, then the other is required.7. P1314 - If either PAL13 or PAL14 is present, then the other is required.

Semantics: 1. PAL04 (Pack) is the number of pieces on the pallet.2. PAL05 (Unit Weight) is the weight of the pallet alone, before loading.3. PAL07 and PAL08 (Length and Width) are the dimensions of the pallet before loading.4. PAL09 (Height) is the height of the pallet and load.5. PAL11 and PAL13 (Gross Weight and Gross Volume) are measured after loading and includes the pallet.

Page 373: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Ship Notice/Manifest - Foodservice - 856

July 2012 [V004010-2012 FS] 45Copyright 2012 - GS1 Canada

HL Hierarchical Level - Pack Pos: 010 Max: 1Detail - Mandatory

Loop: HL Elements: 3

User Option (Usage): Must usePurpose: To identify dependencies among and the content of hierarchically related groups of data segments

Element Summary: Ref Id Element Name Req Type Min/Max UsageHL01 628 Hierarchical ID Number

Description: A unique number assignedby the sender to identify a particular datasegment in a hierarchical structure

M AN 1/12 Must use

HL02 734 Hierarchical Parent ID Number

Description: Identification number of thenext higher hierarchical data segment thatthe data segment being described issubordinate to

O AN 1/12 Must use

HL03 735 Hierarchical Level Code

Description: Code defining thecharacteristic of a level in a hierarchicalstructure

M ID 1/2 Must use

CodeList Summary (Total Codes: 170, Included: 1)Code NameP Pack

Comments: 1. The HL segment is used to identify levels of detail information using a hierarchical structure, such as relating

line-item data to shipment data, and packaging data to line-item data.2. The HL segment defines a top-down/left-right ordered structure.3. HL01 shall contain a unique alphanumeric number for each occurrence of the HL segment in the transaction

set. For example, HL01 could be used to indicate the number of occurrences of the HL segment, in whichcase the value of HL01 would be "1" for the initial HL segment and would be incremented by one in eachsubsequent HL segment within the transaction.

4. HL02 identifies the hierarchical ID number of the HL segment to which the current HL segment is subordinate.5. HL03 indicates the context of the series of segments following the current HL segment up to the next

occurrence of an HL segment in the transaction. For example, HL03 is used to indicate that subsequentsegments in the HL loop form a logical grouping of data referring to shipment, order, or item-level information.

6. HL04 indicates whether or not there are subordinate (or child) HL segments related to the current HLsegment.

User Note 1:User Note 1:The HL segment is used to identify levels of detail information using a hierarchical structure.

HL01 shall contain a unique number for each occurrence of the HL segment within the transaction set. The value assigned tothe first HL segment will be 1, and is incremented by one for each subsequent HL segment within the transaction set.

HL02 identifies the hierarchical ID of the HL segment to which it is subordinate (child of). HL02 will be omitted for the firstoccurrence of the HL segment in the transaction set, since it has no parent. HL03 identifies the application content of theseries of segments following the current HL segment up to the next occurrence of an HL segment, or the CTT or SE segment,

The HL segment is used to identify levels of detail information using a hierarchical structure.

HL01 shall contain a unique number for each occurrence of the HL segment within the transaction set. The value assigned tothe first HL segment will be 1, and is incremented by one for each subsequent HL segment within the transaction set.

HL02 identifies the hierarchical ID of the HL segment to which it is subordinate (child of). HL02 will be omitted for the firstoccurrence of the HL segment in the transaction set, since it has no parent. HL03 identifies the application content of theseries of segments following the current HL segment up to the next occurrence of an HL segment, or the CTT or SE segment,

Page 374: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Ship Notice/Manifest - Foodservice - 856

July 2012 [V004010-2012 FS] 46Copyright 2012 - GS1 Canada

e.g., Shipment, Unit Load, Order, Tare, Pack and Item.e.g., Shipment, Unit Load, Order, Tare, Pack and Item.

Page 375: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Ship Notice/Manifest - Foodservice - 856

July 2012 [V004010-2012 FS] 47Copyright 2012 - GS1 Canada

LIN Item Identification Pos: 020 Max: 1Detail - Optional

Loop: HL Elements: 4

User Option (Usage): UsedPurpose: To specify basic item identification data

Element Summary: Ref Id Element Name Req Type Min/Max UsageLIN02 235 Product/Service ID Qualifier

Description: Code identifying thetype/source of the descriptive numberused in Product/Service ID (234)

M ID 2/2 Must use

CodeList Summary (Total Codes: 477, Included: 2)Code NameLT Lot NumberUK U.P.C./EAN Shipping Container Code (1-2-5-5-1)

Description: GTIN-14 A 14-digit GS1 Identification Key composed of an Indicator Digit, GS1 Company Prefix, ItemReference and Check Digit used to identify trade items SEE CODE SOURCE 41

LIN03 234 Product/Service ID

Description: Identifying number for aproduct or service

M AN 1/48 Must use

LIN04 235 Product/Service ID Qualifier

Description: Code identifying thetype/source of the descriptive numberused in Product/Service ID (234)

C ID 2/2 Used

CodeList Summary (Total Codes: 476, Included: 2)Code NameLT Lot NumberUK U.P.C./EAN Shipping Container Code (1-2-5-5-1)

Description: GTIN-14

A 14-digit GS1 Identification Key composed of an Indicator Digit, GS1 Company Prefix, ItemReference and Check Digit used to identify trade items

SEE CODE SOURCE 41

LIN05 234 Product/Service ID

Description: Identifying number for aproduct or service

C AN 1/48 Used

Syntax Rules: 1. P0405 - If either LIN04 or LIN05 is present, then the other is required.2. P0607 - If either LIN06 or LIN07 is present, then the other is required.3. P0809 - If either LIN08 or LIN09 is present, then the other is required.4. P1011 - If either LIN10 or LIN11 is present, then the other is required.

Page 376: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Ship Notice/Manifest - Foodservice - 856

July 2012 [V004010-2012 FS] 48Copyright 2012 - GS1 Canada

5. P1213 - If either LIN12 or LIN13 is present, then the other is required.6. P1415 - If either LIN14 or LIN15 is present, then the other is required.7. P1617 - If either LIN16 or LIN17 is present, then the other is required.8. P1819 - If either LIN18 or LIN19 is present, then the other is required.9. P2021 - If either LIN20 or LIN21 is present, then the other is required.

10. P2223 - If either LIN22 or LIN23 is present, then the other is required.11. P2425 - If either LIN24 or LIN25 is present, then the other is required.12. P2627 - If either LIN26 or LIN27 is present, then the other is required.13. P2829 - If either LIN28 or LIN29 is present, then the other is required.14. P3031 - If either LIN30 or LIN31 is present, then the other is required.

Semantics: 1. LIN01 is the line item identification

Comments: 1. See the Data Dictionary for a complete list of IDs.2. LIN02 through LIN31 provide for fifteen different product/service IDs for each item. For example: Case, Color,

Drawing No., U.P.C. No., ISBN No., Model No., or SKU.

User Note 1:User Note 1:This segment, at the pack level, is used to specify the GTIN-14 Shipping Container Code, and production information. The SN1segment that follows is used to specify the number of cases identified in the LIN segment. The LIN segment, at the item level,is used to indicate the individual consumer units for the case code.

The codes listed for LIN02 apply to every occurrence of Data Element 235 in the LIN segment.

This segment, at the pack level, is used to specify the GTIN-14 Shipping Container Code, and production information. The SN1segment that follows is used to specify the number of cases identified in the LIN segment. The LIN segment, at the item level,is used to indicate the individual consumer units for the case code.

The codes listed for LIN02 apply to every occurrence of Data Element 235 in the LIN segment.

Page 377: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Ship Notice/Manifest - Foodservice - 856

July 2012 [V004010-2012 FS] 49Copyright 2012 - GS1 Canada

SN1 Item Detail (Shipment) Pos: 030 Max: 1Detail - Optional

Loop: HL Elements: 2

User Option (Usage): UsedPurpose: To specify line-item detail relative to shipment

Element Summary: Ref Id Element Name Req Type Min/Max UsageSN102 382 Number of Units Shipped

Description: Numeric value of unitsshipped in manufacturer's shipping unitsfor a line item or transaction set

M R 1/10 Must use

SN103 355 Unit or Basis for Measurement Code

Description: Code specifying the units inwhich a value is being expressed, ormanner in which a measurement hasbeen taken

M ID 2/2 Must use

CodeList Summary (Total Codes: 794, Included: 12)Code NameBG BagBR BarrelCA CaseDR DrumEA EachGA GallonKG KilogramLB PoundLT LiterPA PailPL Pallet/Unit LoadTE Tote

Syntax Rules: 1. P0506 - If either SN105 or SN106 is present, then the other is required.

Semantics: 1. SN101 is the ship notice line-item identification.

Comments: 1. SN103 defines the unit of measurement for both SN102 and SN104.

User Note 1:User Note 1:This segment, at the pack level, is used only to specify the number of cases identified by the GTIN-14 Shipping ContainerCode in the previous LIN segment. The LIN segment in the item level is used to indicate the individual consumer units for thecase code.

This segment, at the pack level, is used only to specify the number of cases identified by the GTIN-14 Shipping ContainerCode in the previous LIN segment. The LIN segment in the item level is used to indicate the individual consumer units for thecase code.

Page 378: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Ship Notice/Manifest - Foodservice - 856

July 2012 [V004010-2012 FS] 50Copyright 2012 - GS1 Canada

MAN Marks and Numbers Pos: 190 Max: >1Detail - Optional

Loop: HL Elements: 4

User Option (Usage): UsedPurpose: To indicate identifying marks and numbers for shipping containers

Element Summary: Ref Id Element Name Req Type Min/Max UsageMAN01 88 Marks and Numbers Qualifier

Description: Code specifying theapplication or source of Marks andNumbers (87)

M ID 1/2 Must use

CodeList Summary (Total Codes: 20, Included: 2)Code NameGM SSCC-18 and Application Identifier

User Note 1:User Note 1:EAN.UCC Serial Shipping Container Code (SSCC) and Application Identifier

SEE CODE SOURCE 98

EAN.UCC Serial Shipping Container Code (SSCC) and Application Identifier

SEE CODE SOURCE 98

UP U.P.C. Consumer Package Code (1-5-5-1)User Note 1:User Note 1:

GTIN-12 A 12-digit GS1 Identification Key composed of a GS1 Company Prefix, Item Reference, andCheck Digit used to identify trade items

GTIN-12 A 12-digit GS1 Identification Key composed of a GS1 Company Prefix, Item Reference, andCheck Digit used to identify trade items

MAN02 87 Marks and Numbers

Description: Marks and numbers used toidentify a shipment or parts of a shipment

M AN 1/48 Must use

MAN04 88 Marks and Numbers Qualifier

Description: Code specifying theapplication or source of Marks andNumbers (87)

C ID 1/2 Used

CodeList Summary (Total Codes: 20, Included: 2)Code NameGM SSCC-18 and Application Identifier

User Note 1:User Note 1:EAN.UCC Serial Shipping Container Code (SSCC) and Application Identifier

SEE CODE SOURCE 98

EAN.UCC Serial Shipping Container Code (SSCC) and Application Identifier

SEE CODE SOURCE 98

UP U.P.C. Consumer Package Code (1-5-5-1)User Note 1:User Note 1:

GTIN-12 A 12-digit GS1 Identification Key composed of a GS1 Company Prefix, Item Reference, andCheck Digit used to identify trade items

GTIN-12 A 12-digit GS1 Identification Key composed of a GS1 Company Prefix, Item Reference, andCheck Digit used to identify trade items

MAN05 87 Marks and Numbers

Description: Marks and numbers used toidentify a shipment or parts of a shipment

C AN 1/48 Used

Page 379: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Ship Notice/Manifest - Foodservice - 856

Ref Id Element Name Req Type Min/Max Usage

July 2012 [V004010-2012 FS] 51Copyright 2012 - GS1 Canada

Syntax Rules: 1. P0405 - If either MAN04 or MAN05 is present, then the other is required.2. C0605 - If MAN06 is present, then MAN05 is required.

Semantics: 1. MAN01/MAN02 and MAN04/MAN05 may be used to identify two different marks and numbers assigned to the

same physical container.2. When both MAN02 and MAN03 are used, MAN02 is the starting number of a sequential range and MAN03 is

the ending number of that range.3. When both MAN05 and MAN06 are used, MAN05 is the starting number of a sequential range, and MAN06 is

the ending number of that range.

Comments: 1. When MAN01 contains code "UC" (U.P.C. Shipping Container Code) and MAN05/MAN06 contain a range of

ID numbers, MAN03 is not used. The reason for this is that the U.P.C. Shipping Container code is the sameon every carton that is represented in the range in MAN05/MAN06.

2. MAN03 and/or MAN06 are only used when sending a range(s) of ID numbers.3. When both MAN02/MAN03 and MAN05/MAN06 are used to send ranges of ID numbers, the integrity of the

two ID numbers must be maintained.

User Note 1:User Note 1:When the shipping container is the same as the consumer unit, the GTIN may be the only unique identification code on thecontainer. In many applications, it is necessary to positively identify what identification code is to be scanned and matchedat point of receipt. Since the GTIN is not a unique serial shipping container code, only one pack level for each item is requiredwhen using the pick and pack structure. The total number of shipping units for this item is the same as the quantity for theitem in the SN1 segment at the item level.

When the shipping container is the same as the consumer unit, the GTIN may be the only unique identification code on thecontainer. In many applications, it is necessary to positively identify what identification code is to be scanned and matchedat point of receipt. Since the GTIN is not a unique serial shipping container code, only one pack level for each item is requiredwhen using the pick and pack structure. The total number of shipping units for this item is the same as the quantity for theitem in the SN1 segment at the item level.

Page 380: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Ship Notice/Manifest - Foodservice - 856

July 2012 [V004010-2012 FS] 52Copyright 2012 - GS1 Canada

HL Hierarchical Level - Item Pos: 010 Max: 1Detail - Mandatory

Loop: HL Elements: 3

User Option (Usage): Must usePurpose: To identify dependencies among and the content of hierarchically related groups of data segments

Element Summary: Ref Id Element Name Req Type Min/Max UsageHL01 628 Hierarchical ID Number

Description: A unique number assignedby the sender to identify a particular datasegment in a hierarchical structure

M AN 1/12 Must use

HL02 734 Hierarchical Parent ID Number

Description: Identification number of thenext higher hierarchical data segment thatthe data segment being described issubordinate to

O AN 1/12 Must use

HL03 735 Hierarchical Level Code

Description: Code defining thecharacteristic of a level in a hierarchicalstructure

M ID 1/2 Must use

CodeList Summary (Total Codes: 170, Included: 1)Code NameI Item

Comments: 1. The HL segment is used to identify levels of detail information using a hierarchical structure, such as relating

line-item data to shipment data, and packaging data to line-item data.2. The HL segment defines a top-down/left-right ordered structure.3. HL01 shall contain a unique alphanumeric number for each occurrence of the HL segment in the transaction

set. For example, HL01 could be used to indicate the number of occurrences of the HL segment, in whichcase the value of HL01 would be "1" for the initial HL segment and would be incremented by one in eachsubsequent HL segment within the transaction.

4. HL02 identifies the hierarchical ID number of the HL segment to which the current HL segment is subordinate.5. HL03 indicates the context of the series of segments following the current HL segment up to the next

occurrence of an HL segment in the transaction. For example, HL03 is used to indicate that subsequentsegments in the HL loop form a logical grouping of data referring to shipment, order, or item-level information.

6. HL04 indicates whether or not there are subordinate (or child) HL segments related to the current HLsegment.

User Note 1:User Note 1:The HL segment is used to identify levels of detail information using a hierarchical structure.

HL01 shall contain a unique number for each occurrence of the HL segment within the transaction set. The value assigned tothe first HL segment will be 1, and is incremented by one for each subsequent HL segment within the transaction set.

HL02 identifies the hierarchical ID of the HL segment to which it is subordinate (child of). HL02 will be omitted for the firstoccurrence of the HL segment in the transaction set, since it has no parent. HL03 identifies the application content of theseries of segments following the current HL segment up to the next occurrence of an HL segment, or the CTT or SE segment,

The HL segment is used to identify levels of detail information using a hierarchical structure.

HL01 shall contain a unique number for each occurrence of the HL segment within the transaction set. The value assigned tothe first HL segment will be 1, and is incremented by one for each subsequent HL segment within the transaction set.

HL02 identifies the hierarchical ID of the HL segment to which it is subordinate (child of). HL02 will be omitted for the firstoccurrence of the HL segment in the transaction set, since it has no parent. HL03 identifies the application content of theseries of segments following the current HL segment up to the next occurrence of an HL segment, or the CTT or SE segment,

Page 381: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Ship Notice/Manifest - Foodservice - 856

July 2012 [V004010-2012 FS] 53Copyright 2012 - GS1 Canada

e.g., Shipment, Unit Load, Order, Tare, Pack and Item.e.g., Shipment, Unit Load, Order, Tare, Pack and Item.

Page 382: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Ship Notice/Manifest - Foodservice - 856

July 2012 [V004010-2012 FS] 54Copyright 2012 - GS1 Canada

LIN Item Identification Pos: 020 Max: 1Detail - Optional

Loop: HL Elements: 2

User Option (Usage): UsedPurpose: To specify basic item identification data

Element Summary: Ref Id Element Name Req Type Min/Max UsageLIN02 235 Product/Service ID Qualifier

Description: Code identifying thetype/source of the descriptive numberused in Product/Service ID (234)

M ID 2/2 Must use

CodeList Summary (Total Codes: 477, Included: 1)Code NameUK U.P.C./EAN Shipping Container Code (1-2-5-5-1)

Description: GTIN-14

A 14-digit GS1 Identification Key composed of an Indicator Digit, GS1 Company Prefix, ItemReference and Check Digit used to identify trade items

SEE CODE SOURCE 41

LIN03 234 Product/Service ID

Description: Identifying number for aproduct or service

M AN 1/48 Must use

Syntax Rules: 1. P0405 - If either LIN04 or LIN05 is present, then the other is required.2. P0607 - If either LIN06 or LIN07 is present, then the other is required.3. P0809 - If either LIN08 or LIN09 is present, then the other is required.4. P1011 - If either LIN10 or LIN11 is present, then the other is required.5. P1213 - If either LIN12 or LIN13 is present, then the other is required.6. P1415 - If either LIN14 or LIN15 is present, then the other is required.7. P1617 - If either LIN16 or LIN17 is present, then the other is required.8. P1819 - If either LIN18 or LIN19 is present, then the other is required.9. P2021 - If either LIN20 or LIN21 is present, then the other is required.

10. P2223 - If either LIN22 or LIN23 is present, then the other is required.11. P2425 - If either LIN24 or LIN25 is present, then the other is required.12. P2627 - If either LIN26 or LIN27 is present, then the other is required.13. P2829 - If either LIN28 or LIN29 is present, then the other is required.14. P3031 - If either LIN30 or LIN31 is present, then the other is required.

Semantics: 1. LIN01 is the line item identification

Comments: 1. See the Data Dictionary for a complete list of IDs.2. LIN02 through LIN31 provide for fifteen different product/service IDs for each item. For example: Case, Color,

Page 383: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Ship Notice/Manifest - Foodservice - 856

July 2012 [V004010-2012 FS] 55Copyright 2012 - GS1 Canada

Drawing No., U.P.C. No., ISBN No., Model No., or SKU.

User Note 1:User Note 1:The codes listed for LIN02 apply to every occurrence of Data Element 235 in the LIN segment.The codes listed for LIN02 apply to every occurrence of Data Element 235 in the LIN segment.

Page 384: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Ship Notice/Manifest - Foodservice - 856

July 2012 [V004010-2012 FS] 56Copyright 2012 - GS1 Canada

SN1 Item Detail (Shipment) Pos: 030 Max: 1Detail - Optional

Loop: HL Elements: 2

User Option (Usage): UsedPurpose: To specify line-item detail relative to shipment

Element Summary: Ref Id Element Name Req Type Min/Max UsageSN102 382 Number of Units Shipped

Description: Numeric value of unitsshipped in manufacturer's shipping unitsfor a line item or transaction set

M R 1/10 Must use

SN103 355 Unit or Basis for Measurement Code

Description: Code specifying the units inwhich a value is being expressed, ormanner in which a measurement hasbeen taken

M ID 2/2 Must use

CodeList Summary (Total Codes: 794, Included: 12)Code NameBG BagBR BarrelCA CaseDR DrumEA EachGA GallonKG KilogramLB PoundLT LiterPA PailPL Pallet/Unit LoadTE Tote

Syntax Rules: 1. P0506 - If either SN105 or SN106 is present, then the other is required.

Semantics: 1. SN101 is the ship notice line-item identification.

Comments: 1. SN103 defines the unit of measurement for both SN102 and SN104.

User Note 1:User Note 1:This segment is used to specify the quantities associated with the item identified in the LIN at the item level.

When specifying an item, which is comprised of two or more components that are in unique shipping containers, SN103 willcontain code ST for set and the quantity specified in SN102 is the number of sets as identified in the LIN segment. Eachdifferent component is identified in one pack level. See the VICS Note, on the SLN segment, at the pack level.

This segment is used to specify the quantities associated with the item identified in the LIN at the item level.

When specifying an item, which is comprised of two or more components that are in unique shipping containers, SN103 willcontain code ST for set and the quantity specified in SN102 is the number of sets as identified in the LIN segment. Eachdifferent component is identified in one pack level. See the VICS Note, on the SLN segment, at the pack level.

Page 385: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Ship Notice/Manifest - Foodservice - 856

July 2012 [V004010-2012 FS] 57Copyright 2012 - GS1 Canada

PO4 Item Physical Details Pos: 060 Max: 1Detail - Optional

Loop: HL Elements: 2

User Option (Usage): UsedPurpose: To specify the physical qualities, packaging, weights, and dimensions relating to the item

Element Summary: Ref Id Element Name Req Type Min/Max UsagePO401 356 Pack

Description: The number of innercontainers, or number of eaches if thereare no inner containers, per outercontainer

O N0 1/6 Used

PO414 810 Inner Pack

Description: The number of eaches perinner container

O N0 1/6 Used

Syntax Rules: 1. P0203 - If either PO402 or PO403 is present, then the other is required.2. C0506 - If PO405 is present, then PO406 is required.3. P0607 - If either PO406 or PO407 is present, then the other is required.4. P0809 - If either PO408 or PO409 is present, then the other is required.5. C1013 - If PO410 is present, then PO413 is required.6. C1113 - If PO411 is present, then PO413 is required.7. C1213 - If PO412 is present, then PO413 is required.8. L13101112 - If PO413 is present, then at least one of PO410, PO411 or PO412 is required.9. C1716 - If PO417 is present, then PO416 is required.

10. C1804 - If PO418 is present, then PO404 is required.

Semantics: 1. PO415 is used to indicate the relative layer of this package or range of packages within the layers of

packaging. Relative Position 1 (value R1) is the innermost package.2. PO416 is the package identifier or the beginning package identifier in a range of identifiers.3. PO417 is the ending package identifier in a range of identifiers.4. PO418 is the number of packages in this layer.

Comments: 1. PO403 - The "Unit or Basis for Measure Code" in this segment position is for purposes of defining the pack

(PO401) /size (PO402) measure which indicates the quantity in the inner pack unit. For example: If the cartoncontains 24 12-Ounce packages, it would be described as follows: Data element 356 = "24"; Data element357 = "12"; Data element 355 = "OZ".

2. PO413 defines the unit of measure for PO410, PO411, and PO412.

User Note 1:User Note 1:This segment is used to specify the packaging of the item in the case or carton. There may be two levels of packagingspecified. The first level is always specified by using PO401 (Pack). The first level may be actual items, e.g., consumer units,or it may be the number of smaller containers within the case. The second level, specified using PO414 (Inner Pack), is thenumber of eaches in each inner container when PO401 is the number of smaller containers within the case.

This segment is used to specify the packaging of the item in the case or carton. There may be two levels of packagingspecified. The first level is always specified by using PO401 (Pack). The first level may be actual items, e.g., consumer units,or it may be the number of smaller containers within the case. The second level, specified using PO414 (Inner Pack), is thenumber of eaches in each inner container when PO401 is the number of smaller containers within the case.

Page 386: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Ship Notice/Manifest - Foodservice - 856

July 2012 [V004010-2012 FS] 58Copyright 2012 - GS1 Canada

This segment can be used also to specify the weight and/or volume (cube) for the item by using PO406 and PO407, and/orPO408 and PO409.This segment can be used also to specify the weight and/or volume (cube) for the item by using PO406 and PO407, and/orPO408 and PO409.

Page 387: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Ship Notice/Manifest - Foodservice - 856

July 2012 [V004010-2012 FS] 59Copyright 2012 - GS1 Canada

PID Product/Item Description Pos: 070 Max: 200Detail - Optional

Loop: HL Elements: 3

User Option (Usage): UsedPurpose: To describe a product or process in coded or free-form format

Element Summary: Ref Id Element Name Req Type Min/Max UsagePID01 349 Item Description Type

Description: Code indicating the formatof a description

M ID 1/1 Must use

CodeList Summary (Total Codes: 3, Included: 1)Code NameF Free-form

User Note 1:User Note 1:The description will be found in PID05.The description will be found in PID05.

PID02 750 Product/Process Characteristic Code

Description: Code identifying the generalclass of a product or processcharacteristic

O ID 2/3 Used

CodeList Summary (Total Codes: 217, Included: 1)Code Name08 Product

PID05 352 Description

Description: A free-form description toclarify the related data elements and theircontent

C AN 1/80 Used

Syntax Rules: 1. C0403 - If PID04 is present, then PID03 is required.2. R0405 - At least one of PID04 or PID05 is required.3. C0703 - If PID07 is present, then PID03 is required.4. C0804 - If PID08 is present, then PID04 is required.5. C0905 - If PID09 is present, then PID05 is required.

Semantics: 1. Use PID03 to indicate the organization that publishes the code list being referred to.2. PID04 should be used for industry-specific product description codes.3. PID08 describes the physical characteristics of the product identified in PID04. A "Y" indicates that the

specified attribute applies to this item; an "N" indicates it does not apply. Any other value is indeterminate.4. PID09 is used to identify the language being used in PID05.

Comments: 1. If PID01 equals "F", then PID05 is used. If PID01 equals "S", then PID04 is used. If PID01 equals "X", then

both PID04 and PID05 are used.

Page 388: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Ship Notice/Manifest - Foodservice - 856

July 2012 [V004010-2012 FS] 60Copyright 2012 - GS1 Canada

2. Use PID06 when necessary to refer to the product surface or layer being described in the segment.3. PID07 specifies the individual code list of the agency specified in PID03.

Page 389: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Ship Notice/Manifest - Foodservice - 856

July 2012 [V004010-2012 FS] 61Copyright 2012 - GS1 Canada

REF Reference Identification Pos: 150 Max: >1Detail - Optional

Loop: HL Elements: 2

User Option (Usage): UsedPurpose: To specify identifying information

Element Summary: Ref Id Element Name Req Type Min/Max UsageREF01 128 Reference Identification Qualifier

Description: Code qualifying theReference Identification

M ID 2/3 Must use

CodeList Summary (Total Codes: 1503, Included: 3)Code NameCO Customer Order Number

User Note 1:User Note 1:Final Customer Order NumberFinal Customer Order Number

LT Lot NumberSE Serial Number

REF02 127 Reference Identification

Description: Reference information asdefined for a particular Transaction Set oras specified by the ReferenceIdentification Qualifier

C AN 1/30 Must use

Syntax Rules: 1. R0203 - At least one of REF02 or REF03 is required.

Semantics: 1. REF04 contains data relating to the value cited in REF02.

Page 390: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Ship Notice/Manifest - Foodservice - 856

July 2012 [V004010-2012 FS] 62Copyright 2012 - GS1 Canada

DTM Date/Time Reference Pos: 200 Max: 10Detail - Optional

Loop: HL Elements: 2

User Option (Usage): UsedPurpose: To specify pertinent dates and times

Element Summary: Ref Id Element Name Req Type Min/Max UsageDTM01 374 Date/Time Qualifier

Description: Code specifying type of dateor time, or both date and time

M ID 3/3 Must use

CodeList Summary (Total Codes: 1112, Included: 1)Code Name036 Expiration

Description: Date coverage expires

DTM02 373 Date

Description: Date expressed asCCYYMMDD

C DT 8/8 Must use

Syntax Rules: 1. R020305 - At least one of DTM02, DTM03 or DTM05 is required.2. C0403 - If DTM04 is present, then DTM03 is required.3. P0506 - If either DTM05 or DTM06 is present, then the other is required.

Page 391: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Ship Notice/Manifest - Foodservice - 856

July 2012 [V004010-2012 FS] 63Copyright 2012 - GS1 Canada

CTT Transaction Totals Pos: 010 Max: 1Summary - Optional

Loop: N/A Elements: 1

User Option (Usage): UsedPurpose: To transmit a hash total for a specific element in the transaction set

Element Summary: Ref Id Element Name Req Type Min/Max UsageCTT01 354 Number of Line Items

Description: Total number of line items inthe transaction setUser Note 1: The number of HL segmentspresent in the transaction setUser Note 1: The number of HL segmentspresent in the transaction set

M N0 1/6 Must use

Syntax Rules: 1. P0304 - If either CTT03 or CTT04 is present, then the other is required.2. P0506 - If either CTT05 or CTT06 is present, then the other is required.

Comments: 1. This segment is intended to provide hash totals to validate transaction completeness and correctness.

Page 392: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Ship Notice/Manifest - Foodservice - 856

July 2012 [V004010-2012 FS] 64Copyright 2012 - GS1 Canada

SE Transaction Set Trailer Pos: 020 Max: 1Summary - Mandatory

Loop: N/A Elements: 2

User Option (Usage): Must usePurpose: To indicate the end of the transaction set and provide the count of the transmitted segments (including thebeginning (ST) and ending (SE) segments)

Element Summary: Ref Id Element Name Req Type Min/Max UsageSE01 96 Number of Included Segments

Description: Total number of segmentsincluded in a transaction set including STand SE segments

M N0 1/10 Must use

SE02 329 Transaction Set Control Number

Description: Identifying control numberthat must be unique within the transactionset functional group assigned by theoriginator for a transaction setUser Note 1: This must be the same numberas is in the ST segment (ST02) for thetransaction set.

User Note 1: This must be the same numberas is in the ST segment (ST02) for thetransaction set.

M AN 4/9 Must use

Comments: 1. SE is the last segment of each transaction set.

Page 393: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

860 Purchase OrderChange Request - Buyer

Initiated FSFoodservice EDI

Version: 4010-2012 FS Final

Author: GS1 Canada -Foodservice TechnicalStandards Work Group

Publication: 7/1/2012 Notes: For Implementation

December 2012

Page 394: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Purchase Order Change Request - BuyerInitiated Foodservice - 860

July 2012 [V004010-2012 FS] iCopyright 2012 - GS1 Canada

Table of Contents

860 Purchase Order Change Request - Buyer Initiated Foodservice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>ST Transaction Set Header . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>BCH Beginning Segment for Purchase Order Change . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>CUR Currency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>REF Reference Identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>PER Administrative Communications Contact . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>FOB F.O.B. Related Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>SAC Service, Promotion, Allowance, or Charge Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>ITD Terms of Sale/Deferred Terms of Sale . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>DTM Date/Time Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>TD5 Carrier Details (Routing Sequence/Transit Time) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>TD3 Carrier Details (Equipment) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>N9 Reference Identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>MSG Message Text . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>N1 Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>N2 Additional Name Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>N3 Address Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>N4 Geographic Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>REF Reference Identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>POC Line Item Change . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>CTP Pricing Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>PID Product/Item Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>PO4 Item Physical Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>SAC Service, Promotion, Allowance, or Charge Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>CTT Transaction Totals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>SE Transaction Set Trailer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>

. . . . . 1. . . . . 3. . . . . 4. . . . . 6. . . . . 8. . . . . 9. . . . 11. . . . 12. . . . 17. . . . 19. . . . 20. . . . 22. . . . 23. . . . 24. . . . 25. . . . 27. . . . 28. . . . 29. . . . 30. . . . 31. . . . 35. . . . 36. . . . 38. . . . 40. . . . 45. . . . 46

Page 395: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Purchase Order Change Request - BuyerInitiated Foodservice - 860

July 2012 [V004010-2012 FS] 1Copyright 2012 - GS1 Canada

860 Purchase Order Change Request - BuyerInitiated FoodserviceFunctional Group=PC

Purpose: This Draft Standard for Trial Use contains the format and establishes the data contents of the PurchaseOrder Change Request - Buyer Initiated Transaction Set (860) for use within the context of an Electronic DataInterchange (EDI) environment. The transaction set can be used to provide the information required for thecustomary and established business and industry practice relative to a purchase order change. This transaction canbe used: (1) by a buyer to request a change to a previously submitted purchase order or (2) by a buyer to confirmacceptance of a purchase order change initiated by the seller or by mutual agreement of the two parties.

Heading:Pos Id Segment Name Req Max Use Repeat Notes Usage010 ST Transaction Set Header M 1 Must use020 BCH Beginning Segment for

Purchase Order ChangeM 1 Must use

040 CUR Currency O 1 Used050 REF Reference Identification O >1 Used060 PER Administrative

Communications ContactO 3 Used

080 FOB F.O.B. Related Instructions O >1 Used LOOP ID - SAC 25 LOOP ID - SAC 25

120 SAC Service, Promotion,Allowance, or ChargeInformation

O 1 Used

130 ITD Terms of Sale/DeferredTerms of Sale

O 5 Used

150 DTM Date/Time Reference O 10 Used240 TD5 Carrier Details (Routing

Sequence/Transit Time)O 12 Used

250 TD3 Carrier Details (Equipment) O 12 Used LOOP ID - N9 1000 LOOP ID - N9 1000

285 N9 Reference Identification O 1 Used290 MSG Message Text O 1000 Used

LOOP ID - N1 200 LOOP ID - N1 200

300 N1 Name O 1 Used310 N2 Additional Name

InformationO 2 Used

320 N3 Address Information O 2 Used330 N4 Geographic Location O >1 Used340 REF Reference Identification O 12 Used

Detail:Pos Id Segment Name Req Max Use Repeat Notes Usage

LOOP ID - POC >1 LOOP ID - POC >1

010 POC Line Item Change O 1 Used040 CTP Pricing Information O >1 Used

Page 396: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Purchase Order Change Request - BuyerInitiated Foodservice - 860

Pos Id Segment Name Req Max Use Repeat Notes Usage

July 2012 [V004010-2012 FS] 2Copyright 2012 - GS1 Canada

LOOP ID - PID 1000 LOOP ID - PID 1000

050 PID Product/Item Description O 1 Used090 PO4 Item Physical Details O >1 Used

LOOP ID - SAC 25 LOOP ID - SAC 25

130 SAC Service, Promotion,Allowance, or ChargeInformation

O 1 Used

Summary:Pos Id Segment Name Req Max Use Repeat Notes Usage

LOOP ID - CTT 1 N3/010L LOOP ID - CTT 1 N3/010L

010 CTT Transaction Totals O 1 N3/010 Used030 SE Transaction Set Trailer M 1 Must use

Notes: 3/010L Number of line items (CTT01) is the accumulation of the number of POC segments. If used, hash total

(CTT02) is the sum of the value of quantities ordered (POC03) for each POC segment.3/010 Number of line items (CTT01) is the accumulation of the number of POC segments. If used, hash total

(CTT02) is the sum of the value of quantities ordered (POC03) for each POC segment.

Page 397: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Purchase Order Change Request - BuyerInitiated Foodservice - 860

July 2012 [V004010-2012 FS] 3Copyright 2012 - GS1 Canada

ST Transaction Set Header Pos: 010 Max: 1Heading - Mandatory

Loop: N/A Elements: 2

User Option (Usage): Must usePurpose: To indicate the start of a transaction set and to assign a control number

Element Summary: Ref Id Element Name Req Type Min/Max UsageST01 143 Transaction Set Identifier Code

Description: Code uniquely identifying aTransaction Set

M ID 3/3 Must use

CodeList Summary (Total Codes: 298, Included: 1)Code Name860 Purchase Order Change Request - Buyer Initiated

ST02 329 Transaction Set Control Number

Description: Identifying control numberthat must be unique within the transactionset functional group assigned by theoriginator for a transaction setUser Note 1: The number is sequentiallyassigned by the sender, starting with onewithin each functional group. For eachfunctional group, the first transaction setcontrol number will be 0001 and incrementedby one for each additional transaction setwithin the group.

User Note 1: The number is sequentiallyassigned by the sender, starting with onewithin each functional group. For eachfunctional group, the first transaction setcontrol number will be 0001 and incrementedby one for each additional transaction setwithin the group.

M AN 4/9 Must use

Semantics: 1. The transaction set identifier (ST01) used by the translation routines of the interchange partners to select the

appropriate transaction set definition (e.g., 810 selects the Invoice Transaction Set).

Page 398: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Purchase Order Change Request - BuyerInitiated Foodservice - 860

July 2012 [V004010-2012 FS] 4Copyright 2012 - GS1 Canada

BCH Beginning Segment forPurchase Order Change

Pos: 020 Max: 1Heading - Mandatory

Loop: N/A Elements: 8

User Option (Usage): Must usePurpose: To indicate the beginning of the Purchase Order Change Transaction Set and transmit identifyingnumbers and dates

Element Summary: Ref Id Element Name Req Type Min/Max UsageBCH01 353 Transaction Set Purpose Code

Description: Code identifying purpose oftransaction set

M ID 2/2 Must use

CodeList Summary (Total Codes: 65, Included: 2)Code Name01 Cancellation04 Change

BCH02 92 Purchase Order Type Code

Description: Code specifying the type ofPurchase Order

M ID 2/2 Must use

CodeList Summary (Total Codes: 69, Included: 4)Code NameBK Blanket Order (Quantity Firm)RE ReorderRL Release or Delivery Order

Description: An order for goods and services placed against a pre-existing contract orblanket order

SA Stand-alone Order

BCH03 324 Purchase Order Number

Description: Identifying number forPurchase Order assigned by theorderer/purchaserUser Note 1: Retailer's original purchaseorder numberUser Note 1: Retailer's original purchaseorder number

M AN 1/22 Must use

BCH04 328 Release Number

Description: Number identifying arelease against a Purchase Orderpreviously placed by the parties involvedin the transactionUser Note 1: Retailer's release against thepurchase order, if usedUser Note 1: Retailer's release against thepurchase order, if used

O AN 1/30 Used

BCH06 373 Date

Description: Date expressed asCCYYMMDDUser Note 1: Retailer's original purchaseUser Note 1: Retailer's original purchase

M DT 8/8 Must use

Page 399: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Purchase Order Change Request - BuyerInitiated Foodservice - 860

Ref Id Element Name Req Type Min/Max Usage

July 2012 [V004010-2012 FS] 5Copyright 2012 - GS1 Canada

order dateorder date

BCH07 326 Request Reference Number

Description: Reference number or RFQnumber to use to identify a particulartransaction set and query (additionalreference number or description whichcan be used with contract number)

O AN 1/45 Used

BCH08 367 Contract Number

Description: Contract number

O AN 1/30 Used

BCH11 373 Date

Description: Date expressed asCCYYMMDDUser Note 1: Retailer's original purchaseorder change date. The date the change wascreated in the application system. This dataelement is required by the retail industry.

User Note 1: Retailer's original purchaseorder change date. The date the change wascreated in the application system. This dataelement is required by the retail industry.

O DT 8/8 Must use

Semantics: 1. BCH06 is the date assigned by the purchaser to purchase order.2. BCH09 is the seller's order number.3. BCH10 is the date assigned by the sender to the acknowledgment.4. BCH11 is the date of the purchase order change request.

Page 400: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Purchase Order Change Request - BuyerInitiated Foodservice - 860

July 2012 [V004010-2012 FS] 6Copyright 2012 - GS1 Canada

CUR Currency Pos: 040 Max: 1Heading - Optional

Loop: N/A Elements: 5

User Option (Usage): UsedPurpose: To specify the currency (dollars, pounds, francs, etc.) used in a transaction

Element Summary: Ref Id Element Name Req Type Min/Max UsageCUR01 98 Entity Identifier Code

Description: Code identifying anorganizational entity, a physical location,property or an individual

M ID 2/3 Must use

CodeList Summary (Total Codes: 1312, Included: 1)Code NameBY Buying Party (Purchaser)

CUR02 100 Currency Code

Description: Code (Standard ISO) forcountry in whose currency the chargesare specified

M ID 3/3 Must use

CUR03 280 Exchange Rate

Description: Value to be used as amultiplier conversion factor to convertmonetary value from one currency toanother

O R 4/10 Used

CUR04 98 Entity Identifier Code

Description: Code identifying anorganizational entity, a physical location,property or an individual

O ID 2/3 Used

CodeList Summary (Total Codes: 1312, Included: 1)Code NameSE Selling Party

CUR05 100 Currency Code

Description: Code (Standard ISO) forcountry in whose currency the chargesare specified

O ID 3/3 Used

Syntax Rules: 1. C0807 - If CUR08 is present, then CUR07 is required.2. C0907 - If CUR09 is present, then CUR07 is required.3. L101112 - If CUR10 is present, then at least one of CUR11 or CUR12 is required.4. C1110 - If CUR11 is present, then CUR10 is required.5. C1210 - If CUR12 is present, then CUR10 is required.6. L131415 - If CUR13 is present, then at least one of CUR14 or CUR15 is required.7. C1413 - If CUR14 is present, then CUR13 is required.8. C1513 - If CUR15 is present, then CUR13 is required.

Page 401: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Purchase Order Change Request - BuyerInitiated Foodservice - 860

July 2012 [V004010-2012 FS] 7Copyright 2012 - GS1 Canada

9. L161718 - If CUR16 is present, then at least one of CUR17 or CUR18 is required.10. C1716 - If CUR17 is present, then CUR16 is required.11. C1816 - If CUR18 is present, then CUR16 is required.12. L192021 - If CUR19 is present, then at least one of CUR20 or CUR21 is required.13. C2019 - If CUR20 is present, then CUR19 is required.14. C2119 - If CUR21 is present, then CUR19 is required.

Comments: 1. See Figures Appendix for examples detailing the use of the CUR segment.

User Note 1:User Note 1:See Section V (CUR Usage) for usage examples.See Section V (CUR Usage) for usage examples.

Page 402: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Purchase Order Change Request - BuyerInitiated Foodservice - 860

July 2012 [V004010-2012 FS] 8Copyright 2012 - GS1 Canada

REF Reference Identification Pos: 050 Max: >1Heading - Optional

Loop: N/A Elements: 2

User Option (Usage): UsedPurpose: To specify identifying information

Element Summary: Ref Id Element Name Req Type Min/Max UsageREF01 128 Reference Identification Qualifier

Description: Code qualifying theReference Identification

M ID 2/3 Must use

CodeList Summary (Total Codes: 1503, Included: 4)Code NameDP Department Number

User Note 1:User Note 1:This code may be used in the header area or the detail area, but not both.This code may be used in the header area or the detail area, but not both.

IA Internal Vendor NumberUser Note 1:User Note 1:

Identification number assigned to the Selling Organization, by the Purchasing Organizationfor use within the Purchasing Organization's systemIdentification number assigned to the Selling Organization, by the Purchasing Organizationfor use within the Purchasing Organization's system

IT Internal Customer NumberUser Note 1:User Note 1:

Identification number assigned to the Purchasing Organization, by the SellingOrganization, for use within the Selling Organization's systemIdentification number assigned to the Purchasing Organization, by the SellingOrganization, for use within the Selling Organization's system

PD Promotion/Deal Number

REF02 127 Reference Identification

Description: Reference information asdefined for a particular Transaction Set oras specified by the ReferenceIdentification Qualifier

C AN 1/30 Must use

Syntax Rules: 1. R0203 - At least one of REF02 or REF03 is required.

Semantics: 1. REF04 contains data relating to the value cited in REF02.

Page 403: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Purchase Order Change Request - BuyerInitiated Foodservice - 860

July 2012 [V004010-2012 FS] 9Copyright 2012 - GS1 Canada

PER AdministrativeCommunications Contact

Pos: 060 Max: 3Heading - Optional

Loop: N/A Elements: 6

User Option (Usage): UsedPurpose: To identify a person or office to whom administrative communications should be directed

Element Summary: Ref Id Element Name Req Type Min/Max UsagePER01 366 Contact Function Code

Description: Code identifying the majorduty or responsibility of the person orgroup named

M ID 2/2 Must use

CodeList Summary (Total Codes: 230, Included: 2)Code NameBD Buyer Name or DepartmentIC Information Contact

PER02 93 Name

Description: Free-form name

O AN 1/60 Used

PER03 365 Communication Number Qualifier

Description: Code identifying the type ofcommunication number

C ID 2/2 Used

CodeList Summary (Total Codes: 40, Included: 2)Code NameEM Electronic MailTE Telephone

PER04 364 Communication Number

Description: Complete communicationsnumber including country or area codewhen applicable

C AN 1/80 Used

PER05 365 Communication Number Qualifier

Description: Code identifying the type ofcommunication number

C ID 2/2 Used

CodeList Summary (Total Codes: 40, Included: 2)Code NameEM Electronic MailTE Telephone

PER06 364 Communication Number

Description: Complete communicationsnumber including country or area codewhen applicable

C AN 1/80 Used

Syntax Rules:

Page 404: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Purchase Order Change Request - BuyerInitiated Foodservice - 860

July 2012 [V004010-2012 FS] 10Copyright 2012 - GS1 Canada

1. P0304 - If either PER03 or PER04 is present, then the other is required.2. P0506 - If either PER05 or PER06 is present, then the other is required.3. P0708 - If either PER07 or PER08 is present, then the other is required.

Page 405: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Purchase Order Change Request - BuyerInitiated Foodservice - 860

July 2012 [V004010-2012 FS] 11Copyright 2012 - GS1 Canada

FOB F.O.B. Related Instructions Pos: 080 Max: >1Heading - Optional

Loop: N/A Elements: 3

User Option (Usage): UsedPurpose: To specify transportation instructions relating to shipment

Element Summary: Ref Id Element Name Req Type Min/Max UsageFOB01 146 Shipment Method of Payment

Description: Code identifying paymentterms for transportation charges

M ID 2/2 Must use

CodeList Summary (Total Codes: 28, Included: 3)Code NameCC CollectPB Customer Pick-up/BackhaulPP Prepaid (by Seller)

FOB02 309 Location Qualifier

Description: Code identifying type oflocation

C ID 1/2 Used

CodeList Summary (Total Codes: 172, Included: 2)Code NameDE Destination (Shipping)OR Origin (Shipping Point)

FOB03 352 Description

Description: A free-form description toclarify the related data elements and theircontentUser Note 1: Free-form name oftransportation responsibility locationUser Note 1: Free-form name oftransportation responsibility location

O AN 1/80 Used

Syntax Rules: 1. C0302 - If FOB03 is present, then FOB02 is required.2. C0405 - If FOB04 is present, then FOB05 is required.3. C0706 - If FOB07 is present, then FOB06 is required.4. C0809 - If FOB08 is present, then FOB09 is required.

Semantics: 1. FOB01 indicates which party will pay the carrier.2. FOB02 is the code specifying transportation responsibility location.3. FOB06 is the code specifying the title passage location.4. FOB08 is the code specifying the point at which the risk of loss transfers. This may be different than the

location specified in FOB02/FOB03 and FOB06/FOB07.

Page 406: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Purchase Order Change Request - BuyerInitiated Foodservice - 860

July 2012 [V004010-2012 FS] 12Copyright 2012 - GS1 Canada

SAC Service, Promotion,Allowance, or ChargeInformation

Pos: 120 Max: 1Heading - Optional

Loop: SAC Elements: 16

User Option (Usage): UsedPurpose: To request or identify a service, promotion, allowance, or charge; to specify the amount or percentage forthe service, promotion, allowance, or charge

Element Summary: Ref Id Element Name Req Type Min/Max UsageSAC01 248 Allowance or Charge Indicator

Description: Code which indicates anallowance or charge for the servicespecified

M ID 1/1 Must use

CodeList Summary (Total Codes: 7, Included: 4)Code NameA AllowanceC ChargeN No Allowance or ChargeR Allowance Request

SAC02 1300 Service, Promotion, Allowance, orCharge Code

Description: Code identifying the service,promotion, allowance, or chargeUser Note 1: See FoodserviceImplementation Guidelines Appendix - DataElements

User Note 1: See FoodserviceImplementation Guidelines Appendix - DataElements

C ID 4/4 Used

CodeList Summary (Total Codes: 1053, Included: 5)Code NameD350 Goods and Services Credit AllowanceD360 Goods and Services Tax Charge

User Note 1:User Note 1:Provincal Tobacco Tax.Provincal Tobacco Tax.

H490 Subject To Tax On ResaleH770 Tax - State TaxH806 Tax Credit

User Note 1:User Note 1:Provincial Tax Credit.Provincial Tax Credit.

SAC03 559 Agency Qualifier Code

Description: Code identifying the agencyassigning the code values

C ID 2/2 Used

CodeList Summary (Total Codes: 176, Included: 1)

Page 407: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Purchase Order Change Request - BuyerInitiated Foodservice - 860

July 2012 [V004010-2012 FS] 13Copyright 2012 - GS1 Canada

Code NameVI Voluntary Inter-Industry Commerce Standard (VICS) EDI

SAC04 1301 Agency Service, Promotion, Allowance,or Charge Code

Description: Agency maintained codeidentifying the service, promotion,allowance, or chargeUser Note 1: See Section III for code list.User Note 1: See Section III for code list.

C AN 1/10 Used

SAC05 610 Amount

Description: Monetary amountUser Note 1: When SAC01 contains code Aor code C, then this data element is required.This will resolve any differences between thesender's and receiver's system calculations ofamounts, i.e., rounding errors whenallowances or charges are expressed inpercentages or rates.

User Note 1: When SAC01 contains code Aor code C, then this data element is required.This will resolve any differences between thesender's and receiver's system calculations ofamounts, i.e., rounding errors whenallowances or charges are expressed inpercentages or rates.

O N2 1/15 Used

SAC06 378 Allowance/Charge Percent Qualifier

Description: Code indicating on whatbasis allowance or charge percent iscalculated

C ID 1/1 Used

CodeList Summary (Total Codes: 11, Included: 7)Code Name1 Item List Cost2 Item Net Cost3 Discount/Gross

User Note 1:User Note 1:All allowances are off the gross price including cash discount.All allowances are off the gross price including cash discount.

4 Discount/NetUser Note 1:User Note 1:

All allowances are off the gross price. Cash discounts are off the net.All allowances are off the gross price. Cash discounts are off the net.

5 Base Price per UnitUser Note 1:User Note 1:

Line item discountLine item discount

6 Base Price Amount7 Base Price Amount Less Previous Discount

User Note 1:User Note 1:Declining balance methodDeclining balance method

SAC07 332 Percent

Description: Percent expressed as apercentUser Note 1: The percent is sent with adecimal point only when needed, e.g., 10.5%is sent as ``10.5'', and 2% is sent as ``2''.

User Note 1: The percent is sent with adecimal point only when needed, e.g., 10.5%is sent as ``10.5'', and 2% is sent as ``2''.

C R 1/6 Used

SAC08 118 Rate O R 1/9 Used

Page 408: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Purchase Order Change Request - BuyerInitiated Foodservice - 860

Ref Id Element Name Req Type Min/Max Usage

July 2012 [V004010-2012 FS] 14Copyright 2012 - GS1 Canada

Description: Rate expressed in thestandard monetary denomination for thecurrency specified

SAC09 355 Unit or Basis for Measurement Code

Description: Code specifying the units inwhich a value is being expressed, ormanner in which a measurement hasbeen takenUser Note 1: See Section III for code list.User Note 1: See Section III for code list.

C ID 2/2 Used

CodeList Summary (Total Codes: 794, Included: 12)Code NameBG BagBR BarrelCA CaseDR DrumEA EachGA GallonKG KilogramLB PoundLT LiterPA PailPL Pallet/Unit LoadTE Tote

SAC10 380 Quantity

Description: Numeric value of quantityUser Note 1: When SAC02 contains codeD170, this data element is required and willcontain the quantity of free goods. The unit ofmeasure is in SAC09.

SAC10 alone is used to indicate a specificquantity which could be a dollar amount, thatis applicable to the service, promotion,allowance, or charge.

User Note 1: When SAC02 contains codeD170, this data element is required and willcontain the quantity of free goods. The unit ofmeasure is in SAC09.

SAC10 alone is used to indicate a specificquantity which could be a dollar amount, thatis applicable to the service, promotion,allowance, or charge.

C R 1/15 Used

SAC11 380 Quantity

Description: Numeric value of quantity

O R 1/15 Used

SAC12 331 Allowance or Charge Method ofHandling Code

Description: Code indicating method ofhandling for an allowance or charge

O ID 2/2 Used

CodeList Summary (Total Codes: 22, Included: 6)Code Name01 Bill Back

User Note 1:User Note 1:

Page 409: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Purchase Order Change Request - BuyerInitiated Foodservice - 860

Code Name

July 2012 [V004010-2012 FS] 15Copyright 2012 - GS1 Canada

The allowance or charge amount will be adjudicated as a separate item, i.e., a debit/creditmemo or a separate invoice. The amount will not be reflected in the invoice total amount.The allowance or charge amount will be adjudicated as a separate item, i.e., a debit/creditmemo or a separate invoice. The amount will not be reflected in the invoice total amount.

02 Off InvoiceUser Note 1:User Note 1:

The allowance or charge amount will be reflected in the total transaction amount, e.g.,Total Invoice Amount = Merchandise Price + Charges - Allowances.The allowance or charge amount will be reflected in the total transaction amount, e.g.,Total Invoice Amount = Merchandise Price + Charges - Allowances.

03 Vendor Check to CustomerUser Note 1:User Note 1:

The vendor will issue a check directly to the customer of the retailer, or end consumer, forthe allowance or charge amount. The amount is not reflected in the total invoice amount.The vendor will issue a check directly to the customer of the retailer, or end consumer, forthe allowance or charge amount. The amount is not reflected in the total invoice amount.

04 Credit Customer AccountUser Note 1:User Note 1:

The retailer's account will be credited for the amount of the allowance or charge. Theamount is not reflected in the total invoice amount.The retailer's account will be credited for the amount of the allowance or charge. Theamount is not reflected in the total invoice amount.

05 Charge to be Paid by VendorUser Note 1:User Note 1:

The vendor is responsible for the allowance or charge amount. The exact method ofadjudication has been agreed to by the trading partners. The amount will not be reflectedin the total invoice amount.

The vendor is responsible for the allowance or charge amount. The exact method ofadjudication has been agreed to by the trading partners. The amount will not be reflectedin the total invoice amount.

06 Charge to be Paid by CustomerUser Note 1:User Note 1:

When the order/item is a direct ship to the customer, or end consumer of the retailer, theallowance or charge amount is the responsibility of the customer or end consumer. If it isnot a drop ship to the customer of the retailer, then the allowance or charge amount is theresponsibility of the retailer. The exact method of adjudication has been agreed to by thetrading partners. The amount will not be reflected in the total invoice amount.

When the order/item is a direct ship to the customer, or end consumer of the retailer, theallowance or charge amount is the responsibility of the customer or end consumer. If it isnot a drop ship to the customer of the retailer, then the allowance or charge amount is theresponsibility of the retailer. The exact method of adjudication has been agreed to by thetrading partners. The amount will not be reflected in the total invoice amount.

SAC13 127 Reference Identification

Description: Reference information asdefined for a particular Transaction Set oras specified by the ReferenceIdentification Qualifier

C AN 1/30 Used

SAC14 770 Option Number

Description: A unique number identifyingavailable promotion or allowance optionswhen more than one is offered

O AN 1/20 Used

SAC15 352 Description

Description: A free-form description toclarify the related data elements and theircontent

C AN 1/80 Used

SAC16 819 Language Code

Description: Code designating thelanguage used in text, from a standardcode list maintained by the InternationalStandards Organization (ISO 639)

O ID 2/3 Used

Syntax Rules: 1. R0203 - At least one of SAC02 or SAC03 is required.

Page 410: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Purchase Order Change Request - BuyerInitiated Foodservice - 860

July 2012 [V004010-2012 FS] 16Copyright 2012 - GS1 Canada

2. P0304 - If either SAC03 or SAC04 is present, then the other is required.3. P0607 - If either SAC06 or SAC07 is present, then the other is required.4. P0910 - If either SAC09 or SAC10 is present, then the other is required.5. C1110 - If SAC11 is present, then SAC10 is required.6. L130204 - If SAC13 is present, then at least one of SAC02 or SAC04 is required.7. C1413 - If SAC14 is present, then SAC13 is required.8. C1615 - If SAC16 is present, then SAC15 is required.

Semantics: 1. If SAC01 is "A" or "C", then at least one of SAC05, SAC07, or SAC08 is required.2. SAC05 is the total amount for the service, promotion, allowance, or charge.3. If SAC05 is present with SAC07 or SAC08, then SAC05 takes precedence.4. SAC08 is the allowance or charge rate per unit. 5. SAC10 and SAC11 is the quantity basis when the allowance or charge quantity is different from the purchase

order or invoice quantity.6. SAC10 and SAC11 used together indicate a quantity range, which could be a dollar amount, that is applicable

to service, promotion, allowance, or charge.7. SAC13 is used in conjunction with SAC02 or SAC04 to provide a specific reference number as identified by

the code used.8. SAC14 is used in conjunction with SAC13 to identify an option when there is more than one option of the

promotion.9. SAC16 is used to identify the language being used in SAC15.

Comments: 1. SAC04 may be used to uniquely identify the service, promotion, allowance, or charge. In addition, it may be

used in conjunction to further the code in SAC02.2. In some business applications, it is necessary to advise the trading partner of the actual dollar amount that a

particular allowance, charge, or promotion was based on to reduce ambiguity. This amount is commonlyreferred to as "Dollar Basis Amount". It is represented in the SAC segment in SAC10 using the qualifier "DO" -Dollars in SAC09.

User Note 1:User Note 1:There is one segment for each Allowance, Charge, Service, or Promotion being specified. If this segment appears in theheader area of the transaction set, the data applies to the entire transaction set. If this segment appears in the detail areaof the transaction set, the data applies only to that line item. The data specified in the header area is exclusive of the dataspecified in the detail area; it is not the sum of the data in the detail area, i.e., allowances or charges.

SAC03 contains special service requirement codes and special processing codes. This code list is maintained by the VICS EDISMC and is located in Section III of this guideline.

There is one segment for each Allowance, Charge, Service, or Promotion being specified. If this segment appears in theheader area of the transaction set, the data applies to the entire transaction set. If this segment appears in the detail areaof the transaction set, the data applies only to that line item. The data specified in the header area is exclusive of the dataspecified in the detail area; it is not the sum of the data in the detail area, i.e., allowances or charges.

SAC03 contains special service requirement codes and special processing codes. This code list is maintained by the VICS EDISMC and is located in Section III of this guideline.

Page 411: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Purchase Order Change Request - BuyerInitiated Foodservice - 860

July 2012 [V004010-2012 FS] 17Copyright 2012 - GS1 Canada

ITD Terms of Sale/Deferred Termsof Sale

Pos: 130 Max: 5Heading - Optional

Loop: N/A Elements: 8

User Option (Usage): UsedPurpose: To specify terms of sale

Element Summary: Ref Id Element Name Req Type Min/Max UsageITD01 336 Terms Type Code

Description: Code identifying type ofpayment terms

O ID 2/2 Used

CodeList Summary (Total Codes: 65, Included: 4)Code Name05 Discount Not Applicable08 Basic Discount Offered09 Proximo14 Previously agreed upon

ITD02 333 Terms Basis Date Code

Description: Code identifying thebeginning of the terms period

O ID 1/2 Used

CodeList Summary (Total Codes: 17, Included: 6)Code Name1 Ship Date2 Delivery Date3 Invoice Date4 Specified Date7 Effective Date15 Receipt of Goods

ITD03 338 Terms Discount Percent

Description: Terms discount percentage,expressed as a percent, available to thepurchaser if an invoice is paid on orbefore the Terms Discount Due DateUser Note 1: The percent is sent with adecimal point only when needed, e.g., 10.5%is sent as ``10.5'', and 2% is sent as ``2''.

User Note 1: The percent is sent with adecimal point only when needed, e.g., 10.5%is sent as ``10.5'', and 2% is sent as ``2''.

O R 1/6 Used

ITD04 370 Terms Discount Due Date

Description: Date payment is due ifdiscount is to be earned expressed informat CCYYMMDD

C DT 8/8 Used

ITD05 351 Terms Discount Days Due

Description: Number of days in the termsdiscount period by which payment is dueif terms discount is earned

C N0 1/3 Used

Page 412: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Purchase Order Change Request - BuyerInitiated Foodservice - 860

Ref Id Element Name Req Type Min/Max Usage

July 2012 [V004010-2012 FS] 18Copyright 2012 - GS1 Canada

User Note 1: The end of the term period isderived by adding this value to the beginningof the term period, as qualified by ITD02.

User Note 1: The end of the term period isderived by adding this value to the beginningof the term period, as qualified by ITD02.

ITD06 446 Terms Net Due Date

Description: Date when total invoiceamount becomes due expressed in formatCCYYMMDD

O DT 8/8 Used

ITD07 386 Terms Net Days

Description: Number of days until totalinvoice amount is due (discount notapplicable)User Note 1: The end of the term period isderived by adding this value to the beginningof the term period, as qualified by ITD02.

User Note 1: The end of the term period isderived by adding this value to the beginningof the term period, as qualified by ITD02.

O N0 1/3 Used

ITD08 362 Terms Discount Amount

Description: Total amount of termsdiscount

O N2 1/10 Used

Syntax Rules: 1. L03040513 - If ITD03 is present, then at least one of ITD04, ITD05 or ITD13 is required.2. L08040513 - If ITD08 is present, then at least one of ITD04, ITD05 or ITD13 is required.3. L091011 - If ITD09 is present, then at least one of ITD10 or ITD11 is required.

Semantics: 1. ITD15 is the percentage applied to a base amount used to determine a late payment charge.

Comments: 1. If the code in ITD01 is "04", then ITD07 or ITD09 is required and either ITD10 or ITD11 is required; if the code

in ITD01 is "05", then ITD06 or ITD07 is required.

User Note 1:User Note 1:See Section V (ITD Terms Specification and Formulas) for usage examples.

In the transitional period for the retail industry, from paper to full automated EDI transactions, there may be a perceivedneed to send text data with the terms. Clearly the goal is to have the entire retail industry participating in EDI. Therefore, iftext data is needed to be sent for terms, ITD12 will contain the free form text. If additional text is needed, additional ITDsegments will be used.

Many times, deferred terms are specified on the purchase order with only the knowledge that the terms are to be based on adate value which is not known, e.g., invoice or delivery date. What is known is the percentage or dollar amount of eachdeferred installment, and the number of days after the date the terms are based on, that each installment will be due. Inthese cases, ITD01 will contain code 04, indicating deferred or installment terms, and ITD02 will contain the appropriateterms date basis code (most typically code 2 for Delivery Date, code 3 for Invoice Date, or code 15 for Receipt of Goods Date).ITD07 will contain the number of days after the terms basis date that this installment is due. ITD10 or ITD11 will be used toindicate a dollar amount (ITD10) for that installment or the percent (ITD11) for that installment. Use one ITD segment foreach installment.

When specifying deferred terms and the exact terms basis date is known, e.g., invoice date, ITD09 should be used to specifythe exact deferred or installment date.

See Section V (ITD Terms Specification and Formulas) for usage examples.

In the transitional period for the retail industry, from paper to full automated EDI transactions, there may be a perceivedneed to send text data with the terms. Clearly the goal is to have the entire retail industry participating in EDI. Therefore, iftext data is needed to be sent for terms, ITD12 will contain the free form text. If additional text is needed, additional ITDsegments will be used.

Many times, deferred terms are specified on the purchase order with only the knowledge that the terms are to be based on adate value which is not known, e.g., invoice or delivery date. What is known is the percentage or dollar amount of eachdeferred installment, and the number of days after the date the terms are based on, that each installment will be due. Inthese cases, ITD01 will contain code 04, indicating deferred or installment terms, and ITD02 will contain the appropriateterms date basis code (most typically code 2 for Delivery Date, code 3 for Invoice Date, or code 15 for Receipt of Goods Date).ITD07 will contain the number of days after the terms basis date that this installment is due. ITD10 or ITD11 will be used toindicate a dollar amount (ITD10) for that installment or the percent (ITD11) for that installment. Use one ITD segment foreach installment.

When specifying deferred terms and the exact terms basis date is known, e.g., invoice date, ITD09 should be used to specifythe exact deferred or installment date.

Page 413: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Purchase Order Change Request - BuyerInitiated Foodservice - 860

July 2012 [V004010-2012 FS] 19Copyright 2012 - GS1 Canada

DTM Date/Time Reference Pos: 150 Max: 10Heading - Optional

Loop: N/A Elements: 3

User Option (Usage): UsedPurpose: To specify pertinent dates and times

Element Summary: Ref Id Element Name Req Type Min/Max UsageDTM01 374 Date/Time Qualifier

Description: Code specifying type of dateor time, or both date and time

M ID 3/3 Must use

CodeList Summary (Total Codes: 1112, Included: 2)Code Name002 Delivery Requested118 Requested Pick-up

DTM02 373 Date

Description: Date expressed asCCYYMMDD

C DT 8/8 Must use

DTM03 337 Time

Description: Time expressed in 24-hourclock time as follows: HHMM, orHHMMSS, or HHMMSSD, orHHMMSSDD, where H = hours (00-23), M= minutes (00-59), S = integer seconds(00-59) and DD = decimal seconds;decimal seconds are expressed asfollows: D = tenths (0-9) and DD =hundredths (00-99)

C TM 4/8 Used

Syntax Rules: 1. R020305 - At least one of DTM02, DTM03 or DTM05 is required.2. C0403 - If DTM04 is present, then DTM03 is required.3. P0506 - If either DTM05 or DTM06 is present, then the other is required.

User Note 1:User Note 1:This segment is used to specify order processing dates.This segment is used to specify order processing dates.

Page 414: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Purchase Order Change Request - BuyerInitiated Foodservice - 860

July 2012 [V004010-2012 FS] 20Copyright 2012 - GS1 Canada

TD5 Carrier Details (RoutingSequence/Transit Time)

Pos: 240 Max: 12Heading - Optional

Loop: N/A Elements: 5

User Option (Usage): UsedPurpose: To specify the carrier and sequence of routing and provide transit time information

Element Summary: Ref Id Element Name Req Type Min/Max UsageTD501 133 Routing Sequence Code

Description: Code describing therelationship of a carrier to a specificshipment movement

O ID 1/2 Used

CodeList Summary (Total Codes: 23, Included: 13)Code Name1 1st Carrier after Origin Carrier2 2nd Carrier after Origin Carrier3 3rd Carrier after Origin Carrier4 4th Carrier after Origin Carrier5 5th Carrier after Origin Carrier6 6th Carrier after Origin Carrier7 7th Carrier after Origin Carrier8 8th Carrier after Origin Carrier9 9th Carrier after Origin CarrierA Origin Carrier, Agent's Routing (Rail)B Origin/Delivery Carrier (Any Mode)O Origin Carrier (Air, Motor, or Ocean)S Origin Carrier, Shipper's Routing (Rail)

TD502 66 Identification Code Qualifier

Description: Code designating thesystem/method of code structure used forIdentification Code (67)

C ID 1/2 Used

CodeList Summary (Total Codes: 215, Included: 3)Code Name2 Standard Carrier Alpha Code (SCAC)91 Assigned by Seller or Seller's Agent92 Assigned by Buyer or Buyer's Agent

TD503 67 Identification Code

Description: Code identifying a party orother code

C AN 2/80 Used

TD504 91 Transportation Method/Type Code

Description: Code specifying the methodor type of transportation for the shipment

C ID 1/2 Used

CodeList Summary (Total Codes: 71, Included: 2)

Page 415: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Purchase Order Change Request - BuyerInitiated Foodservice - 860

July 2012 [V004010-2012 FS] 21Copyright 2012 - GS1 Canada

Code NameH Customer PickupM Motor (Common Carrier)

TD505 387 Routing

Description: Free-form description of therouting or requested routing for shipment,or the originating carrier's identity

C AN 1/35 Used

Syntax Rules: 1. R0204050612 - At least one of TD502, TD504, TD505, TD506 or TD512 is required.2. C0203 - If TD502 is present, then TD503 is required.3. C0708 - If TD507 is present, then TD508 is required.4. C1011 - If TD510 is present, then TD511 is required.5. C1312 - If TD513 is present, then TD512 is required.6. C1413 - If TD514 is present, then TD513 is required.7. C1512 - If TD515 is present, then TD512 is required.

Semantics: 1. TD515 is the country where the service is to be performed.

Comments: 1. When specifying a routing sequence to be used for the shipment movement in lieu of specifying each carrier

within the movement, use TD502 to identify the party responsible for defining the routing sequence, and useTD503 to identify the actual routing sequence, specified by the party identified in TD502.

User Note 1:User Note 1:This segment is used to specify every carrier in the routing sequence or a specific routing sequence that has been previouslyidentified (usually from a routing guide). The segment can also be used to indicate estimated transit time in days. Only useTD501 if needed for clarity; this is not a requirement in most retail applications. When referring to a pre-established routingguide, use code 91 or 92 in TD502, and identify the routing sequence, from the routing guide, in TD503. To identify a specificprivate parcel service, TD502 will contain code 2, and TD503 will contain the corresponding SCAC. TD510 and TD511 are usedto specify transit time.

This segment is used to specify every carrier in the routing sequence or a specific routing sequence that has been previouslyidentified (usually from a routing guide). The segment can also be used to indicate estimated transit time in days. Only useTD501 if needed for clarity; this is not a requirement in most retail applications. When referring to a pre-established routingguide, use code 91 or 92 in TD502, and identify the routing sequence, from the routing guide, in TD503. To identify a specificprivate parcel service, TD502 will contain code 2, and TD503 will contain the corresponding SCAC. TD510 and TD511 are usedto specify transit time.

Page 416: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Purchase Order Change Request - BuyerInitiated Foodservice - 860

July 2012 [V004010-2012 FS] 22Copyright 2012 - GS1 Canada

TD3 Carrier Details (Equipment) Pos: 250 Max: 12Heading - Optional

Loop: N/A Elements: 1

User Option (Usage): UsedPurpose: To specify transportation details relating to the equipment used by the carrier

Element Summary: Ref Id Element Name Req Type Min/Max UsageTD301 40 Equipment Description Code

Description: Code identifying type ofequipment used for shipment

C ID 2/2 Used

CodeList Summary (Total Codes: 134, Included: 4)Code NameCV Closed VanFT Flat Bed TrailerRT Controlled Temperature Trailer (Reefer)TL Trailer (not otherwise specified)

Syntax Rules: 1. E0110 - Only one of TD301 or TD310 may be present.2. C0203 - If TD302 is present, then TD303 is required.3. C0405 - If TD304 is present, then TD305 is required.4. P0506 - If either TD305 or TD306 is present, then the other is required.

Page 417: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Purchase Order Change Request - BuyerInitiated Foodservice - 860

July 2012 [V004010-2012 FS] 23Copyright 2012 - GS1 Canada

N9 Reference Identification Pos: 285 Max: 1Heading - Optional

Loop: N9 Elements: 2

User Option (Usage): UsedPurpose: To transmit identifying information as specified by the Reference Identification Qualifier

Element Summary: Ref Id Element Name Req Type Min/Max UsageN901 128 Reference Identification Qualifier

Description: Code qualifying theReference Identification

M ID 2/3 Must use

CodeList Summary (Total Codes: 1503, Included: 1)Code NameAH Agreement Number

N902 127 Reference Identification

Description: Reference information asdefined for a particular Transaction Set oras specified by the ReferenceIdentification Qualifier

C AN 1/30 Must use

Syntax Rules: 1. R0203 - At least one of N902 or N903 is required.2. C0605 - If N906 is present, then N905 is required.

Semantics: 1. N906 reflects the time zone which the time reflects.2. N907 contains data relating to the value cited in N902.

Page 418: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Purchase Order Change Request - BuyerInitiated Foodservice - 860

July 2012 [V004010-2012 FS] 24Copyright 2012 - GS1 Canada

MSG Message Text Pos: 290 Max: 1000Heading - Optional

Loop: N9 Elements: 1

User Option (Usage): UsedPurpose: To provide a free-form format that allows the transmission of text information

Element Summary: Ref Id Element Name Req Type Min/Max UsageMSG01 933 Free-Form Message Text

Description: Free-form message text

M AN 1/264 Must use

Syntax Rules: 1. C0302 - If MSG03 is present, then MSG02 is required.

Semantics: 1. MSG03 is the number of lines to advance before printing.

Comments: 1. MSG02 is not related to the specific characteristics of a printer, but identifies top of page, advance a line, etc.2. If MSG02 is "AA - Advance the specified number of lines before print" then MSG03 is required.

User Note 1:User Note 1:This segment will contain any text clauses for the agreement referenced in the previous N9 segment.This segment will contain any text clauses for the agreement referenced in the previous N9 segment.

Page 419: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Purchase Order Change Request - BuyerInitiated Foodservice - 860

July 2012 [V004010-2012 FS] 25Copyright 2012 - GS1 Canada

N1 Name Pos: 300 Max: 1Heading - Optional

Loop: N1 Elements: 4

User Option (Usage): UsedPurpose: To identify a party by type of organization, name, and code

Element Summary: Ref Id Element Name Req Type Min/Max UsageN101 98 Entity Identifier Code

Description: Code identifying anorganizational entity, a physical location,property or an individual

M ID 2/3 Must use

CodeList Summary (Total Codes: 1312, Included: 8)Code NameBO Broker or Sales Office

User Note 1:User Note 1:For a domestic purchase order, this is the manufacturer's sales office. For an importpurchase order this is the sales office that interacts with the manufacturer's/buyer's agent.For a domestic purchase order, this is the manufacturer's sales office. For an importpurchase order this is the sales office that interacts with the manufacturer's/buyer's agent.

BS Bill and Ship ToBT Bill-to-PartyBY Buying Party (Purchaser)SF Ship FromST Ship ToSU Supplier/Manufacturer

User Note 1:User Note 1:Supplier may or may not be the manufacturerSupplier may or may not be the manufacturer

VN VendorUser Note 1:User Note 1:

Party supplying the products being maintainedParty supplying the products being maintained

N102 93 Name

Description: Free-form name

C AN 1/60 Used

N103 66 Identification Code Qualifier

Description: Code designating thesystem/method of code structure used forIdentification Code (67)

C ID 1/2 Used

CodeList Summary (Total Codes: 215, Included: 2)Code Name9 D-U-N-S+4, D-U-N-S Number with Four Character SuffixUL UCC/EAN Location Code

Description: Global Location Number (GLN) (Revised name) A globally unique 13 digit code used for the identification of any physical or legal locationthat needs to be uniquely identified for use in the supply chain. A GS1 identification key SEE CODE SOURCE 583

N104 67 Identification Code C AN 2/80 Used

Page 420: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Purchase Order Change Request - BuyerInitiated Foodservice - 860

Ref Id Element Name Req Type Min/Max Usage

July 2012 [V004010-2012 FS] 26Copyright 2012 - GS1 Canada

Description: Code identifying a party orother codeUser Note 1: This is the location code asdefined by N103. The location code may be aformal number, e.g., DUNS, or it may beassigned by either the buyer or seller. Thelocation refers to a store, warehouse,distribution center, plant, etc. Location codesare used to alleviate the need to sendcomplete names and addresses.

User Note 1: This is the location code asdefined by N103. The location code may be aformal number, e.g., DUNS, or it may beassigned by either the buyer or seller. Thelocation refers to a store, warehouse,distribution center, plant, etc. Location codesare used to alleviate the need to sendcomplete names and addresses.

Syntax Rules: 1. R0203 - At least one of N102 or N103 is required.2. P0304 - If either N103 or N104 is present, then the other is required.

Comments: 1. This segment, used alone, provides the most efficient method of providing organizational identification. To

obtain this efficiency the "ID Code" (N104) must provide a key to the table maintained by the transactionprocessing party.

2. N105 and N106 further define the type of entity in N101.

User Note 1:User Note 1:N103 and N104 are required except when N101 contains code CT, MA or OB.

When the ship to is the end consumer (customer of retailer), N103 and N104 are not required.

In some EDI implementations, it may be necessary to identify the sender and/or receiver of the transaction set within eachtransaction set. To identify the sender of the transaction set, N101 will contain code FR, N103 will contain code 93, and N104will contain the actual identification number. To identify the receiver of the transaction set, N101 will contain code TO, N103will contain code 94, and N104 will contain the actual identification number. These four codes may be used only in thecombination listed above and may be used only to identify the sender and/or receiver of the transaction set.

N103 and N104 are required except when N101 contains code CT, MA or OB.

When the ship to is the end consumer (customer of retailer), N103 and N104 are not required.

In some EDI implementations, it may be necessary to identify the sender and/or receiver of the transaction set within eachtransaction set. To identify the sender of the transaction set, N101 will contain code FR, N103 will contain code 93, and N104will contain the actual identification number. To identify the receiver of the transaction set, N101 will contain code TO, N103will contain code 94, and N104 will contain the actual identification number. These four codes may be used only in thecombination listed above and may be used only to identify the sender and/or receiver of the transaction set.

Page 421: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Purchase Order Change Request - BuyerInitiated Foodservice - 860

July 2012 [V004010-2012 FS] 27Copyright 2012 - GS1 Canada

N2 Additional Name Information Pos: 310 Max: 2Heading - Optional

Loop: N1 Elements: 2

User Option (Usage): UsedPurpose: To specify additional names or those longer than 35 characters in length

Element Summary: Ref Id Element Name Req Type Min/Max UsageN201 93 Name

Description: Free-form name

M AN 1/60 Must use

N202 93 Name

Description: Free-form name

O AN 1/60 Used

Page 422: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Purchase Order Change Request - BuyerInitiated Foodservice - 860

July 2012 [V004010-2012 FS] 28Copyright 2012 - GS1 Canada

N3 Address Information Pos: 320 Max: 2Heading - Optional

Loop: N1 Elements: 2

User Option (Usage): UsedPurpose: To specify the location of the named party

Element Summary: Ref Id Element Name Req Type Min/Max UsageN301 166 Address Information

Description: Address information

M AN 1/55 Must use

N302 166 Address Information

Description: Address information

O AN 1/55 Used

Page 423: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Purchase Order Change Request - BuyerInitiated Foodservice - 860

July 2012 [V004010-2012 FS] 29Copyright 2012 - GS1 Canada

N4 Geographic Location Pos: 330 Max: >1Heading - Optional

Loop: N1 Elements: 4

User Option (Usage): UsedPurpose: To specify the geographic place of the named party

Element Summary: Ref Id Element Name Req Type Min/Max UsageN401 19 City Name

Description: Free-form text for city name

O AN 2/30 Used

N402 156 State or Province Code

Description: Code (StandardState/Province) as defined by appropriategovernment agency

O ID 2/2 Used

N403 116 Postal Code

Description: Code defining internationalpostal zone code excluding punctuationand blanks (zip code for United States)

O ID 3/15 Used

N404 26 Country Code

Description: Code identifying the countryUser Note 1: CA Canada

MX Mexico

US United States

User Note 1: CA Canada

MX Mexico

US United States

O ID 2/3 Used

Syntax Rules: 1. C0605 - If N406 is present, then N405 is required.

Comments: 1. A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location.2. N402 is required only if city name (N401) is in the U.S. or Canada.

Page 424: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Purchase Order Change Request - BuyerInitiated Foodservice - 860

July 2012 [V004010-2012 FS] 30Copyright 2012 - GS1 Canada

REF Reference Identification Pos: 340 Max: 12Heading - Optional

Loop: N1 Elements: 2

User Option (Usage): UsedPurpose: To specify identifying information

Element Summary: Ref Id Element Name Req Type Min/Max UsageREF01 128 Reference Identification Qualifier

Description: Code qualifying theReference Identification

M ID 2/3 Must use

CodeList Summary (Total Codes: 1503, Included: 1)Code NameDK Dock Number

REF02 127 Reference Identification

Description: Reference information asdefined for a particular Transaction Set oras specified by the ReferenceIdentification Qualifier

C AN 1/30 Must use

Syntax Rules: 1. R0203 - At least one of REF02 or REF03 is required.

Semantics: 1. REF04 contains data relating to the value cited in REF02.

User Note 1:User Note 1:This segment is used to identify a dock number, within the ship-to location, when the ship-to-location number does notuniquely identify the ship to and dock number.This segment is used to identify a dock number, within the ship-to location, when the ship-to-location number does notuniquely identify the ship to and dock number.

Page 425: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Purchase Order Change Request - BuyerInitiated Foodservice - 860

July 2012 [V004010-2012 FS] 31Copyright 2012 - GS1 Canada

POC Line Item Change Pos: 010 Max: 1Detail - Optional

Loop: POC Elements: 9

User Option (Usage): UsedPurpose: To specify changes to a line item

Element Summary: Ref Id Element Name Req Type Min/Max UsagePOC01 350 Assigned Identification

Description: Alphanumeric charactersassigned for differentiation within atransaction set

O AN 1/20 Used

POC02 670 Change or Response Type Code

Description: Code specifying the type ofchange to the line item

M ID 2/2 Must use

CodeList Summary (Total Codes: 29, Included: 7)Code NameAI Add Additional Item(s)CE Changes To Item Level Allowance/ChargesCT Change of DatesDI Delete Item(s)PC Price ChangeQD Quantity DecreaseQI Quantity Increase

POC03 330 Quantity Ordered

Description: Quantity orderedUser Note 1: This is the current (net)amount on order before the change quantity(POC04) is applied.

User Note 1: This is the current (net)amount on order before the change quantity(POC04) is applied.

O R 1/15 Used

POC04 671 Quantity Left to Receive

Description: Quantity left to receive asqualified by the unit of measureUser Note 1: This is the quantity to besubtracted or added to the quantity ordered(POC03), based on the code in POC02.

User Note 1: This is the quantity to besubtracted or added to the quantity ordered(POC03), based on the code in POC02.

C R 1/9 Used

POC05 C001 Composite Unit of Measure

Description: To identify a composite unitof measure(See Figures Appendix forexamples of use)

C Comp Used

POC05-01 355 Unit or Basis for Measurement Code

Description: Code specifying the units inwhich a value is being expressed, ormanner in which a measurement hasbeen taken

M ID 2/2 Must use

Page 426: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Purchase Order Change Request - BuyerInitiated Foodservice - 860

Ref Id Element Name Req Type Min/Max Usage

July 2012 [V004010-2012 FS] 32Copyright 2012 - GS1 Canada

User Note 1: See Section III for code list.User Note 1: See Section III for code list.

CodeList Summary (Total Codes: 794, Included: 12)Code NameBG BagBR BarrelCA CaseDR DrumEA EachGA GallonKG KilogramLB PoundLT LiterPA PailPL Pallet/Unit LoadTE Tote

POC06 212 Unit Price

Description: Price per unit of product,service, commodity, etc.User Note 1: The price is sent with adecimal point only when needed, e.g., $15.95would be sent as ``15.95'', and $29.00 wouldbe sent as ``29''.

User Note 1: The price is sent with adecimal point only when needed, e.g., $15.95would be sent as ``15.95'', and $29.00 wouldbe sent as ``29''.

C R 1/17 Used

POC07 639 Basis of Unit Price Code

Description: Code identifying the type ofunit price for an itemUser Note 1: This data element is used toclarify or alter the basis of unit price. The unitprice expressed in POC06 is always in thesame terms as the unit of measure in POC05,unless otherwise specified in POC07.

User Note 1: This data element is used toclarify or alter the basis of unit price. The unitprice expressed in POC06 is always in thesame terms as the unit of measure in POC05,unless otherwise specified in POC07.

O ID 2/2 Used

CodeList Summary (Total Codes: 91, Included: 13)Code NameLD Catalog Price per DozenLE Catalog Price per EachNC No ChargePO Price per OuncePP Price per PoundPR PromotionQT QuotedRD Retail Price per DozenRE Retail Price per EachTD Contract Price per DozenTE Contract Price per EachWD Wholesale Price per DozenWE Wholesale Price per Each

Page 427: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Purchase Order Change Request - BuyerInitiated Foodservice - 860

Ref Id Element Name Req Type Min/Max Usage

July 2012 [V004010-2012 FS] 33Copyright 2012 - GS1 Canada

POC08 235 Product/Service ID Qualifier

Description: Code identifying thetype/source of the descriptive numberused in Product/Service ID (234)

C ID 2/2 Used

CodeList Summary (Total Codes: 477, Included: 1)Code NameUK U.P.C./EAN Shipping Container Code (1-2-5-5-1)

Description: GTIN-14 A 14-digit GS1 Identification Key composed of an Indicator Digit, GS1 Company Prefix, ItemReference and Check Digit used to identify trade items SEE CODE SOURCE 41

POC09 234 Product/Service ID

Description: Identifying number for aproduct or service

C AN 1/48 Used

Syntax Rules: 1. C030405 - If POC03 is present, then POC04 and POC05 are required.2. C0706 - If POC07 is present, then POC06 is required.3. P0809 - If either POC08 or POC09 is present, then the other is required.4. P1011 - If either POC10 or POC11 is present, then the other is required.5. P1213 - If either POC12 or POC13 is present, then the other is required.6. P1415 - If either POC14 or POC15 is present, then the other is required.7. P1617 - If either POC16 or POC17 is present, then the other is required.8. P1819 - If either POC18 or POC19 is present, then the other is required.9. P2021 - If either POC20 or POC21 is present, then the other is required.

10. P2223 - If either POC22 or POC23 is present, then the other is required.11. P2425 - If either POC24 or POC25 is present, then the other is required.12. P2627 - If either POC26 or POC27 is present, then the other is required.

Semantics: 1. POC01 is the purchase order line item identification.

User Note 1:User Note 1:POC03 is the current (net) amount on order before the quantity is applied. POC04 is the quantity to be subtracted or addedbased upon the code in POC02.

The multi-SKU case pack is used by retailers to order cases packed with specific items, each with a specific quantity. This issimilar to the dynamic assortment, however the unit of measurement code in POC05 is different for each use.

For dynamic assortments, POC05 will contain code AS. This identifies the item listed in the Product/Service IDs as anassortment and the contents of the assortment are listed in subsequent SLN segments. For assortments, at least oneoccurrence of the Product/Service ID Qualifier and the Product/Service ID are required to identify the assortment. This maybe a U.P.C., a vendor assigned number, or a retailer assigned number. There is no implication of packaging for assortments;this is part of the trading partners' business practices. Assortments are primarily used as an ordering tool.

For the multi-SKU case pack, POC05 will contain code CA, and there is no requirement to send a Product/Service ID in thePOC segment. The use of code CA in POC05, and the presence of the SLN segments, informs the receiver to pack the caseswith the SKUs and quantities in the SLN segments. The quantity in POC03 is the number of cases being ordered. Each SLNsegment, that follows the POC segment, lists the Product ID, e.g., U.P.C., and the quantity of the SKU that is to be in the case.

POC03 is the current (net) amount on order before the quantity is applied. POC04 is the quantity to be subtracted or addedbased upon the code in POC02.

The multi-SKU case pack is used by retailers to order cases packed with specific items, each with a specific quantity. This issimilar to the dynamic assortment, however the unit of measurement code in POC05 is different for each use.

For dynamic assortments, POC05 will contain code AS. This identifies the item listed in the Product/Service IDs as anassortment and the contents of the assortment are listed in subsequent SLN segments. For assortments, at least oneoccurrence of the Product/Service ID Qualifier and the Product/Service ID are required to identify the assortment. This maybe a U.P.C., a vendor assigned number, or a retailer assigned number. There is no implication of packaging for assortments;this is part of the trading partners' business practices. Assortments are primarily used as an ordering tool.

For the multi-SKU case pack, POC05 will contain code CA, and there is no requirement to send a Product/Service ID in thePOC segment. The use of code CA in POC05, and the presence of the SLN segments, informs the receiver to pack the caseswith the SKUs and quantities in the SLN segments. The quantity in POC03 is the number of cases being ordered. Each SLNsegment, that follows the POC segment, lists the Product ID, e.g., U.P.C., and the quantity of the SKU that is to be in the case.

Page 428: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Purchase Order Change Request - BuyerInitiated Foodservice - 860

July 2012 [V004010-2012 FS] 34Copyright 2012 - GS1 Canada

The total units in each case is the sum of the quantities in the SLN segment.

When POC02 contains code PC, POC06 may be used to specify the new unit cost for the item, and the CTP segmentimmediately following may be used to specify the new price. The type of price is defined by CTP02.

The codes listed for POC08 apply to every occurrence of Data Element 235 in the POC segment.

See Section III for complete U.P.C. and EAN code definitions.

The total units in each case is the sum of the quantities in the SLN segment.

When POC02 contains code PC, POC06 may be used to specify the new unit cost for the item, and the CTP segmentimmediately following may be used to specify the new price. The type of price is defined by CTP02.

The codes listed for POC08 apply to every occurrence of Data Element 235 in the POC segment.

See Section III for complete U.P.C. and EAN code definitions.

Page 429: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Purchase Order Change Request - BuyerInitiated Foodservice - 860

July 2012 [V004010-2012 FS] 35Copyright 2012 - GS1 Canada

CTP Pricing Information Pos: 040 Max: >1Detail - Optional

Loop: POC Elements: 2

User Option (Usage): UsedPurpose: To specify pricing information

Element Summary: Ref Id Element Name Req Type Min/Max UsageCTP02 236 Price Identifier Code

Description: Code identifying pricingspecification

C ID 3/3 Must use

CodeList Summary (Total Codes: 164, Included: 1)Code NameUCP Unit cost price

User Note 1:User Note 1:Item list costItem list cost

CTP03 212 Unit Price

Description: Price per unit of product,service, commodity, etc.User Note 1: The price is sent with adecimal point only when needed, e.g., $15.95would be sent as ``15.95'', and $29.00 wouldbe sent as ``29''.

User Note 1: The price is sent with adecimal point only when needed, e.g., $15.95would be sent as ``15.95'', and $29.00 wouldbe sent as ``29''.

C R 1/17 Must use

Syntax Rules: 1. P0405 - If either CTP04 or CTP05 is present, then the other is required.2. C0607 - If CTP06 is present, then CTP07 is required.3. C0902 - If CTP09 is present, then CTP02 is required.4. C1002 - If CTP10 is present, then CTP02 is required.5. C1103 - If CTP11 is present, then CTP03 is required.

Semantics: 1. CTP07 is a multiplier factor to arrive at a final discounted price. A multiplier of .90 would be the factor if a 10%

discount is given.2. CTP08 is the rebate amount.

Comments: 1. See Figures Appendix for an example detailing the use of CTP03 and CTP04.2. See Figures Appendix for an example detailing the use of CTP03, CTP04 and CTP07.

Page 430: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Purchase Order Change Request - BuyerInitiated Foodservice - 860

July 2012 [V004010-2012 FS] 36Copyright 2012 - GS1 Canada

PID Product/Item Description Pos: 050 Max: 1Detail - Optional

Loop: PID Elements: 3

User Option (Usage): UsedPurpose: To describe a product or process in coded or free-form format

Element Summary: Ref Id Element Name Req Type Min/Max UsagePID01 349 Item Description Type

Description: Code indicating the formatof a description

M ID 1/1 Must use

CodeList Summary (Total Codes: 3, Included: 1)Code NameF Free-form

User Note 1:User Note 1:The description will be found in PID05.The description will be found in PID05.

PID02 750 Product/Process Characteristic Code

Description: Code identifying the generalclass of a product or processcharacteristic

O ID 2/3 Used

CodeList Summary (Total Codes: 217, Included: 5)Code Name08 Product73 Vendor color description74 Vendor size description75 Buyer's Color Description91 Buyer's Item Size Description

PID05 352 Description

Description: A free-form description toclarify the related data elements and theircontent

C AN 1/80 Used

Syntax Rules: 1. C0403 - If PID04 is present, then PID03 is required.2. R0405 - At least one of PID04 or PID05 is required.3. C0703 - If PID07 is present, then PID03 is required.4. C0804 - If PID08 is present, then PID04 is required.5. C0905 - If PID09 is present, then PID05 is required.

Semantics: 1. Use PID03 to indicate the organization that publishes the code list being referred to.2. PID04 should be used for industry-specific product description codes.3. PID08 describes the physical characteristics of the product identified in PID04. A "Y" indicates that the

specified attribute applies to this item; an "N" indicates it does not apply. Any other value is indeterminate.4. PID09 is used to identify the language being used in PID05.

Page 431: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Purchase Order Change Request - BuyerInitiated Foodservice - 860

July 2012 [V004010-2012 FS] 37Copyright 2012 - GS1 Canada

Comments: 1. If PID01 equals "F", then PID05 is used. If PID01 equals "S", then PID04 is used. If PID01 equals "X", then

both PID04 and PID05 are used.2. Use PID06 when necessary to refer to the product surface or layer being described in the segment.3. PID07 specifies the individual code list of the agency specified in PID03.

User Note 1:User Note 1:The PID segment is used to provide product/item descriptions in text and or coded formats. The codes in PID04 aremaintained by the VICS EDI SMC and are only printed in this guideline.

This segment may be used to transmit semi-custom product descriptions, such as made-to-order window coverings, jewelry,furniture, apparel, automotive parts, and other customer specific products. When used for this purpose, PID04 will containthe multi-part VICS EDI Semi-Custom Product Description Code. The complete code list is contained in Section III. In additionto the VICS EDI Semi-Custom Product Description Code, PID05 may be used for text descriptions, PID06 for relativeplacement, and additional MEA segment(s) for actual measurement values.

The PID segment is used to provide product/item descriptions in text and or coded formats. The codes in PID04 aremaintained by the VICS EDI SMC and are only printed in this guideline.

This segment may be used to transmit semi-custom product descriptions, such as made-to-order window coverings, jewelry,furniture, apparel, automotive parts, and other customer specific products. When used for this purpose, PID04 will containthe multi-part VICS EDI Semi-Custom Product Description Code. The complete code list is contained in Section III. In additionto the VICS EDI Semi-Custom Product Description Code, PID05 may be used for text descriptions, PID06 for relativeplacement, and additional MEA segment(s) for actual measurement values.

Page 432: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Purchase Order Change Request - BuyerInitiated Foodservice - 860

July 2012 [V004010-2012 FS] 38Copyright 2012 - GS1 Canada

PO4 Item Physical Details Pos: 090 Max: >1Detail - Optional

Loop: POC Elements: 4

User Option (Usage): UsedPurpose: To specify the physical qualities, packaging, weights, and dimensions relating to the item

Element Summary: Ref Id Element Name Req Type Min/Max UsagePO401 356 Pack

Description: The number of innercontainers, or number of eaches if thereare no inner containers, per outercontainer

O N0 1/6 Used

PO402 357 Size

Description: Size of supplier units inpack

C R 1/8 Used

PO403 355 Unit or Basis for Measurement Code

Description: Code specifying the units inwhich a value is being expressed, ormanner in which a measurement hasbeen taken

C ID 2/2 Used

CodeList Summary (Total Codes: 794, Included: 12)Code NameBG BagBR BarrelCA CaseDR DrumEA EachGA GallonKG KilogramLB PoundLT LiterPA PailPL Pallet/Unit LoadTE Tote

PO414 810 Inner Pack

Description: The number of eaches perinner container

O N0 1/6 Used

Syntax Rules: 1. P0203 - If either PO402 or PO403 is present, then the other is required.2. C0506 - If PO405 is present, then PO406 is required.3. P0607 - If either PO406 or PO407 is present, then the other is required.4. P0809 - If either PO408 or PO409 is present, then the other is required.5. C1013 - If PO410 is present, then PO413 is required.

Page 433: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Purchase Order Change Request - BuyerInitiated Foodservice - 860

July 2012 [V004010-2012 FS] 39Copyright 2012 - GS1 Canada

6. C1113 - If PO411 is present, then PO413 is required.7. C1213 - If PO412 is present, then PO413 is required.8. L13101112 - If PO413 is present, then at least one of PO410, PO411 or PO412 is required.9. C1716 - If PO417 is present, then PO416 is required.

10. C1804 - If PO418 is present, then PO404 is required.

Semantics: 1. PO415 is used to indicate the relative layer of this package or range of packages within the layers of

packaging. Relative Position 1 (value R1) is the innermost package.2. PO416 is the package identifier or the beginning package identifier in a range of identifiers.3. PO417 is the ending package identifier in a range of identifiers.4. PO418 is the number of packages in this layer.

Comments: 1. PO403 - The "Unit or Basis for Measure Code" in this segment position is for purposes of defining the pack

(PO401) /size (PO402) measure which indicates the quantity in the inner pack unit. For example: If the cartoncontains 24 12-Ounce packages, it would be described as follows: Data element 356 = "24"; Data element357 = "12"; Data element 355 = "OZ".

2. PO413 defines the unit of measure for PO410, PO411, and PO412.

User Note 1:User Note 1:This segment is used to specify the packaging of the item in the case or carton. There may be two levels of packagingspecified. The first level is always specified by using PO401 (Pack). The first level may be actual items, e.g., consumer units,or it may be the number of smaller containers within the case. The second level, specified using PO414 (Inner Pack), is thenumber of eaches in each inner container when PO401 is the number of smaller containers within the case. See Section V(Pack/Inner Pack Usage) for usage examples.

This segment can be used also to specify the weight and/or volume (cube) for the item by using PO406 and PO407, and/orPO408 and PO409.

This segment is used to specify the packaging of the item in the case or carton. There may be two levels of packagingspecified. The first level is always specified by using PO401 (Pack). The first level may be actual items, e.g., consumer units,or it may be the number of smaller containers within the case. The second level, specified using PO414 (Inner Pack), is thenumber of eaches in each inner container when PO401 is the number of smaller containers within the case. See Section V(Pack/Inner Pack Usage) for usage examples.

This segment can be used also to specify the weight and/or volume (cube) for the item by using PO406 and PO407, and/orPO408 and PO409.

Page 434: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Purchase Order Change Request - BuyerInitiated Foodservice - 860

July 2012 [V004010-2012 FS] 40Copyright 2012 - GS1 Canada

SAC Service, Promotion,Allowance, or ChargeInformation

Pos: 130 Max: 1Detail - Optional

Loop: SAC Elements: 16

User Option (Usage): UsedPurpose: To request or identify a service, promotion, allowance, or charge; to specify the amount or percentage forthe service, promotion, allowance, or charge

Element Summary: Ref Id Element Name Req Type Min/Max UsageSAC01 248 Allowance or Charge Indicator

Description: Code which indicates anallowance or charge for the servicespecified

M ID 1/1 Must use

CodeList Summary (Total Codes: 7, Included: 4)Code NameA AllowanceC ChargeN No Allowance or ChargeR Allowance Request

SAC02 1300 Service, Promotion, Allowance, orCharge Code

Description: Code identifying the service,promotion, allowance, or chargeUser Note 1: See Section III for code list.User Note 1: See Section III for code list.

C ID 4/4 Used

CodeList Summary (Total Codes: 1053, Included: 5)Code NameD350 Goods and Services Credit AllowanceD360 Goods and Services Tax Charge

User Note 1:User Note 1:Provincal Tobacco Tax.Provincal Tobacco Tax.

H490 Subject To Tax On ResaleH770 Tax - State TaxH806 Tax Credit

User Note 1:User Note 1:Provincial Tax Credit.Provincial Tax Credit.

SAC03 559 Agency Qualifier Code

Description: Code identifying the agencyassigning the code values

C ID 2/2 Used

CodeList Summary (Total Codes: 176, Included: 1)Code NameVI Voluntary Inter-Industry Commerce Standard (VICS) EDI

Page 435: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Purchase Order Change Request - BuyerInitiated Foodservice - 860

Ref Id Element Name Req Type Min/Max Usage

July 2012 [V004010-2012 FS] 41Copyright 2012 - GS1 Canada

SAC04 1301 Agency Service, Promotion, Allowance,or Charge Code

Description: Agency maintained codeidentifying the service, promotion,allowance, or chargeUser Note 1: See Section III for code list.User Note 1: See Section III for code list.

C AN 1/10 Used

SAC05 610 Amount

Description: Monetary amountUser Note 1: When SAC01 contains code Aor code C, then this data element is required.This will resolve any differences between thesender's and receiver's system calculations ofamounts, i.e., rounding errors whenallowances or charges are expressed inpercentages or rates.

User Note 1: When SAC01 contains code Aor code C, then this data element is required.This will resolve any differences between thesender's and receiver's system calculations ofamounts, i.e., rounding errors whenallowances or charges are expressed inpercentages or rates.

O N2 1/15 Used

SAC06 378 Allowance/Charge Percent Qualifier

Description: Code indicating on whatbasis allowance or charge percent iscalculated

C ID 1/1 Used

CodeList Summary (Total Codes: 11, Included: 7)Code Name1 Item List Cost2 Item Net Cost3 Discount/Gross

User Note 1:User Note 1:All allowances are off the gross price including cash discount.All allowances are off the gross price including cash discount.

4 Discount/NetUser Note 1:User Note 1:

All allowances are off the gross price. Cash discounts are off the net.All allowances are off the gross price. Cash discounts are off the net.

5 Base Price per UnitUser Note 1:User Note 1:

Line item discountLine item discount

6 Base Price Amount7 Base Price Amount Less Previous Discount

User Note 1:User Note 1:Declining balance methodDeclining balance method

SAC07 332 Percent

Description: Percent expressed as apercentUser Note 1: The percent is sent with adecimal point only when needed, e.g., 10.5%is sent as ``10.5'', and 2% is sent as ``2''.

User Note 1: The percent is sent with adecimal point only when needed, e.g., 10.5%is sent as ``10.5'', and 2% is sent as ``2''.

C R 1/6 Used

SAC08 118 Rate

Description: Rate expressed in the

O R 1/9 Used

Page 436: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Purchase Order Change Request - BuyerInitiated Foodservice - 860

Ref Id Element Name Req Type Min/Max Usage

July 2012 [V004010-2012 FS] 42Copyright 2012 - GS1 Canada

standard monetary denomination for thecurrency specified

SAC09 355 Unit or Basis for Measurement Code

Description: Code specifying the units inwhich a value is being expressed, ormanner in which a measurement hasbeen takenUser Note 1: See Section III for code list.User Note 1: See Section III for code list.

C ID 2/2 Used

CodeList Summary (Total Codes: 794, Included: 12)Code NameBG BagBR BarrelCA CaseDR DrumEA EachGA GallonKG KilogramLB PoundLT LiterPA PailPL Pallet/Unit LoadTE Tote

SAC10 380 Quantity

Description: Numeric value of quantityUser Note 1: When SAC02 contains codeD170, this data element is required and willcontain the quantity of free goods. The unit ofmeasure is in SAC09.

SAC10 alone is used to indicate a specificquantity which could be a dollar amount, thatis applicable to the service, promotion,allowance, or charge.

User Note 1: When SAC02 contains codeD170, this data element is required and willcontain the quantity of free goods. The unit ofmeasure is in SAC09.

SAC10 alone is used to indicate a specificquantity which could be a dollar amount, thatis applicable to the service, promotion,allowance, or charge.

C R 1/15 Used

SAC11 380 Quantity

Description: Numeric value of quantity

O R 1/15 Used

SAC12 331 Allowance or Charge Method ofHandling Code

Description: Code indicating method ofhandling for an allowance or charge

O ID 2/2 Used

CodeList Summary (Total Codes: 22, Included: 6)Code Name01 Bill Back

User Note 1:User Note 1:The allowance or charge amount will be adjudicated as a separate item, i.e., a debit/creditThe allowance or charge amount will be adjudicated as a separate item, i.e., a debit/credit

Page 437: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Purchase Order Change Request - BuyerInitiated Foodservice - 860

Code Name

July 2012 [V004010-2012 FS] 43Copyright 2012 - GS1 Canada

memo or a separate invoice. The amount will not be reflected in the invoice total amount.memo or a separate invoice. The amount will not be reflected in the invoice total amount.

02 Off InvoiceUser Note 1:User Note 1:

The allowance or charge amount will be reflected in the total transaction amount, e.g.,Total Invoice Amount = Merchandise Price + Charges - Allowances.The allowance or charge amount will be reflected in the total transaction amount, e.g.,Total Invoice Amount = Merchandise Price + Charges - Allowances.

03 Vendor Check to CustomerUser Note 1:User Note 1:

The vendor will issue a check directly to the customer of the retailer, or end consumer, forthe allowance or charge amount. The amount is not reflected in the total invoice amount.The vendor will issue a check directly to the customer of the retailer, or end consumer, forthe allowance or charge amount. The amount is not reflected in the total invoice amount.

04 Credit Customer AccountUser Note 1:User Note 1:

The retailer's account will be credited for the amount of the allowance or charge. Theamount is not reflected in the total invoice amount.The retailer's account will be credited for the amount of the allowance or charge. Theamount is not reflected in the total invoice amount.

05 Charge to be Paid by VendorUser Note 1:User Note 1:

The vendor is responsible for the allowance or charge amount. The exact method ofadjudication has been agreed to by the trading partners. The amount will not be reflectedin the total invoice amount.

The vendor is responsible for the allowance or charge amount. The exact method ofadjudication has been agreed to by the trading partners. The amount will not be reflectedin the total invoice amount.

06 Charge to be Paid by CustomerUser Note 1:User Note 1:

When the order/item is a direct ship to the customer, or end consumer of the retailer, theallowance or charge amount is the responsibility of the customer or end consumer. If it isnot a drop ship to the customer of the retailer, then the allowance or charge amount is theresponsibility of the retailer. The exact method of adjudication has been agreed to by thetrading partners. The amount will not be reflected in the total invoice amount.

When the order/item is a direct ship to the customer, or end consumer of the retailer, theallowance or charge amount is the responsibility of the customer or end consumer. If it isnot a drop ship to the customer of the retailer, then the allowance or charge amount is theresponsibility of the retailer. The exact method of adjudication has been agreed to by thetrading partners. The amount will not be reflected in the total invoice amount.

SAC13 127 Reference Identification

Description: Reference information asdefined for a particular Transaction Set oras specified by the ReferenceIdentification Qualifier

C AN 1/30 Used

SAC14 770 Option Number

Description: A unique number identifyingavailable promotion or allowance optionswhen more than one is offered

O AN 1/20 Used

SAC15 352 Description

Description: A free-form description toclarify the related data elements and theircontent

C AN 1/80 Used

SAC16 819 Language Code

Description: Code designating thelanguage used in text, from a standardcode list maintained by the InternationalStandards Organization (ISO 639)

O ID 2/3 Used

Syntax Rules: 1. R0203 - At least one of SAC02 or SAC03 is required.2. P0304 - If either SAC03 or SAC04 is present, then the other is required.

Page 438: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Purchase Order Change Request - BuyerInitiated Foodservice - 860

July 2012 [V004010-2012 FS] 44Copyright 2012 - GS1 Canada

3. P0607 - If either SAC06 or SAC07 is present, then the other is required.4. P0910 - If either SAC09 or SAC10 is present, then the other is required.5. C1110 - If SAC11 is present, then SAC10 is required.6. L130204 - If SAC13 is present, then at least one of SAC02 or SAC04 is required.7. C1413 - If SAC14 is present, then SAC13 is required.8. C1615 - If SAC16 is present, then SAC15 is required.

Semantics: 1. If SAC01 is "A" or "C", then at least one of SAC05, SAC07, or SAC08 is required.2. SAC05 is the total amount for the service, promotion, allowance, or charge.3. If SAC05 is present with SAC07 or SAC08, then SAC05 takes precedence.4. SAC08 is the allowance or charge rate per unit. 5. SAC10 and SAC11 is the quantity basis when the allowance or charge quantity is different from the purchase

order or invoice quantity.6. SAC10 and SAC11 used together indicate a quantity range, which could be a dollar amount, that is applicable

to service, promotion, allowance, or charge.7. SAC13 is used in conjunction with SAC02 or SAC04 to provide a specific reference number as identified by

the code used.8. SAC14 is used in conjunction with SAC13 to identify an option when there is more than one option of the

promotion.9. SAC16 is used to identify the language being used in SAC15.

Comments: 1. SAC04 may be used to uniquely identify the service, promotion, allowance, or charge. In addition, it may be

used in conjunction to further the code in SAC02.2. In some business applications, it is necessary to advise the trading partner of the actual dollar amount that a

particular allowance, charge, or promotion was based on to reduce ambiguity. This amount is commonlyreferred to as "Dollar Basis Amount". It is represented in the SAC segment in SAC10 using the qualifier "DO" -Dollars in SAC09.

User Note 1:User Note 1:There is one segment for each Allowance, Charge, Service, or Promotion being specified. If this segment appears in theheader area of the transaction set, the data applies to the entire transaction set. If this segment appears in the detail areaof the transaction set, the data applies only to that line item. The data specified in the header area is exclusive of the dataspecified in the detail area; it is not the sum of the data in the detail area, i.e., allowances or charges.

SAC03 contains special service requirement codes and special processing codes. This code list is maintained by the VICS EDISMC and is located in Section III of this guideline.

There is one segment for each Allowance, Charge, Service, or Promotion being specified. If this segment appears in theheader area of the transaction set, the data applies to the entire transaction set. If this segment appears in the detail areaof the transaction set, the data applies only to that line item. The data specified in the header area is exclusive of the dataspecified in the detail area; it is not the sum of the data in the detail area, i.e., allowances or charges.

SAC03 contains special service requirement codes and special processing codes. This code list is maintained by the VICS EDISMC and is located in Section III of this guideline.

Page 439: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Purchase Order Change Request - BuyerInitiated Foodservice - 860

July 2012 [V004010-2012 FS] 45Copyright 2012 - GS1 Canada

CTT Transaction Totals Pos: 010 Max: 1Summary - Optional

Loop: CTT Elements: 1

User Option (Usage): UsedPurpose: To transmit a hash total for a specific element in the transaction set

Element Summary: Ref Id Element Name Req Type Min/Max UsageCTT01 354 Number of Line Items

Description: Total number of line items inthe transaction setUser Note 1: The number of POC segmentspresent in the transaction setUser Note 1: The number of POC segmentspresent in the transaction set

M N0 1/6 Must use

Syntax Rules: 1. P0304 - If either CTT03 or CTT04 is present, then the other is required.2. P0506 - If either CTT05 or CTT06 is present, then the other is required.

Comments: 1. This segment is intended to provide hash totals to validate transaction completeness and correctness.

Page 440: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Purchase Order Change Request - BuyerInitiated Foodservice - 860

July 2012 [V004010-2012 FS] 46Copyright 2012 - GS1 Canada

SE Transaction Set Trailer Pos: 030 Max: 1Summary - Mandatory

Loop: N/A Elements: 2

User Option (Usage): Must usePurpose: To indicate the end of the transaction set and provide the count of the transmitted segments (including thebeginning (ST) and ending (SE) segments)

Element Summary: Ref Id Element Name Req Type Min/Max UsageSE01 96 Number of Included Segments

Description: Total number of segmentsincluded in a transaction set including STand SE segments

M N0 1/10 Must use

SE02 329 Transaction Set Control Number

Description: Identifying control numberthat must be unique within the transactionset functional group assigned by theoriginator for a transaction setUser Note 1: This must be the same numberas is in the ST segment (ST02) for thetransaction set.

User Note 1: This must be the same numberas is in the ST segment (ST02) for thetransaction set.

M AN 4/9 Must use

Comments: 1. SE is the last segment of each transaction set.

Page 441: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

997 FunctionalAcknowledgment

Foodservice EDI

Version: 4010-2012 FS Final

Author: Technical StandardsWork Group -Foodservice

Publication: 7/1/2012 Notes: For Implementation

December 2012

Page 442: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Functional Acknowledgment - 997

July 2012 [V004010-2012 FS] iCopyright 2012 - GS1 Canada

Table of Contents

997 Functional Acknowledgment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>ST Transaction Set Header . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>AK1 Functional Group Response Header . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>AK2 Transaction Set Response Header . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>AK3 Data Segment Note . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>AK4 Data Element Note . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>AK5 Transaction Set Response Trailer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>AK9 Functional Group Response Trailer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>SE Transaction Set Trailer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>

. . . . . 1. . . . . 2. . . . . 3. . . . . 4. . . . . 5. . . . . 6. . . . . 8. . . . 10. . . . 13

Page 443: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Functional Acknowledgment - 997

July 2012 [V004010-2012 FS] 1Copyright 2012 - GS1 Canada

997 Functional AcknowledgmentFunctional Group=FA

Purpose: This Draft Standard for Trial Use contains the format and establishes the data contents of the FunctionalAcknowledgment Transaction Set (997) for use within the context of an Electronic Data Interchange (EDI)environment. The transaction set can be used to define the control structures for a set of acknowledgments toindicate the results of the syntactical analysis of the electronically encoded documents. The encoded documents arethe transaction sets, which are grouped in functional groups, used in defining transactions for business datainterchange. This standard does not cover the semantic meaning of the information encoded in the transaction sets.

Heading:Pos Id Segment Name Req Max Use Repeat Notes Usage010 ST Transaction Set Header M 1 N1/010 Must use020 AK1 Functional Group Response

HeaderM 1 N1/020 Must use

LOOP ID - AK2 999999 N1/030L LOOP ID - AK2 999999 N1/030L

030 AK2 Transaction Set ResponseHeader

O 1 N1/030 Used

LOOP ID - AK3 999999 C1/040L LOOP ID - AK3 999999 C1/040L

040 AK3 Data Segment Note O 1 C1/040 Used050 AK4 Data Element Note O 99 Used060 AK5 Transaction Set Response

TrailerM 1 Must use

070 AK9 Functional Group ResponseTrailer

M 1 Must use

080 SE Transaction Set Trailer M 1 Must use

Notes: 1/010 There is only one Functional Acknowledgment Transaction Set per acknowledged functional group.1/020 AK1 is used to respond to the functional group header and to start the acknowledgement for a functional

group. There shall be one AK1 segment for the functional group that is being acknowledged.1/030L AK2 is used to start the acknowledgement of a transaction set within the received functional group. The

AK2 segments shall appear in the same order as the transaction sets in the functional group that hasbeen received and is being acknowledged.

1/030 AK2 is used to start the acknowledgement of a transaction set within the received functional group. TheAK2 segments shall appear in the same order as the transaction sets in the functional group that hasbeen received and is being acknowledged.

Comments: 1/040L The data segments of this standard are used to report the results of the syntactical analysis of the

functional groups of transaction sets; they report the extent to which the syntax complies with thestandards for transaction sets and functional groups. They do not report on the semantic meaning of thetransaction sets (for example, on the ability of the receiver to comply with the request of the sender).

1/040 The data segments of this standard are used to report the results of the syntactical analysis of thefunctional groups of transaction sets; they report the extent to which the syntax complies with thestandards for transaction sets and functional groups. They do not report on the semantic meaning of thetransaction sets (for example, on the ability of the receiver to comply with the request of the sender).

Page 444: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Functional Acknowledgment - 997

July 2012 [V004010-2012 FS] 2Copyright 2012 - GS1 Canada

ST Transaction Set Header Pos: 010 Max: 1Heading - Mandatory

Loop: N/A Elements: 2

User Option (Usage): Must usePurpose: To indicate the start of a transaction set and to assign a control number

Element Summary: Ref Id Element Name Req Type Min/Max UsageST01 143 Transaction Set Identifier Code

Description: Code uniquely identifying aTransaction Set

M ID 3/3 Must use

CodeList Summary (Total Codes: 298, Included: 1)Code Name997 Functional Acknowledgment

ST02 329 Transaction Set Control Number

Description: Identifying control numberthat must be unique within the transactionset functional group assigned by theoriginator for a transaction setNote: The number is sequentially assigned bythe sender, starting with one within eachfunctional group. For each functional group,the first transaction set control number will be0001 and incremented by one for eachadditional transaction set within the group.

Note: The number is sequentially assigned bythe sender, starting with one within eachfunctional group. For each functional group,the first transaction set control number will be0001 and incremented by one for eachadditional transaction set within the group.

M AN 4/9 Must use

Semantics: 1. The transaction set identifier (ST01) used by the translation routines of the interchange partners to select the

appropriate transaction set definition (e.g., 810 selects the Invoice Transaction Set).

Page 445: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Functional Acknowledgment - 997

July 2012 [V004010-2012 FS] 3Copyright 2012 - GS1 Canada

AK1 Functional Group ResponseHeader

Pos: 020 Max: 1Heading - Mandatory

Loop: N/A Elements: 2

User Option (Usage): Must usePurpose: To start acknowledgment of a functional group

Element Summary: Ref Id Element Name Req Type Min/Max UsageAK101 479 Functional Identifier Code

Description: Code identifying a group ofapplication related transaction setsNote: This is the functional group ID of thegroup that is being acknowledged, e.g., if apurchase order group is being acknowledged,the value would be PO; it is the value sent inGS01 for the original transmission.

Note: This is the functional group ID of thegroup that is being acknowledged, e.g., if apurchase order group is being acknowledged,the value would be PO; it is the value sent inGS01 for the original transmission.

M ID 2/2 Must use

CodeList Summary (Total Codes: 234, Included: 6)Code NameIN Invoice Information (810,819)PC Purchase Order Change Request - Buyer Initiated (860)PO Purchase Order (850)PR Purchase Order Acknowledgement (855)RA Payment Order/Remittance Advice (820)SH Ship Notice/Manifest (856)

AK102 28 Group Control Number

Description: Assigned number originatedand maintained by the senderNote: This is the control number assigned tothe group being acknowledged, e.g., this is thecontrol number assigned by the sender of theoriginal transmission. It is the value sent inGS06 for the original transmission.

Note: This is the control number assigned tothe group being acknowledged, e.g., this is thecontrol number assigned by the sender of theoriginal transmission. It is the value sent inGS06 for the original transmission.

M N0 1/9 Must use

Semantics: 1. AK101 is the functional ID found in the GS segment (GS01) in the functional group being acknowledged.2. AK102 is the functional group control number found in the GS segment in the functional group being

acknowledged.

Page 446: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Functional Acknowledgment - 997

July 2012 [V004010-2012 FS] 4Copyright 2012 - GS1 Canada

AK2 Transaction Set ResponseHeader

Pos: 030 Max: 1Heading - Optional

Loop: AK2 Elements: 2

User Option (Usage): UsedPurpose: To start acknowledgment of a single transaction set

Element Summary: Ref Id Element Name Req Type Min/Max UsageAK201 143 Transaction Set Identifier Code

Description: Code uniquely identifying aTransaction SetNote: This is the transaction set ID of thetransaction being acknowledged, e.g., if apurchase order is being acknowledged, thevalue would be 850; it is the value sent in ST01for the original transmission.

Note: This is the transaction set ID of thetransaction being acknowledged, e.g., if apurchase order is being acknowledged, thevalue would be 850; it is the value sent in ST01for the original transmission.

M ID 3/3 Must use

CodeList Summary (Total Codes: 298, Included: 6)Code Name810 Invoice820 Payment Order/Remittance Advice850 Purchase Order855 Purchase Order Acknowledgment856 Ship Notice/Manifest860 Purchase Order Change Request - Buyer Initiated

AK202 329 Transaction Set Control Number

Description: Identifying control numberthat must be unique within the transactionset functional group assigned by theoriginator for a transaction setNote: This is the control number assigned tothe transaction set being acknowledged, e.g.,this is the control number assigned by thesender of the original transmission. It is thevalue sent in ST02 for the originaltransmission.

Note: This is the control number assigned tothe transaction set being acknowledged, e.g.,this is the control number assigned by thesender of the original transmission. It is thevalue sent in ST02 for the originaltransmission.

M AN 4/9 Must use

Semantics: 1. AK201 is the transaction set ID found in the ST segment (ST01) in the transaction set being acknowledged.2. AK202 is the transaction set control number found in the ST segment in the transaction set being

acknowledged.

Page 447: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Functional Acknowledgment - 997

July 2012 [V004010-2012 FS] 5Copyright 2012 - GS1 Canada

AK3 Data Segment Note Pos: 040 Max: 1Heading - Optional

Loop: AK3 Elements: 4

User Option (Usage): UsedPurpose: To report errors in a data segment and identify the location of the data segment

Element Summary: Ref Id Element Name Req Type Min/Max UsageAK301 721 Segment ID Code

Description: Code defining the segmentID of the data segment in error (SeeAppendix A - Number 77)

M ID 2/3 Must use

AK302 719 Segment Position in Transaction Set

Description: The numerical countposition of this data segment from thestart of the transaction set: the transactionset header is count position 1

M N0 1/6 Must use

AK303 447 Loop Identifier Code

Description: The loop ID number givenon the transaction set diagram is thevalue for this data element in segmentsLS and LE

O AN 1/6 Used

AK304 720 Segment Syntax Error Code

Description: Code indicating error foundbased on the syntax editing of a segment

O ID 1/3 Used

CodeList Summary (Total Codes: 8, Included: 3)Code Name1 Unrecognized segment ID2 Unexpected segment3 Mandatory segment missing

Page 448: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Functional Acknowledgment - 997

July 2012 [V004010-2012 FS] 6Copyright 2012 - GS1 Canada

AK4 Data Element Note Pos: 050 Max: 99Heading - Optional

Loop: AK3 Elements: 4

User Option (Usage): UsedPurpose: To report errors in a data element or composite data structure and identify the location of the data element

Element Summary: Ref Id Element Name Req Type Min/Max UsageAK401 C030 Position in Segment

Description: Code indicating the relativeposition of a simple data element, or therelative position of a composite datastructure combined with the relativeposition of the component data elementwithin the composite data structure, inerror; the count starts with 1 for the simpledata element or composite data structureimmediately following the segment ID

M Comp Must use

AK401-01 722 Element Position in Segment

Description: This is used to indicate therelative position of a simple data element,or the relative position of a compositedata structure with the relative position ofthe component within the composite datastructure, in error; in the data segment thecount starts with 1 for the simple dataelement or composite data structureimmediately following the segment ID

M N0 1/2 Must use

AK402 725 Data Element Reference Number

Description: Reference number used tolocate the data element in the DataElement Dictionary

O N0 1/4 Used

AK403 723 Data Element Syntax Error Code

Description: Code indicating the errorfound after syntax edits of a data element

M ID 1/3 Must use

CodeList Summary (Total Codes: 10, Included: 7)Code Name1 Mandatory data element missing2 Conditional required data element missing.3 Too many data elements.4 Data element too short.5 Data element too long.6 Invalid character in data element.7 Invalid code value.

AK404 724 Copy of Bad Data Element

Description: This is a copy of the dataelement in error

O AN 1/99 Used

Page 449: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Functional Acknowledgment - 997

Ref Id Element Name Req Type Min/Max Usage

July 2012 [V004010-2012 FS] 7Copyright 2012 - GS1 Canada

Semantics: 1. In no case shall a value be used for AK404 that would generate a syntax error, e.g., an invalid character.

Page 450: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Functional Acknowledgment - 997

July 2012 [V004010-2012 FS] 8Copyright 2012 - GS1 Canada

AK5 Transaction Set ResponseTrailer

Pos: 060 Max: 1Heading - Mandatory

Loop: AK2 Elements: 6

User Option (Usage): Must usePurpose: To acknowledge acceptance or rejection and report errors in a transaction set

Element Summary: Ref Id Element Name Req Type Min/Max UsageAK501 717 Transaction Set Acknowledgment

Code

Description: Code indicating accept orreject condition based on the syntaxediting of the transaction set

M ID 1/1 Must use

CodeList Summary (Total Codes: 6, Included: 3)Code NameA AcceptedE Accepted But Errors Were NotedR Rejected

AK502 718 Transaction Set Syntax Error Code

Description: Code indicating error foundbased on the syntax editing of atransaction set

O ID 1/3 Used

CodeList Summary (Total Codes: 25, Included: 5)Code Name1 Transaction Set Not Supported2 Transaction Set Trailer Missing3 Transaction Set Control Number in Header and Trailer Do Not Match4 Number of Included Segments Does Not Match Actual Count5 One or More Segments in Error

AK503 718 Transaction Set Syntax Error Code

Description: Code indicating error foundbased on the syntax editing of atransaction set

O ID 1/3 Used

CodeList Summary (Total Codes: 25, Included: 5)Code Name1 Transaction Set Not Supported2 Transaction Set Trailer Missing3 Transaction Set Control Number in Header and Trailer Do Not Match4 Number of Included Segments Does Not Match Actual Count5 One or More Segments in Error

AK504 718 Transaction Set Syntax Error Code

Description: Code indicating error foundbased on the syntax editing of atransaction set

O ID 1/3 Used

Page 451: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Functional Acknowledgment - 997

Ref Id Element Name Req Type Min/Max Usage

July 2012 [V004010-2012 FS] 9Copyright 2012 - GS1 Canada

CodeList Summary (Total Codes: 25, Included: 5)Code Name1 Transaction Set Not Supported2 Transaction Set Trailer Missing3 Transaction Set Control Number in Header and Trailer Do Not Match4 Number of Included Segments Does Not Match Actual Count5 One or More Segments in Error

AK505 718 Transaction Set Syntax Error Code

Description: Code indicating error foundbased on the syntax editing of atransaction set

O ID 1/3 Used

CodeList Summary (Total Codes: 25, Included: 5)Code Name1 Transaction Set Not Supported2 Transaction Set Trailer Missing3 Transaction Set Control Number in Header and Trailer Do Not Match4 Number of Included Segments Does Not Match Actual Count5 One or More Segments in Error

AK506 718 Transaction Set Syntax Error Code

Description: Code indicating error foundbased on the syntax editing of atransaction set

O ID 1/3 Used

CodeList Summary (Total Codes: 25, Included: 5)Code Name1 Transaction Set Not Supported2 Transaction Set Trailer Missing3 Transaction Set Control Number in Header and Trailer Do Not Match4 Number of Included Segments Does Not Match Actual Count5 One or More Segments in Error

Note:Note:The codes listed for AK502 apply to every occurrence of Data Element 718 in the AK5 segment.The codes listed for AK502 apply to every occurrence of Data Element 718 in the AK5 segment.

Page 452: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Functional Acknowledgment - 997

July 2012 [V004010-2012 FS] 10Copyright 2012 - GS1 Canada

AK9 Functional Group ResponseTrailer

Pos: 070 Max: 1Heading - Mandatory

Loop: N/A Elements: 9

User Option (Usage): Must usePurpose: To acknowledge acceptance or rejection of a functional group and report the number of includedtransaction sets from the original trailer, the accepted sets, and the received sets in this functional group

Element Summary: Ref Id Element Name Req Type Min/Max UsageAK901 715 Functional Group Acknowledge Code

Description: Code indicating accept orreject condition based on the syntaxediting of the functional group

M ID 1/1 Must use

CodeList Summary (Total Codes: 7, Included: 4)Code NameA AcceptedE Accepted, But Errors Were Noted.P Partially Accepted, At Least One Transaction Set Was RejectedR Rejected

AK902 97 Number of Transaction Sets Included

Description: Total number of transactionsets included in the functional group orinterchange (transmission) groupterminated by the trailer containing thisdata element

M N0 1/6 Must use

AK903 123 Number of Received Transaction Sets

Description: Number of Transaction Setsreceived

M N0 1/6 Must use

AK904 2 Number of Accepted Transaction Sets

Description: Number of acceptedTransaction Sets in a Functional Group

M N0 1/6 Must use

AK905 716 Functional Group Syntax Error Code

Description: Code indicating error foundbased on the syntax editing of thefunctional group header and/or trailer

O ID 1/3 Used

CodeList Summary (Total Codes: 23, Included: 5)Code Name1 Functional Group Not Supported2 Functional Group Version Not Supported3 Functional Group Trailer Missing4 Group Control Number in the Functional Group Header and Trailer Do Not Agree5 Number of Included Transaction Sets Does Not Match Actual Count

AK906 716 Functional Group Syntax Error Code

O ID 1/3 Used

Page 453: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Functional Acknowledgment - 997

Ref Id Element Name Req Type Min/Max Usage

July 2012 [V004010-2012 FS] 11Copyright 2012 - GS1 Canada

Description: Code indicating error foundbased on the syntax editing of thefunctional group header and/or trailer

CodeList Summary (Total Codes: 23, Included: 5)Code Name1 Functional Group Not Supported2 Functional Group Version Not Supported3 Functional Group Trailer Missing4 Group Control Number in the Functional Group Header and Trailer Do Not Agree5 Number of Included Transaction Sets Does Not Match Actual Count

AK907 716 Functional Group Syntax Error Code

Description: Code indicating error foundbased on the syntax editing of thefunctional group header and/or trailer

O ID 1/3 Used

CodeList Summary (Total Codes: 23, Included: 5)Code Name1 Functional Group Not Supported2 Functional Group Version Not Supported3 Functional Group Trailer Missing4 Group Control Number in the Functional Group Header and Trailer Do Not Agree5 Number of Included Transaction Sets Does Not Match Actual Count

AK908 716 Functional Group Syntax Error Code

Description: Code indicating error foundbased on the syntax editing of thefunctional group header and/or trailer

O ID 1/3 Used

CodeList Summary (Total Codes: 23, Included: 5)Code Name1 Functional Group Not Supported2 Functional Group Version Not Supported3 Functional Group Trailer Missing4 Group Control Number in the Functional Group Header and Trailer Do Not Agree5 Number of Included Transaction Sets Does Not Match Actual Count

AK909 716 Functional Group Syntax Error Code

Description: Code indicating error foundbased on the syntax editing of thefunctional group header and/or trailer

O ID 1/3 Used

CodeList Summary (Total Codes: 23, Included: 5)Code Name1 Functional Group Not Supported2 Functional Group Version Not Supported3 Functional Group Trailer Missing4 Group Control Number in the Functional Group Header and Trailer Do Not Agree5 Number of Included Transaction Sets Does Not Match Actual Count

Page 454: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Functional Acknowledgment - 997

July 2012 [V004010-2012 FS] 12Copyright 2012 - GS1 Canada

Comments: 1. If AK901 contains the value "A" or "E", then the transmitted functional group is accepted.

Note:Note:The codes listed for AK905 apply to every occurrence of Data Element 716 in the AK9 segment.The codes listed for AK905 apply to every occurrence of Data Element 716 in the AK9 segment.

Page 455: Foodservice EDI Transaction Sets Order to Cash...Foodservice EDI Transaction Sets Order to Cash Business Process Flow Information With Implementation Guidelines Prepared by: Technical

Canadian Foodservice ImplementationGuidelines for EDI

GS1 Canada Functional Acknowledgment - 997

July 2012 [V004010-2012 FS] 13Copyright 2012 - GS1 Canada

SE Transaction Set Trailer Pos: 080 Max: 1Heading - Mandatory

Loop: N/A Elements: 2

User Option (Usage): Must usePurpose: To indicate the end of the transaction set and provide the count of the transmitted segments (including thebeginning (ST) and ending (SE) segments)

Element Summary: Ref Id Element Name Req Type Min/Max UsageSE01 96 Number of Included Segments

Description: Total number of segmentsincluded in a transaction set including STand SE segments

M N0 1/10 Must use

SE02 329 Transaction Set Control Number

Description: Identifying control numberthat must be unique within the transactionset functional group assigned by theoriginator for a transaction setNote: This must be the same number as is inthe ST segment (ST02) for the transaction set.Note: This must be the same number as is inthe ST segment (ST02) for the transaction set.

M AN 4/9 Must use

Comments: 1. SE is the last segment of each transaction set.