dhl invoice data interchange (idi) specification v14 · complete idi customer request form that...

DHL Confidential & Proprietary

DHL Express

Confidential and Proprietary

DHL Invoice Data Interchange (IDI) Specification v14.01

Doc. Ref.: DHL IDI Implementation and User Guide v14.01

Version: 14.01

Status: Approved

Created by:

Thomas J. Lee, IV EDI IT Program Manager

Edited by: John Mihaiu EDI Administrator

Effective Date:

December 20, 2016


Confidentiality

The specifications, definitions and examples in this manual are to be used by the recipient for the sole purpose of programming to meet DHL Express requirements, and should not be altered or modified by the recipient.

This document contains confidential, proprietary information. No part of this document may be used, modified, reproduced, disseminated, or disclosed without the express written consent of DHL Express, Inc. DHL employees, third-party vendors, and others authorized to use this document shall only disclose this information internally to their coworkers, employees, or agents on a need-to-know basis and in keeping with DHL confidentiality requirements. The information in this document is subject to change without notice.

DHL EXPRESS SHALL NOT BE LIABLE FOR TECHNICAL OR EDITORIAL ERRORS OR OMISSIONS CONTAINED HEREIN NOR FOR INCIDENTAL OR CONSEQUENTIAL DAMAGES RESULTING FROM THE USE OF THIS INFORMATION.

© 2012 - 2011 DHL Express, Inc. All rights reserved.

Terms and Conditions

The requirements and specifications outlined in this manual are governed by DHL’s General Terms and Conditions, found on DHL’s website, www.DHL.com.


Contents

Chapter 1 ......................................................................................................................................... 1

Introduction .................................................................................................................................... 1

1.1 EDI Definition ........................................................................................................................... 1 1.2 Audience................................................................................................................................... 1

Chapter 2......................................................................................................................................... 2

EDI Guidelines ............................................................................................................................... 2

2.1 Requirements........................................................................................................................... 2 2.2 IDI Setup Process .................................................................................................................... 3 2.3 RDI Setup Process .................................................................................................................. 4 2.4 Payment of Charges ................................................................................................................ 5

Chapter 3......................................................................................................................................... 6

Invoice Data Configuration ........................................................................................................... 6

3.1 Electronic Invoice Format Summary ..................................................................................... 6 3.2 Billing Cycle ............................................................................................................................. 6 3.3 Processing Schedule .............................................................................................................. 7 3.6 Invoice Presentation ............................................................................................................... 7 3.7 Unique File Control Number................................................................................................... 7 3.8 Invoice Number Format .......................................................................................................... 8 3.9 Invoice Types ........................................................................................................................... 8 3.10 Invoice Adjustments - Debit/Credit Note Process.............................................................. 9

Chapter 4....................................................................................................................................... 10

Remittance Data Configuration.................................................................................................. 10

4.1 Electronic Remittance Format Summary ............................................................................ 10 4.2 Exception Report ................................................................................................................... 11

Chapter 5....................................................................................................................................... 12

Data Delivery Options ................................................................................................................. 12

5.1 Message Transport Options ................................................................................................. 12 5.2 File Notification...................................................................................................................... 13 5.3 Data Retention ....................................................................................................................... 13

Chapter 6....................................................................................................................................... 14

Electronic vs. Paper Invoicing ................................................................................................... 14

6.1 Electronic vs. Paper Invoicing ............................................................................................. 14 6.2 Past Due Invoices .................................................................................................................. 14 6.3 Proof of Delivery .................................................................................................................... 14

Chapter 7....................................................................................................................................... 15

EDI Compliance Testing ............................................................................................................. 15

7.1 IDI Testing .............................................................................................................................. 15 7.2 RDI Testing............................................................................................................................. 16

Chapter 8....................................................................................................................................... 17

Resources .................................................................................................................................... 17

2014-03-12 IDI v14.01 Page i

2016-12-20 IDI v14.01 DHL Confidential & Proprietary

Page ii

8.1 Who to Contact ...................................................................................................................... 17

Chapter 9....................................................................................................................................... 18

IDI DHL3 Format........................................................................................................................... 18

9.1 Data Structure ........................................................................................................................ 18

Chapter 10 ..................................................................................................................................... 30

IDI DHL6 Format........................................................................................................................... 30

10.0 Data Structure ...................................................................................................................... 30 10.2 Record Layout ..................................................................................................................... 31

Chapter 12 ..................................................................................................................................... 52

IDI 110DHL Format ...................................................................................................................... 52

Data Structure .............................................................................................................................. 52 110DHL Data Wrapping ............................................................................................................... 95

Chapter 13 ..................................................................................................................................... 96

RDI Proprietary Remittance Format .......................................................................................... 96

Data Structure .............................................................................................................................. 96 RDI Proprietary Format Sample File .......................................................................................... 97

Chapter 14 ..................................................................................................................................... 98

RDI 820 Remittance Format ........................................................................................................ 98

Data Structure .............................................................................................................................. 98 820 Sample File.......................................................................................................................... 133

Appendix A: Special Charge Codes for Shipment Level Charges ...................................... 134

Appendix B: Special Charge Codes for Customer Level Fees ............................................ 135

Appendix C: Service Level Codes .......................................................................................... 136

Appendix D: Rate Zones .......................................................................................................... 137

Appendix E: Adjustment Reason Codes................................................................................ 138

Terminology ............................................................................................................................... 139

Revision History ........................................................................................................................ 141

2016-12-20 IDI v14.01DHL Confidential & Proprietary

Page iii

This page was intentionally left blank

2016-12-20- IDI v14.01 DHL Confidential & Proprietary

Page 1 of 146

Chapter 1 Introduction

1.1 EDI Definition Electronic Data Interchange (EDI) is the computer-to-computer exchange of electronic business data in an agreed upon format. DHL provides the service of processing invoices via EDI at no cost to our customers because we understand the benefits that it affords them:

Improved business relationships because DHL electronic invoicing provides the flexibility that our customers need.

Reduced costs because electronic invoicing bypasses the manual and costly data entry process typically used to get invoice details into an accounts payable system.

Increased productivity

Increased accuracy

Increased profits

1.2 Audience This document is intended to serve as a guide to assist trading partners in receiving electronic invoice messages for US Outbound and US Inbound shipments in a standard X12 or a DHL proprietary flat file format. The primary audience of this document is intended to be the trading partner’s technical or EDI support staff.


Page 2 of 146

Chapter 2 EDI Guidelines

2.1 Requirements In addition to accepting DHL’s terms and conditions all customers must comply with the following requirements:

Remittance

Customers who receive electronic invoicing are required to submit an electronic remittance to DHL. DHL offers multiple electronic remittance options including an option that does not require customers to do any programming. See electronic remittance section for guidelines.

File Acknowledgements

Customers and freight payment companies who elect to receive an ANSI 110 format are required to return a 997 acknowledgement file back to DHL within 72 hours.

Programming Updates

Customers are responsible for making changes to support addenda or revisions within the time-frame defined by DHL. DHL will make best-effort attempts to provide advanced 60 days notice.

Appendix Updates

DHL charge codes (appendix A) will be updated the first Friday of March, June, September, and November and published on DHL’s public ftp mailbox (See Appendix A). Any charge codes that have changed and their effective date will be noted. DHL will make best-effort attempts to provide advanced 60 days notice. It is the customer’s responsibility to download additional copies, distribute internally, and modify programming as necessary.

Data Transport

DHL provides a variety of communications options. It is the customer’s responsibility to retrieve the files in a timely manner. Delays on retrieving files does not warrant delayed payment.

Failure to retrieve electronic invoicing files in a timely manner may result in a termination of EDI service.


Page 3 of 146

2.2 IDI Setup Process The IDI setup process consists of the following steps:

1. Review the IDI-RDI user implementation guide and decide on format, configuration options and details of file delivery.

2. Contact DHL’s EDI Analyst for consultation at [email protected].

3. Complete IDI customer request form that includes: trading partner

information, account numbers, file format, file delivery method, delivery schedule and selected configuration items. Customer must provide ISA/GS receiver id and receiver qualifier if the DHL110 X12 file format is selected. Return the signed IDI agreement.

4. A test Trading Partner ID is setup by DHL and an IDI test file containing

live shipment data is provided to the customer if there is activity on the account.

5. Customer completes configuration and programming to receive and

process IDI files, in accordance to the DHL IDI specifications, in their backend systems.

6. Once testing is successfully completed the customer emails the DHL EDI

Analyst and requests that the IDI account(s) be changed from a test to a production status. Customer to advise the EDI analyst of the ISA or GSA information to be used in the production file.

7. Refer to the “Getting Help” section within this guide if you have questions

during the implementation process.


Page 4 of 146

2.3 RDI Setup Process The RDI setup process consists of the following steps:

1. Review the RDI user implementation guide and decide on format, configuration options and details of file delivery.

2. For questions contact DHL’s Site Activation EDI Analyst at

[email protected].

3. Return request forms DHL’s Site Activation EDI Analyst.

4. A test Trading Partner ID is setup by DHL then a notification is sent out to customer to begin testing.

5. Customer completes configuration and programming to send RDI files in

accordance to the DHL RDI specifications in their backend systems.

6. Move RDI to production. The following items need to be completed before moving to production:

a. Testing is completed successfully with RDI

b. DHL provides an email notification to inform customer the RDI has passed the testing phase and will be moved to production.

7. Refer to the “Getting Help” section within this guide if you have questions during the implementation process.


Page 5 of 146

2.4 Payment of Charges

For purposes of this document, “Charges” means all applicable transportation and other charges, including but not limited to, all applicable accessorial charges, surcharges, additional handling charges, late payment fees, and collection costs including collection agency fees, legal fees, court costs, credit reports, and bad check collection fees, in accordance with applicable laws.

Notwithstanding any billing plan that is in effect or payment or billing option selected at the time of shipment, the shipper is ultimately liable for and agrees to pay all Charges, including in the event of insolvency, bankruptcy, or non-payment or refusal to pay by the consignee or third party.

All Charges must be ‘paid in full’ (per the invoice), in the lawful money of the United States of America.

Requests for invoice adjustments and/or disputes must be received separately from a payment. A partial payment against an invoice and/or waybill will not be considered as a dispute and will not be considered as a request for an invoice adjustment.

You must furnish, with your ‘payment in full’, the invoice number being paid and its corresponding dollar amount; or each invoice number being paid and each of its corresponding ‘fully paid’ dollar amounts. The payment amount must match the exact amount of the invoice and/or waybill total.

Upon notification from DHL, you must promptly provide sufficient payment documentation, at the ‘fully paid’ invoice and/or waybill level, for any payment that DHL is unable to properly apply against your account. If sufficient payment documentation is not received within 30 days of receipt of payment, DHL, in accordance with applicable laws, may treat the unidentified payment as a ‘payment in fact’ of charges owing to DHL, and apply it against the oldest invoices and/or waybills.


Page 6 of 146

Chapter 3 Invoice Data Configuration

3.1 Electronic Invoice Format Summary Select the format that best suits your internal processing needs. DHL does not customize or modify existing formats. These files are not sorted, preformatted, or sub-totaled. DHL6 format does not have a header record; however Excel templates are available on request.

DHL Express provides electronic invoices in the following formats.

Format DHL3 – This is a multiple record type format. Each record starts with a two-character record type indicator and is 80 bytes long.

Format DHL6 – This is single record comma-delimited format. Each record is 4013 bytes. A comma separates each field, making it easy to pull data into spreadsheet software.

Format 110DHL – This ANSI X12 format is widely used, making it a good choice for customers using multiple carriers and that want to receive invoice information from all in the same format. An EDI translator is required to process the X12-110 data files.

For more information about ASC X12 standards or to purchase an Implementation Guide, contact:

American National Standards Institute 1800 Diagonal Road, Suite 355

Alexandria, VA 22314 (703) 548-7005

http://www.x12.org/ or http://www.disa.org/

3.2 Billing Cycle DHL offers daily or weekly billing cycles for US Export freight and duty charges as well as import freight invoices. The shipment data contained in the electronic invoice files are controlled by the ship dates. DHL will attempt to provide invoice data for shipments tendered the prior day (assuming daily invoicing cycle), but there may be a delay. DHL pays import duty charges on behalf of our customer to ensure the prompt movement of our customer’s shipments through customs and therefore these charges are billed immediately upon charges being entered into DHL’s system. Customers should expect to receive inbound duty invoices outside of their normal billing cycle.


Page 7 of 146

3.3 Processing Schedule

IDI files will be available to retrieve the day after your assigned invoicing day. As an example, the weekly cycle ends on Wednesday so the file will be available on Thursday morning. Please work with your assigned DHL salesperson to define an invoicing schedule that is suitable for your company. The available schedules are below:

Daily

Weekly on Wednesday night

Please note that month end billing will occur on the last business day of the month. The weekly Wednesday night billing cycle will not be run during the last week and will be included in the month end billing process.

3.6 Invoice Presentation DHL provides several options on how to apply an invoice number to shipments. Select the option that fits best with your accounting and payment processing.

*Bill each unique shipment number under a unique invoice number (single shipment invoicing).

Bill all accounts to one single invoice for the opted billing period (parent-

child invoicing).

Bill one account to a single invoice number.

*DHL’s preferred electronic invoicing presentation format.

3.7 Unique File Control Number The Unique File Control Number is a number assigned to each trading partner beginning with ‘1’ and incrementing sequentially with subsequent invoice files.


Page 8 of 146

3.8 Invoice Number Format DHL’s invoice numbers will consist of 13 characters for the following invoice types:

Export invoice Export duty invoice Import Invoice Credit Invoice Debit Invoice

DHL’s invoice numbers will consist of 9 characters for the following type of invoice:

Import Duty Invoice

Below is an outline of the formats that will be used.

13 character format = AAAXX########

AAA = Origin IATA

X = Alpha numeric

# = Numeric

9 character format = D########

Examples:

Type of Invoice Regular Invoice Credit Note Debit Note

Export AAA0######### AAAN######### AAAD#########

Import AAAI######### AAAIN######## AAAID#########

Import Duty D######## AAAN######### AAAD#########

3.9 Invoice Types The descriptive content of the shipment data attached to each invoice will be represented in the ‘Invoice Type’ field in each format. Below are the categories and qualifiers that will be used.

Export Invoice/ Export Duty Invoice = UO

Credit Memo = CN

Debit Memo = DR

Import Invoice/ Import Duty Invoice = 21


Page 9 of 146

The Invoice Type field can be found in the following locations:

110DHL Format – B3A01 Element

DHL6 Format – Starting position 72

DHL3 Format – I1 segment, starting position 37

3.10 Invoice Adjustments - Debit/Credit Note Process The customer may submit an inquiry for any charge they believe is incorrect. If after the query is received, the amount is verified to be incorrect, DHL will process a credit note to remove the entire charge of the original invoice. A debit note will be issued for the new charge amount. For Customers who receive an electronic invoice, the credit/debit note(s) will be presented on a future electronic file separate from their normal invoice cycle.

Other Changes:

1. A new invoice number will be assigned to the credit/debit note (see example below)

2. The corrected charge may appear on a future electronic feed outside of the normal billing cycle.

3. Customer may reference the corrected (credit/debit note) back to the original shipment number from the initial invoice.

Example:

Regular Invoice Credit Note Debit Note Invoice Number AAA0123999777 AAANXXXXXXXXX AAADXXXXXXXXX Weight Charge USD 1339.27 USD -1339.27 USD 1339.27 Extra Charge “A” USD 10.00 USD -10.00 USD 10.00 Extra Charge “B” USD 20.00 USD -20.00 USD 20.00 Extra Charge “D” USD 30.00 USD -30.00 USD 30.00 Extra Charge “E” USD 40.00 USD -40.00 USD 40.00 Extra Charge “G” USD 50.00 USD -50.00 USD 50.00 Extra Charge “H” USD 60.00 USD -60.00 USD 600.00 Extra Charge “J” USD 80.00 USD -80.00 USD 800.00


Page 10 of 146

Chapter 4 Remittance Data Configuration

4.1 Electronic Remittance Format Summary Customers receiving electronic invoicing (IDI) are required to submit an electronic remittance to DHL. All remittance file formats must be submitted to DHL at the invoice level to ensure the accuracy of payment application.

RDI Formats - DHL customers can choose one of three remittance formats.

1. Excel RDI Translator Template Format – MS Excel Translator Template is provided by DHL. This format will allow information to be inserted into 5 columns with a maximum of 60,000 rows of data. Exceptions can be included using this method. Details of this process are outlined in section 4.3.

2. Format 820 – This ANSI X12 format is widely used, making it a good choice for customers using multiple carriers and that want to send remittance information to all in the same format. An EDI translator is required to generate the X12-820 data files.

3. DHL Proprietary Format – This is a multiple record type format. Each record starts with a single-character record type indicator and is 35 bytes long.

The remittance address for customers sending electronic remittance files is:

DHL Express (USA), Inc.

16592 Collections Center Dr.

Chicago, IL 60693

Required information on the check stub:

EDI MM/DD/YY Total Amount Paid for File

Example: EDI 01/30/05 $24353.17


Page 11 of 146

4.2 Exception Report

Instructions for submitting remittance information to DHL in the spreadsheet format:

1. Email [email protected] and request a copy of the spreadsheet template. This spreadsheet must be submitted each time you wish to make a payment. The amount paid and detailed in this file must match the total amount paid. Upon completion, email this spreadsheet to [email protected].

2. The Trading Partner and Company Name should be: "the name of your

company" unless you are a freight payer. If you are a freight payer, Trading Partner should be the name of your company and Company Name should be the name of the company on whose behalf you are paying. NOTE: These names will be assigned to you during testing.

3. The Check Number should be the check number of the payment or for

ACH / Wire payments, place the total amount of the payment here with no decimals (i.e. if the total of the paid amount is $1,000,000.00, type 100000000 in this field).

4. The shipment number field should indicate the specific invoice number to

which payment is to be applied.

5. The Amount Paid should be the specific amount you are paying against a specific Invoice. No credits can be listed in this column. The total of this column must match the total amount paid.

6. The Amount Adjusted should be the amount deducted from the original

amount billed at the specific Invoice level.

7. For any amount adjusted in column 'F,' please complete the Reason Adjusted column for the corresponding item. Refer to Appendix E for a listing of valid reason codes that should be used in this column.

8. This Excel spreadsheet must never be populated with more than 60,000

