The ANSI 835, TRN02 Reference Identification is described as follows:
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
SEMANTIC: TRN02 provides unique identification for the transaction.
INDUSTRY NAME: Check or EFT Trace Number
This number must be unique within the sender/receiver relationship. The number is assigned by the sender. If payment is made by check, this must be the check number. If payment is made by EFT, this must be the EFT reference number. If this is a non-payment 835, this must be a unique remittance advice identification number.
See 1.10.2.3, Reassociation of Dollars and Data, for additional information.
Section 1.10.2.2 Remittance Tracking indicates the following:
1.10.2.2 Remittance Tracking
Remittance Tracking Segments
The Reassociation Key Segment, TRN, contains a trace number for the transaction set. Trace Number, TRN02, which is used to reassociate payments and remittances sent separately, must be a unique number for this business purpose between the payer and the payee. This will be:
For check payments, TRN02 is the check number.
For EFT payments, TRN02 is the unique number assigned by the payer to identify this EFT.
For non-payment transactions, TRN02 is a unique number generated by the transaction set originator as that 835's identification number (e.g., a control number plus a suffix or a date/time stamp).
In addition, TRN03 is the payer's identification number. TRN03 allows the payee to avoid matching problems in case multiple payers use the same number in TRN02.
NOTE Due to the need for remittance tracking, there is a one to one relationship between any specific 835 and the related payment mechanism (check or EFT). One 835 must only relate to a single payment mechanism and one payment mechanism must only relate to a single 835. The only exception is a non-payment 835 (BPR02=0) where there is no associated payment mechanism.
A payer is using the same trace number (TRN02) for multiple providers based on Payee ID. For example, REMIT1 was issued 5 times to Provider 1 but in each instance the Payee ID (NP) was different. The same trace number is also seen with Provider 2 and Provider 3 (Separate facilities). Could you clarify who is considered the ‘receiver’ as described in the TRN02 (This number must be unique within the sender/receiver relationship.)? Would this be the Receiver in GS03 or is “Receiver” being used to mean “Payee”?
Refer to Note in 005010X221A1 front matter section 1.10.2.2 Remittance Tracking:
“The Reassociation Key Segment, TRN, contains a trace number for the transaction set. Trace Number, TRN02, which is used to reassociate payments and remittances sent separately, must be a unique number for this business purpose between the payer and the payee.”
In reference to the TRN02, the number must be unique within the sender and receiver relationship. The intent of the authors of the 005010X221A1 is the receiver is the payee in the 1000B loop and the sender is the payer in the 1000A loop.
Refer to Note in 005010X221A1 front matter section 1.10.2.2 Remittance Tracking:
“The Reassociation Key Segment, TRN, contains a trace number for the transaction set. Trace Number, TRN02, which is used to reassociate payments and remittances sent separately, must be a unique number for this business purpose between the payer and the payee.”
In reference to the TRN02, the number must be unique within the sender and receiver relationship. The intent of the authors of the 005010X221A1 is the receiver is the payee in the 1000B loop and the sender is the payer in the 1000A loop.