AlllOS MOSSMfl

PUBLICATIONS

NIST Special Publication 881-44

Federal Implementation Guideline

for Electronic Data Interchange

ASC X12 003040 Transaction Set 820A

Payment Order/Remittance Advice

(Automated Standard Application for

Payments)

Implementation Convention

NIST

QC

100

.U57

NO. 881 -W

1998

U.S. DEPARTMENT OF COMMERCE

Technology Administration

National Institute of

Standards and Technology
rhe National Institute of Standards and Technology was established in 1988 by Congress to "assist industry in the development of technology . . . needed to improve product quality, to modernize manufacturing processes,

to ensure product reliability . . . and to facilitate rapid commercialization ... of products based on new scientific

discoveries."

NIST, originally founded as the National Bureau of Standards in 1901, works to strengthen U.S. industry's

competitiveness; advance science and engineering; and improve public health, safety, and the environment. One

of the agency's basic functions is to develop, maintain, and retain custody of the national standards of

measurement, and provide the means and methods for comparing standards used in science, engineering,

manufacturing, commerce, industry, and education with the standards adopted or recognized by the Federal

Government.

As an agency of the U.S. Commerce Department's Technology Administration, NIST conducts basic and

applied research in the physical sciences and engineering, and develops measurement techniques, test methods, standards, and related services. The Institute does generic and precompetitive work on new and

advanced technologies. NIST's research facilities are located at Gaithersburg, MD 20899, and at Boulder, CO 80303.

Major technical operating units and their principal activities are listed below. For more information contact the

Publications and Program Inquiries Desk, 301-975-3058.

Office of the Director

• National Quality Program

• International and Academic Affairs

Technology Services

• Standards Services

• Technology Partnerships

• Measurement Services

• Technology Innovation

• Information Services

Advanced Technology Program

• Economic Assessment

• Information Technology and Applications

• Chemical and Biomedical Technology

• Materials and Manufacturing Technology

• Electronics and Photonics Technology

Manufacturing Extension Partnership

Program

• Regional Programs

• National Programs

• Program Development

Electronics and Electrical Engineering

Laboratory

• Microelectronics

• Law Enforcement Standards

• Electricity

• Semiconductor Electronics

• Electromagnetic Fields'

• Electromagnetic Technology 1

• Optoelectronics'

Chemical Science and Technology

Laboratory

• Biotechnology

• Physical and Chemical Properties

2

• Analytical Chemistry

• Process Measurements

• Surface and Microanalysis Science

Physics Laboratory

• Electron and Optical Physics

• Atomic Physics

• Optical Technology

• Ionizing Radiation

• Time and Frequency'

• Quantum Physics'

Materials Science and Engineering

Laboratory

• Intelligent Processing of Materials

• Ceramics

• Materials Reliability'

• Polymers

• Metallurgy

• NIST Center for Neutron Research

Manufacturing Engineering

Laboratory

• Precision Engineering

• Automated Production Technology

• Intelligent Systems

• Fabrication Technology

• Manufacturing Systems Integration

Building and Fire Research

Laboratory

• Structures

• Building Materials

• Building Environment

• Fire Safety Engineering

• Fire Science

Information Technology Laboratory

• Mathematical and Computational Sciences 2

• Advanced Network Technologies

• Computer Security

• Information Access and User Interfaces

• High Performance Systems and Services

• Distributed Computing and Information Services

• Software Diagnostics and Conformance Testing

'At Boulder, CO 80303.

2 Some elements at Boulder, CO.
NIST Special Publication 881-44

Federal Implementation Guideline

for Electronic Data Interchange

ASC X12 003040 Transaction Set 820A

Payment Order/Remittance Advice

(Automated Standard Application for

Payments)

Implementation Convention

Electronic Commerce Acquisition Program Management Office

Standard Management Committee - Secretariat

National Institute of Standards and Technology

Gaithersburg, MD 20899-0001

Editor: Dr. Jean-Philippe Favreau

January 1998

U.S. DEPARTMENT OF COMMERCE

William M. Daley, Secretary

Technology Administration

Gary R. Bachula, Acting Under Secretary for Technology

National Institute of Standards and Technology

Raymond G. Kammer, Director
Reports on Information Technology

The National Institute of Standards and Technology (NIST)'s Information Technology Laboratory (ITL)

develops standards and guidelines, provides technical assistance, and conducts research for computers