rows/line items.

9. Do not add, delete, or modify any columns.

10. DHL’s exception report natively supports Excel 2003 and Excel 2000 'xls' formats. If you are using Excel 2007, save the file in 2003 format.

Below is an example of the exception report. For copies of this template submit a request to [email protected].

Trading Partner

Company

Name

Check

Number Shipment

NumberAmount

PaidAmount

Adjusted

Reason Adjusted


Page 12 of 146

Chapter 5 Data Delivery Options

5.1 Message Transport Options DHL promotes communication methods and protocols that provide guaranteed delivery, enhanced security, and are resilient resulting in improved customer service and lower support cost. These protocols provide a level of security and reliability which allows DHL to effectively support your electronic business transactions. DHL recommends the use of secure protocols, such as Cyclone or secure FTP, to transfer sensitive data.

Communication Method

Guaranteed Delivery

Built in Resend Rules

Encryption Ease of Support

CommunicationCharges

EDINT AS2 Y Y Y Y N

FTP Mailbox Y* Y* Y* Y N

* Available upon request

DHL supports the following communication options to exchange IDI and RDI files:

EDIINT AS2 – an HTTPS based transport specification using SMIME encryption. DHL’s preferred communication method as it is easy to implement and very robust. The IETF working group has a webpage and information can be found at http://www.ietf.org/html.charters/OLD/ediint-charter.html.

DHL supports connectivity to your existing B2B application that is AS2 compliant. DHL has established communication with many 3rd party software solutions including: Cyclone Interchange/Central, WebMethods, Tibco BCRN, Microsoft Biztalk, and Templar.

DHL can provide customers with a B2B application that is AS2 compliant. The typical implementation can be done in 1-3 business days and requires no firewall changes. Ask your DHL EDI administrator for additional details.

FTP Mailbox – an ECPortal mailbox created and managed by DHL. The mailbox allows customers to systematically send, receive, or retrieve the messages on the internet using a web browser.

Work with your DHL EDI Setup Analyst if the communications options listed above do not meet your needs.


Page 13 of 146

5.2 File Notification

DHL can provide an email notification when a new IDI file has been created. This notification can be emailed to 10 email addresses and contains the following details:

Application Cycle Number Batch Control Number Trading Partner ID Remote ID Format Description Total number of Invoices, shipments and charges.

5.3 Data Retention DHL will retain invoicing data for a twenty-six week time period. During the twenty-six weeks after the original data was produced, the data can be provided to the customer again upon request.


Page 14 of 146

Chapter 6 Electronic vs. Paper Invoicing

6.1 Electronic vs. Paper Invoicing

The table below summarizes when customers will receive hardcopy invoices.

Invoice Type Sent via

Electronic Invoice

Sent on Paper

Original Invoice Y N Past Due Statement N Y Adjusted Invoice – Credit/Debit Memo Y N

6.2 Past Due Invoices Customers can obtain a listing of their outstanding invoices through past due statements. These statements are Microsoft Excel spreadsheets and are handled by DHL Revenue Assurance Analysts.

6.3 Proof of Delivery Proof of delivery information will only be provided in the electronic invoicing file when contractually obligated. Please contact your DHL sales representative for any questions on this functionality.


Page 15 of 146

Chapter 7 EDI Compliance Testing

7.1 IDI Testing It is the customer’s responsibility to complete an appropriate amount of testing and inform DHL when their systems are ready to receive the IDI files.

IDI testing includes the following steps:

Customer sign and email a scanned copy of the IDI trading partner agreement to [email protected]

DHL will provide EDI invoice test files using the customer’s paper invoice data,

provided current open invoices are in DHL’s system. Customers will be advised when test data is available for processing.

Customers are responsible for testing the file receipt/communication process,

mapping to selected file format, establishing automated remittance processing, and loading data into internal accounts payable/processing system.

Once the customer has successfully tested the IDI file receipt, format and

internal processing the customer must inform DHL to move the IDI account to production. DHL will not move accounts into production until customers advise their DHL EDI analyst that testing is completed, and automated remittance processing is available.

DHL will test and advise customers of any issues or corrections that must be

made prior to moving accounts into EDI billing production status.

DHL will move the account to production. The customer must submit a change request if additional account numbers need to be added to an existing IDI feed. Contact the DHL account manager or the DHL EDI analyst to request the change


Page 16 of 146

7.2 RDI Testing

It is the customer’s responsibility to complete an appropriate amount of testing and inform DHL when their systems are ready to transmit RDI files.

RDI testing includes the following steps:

DHL will setup an RDI test Trading Partner ID for the customer based on the format and configuration items selected

Customers are responsible for testing the file communication process, and

mapping to selected file format.

Once the customer has successfully transmitted a test RDI file, DHL will process the file and inform the customer of any issues. The trading partner will remain in a test status until a successful file has been processed through DHL’s RDI systems.

Once testing has been successfully completed for RDI, the customer must inform

DHL to move the accounts to production. DHL will not move accounts into production until customers advise their DHL EDI Site Activation Analyst that testing is completed, and automated remittance processing is in place.


Page 17 of 146

Chapter 8 Resources

8.1 Who to Contact

Who To Contact Type of Help

New Activations:

[email protected]

New IDI or RDI setup questions

RDI testing

IDI Testing

Product Support:

[email protected]

Terminate an existing IDI feed

IDI or RDI file format issues

Missing IDI file or to request a replacement file

IDI file transport issue

Change file transport method, transport location, or customer contact information

Data Content Support:

[email protected]

DHL billing process questions

Invoice content issues such as rate or fee questions

Frequency of IDI file delivery

Add or remove account number(s) to an existing IDI feed


Page 18 of 146

Chapter 9 IDI DHL3 Format

9.1 Data Structure This is a multiple record type format. Each record starts with a two-character record type indicator and is 80 bytes long. An invoice is represented by a combination of up to 29 record types. A single batch header record precedes data.

H1 Batch Header

The following records appear once for each invoice.

I1 Invoice Header 1 I2 Invoice Header 2 B1 Bill-To Customer Details 1 B2 Bill-To Customer Details 2 B3 Bill-To Customer Details 3

The record types below represent invoice data for each shipment and appear following the records described above.

►A1 Shipment Details 1 ►A2 Shipment Details 2 ►A3 Shipment Details 3 ►A4 Shipment Details 4 ►A5 Shipment Details 5 ►S1 Shipper Details 1 ►S2 Shipper Details 2 ►S3 Shipper Details 3 ►R1 Receiver Details 1 ►R2 Receiver Details 2 ►R3 Receiver Details 3 ►O1 Accessorial Charges (if charges exist, may have up to 30 occurrences) ►D1 Dimensions (if dimensions exist, may have up to 9 occurrences) F1 Fee Details 1 F2 Fee Details 2 E1 Assesse Details 1 E2 Assessee Details 2 E3 Assessee Details 3

A single batch trailer record follows your data.

T1 Batch Trailer

Note: The record types in Green or ► are in invoices for shipment level charges and information only.


Page 19 of 146

The record types in Red or are in invoices for customer level fees and information only.

The record types in Blue or are in both customer level and shipment level invoices.

* Null Values –

Fields with a field type of ‘X’ contain spaces

Fields with a field type of ‘9’ contain zeros

Record Layout H1: Batch Header Field Name Field Type Start End Length Remarks

Record Type XX 1 2 2 Always H1

Sender XXX 3 5 3 Always DHL

Trading Partner Name X(12) 6 17 12 DHL’s Trading Partner name for customer invoiced

Batch Control Number 9(9) 18 26 9 DHL’s control number for this batch

System Date 9(8) 27 34 8 CCYYMMDD

Filler X(46) 35 80 46

Record Layout I1: Invoice Header 1 Field Name Field Type Start End Length Remarks

Record Type XX 1 2 2 Always I1

Invoice Number X(13) 3 15 13

Invoice Date 9(8) 16 23 8 CCYYMMDD

Invoice Due Date 9(8) 24 31 8 CCYYMMDD

Invoice Net Due Days 999 32 34 3

Payment Terms XX 35 36 2 NS=Not Available

Invoice Type Code XX 37 38 2 UO= Export Invoice

CN = Credit Memo

DR = Debit Memo

21= Import Invoice/Customs Duty

Total Item Count 9(5) 39 43 5

Invoice Open Amount 9(9)V99 44 54 11 $$$$$$$$$¢¢

Invoice Total Freight Charge

9(9)V99 55 65 11 $$$$$$$$$¢¢

Invoice Total Other Charges

9(9)V99 66 76 11 $$$$$$$$$¢¢


Page 20 of 146

Field Name Field Type Start End Length Remarks

Filler X(3) 77 80 3

Record Layout I2: Invoice Header 2 Field Name Field Type Start End Length Remarks

Record Type XX 1 2 2 Always I2

Invoice Total Adjustment

S9(9)V99 3 14 12 Null Value

Invoice Total Paid Amount

S9(9)V99 15 26 12 Null Value

Invoice Billing Currency Code

XXX 27 29 3 ISO Currency code

Invoice Payment Currency Code


Invoice Total Chargeable Weight

9(7)V9 33 40 8

Invoice Total Shippers Weight

9(7)V9 41 48 8

Invoice Unit of Measurement-Weight

XX 49 50 2 LB=Pounds

Invoice Total Piece Count

9(5) 51 55 5

Filler X(25) 56 80 25

Record Layout B1: Bill-To Customer Details 1 Field Name Field Type Start End Length Remarks

Record Type XX 1 2 2 Always B1

Bill To Name X(25) 3 27 25

Bill To Name Extension

X(25) 28 52 25 Null Value

Bill To Address 1 X(25) 53 77 25

Filler XXX 78 80 3


Page 21 of 146




Bill To City X(20) 28 47 20

Bill To State/Province XX 48 49 2

Bill To Zip/Postal Code

X(9) 50 58 9

Bill To Country Code XXX 59 61 3 ISO country code

Bill To Customer Number

9(11) 62 72 11 Customer number of paying party

Filler X(8) 73 80 8



Bill To Accounting Control Data

X(25) 3 27 25

Filler X(53) 28 80 53

Record Layout A1: Shipment Details 1 Field Name Field Type Start End Length Remarks

Record Type XX 1 2 2 Always A1

Shipment Number 9(11) 3 13 11

Shipment Bill To Code X 14 14 1 S=Bill to Shipper 3=Bill to Party

F=Party that Remits Fee Payment

Shipment Open Amount

9(9)V99 15 25 11 $$$$$$$$$¢¢

Shipment Billing Currency Code

XXX 26 28 3 ISO currency code

Shipment Payment Currency Code


Shipment Exchange Rate

9(5)V9(5) 32 41 10

Discount Amount 9(9)V99 42 52 11 $$$$$$$$$¢¢

Shipment Accounting Control Data

X(25) 53 77 25

Filler XXX 78 80 3


Page 22 of 146



Bill to Party Customer Number

9(11) 3 13 11

Consol-to Customer Number

9(11) 14 24 11 Null Value

Consol Code XX 25 26 2 Null Value

Consol Rate Message Code

XX 27 28 2 Null Value

Pick Up Location XX 29 30 2 Null Value

Origin Station Code XXX 31 33 3

Destination Station Code

XXX 34 36 3

Pickup Date 9(8) 37 44 8 CCYYMMDD

Pickup Time 9(4) 45 48 4 HHMM

Delivery Date 9(8) 49 56 8 CCYYMMDD

Contact your sales representative for approval

Delivery Time 9(4) 57 60 4 HHMM

Contact your sales representative for approval

Filler X(20) 61 80 20


Page 23 of 146



Receiver Signature X(25) 3 27 25 Contact your sales representative for approval

Filler XXX 28 30 3

Waybill Type Code X 31 31 1 D=Domestic I=International

Shipment Type Code X 32 32 1 E=Express F=Freight

Service Type Code XX 33 34 2 Null Value

Dutiable Shipment Code

X 35 35 1 D=Dutiable Shipment

Service Level XX 36 37 2 See Appendix C for a list of service level codes.

Freight Description X(40) 38 77 40

Filler XXX 78 80 3



Package Type X 3 3 1 E= Non-Doc (Dutiable shipments up to 150 lbs) L= Doc (Non-Dutiable shipments up to 150 lbs)

Chargeable Weight 9(7)V9 4 11 8

Shippers Weight 9(7)V9 12 19 8

Dimensional Weight 9(7)V9 20 27 8

Shipment Unit of Measurement-Weight

XX 28 29 2 KG=Kilograms LB=Pounds

Weight Code XX 30 31 2 A1=Dimensional Weight A2=Reweighed A3=Shippers Weight

Shipment Volume 9(7) 32 38 7

Shipment Unit of Measurement-Volume

X 39 39 1 N=Cubic Inches

Piece Count 9(5) 40 44 5 Total number of packages


Page 24 of 146


Scale X(7) 45 51 7 Formerly rate Scale Number or Tariff Agreement Number. Rate Scale Number is the last 4 digits of the main account number that “owns” the rate contract.

Rate Zone XX 52 53 2 Rate Zone details are not passed for Us Import shipments. Country to country pricing is used in this shipping scenario.

Freight Rate 9(7)V99 54 62 9 Null Value

Freight Charge Amount

9(8)V99 63 72 10 $$$$$$$$¢¢

Filler X(8) 73 80 8



Shipment Value Protection Amount

9(9)V99 3 13 11 $$$$$$$$$¢¢

COD Amount 9(9)V99 14 24 11 Null Value

Filler X(56) 25 80 56

Record Layout S1: Shipper Details 1 Field Name Field Type Start End Length Remarks

Record Type XX 1 2 2 Always S1

Shipper Name X(25) 3 27 25

Shipper Name Extension


Shipper Address 1 X(25) 53 77 25

Filler XXX 78 80 3


Page 25 of 146



Shipper Address 2 X(25) 3 27 25

Shipper City X(20) 28 47 20

Shipper State/Province

XX 48 49 2

Shipper Zip/Postal Code

X(9) 50 58 9

Shipper Country Code XXX 59 61 3 ISO country code

Shipper Customer Number

9(11) 62 72 11

Filler X(8) 73 80 8



Shipper Reference Number

X(35) 3 37 35

Sent By X(25) 38 62 25

Filler X(18) 63 80 18


Page 26 of 146

Record Layout R1: Receiver Details 1 Field Name Field Type Start End Length Remarks

Record Type XX 1 2 2 Always R1

Receiver Name X(25) 3 27 25

Receiver Name Extension


Receiver Address 1 X(25) 53 77 25

Filler XXX 78 80 3



Receiver Address 2 X(25) 3 27 25

Receiver City X(20) 28 47 20

Receiver State/Province

XX 48 49 2

Receiver Zip/Postal Code

X(9) 50 58 9

Receiver Country Code

XXX 59 61 3 ISO country code

Receiver Customer Number

9(11) 62 72 11 Null Value

Filler X(8) 73 80 8



Receiver Reference Number


Attention Of X(25) 28 52 25

Filler X(28) 53 80 28


Page 27 of 146

Record Layout O1: Accessorial Charges

Note: If charges exist, may have up to 30 occurrences.


Record Type XX 1 2 2 Always O1

Accessorial Charge 9(9)V99 3 13 11 $$$$$$$$$¢¢

Accessorial Code XXX 14 16 3 See Appendix A for a list of ISO special charge codes.

Accessorial Description

X(30) 17 46 30

Filler X(34) 47 80 34

Record Layout D1: Dimensions

Note: If dimensions exist, may have up to 9 occurrences.


Record Type XX 1 2 2 Always D1

Height 999 3 5 3

Length 999 6 8 3

Width 999 9 11 3

Dimension Piece Count

999 12 14 3

Unit of Measurement- Dimensions

X 15 15 1 N=Inches

Filler X(65) 16 80 65


Page 28 of 146

Record Layout F1: Fee Details 1 Field Name Field Type Start End Length Remarks

Record Type XX 1 2 2 Always F1

Fee Number 9(11) 3 13 11

Fee Date 9(8) 14 21 8 CCYYMMDD

Fee Bill To Code X 22 22 1 F=Party that Remits Fee Payment

Fee Type Code XXX 23 25 3 See Appendix B for a list of fee codes.

Fee Description X(15) 26 40 15

Fee Open Amount 9(9)V99 41 51 11 $$$$$$$$$¢¢

Fee Billing Currency Code


Fee Payment Currency Code


Fee Exchange Rate 9(5)V9(5) 58 67 10

Filler X(13) 68 80 13

Record Layout F2: Fee Details 2 Field Name Field Type Start End Length Remarks

Record Type XX 1 2 2 Always F2

Fee Rate 999V99 3 7 5 $$$¢¢

Fee Calculation Code XX 8 9 2 VS=Various

Fee Basis Amount 9(11)V99 10 22 13 Null Value

Fee Basis Count 9(13) 23 35 13 Null Value

Fee Beginning Date 9(8) 36 43 8 CCYYMMDD

Fee End Date 9(8) 44 51 8 CCYYMMDD

Fee Period Type X 52 52 1 N=non-Periodically

Filler X(28) 53 80 28

Record Layout E1: Assessee Details 1 Field Name Field Type Start End Length Remarks

Record Type XX 1 2 2 Always E1

Assessee Name X(25) 3 27 25

Assessee Name Extension


Assessee Address 1 X(25) 53 77 25

Filler XXX 78 80 3


Page 29 of 146




Assessee City X(20) 28 47 20

Assessee State/Province

XX 48 49 2

Assessee Zip/Postal Code

X(9) 50 58 9

Assessee Country Code

XXX 59 61 3 ISO country code

Assessee Customer Number

9(11) 62 72 11

Filler X(8) 73 80 8



Assessee Contact Name

X(25) 3 27 25

Assessee Accounting Control Data

X(25) 28 52 25

Filler X(28) 53 80 28

Record Layout T1: Batch Trailer Field Name Field Type Start End Length Remarks

Record Type XX 1 2 2 Always T1

Total Invoice Count 9(11) 3 13 11

Trailer Total Item Count 9(11) 14 24 11

Total Open Amount 9(9)V99 25 35 11 $$$$$$$$$¢¢

Trailer Total Piece Count 9(11) 36 46 11

Trailer Total Chargeable Weight

9(11)V9 47 58 12

Trailer Unit of Measurement – Weight


Filler X(20) 61 80 20


Page 30 of 146

Chapter 10 IDI DHL6 Format

