How FMV Exceptions
Should Be Evaluated in Practice

FMV frameworks are designed to provide consistent guidance, but they do not fit every situation perfectly. Fair market value standards are no exception, and the way those limits are handled says a great deal about the integrity of a company's overall approach to HCP contracting. FMV exceptions are among the most routinely misunderstood concepts in life sciences compliance. The misunderstanding rarely stems from bad intentions. It typically arises from confusion about what an exception actually is and what it is not. This distinction is not technical. It has real compliance implications.

Exceptions Are Not Approvals to Exceed FMV

The most important principle in evaluating an FMV exception is also the one most commonly overlooked. Approving an exception is not the same as approving a payment above fair market value. That distinction matters enormously.

An FMV exception is not a mechanism for overriding compliance standards when a business team wants to pay more than the standard rate allows. Approving a payment that genuinely exceeds FMV is not an exception. It is a violation. What the exception process actually addresses is the possibility that a standard FMV rate, designed to apply broadly across a population of HCPs, may not accurately reflect the fair market value for a specific individual in a specific circumstance. The purpose of the exception is to determine whether a higher rate is, in fact, the correct FMV for that individual. It is not to authorize a departure from FMV as a concept.

This reframing matters because it changes the nature of the analysis. When reviewing an exception request, the compliance function is not weighing whether to bend the rules. It is evaluating whether the rules, properly applied, yield a different result for that HCP in that context.

How Exception Requests Arise and Why They Create Risk

FMV standards are designed to apply accurately in most situations. They are grounded in objective data and calibrated to reflect the market value of different types and levels of expertise. By design, they are broadly correct, but not perfectly precise in every case. That gap is where exception requests originate.

In practice, exception requests tend to emerge when business teams identify an HCP whose circumstances appear to fall outside the standard framework. Sometimes the request reflects a genuine outlier, an individual with expertise so specialized or so narrowly distributed in the market that the standard methodology does not capture it well. More often, the request reflects something else. It reflects a business preference, a relationship, or an assumption about value that has no bearing on what the market would actually pay for the HCP's time.

This is where the risk concentrates. Some business leaders have a natural tendency to seek flexibility and to frame their situation as uniquely deserving of different treatment. Without a structured evaluation process, compliance functions can find themselves approving exceptions that look reasonable in isolation but are difficult to justify in the aggregate. Because the Anti-Kickback Statute does not require proof of intent, even well-intentioned decisions to approve inflated rates carry meaningful legal exposure.

Evaluating an Exception: Ask the Right Questions

A sound exception evaluation begins with a precise question. What is it about this HCP, in this engagement, that suggests the standard FMV rate does not accurately reflect their market value?

What Distinguishes This HCP from Others at the Highest Tier?

This is not a question about the HCP's value to the company or their familiarity with a product or disease state. Neither factor is relevant to fair market value. It is a question about the HCP's standing in the broader medical community, including recognized expertise, credentials, and level of achievement relative to peers.

Why Are Those Characteristics Necessary for the Engagement?

This question distinguishes between selection criteria and compensation criteria. An HCP may be uniquely suited to an engagement without that uniqueness justifying a higher rate. If a national-level thought leader in the relevant area could accomplish the same project goals, then the additional characteristics do not support an exception.

What Is the Basis for Concluding the Standard Rate Is Not Appropriate?

This requires more than an assertion. The requestor should be able to explain why the standard methodology produces an inaccurate result for that individual, not simply that the HCP is unwilling to work at the standard rate or that a competitor appears to be paying more.

Supporting that analysis requires additional documentation. This includes whether similar HCPs have been approached at standard rates, how the requested rate was developed, and whether any negotiation took place. A rate that was never negotiated and simply reflects what was requested does not carry the evidentiary weight needed to support an exception.

Why Documentation Requirements Are More Demanding, Not Less

There is sometimes an assumption that exception approvals represent a relaxation of compliance requirements. The opposite is true. Because an exception involves determining that a higher rate reflects FMV for a specific individual, the evidentiary standard is necessarily higher than for a standard engagement. Standard rates are supported by the methodology itself, including the objective data and consistent application that underpin the framework. An exception rate has no such structural support. It must stand on its own, and the documentation must be sufficient to withstand scrutiny on that basis alone. Regulatory review of a specific arrangement, or of exception patterns across a company, will focus on whether that documentation is adequate and whether approvals reflect genuine FMV determinations rather than accommodation of business pressure.

The practical implication is clear. Exceptions should be rare, evaluated with rigor, and documented in a way that makes the reasoning transparent and defensible. An exception process that is easy to invoke and easier to approve is not a safeguard. It is a vulnerability.