and resources. As part of the overall federal effort to establish a single face to industry for conducting

electronic commerce, ITL has been designated as the organization responsible for coordinating the

development of Federal Implementation Conventions (ICs) for Electronic Data Interchange (EDI). ICs are

defined by functional-area experts who create and select options from standard EDI Transaction Sets to

yield the implementations to be used for practical EDI. These ICs are made available to federal agencies

and industry by electronic means and this Special Publication Series.

National Institute of Standards and Technology Special Publication 881-44

Natl. Inst. Stand. Technol. Spec. Publ. 881-44, 20 pages (Jan. 1998)

CODEN: NSPUE2

U.S. GOVERNMENT PRINTING OFFICE

WASHINGTON: 1998

For sale by the Superintendent of Documents, U.S. Government Printing Office, Washington, DC 20402
820 Payment Order/Remittance Advice

Functional Group ID=RA

Introduction:

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.

Notes:

1. This is the current standardfor Federal Domestic Assistance payments made via the Automated Standard

Application for Payments (ASAP) system ofthe Financial Management Service, US Treasury.

2. The totalpayment amount in one 820 transaction set represents the total amountpaid to one Payment

Requester on behalfofone or more Federal Program Agenciesfor distribution to one or more Recipient

Organizations.

Heading:

Must Use

Pos. No. 010Seg. IDST

Must Use 020 BPR

Not Used 030 NTE

035 TRN

Not Used 040 CUR

050 REF

Not Used 060 DTM

070 Nl

Not Used 080 N2

Not Used 090 N3

Not Used 100 N4

Not Used 110 REF

Not Used 120 PER

Detail:

Pos. No.Seg. ID

010 ENT

020 Nl

Not Used 030 N2

Not Used 040 N3

Req. Loop Notes and

Name Pes. Max.Use Repeat Comments

Transaction Set Header M 1

Beginning Segment for Payment M 1 Order/Remittance Advice

Note/Special Instruction O >1

Trace O 1 cl

Currency O 1 c2

Reference Numbers 0 >1

Date/Time/Period 0 >1 LOOP ID - Nl >1

Name 0 ! c3

Additional Name Information 0 >1

Address Information 0 >1

Geographic Location 0 1

Reference Numbers 0 >1

Administrative Communications Contact 0 >1

Req. Loop Notes and

Name Pes. Max.Use Repeat Comments

LOOP ID -Nl

Name

Additional Name Information

Address Information

003040F820A0 July 29, 1997
820A - Automated Standard Application for Payments

Not Used

Not Used

Not Used

Not Used

Not Used

Not Used 130

140

141

Not Used 144

147

148

150

160

Not Used 204

IT1

REF

DTM

LOOPID-IT1

Baseline Item Data (Invoice) O

SLN

LOOP ID - SLN

Subline Item Detail O

ITA

TXI

RMR

NTE

LOOP ID - ITA

Allowance, Charge or Service

Tax Information

O

O

LOOP ID - RMR

Remittance Advice Accounts Receivable Open O

Item Reference

Note/Special Instruction O

SLN

LOOP ID - SLN

Subline Item Detail O

1

>1

>1

Not Used 050 N4 Geographic Location O 1

Not Used 060 REF Reference Numbers O >1

Not Used 070 PER Administrative Communications Contact O >1

LOOP ID - ADX >1

Not Used 080 ADX Adjustment O 1 c6

iNot used uvu IN 1 c. iNOTc/opecicU instruction >11

"Wot T IcpH i on PER Administrative* Communication5; Contact o >1

Not Used 105 DTM Date/Time/Period O 1

F OOP ID - REF >1

Not Used 110 REF Reference Numbers O 1

Not Used 120 DTM Date/Time/Period 0 >1

>1

c7 LOOP ID - REF >1

Reference Numbers O ]

Date/Time/Period O 1

LOOP ID - ITA >1

Not Used 142 ITA Allowance, Charge or Service O 1

Not Used 143 TXI Tax Information O >1

>1

LOOP ID - REF >1

Not Used 145 REF Reference Numbers O 1

Not Used 146 DTM Date/Time/Period O >1

>1

170 REF Reference Numbers O >1

Not Used 180 DTM Date/Time/Period O >1 LOOP ID - IT1 >1

Not Used 190 IT1 Baseline Item Data (Invoice) O 1 c9 LOOP ID - REF >1