10.0 Data Structure This is a comma-delimited format. A comma separates each field, making it easy to pull the data into spreadsheet software.

*Null values are defined based on the field type.

A field type of ‘X’ will represent a null value with spaces

A field type of ‘9’ will represent a null value with zeroes.

Record Layout Summary Start End Length

DHL6 RECORD 1 4013 4013

BATCH DATA 1 32 32

INVOICE DATA 33 364 332

ITEM DATA 365 424 60

SHIPMENT DATA 425 1151 727

ACCESSORIAL DATA 1152 2441 1290

DIMENSIONS DATA 2442 2507 66

CONSOL DATA 2508 2651 144

FEE DATA 2652 2945 294

FEE TEXT DATA 2946 3965 1020

ITEM ADJUSTMENTS & PAYMENTS DATA 3966 3993 28

FILLER 3994 4013 20

Accessorial charges that have an asterisk (*) indicate that the charge is included in the Shipment Total Other Charges.

Note: The fields in Green or ► are in invoices for shipment level charges and information only.

The record types in Red or are in invoices for customer level fees and information only.

The fields in Blue or are in both customer level and shipment level invoices.


Page 31 of 146

10.2 Record Layout


DHL6 RECORD 1 4012 4012

BATCH DATA GROUP 1 32 32

Trading Partner Name X(12) 1 12 12 DHL’s trading partner name for customer invoiced

Filler X 13 13 1 Value=,

Batch Control Number 9(9) 14 22 9 DHL’s control number for this batch


System Date 9(8) 24 31 8 CCYYMMDD


INVOICE DATA GROUP 33 363 331

Invoice Number X(13) 33 45 13 See section 3.8 for format details


Invoice Date 9(8) 47 54 8 CCYYMMDD


Invoice Due Date 9(8) 56 63 8 CCYYMMDD


Invoice Net Due Days 999 65 67 3


Payment Terms XX 69 70 2 NS=Not Available


Invoice Type Code XX 72 73 2 UO=Export Invoice

CN = Credit Memo

DR = Debit Memo

21 = Import Invoice/Customs Duty


Total Item Count 9(5) 75 79 5


Invoice Open Amount 9(9).99 81 92 12 $$$$$$$$$.¢¢


►Invoice Total Freight Charge

9(9).99 94 105 12 $$$$$$$$$.¢¢


Page 32 of 146



►Invoice Total Other Charges

9(9).99 107 118 12 $$$$$$$$$.¢¢


Invoice Total Adjustment S9(9).99 120 132 13 $$$$$$$$$.¢¢


Invoice Total Paid Amount

S9(9).99 134 146 13 Null Value


Invoice Billing Currency Code



Invoice Payment Currency Code



►Invoice Total Chargeable Weight

9(7).9 156 164 9


►Invoice Total ShippersWeight

9(7).9 166 174 9


►Invoice Unit of Measurement-Weight



►Invoice Total Piece Count

9(5) 179 183 5


Bill To Name X(25) 185 209 25


Bill To Name Extension X(25) 211 235 25 Null Value






Bill To City X(20) 289 308 20



Page 33 of 146


Bill To State/Province XX 310 311 2


Bill To Zip/Postal Code X(9) 313 321 9


Bill To Country Code XXX 323 325 3 ISO country code


Bill To Customer Number 9(11) 327 337 11 Customer number of paying party


Bill To Accounting Control Data

X(25) 339 363 25


ITEM DATA GROUP 365 424 60

Item Number 9(11) 365 375 11


Bill To Code X 377 377 1 S=Bill to Shipper 3=Bill to Party

F=Party that Remits Fee Payment


Item Open Amount 9(9).99 379 390 12 $$$$$$$$$.¢¢


►Shipment Total Other Charges

9(9).99 392 403 12 $$$$$$$$$.¢¢


Item Billing Currency Code



Item Payment Currency Code



Exchange Rate 9(5).9(5) 413 423 11


SHIPMENT DATA GROUP 425 1151 727

► Discount Amount 9(9).99 425 436 12 $$$$$$$$$.¢¢

Total Discount amount


Page 34 of 146



►Consol Code XX 438 439 2 Null Value


► Consol Rate Message Code

XX 441 442 2 Null Value


►Shipper Name X(25) 444 468 25


► Shipper Name Extension

X(25) 470 494 25 Null Value


►Shipper Address 1 X(25) 496 520 25


►Shipper Address 2 X(25) 522 546 25


►Shipper City X(20) 548 567 20


►Shipper State/Province XX 569 570 2


►Shipper Zip/Postal Code X(9) 572 580 9


►Shipper Country Code XXX 582 584 3 ISO country code


►Shipper Customer Number

9(11) 586 596 11


►Shipper Reference Number

X(35) 598 632 35


►Sent By X(25) 634 658 25


►Receiver Name X(25) 660 684 25


► Receiver Name Extension

X(25) 686 710 25 Null Value



Page 35 of 146


►Receiver Address 1 X(25) 712 736 25


►Receiver Address 2 X(25) 738 762 25


►Receiver City X(20) 764 783 20


►Receiver State/Province XX 785 786 2


►Receiver Zip/Postal Code

X(9) 788 796 9


►Receiver Country Code XXX 798 800 3 ISO country code


► Receiver Customer Number

9(11) 802 812 11 Null Value


► Receiver Reference Number

X(25) 814 838 25 Null Value


►Attention Of X(25) 840 864 25


►Shipment Accounting Control Data

X(25) 866 890 25


►Third Party Account Number

9(11) 892 902 11 Only applicable when shipment has bill to 3rd

party terms.


► Consol-to Customer Number

9(11) 904 914 11 Null Value


►Pick Up Location XX 916 917 2 Null Value


►Origin Station Code XXX 919 921 3


►Destination Station Code XXX 923 925 3



Page 36 of 146


►Pickup Date 9(8) 927 934 8 CCYYMMDD


►Pickup Time 9(4) 936 939 4 HHMM


►Delivery Date 9(8) 941 948 8 CCYYMMDD

Contact your your sales representative for approval


►Delivery Time 9(4) 950 951 4 HHMM

Contact your your sales representative for approval


►Receiver Signature X(25) 955 979 25 Contact your your sales representative for approval


►Filler XXX 981 983 3


►Waybill Type Code X 985 985 1 D=Domestic I=International


►Shipment Type Code X 987 987 1 E=Express


►Service Type Code XX 989 990 2 Null Value


►Dutiable Shipment Code X 992 992 1 D=Dutiable Shipment


►Service Level XX 994 995 2 See Appendix C for a list of service level codes


►Freight Description X(40) 997 1036 40



Page 37 of 146


►Package Type X 1038 1038 1 E= Non-Doc (Dutiable shipments up to 150 lbs) L= Doc (Non-Dutiable shipments up to 150 lbs)


►Chargeable Weight 9(7).9 1040 1048 9


►Shippers Weight 9(7).9 1050 1058 9


►Dimensional Weight 9(7).9 1060 1068 9


►Shipment Unit of Measurement-Weight

XX 1070 1071 2 KG=Kilograms LB=Pounds


►Weight Code XX 1072 1074 2 A1=Dimensional Weight A2=Reweighed A3=Shippers Weight


►Shipment Volume 9(7) 1076 1082 7


►Shipment Unit of Measurement-Volume

X 1084 1084 1 N=Cubic Inches


►Piece Count 9(5) 1086 1090 5 Total number of packages


►Scale X(7) 1092 1098 7 Formerly rate Scale Number or Tariff Agreement Number. Rate Scale Number is the last 4 digits of the main bill to account for the rate contract.



Page 38 of 146


►Rate Zone XX 1100 1101 2 Rate Zone details are not passed for Us Import shipments. Country to country pricing is used in this shipping scenario.


►Freight Rate 9(7).99 1103 1112 10 Null Value


►Freight Charge Amount 9(8).99 1114 1124 11 $$$$$$$$.¢¢


► Shipment Value Protection Amount

9(9).99 1126 1137 12 $$$$$$$$$.¢¢


►COD Amount 9(9).99 1139 1150 12 Null Value


ACCESSORIAL DATA – OCCURS 30 TIMES

GROUP 1152 2441 1290

ACCESSORIAL 1 GROUP 1152 1194 43

►Accessorial Charge* 9(9).99 1152 1163 12 $$$$$$$$$.¢¢


►Accessorial Code XXX 1165 1167 3 See Appendix A for a list of ISO special charge codes.


►Accessorial Description X(25) 1169 1193 25












Page 39 of 146
































Page 40 of 146































Page 41 of 146































Page 42 of 146































Page 43 of 146































Page 44 of 146































Page 45 of 146



























DIMENSIONS DATA – OCCURS 9 TIMES

GROUP 2442 2507 66

DIMENSIONS 1 GROUP 2442 2457 16

►Height 999 2442 2444 3


Page 46 of 146



►Length 999 2446 2448 3


►Width 999 2450 2452 3


►Dimension Piece Count 999 2454 2456 3



►Height 999 2458 2460 3


►Length 999 2462 2464 3


►Width 999 2466 2468 3





►Height 999 2474 2476 3


►Length 999 2478 2480 3


►Width 999 2482 2484 3





►Height 999 2490 2492 3


►Length 999 2494 2496 3


►Width 999 2498 2500 3





Page 47 of 146


►Unit of Measurement- Dimensions

X 2506 2506 1 N=Inches


CONSOL 1 GROUP 2508 2525 18

►Airline Number 999 2508 2510 3

►Dash 1 X 2511 2511 1 Value=-

►Origin Station Code XXX 2512 2514 3

►Dash 2 X 2515 2515 1 Value=-

►Consol Number 9(9) 2516 2524 9



►Airline Number 999 2526 2528 3 Null Value

►Dash 1 X 2529 2529 1 Value=-

►Origin Station Code XXX 25230 2532 3 Null Value

►Dash 2 X 2533 2533 1 Value=-

►Consol Number 9(9) 2534 2542 9 Null Value




►Dash 1 X 2547 2547 1 Value=-


►Dash 2 X 2551 2551 1 Value=-





►Dash 1 X 2565 2565 1 Value=-


►Dash 2 X 2569 2569 1 Value=-





►Dash 1 X 2583 2583 1 Value=-


Page 48 of 146



►Dash 2 X 2587 2587 1 Value=-





►Dash 1 X 2601 2601 1 Value=-


►Dash 2 X 2605 2605 1 Value=-





►Dash 1 X 2619 2619 1 Value=-


►Dash 2 X 2623 2623 1 Value=-





►Dash 1 X 2637 2637 1 Value=-


►Dash 2 X 2641 2641 1 Value=-



FEE DATA GROUP 2652 2945 294

Assessee Name X(25) 2652 2676 25


Assessee Name Extension

X(25) 2678 2702 25






Page 49 of 146



Assessee City X(20) 2756 2775 20


Assessee State/Province XX 2777 2778 2


Assessee Zip/Postal Code

X(9) 2780 2788 9


Assessee Country Code XXX 27890 2792 3 ISO country code


Assessee Customer Number

9(11) 2794 2804 11


Assessee Contact Name X(25) 2806 2830 25


Assessee Accounting Control Data

X(25) 2832 2856 25


Fee Date 9(8) 2858 2865 8 CCYYMMDD


Fee Type Code XXX 2867 2869 3 See Appendix B for a list of fee codes.


Fee Description X(15) 2871 2885 15


Fee Rate 9(3).99 2887 2892 6 $$$.¢¢


Fee Calculation Code XX 2894 2895 2 VS=Various


Fee Basis Amount 9(11).99 2897 2910 14 Null Value


Fee Basis Count 9(13) 2912 2924 13 Null Value


Fee Beginning Date 9(8) 2926 2933 8 CCYYMMDD

Null Value


Page 50 of 146



Fee End Date 9(8) 2935 2942 8 CCYYMMDD

Null Value


Fee Period Type X 2944 2944 1 N=non-Periodically


FEE TEXT DATA – OCCURS 20 TIMES

GROUP 2946 3965 1020

Fee Text 1 X(50) 2946 2995 50 Null Value



























Page 51 of 146
















ITEM ADJUSTMENTS AND PAYMENTS DATA

GROUP 3966 3993 28

Item Total Adjustment S9(9).99 3966 3978 13 $$$$$$$$$.¢¢

Null Value


Item Total Paid Amount S9(9).99 3980 3992 13 Null Value


FILLER GROUP 3994 4013 20

Filler X(20) 3994 4013 20


Page 52 of 146

Chapter 12 IDI 110DHL Format

Data Structure ASC X12 Air Freight Details & Invoice Transaction 110 Version 004010. The transaction set can be used to provide a customer with an air invoice for transportation and other charges related to shipments, including Original Invoices, Past Due Billings, Balance Due Bills and Revisions.

IA Functional Group - To indicate the beginning of a functional group and to provide control information

N1 Name - To identify a party by type of organization, name, and code

N2 Additional Name Information - To specify additional names or those longer than 35 characters in length

N3 Address Information - To specify the location of the named party

N4 Geographic Location - To specify the geographic place of the named party

N9 Reference Identification - To transmit identifying information as specified by the Reference Identification Qualifier

LX Assigned Number - To reference a line number in a transaction set

N1 Name - To identify a party by type of organization, name, and code

N2 Additional Name Information - To specify additional names or those longer than 35 characters in length

N3 Address Information - To specify the location of the named party

N4 Geographic Location - To specify the geographic place of the named party

N9 Reference Identification - To transmit identifying information as specified by the Reference Identification Qualifier

PER Administrative Communications Contact - To identify a person or office to whom administrative communications should be directed

P1 Pick-up - To specify the pick-up details including time, date, and equipment

R1 Route Information (Air) - To specify airline and airport routing sequences

POD Proof of Delivery - To provide proof of delivery

RMT Remittance Advice - To indicate the detail on items

NTE Note/Special Instruction - To transmit information in a free-form format, if necessary, for comment or special instruction

L5 Description, Marks and Numbers - To specify the line item in terms of description, quantity, packaging, and marks and numbers


Page 53 of 146

L0 Line Item - Quantity and Weight - To specify quantity, weight, volume, and type of service for a line item including applicable "quantity/rate-as" data

L4 Measurement - To describe physical dimensions and quantities

L10 Weight - To transmit weight information

SL1 Tariff Reference - To reference details of the tariff used to arrive at applicable rates or charges for customer-requested service

L1 Rate and Charges - To specify rate and charges detail relative to a line item including freight charges, advances, special charges, and entitlements

C3 Currency - To specify the currency being used in the transaction set

L3 Total Weight and Charges - To specify the total shipment in terms of weight, volume, rates, charges, advances, and prepaid amounts applicable to one or more line items

SE Transaction Set Trailer - To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)

GE Functional Group Trailer - To indicate the end of a functional group and to provide control information

IEA Interchange Control Trailer - To define the end of an interchange of zero or more functional groups and interchange-related control segments


Page 54 of 146

IA Functional Group To indicate the beginning of a functional group and to provide control information

Pos Id Segment Name Req Max Use Repeat Notes Usage

ISA Interchange Control Header M 1 Used

GS Functional Group Header M 1 Used


010 ST Transaction Set Header M 1 Must use

Segments:

Heading:

020 B3 Beginning Segment for Carrier's Invoice

M 1 Must use

030 B3A Invoice Type O 1 Used

050 C3 Currency O 1 Used

065 ITD Terms of Sale/Deferred Terms of Sale

O 1 Used

LOOP ID - N1 3

075 N1 Name O 1 N1/075 Used

080 N2 Additional Name Information O 1 Used

090 N3 Address Information O 2 Used

100 N4 Geographic Location O 1 Used

110 N9 Reference Identification O 10 Used


Page 55 of 146


LOOP ID - LX 50000

010 LX Assigned Number M 1 Must use

Detail:

LOOP ID - N1 2 020 N1 Name O 1 N2/020 Used

030 N2 Additional Name Information O 1 Used

040 N3 Address Information O 2 Used

050 N4 Geographic Location O 1 Used

060 N9 Reference Identification O 10 Used

070 PER Administrative Communications Contact

O 1 Used

085 P1 Pick-up O 1 Used

090 R1 Route Information (Air) O 1 Used

100 POD Proof of Delivery O 1 Used

125 RMT Remittance Advice O 10 Used

140 NTE Note/Special Instruction O 10 Used

LOOP ID - L5 4 150 L5 Description, Marks and Numbers M 1 Must use 160 L0 Line Item - Quantity and Weight O 1 Used 163 L4 Measurement O 4 Used 165 L10 Weight O 4 Used 167 SL1 Tariff Reference O 1 Used LOOP ID - L1 30 175 L1 Rate and Charges O 1 Used 180 C3 Currency O 1 Used 175 L1 Rate and Charges O 1 Used

Pos Id Segment Name Req Max Use Repeat Notes Usage 015 L3 Total Weight and Charges M 1 Must use

045 SE Transaction Set Trailer M 1 Must use

Summary:


Segments:

GE Functional Group Trailer M 1 Used

IEA Interchange Control Trailer M 1 Used

Notes: 1/075 The N1 Loop is used only to convey entity information relevant to the debtor or for a party other than the shipper or consignee. 2/020 The N1 loop is used to convey entity information relevant to the shipper and consignee.


Page 56 of 146

ISA Interchange Control Header Pos: Max: 1

- Mandatory Loop: N/A Elements: 16

To start and identify an interchange of zero or more functional groups and interchange-related control segments

Element Summary:

Ref _ Id_ Element Name _

Req Type Min/Max Usage_

ISA01 I01 Authorization Information Qualifier Description: Code to identify the type of information in the Authorization Information

M ID 2/2 Must use

User Note 1: Mutually defined

ISA02 I02 Authorization Information M AN 10/10 Must

Description: Information used for additional useidentification or authorization of the interchange sender or the data in the interchange; the type of information is

set by the Authorization Information Qualifier (I01) User Note 1: Mutually defined

ISA03 I03 Security Information Qualifier M ID 2/2 Must

Description: Code to identify the type of information in use

the Security Information User Note 1: Mutually defined

ISA04 I04 Security Information M AN 10/10 Must

Description: This is used for identifying the security useinformation about the interchange sender or the data in the interchange; the type of information is set by the

Security Information Qualifier (I03) User Note 1: Mutually defined

ISA05 I05 Interchange ID Qualifier M ID 2/2 Must

Description: Qualifier to designate the system/method use

of code structure used to designate the sender or receiver ID element being qualified

Code Name _

