How to audit-proof nutrition claims and survive a clawback
How to keep MNT claims safe in a payer review: what triggers audits, a per-note checklist, the five clawback failure modes, and records requests.
A payer can review records for sessions you delivered months or years ago, decide the documentation doesn't support what you billed, and demand the money back. That is a recoupment. RDs call it a clawback, because the money was already earned, collected and spent.
A clawback judges your paperwork, not your clinical work. Paperwork can be fixed with a few habits that take seconds per visit, and they remove most of the risk.
This page covers what triggers a review, what the record has to prove, a checklist for every note, the five ways RDs actually fail, and what to do when a letter arrives anyway.
This is general information for practice management, not legal advice. Your payer contracts and state law govern your specific situation.
What a clawback is
A claim can be reviewed before it pays or after. The two feel very different.
| Pre-payment review | Post-payment audit | |
|---|---|---|
| When | Payment is held; the payer asks for records before paying | Months or years after the claim paid |
| What's at stake | Delayed or denied payment on pending claims | Recoupment: repaying money you already have |
| How it reaches you | Payment stalls, then a records request | A records request, then a findings letter and a demand |
| How it's collected | Nothing to collect; the claim doesn't pay | Direct repayment, or offset against your future remittances |
The offset surprises people. A payer collecting a recoupment often pays you less on unrelated claims until the balance clears, so an audit from last spring shows up as this month's remittance coming in short. An offset is visible on the remittance long before anyone explains it to you, which is one reason to read your ERAs and EOBs line by line.
What gets you reviewed
Some reviews are random and you cannot prevent them. The rest start with your claims data, not your charts. Payer software looks for outliers, and the patterns that flag dietitians are consistent:
- Everything billed at maximum units. If every session lands at the top of the unit range, you look like a provider billing by default instead of by the clock. Real visits run different lengths, so real caseloads produce a mix.
- Time that can't support the units. Units imply minutes. Stack enough maximum-unit sessions on one calendar day and the arithmetic describes a workday that couldn't have happened.
- Initial-assessment codes that repeat. 97802 is the initial assessment. Seeing it more than once for the same patient, or at an odd ratio to 97803, is an easy automated flag.
- Visit frequency well above peers. Every patient, every week, for months, at a rate far above other RDs in your region.
- Diagnosis inconsistency. The condition on the claim, the condition in the referral, and the condition your note addresses should be the same condition.
- Unsigned or late-signed notes. These don't trigger the review, but they turn a routine review into a finding.
Our guide to insurance audits for dietitians covers the triggers and the audit process in more depth. This post is about the defense.
The record has to prove the work
An audit does not ask whether you did good work. It asks whether the record proves you did the work you billed.
That is unfair in one direction. You can deliver excellent, medically necessary care and still lose the money, because the note didn't say what the reviewer needed to read. The reviewer wasn't in the room. They have your note, your claim and, where it applies, your referral. If those documents don't agree and can't stand on their own, the care you provided is invisible to them.
Think of it as a chain: chart, code, defense. The chart records what happened, including how long it took. The code (CPT, units, diagnosis) comes from the chart. The defense is producing the chart that generated the code.
The chain breaks at its weakest link. A good note attached to a claim with mismatched units fails. Perfect coding on a note with no documented time fails. A defense assembled under deadline from notes written weeks after the visits fails worst of all, because anyone who reads records for a living can see a reconstruction.
So the defense gets built when you bill, not when the letter arrives.
The audit-proof checklist
Each line answers a question the reviewer has to settle from your record alone. Run it before you sign, every time:
- Date of service and place of service stated, matching the claim (including the correct telehealth designation if the visit was virtual)
- Start and stop time, or total face-to-face minutes, written explicitly ("Total face-to-face time 53 minutes, 3:00 to 3:53pm")
- Units that follow from that time, under the midpoint logic your payer applies, never a default number
- CPT that matches the visit type: initial assessment code for an initial assessment, follow-up code for a follow-up
- Diagnosis named in the note, and it is the same diagnosis on the claim
- Assessment tied to that diagnosis with specifics: labs, weights, intake data, glucose logs, dates, numbers
- Intervention described concretely: what you taught, adjusted or counseled, not "provided nutrition education"
- Medical necessity stated in clinical language: why this patient needed this service on this date
- Plan with measurable goals and a follow-up interval, plus progress against prior goals on follow-up visits
- Referral on file where the payer requires one, with the referring provider's name and NPI
- Signature, credentials, and date, signed the day of service
- Consistency check: note, claim, and referral tell the same story about the same patient, condition, date, and duration
If your template has a field for all twelve, you fill in a form instead of remembering a skill. Our SOAP note templates for dietitians are built around these elements, and charting for medical necessity covers the wording that makes the necessity line specific.
Payers don't all want the same things. Some require the referral in the record, some want specific elements in a plan of care, and some have their own MNT policy that defines covered diagnoses. Check documentation requirements by payer for the ones you're contracted with, and treat the checklist as the minimum.
The five failure modes
Nearly every clawback against a private-practice RD traces to one of these.
1. No documented time on a time-based code
This is the most common finding, and the cheapest for a reviewer to make. 97802 and 97803 are timed codes. A note with no minutes cannot support any number of units, so the reviewer doesn't have to argue with your clinical judgment. The units are unsupported, and that's the finding.
Fix: write start and stop times in every note, and let the units follow the clock. A 38-minute visit is a 38-minute visit.
2. Necessity implied instead of stated
"Discussed diet, patient doing well" describes a session that happened. It doesn't show that the session was medically necessary for a diagnosed condition, which is what is being reviewed. A reviewer can deny a note that could describe any patient on any day without feeling unfair.
Fix: name the condition, connect your findings to it, describe the intervention specifically, and state what continued care is for. The phrase-level detail is in charting for medical necessity.
3. Diagnosis that doesn't match across documents
The claim says one thing, the note addresses another, the referral names a third. Each mismatch is a finding. The classic RD version involves Z71.3, which some payers' preventive benefits accept and others reject outright as a primary diagnosis. It gets its own page: why Z71.3 causes nutrition claim denials.
Fix: code from the note, not from memory or habit, and confirm the primary diagnosis is one the payer's MNT policy covers. The wider list of coding failures is in why nutrition claims get denied.
4. Missing signature, late signature, or a note written long after the visit
To an auditor, an unsigned note is no note at all. A note created weeks after the date of service raises the question of what it was based on. And notes that are nearly identical across patients read as a template, not a record of care.
Fix: sign the same day, with credentials. If you need to add something later, label it as an addendum with the real date. Never edit the original to look contemporaneous: that turns a documentation problem into a fraud problem.
5. Records you can't produce quickly and completely
You can do everything right clinically and still lose because the export took two weeks, three notes were in a different system, and the referrals were in a drawer. Deadlines in audit letters are short and enforced.
Fix: keep notes, referrals, claims and remittances in a single system you can search by date of service. How to answer the request itself is covered in what to do when a payer requests your chart notes.
When it happens anyway
1. The records request arrives. Read what's being asked for, usually complete notes for a list of dates of service, plus referrals and sometimes intake forms. Put the deadline on your calendar the day the letter arrives. It's stated in the request, and it's shorter than you think. Missing it is generally treated as failure to support the claims, the same outcome as bad documentation. If you need more time, ask in writing before the deadline.
2. You send an organized packet. One clean set per date of service, in order, signatures visible, plus a short cover letter listing what's enclosed for each claim. Keep a complete copy of everything you sent and proof of delivery. Send exactly what was requested: complete, and nothing more. The full response playbook is in insurance audits for dietitians.
3. Findings arrive. Some claims will be fine. Some may be downcoded. Some may be recouped. Before you accept anything, read the findings claim by claim against your own copy of what you sent. Reviewers make mistakes, including missing documents you did submit.
4. You appeal what's wrong. Audit findings carry appeal rights, with their own deadlines. The structure is the same as appealing a denied nutrition claim: identifiers, the specific finding you dispute, why it's wrong in two or three sentences, the documentation that proves it, and a specific request. There's just more money attached. If the payer extrapolated an error rate across claims it never reviewed, contest the sample and the arithmetic, since that is often where most of the dollars are.
5. Watch every other clock while this runs. An audit eats attention, and timely filing suffers when attention goes elsewhere. Claims still have to go out and denials still have to be worked while you assemble records. See timely filing limits by payer for why the weeks you're most behind are the weeks a deadline does its damage.
If a finding stands and the money is owed, negotiate a repayment plan instead of letting offsets drain your cash flow. If the amount was extrapolated, that math can be contested on appeal. When the number is large, a few hours with a healthcare attorney or an experienced billing consultant costs little next to what's in dispute.
Make it a system
The checklist asks for consistency more than expertise: the same twelve elements on every note, including the busiest week of the year. Solo practice is worst at exactly that. Documentation quality slips because Thursday had six clients and the notes got written Sunday night from memory, so the time becomes an estimate and the intervention becomes a summary.
A system does three things:
- It captures time and content while the session is happening, not from recall.
- It derives the code from the note, so units and diagnosis can't drift from what the record supports.
- It checks the chain before the claim goes out, while fixing it is free.
A template, a timer and discipline can do all three, and plenty of RDs manage it. The test is whether the discipline holds in the months your caseload is full, because those are the claims a lookback will land on.
Duo Practice records the session and drafts the note and the claim from it, so the face-to-face time and the intervention are captured, not reconstructed, and the units come from the session time. You review and press Submit. Duo does not represent you in an audit and does not give legal advice. Create your free account. The EHR is free; billing is 3.9% of what an insurer pays, plus your own Claim.MD plan.
Frequently asked questions
How far back can a payer audit my claims?
There is no single answer. The lookback window is set by your payer contract, the payer's own policy, and in some cases state law or the rules for that plan type. Medicare, Medicaid and commercial plans all work on different timelines. Your network contract tells you yours, so read it before you need it.
Do I have to comply with a payer's request for chart notes?
If you are contracted with that payer, your agreement almost always obligates you to produce records for claims under review, and HIPAA permits disclosure for payment and health care operations. Not responding is generally treated as a failure to support the claims, which leads to denial or recoupment of every claim in the sample. Respond, meet the deadline, and send exactly what was requested.
Does a paid claim mean my documentation was accepted?
No. Most claims pay without a human ever reading a note, because adjudication checks data, not documentation. Payment is provisional until the record behind it has survived review, which is why a claim paid a year ago can still be recouped today.
Part of Denials, ERAs & appeals.