820 Payment Order/Remittance Advice
Ford · X12 003040
Ford’s published 820 specification, rendered as an interactive guide. Expand any segment to see its elements, data types, lengths and accepted codes — then validate your own document against it below.
Specification
43 of 43 segments
HEADING
ST
Transaction Set Header ST
pos 010
Optional
max —
BPR
Beginning Segment For Payment Order Remittance Advice BPR
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: BPR~I~+50940.00~C~ACH~~01~70000000~~700~9B69KA0000~~~~~~010921~VEN’
pos 020
Required
max —
NTE
Note Special Instruction NTE
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: NTE~PAY~ YOUR REFERENCE NUMBER 86807’
pos 030
Optional
max —
TRN
Trace TRN
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: TRN~3~000013000~9B69KA0000’
pos 035
Optional
max —
CUR
Currency CUR
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: CUR~BY~MXP’
pos 040
Optional
max —
REF
Reference Numbers REF
pos 050
Optional
max —
N1 LoopPayeevariant 1 of 2
N1
Name N1
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.
pos 070
Required
max —
N2
Additional Name Information N2
Example: N2~CENTRAL ACCOUNTING SERVICES’
pos 080
Optional
max —
N3
Address Information N3
pos 090
Optional
max —
N4
Geographic Location N4
pos 100
Optional
max —
REF
Reference Numbers REF
pos 110
Optional
max —
PER
Administrative Communications Contact PER
Example: PER~AP~~TE~734-525-7800’
pos 120
Optional
max —
N1 LoopPayervariant 2 of 2
N1
Name N1
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: N1~PR~FORD MOTOR COMPANY~92~B69KA’
pos 070
Required
max —
N2
Additional Name Information N2
Example: N2~CENTRAL ACCOUNTING SERVICES’
pos 080
Optional
max —
N3
Address Information N3
pos 090
Optional
max —
N4
Geographic Location N4
pos 100
Optional
max —
REF
Reference Numbers REF
pos 110
Optional
max —
PER
Administrative Communications Contact PER
Example: PER~AP~~TE~734-525-7800’
pos 120
Optional
max —
DETAIL
ENT Loop
ENT
Entity ENT
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: ENT~1~~~~SU~92~B816N’
pos 010
Required
max —
N1 LoopPayeevariant 1 of 2
N1
Name N1
pos 020
Required
max —
N1 LoopSupplier/Manufacturervariant 2 of 2
N1
Name N1
Example: N1~SU~PLASTIC PRODUCTS’
pos 020
Required
max —
ADX Loop
ADX
Adjustment ADX
Example: ADX~+123.45~01’
pos 080
Required
max —
NTE
Note Special Instruction NTE
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: NTE~PAY~ PART# 1L54-10218A32-A1 EA’
pos 090
Optional
max —
DTM
Invoicevariant 1 of 2
Example: DTM~003~010824~~~20’
pos 105
Optional
max —
DTM
Issuevariant 2 of 2
pos 105
Optional
max —
REF Loop
REF
Reference Numbers REF
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: REF~PE~AP01’
pos 110
Required
max —
DTM
Invoicevariant 1 of 3
Example: : DTM~003~010824~~~20’
pos 120
Optional
max —
DTM
Shippedvariant 2 of 3
pos 120
Optional
max —
DTM
Recievedvariant 3 of 3
pos 120
Optional
max —
IT1 Loop
IT1
Baseline Item Data Invoice IT1
Example: IT1~~+1680.000~EA~+110.09000~CP’
pos 130
Required
max —
REF Loop
REF
Reference Numbers REF
Example: REF~PE~AP01’
pos 140
Required
max —
DTM
Date Time Reference DTM
Example: DTM~003~010824~~~20’
pos 141
Optional
max —
SLN Loop
SLN
Subline Item Detail SLN
For retroactive price adjustments caused by a price change, two SLN loops are used.
Example:
SLN~000002~A~+5.000~EA~41.75000~CP’
SLN~000001~D~+5.000~EA~41.1227~LR’
pos 144
Required
max —
RMR Loop
RMR
Remittance Advice Accounts Receivable Open Item Reference RMR
Parties using this segment should agree on the content of RMR01 and RMR02 prior to initiating communication.
Example: RMR~PK~ YE6394~~+46714.75~+46714.75~+.00’
pos 150
Required
max —
NTE
Note Special Instruction NTE
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: NTE~PAY~ YOUR REFERENCE NUMBER 86807’
pos 160
Optional
max —
REF
Reference Numbers REF
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: REF~IV~ 86807’
pos 170
Optional
max —
DTM
Invoicevariant 1 of 3
Example: DTM~003~010824~~~20’
pos 180
Optional
max —
DTM
Shippedvariant 2 of 3
pos 180
Optional
max —
DTM
Issuevariant 3 of 3
pos 180
Optional
max —
IT1 Loop
IT1
Baseline Item Data Invoice IT1
Example: IT1~~+9815.000~EA~+2.38581~CP’
pos 190
Required
max —
REF Loop
REF
Reference Numbers REF
Example: REF~PM~XT 2 RDX’
pos 200
Required
max —
DTM
Date Time Reference DTM
Example: DTM~003~010824~~~20’
pos 201
Optional
max —
SUMMARY
SE
Transaction Set Trailer SE
pos 010
Optional
max —
Validate a 820
Paste or upload a document and check it against Ford’s published rules — segment order and repetition, required elements, field lengths, data types and accepted codes. Nothing is stored.
Go live on Ford’s 820 in days, not months
Weredi maps this guide to your ERP, runs the test cycle with Ford, and keeps the spec current as it changes.