01 Duns (Dun & Bradstreet) Number 02 SCAC (Standard Carrier Alpha Code) ZZ Name

ISA06 I06 Interchange Sender ID M AN 15/15 Must

Description: Identification code published by the use

sender for other parties to use as the receiver ID to route data to them; the sender always codes this value

in the sender ID element

ISA07 I05 Interchange ID Qualifier M ID 2/2 Must

Description: Qualifier to designate the system/method use


Page 57 of 146



of code structure used to designate the sender or receiver ID element being qualified

Code Name _

01 Duns (Dun & Bradstreet) Number ZZ Name

ISA08 I07 Interchange Receiver ID M AN 15/15 Must

Description: Identification code published by the usereceiver of the data; When sending, it is used by the sender as their sending ID, thus other parties sending to

them will use this as a receiving ID to route data to them User Note 1: Mutually defined

ISA09 I08 Interchange Date Description: Date of the interchange

User Note 1: YYMMDD

M DT 6/6 Must use

ISA10 I09 Interchange Time

Description: Time of the interchange

User Note 1: HHMM

M TM 4/4 Must use

ISA11 I10 Interchange Control Standards Identifier M ID 1/1 Must

Description: Code to identify the agency responsible usefor the control standard used by the message that is

enclosed by the interchange header and trailer

Code Name _

U U.S. EDI Community of ASC X12, TDCC, and UCS

ISA12 I11 Interchange Control Version Number

Description: This version number covers the interchange control segments

M ID 5/5 Must use

Code _ Name _

00400 Standard Issued as ANSI X12.5-1997

ISA13 I12 Interchange Control Number Description: A control number assigned by the interchange sender

M N0 9/9 Must use

ISA14 I13 Acknowledgment Requested Description: Code sent by the sender to request an interchange acknowledgment (TA1)

M ID 1/1 Must use

All valid standard codes are used. ISA15 I14 Usage Indicator

Description: Code to indicate whether data enclosed by this interchange envelope is test, production or information

M ID 1/1 Must use

Code Name


Page 58 of 146



_ P Production Data T Test Data

ISA16 I15 Component Element Separator M 1/1 Must

Description: Type is not applicable; the component use

element separator is a delimiter and not a data element; this field provides the delimiter used to separatecomponent data elements within a composite datastructure; this value must be different than the data

element separator and the segment terminator User Note 1: Always >


Page 59 of 146

GS Functional Group Header Pos: Max: 1


To indicate the beginning of a functional group and to provide control information

Element Summary:


Req Type Min/MaxUsage_

GS01 479 Functional Identifier Code Description: Code identifying a group of application related transaction sets

M ID 2/2 Must use

Code Name _

IA Air Freight Details and Invoice (110, 980)

GS02 142 Application Sender's Code Description: Code identifying party sending transmission; codes agreed to by trading partners

M AN 2/15 Must use

GS03 124 Application Receiver's Code Description: Code identifying party receiving transmission. Codes agreed to by trading partners

M AN 2/15 Must use

User Note 1: Mutually defined

GS04

373

Date Description: Date expressed as CCYYMMDD

M

DT

8/8 Must use

GS05

337

Time Description: Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, or HHMMSSD, or HHMMSSDD, where H = hours (00-23), M = minutes (00-59), S = integer seconds (00-59) and DD = decimal seconds; decimal seconds are expressed as follows: D = tenths (0-9) and DD = hundredths (00-99)

M

TM

4/8 Must use

User Note 1: HHMM

GS06

28

Group Control Number Description: Assigned number originated and maintained by the sender

M

N0

1/9 Must use

User Note 1: Same as interchange control number

GS07

455

Responsible Agency Code Description: Code used in conjunction with Data Element 480 to identify the issuer of the standard

M

ID

1/2 Must use

Code Name _

X Accredited Standards Committee X12

GS08

480

Version / Release / Industry Identifier Code Description: Code indicating the version, release, sub

M

AN

1/12 Must use


Page 60 of 146


Req Type Min/MaxUsage_

release, and industry identifier of the EDI standard being used, including the GS and GE segments; if code in DE455 in GS segment is X, then in DE 480 positions 1-3 are the version number; positions 4-6 are the release and sub release, level of the version; and positions 7-12 are the industry or trade association identifiers (optionally assigned by user); if code in DE455 in GS segment is T, then other formats are allowed

Code _ Name _

004010 Draft Standards Approved for Publication by ASC X12 Procedures Review Board through October 1997

Semantics: 1. GS04 is the group date. 2. GS05 is the group time. 3. The data interchange control number GS06 in this header must be identical to the same data element in the associated functional group trailer, GE02.

Comments: 1. A functional group of related transaction sets, within the scope of X12 standards, consists of a collection of similar transaction sets enclosed by a functional group header and a functional group trailer.


Page 61 of 146

ST Transaction Set Header Pos: 010 Max: 1

Heading - Mandatory Loop: N/A Elements: 2

To indicate the start of a transaction set and to assign a control number

Element Summary:



ST01 143 Transaction Set Identifier Code Description: Code uniquely identifying a Transaction Set

M ID 3/3 Must use

Code Name _

110 Air Freight Details and Invoice

ST02 329 Transaction Set Control Number M AN 4/9 Must

Description: Identifying control number that must be use

unique within the transaction set functional group assigned by the originator for a transaction set

User Note 1: Incrementing number 1-999999999

Semantics: 1. The transaction set identifier (ST01) used by the translation routines of the interchange partners to select the appropriate transaction set definition (e.g., 810 selects the Invoice Transaction Set).


Page 62 of 146

B3 Beginning Segment for Carrier's Invoice

Pos: 020 Max: 1 Heading - Mandatory

Loop: N/A Elements: 6

To transmit basic data relating to the carrier's invoice

Element Summary:



B302 76 Invoice Number Description: Identifying number assigned by issuer

M AN 1/22 Must use

User Note 1: Maximum length = 13 See section 3.8 for additional details

B304 146 Shipment Method of Payment

Description: Code identifying payment terms for transportation charges

M ID 2/2 Must use

Code Name _

MX Mixed

B306 373 Date Description: Date expressed as CCYYMMDD

M DT 8/8 Must use

User Note 1: Invoice date

B307 193 Net Amount Due M N2 1/12 Must

Description: Total charges to be paid by the receiver of usethis transaction set expressed in the standard monetary

denomination for the currency specified User Note 1: Total charges

B311 140 Standard Carrier Alpha Code Description: Standard Carrier Alpha Code

User Note 1: Value = DHLC

M ID 2/4 Must use

B312 373 Date

Description: Date expressed as CCYYMMDD

User Note 1: Current system date

O DT 8/8 Used

Syntax:

1. B309 P0910 -- If either B309 or B310 are present, then the others are required.

Semantics: 1. B306 is the billing date. 2. On collect freight bills the data in B309 will be the actual delivery date. For the shipments invoiced prior to delivery, the B309 will be the estimated date of delivery. 3. If B314 is used, B304 will indicate the party or parties responsible for payment of the transportation terms identified in B314.


Page 63 of 146

B3A Invoice Type Pos: 030 Max: 1

Heading - Optional Loop: N/A Elements: 2

To indicate type of invoice and number of shipments

Element Summary:


Req Type Min/Max sage_

B3A01 640 Transaction Type Code Description: Code specifying the type of transaction

M ID 2/2 Must use

Code Name _

UO Export Invoice CN Credit Memo DR Debit Memo 21 Import Invoice/Customs Duty

B3A02 21 Number of Shipments O N0 1/5 Used

Description: Total number of shipments on this transaction

User Note 1: Number of items

Comments: 1. B3A02 is the number of shipments invoiced.


Page 64 of 146

C3 Currency Pos: 050 Max: 1

Heading - Optional Loop: N/A Elements: 2

To specify the currency being used in the transaction set

Element Summary:



C301 100 Currency Code Description: Code (Standard ISO) for country in whose currency the charges are specified

M ID 3/3 Must use

User Note 1: ISO currency code for the billing currency - will be the same as the payment currency (target currency for currency conversion)

User Note 2: Always USD

C303 100 Currency Code Description: Code (Standard ISO) for country in whose

O ID 3/3 Used

currency the charges are specified User Note 1: ISO currency code for the payment

currency - will be the same as the billing currency (target currency for currency conversion)


Semantics: 1. C301 is the billing currency. 2. C303 is the payment currency. 3. C304 is the rated currency.

Comments: 1. Currency is implied by the code for the country in whose currency the monetary amounts are specified.


Page 65 of 146

ITD Terms of Sale/Deferred Terms of Sale

Pos: 065 Max: 1 Heading - Optional

Loop: N/A Elements: 4

To specify terms of sale

Element Summary:

Ref _ Id_ Element Name Req Type Min/Max Usage

_ _

ITD01 336 Terms Type Code Description: Code identifying type of payment terms

O ID 2/2 Used

Code Name _

05 Discount Not Applicable

ITD02 333 Terms Basis Date Code Description: Code identifying the beginning of the terms period

O ID 1/2 Used

Code Name _

3 Invoice Date

ITD06 446 Terms Net Due Date O DT 8/8 Used

Description: Date when total invoice amount becomes due expressed in format CCYYMMDD

User Note 1: Invoice due date

ITD07 386 Terms Net Days O N0 1/3 Used

Description: Number of days until total invoice amount is due (discount not applicable)

User Note 1: Invoice net due days

Syntax:

L03040513 -- If ITD03 is present, then at least one of ITD04, ITD05 or ITD13 is required. L08040513 -- If ITD08 is present, then at least one of ITD04, ITD05 or ITD13 is required. L091011 -- If ITD09 is present, then at least one of ITD10 or ITD11 is required.

Semantics: 1. ITD15 is the percentage applied to a base amount used to determine a late payment charge.

Comments: 1. If the code in ITD01 is "04", then ITD07 or ITD09 is required and either ITD10 or ITD11 is required; if the code in ITD01 is "05", then ITD06 or ITD07 is required.


Page 66 of 146

N1 Name Pos: 075 Max: 1

Heading - Optional Loop: N1 Elements: 4

To identify a party by type of organization, name, and code

Element Summary:



N101 98 Entity Identifier Code Description: Code identifying an organizational entity, a physical location, property or an individual

M ID 2/3 Must use

Code Name _

BT Bill-to-Party

N102 93 Name Description: Free-form name

C AN 1/60 Used

User Note 1: Bill-to name User Note 2: Maximum length = 25

N103

66

Identification Code Qualifier C

ID

1/2 Used

Description: Code designating the system/method of code structure used for Identification Code (67)

Code Name _

25 Carrier's Customer Code

N104

67

Identification Code C

AN

2/80 Used

Description: Code identifying a party or other code User Note 1: Bill-to customer number User Note 2: Maximum length = 11

Syntax:

1. N102 R0203 -- At least one of N102 or N103 is required. 2. N103 P0304 -- If either N103 or N104 are present, then the others are required.

Comments: 1. This segment, used alone, provides the most efficient method of providing organizational identification. To obtain this efficiency the "ID Code" (N104) must provide a key to the table maintained by the transaction processing party. 2. N105 and N106 further define the type of entity in N101.


Page 67 of 146

N3 Address Information Pos: 090 Max: 2


To specify the location of the named party

Element Summary:



N301 166 Address Information Description: Address information

M AN 1/55 Must use

User Note 1: Bill-to address User Note 2: Maximum length = 25

N302

166

Address Information O

AN

1/55 Used

Description: Address information User Note 1: Bill-to additional address User Note 2: Maximum length = 25


Page 68 of 146

N4 Geographic Location Pos: 100 Max: 1


To specify the geographic place of the named party

Element Summary:



N401 19 City Name O AN 2/30 Used

Description: Free-form text for city name User Note 1: Bill-to city name

User Note 2: For international shipments, N401 may contain the city and/or province.

User Note 3: Maximum length = 20

N402

156

State or Province Code O

ID

2/2 Used

Description: Code (Standard State/Province) as defined by appropriate government agency

User Note 1: Bill-to state (USA) or province

N403

116

Postal Code O

ID

3/15 Used

Description: Code defining international postal zone code excluding punctuation and blanks (zip code for United States)

User Note 1: Bill-to postal code User Note 2: Maximum length = 12

N404

26

Country Code O

ID

2/3 Used

Description: Code identifying the country User Note 1: Bill-to ISO country code

Syntax:

1. N406 C0605 -- If N406 is present, then N405 is required

Comments: 1. A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location. 2. N402 is required only if city name (N401) is in the U.S. or Canada.


Page 69 of 146

N9 Reference Identification Pos: 110 Max: 10


To transmit identifying information as specified by the Reference Identification Qualifier

Element Summary:



N901 128 Reference Identification Qualifier Description: Code qualifying the Reference Identification

M ID 2/3 Must use

Code Name _

80 Charge Number

N902 127 Reference Identification Description: Reference information as defined for a

C AN 1/30 Used

particular Transaction Set or as specified by theReference Identification Qualifier

User Note 1: Accounting control reference number User Note 2: Maximum length = 25


Page 70 of 146

LX Assigned Number Pos: 010 Max: 1

Detail - Mandatory Loop: LX Elements: 1

To reference a line number in a transaction set

Element Summary:



LX01 554 Assigned Number Description: Number assigned for differentiation within a transaction set

M N0 1/6 Must use

User Note 1: Incrementing number 1-50000


Page 71 of 146

N1 Name Pos: 020 Max: 1

Detail - Optional Loop: N1 Elements: 4


Element Summary:



N101 98 Entity Identifier Code Description: Code identifying an organizational entity, a physical location, property or an individual

M ID 2/3 Must use

Code Name

_ CN Consignee SH Shipper

N102

93

Name C

AN

1/60 Used

Description: Free-form name User Note 1: Shipper name - if N101 = SH

Consignee name - if N101 = CN


N103

66

Identification Code Qualifier C

ID

1/2 Used


Code Name _

25 Carrier's Customer Code

N104

67

Identification Code C

AN

2/80 Used

Description: Code identifying a party or other code User Note 1: Shipper customer number - if N101 = SH

Assessee customer number - if N101 = PU, RM or 77


Syntax:

1. N102 R0203 -- At least one of N102 or N103 is required. 2. N103 P0304 -- If either N103 or N104 are present, then the others are required.

Comments: 1. This segment, used alone, provides the most efficient method of providing organizational identification. To obtain this efficiency the "ID Code" (N104) must provide a key to the table maintained by the transaction processing party. 2. N105 and N106 further define the type of entity in N101.


Page 72 of 146

N3 Address Information Pos: 040 Max: 2


To specify the location of the named party

Element Summary:



N301 166 Address Information Description: Address information

M AN 1/55 Must use

User Note 1: Shipper address - if N101 = SH

Consignee address - if N101 = CN


N302

166

Address Information O

AN

1/55 Used

Description: Address information User Note 1: Shipper additional address - if N101 =

SH

Consignee additional address - if N101 = CN User Note 2: Maximum length = 25


Page 73 of 146

N4 Geographic Location Pos: 050 Max: 1


To specify the geographic place of the named party

Element Summary:



N401 19 City Name O AN 2/30 Used

Description: Free-form text for city name User Note 1: Shipper city - if N101 = SH

Consignee city - if N101 = CN

User Note 2: For international shipments, N401 may contain the city or province.


N402

156

State or Province Code O

ID

2/2 Used

Description: Code (Standard State/Province) as defined by appropriate government agency

User Note 1: Shipper state (USA) or province - if N101 = SH

Consignee state (USA) or province - if N101 = CN

N403

116

Postal Code

O

ID

3/15

Used

Description: Code defining international postal zone code excluding punctuation and blanks (zip code for United States)

User Note 1: Shipper postal code - if N101 = SH

Consignee postal code - if N101 = CN


N404

26

Country Code O

ID

2/3 Used

Description: Code identifying the country User Note 1: Shipper ISO country code - if N101 = SH

Consignee ISO country code - if N101 = CN

Syntax:

1. N406 C0605 -- If N406 is present, then N405 is required

Comments: 1. A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location. 2. N402 is required only if city name (N401) is in the U.S. or Canada.


Page 74 of 146

N9 Reference Identification Pos: 060 Max: 10


To transmit identifying information as specified by the Reference Identification Qualifier

Element Summary:



N901 128 Reference Identification Qualifier Description: Code qualifying the Reference Identification

M ID 2/3 Must use

Code Name 14 Master Account Number 80 Charge Number CR Customer Reference Number XX Assessed Period (Rating Period)

N902 127 Reference Identification C AN 1/30 Used

Description: Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier

N903 369 Free-form Description C AN 1/45 Used

Description: Free-form descriptive text User Note 1: Shipper reference number - if N101 = SH

and N901 = CR

Consignee reference number - if N101 = CN and N901 = CR

User Note 2: Maximum length for shipper reference number = 35

Maximum length for consignee reference number = 25


Page 75 of 146

PER Administrative Communications Contact

Pos: 070 Max: 1 Detail - Optional

Loop: N1 Elements: 2

To identify a person or office to whom administrative communications should be directed

Element Summary:



PER01 366 Contact Function Code Description: Code identifying the major duty or responsibility of the person or group named

M ID 2/2 Must use

Code Name DC Delivery Contact NT Notification Contact SH Shipper Contact

PER02

93

Name O

AN

1/60 Used

Description: Free-form name User Note 1: Sent by name - if PER01 = SH

Attention of name - if PER01 = DC

Assessee contact name - if PER01 = NT



Page 76 of 146

P1 Pick-up Pos: 085 Max: 1

Detail - Optional Loop: LX Elements: 5

To specify the pick-up details including time, date, and equipment

Element Summary:



P102 109 Pick-up Date Description: Date the carrier picks up the shipment from the shipper or supplier expressed in format CCYYMMDD

M DT 8/8 Must use

P103 374 Date/Time Qualifier Description: Code specifying type of date or time, or both date and time

M ID 3/3 Must use

Code Name _

011 Shipped

P104 111 Pick-up Time Description: Time (HHMM) that the carrier is to pick up the shipment

O TM 4/4 Used

P107 21 Number of Shipments O N0 1/5 Used

Description: Total number of shipments on this transaction

User Note 1: Always 1

Semantics: 1. P107 is the number of shipments tendered.

Comments: 1. P103 is the pick-up date qualifier.

User Note 1:

This segment is only shown for shipment items.


Page 77 of 146

R1 Route Information (Air) Pos: 090 Max: 1


To specify airline and airport routing sequences

Element Summary:

