X12 837P PER Segment Guide: Fields, Format, and Testing Gotchas
A claim can be perfectly billed and still stall at the payer because nobody can reach the submitter to ask a follow-up question. PER is the segment that prevents that — a name, a phone number, maybe an email — and it's small enough that test suites routinely skip it or hardcode one contact for every claim in the file.
PER (Administrative Communications Contact) is an optional segment in an X12 837P claim that identifies a person or department the payer can contact about the claim, along with one or more ways to reach them. It commonly appears at the billing provider level, pairing a contact function code with a name and up to two communication number qualifier/value pairs.
The elements that actually matter in practice
Example
A synthetic PER segment naming BILLING DEPT as the information contact (IC), reachable by telephone (TE) at 303-555-0142 or by email (EM) at a fictitious test address.
Where this trips people up
Because PER is optional and doesn't affect whether a claim adjudicates, a lot of test data generators either omit it entirely or stamp the exact same contact block onto every claim in a batch. That works fine until a downstream system assumes PER is always present and throws a null-reference error on the one claim in production where the submitter left it off, or until a report that groups claims by billing contact shows every single claim funneling through one placeholder name because the test data never varied it.