TRN02 in X12 275: A Field Guide to Reference Identification
TRN02 is the actual trace number — the string a payer's system will search for when it tries to attach this document to an open request. Every other element in TRN exists to give this one value context.
TRN02 is the second element of the TRN segment — the reference identification value itself. In a 275 attachment transaction, it's typically populated with the original claim number the attachment supports or the identifier a payer assigned to a specific documentation request.
The elements that actually matter in practice
Example
A synthetic TRN02 value of CLM4471029, reused from the claim this attachment supports rather than generated independently. Synthetic data only.
Where this trips people up
Synthetic test generators built without a shared reference between the claim and attachment datasets often invent a fresh, random value for TRN02 on each 275 record instead of pulling the actual claim number. The transaction still passes basic structural checks, but any test that verifies whether the attachment can be located by its claim number fails, because there was never a real link to begin with — the same gap that causes unmatched attachments in production.