— Michael N. Brown
Every step of the revenue cycle generates data.
Eligibility. Coding. Claims. Denials. Payments. Adjustments. A/R aging. Charge lag. Payment velocity.
Healthcare organizations have more visibility than ever before. Dashboards are full. Reports are running. Metrics are being tracked across systems, teams, and payers.
And yet, many practices still struggle to answer the questions that matter most:
- Where is revenue leaking?
- Why are denials increasing?
- Which claims are sitting too long?
- What payer issues are creating delays?
- Which write-offs were unavoidable — and which were preventable?
The problem is not a lack of data.
The problem is that data often exists without enough context, accountability, or operational follow-through.
Data Alone Does Not Create Clarity
In healthcare, more reporting does not automatically mean better decision-making.
A practice may know its denial rate. It may know its days in A/R. It may receive monthly payment reports. But those numbers only become useful when leadership can connect them to what is actually happening inside the workflow.
For example, a rising denial rate does not tell the full story by itself. The real question is why the denials are rising.
- Is it an eligibility issue at the front desk?
- A payer policy change?
- A missing authorization?
- Incomplete documentation?
- A coding issue?
- A claim that was never followed up on in time?
Without that deeper review, data becomes a snapshot instead of a strategy. It shows that something happened, but not what needs to change.
The Reports That Reveal the Real Story
One of the most important places to start is with adjustment and write-off reporting.
Many organizations look at payments and assume that if cash is coming in, the revenue cycle is functioning. But payments only show what was collected. Adjustments show what was not.
That distinction matters.
Some adjustments are expected, such as contractual write-offs based on payer agreements. But others are preventable. These may include write-offs tied to timely filing, missing authorizations, eligibility issues, non-covered services, medical necessity denials, or documentation gaps.
Those are not just accounting entries. They are operational signals.
If a claim is written off because a referral was never obtained, that points to a front-end process issue. If a claim is denied for medical necessity because the payer required documentation that was not submitted, that points to a documentation or appeal workflow issue. If a high-dollar claim sits too long and misses a filing deadline, that points to an A/R follow-up issue.
The value is not in knowing that money was written off.
The value is in knowing why it was written off, and whether it could have been prevented.
A/R Aging Shows Where Revenue Is Getting Stuck
Aging accounts receivable reports are another example of data that is only useful when interpreted correctly.
A healthy A/R report should show most receivables in the 0-to-30-day bucket, with smaller amounts in 31-to-60, 61-to-90, and 90-plus days. When that pattern starts to flatten or invert, it is a red flag.
But again, the number alone is not enough.
If the 90-plus-day bucket is growing, leadership needs to know what is driving it.
- Which payer is responsible?
- Are the claims denied or untouched?
- Is the issue documentation, routing, authorization, or payer delay?
- How many times has each claim been worked?
- Does the team have enough capacity to follow up consistently?
This is where data must move from reporting to action. A/R does not age because of one large problem. It usually builds through hundreds of smaller breakdowns: missed follow-ups, delayed documentation, payer changes, coding backlogs, or claims that sit without ownership.
When those issues are not identified early, revenue quietly stalls.
Charge Lag and Payment Velocity Matter Because Timing Matters
Two additional metrics often reveal how efficiently the revenue cycle is actually moving: charge lag and payment velocity.
Charge lag measures the time between when a service is performed and when the charge is entered into the billing system. Every day of charge lag adds time to the cash cycle. If documentation is delayed, coding is delayed. If coding is delayed, claim submission is delayed. If the claim is delayed, payment is delayed.
Payment velocity shows how quickly money comes in after a claim is submitted. When payment velocity drops for a specific payer, procedure, or location, it may signal a policy change, payer processing issue, documentation problem, or workflow breakdown.
These metrics are powerful because they help organizations move from reactive to proactive. Instead of waiting for A/R to grow or denials to spike, practices can spot early warning signs and intervene before the problem becomes more expensive.
Where FHP Takes a Different Approach
At Fellow Health Partners, we believe revenue cycle data should do more than populate a dashboard. It should guide decisions, identify root causes, and drive measurable operational improvement.
Just as importantly, that approach should be individualized to each client. The most useful insights come from understanding a client’s specific data, specialty, payer mix, operational nuances, and workflow realities, not from applying the same reporting template to every organization.
That means looking beyond high-level metrics and asking more useful questions:
- Which denials are preventable?
- Which write-offs are non-contractual?
- Which payers are slowing payment?
- Which procedures are driving denials?
- Which claims are aging without enough follow-up?
- Where is charge lag occurring, provider documentation, coding, or billing?
- What needs to change in the workflow to prevent the same issue from happening again?
FHP helps organizations connect the data to the work behind the data.
That includes reviewing adjustment trends, separating contractual from non-contractual write-offs, identifying denial patterns by payer and procedure, monitoring A/R aging, tracking charge lag, evaluating payment velocity, and building reporting structures that create accountability.
The goal is not simply to show clients what happened.
The goal is to help them understand why it happened, what it is costing them, and what can be done to fix it.
Data Should Lead to Action
A dashboard is only valuable if someone is using it to make better decisions.
Too often, healthcare organizations receive reports that are reviewed too infrequently, reviewed without context, or reviewed without clear ownership for follow-up. In those cases, even accurate data can fail to improve performance.
High-performing organizations use revenue cycle data differently. They do not just track metrics. They use those metrics to manage the business.
- They review trends consistently.
- They investigate outliers.They assign accountability.
- They identify payer-specific issues.
- They correct workflow breakdowns.
- They use data to prioritize where teams should focus their time.
That is how reporting becomes execution.
Final Thought
Healthcare does not have a data problem.
It has a clarity and execution problem.
The organizations that perform best will not be the ones with the most reports or the most complex dashboards. They will be the ones that know how to interpret the right data, connect it to real operational issues, and act before revenue is lost.
Because in the revenue cycle, the numbers matter.
But what you do with them matters more.
