What Is a Claim Scrubber? The Checks a NEMT Claim Should Pass Before It Goes Out

Billing and getting paid

Overview

A claim scrubber is software that checks a claim for errors before you send it, so a missing modifier or a blank field is fixed while the claim is still yours. For NEMT, a claim passes your own rules, then the file checks at the clearinghouse and payer, then the payer's edits. A scrubber cannot prove the trip happened, so a signed trip record still matters.

  • A scrubber catches the errors a rule can see: missing fields, wrong modifiers, too many units, a duplicate, a late claim.
  • Every Medicaid agency checks eligibility, provider authorization, duplicates, rate limits, and other insurance before it pays (42 CFR 447.45(f), as of October 2026).
  • A scrubber knows a plan's own rules only if someone loads them. South Country Health Alliance rejects or denies A0130, T2003, and T2005 claims that lack the driver's license number.
  • CMS publishes Medicaid unit limits, but its public file is not the state's edit file. For October 1 to December 31, 2026, A0130 has a limit of 2 units per line.
  • No scrubber checks the signature, trip log, or GPS record behind the claim. Those are what an auditor asks for.

What a claim scrubber is

A claim scrubber is a set of automatic checks that read a claim before you send it and flag what would make a payer reject or deny it. It looks for what a rule can see: a blank required field, a modifier the payer does not accept with that code, more units than the payer allows, a second claim for the same rider, date, and code, or a claim that is past its filing deadline. You fix the flags, then send.

It is not a promise of payment. CMS’s Medicaid NCCI page (last modified March 4, 2026) says CMS provides no look-up service or clean claims tool, so no federal tool will tell you a claim is clean. A scrubber is only as good as the rules loaded into it. For what makes a claim clean in the first place, see clean claim.

The three places a NEMT claim gets checked

Check Where it runs What comes back
Your own rules In your billing or dispatch system, before you send A warning on your screen
File and format checks At your clearinghouse and again at the payer’s front door A 999 for the file and a 277CA for each claim
The payer’s edits In the payer’s claims system A denial on the remittance, or a rejection report

Only the first check is yours to design. The second reads the standard 837P file format, and Medicare’s claims manual (Chapter 24, April 10, 2025) shows how the reports split: an error that spoils the whole file comes back on a TA1 or 999, and an error in one claim comes back as a rejection on the 277CA. See claim rejection vs denial for what to do with each report, and clearinghouse for who sends them.

What the payer’s edits check

Federal rule 42 CFR 447.45(f) tells every state Medicaid agency to check every claim before it pays: that the rider was in the eligibility file and you were authorized to give the service, that the services fit the rider’s circumstances, that the claim duplicates no other, that the payment stays within the state plan’s rates and limits, and whether another insurer should pay first (as of October 2026). Two of those checks rest on data only the payer holds, its eligibility file and the claims it has already reviewed, so a scrubbed claim can still deny.

States also run the National Correct Coding Initiative (NCCI). Section 1903(r) of the Social Security Act, at 42 U.S.C. 1396b(r)(1)(B)(iv), requires state claims systems to incorporate compatible NCCI methods, and CMS says the methods must be applied to fee-for-service claims, while calling their use on claims processed by managed care organizations desirable but optional. NCCI has two edit types: code pairs that should not be billed together, and medically unlikely edits (MUEs), which cap the units of one code per rider per day. Medicaid applies MUEs to each claim line separately.

CMS’s public MUE file for dates of service October 1 to December 31, 2026 lists A0130 at 2 units, A0100 and A0110 at 2, and A0425 at 250. It lists no value for T2001, T2003, T2005, T2007, S0209, S0215, or T2049. The file itself says states should not use it as their edit file, so your state’s own edits decide. Use it as a guide, and take your real limits from your state or plan.

NEMT rules worth loading into your own scrubber