Not Used 200 REF Reference Numbers O 1

Not Used 201 DTM Date/Time/Period O 1

LOOP ID - ITA >1

Not Used 202 ITA Allowance, Charge or Service O 1

Not Used 203 TXI Tax Information O >1

>1

LOOP ID - REF >1

Not Used 205 REF Reference Numbers O 1

Not Used 206 DTM Date/Time/Period O >1

LOOP ID - ITA >1

003040F820A0 July 29, 1997
820A - Automated Standard Application for Payments

Not Used 207 ITA Allowance, Charge or Service O 1

Not Used 208 TXI Tax Information O >1

LOOP ID - INV

Not Used 350 INV Investment Vehicle Selection O 1

Not Used 355 DTP Date or Time or Period O >1

LOOP ID - ADX >1

Not Used 210 ADX Adjustment O 1 clO

Not Used 220 NTE Note/Special Instruction O >1

Not Used 230 PER Administrative Communications Contact O >1 LOOPID-REF >1

Not Used 240 REF Reference Numbers O 1

Not Used 250 DTM Date/Time/Period O >1

LOOPID-IT1 >1

Not Used 260 IT1 Baseline Item Data (Invoice) O 1 cl I LOOPID-REF >1

Not Used 270 REF Reference Numbers O 1

Not Used 271 DTM Date/Time/Period O 1

LOOP ID - ITA >1

Not Used 272 ITA Allowance, Charge or Service O 1

Not Used 273 TXI Tax Information O >1

LOOPLD-SLN >1

Not Used 274 SLN Subline Item Detail O 1 LOOP ID - REF >1

Not Used 275 REF Reference Numbers O 1

Not Used 276 DTM Date/Time/Period O >1

LOOP ID - ITA >1

Not Used 277 ITA Allowance, Charge or Service O 1

Not Used 278 TXI Tax Information O >1

LOOP ID -TXP >1

Not Used 280 TXP Tax Payment O 1

Not Used 285 TXI Tax Information O >1

LOOP ID -LX >1

Not Used 290 LX Assigned Number O 1

Not Used 295 REF Reference Numbers O >1

Not Used 300 TRN Trace O >1

LOOPID-NM1 >1

Not Used 305 NM1 Individual or Organizational Name O 1

Not Used 310 REF Reference Numbers O >1

Not Used 315 G53 Maintenance Type O 1 LOOP ID -AIN >1

Not Used 320 AIN Income O 1

Not Used 325 QTY Quantity O >1

Not Used 330 DTP Date or Time or Period 0 >1

LOOP ID -PEN >1

Not Used 335 PEN Pension Information O 1

Not Used 340 AMT Monetary Amount O >1

Not Used 345 DTP Date or Time or Period O >1

003040F820A0 3 July 29, 1997
820A - Automated Standard Application for Payments

Summary:

Must Use

Pos. No. 010Seg.

IS

SE

Name

Transaction Set Trailer

Req.

Pes. MMax.Use

Loop

Repeat

Notes and

Comments

Transaction Set Comments

1. The TRN segment is used to uniquely identify a payment order/remittance advice.

2. The CUR segment does not initiate a foreign exchange transaction.

3. The Nl loop allows for name/address information for the payer and payee which would be utilized to address

remittance(s) for delivery.

4. ENT09 may contain the payee's accounts receivable customer number.

5. Allowing the Nl 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).

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

7. Loop IT1 within the ADX loop is the adjustment line item detail loop.

8. Loop RMR is for open items being referenced or for payment on account.

9. Loop IT1 within the RMR loop is the remittance line item detail loop.

10. This ADX loop can only contain adjustment information for the immediately preceding RMR segment and

affects the amount (RMR04) calculation. If this adjustment amount is not netted to the immediately preceding

RMR, use the outer ADX loop (position 080).

11. Loop IT1 within the ADX loop is the adjustment line item detail loop.

003040F820A0 4 July 29, 1997
820A - Automated Standard Application for Payments

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

ST Transaction Set Header

010

Heading

Mandatory

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

1 The transaction set identifier (ST01) used by the translation routines of the

interchange partners to select the appropriate transaction set definition (e.g., 810

selects the Invoice Transaction Set).

Ref.

Pes.

Must Use ST01

Must Use ST02

Data

Element

143

329

Data Element Summary

Name Attributes

