US Medical BillingRevenue cycle solutions
Compliance and Regulations

The Anti-Kickback Statute in Medical Billing

The Anti-Kickback Statute turns a business instinct on its head: in most industries, rewarding someone who sends you customers is ordinary and legal, but in the federal health care programs, paying for a referral is a crime. The statute makes it a felony to knowingly and willfully give or take anything of value to induce or reward the referral or purchase of items and services those programs pay for. A billing operation does not usually negotiate the arrangements the statute governs, but it submits the claims those arrangements produce — and because a claim tainted by a kickback is a false claim, the HHS Office of Inspector General treats the two as inseparable.

Updated 13 min read

On this page

Key takeaways

What the Anti-Kickback Statute prohibits

The Anti-Kickback Statute is found at 42 U.S.C. § 1320a-7b(b), part of the Social Security Act. It draws a line around two sides of the same transaction. One subsection reaches anyone who knowingly and willfully solicits or receives remuneration; the other reaches anyone who knowingly and willfully offers or pays it. “Knowingly and willfully” is the statute's own standard, and it is what makes this a criminal law rather than a paperwork rule: the conduct it punishes is an intentional exchange, not an honest mistake.

What the exchange has to be aimed at is the second half of the prohibition. The payment is unlawful when it is made in return for referring a person for an item or service, or in return for purchasing, leasing, ordering, or arranging for or recommending any good, facility, service, or item — where payment for that item or service may be made, in whole or in part, under a federal health care program. The federal-program hook is essential: the statute does not police private-pay business. It polices arrangements that steer the spending of Medicare, Medicaid, and the other federal programs.

What “federal health care program” covers

A violation is a felony. The statute provides for criminal fines and imprisonment on conviction; the specific amounts and terms are set in the law and change over time, which is exactly why the number to remember is not a dollar figure but the fact that this is criminal exposure, not a billing adjustment. And it is not the only consequence, as the next section explains.

Why it matters to a billing operation

The reason the statute belongs in a billing team's field of vision, and not only a lawyer's, is a provision added in 2010: a claim that includes items or services resulting from a violation of the Anti-Kickback Statute constitutes a false or fraudulent claim for purposes of the False Claims Act. That single sentence connects a back-room arrangement to the claim that leaves the billing system. If the referral behind a service was bought, the clean-looking claim built on it is, in the government's eyes, false — and the practice that submitted it is exposed to False Claims Act liability on top of the criminal statute.

A second 2010 change removed a common defense. A person need not have actual knowledge of the statute, or a specific intent to violate it, to be liable. “I didn't know there was a law against it” is not an answer. The “knowingly and willfully” standard still applies to the conduct — the parties have to mean to make the payment — but they do not have to have been thinking about the Anti-Kickback Statute when they did.

The exposure runs both ways, and beyond prosecution

There is a monetary tail as well. Amounts a federal program paid on claims tainted by a kickback are an overpayment the practice generally has to return, and under the False Claims Act the exposure can multiply beyond what was paid. Catching a problem arrangement before it produces claims is far cheaper than unwinding months of them after an enforcement action names it.

What counts as remuneration

The statute prohibits “any remuneration,” and it lists forms to make the breadth unmistakable: a kickback, bribe, or rebate, paid directly or indirectly, overtly or covertly, in cash or in kind. OIG's plain-language guidance sharpens it to a phrase worth memorizing — remuneration is anything of value. It is not limited to an envelope of cash. It includes free or below-market rent, expensive meals and travel, and compensation for a medical directorship or a consulting role that exceeds fair market value or is not tied to real services performed.

The reason so many ordinary-sounding arrangements draw scrutiny is that the question is not whether money changed hands for a legitimate reason, but whether even one purpose of the payment was to induce referrals or federal-program business. A lease, a stipend, or a discount can be entirely defensible on its face and still be a problem if it is priced or structured to reward the flow of referrals. That is why the same arrangement can be fine between two parties with no referral relationship and risky between two parties who send each other federal business.

Waiving patient cost-sharing is not a free courtesy

Safe harbors: how a lawful arrangement is protected

Because the prohibition is written broadly enough to touch arrangements that are perfectly legitimate — a practice does have to rent space, hire employees, and contract for services — federal regulation carves out categories of protected arrangements called safe harbors. They live at 42 CFR § 1001.952. An arrangement that fits squarely within a safe harbor “shall not be treated as a criminal offense” under the statute and will not serve as the basis for an exclusion. The label is regulatory, not statutory: the statute itself authorizes the Secretary to specify payment practices the prohibition will not apply to, and the regulation is where the term “safe harbor” actually appears.

Each safe harbor is a named category followed by a list of conditions, and the conditions are cumulative: an arrangement has to meet every one of them to be protected. The categories most relevant to a practice include space rental, equipment rental, personal services and management contracts, bona fide employees, discounts, group purchasing organizations, and practitioner recruitment. Across many of them the same discipline recurs — pay fair market value, put the arrangement in writing, set the term and the compensation in advance, and keep the deal commercially reasonable without regard to the volume or value of referrals.

Not fitting a safe harbor is not the same as breaking the law

How it differs from Stark and the False Claims Act

The Anti-Kickback Statute is one of three fraud-and-abuse laws a billing operation hears named together, and they are easy to blur. The differences are not academic — they change what a practice has to prove, and what it is exposed to.

