A patient walks into an urgent care clinic and hands over an insurance card the front desk has never seen before. Across town, at 11 p.m., a billing office in a forty-provider group is folding the day’s encounters into a single file addressed to its clearinghouse. Both moments involve medical billing. Neither happens the same way. The real-time vs batch medical billing question is really a question about timing: does a transaction move the instant it’s triggered, or does it wait to travel with a group of others on a fixed schedule? For health care providers, and for students working through a medical billing and coding curriculum, that distinction shapes cash flow, staffing, error correction, and how quickly a claim actually gets paid. This article walks through both models, where each one is required or optional, and what the underlying data shows about which fits a given task.
What is batch processing in medical billing?
A batch, in medical billing, is a defined group of claims, eligibility requests, or remittance files assembled and transmitted together as one unit instead of one at a time. Batch processing insurance transactions, or batching insurance claims, means collecting these items over a set window, usually a business day, and sending them in a single submission to a clearinghouse or directly to a payer. Ask a biller what is a batch, and the answer usually points to a screen inside the practice management software: batch claims appear there as a running list created that day, tagged with a batch number, waiting to be scrubbed and released together.
Batch billing exists for a practical reason. Transmitting one claim at a time, hundreds of times a day, multiplies connection overhead and the odds of a dropped transaction. Grouping claims into a batch lets the practice management software apply the same pre-submission edits to every claim at once and hand the clearinghouse one organized package instead of a stream of one-off files. Batching isn’t limited to claims. Remittance advice, the payer’s report of what it paid and why, is typically batched too: AAPC’s billing guidance explains that remittance files are organized by date of service because a single batch remittance advice often includes payment information for multiple patients.
Describe the components of a daily batch within the PMS
A daily batch inside a practice management system is a structured record, not just a folder of claims. Most systems build it from the same core pieces:
- Batch header: a unique batch number, the date and time it was created, the billing provider’s NPI, and the staff member who generated it.
- Claim count and total charges: a running tally of how many claims are included and the combined dollar amount billed, used later to reconcile against what the clearinghouse and payer confirm.
- Individual claim records: each claim carries its own patient, payer, date of service, and procedure and diagnosis codes, formatted as an 837P, 837I, or 837D transaction depending on whether it’s professional, institutional, or dental.
- Pre-submission edits: often called scrubbing, this step checks every claim against X12 syntax rules and payer-specific requirements before transmission, catching a missing NPI, an invalid code, or a formatting error before it becomes a rejection.
- Submission log and acknowledgment trail: once transmitted, the batch generates a 999 confirming the file itself was valid X12, followed by a 277CA confirming which individual claims were accepted into the payer’s adjudication system and which were rejected before ever reaching it.
The difference between the 999 and the 277CA trips up a lot of billing students. The 999 is a file-level receipt, the 277CA is a claim-level receipt, and neither one confirms payment. That confirmation, itemized claim by claim, arrives later in an 835 remittance file, which is itself usually organized and posted in its own batch.
What is real-time medical billing?
Real-time medical billing flips the batch model. A transaction is submitted and answered within the same short window, often while the patient is still at the front desk. The term real time billing gets applied loosely, though, so it helps to separate two things that often get bundled together: real-time transmission and real-time adjudication.
Real-time transmission means a single eligibility check, claim-status inquiry, or occasionally a claim itself, is sent and acknowledged in seconds rather than folded into an overnight run. CAQH’s Phase IV Operating Rule Set treats claim submission this way as its own processing mode, labeled real time processing without adjudication: the payer confirms receipt quickly but doesn’t necessarily decide, on the spot, how much it will pay.
Real-time adjudication (RTCA) goes further and returns an actual payment decision, not just a receipt. It exists, but only a subset of medical and dental payers support it. A supported dental claim, for instance, can return within seconds showing the copay, any frequency limits already used that year, and the patient’s final balance, according to healthcare RCM glossary publisher Ventus AI. The model isn’t new. RealMed Corporation, an Indianapolis company, was adjudicating outpatient medical claims this way as early as 2000, according to a history of claims technology published by Infosys BPM. Even now, most of what gets called real-time medical billing in daily practice means fast transmission and acknowledgment, not an instant payment decision.
What are the main differences between real-time and batch insurance eligibility verification services?
Eligibility verification is where the real-time vs batch choice shows up most in a typical day, since eligibility checks (the X12 270 inquiry and 271 response) are routinely run both ways. CAQH’s Committee on Operating Rules for Information Exchange, known as CORE, sets the timing standard for both modes.
In real-time mode, a 270 inquiry must get back a 271 response, or a 999 error notice, within 20 seconds. This is a certification requirement under the CAQH CORE Eligibility & Benefits Infrastructure Rule, not a casual guideline, and compliant health plans and clearinghouses must log timestamps to prove they meet it.
Batch mode runs on a different clock. Under the same rule set, an eligibility batch received by a health plan at or before 9:00 p.m. Eastern must get a response back by 7:00 a.m. Eastern the following business day. A front desk running a real-time check finds out before the patient sits down. A billing office running an overnight batch against tomorrow’s full schedule finds out the next morning, before the first patient arrives.
That gap drives how practices actually use each mode: real-time checks for walk-ins and same-day additions, batch checks for verifying an entire day’s or week’s schedule at once without tying up staff on one-by-one lookups. Adoption of the electronic version of this transaction, in either mode, is already high. The 2024 CAQH Index found that 96% of medical eligibility transactions and 82% of dental transactions were fully electronic in 2023, and eligibility checks remain the single highest-volume administrative transaction in medicine, accounting for 54% of all administrative transactions tracked in the 2023 CAQH Index.
What types of insurance eligibility verification services are available for medical practices?
Practices generally draw on four channels, and most use more than one.
- Payer web portals: each insurer’s own site, checked one patient at a time. Usually free to use, but staff need a separate login for every payer and there’s no batching.
- Clearinghouse-integrated eligibility feeds: built into the practice management software, these route 270/271 transactions, real time, batch, or both, through one connection to many payers. Vendors in this space include Availity, Waystar, Experian Health, and TriZetto Provider Solutions, each combining some mix of eligibility checking with claims submission and remittance processing.
- Dedicated eligibility verification vendors: smaller, API-first companies specializing in eligibility alone, usually priced per transaction. Eligibility vendor pVerify, for example, publishes per-transaction pricing as low as $0.25, well below the cost of a manual, phone-based check.
- Interactive voice response and live phone verification: still necessary for coordination-of-benefits questions, out-of-network exceptions, and plans that don’t return complete data electronically. It’s also the slowest, most labor-intensive option, and the CAQH Index has repeatedly flagged manual verification as the highest-cost category per transaction.
Real-time vs batch medical billing: how claims processing options compare for speed and accuracy
Speed and accuracy pull in different directions depending on where in the process a transaction sits.
Factor | Real-time processing | Batch processing |
Typical transaction | Eligibility inquiry (270/271), claim status (276/277) | Claim submission (837), remittance (835) |
Standard response window | 20 seconds or less (CAQH CORE rule) | Next business day by 7 a.m. Eastern for eligibility; 14 to 29 days for Medicare claim payment |
Where errors surface | At the point of service, before the patient leaves | During clearinghouse scrubbing (hours) or payer adjudication (days to weeks) |
Best suited for | Walk-ins, same-day changes, urgent coverage questions | Full-day patient rosters, high-volume claim submission, routine remittance posting |
On accuracy, the industry benchmark for a clean claim rate, a claim accepted without edits on first submission, sits between 90% and 95%, with high-performing billing operations reaching the upper end. Denial rates tell a messier story. SSI Group, citing a Premier Inc. report from February 2025, puts the industry average claim denial rate at 5% to 10%. Other 2024 industry data put the initial denial rate closer to 11.8%, up from roughly 10.2% in 2020, and Experian Health’s 2025 State of Claims survey found that 41% of providers now report denial rates of 10% or higher, a share that has grown every year since the survey began in 2022.
Real-time transactions don’t eliminate denials, but they change which ones happen. A real-time eligibility check catches a lapsed policy or a wrong member ID before the claim is even built, preventing a coverage denial rather than fixing it afterward. Where real-time claim adjudication is supported, the effect on cash flow shows up directly in two numbers: healthcare RCM vendor Ventus AI reports point-of-service collections rising 20% to 40%, with accounts receivable days dropping by 5 to 10, at payers that support the feature. Batch processing catches its errors later and in bulk, through clearinghouse scrubbing and the 999/277CA cycle described earlier, which handles volume efficiently but surfaces a single claim’s problem more slowly.
How do medical claims management services differ by turnaround time?
Once a claim leaves the practice, turnaround time is set less by submission mode and more by the payer’s own adjudication clock, and for Medicare that clock is written into federal regulation. The Administrative Simplification Compliance Act of 2001 (Public Law 107-105) already requires most initial Medicare claims to be submitted electronically. The main exception covers physicians, practitioners, and suppliers with fewer than 10 full-time equivalent employees, who may still file on paper.
Once submitted, the Medicare Claims Processing Manual sets a payment floor: an electronic clean claim, one needing no further investigation, can’t be paid before 14 days from receipt, while a paper clean claim waits 29 days. Medicare owes interest on any clean claim not paid within 30 days, electronic or paper. That gap between 14 and 29 days is the clearest evidence that submitting electronically, in real time or batch, still beats paper, even though neither format gets a full medical claim adjudicated instantly. Full adjudication almost always takes days regardless of transmission speed, since it checks eligibility, medical necessity, coding edits, and contract terms that a 20-second round trip cannot resolve.
Where claims management services genuinely differ is in what they layer on top of that baseline. Some vendors submit strictly on a batch schedule and leave status checks to the practice. Others submit in batch but poll claim status automatically and near-instantly, surfacing a rejection or a pending review within hours instead of waiting for the next scheduled run. That hybrid, batch submission paired with automated real-time status checks, is common enough among clearinghouses that it’s worth asking about by name when comparing vendors, rather than assuming real time and batch describe two separate service tiers.
What happens when a clearinghouse goes down
Both real-time and batch workflows depend on the same layer of infrastructure: the clearinghouse sitting between the practice management system and the payer. The February 2024 cyberattack on Change Healthcare showed what happens when that layer fails.
Change Healthcare, a UnitedHealth Group subsidiary since 2022, disclosed on February 21, 2024, that a threat actor had accessed its systems, and the company disconnected its own platforms to contain the incident. The scale of the disruption traced back to how much of the country’s claims volume ran through one company: a 2022 Justice Department lawsuit had already cited UnitedHealth’s own figures showing that roughly half of all U.S. medical claims passed through Change Healthcare’s clearinghouse.
A survey by the Healthcare Financial Management Association found that among providers for whom Change Healthcare was the primary clearinghouse, 64% shifted claims submission to a payer web portal and 62% reverted to paper claims as workarounds, while 86% reported cash-flow strain during the outage. By late March 2024, more than a month after the attack, the company reported that over $14 billion in claims had been queued for processing as its systems came back online.
Both real-time and batch transactions ran through the same disrupted pipeline during the outage, so the safer processing mode wasn’t the deciding factor in who recovered fastest. What mattered was whether a practice already knew which alternate clearinghouse or payer portal it could fall back on, and whether that fallback had actually been tested rather than left theoretical.
Choosing between real-time and batch workflows
Neither model replaces the other. Most practices run both, and the right split depends on a few concrete factors.
Patient flow matters first. A practice built around scheduled visits, booked days or weeks out, can rely on an overnight batch eligibility run and know coverage status before the office opens. A walk-in urgent care clinic can’t wait for an overnight batch; real-time eligibility at check-in is close to mandatory there, since there’s often no advance schedule to batch against in the first place.
Staffing and volume matter next. A solo practitioner’s office generates a handful of claims a day, so batching changes little. A multi-provider group generating hundreds of daily encounters gains real efficiency from batch claim submission, since transmitting each claim individually would add administrative overhead without adding accuracy.
Payer mix plays a role too. Not every payer supports real-time claim adjudication, and coverage of the feature varies by specialty and by plan. A practice whose payer mix leans toward plans that support real-time eligibility and status checking gets more value from that connectivity than one whose payers mostly still require batch or manual verification.
Cost is the final factor, and it’s where the CAQH figures already mentioned become directly useful. A manual transaction, a phone call to verify benefits, for instance, runs several times higher in staff time than an electronic one, batch or real time. That’s why the financial case for moving off manual verification altogether is usually stronger than the case for choosing real time over batch specifically.
Real-time vs batch medical billing, once both sides are understood correctly, plays out as dozens of small decisions made every day rather than one policy set once: run this eligibility check now or let it ride in tonight’s batch, submit this claim the moment it’s coded or hold it for the evening file. The CORE rules that set a 20-second ceiling on real-time eligibility and a 9 p.m. to 7 a.m. window on batch eligibility, and the CMS payment floor that pays electronic claims two weeks faster than paper ones, exist because transaction timing carries real financial consequences for the people submitting them. Getting that split right, transaction by transaction, is what separates a billing operation that gets paid on schedule from one that’s always catching up.