PentaSAP PAYMENT ANSI ASC X12

Transcription

1 IMPLEMENTATION GUIDELINES FOR ANSII ASC X12 EDI CONVENTIONS PentaSAP PAYMENT ORDER/REMITTANCE ADVICE (820) TRANSACTION SET CHRYSLER INFORMATION & COMMUNICATION TECHNOLOGY MANAGEMENT 800 CHRYSLER DRIVE AUBURN HILLS, MI CIMS ANSI ASC X12 VERSION/RELEASE

2 820 Payment Order/Remittance Advice Introduction: Functional Group ID=RA This Draft Standard for Trial Use contains the format and establishes the data contents of the Payment Order/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 payment and send a remittance advice. This transaction set can be an order to a financial institution to make a payment to a payee. It can also be a remittance advice identifying the detail needed to perform cash application to the payee's accounts receivable system. The remittance advice can go directly from payer to payee, through a financial institution, or through a third party agent. Notes: Chrysler will use this transaction set to only transmit payment detail remittance information. This transaction is not for Electronic Funds Transfer. Notes about the 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 Chrysler requirements. 4. The data segment sequence tables 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. Comments that relate to an element or code value will now appear underneath, where previously the comments would appear to the right. History of Change: 06/2004: Add CUR at position 1/040 for GAP Foreign Funds implementation 11/2007: Transition to Chrysler LLC with removal of references to Daimler 07/14/2010: Name change from Chrysler LLC to Chrysler Updated Address 01/11/2012: TRN02 Size changed from1/7 to 1/15 N104 Size changed from 5/7 to 2/17 08/20/2012 V/R Chrysler

3 REF01 Removed Purchase Order Suffix (PS) from reference number qualifier REF01 Added Plant (PE) to reference number qualifier IT104 reduced to a maximum of 2 digits to the right of the decimal point SLN04 reduced to a maximum of 2 digits to the right of the decimal point SLN06 reduced to a maximum of 2 digits to the right of the decimal point 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 BPR Beginning Segment for Payment M M 1 Order/Remittance Advice NTE Note/Special Instruction O > TRN Trace O 1 c CUR Currency O 1 c2 050 REF Reference Numbers O Not > DTM Date/Time/Period O >1 LOOP ID - N1 > N1 Name O 1 c3 080 N2 Additional Name Information O Not >1 090 N3 Address Information O Not >1 100 N4 Geographic Location O Not REF Reference Numbers O Not > PER Administrative Communications Contact O >1 Detail: Page Pos. Seg. Base User Loop Notes and No. No. ID Name Guide Status Max.Use Repeat Comments LOOP ID - ENT > ENT Entity O 1 c4 LOOP ID - N1 >1 020 N1 Name O Not 1 c5 030 N2 Additional Name Information O Not >1 040 N3 Address Information O Not >1 050 N4 Geographic Location O Not REF Reference Numbers O Not >1 070 PER Administrative Communications Contact O Not >1 LOOP ID - ADX > ADX Adjustment O 1 c NTE Note/Special Instruction O >1 100 PER Administrative Communications Contact O Not >1 LOOP ID - REF > REF Reference Numbers O DTM Date/Time/Period O >1 08/20/2012 V/R Chrysler

4 LOOP ID - IT1 > IT1 Baseline Item Data (Invoice) O 1 c7 LOOP ID - REF > REF Reference Numbers O DTM Date/Time/Period O 1 LOOP ID - ITA > ITA Allowance, Charge or Service O TXI Tax Information O Not >1 LOOP ID - SLN > SLN Subline Item Detail O 1 LOOP ID - REF >1 145 REF Reference Numbers O Not DTM Date/Time/Period O Not >1 LOOP ID - ITA >1 147 ITA Allowance, Charge or Service O Not TXI Tax Information O Not >1 LOOP ID - RMR > RMR Remittance Advice Accounts Receivable Open Item Reference O 1 c8 160 NTE Note/Special Instruction O Not >1 170 REF Reference Numbers O Not > DTM Date/Time/Period O >1 LOOP ID - IT1 > IT1 Baseline Item Data (Invoice) O 1 c9 LOOP ID - REF > REF Reference Numbers O DTM Date/Time/Period O 1 LOOP ID - ITA > ITA Allowance, Charge or Service O TXI Tax Information O Not >1 LOOP ID - SLN >1 204 SLN Subline Item Detail O Not 1 LOOP ID - REF >1 205 REF Reference Numbers O Not DTM Date/Time/Period O Not >1 LOOP ID - ITA >1 207 ITA Allowance, Charge or Service O Not TXI Tax Information O Not >1 LOOP ID - ADX >1 210 ADX Adjustment O Not 1 c NTE Note/Special Instruction O Not >1 230 PER Administrative Communications Contact O Not >1 LOOP ID - REF >1 240 REF Reference Numbers O Not 1 08/20/2012 V/R Chrysler

5 250 DTM Date/Time/Period O Not >1 LOOP ID - IT1 >1 260 IT1 Baseline Item Data (Invoice) O Not 1 c11 LOOP ID - REF >1 270 REF Reference Numbers O Not DTM Date/Time/Period O Not 1 LOOP ID - ITA >1 272 ITA Allowance, Charge or Service O Not TXI Tax Information O Not >1 LOOP ID - SLN >1 274 SLN Subline Item Detail O Not 1 LOOP ID - REF >1 275 REF Reference Numbers O Not DTM Date/Time/Period O Not >1 LOOP ID - ITA >1 277 ITA Allowance, Charge or Service O Not TXI Tax Information O Not >1 LOOP ID - TXP >1 280 TXP Tax Payment O Not TXI Tax Information O Not >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 Transaction Set Comments 1. The TRN segment is used to uniquely identify a payment order/remittance advice. 2. The CUR segment does not initiate a foreign exchange transaction. 3. The N1 loop allows for name/address information for the payer and payee which would be utilized to address remittance(s) for delivery. 4. ENT09 may contain the payee's accounts receivable customer number. 5. Allowing the N1 segment to repeat in this area allows the paying entity within a payer and the paid entity within a payee to be identified (not the payer and payee). 6. This ADX adjustment loop contains adjustment information not related to items referenced by any RMR segment in this transaction (see Comment G). This ADX loop may contain adjustments of any other nature. 7. Loop IT1 within the ADX loop is the adjustment line item detail loop. 8. Loop RMR is for items being paid. 9. Loop IT1 within the RMR loop is the remittance line item detail loop. 10. Loop ADX within the RMR loop is the adjustment loop for the remittance detail in this payment. This adjustment loop can only contain adjustment information for the RMR loop. 11. Loop IT1 within the ADX loop is the adjustment line item detail loop. 08/20/2012 V/R Chrysler

