Most practices hear about AI in billing as a promise: fewer denials, faster cash, smaller teams. The reality is more specific. AI is very good at a handful of revenue cycle tasks and unreliable at others, and the difference matters when every claim carries a compliance obligation.
What AI actually does in the revenue cycle
Across the revenue cycle, AI tools fall into three groups:
- Prediction: scoring claims for denial risk, estimating which aged claims are worth working, flagging payers whose behavior has changed.
- Language: reading operative notes and comparing them with codes, drafting appeal letters, summarizing payer policies and bulletins.
- Automation: checking eligibility, filling authorization forms, posting payments and routing work queues.
Each of these saves time on repetitive work. None of them replaces the judgment of a credentialed coder or an experienced AR specialist.
Where AI helps most
| Task | What AI does | Why it works |
|---|---|---|
| Denial prediction | Scores each claim before submission | Denials follow patterns by payer, code and modifier |
| Coding cross-checks | Compares the op note with billed CPT codes and modifiers | Finds missed add-ons and unsupported lines quickly |
| Appeal drafting | Writes a first draft citing the record and policy | Saves the slowest part of appeal work |
| Underpayment detection | Compares allowed amounts with contract terms | Humans can't check every line by hand |
| AR prioritization | Ranks aged claims by value and deadline | Puts effort where recovery is likely |
Where AI fails
AI models can sound confident and still be wrong. In billing that shows up as:
- Invented codes or rules. A model may cite a modifier rule or policy that doesn't exist.
- Missing context. It doesn't know your payer contracts, local coverage decisions or what the physician said in the hallway.
- Over-coding risk. A tool tuned to "find missed revenue" can push toward codes the documentation doesn't support, which creates audit exposure.
The rule we follow: software flags and drafts; a credentialed person decides.
Safeguards every practice should require
- A signed Business Associate Agreement with any vendor whose AI touches protected health information.
- Minimum-necessary data: the tool sees only the fields its task needs.
- No training of public models on your patients' data.
- Human review of every coding suggestion and appeal before submission, with the reviewer logged.
- Coding decisions grounded in CPT, ICD-10-CM and NCCI rules, not model output.
How RAS uses AI
We use AI for denial risk scoring, op-note-to-code cross-checks, appeal drafting, payer policy tracking and AR prioritization. Every output is reviewed by our credentialed coding and AR team before it touches a claim. The guides in this series cover each use case in detail, starting with denial prediction.
This article is general billing information, not legal or coding-compliance advice. Payer rules, CPT descriptors and federal guidance change; check the current versions for your claims.