Table of Contents >> Show >> Hide
- What Is a BFSF, Exactly?
- What CMS Actually Finalized
- What CMS Did Not Finalize
- Why This Rule Matters for Drug Manufacturers
- Examples of Fees and Services Likely to Get More Attention
- What Smart Manufacturers Should Be Doing Now
- Experience in the Real World: What This Change Feels Like Inside a Company
- Final Takeaway
- SEO Tags
Note: This article is based on current CMS policy and related U.S. regulatory analysis through early 2026. It explains a technical pricing rule in plain English, without the legalese headache.
Sometimes a federal rule arrives with all the drama of a thunderstorm. Other times, it shows up like a spreadsheet with sharp elbows. The CMS final rule on bona fide service fees, or BFSFs, is the second kind. It is not flashy, but it matters a lot for drug manufacturers, government pricing teams, finance departments, distributors, group purchasing organizations, and anyone who has ever stared at an average sales price calculation long enough to question their life choices.
At the center of the issue is a simple but expensive question: when a manufacturer pays a fee to another company, is that fee truly for a service, or is it really a disguised price concession? That distinction matters because bona fide service fees are not deducted from Medicare Part B average sales price, while price concessions are. And when CMS tightens the rules around that line, manufacturers have to change how they document, classify, and defend those payments.
The good news is that CMS did not finalize the most aggressive parts of its proposal. The bad news, if you are in compliance, pricing, or contracting, is that the agency still raised the bar. The final rule keeps the existing core BFSF definition in place, but adds more structure around documentation, pass-through verification, and bundled arrangements. In other words, the definition survived, but the easy assumptions did not.
What Is a BFSF, Exactly?
Before getting into the rule change, it helps to define the term without turning this into a regulatory hostage situation. A bona fide service fee is a payment from a manufacturer to an entity for a real, itemized service performed on the manufacturer’s behalf. The fee must reflect fair market value, the manufacturer must otherwise have had to perform or contract for the service, and the fee cannot be passed on in whole or in part to the recipient’s client or customer.
That framework has long mattered in Medicare Part B ASP reporting. If a fee qualifies as a BFSF, it generally is not treated as a price concession and therefore is not deducted from ASP. If it does not qualify, it may need to be treated as a discount, rebate, or other price concession that lowers ASP. And since Medicare Part B reimbursement is tied to ASP, this is not just a paperwork problem. It can affect payment amounts, forecasting, provider reimbursement, and audit exposure.
Historically, manufacturers had more room to exercise judgment, especially around fair market value and the “not passed on” prong. CMS’s final rule does not throw away the four-part test. Instead, it changes how manufacturers must prove they satisfied it.
What CMS Actually Finalized
1. CMS kept the BFSF definition, but added more compliance muscle
This is the most important takeaway. CMS did not finalize a brand-new BFSF definition or adopt its most controversial proposal for detailed fair market value methods. That matters because many commenters argued that the proposed rewrite was too rigid, too fast, and too difficult to operationalize.
Still, nobody in pharma should mistake that restraint for a free pass. CMS finalized policies that require manufacturers to submit reasonable assumptions with ASP reporting, including documentation of the methodology used to determine fair market value for current, new, and renewed BFSF contracts. In plain English, “trust us” is no longer a business process.
2. Pass-through verification is now a real requirement
One of the biggest changes is the shift from assumption to evidence. CMS finalized a requirement that manufacturers provide verification that a BFSF is not passed on to a client or customer of the fee recipient. That is a major operational change because manufacturers historically had more flexibility to presume non-pass-through absent contrary evidence.
CMS later clarified through its FAQ that certification is tied to new or prospective contracts executed on or after January 1, 2026, as well as renewals and contract changes that effectively trigger a new certification event. The agency also made clear that manufacturers do not need to resubmit the certification every quarter. But do not relax too much: if a contract changes, including by adding a new product, package size, acquired product, or fee amount, CMS treats that as an amendment requiring fresh certification.
That means legal teams and contract operations groups are now part of the ASP conversation in a much more direct way. If a service provider refuses to provide certification, CMS has said the fee cannot be treated as a bona fide service fee. That is a serious leverage point in negotiations.
3. Bundled arrangements finally got a formal definition
CMS also finalized a definition of “bundled arrangement” for ASP purposes. This may sound like side salad compared with BFSFs, but it is a big deal. Bundled arrangements can include rebates, discounts, or other price concessions conditioned on purchasing the same drug, other drugs, another product, or meeting some performance condition such as market share or formulary placement.
Why does that matter? Because discounts in bundled arrangements must be allocated proportionately across the drugs or products in the arrangement. Manufacturers that relied on looser internal approaches now need a more disciplined allocation framework. This is especially important where contract strategy and ASP reporting have not always spoken the same language. Now CMS has handed them a dictionary and expects them to use it.
4. Reasonable assumptions are no longer optional wallpaper
Another major shift is that reasonable assumptions must now be submitted as part of quarterly ASP reporting. For BFSFs, that includes fair market value methodology documentation. CMS later clarified that it will accept well-detailed summaries describing the data sources, assumptions, and rationale supporting FMV determinations. It also said manufacturers may submit a summary for bundled arrangements and reallocation approaches rather than separate write-ups for every single arrangement.
That is helpful, but it still creates a heavier recordkeeping burden. Manufacturers now need a defensible written story for why a fee qualifies as a BFSF, how FMV was determined, and how bundled discounts were allocated. This is not just a finance exercise anymore. It is a documentation exercise built for future scrutiny.
What CMS Did Not Finalize
Here is where the story gets interesting. CMS proposed a broader set of BFSF changes that made manufacturers very nervous. In the end, the agency backed away from several of them.
Most notably, CMS did not finalize a revised BFSF definition that would have more explicitly dictated how FMV had to be established. It also did not finalize certain proposed examples of payments that would not qualify as BFSFs, and it did not finalize the proposed expansion of the “not passed on” language to affiliates in the regulatory definition. That is not a trivial retreat. It means the core test remains familiar, even though the proof requirements became stricter.
CMS also stopped short of finalizing its proposal that certain manufacturer-paid preparatory services for autologous cell and gene therapies should automatically lose BFSF treatment. Instead, those services may still qualify as BFSFs if the existing four-part test is met. So while the final rule is tighter, it is not the full-scale crackdown many manufacturers feared in the summer proposal.
Why This Rule Matters for Drug Manufacturers
The practical impact is bigger than the regulatory text may suggest. First, the final rule increases the risk that some fees once treated as BFSFs will be reexamined and potentially reclassified as price concessions. If that happens, ASP may go down. Lower ASP can change Medicare Part B reimbursement, affect contract modeling, and trigger restatements in some circumstances.
Second, this rule reaches well beyond the government pricing team. It touches legal review, distributor and GPO contracts, fair market value analysis, internal controls, audit readiness, and cross-functional governance. A pricing assumption that once lived in a spreadsheet now needs support from contracts, certification workflow, and documentation logic that can survive outside the spreadsheet.
Third, although these changes apply directly to ASP and not directly to Medicaid AMP or best price, manufacturers cannot treat the rule as Medicare-only background noise. In practice, companies often strive for consistency across ASP, AMP, and best price where appropriate. If a fee looks one way in ASP and another way in Medicaid calculations, companies should be ready to explain why. CMS and industry have historically cared about that consistency, even when the legal requirements are not identical.
In short, this is one of those rules that looks technical until it hits a real contract portfolio. Then it suddenly becomes very personal.
Examples of Fees and Services Likely to Get More Attention
CMS’s FAQ offers helpful clues about what the agency sees as directly related to a Part B drug. It points to services specifically associated with the product, such as distribution and logistics, administrative functions, and drug-specific data reporting. Those examples suggest manufacturers should focus less on labels and more on substance. Calling something a “service fee” is easy. Demonstrating that it is itemized, at fair market value, and not passed through is the part that keeps compliance teams up at night.
Manufacturers should also pay close attention to contract amendments. A new package size, a newly acquired product, a product launch, a change in fee amount, or an adjustment to contract term can all trigger a new certification requirement. That means the real risk is not only in brand-new contracts. It is in the quiet, everyday changes that happen all the time.
What Smart Manufacturers Should Be Doing Now
The first priority is contract inventory. A manufacturer cannot classify what it cannot find. Companies should identify all arrangements that involve potential BFSFs tied to Part B drugs and map which are current, new, renewed, or likely to be amended. Next comes documentation: fair market value methodology summaries need to be written clearly enough that someone outside the original deal team can follow the logic.
Then comes the human part. Service providers may need education on why a certification is suddenly required and why delay can affect fee treatment. Internal teams also need a decision tree for when an amendment becomes a new certification event. Without that, the company will end up arguing about definitions every quarter, which is a terrible hobby.
Finally, manufacturers should build a governance loop between pricing, legal, contracting, finance, and market access. The final rule rewards coordination and punishes silos. If one team negotiates fees, another calculates ASP, and a third stores the documentation somewhere mysterious, the organization is practically inviting a future headache.
Experience in the Real World: What This Change Feels Like Inside a Company
In practice, the experience of dealing with the CMS final rule is less like reading a rulebook and more like cleaning out a garage that looked organized until the lights came on. Companies often discover that their BFSF universe is spread across contract management systems, shared drives, email chains, and institutional memory stored inside three people who are always in meetings.
The first real-world shock is usually inventory. Teams think they have ten important service-fee arrangements, then realize there are forty-seven versions, six amendments, three side letters, and a distributor addendum that everyone forgot about because it was signed during a holiday week. The final rule turns that kind of “we’ll deal with it later” behavior into a risk factor.
The second experience is that fair market value stops being an abstract concept and becomes a documentation discipline. A company may have perfectly reasonable business logic for why a service fee was set the way it was. But when CMS expects a clear methodology summary, verbal logic is not enough. The file has to explain the data sources, assumptions, and rationale in a way that is coherent months later, after the people who negotiated the deal have moved on to the next fire drill.
The third challenge is provider and trading partner communication. Some service providers will understand the certification request immediately. Others may respond as if you just asked for their childhood diary. That creates timing pressure because a fee that lacks required certification may not qualify as a BFSF. Suddenly, what looked like a reimbursement policy issue becomes a relationship-management issue.
Another common experience is internal disagreement over what counts as “new,” “renewed,” or “amended.” On paper that sounds manageable. In real life, it turns into questions like: does adding a new NDC trigger certification, what about a fee rate adjustment, what about a term extension, what about a product acquired through a transaction, and who is responsible for spotting the trigger in time? These are not philosophical questions. They are calendar questions with regulatory consequences.
And then there is the quarterly reporting clock. Even though CMS clarified that certifications are not due every quarter for the same contract, the operational work still becomes recurring. Teams have to monitor contract changes, update FMV documentation when appropriate, summarize assumptions, and preserve the logic behind bundled arrangement allocations. The result is that compliance becomes less about one-time interpretation and more about ongoing maintenance.
That is why the smartest organizations will treat this final rule as a process redesign project, not just a legal memo. The winners will be the manufacturers that create clear ownership, simple workflows, and documentation standards that can survive turnover, audits, and the passage of time. Everyone else may find themselves learning a painful truth of government pricing: the rule is only half the battle, and the file is the other half.
Final Takeaway
CMS did not rewrite the DNA of BFSFs, but it absolutely changed how manufacturers must live with them. The final rule preserves the core four-part framework while demanding stronger proof, clearer assumptions, better fair market value documentation, and more formal verification that fees are not passed through. At the same time, CMS finalized a bundled arrangement definition that will force more disciplined discount allocation in ASP reporting.
So yes, the rule is narrower than the proposal. But it is still a meaningful compliance upgrade. For drug manufacturers, the message is simple: if a fee is going to stay outside ASP as a BFSF, the company now needs a sharper file, a cleaner contract trail, and fewer leaps of faith. In government pricing, paperwork may not be glamorous, but it definitely pays the rent.
