AI Upcoding and Coding Compliance Risks

Upcoding is not new, but AI changes its scale and how it happens. A person who upcodes affects the claims they touch. A coding model that leans toward higher codes affects every claim it processes. That lean can come from training on historical billing data that already contained upcoding, from a product built to maximize 'revenue capture', or from documentation habits the tool picks up, such as cloned notes and long problem lists copied forward. Generative documentation tools add a second route. An ambient scribe can phrase a diagnosis more specifically or more severely than the clinician meant, and that wording then drives the code. The legal exposure mostly comes from the False Claims Act. Under the Act, submitting false claims to federal programs such as Medicare and Medicaid can lead to treble damages plus a civil penalty for each claim, and the penalty amounts are adjusted for inflation. Proof of intent to defraud is not required. The Act defines 'knowingly' to include deliberate ignorance and reckless disregard of the truth. Accepting AI suggestions in bulk with no review, or ignoring internal audit findings, can arguably meet that standard. The qui tam provisions let private whistleblowers, often coders, auditors or former employees, file suit and share in any recovery. Separately, federal law requires providers to report and return identified Medicare and Medicaid overpayments within 60 days, so an audit that finds AI-driven errors creates an obligation to repay. Three misconceptions come up often. The first is that the vendor carries the risk. A contract may include indemnification, but the billing provider certifies the claim. The second is that anything the AI wrote counts as documentation. Codes must be supported by what the treating clinician documented and agreed to. The third is that undercoding is the safe choice. Systematic undercoding is also inaccurate coding. The goal is codes that match the record, not codes pushed in either direction.