RFI Browser

Back  RFI # 2010: unique trn02 per tin in 835

Formal vs. Informal Help Informal Formal

Submitter

Sharon Sieve

Description

Mcare Mac uses the same ck/eft nbr on era's for same tax id. the payer sends one 835 envelope per tax id. The payer uses the same remit nbr for same date and tax id but does have a different npi. Need to verify if compliant or not. Issue is the files overwrite each other and we only receive one per trn02 nbr whe the file is distributed. Files are being lost and we have to request manually from our Clearing Account.

Submitter Assigned Keywords

unique trn02 in 835 era files

Response

In the 005010X221A1 TR3, the note for the TRN02 explicitly states, “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.”

And in Section 1.10.2.2 - Remittance Tracking the TR3 further states ' 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. The section also states '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. By default this means the unique value reported in the TRN02 must relate to only one 835 (ST-SE) and that 835's associated payment (check/EFT).

So for each transaction set (ST-SE), a unique TRN02 is required, and only 1 payee loop is allowed. The requirement for a unique value is related to the receiver in the relationship, and not just the provider. In the case stated, since the same tax ID is reported for the payee, sending the same value in multiple TRN02s violates the requirement that the number be unique within the sender/receiver relationship. However for that one payee multiple LX loops are allowed, and each LX may report a different NPI that is associated to the payee.

So bundling multiple LX Loops into one 835 is allowed as long as there is only one unique TRN02 for that 835 and corresponding payment (Check/EFT) within the Payer/Payee relationship. Using the same TRN02 value for multiple 835s and corresponding payments within the sender/receiver or payer/payee relationship is not allowed per the TR3.
Submission 2/13/2015
Status Date 4/2/2015
Status F - Final
Primary References
Document 005010X221
Section1.10.2.2
Page19