How the Anti-Kickback Statute, the Stark law, and the False Claims Act differ
How the Anti-Kickback Statute, the Stark law, and the False Claims Act differ
DimensionAnti-Kickback StatuteStark lawFalse Claims Act
What it targetsRemuneration to induce or reward referrals or federal-program businessA physician's referral for designated health services to an entity the physician has a financial relationship withPresenting, or causing the presentation of, a false or fraudulent claim
Intent requiredCriminal: knowing and willful (but no need to know the statute exists)None — strict liability; the referral itself is barredKnowing, which includes deliberate ignorance and reckless disregard; no specific intent to defraud needed
Who it reachesAnyone — both the payer and the recipient of the kickbackPhysicians (and their immediate family), and the billing entityAnyone who submits or causes a false claim
Program scopeAll federal health care programsMedicare designated health services (with a separate Medicaid effect)Any claim for federal money
Civil or criminalCriminal, plus civil penalties and exclusionCivil — denied payment, refunds, civil penaltiesCivil, with a whistleblower (qui tam) mechanism
How a lawful deal is protectedSafe harbors (regulatory)Exceptions (statutory and regulatory)

The one bridge to keep in view: a claim resulting from an Anti-Kickback Statute violation is itself a false claim, so a kickback does not stay in its own lane — it becomes False Claims Act exposure on the claims that follow.

The cleanest way to hold the three apart: the Stark law asks a yes-or-no question about a physician's financial relationship and does not care about intent, so it is strict; the Anti-Kickback Statute asks about intent and reaches anyone, so it is criminal; and the False Claims Act is the collector, turning a violation of either — or an ordinary billing lie — into liability on the claim itself.

What a billing operation should actually do

A billing team rarely writes the contracts the statute governs, but it sees their output every day, and it is often the first place a problem becomes visible. The practical posture is not to become a compliance lawyer; it is to know what an arrangement that needs review looks like and to route it there before it turns into claims.

  1. Treat financial arrangements as a claims question

    A payment to or from a referral source — rent, a directorship, a consulting fee, a discount, a marketing deal — is not just an administrative matter, because the claims that flow from the relationship inherit its risk. When the source of a stream of business is a paid arrangement, that arrangement should have been vetted before the first claim went out.
  2. Escalate, do not adjudicate

    The right response to a possible kickback is not a judgment call at the billing desk. Route the arrangement to the compliance program and to qualified counsel, who can test it against the safe harbors and the facts. A documented escalation is also what a compliance program's reporting and response elements are built to receive.
  3. Mind the vendors and contractors

    The companies a practice pays for services are the same ones it manages under business associate agreements and screens against the exclusion lists, and their compensation arrangements can raise anti-kickback questions if payment is tied to referrals rather than to fair-market work. Vendor oversight and anti-kickback review naturally sit together.
  4. Do not waive cost-sharing as a matter of routine

    Keep copayment, coinsurance, and deductible collection as the default, waive only on documented, individualized hardship, and never advertise forgiveness. This is one anti-kickback exposure a front-office and billing team controls directly.

Screening is the other place billing and anti-kickback risk meet. Because an Anti-Kickback Statute violation can end in exclusion, the same exclusion screening a practice runs on its workforce and vendors is part of how it keeps an excluded party — including one excluded for a kickback — off its claims. The controls reinforce each other: a compliance program that reviews arrangements up front and screens the people behind the claims is answering the anti-kickback question before an auditor asks it.

Educational, not legal advice

Common questions

Is the Anti-Kickback Statute a criminal law or a civil one?

It is a criminal law. A knowing and willful violation of 42 U.S.C. § 1320a-7b(b) is a felony, punishable by fines and imprisonment. But the same conduct can also carry civil consequences — civil monetary penalties and exclusion from the federal health care programs — and, because a claim resulting from a kickback is treated as a false claim, False Claims Act liability. So the exposure is criminal and civil at once.

Does someone have to know they are breaking the Anti-Kickback Statute to be liable?

No. A 2010 amendment made clear that a person need not have actual knowledge of the statute or a specific intent to violate it. The “knowing and willful” standard applies to the act of making or taking the payment, not to awareness of the law, so “I didn't know there was a statute” is not a defense. That is a key difference from the everyday assumption that ignorance of a technical rule is an excuse.

What is a safe harbor, and does an arrangement have to fit one?

A safe harbor is a category of arrangement that federal regulation (42 CFR § 1001.952) protects from anti-kickback prosecution when the arrangement meets every one of the safe harbor's conditions. Fitting a safe harbor is voluntary, and an arrangement that does not fit one is not automatically illegal — it loses the guaranteed protection and is judged on its own facts for whether it was meant to induce referrals. The safest course, where possible, is to structure an arrangement to fit a safe harbor completely.

How is the Anti-Kickback Statute different from the Stark law?

The Stark law is a strict-liability civil law: it bars a physician from referring designated health services payable by Medicare to an entity the physician has a financial relationship with, unless an exception is fully met, and it does not require any bad intent. The Anti-Kickback Statute is a criminal law that requires the payment to be knowing and willful, reaches anyone rather than only physicians, and applies across all federal health care programs. Stark uses “exceptions”; the Anti-Kickback Statute uses “safe harbors.”

Can a billing company or vendor arrangement implicate the statute?

Yes, if compensation is tied to referrals rather than to fair-market work. The statute reaches indirect remuneration and payments in kind, so a vendor, contractor, or billing-company arrangement structured to reward the flow of federal-program business can be a problem even though the service itself is legitimate. That is why the personal services and management contract safe harbor exists and why such arrangements should be documented at fair market value and reviewed by counsel.

Key terms in this article

Defined once, on their own pages.

Authoritative sources

Ready to improve your revenue cycle?

Explore our services and knowledge base to see how we can help.