Ford
/
Payment Order/Remittance Advice
  • Specification
  • EDI Inspector
Import
Stedi maintains this guide based on public documentation from Ford. Contact Ford for official EDI specifications. To report any errors in this guide, please contact us.
Go to EDI Guide Catalog
Ford logo

X12 820 Payment Order/Remittance Advice

X12 Release 3040

This Draft Standard for Trial Use contains the format and establishes the data contents of the Payment Order/Remittance Advice Transaction Set (820) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to make a payment, send a remittance advice, or make a payment and send a remittance advice.

This transaction set can be an order to a financial institution to make a payment to a payee. It can also be a remittance advice identifying the detail needed to perform cash application to the payee's accounts receivable system. The remittance advice can go directly from payer to payee, through a financial institution, or through a third party agent.

Delimiters
  • ~ Segment
  • * Element
  • > Component
EDI sample
    View the latest version of this implementation guide as an interactive webpage
    Powered by
    Build free EDI implementation guides at stedi.com
    Overview
    ISA
    -
    Interchange Control Header
    Max use 1
    Required
    GS
    -
    Functional Group Header
    Max use 1
    Required
    heading
    ST
    010
    Transaction Set Header
    Max use 1
    Required
    BPR
    020
    Beginning Segment for Payment Order/Remittance Advice
    Max use 1
    Required
    NTE
    030
    Note/Special Instruction
    Max use 1
    Optional
    TRN
    035
    Trace
    Max use 1
    Optional
    CUR
    040
    Currency
    Max use 1
    Optional
    REF
    050
    Reference Numbers
    Max use 1
    Optional
    Payee
    GE
    -
    Functional Group Trailer
    Max use 1
    Required
    IEA
    -
    Interchange Control Trailer
    Max use 1
    Required
    ISA

    Interchange Control Header

    RequiredMax use 1

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

    Example
    ISA-01
    I01
    Authorization Information Qualifier
    Required

    Code to identify the type of information in the Authorization Information.

    00
    No Authorization Information Present (No Meaningful Information in I02)
    ISA-02
    I02
    Authorization Information
    Required
    Min 10Max 10

    Information used for additional identification or authorization of the sender or the data in the interchange. The type of information is set by the Authorization Information Qualifier.

    ISA-03
    I03
    Security Information Qualifier
    Required

    Code to identify the type of information in the Security Information.

    00
    No Security Information Present (No Meaningful Information in I04)
    ISA-04
    I04
    Security Information
    Required
    Min 10Max 10

    This is used for identifying the security information about the sender or the data in the interchange. The type of information is set by the Security Information Qualifier.

    ISA-05
    I05
    Interchange ID Qualifier
    Required
    Min 2Max 2

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

    Codes
    ISA-06
    I06
    Interchange Sender ID
    Required
    Min 15Max 15

    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 number in the sender ID element.

    ISA-07
    I05
    Interchange ID Qualifier
    Required
    Min 2Max 2

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

    Codes
    ISA-08
    I07
    Interchange Receiver ID
    Required
    Min 15Max 15

    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.

    ISA-09
    I08
    Interchange Date
    Required
    YYMMDD format

    Date of the interchange.

    ISA-10
    I09
    Interchange Time
    Required
    HHMM format

    Time of the interchange.

    ISA-11
    I10
    Interchange Control Standards Identifier
    Required

    Code to identify the agency responsible for the control standard used by the message that is enclosed by the interchange header and trailer.

    U
    U.S. EDI Community of ASC X12, TDCC, and UCS
    ISA-12
    I11
    Interchange Control Version Number
    Required

    This version number covers the interchange control segments.

    00304
    Draft Standards for Trial Use Approved for Publication by ASC X12 Procedures Review Board through October 1993
    ISA-13
    I12
    Interchange Control Number
    Required
    Min 9Max 9

    This number uniquely identifies the interchange data to the sender. It is assigned by the sender. Together with the sender ID it uniquely identifies the interchange data to the receiver. It is suggested that the sender, receiver, and all third parties be able to maintain an audit trail of interchanges using this number.

    ISA-14
    I13
    Acknowledgment Requested
    Required
    Min 1Max 1

    Code sent by the sender to request an interchange acknowledgment.

    0
    No Acknowledgment Requested
    1
    Interchange Acknowledgment Requested
    ISA-15
    I14
    Test Indicator
    Required
    Min 1Max 1

    Code to indicate whether data enclosed by this interchange envelope is test or production.

    P
    Production Data
    T
    Test Data
    ISA-16
    I15
    Subelement Separator
    Required
    Min 1Max 1

    This is a field reserved for future expansion in separating data element subgroups. (In the interest of a migration to international standards, this must be different from the data element separator).

    >
    Component Element Separator

    Functional Group Header

    RequiredMax use 1

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

    Example
    GS-01
    479
    Functional Identifier Code
    Required

    Code identifying a group of application related Transaction Sets.

    RA
    Payment Order/Remittance Advice (820)
    GS-02
    142
    Application Sender's Code
    Required
    Min 2Max 15

    Code identifying party sending transmission. Codes agreed to by trading partners.

    GS-03
    124
    Application Receiver's Code
    Required
    Min 2Max 15

    Code identifying party receiving transmission. Codes agreed to by trading partners.

    GS-04
    373
    Date
    Required
    YYMMDD format

    Date (YYMMDD).

    GS-05
    337
    Time
    Required
    HHMM, HHMMSS, HHMMSSD, or HHMMSSDD format

    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)

    GS-06
    28
    Group Control Number
    Required
    Min 1Max 9

    Assigned number originated and maintained by the sender.

    GS-07
    455
    Responsible Agency Code
    Required
    Min 1Max 2

    Code used in conjunction with Data Element 480 to identify the issuer of the standard.

    T
    Transportation Data Coordinating Committee (TDCC)
    X
    Accredited Standards Committee X12
    GS-08
    480
    Version / Release / Industry Identifier Code
    Required

    Code indicating the version, release, subrelease, 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 subrelease, 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.

    003040
    Draft Standards Approved for Publication by ASC X12 Procedures Review Board through October 1993

    Heading

    ST
    010

    Transaction Set Header

    RequiredMax use 1

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

    Example
    ST-01
    143
    Transaction Set Identifier Code
    Required

    Code uniquely identifying a Transaction Set.

    • 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).
    820
    X12.4 Payment Order/Remittance Advice
    ST-02
    329
    Transaction Set Control Number
    Required
    Min 4Max 9

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

    BPR
    020

    Beginning Segment for Payment Order/Remittance Advice

    RequiredMax use 1

    (1) To indicate the beginning of a PaymentOrder/Remittance Advice Transaction Set and total payment amount or (2) to enable related transfer of funds and/or information from payer to payee to occur

    Usage notes

    When using this transaction set to initiate a payment, BPR06 through BPR16 may be required, depending on the conventions of the specific financial channel being used.

    Example: BPRI+50940.00CACH01~700000007009B69KA0000~~~~~~010921VEN’

    Example
    If either (DFI) ID Number Qualifier (BPR-06) or (DFI) Identification Number (BPR-07) is present, then the other is required
    If Account Number Qualifier Code (BPR-08) is present, then Account Number (BPR-09) is required
    If Account Number Qualifier Code (BPR-14) is present, then Account Number (BPR-15) is required
    If either (DFI) ID Number Qualifier (BPR-18) or (DFI) Identification Number (BPR-19) is present, then the other is required
    If Account Number Qualifier Code (BPR-20) is present, then Account Number (BPR-21) is required
    BPR-01
    305
    Transaction Handling Code
    Required

    Code designating the action to be taken by all parties.

    I
    Remittance Information Only
    BPR-02
    782
    Monetary Amount
    Required
    Min 1Max 15

    Monetary amount.

    • BPR02 specifies the payment amount.
    BPR-03
    478
    Credit/Debit Flag Code
    Required

    Code indicating whether amount is a credit or debit

    C
    Credit
    D
    Debit
    BPR-04
    591
    Payment Method Code
    Required

    Code identifying the method for the movement of payment instructions

    ACH
    Automated Clearing House (ACH)
    CHK
    Check
    BPR-05
    812
    Payment Format Code
    Optional
    Min 1Max 10

    Code identifying the payment format to be used.

    BPR-06
    506
    (DFI) ID Number Qualifier
    Optional

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

    • When using this transaction set to initiate a payment, BPR06 through BPR16 may be required, depending on the conventions of the specific financial channel being used.
    • BPR06 and BPR07 relate to the originating depository financial institution (ODFI).
    01
    ABA Transit Routing Number Including Check Digits (9 digits)
    02
    Swift Identification (8 or 11 characters)
    BPR-07
    507
    (DFI) Identification Number
    Optional
    Min 3Max 12

    Depository Financial Institution (DFI) identification number.

    BPR-08
    896
    Account Number Qualifier Code
    Optional
    Min 2Max 2

    Code indicating type of bank account or other financial asset

    BPR-09
    508
    Account Number
    Optional
    Min 1Max 35

    Account number assigned.

    • BPR09 is the account of the company originating the payment. This account may be debited or credited depending on the type of payment order.
    Usage notes

    This Ford bank account may be debited or credited depending on the type of payment order.

    BPR-10
    509
    Originating Company Identifier
    Optional
    Min 10Max 10

    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.

    Usage notes

    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, and a user assigned number is 9.

    This segment must equal TRN03.

    BPR-11
    510
    Originating Company Supplemental Code
    Optional
    Min 9Max 9

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

    BPR-12
    506
    (DFI) ID Number Qualifier
    Optional
    Min 2Max 2

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

    • BPR12 and BPR13 relate to the receiving depository financial institution (RDFI).
    BPR-13
    507
    (DFI) Identification Number
    Optional
    Min 3Max 12

    Depository Financial Institution (DFI) identification number.

    BPR-14
    896
    Account Number Qualifier Code
    Optional
    Min 2Max 2

    Code indicating type of bank account or other financial asset

    BPR-15
    508
    Account Number
    Optional
    Min 1Max 35

    Account number assigned.

    • BPR15 is the account number of the receiving company to be debited or credited with the payment order.
    BPR-16
    513
    Effective Entry Date
    Optional
    YYMMDD format

    Date the originating company intends for the transaction to be settled.

    BPR-17
    1048
    Business Function Code
    Optional

    Code identifying the business reason for this payment

    • BPR17 is a code identifying the business reason for the this payment.
    VEN
    Vendor Payment
    BPR-18
    506
    (DFI) ID Number Qualifier
    Optional
    Min 2Max 2

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

    • BPR18, BPR19, BPR20 and BPR21, if used, identify a third bank identification number and account to be used for return items only.
    BPR-19
    507
    (DFI) Identification Number
    Optional
    Min 3Max 12

    Depository Financial Institution (DFI) identification number.

    BPR-20
    896
    Account Number Qualifier Code
    Optional
    Min 2Max 2

    Code indicating type of bank account or other financial asset

    BPR-21
    508
    Account Number
    Optional
    Min 1Max 35

    Account number assigned.

    NTE
    030

    Note/Special Instruction

    OptionalMax use >1

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

    Usage notes

    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.

    Example: NTEPAY YOUR REFERENCE NUMBER 86807’

    Example
    NTE-01
    363
    Note Reference Code
    Optional

    Code identifying the functional area or purpose for which the note applies.

    PAY
    Payables
    NTE-02
    3
    Free Form Message
    Required
    Min 1Max 60

    Free-form text.

    TRN
    035

    Trace

    OptionalMax use 1

    To uniquely identify a transaction to an application.

    • The TRN segment is used to uniquely identify a payment order/remittance advice.
    Usage notes

    This segment is used to uniquely identify this transaction set and to reassociate payment and remittance information that may have been split. This number is unique within an originator’s application. When the payment and remittance are split, this number can be used for reassociation.

    Example: TRN3000013000~9B69KA0000’

    Example
    TRN-01
    481
    Trace Type Code
    Required

    Code identifying which transaction is being referenced.

    1
    Current Transaction Trace Numbers
    2
    Referenced Transaction Trace Numbers
    3
    Financial Reassociation Trace Number

    Payment and remittance are separate.

    TRN-02
    127
    Reference Number
    Required
    Min 1Max 30

    Reference number or identification number as defined for a particular Transaction Set, or as specified by the Reference Number Qualifier.

    • TRN02 provides unique identification for the transaction.
    Usage notes

    Only a check number is sent in this Reference Number.

    TRN-03
    509
    Originating Company Identifier
    Optional
    Min 10Max 10

    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.

    • TRN03 identifies an organization.
    Usage notes

    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, and a user assigned number is 9.

    This segment must equal the Originating Company Identifier which is on the beginning segment.

    TRN-04
    127
    Reference Number
    Optional
    Min 1Max 30

    Reference number or identification number as defined for a particular Transaction Set, or as specified by the Reference Number Qualifier.

    • TRN04 identifies a further subdivision within the organization.
    CUR
    040

    Currency

    OptionalMax use 1

    To specify the currency (dollars, pounds, francs, etc.) used in a transaction

    • The CUR segment does not initiate a foreign exchange transaction.
    Usage notes

    This segment is not used for domestic originator/receiver transactions. Monetary values are assumed to be expressed in the currency of the country of the transaction originator unless this segment is used to specify a different currency.

    Example: CURBYMXP’

    Example
    CUR-01
    98
    Entity Identifier Code
    Required

    Code identifying an organizational entity, a physical location, or an individual

    BY
    Buying Party (Purchaser)
    CUR-02
    100
    Currency Code
    Required

    Code (Standard ISO) for country in whose currency the charges are specified.

    CAD
    Canadian Dollar
    MXP
    Mexican Peso
    USD
    US Dollar
    REF
    050

    Reference Numbers

    OptionalMax use >1

    To specify identifying numbers.

    Example
    At least one of Reference Number (REF-02) or Description (REF-03) is required
    REF-01
    128
    Reference Number Qualifier
    Required
    Min 2Max 2

    Code qualifying the Reference Number.

    REF-02
    127
    Reference Number
    Optional
    Min 1Max 30

    Reference number or identification number as defined for a particular Transaction Set, or as specified by the Reference Number Qualifier.

    REF-03
    352
    Description
    Optional
    Min 1Max 80

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

    N1 Payee
    OptionalMax >1
    Variants (all may be used)
    N1Payer
    N1
    070

    Name

    RequiredMax use 1

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

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

    At least two N1 loops will be used, one containing payer information, one containing payee information, to facilitate remittance delivery and error resolution.

    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.

    Example
    At least one of Name (N1-02) or Identification Code Qualifier (N1-03) is required
    If either Identification Code Qualifier (N1-03) or Identification Code (N1-04) is present, then the other is required
    N1-01
    98
    Entity Identifier Code
    Required

    Code identifying an organizational entity, a physical location, or an individual

    PE
    Payee
    N1-02
    93
    Name
    Optional
    Min 1Max 35

    Free-form name.

    Usage notes

    At least one of N102 or N103 is required. Name of receiving supplier/vendor.

    N1-03
    66
    Identification Code Qualifier
    Optional

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

    92
    Assigned by Buyer or Buyer's Agent
    N1-04
    67
    Identification Code
    Optional
    Min 2Max 17

    Code identifying a party or other code.

    • 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.
    Usage notes

    Ford assigned supplier code.

    N2
    080

    Additional Name Information

    OptionalMax use >1

    To specify additional names or those longer than 35 characters in length

    Usage notes

    Example: N2~CENTRAL ACCOUNTING SERVICES’

    Example
    N2-01
    93
    Name
    Required
    Min 1Max 35

    Free-form name.

    Usage notes

    Ford usage -
    "Central Accounting Services"
    "Kentucky Truck Plant"
    "Hermosillo Stamping and Assembly Plant"
    "Ford of Mexico Operations"

    N2-02
    93
    Name
    Optional
    Min 1Max 35

    Free-form name.

    N3
    090

    Address Information

    OptionalMax use >1

    To specify the location of the named party

    Example
    N3-01
    166
    Address Information
    Required
    Min 1Max 35

    Address information

    N3-02
    166
    Address Information
    Optional
    Min 1Max 35

    Address information

    N4
    100

    Geographic Location

    OptionalMax use 1

    To specify the geographic place of the named party

    Example
    N4-01
    19
    City Name
    Optional
    Min 2Max 30

    Free-form text for city name.

    • A combination of either N401 through N404 (or N405 and N406) may be adequate to specify a location.
    N4-02
    156
    State or Province Code
    Optional
    Min 2Max 2

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

    • N402 is required only if city name (N401) is in the USA or Canada.
    N4-03
    116
    Postal Code
    Optional
    Min 3Max 9

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

    N4-04
    26
    Country Code
    Optional
    Min 2Max 3

    Code identifying the country.

    REF
    110

    Reference Numbers

    OptionalMax use >1

    To specify identifying numbers.

    Example
    At least one of Reference Number (REF-02) or Description (REF-03) is required
    REF-01
    128
    Reference Number Qualifier
    Required
    Min 2Max 2

    Code qualifying the Reference Number.

    REF-02
    127
    Reference Number
    Optional
    Min 1Max 30

    Reference number or identification number as defined for a particular Transaction Set, or as specified by the Reference Number Qualifier.

    REF-03
    352
    Description
    Optional
    Min 1Max 80

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

    PER
    120

    Administrative Communications Contact

    OptionalMax use >1

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

    Usage notes

    Example: PERAP~~TE734-525-7800’

    Example
    If either Communication Number Qualifier (PER-03) or Communication Number (PER-04) is present, then the other is required
    If either Communication Number Qualifier (PER-05) or Communication Number (PER-06) is present, then the other is required
    PER-01
    366
    Contact Function Code
    Required

    Code identifying the major duty or responsibility of the person or group named.

    AP
    Accounts Payable Department
    PER-02
    93
    Name
    Optional
    Min 1Max 35

    Free-form name.

    Usage notes

    Name is Accounts Payable.

    PER-03
    365
    Communication Number Qualifier
    Optional

    Code identifying the type of communication number.

    TE
    Telephone
    PER-04
    364
    Communication Number
    Optional
    Min 1Max 80

    Complete communications number including country or area code when applicable.

    Usage notes

    Example of Communication Number: "313 458 0165".

    PER-05
    365
    Communication Number Qualifier
    Optional
    Min 2Max 2

    Code identifying the type of communication number.

    PER-06
    364
    Communication Number
    Optional
    Min 1Max 80

    Complete communications number including country or area code when applicable.

    N1 Payer
    OptionalMax >1
    Variants (all may be used)
    N1Payee
    N1
    070

    Name

    RequiredMax use 1

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

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

    At least two N1 loops will be used, one containing payer information, one containing payee information, to facilitate remittance delivery and error resolution.

    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.

    Example: N1PRFORD MOTOR COMPANY92B69KA’

    Example
    At least one of Name (N1-02) or Identification Code Qualifier (N1-03) is required
    If either Identification Code Qualifier (N1-03) or Identification Code (N1-04) is present, then the other is required
    N1-01
    98
    Entity Identifier Code
    Required

    Code identifying an organizational entity, a physical location, or an individual

    PR
    Payer
    N1-02
    93
    Name
    Optional
    Min 1Max 35

    Free-form name.

    Usage notes

    At least one of N102 or N103 is required. Name of the Ford paying activity.

    N1-03
    66
    Identification Code Qualifier
    Optional

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

    92
    Assigned by Buyer or Buyer's Agent
    N1-04
    67
    Identification Code
    Optional
    Min 2Max 17

    Code identifying a party or other code.

    • 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.
    Usage notes

    Code of the Ford paying activity.

    N2
    080

    Additional Name Information

    OptionalMax use >1

    To specify additional names or those longer than 35 characters in length

    Usage notes

    Example: N2~CENTRAL ACCOUNTING SERVICES’

    Example
    N2-01
    93
    Name
    Required
    Min 1Max 35

    Free-form name.

    Usage notes

    Ford usage -
    "Central Accounting Services"
    "Kentucky Truck Plant"
    "Hermosillo Stamping and Assembly Plant"
    "Ford of Mexico Operations"

    N2-02
    93
    Name
    Optional
    Min 1Max 35

    Free-form name.

    N3
    090

    Address Information

    OptionalMax use >1

    To specify the location of the named party

    Example
    N3-01
    166
    Address Information
    Required
    Min 1Max 35

    Address information

    N3-02
    166
    Address Information
    Optional
    Min 1Max 35

    Address information

    N4
    100

    Geographic Location

    OptionalMax use 1

    To specify the geographic place of the named party

    Example
    N4-01
    19
    City Name
    Optional
    Min 2Max 30

    Free-form text for city name.

    • A combination of either N401 through N404 (or N405 and N406) may be adequate to specify a location.
    N4-02
    156
    State or Province Code
    Optional
    Min 2Max 2

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

    • N402 is required only if city name (N401) is in the USA or Canada.
    N4-03
    116
    Postal Code
    Optional
    Min 3Max 9

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

    N4-04
    26
    Country Code
    Optional
    Min 2Max 3

    Code identifying the country.

    REF
    110

    Reference Numbers

    OptionalMax use >1

    To specify identifying numbers.

    Example
    At least one of Reference Number (REF-02) or Description (REF-03) is required
    REF-01
    128
    Reference Number Qualifier
    Required
    Min 2Max 2

    Code qualifying the Reference Number.

    REF-02
    127
    Reference Number
    Optional
    Min 1Max 30

    Reference number or identification number as defined for a particular Transaction Set, or as specified by the Reference Number Qualifier.

    REF-03
    352
    Description
    Optional
    Min 1Max 80

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

    PER
    120

    Administrative Communications Contact

    OptionalMax use >1

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

    Usage notes

    Example: PERAP~~TE734-525-7800’

    Example
    If either Communication Number Qualifier (PER-03) or Communication Number (PER-04) is present, then the other is required
    If either Communication Number Qualifier (PER-05) or Communication Number (PER-06) is present, then the other is required
    PER-01
    366
    Contact Function Code
    Required

    Code identifying the major duty or responsibility of the person or group named.

    AP
    Accounts Payable Department
    PER-02
    93
    Name
    Optional
    Min 1Max 35

    Free-form name.

    Usage notes

    Name is Accounts Payable.

    PER-03
    365
    Communication Number Qualifier
    Optional

    Code identifying the type of communication number.

    TE
    Telephone
    PER-04
    364
    Communication Number
    Optional
    Min 1Max 80

    Complete communications number including country or area code when applicable.

    Usage notes

    Example of Communication Number: "313 458 0165".

    PER-05
    365
    Communication Number Qualifier
    Optional
    Min 2Max 2

    Code identifying the type of communication number.

    PER-06
    364
    Communication Number
    Optional
    Min 1Max 80

    Complete communications number including country or area code when applicable.

    Detail

    ENT Loop
    OptionalMax >1
    ENT
    010

    Entity

    RequiredMax use 1

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

    • ENT09 may contain the payee's accounts receivable customer number.
    Usage notes

    If there are any segments in the detail area, the ENT segment is mandatory to indicate a loop start. In a single-to-single entity relationship, the ENT segment is used as a placeholder and only the ENT01 is required. In other than single-to-single relationships, elements ENT02 - ENT07 are used to designate sub-entities of the parties.

    This segment allows for the grouping of data by entity/entities at or within a master/masters. A master (e.g., an organization) can be comprised of numerous subgroups (e.g., entities.) This master may send grouped data to another master (e.g., an organization) which is comprised of one or more entities. Groupings are as follows:

    (1) Single/Single: Only ENT01 is necessary because there is a single entity (the sending master) communicating with a single entity (the receiving master.)
    (2) Single/Multiple: ENT05, ENT06, and ENT07 would be used to identify the entities within the receiving master. The sending master is a single entity so no other data elements need be used.
    (3) Multiple/Single: ENT02, ENT03, and ENT04 would be used to identify the entities within the sending master. The receiving master is a single entity so no other data elements need be used.
    (4) Multiple/Multiple: ENT02, ENT03, and ENT04 would be used to identify the entities within the sending master. ENT05, ENT06, and ENT07 would be used to identify the entities within the receiving master.

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

    Example: ENT1~~~~SU92~B816N’

    Example
    If either Entity Identifier Code (ENT-05), Identification Code Qualifier (ENT-06) or Identification Code (ENT-07) are present, then the others are required
    ENT-01
    554
    Assigned Number
    Optional
    Min 1Max 6

    Number assigned for differentiation within a transaction set.

    Usage notes

    "1" - Initial use to indicate loop start. Will increase usage with introduction of "Ship From" information resulting in use of ENT05 - ENT07 segments.

    ENT-05
    98
    Entity Identifier Code
    Optional

    Code identifying an organizational entity, a physical location, or an individual

    Usage notes

    If any of ENT05, ENT06, or ENT07 are present, then all are required.

    SU
    Supplier/Manufacturer
    ENT-06
    66
    Identification Code Qualifier
    Optional
    Min 1Max 2

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

    ENT-07
    67
    Identification Code
    Optional
    Min 2Max 17

    Code identifying a party or other code.

    N1 Payee
    OptionalMax >1
    Variants (all may be used)
    N1Supplier/Manufacturer
    N1
    020

    Name

    RequiredMax use 1

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

    • Allowing the N1 segment to repeat in this area allows the paying entity within a payer and the paid entity within a payee to be identified (not the payer and payee).
    Example
    N1-01
    98
    Entity Identifier Code
    Required

    Code identifying an organizational entity, a physical location, or an individual

    Usage notes

    Use N101 and N102 only if the Ford "vouchered supplier code" information is provided (ENT05, -06, -07), otherwise this segment is not needed.

    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.

    Refer to 003040 Data Element Dictionary for acceptable code values.

    PE
    Payee
    N1-02
    93
    Name
    Optional
    Min 1Max 35

    Free-form name.

    Usage notes

    At least one of N102 or N103 is required. Name of the receiver’s "Ship From" location.

    N1 Supplier/Manufacturer
    OptionalMax >1
    Variants (all may be used)
    N1Payee
    N1
    020

    Name

    RequiredMax use 1

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

    • Allowing the N1 segment to repeat in this area allows the paying entity within a payer and the paid entity within a payee to be identified (not the payer and payee).
    Usage notes

    Example: N1SUPLASTIC PRODUCTS’

    Example
    N1-01
    98
    Entity Identifier Code
    Required

    Code identifying an organizational entity, a physical location, or an individual

    Usage notes

    Use N101 and N102 only if the Ford "vouchered supplier code" information is provided (ENT05, -06, -07), otherwise this segment is not needed.

    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.

    Refer to 003040 Data Element Dictionary for acceptable code values.

    SU
    Supplier/Manufacturer
    N1-02
    93
    Name
    Optional
    Min 1Max 35

    Free-form name.

    Usage notes

    At least one of N102 or N103 is required.

    ADX Loop
    OptionalMax >1
    ADX
    080

    Adjustment

    RequiredMax use 1

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

    • This ADX loop contains adjustment items which are not netted to an RMR segment in this transaction set.
    Usage notes

    Example: ADX+123.4501’

    Example
    If either Reference Number Qualifier (ADX-03) or Reference Number (ADX-04) is present, then the other is required
    ADX-01
    782
    Monetary Amount
    Required
    Min 1Max 15

    Monetary amount.

    • 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.
    Usage notes

    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.

    ADX-02
    426
    Adjustment Reason Code
    Required

    Code indicating reason for credit memo, or adjustment to invoice, credit memo, or payment.

    • ADX02 specifies the reason for claiming the adjustment.
    01
    Pricing Error
    06
    Quantity Contested
    46
    Transportation Charge Incorrect
    72
    Authorized Return
    C1
    Settlement of Account
    E2
    Covered By Debit Memo
    ZZ
    Mutually Defined
    ADX-03
    128
    Reference Number Qualifier
    Optional

    Code qualifying the Reference Number.

    • ADX03 and ADX04 specify the identification of the adjustment.
    CM
    Credit Memo
    CR
    Customer Reference Number
    DL
    Debit Memo
    ET
    Excess Transportation
    IV
    Seller's Invoice Number
    RZ
    Returned Goods Authorization Number
    SI
    Shipper's Identifying Number for Shipment (SID)

    A unique number (to the shipper) assigned by the shipper to identify the shipment.

    ADX-04
    127
    Reference Number
    Optional
    Min 1Max 30

    Reference number or identification number as defined for a particular Transaction Set, or as specified by the Reference Number Qualifier.

    NTE
    090

    Note/Special Instruction

    OptionalMax use >1

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

    Usage notes

    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.

    Example: NTEPAY PART# 1L54-10218A32-A1 EA’

    Example
    NTE-01
    363
    Note Reference Code
    Optional

    Code identifying the functional area or purpose for which the note applies.

    PAY
    Payables
    NTE-02
    3
    Free Form Message
    Required
    Min 1Max 60

    Free-form text.

    DTM
    105

    Invoice

    OptionalMax use 1

    To specify pertinent dates and times

    Usage notes

    Example: DTM003010824~~~20’

    Example
    Variants (all may be used)
    DTMIssue
    DTM-01
    374
    Date/Time Qualifier
    Required

    Code specifying type of date or time, or both date and time.

    003
    Invoice
    DTM-02
    373
    Date
    Optional
    YYMMDD format

    Date (YYMMDD).

    Usage notes

    At least one of DTM02, DTM03, or DTM06 is required.

    DTM-05
    624
    Century
    Optional
    Min 2Max 2

    The first two characters in the designation of the year (CCYY).

    DTM
    105

    Issue

    OptionalMax use 1

    To specify pertinent dates and times

    Example
    Variants (all may be used)
    DTMInvoice
    DTM-01
    374
    Date/Time Qualifier
    Required

    Code specifying type of date or time, or both date and time.

    102
    Issue

    For use as the invoice date on Ford-created retroactive price adjustments.

    DTM-02
    373
    Date
    Optional
    YYMMDD format

    Date (YYMMDD).

    Usage notes

    At least one of DTM02, DTM03, or DTM06 is required.

    DTM-05
    624
    Century
    Optional
    Min 2Max 2

    The first two characters in the designation of the year (CCYY).

    REF Loop
    OptionalMax >1
    REF
    110

    Reference Numbers

    RequiredMax use 1

    To specify identifying numbers.

    Usage notes

    This REF segment contains ancillary reference numbers that relate to the preceding ADX segment. This segment is not intended to identify the primary document number.

    Example: REFPEAP01’

    Example
    REF-01
    128
    Reference Number Qualifier
    Required

    Code qualifying the Reference Number.

    OI
    Original Invoice Number
    PE
    Plant Number
    RZ
    Returned Goods Authorization Number
    SI
    Shipper's Identifying Number for Shipment (SID)
    TN
    Transaction Reference Number
    VT
    Motor Vehicle ID Number

    For COPAC outbound freight payments.

    ZZ
    Mutually Defined

    Inbound freight recovery.

    REF-02
    127
    Reference Number
    Optional
    Min 1Max 30

    Reference number or identification number as defined for a particular Transaction Set, or as specified by the Reference Number Qualifier.

    DTM
    120

    Invoice

    OptionalMax use >1

    To specify pertinent dates and times

    Usage notes

    Example: : DTM003010824~~~20’

    Example
    Variants (all may be used)
    DTMShippedDTMRecieved
    DTM-01
    374
    Date/Time Qualifier
    Required

    Code specifying type of date or time, or both date and time.

    003
    Invoice
    DTM-02
    373
    Date
    Optional
    YYMMDD format

    Date (YYMMDD).

    Usage notes

    At least one of DTM02, DTM03, or DTM06 is required.

    DTM-05
    624
    Century
    Optional
    Min 2Max 2

    The first two characters in the designation of the year (CCYY).

    DTM
    120

    Shipped

    OptionalMax use >1

    To specify pertinent dates and times

    Example
    Variants (all may be used)
    DTMInvoiceDTMRecieved
    DTM-01
    374
    Date/Time Qualifier
    Required

    Code specifying type of date or time, or both date and time.

    011
    Shipped
    DTM-02
    373
    Date
    Optional
    YYMMDD format

    Date (YYMMDD).

    Usage notes

    At least one of DTM02, DTM03, or DTM06 is required.

    DTM-05
    624
    Century
    Optional
    Min 2Max 2

    The first two characters in the designation of the year (CCYY).

    DTM
    120

    Recieved

    OptionalMax use >1

    To specify pertinent dates and times

    Example
    Variants (all may be used)
    DTMInvoiceDTMShipped
    DTM-01
    374
    Date/Time Qualifier
    Required

    Code specifying type of date or time, or both date and time.

    050
    Received
    DTM-02
    373
    Date
    Optional
    YYMMDD format

    Date (YYMMDD).

    Usage notes

    At least one of DTM02, DTM03, or DTM06 is required.

    DTM-05
    624
    Century
    Optional
    Min 2Max 2

    The first two characters in the designation of the year (CCYY).

    IT1 Loop
    OptionalMax >1
    IT1
    130

    Baseline Item Data (Invoice)

    RequiredMax use 1

    To specify the basic and most frequently used line item data for the invoice and related transactions.

    • Loop IT1 within the ADX loop is the adjustment line item detail loop.
    Usage notes

    Example: IT1~~+1680.000EA+110.09000~CP’

    Example
    IT1-02
    358
    Quantity Invoiced
    Required
    Min 1Max 10

    Number of units invoiced (supplier units).

    IT1-03
    355
    Unit or Basis for Measurement Code
    Required
    Min 2Max 2

    Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken

    IT1-04
    212
    Unit Price
    Required
    Min 1Max 14

    Price per unit of product, service, commodity, etc.

    IT1-05
    639
    Basis of Unit Price Code
    Optional

    Code identifying the type of unit price for an item.

    CP
    Current Price (Subject to Change)
    NT
    Net

    Indicates a net unit price.

    REF Loop
    OptionalMax >1
    REF
    140

    Reference Numbers

    RequiredMax use 1

    To specify identifying numbers.

    Usage notes

    Example: REFPEAP01’

    Example
    REF-01
    128
    Reference Number Qualifier
    Required

    Code qualifying the Reference Number.

    IV
    Seller's Invoice Number
    PE
    Plant Number
    PM
    Part Number
    PO
    Purchase Order Number
    PS
    Purchase Order Number Suffix
    REF-02
    127
    Reference Number
    Optional
    Min 1Max 30

    Reference number or identification number as defined for a particular Transaction Set, or as specified by the Reference Number Qualifier.

    DTM
    141

    Date/Time Reference

    OptionalMax use 1

    To specify pertinent dates and times

    Usage notes

    Example: DTM003010824~~~20’

    Example
    DTM-01
    374
    Date/Time Qualifier
    Required

    Code specifying type of date or time, or both date and time.

    003
    Invoice
    007
    Effective
    011
    Shipped
    050
    Received
    DTM-02
    373
    Date
    Optional
    YYMMDD format

    Date (YYMMDD).

    Usage notes

    At least one of DTM02, DTM03, or DTM06 is required.

    DTM-05
    624
    Century
    Optional
    Min 2Max 2

    The first two characters in the designation of the year (CCYY).

    SLN Loop
    OptionalMax >1
    SLN
    144

    Subline Item Detail

    RequiredMax use 1

    To specify product subline detail item data

    Usage notes

    For retroactive price adjustments caused by a price change, two SLN loops are used.

    Example:
    SLN000002A+5.000EA41.75000CP’
    SLN000001D+5.000EA41.1227LR’

    Example
    If Basis of Unit Price Code (SLN-07) is present, then Unit Price (SLN-06) is required
    SLN-01
    350
    Assigned Identification
    Required
    Min 1Max 11

    Alphanumeric characters assigned for differentiation within a transaction set.

    • SLN01 is the identifying number for the subline item.
    • SLN01 is related to (but not necessarily equivalent to) the baseline item number. Example: 1.1 or 1A might be used as a subline number to relate to baseline number 1.
    Usage notes

    SLN01 is related to (but not necessarily equivalent to) the baseline item
    number. Example: 1.1 or 1A might be used as a subline number to relate to
    baseline number 1.

    SLN-03
    661
    Configuration Code
    Required

    Code indicating the relationship of the subline item to the baseline item.

    A
    Added
    D
    Deleted
    SLN-04
    380
    Quantity
    Required
    Min 1Max 15

    Numeric value of quantity.

    SLN-05
    355
    Unit or Basis for Measurement Code
    Required
    Min 2Max 2

    Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken

    SLN-06
    212
    Unit Price
    Optional
    Min 1Max 14

    Price per unit of product, service, commodity, etc.

    Usage notes

    If SLN07 or SLN08 are present, then SLN06 is required.

    SLN-07
    639
    Basis of Unit Price Code
    Optional

    Code identifying the type of unit price for an item.

    CP
    Current Price (Subject to Change)
    LR
    Previous Catalog Price
    RMR Loop
    OptionalMax >1
    RMR
    150

    Remittance Advice Accounts Receivable Open Item Reference

    RequiredMax use 1

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

    • Loop RMR is for open items being referenced or for payment on account.
    Usage notes

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

    Example: RMRPK YE6394~~+46714.75+46714.75+.00’

    Example
    If either Reference Number Qualifier (RMR-01) or Reference Number (RMR-02) is present, then the other is required
    RMR-01
    128
    Reference Number Qualifier
    Optional

    Code qualifying the Reference Number.

    • Parties using this segment should agree on the content of RMR01 and RMR02 prior to initiating communication.
    CM
    Credit Memo
    DL
    Debit Memo
    FR
    Freight Bill Number
    IV
    Seller's Invoice Number
    OI
    Original Invoice Number
    PK
    Packing List Number
    SI
    Shipper's Identifying Number for Shipment (SID)

    A unique number (to the shipper) assigned by the shipper to identify the shipment.

    RMR-02
    127
    Reference Number
    Optional
    Min 1Max 30

    Reference number or identification number as defined for a particular Transaction Set, or as specified by the Reference Number Qualifier.

    RMR-03
    482
    Payment Action Code
    Optional

    Code specifying the type of accounts receivable open item(s) to be included in a cash application.

    • If RMR03 is present, it specifies how the cash is to be applied.
    • 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.
    ER
    Evaluated Receipts Settlement
    PO
    Payment on Account
    RMR-04
    782
    Monetary Amount
    Optional
    Min 1Max 15

    Monetary amount.

    • RMR04 is the amount paid.
    Usage notes

    RMR04 is the net amount being paid, inclusive of discounts and adjustments. RMR04 must be signed if negative. If negative, it reduces the payment amount; if positive, it increases the payment amount.

    RMR-05
    777
    Total Invoice or Credit/Debit Amount
    Optional
    Min 1Max 15

    Amount of Invoice (including charges, less allowances) before terms discount (if discount is applicable) or debit amount or credit amount of referenced items.

    • RMR05 may be needed by some payees to distinguish between duplicate reference numbers.
    RMR-06
    780
    Amount of Discount Taken
    Optional
    Min 1Max 15

    Amount of discount taken, which may be less than or equal to the amount of discount permitted

    • RMR06 may be used to specify discount taken.
    Usage notes

    The value of the RMR06 is positive and it reduces the Total Invoice (RMR05) amount.

    NTE
    160

    Note/Special Instruction

    OptionalMax use >1

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

    Usage notes

    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.

    Example: NTEPAY YOUR REFERENCE NUMBER 86807’

    Example
    NTE-01
    363
    Note Reference Code
    Optional

    Code identifying the functional area or purpose for which the note applies.

    PAY
    Payables
    NTE-02
    3
    Free Form Message
    Required
    Min 1Max 60

    Free-form text.

    REF
    170

    Reference Numbers

    OptionalMax use >1

    To specify identifying numbers.

    Usage notes

    This REF segment contains ancillary reference numbers that relate to the preceding RMR segment. This segment is not intended to duplicate the reference number in RMR02 for the primary document reference number.

    Example: REFIV 86807’

    Example
    REF-01
    128
    Reference Number Qualifier
    Required

    Code qualifying the Reference Number.

    CR
    Customer Reference Number
    IV
    Seller's Invoice Number
    PE
    Plant Number
    PK
    Packing List Number
    PO
    Purchase Order Number
    TN
    Transaction Reference Number
    REF-02
    127
    Reference Number
    Optional
    Min 1Max 30

    Reference number or identification number as defined for a particular Transaction Set, or as specified by the Reference Number Qualifier.

    DTM
    180

    Invoice

    OptionalMax use >1

    To specify pertinent dates and times

    Usage notes

    Example: DTM003010824~~~20’

    Example
    Variants (all may be used)
    DTMShippedDTMIssue
    DTM-01
    374
    Date/Time Qualifier
    Required

    Code specifying type of date or time, or both date and time.

    003
    Invoice
    DTM-02
    373
    Date
    Optional
    YYMMDD format

    Date (YYMMDD).

    Usage notes

    At least one of DTM02, DTM03, or DTM06 is required.

    DTM-05
    624
    Century
    Optional
    Min 2Max 2

    The first two characters in the designation of the year (CCYY).

    DTM
    180

    Shipped

    OptionalMax use >1

    To specify pertinent dates and times

    Example
    Variants (all may be used)
    DTMInvoiceDTMIssue
    DTM-01
    374
    Date/Time Qualifier
    Required

    Code specifying type of date or time, or both date and time.

    011
    Shipped
    DTM-02
    373
    Date
    Optional
    YYMMDD format

    Date (YYMMDD).

    Usage notes

    At least one of DTM02, DTM03, or DTM06 is required.

    DTM-05
    624
    Century
    Optional
    Min 2Max 2

    The first two characters in the designation of the year (CCYY).

    DTM
    180

    Issue

    OptionalMax use >1

    To specify pertinent dates and times

    Example
    Variants (all may be used)
    DTMInvoiceDTMShipped
    DTM-01
    374
    Date/Time Qualifier
    Required

    Code specifying type of date or time, or both date and time.

    102
    Issue
    DTM-02
    373
    Date
    Optional
    YYMMDD format

    Date (YYMMDD).

    Usage notes

    At least one of DTM02, DTM03, or DTM06 is required.

    DTM-05
    624
    Century
    Optional
    Min 2Max 2

    The first two characters in the designation of the year (CCYY).

    IT1 Loop
    OptionalMax >1
    IT1
    190

    Baseline Item Data (Invoice)

    RequiredMax use 1

    To specify the basic and most frequently used line item data for the invoice and related transactions.

    • Loop IT1 within the RMR loop is the remittance line item detail loop.
    Usage notes

    Example: IT1~~+9815.000EA+2.38581~CP’

    Example
    IT1-02
    358
    Quantity Invoiced
    Required
    Min 1Max 10

    Number of units invoiced (supplier units).

    IT1-03
    355
    Unit or Basis for Measurement Code
    Required
    Min 2Max 2

    Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken

    IT1-04
    212
    Unit Price
    Required
    Min 1Max 14

    Price per unit of product, service, commodity, etc.

    IT1-05
    639
    Basis of Unit Price Code
    Optional

    Code identifying the type of unit price for an item.

    CP
    Current Price (Subject to Change)
    REF Loop
    OptionalMax >1
    REF
    200

    Reference Numbers

    RequiredMax use 1

    To specify identifying numbers.

    Usage notes

    Example: REFPMXT 2 RDX’

    Example
    REF-01
    128
    Reference Number Qualifier
    Required

    Code qualifying the Reference Number.

    IV
    Seller's Invoice Number
    PE
    Plant Number
    PM
    Part Number
    PO
    Purchase Order Number
    PS
    Purchase Order Number Suffix
    REF-02
    127
    Reference Number
    Optional
    Min 1Max 30

    Reference number or identification number as defined for a particular Transaction Set, or as specified by the Reference Number Qualifier.

    DTM
    201

    Date/Time Reference

    OptionalMax use 1

    To specify pertinent dates and times

    Usage notes

    Example: DTM003010824~~~20’

    Example
    DTM-01
    374
    Date/Time Qualifier
    Required

    Code specifying type of date or time, or both date and time.

    007
    Effective
    DTM-02
    373
    Date
    Optional
    YYMMDD format

    Date (YYMMDD).

    Usage notes

    At least one of DTM02, DTM03, or DTM06 is required.

    DTM-05
    624
    Century
    Optional
    Min 2Max 2

    The first two characters in the designation of the year (CCYY).

    Summary

    SE
    010

    Transaction Set Trailer

    RequiredMax use 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).

    Example
    SE-01
    96
    Number of Included Segments
    Required
    Min 1Max 10

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

    SE-02
    329
    Transaction Set Control Number
    Required
    Min 4Max 9

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

    Functional Group Trailer

    RequiredMax use 1

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

    Example
    GE-01
    97
    Number of Transaction Sets Included
    Required
    Min 1Max 6

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

    GE-02
    28
    Group Control Number
    Required
    Min 1Max 9

    Assigned number originated and maintained by the sender.

    Interchange Control Trailer

    RequiredMax use 1

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

    Example
    IEA-01
    I16
    Number of Included Functional Groups
    Required
    Min 1Max 5

    A count of the number of functional groups included in a transmission.

    IEA-02
    I12
    Interchange Control Number
    Required
    Min 9Max 9

    This number uniquely identifies the interchange data to the sender. It is assigned by the sender. Together with the sender ID it uniquely identifies the interchange data to the receiver. It is suggested that the sender, receiver, and all third parties be able to maintain an audit trail of interchanges using this number.

    EDI Samples

    Sample

    ST~820~0001
    BPR~I~+99999.00~C~ACH~~01~700 00000~~700~9999990000~~~~~~010921~VEN
    TRN~3~000013000~9B69KA0000
    N1~PR~FORD MOTOR COMPANY~92~B69KA
    N2~CENTRAL ACCOUNTING SERVICES
    N1~PE~PLASTIC PRODUCTS~92~B816N
    PER~AP~~TE~734-525-9999
    ENT~1~~~~SU~92~B999N
    N1~SU~PLASTIC PRODUCTS
    RMR~IV~ DELD~~+750.00~+750.00~+.00
    NTE~PAY~ PART# 1L54-90218A32-A1 EA
    NTE~PAY~ QTY 000000015 PRICE 000000000000050 USD
    REF~PO~129116
    REF~TN~126319700178A
    REF~PE~5001
    RMR~IV~ F-2587-E~~+49440.00~+49440.00~+.00
    NTE~PAY~ PART# 1L54-9000082-A1 EA
    NTE~PAY~ PART# 1L54-90286B20-A1 EA
    NTE~PAY~ PART# 1L54-90218A34-A1 EA
    NTE~PAY~ QTY 000000012 PRICE 000000000009999 USD
    NTE~PAY~ QTY 000000015 PRICE 000000000000099 USD
    NTE~PAY~ QTY 000000015 PRICE 000000000000099 USD
    REF~PO~129116
    REF~TN~126319700181A
    REF~PE~5001
    RMR~IV~ 00129116~~+750.00~+750.00~+.00
    NTE~PAY~ PART# 1L54-90286B21-A1 EA
    NTE~PAY~ QTY 000000015 PRICE 000000000000099 USD
    REF~PO~129999
    REF~TN~126319700004A
    REF~PE~5001
    SE~32~0001

    Stedi is a registered trademark of Stedi, Inc. All names, logos, and brands of third parties listed on this page are trademarks of their respective owners (including “X12”, which is a trademark of X12 Incorporated). Stedi, Inc. and its products and services are not endorsed by, sponsored by, or affiliated with these third parties. Use of these names, logos, and brands is for identification purposes only, and does not imply any such endorsement, sponsorship, or affiliation.