Operations teams
“A supplier operations team can see partner setup, validation, exceptions, and QuickBooks handoff in one workspace instead of chasing spreadsheets.”
X12 segment reference
PER — Administrative Communications Contact
X12 PER segment reference: contact name, function code, and communication numbers (phone, email, fax) attached to parties in EDI documents.
PER segment facts
- PER pairs a function code with up to three communication qualifier/number pairs, so one segment can carry phone, email, and fax.
- Qualifier/value mismatches in PER03/PER04 are a common validation defect when generators hardcode the wrong pairing.
- SignalEDI maps PER contacts to structured contact objects so downstream systems can route order and shipping notifications.
What the PER segment does
PER attaches a contact to a party or document — buyer, seller, or shipping contact — with a function code and communication numbers such as telephone, email, and fax.
Loop: Header or N1 loop
Key elements
| Element | Name | Description |
|---|---|---|
| PER01 | Contact function code | BD=buyer, IC=information contact, SH=shipper contact — partner guides specify. |
| PER02 | Name | Contact person or department name. |
| PER03 | Communication number qualifier | TE=telephone, EM=email, FX=fax. |
| PER04 | Communication number | The phone, email, or fax value matching PER03. |
Example PER segment
PER*BD*Jane Buyer*TE*5135551212*EM*orders@retailer.com~
Parse and validate samples with the free EDI validator or send JSON via the JSON→X12 mapping guide.
Common PER errors
- PER03/PER04 qualifier and value mismatch (email value under TE qualifier)
- Missing mandatory PER contact when the partner requires order or shipping contacts
- Free-text formatting that breaks element delimiters
Related reference
FAQ
Frequently asked questions
It depends on the partner — some retailers require a buyer or order contact in PER, while others treat it as optional.
Trust & proof
Built for SMB teams that need API-first EDI, healthcare diligence, and predictable pricing.
SignalEDI keeps the public promise consistent across every route: real-time processing, transparent monthly plans, no per-document fees on core plans, QuickBooks-friendly handoffs, and core healthcare X12 workflows on paid plans.
Supports HIPAA complianceBAA path documentedSecure API + webhooksNo per-document fees on core plans
Healthcare billing
“837, 835, and 270/271 workflows are explained in plain English, with handling that supports HIPAA compliance and a documented BAA review path for diligence.”
Developer teams
“JSON/CSV in and X12 out, with API docs, webhooks, real-time status, and validation responses that make EDI feel like modern infrastructure.”