Website Notice: We are making improvements to our website layout to provide a better browsing experience. Some content may be updated during this process.
A claim has a problem.
But what kind of problem?
Was it rejected before it could be properly processed?
Was it processed and then denied?
Or did the payer issue payment, but for less than the practice expected?
To a busy medical billing team, all three situations can appear in AR as money that has not been fully collected.
But they are not the same problem.
And treating them the same way can lead to unnecessary resubmissions, incorrect follow-up, missed reimbursement, and more time spent researching accounts that require completely different actions.
The first step toward working an account effectively is knowing what actually happened to the claim.
Claim was not accepted for processing.
Payer processed the claim but did not approve payment.
Payment was issued, but less than expected.
Identify the issue before taking the next step.
See the history and details behind the balance.
A rejection, denial, and underpayment can all leave money outstanding, but they happen at different points in the claim process.
A rejection generally means the claim or transaction was not accepted for normal processing because something prevented it from meeting submission requirements. CMS guidance, for example, identifies incomplete or incorrect billing information among reasons a claim transaction may be rejected and notes that rejected Medicare claims are corrected and resubmitted as new claims.
A denial means the claim has reached a payer decision in which payment or coverage is not allowed in whole or in part. Depending on the reason, the appropriate response may involve correction, additional documentation, reconsideration, appeal, or another payer-specific action.
An underpayment is different again.
The payer has issued payment, but the amount may not match the reimbursement the practice expected. Understanding the difference requires reviewing the remittance, allowed amount, adjustments, patient responsibility, and other payment information. Standard adjustment and remark codes are used on remittance advice to explain claim-level or service-line payment adjustments.
The balance may look similar on the AR report.
The solution may be completely different.
When a claim is rejected, the first question should be:
What prevented this claim from being accepted correctly?
The issue may involve information such as:
The important point is that staff should identify and correct the reason for the rejection before simply sending the same information again.
Repeatedly submitting a claim without correcting the underlying problem does not create progress.
It creates another cycle of work.
A good rejection review should make it easy for staff to see what failed, what needs correction, and whether the corrected claim has actually been accepted afterward.
A denied claim has a different story.
The payer has made a decision about the claim or service, so simply treating it as a submission problem may lead staff in the wrong direction.
The denial may involve issues such as:
Different denial reasons require different responses.
One claim may need supporting documentation.
Another may require a corrected claim.
Another may need an appeal.
And another may have been processed correctly and require no additional payer action.
That is why the denial reason matters more than the word “denied.”
Before taking action, staff need to understand what the payer actually decided and what options remain.
Underpayments present another challenge because the account shows something positive:
Money was received.
That can make the claim look less urgent than a rejection or denial.
But payment does not automatically mean the reimbursement was correct.
Staff may need to compare:
The payer’s remittance information helps explain how a payment was calculated and why adjustments were made.
If the amount does not align with what the practice reasonably expected, the account may still require investigation.
This is especially important when the same payment difference begins appearing repeatedly across similar claims.
A small discrepancy on one claim may be easy to overlook.
Repeated across many claims, it can become a much larger revenue issue.
Misclassifying the Problem Can Create More AR Work
The wrong classification often leads to the wrong action.
Imagine three accounts with outstanding balances.
On the first, staff keep calling the payer even though the claim was rejected and simply needs corrected information.
On the second, staff repeatedly resubmit a denied claim even though the payer is waiting for documentation.
On the third, staff accept the payment and move the remaining amount forward without noticing that reimbursement may have been lower than expected.
All three accounts are being worked.
But activity is not the same as effective AR management.
The more useful question is:
Getting that answer early can prevent unnecessary calls, duplicate submissions, incorrect patient billing, and repeated account research.
When an account shows an unexpected balance, staff can begin with three questions.
If not, determine why it was rejected and what needs to be corrected before resubmission.
Review the payer response, denial or adjustment information, and any action required.
Compare the payment, allowed amount, adjustments, patient responsibility, and expected reimbursement.
From there, staff can determine whether the account needs:
The purpose of this review is not to add another complicated step.
It is to prevent staff from spending time on the wrong one.
Rejections, denials, and underpayments demonstrate why an AR balance alone is not enough.
A balance tells staff that money remains.
It does not necessarily explain why.
Teams also need access to the claim history, payer response, previous actions, payment information, supporting documentation, and other context surrounding the account.
When that information is scattered across several systems or difficult to reconstruct, even identifying the type of problem can consume unnecessary staff time.
Zybex helps healthcare organizations manage the information and activity surrounding AR accounts so teams can better understand what happened, what has already been done, and what may still require attention.
The goal is not simply to put more information in front of staff.
It is to help make the information surrounding an account useful when someone needs to decide what to do next.
Find the Friction Behind the Account
A rejection, denial, or underpayment may begin as a claim-level issue.
But the way the team handles it can reveal something larger about the operation.
Can staff quickly tell whether the claim was rejected or denied?
Can they easily find the payer’s reason?
Can they see what action another employee already took?
Can they recognize when a payment may be lower than expected?
Can they identify similar problems happening across other accounts?
If answering those questions requires extensive searching, repeated payer calls, or rebuilding account history every time someone touches the claim, the issue may involve more than the claim itself.
It may be exposing operational friction.
The Healthcare Operations Friction Assessment helps medical practices identify where information, processes, handoffs, and everyday account work may be creating unnecessary difficulty.
Take the Healthcare Operations Friction Assessment:
The Healthcare Operations Friction Toolkit can also help teams review practical areas of their workflow and identify opportunities to make account work more structured and manageable.
Because a denial, rejection, and underpayment may all appear as money still sitting in AR.
But knowing which problem you are actually dealing with is what helps determine the right response.
Enter your email below to receive the toolkit.
Enter your name and email below to access the toolkit
Your Healthcare Operations Friction Toolkit is ready.
See where workflow friction may be making AR work harder than necessary.
We use cookies to improve your experience on our site. By using our site, you consent to cookies.
Manage your cookie preferences below:
Essential cookies enable basic functions and are necessary for the proper function of the website.
These cookies are needed for adding comments on this website.
Statistics cookies collect information anonymously. This information helps us understand how visitors use our website.
Google Analytics is a powerful tool that tracks and analyzes website traffic for informed marketing decisions.
Service URL: policies.google.com (opens in a new window)
You can find more information in our Cookie Policy and .