AnyLearn
All lessons
Businessintermediate

Claims, Denials, Compliance, and Getting Hired

Codes only become money once a claim is submitted, adjudicated, and often re-worked. This lesson follows the claim lifecycle through clearinghouses and payers, explains why denial management is where billers earn their value, covers the compliance line that separates accurate coding from fraud, and how to get certified and hired.

Updated · AI-authored, review-gated · how lessons are made

Not signed in: your progress and quiz score won't be saved.
Progress1 / 7

From codes to cash

Lesson 2 produced a clean set of codes. Codes are not money. This lesson is about the billing half of the profession: turning coded services into a claim, getting it paid, and dealing with the large fraction that come back denied.

The biller's world is different from the coder's. The coder reads charts and codebooks; the biller works claims, payer rules, and denials, and the core skill is not clinical translation but navigating each payer's requirements and relentlessly following up until the provider is paid.

This lesson covers:

  • The claim lifecycle: how a claim travels from provider to payer and back.
  • Denials: why they happen, how common they are, and how they are worked, the heart of the job.
  • Compliance: the line between coding accurately and committing fraud.
  • The path in: certifications and how to get hired.

A framing to carry: submitting a claim is easy; getting it paid is the job. Anyone can send a claim. The value a biller adds is in the claims that do not sail through, the denials, the underpayments, the appeals, because that is where a provider's revenue is actually saved or lost. As you will see, a striking share of denied money is simply never recovered, and closing that gap is precisely what billers are hired to do.

Full lesson text

All 7 steps on one page, for reading, reference, and search.

Show

1. From codes to cash

Lesson 2 produced a clean set of codes. Codes are not money. This lesson is about the billing half of the profession: turning coded services into a claim, getting it paid, and dealing with the large fraction that come back denied.

The biller's world is different from the coder's. The coder reads charts and codebooks; the biller works claims, payer rules, and denials, and the core skill is not clinical translation but navigating each payer's requirements and relentlessly following up until the provider is paid.

This lesson covers:

  • The claim lifecycle: how a claim travels from provider to payer and back.
  • Denials: why they happen, how common they are, and how they are worked, the heart of the job.
  • Compliance: the line between coding accurately and committing fraud.
  • The path in: certifications and how to get hired.

A framing to carry: submitting a claim is easy; getting it paid is the job. Anyone can send a claim. The value a biller adds is in the claims that do not sail through, the denials, the underpayments, the appeals, because that is where a provider's revenue is actually saved or lost. As you will see, a striking share of denied money is simply never recovered, and closing that gap is precisely what billers are hired to do.

2. The claim lifecycle

A claim travels a defined path, and knowing it is the biller's map. The technical form of a healthcare claim is standardized under HIPAA as the 837 electronic transaction, and the payer's response comes back as the 835 electronic remittance advice. Those numbers are worth knowing because billers see them constantly.

The journey:

  • Charge entry. The coded services become charges on the claim, tied to the patient, provider, diagnoses, and procedures.
  • Scrubbing. Billing software (and billers) check the claim for errors before it goes out, missing data, mismatched codes, medical-necessity problems, catching what would otherwise be a denial.
  • Submission via a clearinghouse. Most claims do not go straight to the payer. They pass through a clearinghouse, an intermediary that formats, validates, and routes claims to the right payer, and returns status. Think of it as the postal service and quality check between provider and payer.
  • Adjudication. The payer processes the claim against the member's coverage, its rules, and medical necessity, and decides: pay in full, pay reduced, or deny.
  • Remittance (the 835). The payer sends back an electronic remittance advice explaining what it paid and why, the biller's key document.
  • Payment posting. The biller records the payment against the account and identifies the balance.
  • Patient billing. Whatever the payer did not cover, the copay, deductible, or coinsurance, is billed to the patient.

The biller's craft concentrates at two points: scrubbing (prevent denials before they happen) and reading the remittance (understand exactly what the payer did and why). A clean claim, one that is accepted and paid on first submission with no rework, is the goal, and the clean claim rate is a core metric of a billing operation, because every claim that is not clean costs time and delays cash.

3. Denials: where the job really is

Now the reality that defines the profession: a large share of claims are denied, and denials are where a biller earns their keep. This is not an occasional exception; it is a routine, high-volume part of the work.

The scale is significant. Industry data shows initial denial rates commonly in the low-to-mid teens: commercial payers around 14 percent, Medicare Advantage plans averaging near 15.7 percent, and, per an analysis of ACA marketplace plans, about 19 percent of in-network claims denied in 2023. And coding errors alone account for roughly 15 to 20 percent of initial denials. A big fraction of claims do not get paid the first time.

