BofA-820v4010 Rcpt-XC
BofA-820v4010 Rcpt-XC
Version/Release 004010
The Payment Order/Remittance Advice 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.
For further details of the transaction sets and segments utilized by Bank of America, please contact your
Treasury Management Officer or Product Management Officer.
Introduction
To allow for transmissions of different types of transactions sets from one party to another in the same transmission,
a hierarchy structure of headers and trailers is used. This structure allows the data to be segregated logically for easy
interpretation by the receiver. A brief description of the records in the ASC X12 structure is reviewed below:
ISA
Interchange Control Header - The Interchange Control Header is the beginning outer envelope of one or more
Functional Groups or interchange-related control segments. This header contains the value of the data element
separators, data segment terminators, the identity of the sender and receiver and the required authorization and
security information.
GS
Functional Group Header - The Functional Group Header provides the required control information such as date,
time and control number of the transmission as well as the value for the ANSI version that the two parties are
utilizing.
ST
Transaction Set Header - The Transaction Set Header establishes the transaction set that is used in the transmission.
This transaction set (ex. 820) identifies to all parties the type of information that will follow in the identified
segment.
SE
Transaction Set Trailer - The Transaction Set Trailer ends the transaction set and provides the count of the
transmitted segments.
GE
Functional Group Trailer - The Functional Group Trailer ends the transaction related information or data within the
boundaries of the ST header and SE trailer.
IEA
Interchange Control Trailer - The Interchange Control Trailer is the ending outer envelope of one or more Functional
Groups or interchange-related control segments. This trailer contains the number of the functional groups and the
established control number identified in the ISA.
Contained on the following pages is additional information that will help you in determining the appropriate values
for insertion in your ANSI transmission that is specific to Bank of America. This information is a supplement to the
ANSI standards and is a representation of data segments used in most versions and releases. Bank of America
supports all versions and releases of ANSI standards. If a content value is specified in these instructions, please use
the value provided in this document in the generation of that record.
If you should need additional assistance in determining what values are appropriate for these fields, please call the
EDI Implementation Support representative identified on the Bank of America customer support list.
Order of Structure
To properly process an 820 Payment Order/Remittance Advice transaction set, several data segments are required.
While the ANSI specifications may list some segments as optional, please refer to these instructions to insure
whether they are required to properly process an 820. While the following 820 structure is representative of
Version/Release 003040, others may apply and/or are supported.
Data Elements
Reference Reference
Designator Number Name Type Length Req.
Notes:
ISA02: 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.
ISA04: 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.
ISA05: Qualifier to designate the system/method of code structure used to designate the sender or receiver ID
element being qualified.
(16= Bank of America ID Qualifier)
ISA06: 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.
(055169452TST2 = Bank of America Sender ID during testing)
(0551694520002 = Bank of America Sender ID during production)
ISA07: Qualifier to designate the system/method of code structure used to designate the sender or receiver ID
element being qualified.
(ZZ = Mutually Defined)
(01 = DUNS Dun & Bradstreet)
ISA08: 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.
Notes (Continued):
ISA11: 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)
ISA12: This version number covers the interchange control segments (00401).
ISA13: 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.
The control number provided in the ISA header must match the control number provided in the IEA trailer.
This value signifies the beginning and end of an interchange session with Bank of America.
ISA15: Code to indicate whether data enclosed by this interchange envelope is test or production.
(T = Test Data)
(P = Production Data)
ISA16: This is a field reserved for future expansion in separating data element subgroups. (in the interest of a
migration to international standards, this should be different from the data element separator.)
Segment Identifier: GS
Segment Name: Functional Group Header
Segment Purpose: To indicate the beginning of a functional group and to provide control information
Data Elements
Reference Reference
Designator Number Name Type Length Req.
Notes:
GS02: Code identifying party sending transmission. Codes agreed to by trading partners.
(055169452002 = Bank of America Sender ID
GS03: Code identifying party receiving transmission. Codes agreed to by trading partners.
(Same as ISA08 unless requested otherwise)
GS06: Assigned number originated and maintained by the sender. The control number provided in the GS header
must match the control number provided in the GE trailer. This value signifies the beginning and end of a
functional group.
Notes (Continued):
GS07: Code used in conjunction with Data Element 480 to identify the issuer of the standard.
(X = Accredited Standards Committee X12)
GS08: Code indicating the version, release, subrelease and industry identifier of the EDI standard being used,
including the GS and GE segments. Positions 1-3, version number, positions 4-6, release and subrelease
level version; positions 7-12, industry or trade association identifier (optionally assigned by user).
Version 4010 = “004010”
Segment Identifier: ST
Segment Name: Transaction Set Header
Segment Purpose: To indicate the start of a transaction set and to assign a control number
Data Elements
Reference Reference
Designator Number Name Type Length Req.
Notes:
ST02: Identifying control number assigned by the originator for a transaction set. The control number provided in
the ST header must match the control number provided in the SE trailer. This value signifies the beginning
and end of an included transaction set.
Segment Identifier: SE
Segment Name: Transaction Set Trailer
Segment Purpose: To indicate the end of the transaction set and provide the count of the transmitted
segments (including the beginning ST and ending SE segments)
Data Elements
Reference Reference
Designator Number Name Type Length Req.
Notes:
SE01: Total number of segments included in a transaction set including ST and SE segments.
SE02: Identifying control number assigned by the originator for a transaction set. (The control number provided
in the SE trailer must match the control number provided in the ST header. This value signifies the
beginning and end of an included transaction set.)
Segment Identifier: GE
Segment Name: Functional Group Trailer
Segment Purpose: To indicate the end of the functional group and to provide control information
Data Elements
Reference Reference
Designator Number Name Type Length Req.
Notes:
GE01: Total number of transaction sets included in the functional group or interchange (transmission) group
terminated by the trailer containing this data element.
GE02: Assigned number originated and maintained by the sender. (The control number provided in the GE trailer
must match the control number provided in the GS header. This value signifies the beginning and end of a
functional group.)
Data Elements
Reference Reference
Designator Number Name Type Length Req.
Notes:
IEA02: 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.
(The control number provided in the IEA trailer must match the control number provided in the ISA
header. This value signifies the beginning and end of an interchange session.)
Heading:
Pos. Seg. Req. Loop Notes and
No. ID Name Des. Max.Use Repeat Comments
M 010 ST Transaction Set Header M 1
M 020 BPR Beginning Segment for Payment M 1
Order/Remittance Advice
030 NTE Note/Special Instruction O >1
035 TRN Trace O 1 c1
040 CUR Currency O 1 c2
050 REF Reference Identification O >1
060 DTM Date/Time Reference O >1
LOOP ID - N1 >1
070 N1 Name O 1 c3
080 N2 Additional Name Information O >1
090 N3 Address Information O >1
100 N4 Geographic Location O 1
110 REF Reference Identification O >1
120 PER Administrative Communications Contact O >1
130 RDM Remittance Delivery Method O 1
140 DTM Date/Time Reference O 1
LOOP ID - LX >1
290 LX Assigned Number O 1 n4
295 REF Reference Identification O >1
300 TRN Trace O >1
LOOP ID - NM1 >1
305 NM1 Individual or Organizational Name O 1
310 REF Reference Identification O >1
315 G53 Maintenance Type O 1
LOOP ID - N9 1
360 N9 Reference Identification O 1 n5
LOOP ID - AMT >1
370 AMT Monetary Amount O 1 c12
380 REF Reference Identification O >1
LOOP ID - N1 >1
390 N1 Name O 1
400 REF Reference Identification O >1
LOOP ID - EMS >1
410 EMS Employment Position O 1
420 ATN Attendance O >1
430 AIN Income O >1
440 PYD Payroll Deduction O >1
LOOP ID - ASM 1
540 ASM Amount and Settlement Method O 1
550 ADX Adjustment O 1
Segment: N1 Name
Position: 070
Loop: N1 Optional
Level: Heading
Usage: Optional
Max Use: 1
Purpose: To identify a party by type of organization, name, and code
Syntax Notes: 1 At least one of N102 or N103 is required.
2 If either N103 or N104 is present, then the other is required.
Semantic Notes:
Segment: N1 Name
Position: 390
Loop: N1 Optional
Level: Detail
Usage: Optional
Max Use: 1
Purpose: To identify a party by type of organization, name, and code
Syntax Notes: 1 At least one of N102 or N103 is required.
2 If either N103 or N104 is present, then the other is required.
Semantic Notes:
Comments: 1 This segment, used alone, provides the most efficient method of providing
organizational identification. To obtain this efficiency the "ID Code" (N104) must
provide a key to the table maintained by the transaction processing party.
2 N105 and N106 further define the type of entity in N101.
Revision History
REV # Date Modification TSAG # Author
1.00 March 11, Added Revision History to all existing N/A TSAG
2007 specifications