What Makes a Claim Clean
A clean claim is one a payer accepts on first submission without needing anything corrected, added, or explained. That is a deceptively simple definition, because clean is not a quality a claim has on its own — it is a claim being right for a particular payer, under that payer's current rules.
Updated 6 min read
Reviewed by Anwaar Tayyab
Director of Billing Operations ·
On this page
Key takeaways
- Clean means accepted first time with no correction — not error-free in the abstract. The same claim can be clean for one payer and not another.
- Edits come in layers that ask different questions: is it structurally valid, are the codes valid, and will this payer accept this claim.
- Payer edits are the layer that moves. Rules change, and an edit set that is not maintained will pass claims the payer has started refusing.
- Clean is upstream work wearing a billing label. Most of what makes a claim clean was decided at registration, in the documentation, and in coding — before billing saw it.
What clean actually means
The operational definition is narrow and worth stating precisely: a claim is clean if it goes through on the first attempt with no intervention. Not paid in full — accepted and processed without needing correction. A clean claim can still be denied on the merits, and a claim that took three attempts to get accepted was never clean even if it was eventually paid in full.
That definition has a consequence people find uncomfortable: clean is relative. Payers have different requirements, and a claim that is perfectly acceptable to one can be refused by another for a rule the first does not apply. There is no such thing as a claim that is clean in the abstract — only a claim that is clean for the payer it was sent to, under the rules in force the day it arrived.
Clean is measured, and the measurement has a catch
The layers of edits
Scrubbing is not one check. It is layers of them, and they ask genuinely different questions — which is why a claim can pass one layer completely and fail the next for a reason the first had no opinion about.
| Layer | The question it asks | How often it changes |
|---|---|---|
| Format | Is this structurally a valid claim? Required fields present, values the right shape, the transaction well formed. | Rarely. The standards are stable, so a format failure usually means a data problem rather than a rule that moved. |
| Data and identity | Do the identifiers match? Member ID, NPI, dates that are internally consistent. | Rarely as rules, constantly as data. The rule is stable; the patient's coverage is not. |
| Code validity | Are the reported codes current, and validly combined? Whether a modifier is permitted with a code, whether a code retired. | On a schedule. Code sets are revised, and a claim can be refused for a code that was correct last year. |
| Payer rules | Will this payer accept this claim? Its coverage policies, its documentation requirements, its own quirks. | Continuously. This is the layer that goes stale. |
The layers are ordered by how much they move, and that ordering is the practical point: a format failure is a bug in your process, while a payer-rule failure is often the rule having changed underneath a process that was working yesterday.
The layer that moves
Every layer above the last one is fairly stable. Payer rules are not. That alone explains a failure pattern that is otherwise baffling: a claim type that has been going through cleanly for a year suddenly starts coming back, and nothing in the practice changed.
Because nothing in the practice did change. A scrubber is only as current as its edit set, so an edit that is not maintained will happily pass claims the payer has started refusing — the gate is open, and the check it was supposed to run no longer matches the rule it was checking against. The claims look clean right up until the payer disagrees.
A cluster of one reason is usually an edit, not a habit
Clean is decided upstream
It is worth being blunt about where clean is actually produced, because the term sounds like a billing property and mostly is not. By the time a claim reaches the scrubber, nearly everything that determines whether it is clean has already been decided by someone else.
- Registration decided identity and coverage
- Whether the member ID matches, whether the coverage was active, whether the right plan is being billed first. Billing cannot make a claim clean if the eligibility underneath it is wrong — it can only find out sooner.
- Documentation decided what can be supported
- A claim can only assert what the record establishes. Where the clinical reason for a service is not in the note, no amount of billing care puts it there.
- Coding decided what is asserted
- Which codes, which modifiers, which diagnosis pairing. Scrubbing checks whether those choices can be transmitted and accepted — it does not check whether they were the right choices.
- Billing decided how fast, and how well-checked
- The one part billing owns outright: whether the claim is checked before it goes, and whether it goes promptly. That is not nothing — it is the difference between finding a problem at the cheapest gate and finding it at the most expensive one.
Which is why reading the clean claim rate as a billing scorecard gets the diagnosis wrong. When it falls, the question is not who in billing slipped — it is which upstream input changed, because billing owns only the last two of the four decisions above. Denial Prevention sets out what to do with that answer.
Common questions
Does a clean claim mean the claim gets paid?
No. Clean means accepted and processed on first submission with no correction needed — it is about whether the claim could be handled, not about whether the payer agrees it owes money. A clean claim can still be denied on the merits: the coverage may not include the service, or the reported diagnosis may not support it. Clean is a submission-quality property; payment is a coverage decision.
Can the same claim be clean for one payer and not another?
Yes, and that is the most important thing to understand about the term. Payers apply different rules, so a claim that one accepts without comment can be refused by another for a requirement the first does not have. There is no claim that is clean in the abstract — only a claim that is clean for the payer it was sent to, under the rules in force when it arrived.
Our claims were going through fine and now they aren't. What changed?
Very often, a rule did. Payer requirements change, and a scrubber is only as current as its edit set — so an edit that is not maintained will keep passing claims the payer has started refusing. When failures rise sharply and share a single reason, a rule change or a stale edit is a better first hypothesis than a sudden decline in the billing team, because human error is distributed rather than arriving all at once on one reason.
Is a claim held by our scrubber a bad sign?
Usually the opposite — a hold is an edit doing its job at the cheapest point in the lifecycle, which is covered in The Claim Lifecycle. What is worth reading into a hold rate here is which layer is holding claims. A rise in format holds points at a data or interface problem; a rise in payer-rule holds usually means a rule moved and your edit set caught up with it, which is the system working exactly as intended.
Key terms in this article
Defined once, on their own pages.
Continue learning
Where to go next on claims.
Clean claim rate calculator
Calculate the share of your claims that pass on first submission.
Submitting Claims
What happens after the scrubber — routing, and the acknowledgments that report the result.
Denial Prevention
The upstream controls that decide whether a claim can be clean at all.
Clean claim rate
The metric, and why it moves before the denial rate does.
Corrections
The article said payer rules change “without announcement” and that payers “are not obliged to tell you when they change.” That is not correct for the largest payers. Under 42 U.S.C. 1395hh(b)(1) the Secretary must give notice of a proposed Medicare regulation in the Federal Register and allow not less than 60 days for public comment, and under 1395hh(c)(1) must publish in the Federal Register, not less frequently than every 3 months, a list of all manual instructions, interpretative rules, statements of policy, and guidelines of general applicability. The assertion has been removed from the comparison table, from the section that followed it, and from the FAQ answer. The article's actual point is unaffected: payer rules are still the layer that moves, and an edit set that is not maintained will still pass claims the payer has started refusing.
Authoritative sources
- X12 — Transaction sets, including the 837 health care claim (opens in a new tab)
X12 defines and maintains the transaction sets that establish the data content exchanged for a business purpose, each maintained by a subcommittee of its Accredited Standards Committee. The listing includes the 837 health care claim — the transaction the format layer of scrubbing validates a claim against.
- CMS — Medicare Claims Processing Manual, Pub. 100-04, Chapter 1, Section 80.2, Definition of Clean Claim (opens in a new tab)
Defines a clean claim, for Medicare, as one that does not require the contractor to investigate or develop external to its Medicare operation on a prepayment basis. Its examples include claims that pass all contractor and Common Working File edits, that do not require external development, and that carry all basic information necessary to adjudicate the claim along with all required supporting documentation.
- HFMA — MAP Keys: Clean Claim Rate (CL-1) (opens in a new tab)
Healthcare Financial Management Association. Its MAP Keys are revenue-cycle key performance indicators that HFMA states are used to track performance through objective, consistent calculations, each published with a detailed definition giving its inclusions, exclusions, and the data sources the figure is drawn from. Clean Claim Rate (CL-1) is one of them: the count of claims that clear edits with no manual intervention, over the count of claims accepted into the claims processing tool for billing. The definition runs down to its exclusions — printed and mailed claims, claims held because intervention is required, and claims never sent to the claims processing system are all outside the count.
- 42 U.S.C. 1395hh — Rulemaking for the Medicare program (opens in a new tab)
United States Code, 2023 Edition (GPO). Subsection (b)(1) requires the Secretary, before issuing any Medicare regulation in final form, to provide notice of the proposed regulation in the Federal Register and a period of not less than 60 days for public comment, subject to the exceptions listed in (b)(2). Subsection (c)(1) requires publication in the Federal Register, not less frequently than every 3 months, of a list of all manual instructions, interpretative rules, statements of policy, and guidelines of general applicability promulgated to carry out the Medicare subchapter that have not previously been published in such a list. The source for the correction recorded above: the country's largest payer is under a statutory duty to publish its rule and manual changes.