Silent PPOs and Network Leasing
A remittance arrives from a payer the practice has no agreement with, and it has taken a network discount. The reflex is to treat it as an error. Often it is not: the agreement the practice did sign gave the network the right to make its panel available to other payers, and the discount traveled down a path nobody read. So the useful first question is not whether the reduction is fair, but whether a contractual route to it exists — because a permitted discount and an unsupported one look identical on the remittance and have opposite remedies.
Updated 9 min read
On this page
Key takeaways
- A network discount can reach a payer the practice never contracted with, through an access grant in the agreement it did sign.
- The question is about the access clause, not about the discount. A permitted discount and an unsupported one are indistinguishable on the remittance.
- Under 45 CFR 147.212, plans and issuers must publish an in-network rate machine-readable file, updated monthly.
- Each rate in that file must be tied to the provider's NPI, TIN and place of service — so a practice can look itself up by its own identifiers.
- The file must also carry the last date of the contract term for each provider-specific rate, which is what makes an expired or unrecognized relationship visible.
- The files must be free and open — no account, no password, no personally identifiable information — so checking costs nothing but time.
- The file shows what a plan asserts. It does not decide whether the access grant in your own agreement actually reached that payer.
- If access was permitted, the remedy is at renewal. If it was not, it is a recovery. The two are worth separating before anyone writes an appeal.
How a discount reaches a stranger
A participation agreement does two separable things. It sets rates, which is the part everyone negotiates, and it grants somebody the right to make the practice's participation available — which is the part that is often a single sentence in the definitions or the general-provisions section. The second sentence is what decides how far the first one travels.
The panel is assembled
A network contracts with providers and holds a panel with agreed rates. Nothing unusual so far; this is what payer contracting is.Access is granted to others
The agreement permits the network to make that panel available to third parties — other payers, plan administrators, or entities that reprice claims on a payer's behalf. The wording is rarely dramatic and is frequently a defined term doing the work rather than a clause anyone would notice.A claim is repriced
A payer with no direct relationship to the practice runs a claim through that access and applies the panel's rate. The reduction posts as a contractual adjustment like any other.The practice sees the result and not the path
The remittance shows an unfamiliar name and a network-looking reduction. Everything that would explain it — the access grant, the downstream agreement, the repricing arrangement — sits in documents the practice does not hold.
Why the phrase is contested, and why the article uses it anyway
Two situations that look the same and are not
Separating these before drafting anything is what stops a practice spending an appeal cycle on a discount its own contract authorized, and stops it writing off a reduction that had no basis at all.
| Access was granted | No route exists | |
|---|---|---|
| What happened | The agreement permitted the network to make the panel available, and this payer reached it that way. | A network rate was applied with no agreement, and no access grant, connecting the practice to this payer. |
| Is the discount owed? | Yes. Unwelcome is not the same as unowed, and the contract is the answer. | No. The correct amount is whatever applies absent a contract, which makes this a shortfall. |
| Where the remedy lives | At renewal — narrowing or removing the grant. See payer contract renegotiation. | In recovery — see contract-based underpayment recovery. |
| What settles it | The access language in your own agreement, read against how it defines the counterparty. | The same language, plus whether the plan itself asserts an in-network rate for your NPI. |
Both columns start in the same place: the practice's own contract. That is why this is a contracts problem rather than a posting problem, even though it is always discovered in posting.
The public file that can answer half the question
Historically a practice could only ask the payer whether it claimed a network relationship — which is asking the party with an interest in the answer. Under 45 CFR 147.212 (opens in a new tab), group health plans and issuers must publish their in-network negotiated rates in a machine-readable file. The rule itself — who it binds, how it differs from Hospital Price Transparency and the No Surprises Act — belongs to the Transparency in Coverage rule, and is not restated here. What matters for this question is narrower: four required contents that make the file usable from the provider side, as a lookup rather than as a compliance obligation.
- Rates are tied to provider identifiers. Each negotiated rate must be associated with the NPI, Tax Identification Number and place of service code for each in-network provider. A practice can therefore search for itself, by its own numbers, rather than by a name that may be recorded differently.
- So is the end of the term. Each provider-specific rate must be associated with the last date of the contract term, or the expiration date. That is the field that makes a relationship the practice does not recognize — or one it believes ended — visible as something other than a rumor.
- Access is unconditional. The files must be publicly available and accessible to any person free of charge and without conditions — no user account, no password or other credentials, and no submission of personally identifiable information. Nobody has to be asked for permission.
- They are current by requirement. Plans and issuers must update the files monthly and clearly indicate the date they were most recently updated, so a file's age is itself readable rather than assumed.
What the file does not settle
Working it as a pattern rather than a claim
The single claim is almost never worth the analysis on its own. What makes this worth an afternoon is that the answer generalizes: an access grant that let one unfamiliar payer in has been letting others in for as long as it has existed.
- Read your own access language first. Before contacting anyone. The question is who the agreement lets make the panel available, to whom, and how the counterparty is defined — the same definitional question the all-products clause raises about a payer's own product lines, asked about third parties instead.
- Group the remittances by the reducing party. One unfamiliar name across many claims is a configuration question. Many unfamiliar names once each is a different problem and probably a broader grant.
- Look yourself up before you write. Checking the plan's public file for your own NPI and TIN costs nothing and changes the letter you write, because it converts a suspicion into a documented assertion or a documented absence.
- Ask for the route, not for the money. The productive request is which agreement the discount was taken under. A payer that can name it has answered the question; a payer that cannot has also answered it.
- Fix it where it is fixable. If access was granted, no amount of appealing individual claims will change the outcome — the clause is the outcome, and it is a renewal item. Recording it against the contract while it is fresh is what makes it survive to the next negotiation.
State law is the part this page will not summarize
Common questions
A payer we have never contracted with took a network discount. Is that allowed?
It may well be, and that is the uncomfortable part. Participation agreements frequently grant the network the right to make its panel available to third parties, and where that grant exists the discount traveled a route the practice agreed to. The question is not whether the reduction feels justified but whether a contractual path to it exists, which is answered by the access language in your own agreement and by how that agreement defines the counterparty. Where no such path exists, the reduction has no basis and the matter is a shortfall to be recovered rather than a term to be renegotiated.
How can we check whether a plan claims us as in-network?
Group health plans and issuers must publish an in-network rate machine-readable file under 45 CFR 147.212, and the rates in it must be associated with the NPI, Tax Identification Number and place of service code for each in-network provider. That means a practice can search for its own identifiers rather than for a name that may be recorded inconsistently. The files must be publicly available to any person free of charge and without conditions — no account, no password, no personally identifiable information — and must be updated monthly with the last-updated date shown. It answers what the plan asserts, which is genuinely useful and is not the same as settling whether your contract permitted the access.
Does the file tell us when a relationship ended?
It carries the field that would. Each provider-specific applicable rate must be associated with the last date of the contract term or the expiration date, so a plan asserting a rate for a practice is also asserting a period for it. That is what turns a disagreement about whether a relationship still exists into a comparison between two documents. It remains the plan's assertion rather than an adjudication, so it is evidence for an argument rather than the end of one.
Should we appeal these claim by claim?
Rarely as the first move. If an access grant permitted the discount, appealing individual claims cannot succeed, because the contract is the reason for the reduction — the remedy is narrowing that grant at renewal. If no route exists, the value is still in the pattern rather than the claim: the same grant, or the same absence of one, has been operating across every claim that payer touched, so a documented population produces a configuration fix while a single claim produces at most a one-off adjustment. Establish which case you are in first; the correct action differs completely between them.
Can we simply refuse to allow network leasing?
That is a negotiation question rather than an operational one, and it is asked at the right time by knowing what your current agreement says before the renewal conversation opens. Whether a narrower grant is achievable depends on the counterparty, the practice's position, and in some states on rules that constrain the arrangement independently of what either party wants. What is within any practice's control is not signing a broader grant unknowingly next time, which requires having read the definitions section rather than only the rate exhibit.
Key terms in this article
Defined once, on their own pages.
Continue learning
The clause this one lives beside, and where each answer goes next.
The All-Products Clause
The first-party version — one signature reaching more of the same payer's product lines.
Reading a Payer Contract
How to read an agreement backwards from a question, including who the counterparty actually is.
Contract-Based Underpayment Recovery
Where an unsupported reduction goes once the relationship question is settled.
Payer Contract Renegotiation
Where a permitted but unwanted access grant is actually fixed.
The Transparency in Coverage Rule
The rule behind the public rate files — who it binds, and what else it requires.
Contractual Variance Calculator
Compare the amount paid against the rate you expected, from your own contracted rates.
Authoritative sources
- 45 CFR § 147.212 — Transparency in coverage: requirements for public disclosure (opens in a new tab)
Requires a group health plan or health insurance issuer to make required information available on an internet website in three machine-readable files, including an in-network rate machine-readable file covering all covered items and services. Negotiated rates in that file must be associated with the National Provider Identifier, Tax Identification Number, and Place of Service Code for each in-network provider, and associated with the last date of the contract term or expiration date for each provider-specific applicable rate. The files must be publicly available and accessible to any person free of charge and without conditions, such as establishment of a user account, password, or other credentials, or submission of personally identifiable information. Plans and issuers must update the files monthly and clearly indicate the date the files were most recently updated.