6 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: 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). Comments: 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 Payment Order/Remittance Advice ST Transaction Set Control Number M AN 4/9 M Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set 08/20/2012 V/R Chrysler

7 Segment: BPR Beginning Segment for Payment Order/Remittance Advice Position: 020 Loop: Level: Heading Usage: Mandatory Max Use: 1 Purpose: (1) To indicate the beginning of a PaymentOrder/Remittance Advice Transaction Set and total payment amount or (2) to enable related transfer of funds and/or information from payer to payee to occur Syntax Notes: 1 If either BPR06 or BPR07 is present, then the other is required. 2 If BPR08 is present, then BPR09 is required. 3 If either BPR12 or BPR13 is present, then the other is required. 4 If BPR14 is present, then BPR15 is required. Semantic Notes: 1 BPR02 specifies the payment amount. 2 When using this transaction set to initiate a payment, BPR06 through BPR16 may be required, depending on the conventions of the specific financial channel being used. BPR06 and BPR07 relate to the originating depository financial institution (ODFI). 3 BPR12 and BPR13 relate to the receiving depository financial institution (RDFI). 4 BPR15 is the account number of the receiving company to be debited or credited with the payment order. 5 BPR17 is a code identifying the business reason for this payment. Comments: 1 BPR09 is the account of the company originating the payment. This account may be debited or credited depending on the type of payment order. Notes: Chrysler uses this segment to detail the type of remittance advice and method of payment. EXAMPLE: BPR*I* *C*PBC************ Data Element Summary Ref. Data Base User Des. Element Name Attributes Attributes BPR Transaction Handling Code M ID 1/1 M Code designating the action to be taken by all parties E Debit/Credit Advice with Remittance Detail I Remittance Information Only BPR Monetary Amount M R 1/15 M Monetary amount Total payment amount. BPR Credit/Debit Flag Code M ID 1/1 M Code indicating whether amount is a credit or debit C Credit Credit to receiver and debit to originator. D Debit 08/20/2012 V/R Chrysler

8 Debit to receiver and credit to originator. BPR Payment Method Code M ID 3/3 M Code used to designate the actual funds transfer method. NON PBC WRT ZZZ Non-Payment Data Pay By Check Wire Transfer Mutually Defined for Electronic Funds Transfer BPR Payment Format Code O ID 1/10 Not BPR (DFI) ID Number Qualifier X ID 2/2 Not BPR (DFI) Identification Number X AN 3/12 Not BPR Account Number Qualifier Code O ID 2/2 Not BPR Account Number X AN 1/35 Not BPR Originating Company Identifier O AN 10/10 Not BPR Originating Company Supplemental Code O AN 9/9 Not BPR (DFI) ID Number Qualifier X ID 2/2 Not BPR (DFI) Identification Number X AN 3/12 Not BPR Account Number Qualifier Code O ID 2/2 Not BPR Account Number X AN 1/35 Not BPR Effective Entry Date M DT 6/6 M Date the originating company intends for the transaction to be settled. Check issue date in YYMMDD format. BPR Business Function Code O ID 1/3 Not 08/20/2012 V/R Chrysler

9 Segment: NTE Note/Special Instruction Position: 030 Loop: Level: Heading Usage: Optional Max Use: >1 Purpose: To transmit information in a free-form format, if necessary, for comment or special instruction Syntax Notes: Semantic Notes: Comments: 1 The NTE segment permits free-form information/data which, under ANSI X12 standard implementations, is not machine processable. The use of the NTE segment should therefore be avoided, if at all possible, in an automated environment. Notes: To transmit information in a free form format, if necessary, for comments or special instructions. EXAMPLE: NTE*ZZZ*DEBIT BALANCE STATEMENT Data Element Summary Ref. Data Base User Des. Element Name Attributes Attributes NTE Note Reference Code M ID 3/3 M Code identifying the functional area or purpose for which the note applies ZZZ Mutually Defined NTE02 3 Free Form Message M AN 1/60 M Free-form text 08/20/2012 V/R Chrysler

10 Segment: TRN Trace Position: 035 Loop: Level: Heading Usage: Optional Max Use: 1 Purpose: To uniquely identify a transaction to an application Syntax Notes: Semantic Notes: 1 TRN02 provides unique identification for the transaction. 2 TRN03 identifies an organization. 3 TRN04 identifies a further subdivision within the organization. Comments: Notes: This segment is used to uniquely identify this transaction set and to reassociate payment and remittance that have been split. This number is unique within a sender/receiver relationship and is assigned by the originator's application. EXAMPLE: TRN*1*876547* Data Element Summary Ref. Data Base User Des. Element Name Attributes Attributes TRN Trace Type Code M ID 1/2 M Code identifying which transaction is being referenced 1 Current Transaction Trace Numbers TRN Reference Number M AN 1/30 M AN 1/15 Reference number or identification number as defined for a particular Transaction Set, or as specified by the Reference Number Qualifier. If a payment, the check number for this Remittance Advice; If a Debit Memo, the document effective date. TRN Originating Company Identifier M AN 10/10 M A unique identifier designating the company initiating the funds transfer instructions. The first character is one-digit ANSI identification code designation (ICD) followed by the nine-digit identification number which may be an IRS employer identification number (EIN), data universal numbering system (DUNS), or a user assigned number; the ICD for an EIN is 1, DUNS is 3, user assigned number is 9 Chrysler use: " " TRN Reference Number O AN 1/30 Not 08/20/2012 V/R Chrysler

