What is an EDI Companion Guide?
An EDI companion guide is a document published by a carrier, payer, or other trading partner that explains exactly how it expects a standard transaction, such as an X12 834 enrollment file, to be formatted, sent, and tested.
Standards such as the X12 834 define a common structure, but they leave many decisions to each organization. The companion guide records those decisions for one trading partner. Anyone sending files to that partner, whether an employer, broker, TPA, or benefits administration platform, builds the feed to match it.
What a Companion Guide Covers
- The transactions and versions the partner accepts, such as 834 version 005010X220A1
- Which optional loops, segments, and elements it requires or ignores
- Identifier rules, including which member ID to send and how dependents are coded
- Whether it expects full files or change-only files, and how often
- File naming, encryption, SFTP connection details, and envelope values
- Testing steps the sender must pass before files go to production
Companion Guides for Flat Files
Many carriers and most benefits vendors accept CSV, Excel, or fixed-width files rather than EDI. Their file specifications do the same job: they define column order, field lengths, valid codes, and delivery rules. The work is the same either way: map your data to the partner's layout and keep it matching when either side changes.
Why Companion Guides Create Work
A benefits administrator connected to dozens of carriers maintains dozens of companion-guide variations. Each new connection means reading a new guide, building the mapping, and going through the partner's testing cycle. When a carrier revises its guide, every affected feed has to be updated and tested again.
Companion Guides and Integrate.io
Integrate.io lets teams build each partner's output format, EDI or flat file, as a reusable mapping from one standardized source, then deliver it on schedule. Read more about EDI and the 834 file layout, or see how this works for carriers and benefits administration platforms.
FAQ
Frequently asked questions
Clear answers to the questions teams ask when evaluating Integrate.io.
What is the difference between an implementation guide and a companion guide?
The implementation guide, called the TR3 for HIPAA transactions, defines the standard for everyone. A companion guide is one trading partner's supplement to it. It specifies which optional segments that partner uses, the code values and identifiers it expects, and its transmission and testing rules. A companion guide may not contradict the implementation guide.
Do flat files have companion guides?
Yes. Carriers and vendors that accept CSV or fixed-width files publish file specifications that serve the same purpose: column order, field lengths, required values, file naming, and delivery details. In the benefits industry these documents are often called companion guides too.
Why does every carrier have a different companion guide?
The X12 standards leave room for choices, such as optional segments, member identifier types, and how changes are signaled. Each carrier makes those choices to fit its own systems. A sender working with many carriers therefore produces many slightly different versions of the same transaction.
Need help with your data integration?
Our team of experts is ready to help you build reliable data pipelines with Integrate.io.
Book a Demo
