IMPLEMENTATION GUIDELINES FOR ANSI ASC X12 EDI CONVENTIONS CARRIER PAYMENT ORDER/REMITTANCE ADVICE (820) TRANSACTION SET

Size: px
Start display at page:

Download "IMPLEMENTATION GUIDELINES FOR ANSI ASC X12 EDI CONVENTIONS CARRIER PAYMENT ORDER/REMITTANCE ADVICE (820) TRANSACTION SET"

Transcription

1 IMPLEMENTATION GUIDELINES FOR ANSI ASC X12 EDI CONVENTIONS CARRIER PAYMENT ORDER/REMITTANCE ADVICE (820) TRANSACTION SET FCA US INFORMATION & COMMUNICATION TECHNOLOGY MANAGEMENT ANSI ASC X12 VERSION/RELEASE

2 820 Payment Order/Remittance Advice Functional Group ID=RA Introduction: This standard provides the format and establishes the data contents of a payment order/remittance advice transaction set. The payment order/remittance advice transaction set can be used for three different purposes: (1) to order a financial institution to make payment to payee(s) on behalf of the sending party, (2) to report the completion of a payment to payee(s) by a financial institution, and (3) to give advice to the payee by the payor on the application of a payment made with the payment order or by some other means. This standard is not designed for exception reporting from the financial institution to either party. Notes: The transaction should echo key fields from the freight bill (210 Freight Invoice or paper freight bill). FCA US will use the 820 Remittance Advice to inform carriers that a check has been processed, and is in the mail. The remittance advice will echo the detail line item information normally contained on the paper remittance advice attached to the check. FCA US only transmits an 820 Remittance Advice Transaction Set when it recognizes a Carrier's capability to receive EDI transmissions. The 820 is transmitted under the following conditions: - Carrier has EDI capability - Freight bill data is validated according to the guidelines established by the FCA US service bureau FCA US processes freight payments based on the carrier's submission of paper freight bills or 210 Freight Invoice transaction sets. Letters have been sent to carriers detailing the FCA US guidelines in submitting freight bills. Notes about the new format of this implementation guide: 1. The requirements contained herein have not changed, with the exception of anything that may appear in the History of Changes section below. 2. The term 'Base Status' refers to the requirements as defined by the ASC X12 Standards Organization. 3. The terms 'User Status' and 'User Attributes' refer to FCA US requirements. 4. Data segment sequence tables for each hierarchical level will no longer be presented at the beginning of each hierarchical level. The data segment sequence tables for each hierarchical level will now be presented at the beginning. 5. Segment Syntax and Semantic notes as defined by ASC X12 will now be included where in the 'old' format they were not. 6. Element Description as defined by ASC X12 will now be included where in the 'old' format they were not. 7. Many comments that relate to a particular code value will now appear underneath the code value description, where previously the comments would appear to the right. History of Change: 01/28/2015 V/R FCA US

3 02/05/2008: Upgrade document format; transition to Chrysler LLC. 07/15/2010: Name change from Chrysler LLC to Chrysler Updated Address 01/28/2015: Name Change To FCA US Heading: Page Pos. Seg. Base User Loop Notes and No. No. ID Name Guide Status Max.Use Repeat Comments ST Transaction Set Header M M BPS Beginning Segment for Payment M M 1 Order/Remittance Advice 030 NTE Note/Special Instruction F Not CUR Currency O REF Reference Numbers M M DTM Date/Time/Period M M 10 LOOP ID - N N1 Name O N2 Additional Name Information O N3 Address Information O Not N4 Geographic Location O Not REF Reference Numbers O Not PER Administrative Communications Contact O 3 Detail: Page Pos. Seg. Base User Loop Notes and No. No. ID Name Guide Status Max.Use Repeat Comments LS Loop Header M M 1 LOOP ID - N N1 Name M M 1 LOOP ID - RMT > RMT Remittance Advice O CUR Currency O Not REF Reference Numbers O DTM Date/Time/Period O LE Loop Trailer M M 1 Summary: Page Pos. Seg. Base User Loop Notes and No. No. ID Name Guide Status Max.Use Repeat Comments SE Transaction Set Trailer M M 1 01/28/2015 V/R FCA US

4 Segment: ST Transaction Set Header Position: 010 Loop: Level: Heading Usage: Mandatory Max Use: 1 Purpose: To indicate the start of a transaction set and to assign a control number Syntax Notes: Semantic Notes: Comments: 1 The transaction set identifier (ST01) is intended for use by the translation routines of the interchange partners to select the appropriate transaction set definition (e.g., 810 selects the invoice transaction set). Notes: Example: ST~820~0001 Data Element Summary Ref. Data Base User Des. Element Name Attributes Attributes ST Transaction Set Identifier Code M ID 3/3 M Code uniquely identifying a Transaction Set 820 X12.4 Remittance/Payment Advice ST Transaction Set Control Number M AN 4/9 M Identifying control number assigned by the originator for a transaction set. 01/28/2015 V/R FCA US

5 Segment: BPS Beginning Segment for Payment Order/Remittance Advice Position: 020 Loop: Level: Heading Usage: Mandatory Max Use: 1 Purpose: To (1) indicate the beginning of a payment order/remittance advice transaction set and total payment and (2) to enable related transfer of funds and/or information from payor to payee to occur while utilizing an automated clearing house (ACH) or other banking network. Syntax Notes: Semantic Notes: Comments: 1 BPS02 is the total currency amount of all items being paid in this transaction. 2 When using this transaction set to initiate a payment, BPS04, BPS05, BPS07, BPS09, BPS10, BPS11, and BPS12 may be required, depending upon the conventions issued by the specific banking channel being used. BPS04 and BPS05 relate to the originating depository financial institute (DFI). 3 BPS06 is the account number of the sending company to be debited or credited with payment. 4 BPS09 and BPS10 relate to the receiving DFI. 5 BPS11 is the account number of the receiving company to be debited or credited with the payment. 6 BPS13 is conditional on the ability of the receiving depository financial institution (RDFI) to furnish the actual settlement date, and shall be left blank (omitted) by the originating company. Notes: The BPS02 element is the total currency amount of all line item remittances being paid in this transaction. Example: BPS~PBC~ ~I Data Element Summary Ref. Data Base User Des. Element Name Attributes Attributes BPS Payment Method Code M ID 3/3 M Code used to designate the actual funds transfer method. PBC Commercial Check BPS Monetary Amount M R 1/15 M R 1/9 Monetary amount Total amount being paid BPS Transaction Handling Code M ID 1/1 M Code designating the action to be taken by all parties I Remittance Information Only BPS (DFI) ID Number Qualifier O ID 2/2 Not 01/28/2015 V/R FCA US

6 BPS (DFI) Identification Number O AN 3/12 Not BPS Account Number O AN 1/35 Not BPS Originating Company Identifier O AN 10/10 Not BPS Originating Company Supplemental Code O AN 9/9 Not BPS (DFI) ID Number Qualifier O ID 2/2 Not BPS (DFI) Identification Number O AN 3/12 Not BPS Account Number O AN 1/35 Not BPS Effective Entry Date O DT 6/6 Not BPS Settlement Date C DT 6/6 Not 01/28/2015 V/R FCA US

7 Segment: CUR Currency Position: 040 Loop: Level: Heading Usage: Optional Max Use: 1 Purpose: To specify the currency (dollars, pounds, francs, etc.) used in a transaction Syntax Notes: 1 If CUR08 is present, then CUR07 is required. 2 If CUR09 is present, then CUR07 is required. 3 If CUR11 is present, then CUR10 is required. 4 If CUR12 is present, then CUR10 is required. 5 If CUR14 is present, then CUR13 is required. 6 If CUR15 is present, then CUR13 is required. 7 If CUR17 is present, then CUR16 is required. 8 If CUR18 is present, then CUR16 is required. 9 If CUR20 is present, then CUR19 is required. 10 If CUR21 is present, then CUR19 is required. Semantic Notes: Comments: 1 Monetary values are assumed to be expressed in the currency of the country of the transaction originator unless the optional CUR segment is used to specify a different currency. The CUR segment also permits the transaction originator to indicate a specific exchange rate, foreign exchange location and date/time as the basis for a currency conversion. Example 1. Assuming the currency of the transaction originator is U.S. dollars, the following CUR segment, when used in the heading area of a transaction, would indicate that all monetary values appearing in the transaction are expressed in Canadian Dollars (CAD). (In this example the exchange rate is at the discretion of the receiver). CUR*BY*CAD* N/L Example 2. Assuming the currency of the transaction originator is U.S. dollars, the following CUR segment, when used in the detail area of a transaction, describes a currency conversion for that particular item from U.S. dollars to Canadian dollars. It also indicates that a specific exchange rate, at a specified foreign exchange location on a given date/time be used as the basis for the currency conversion. Notes below the diagram describe the meaning of the element values. CUR*BY*USD*1.20*SE*CAD*NY*007*840821*1400 N/L Identifies the buyer's (BY) currency as U.S. dollars (USD). 2. The multiplier (1.20) is the exchange rate factor for the conversion. 3. Identifies the seller's (SE) currency as Canadian dollars (CAD). 4. Indicates the basis for the exchange rate as the New York Foreign Exchange (NY) and the effective date/time (007) as August 21, 1984 (840821) at 2:00 P.M. (1400). The value for this item is to be converted to Canadian dollars (CAD) at the exchange rate of 1.20, based on the New York Foreign Exchange (NY) at 2:00 P.M. (1400) on August 21, The actual unit price conversion for the item would be: The unit price value 7.50 (U.S. dollars) multiplied by the exchange rate (1.20) equals 9.00 Canadian dollars (7.50 X 1.20 = 9.00) CUR07 through CUR21 provide for five (5) dates/times relating to the currency conversion, i.e., effective date, expiration date, etc. Notes: The FCA US Carrier payment process currently uses two currencies, U.S and Canadian. The process will NOT mix currencies on a single check. For a Carrier performing transportation services in both the U.S.A. and Canada, separate 01/28/2015 V/R FCA US

8 checks will be issued. Examples: CUR~BY~USD CUR~BY~CAD Data Element Summary Ref. Data Base User Des. Element Name Attributes Attributes CUR01 98 Entity Identifier Code M ID 2/2 M Code identifying an organizational entity or a physical location. BY Buying Party (Purchaser) CUR Currency Code M ID 3/3 M Code (Standard ISO) for country in whose currency the charges are specified 'USD' = U.S. Dollar 'CAD' = Canadian Dollar CUR Exchange Rate O R 4/6 Not CUR04 98 Entity Identifier Code O ID 2/2 Not CUR Currency Code O ID 3/3 Not CUR Currency Market/Exchange Code O ID 3/3 Not CUR Date/Time Qualifier C ID 3/3 Not CUR Date O DT 6/6 Not CUR Time O TM 4/4 Not CUR Date/Time Qualifier C ID 3/3 Not CUR Date O DT 6/6 Not CUR Time O TM 4/4 Not CUR Date/Time Qualifier C ID 3/3 Not CUR Date O DT 6/6 Not CUR Time O TM 4/4 Not CUR Date/Time Qualifier C ID 3/3 Not 01/28/2015 V/R FCA US

