About Us
iRCM is an industry leader with innovative technology and an expert team. We are a complete Revenue Cycle Management solution that streamlines reimbursements and delivers remarkable results.
Contact Info
iRCM is an industry leader with innovative technology and an expert team. We are a complete Revenue Cycle Management solution that streamlines reimbursements and delivers remarkable results.
Running a lab test is the easy part to picture. What happens afterward turning that test into an actual payment is where most of the real work sits, and it’s a process most patients (and even a few providers) never see.
What is lab billing, exactly? It’s the chain of steps a laboratory follows to get reimbursed for a service: confirming who’s covering the cost, checking that the test qualifies for payment, coding it correctly, sending the claim out, chasing down anything that gets denied, and reconciling what actually comes back.
None of that is guaranteed just because the test itself went smoothly. A perfectly performed, clinically justified test can still sit unpaid for months over a coding slip, a missing form, an authorization nobody requested, or a claim that never got followed up on.
From the moment a test is ordered to the moment the account is closed out, laboratory billing generally follows the same core sequence.
The cycle begins with a physician’s order. Before anything else happens, the lab has to make sure that order actually has what’s needed — who ordered it, who the patient is, what diagnosis or clinical reason justifies the test, and whatever supporting paperwork the payer will want later.
A thin or unclear order rarely causes an issue right away. The fallout usually shows up further downstream, once coding, submission, or a medical-necessity review is already underway.
Before a claim can go anywhere, the lab has to lock down the patient’s demographic and insurance information, which typically covers:
When specimens arrive from an outside referring office, it’s worth being explicit about who is responsible for supplying this information; that gap between two parties is one of the more common places a claim quietly falls apart. Checking eligibility before the test is billed, rather than discovering a lapse afterward, is one of the simplest ways to head off a denial while there’s still time to act.
A test can make complete clinical sense and still not satisfy what a specific payer requires for payment. Medicare, for instance, ties laboratory coverage to National Coverage Determinations (NCDs) and Local Coverage Determinations (LCDs) — policies that define which diagnoses justify a test, and sometimes cap how often it can be billed.
Overlooking this step is a fast track to a medical-necessity denial after the fact, and unwinding that kind of denial takes far more effort than checking coverage rules would have taken up front.
Once testing wraps up, the billing team attaches the CPT or HCPCS code that reflects the actual service, along with a diagnosis code that supports why the test was ordered in the first place.
Precision matters here more than almost anywhere else in the cycle. A code that doesn’t line up with the service performed, a modifier that’s missing, or a diagnosis mismatch against payer edits can bounce the claim before anyone even looks at it manually.
With coding locked in and an internal check completed, the claim goes out electronically, carrying the patient, provider, lab, diagnosis, and procedure information the payer needs to adjudicate it.
This is essentially where medical claim processing happens: the point where a verified, coded encounter becomes an actual claim ready for a payer to act on. It’s also where iRCM’s team focuses a lot of attention, since catching a mismatched ID, an invalid code, or a missing field here prevents a rejection that would otherwise cost days or weeks later.
Sending the claim isn’t where the job ends. It needs to be watched to be accepted, adjudicated, and eventually paid, with any rejection corrected and resent quickly rather than left sitting.
Anything that stalls should land in a defined follow-up process instead of getting forgotten. Labs that skip this step tend to watch their A/R quietly age past the point where it’s easy to collect.
Once a payer responds, the billing team posts the payment and checks it against what was expected, looking for:
Posting payments carefully is what keeps a lab’s A/R picture honest, and it’s often the first place an underpayment gets noticed at all.
Every denial deserves a real look at why it happened; eligibility, medical necessity, a coding slip, a missing authorization, thin documentation, or a duplicate claim are the usual suspects.
Simply resending a denied claim without diagnosing the cause tends to produce a second denial. It’s more productive to pin down what actually went wrong and decide from there whether the claim needs a correction, an appeal, or a write-off.
The Clinical Laboratory Fee Schedule (CLFS) sets Medicare’s payment rates for most clinical diagnostic laboratory tests. Rates are built from a weighted median of private payer pricing and refreshed on a multi-year reporting cycle rather than annually.
As of 2026, CMS has confirmed there’s no phase-in payment cut this year. Between 2027 and 2029, though, annual reductions for affected tests are capped at 15% relative to the previous year’s payment amount.
One point worth remembering: appearing on the CLFS, or having a listed payment amount, doesn’t guarantee Medicare will actually pay for that test in a given case. Coverage still comes down to medical necessity and the relevant NCD or LCD; the fee schedule only tells you the rate if the claim is approved.
The Clinical Laboratory Improvement Amendments (CLIA) establish federal quality benchmarks for any lab testing done on human specimens, with CMS responsible for making sure results stay accurate, dependable, and timely.
Labs need the CLIA certification level that matches the complexity of what they test, and CMS won’t process Medicare or Medicaid payments without that certification being current. Put plainly, CLIA compliance isn’t a side issue; it’s a condition of getting paid in the first place.
It’s worth handling CLIA status the same way a billing team handles payer credentialing: something to actively confirm is current and accurately on file, not something to assume is fine until a claim gets rejected.
Getting paid for lab work involves a lot more moving parts than reporting a test code, which is exactly why so many claims run into trouble. The recurring issues include:
The best time to deal with a denial is before it happens, not after the claim comes back rejected. Claim scrubbing, running a claim against payer-specific rules and formatting checks before it’s ever sent, catches a meaningful share of these problems in advance. iRCM breaks this down further in Claim Scrubbing in Medical Billing, which explains how scrubbing flags errors that would otherwise become denials.
Billing Area | What Gets Checked |
Patient details | Name, date of birth, member ID, demographics |
Insurance | Coverage is active, and payer is correct |
Order | Provider and test information is complete |
Medical necessity | Diagnosis supports the applicable coverage policy |
Coding | CPT or HCPCS code matches the service |
Authorization | Approval on file where it’s required |
CLIA | Certification current and correctly documented |
Documentation | Records available to back up the billed service |
Claim | Fully complete and accurate before it’s sent |
Payment | Reimbursement and adjustments posted correctly |
Tracking why claims get denied is just as important as fixing them one at a time. A repeat issue points to a broken workflow, not bad luck, and it’s worth solving at the root instead of resubmitting the same problem over and over.
An Advance Beneficiary Notice of Noncoverage (ABN) is a Medicare form given to a patient when a provider or an independent lab has reason to think Medicare won’t pay for a particular service. Independent laboratories are allowed to issue this notice themselves. Doing so warns the patient in advance that Medicare might deny the claim and, where applicable, shifts the financial responsibility onto the patient if that denial happens.
For a lab, this usually comes up when a test looks unlikely to meet Medicare’s coverage or medical-necessity standard for the diagnosis on file, giving the patient a heads-up before the bill arrives, rather than after.
There’s no single trick that fixes lab billing — it comes down to repeating the right steps consistently, every time a claim moves through the cycle.
Lab billing sits at one of the more fragile points of a laboratory’s finances, mostly because a well-performed test still doesn’t guarantee a payment shows up. Cash flow gets held up by claim data that’s wrong, denials tied to medical necessity, coding errors, or claims that get submitted and then never followed up on. All of that is avoidable, but only if there’s a process actually designed to catch it.
A healthy laboratory revenue cycle treats order intake, coding, claim submission, denial handling, payment posting, and A/R follow-up as one connected system rather than isolated tasks. That connection is what allows a recurring problem to get caught early and fixed at its source, instead of repeating on the next claim and the one after that.
Outsourcing isn’t necessary for every lab, but it becomes worth a serious look once claim volume, coding complexity, denials, or A/R follow-up start outgrowing what an internal team can realistically keep up with.
A few things are worth confirming directly before signing on with a laboratory billing service provider:
A good billing partner does more than take billing tasks off your plate. It should be able to point out what’s actually causing recurring problems and help fix the workflow behind them, not just process whatever claims come through.
Lab billing turns a completed laboratory service into a claim that’s coded correctly, submitted on time, tracked through to resolution, and ultimately paid, and that involves a lot more than picking the right CPT or HCPCS code.
Verifying patient and insurance details, confirming medical necessity, coding accurately, staying CLIA-compliant, submitting claims promptly, managing denials with discipline, and posting payments carefully all have to work in sync for a claim to get paid without a fight. If your lab’s billing process feels stretched thin, or the same denials keep showing up month after month, iRCM can help you find where things need to tighten up.Â
Lab billing is the process of coding, submitting, tracking, and collecting payment for laboratory services delivered to patients.
It’s the Medicare payment schedule that covers most clinical diagnostic lab tests. Being listed on it doesn’t automatically mean Medicare will cover a specific claim.
CLIA refers to the Clinical Laboratory Improvement Amendments, which set federal quality standards for testing on human specimens. Labs generally need current CLIA certification to receive Medicare or Medicaid payment.
Typical causes include eligibility problems, coding errors, incomplete documentation, medical necessity gaps, missing prior authorization, frequency limits, or other payer-specific requirements.
An ABN is a Medicare notice used when a provider, including an independent lab, expects a service might not be covered. It informs the patient they may be responsible for the cost if Medicare denies the claim.
Verifying patient and payer details upfront, confirming medical necessity and coverage, coding accurately, securing required authorizations, scrubbing claims before submission, and tracking denial patterns over time.
It typically handles claim submission, coding support, denial resolution, payment posting, A/R management, reconciliation, and ongoing revenue cycle reporting on the lab’s behalf.
iRCM is an industry leader with innovative technology and an expert team. We are a complete Revenue Cycle Management solution that streamlines reimbursements and delivers remarkable results.