Transaction Set Identifier Code M ID 3/3

Code uniquely identifying a Transaction Set

820 XI 2.4 Payment Order/Remittance Advice

Transaction Set Control Number M AN 4/9

Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set 1) Contains the Entry Detail Sequence portion oftheACH Trace Number (7

positions).

2) Assigned by the Federal Reserve Bank ofRichmond.

3) Must equal the value in data element SE02.

003040F820A0 5 July 29, 1997
820A - Automated Standard Application for Payments

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

BPR Beginning Segment for Payment Order/Remittance Advice

Semantic Notes:

Comments:

020

Heading

Mandatory

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

12

3

4

5

6

1

2

3

4

5

6

If either BPR06 or BPR07 is present, then the other is required.

If BPR08 is present, then BPR09 is required.

If either BPR12 or BPR13 is present, then the other is required.

If BPR14 is present, then BPR15 is required.

If either BPR18 or BPR19 is present, then the other is required.

If BPR20 is present, then BPR21 is required.

BPR02 specifies the payment amount.

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

BPR12 and BPR13 relate to the receiving depository financial institution (RDFI).

BPR15 is the account number of the receiving company to be debited or credited

with the payment order.

BPR17 is a code identifying the business reason for this payment.

BPR18, BPR19, BPR20 and BPR21, if used, identify a third bank identification

number and account to be used for return items only.

BPR09 is the account of the company originating the payment. This account may be

debited or credited depending on the type of payment order.

Ref.

Pes.

Must Use BPR01

Must Use BPR02

Must Use BPR03

Must Use BPR04

Must Use BPR05

Must Use BPR06

Data

Element

305

782

478

591

812

506

Data Element Summary

Name Attributes

Transaction Handling Code M ID 1/1

Code designating the action to be taken by all parties

C Payment Accompanies Remittance Advice

Monetary Amount M R 1/15

Monetary amount

1. Totalpayment amount to be credited to the Payment Requester's account

at the receiving financial institution. Equal to the ACH entry detail total

transaction amount,

2. A decimalpoint is required when the amount is in dollars and cents. Totalpayment amount cannot exceed eleven characters (including the

decimal) when converted to NACHAformat, e.g., 99999999.99.

Credit/Debit Flag Code M ID 1/1

Code indicating whether amount is a credit or debit

C Credit

Payment Method Code M ID 3/3

Code identifying the method for the movement of payment instructions

ACH Automated Clearing House (ACH)

Payment Format Code O ID 1/10

Code identifying the payment format to be used

CTX Corporate Trade Exchange (CTX) (ACH)

(DFI) ID Number Qualifier X ID 2/2

Code identifying the type of identification number of Depository Financial

Institution (DFI)

Pertains to Originating DFI.

003040F820A0 6 July 29, 1997
820A - Automated Standard Application for Payments

01

Must Use BPR07

Not Used BPR08

Not Used BPR09

Must Use BPR10

507

896

508

509

Not Used BPR11

Must Use BPR12

510

506

Must Use BPR13 507

Must Use BPR14 896

Must Use BPR15

Must Use BPR16

Not Used BPR17

Not Used BPR18

Not Used BPR19

003040F820A0

508

513

1048

506

507

ABA Transit Routing Number Including Check Digits

(9 digits)

(DFI) Identification Number X AN 3/12

Depository Financial Institution (DFI) identification number

Identifies the organization originating the payment, in this case, ASAP.

Contains the ASAPABA Number (05103680-3).

Account Number Qualifier Code O ID 2/2

Code indicating type of bank account or other financial asset Account Number X AN 1/35

Account number assigned

Originating Company Identifier O AN 10/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

/. Identifies ASAP as the originating company.

2. Contains the 9-digit ABA Numberfor ASAPpreceded by the number "9 "

to indicate a user assigned identifier.

Originating Company Supplemental Code O AN 9/9

A code defined between the originating company and the originating

depository financial institution (ODFI) that uniquely identifies the company

initiating the transfer instructions

(DFI) ID Number Qualifier X ID 2/2

Code identifying the type of identification number of Depository Financial

Institution (DFI)

Pertains to the Receiving DFI.

0 1 ABA Transit Routing Number Including Check Digits

(9 digits)

(DFI) Identification Number X AN 3/12

Depository Financial Institution (DFI) identification number

1. Identifies the receiving DFI.