9 CUR Date O DT 6/6 Not CUR Time O TM 4/4 Not CUR Date/Time Qualifier C ID 3/3 Not CUR Date O DT 6/6 Not CUR Time O TM 4/4 Not 01/28/2015 V/R FCA US

10 Segment: REF Reference Numbers Position: 050 Loop: Level: Heading Usage: Mandatory Max Use: 5 Purpose: To specify identifying numbers. Syntax Notes: 1 At least one of REF02 or REF03 is required. Semantic Notes: Comments: Notes: For the issuance of a check, FCA US will generate two REF segments at the heading level. One REF will reference just the check number that is being applied to all of the following detail line items appearing on the Remittance Advice, while the second REF will identify both the check number as well as the paying bank. Although the standard allows for up to 30 characters, FCA US stores and returns only 7 characters of the check number when the equals 'CK'. When the equals 'DD', FCA US will transmit fourteen (14) characters consisting of a seven (7) position check number as well as a seven (7) positon bank number. Examples: REF~CK~ REF~DD~ Data Element Summary Ref. Data Base User Des. Element Name Attributes Attributes REF M ID 2/2 M Code qualifying the Reference Number. CK Check Number DD Document Identification Code REF Reference Number C AN 1/30 AN 1/14 Reference number or identification number as defined for a particular Transaction Set, or as specified by the. Check number qualified by REF01. Example: REF Description C AN 1/80 Not 01/28/2015 V/R FCA US

11 Segment: DTM Date/Time/Period Position: 060 Loop: Level: Heading Usage: Mandatory Max Use: 10 Purpose: To specify pertinent dates and times Syntax Notes: 1 At least one of DTM02 or DTM03 is required. Semantic Notes: Comments: Notes: FCA US will always use 1 DTM segment in the Heading Area to convey the check paid date appearing on the check Example: DTM~020~ Data Element Summary Ref. Data Base User Des. Element Name Attributes Attributes DTM Date/Time Qualifier M ID 3/3 M Code specifying type of date or time, or both date and time 020 Check DTM Date C DT 6/6 Date (YYMMDD) Check Paid Date DTM Time C TM 4/4 Not DTM Time Code O ID 2/2 Not 01/28/2015 V/R FCA US

12 Segment: N1 Name Position: 070 Loop: N1 Optional Level: Heading Usage: Optional Max Use: 1 Purpose: To identify a party by type of organization, name, and code Syntax Notes: 1 At least one of N102 or N103 is required. 2 If either N103 or N104 is present, then the other is required. Semantic Notes: 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 transaction processing party. Notes: FCA US will use TWO occurrences of the N1 segment. The first occurrence will identify FCA US as the 'payer' of the check, the second N1 segment will identify the 'paying bank' on which the check is drawn. Elements N103 and N104 are conditional, and predicated on the contents of element N101. If element N101 contains 'PR', then elements N103 and N104 are blank. If element N101 contains a 'PB', then elements N103 and N104 contain FCA US assigned codes for the paying bank. Examples: N1~PR~FCA US N1~PB~MORGAN GUARANTY AND TRUST~92~ N1~PB~BANK OF MONTREAL~92~ Data Element Summary Ref. Data Base User Des. Element Name Attributes Attributes N Entity Identifier Code M ID 2/2 M Code identifying an organizational entity or a physical location. PB Paying Bank PR Payer N Name C AN 1/35 Free-form name FCA US assigned name for payment N C ID 1/2 Code designating the system/method of code structure used for Identification Code (67) 92 Assigned by Buyer or Buyer's Agent N Identification Code C ID 2/17 ID 2/7 Code identifying a party. If N101 = 'PB', and CUR02 = 'USD', then N104 = ' '. If N101 = 'PB', and CUR02 = 'CAD', then N104 = ' ' 01/28/2015 V/R FCA US

13 Segment: N2 Additional Name Information Position: 080 Loop: N1 Optional Level: Heading Usage: Optional Max Use: 2 Purpose: To specify additional names or those longer than 35 characters in length Syntax Notes: Semantic Notes: Comments: Notes: FCA US will use N2 segments to support the identification of additional name information pertaining to organization specified in the N1 segment. Examples: N2~LOGISTICS OFFICE N2~TRANSPORTATION SERVICES Data Element Summary Ref. Data Base User Des. Element Name Attributes Attributes N Name M AN 1/35 M Free-form name FCA US use: As needed N Name O AN 1/35 Free-form name FCA US use: As needed 01/28/2015 V/R FCA US

14 Segment: PER Administrative Communications Contact Position: 120 Loop: N1 Optional Level: Heading Usage: Optional Max Use: 3 Purpose: To identify a person or office to whom administrative communications should be directed Syntax Notes: 1 If PER03 is present, then PER04 is required. Semantic Notes: Comments: Notes: FCA US will use one PER segment at the heading level to identify Logistics personnel who have payment authority and responsibility. A name and telephone number will be provided. A PER segment will only be provided for the N1 loop pertaining to the FCA US location. Examples: PER~IC~JOHN DOE~TE~ PER~IC~JANE DOE~TE~ Data Element Summary Ref. Data Base User Des. Element Name Attributes Attributes PER Contact Function Code M ID 2/2 M Code identifying the major duty or responsibility of the person or group named IC Information Contact PER02 93 Name O AN 1/35 Free-form name Information Contact with payment responsibility PER Communication Number Qualifier O ID 2/2 Code identifying the type of communication number TE Telephone PER Communication Number C AN 7/21 AN 7/10 Complete communications number including country or area code when applicable Contact telephone number 01/28/2015 V/R FCA US

15 Segment: LS Loop Header Position: 010 Loop: Level: Detail Usage: Mandatory Max Use: 1 Purpose: To indicate that the next segment begins a loop Syntax Notes: Semantic Notes: Comments: 1 LS is a control segment. LS is always used in conjunction with a corresponding loop trailer (end) - LE, as illustrated below. The LS and LE indicate the start and end of a loop but are not part of the iteration of the loop. LOOP NESTING Loop "A" Header (LS "A") Loop "B" Header (LS "B") Loop "C" Header (LS "C") Loop "C" Trailer (LE "C") Loop "D" Header (LS "D") Loop "D" Trailer (LE "D") Loop "B" Trailer (LE "B") Loop "A" Trailer (LE "A") Neither LS nor LE is used if the data within the loop is not used. Notes: The LS segment is a control segment. It is always used in conjunction with a corresponding loop trailer (end) segment - LE. The LS and LE segments indicate the start and end of a loop, but are not part of the iteration of the loop. Example: LS~1 Data Element Summary Ref. Data Base User Des. Element Name Attributes Attributes LS Loop Identifier Code M ID 1/4 M Code identifying a loop within the transaction set which is bounded by the related LS and LE segments (corresponding LS and LE segments must have the same value for loop identifier). (Note: The loop ID number given on the transaction set diagram is recommended as the value for this data element in segments LS and LE.) '1' for the initial LS segment. Maximum use is 1 for each transaction set 01/28/2015 V/R FCA US

16 Segment: N1 Name Position: 020 Loop: N1 Mandatory Level: Detail Usage: Mandatory Max Use: 1 Purpose: To identify a party by type of organization, name, and code Syntax Notes: 1 At least one of N102 or N103 is required. 2 If either N103 or N104 is present, then the other is required. Semantic Notes: 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 transaction processing party. Notes: FCA US will use as many 'N1' segments as necessary in the LS/LE loop to identify both the origin supplier as well as the destination receiving location. The first N1 segment within a loop will always identify the 'RC' receiving location, while the following 'N1' segments will identify 'SF' shipping origins until another 'N1' segment containing an 'RC' is encountered. Examples: N1~RC~STERLING HEIGHTS ASSEMBLY~92~04025 N1~SF~HOLLEY AUTOMOTIVE DIVISION~92~46435 C N1~RC~JEFFERSON NORTH ASSEMBLY~92~04012 N1~SF~MODERN TOOL & DIE COMPANY~92~63769 F Data Element Summary Ref. Data Base User Des. Element Name Attributes Attributes N Entity Identifier Code M ID 2/2 M Code identifying an organizational entity or a physical location. RC Receiving Location SF Ship From N Name C AN 1/35 Free-form name FCA US assigned plant or supplier name N C ID 1/2 Code designating the system/method of code structure used for Identification Code (67) 92 Assigned by Buyer or Buyer's Agent N Identification Code C ID 2/17 Code identifying a party. If N101 = 'RC', the FCA US assigned receiving location code; If N101 = 'SF', the FCA US assigned supplier location code 01/28/2015 V/R FCA US

17 Segment: RMT Remittance Advice Position: 030 Loop: RMT Optional Level: Detail Usage: Optional Max Use: 1 Purpose: To indicate the detail on items Syntax Notes: Semantic Notes: Comments: 1 Parties using this segment should agree on the content of RMT01 and RMT02 prior to initiating transaction communication. 2 RMT03 may also be used to specify the amount paid when different from the amount invoiced. 3 RMT08 is any amount being deducted from or added to a particular invoice or line item for reasons other than payment discount (e.g., damaged goods, short shipment, tax, penalty or late charge payment). Notes: The RMT01 and RMT02 will qualify the primary Reference Qualifier and Number as the Bill of Lading Number. Other secondary references such as conveyance, trailer, or freight bill numbers will be specified in the REF segments. The RMT03 specifies a paid amount for a detail specific shipment. The sum of all amounts in the RMT03 segment must equal the total check amount specified in the heading BPS02 amount element. If the RMT03 element is zero (0), the detail line item amount has been rejected or denied for payment, and the Adjustment Reason Code (RMT09) will contain a code indicating the reason. The RMT08 element will specify the actual denied or rejected amount. FCA US will use the Description element (RMT10) to indicate that the detail remittance line is the result of the ASN process, submitted freight bills, or adjustment process. Examples: RMT~BM~ ~ ~~~~~~~ASN RMT~BM~27364~0~~~~~524.37~19~FREIGHT BILL NOTE: EXAMPLE 2 AND THE EXAMPLES AT THE END OF THE 820 TRANSACTION SET ILLUSTRATE A ZERO (0) IN ELEMENT RMT03. THIS IS FOR READABILITY PURPOSES ONLY. SINCE THE ELEMENT RMT03 IS OPTIONAL, MOST TRANSLATORS WILL REPLACE THE ELEMENT WITH THE DESIGNATED ELEMENT SEPARATOR RMT~BM~27364~~~~~~~524.37~19~FREIGHT BILL Data Element Summary Ref. Data Base User Des. Element Name Attributes Attributes RMT M ID 2/2 M 01/28/2015 V/R FCA US

