Most claim problems do not start with the payer. They start with a small detail that was missed before the claim left the practice, such as inactive coverage, a mismatched member number, or documentation that does not fully support the service billed. A short pre-submission check gives your team a chance to catch those issues while they are still quick to fix.
Why a pre-submission check matters
A claim that leaves with an error usually comes back as a rejection, a denial, or a request for more information. Each return adds rework for your staff: someone has to find the problem, correct it, resubmit the claim, and then follow up again.
A consistent check will not remove every denial, and no honest billing partner should suggest that it will. What it does is reduce avoidable mistakes, make follow-up easier, and show your team which problems keep repeating.
The best time to fix a claim is before it leaves the practice, while the correction is still small.
What to check before a claim goes out
Use the same order every time, so nothing depends on memory or on who is working that day. Keep the check short enough that staff will actually use it on busy days.
1. Patient details and coverage
Start with the basics, because small mismatches here can stop a claim early. Compare the claim with the details your practice has on file for that visit.
- Patient name and date of birth match the insurance card on file
- Member number is complete and entered exactly as shown
- Coverage was active on the date of service
- The claim is being sent to the correct payer for that coverage
If the patient has more than one coverage, confirm which one applies to the visit before you bill. Sorting out coordination of benefits after a denial typically takes longer than checking it first.
2. Eligibility, authorisation, and referrals
Coverage alone does not always mean a service can be billed without anything else in place. Where a plan requires it, check that the groundwork was done before the visit or before submission.
- Eligibility was verified for the date of service
- Any required authorisation is on file and matches the planned service
- Any required referral is recorded and still valid for the visit
- The details on the claim match the details that were authorised
Requirements vary by payer, plan, and service, so work from the requirements that apply to your practice and your patients. If something is missing, it is usually easier to address it before submission than after a denial.
3. Documentation and coding support
The claim should tell the same story as the clinical record. Before submission, confirm that the documentation in the chart supports what is being billed.
- The note supports the services and the level of service billed
- Diagnoses recorded in the note support the services on the claim
- Units, dates, and places of service on the claim match the encounter
- Any information the payer typically needs is present in the record
This is where medical coding review earns its place. A second look at coding and documentation before submission can catch gaps that are simple to correct in the office and harder to explain later.
4. Provider and claim details
Next, check the details that identify who provided the care and where. These fields are easy to overlook because they often carry over from templates or earlier claims.
- Billing and rendering provider details are correct for the visit
- Provider identifiers on the claim match your practice records
- Facility and service location details match the encounter
- Charges on the claim match the services documented
If your practice has added a provider, changed a location, or updated a system template recently, give these fields extra attention. Template errors tend to repeat quietly until someone spots the pattern.
How to make the check a habit
A checklist only helps if it becomes part of the normal workflow, not an extra task added at the end of the day. Build it into the point where claims are prepared, and keep ownership clear.
Use one checklist for the whole team
Write the check down in one place and use the same version across the practice. When a step changes, update the checklist itself, not just one person's memory.
- Prepare the claim using the checklist above
- Hold any claim that fails a step, and record why it was held
- Fix the issue or escalate it the same day where possible
- Release the claim only when the failed step passes
Keep a simple issue log
Each time the check catches a problem, record the type of issue, where it was caught, and what caused it. You do not need a complex report. A short, consistent log is enough to show patterns over time.
Review the log regularly and group issues by cause, not by person. If the same problem appears again and again, fix the source, such as intake forms, eligibility steps, templates, or documentation habits. That is the heart of denial prevention: fewer repeat errors, not just faster appeals.
Next step
Start with your next batch of claims and run this check for one full week, noting every issue it catches. At the end of the week, you will have a clear, honest picture of where your revenue cycle is losing time, and which fix should come first.
If you would like a second pair of eyes on that picture, contact T Zync to talk through your medical billing and revenue cycle workflow.