2. Contains the 9-digit ABA Numberfor the Payment Requester's ACHDFI

as indicated in the ASAP Payment Requester Profile.

Account Number Qualifier Code O ID 2/2

Code indicating type of bank account or other financial asset

1. Identifies the type ofaccount at the ACHDFI indicated in the Payment

Requester Profile.

AN 1/35

2. BPR15 identifies the account number.

DA Demand Deposit

SG Savings

Account Number

Account number assigned

Identifies the Payment Requester's ACH bank account to be credited.

Effective Entry Date O DT 6/6

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

Indicates the Settlement Date in YYMMDDformat

Business Function Code O ID 1/3

Code identifying the business reason for this payment

(DFI) ID Number Qualifier X ID 2/2

Code identifying the type of identification number of Depository Financial

Institution (DFI)

(DFI) Identification Number X AN 3/12

July 29, 1997
820A - Automated Standard Application for Payments

Depository Financial Institution (DFI) identification number

Not Used BPR20 896 Account Number Qualifier Code O ID 2/2

Code indicating type of bank account or other financial asset Not Used BPR21 508 Account Number X AN 1/35

Account number assigned

003040F820A0 8 July 29, 1997
820A - Automated Standard Application for Payments

Segment: TRN Trace

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

Notes:

Ref.

Pes.

Must Use TRN01

Must Use TRN02

Not Used TRN03

Not Used TRN04

035

Heading

Optional

1To uniquely identify a transaction to an application

1 TRN02 provides unique identification for the transaction.

2 TRN03 identifies an organization.

3 TRN04 identifies a further subdivision within the organization.

This segment must be used in each ASAP 820. It allowsfor identification ofthe

transaction setsfor tracking purposes.

Data Element Summary

Data

Element

481

Attributes

M ID 1/2

127 M AN 1/30

509

127

Name

Trace Type Code

Code identifying which transaction is being referenced

Pertains to the ACH Trace Number.

1 Current Transaction Trace Numbers

Reference Number

Reference number or identification number as defined for a particular

Transaction Set, or as specified by the Reference Number Qualifier.

1. Contains the ACH Trace Number.

2. Must contain all 15 positions to conform to NACHAformatfor

identification ofthe transaction set within the banking community.

Originating Company Identifier 6 AN 10/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

Reference Number O AN 1/30

Reference number or identification number as defined for a particular

Transaction Set, or as specified by the Reference Number Qualifier.

003040F820A0 9 July 29, 1997
820A - Automated Standard Application for Payments

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

Notes:

REF Reference Numbers

050

Heading

Optional

>1

To specify identifying numbers.

1 At least one of REF02 or REF03 is required.

This segment must be used at least once but not more than twice in each transaction

set

Must Use

Ref.

Pes.

REF01

Must Use REF02

Not Used REF03

One occurrence ofthis REF segment must contain the partial ASAP Sequence

Number, which identifies the transaction within ASAP. This occurrence is required

The other occurrence is optional It contains the Requester Reference Number, an

optional data element in ASAPfor use at the Payment Requester's discretion.

Data

Element

128

127

352

Data Element Summary

Attributes

M ID 2/2

Name

Reference Number Qualifier

Code qualifying the Reference Number.

55 Sequence Number

Usedfor the required partial ASAP Sequence

Number.

EM Electronic Payment Reference Number

Usedfor the optional Requester Reference Number.

Reference Number X AN 1/30

Reference number or identification number as defined for a particular

Transaction Set, or as specified by the Reference Number Qualifier.

/. When REF01 is 55, this element containsfirstfourportions ofthe ASAP

Sequence Number (Payment Request Date, Input Endpoint, Screen

Sequence Number, and Payment Request Timestamp). (29 positions). The

Payment Request Item Number is not included

2. When REF01 is EM, this element contains the Requester Reference

Number. (15 positions).

Description X AN 1/80

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

003040F820A0 10 July 29, 1997
820A - Automated Standard Application for Payments

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

Notes:

Nl Name

070

Nl

Heading

Optional

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

1 At least one of N1 02 or N1 03 is required.

2 If either N103 or N104 is present, then the other is required.

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 N1 05 and N1 06 further define the type of entity in N1 0 1

There must be two iterations ofthe Nl loop.

One iteration must identify the Payee - Le., the Payment Requester.

The other iteration must identify the Payer - Le., ASAP.

Ref.