11 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 See Figures Appendix for examples detailing the use of the CUR segment. Notes: Beginning with the implementation of GAP Foreign Funds, this segment will now be mandatory. Suppliers should now submit invoices with appropriate currency code as required by their purchase orders. EXAMPLE: CUR*SU*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, a physical location, or an individual SU Supplier/Manufacturer CUR Currency Code M ID 3/3 M Code (Standard ISO) for country in whose currency the charges are specified This currency code will be the same as the currency code submitted on supplier PentaSAP Invoices (810). Note: the code list for this element is maintained by the United Nations Economic Commission for Europe. The entire code list for this element can be found at the website for the UN/ECE at Follow the path: - Trade Development - Committee for Trade, Industry and Enterprise Development - Trade Facilitation and E-Business - Recommendations 08/20/2012 V/R Chrysler

12 - #9 Alphabetic Code of the Representation of Currencies Additional Note: As with any website, changes to the United Nations website are possible. The path that should be followed to obtain the ISO Recommendation is subject to change without notice and may not be represented in this documentation. This path is provided to assist the trading partner. 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 X ID 3/3 Not CUR Date O DT 6/6 Not CUR Time O TM 4/6 Not CUR Date/Time Qualifier X ID 3/3 Not CUR Date O DT 6/6 Not CUR Time O TM 4/6 Not CUR Date/Time Qualifier X ID 3/3 Not CUR Date O DT 6/6 Not CUR Time O TM 4/6 Not CUR Date/Time Qualifier X ID 3/3 Not CUR Date O DT 6/6 Not CUR Time O TM 4/6 Not CUR Date/Time Qualifier X ID 3/3 Not CUR Date O DT 6/6 Not CUR Time O TM 4/6 Not 08/20/2012 V/R Chrysler

13 08/20/2012 V/R Chrysler

14 Segment: DTM Date/Time/Period Position: 060 Loop: Level: Heading Usage: Optional Max Use: >1 Purpose: To specify pertinent dates and times Syntax Notes: 1 At least one of DTM02 or DTM03 is required. Semantic Notes: Comments: Notes: Chrysler will use one segment in the Heading Area for transaction set create date. EXAMPLE: DTM*097*110226***20 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 097 Transaction Creation DTM Date M DT 6/6 M Date (YYMMDD) Transaction Set Create Date DTM Time X TM 4/6 Not DTM Time Code O ID 2/2 Not DTM Century O N0 2/2 The first two characters in the designation of the year (CCYY) The century for the date in DTM02. 08/20/2012 V/R Chrysler

15 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: Two N1 loops are used at the Heading level to identify the payer and payee of the remittance. EXAMPLES: N1*PE*ABC COMPANY*92*11478 N1*PR*CHRYSLER*92*04000 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, a physical location, or an individual PE Payee PR Payer N Name X AN 1/35 AN 1/30 Free-form name If N101 = "PE", the name of the supplier or manufacturer; If N101 = "PR", the customer name, "Chrysler". N Identification Code Qualifier M ID 1/2 M ID 2/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 M AN 2/17 M Code identifying a party or other code Chrysler use: If N101 = "PE", the Chrysler assigned supplier code; If N101 = "PR", "04000" if transaction originating from PentaSAP, use "04001" if transaction originating from Checkwriter System. 08/20/2012 V/R Chrysler

16 Segment: PER Administrative Communications Contact Position: 120 Loop: N1 Optional Level: Heading Usage: Optional Max Use: >1 Purpose: To identify a person or office to whom administrative communications should be directed Syntax Notes: 1 If either PER03 or PER04 is present, then the other is required. 2 If either PER05 or PER06 is present, then the other is required. Semantic Notes: Comments: Notes: This segment is used to convey the telephone number of Chrysler's Accounts Payable Department. EXAMPLE: PER*AP**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 AP Accounts Payable Department PER02 93 Name O AN 1/35 Not PER Communication Number Qualifier M ID 2/2 M Code identifying the type of communication number TE Telephone PER Communication Number M AN 1/25 M AN 1/10 Complete communications number including country or area code when applicable U.S.: " " Canada: " " PER Communication Number Qualifier X ID 2/2 Not PER Communication Number X AN 1/25 Not 08/20/2012 V/R Chrysler

17 Segment: ENT Entity Position: 010 Loop: ENT Optional Level: Detail Usage: Optional Max Use: 1 Purpose: To designate the entities which are parties to a transaction and specify a reference meaningful to those entities Syntax Notes: 1 If any of ENT02 ENT03 or ENT04 is present, then all are required. 2 If any of ENT05 ENT06 or ENT07 is present, then all are required. 3 If either ENT08 or ENT09 is present, then the other is required. Semantic Notes: 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 data to another master (e.g., an organization) which is comprised of one or more entities. Groupings are as follows: (1) Single/Single: Only ENT01 is necessary, because there is a single entity (the sending master) communicating with a single entity (the receiving master). (2) Single/Multiple: ENT05, ENT06, and ENT07 would be used to identify the entities within the receiving master. The sending master is a single entity, so no other data elements need be used. (3) Multiple/Single: ENT02, ENT03, and ENT04 would be used to identify the entities within the sending master. The receiving master is a single entity, so no other data elements need be used. (4) Multiple/Multiple: ENT02, ENT03, and ENT04 would be used to identify the entities within the sending master. ENT05, ENT06, and ENT07 would be used to identify the entities within the receiving master. This segment also allows for the transmission of a unique reference number that is meaningful between the entities. Notes: If any segments in the detail area are used, the ENT segment is mandatory to indicate a loop start. In a single/single entity relationship, this segment is used as a placeholder and only ENT01 is required. EXAMPLE: ENT*1 Data Element Summary Ref. Data Base User Des. Element Name Attributes Attributes ENT Assigned Number O N0 1/6 Number assigned for differentiation within a transaction set Chrysler use: "1". ENT02 98 Entity Identifier Code X ID 2/2 Not ENT03 66 Identification Code Qualifier X ID 1/2 Not 08/20/2012 V/R Chrysler