18 Code qualifying the Reference Number. BM Bill of Lading Number RMT Reference Number M AN 1/30 M AN 1/16 Reference number or identification number as defined for a particular Transaction Set, or as specified by the. Bill of Lading RMT Monetary Amount O R 1/15 R 1/9 Monetary amount Line item payment RMT Total Invoice Amount O R 1/15 Not RMT Amount Subject to Terms Discount O R 1/15 Not RMT Discounted Amount Due O R 1/15 Not RMT Amount of Discount Taken O R 1/15 Not RMT Monetary Amount O R 1/15 R 1/9 Monetary amount The amount being denied or rejected. RMT Adjustment Reason Code O ID 2/2 Code indicating reason for adjustment to invoice or payment. If RMT08 element is used, RMT09 is mandatory. 19 Duplicate Billing 20 Balance Due Declined 52 Credit for Previous Overpayment 53 Remittance for Previous Underpayment RMT Description O AN 1/80 A free-form description to clarify the related data elements and their content Remittance Description/Code: 'ASN' 'Balance Due' 'Cancellation' 'Debit Memo' 'Freight Bill' 'Voluntary Refund' 01/28/2015 V/R FCA US

19 Segment: REF Reference Numbers Position: 050 Loop: RMT Optional Level: Detail Usage: Optional Max Use: 15 Purpose: To specify identifying numbers. Syntax Notes: 1 At least one of REF02 or REF03 is required. Semantic Notes: Comments: Notes: Provides reference numbers for the carrier to trace payments to a particular shipment or shipments. The primary Bill of Lading reference will be provided in the RMT segment. Additional REF segments within a loop may provide: - Carrier's Conveyance Number (Trailer No.) - Carrier Invoice Number (if available) - Carrier Purchase Order Number (CPO-ID Code) - Check Number of a previous remittance if denied Although the standard allows for up to 30 characters, FCA US stores and returns only the first 16 characters of the supplier's Bill of Lading Number from the original ASN (856). For Conveyance Codes or Trailer Numbers, FCA US will return the first 10 characters that are available. Carrier Purchase Order Numbers will contain up to 9 characters. Examples: REF~CN~ REF~EQ~ REF~PO~ Data Element Summary Ref. Data Base User Des. Element Name Attributes Attributes REF M ID 2/2 M Code qualifying the Reference Number. CK Check Number only if RMT03 equal zero. CN Carrier's Reference Number (PRO/Invoice) EQ Equipment Number PO Purchase Order Number REF Reference Number C AN 1/30 AN 1/16 Reference number or identification number as defined for a particular Transaction Set, or as specified by the. 01/28/2015 V/R FCA US

20 REF Description C AN 1/80 Not 01/28/2015 V/R FCA US

21 Segment: DTM Date/Time/Period Position: 060 Loop: RMT Optional Level: Detail Usage: Optional Max Use: 10 Purpose: To specify pertinent dates and times Syntax Notes: 1 At least one of DTM02 or DTM03 is required. Semantic Notes: Comments: Notes: FCA US will use the DTM segment in the Detail Area to support each RMT and REF segment. When the RMT segment RMT01 element 'Reference Qualifier' indicates 'BM', the DTM segment date will be a 'bill of lading' date. If the REF segment REF01 qualifier specifies a 'CN', the DTM segment date will be a freight bill date. If the REF segment REF01 element defines a 'EQ', the DTM segment will specify a trailer arrival date. If the REF segment REF01 element contains a 'PO', then the following DTM segment will contain the contract's expiration date. If the RMT segment RMT03 contains a 0 (zero) amount indicating that a remittance line item is denied, then the REF segment will contain a 'CK' to indicate the check number on which the remittance line item was paid, and the DTM segment will specify the date on which the check that check was issued. NOTE: The current Remittance Advice check paid date is always shown in the DTM segment at the heading level. Examples: DTM~011~ DTM~036~ DTM~022~ Data Element Summary Ref. Data Base User Des. Element Name Attributes Attributes DTM Date/Time Qualifier M ID 3/3 M Code specifying type of date or time, or both date and time 011 Shipped 020 Check 022 Freight Bill 036 Expiration 050 Received 095 Bill of Lading DTM Date C DT 6/6 Date (YYMMDD) 01/28/2015 V/R FCA US

22 Date qualified by DTM01 (YYMMDD) DTM Time C TM 4/4 Not DTM Time Code O ID 2/2 Not 01/28/2015 V/R FCA US

23 Segment: LE Loop Trailer Position: 070 Loop: Level: Detail Usage: Mandatory Max Use: 1 Purpose: To indicate that the loop immediately preceding this segment is complete Syntax Notes: Semantic Notes: Comments: 1 LE is a control segment. LE is always used in conjunction with a corresponding loop header (start) - LS, as illustrated below. The LS and LE indicate the start and end of a loop but are not part of the iteration of the loop. LOOP NESTING Loop "A" Header (LS "A") Loop "B" Header (LS "B") Loop "C" Header (LS "C") Loop "C" Trailer (LE "C") Loop "D" Header (LS "D") Loop "D" Trailer (LE "D") Loop "B" Trailer (LE "B") Loop "A" Trailer (LE "A") Neither LS nor LE is used if the data within the loop is not used. Notes: The LE segment is a control segment. It is always used in conjunction with a corresponding loop header (start) segment - LS. The LS and LE segments indicate the start and end of a loop, but are not part of the iteration of the loop. Example: LE~1 Data Element Summary Ref. Data Base User Des. Element Name Attributes Attributes LE Loop Identifier Code M ID 1/4 M Code identifying a loop within the transaction set which is bounded by the related LS and LE segments (corresponding LS and LE segments must have the same value for loop identifier). (Note: The loop ID number given on the transaction set diagram is recommended as the value for this data element in segments LS and LE.) 01/28/2015 V/R FCA US

24 Segment: SE Transaction Set Trailer Position: 010 Loop: Level: Summary Usage: Mandatory Max Use: 1 Purpose: To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments). Syntax Notes: Semantic Notes: Comments: 1 SE is the last segment of each transaction set. Notes: Example: SE~51~0001 Data Element Summary Ref. Data Base User Des. Element Name Attributes Attributes SE01 96 Number of Included Segments M N0 1/6 M Total number of segments included in a transaction set including ST and SE segments SE Transaction Set Control Number M AN 4/9 M Identifying control number assigned by the originator for a transaction set. 01/28/2015 V/R FCA US

25 FCA US Carrier Remittance Advice Example 1: EDI Format ST~820~0001 Remittance Advice for Carrier Payment (No Rejects) Interpretation Transaction Set Identifier Code = 820 (X12.4 Remittance/Payment Advice) Transaction Set Control Number = 0001 BPS~PBC~ ~I CUR~BY~USD REF~CK~ REF~DD~ DTM~020~ N1~PR~FCA US N2~TRANSPORTATION SERVICES PER~IC~JOHN DOE~TE~ N1~PB~MORGAN GUARANTY~92~ Payment Method Code = PBC (Commercial Check) Monetary Amount = Transaction Handling Code = I (Remittance Information Only) Entity Identifier Code = BY (Buying Party <Purchaser>) Currency Code = USD = CK (Check Number) Reference Number = = DD (Document Identification Code) Reference Number = Date/Time Qualifier = 020 (Check) Date = 10/17/1990 Entity Identifier Code = PR (Payer) Name = FCA US Name = TRANSPORTATION SERVICES Contact Function Code = IC (Information Contact) Name = JOHN DOE Communication Number Qualifier = TE (Telephone) Communication Number = Entity Identifier Code = PB (Paying Bank) Name = MORGAN GUARANTY Identification Code = LS~1 Loop Identifier Code = 1 N1~RC~JEFFERSON NORTH ASSEMBLY~92~04012 Entity Identifier Code = RC (Receiving Location) Name = JEFFERSON NORTH ASSEMBLY Identification Code = /28/2015 V/R FCA US

26 FCA US Carrier Remittance Advice Example 1: EDI Format Remittance Advice for Carrier Payment (No Rejects) (continued) Interpretation N1~SF~PRINCE CORPORATION~92~75813 B RMT~BM~ ~328.45~~~~~~~ASN REF~CN~ REF~EQ~ REF~PO~27364 DTM~095~ DTM~022~ DTM~050~ DTM~036~ Entity Identifier Code = SF (Ship From) Name = PRINCE CORPORATION Identification Code = B = BM (Bill of Lading Number) Reference Number = Monetary Amount = Description = ASN = CN (Carrier's Reference Number <PRO/Invoice>) Reference Number = = EQ (Equipment Number) Reference Number = = PO (Purchase Order Number) Reference Number = Date/Time Qualifier = 095 (Bill of Lading) Date = 10/11/1990 Date/Time Qualifier = 022 (Freight Bill) Date = 10/11/1990 Date/Time Qualifier = 050 (Received) Date = 10/11/1990 Date/Time Qualifier = 036 (Expiration) Date = 01/31/1991 N1~SF~HOLLEY AUTOMOTIVE DIVISION~92~46435 C Entity Identifier Code = SF (Ship From) Name = HOLLEY AUTOMOTIVE DIVISION Identification Code = C RMT~BM~ ~419.07~~~~~~~ASN REF~CN~ = BM (Bill of Lading Number) Reference Number = Monetary Amount = Description = ASN = CN (Carrier's Reference Number <PRO/Invoice>) Reference Number = /28/2015 V/R FCA US