Pes.

Must Use N101

Must Use N102

N103

N104

Not Used N105

Data Element Summary

Data

Element Name

98

93

66

67

706

Attributes

Entity Identifier Code M ID 2/2

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

PE Payee

The Payment Requester receiving thefunds.

PR Payer

The ASAP system.

Name X AN 1/35

Free-form name

1. IfNIOl is code PE, this element contains the Payment Requester Short

Name as defined in the Payment Requester Profile. (10 positions).

2. IfNIOl is code PR, this element contains the literal, "Treasury/FMSASAP".

Identification Code Qualifier X ID 1/2

Code designating the system/method of code structure used for Identification

Code (67)

1. IfNIOl is code PE, this element is required.

2. IfNIOl is code PR, this element is not used.

93 Code assigned by the organization originating the

transaction set Identification Code X AN 2/17

Code identifying a party or other code

1. IfNIOl is code PE, this element is required and contains the Payment

Requester ID defined in ASAP (7 positions).

2. IfNIOl is code PR, this element is not used.

Entity Relationship Code

Code describing entity relationship

O ID 2/2

003040F820A0 11 July 29, 1997
820A - Automated Standard Application for Payments

Not Used N106 98 Entity Identifier Code O ID 2/2

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

003040F820A0 12 July 29, 1997
820A - Automated Standard Application for Payments

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

ENT Entity

Notes:

010

ENT

Detail

Optional

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

meaningful to those entities

1 If any of ENT02 ENT03 or ENT04 is present, then all are required.

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

3 If either ENT08 or ENT09 is present, then the other is required.

1 This segment allows for the grouping of data by entity/entities at or within a master/masters. A master (e.g., an organization) can be comprised of numerous

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