Here is the part that turns denials into a career: most denied claims are never reworked. According to MGMA figures, about 63 percent of denied claims are never resubmitted, and US practices forfeit an estimated 25 billion dollars a year in denied claims that are never appealed. That is money the provider earned and simply never collected, because nobody worked the denial.

That single fact is the biller's value proposition. A denied claim is not lost, it is often recoverable, if someone reads the denial reason, fixes the issue, and resubmits or appeals within the deadline. Working denials is precisely the labor most practices skip, which is why a diligent biller who actually recovers denied revenue is directly, measurably valuable.

So the honest picture of billing is not "send claims." It is denial management: understanding why a claim was denied, correcting it, and fighting for the payment, over and over, against payers who benefit from claims going unworked. The biller is the person who does not let the money sit.

4. Working a denial

Denial management has a method, and it turns a rejection into recovered revenue. Walk a realistic case.

A claim for a diagnostic test comes back denied. The biller works it:

  1. Read the remittance. The 835 carries a denial reason code. Say it reads, in effect, "service not medically necessary for the diagnosis submitted."
  2. Diagnose the denial. This is a medical-necessity mismatch (Lesson 2): the diagnosis on the claim did not justify the test. Denials fall into recognizable buckets, eligibility (patient not covered), coding (wrong or unsupported codes), medical necessity, missing information, timely-filing (submitted too late), and each has a different fix.
  3. Determine whether it is correctable. Was the wrong diagnosis coded, when the documentation actually supported a justifying one? If the chart supports a diagnosis that establishes necessity, this is fixable.
  4. Correct and act. Recode from the documentation and resubmit, or, if the original coding was right and the payer is wrong, file an appeal with the supporting documentation, before the payer's deadline.
  5. Track it. Log the denial, the reason, and the outcome, so patterns emerge ("this payer keeps denying this test") and can be fixed upstream in the scrubbing step.

Two things make this the skilled core of billing. First, it requires knowing why claims are denied and how each payer works, which is real, learnable expertise, not clerical work. Second, it is deadline-bound, timely-filing and appeal windows are strict, so denials must be worked promptly or the money is lost permanently.

The biller who systematically works denials, understands the reason codes, fixes what is fixable, appeals what is wrong, and feeds patterns back into prevention, is the one recovering the revenue that 63 percent of practices leave on the table. That is the job.

5. The compliance line

The same knowledge that gets claims paid can be misused to get paid too much, and the line between them is a legal one every biller and coder must respect. Coding accurately is the job; coding to inflate payment is fraud, and it carries serious consequences.

The recognized forms:

  • Upcoding. Billing a higher-level or more expensive service or diagnosis than was actually provided or documented, a longer visit, a more complex procedure, a more severe condition, than the record supports.
  • Unbundling (fragmentation). Billing separately for services that should be grouped under a single code, which inflates the total, when they are meant to be paid as one.
  • Modifier misuse. Adding modifiers to suggest additional, distinct procedures that were really part of the base service, precisely the abuse the modifier system enables if used dishonestly (Lesson 2).
  • Billing for services not rendered, or exaggerating time or complexity beyond what was medically necessary and documented.

The governing law in the US is the False Claims Act, which makes submitting false claims to government payers illegal and carries penalties per false claim (commonly cited in the range of roughly 11,000 to 22,000 dollars each, plus multipliers), on top of repayment and potential exclusion from federal programs. Real practices have paid large settlements over exactly these issues, including modifier misuse.

The principle that keeps a coder safe is simple and absolute: code what is documented, accurately, and only that. Not more (to earn more), not less (which loses legitimate revenue and can also be non-compliant). The documentation is the truth, and the code must match it.

This is why the profession is built on integrity as much as skill. A biller or coder is trusted to convert care into payment honestly, and "the doctor told me to" or "everyone does it" is not a defense. Compliance is not a constraint bolted onto the job; it is the job done correctly.

6. Getting certified and hired

You now have the whole profession: the revenue cycle (Lesson 1), coding (Lesson 2), and billing, denials, and compliance (this lesson). Here is how a career switcher turns that into a job.

Get certified. It is the key that opens the door. Employers hire on certification, and it reliably raises pay, per AAPC, certified professionals earn roughly 20 percent more than non-certified peers. The main credentials, from the professional bodies AAPC and AHIMA:

  • CPC (Certified Professional Coder, AAPC): the standard entry credential for coding, tests reading documentation and assigning correct ICD-10, CPT, and HCPCS codes.
  • CPB (Certified Professional Biller, AAPC): focused on billing, claim submission, payer rules, denial management, collections.
  • CCS (Certified Coding Specialist, AHIMA) and others exist for specific settings and specialties.

Pick based on the half you want (coding vs billing), or, common for switchers, learn both to be the versatile biller/coder a small practice needs.

