Trading partner agreement: the paperwork before you send electronic claims
In electronic billing, a trading partner agreement sets the terms under which a provider and a payer exchange electronic transactions, such as claims and remittances. HIPAA defines it and forbids it from changing the standard transactions. Medicare requires every provider that bills electronically to sign one, even through a clearinghouse. Indiana Medicaid requires it only from entities that connect directly, such as clearinghouses and billing services.
On this page
What the agreement covers
The HIPAA definition in 45 CFR 160.103 covers any agreement that governs how two parties trade information in electronic transactions. It can stand alone or sit inside a larger contract, and it typically spells out each side’s duties when a standard transaction is sent. For a transportation company, the transactions that matter are the 837P claim, the 835 remittance, and the acknowledgments that come back.
What the agreement cannot do matters just as much. Under 45 CFR 162.915, a trading partner agreement may not:
- Change how a data element or segment in the standard is defined or used, except where state or federal law or fraud prevention requires it.
- Add data elements or segments beyond the standard’s maximum data set.
- Use codes or data elements the standard marks as “not used” or leaves out.
- Change the meaning or intent of the standard’s implementation specifications.
Payer companion guides have to work inside those limits, explaining the payer’s choices within the 837P instead of changing it. HIPAA also lets a clearinghouse or another business associate do the work for you, as long as you require it to follow the same transaction rules.
Who signs one
Payers disagree on this, so check each one you bill.
| Payer | Who signs | What you get | Renewal |
|---|---|---|---|
| Medicare | Every provider that exchanges EDI, directly or through a billing agent or clearinghouse, signs an EDI enrollment form with its contractor | Access for the provider and any third party it names | Terms set by the contractor’s form; report billing agent or clearinghouse changes in advance |
| Indiana Medicaid | Entities that connect directly: providers using approved software, clearinghouses, billing services, and managed care entities | A trading partner ID, logon, and file transfer access | Four-year term, renewable |
| New York Medicaid | Each submitter certifies its electronic transmitter ID (ETIN) | An active ETIN for claims, eligibility checks, and files | Every year, with a notarized original signature |
Medicare’s trading partner agreement is made up of two forms: EDI registration and EDI enrollment. Its enrollment terms have the provider promise accurate, complete, and truthful claims, and they make the submitter ID or NPI the provider’s legal electronic signature. One note links this to direct deposit: a provider that takes EFT payments but sends no EDI transactions does not complete an EDI enrollment form.
Indiana spells out the exemption the others lack. A provider that bills only through the state’s provider portal, its phone-based assistant, or a state-approved clearinghouse or billing company stays out of the trading partner process. The agreement also covers only the state’s fiscal agent, so managed care plans and other contractors set up their own electronic connections.
Testing before the first production claim
Payers test before they accept live claims. Indiana requires two levels of testing for software that connects directly:
- Compliance testing. Data integrity, balancing, and situational rules. A transaction passes when it processes without errors and produces a 999 acknowledgment.
- Specification testing. Conformity with the state’s companion guides, including field lengths, security, volume, and external code sets.
Third-party HIPAA certification is not required, and the process can take days or weeks. Production credentials are not issued until the software passes for that transaction type, and adding transaction types later means a new signed agreement.
Keeping the connection alive
Most trouble comes after setup. In New York, a claim whose billing, group, or rendering NPI is not tied to the sending ETIN gets rejected. A lapsed ETIN stops claims and eligibility checks and can switch electronic remittances back to paper, and the state allows only one seven-day grace period. Medicare asks providers to report in writing, ahead of time, when they drop or add a billing agent or clearinghouse.
Put each renewal date on a calendar and update the payer before you change clearinghouses or billing services. A connection that quietly lapses shows up later as a pile of claim rejections and a shrinking filing window.
Frequently asked questions
- Clearinghouse users: does each provider still sign an agreement?
- Payers differ. Indiana Medicaid exempts providers who send claims only through its provider portal or through a state-approved clearinghouse or billing company. Medicare takes the opposite approach: each provider signs an EDI enrollment form with its contractor even when a clearinghouse or billing agent sends the claims. Check each payer before you assume the clearinghouse covers you.
- What is a submitter ID?
- It is the number a payer assigns to the person or company that sends electronic files. Indiana issues a trading partner ID with logon and file transfer details once the paperwork is approved. New York calls it an ETIN. In Medicare's EDI enrollment terms, the provider agrees that its submitter ID or NPI acts as its legal electronic signature on claims.
- Does a trading partner agreement expire?
- Some do. Indiana's agreement runs four years from signing and renews in four-year terms. New York requires the ETIN certification to be renewed every year with an original, notarized signature, and a lapsed ETIN shuts off electronic claims until it is fixed. Medicare's EDI enrollment form does not expire just because the person who signed it leaves the company.