18 ENT04 67 Identification Code X AN 2/17 Not ENT05 98 Entity Identifier Code X ID 2/2 Not ENT06 66 Identification Code Qualifier X ID 1/2 Not ENT07 67 Identification Code X AN 2/17 Not ENT Reference Number Qualifier X ID 2/2 Not ENT Reference Number X AN 1/30 Not 08/20/2012 V/R Chrysler

19 Segment: ADX Adjustment Position: 080 Loop: ADX Optional Level: Detail Usage: Optional Max Use: 1 Purpose: To convey accounts-payable adjustment information for the purpose of cash application, including payer-generated debit/credit memos Syntax Notes: 1 If ADX04 is present, then ADX03 is required. Semantic Notes: Comments: 1 ADX01 specifies the amount of the adjustment and must be signed if negative. If positive, it reduces the payment amount. If negative, it increases the payment amount. 2 ADX02 specifies the reason for claiming the adjustment. 3 ADX03 and ADX04 specify the identification of the adjustment itself as provided by the payer. If ADX is subsequent to an RMR segment, then a payee reference may be used. Notes: This ADX loop contains adjustment information not related to items referenced by any RMR segment in this transaction. This ADX loop may contain adjustments of any other nature. ADX03 and ADX04 identify the primary document number for the remittance. EXAMPLE: ADX*11500*E2*DL* Data Element Summary Ref. Data Base User Des. Element Name Attributes Attributes ADX Monetary Amount M R 1/15 M Monetary amount This element will be signed if negative; If positive, payment amount is reduced; If negative, payment amount is increased. ADX Adjustment Reason Code M ID 2/2 M Code indicating reason for credit memo, or adjustment to invoice, credit memo, or payment. 01 Pricing Error 06 Quantity Contested (RDR) 72 Authorized Return (RMO) E2 Covered By Debit Memo ZZ Mutually Defined (Covered by Credit Memo) 08/20/2012 V/R Chrysler

20 ADX Reference Number Qualifier X ID 2/2 Code qualifying the Reference Number. CM DL ET Credit Memo Debit Memo Excess Transportation ADX Reference Number O AN 1/30 AN 1/15 Reference number or identification number as defined for a particular Transaction Set, or as specified by the Reference Number Qualifier. Value qualified by ADX03. If less than 15 characters, this value is right justified and zero filled; If original EDI value was 16 characters, left justified with rightmost character truncated. 08/20/2012 V/R Chrysler

21 Segment: NTE Note/Special Instruction Position: 090 Loop: ADX Optional Level: Detail Usage: Optional Max Use: >1 Purpose: To transmit information in a free-form format, if necessary, for comment or special instruction Syntax Notes: Semantic Notes: Comments: 1 The NTE segment permits free-form information/data which, under ANSI X12 standard implementations, is not machine processable. The use of the NTE segment should therefore be avoided, if at all possible, in an automated environment. Notes: To transmit information in a free form format, if necessary, for comments or special instructions. EXAMPLE: NTE*ZZZ*DEBIT BALANCE STATEMENT Data Element Summary Ref. Data Base User Des. Element Name Attributes Attributes NTE Note Reference Code O ID 3/3 Code identifying the functional area or purpose for which the note applies ZZZ Mutually Defined NTE02 3 Free Form Message M AN 1/60 M Free-form text 08/20/2012 V/R Chrysler

22 Segment: REF Reference Numbers Position: 110 Loop: REF Optional Level: Detail Usage: Optional Max Use: 1 Purpose: To specify identifying numbers. Syntax Notes: 1 At least one of REF02 or REF03 is required. Semantic Notes: Comments: Notes: This REF segment contains ancillary reference numbers relating to the preceding ADX segment. This segment is not intended to identify the primary document number. ADX03 and ADX04 are used for the primary document number. This REF segment is required to start the REF-DTM loop to allow for the use of the following DTM segment. EXAMPLE: REF*IV* Data Element Summary Ref. Data Base User Des. Element Name Attributes Attributes REF Reference Number Qualifier M ID 2/2 M Code qualifying the Reference Number. BM Bill of Lading Number CR Customer Reference Number IV Seller's Invoice Number PE Plant Number PK Packing List Number PM Part Number PO Purchase Order Number SI Shipper's Identifying Number for Shipment (SID) REF Reference Number M AN 1/30 M AN 1/15 Reference number or identification number as defined for a particular Transaction Set, or as specified by the Reference Number Qualifier. If less than 15 characters, this value is right justified and zero filled; If original EDI value was 16 characters, left justified with rightmost character truncated. If REF01 = 'PK', for Supplier Ship Direct (SSD) only: for location 03103, the MOPAR SSD number, if available. REF Description X AN 1/80 Not 08/20/2012 V/R Chrysler

