X12 820 Payment Order/Remittance Advice
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.
- ~ Segment
- * Element
- > Component
Interchange Control Header
To start and identify an interchange of one or more functional groups and interchange-related control segments
Code to identify the type of information in the Authorization Information.
- 00
- No Authorization Information Present (No Meaningful Information in I02)
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.
Code to identify the type of information in the Security Information.
- 00
- No Security Information Present (No Meaningful Information in I04)
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.
Qualifier to designate the system/method of code structure used to designate the sender or receiver ID element being qualified.
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.
Qualifier to designate the system/method of code structure used to designate the sender or receiver ID element being qualified.
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.
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
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
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.
Code sent by the sender to request an interchange acknowledgment.
- 0
- No Acknowledgment Requested
- 1
- Interchange Acknowledgment Requested
Code to indicate whether data enclosed by this interchange envelope is test or production.
- P
- Production Data
- T
- Test Data
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
To indicate the beginning of a functional group and to provide control information
Code identifying a group of application related Transaction Sets.
- RA
- Payment Order/Remittance Advice (820)
Code identifying party sending transmission. Codes agreed to by trading partners.
Code identifying party receiving transmission. Codes agreed to by trading partners.
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)
Assigned number originated and maintained by the sender.
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
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
Transaction Set Header
To indicate the start of a transaction set and to assign a control number
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
Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set
Beginning Segment for Payment Order/Remittance Advice
(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
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’
Code designating the action to be taken by all parties.
- I
- Remittance Information Only
Code indicating whether amount is a credit or debit
- C
- Credit
- D
- Debit
Code identifying the method for the movement of payment instructions
- ACH
- Automated Clearing House (ACH)
- CHK
- Check
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)
Depository Financial Institution (DFI) identification number.
Code indicating type of bank account or other financial asset
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.
This Ford bank account may be debited or credited depending on the type of payment order.
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.
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.
A code defined between the originating company and the originating depository financial institution (ODFI) that uniquely identifies the company initiating the transfer instructions.
Code identifying the type of identification number of Depository Financial Institution (DFI).
- BPR12 and BPR13 relate to the receiving depository financial institution (RDFI).
Depository Financial Institution (DFI) identification number.
Code indicating type of bank account or other financial asset
Account number assigned.
- BPR15 is the account number of the receiving company to be debited or credited with the payment order.
Date the originating company intends for the transaction to be settled.
Code identifying the business reason for this payment
- BPR17 is a code identifying the business reason for the this payment.
- VEN
- Vendor Payment
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.
Depository Financial Institution (DFI) identification number.
Code indicating type of bank account or other financial asset
Note/Special Instruction
To transmit information in a free-form format, if necessary, for comment or special instruction
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’
Trace
To uniquely identify a transaction to an application.
- The TRN segment is used to uniquely identify a payment order/remittance advice.
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’
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.
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.
Only a check number is sent in this Reference Number.
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.
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.
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.
Currency
To specify the currency (dollars, pounds, francs, etc.) used in a transaction
- The CUR segment does not initiate a foreign exchange transaction.
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’
Reference Numbers
To specify identifying numbers.
Reference number or identification number as defined for a particular Transaction Set, or as specified by the Reference Number Qualifier.
A free-form description to clarify the related data elements and their content.
Name
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.
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.
Code identifying an organizational entity, a physical location, or an individual
- PE
- Payee
Free-form name.
At least one of N102 or N103 is required. Name of receiving supplier/vendor.
Code designating the system/method of code structure used for Identification Code (67).
- 92
- Assigned by Buyer or Buyer's Agent
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.
Ford assigned supplier code.
Additional Name Information
To specify additional names or those longer than 35 characters in length
Example: N2~CENTRAL ACCOUNTING SERVICES’
Free-form text for city name.
- A combination of either N401 through N404 (or N405 and N406) may be adequate to specify a location.
Code (Standard State/Province) as defined by appropriate government agency.
- N402 is required only if city name (N401) is in the USA or Canada.
Code defining international postal zone code excluding punctuation and blanks (zip code for United States).
Reference Numbers
To specify identifying numbers.
Reference number or identification number as defined for a particular Transaction Set, or as specified by the Reference Number Qualifier.
A free-form description to clarify the related data elements and their content.
Administrative Communications Contact
To identify a person or office to whom administrative communications should be directed
Example: PERAP~~TE734-525-7800’
Code identifying the major duty or responsibility of the person or group named.
- AP
- Accounts Payable Department
Code identifying the type of communication number.
- TE
- Telephone
Complete communications number including country or area code when applicable.
Example of Communication Number: "313 458 0165".
Code identifying the type of communication number.
Complete communications number including country or area code when applicable.
Name
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.
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’
Code identifying an organizational entity, a physical location, or an individual
- PR
- Payer
Free-form name.
At least one of N102 or N103 is required. Name of the Ford paying activity.
Code designating the system/method of code structure used for Identification Code (67).
- 92
- Assigned by Buyer or Buyer's Agent
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.
Code of the Ford paying activity.
Additional Name Information
To specify additional names or those longer than 35 characters in length
Example: N2~CENTRAL ACCOUNTING SERVICES’
Free-form text for city name.
- A combination of either N401 through N404 (or N405 and N406) may be adequate to specify a location.
Code (Standard State/Province) as defined by appropriate government agency.
- N402 is required only if city name (N401) is in the USA or Canada.
Code defining international postal zone code excluding punctuation and blanks (zip code for United States).
Reference Numbers
To specify identifying numbers.
Reference number or identification number as defined for a particular Transaction Set, or as specified by the Reference Number Qualifier.
A free-form description to clarify the related data elements and their content.
Administrative Communications Contact
To identify a person or office to whom administrative communications should be directed
Example: PERAP~~TE734-525-7800’
Code identifying the major duty or responsibility of the person or group named.
- AP
- Accounts Payable Department
Code identifying the type of communication number.
- TE
- Telephone
Complete communications number including country or area code when applicable.
Example of Communication Number: "313 458 0165".
Code identifying the type of communication number.
Complete communications number including country or area code when applicable.
Detail
Entity
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.
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’
Number assigned for differentiation within a transaction set.
"1" - Initial use to indicate loop start. Will increase usage with introduction of "Ship From" information resulting in use of ENT05 - ENT07 segments.
Code identifying an organizational entity, a physical location, or an individual
If any of ENT05, ENT06, or ENT07 are present, then all are required.
- SU
- Supplier/Manufacturer
Code designating the system/method of code structure used for Identification Code (67).
Name
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).
Code identifying an organizational entity, a physical location, or an individual
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
Free-form name.
At least one of N102 or N103 is required. Name of the receiver’s "Ship From" location.
Name
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: N1SUPLASTIC PRODUCTS’
Code identifying an organizational entity, a physical location, or an individual
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
Adjustment
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.
Example: ADX+123.4501’
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.
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.
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
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.
Reference number or identification number as defined for a particular Transaction Set, or as specified by the Reference Number Qualifier.
Note/Special Instruction
To transmit information in a free-form format, if necessary, for comment or special instruction
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’
Code specifying type of date or time, or both date and time.
- 003
- Invoice
Date (YYMMDD).
At least one of DTM02, DTM03, or DTM06 is required.
Issue
To specify pertinent dates and times
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.
Date (YYMMDD).
At least one of DTM02, DTM03, or DTM06 is required.
Reference Numbers
To specify identifying numbers.
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’
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.
Reference number or identification number as defined for a particular Transaction Set, or as specified by the Reference Number Qualifier.
Invoice
To specify pertinent dates and times
Example: : DTM003010824~~~20’
Code specifying type of date or time, or both date and time.
- 003
- Invoice
Date (YYMMDD).
At least one of DTM02, DTM03, or DTM06 is required.
Code specifying type of date or time, or both date and time.
- 011
- Shipped
Date (YYMMDD).
At least one of DTM02, DTM03, or DTM06 is required.
Code specifying type of date or time, or both date and time.
- 050
- Received
Date (YYMMDD).
At least one of DTM02, DTM03, or DTM06 is required.
Baseline Item Data (Invoice)
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.
Example: IT1~~+1680.000EA+110.09000~CP’
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
Code identifying the type of unit price for an item.
- CP
- Current Price (Subject to Change)
- NT
- Net
Indicates a net unit price.
Reference Numbers
To specify identifying numbers.
Example: REFPEAP01’
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
Reference number or identification number as defined for a particular Transaction Set, or as specified by the Reference Number Qualifier.
Date/Time Reference
To specify pertinent dates and times
Example: DTM003010824~~~20’
Code specifying type of date or time, or both date and time.
- 003
- Invoice
- 007
- Effective
- 011
- Shipped
- 050
- Received
Date (YYMMDD).
At least one of DTM02, DTM03, or DTM06 is required.
Subline Item Detail
To specify product subline detail item data
For retroactive price adjustments caused by a price change, two SLN loops are used.
Example:
SLN000002A+5.000EA41.75000CP’
SLN000001D+5.000EA41.1227LR’
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.
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.
Code indicating the relationship of the subline item to the baseline item.
- A
- Added
- D
- Deleted
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
Price per unit of product, service, commodity, etc.
If SLN07 or SLN08 are present, then SLN06 is required.
Code identifying the type of unit price for an item.
- CP
- Current Price (Subject to Change)
- LR
- Previous Catalog Price
Remittance Advice Accounts Receivable Open Item Reference
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.
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’
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.
Reference number or identification number as defined for a particular Transaction Set, or as specified by the Reference Number Qualifier.
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
Monetary amount.
- RMR04 is the amount paid.
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.
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.
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.
The value of the RMR06 is positive and it reduces the Total Invoice (RMR05) amount.
Note/Special Instruction
To transmit information in a free-form format, if necessary, for comment or special instruction
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’
Reference Numbers
To specify identifying numbers.
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’
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
Reference number or identification number as defined for a particular Transaction Set, or as specified by the Reference Number Qualifier.
Invoice
To specify pertinent dates and times
Example: DTM003010824~~~20’
Code specifying type of date or time, or both date and time.
- 003
- Invoice
Date (YYMMDD).
At least one of DTM02, DTM03, or DTM06 is required.
Code specifying type of date or time, or both date and time.
- 011
- Shipped
Date (YYMMDD).
At least one of DTM02, DTM03, or DTM06 is required.
Code specifying type of date or time, or both date and time.
- 102
- Issue
Date (YYMMDD).
At least one of DTM02, DTM03, or DTM06 is required.
Baseline Item Data (Invoice)
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.
Example: IT1~~+9815.000EA+2.38581~CP’
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
Code identifying the type of unit price for an item.
- CP
- Current Price (Subject to Change)
Reference Numbers
To specify identifying numbers.
Example: REFPMXT 2 RDX’
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
Reference number or identification number as defined for a particular Transaction Set, or as specified by the Reference Number Qualifier.
Date/Time Reference
To specify pertinent dates and times
Example: DTM003010824~~~20’
Code specifying type of date or time, or both date and time.
- 007
- Effective
Date (YYMMDD).
At least one of DTM02, DTM03, or DTM06 is required.
Summary
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).
Total number of segments included in a transaction set including ST and SE segments.
Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set
Functional Group Trailer
To indicate the end of a functional group and to provide control information
Total number of transaction sets included in the functional group or interchange (transmission) group terminated by the trailer containing this data element.
Assigned number originated and maintained by the sender.
Interchange Control Trailer
To define the end of an interchange of one or more functional groups and interchange-related control segments
A count of the number of functional groups included in a transmission.
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.
Sample
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.