X12 275 BGN01 (Transaction Set Purpose Code): Format, Values, and Testing Notes
One code decides whether the receiving system treats this attachment as new or as a do-over. Miss it in test data and your reissue path never gets exercised until a real resend breaks it.
BGN01 is the first element of the BGN segment in an X12 275 — a single code stating whether the transaction is being submitted for the first time or being reissued after an earlier attempt.
Valid code values
Example
A synthetic BGN marking this transaction as a reissue (BGN01=18) of a previously submitted attachment set, still carrying its original control number. Synthetic data, not a real submission.
Where this trips people up
Synthetic 275 fixtures overwhelmingly default BGN01 to '00' because it's the simplest, most common path to generate. That leaves the reissue branch of the parser completely untested until a payer actually bounces an attachment and the sender resends it — at which point a system that assumes every BGN01 is '00' may log a duplicate record instead of recognizing the resend as a correction of the original.