TRN

Reassociation Key

Pos: 035	Max: 1
Heading - Optional
Loop: N/A	Elements: 4

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

The payment and remittance have not been separated.

3

Financial Reassociation Trace Number

The payment and remittance information have been separated and need to be reassociated by the receiver.

TRN02

127

Reference Identification
Description: Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
Health Care Industry: Check or EFT Trace Number
This field is used to re-associate the payment with the remittance information.

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
TRN03 must contain the Federal Tax ID Number proceeded by a 1. When TRN03 is used, it must be identical to BPR10.
This is required when the receiver needs an originating company identification to reassociate a payment to a remittance.

O

AN

10/10

Situational

TRN04

127

Reference Identification
Description: Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
Health Care Industry: Originating Company Supplemental Code
If both TRN04 and BPR11 are used they must be identical.
This is required when the Payer is sending multiple premium payments for multiple group plans and the receiver needs an additional identifier for re-association.

O

AN

1/30

Situational

1.

TRN02 provides unique identification for the transaction.

2.

TRN03 identifies an organization.

3.

TRN04 identifies a further subdivision within the organization.

Notes:

1. The purpose of this segment is to uniquely identify this transaction set and aid in the reassociating payment and remittance data that have been separated. See section 2.2.5 and 2.2.6 for more information.

Example:

TRN*1*12345*1512345678*1999999999~