TRN

Reassociation Trace Number

Pos: 040

Max: 1

Heading - Optional

Loop: N/A

Elements: 4


User Option (Usage): Required
To uniquely identify a transaction to an application

Element Summary:

 

Ref

Id

Element Name

Req

Type

Min/Max

Usage

 

TRN01

481

Trace Type Code
Description: Code identifying which transaction is being referenced

M

ID

1/2

Required

 

Code

Name

 

1

Current Transaction Trace Numbers

 

TRN02

127

Reference Identification
Description: Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
Industry: Check or EFT Trace Number
This number must be unique within the sender/receiver relationship. The number is assigned by the sender. For example, if a payment is made by check, this number should be the check number.
There may be a number of uses for the trace number. If payment and remittance detail are separated, this number is used to reassociate data to dollars. See 2.2.3, Reassociation of Data and Dollars.

M

AN

1/30

Required

 

TRN03

509

Originating Company Identifier
Description: 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
Industry: Payer Identifier
TRN03 must contain the Federal Tax ID Number, preceded by a “1.” When BPR10 is used, it must be identical to TRN03.

O

AN

10/10

Required

 

TRN04

127

Reference Identification
Description: Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
Industry: Originating Company Supplemental Code
If both TRN04 and BPR11 are used, they must be identical.
This element is required when information beyond the Originating Company Identifier in TRN03 is necessary for the payee to identify the source of the payment.

O

AN

1/30

Situational


Semantics:

1.

TRN02 provides unique identification for the transaction.

2.

TRN03 identifies an organization.

3.

TRN04 identifies a further subdivision within the organization.


Notes:

1. This segment’s purpose is to uniquely identify this transaction set and to aid in reassociating payments and remittances that have been separated.

Example:

TRN*1*12345*1512345678*199999999~



Prev First Page Next