Then make yourself hireable:

  • Train deliberately. A focused program plus exam prep, months of real study. The code sets and rules are a genuine body of knowledge (Lessons 2 and 3), not a weekend skill.
  • Get hands-on practice. Coding practice cases, sample charts, and any externship or entry role build the accuracy employers actually test for.
  • Expect to start at the entry rung. A first coding or billing job, sometimes an apprentice-level or AAPC "apprentice" designation until you have experience, then grow into specialties or denial-focused roles that pay more.
  • Speak the language in interviews. Demonstrate you understand medical necessity, denial types, the clean-claim goal, and compliance, exactly the thinking this cursus taught, because that is what signals a real coder or biller versus someone who took a class.

The honest close: this is a learnable, credentialed, in-demand, often-remote knowledge career for precise, diligent people. The barrier is real study and a certification, not a degree, which is exactly what makes it one of the more achievable switches into a large and stable industry. Master the translation and the collection, prove it with a credential, and the door opens.

7. The claim lifecycle and the denial loop

Charges are scrubbed and submitted through a clearinghouse to the payer, which adjudicates and returns a remittance; clean claims are posted and the patient billed, while denials are diagnosed by reason, corrected or appealed before the deadline, and their patterns fed back into scrubbing.

flowchart TD
  A["Charge entry from codes"] --> B["Scrub for errors"]
  B --> C["Submit via clearinghouse"]
  C --> D["Payer adjudicates"]
  D -->|Paid| E["Post payment; bill patient share"]
  D -->|Denied| F["Read remittance; diagnose reason"]
  F --> G["Correct and resubmit or appeal"]
  G --> C
  F --> H["Feed pattern back into scrubbing"]
  H --> B

Check your understanding

The lesson ends with a 5-question quiz. Take it in the player above to see your score.

  1. What is a clearinghouse's role in the claim lifecycle?
    • It is the bank that holds the provider's money
    • An intermediary that formats, validates, and routes claims from provider to the correct payer and returns status, like a postal service and quality check between them
    • The government agency that sets all codes
    • The software that treats patients
  2. Why is denial management described as where a biller 'earns their keep'?
    • Because denials are rare and easily ignored
    • Because denials are routine (often mid-teens percent of claims) and about 63% of denied claims are never reworked, forfeiting an estimated $25B/year, so a biller who works denials recovers real, otherwise-lost revenue
    • Because denied claims cannot be recovered
    • Because billers are paid per claim submitted
  3. What is the correct first step when working a denial?
    • Immediately write off the claim as lost
    • Resubmit the identical claim and hope
    • Read the remittance (835) to get the denial reason code, then diagnose which bucket it falls into (eligibility, coding, medical necessity, timely filing) since each has a different fix
    • Bill the full amount to the patient
  4. What distinguishes accurate coding from fraud?
    • Fraud is only a problem if the payer notices
    • Coding what is documented, accurately and only that, is the job; upcoding, unbundling, modifier misuse, or billing for services not rendered inflate payment and are fraud under the False Claims Act
    • There is no legal difference
    • Coding higher is fine if the doctor approves it
  5. What is the practical key to getting hired as a biller or coder?
    • A four-year healthcare degree
    • Certification (e.g. CPC for coding, CPB for billing from AAPC), which employers hire on and which reliably raises pay (~20% per AAPC), plus deliberate training and hands-on practice
    • Prior work as a physician
    • Nothing beyond applying online

Related lessons

Programming
intermediate

Integration Engines and the Interoperability Career

The hub that makes healthcare data flow: how an integration engine like Mirth Connect routes, filters, and transforms messages between systems, how it compares to a general dataflow tool like Apache NiFi, the other standards you will meet, and the concrete skills to break into interoperability engineering.

9 steps·~14 min
Programming
intermediate

Healthcare Interoperability and the HL7 v2 Standard

Why hospital systems cannot talk to each other by default, and the standard that fixes it. Covers the four levels of interoperability, the HL7 family, and the anatomy of an HL7 v2 message: segments, fields, and delimiters. The foundation for a career in healthcare integration.

8 steps·~12 min
Business
intermediate

Go-to-Market: Launches, Enablement, and Competing

Positioning and messaging are useless if they never reach the market. This lesson covers how a PMM takes a product out: go-to-market strategy, tiering launches to match effort to impact, arming sales with enablement and battlecards, competitive intelligence and win/loss, measuring PMM impact, and how to break into the role.

8 steps·~12 min
Business
intermediate

What Product Marketing Actually Is

Product marketing is the discipline of bringing a product to market successfully, and it is one of the most misunderstood and highest-leverage roles in tech. This lesson defines it: how a PMM differs from a product manager, why they are the connective tissue between product, sales, and marketing, and why positioning is the foundation of everything.

8 steps·~12 min