The reconciliation is only as good as the deposits underneath it
A practice manager's weekly income update looks, from the owner's side of the table, like a single confident number. From the billing team's side, it is the end of a routine that started days earlier — remittances requested, downloaded, opened, and read one payer at a time, across however many contracts the clinic holds.
Where that routine breaks down is rarely the analysis. Totalling collections and spotting a slow payer is fast once the numbers exist in one place. The slow, error-prone part is getting them into that one place at all — a dozen remittances in a dozen formats, from a dozen payers, gathered by whoever on the team had an hour free that week.
Where clinics actually lose time
None of these five is a single dramatic failure — each one is a small, recurring drag that a practice manager tolerates because no individual week is bad enough to justify fixing it. Added up across a year, they are usually the largest line item in what the reconciliation routine actually costs, well ahead of anything the analysis itself takes.
Retyping claim lines from PDF remittances
The single largest time cost in most routines, and the one least visible to anyone above the team actually doing it.
Chasing a payer's remittance that arrived late
One missing remittance holds up the whole reconciliation, or gets carried forward silently and quietly discovered wrong later.
Reconciling combined payouts covering several remittances
A single deposit from a high-volume payer is easy to mismatch to the wrong batch if it is not explicitly grouped.
Explaining a collections dip that was actually timing lag
A figure that looks like a real shortfall is sometimes just claims still in a payer's normal cycle — and untangling which takes longer than either would alone.
Rebuilding the whole process after someone leaves
Undocumented routines walk out the door with whoever built them, and the next person starts over.
A realistic weekly routine
Request or gather remittances
Every payer, every account, as of the same cutoff — a portal download where one exists, an emailed PDF everywhere else.
Read every claim line
Billed, allowed, adjustment, patient responsibility, paid, and any denial code, from whatever format each remittance arrives in.
Match deposits
Confirm each bank deposit is explained by one or several remittances, catching a missing or misgrouped payment before it reaches the totals.
Flag every denial
Logged with its appeal deadline the same week it happens, so it is never counted as a lost cause before it needed to be.
Total by payer and by provider
Two views of the same underlying numbers, because the practice manager, the owner and a specific provider each read a different one first.
Compare against last week and the trend
The single chart that usually gets the most attention in the actual meeting.
Notice that only step two — reading each claim line — is genuinely mechanical. Steps one, three, four, five and six all involve a decision at some point: which remittance counts as this week's, whether a mismatch is really a misgrouped payout, how a denial should be prioritised. Removing the friction from step two is what frees the practice manager's time for the decisions that actually need a person, rather than for retyping numbers a document already states clearly.
Who owns each step matters more than it first appears, too. In clinics where “whoever has time” gathers the remittances, the routine quietly degrades the first busy week — a payer gets missed, nobody notices until the following week's reconciliation, and a denial ages past its appeal window without anyone flagging it. Naming an owner for steps one through four, even if the same person doesn't do all of them every week, is a small governance decision that keeps the routine from silently eroding.
The cost of doing it by hand, honestly
For a clinic with a dozen payers and a few hundred claims a month, manual gathering and reading commonly runs three to seven hours a week — more in a week where a remittance format changes without warning.
| Approach | Typical time per week | Where it goes wrong |
|---|---|---|
| Fully manual | 3-7 hours | Retyping errors, denials silently aging past appeal |
| Spreadsheet template, manual entry | 2-5 hours | Still relies on someone reading each remittance correctly |
| Document reader plus a template | Under an hour | Requires the payer list and template set up once first |
At a loaded internal cost of £25-35 an hour, the gap between the first and third row is roughly £75-210 a week — £4,000-11,000 a year — for a task that produces exactly the same reconciliation either way. The larger and less predictable cost is what a denial that ages past its appeal window costs when nobody catches it in time.
What changes
Hours back, every week
The mechanical reading work shrinks from hours to minutes, freeing time for the follow-up calls that actually need a person.
A traceable figure
Every claim on the reconciliation links back to the remittance it came from, for when the owner or a payer audit asks where a number came from.
A routine that survives a handover
Documented steps and a fixed template, not tribal knowledge that leaves with whoever built it.
A trend, not just a snapshot
Weekly figures accumulate into a real per-payer history, so a slow payer shows up in weeks, not quarters.
Who does what, once the routine exists
A weekly reconciliation routine works best when it is a chain of clearly separated jobs, not one person doing everything under time pressure. Splitting it up also makes the routine survive someone being on leave or leaving the practice entirely, which a one-person process never does.
| Step | Typically owned by | Judgment required |
|---|---|---|
| Gathering remittances | Billing coordinator or front-office staff | Low — mostly chasing and downloading |
| Reading claim lines | Automated, or a coordinator as fallback | Low — the numbers are stated on the document |
| Flagging denials and mismatches | Billing coordinator, escalated when unclear | Medium — needs context on the payer's normal patterns |
| Reviewing the trend and following up | Practice manager | High — this is the actual judgement the reconciliation exists for |
| Presenting to the owner or partners | Practice manager | High — framing and anticipating questions |
The pattern worth noticing is that the two lowest-judgement rows — gathering and reading — are also the two that consume the most clock time in a manual routine, while the two highest-judgement rows — reviewing and presenting — take the manager's time but relatively little of it. Automating the low-judgement rows does not change who owns the high-judgement ones; it just stops the low-judgement work from eating the hours that should go to the judgement calls instead.
Scenario: the new payer contract
A clinic signs its first contract with a new regional payer mid-quarter. The payer's remittances arrive in a layout nobody on the team recognises, with reference codes the practice management system does not automatically map.
Under a fully manual routine, this is the payer whose claims get set aside “to figure out later” and then quietly stay unreconciled for weeks, because nobody has time to build a special process for one payer on top of the existing workload for every other payer.
A document reader that works from the remittance's structure rather than a payer-specific template treats the new payer the same way as every existing one — read the claim lines, the adjustments, the paid amounts, add the payer to the list, and its remittances are in the reconciliation from the first one that arrives rather than absent until someone builds a special case for it.
Scenario: the multi-provider clinic
A clinic with six providers wants to know not just the total collections for the practice, but which providers' claims are collecting well and which are lagging — information the owner needs before a compensation or scheduling conversation.
Answering that from a blended clinic-wide total is impossible — it shows one figure, not six. What actually answers the question is the same claim-level detail already being read for the reconciliation, simply totalled per provider instead of only per payer.
Because the weekly routine already reads every claim line with its provider attached, that per-provider breakdown already exists by the time anyone asks for it — nobody has to reconstruct six providers' worth of claims from scratch under time pressure before a compensation meeting.
Scenario: the denial nobody caught in time
A payer denies a batch of claims for a documentation issue that, once corrected, would have been easily appealed. Under a monthly reconciliation cadence, the denials sit in a stack of remittances nobody has read closely for three weeks — by the time anyone notices, the appeal window on the earliest claims has already closed.
A weekly routine that reads every claim line the same week the remittance arrives catches this pattern immediately: the same denial code, appearing on several claims from the same payer, in the same week. That repetition is exactly the kind of signal that a quick weekly read surfaces and a monthly one buries under everything else that accumulated in between.
The claims caught in week one get appealed. The claims that would have been caught in week one under a monthly cadence, discovered instead in week four, do not — and that difference, multiplied across a year of similar denial batches, is usually a far larger figure than the time saved by reconciling less often.
What the practice owner actually wants to see
One clear collections total, with the confidence to answer a follow-up question about any part of it.
A trend, not just this week's figure — whether collections are improving, holding steady, or deteriorating.
Payer performance broken out, not blended into one number that hides which payer is actually running behind.
Denials and follow-up status stated plainly, rather than requiring the owner to ask what happened to a specific claim.
None of the four is achievable from a single remittance's summary total, or from a snapshot with no history behind it. All four are what a consistent weekly routine, built from real claim-level data, naturally produces as a side effect of just doing it the same way every week.
| A single snapshot | A weekly trend | |
|---|---|---|
| Shows | Where collections stand today | Where collections have been heading |
| A partner's question | 'Is this typical?' — unanswerable | Answerable directly from the history |
| Owner confidence | One number to take on trust | A pattern the owner can reason about |
Scenario: a clinic that just added a location
A clinic opens a second location, adding new provider NPIs, a new set of payer enrollments still working through credentialing, and a period where some claims from the new site pay under the old location's contracts and some do not, depending on which payer has finished processing the change.
Under a routine that was never designed to separate locations, this transition period is exactly when income figures become hardest to trust — a dip in collections could mean a genuine problem at the new site, or it could simply mean claims are sitting in credentialing limbo, indistinguishable without location-level detail.
Because the weekly routine already reads every claim line individually, adding a location field costs nothing extra to track — each claim carries its site along with its payer and provider, and the reconciliation can show the new location's ramp-up separately from the established site's steady baseline, exactly the view a practice owner actually wants during a period of expansion.
That location-level detail costs nothing to add if the routine already reads every claim individually, and it is precisely what turns a confusing dip into an explained, temporary ramp-up the owner can actually plan around, rather than an unexplained number that prompts an uncomfortable conversation before anyone has the full picture.
The same principle scales to a third or fourth location just as easily as it does to a second — the routine does not get harder to run, it simply produces one more column in the same table, growing with the clinic instead of needing to be rebuilt each time it opens a new door, expands a service line, or brings on another provider — the routine scales with the business rather than becoming a bottleneck on its growth.
What this does not replace
Not a billing service
No claim submission, no coding, no appeal filing — this is the reconciliation layer underneath a billing service, not a substitute for one.
Not the statutory close
A monthly close is a formal, audited process. This is the operational weekly view that sits alongside it.
Not a forecast
The reconciliation shows what the clinic has collected, from documents. What it will collect next month is a separate exercise, with its own assumptions.
Not a denial-management workflow
Denials are surfaced with their appeal deadline. Filing the appeal itself remains a human task.
Why traceability matters more than it seems
Every figure in a clinic's income reconciliation should be able to answer one question instantly: which remittance did this come from? In a manual spreadsheet, that answer usually lives in someone's memory, or in a folder of PDFs loosely associated with a row, and finding it again three months later takes longer than re-reading the remittance would have.
This matters more than it sounds like it should, for three recurring situations. The first is a payer audit asking to see the source for a claim that was reconciled six weeks ago — a routine request that still needs an answer within the day rather than a week of searching. The second is a new billing service or accountant taking over, where the whole revenue history gets re-examined from scratch and every figure needs a document behind it. The third is simpler and more common: the practice manager themself, three weeks later, trying to remember why one payer's total moved the way it did.
A routine where every claim is read directly from a stored remittance, rather than retyped into a cell that then becomes the only record, answers all three automatically. The traceability is not an extra feature bolted onto the reconciliation — it is a natural side effect of reading the number from the document every time instead of copying it once and trusting the copy afterward.
Starting this week
Take next week's remittances — every payer, every account you would normally gather by hand — and read them together as a trial alongside the existing routine, not instead of it yet.
Compare the time it took against a normal week, and check the totals agree. Most practice managers who run this comparison once do not need convincing further; the time difference is usually visible after a single cycle.
For the underlying method this routine is built on, see practice income reconciliation and how to reconcile insurer payments.