(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. Identifies a Recipient Organization /Federal Program Agency combination. At least

one ENTloop is requiredper transaction set

There will be one or more RO/FPA combinations within a singlepayment transaction

to a Payment Requester, and each RO/FPA combination will be represented by one

ENTloop within the 820 transaction set. There will be one or more RMR loops within

each ENTloop, where each RMR loop refers to a single ASAP account. Thepresence

ofonly one RMR in an 820 indicates an individualpayment, and multiple RMRs

indicate a summarypayment

Ref.

Pes.

Not Used ENT01

Must Use ENT02

Must Use ENT03

Data

Element

554

98

66

Must Use ENT04 67

Data Element Summary

Name Attributes

Assigned Number O NO 1/6

Number assigned for differentiation within a transaction set

Entity Identifier Code X ID 2/2

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

Indicates that the sending sub-entity is a Federal Program Agency,

2R Federal Facility

Identification Code Qualifier X ID 1/2

Code designating the system/method of code structure used for Identification

Code (67)

Indicates the type ofID code ofthe sending sub-entity.

ZZ Mutually Defined

Identification Code X AN 2/17

003040F820A0 13 July 29, 1997
Must Use ENT05

Must Use ENT06

Must Use ENT07

Not Used ENT08

Not Used ENT09

820A - Automated Standard Application for Payments

Code identifying a party or other code

Contains the required Agency Location Code (ALC) (8 positions) and the

optional Region (2 positions).

98 Entity Identifier Code X ID 2/2

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

Indicates that the receiving sub-entity is the Recipient Organization.

MA Party for whom Item is Ultimately Intended

66 Identification Code Qualifier X ID 1/2

Code designating the system/method of code structure used for Identification

Code (67)

Indicates the type ofID ofthe receiving sub-entity.

93 Code assigned by the organization originating the

transaction set 67 Identification Code X AN 2/17

Code identifying a party or other code

Contains the Recipient Organization ID as defined within ASAP (7

positions). Identifies the organization granted Federalfunds.

128 Reference Number Qualifier X ID 2/2

Code qualifying the Reference Number.

127 Reference Number X AN 1/30

Reference number or identification number as defined for a particular

Transaction Set, or as specified by the Reference Number Qualifier.

003040F820A0 14 July 29, 1997
820A - Automated Standard Application for Payments

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

Notes:

Ref.

Pes.

Must Use N101

Must Use N102

Not Used N103

Not Used N104

Not Used N105

Not Used N106

Nl Name

020

Nl

Detail

Optional

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

1 At least one of N102 or N103 is required.

2 If either N1 03 or N104 is present, then the other is required.

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 N 101.

There should be two iterations ofthis Nl loop within each ENTloop.

One iteration must identify the Federal Program Agency granting thefunds (the

sending sub-entity).

The other iteration must identify the Recipient Organization which ultimately receives

the Federalfunds (the receiving sub-entity).

Data

Element

98

93

66

67

706

98

Data Element Summary

Name Attributes

Entity Identifier Code M ID 2/2

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

1. Indicates the type ofsending or receiving sub-entity.

2. For the sending sub-entity (the Federal Program Agency), the value of

this element must equal the value ofelement ENT02.

3. For the receiving sub-entity (the Recipient Organization), the value of

this element must equal the value ofelement ENT05.

2R Federal Facility

Federal Program Agency

MA Party for whom Item is Ultimately Intended

Recipient Organization

Name X AN 1/35

Free-form name

1. IfNIOl is code 2R, this element contains the Federal Program Agency's

short name as indicated in its ASAP Profile (10 positions).

2. IfNIOl is code MA, this element contains the Recipient Organization's

short name as indicated in its ASAP Profile (10 positions).

Identification Code Qualifier X ID 1/2

Code designating the system/method of code structure used for Identification

Code (67)

Identification Code X AN 2/17

Code identifying a party or other code

Entity Relationship Code O ID 2/2

Code describing entity relationship

Entity Identifier Code O ID 2/2

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

003040F820A0 15 July 29, 1997
820A - Automated Standard Application for Payments

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

RMR Remittance Advice Accounts Receivable Open Item Reference

150

RMR

Detail

Optional

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

to convey the appropriate detail

1 If either RMR01 or RMR02 is present, then the other is required.

1 If RMR03 is present, it specifies how the cash is to be applied.

1 Parties using this segment should agree on the content of RMR01 and RMR02 prior

to initiating communication.

2 If RMR03 is not present, this is a payment for an open item. If paying an open item,

RMR02 must be present. If not paying a specific open item, RMR04 must be present.

3 RMR04 is the amount paid.

4 RMR05 may be needed by some payees to distinguish between duplicate reference

numbers.

5 RMR06 may be used to specify discount taken.

Notes: There is one RMR loop for each payment request against an ASAP account There

must be at least one RMR loop within each ENT loop.

Ref.

Pes.

Must Use RMR01

Must Use RMR02

Not Used RMR03

Must Use RMR04

Must Use RMR05

Not Used RMR06

Data Element Summary

Data

Element Name

128 Reference Number Qualifier

Code qualifying the Reference Number.

1 1 Account Number

Attributes

X ID 2/2

Number identifies a telecommunications industry

account

127 Reference Number X AN 1/30

Reference number or identification number as defined for a particular

Transaction Set, or as specified by the Reference Number Qualifier.

Contains the ASAP Account ID (20 positions).

482 Payment Action Code O ID 2/2

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

782 Monetary Amount O R 1/15

Monetary amount

The actual paymentfor the request against the ASAP Account ID in RMR02

for the Recipient Organization in ENT07from the Federal Program Agency

in ENT04.

Ill Total Invoice or Credit/Debit Amount O R 1/15

Amount of Invoice (including charges, less allowances) before terms discount

(if discount is applicable) or debit amount or credit amount of referenced

items.

Contains the amount requestedfrom the ASAP Account in RMR02for the

Recipient Organization in ENT07from the Federal Program Agency in

ENT04.

780 Amount of Discount Taken O R 1/15

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

discount permitted

003040F820A0 16 July 29, 1997
820A - Automated Standard Application for Payments

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

Notes:

Must Use

Ref.

Pes.

REF01

Must Use REF02

Not Used REF03

REF Reference Numbers

170

RMR

Detail

Optional

>1

To specify identifying numbers.

1 At least one of REF02 or REF03 is required.

This REF segment must appear at least once but no mote than twicefor each RMR

loop.

One occurrence ofthis REF segment must contain the Payment Request Item Number

portion ofthe ASAP Sequence Number. This occurrence is required.

The other occurrence is optional It contains the Catalog ofFederal Domestic

Assistance (CFDA) number, an optional data element in ASAP.

Data

Element

128

Data Element Summary

Name

Reference Number Qualifier

Code qualifying the Reference Number.

IX Item Number

Attributes

M ID 2/2

127

352

Indicates that the Payment Request Item Number

follows.

ZZ Mutually Defined

Indicates that the CFDA Numberfollows.

Reference Number X AN 1/30

Reference number or identification number as defined for a particular

Transaction Set, or as specified by the Reference Number Qualifier.

1. IfREFOl is code FX, this element contains the Payment Request Item

Number portion ofthe ASAP Sequence Number (6 positions).

2. IfREFOl is code ZZ, this element contains the Catalog ofFederal

Domestic Assistance (CFDA) number (5 positions).

Description X AN 1/80

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

003040F820A0 17 July 29, 1997
820A - Automated Standard Application for Payments

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

SE Transaction Set Trailer

010

Summary

Mandatory

1To indicate the end of the transaction set and provide the count of the transmitted

segments (including the begmning (ST) and ending (SE) segments).

SE is the last segment of each transaction set.

Data Element Summary

Ref. Data

Pes. Element Name Attributes

Must Use SE01 96 Number of Included Segments M NO 1/10

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

segments

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

Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set Contains the Entry Detail Sequenceportion ofthe ACH Trace Number (7

positions). Must equal the value in data element ST02.

003040F820A0 18 July 29, 1997
Technical Publications

Periodical

Journal of Research of the National Institute of Standards and Technology—Reports NIST research

and development in those disciplines of the physical and engineering sciences in which the Institute is

active. These include physics, chemistry, engineering, mathematics, and computer sciences. Papers cover a broad range of subjects, with major emphasis on measurement methodology and the basic technology

underlying standardization. Also included from time to time are survey articles on topics closely related to the Institute's technical and scientific programs. Issued six times a year.

Nonperiodicals

Monographs—Major contributions to the technical literature on various subjects related to the

Institute's scientific and technical activities. Handbooks—Recommended codes of engineering and industrial practice (including safety codes) developed in cooperation with interested industries, professional organizations, and regulatory bodies.

Special Publications—Include proceedings of conferences sponsored by NIST, NIST annual reports, and

other special publications appropriate to this grouping such as wall charts, pocket cards, and bibliographies.

National Standard Reference Data Series—Provides quantitative data on the physical and chemical

properties of materials, compiled from the world's literature and critically evaluated. Developed under a worldwide program coordinated by NIST under the authority of the National Standard Data Act (Public

Law 90-396). NOTE: The Journal of Physical and Chemical Reference Data (JPCRD) is published

