9.5 Audits, Denials, Rebilling, and Overpayment Risk
Key Takeaways
- Audits should evaluate whether coding was supported at the time of billing by documentation, official guidelines, payer rules, and facility policy.
- Denial management must distinguish coding error, documentation insufficiency, authorization failure, coverage exclusion, payer processing error, and contract dispute.
- Rebilling is appropriate when the original claim was wrong and the corrected claim is supported; it is not appropriate as unsupported payment engineering.
- Potential overpayments require timely escalation through facility compliance processes, because repayment and correction duties may apply.
Defensible corrections and denial response
Audits, denials, rebilling, and overpayment handling are where coding decisions are tested after the claim leaves the coding desk. An audit may come from internal quality review, compliance, a payer, a government contractor, a vendor, or a focused review after denial trends. A denial may challenge medical necessity, coding accuracy, modifier use, DRG assignment, authorization, coverage, timeliness, or documentation. The coder's role is to evaluate the evidence and rules without treating payment as proof of correctness.
A paid claim can still be wrong. A denied claim can still be coded correctly. This is a core CCS compliance principle. Payment systems use edits, contracts, benefit logic, and payer-specific processing that do not always match coding truth. The coder must decide whether the denial reveals a coding error, a documentation gap, a missing attachment, a coverage issue, a payer processing issue, or a billing workflow problem. Each cause has a different remedy.
| Review finding | Likely action | What not to do |
|---|---|---|
| Wrong code assigned for documented service | Correct and rebill according to policy | Defend a code known to be wrong |
| Documentation supports code, payer missed policy exception | Appeal with record excerpts and policy support | Change to an unsupported code just to pay |
| Missing operative report or order caused denial | Submit required documentation if allowed | Alter codes when documentation was the issue |
| Authorization absent | Route to billing, utilization, or authorization process | Recode the service as something else |
| Overcoded secondary diagnosis identified | Escalate, correct, and follow refund process if needed | Ignore because the claim already paid |
| Conflicting documentation discovered after billing | Query or follow correction policy if allowed | Choose the version that preserves payment without clarification |
Audits should be reproducible. A reviewer should be able to see the claim, the coded data, the relevant record sections, the applicable guideline or payer rule, the original coder rationale if available, and the reason for any change. If a secondary diagnosis is removed, the audit note should explain whether it lacked provider documentation, did not meet reporting criteria, was ruled out, was from a prior encounter only, or was clinically irrelevant under facility policy. If a code is retained, the note should point to the support.
Denial response should avoid two extremes. The first is automatic appeal of every denial, which wastes effort and may defend weak claims. The second is automatic recoding, which can create false claim risk if the new code is chosen only for payment. A structured denial workflow asks what the payer challenged, whether the challenge is valid, whether the record supports the original claim, whether a correction is warranted, and whether the organization has a broader trend to fix.
A practical audit and denial workflow is:
- Identify the claim version, date of service, payer, denial code or audit issue, and amount at risk.
- Pull the source record as it existed for the service and any allowed late documentation or clarification under policy.
- Recode the issue independently using current official guidance for the date of service and payer policy in effect for the claim.
- Compare the independent result to the billed claim. Mark each difference as coding error, documentation issue, payer rule issue, charge capture issue, or unclear.
- Decide the outcome: uphold original coding, correct and rebill, appeal, request provider clarification, route to another department, or escalate compliance risk.
- For potential overpayment, follow facility policy for compliance review, claim adjustment, refund, and documentation.
- Track patterns so education, charge build changes, provider documentation improvement, or edit rules can prevent recurrence.
Overpayment risk deserves special attention. If a review shows that the organization received payment for unsupported codes, duplicate charges, unbundled services, wrong units, or incorrectly assigned DRGs, the issue is not merely educational. Facility compliance leadership may need to determine scope, timing, repayment obligations, and whether a broader lookback is required. A coder should not independently conceal, delete, or quietly ignore such findings.
Rebilling must be accurate. If an inpatient account was assigned the wrong principal diagnosis because the condition after study was not present on admission as originally believed, correction may change the DRG and payment. If an outpatient claim used the wrong CPT code for the documented procedure, correction may change APC payment or denial status. The correction should reflect the record and rules, not the desired financial outcome.
For CCS exam questions, watch the verb. If the question asks for the next best action after an audit finds unsupported coding, the answer likely involves correction and compliance escalation. If it asks what to do with a denial when documentation supports the original code, the answer may be appeal with official-source support. If it asks whether a coder should change a diagnosis to one on a payer list, the answer is no unless the documentation supports that diagnosis. The best answer preserves truth first, then payment process.
A payer denial says a procedure was not medically necessary, but review shows the record and payer policy support the service. What is the best next action?
An internal audit finds that a paid claim included an unsupported MCC. What is the most compliant response?
Which denial review conclusion most strongly supports rebilling with corrected codes?