How to bring a private practice's billing up to date with AI

TLDR: A private practice keeps two sets of books whether it means to or not: the claims side that lives in the practice management system, and the business side that lives in a ledger like Xero or QuickBooks Online, with Dext feeding it the expense paperwork. Most of the money a practice loses goes missing in the seam between them, so the fix is not a better tool, it is a scheduled pass over what came back.

Why Thursday evening disappears

The last patient left at seven. On the front desk there is a stack of encounter slips from Tuesday that never got entered, a remittance that landed on Monday with three lines paid at less than expected and one line denied outright, and a patient on the voicemail asking why she got a bill for a visit her insurance was supposed to cover. None of that is medicine. All of it is Thursday evening.

The part software takes away is the retyping and the matching. The part it does not take away is the deciding, and in a practice the deciding starts earlier than most people think. By the time a denial is four weeks old, the appeal is harder, the patient has forgotten the visit, and whoever coded it has seen two hundred patients since.

What separates the practices that keep this under control from the ones that lose evening after evening is almost never the product. It is whether the work happens on a schedule or whenever someone finally has time.

The route, and who answers for each leg

The colour is worth reading. The leg in the middle belongs to somebody else entirely, and no amount of automation on your side shortens it. The leg that genuinely automates is the return trip, where deposits and remittances land and get matched. The first and last legs look clerical and are not, because a wrong code and an unappealed denial both cost real money and both need a person. When a vendor sells automated billing, the honest ones mean the third leg.

Keep the claims system and the ledger apart

This is the distinction that decides whether the rest works. Your practice management system or EHR knows the patient, produces the claim and sends it to the payer, usually through a clearinghouse. Your ledger knows the money: what came in, what went out, what is owed and what the business earned. They are different jobs and they need different software.

Xero starts at $25 a month and suits a practice that wants strong bank reconciliation and an easy handoff to whoever does the books. QuickBooks Online starts at $85 a month and earns its price when the practice already sits inside the wider US ecosystem of payroll and payment tools. Neither one is a billing system for claims, and buying one expecting it to be is the most common wasted subscription in this vertical.

The two connect at exactly one point: the deposit. When a payer pays, the money arrives in the bank, the ledger sees it, and the remittance explains which claims it covered. Get that seam right and the rest of the month is quiet.

Capture the charge at the desk

The single habit with the best return is entering the charge while the patient is still in front of you. Codes chosen from memory on Friday are worse codes, and a visit that never got entered is not a slow payment, it is revenue that does not exist.

The same rule covers the money you collect on the spot. Copays and self-pay balances taken at the desk never become collections work. What is left over, the balance the payer decides weeks later, is the part that needs a system rather than a habit.

Expenses run the same way. Medical supplies, lab, sterilisation, rent, utilities and continuing education all arrive as paper or as email, and Dext starts at $25 a month to read them on arrival and post them without typing. Categorise them once with the practice’s own shape, by clinical supplies, structure, equipment and training, and the profitability analysis later has something to work with.

Work what came back, on a schedule

The order matters. Match deposits before you judge anything, because a line that looks unpaid is often paid inside a batch you have not opened yet. Every hour spent chasing a payment that already arrived is an hour that teaches the team the pass is pointless.

Each payer sets its own window for appealing a denial and its own window for filing in the first place. The deadline that governs you is the one in your contract, not a general rule, so write it on the payer’s card and let the date drive the queue.

The four exceptions that always show up

The denial nobody opened. The remittance comes back with an adjustment or denial reason on a line, and the line sits there because working it is nobody’s named job. This is the expensive one, and it is expensive quietly. The exit is a standing owner and the payer’s own appeal window on the calendar.

The deposit that matches nothing. A payer pays sixteen claims in one transfer, so the bank line will never equal an invoice. People spend hours trying to force a match that cannot exist. The exit is to reconcile the deposit against the remittance batch and let the ledger hold the batch, not the individual claim.

The balance the patient never expected. Patient responsibility is decided during adjudication, which happens after the visit, so the bill arrives when the appointment is a memory. The exit is two sentences at the desk warning that a balance may follow, and then sending it within days. A statement that arrives six weeks later gets a phone call instead of a payment.

The credit balance hiding in the total. A secondary payer pays after the primary, or a patient prepaid an estimate that came in high. The account now owes money outward while the receivables total still reads as money owed to you. The exit is a monthly look at credit balances specifically, because no aging report surfaces them on its own.

What to count to know it is working

Pick your starting numbers before you change any software, and count them again after one full cycle. Three are enough.

Count the days between a visit and its claim going out, for one ordinary week. Count the denied or short-paid lines still untouched on the last day of the month. Count the dollars in patient balances older than sixty days. Those three move together, and they move because of the schedule rather than the subscription, which is exactly why they are the ones to watch.

Add a fourth if you are choosing between products: the number of manual corrections you make to what the system proposed. A tool that saves an hour of entry and costs an hour of fixing has saved nothing.

The approval boundary

Software can read a supply invoice, propose a category, match a deposit to a batch and draft a plain-English explanation of a balance for a patient. It should not decide what code goes on a claim, and it should not decide to write a balance off.

Coding is a professional judgment with real exposure behind it, and the person who makes it has to be able to defend it. Write-offs are a business decision with a dollar figure attached. Both belong to a named human, and the useful thing automation does is put the right information in front of that human faster.

For anything the software touched, keep the original document, what the system proposed, the correction if there was one, and who approved it. A later review then costs an afternoon of reading instead of a reconstruction from memory.

The month itself closes the way any small business closes, and that routine is in month-end close with the mechanics in bank reconciliation. What comes out the other end feeds the practice’s management reports, and the patient balances that outlive friendly reminders belong in collections. If your bookkeeper is the one who really closes, see working with an accountant. The rest of the back office lives in AI for health and wellness.

Frequently asked questions

Doesn’t my practice management system already do all this?

It does the claims half, often well. What it usually does not do is the business half: expense capture, bank reconciliation, the profit and loss your accountant needs, and the view of the practice as a company rather than as a stream of encounters. The common setup is a clinical or practice management system for claims plus a ledger for the books, connected at the deposit.

Do I have to file claims electronically?

For healthcare claims the rules are specific rather than general. Under HIPAA, a covered entity conducting a covered transaction electronically with another covered entity has to conduct it as a standard transaction, and for claims the adopted standards are ASC X12N and, for retail pharmacy, NCPDP. Medicare goes further: an initial claim may be paid only if submitted electronically. That one carries a waiver for a small provider or supplier, defined in the statute as a provider of services with fewer than 25 full-time equivalent employees, or a physician, practitioner, facility or supplier with fewer than 10, which is where most private practices sit. Dental claims have their own separate waiver. Confirm your own case with whoever files for you rather than assuming it in either direction.

Should I let AI pick the codes?

No, and treat the offer as a warning sign. Suggestion is fine and can be genuinely useful, especially for catching an obvious omission. Selection is a professional judgment that has to be defensible by the person who made it, and no product release moves that boundary.

Is this worth it for a solo practice?

The ledger and the expense capture pay for themselves quickly at almost any size, because the alternative is a shoebox and an accountant’s hourly rate. The weekly billing pass is the part that scales with payer mix, not with patient volume. A cash-only practice with no insurance claims can skip the payer half of this entirely and still keep the ledger side.

What if my biller refuses to change anything?

Common, and forcing it is usually the wrong fight. Ask two questions instead: what format they want the charges in, and what they need from you to appeal a denial faster. If the answers arrive without friction, the existing arrangement is probably fine and the ledger side is where your effort should go. If nobody can say who owns a denied line, that is the problem to fix, and it is not a software problem.