bimonthly for NIST by the American Chemical Society (ACS) and the American Institute of Physics (AIP).

Subscriptions, reprints, and supplements are available from ACS, 1155 Sixteenth St., NW, Washington, DC

20056.

Building Science Series—Disseminates technical information developed at the Institute on building

materials, components, systems, and whole structures. The series presents research results, test methods, and

performance criteria related to the structural and environmental functions and the durability and safety

characteristics of building elements and systems.

Technical Notes—Studies or reports which are complete in themselves but restrictive in their treatment of

a subject. Analogous to monographs but not so comprehensive in scope or definitive in treatment of the

subject area. Often serve as a vehicle for final reports of work performed at NIST under the sponsorship of

other government agencies.

Voluntary Product Standards—Developed under procedures published by the Department of Commerce

in Part 10, Title 15, of the Code of Federal Regulations. The standards establish nationally recognized

requirements for products, and provide all concerned interests with a basis for common understanding of

the characteristics of the products. NIST administers this program in support of the efforts of private-sector

standardizing organizations.

Order the following NIST publications—FIPS and NISTIRs—from the National Technical Information

Service, Springfield, VA 22161.

Federal Information Processing Standards Publications (FIPS PUB)—Publications in this series

collectively constitute the Federal Information Processing Standards Register. The Register serves as the

official source of information in the Federal Government regarding standards issued by NIST pursuant to the Federal Property and Administrative Services Act of 1949 as amended, Public Law 89-306 (79 Stat. 1127), and as implemented by Executive Order 11717 (38 FR 12315, dated May 11, 1973) and Part 6 of

Title 15 CFR (Code of Federal Regulations).

NIST Interagency Reports (NISTIR)—A special series of interim or final reports on work performed by

NIST for outside sponsors (both government and nongovernment). In general, initial distribution is handled

by the sponsor; public distribution is by the National Technical Information Service, Springfield, VA 22161,

in paper copy or microfiche form.
U

i-

<u© ^ O C/J c o E 3 oI OS

Os

00o

Q 6X)

o