27 FCA US Carrier Remittance Advice Example 1: EDI Format Remittance Advice for Carrier Payment (No Rejects) (continued) Interpretation REF~EQ~ REF~PO~26374 DTM~095~ DTM~022~ DTM~050~ DTM~036~ = EQ (Equipment Number) Reference Number = = PO (Purchase Order Number) Reference Number = Date/Time Qualifier = 095 (Bill of Lading) Date = 11/22/1990 Date/Time Qualifier = 022 (Freight Bill) Date = 12/11/1990 Date/Time Qualifier = 050 (Received) Date = 12/10/1990 Date/Time Qualifier = 036 (Expiration) Date = 10/01/1992 N1~SF~MODERN TOOL & DIE COMPANY~92~63769 F Entity Identifier Code = SF (Ship From) Name = MODERN TOOL & DIE COMPANY Identification Code = F RMT~BM~ ~ ~~~~~~~FREIGHT BILL REF~CN~ REF~EQ~ REF~PO~2543 DTM~095~ DTM~022~ DTM~050~ = BM (Bill of Lading Number) Reference Number = Monetary Amount = Description = FREIGHT BILL = CN (Carrier's Reference Number <PRO/Invoice>) Reference Number = = EQ (Equipment Number) Reference Number = = PO (Purchase Order Number) Reference Number = 2543 Date/Time Qualifier = 095 (Bill of Lading) Date = 11/14/1990 Date/Time Qualifier = 022 (Freight Bill) Date = 10/11/1990 Date/Time Qualifier = 050 (Received) Date = 11/12/ /28/2015 V/R FCA US

28 FCA US Carrier Remittance Advice Example 1: EDI Format Remittance Advice for Carrier Payment (No Rejects) (continued) Interpretation DTM~036~ N1~RC~STERLING HTS ASSEMBLY~92~04025 N1~SF~MANTON DIVISION~92~65548 C RMT~BM~273456~124.86~~~~~~~ASN REF~CN~ REF~EQ~ DTM~095~ DTM~022~ DTM~050~ N1~SF~CARTEX CORPORATION~92~18918 C RMT~BM~38746~335.12~~~~~~~FREIGHT BILL Date/Time Qualifier = 036 (Expiration) Date = 12/01/1991 Entity Identifier Code = RC (Receiving Location) Name = STERLING HTS ASSEMBLY Identification Code = Entity Identifier Code = SF (Ship From) Name = MANTON DIVISION Identification Code = C = BM (Bill of Lading Number) Reference Number = Monetary Amount = Description = ASN = CN (Carrier's Reference Number <PRO/Invoice>) Reference Number = = EQ (Equipment Number) Reference Number = Date/Time Qualifier = 095 (Bill of Lading) Date = 12/09/1990 Date/Time Qualifier = 022 (Freight Bill) Date = 10/11/1990 Date/Time Qualifier = 050 (Received) Date = 12/09/1990 Entity Identifier Code = SF (Ship From) Name = CARTEX CORPORATION Identification Code = C = BM (Bill of Lading Number) Reference Number = Monetary Amount = Description = FREIGHT BILL 01/28/2015 V/R FCA US

29 FCA US Carrier Remittance Advice Example 1: EDI Format Remittance Advice for Carrier Payment (No Rejects) (continued) Interpretation REF~CN~ REF~EQ~ REF~PO~2543 DTM~095~ DTM~022~ DTM~050~ DTM~036~ = CN (Carrier's Reference Number <PRO/Invoice>) Reference Number = = EQ (Equipment Number) Reference Number = = PO (Purchase Order Number) Reference Number = 2543 Date/Time Qualifier = 095 (Bill of Lading) Date = 11/30/1990 Date/Time Qualifier = 022 (Freight Bill) Date = 12/01/1990 Date/Time Qualifier = 050 (Received) Date = 12/01/1990 Date/Time Qualifier = 036 (Expiration) Date = 12/01/1991 LE~1 Loop Identifier Code = 1 SE~58~0001 Number of Included Segments = 58 Transaction Set Control Number = /28/2015 V/R FCA US

30 FCA US Carrier Remittance Advice Example 2: EDI Format ST~820~0002 Remittance Advice for Carrier Payment (Denied Duplicate Payments) Interpretation Transaction Set Identifier Code = 820 (X12.4 Remittance/Payment Advice) Transaction Set Control Number = 0002 BPS~PBC~663.57~I CUR~BY~USD REF~CK~ REF~DD~ DTM~020~ N1~PR~FCA US N2~TRANSPORTATION SERVICES PER~IC~JOHN DOE~TE~ N1~PB~MORGAN GUARANTY~92~ Payment Method Code = PBC (Commercial Check) Monetary Amount = Transaction Handling Code = I (Remittance Information Only) Entity Identifier Code = BY (Buying Party <Purchaser>) Currency Code = USD = CK (Check Number) Reference Number = = DD (Document Identification Code) Reference Number = Date/Time Qualifier = 020 (Check) Date = 10/17/1990 Entity Identifier Code = PR (Payer) Name = FCA US Name = TRANSPORTATION SERVICES Contact Function Code = IC (Information Contact) Name = JOHN DOE Communication Number Qualifier = TE (Telephone) Communication Number = Entity Identifier Code = PB (Paying Bank) Name = MORGAN GUARANTY Identification Code = LS~1 Loop Identifier Code = 1 N1~RC~JEFFERSON NORTH ASSEMBLY~92~04012 Entity Identifier Code = RC (Receiving Location) Name = JEFFERSON NORTH ASSEMBLY Identification Code = /28/2015 V/R FCA US

31 FCA US Carrier Remittance Advice Example 2: EDI Format Remittance Advice for Carrier Payment (Denied Duplicate Payments) (continued) Interpretation N1~SF~PRINCE CORPORATION~92~75813 B RMT~BM~ ~328.45~~~~~~~ASN REF~CN~ REF~EQ~ REF~PO~27364 DTM~095~ DTM~022~ DTM~050~ DTM~036~ Entity Identifier Code = SF (Ship From) Name = PRINCE CORPORATION Identification Code = B = BM (Bill of Lading Number) Reference Number = Monetary Amount = Description = ASN = CN (Carrier's Reference Number <PRO/Invoice>) Reference Number = = EQ (Equipment Number) Reference Number = = PO (Purchase Order Number) Reference Number = Date/Time Qualifier = 095 (Bill of Lading) Date = 10/11/1990 Date/Time Qualifier = 022 (Freight Bill) Date = 10/11/1990 Date/Time Qualifier = 050 (Received) Date = 10/11/1990 Date/Time Qualifier = 036 (Expiration) Date = 01/31/1991 N1~SF~HOLLEY AUTOMOTIVE DIVISION~92~46435 C Entity Identifier Code = SF (Ship From) Name = HOLLEY AUTOMOTIVE DIVISION Identification Code = C RMT~BM~ ~0~~~~~419.07~19~FREIGHT BILL = BM (Bill of Lading Number) Reference Number = Monetary Amount = 0 Monetary Amount = Adjustment Reason Code = 19 (Duplicate Billing) Description = FREIGHT BILL 01/28/2015 V/R FCA US

32 FCA US Carrier Remittance Advice Example 2: EDI Format Remittance Advice for Carrier Payment (Denied Duplicate Payments) (continued) Interpretation REF~CN~ REF~EQ~ REF~PO~26374 REF~CK~ DTM~095~ DTM~022~ DTM~050~ DTM~036~ DTM~020~ = CN (Carrier's Reference Number <PRO/Invoice>) Reference Number = = EQ (Equipment Number) Reference Number = = PO (Purchase Order Number) Reference Number = = CK (Check Number) Reference Number = Date/Time Qualifier = 095 (Bill of Lading) Date = 11/22/1990 Date/Time Qualifier = 022 (Freight Bill) Date = 12/11/1990 Date/Time Qualifier = 050 (Received) Date = 12/10/1990 Date/Time Qualifier = 036 (Expiration) Date = 10/01/1992 Date/Time Qualifier = 020 (Check) Date = 06/24/1990 N1~SF~MODERN TOOL & DIE COMPANY~92~63769 F Entity Identifier Code = SF (Ship From) Name = MODERN TOOL & DIE COMPANY Identification Code = F RMT~BM~ ~0~~~~~ ~19~FREIGHT BILL = BM (Bill of Lading Number) Reference Number = Monetary Amount = 0 Monetary Amount = Adjustment Reason Code = 19 (Duplicate Billing) Description = FREIGHT BILL REF~CN~ = CN (Carrier's Reference Number <PRO/Invoice>) Reference Number = /28/2015 V/R FCA US

33 FCA US Carrier Remittance Advice Example 2: EDI Format Remittance Advice for Carrier Payment (Denied Duplicate Payments) (continued) Interpretation REF~EQ~ REF~PO~2543 REF~CK~ DTM~095~ DTM~022~ DTM~050~ DTM~036~ DTM~020~ N1~RC~STERLING HTS ASSEM~92~04025 N1~SF~MANTON DIVISION~92~65548 C RMT~BM~273456~0~~~~~124.86~19~ASN REF~CN~ = EQ (Equipment Number) Reference Number = = PO (Purchase Order Number) Reference Number = 2543 = CK (Check Number) Reference Number = Date/Time Qualifier = 095 (Bill of Lading) Date = 11/14/1990 Date/Time Qualifier = 022 (Freight Bill) Date = 12/11/1990 Date/Time Qualifier = 050 (Received) Date = 11/12/1990 Date/Time Qualifier = 036 (Expiration) Date = 12/01/1991 Date/Time Qualifier = 020 (Check) Date = 07/15/1990 Entity Identifier Code = RC (Receiving Location) Name = STERLING HTS ASSEM Identification Code = Entity Identifier Code = SF (Ship From) Name = MANTON DIVISION Identification Code = C = BM (Bill of Lading Number) Reference Number = Monetary Amount = 0 Monetary Amount = Adjustment Reason Code = 19 (Duplicate Billing) Description = ASN = CN (Carrier's Reference Number <PRO/Invoice>) Reference Number = /28/2015 V/R FCA US

34 FCA US Carrier Remittance Advice Example 2: EDI Format Remittance Advice for Carrier Payment (Denied Duplicate Payments) (continued) Interpretation REF~EQ~ REF~CK~ DTM~095~ DTM~022~ DTM~050~ DTM~020~ N1~SF~CARTEX CORPORATION~92~18918 C RMT~BM~38746~335.12~~~~~~~FREIGHT BILL REF~CN~ REF~EQ~ REF~PO~2543 DTM~095~ DTM~022~ DTM~050~ = EQ (Equipment Number) Reference Number = = CK (Check Number) Reference Number = Date/Time Qualifier = 095 (Bill of Lading) Date = 12/09/1990 Date/Time Qualifier = 022 (Freight Bill) Date = 10/11/1990 Date/Time Qualifier = 050 (Received) Date = 12/09/1990 Date/Time Qualifier = 020 (Check) Date = 07/15/1990 Entity Identifier Code = SF (Ship From) Name = CARTEX CORPORATION Identification Code = C = BM (Bill of Lading Number) Reference Number = Monetary Amount = Description = FREIGHT BILL = CN (Carrier's Reference Number <PRO/Invoice>) Reference Number = = EQ (Equipment Number) Reference Number = = PO (Purchase Order Number) Reference Number = 2543 Date/Time Qualifier = 095 (Bill of Lading) Date = 11/30/1990 Date/Time Qualifier = 022 (Freight Bill) Date = 12/01/1990 Date/Time Qualifier = 050 (Received) Date = 12/01/ /28/2015 V/R FCA US

35 FCA US Carrier Remittance Advice Example 2: EDI Format Remittance Advice for Carrier Payment (Denied Duplicate Payments) (continued) Interpretation DTM~036~ Date/Time Qualifier = 036 (Expiration) Date = 12/01/1991 LE~1 Loop Identifier Code = 1 SE~64~0002 Number of Included Segments = 64 Transaction Set Control Number = /28/2015 V/R FCA US

36 FCA US Carrier Remittance Advice Example 3: EDI Format ST~820~0003 Remittance Advice for Carrier Payment (Balance Due Payments) Interpretation Transaction Set Identifier Code = 820 (X12.4 Remittance/Payment Advice) Transaction Set Control Number = 0003 BPS~PBC~ ~I CUR~BY~USD REF~CK~ REF~DD~ DTM~020~ N1~PR~FCA US N2~TRANSPORTATION SERVICES PER~IC~JOHN DOE~TE~ N1~PB~MORGAN GUARANTY~92~ Payment Method Code = PBC (Commercial Check) Monetary Amount = Transaction Handling Code = I (Remittance Information Only) Entity Identifier Code = BY (Buying Party <Purchaser>) Currency Code = USD = CK (Check Number) Reference Number = = DD (Document Identification Code) Reference Number = Date/Time Qualifier = 020 (Check) Date = 10/17/1990 Entity Identifier Code = PR (Payer) Name = FCA US Name = TRANSPORTATION SERVICES Contact Function Code = IC (Information Contact) Name = JOHN DOE Communication Number Qualifier = TE (Telephone) Communication Number = Entity Identifier Code = PB (Paying Bank) Name = MORGAN GUARANTY Identification Code = LS~1 Loop Identifier Code = 1 N1~RC~JEFFERSON NORTH ASSEMBLY~92~04012 Entity Identifier Code = RC (Receiving Location) Name = JEFFERSON NORTH ASSEMBLY Identification Code = /28/2015 V/R FCA US

37 FCA US Carrier Remittance Advice Example 3: EDI Format Remittance Advice for Carrier Payment (Balance Due Payments) (continued) Interpretation N1~SF~PRINCE CORPORATION~92~75813 B RMT~BM~ ~328.45~~~~~~~FREIGHT BILL REF~CN~ REF~EQ~ REF~PO~27364 DTM~095~ DTM~022~ DTM~050~ DTM~036~ Entity Identifier Code = SF (Ship From) Name = PRINCE CORPORATION Identification Code = B = BM (Bill of Lading Number) Reference Number = Monetary Amount = Description = FREIGHT BILL = CN (Carrier's Reference Number <PRO/Invoice>) Reference Number = = EQ (Equipment Number) Reference Number = = PO (Purchase Order Number) Reference Number = Date/Time Qualifier = 095 (Bill of Lading) Date = 10/11/1990 Date/Time Qualifier = 022 (Freight Bill) Date = 10/11/1990 Date/Time Qualifier = 050 (Received) Date = 10/11/1990 Date/Time Qualifier = 036 (Expiration) Date = 01/31/1991 N1~SF~HOLLEY AUTOMOTIVE DIVISION~92~46435 C Entity Identifier Code = SF (Ship From) Name = HOLLEY AUTOMOTIVE DIVISION Identification Code = C RMT~BM~ ~419.07~~~~~419.07~53~BALANCE DUE = BM (Bill of Lading Number) Reference Number = Monetary Amount = Monetary Amount = Adjustment Reason Code = 53 (Remittance for Previous Underpayment) Description = BALANCE DUE 01/28/2015 V/R FCA US

38 FCA US Carrier Remittance Advice Example 3: EDI Format Remittance Advice for Carrier Payment (Balance Due Payments) (continued) Interpretation REF~CN~ REF~EQ~ REF~PO~26374 DTM~095~ DTM~022~ DTM~050~ DTM~036~ = CN (Carrier's Reference Number <PRO/Invoice>) Reference Number = = EQ (Equipment Number) Reference Number = = PO (Purchase Order Number) Reference Number = Date/Time Qualifier = 095 (Bill of Lading) Date = 11/22/1990 Date/Time Qualifier = 022 (Freight Bill) Date = 12/11/1990 Date/Time Qualifier = 050 (Received) Date = 12/10/1990 Date/Time Qualifier = 036 (Expiration) Date = 10/01/1992 N1~SF~MODERN TOOL & DIE COMPANY~92~63769 F Entity Identifier Code = SF (Ship From) Name = MODERN TOOL & DIE COMPANY Identification Code = F RMT~BM~ ~ ~~~~~ ~52~DEBIT MEMO = BM (Bill of Lading Number) Reference Number = Monetary Amount = Monetary Amount = Adjustment Reason Code = 52 (Credit for Previous Overpayment) Description = DEBIT MEMO REF~CN~ REF~EQ~ REF~PO~2543 = CN (Carrier's Reference Number <PRO/Invoice>) Reference Number = = EQ (Equipment Number) Reference Number = = PO (Purchase Order Number) Reference Number = /28/2015 V/R FCA US

39 FCA US Carrier Remittance Advice Example 3: EDI Format Remittance Advice for Carrier Payment (Balance Due Payments) (continued) Interpretation DTM~095~ DTM~022~ DTM~050~ DTM~036~ N1~SF~MANTON DIVISION~92~65548 C N1~RC~STERLING HTS ASSEM~92~04025 RMT~BM~273456~124.86~~~~~~53~FREIGHT BILL REF~CN~ REF~EQ~ DTM~095~ DTM~022~ DTM~050~ Date/Time Qualifier = 095 (Bill of Lading) Date = 11/14/1990 Date/Time Qualifier = 022 (Freight Bill) Date = 12/11/1990 Date/Time Qualifier = 050 (Received) Date = 11/12/1990 Date/Time Qualifier = 036 (Expiration) Date = 12/01/1991 Entity Identifier Code = SF (Ship From) Name = MANTON DIVISION Identification Code = C Entity Identifier Code = RC (Receiving Location) Name = STERLING HTS ASSEM Identification Code = = BM (Bill of Lading Number) Reference Number = Monetary Amount = Adjustment Reason Code = 53 (Remittance for Previous Underpayment) Description = FREIGHT BILL = CN (Carrier's Reference Number <PRO/Invoice>) Reference Number = = EQ (Equipment Number) Reference Number = Date/Time Qualifier = 095 (Bill of Lading) Date = 12/09/1990 Date/Time Qualifier = 022 (Freight Bill) Date = 10/11/1990 Date/Time Qualifier = 050 (Received) Date = 12/09/ /28/2015 V/R FCA US

40 FCA US Carrier Remittance Advice Example 3: EDI Format Remittance Advice for Carrier Payment (Balance Due Payments) (continued) Interpretation N1~SF~CARTEX CORPORATION~92~18918 C RMT~BM~38746~335.12~~~~~~~ASN REF~CN~ REF~EQ~ REF~PO~2543 DTM~095~ DTM~022~ DTM~050~ DTM~036~ Entity Identifier Code = SF (Ship From) Name = CARTEX CORPORATION Identification Code = C = BM (Bill of Lading Number) Reference Number = Monetary Amount = Description = ASN = CN (Carrier's Reference Number <PRO/Invoice>) Reference Number = = EQ (Equipment Number) Reference Number = = PO (Purchase Order Number) Reference Number = 2543 Date/Time Qualifier = 095 (Bill of Lading) Date = 11/30/1990 Date/Time Qualifier = 022 (Freight Bill) Date = 12/01/1990 Date/Time Qualifier = 050 (Received) Date = 12/01/1990 Date/Time Qualifier = 036 (Expiration) Date = 12/01/1991 LE~1 Loop Identifier Code = 1 SE~58~0003 Number of Included Segments = 58 Transaction Set Control Number = /28/2015 V/R FCA US

820 Payment Order/Remittance Advice

820 Payment Order/Remittance Advice 820 Payment Order/Remittance Advice X12/V4010/820: 820 Payment Order/Remittance Advice Version: 1.0 Draft Author: Charles Mackey Company: C.H. Robinson Publication: 8/6/2009 Trading Partner: Created: 8/6/2009

More information

810 IBM Subset - Invoice To Customer - (004010)

810 IBM Subset - Invoice To Customer - (004010) 810 IBM Subset - Invoice To Customer - (004010) Functional Group ID=IN Introduction: This Draft Standard for Trial Use contains the format and establishes the data contents of the Invoice Transaction Set

More information

IMPLEMENTATION GUIDELINES FOR ANSI ASC X12 EDI CONVENTIONS COMMODITY PROCUREMENT ACCOUNT ANALYSIS (822) TRANSACTION SET

IMPLEMENTATION GUIDELINES FOR ANSI ASC X12 EDI CONVENTIONS COMMODITY PROCUREMENT ACCOUNT ANALYSIS (822) TRANSACTION SET IMPLEMENTATION GUIDELINES FOR ANSI ASC X12 EDI CONVENTIONS COMMODITY PROCUREMENT ACCOUNT ANALYSIS (822) TRANSACTION SET FCA US INFORMATION & COMMUNICATION TECHNOLOGY MANAGEMENT ANSI ASC X12 VERSION/RELEASE

More information

820 Remittance Advice

820 Remittance Advice 820 Remittance Advice Lowe's EDI 820 Remittance Advice Version: 4010 Author: Lowe's Companies, Inc. Modified: 10/3/2008 Notes: This 820 Implementation Guide is shared across all vendor types. 820 Payment

More information

ANSI X (Lockbox) Inbound (to Eclipse) Version 4010

ANSI X (Lockbox) Inbound (to Eclipse) Version 4010 ANSI X12 823 (Lockbox) Inbound (to Eclipse) Version 4010 Eclipse 823 4010 (customer) 1 10/11/2012 823 Lockbox Functional Group=LB Purpose: This Draft Standard for Trial Use contains the format and establishes

More information

ESIS. EDI Implementation Guide. Purchase Order Change X Version 4010 Release 8.0. EDI_Guide_Change_Order_X12_860_Version_4010_Release_8-0.

ESIS. EDI Implementation Guide. Purchase Order Change X Version 4010 Release 8.0. EDI_Guide_Change_Order_X12_860_Version_4010_Release_8-0. EDI Implementation Guide ESIS Purchase Order Change X12 860 Version 4010 Release 8.0 Page 1 of 37 EDI Implementation Support Information EDI Contact Name: ESIS, E-Commerce Provider of Raytheon EDI Contact

More information

824 Application Advice

824 Application Advice 824 Application Advice X12/V4010/824: 824 Application Advice Version: 1.0 Final Author: IBM Publication: Trading Partner: P2P Modified: 08/17/2006 Notes: Table of Contents 824 Application Advice.................................................................................................

More information

812 Credit/Debit Adjustment

812 Credit/Debit Adjustment 812 Credit/Debit Adjustment Functional Group ID=CD Introduction: This Draft Standard for Trial Use contains the format and establishes the data contents of the Credit/Debit Adjustment Transaction Set (812)

More information

International Truck and Engine Corporation

International Truck and Engine Corporation International Truck and Engine Corporation EDI 824 - - Application Advice VERSION: ANSI ASC X12 Version Release 3040 FINAL Publication Date: April 20, 2000 Created: September 11, 1997 12:21 PM 824 Application

More information

860 Purchase Order Change Request (Buyer Initiated) X12 Version Version: 2.0

860 Purchase Order Change Request (Buyer Initiated) X12 Version Version: 2.0 860 Purchase Order Change Request (Buyer Initiated) X12 Version 4010 Version: 2.0 Author: Advance Auto Parts Company: Advance Auto Parts Publication: 02/08/2017 1/26/2017 Purchase Order Change Request

More information

Remittance Advice

Remittance Advice 2.2 820 Remittance Advice INFORMATION TMM REQUIRES FROM TRADING PARTNER SCOPE THIS INFORMATION INCLUDES START-UP INFORMATION SPECIFIC TO TRADING PARTNER. APPROACH THE FOLLOWING INFORMATION WILL BE REQUIRED

More information

824 Application Advice

824 Application Advice 824 Application Advice Functional Group ID=AG Introduction: This Draft Standard for Trial Use contains the format and establishes the data contents of the Application Advice Transaction Set (824) for use

More information

Inbound ANSI X Version 04010

Inbound ANSI X Version 04010 Inbound ANSI X12 850 Version 04010 For CLP License Ordering Version: ANSI X12 850 4010 Author: Adobe EDI Modified: 06/09/2010 CLP_X12_ANSI8504010_060910.ecs 1 For internal use only 850 Purchase Order Functional

More information

Inbound X Version 04010

Inbound X Version 04010 Inbound X12 850 Version 04010 For Value Incentive Plan (VIP) License Ordering Version: ANSI ASC X12 850 4010 Author: Adobe EDI Company: Adobe Systems Inc Modified: 8/31/2015 850 Purchase Order Functional

More information

IMPLEMENTATION GUIDELINES FOR ANSI ASC X12 EDI CONVENTIONS RAW STEEL ORDER STATUS REPORT (870) TRANSACTION SET

IMPLEMENTATION GUIDELINES FOR ANSI ASC X12 EDI CONVENTIONS RAW STEEL ORDER STATUS REPORT (870) TRANSACTION SET IMPLEMENTATION GUIDELINES FOR ANSI ASC X12 EDI CONVENTIONS RAW STEEL ORDER STATUS REPORT (870) TRANSACTION SET FCA US INFORMATION & COMMUNICATION TECHNOLOGY MANAGEMENT ANSI ASC X12 VERSION/RELEASE 003040

More information

940 Warehouse Shipping Order

940 Warehouse Shipping Order 940 Warehouse Shipping Order X12/V4030/940: 940 Warehouse Shipping Order Version: 1.0 Author: Abbott Nutrition ebusiness Company: Abbott Nutrition Created: 03/21/2012 Current: 03/21/2012 Table of Contents

More information

822 Account Analysis. Heading: Detail: Functional Group ID=AA. GISB Statement of Account

822 Account Analysis. Heading: Detail: Functional Group ID=AA. GISB Statement of Account 822 Account Analysis Functional Group ID=AA Heading: Pos. Seg. Req. Loop Notes and No. ID Name Des. Max.Use Repeat Comments 0100 ST Transaction Set Header M 1 0200 BGN Beginning Segment M 1 0300 DTM Date/Time

More information

Purchase Order Change Request - Buyer Initiated

Purchase Order Change Request - Buyer Initiated 860 Purchase Order Change Request - Buyer Initiated Functional Group= PC Purpose: This Draft Standard for Trial Use contains the format and establishes the data contents of the Purchase Order Change Request

More information

An example of a paper copy Planning Schedules with Release Capability and its ASC X12 interpretation can be found at the back of this guideline.

An example of a paper copy Planning Schedules with Release Capability and its ASC X12 interpretation can be found at the back of this guideline. Introduction This guideline provides a description and technical layout of the data segments used when creating 3M s EDI Planning Schedules with Release Capability (Forecast) (ASC X12 transaction set 830)

More information

875 - Grocery Products Purchase Order Author: DOT FOODS, INC. Publication: March 3, 2005

875 - Grocery Products Purchase Order Author: DOT FOODS, INC. Publication: March 3, 2005 875 - Grocery Products Purchase Order Author: DOT FOODS, INC. Publication: March 3, 2005 DOT FOODS, INC. Distributor 875 Page 1 875 Grocery Products Purchase Order Functional Group=OG This Draft Standard

More information

DOLLAR GENERAL CORPORATION Electronic Data Interchange. Remittance Advice 820 Carrier Mapping Guidelines. ANSI X12 Version 4010

DOLLAR GENERAL CORPORATION Electronic Data Interchange. Remittance Advice 820 Carrier Mapping Guidelines. ANSI X12 Version 4010 DOLLAR GENERAL CORPORATION Electronic Data Interchange Remittance Advice 820 Carrier Mapping Guidelines ANSI X12 Version 4010 Implementation Guideline 820 Version: 1-10/01/07 Page 1 Document Change Log

More information

Plex Systems IMPLEMENTATION GUIDELINES FOR ANSI X12 EDI CONVENTIONS. 824 TRANSACTION SET APPLICATION ADVICE Version Created November 11, 2015

Plex Systems IMPLEMENTATION GUIDELINES FOR ANSI X12 EDI CONVENTIONS. 824 TRANSACTION SET APPLICATION ADVICE Version Created November 11, 2015 Plex Systems IPLEENTATION GUIDELINES FOR ANSI X12 EDI CONVENTIONS 824 TRANSACTION SET APPLICATION ADVICE Version 004010 Created November 11, 2015 2 P a g e 824 Application Advice FUNCTIONAL GROUP=AG This

More information

JR Simplot Corporate 810 Invoice

JR Simplot Corporate 810 Invoice JR Simplot Corporate 810 Invoice X12/V4010/810: 810 Invoice Version: 1.0 Company: JR Simplot Company Modified: 3/2/2018 Notes: edi@simplot.com Table of Contents 810 Invoice.......................................................................................................................................

More information

816 Organizational Relationships

816 Organizational Relationships 816 Organizational Relationships Functional Group ID=OR Introduction: This Draft Standard for Trial Use contains the format and establishes the data contents of the Organizational Relationships Transaction

More information

NAPM RAIL INDUSTRY FORUM Application Advice IMPLEMENTATION GUIDELINE FOR EDI

NAPM RAIL INDUSTRY FORUM Application Advice IMPLEMENTATION GUIDELINE FOR EDI 824 Application Advice Functional Group=AG This Draft Standard for Trial Use contains the format and establishes the data contents of the Application Advice Transaction Set (824) for use within the context

More information

X12 Implementation. Guidelines. For. Outbound. Payment Order / Remittance Advice. (820o)

X12 Implementation. Guidelines. For. Outbound. Payment Order / Remittance Advice. (820o) X2 Implementation Guidelines For utbound Payment rder / Remittance Advice (820o) 820 Payment rder/remittance Advice Functional Group ID=RA Introduction: This Standard contains the format and establishes

More information

850 Purchase Order

850 Purchase Order 850 Purchase Order - 4010 Version: 1.0 Author: Land O' Lakes Inc. V4010 1 850 Purchase Order Functional Group=PO This Draft Standard for Trial Use contains the format and establishes the data contents

More information

567 Contract Completion Status

567 Contract Completion Status 567 Contract Completion Status Functional Group ID=D3 Introduction: This Draft Standard for Trial Use contains the format and establishes the data contents of the Contract Completion Status Transaction

More information

Invoice Specification EDI 810

Invoice Specification EDI 810 Invoice Specification EDI 80 This document is solely for the use of Logicbroker, Inc. personnel and its intended client. No part of it may be circulated, Quoted, or reproduced for distribution outside

More information

850 Purchase Order. Version: X12

850 Purchase Order. Version: X12 850 Purchase Order Version: 004010 X12 Company: DOT FOODS, INC. Publication: 5/18/2012 850 Purchase Order Functional Group= PO Purpose: This Draft Standard for Trial Use contains the format and establishes

More information

EDI GUIDELINES PAYMENT ORDER/REMITTANCE ADVICE 820 FUNCTIONAL ACKNOWLEGEMENT 997 VERSIONS 4010 FINANCIAL INSTITUTION VERSION

EDI GUIDELINES PAYMENT ORDER/REMITTANCE ADVICE 820 FUNCTIONAL ACKNOWLEGEMENT 997 VERSIONS 4010 FINANCIAL INSTITUTION VERSION EDI GUIDELINES PAYENT ORDER/REITTANCE ADVICE 820 FUNCTIONAL ACKNOWLEGEENT 997 VERSIONS 4010 FINANCIAL INSTITUTION VERSION T:\Internet arketing\deliverables\820 EFT Bank guidelines.doc Rev. 6/27/2007 9:58

More information

Orchard Supply Hardware Direct to Consumer 850 Purchase Order

Orchard Supply Hardware Direct to Consumer 850 Purchase Order Orchard Supply Hardware Direct to Consumer 850 Purchase Order X12/V4010/850: 850 Purchase Order Author: Orchard Supply Hardware Trading Partner: Created: May 25, 2011 Modified: June 9, 2011 Notes: ISA/GS

More information

3. When the transaction set is accepted with data content change, the corrected data MUST be provided.

3. When the transaction set is accepted with data content change, the corrected data MUST be provided. 824 Application Advice Functional Group ID=AG Introduction: This Draft Standard for Trial Use contains the format and establishes the data contents of the Application Advice Transaction Set (824) for use

More information

824 Application Advice

824 Application Advice 824 Application Advice Functional Group ID=AG Introduction: This Draft Standard for Trial Use contains the format and establishes the data contents of the Application Advice Transaction Set (824) for use

More information

521 Income or Asset Offset

521 Income or Asset Offset 521 Income or Asset Offset Functional Group ID=AO Introduction: This Draft Standard for Trial Use contains the format and establishes the data contents of the Income or Asset Offset Transaction Set (521)

More information

HACHETTE BOOK GROUP USA 850 Purchase Order VERSION 4010 IMPLEMENTATION GUIDE

HACHETTE BOOK GROUP USA 850 Purchase Order VERSION 4010 IMPLEMENTATION GUIDE HACHETTE BOOK GROUP USA 850 Purchase Order VERSION 400 IMPLEMENTATION GUIDE Purchase Order 850 Functional Group PO 400 This Draft Standard for Trial Use contains the format and establishes the data contents

More information

Introduction: Heading: Detail: Summary: Functional Group ID=TX

Introduction: Heading: Detail: Summary: Functional Group ID=TX 864 Text Message Functional Group ID=TX Introduction: This Draft Standard for Trial Use contains the format and establishes the data content of the Text Message Transaction Set (864) for use within the

More information

ANSI X (Advance Shipment Notification) Inbound (to Eclipse) Version 4010

ANSI X (Advance Shipment Notification) Inbound (to Eclipse) Version 4010 ANSI X12 856 (Advance Shipment Notification) Inbound (to Eclipse) Version 4010 Eclipse 856 4010 (Vendor) 1 10/12/2012 856 Ship Notice/Manifest Functional Group=SH Purpose: This Draft Standard for Trial

More information

810 Invoice Service Parts Version:

810 Invoice Service Parts Version: 810 Invoice Service Parts Version: 004010 CNH_810v4010_ServiceParts.ecs 1 Table of Contents 810 Invoice... 4 ISA Interchange Control Header... 7 GS Functional Group Header... 9 ST Transaction Set Header...

More information

832 Price/Sales Catalog

832 Price/Sales Catalog 832 Price/Sales Catalog Functional Group ID=SC Transaction Layout: Heading: ARM Pos. Seg. Req. Loop Notes and Required No. ID Name Des. Max.Use Repeat Comments Required 010 ST Transaction Set Header M

More information

846 RAPID Inventory Inquiry/Advice Standard

846 RAPID Inventory Inquiry/Advice Standard 846 RAPID Inventory Inquiry/Advice Standard Functional Group ID=IB Introduction: This Standard contains the format and establishes the data contents of the Inventory Inquiry/Advice Transaction Set (846)

More information

IMPLEMENTATION GUIDELINES FOR ANSI ASC X12 EDI CONVENTIONS MOPAR TIRE PROGRAM PRICE/SALES CATALOG (832) TRANSACTION SET

IMPLEMENTATION GUIDELINES FOR ANSI ASC X12 EDI CONVENTIONS MOPAR TIRE PROGRAM PRICE/SALES CATALOG (832) TRANSACTION SET IMPLEMENTATION GUIDELINES FOR ANSI ASC X12 EDI CONVENTIONS MOPAR TIRE PROGRAM PRICE/SALES CATALOG (832) TRANSACTION SET FCA US INFORMATION & COMMUNICATION TECHNOLOGY MANAGEMENT ANSI ASC X12 VERSION/RELEASE

More information

Karmax Heavy Stamping

Karmax Heavy Stamping Heavy Stamping Application Advice (824) ANSI X12 Standard Version 003010 IMPLEMENTATION GUIDE This guide has been produced by Heavy Stamping a division of Magna International Inc All rights reserved. 824.doc

More information

824 Application Advice

824 Application Advice 824 Application Advice Functional Group ID=AG Introduction: This Draft Standard for Trial Use contains the format and establishes the data contents of the Application Advice Transaction Set (824) for use

More information

855 Purchase Order Acknowledgment. United Natural Foods

855 Purchase Order Acknowledgment. United Natural Foods 855 Purchase Order Acknowledgment Company: United Natural Foods Table of Contents 855 Purchase Order Acknowledgment... 1 ST Transaction Set Header... 2 BAK Beginning Segment for Purchase Order Acknowledgment...

More information

850 Purchase Order X12/V4010/850: 850 Purchase Order Version: 1.0 Final Publication: 1/21/2009 Notes:

850 Purchase Order X12/V4010/850: 850 Purchase Order Version: 1.0 Final Publication: 1/21/2009 Notes: 850 Purchase Order X12/V4010/850: 850 Purchase Order Version: 1.0 Final Publication: 1/21/2009 Notes: Table of Contents 850 Purchase Order...1 ISA Interchange Control Header...3 GS Functional Group Header...5

More information

BWI Group. Supplier EDI Specification. Remittance Advice Message REMADV. EDIFACT REMADV D.99.B BWI Version 1.0

BWI Group. Supplier EDI Specification. Remittance Advice Message REMADV. EDIFACT REMADV D.99.B BWI Version 1.0 BWI Group Supplier EDI Specification Remittance Advice Message REMADV EDIFACT REMADV D.99.B BWI Version 1.0 Implementation Guideline BWI Group REMADV Version 1.0 / 06/23/2010 II.M01-1 CHANGE CONTROL Document

More information

DSW Shoe Warehouse 832 Price/Sales Catalog Vendor Direct

DSW Shoe Warehouse 832 Price/Sales Catalog Vendor Direct DSW Shoe Warehouse 832 Price/Sales Catalog Vendor Direct X12/V4010/832: 832 Price/Sales Catalog Version: 1.0 Final Author: Publication: Trading Partner: All Notes: Brand Technology Services Table of Contents

More information

870 Order Status Report

870 Order Status Report 870 Order Status Report Introduction: Functional Group ID=RS This Draft Standard for Trial Use contains the format and establishes the data contents of the Order Status Report Transaction Set (870) for

More information

Plex Systems IMPLEMENTATION GUIDELINES FOR ANSI X12 EDI CONVENTIONS. 830 TRANSACTION SET MATERIAL RELEASE Version Revised November 18, 2009

Plex Systems IMPLEMENTATION GUIDELINES FOR ANSI X12 EDI CONVENTIONS. 830 TRANSACTION SET MATERIAL RELEASE Version Revised November 18, 2009 Plex Systems IMPLEMENTATION GUIDELINES FOR ANSI X12 EDI CONVENTIONS 830 TRANSACTION SET MATERIAL RELEASE Version 004010 Revised November 18, 2009 2 P a g e 830 Material Release Functional Group ID=PS Introduction:

More information

Pos Id Segment Name Req Max Use Repeat Notes Usage 0100 ST Transaction Set Header M 1 Must use 0200 BGN Beginning Segment M 1 Must use

Pos Id Segment Name Req Max Use Repeat Notes Usage 0100 ST Transaction Set Header M 1 Must use 0200 BGN Beginning Segment M 1 Must use 824 Application Advice Functional Group= AG Purpose: This Draft Standard for Trial Use contains the format and establishes the data contents of the Application Advice Transaction Set (824) for use within

More information

865 Purchase Order Change Acknowledgment/Request - Seller Initiated

865 Purchase Order Change Acknowledgment/Request - Seller Initiated Changes 5/2011: SCH11 Schedule line identifier 865 Purchase Order Change Acknowledgment/Request - Seller Initiated Introduction: Functional Group ID=CA This standard provides for the format and establishes

More information

855 Purchase Order Acknowledgment

855 Purchase Order Acknowledgment 855 Purchase Order Acknowledgment X12/V4010/855: 855 Purchase Order Acknowledgment Version: 2.0 Final Author: Insight Direct USA, Inc. Modified: 01/17/2014 855 Purchase Order Acknowledgment Functional

More information

Electronic Commerce Customer Guide

Electronic Commerce Customer Guide Electronic Commerce 864 Transaction Set Electronic Data Interchange - Electronic Funds Transfer SBC Trading Partners Business Customers Value Added Networks Payment System Building Electronic Partnerships

More information

Implementation Guide to Payment and Remittance Message. EDI 820 Version Description: This transaction set can be an order to a

Implementation Guide to Payment and Remittance Message. EDI 820 Version Description: This transaction set can be an order to a Implementation Guide to Payment and Remittance Message EDI 820 Version 4010 Description: This transaction set can be an order to a financial institution to make a payment to a payee. It can also be a remittance

More information

IMPLEMENTATION GUIDELINES FOR ANSI ASC X12 EDI CONVENTIONS VEHICLE LOGISTICS VISTA ROUTING AND CARRIER INSTRUCTIONS (853) TRANSACTION SET

IMPLEMENTATION GUIDELINES FOR ANSI ASC X12 EDI CONVENTIONS VEHICLE LOGISTICS VISTA ROUTING AND CARRIER INSTRUCTIONS (853) TRANSACTION SET IMPLEMENTATION GUIDELINES FOR ANSI ASC X12 EDI CONVENTIONS VEHICLE LOGISTICS VISTA ROUTING AND CARRIER INSTRUCTIONS (853) TRANSACTION SET FCA US INFORMATION & COMMUNICATION TECHNOLOGY MANAGEMENT ANSI ASC

More information

850 - Purchase Order Author: DOT FOODS, INC. Publication: September 24, 2008

850 - Purchase Order Author: DOT FOODS, INC. Publication: September 24, 2008 850 - Purchase Order Author: DOT FOODS, INC. Publication: September 24, 2008 850 Purchase Order Functional Group=PO Purpose: This Draft Standard for Trial Use contains the format and establishes the data

More information

SYSCO only provide the customer address of a certain type of customers.

SYSCO only provide the customer address of a certain type of customers. 816 Organizational Relationships Functional Group ID=OR Introduction: This Draft Standard for Trial Use contains the format and establishes the data contents of the Organizational Relationships Transaction

More information

International Truck and Engine Corporation

International Truck and Engine Corporation International Truck and Engine Corporation EDI 870 -- Order Status Report VERSION: ANSI ASC X12 Version Release 3020 FINAL Publication Date: February 6, 2001 Trading Partner: Truck Marketing Created: January

More information

879 - Price Information

879 - Price Information 879 - Price Information Author: DOT FOODS, INC. Publication: September 24, 2008 879 Price Information Functional Group=QG Purpose: This Draft Standard for Trial Use contains the format and establishes

More information

HCHETTE BOOK GROUP USA 855 Purchase Order Acknowledgement VERSION 4010 IMPLEMENTATION GUIDE

HCHETTE BOOK GROUP USA 855 Purchase Order Acknowledgement VERSION 4010 IMPLEMENTATION GUIDE HCHETTE BOOK GROUP USA 855 Purchase Order Acknowledgement VERSION 4010 IMPLEMENTATION GUIDE 1 Purchase Order Acknowledgement 855 4010 Functional Group PR This Draft Standard for Trial Use contains the

More information

CVS/Caremark. Implementation Guide. 810 DSD Invoice. Version X

CVS/Caremark. Implementation Guide. 810 DSD Invoice. Version X CVS/Caremark Implementation Guide 810 DSD Invoice Version X12-4010 810 Mapping Specifications v4010 i Table of Contents 810 Invoice... 1 ISA Interchange Control Header... 2 GS Functional Group Header...

More information

ANSI X (Purchase Order) Inbound (to Eclipse) Version 4010

ANSI X (Purchase Order) Inbound (to Eclipse) Version 4010 ANSI X12 850 (Purchase Order) Inbound (to Eclipse) Version 4010 Eclipse 850 4010 (Customer) 1 10/11/2012 850 Purchase Order Functional Group=PO Purpose: This Draft Standard for Trial Use contains the format

More information

Oshkosh 860 Purchase Order Change Request - Buyer Initiated

Oshkosh 860 Purchase Order Change Request - Buyer Initiated Oshkosh 860 Purchase Order Change Request - Buyer Initiated AIAG X12/V4010/860: 860 Purchase Order Change Request - Buyer Initiated Version: 1.0 Final Company: Oshkosh Corporation Publication: 11/13/2015

More information

810 Invoice. Version: 1.0 Final. X12/V4010/810: 810 Invoice. Company: Baker & Taylor Modified: 10/26/2010 Notes:

810 Invoice. Version: 1.0 Final. X12/V4010/810: 810 Invoice. Company: Baker & Taylor Modified: 10/26/2010 Notes: 810 Invoice X12/V4010/810: 810 Invoice Version: 1.0 Final Author: Baker & Taylor Company: Baker & Taylor Modified: 10/26/2010 Notes: Table of Contents 810 Invoice... 1 ISA Interchange Control Header...

More information

830W (R1) War Material Requirements 830 Planning Schedule with Release Capability

830W (R1) War Material Requirements 830 Planning Schedule with Release Capability 830 Planning Schedule with Release Capability Introduction: Functional Group ID=PS This Draft Standard for Trial Use contains the format and establishes the data contents of the Planning Schedule with

More information

Product Transfer and Resale Report - 867

Product Transfer and Resale Report - 867 867 Product Transfer and Resale Report - 4010 Version: 1.0 Author: Land O' Lakes, Inc. V4010 1 867 Product Transfer and Resale Report Functional Group=PT This Draft Standard for Trial Use contains the

More information

830 Planning Schedule with Release Capability

830 Planning Schedule with Release Capability 830 Planning Schedule with Release Capability Introduction: Functional Group ID=PS This Draft Standard for Trial Use contains the format and establishes the data contents of the Planning Schedule with

More information

An example of a routing guide and its ASC X12 interpretation can be found at the back of this guideline.

An example of a routing guide and its ASC X12 interpretation can be found at the back of this guideline. Introduction This guideline provides a description and technical layout of the data segments recommended for use by a carrier when sending EDI loading and/or routing guides (ASC X12 transaction set 217).

More information

LOOP ID - PO PO1 Baseline Item Data M 1 N2/ REF Reference Identification O >1

LOOP ID - PO PO1 Baseline Item Data M 1 N2/ REF Reference Identification O >1 850 Purchase Order Functional Group=PO This Draft Standard for Trial Use contains the format and establishes the data contents of the Purchase Order Transaction Set (850) for use within the context of

More information

EDI Specifications Guide. 855 Supplier Purchase Order Acknowledgement. Last Update May 2016

EDI Specifications Guide. 855 Supplier Purchase Order Acknowledgement. Last Update May 2016 855 Supplier Purchase Order Acknowledgement Last Update May 2016 855 Purchase Order Acknowledgment- Functional Group=PR VER. 4010 FISHER SCIENTIFIC This Standard contains the format and establishes the

More information

846 Inventory Inquiry/Advice

846 Inventory Inquiry/Advice 846 Inventory Inquiry/Advice X12/V5010/846: 846 Inventory Inquiry/Advice Company: Contact: GovX.com integrations@govx.com 846 Inventory Inquiry/Advice Functional Group=IB Purpose: This X12 Transaction

More information

JR Simplot Food Group Grocery Products Purchase Order. UCS/V4010/875: 875 Grocery Products Purchase Order Version: 1.0

JR Simplot Food Group Grocery Products Purchase Order. UCS/V4010/875: 875 Grocery Products Purchase Order Version: 1.0 JR Simplot Food Group - 875 Grocery Products Purchase Order UCS/V4010/875: 875 Grocery Products Purchase Order Version: 1.0 Company: JR Simplot Company Modified: 9/4/2018 Table of Contents 875 Grocery

More information

867 Bill Back itradenetwork OMS

867 Bill Back itradenetwork OMS 867 Bill Back itradenetwork OMS X12/V4010/867: 867 Product Transfer and Resale Report Version: 1.3 Final Company: itradenetwork Publication: 12/23/2013 Trading Partner: Current: 4/3/2015 Table of Contents

More information

GovX Purchase Order. X12/V5010/850: 850 Purchase Order

GovX Purchase Order. X12/V5010/850: 850 Purchase Order 850 Purchase Order X12/V5010/850: 850 Purchase Order Company: GovX.com 1 4/12/2013 Purchase Order - 850 10/16/2015 Added TD5 segment 1/7/2016 9/19/2018 Added new value UP in PO106 Added TD512 segment Table

More information

CP EDI 824 Guidelines Version CP EDI 824 Guidelines (Version 4010)

CP EDI 824 Guidelines Version CP EDI 824 Guidelines (Version 4010) CP EDI 824 Guidelines (Version 4010) CP EDI 824 Guidelines 1 November, 2018 824 Application Advice Introduction: CP EDI 824 Guidelines Version 4010 Functional Group ID=AG This X12 Transaction Set contains

More information

Patrick Morin. EDI Implementation Guide for Purchase Order (850) Version

Patrick Morin. EDI Implementation Guide for Purchase Order (850) Version Patrick Morin EDI Implementation Guide for Purchase Order (850) Version 2015-04-21 Contents Contents 2 Introduction 4 Revisions 5 Contacts 6 Patrick Morin... 6 Alligacom Inc.... 6 General Information 7

More information

862 Shipping Schedule

862 Shipping Schedule AN AIAG IMPLEMENTATION GUIDELINE VERSION 004 RELEASE 010 862 862 Shipping Schedule PREFACE This is the AIAG s recommended usage for the 862 - Shipping Schedule for ASC X12 version release 004010. Prior

More information

GovX Purchase Order. X12/V5010/850: 850 Purchase Order

GovX Purchase Order. X12/V5010/850: 850 Purchase Order 850 Purchase Order X12/V5010/850: 850 Purchase Order Company: GovX.com 1 4/12/2013 Purchase Order - 850 10/16/2015 Added TD5 segment 1/7/2016 Added new value UP in PO106 2 Table of Contents 850 Purchase

More information

860 Purchase Order Change v.4 (4010) Hubbell to Supplier Outbound Transaction

860 Purchase Order Change v.4 (4010) Hubbell to Supplier Outbound Transaction 860 Purchase Order Change v.4 (4010) Hubbell to Supplier Outbound Transaction Functional Group ID=PC Introduction: This Draft Standard for Trial Use contains the format and establishes the data contents

More information

EDIFACT Implementation. Guidelines. For. Outbound Delivery Just In Time Message (DELJIT)

EDIFACT Implementation. Guidelines. For. Outbound Delivery Just In Time Message (DELJIT) EDIFACT Implementation Guidelines For Outbound Delivery Just In Time Message (DELJIT) FDODELJ (D.98B) 1 August 2, 2001 DELJIT Delivery Just in Time Message Introduction: A message provides the ability

More information

Transaction Set 849 Response to Product Transfer Account Adjustment

Transaction Set 849 Response to Product Transfer Account Adjustment The Global Network for B2B Integration in High Tech Industries Transaction Set 849 Response to Product Transfer Account Adjustment Functional Group ID = CF X12 Version 004 Release 010 December 2002 2 Revision

More information

EDI Specifications Guide. 856 Customer Advance Ship Notice

EDI Specifications Guide. 856 Customer Advance Ship Notice 856 Customer Advance Ship Notice 856 Ship Notice/Manifest - Functional Group=SH VER. 4010 FISHER SCIENTIFIC This Standard contains the format and establishes the data contents of the Fisher Scientific

More information

814 General Request, Response or Confirmation

814 General Request, Response or Confirmation 814 General Request, Response or Confirmation Introduction: Functional Group ID=GE This Draft Standard for Trial Use contains the format and establishes the data contents of the General Request, Response

More information

860 Purchase Order Change Request - Buyer Initiated

860 Purchase Order Change Request - Buyer Initiated 860 Purchase Order Change Request - Buyer Initiated X12/V4010/860 :860 Purchase Order Change Request - Buyer Initiated Company: General Mills Modified: 1/11/2018 Notes: Table of Contents 860 Purchase Order

More information

EDI Implementation Guide Version

EDI Implementation Guide Version EDI Implementation Guide Version 004010 867 Product Transfer and Resale Report Verizon Implementation Guide 1 04/12/17 867 Product Transfer and Resale Report Functional Group ID=PT Introduction: This Draft

More information

865 Purchase Order Change Acknowledgment/Request - Seller Initiated

865 Purchase Order Change Acknowledgment/Request - Seller Initiated 865 Purchase Order Change Acknowledgment/Request - Seller Initiated X12/V4030/865 : 865 Purchase Order Change Acknowledgment/Request - Seller Initiated Version: 1.2 Draft Author: Alain Bérubé Company:

More information

RCI 855 Purchase Order Acknowledgment

RCI 855 Purchase Order Acknowledgment RCI 855 Purchase Order Acknowledgment X12/V4030/855 : 855 Purchase Order Acknowledgment Version: 1.0 Draft Company: DiCentral Publication: 8/18/2017 Notes Table of Contents 855 Purchase Order Acknowledgment.....................................................................................................

More information

EDI 850 Version 4010 ANSI X12 Purchase Order Specifications

EDI 850 Version 4010 ANSI X12 Purchase Order Specifications EDI 850 Version 4010 ANSI X12 Purchase Order Specifications Coupa Software, Inc. 1855 S. Grant St. 5 th Floor San Mateo, CA 94402 www.coupa.com Contents Purchase Order Details 3 Introduction 3 File Format

More information

850 Purchase Order - v4030

850 Purchase Order - v4030 850 Purchase Order - v4030 X12/V4030/850 Version: 1.0 Final Author: Inovis Publication: April 1, 2008 PepBoys850_4030_FINAL.ecs 1 Ver 1.0 Revision History Date Version Revision Approved By April 1, 2008

More information

BRP Inc. ELECTRONIC DATA INTERCHANGE (EDI) IMPLEMENTATION GUIDE 865 VERSION 4010 FROM SUPPLIER. Document version 1.5

BRP Inc. ELECTRONIC DATA INTERCHANGE (EDI) IMPLEMENTATION GUIDE 865 VERSION 4010 FROM SUPPLIER. Document version 1.5 BRP Inc. ELECTRONIC DATA INTERCHANGE (EDI) IMPLEMENTATION GUIDE 865 VERSION 4010 FROM SUPPLIER Document version 1.5 The following guide is intended to facilitate the user in implementing Electronic Data

More information

EDI Implementation Guide Version

EDI Implementation Guide Version EDI Implementation Guide Version 004010 861 Receiving Advice/Acceptance Certificate Verizon Implementation Guide 1 04/20/17 861 Receiving Advice/Acceptance Certificate Introduction: Functional Group ID=RC

More information

855 Purchase Order Acknowledgment

855 Purchase Order Acknowledgment Changes 9/2009: PO1 Segment is mandatory PO1 segment 02 position is mandatory Changes 5/2011: SCH11 Schedule line identifier 855 Purchase Order Acknowledgment Functional Group ID=PR Introduction: This

More information

860 Purchase Order Change Request - Buyer Initiated

860 Purchase Order Change Request - Buyer Initiated 860 Purchase Order Change Request - Buyer Initiated X12/V4010/860 :860 Purchase Order Change Request - Buyer Initiated Company: General Mills Modified: 1/7/2016 Notes: Table of Contents 860 Purchase Order

More information

865 Purchase Order Change Acknowledgment/Request - Seller Initiated

865 Purchase Order Change Acknowledgment/Request - Seller Initiated Purchase Order Change Acknowledgment/Request - Seller Initiated X12/V4010/ : Purchase Order Change Acknowledgment/Request - Seller Initiated Version: 1.1 Final Author: Advance Auto Parts Company: Advance

More information

850 Purchase Order. X12/V4010/850: 850 Purchase Order

850 Purchase Order. X12/V4010/850: 850 Purchase Order 850 Purchase Order X12/V4010/850: 850 Purchase Order Company: General Mills Modified: 1/11/2018 Notes: Production Orders for copack and warehousing partners. Table of Contents 850 Purchase Order............................................................................................................................

More information

ANSI X12 version Receiving Advice/ Acceptance Certificate

ANSI X12 version Receiving Advice/ Acceptance Certificate ANSI X12 version 4010 861 Receiving Advice/ Acceptance Certificate VERSION: 1.0 FINAL Author: Superior Essex Publication Date: 8/22/00 Trading Partner: All Partners 861 All Partners 4010 Inbound.rtf 1

More information

850 Purchase Order. X12/V4010/850 : 850 Purchase Order Version: 2.0 Final

850 Purchase Order. X12/V4010/850 : 850 Purchase Order Version: 2.0 Final 850 Purchase Order X12/V4010/850 : 850 Purchase Order Version: 2.0 Final Author: D&H Distributors Company: D&H Distributors Publication: 8/15/2016 Trading Partner: Modified: 8/12/2016 Notes EDI notes The

More information

850 Purchase Order X12 Version Version: 2.0

850 Purchase Order X12 Version Version: 2.0 850 Purchase Order X12 Version 4010 Version: 2.0 Author: Advance Auto Parts Company: Advance Auto Parts Publication: 12/03/2016 Revision History Date Version Description Author 1/15/2013 NA Original publication

More information

Functional Acknowledgment - 997

Functional Acknowledgment - 997 997 Functional Acknowledgment - 4010 Version: 1.0 Author: V4010 1 997 Functional Acknowledgment Functional Group=FA This Draft Standard for Trial Use contains the format and establishes the data contents

More information