Coding to the documentation is required. Coding to the reimbursement is not. The distinction is narrower in conversation than in consequence — one is capturing work that was performed and recorded, the other is selecting a code because it pays more.
Every billing conversation eventually reaches a vendor promising to "optimize" your coding. The word is doing a lot of work, and it is worth being precise about which side of a real line it sits on.
The legitimate version
Under-coding is a real and common problem. Providers document thorough work and then bill conservatively out of caution, or out of habit formed during a payer review years ago. Services genuinely performed and genuinely documented go unbilled. Modifiers that the record supports are omitted because nobody applied them.
Correcting that is not aggressive. It is accuracy, and it happens to move revenue upward. A coder who reads the note and finds it supports more than was billed is doing the job.
The version that is not
Upcoding is assigning a code the documentation does not support because it pays better. It rarely announces itself. It looks like a pattern: a practice whose E/M distribution sits notably higher than its peers with no clinical explanation, modifiers applied by default rather than by the record, a code set that shifts after a vendor change without any change in the medicine.
The test is not intent, and this catches people out. Liability can attach to patterns and to knowing disregard, not only to deliberate fraud. "We did not mean to" is a weaker defense than it feels.
Where the direction of travel is decided
The question that separates the two is simple: does the change start from the record or from the fee schedule? A coder reading a note and concluding it supports a higher level is working forward from documentation. Someone reviewing reimbursement and asking which codes would pay more is working backward from money, and backward is where trouble is.
This is also why the same party assigning codes and being paid a percentage of what those codes collect deserves scrutiny. The arrangement is common and it is not inherently improper — but the incentive is structural, and the honest response is a documented query process rather than a reassurance.
What to ask a coding vendor
Ask what happens when a note does not support the code the provider selected. The answer you want is that they query the provider. If the answer is that they code to what is documented and move on, that is acceptable. If the answer involves any version of making the most of it, keep looking.
The test is the note, not the intent
Reviewers do not assess motive. They compare the code to the documentation, and a code the note does not support fails whether it was chosen carelessly or deliberately.
That makes documentation quality the practical compliance control, not coder instruction.
Audit both directions
A sample audit that only looks for overcoding misses the undercoding that is costing money. Reviewing both gives you a genuine picture and makes the exercise useful rather than purely defensive.
Practices frequently find both in the same sample, from different clinicians.
Fix the documentation, not the code
Where the work was done and the note does not show it, the answer is a better note next time rather than a higher code this time.
Templates that prompt for the elements each level requires do more than any amount of coding training, because they intervene while the information still exists.
Common questions
- What is the difference between coding optimization and upcoding?
- Optimization means capturing everything the documentation supports. Upcoding means billing a level the documentation does not support because it pays better.
- Is it upcoding if the work was actually done?
- If the work was done and documented, coding it is correct. If it was done and not documented, the code is unsupported regardless of what happened clinically.
- How do I know if my coding is too aggressive?
- Compare your code distribution to peers and audit a sample against the notes. If the documentation does not support the code, the pattern is a problem.
- Is undercoding safe?
- It is not a compliance risk but it is a real financial loss, and consistent undercoding is its own kind of inaccuracy.
- Who is responsible if a coder selects the wrong level?
- The practice submits the claim, so the practice carries the exposure. Delegating coding does not delegate accountability.
Denials Piling Up?
We handle the revenue cycle end to end — coding by certified coders, claim submission, denial management and appeals, and A/R follow-up, with six reported numbers every month.