You pull the receivables report and you pull the collections figure, and the two do not reconcile. Nothing is broken. They are answering different questions, and once you know which four things account for the gap, the difference stops being a mystery and becomes a checklist.
Why does my AR report not match my collections?
Because receivables record what has been billed and remains open, while collections record money that has posted. Four things sit between them: balances that cleared through an adjustment rather than a payment, payments received and not yet posted, work delivered and not yet billed, and balances that changed category without leaving the report. Each one is a configuration question rather than an accounting error.
The two reports measure different moments
Your accounts receivable report is a snapshot of open balances at the moment you run it. Every line is something that has been billed and has not yet resolved.
Your collections figure is a sum of money that posted across a period.
Those are different shapes of number. One is a position, one is a flow. They will never tie exactly, and the useful question is not whether they match but whether the difference is explainable.
In a practice where somebody can explain the difference in four lines, the reporting is sound. In a practice where nobody can, the difference is where the attention belongs.
Cause one: balances that cleared without a payment
A balance can leave your receivables report in two ways. Somebody pays it, or somebody adjusts it.
Contractual adjustments, write-offs, and reclassifications all reduce receivables and none of them produce a dollar of collections. That is correct behaviour and it is the single largest reason the two figures diverge.
The check: pull every adjustment code used in the period and total them by code. Receivables reduced, minus adjustments, should approach collections. Where it does not, keep going down this list.
Worth doing carefully, because adjustment code use drifts. A code created for one purpose gets applied to a similar one, then to a less similar one, and after a few years the list and its actual use have separated. Nothing surfaces that automatically, because reports read the code rather than the intention behind it.
Cause two: payments received and not posted
The remittance arrived. Nobody applied it. The balance is still open on your report and the money may already be in your bank.
This one runs in the opposite direction from what people assume. It makes receivables look higher than reality rather than lower, and it makes collections look lower than reality for the period.
The check: compare remittances received in the period against payments posted in the period. A gap of a day or two is a normal rhythm. A gap measured in weeks is a backlog, and it distorts every downstream figure until it clears.
Posting backlogs tend to form after something specific. A staffing gap, a system change, a fortnight of unusual volume. They persist afterwards because catching up needs capacity beyond the daily flow, and the daily flow is already using it.
Cause three: work delivered and not yet billed
This is the one that surprises people, because it explains a gap in a direction the report cannot show you at all.
Receivables count balances that have been billed. A visit that happened last month and has not yet become a claim is not on the report. It is not late receivables, it is not slow collections, and it appears in neither number.
Documentation waiting on a signature, an encounter waiting on a chargeslip, a claim built and not yet released. All real, all delivered, none of it visible in either figure you are comparing.
The check: compare completed appointments for a period against charges created for the same period. Anything seen with no corresponding charge is this category. Most practices have never run that comparison, because it starts in one part of the system and finishes in another.
This is also why the two reports can both look healthy while cash feels wrong. Neither of them is measuring the part of the process where the delay is happening.
Cause four: balances that changed category
A balance moves from insurance responsibility to patient responsibility. Nothing was forgiven and nothing was collected, but the balance now sits in a different place on the report and its age may have reset.
Reclassification is used loosely across practice management systems rather than defined by a standards body, which is part of why it drifts. Where reporting groups reclassified balances alongside active ones, the total stops describing what you think it describes.
The check: identify which codes in your list move a balance rather than clearing it, then look at how much volume runs through them. A code doing something other than its name suggests is the most common single finding when a practice looks at this properly.
Getting deeper visibility from your AdvancedMD data
Everything above is standard practice management behaviour and it applies to any system. What differs between practices is how much of it has been configured to surface on its own.
Standard reports show you receivables and collections. Reconciling the two is a separate view, and it is one most practices have never built because it draws on data from several places at once.
Three things make that view work.
Adjustment activity grouped by code and by user. Not just the total. Which codes carry the volume, who is applying them, and what each one actually does to a balance.
Remittances received against payments posted. Two figures side by side for the same period, with the age of the oldest unposted item.
Completed appointments against charges created. The comparison that surfaces work delivered and never billed.
None of those require anything you do not already hold. They require somebody deciding the view is worth building, which is a configuration decision rather than a system one, and most practices have simply never had a reason to make it.
What this means for you
Take a closed month and account for the difference in four lines. Adjustments. Unposted payments. Delivered and unbilled. Reclassified balances.
If those four explain the gap, your reporting is sound and you can stop wondering. If a residual remains after all four, that residual is the number worth chasing, and it is a far more useful thing to walk into a meeting with than a feeling that something is off.
Grab 30 minutes with us. Prep nothing. You will see the four lines on your own numbers and what is left over.
Questions people ask
Why does my AR report not match my collections?
Because receivables record what has been billed and remains open, while collections record money that has posted. Four things sit between them: adjustments that cleared balances without payment, payments received and not posted, work delivered and not yet billed, and balances that changed category.
Should accounts receivable and collections ever tie exactly?
No. One is a position at a moment and the other is a flow across a period. They are different shapes of number. The useful test is whether somebody can explain the difference in four lines, not whether the figures match.
How do adjustments affect the gap between AR and collections?
They reduce receivables without producing any collections, which is correct behaviour and usually the largest single cause. Pull every adjustment code used in the period and total by code, because code use drifts over years and no report surfaces that on its own.
Can unbilled work explain the difference?
It can explain a gap that neither report shows. A visit that has not become a claim is not in receivables and not in collections. Compare completed appointments against charges created for the same period to find it.
What is a payment posting backlog doing to my numbers?
Making receivables look higher than reality and collections look lower for the period. Compare remittances received against payments posted. A day or two is a rhythm. Weeks is a backlog that distorts everything downstream until it clears.
PracticePath is not affiliated with, endorsed by, or sponsored by AdvancedMD. AdvancedMD is a trademark of AdvancedMD, Inc. All references are for descriptive purposes only.