23 Segment: DTM Date/Time/Period Position: 120 Loop: REF Optional Level: Detail Usage: Optional Max Use: >1 Purpose: To specify pertinent dates and times Syntax Notes: 1 At least one of DTM02 or DTM03 is required. Semantic Notes: Comments: Notes: The document date is in the first occurrence of the DTM. This is the date of the primary document specified in the previous ADX04 element. EXAMPLES: DTM*003*110116***20 DTM*011*110115***20 DTM*102*110105***20 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 003 Invoice 011 Shipped 102 Issue DTM Date M DT 6/6 M Date (YYMMDD) DTM Time X TM 4/6 Not DTM Time Code O ID 2/2 Not DTM Century O N0 2/2 The first two characters in the designation of the year (CCYY) The century for the date in DTM02. 08/20/2012 V/R Chrysler

24 Segment: IT1 Baseline Item Data (Invoice) Position: 130 Loop: IT1 Optional Level: Detail Usage: Optional Max Use: 1 Purpose: To specify the basic and most frequently used line item data for the invoice and related transactions Syntax Notes: 1 If IT106 is present, then IT107 is required. 2 If IT108 is present, then IT109 is required. 3 If IT110 is present, then IT111 is required. 4 If IT112 is present, then IT113 is required. 5 If IT114 is present, then IT115 is required. 6 If IT116 is present, then IT117 is required. 7 If IT118 is present, then IT119 is required. 8 If IT120 is present, then IT121 is required. 9 If IT122 is present, then IT123 is required. 10 If IT124 is present, then IT125 is required. Semantic Notes: 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 ID's. 2 IT106 through IT125 provides for ten (10) different product/service ID's for each item. For example: Case, Color, Drawing No., UPC No., ISBN No., Model No., SKU. Notes: Loop IT1 within the ADX loop is the adjustment line item detail loop. This segment identifies line items on the preceding ADX. EXAMPLE: IT1*1*1000*EA*1150 Data Element Summary Ref. Data Base User Des. Element Name Attributes Attributes IT Assigned Identification O AN 1/11 Alphanumeric characters assigned for differentiation within a transaction set Line number. IT Quantity Invoiced M R 1/10 M Number of units invoiced (supplier units) IT Unit or Basis for Measurement Code M ID 2/2 M Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken 08/20/2012 V/R Chrysler

25 IT Unit Price M R 1/14 M Price per unit of product, service, commodity, etc. The unit price with a maximum of 2 digits to the right of the decimal point. For Retroactive Price Adjustments, this will be the net price of the difference between the current price and previous price. IT Basis of Unit Price Code O ID 2/2 Not IT Product/Service ID Qualifier O ID 2/2 Not IT Product/Service ID X AN 1/30 Not IT Product/Service ID Qualifier O ID 2/2 Not IT Product/Service ID X AN 1/30 Not IT Product/Service ID Qualifier O ID 2/2 Not IT Product/Service ID X AN 1/30 Not IT Product/Service ID Qualifier O ID 2/2 Not IT Product/Service ID X AN 1/30 Not IT Product/Service ID Qualifier O ID 2/2 Not IT Product/Service ID X AN 1/30 Not IT Product/Service ID Qualifier O ID 2/2 Not IT Product/Service ID X AN 1/30 Not IT Product/Service ID Qualifier O ID 2/2 Not IT Product/Service ID X AN 1/30 Not IT Product/Service ID Qualifier O ID 2/2 Not IT Product/Service ID X AN 1/30 Not IT Product/Service ID Qualifier O ID 2/2 Not IT Product/Service ID X AN 1/30 Not 08/20/2012 V/R Chrysler

26 IT Product/Service ID Qualifier O ID 2/2 Not IT Product/Service ID X AN 1/30 Not 08/20/2012 V/R Chrysler

27 Segment: REF Reference Numbers Position: 140 Loop: REF Optional Level: Detail Usage: Optional Max Use: 1 Purpose: To specify identifying numbers. Syntax Notes: 1 At least one of REF02 or REF03 is required. Semantic Notes: Comments: Notes: This REF segment contains reference numbers relating to the preceding IT1 segment. EXAMPLES: REF*PO* REF*PM* AA REF*PE*04025 Data Element Summary Ref. Data Base User Des. Element Name Attributes Attributes REF Reference Number Qualifier M ID 2/2 M Code qualifying the Reference Number. IV Seller's Invoice Number PE Plant Number PM Part Number PO Purchase Order Number SI Shipper's Identifying Number for Shipment (SID) REF Reference Number M AN 1/30 M AN 1/15 Reference number or identification number as defined for a particular Transaction Set, or as specified by the Reference Number Qualifier. Value as qualified by REF01. REF Description X AN 1/80 Not 08/20/2012 V/R Chrysler

28 Segment: DTM Date/Time/Period Position: 141 Loop: REF Optional Level: Detail Usage: Optional Max Use: 1 Purpose: To specify pertinent dates and times Syntax Notes: 1 At least one of DTM02 or DTM03 is required. Semantic Notes: Comments: Notes: for the Shipped date that is associated with the original SID/Invoice that the retro activity is being applied to. EXAMPLE: DTM*011*110115***20 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 Shipped date. 011 Shipped DTM Date X DT 6/6 Date (YYMMDD) DTM Time X TM 4/6 Not DTM Time Code O ID 2/2 Not DTM Century O N0 2/2 The first two characters in the designation of the year (CCYY) The century for the date in DTM02. 08/20/2012 V/R Chrysler

