Batch vs real-time eligibility verification: which to use
Use a real-time check when a patient is at the desk or on the phone and you need an answer now. Use a batch check to verify a whole day’s schedule, or a larger group of patients, ahead of time. Most clinics do best with both: a batch run before the visit to catch problems early, then a real-time check at arrival to catch late changes. This guide explains how each one works and what the industry rules set for speed.
What is the difference between real-time and batch?
Both send the same 270 eligibility inquiry and get the same 271 answer back. (Our guide to 270/271 transactions covers the format.) The difference is how you send it and how long you wait.
- Real-time: you send one inquiry and stay connected until the answer arrives. CMS describes its Medicare system this way: in real-time mode, the trading partner “transmits a 270 request and remains connected while the receiver processes the transaction and returns a 271 response.”
- Batch: you send a file with many inquiries, then pick up the file of answers later. You do not wait on the line.
A clearinghouse or practice management system usually hides this from your staff. You may see it as a button for “check now” and a setting for “verify tomorrow’s appointments.”
How fast is a real-time check?
The CAQH CORE Eligibility & Benefits Infrastructure Rule (version EB.2.0, April 2022) sets the maximum response time for a real-time 270 at 20 seconds or less. A 999 error response must come back in the same time under that text. The rule says conformance means 90 percent of required responses arrive within that limit, measured over a calendar month.
That 90 percent figure matters. It is a target measured over a month, not a promise for every check, so some checks will be slower. Federal rules, adopted in 2011 (45 CFR 162.1203) adopt earlier versions of the CAQH CORE response-time rules (version 1.1.0, March 2011) for HIPAA health plans. The figures in this post come from the newer EB.2.0 text, so ask your clearinghouse what your payers actually follow.
Conformance is 90 percent of required responses within a calendar month.
Source caqh.org
How fast is a batch check?
The same CAQH CORE rule has a batch section. A 270 batch submitted by 9:00 pm Eastern time on a business day must get its 271 responses back by 7:00 am Eastern time the following business day. Each health plan or its agent defines which days count as business days. The rule also says a 999 acknowledgement must be available within one hour of receiving the batch. Again, conformance is measured as 90 percent of required responses within a calendar month.
- 9 pm, business daySubmit a 270 batch by this time (Eastern) for next-morning return
- Within 1 hour999 acknowledgement available after receipt
- 7 am, next business day271 batch due back (Eastern)
From the CAQH CORE EB.2.0 text. Your clearinghouse may be faster, or may add its own steps.
Source caqh.org
This is why batch fits overnight work. A clinic that sends tomorrow’s schedule by 9:00 pm Eastern on a business day can expect answers by 7:00 am Eastern the next business day, if the plan meets the rule. It does not fit a patient standing at the window.
Plans can also have planned downtime. The same rule requires system availability of at least 90 percent per calendar week for both modes, which leaves room for regular maintenance. A batch sent during a maintenance window may come back late.
When should a clinic use real-time checks?
Real-time is the better choice when someone is waiting or the answer changes what you do next:
- A patient is checking in and the card looks new.
- A walk-in or same-day patient is added to the schedule.
- A batch result came back rejected and you fixed the member ID or date of birth. (See our guide to 271 AAA error codes.)
- You are booking a high-cost service and want to confirm coverage before the patient leaves.
A 2025 Stedi guide also names real-time checks as the default for a patient at the front desk and for pre-visit verification. Stedi is a vendor, so treat its advice as one view.
When should a clinic use batch checks?
Batch is better when you can plan ahead and volume is the problem:
- Verifying the next day’s appointments every evening.
- Refreshing coverage for all patients with visits this week or this month.
- Checking a long list of patients after a plan year change, when many ID cards change at once.
The same guide says software teams using its API usually start adding batch once they run “several thousands” of time-insensitive checks at once. A small clinic may never reach that scale, but the idea still works: a list of 30 patients for tomorrow is easier to run as one job than as 30 phone calls or portal visits. Check your own system, though, because it may offer only one mode, or it may call a scheduled run of real-time checks a “batch.”
Why use both?
A check is a snapshot. CMS says in its Medicare guide (2022) that the data in a 271 is “true and accurate only at the particular time of the transaction,” and that a response is not a guarantee of payment. Coverage can end, change or be corrected between the night before and the morning of the visit.
A simple routine that uses both:
- Evening before: run a batch for tomorrow’s schedule.
- Next morning: sort the results. Fix rejections, and call the patient about any inactive coverage before they arrive.
- At arrival: run one real-time check for patients whose coverage is new, flagged, or unusual.
- Record it: save the date, time, payer and result, as in our insurance verification checklist.
This is a suggested routine, not a rule. Adjust it to your payers and your volume.
What should you ask your vendor?
Before you rely on either mode, ask your clearinghouse or software vendor:
- Which payers support real-time checks, and which are batch only?
- What is the actual typical response time for each payer, not the maximum?
- How are rejections shown to staff, and can they be rerun in one click?
- How do you handle a payer that is down?
- What does each check cost, and does cost differ between modes?
Payers can add their own limits in their companion guides, so read the guide for your largest payers.
Where Clinicrung fits
Clinicrung is being built to run routine eligibility checks ahead of visits and flag the ones that come back rejected or inactive, so a person can follow up. It is not built yet, and early access is delivered in small groups, partly by hand. Start your free trial.
This post is general information about eligibility transactions, not legal, billing or compliance advice. Payer rules and software vary, so check each payer’s current guide and ask a qualified professional about your situation.