X12 275 TRN03 Field Guide: Originating Company Identifier Values and Common Mistakes
The same-looking reference number can mean two different things depending on who assigned it. TRN03 is the element that removes that ambiguity, and it's the one most often left blank.
TRN03 is the third element of the TRN segment — an identifier for the company that originated the reference number carried in TRN02. In a 275, it tells the receiving system whose numbering scheme the trace value belongs to, which matters once more than one trading partner's reference numbers are in play.
The elements that actually matter in practice
Example
A synthetic TRN03 value of 9887001122 identifying the company that assigned reference number CLM4471029. Synthetic data only.
Where this trips people up
Because TRN03 is easy to treat as an optional formality, synthetic test files often leave it blank or repeat the same placeholder value across every record regardless of which party actually generated the trace number. That works fine in a single-partner test environment, but the moment two trading partners' reference numbers happen to overlap, a receiving system with no reliable TRN03 has no way to tell them apart, and reconciliation logic that assumes reference numbers are globally unique starts matching attachments to the wrong claims.