29 Segment: ITA Allowance, Charge or Service Position: 142 Loop: ITA Optional Level: Detail Usage: Optional Max Use: 1 Purpose: To specify allowances, charges, or services Syntax Notes: 1 If ITA02 is present, then at least one of ITA03 ITA13 or ITA14 is required. 2 If ITA08 is present, then ITA09 is required. 3 If ITA10 is present, then ITA11 is required. 4 If ITA15 is present, then ITA02 is required. Semantic Notes: 1 ITA12 is the quantity of free goods. Comments: 1 If ITA01 = A-Allowance or C-Charge, then at least one of ITA06, ITA07, or ITA08 must be present. 2 ITA02 identifies the source of the code value in ITA03 or ITA15. 3 If ITA07 is present with either ITA06 or ITA08, then ITA07 takes precedence. 4 ITA13 is used to clarify the allowance, charge, or service. 5 ITA15 specifies the individual code list of the agency specified in ITA02. 6 ITA16 describes the relationship of ITA06, ITA07 or ITA09 to an associated segment. Notes: This segment is used to specify charges associated with clauses, cost codes, transportation and discounts. Either ITA05 or ITA14 is required. The Allowance or Charge Total Amount element (ITA07) is in the N2 format which calls for numeric data with 2 implied decimal points. If the charge or allowance is $100.00, the amount would be transmitted as "10000" (the decimal point is not transmitted). EXAMPLES: ITA*C***06*023A**54321******CLAUSE (PO clause) ITA*C***06***3500*******TTB (transportation) ITA*A***04***20000*******PAF (price reduction) Data Element Summary Ref. Data Base User Des. Element Name Attributes Attributes ITA Allowance or Charge Indicator M ID 1/1 M Code which indicates an allowance or charge for the service specified A Allowance C Charge ITA Agency Qualifier Code X ID 2/2 Not ITA Special Services Code X ID 2/10 Not ITA Allowance or Charge Method of Handling Code M ID 2/2 M Code indicating method of handling for an allowance or charge 08/20/2012 V/R Chrysler

30 If ITA01 = "A", use "04" = Credit Customer Account; If ITA01 = "C", use "06" = Charge to be Paid by Customer. 04 Credit Customer Account 06 Charge to be Paid by Customer ITA Allowance or Charge Number O AN 1/16 AN 1/4 The number assigned by a vendor referencing an allowance, promotion, deal or charge If the additional charge is based on a clause or cost code in the Chrysler Purchase Order and that clause or cost code is being billed to Chrysler, that clause number or cost code must appear here; otherwise, if the P.O. code is unknown, refer to Appendix G, "Chrysler Charge Code Conversion Table." ITA Allowance or Charge Rate O R 1/9 Not ITA Allowance or Charge Total Amount O N2 1/9 Must Use Total dollar amount for the allowance or charge The total amount of the charges or allowances that pertain to this shipment or part. ITA Allowance/Charge Percent Qualifier O ID 1/1 Not ITA Allowance or Charge Percent X R 1/6 Not ITA Allowance or Charge Quantity O R 1/10 Not ITA Unit or Basis for Measurement Code X ID 2/2 Not ITA Quantity O R 1/15 Not ITA Description X AN 1/80 A free-form description to clarify the related data elements and their content A Description of the charge or allowance. ITA Special Charge or Allowance Code X ID 3/3 Code identifying type of special charge or allowance PAF Price Deviation Show as a positive money amount in ITA07. TTB Transportation-Direct Billing ITA Source Subqualifier O AN 1/15 Not ITA Relationship Code O ID 1/1 Not 08/20/2012 V/R Chrysler

31 Segment: SLN Subline Item Detail Position: 144 Loop: SLN Optional Level: Detail Usage: Optional Max Use: 1 Purpose: To specify product subline detail item data Syntax Notes: 1 If SLN07 is present, then SLN06 is required. 2 If SLN08 is present, then SLN06 is required. 3 If SLN09 is present, then SLN10 is required. 4 If SLN11 is present, then SLN12 is required. 5 If SLN13 is present, then SLN14 is required. 6 If SLN15 is present, then SLN16 is required. 7 If SLN17 is present, then SLN18 is required. 8 If SLN19 is present, then SLN20 is required. 9 If SLN21 is present, then SLN22 is required. 10 If SLN23 is present, then SLN24 is required. 11 If SLN25 is present, then SLN26 is required. 12 If SLN27 is present, then SLN28 is required. Semantic Notes: 1 SLN01 is the identifying number for the subline item. 2 SLN02 is the identifying number for the subline level. The subline level is analogous to the level code used in a bill of materials. Comments: 1 See the Data Dictionary for a complete list of ID's. 2 SLN01 is related to (but not necessarily equivalent to) the baseline item number. Example: 1.1 or 1A might be used as a subline number to relate to baseline number 1. 3 SLN09 through SLN28 provide for ten (10) different product/service ID's for each item. For example: Case, Color, Drawing No., UPC No., ISBN No., Model No., SKU. Notes: For retroactive price adjustments caused by a price change, two SLN segments are used. The first SLN will contain the value "D" in the SLN03 to indicate that the price in the SLN06 is the old price. The SLN will contain the value "A" in the SLN03 to indicate that the price in the SLN06 is the new price. EXAMPLES: SLN*001**D*30*EA*8.12*LR SLN*002**A*30*EA*8.52*CP Data Element Summary Ref. Data Base User Des. Element Name Attributes Attributes SLN Assigned Identification M AN 1/11 M Alphanumeric characters assigned for differentiation within a transaction set SLN Assigned Identification O AN 1/11 Not SLN Configuration Code M ID 1/1 M 08/20/2012 V/R Chrysler

32 Code indicating the relationship of the subline item to the baseline item. A D Added Deleted SLN Quantity M R 1/15 M Numeric value of quantity The quantity with a maximum of 2 digits to the right of the decimal point. SLN Unit or Basis for Measurement Code M ID 2/2 M Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken SLN Unit Price X R 1/14 Price per unit of product, service, commodity, etc. The unit price with a maximum of 2 digits to the right of the decimal point. SLN Basis of Unit Price Code O ID 2/2 Code identifying the type of unit price for an item CP Current Price (Subject to Change) LR Previous Catalog Price SLN Relationship Code O ID 1/1 Not SLN Product/Service ID Qualifier O ID 2/2 Not SLN Product/Service ID X AN 1/30 Not SLN Product/Service ID Qualifier O ID 2/2 Not SLN Product/Service ID X AN 1/30 Not SLN Product/Service ID Qualifier O ID 2/2 Not SLN Product/Service ID X AN 1/30 Not SLN Product/Service ID Qualifier O ID 2/2 Not SLN Product/Service ID X AN 1/30 Not SLN Product/Service ID Qualifier O ID 2/2 Not SLN Product/Service ID X AN 1/30 Not SLN Product/Service ID Qualifier O ID 2/2 Not SLN Product/Service ID X AN 1/30 Not 08/20/2012 V/R Chrysler