Ref _ Id_ Element Name Req Type Min/Max Usage

_ _

R101 140 Standard Carrier Alpha Code Description: Standard Carrier Alpha Code

O ID 2/4 Used

User Note 1: Value = DHLC

R102 140 Standard Carrier Alpha Code O ID 2/4 Used

Description: Standard Carrier Alpha Code User Note 1: This data element is only shown for

international shipments.

User Note 2: AIR = Air

R103 5 Airport Code

Description: Code (IATA) for airport

User Note 1: Shipment origin

M ID 3/5 Must use

R104 4 Air Carrier Code

Description: Code (IATA) for the air carrier

User Note 1: Value = DHL

M ID 3/3 Must use

R105 5 Airport Code

Description: Code (IATA) for airport

User Note 1: Shipment destination

M ID 3/5 Must use

Syntax:

1. R106 P0607 -- If either R106 or R107 are present, then the others are required. 2. R108 P0809 -- If either R108 or R109 are present, then the others are required. 3. R110 P1011 -- If either R110 or R111 are present, then the others are required. 4. R112 P1213 -- If either R112 or R113 are present, then the others are required.

User Note 1:



Page 78 of 146

POD Proof of Delivery Pos: 100 Max: 1


To provide proof of delivery

Element Summary:

Ref _ Id_ Element Name

_ Req Type Min/Max sage_

POD01 373 Date Description: Date expressed as CCYYMMDD

M DT 8/8 Must use

User Note 1: Delivery date

POD02 337 Time Description: Time expressed in 24-hour clock time as

O TM 4/8 Used

follows: HHMM, or HHMMSS, or HHMMSSD, orHHMMSSDD, where H = hours (00-23), M = minutes (00-59), S = integer seconds (00-59) and DD = decimal seconds; decimal seconds are expressed as follows: D = tenths (0-9) and DD = hundredths (00-99)

User Note 1: Delivery time User Note 2: HHMM

POD03 93 Name M AN 1/60 Must

Description: Free-form name User Note 1: Receiver signature name

use


User Note 1:

This segment is only shown for shipment items and must be requested. See your Sales Representative for details.


Page 79 of 146

RMT Remittance Advice Pos: 125 Max: 10


To indicate the detail on items

Element Summary:


Req Typ e

Min/Max Usage_

RMT01 128 Reference Identification Qualifier Description: Code qualifying the Reference Identification

M ID 2/3 Must use

Code Name _

AW Air Waybill Number SV Service Charge Number

RMT02 127 Reference Identification Description: Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier

M AN 1/30 Must use

User Note 1: Shipment number - if RMT01 = AW Airway bill number is 10 digits preceded with zeros.

Fee number - if RMT01 = SV


RMT03

782

Monetary Amount O

R

1/18 Used

Description: Monetary amount User Note 1: Total amount due for this item

RMT10

352

Description O

AN

1/80 Used

Description: A free-form description to clarify the related data elements and their content

User Note 1: Fee text - if RMT01 = SV

Semantics: 1. RMT04 is the amount of invoice (including charges, less allowances) before terms discount (if discount is applicable) or debit amount or credit amount of referenced items. 2. RMT05 is the amount upon which the terms discount amount is calculated. 3. RMT06 is the amount of invoice due if paid by terms discount due date (total invoice amount less terms discount amount). 4. RMT07 is the amount of discount taken which may be less than or equal to the amount of discount permitted. 5. 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).

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.


Page 80 of 146

NTE Note/Special Instruction Pos: 140 Max: 10


To transmit information in a free-form format, if necessary, for comment or special instruction

Element Summary:


Req Typ e

Min/Max Usage_

NTE01 363 Note Reference Code O ID 3/3 Used

Description: Code identifying the functional area or purpose for which the note applies

Code Name _

ADD Additional Information CUS Customs declaration

NTE02 352 Description Description: A free-form description to clarify the related data elements and their content

M AN 1/80 Must use

User Note 1: Discount information - if NTE01 = ADD and this is a shipment item

Dutiable shipment message - if NTE01 = CUS and this is a dutiable shipment item

Additional fee text - if NTE01 = ADD and this is a fee item

User Note 2: Discount information formatted as:

'Incentive Discount Amount $$$$$$$$$9.cc'

Dutiable shipment message formatted as: 'Dutiable Shipment'

Comments: 1. The NTE segment permits free-form information/data which, under ANSI X12 standard implementations cannot be processed by a system. The use of the NTE segment should therefore be avoided, if at all possible, in an automated environment.

User Note 1:

For fee items, these segments are only shown if additional fee text is available after 10 RMT segments are exhausted.


Page 81 of 146

L5 Description, Marks and Numbers Pos: 150 Max: 1

Detail - Mandatory Loop: L5 Elements: 3

To specify the line item in terms of description, quantity, packaging, and marks and numbers

Element Summary:

Ref _ Id_ Element Name Req Typ Min/Max Usage

_ e _

L501 213 Lading Line Item Number Description: Sequential line number for a lading item

O N0 1/3 Used


L502 79 Lading Description Description: Description of an item as required for

O AN 1/50 Used

rating and billing purposes User Note 1: This data element is only shown for

shipment items.

User Note 2: Freight description (used only on high value shipments and shipments destined to Puerto Rico, Canada and other international destinations)

L505

103

Packaging Code

O

AN

3/5

Used

Description: Code identifying the type of packaging; Part 1: Packaging Form, Part 2: Packaging Material; if the Data Element is used, then Part 1 is always required

User Note 1: This data element is only shown for shipment items.

User Note 2: The following packaging codes are used:

PKG89 = Doc (Non-Dutiable shipments up to 150 lbs) PKG90 = Non-Doc (Dutiable shipments up to 150 lbs)

Syntax:

1. L503 P0304 -- If either L503 or L504 are present, then the others are required. 2. L507 C0706 -- If L507 is present, then L506 is required 3. L508 P0809 -- If either L508 or L509 are present, then the others are required.

Comments: 1. L502 may be used to send quantity information as part of the product description.


Page 82 of 146

L0 Line Item - Quantity and Weight Pos: 160 Max: 1

Detail - Optional Loop: L5 Elements: 10

To specify quantity, weight, volume, and type of service for a line item including applicable "quantity/rate-as" data

Element Summary:

Ref _ Id_ Element Name Req Typ Min/Max Usage

_ e _


O N0 1/3 Used


L002 220 Billed/Rated-as Quantity C R 1/11 Used

Description: Basis for rating (miles, value, volume, etc.); Note: Weight may be defined by either data element 220 or 81

User Note 1: Chargeable weight

L003 221 Billed/Rated-as Qualifier Description: Code identifying the type of quantity or

C ID 2/2 Used

value on which the rate or item pricing is based Code Name

_ KG Kilogram LB Pound

L004 81 Weight Description: Numeric value of weight

User Note 1: Shippers (actual) weight

C R 1/10 Used

L005 187 Weight Qualifier Description: Code defining the type of weight

C ID 1/2 Used

User Note 1: Codes to qualify how the chargeable weight is derived

Code Name _

A1 Dimensional WeightA2 Reweighed By Carrier

A3 Shippers Weight

L006 183 Volume Description: Value of volumetric measure

User Note 1: Shipment volume

C R 1/8 Used

L007 184 Volume Unit Qualifier

Description: Code identifying the volume unit C ID 1/1 Used

Code Name _

N Cubic Inches


Page 83 of 146


Req Typ e

Min/Max Usage_

L008 80 Lading Quantity C N0 1/7 Used

Description: Number of units (pieces) of the lading commodity

User Note 1: Number of pieces


L009 211 Packaging Form Code C ID 3/3 Used

Description: Code for packaging form of the lading quantity

Code Name _

PCS Pieces

L011 188 Weight Unit Code O ID 1/1 Used

Description: Code specifying the weight unit Code Name

_ K Kilograms L Pounds

Syntax:

P0203 -- If either L002 or L003 are present, then the others are required. P0405 -- If either L004 or L005 are present, then the others are required. P0607 -- If either L006 or L007 are present, then the others are required. P0809 -- If either L008 or L009 are present, then the others are required. C1104 -- If L011 is present, then L004 is required P1315 -- If either L013 or L015 are present, then the others are required.

Semantics: 1. L008 is the number of handling units of the line item tendered to the carrier. 2. L013 can only be used if the code in L009 is PLT, SKD, or SLP. 3. L015 designates whether the carrier will be required to verify the number of units contained on a pallet, slip sheet or skid. Code "Y" indicates that the carrier will be required to verify. Code "N" indicates that the carrier will not be required to verify.

Comments: 1. L013 is used to convey the total number of boxes, cartons, or pieces contained on a pallet, skid, or slip sheet for the line item.

User Note 1:



Page 84 of 146

L4 Measurement Pos: 163 Max: 4


To describe physical dimensions and quantities

Element Summary:

Ref _ Id_ Element Name Req Typ

e Min/Max

Usage _

L401 82 Length Description: Largest horizontal dimension of an object measured when the object is in the upright position User Note 1: Maximum length = 3

M R 1/8 Must use

L402 189 Width M R 1/8 Must

Description: Shorter measurement of the two horizontal use

dimensions measured with the object in the upright position


L403 65 Height M R 1/8 Must

Description: Vertical dimension of an object measured use

when the object is in the upright position User Note 1: Maximum length = 3

L404 90 Measurement Unit Qualifier Description: Code specifying the linear dimensional unit

M ID 1/1 Must use

Code Name _

N Inches

L405 380 Quantity Description: Numeric value of quantity

O R 1/15 Used

Semantics: 1. L406 is the Rounding in Pattern for dimensional shipments.

User Note 1:



Page 85 of 146

L10 Weight Pos: 165 Max: 4


To transmit dimensional information

Element Summary:


_ Req Typ

e Min/Max Usage

_

L1001 81 Weight Description: Numeric value of weight

M R 1/10 Must use

User Note 1: Dimensional weight


M ID 1/2 Must use

Code Name _

A1 Dimensional Weight



_ K Kilograms L Pounds

User Note 1:



Page 86 of 146

SL1 Tariff Reference Pos: 167 Max: 1


To reference details of the tariff used to arrive at applicable rates or charges for customer-requested service

Element Summary:


Req Typ e

Min/Max Usage_

SL101 284 Service Level Code Description: Code indicating the level of transportation service or the billing service offered by the transportation carrier

M ID 2/2 Must use

User Note 1: Refer to Appendix C for a list of service level codes

SL104

320

Scale

C

AN

1/10

Used

Description: A carrier-maintained reference used to further identify a schedule of rates within a tariff

User Note 1: Formerly rate Scale Number or Tariff Agreement Number. Rate Scale Number is the last 4 digits of the bill to account number Rate Zone is provided for outbound US shipments when available.

Rate Zone details are not passed for Us Import shipments. Country to country pricing is used in this shipping scenario.

Format example: – “1234 /A9”

SL107

146

Shipment Method of Payment O

ID

2/2 Used

Description: Code identifying payment terms for transportation charges

Code Name _

PP Bill to Shipper (Prepaid) TP Bill to Party

SL109 210 International/Domestic Code O ID 1/1 Used

Description: Code indicating international or domestic shipment

All valid standard codes are used.

Semantics: 1. SL101 is the service requested by the customer.

Comments: 1. Scale and commodity codes are proprietary codes maintained by the carrier.

2014-03-12 101 v14.01DHL Confidential & Proprietary

Page 87 of 146

User Note 1:

This segment is only shown for shif2ment items.


Page 88 of 146

L1 Rate and Charges

Pos: 175 Max: 1 Detail - Optional

Loop: L1 Elements: 8

To specify rate and charges detail relative to a line item including freight charges, advances, special charges, and entitlements

Element Summary:


_ Req Typ

e Min/Max Usage_


User Note 1: Incrementing number 1 - 30

O N0 1/3 Used

L102 60 Freight Rate

Description: Rate that applies to the specific commodity

User Note 1: Freight rate - if L108 = 400

C R 1/9 Used

Rate used to assess the fee if this is a fee item

L103 122 Rate/Value Qualifier

Description: Code qualifying how to extend charges or interpret value Code Name

VS Various

C ID 2/2 Used

L104 58 Charge

Description: For a line item: freight or special charge; for the total invoice: the total charges -- expressed in the standard monetary denomination for the currency specified User Note 1: Charge amount if this is a shipment item

C N2 1/12 Used

Amount of fee assessed if this is a fee item

User Note 2: Negative signs (-) will not be passed. Invoice credits are expressed by the use of the CN qualifier in the B3A.01element.

L108

150

Special Charge or Allowance Code Description: Code identifying type of special charge or

O

ID

3/3

Used

allowance User Note 1: Refer to Appendix A for a list of Special

Charge Codes for Shipment level charges. Refer to Appendix B for a list of Special Charge Codes for customer level fees.

L112

276

Special Charge Description

O

AN

2/25

Used

Description: Identification of special charge; this data element is used whenever an applicable code cannot be found in data element 150


Page 89 of 146

Ref _ Id_ Element Name Req Typ Min/Max Usage_

_ e

L114 74 Shipment Value Protection Amount Description: Monetary assigned value expressed in the

C N2 2/12 Used

standard monetary denomination for the currencyspecified

User Note 1: Shipment Value Protection value - if L108 ='745' or ‘INS’

L115

122

Rate/Value Qualifier

C

ID

2/2

Used

Description: Code qualifying how to extend charges or interpret value

Code Name _

PS Per Shipment

Syntax:

1. L102 P0203 -- If either L102 or L103 are present, then the others are required. 2. L104 R040506 -- At least one of L104, L105 or L106 is required. 3. L114 P1415 -- If either L114 or L115 are present, then the others are required. 4. L117 P1718 -- If either L117 or L118 are present, then the others are required.

Semantics: 1. L119 is the percent used to determine the charge in L104. 2. L120, if used, indicates the currency for all monetary amounts in this L1 segment. 3. L121 is the origin rated as charge amount.


Page 90 of 146

C3 Currency Pos: 180 Max: 1


To specify the currency being used in the transaction set

Element Summary:


_ Req Typ

e Min/Max Usage_

C301 100 Currency Code Description: Code (Standard ISO) for country in whose currency the charges are specified User Note 1: ISO currency code for the billing currency - will be the same as the payment currency (target currency for currency conversion)


M ID 3/3 Must use

C302 280 Exchange Rate

Description: Value to be used as a multiplier conversion factor to convert monetary value from one currency to another

O R 4/10 Used

C303 100 Currency Code

Description: Code (Standard ISO) for country in whose currency the charges are specified User Note 1: ISO currency code for the payment currency - will be the same as the billing currency (target currency for currency conversion)


O ID 3/3 Used

Semantics: 1. C301 is the billing currency. 2. C303 is the payment currency. 3. C304 is the rated currency.

Comments: 1. Currency is implied by the code for the country in whose currency the monetary amounts are specified.


Page 91 of 146

L3 Total Weight and Charges Pos: 015 Max: 1

Summary - Mandatory Loop: N/A Elements: 4

To specify the total shipment in terms of weight, volume, rates, charges, advances, and prepaid amounts applicable to one or more line items

Element Summary:


_ Req Typ

e Min/Max Usage_

L301 81 Weight Description: Numeric value of weight User Note 1: This data element is only shown for shipment items.

User Note 2: Total chargeable weight

C R 1/10 Used


C ID 1/2 Used

User Note 1: This data element is only shown for shipment items.

Code Name _

B Billed Weight

L305 58 Charge Description: For a line item: freight or special charge; for

O N2 1/12 Used

the total invoice: the total charges -- expressed in thestandard monetary denomination for the currency specified

User Note 1: Total item charges



_ L Pounds

Syntax:

1. L301 P0102 -- If either L301 or L302 are present, then the others are required. 2. L303 P0304 -- If either L303 or L304 are present, then the others are required. 3. L309 P0910 -- If either L309 or L310 are present, then the others are required. 4. L312 C1201 -- If L312 is present, then L301 is required 5. L314 P1415 -- If either L314 or L315 are present, then the others are required. Semantics: 1. L305 is the total charges.


Page 92 of 146

SE Transaction Set Trailer Pos: 045 Max: 1


To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)

Element Summary:


_ Req Typ

e Min/Max Usage_

SE01 96 Number of Included Segments Description: Total number of segments included in a transaction set including ST and SE segments

M N0 1/10 Must use

SE02 329 Transaction Set Control Number

Description: Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set

M AN 4/9 Must use

Comments: 1. SE is the last segment of each transaction set.


Page 93 of 146

GE Functional Group Trailer Pos: Max: 1


To indicate the end of a functional group and to provide control information

Element Summary:


_ Req Typ

e Min/Max Usage_

GE01 97 Number of Transaction Sets Included Description: Total number of transaction sets included in the functional group or interchange (transmission) group terminated by the trailer containing this data element

M N0 1/6 Must use

GE02 28 Group Control Number

Description: Assigned number originated and maintained by the sender

M N0 1/9 Must use

Semantics: 1. The data interchange control number GE02 in this trailer must be identical to the same data element in the associated functional group header, GS06.

Comments: 1. The use of identical data interchange control numbers in the associated functional group header and trailer is designed to maximize functional group integrity. The control number is the same as that used in the corresponding header.


Page 94 of 146

IEA Interchange Control Trailer Pos: Max: 1


To define the end of an interchange of zero or more functional groups and interchange-related control segments

Element Summary:


Req Typ e

Min/Max Usage_

IEA01 I16 Number of Included Functional Groups Description: A count of the number of functional groups included in an interchange

M N0 1/5 Must use

IEA02

I12

Interchange Control Number Description: A control number assigned by the interchange sender

M

N0

9/9 Must use


Page 95 of 146

110DHL Data Wrapping Each record/line in the 110 transaction file output consists of 80 "data" characters. Subsequent data characters are 'wrapped' to the next 80-byte record/line. There are NO non-data "control" characters included in any record/line.

For purposes of optimizing transmission, the 80-byte records/lines are placed into larger multi-record blocks of data for transmission. As these multi-record blocks are created by the communication protocol, 'record separator' communication control characters are inserted between each record/line. These control characters facilitate the de-blocking of the data (breaking the multi-record blocks back into individual records/lines) at the remote site.

The specific control characters used can vary somewhat depending on computing platform and/or communication protocol. The most common are the Carriage Return, Line Feed and New Line characters. The actual hex value of these characters depends on whether the computing platform is EBCDIC based (primarily mainframe) or ASCII (primarily PC and UNIX).

