Insurance Billing

Prior Authorization for Nutrition Services: When You Need It and How to Get It

When MNT requires prior authorization, how dietitians request it, what goes on the claim, and why a no-auth denial usually can't be billed to the patient.

By Alva Health Team · Published July 12, 2026 · ← All articles

You verified benefits, got the referral, billed clean codes — and the claim still denied: "authorization required." Worse, when you call to fix it, the payer tells you authorizations can't be issued after the fact. The visit happened, the care was covered, and nobody is going to pay for it.

Prior authorization is not the norm for nutrition services, which is exactly what makes it dangerous: it shows up on a minority of plans, unannounced, and the penalty for missing it usually lands on you, not the patient.

Here's when auth applies to MNT, how to find out before it bites, and how to run the request process without losing hours to it.

What prior authorization actually is

Prior authorization (also "pre-authorization," "pre-certification," or just "auth") is the payer's requirement that you get approval before delivering a service. The payer reviews the request against its medical policy and, if approved, issues an authorization number covering a specific patient, specific codes, a set number of visits or units, and a date range.

It's a different gate than the ones you already manage:

• Eligibility — does the patient have active coverage?
• Benefits — does the plan cover nutrition counseling, and on what terms?
• Referral — did the right provider order the service?
• Prior authorization — did the payer approve this care, in advance?

A claim can clear the first three and still die on the fourth.

How common is auth for MNT?

Honest answer: not very — and that's the trap. Most commercial plans pay 97802 and 97803 without prior authorization. But it does appear, most commonly in these situations:

Traditional Medicare does not require prior authorization for MNT — it requires a physician referral, which is a different thing (our Medicare MNT guide covers those rules).

Because auth is the exception, practices stop asking about it. Then plan number 37 requires it, and the denial arrives six weeks after the visit.

How to find out: it's one verification question

Auth requirements live at the plan level, so the answer comes from the same benefits verification you should be running before every new patient. Add these to your verification call:

1. "Is prior authorization required for CPT 97802 or 97803 under this plan?"
2. "Is authorization required after a certain number of visits?"
3. "If yes — how do I submit the request, and what's the typical turnaround?"
4. "Can I have a reference number for this call?"

That last one matters: if a rep says "no auth required" and the claim later denies for no auth, the call reference is the backbone of your appeal.

The request process, step by step

When a plan does require auth, the process is bureaucratic but predictable:

1. Gather the packet. Payers typically want: patient demographics and member ID; the referring physician's name, NPI, and diagnosis (ICD-10 — e.g., E11.9, N18.3, E66.9, whatever the referral supports); the CPT codes you'll bill; the number of visits or units requested; and sometimes a brief clinical summary or the referral itself establishing medical necessity.
2. Submit through the payer's channel. Usually the provider portal; sometimes fax with a payer-specific form. Portal submissions are easier to track and time-stamp.
3. Wait — and log the dates. Routine requests commonly turn around in days to a couple of weeks, but timelines vary by payer and state. If a patient is booked soon, ask whether an expedited review is available.
4. Record the approval. You'll receive an authorization number, the approved codes, the visit/unit count, and the valid date range. Store all four with the patient's record — you'll need every one of them.

If the request is denied, you can appeal it like any adverse decision — with clinical documentation and the referring physician's support. That's a pre-service appeal, and it's usually more winnable than fighting a post-service no-auth denial.

Putting the auth on the claim

An approved auth only protects you if the claim references it. The authorization number goes in the prior authorization field of the claim — Box 23 on the CMS-1500, or the corresponding field in your billing software. Omit it and the payer's system may deny for no auth even though one exists — a self-inflicted, though fixable, denial.

Also make sure the claim matches the auth: same CPT codes, dates of service inside the auth window, visits within the approved count. Mismatches deny.

Retro-authorization: don't plan on it

If the visit already happened without an auth, your options are thin. Most payers grant retroactive authorization only in narrow cases — emergencies, or situations where coverage genuinely couldn't be verified. A few allow a short retro window (sometimes measured in days). Always ask, because occasionally the answer is yes. But build your workflow assuming the answer is no.

The denial usually isn't patient-billable

Here's the part that makes prevention non-negotiable. When an in-network claim denies for missing authorization, most network contracts treat obtaining the auth as your responsibility — which means the denial is a provider write-off. You generally cannot bill the patient for it, and trying to invites contract trouble.

So a missed auth isn't a paperwork inconvenience; it's the full value of the visit, gone. Compare that to a denied-for-coding claim, which a corrected claim usually rescues (see why nutrition claims get denied for the full taxonomy). No-auth denials sit in the small, brutal category of denials that are cheap to prevent and nearly impossible to cure.

Tracking: the second failure mode

The first failure is not getting the auth. The second is outliving it. Every auth has two fuses burning:

• The visit count. Six approved visits means visit seven denies.
• The expiration date. An auth valid through a set date means the visit after it denies, even with visits remaining.

For ongoing MNT patients — exactly the ones auth-requiring plans tend to cover — you need a running tally: visits used against visits approved, and days remaining on the window. Request the renewal before the last covered visit, since renewals take as long as originals.

A spreadsheet works at low volume. It stops working the month you're busy, which is also the month it costs the most.

The system that makes auth a non-event

Prior authorization rewards exactly one thing: knowing about it early. Ask on every verification, request before the first visit, put the number on every claim, and watch the two fuses. Practices that do this treat auth as ten minutes of admin. Practices that don't treat it as a category of unrecoverable revenue.

How Alva helps: Alva's benefits verification flags authorization requirements before the first visit, and claim validation catches a missing auth number before submission instead of after the denial. That's the difference between a write-off and a routine claim — built into a $99/month platform. Start a 7-day free trial.