33 SLN Product/Service ID Qualifier O ID 2/2 Not SLN Product/Service ID X AN 1/30 Not SLN Product/Service ID Qualifier O ID 2/2 Not SLN Product/Service ID X AN 1/30 Not SLN Product/Service ID Qualifier O ID 2/2 Not SLN Product/Service ID X AN 1/30 Not SLN Product/Service ID Qualifier O ID 2/2 Not SLN Product/Service ID X AN 1/30 Not 08/20/2012 V/R Chrysler

34 Segment: RMR Remittance Advice Accounts Receivable Open Item Reference Position: 150 Loop: RMR Optional Level: Detail Usage: Optional Max Use: 1 Purpose: To specify the accounts receivable open item(s) to be included in the cash application and to convey the appropriate detail Syntax Notes: 1 If RMR02 is present, then RMR01 is required. Semantic Notes: 1 If RMR03 is present, it specifies the open item(s) to be included in the cash application. 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, the item referenced in RMR02 is to be included in the cash application. 3 RMR04 is the amount paid. 4 RMR05 may be needed by some payees to distinguish between duplicate reference numbers. 5 RMR06 may be used to specify discount taken. Notes: This RMR segment contains invoice level information. The RMR loop is for open items being referenced or for payment on account. These are supplier-initiated documents or shipments for payment. Pay-As-Built (PAB) and Evaluated Receipts Settlement (ERS) payments are included, as they are Accounts Receivable open items to the supplier. EXAMPLE: RMR*SI* ** * *500 Data Element Summary Ref. Data Base User Des. Element Name Attributes Attributes RMR Reference Number Qualifier M ID 2/2 M Code qualifying the Reference Number. IV Seller's Invoice Number ERS SI Shipper's Identifying Number for Shipment (SID) RMR Reference Number M AN 1/30 M AN 1/15 Reference number or identification number as defined for a particular Transaction Set, or as specified by the Reference Number Qualifier. Value qualified in RMR01. If less than 15 characters, this value is right justified and zero filled; If original EDI value was 16 characters, left justified with rightmost character 08/20/2012 V/R Chrysler

35 truncated. RMR Payment Action Code O ID 2/2 Not RMR Monetary Amount O R 1/15 Monetary amount Total net invoice amount paid - must be signed if negative; If negative, it reduces the BPR payment amount; If positive, it increases the BPR payment amount. RMR Total Invoice or Credit/Debit Amount O R 1/15 Amount of Invoice (including charges, less allowances) before terms discount (if discount is applicable) or debit amount or credit amount of referenced items. The gross invoice amount from the original value of the document. RMR Amount of Discount Taken O R 1/15 Amount of discount. The discount amount for the invoice. This value is always positive and reduces the Total Invoice Amount (RMR05). 08/20/2012 V/R Chrysler

36 Segment: DTM Date/Time/Period Position: 180 Loop: RMR Optional Level: Detail Usage: Optional Max Use: >1 Purpose: To specify pertinent dates and times Syntax Notes: 1 At least one of DTM02 or DTM03 is required. Semantic Notes: Comments: Notes: This DTM segment is for invoice level information. The document date is in the first occurrence of the DTM. This is the date of the primary document specified in the previous RMR02 element. EXAMPLES: DTM*003*110116***20 DTM*102*110105***20 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 003 Invoice 011 Shipped (ERS) 102 Issue DTM Date X DT 6/6 Date (YYMMDD) The date qualified by DTM01 in YYMMDD format. DTM Time X TM 4/6 Not DTM Time Code O ID 2/2 Not DTM Century O N0 2/2 The first two characters in the designation of the year (CCYY) The century for the date in DTM02. 08/20/2012 V/R Chrysler

37 Segment: IT1 Baseline Item Data (Invoice) Position: 190 Loop: IT1 Optional Level: Detail Usage: Optional Max Use: 1 Purpose: To specify the basic and most frequently used line item data for the invoice and related transactions Syntax Notes: 1 If IT106 is present, then IT107 is required. 2 If IT108 is present, then IT109 is required. 3 If IT110 is present, then IT111 is required. 4 If IT112 is present, then IT113 is required. 5 If IT114 is present, then IT115 is required. 6 If IT116 is present, then IT117 is required. 7 If IT118 is present, then IT119 is required. 8 If IT120 is present, then IT121 is required. 9 If IT122 is present, then IT123 is required. 10 If IT124 is present, then IT125 is required. Semantic Notes: 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 ID's. 2 IT106 through IT125 provides for ten (10) different product/service ID's for each item. For example: Case, Color, Drawing No., UPC No., ISBN No., Model No., SKU. Notes: This IT1 segment is for invoice level information. Loop IT1 within the RMR loop is the remittance line item detail loop. This segment identifies each line item being paid. EXAMPLE: IT1*1*1000*EA*1150 Data Element Summary Ref. Data Base User Des. Element Name Attributes Attributes IT Assigned Identification O AN 1/11 Alphanumeric characters assigned for differentiation within a transaction set Invoice line number. IT Quantity Invoiced M R 1/10 M Number of units invoiced (supplier units) IT Unit or Basis for Measurement Code M ID 2/2 M Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken IT Unit Price M R 1/14 M Price per unit of product, service, commodity, etc. 08/20/2012 V/R Chrysler

