“What do we need to buy?” the owner asks, expecting a shopping list. The list is shorter than the sales conversations suggest, and most of it is capability, not product.
Worth separating those two. A practice that knows which capabilities it needs can judge any tool. A practice working from a product list is buying someone else’s assumptions. This sits inside owning your own money path, once you have decided the in-house direction.
Here is the stretch the tools have to cover. A visit becomes a charge, the visit written up as a billable line, and the charge becomes a claim, the bill sent to the insurance company. The insurance company answers with a payment or a denial, a refusal to pay with a reason code. The answer is recorded, and the patient pays their share.
Five capabilities cover that stretch, and you already own most of them.
What software do I need to bill in house?
Less than most vendors will tell you. If you have a practice management system, the software that runs your schedule and billing, you already hold most of it. What you need on top is a way to reach insurers electronically, a way to check a patient’s coverage, a way to take payments, and a way to see what is stuck.
At one practice, the coverage check was built into the system and switched off, and claims denied for months for coverage a single click would have caught.
The capabilities
Building and checking claims. Turning a charge into a claim that passes the automatic checks before it goes out. Almost always already in the practice management system.
Sending claims and getting answers back. A route to insurers and a route back, through a clearinghouse, the middleman service that carries claims to insurers. Enrollment, the paperwork that lets claims move to an insurer electronically, takes weeks whichever one you use.
Checking coverage. Confirming a patient’s insurance is active, ideally before the visit rather than after the denial. Included in the system, and usually unused.
Taking payments. Card capture at the desk and stored cards for balances, set up so a payment lands against the right balance without anyone matching it by hand.
Seeing what is stuck. The capability practices go without, because it is the one nothing ships as a single button.
What you probably already have
This is where practices overspend, and it is worth an hour before any purchasing call. A practice management system already includes building and checking claims, a clearinghouse connection, coverage checking, statement printing, and a reporting layer. When billing was outsourced, those were being used by someone else on your behalf, or set up once and never revisited.
The audit is simple. List the five capabilities above. For each, ask whether the current system does it, whether it is switched on, and whether anybody is using it. Most practices find at least two things they were about to buy.
The capability nothing ships
Seeing what is stuck is the one you have to assemble, and it is the difference between running billing and watching it run. Standard reports read one thing at a time. A note report reads notes, a charge report reads charges, an aging report (the list of unpaid bills by age) reads open balances. Each is accurate about its own subject.
What you need is the comparison between them. Completed appointments against created charges. Signed notes against created charges. Charges posted against claims sent. Payments received against payments recorded. Those comparisons show where work has stopped.
None is a product, and all draw on records the system already keeps, so building them is a setup decision, not a purchase. A practice that brings billing in house without that view has moved the work inside and kept the blindness.
What to be careful about
Buying tools before defining the routine. Software supports a way of working. Bought first, it becomes the way of working, and you end up shaped by a vendor’s assumptions rather than your own.
Adding systems that do not talk to each other. Every extra place data lives is another reconciliation somebody does by hand, and manual reconciliation is where backlogs of unrecorded payments start.
Assuming a feature runs because it exists. The coverage check is the common one. Present in most systems, switched on in fewer, actually used before the visit in fewer still.
Real situations, and what the system already held
At one practice, the coverage check sat inside the practice management system, switched off. Claims denied for months for coverage that a click before the visit would have confirmed. Nobody had bought anything wrong; a feature they already owned was simply never turned on.
At another, the owner was about to buy a separate claim-scrubbing tool. The practice management system already did it, correctly, and had been doing it on the old billing company’s behalf. An hour of audit saved a purchase and a second system to reconcile.
What this means for you
Audit before you buy. Five capabilities, and for each ask whether you have it, whether it is on, and whether anybody uses it. Then build the fifth, the view of what is stuck, because it is the one nothing ships and the one that decides whether you can see what is happening.
Grab 30 minutes with us. Prep nothing. You will see which of the five you already have and which one is missing.
Questions people ask
What software do I need to bill in house?
Less than most vendors suggest. If you have a practice management system you already hold most of it. What you need on top is electronic claim sending, coverage checking, payment acceptance, and a view of what is stuck.
What do practices already have without realizing?
Building and checking claims, a clearinghouse connection, coverage checking, and statement printing are included in a practice management system. When billing was outsourced, those were being used by someone else on your behalf.
What capability is hardest to get?
Seeing what is stuck, because it is the only one that is a comparison rather than a feature. Completed appointments against created charges, signed notes against created charges, charges posted against claims sent, payments received against payments recorded.
Should I buy software before or after defining the process?
After. Software supports a way of working, and bought first it becomes the way of working. The result is a routine shaped by a vendor’s assumptions rather than your own.
Why is adding more systems a risk?
Because every extra place data lives is another reconciliation somebody does by hand, and manual reconciliation is where backlogs of unrecorded payments start.