The creation of large multi-record data blocks consisting of multiple individual records separated by control characters is not unique to the 80-byte 'wrapped' X12 format data. Proprietary data formats DHL3 and DHL6 are handled the same way. For transmission purposes, multiple proprietary format records are placed into multi- record blocks with record separator characters in between.


Page 96 of 146

Chapter 13 RDI Proprietary Remittance Format

Data Structure This is a multiple record type format. The Header, Detail and Trailer records start with a one-character record type indicator that is 35 bytes long. One occurrence of the header and trailer record is expected with multiple occurrences of the detail record.

Record Layout: Header Record Field Name Field Type Start End Length Remarks

Header Identification X(1) 1 1 1 Always B Trading Partner ID

X(12) 2 13 12

DHL assigned Trading Partner ID

Payor Name X(10) 14 23 10 Company name Filler X(3) 24 26 3 Always blanks Application ID X(1) 27 27 1 Always R Check Number X(8) 28 35 8 Customer check number


Page 97 of 146

Record Layout: Detail Record Field Name Field Type Start End Length Remarks

Detail ID X(1) 1 1 1 Always D Invoice Number

X(13)

2

14

11

Invoice Number - Always 13 characters - Right Justify - Zero Fill

Invoice Amount

9(7)V99

15

23

9

Amount paid on Invoice - Right Justify - Zero Fill

Filler X(12) 24 35 14 Always blanks

Record Layout: Trailer Record Field Name Field Type Start End Length Remarks

Identification X(1) 1 1 1 Always T Payor Name

X(10) 2 11 10

Company name. Same as Header Record.

Transmitted Amount

9(7)V99 12 20 9

Total amount of items being paid.

Transmitted Items

9(7) 21 27 7

Total number of items being paid.

Check Number

9(8)

28

35

8

Customer check number for this payment. Same as header record.

RDI Proprietary Format Sample File

BTRADINGIDXXXCOMPANY890 R01234567 DABC012345678901123456789 DABC012345678902123456789 DABC012345678903123456789 DABC012345678904123456789 DABC012345678905123456789 DABC012345678906123456789 DABC012345678907123456789 DABC012345678908123456789 DABC012345678909123456789 DABC012345678900123456789 TCOMPANY890123456789777777701234567


Page 98 of 146

Chapter 14 RDI 820 Remittance Format

Data Structure ANSI X 12 Payment Order/Remittance Advice Transaction 820 Versions 004010..

Special Notes:

Terminators

The segment terminator for the Electronic Remittance files should always be a tilde (~).

The field delimiter should always be an asterisk (*).

Data Presentation:

Data should always be unwrapped prior to sending to DHL

Control Record - The FIRST record is an 80-byte control record

RA Functional Group - To indicate the beginning of a functional group and to provide control information

ISA Interchange Control Header - To start and identify an interchange of zero or more functional groups and interchange-related control segments

GS Functional Group Header - To indicate the beginning of a functional group and to provide control information

ST Transaction Set Header - To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)

BPR Beginning Segment for Payment Order/Remittance Advice - To indicate the beginning of a Payment Order/Remittance Advice Transaction Set and total payment amount, or to enable related transfer of funds and/or information from payer to payee to occur

TRN Trace - To uniquely identify a transaction to an application

REF Reference Identification - To specify identifying information

DTM Date/Time Reference - To specify pertinent dates and times

Loop N1 - To identify a party by type of organization, name, and code

N1 Name - Payer - To identify a party by type of organization, name, and code


Page 99 of 146

N1 Name - Payee - To identify a party by type of organization, name, and code

Loop ENT - To designate the entities which are parties to a transaction and specify a reference meaningful to those entities.

ENT Entity - To designate the entities which are parties to a transaction and specify a reference meaningful to those entities.

Loop NM1 - To supply the full name of an individual or organizational entity

NM1 Individual or Organizational Name - Payer - To supply the full name of an individual or organizational entity

NM1 Individual or Organizational Name - Payee - To supply the full name of an individual or organizational entity

Loop NM1 - To supply the full name of an individual or organizational entity

RMR Remittance Advice Accounts Receivable Open Item Reference

REF Reference Identification - To specify identifying information

DTM Date/Time Reference - To specify pertinent dates and times

Loop ADX - To convey accounts-payable adjustment information for the purpose of cash application, including payer-generated debit/credit memos

ADX Adjustment - To convey accounts-payable adjustment information for the purpose of cash application, including payer-generated debit/credit memos. Adjustments must be requested at the shipment level.

NTE Note/Special Instruction - To transmit information in a free-form format, if necessary, for comment or special instruction

SE Transaction Set Trailer - To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)

GE Functional Group Trailer - To define the end of an interchange of zero or more functional groups and interchange-related control segments

IEA Interchange Control Trailer - To define the end of an interchange of zero or more functional groups and interchange-related control segments


Page 100 of 146

RA Functional Group 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.

Not Defined: Pos Id Segment Name Req Max Use Repeat Notes Usage

ISA Interchange Control Header M 1 Must use

GS Functional Group Header M 1 Must use

Heading:

Pos Id Segment Name Req Max Use Repeat Notes Usage 010 ST Transaction Set Header M 1 Must use 020 BPR Beginning Segment for

Payment Order/Remittance Advice

M 1 Must use

035 TRN Trace M 1 C1/035 Must use 050 REF Reference Identification O >1 Used 060 DTM Date/Time Reference O >1 Used

LOOP ID - N1 >1 C1/070L 070 N1 Name - Payer M 1 C1/070 Used 070 N1 Name - Payee O 1 C1/070 Used

Detail:

Pos Id Segment Name Req Max Use Repeat Notes Usage LOOP ID - ENT >1 CN2/010L

010 ENT Entity M 1 CN2/010 Used

LOOP ID - NM1 >1 C2/020L 020 NM1 Individual or Organizational

Name - Payer 020 NM1 Individual or Organizational

Name - Payee

O 1 C2/020 Used O 1 C2/020 Used

LOOP ID - RMR >1 C2/150L 150 RMR Remittance Advice

Accounts Receivable Open Item Reference

M 1 C2/150 Used

170 REF Reference Identification O >1 Used 180 DTM Date/Time Reference O >1 Used

LOOP ID - ADX >1 C2/210L 210 ADX Adjustment C 1 C2/210 Used 220 NTE Note/Special Instruction O >1 Used

Summary: Pos Id Segment Name Req Max Use Repeat Notes Usage 010 SE Transaction Set Trailer M 1 Must use


Page 101 of 146

Not Defined: Pos Id Segment Name Req Max Use Repeat Notes Usage

GE Functional Group Trailer M 1 Must useIEA Interchange Control Trailer M 1 Must use

Notes: 2/010L The ENT loop is for vendor or consumer third party consolidated payments. 2/010 The ENT loop is for vendor or consumer third party consolidated payments.

Comments: 1/035 The TRN segment is used to uniquely identify a payment order/remittance advice. 1/070L The N1 loop allows for name/address information for the payer and payee which would be utilized to

address remittance(s) for delivery. 1/070 The N1 loop allows for name/address information for the payer and payee which would be utilized to

address remittance(s) for delivery. 1/070 The N1 loop allows for name/address information for the payer and payee which would be utilized to

address remittance(s) for delivery. 2/010L ENT09 may contain the payee's accounts receivable customer number. 2/010 ENT09 may contain the payee's accounts receivable customer number. 2/020L Allowing the NM1 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). 2/020 Allowing the NM1 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). 2/020 Allowing the NM1 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). 2/150L Loop RMR is for open items being referenced or for payment on account. 2/150 Loop RMR is for open items being referenced or for payment on account. 2/210L This ADX loop can only contain adjustment information for the immediately preceding RMR segment and

affects the amount (RMR04) calculation. If this adjustment amount is not netted to the immediately preceding RMR, use the outer ADX loop (position 080).

2/210 This ADX loop can only contain adjustment information for the immediately preceding RMR segment and affects the amount (RMR04) calculation. If this adjustment amount is not netted to the immediately preceding RMR, use the outer ADX loop (position 080).


Page 102 of 146

ISA Interchange Control Header Pos: Max: 1


To start and identify an interchange of zero or more functional groups and interchange-related control segments

Element Summary: Ref ISA01

Id I01

Element Name Authorization Information Qualifier

Req M

Type ID

Min/Max 2/2

Usage Not used

Description: Code to identify the type of information in the Authorization Information

General Notes: LITERAL = '00' All valid standard codes are used.

ISA02 I02 Authorization Information M AN 10/10 Not used

Description: Information used for additional identification or authorization of the interchange sender or the data in the interchange; the type of information is set by the Authorization Information Qualifier (I01)

General Notes: LITERAL = ' '

ISA03 I03 Security Information Qualifier M ID 2/2 Not used

Description: Code to identify the type of information in the Security Information

General Notes: LITERAL = '00'

Code Name 00 No Security Information Present (No Meaningful Information in I04)

ISA04 I04 Security Information

Description: This is used for identifying the

M AN 10/10 Not used

security information about the interchangesender or the data in the interchange; the type of information is set by the Security Information Qualifier (I03)

General Notes: LITERAL = ' '

ISA05 I05 Interchange ID Qualifier M ID 2/2 Must use

Description: Qualifier to designate the system/method of code structure used to designate the sender or receiver ID element being qualified

Code Name

ZZ Mutually Defined

ISA06 I06 Interchange Sender ID M AN 15/15 Must use

Description: Identification code published by the sender for other parties to use as the receiver ID to route data to them; the sender always codes this value in the sender ID element

General Notes: Sender ID/Trading Partner ID

ISA07 I05 Interchange ID Qualifier M ID 2/2 Must use


Page 103 of 146

Description: Qualifier to designate the system/method of code structure used to designate the sender or receiver ID element being qualified

Code Name ZZ Mutually Defined

ISA08 I07 Interchange Receiver ID M AN 15/15 Must use

Description: Identification code published by the receiver of the data; When sending, it is used by the sender as their sending ID, thus other parties sending to them will use this as a receiving ID to route data to them

General Notes: LITERAL = 'DHLC' for production. LITERAL = 'DHLT' for test.

ISA09 I08 Interchange Date M DT 6/6 Must use

Description: Date of the interchange General Notes: Date Envelope Generated

ISA10 I09 Interchange Time M TM 4/4 Must use

Description: Time of the interchange General Notes: Time Envelope Generated

ISA11 I10 Interchange Control Standards Identifier M ID 1/1 Must use

Description: Code to identify the agency responsible for the control standard used by the message that is enclosed by the interchange header and trailer All valid standard codes are used.

ISA12 I11 Interchange Control Version Number M ID 5/5 Must use

Description: Code specifying the version number of the interchange control segments

Code Name 00401 Draft Standards for Trial Use Approved for Publication by ASC X12 Procedures

Review Board through October 1997

ISA13 I12 Interchange Control Number

Description: A control number assigned by

M N0 9/9 Must use

the interchange sender

General Notes: Sequential number incremented by 1 for each envelope (IEA02).

ISA14 I13 Acknowledgment Requested M ID 1/1 Must use

Description: Code sent by the sender to request an interchange acknowledgment (TA1)

Code Name 0 No Acknowledgment Requested

ISA15 I14 Usage Indicator M ID 1/1 Must use

Description: Code to indicate whether data enclosed by this interchange envelope is test, production or information

Code Name P Production Data


Page 104 of 146

ISA16 I15 Component Element Separator

Description: Type is not applicable; the

M 1/1 Must use

component element separator is a delimiter and not a data element; this field provides thedelimiter used to separate component dataelements within a composite data structure;this value must be different than the dataelement separator and the segmentterminator

General Notes: A tilde (~) is the segment terminator required by DHL.


Page 105 of 146

GS Functional Group Header Pos: Max: 1


To indicate the beginning of a functional group and to provide control information

Element Summary:

Ref Id Element Name Req Type Min/Max Usage GS01 479 Functional Identifier Code M ID 2/2 Must use

Description: Code identifying a group of application related transaction sets

Code Name RA Payment Order/Remittance Advice (820)

GS02 142 Application Sender's Code

Description: Code identifying party sending

M AN 2/15 Must use

transmission; codes agreed to by tradingpartners

General Notes: Sender ID/Trading Partner ID

GS03 124 Application Receiver's Code M AN 2/15 Must use

Description: Code identifying party receiving transmission; codes agreed to by trading partners

General Notes: LITERAL = 'DHLC' for production. LITERAL = 'DHLT' for test.

GS04 373 Date M DT 8/8 Must use


GS05 337 Time M TM 4/8 Must use

Description: Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, orHHMMSSD, or HHMMSSDD, where H = hours (00-23), M = minutes (00-59), S = integer seconds (00-59) and DD = decimal seconds; decimal seconds are expressed as follows: D = tenths (0-9) and DD = hundredths (00-99)

General Notes: Format = HHMM where H = hours (00-23), M = minutes (00-59)

GS06 28 Group Control Number M N0 1/9 Must use


General Notes: Sequential number assignedby the Sender. Equal to GE02.

GS07 455 Responsible Agency Code M ID 1/2 Must use

Description: Code identifying the issuer of the standard; this code is used in conjunction with Data Element 480


Page 106 of 146

Code Name X Accredited Standards Committee X12

GS08 480 Version / Release / Industry Identifier Code

Description: Code indicating the version,

M AN 1/12 Must use

release, subrelease, and industry identifier of the EDI standard being used, including theGS and GE segments; if code in DE455 inGS segment is X, then in DE 480 positions 1-3 are the version number; positions 4-6 arethe release and subrelease, level of theversion; and positions 7-12 are the industry ortrade association identifiers (optionallyassigned by user); if code in DE455 in GS

segment is T, then other formats are allowed

Code Name 004010 Draft Standards Approved for Publication by ASC X12 Procedures Review

Board through October 1997

Semantics:

1. GS04 is the group date. 2. GS05 is the group time. 3. The data interchange control number GS06 in this header must be identical to the same data element in the

associated functional group trailer, GE02.

Comments:

1. A functional group of related transaction sets, within the scope of X12 standards, consists of a collection of similar transaction sets enclosed by a functional group header and a functional group trailer.


Page 107 of 146

ST Transaction Set Header Pos: 010 Max: 1


To indicate the start of a transaction set and to assign a control number

Element Summary:

Ref Id Element Name Req Type Min/Max Usage ST01 143 Transaction Set Identifier Code M ID 3/3 Must use

Description: Code uniquely identifying a Transaction Set

Code Name 820 Payment Order/Remittance Advice

ST02 329 Transaction Set Control Number

Description: Identifying control number that

M AN 4/9 Must use

must be unique within the transaction setfunctional group assigned by the originator fora transaction set

General Notes: Number assigned by the Sender. Equal to SE02.

Semantics: 1. The transaction set identifier (ST01) used by the translation routines of the interchange partners to select the

appropriate transaction set definition (e.g., 810 selects the Invoice Transaction Set).


Page 108 of 146

BPR Beginning Segment for Payment Order/Remittance Advice Pos: 020 Max: 1

- Mandatory Loop: N/A Elements:16

To indicate the beginning of a Payment Order/Remittance Advice Transaction Set and total payment amount, or to enable related transfer of funds and/or information from payer to payee to occur

Element Summary: Ref Id Element Name Req Type Min/Max Usage BPR01 305 Transaction Handling Code M ID 1/2 Must use

Description: Code designating the action to be taken by all parties

Code Name C Payment Accompanies Remittance Advice I Remittance Information Only

BPR02 782 Monetary Amount

Description: Monetary amount

M R 1/18 Must use

General Notes: Total Payment Amount.

BPR03 478 Credit/Debit Flag Code M ID 1/1 Must use

Description: Code indicating whether amount is a credit or debit

Code Name

C Credit

BPR04 591 Payment Method Code M ID 3/3 Must use

Description: Code identifying the method for the movement of payment instructions

Code Name

ACH Automated Clearing House (ACH) CHK Check

BPR05 812 Payment Format Code O ID 1/10 Used

Description: Code identifying the payment format to be used

Code Name CCD Cash Concentration/Disbursement (CCD) (ACH) CCP Cash Concentration/Disbursement plus Addenda (CCD+) (ACH) CTX Corporate Trade Exchange (CTX) (ACH) PBC Commercial/Corporate Check

BPR06 506 (ODFI) ID Number Qualifier X ID 2/2 Used

Description: Code identifying the type of identification number of Depository Financial Institution (DFI)

Code Name 01 ABA Transit Routing Number Including Check Digits (9 digits)

BPR07 507 (ODFI) Identification Number X AN 3/12 Used

Description: Depository Financial Institution (DFI) identification number

General Notes: Sender's Bank ABA Code.


Page 109 of 146

BPR08 569 Account Number Qualifier

Description: Code indicating the type of account

O ID 1/3 Used

Code Name DA Demand Deposit

BPR09 508 Account Number X AN 1/35 Used

Description: Account number assigned General Notes: Sender's Demand Deposit

Account (DDA) Number. Provided when utilizing a CTX 820 that is sent with funds.

BPR10 509 Originating Company Identifier O AN 10/10 Used

Description: 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

General Notes: Sender's Company Tax ID.

BPR11 510 Originating Company Supplemental Code O AN 9/9 Not used

Description: A code defined between the originating company and the originating depository financial institution (ODFI) that uniquely identifies the company initiating the transfer instructions

BPR12 506 (RDFI) ID Number Qualifier X ID 2/2 Used

Description: Code identifying the type of identification number of Depository Financial Institution (DFI)

Code Name 01 ABA Transit Routing Number Including Check Digits (9 digits)

BPR13 507 (RDFI) Identification Number

Description: Depository Financial Institution

X AN 3/12 Used

(DFI) identification number

General Notes: Receiver's Bank ABA code. This will be provided by the DHL Site Activation team once testing is completed.

BPR14 569 Account Number Qualifier O ID 1/3 Used

Description: Code indicating the type of account

Code Name DA Demand Deposit

BPR15 508 Account Number

Description: Account number assigned

X AN 1/35 Used

General Notes: Receiving Company's Account Number. This will be provided by the DHL Site Activation team once testing is completed.


Page 110 of 146

BPR16 373 Date

Description: Date expressed as CCYYMMDD General Notes: Expected day of good funds.

O DT 8/8 Used

Syntax Rules:

