Audits & Appeals

How to Audit-Proof Your Nutrition Claims (and Survive a Clawback)

A complete system for making MNT claims audit-proof: what triggers a payer review, the per-note checklist that survives it, the five failure modes that cause clawbacks, and what to do when a records request lands.

By Javier Alvarez, CEO of Farela · Published July 24, 2026 · ← All articles

Here is the fear, stated plainly, because pretending it isn't there doesn't help: 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 — money you earned, collected, and spent. It's called a recoupment, and RDs call it a clawback because that's what it feels like.

Now the part that actually matters: a clawback is not a judgment about your clinical work. It's a judgment about your paperwork. And paperwork is a system problem, which means it's solvable — not with vigilance or luck, but with a handful of habits that take seconds per visit and make the whole category of risk mostly go away.

This is the method. What triggers a review, what the record has to prove, the checklist that gets you there, the five ways RDs actually fail, and what to do when a letter lands anyway.

This is general information for practice management, not legal advice. Your payer contracts and state law govern your specific situation.

What a clawback actually is

Two things can happen to a claim after you submit it, and they feel very different.

The offset mechanism is what surprises people. A payer collecting a recoupment frequently just pays you less on unrelated claims until the balance clears, so an audit from last spring shows up as this month's remittance being mysteriously short. That's one reason reading your ERAs and EOBs line by line matters — an offset is visible there long before anyone explains it to you.

The honest risk picture

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 you bill lands at the top of the unit range, you look like a provider billing by default rather than by the clock. Real caseloads produce a mix, because real visits run different lengths.
• 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 actually addresses should be the same condition.
• Unsigned or late-signed notes. These don't trigger the review, but they're what turns a routine review into a finding.

A deeper treatment of triggers and the audit process itself lives in our guide to insurance audits for dietitians. This post is about the defense.

The principle everything else follows from

An audit does not evaluate whether you did good work. It evaluates whether the record proves you did the work you billed.

That distinction is the entire game, and it's genuinely unfair in one direction: you can deliver excellent, medically necessary care and still lose the money, because the note didn't say the things the reviewer needed to read. The reviewer wasn't in the room. They have your note, your claim, and — where applicable — your referral. If those three documents don't agree and don't stand on their own, the care you actually provided is invisible.

So think of it as a chain: chart → code → defense.

• The chart records what happened, including how long it took.
• The code is derived from the chart — the CPT, the units, the diagnosis.
• The defense is simply producing the chart that generated the code.

A chain fails at its weakest link. A beautiful note attached to a claim with mismatched units fails. Perfect coding on top of a note with no documented time fails. And a defense assembled under deadline pressure from notes written weeks after the visits fails most of all, because reconstruction is visible to anyone who reads records for a living.

The fix is to stop treating the defense as something you build when the letter arrives. It's built at the moment of billing, or it isn't built at all.

The audit-proof checklist

This is the centerpiece. Every MNT note should carry all of it — not because auditors are pedantic, but because each line is one of the questions a reviewer is required to answer 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–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

Twelve lines. If your template surfaces all twelve, audit-proofing stops being a skill you exercise and becomes a form you complete. Our SOAP note templates for dietitians are built around exactly these elements, and charting for medical necessity covers the language that makes the necessity line persuasive instead of generic.

One caveat worth stating: payers do not all want the same things. Some require the referral in the record; some want specific elements in a plan of care; some have their own MNT policy defining covered diagnoses. Check documentation requirements by payer for the ones you're contracted with, and treat the checklist above as the floor rather than the ceiling.

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 one 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 about your clinical judgment — the units are simply unsupported.

Fix: write start and stop times in every note, and let the units follow the clock rather than the other way around. 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 establish that the session was medically necessary for a diagnosed condition, which is the thing being reviewed. Notes that could describe any patient on any day are notes a reviewer can deny 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 — accepted by some payers' preventive benefits, rejected outright as a primary diagnosis by others — which is worth understanding on its own terms in 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 actually covers. The broader catalog of coding-driven failures is in why nutrition claims get denied.

4. Missing signature, late signature, or a note written long after the visit

An unsigned note is, to an auditor, no note at all. A note created weeks after the date of service raises the obvious question of what it was based on. And a series of notes that are textually near-identical across patients reads as a template rather than a record of care.

Fix: sign the same day, with credentials. If you genuinely need to add something later, label it as an addendum with the real date — never edit the original to look contemporaneous.

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 retrievable by date of service in one place. The mechanics of the response are covered in what to do when a payer requests your chart notes.

When it happens anyway

Random reviews exist. Here's the sequence, and where the deadlines bite.

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. Calendar the deadline 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, which produces 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, but not 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. Read the findings against your own copy of what you sent, claim by claim, before you accept anything — reviewers make mistakes, including missing documents you actually submitted.

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're disputing, why it's wrong in two or three sentences, the documentation that proves it, and a specific request — just with more money attached. If the payer extrapolated an error rate across claims it never reviewed, contest the sample and the arithmetic; that's often where the largest dollars are.

5. Watch every other clock while this runs. An audit consumes attention, and attention is what timely filing feeds on. Claims still have to go out and denials still have to be worked while you're assembling records — see timely filing limits by payer for why the weeks you're most behind are the weeks the deadline does its damage.

If a finding stands and the amount is real, negotiate a repayment plan rather than letting offsets quietly drain your cash flow. And when the number is large, paying a healthcare attorney or an experienced billing consultant for a few hours is cheap relative to what's in dispute.

Making it systematic instead of heroic

Read back through the checklist and notice what it demands: not expertise, but consistency — the same twelve elements, on every note, on the busiest week of the year. That's precisely the thing solo practice is worst at. Documentation quality doesn't decay because RDs forget what good documentation is. It decays because Thursday had six clients and the notes got written Sunday night from memory, where the time becomes an estimate and the intervention becomes a summary.

Systematizing it means three things:

1. Capture time and content while the session is happening, not from recall.
2. Derive the code from the note, so units and diagnosis can't drift from what the record supports.
3. Check the chain before the claim goes out, while fixing it is free.

You can do all three with a template, a timer, and real discipline. Plenty of RDs do. The question is whether that discipline survives the months when your caseload is full — because the claims billed during those months are exactly the ones a lookback will land on.

How Farela helps: Farela drafts each note from the actual session, so the face-to-face time and the intervention content are recorded rather than reconstructed — then runs an automated check behind every claim before it's filed, verifying that the documented session supports the CPT code, the units, and the diagnosis. Your audit defense gets built at the moment of billing instead of reassembled under a deadline eighteen months later. Farela does not represent you in an audit and does not give legal advice; it makes sure the record and the claim never tell different stories. $99/month — start a 7-day free trial.