These are payer rules, each with its date. None is national.

  • Origin and destination modifiers. South Country Health Alliance (manual updated February 27, 2026) wants them on every pickup and mileage line. See origin and destination modifiers.
  • Same-day trips on one claim. Arizona’s fee-for-service manual (July 31, 2026) says all trips for one member on one date go on one claim, with the base rate on line 1, loaded miles on line 2, and wait time on line 3. A second claim for the same date denies as a duplicate.
  • Addresses. Arizona has required the pickup and drop-off addresses on every NEMT trip since November 1, 2022, in the “Additional Information” field of the 837P. A paper claim lists the street address and zip code in box 19.
  • Wait time. Arizona does not allow T2007 for waits under 30 minutes, for a one-way trip, or when the medical site is 10 miles or less away. South Country pays it only after the first 60 minutes, up to 2 units of 30 minutes.
  • Authorization. Arizona lets fee-for-service providers bill without prior authorization when one member’s mileage on one date is under 100 miles. MTM Health’s Virginia handbook says not to transport a member without the trip ID. See prior authorization.
  • Trip data. MTM Health in Virginia denies a claim when the trip ID, scheduled pickup time, actual pickup time, departure time, arrival time, or the member’s signature is missing, or the trip is not in completed status. It gives providers 6 months from the date of service to send a clean claim.
  • Filing deadline. Federal rule 42 CFR 447.45(d)(1) requires a state to make providers file within 12 months of the date of service, and states and brokers can set less. See timely filing limit.

A wheelchair trip caught before it went out

You drive a South Country member in a wheelchair from home to a doctor’s office. Your system builds two lines: A0130 for the pickup and S0209 for the loaded miles. A scrubber that holds South Country’s Chapter 27 flags two problems:

  1. Neither line has an origin and destination modifier. The manual wants them on every pickup and mileage line, and RP means residence to physician’s office.
  2. The A0130 line has no driver’s license number in the description field of Loop 2400, SV101-7. The manual says a claim without it will reject or deny, and the number must have no spaces or dashes.

You add RP to both lines and the license number to the A0130 line, then send. Another payer would have needed different fixes, so a scrubber keeps one list of rules for each payer.

What a scrubber cannot catch

A scrubber checks that a field is filled in. It cannot check that the field is true. It cannot see that the rider signed, that the driver’s trip record matches the miles billed, or that the GPS trail agrees with the pickup time. Those are what a payer’s auditor asks for later, and MTM Health’s Virginia handbook scores providers on a measure that compares each trip’s time with its miles. Keep the signed record behind every claim, as described in NEMT trip documentation.

How to use one

  1. Load each payer’s rules from its manual, with the manual’s date, and note where each rule comes from.
  2. Run every batch before you send it. Fix flags the same day, because the filing clock keeps running.
  3. Turn each rejection into a rule. When a payer rejects something your scrubber passed, add that check.
  4. Review the rules when payers change them. CMS posts new NCCI edit files each quarter, and manuals are revised in between.
  5. Read the denials that still come. They show what the scrubber cannot see. See NEMT claim denials.

Frequently asked questions

What does a claim scrubber do?

It runs a list of rules against each claim before it is sent and flags the ones that would fail, such as a missing member ID, an origin and destination modifier left off, more units than a payer allows, a duplicate line, or a claim past its filing deadline. You fix the flags and send a claim the payer can process. It does not decide whether the payer will pay.

Is a claim scrubber the same as a clearinghouse?

No. A clearinghouse converts your claims into the standard 837P file, routes them to each payer, and returns the 999 and 277CA reports. A scrubber is a set of checks, and some billing systems and clearinghouses include one. Ask yours which rules it runs, and whether it holds each payer's own requirements or only the standard file format.

Can a scrubbed claim still be denied?

Yes. Under 42 CFR 447.45(f), a Medicaid agency checks every claim before payment for eligibility, provider authorization, duplicates, rates and limits, and other insurance. A rider whose coverage lapsed, a trip with no authorization, or a missing signature can all pass your checks and still deny. A clean claim is one the payer can process without asking for more.

Does CMS offer a free claim scrubber?

No. CMS's Medicaid NCCI page, last modified March 4, 2026, says it provides no look-up service or clean claims tool. It does post public NCCI edit files each quarter, which help you set unit limits, but the page says states must use the edit files from CMS's secure portal and not the public ones.

What should a NEMT claim scrubber check first?

Start with the rule behind your last few rejections. Common ones are origin and destination modifiers on every pickup and mileage line, units against the payer's limits, wait time only where the payer allows it, the authorization or trip number, pickup and drop-off addresses where required, and the filing deadline. Add each payer's own rules from its manual.

Official resources

Join the NEMT Guide Digest

Our free newsletter for NEMT owners: broker changes, new state rules, and new guides, sent when there is news worth your time. No spam.