1. P0607 - If either BPR06 or BPR07 is present, then the other is required. 2. C0809 - If BPR08 is present, then BPR09 is required. 3. P1213 - If either BPR12 or BPR13 is present, then the other is required. 4. C1415 - If BPR14 is present, then BPR15 is required. 5. P1819 - If either BPR18 or BPR19 is present, then the other is required. 6. C2021 - If BPR20 is present, then BPR21 is required.

Semantics:

1. BPR02 specifies the payment amount. 2. When using this transaction set to initiate a payment, all or some of BPR06 through BPR16 may be required,

depending on the conventions of the specific financial channel being used. 3. BPR06 and BPR07 relate to the originating depository financial institution (ODFI). 4. BPR08 is a code identifying the type of bank account or other financial asset. 5. BPR09 is the account of the company originating the payment. This account may be debited or credited

depending on the type of payment order. 6. BPR12 and BPR13 relate to the receiving depository financial institution (RDFI). 7. BPR14 is a code identifying the type of bank account or other financial asset. 8. BPR15 is the account number of the receiving company to be debited or credited with the payment order. 9. BPR16 is the date the originating company intends for the transaction to be settled (i.e., Payment Effective

Date). 10. BPR17 is a code identifying the business reason for this payment. 11. BPR18, BPR19, BPR20 and BPR21, if used, identify a third bank identification number and account to be used

for return items only. 12. BPR20 is a code identifying the type of bank account or other financial asset.


Page 111 of 146

TRN Trace Pos: 035 Max: 1

- Mandatory Loop: N/A Elements:4

To uniquely identify a transaction to an application

Element Summary:

Ref Id Element Name Req Type Min/Max Usage TRN01 481 Trace Type Code M ID 1/2 Must use

Description: Code identifying which transaction is being referenced

Code Name 1 Current Transaction Trace Numbers

TRN02 127 Reference Identification

Description: Reference information as

M AN 1/30 Must use

defined for a particular Transaction Set or asspecified by the Reference Identification Qualifier

General Notes: Sender assigned number to be used as a check number to trace the payment in the Sender and Receiver's records.

TRN03 509 Originating Company Identifier O AN 10/10 Not used

Description: 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

TRN04 127 Reference Identification O AN 1/30 Not used


Semantics: 1. TRN02 provides unique identification for the transaction. 2. TRN03 identifies an organization. 3. TRN04 identifies a further subdivision within the organization.


Page 112 of 146

REF Reference Identification Pos: 050 Max: 1

- Optional Loop: N/A Elements:3

To specify identifying information

Element Summary:

Ref Id Element Name Req Type Min/Max Usage REF01 128 Reference Identification Qualifier M ID 2/3 Must use

Description: Code qualifying the Reference Identification

Code Name CK Check Number TN Transaction Reference Number

REF02 127 Reference Identification

Description: Reference information as

M AN 1/30 Used

defined for a particular Transaction Set or asspecified by the Reference Identification Qualifier

General Notes: Sender assigned number to be used as a check number to trace the payment in the Sender and Receiver's records.

REF03 352 Description X AN 1/80 Not used


Syntax Rules: 1. R0203 - At least one of REF02 or REF03 is required.

Semantics:

1. REF04 contains data relating to the value cited in REF02.


Page 113 of 146

DTM Date/Time Reference Pos: 060 Max: >1

- Optional Loop: N/A Elements:4

To specify pertinent dates and times

Element Summary:

Ref Id Element Name Req Type Min/Max Usage DTM01 374 Date/Time Qualifier M ID 3/3 Not used

Description: Code specifying type of date or time, or both date and time

Code Name 020 Check 097 Transaction Creation

DTM02 373 Date

Description: Date expressed as

X DT 8/8 Not used

CCYYMMDD

DTM03 337 Time X TM 4/8 Not used

Description: Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, or HHMMSSD, or HHMMSSDD, where H = hours (00-23), M = minutes (00-59), S = integer seconds (00-59) and DD = decimal seconds; decimal seconds are expressed as follows: D = tenths (0-9) and DD = hundredths (00-99)

DTM04 623 Time Code O ID 2/2 Not used

Description: Code identifying the time. In accordance with International Standards Organization standard 8601, time can be specified by a + or - and an indication in hours in relation to Universal Time Coordinate (UTC) time; since + is a restricted character, + and - are substituted by P and M in the codes that follow All valid standard codes are used.

Syntax Rules: 1. R020305 - At least one of DTM02, DTM03 or DTM05 is required. 2. C0403 - If DTM04 is present, then DTM03 is required. 3. P0506 - If either DTM05 or DTM06 is present, then the other is required.


Page 114 of 146

Loop N1 Pos: 070 Repeat: >1

Mandatory Loop: N1 Elements: N/A


Loop Summary:

Pos Id Segment Name Req Max Use Repeat Usage070 N1 Name - Payer M 1 Used070 N1 Name - Payee O 1 Used

N1 Name - Payer Pos: 070 Max: 1

Mandatory Loop: N1 Elements: 4


Element Summary:

Ref N101

Id 98

Element Name Entity Identifier Code

Req M

Type ID

Min/Max 2/3

Usage Must use

Description: Code identifying an organizational entity, a physical location, property or an individual

General Notes: Valid codes for Payer: 'PR' or'AK' Valid codes for Payee: 'PE'

Code Name AK Party to Whom Acknowledgment Should Be Sent PR Payer

N102 93 Name

Description: Free-form name

X AN 1/60 Used

General Notes: If N101 = 'PR' or 'AK' providename of company as it appears on a business check in N102. This will enable matching of the check and the remittance file.

If N101 = 'PE' then N102 = 'DHL'

N103 66 Identification Code Qualifier X ID 1/2 Not used


Code Name G Payee Identification Number 91 Assigned by Seller or Seller's Agent


Page 115 of 146

N104 67 Identification Code X AN 2/80 Not used

Description: Code identifying a party or other code

General Notes: Payor account number (if available)

Syntax Rules: 1. R0203 - At least one of N102 or N103 is required. 2. P0304 - If either N103 or N104 is present, then the other is required.

Comments:

1. This segment, used alone, provides the most efficient method of providing organizational identification. To obtain this efficiency the "ID Code" (N104) must provide a key to the table maintained by the transaction processing party.

2. N105 and N106 further define the type of entity in N101.


Page 116 of 146

N1 Name - Payee Pos: 070 Max: 1

Optional Loop: N1 Elements: 4


Element Summary:

Ref N101

Id 98


Req M

Type ID

Min/Max 2/3

Usage Must use


General Notes: Valid codes for Payer: 'PR' or'AK' Valid codes for Payee: 'PE'

Code Name AK Party to Whom Acknowledgment Should Be Sent PR Payer

N102 93 Name

Description: Free-form name

X AN 1/60 Used

General Notes: If N101 = 'PR' or 'AK' providename of company as it appears on a business check in N102. This will enable matching of the check and the remittance file.

If N101 = 'PE' then N102 = 'DHL'

N103 66 Identification Code Qualifier X ID 1/2 Not used


Code Name G Payee Identification Number 91 Assigned by Seller or Seller's Agent

N104 67 Identification Code X AN 2/80 Not used

Description: Code identifying a party or other code

General Notes: Payor account number (if available)

Syntax Rules: 1. R0203 - At least one of N102 or N103 is required. 2. P0304 - If either N103 or N104 is present, then the other is required.

Comments: 1. This segment, used alone, provides the most efficient method of providing organizational identification. To

obtain this efficiency the "ID Code" (N104) must provide a key to the table maintained by the transaction processing party.

2. N105 and N106 further define the type of entity in N101.


Page 117 of 146

Loop ENT Pos: 010 Repeat: >1

Mandatory Loop: ENT Elements: N/A

To designate the entities which are parties to a transaction and specify a reference meaningful to those entities.

Loop Summary:

Pos Id Segment Name Req Max Use Repeat Usage010 ENT Entity M 1 Used 020 Loop NM1 O >1 Used 150 Loop RMR O >1 Used

ENT Entity Pos: 010 Max: 1

Detail - Mandatory Loop: ENT Elements: 1

To designate the entities which are parties to a transaction and specify a reference meaningful to those entities.

Element Summary:

Ref Id Element Name Req Type Min/Max UsageENT01 554 Assigned Number O N0 1/6 Used

Description: Number assigned for differentiation within a transaction set General Notes: LITERAL = '1'

Syntax Rules:

1. P020304 - If either ENT02, ENT03 or ENT04 are present, then the others are required. 2. P050607 - If either ENT05, ENT06 or ENT07 are present, then the others are required. 3. P0809 - If either ENT08 or ENT09 is present, then the other is required.

Comments: 1. This segment allows for the grouping of data by entity/entities at or within a master/masters. A master (e.g., an

organization) can be comprised of numerous subgroups (e.g., entities). This master may send grouped data to another master (e.g., an organization) which is comprised of one or more entities. Groupings are as follows:

2. (1) Single/Single: Only ENT01 is necessary, because there is a single entity (the sending master) communicating with a single entity (the receiving master).

3. (2) Single/Multiple: ENT05, ENT06, and ENT07 would be used to identify the entities within the receiving master. The sending master is a single entity, so no other data elements need be used.

4. (3) Multiple/Single: ENT02, ENT03, and ENT04 would be used to identify the entities within the sending master. The receiving master is a single entity, so no other data elements need be used.

5. (4) Multiple/Multiple: ENT02, ENT03, and ENT04 would be used to identify the entities within the sending master. ENT05, ENT06, and ENT07 would be used to identify the entities within the receiving master.

6. This segment also allows for the transmission of a unique reference number that is meaningful between the


Page 118 of 146

entities.

General Notes: Only one ENT per file (each ST/SE) should be provided.

ENT segment is mandatory for CTX820 per banking requirements.

ENT segment is optional when transmitting the 820 directly to DHL.


Page 119 of 146

Loop NM1 Pos: 020 Repeat: >1

Optional Loop: NM1 Elements: N/A

To supply the full name of an individual or organizational entity

Loop Summary: Pos Id Segment Name Req Max Use Repeat Usage020 NM1 Individual or Organizational Name - Payer O 1 Used 020 NM1 Individual or Organizational Name - Payee O 1 Used

NM1 Individual or Organizational Name - Payer Pos: 020 Max: 1

Detail - Optional Loop: NM1 Elements: 3


Element Summary: Ref NM101

Id 98


Req M

Type ID

Min/Max 2/3

Usage Must use


Code Name

PR Payer

NM102 1065 Entity Type Qualifier M ID 1/1 Must use

Description: Code qualifying the type of entity All valid standard codes are used.

NM103 1035 Name Last or Organization Name O AN 1/35 Used

Description: Individual last name or organizational name

General Notes: If NM102 = 'PR' then providePayer Name in NM103.

If NM102 = 'PE' then provide 'DHL' in NM103.

Syntax Rules: 1. P0809 - If either NM108 or NM109 is present, then the other is required. 2. C1110 - If NM111 is present, then NM110 is required.

Semantics: 1. NM102 qualifies NM103.

Comments:

1. NM110 and NM111 further define the type of entity in NM101.


Page 120 of 146

NM1 Individual or Organizational Name - Payee Pos: 020 Max: 1

Detail - Optional Loop: NM1 Elements: 3


Element Summary:

Ref NM101

Id 98


Req M

Type ID

Min/Max 2/3

Usage Must use


Code Name

PE Payee

NM102 1065 Entity Type Qualifier M ID 1/1 Must use

Description: Code qualifying the type of entity All valid standard codes are used.

NM103 1035 Name Last or Organization Name O AN 1/35 Used

Description: Individual last name or organizational name

General Notes: If NM102 = 'PR' then providePayer Name in NM103.

If NM102 = 'PE' then provide 'DHL' in NM103.

Syntax Rules: 1. P0809 - If either NM108 or NM109 is present, then the other is required. 2. C1110 - If NM111 is present, then NM110 is required.

Semantics:

1. NM102 qualifies NM103.

Comments:

1. NM110 and NM111 further define the type of entity in NM101.


Page 121 of 146

Loop NM1 Pos: 150 Repeat: >1

Optional Loop: RMR Elements: N/A

To specify the accounts receivable open item(s) to be included in the cash application and to convey the appropriate detail

Loop Summary:

Pos 150

Id RMR

Segment Name Remittance Advice Accounts Receivable

Req M

Max Use 1

Repeat UsageUsed

Open Item Reference 170 REF Reference Identification O >1 Used 180 DTM Date/Time Reference O >1 Used 210 Loop ADX O >1 Used

NTE


Page 122 of 146

RMR Remittance Advice Accounts Receivable Open Item Reference

Pos: 150 Max: 1 Detail - Mandatory

Loop: RMR Elements: 6

To specify the accounts receivable open item(s) to be included in the cash application and to convey the appropriate detail

Element Summary:

Ref RMR01

Id 128

Element Name Reference Identification Qualifier

Req M

Type ID

Min/Max 2/3

Usage Used


Spec Usage Exception Notes: This field is Relational in the ANSI standard, but for DHL it is mandatory.

Code Name FR Freight Bill Number IV Seller's Invoice Number

RMR02 127 Reference Identification M AN 1/30 Used

Description: Reference information as defined for a particular Transaction Set or asspecified by the Reference IdentificationQualifier

Spec Usage Exception Notes: This field is Relational in the ANSI standard, but for DHL

it is mandatory. General Notes: DHL Invoice Number.

RMR03 482 Payment Action Code O ID 2/2 Not used

Description: Code specifying the accounts receivable open item(s), if any, to be included

in the cash application. Code Name

PI Pay Item PP Partial Payment

RMR04 782 Monetary Amount M R 1/18 Used

Description: Monetary amount General Notes: Amount paid on invoice number or airway bill.

RMR05 782 Monetary Amount O R 1/18 Not used


RMR06 782 Monetary Amount O R 1/18 Not used


Syntax Rules: 1. P0102 - If either RMR01 or RMR02 is present, then the other is required. 2. P0708 - If either RMR07 or RMR08 is present, then the other is required.


Page 123 of 146

Semantics: 1. If RMR03 is present, it specifies how the cash is to be applied. 2. RMR04 is the amount paid. 3. RMR05 is the amount of invoice (including charges, less allowance) before terms discount (if discount is

applicable) or debit amount or credit amount of referenced items. 4. RMR06 is the amount of discount taken. 5. RMR08, if present, represents an interest penalty payment, amount late interest paid, or amount anticipation.

Comments:

1. Parties using this segment should agree on the content of RMR01 and RMR02 prior to initiating communication.

2. If RMR03 is not present, this is a payment for an open item. If paying an open item, RMR02 must be present. If not paying a specific open item, RMR04 must be present.

3. RMR05 may be needed by some payees to distinguish between duplicate reference numbers.


Page 124 of 146

REF Reference Identification Pos: 170 Max: >1

Detail - Optional Loop: RMR Elements: 3

To specify identifying information

Element Summary:

Ref REF01

Id 128

Element Name Reference Identification Qualifier

Req M

Type ID

Min/Max 2/3

Usage Not used

Description: Code qualifying the Reference Identification All valid standard codes are used.

REF02 127 Reference Identification X AN 1/30 Not used


REF03 352 Description X AN 1/80 Not used


Syntax Rules: 1. R0203 - At least one of REF02 or REF03 is required.

Semantics:

1. REF04 contains data relating to the value cited in REF02.


Page 125 of 146

DTM Date/Time Reference Pos: 180 Max: >1

Detail - Optional Loop: RMR Elements: 6

To specify pertinent dates and times

Element Summary:

Ref DTM01

Id 374

Element Name Date/Time Qualifier

Req M

Type ID

Min/Max 3/3

Usage Not used

Description: Code specifying type of date or time, or both date and time All valid standard codes are used.

DTM02 373 Date X DT 8/8 Not used


DTM03 337 Time X TM 4/8 Not used

Description: Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, orHHMMSSD, or HHMMSSDD, where H = hours (00-23), M = minutes (00-59), S = integer seconds (00-59) and DD = decimal seconds; decimal seconds are expressed as follows: D = tenths (0-9) and DD = hundredths (00-99)

DTM04 623 Time Code O ID 2/2 Not used

Description: Code identifying the time. In accordance with International Standards Organization standard 8601, time can be specified by a + or - and an indication in hours in relation to Universal Time Coordinate (UTC) time; since + is a restricted character, + and - are substituted by P and M in the codes that follow All valid standard codes are used.

DTM05 1250 Date Time Period Format Qualifier X ID 2/3 Not used

Description: Code indicating the date format, time format, or date and time format All valid standard codes are used.

DTM06 1251 Date Time Period X AN 1/35 Not used

Description: Expression of a date, a time, or range of dates, times or dates and times

Syntax Rules: 1. R020305 - At least one of DTM02, DTM03 or DTM05 is required. 2. C0403 - If DTM04 is present, then DTM03 is required. 3. P0506 - If either DTM05 or DTM06 is present, then the other is required.


Page 126 of 146

Loop ADX Pos: 210 Repeat: >1

Optional Loop: ADX Elements: N/A

To convey accounts-payable adjustment information for the purpose of cash application, including payer-generated debit/credit memos

Loop Summary:

Pos Id Segment Name Req Max Use Repeat Usage 210 ADX Adjustment C 1 Used 220 NTE Note/Special Instruction O >1 Used

General Notes: The ADX segment is used to list Airbill numbers that are being short paid/adjusted and the reason for the short payment/adjustment. These ADX records are extracted separately from the remittance payment data, therefore you must list the Airbill number in the ADX04 and you must use standard ANSII codes (data element 426) in the ADX02 to provide the reason of the short payment/adjustment. Do not put ZZ in ADX02, as we must have a valid reason code that provides an explanation for the short payment/adjustment.

Please add the NTE segment to give a more detailed explanation of reason for adjustment

Adjustments must be requested at the shipment level.


Page 127 of 146

ADX Adjustment Pos: 210 Max: 1

Detail - Conditional Loop: ADX Elements: 4

To convey accounts-payable adjustment information for the purpose of cash application, including payer-generated debit/credit memos. All adjustments must be submitted at the shipment level.

Element Summary:

Ref ADX01

Id 782

Element Name Monetary Amount

Req M

Type R

Min/Max 1/18

Usage Must use

Description: Monetary amount General Notes: Amount paid if different from

amount invoiced.

ADX02 426 Adjustment Reason Code M ID 2/2 Must use

Description: Code indicating reason for debit or credit memo or adjustment to invoice, debit or credit memo, or payment