38 The unit price as shown on the invoice with a maximum of 2 digits to the right of the decimal point. For ERS and PAB, the unit price as shown on the Purchase Order. IT Basis of Unit Price Code O ID 2/2 Not IT Product/Service ID Qualifier O ID 2/2 Not IT Product/Service ID X AN 1/30 Not IT Product/Service ID Qualifier O ID 2/2 Not IT Product/Service ID X AN 1/30 Not IT Product/Service ID Qualifier O ID 2/2 Not IT Product/Service ID X AN 1/30 Not IT Product/Service ID Qualifier O ID 2/2 Not IT Product/Service ID X AN 1/30 Not IT Product/Service ID Qualifier O ID 2/2 Not IT Product/Service ID X AN 1/30 Not IT Product/Service ID Qualifier O ID 2/2 Not IT Product/Service ID X AN 1/30 Not IT Product/Service ID Qualifier O ID 2/2 Not IT Product/Service ID X AN 1/30 Not IT Product/Service ID Qualifier O ID 2/2 Not IT Product/Service ID X AN 1/30 Not IT Product/Service ID Qualifier O ID 2/2 Not IT Product/Service ID X AN 1/30 Not IT Product/Service ID Qualifier O ID 2/2 Not 08/20/2012 V/R Chrysler

39 IT Product/Service ID X AN 1/30 Not 08/20/2012 V/R Chrysler

40 Segment: REF Reference Numbers Position: 200 Loop: REF Optional Level: Detail Usage: Optional Max Use: 1 Purpose: To specify identifying numbers. Syntax Notes: 1 At least one of REF02 or REF03 is required. Semantic Notes: Comments: Notes: This REF segment is for invoice line item detail level information. This REF segment contains reference numbers relating to the preceding IT1 segment in the RMR loop. EXAMPLES: REF*PO* REF*PM* AA REF*PE*04025 Data Element Summary Ref. Data Base User Des. Element Name Attributes Attributes REF Reference Number Qualifier M ID 2/2 M Code qualifying the Reference Number. BM Bill of Lading Number IX Item Number OI Original Invoice Number OQ Order Number PE Plant Number PK Packing List Number PM Part Number PO Purchase Order Number VT Motor Vehicle ID Number REF Reference Number M AN 1/30 M AN 1/15 Reference number or identification number as defined for a particular Transaction Set, or as specified by the Reference Number Qualifier. Chrysler use: M AN 01/15 Value qualified in REF01. If REF01 = "BM", "OI" or "PK" : If less than 15 characters, this value is right justified and zero filled; If original EDI value was 16 characters, left justified with rightmost character truncated. 08/20/2012 V/R Chrysler

41 If REF01 = 'PK', for Supplier Ship Direct (SSD) only: for location 3103, the MOPAR SSD number, if available. For Nissan Versa only: If REF01 = "OI", the original invoice number; If REF01 = "VT", the Full 17-digit VIN; If REF01 = "OQ", the Chrysler Vehicle Order Number; If REF01 = "IX", the End Item Code. REF Description X AN 1/80 Not 08/20/2012 V/R Chrysler

42 Segment: DTM Date/Time/Period Position: 201 Loop: REF Optional Level: Detail Usage: Optional Max Use: 1 Purpose: To specify pertinent dates and times Syntax Notes: 1 At least one of DTM02 or DTM03 is required. Semantic Notes: Comments: Notes: This DTM segment is for invoice line item detail level information. This DTM segment contains dates relating to the previous IT1 segment within the RMR loop. EXAMPLE: DTM*011*110115***20 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 DTM Date X DT 6/6 Date (YYMMDD) The date qualified by DTM01 in YYMMDD format. DTM Time X TM 4/6 Not DTM Time Code O ID 2/2 Not DTM Century O N0 2/2 The first two characters in the designation of the year (CCYY) The century for the date in DTM02. 08/20/2012 V/R Chrysler

43 Segment: ITA Allowance, Charge or Service Position: 202 Loop: ITA Optional Level: Detail Usage: Optional Max Use: 1 Purpose: To specify allowances, charges, or services Syntax Notes: 1 If ITA02 is present, then at least one of ITA03 ITA13 or ITA14 is required. 2 If ITA08 is present, then ITA09 is required. 3 If ITA10 is present, then ITA11 is required. 4 If ITA15 is present, then ITA02 is required. Semantic Notes: 1 ITA12 is the quantity of free goods. Comments: 1 If ITA01 = A-Allowance or C-Charge, then at least one of ITA06, ITA07, or ITA08 must be present. 2 ITA02 identifies the source of the code value in ITA03 or ITA15. 3 If ITA07 is present with either ITA06 or ITA08, then ITA07 takes precedence. 4 ITA13 is used to clarify the allowance, charge, or service. 5 ITA15 specifies the individual code list of the agency specified in ITA02. 6 ITA16 describes the relationship of ITA06, ITA07 or ITA09 to an associated segment. Notes: This segment is used to specify charges associated with clauses, cost codes, transportation, and price deviations. Either ITA05 or ITA14 is required. The Allowance or Charge Total Amount element (ITA07) is in the N2 format which calls for numeric data with 2 implied decimal points. If the charge or allowance is $100.00, the amount would be transmitted as "10000" (the decimal point is not transmitted). EXAMPLES: ITA*C***06*023A**54321******CLAUSE (PO clause) ITA*C***06***3500*******TTB (transportation) ITA*A***04***20000*******PAF (price reduction) Data Element Summary Ref. Data Base User Des. Element Name Attributes Attributes ITA Allowance or Charge Indicator M ID 1/1 M Code which indicates an allowance or charge for the service specified A Allowance C Charge ITA Agency Qualifier Code X ID 2/2 Not ITA Special Services Code X ID 2/10 Not ITA Allowance or Charge Method of Handling Code M ID 2/2 M Code indicating method of handling for an allowance or charge 08/20/2012 V/R Chrysler