General Notes: Reason code for the short pay/adjustment. Please note that 'ZZ' is not a valid reason code.

Code Name 01 Pricing Error 17 Required Data Missing 18 Not Company Bill 19 Duplicate Billing 20 Balance Due Declined 22 Weight Error 29 Fee Incorrect 30 Delivery Charge Incorrect 31 Pickup Charge Incorrect 32 Oversize Premium Invalid 34 Declared Value Incorrect 37 Dimensions Incorrect 38 Service Incorrect 39 Shipper/Consignee reference number missing 73 Bill of Lading not Received A9 Proof of Delivery Not Received D1 Transfer Between Accounts H2 Payment Previously Sent VO Void

ADX03 128 Reference Identification Qualifier


Code Name AW Air Waybill Number

M ID 2/3 Used


Page 128 of 146

ADX04 127 Reference Identification

Description: Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier General Notes: DHL Airway Bill Number

M AN 1/30 Used

Syntax Rules:

1. P0304 - If either ADX03 or ADX04 is present, then the other is required.

Semantics:

1. ADX01 specifies the amount of the adjustment and must be signed if negative. If negative, it reduces the payment amount; if positive, it increases the payment amount.

2. ADX02 specifies the reason for claiming the adjustment. 3. ADX03 and ADX04 specify the identification of the adjustment.

General Notes: The ADX segment is required if invoice or airway bill is short paid or adjusted.


Page 129 of 146

NTE Note/Special Instruction Pos: 220 Max: >1

Detail - Optional Loop: ADX Elements: 2

To transmit information in a free-form format, if necessary, for comment or special instruction

Element Summary:

Ref NTE01

Id 363

Element Name Note Reference Code

Req O

Type ID

Min/Max 3/3

UsageUsed

Description: Code identifying the functional area or purpose for which the note applies

General Notes: Used to give a text description of the reason or adjustment

Code Name ZZZ Mutually Defined

NTE02 352 Description

Description: A free-form description to clarify

M AN 1/80 Must use

the related data elements and their content General Notes: Text Description of Reason

For Adjustment. Used to provide a more detailed description of an adjustment made in the previous RMR and ADX segments.

DHL's systems only read the first 41 characters of NTE02.

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.


Page 130 of 146

SE Transaction Set Trailer Pos: 010 Max: 1


To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)

Element Summary:

Ref SE01

Id 96

Element Name Number of Included Segments

Req M

Type N0

Min/Max 1/10

Usage Must use

Description: Total number of segments included in a transaction set including ST and SE segments

SE02 329 Transaction Set Control Number M AN 4/9 Must use

Description: Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set

General Notes: Equal to ST02.

Comments: 1. SE is the last segment of each transaction set.


Page 131 of 146

GE Functional Group Trailer Pos: Max: 1

Not Defined - Mandatory Loop: N/A Elements: 2

To indicate the end of a functional group and to provide control information

Element Summary:

Ref GE01

Id 97

Element Name Number of Transaction Sets Included

Req M

Type N0

Min/Max 1/6

Usage Must use

Description: Total number of transaction sets included in the functional group or interchange (transmission) group terminated by the trailer containing this data element

GE02 28 Group Control Number M N0 1/9 Must use


General Notes: Equal to GS06

Semantics: 1. The data interchange control number GE02 in this trailer must be identical to the same data element in the

associated functional group header, GS06.

Comments:

1. The use of identical data interchange control numbers in the associated functional group header and trailer is designed to maximize functional group integrity. The control number is the same as that used in the corresponding header.


Page 132 of 146

IEA Interchange Control Trailer Pos: Max: 1

Not Defined - Mandatory Loop: N/A Elements: 2

To define the end of an interchange of zero or more functional groups and interchange-related control segments

Element Summary:

Ref IEA01

Id I16

Element Name Number of Included Functional Groups

Req M

Type N0

Min/Max 1/5

Usage Must use

Description: A count of the number of functional groups included in an interchange

IEA02 I12 Interchange Control Number M N0 9/9 Must use

Description: A control number assigned by the interchange sender

General Notes: Equal to ISA13.


Page 133 of 146

820 Sample File GS*RA*ABC CO*DHLC*YYYYMMDD*HHMM*00001*T*004010\

(name) (create date &(time) (version)

ST*820*000100001\

BPR*C*$$$$$.$$*C*ACH*CTX*01*123456789*DA*123456789*12345678**01*053100494*DA*8736000912 *YYYYMMDD\

(total amt) (sender bank ABA) (sender DDA #) (sender tax ID) (AFC bank ABA #) (AFC acct #) (pymt date)

REF*TN*12345678\ Check/trace # can be 00000000

(check or trace #) 1 to 8 characters long 0 fill - right justify

DTM*108*YYYYMMDD\ Date is not verified by DHL,

(date pymt sent) so it can be the date the file was created, or a standard set date

N1*PR*ABC CO\ Payer Name - Mandatory Segment

or (name) AK

N1*PE*DHL EXPRESS\ Payee Name - Optional Segment

(name) ENT*1\ Beginning of Loop structure

NM1*PE*DHL EXPRESS\

RMR*FR*00123456789**20000.00\ RMR segment: ADX*10.00*30*FR*00123456789\ Invoice/Airbill # is 11 characters long, RMR*FR*03213054769**4013.00\ 0 fill, & right justify RMR*FR*000H4621319**700.79\ Amount is 1 to 15 characters long ADX*15.30*30*FR*000H4621319\ ADX segment: NTE*ZZ*more detailed explanation for ADX adjustment Appears below the RMR segment it is referring to.

listed in an

record.

NTE segment: DHL reads the first 41 characters NTE segment that follows an ADX

ADX & NTE appear below the RMR segment it is referring to.

SE*123456*000100001\ # of seq. includes the ST & SE

(total #) (same as ST02) 1 to 6 characters long (of seq)

GE*123456*00001\

(# of sets) (same as GS06) # of sets is 1 to 6 characters long


Page 134 of 146

Appendix A: Special Charge Codes for Shipment Level Charges

Please note that charge code information is updated

quarterly and can be found at:

EC Portal web address: https://ecportal.dhl-usa.com/cehttp/html/main.htm

Mailbox ID: EDISPECS Password: EDISPECS

(It is the customer’s responsibility to check for these updates)


Page 135 of 146

Appendix B: Special Charge Codes for Customer Level Fees

Code Description

355 Document Retrieval Fee (Extra Copies and Mailings)

PUC Scheduled Pickup Fee

593 Re-Invoice Fee (Re-bill Charge)

LPC Late Payment Charge

RHM Equipment Usage Fee (Recurring Hardware Maintenance Charge)

TPA Low Usage Fee (Carrier Equipment Pool Charge)

WFT PROD No Freight (Wasted/Futile Trip)


Page 136 of 146

Appendix C: Service Level Codes

* Note: (Document or Non Document information noted in package type field)

Code Description

9A Express 9 a.m.

AE Air Economy

AC Break Bulk Express

BC Global Mail Business

CG International Ground

CX Express Worldwide

ES Import Express Flex

EU Intra Europe

FC Express Easy

GP Medical Express

IE Express Worldwide

IX Economy Select (EU)

MW Break Bulk Economy

NS Non-Service

ON Domestic Express

PA Express (10:30 A.M)

PB Express Envelope

PN Express (12:00 A.M)

R5 Freight Worldwide

RS Auto Reversals

SA Same Day

ST Domestic Economy Select

ZZ Duty Charge


Page 137 of 146

Appendix D: Rate Zones

Note: For International Rate Zones, refer to your DHL Rates Package or DHL’s Published Rates. Published rates may be found at the DHL website www.dhl.com.


Page 138 of 146

Appendix E: Adjustment Reason Codes

Code Description

01 Pricing Error

17 Required Data Missing

18 Not Company Bill

19 Duplicate Billing

20 Balance Due Declined

22 Weight Error

29 Fee Incorrect

30 Delivery Charge Incorrect

31 Pickup Charge Incorrect

32 Oversize Premium Invalid

34 Declared Value Incorrect

37 Dimensions Incorrect

38 Service Incorrect

39 Shipper/Consignee reference Number Missing

73 Bill of Lading Not Received

A9 Proof of Delivery Not Received

D1 Transfer Between Accounts

H2 Payment Previously Sent

VO Void


Page 139 of 146

Terminology

Term DHL Definition

Account Number A unique number assigned to a DHL customer. Large customers may have multiple account numbers, assigned to different physical locations, department, etc.

Accounting Control Field Customer information hard-coded in the DHL system, at the account number level, that is passed to the EDI invoice.

Shippers Weight The amount of the measured heaviness of a package submitted to DHL by the shipping party. This is typically determined by placing the package on a scale or similar device.

Adjusted Invoice Invoice generated reflecting changes in charges

* Balance due Invoice Invoice generated if partial payment is received by DHL

Chargeable Weight Weight used to calculate the freight charge and is the greater of the actual or dimensional weight.

* Credit Memo An invoice with a negative amount used to apply a credit towards another invoice that has already been mailed out.

* Debit Memo An invoice used to pass an additional charge from another invoice.

Dimensional Weight A value derived by the following formula: (L x W x H)/D, where L is package length, W is package width, H is package height, and D is a dimensional factor (usually 194 for domestic shipments and 166 for international shipments).

Freight Charge Price calculated based on the cost to move a shipment from origin to destination based on chargeable weight.

Item Number An 10 digit number assigned to a shipment or fee

Length The longest side of a package.

* Original Invoice Invoice generated the first time a shipment is billed

* Past Due Invoice Invoice generated after the original invoice was not paid

Piece A physical package.


Page 140 of 146

Trading Partner A customer or third-party entity that is configured to send or receive electronic data with DHL.

Payment Remittance Details which outline how payment should be applied.

*See Chapter 3 and 6 for details on how these are handled via EDI billing.


Page 141 of 146

Revision History

Rev. # Release Date Updated by Reason for Update Status

1.0 10/11/05 Omar Douglas DHL branded baseline document. Approved

1.1 11/16/05 Omar Douglas Updated 110 to include rate zone in SL104 segment, description and examples included.

Approved

1.2 12/22/05 Omar Douglas Added the following special charge codes in Appendix A: 270, 185, ZFF, PSG, PVB, and AGS. Description changes were made to: WAR, 20, HHB.

Approved

1.2.1 1/11/06 Omar Douglas Updated RMT 02 max length from 11 to 12. Description updated to indicate when populated with the airway bill the default is to include preceding zeros.

Approved

1.2.2 5/1/06 Omar Douglas Updated Appendix A to include the following fees:

Fee Description OVR Large Package Fee OVR OVERSIZE 1 OVR OVERSIZE 2 OVR OVERSIZE 3 761 Signature Preferred 761 Adult Signature Required DEL Deliver to Address Only

Approved

1.2.2 9/19/06 Omar Douglas Added Rate Zone “OF. Updated Service Level Descriptions

1.2.2 10/3/06 Omar Douglas Added service level “EU” Approved

1.4 12/18/06 Annie Richardson Updated LX loops to 50,000 Approved


Page 142 of 146

Rev. # Release Date Updated by Reason for Update Status

8.00 11/29/07 Annie Richardson Inclusion of Canadian Postal Codes

Removed information pertaining to credit card payments

Appendix A Charge code Inclusions: 355 MES LFT

375 MRK UPK

390 OAC IAC

685 OFU TER

AAS PAG DEM

ALP PER TAY

BSS PFA CTX

COP SSF TAA

Appendix A Charge code Removals

185

635

Appendix A Charge code Changes:

Old New Fee Description SUR LPF LAB PACK HANDLING

CHARGE DEL HOL SUNDAY/HOLIDAY/AFTER HRS

SRVC PUC HOL SUNDAY/HOLIDAY/AFTER HRS

SRVC DEL 761 DELIVER TO ADDRESS ONLY

635 175 CUSTOMS REGISTRATION 680 140 PROD SERVICE

315 SER DELIVER DUTY PAID SERVICE

8.01 12/5/2008 Annie Richardson Update Service Level codes in Appendix C (page 149)

Remove Appendix A and directed customers to view this on www.dhl- usa.com/idi-updates (page 147)

Updated RDI verbiage to reflect requirement to remit at the shipment level. (pages 111, 140-141)

Updated invoice field requirements in the RDI proprietary mapping to reflect shipment level requirements(page 109)

Updated ADX charge codes (page 140)

Approved


Page 143 of 146

9.2 6/1/2009 Annie Richardson Updated number of dimensional loops in the DHL3 format to 9 occurrences.

Updated the billing schedule

Expanded invoice number field length to 13 in all IDI and RDI formats

Add “Null Value” to description field of elements that will no longer contain data in the DHL3 and DHL6 formats

Updated Adjustment Section to reflect new credit/debit memo processes.

Added section on invoice number methodology

Added requirement for return 997 acknowledgement

Added requirement of segment and field terminators for RDI 820 format

Added requirement to unwrap RDI 820 file prior to sending

Updated invoice presentation types

Added control number information

Removed IDI to RDI information

Updated service level code table

Updated Billing Cycle Section 3.2 to reflect billing based on shipment date (previously delivery based)

Element Change

Bill to Code Deleted receiver qualifier and updated 3 to reflect payer party

Invoice type code Original invoice will be the only type supported

Name Extension line

Data no longer passed

Address Line 2 Will be populated with additional address information if available

Payment Terms NS is the only qualifier that will be used.

Fee Period Type Weekly, Monthly Quarterly, and Annually qualifiers removed.

Receiver Customer Number

Data no longer passed.


Page 144 of 146

Scale Data no longer passed

Rate Zone Data no longer passed

Third Party Account Number


Console to Customer Number


COD Amount Data no longer passed

Weight Code Reweigh, dimmed and actual weight only supported

National Discount Amount in DHL3 and DHL 6 formats

Data will reflect actual shipment discount not national discount amount

Pickup Location

(i.e. drop box, airport etc)


Package Type Letter and Other will only be supported

Shipment Type code

Will only support Express qualifier

9.4 6/1/2009 Annie Richardson Updated the package type in all formats to include qualifiers to note the type of invoice:

DHL110 Format - B3A01 element DHL3 Format - I1 segment starting position 37 DHL6 Format - Starting Position 72

Qualifiers: UO = Original Invoice CN = Credit Memo DR = Debit Memo 21 = Import Invoice

Removed consignee qualifier from the N104

Removed name extension reference in the N102 segment.

9.5 6/1/2009 Annie Richardson Updated SL104 element in the 110 format to reflect that scales and zones will be present for domestic shipments.

Updated Scale element in DHL3 and DHL6 to reflect that scales and zones


Page 145 of 146

will be present.

Corrected DHL3 invoice number length

9.6 7/23/2009 Annie Richardson Updated customer level fee appendix B

Add bill to type F to DHL3 and DHL6

9.7 7/27/09 Annie Richardson Corrected record length of last filler element in DHL6 to 4013

11.0 9/3/10 Annie Richardson DHL3 removed optional AC record shipment level fee adjustments. No longer being passed as of version 9.0

DHL3 removed optional FC record Fee Level Adjustments. No longer being passed as of version 9.0

Clarification in DHL6 position 892 is 3rd

party account number when applicable

Added Appendix E

Changed terminology of “Actual Weight” to “Shippers Weight”

Clarification on invoice type code 21. From Import Invoice to Import Invoice/Duty Invoice

Removed Fax Number for completed setup request forms

Removed CC qualifier in SL1.07 as this is no longer an option as of v9.0

Added ZZ as Duty Charge to Appendix C.

Removed shipment level qualifiers for proprietary and 820 Remittance files.

Changed “Preferred” method of remittance from shipment level to invoice level

Clarification on scheduled updates for Appendix A.

Update to payment remittance address

Removed reference to “$$add card” record

N1.01 removed PU, 77 and RMT qualifiers

Clarification on paper vs electronic invoicing

Clarification on debit and credit memo process

Clarification on invoice numbering convention.

11.2 Removed X1 record from DHL3 as this is data that is not being passed.

Updated billing cycle information

11.3 August 16, 2011 Thomas Lee Clarified descriptions for package type doc and non-doc

Change doc to “Doc (Non-Dutiable

Approved


Page 146 of 146

shipments up to 150 lbs)” for 110, DHL6 and DHL3 specs

Change non-doc to “Non-Doc (Dutiable shipments up to 150 lbs)” for 110, DHL6 and DHL3 specs

12.01 March 5, 2012 Section 5.1 - Secure Protocol updated Approved

12.02 Nov 14, 2012 John Mihaiu Section 2.1 – Appendix Updates

Verbiage regarding new process/location of DHL Charge Codes.

Section 3.1 & 10.0 Format DHL6

Correction to byte count of data format.

Record End/Length corrected.

Section 5.1 – Message Transport Options

Removed AS1 references no longer

supported.

Chapter 12 - IDI 110DHL Format

L4 Measurements

Removed verbiage regarding 9 occurrences. No longer valid as of ANSI X12 version 4010. Max = 4.

Appendix A – Special Charge Codes for Shipment Level Charges

Verbiage regarding new process/location of DHL Charge Codes.

Appendix B– ANSI Code

ANSI code changed from 540 to PUC.

“Scheduled Pickup Fee”

12.03 December 20, 2016 John Mihaiu Appendix B– Description Change

ANSI Description changed for PUC.

“Monthly Pickup Service”


Page 147 of 146

12.03 December 20, 2016 John Mihaiu Appendix A – Special Charge Codes for Shipment Level Charges

Addition/Removals/changes of ANSI codes and descriptions.

Appendix A:

Change

055 Advance Payment

240 BROKER NOTIFICATION

460 Neutral Delivery

480 Printed Invoice

495 Post Clearance Modification

540 Non Standard Pickup

586 Shipment Labeling

600 Shipment Redirect

690 Personal Effects

BND Under Bond Guarantee

CSE Single Clearance

CTX Advanced Payment

CUS Other Government Agency

DTC Elevated Risk

EPS Climate Neutral Services

GAT Other Government Agency

HOL Holiday Delivery

HSC Proof of Idenitity

IAC Other Government Agency

INS Shipment Value Protection

Remove:

550 Preparing Waybill

CLN Spill Cleaning

DTD DIRECT DEBIT DUTY

HDG HOLDING CHARGE

ICE Coolant Material

PEN MITIGATION OF PENALTY

RCL Repeat Delivery Attempt

WHC LOGISTICS SERVICES

dhl invoice data interchange (idi) specification v14 · complete idi customer request form that...

Documents