Why Does a PointClickCare Facility Still See PDPM Underpayment and Aging A/R If the Platform Is Configured Correctly?
Your PointClickCare is set up right. The pay rates are loaded, the modules are turned on, the interfaces are green.
How to Close the PDPM and A/R Gap Inside PointClickCare
The goal is a PDPM score that matches the acuity you are actually documenting, and an A/R column that shrinks instead of ages. Here is what does that, move by move, without touching your configuration.
1. Reconcile the MDS-Driven PDPM Components Against the Clinical Record
PDPM reimbursement is built from the MDS, and the MDS is only as accurate as the cross-check behind it. Before an assessment locks, someone has to compare the coded items, section GG function scores, active diagnoses, the NTA comorbidities, against the therapy minutes, nursing notes, and physician documentation actually in the chart. When items are coded conservatively because the coder was not certain the support existed, the facility gives up accurate revenue it earned. Reconciling the coding to the record is where the suppressed score gets recovered, legitimately, not inflated.
2. Run the Denial and A/R Reports on a Fixed Monthly Cadence
PointClickCare will tell you exactly what is denied and what is aging; the reports exist and most facilities never open them on a schedule. Put a fixed monthly cadence on it. Pull the denial report, categorize the reasons, and route each one to a corrected claim or an appeal. Pull the A/R aging and work the oldest buckets first. A report you run once a quarter when someone remembers is not a control; a report worked every month by someone who owns it is how denials stop repeating and aged claims stop turning into write-offs.
3. Work Every Aged Claim to Resolution, Not to the Bottom of the Pile
Aging A/R does not resolve itself, and in a short-staffed business office the aged claims are exactly the ones that get skipped because they are the hardest. Reverse that. Work each aged claim inside the platform until it either pays, is corrected and resubmitted, appealed, or documented for a write-off decision made on purpose rather than by neglect. The claims that sit past 90 and 120 days are where real money quietly dies, which is exactly what dedicated aged A/R calling is built to clear, one claim at a time until the column moves.
4. Turn the Reporting Into a Routine Instead of an Afterthought
The platform's reporting is a revenue tool that most facilities under-use because nobody has the hours to build it into the week. Make it routine: PDPM component trends, denial reasons by payer, A/R aging by bucket, and cash posted against expected. When the numbers are reviewed on a cadence, a suppressed PDPM trend or a denial pattern shows up while you can still fix it, instead of surfacing at year end as a number you cannot get back.
5. Hand the Revenue Modules to a Dedicated Team
Facilities that stop leaking PDPM revenue and clear their A/R do it by handing the platform's revenue modules to a dedicated team: remote specialists who reconcile the MDS, work the denial and A/R reports every month, and chase every aged claim, live in 1 to 2 weeks. The MDS coordinator and business office go back to residents and care, a trained backup covers every gap, and the reports stop being the thing nobody has time to open. Below is what it sounds like when nobody owns this yet, in providers' own words.
Key Pain Points and Discussions by Providers
representative composite examples based on common workflow discussions
“Everyone kept saying the software was underbilling us. It was not. When we actually audited the MDS, the items that drive PDPM were being coded on the safe side, and nobody was tying them back to what therapy and nursing had already documented in the same chart.” composite example: SNF administrator
“Our A/R report lives in the system and we barely open it. There is no time. The MDS coordinator is buried, the business office is one person, and the aged claims just sit there getting older until they are basically uncollectible.” composite example: director of nursing, skilled nursing facility
“The denials are not even complicated. They repeat. Same reason, same payer, month after month, because nobody works the denial report on a schedule and nobody fixes the thing upstream that is causing them.” composite example: business office manager, skilled nursing facility
“We finally cross-checked section GG against the nursing notes and found we had been understating function scores on residents who genuinely needed more assistance. That was real reimbursement we simply were not capturing, and the platform had no way to know.” composite example: MDS coordinator
“The reporting inside the platform is powerful and we use almost none of it. I know the PDPM trends and the aging are sitting right there, but between the surveys and the staffing, actually working those numbers every month never happens.” composite example: regional revenue lead, skilled nursing group
Our Answer
Here is what we actually do. A dedicated remote specialist reconciles the MDS-driven PDPM components, section GG function scores, active diagnoses, and NTA comorbidities, against the therapy and nursing documentation before the assessment locks, so the score reflects the acuity you are already charting instead of a conservative guess. They run the denial and A/R reports inside PointClickCare on a fixed monthly cadence, categorize every denial reason, and work each aged claim until it resolves or is documented for a write-off decision. Our specialists are trained healthcare operations professionals, overseas-trained physicians and US-licensed nurses, trained in SNF revenue cycle and PDPM workflows, working inside your platform, with approved AI tools assisting with first-pass reconciliation and a human verifying every coding cross-check and appeal. This is our revenue cycle management support built around the tools you already run, in one paragraph.
Why This Keeps Happening
If the platform is configured correctly, why does the money still leak? Because the platform is not the payer and it is not the coder; it is a ledger that records whatever the MDS tells it. PDPM reimbursement is calculated directly from the MDS assessment, and CMS's own model ties the payment components to specific coded items, so any mismatch between the clinical documentation and what is coded in the MDS produces an incorrect rate. When items are coded conservatively, the facility is underpaid, and the system has no way to catch it, because from its perspective the coding was complete.
The pressure that creates the gap is bandwidth. In a skilled nursing facility the MDS coordinator and the business office are usually a very small team wearing many hats, and the revenue modules, denial reports, A/R aging, PDPM component review, are exactly the work that gets deferred when a survey or a staffing crisis lands. Industry guidance on PDPM is blunt that accurate section GG and diagnosis coding is where facilities most often lose reimbursement, and that the Triple Check review before billing is the control that catches it. Without the hours to run that control every cycle, the leak is structural. Closing it is what a dedicated AI medical coding review with human verification is built to do.
And the cost compounds quietly. A suppressed PDPM score is not a one-time miss; it repeats on every assessment for every resident until someone catches the pattern, and aged A/R that is never worked slides past the timely-filing and appeal windows until it is simply uncollectible. By the time it shows up as a year-end number, the money is gone and cannot be re-billed. The lost revenue is real, and unlike a denied claim you can appeal, an under-coded assessment that already locked is far harder to recover.
Most groups have already tried the obvious fixes before they talk to anyone. Each one fails the same way: the work lands back on the practice. The pattern, in one table:
| What you tried | What actually happened | Who ended up doing the work |
|---|---|---|
| Assumed the platform was underbilling and asked the vendor | The configuration checked out; the gap was in conservative MDS coding the vendor cannot see | The software, wrongly blamed |
| Left the MDS coordinator to catch coding gaps alone | Buried in assessments and surveys, no time to cross-check every item against the chart | One overloaded coordinator |
| Ran the A/R report occasionally when someone remembered | Aged claims slid past the filing and appeal windows and became write-offs | Nobody on a schedule |
| Gave the revenue modules to a dedicated remote specialist | MDS reconciled to the record, denial and A/R reports worked monthly, every aged claim chased to resolution | Someone whose whole job it is |
The Solution
So what does "someone whose whole job it is" look like inside PointClickCare? The specialist starts where the facility usually cannot: reconciling the MDS-driven PDPM components against the actual clinical record before the assessment locks. They compare section GG scores to nursing documentation, active diagnoses to physician notes, and NTA comorbidities to what is charted, so the coding reflects the acuity you are already documenting. That is not upcoding; it is capturing the reimbursement the record already supports, which is exactly what dedicated revenue cycle management is built to protect.
Then comes the part the business office never has hours for. The specialist runs the denial and A/R reports on a fixed monthly cadence, categorizes every denial reason so the repeating ones get fixed upstream, and works each aged claim inside the platform until it pays, resubmits, appeals, or is documented for a deliberate write-off. The oldest buckets get worked first, because that is where the money is dying. The reporting the platform offers stops sitting unused and becomes the routine that catches a suppressed trend while you can still act on it.
Behind all of it, Approved AI tools may assist with the first pass and a trained human reviewer verifies. The workflow flags coding mismatches, categorizes denials, and surfaces aging; a person confirms every clinical cross-check and owns every appeal. Because that work moves resident charts and PHI through a coding and billing process, every control that protects it is documented and auditable, and the whole approach is described on our HIPAA and security page, because moving clinical documentation through a revenue workflow is only safe when the controls are real.
Who Actually Does This Work
Fair question: why would an outsourced team recover your PDPM revenue better than your own staff who know the building? Because reconciling MDS coding to the clinical record and working an A/R report to zero is their entire day, not the thing they squeeze between care and surveys. The people working your revenue modules are trained healthcare operations professionals: overseas-trained physicians, US-licensed nurses, and PharmDs, all trained in SNF revenue cycle and PDPM workflows. They know how section GG drives the function score, how NTA comorbidities are captured, and how to read a denial report so the pattern behind it gets fixed. That is not a generalist task handed to whoever is free; it is a specialty.
We are not a billing mill. We are a clinical operations partner, a healthcare BPO built on dedicated virtual staff: 500+ team members, 24/7 coverage, and the AI-assisted plus human-verified workflow you just read about behind every one of them. A typical facility is live in 1 to 2 weeks, at approximately 68% below equivalent in-house staffing costs. Trained backup coverage is included in the managed-service model.
And the security piece your compliance officer will ask about: Staffingly maintains active ISO/IEC 27001:2022 certification and operates under HIPAA-compliant controls and signed BAAs. SOC 2 Type II reporting and security controls apply according to the relevant entity, client environment, facility, device, and workflow. Venn Blue Border and related workstation restrictions are used where applicable. Staffingly maintains $5M in professional liability (E&O) and cyber insurance as part of its enterprise risk-management program; the full detail lives in our HIPAA and security posture.
Put the routine and the people together, and a specific list of things simply stops happening.
Ready to Recover Your Suppressed PDPM Revenue?
Comparing the best home care and LTC billing services? See how a dedicated remote team compares, then browse every pain point we solve.
How We Build a More Durable Process
A person alone is not the fix, and neither is a report alone. The fix is a documented SNF revenue workflow: which MDS items to cross-check against which part of the chart before an assessment locks, the fixed cadence for the denial and A/R reports, the aging buckets and the order they get worked, and the escalation path when a claim is heading toward a write-off. Before we take a single assessment for a new facility, we chart where your PDPM scores are landing versus your documented acuity and where your A/R is aging, so we can see where the revenue is actually leaking and build the workflow against that, not a generic template.
From there the workflow becomes a living playbook rather than knowledge locked in one coordinator's head. It records how each PDPM component should be reconciled, how denials are categorized and fixed upstream, how aged claims are worked and when a write-off is a real decision, and the reporting cadence that keeps all of it visible. It is written down, kept current as CMS updates the PDPM mappings, and owned by the team. When your specialist is out, a trained backup works the same playbook the same way, so a suppressed score or an aging claim never waits for one person to come back.
That is the difference between recovering this month's underpayment and fixing the process for good, and it is what a dedicated revenue partner actually buys you. A coordinator or biller leaving used to mean the MDS cross-check and the A/R fell apart and the leak reopened. Under this model the workflow keeps running, the playbook stays, the backup steps in, and PDPM underpayment stops being the thing your correctly configured platform quietly costs you.
The Whole Thing in Four Sentences
A PointClickCare facility still sees PDPM underpayment and aging A/R because the platform records whatever coding it is given, and MDS items that drive reimbursement are coded conservatively and never cross-checked against the therapy and nursing documentation, while the denial and A/R reports go unworked. Blaming the software, or leaving the cross-check and the reports to an overloaded coordinator, fails the same way. The fix is to reconcile the MDS to the clinical record before it locks, run and act on the denial and A/R reports every month, work every aged claim to resolution, and make the reporting a routine. A multi-building skilled nursing group can use this workflow without exposing patient information or naming client organizations.
If you want to check us out before talking to anyone: our security posture is independently auditable, we are an MGMA 2026 Corporate Member, and 800+ providers run back office work with us.
Ready to recover your suppressed PDPM revenue? Start with a Two-Week Free Trial: your real MDS and A/R, dedicated specialists reconciling the coding and working the aging, and if it does not earn the handoff, you walk away. From here down is the sales part, and it is short: here is exactly what it costs.
One Flat Weekly Rate. 45 Hours of Coverage.
No hourly meters, no setup fees, no security deposits, no long-term contracts. Two-Week Free Trial. Your dedicated team member covers your desk 45 hours every week, and a trained backup steps in at no charge whenever they are out.
One dedicated remote specialist reconciling MDS-driven PDPM components and working the denial and A/R reports inside PointClickCare, single skilled nursing facility
5+ remote specialists covering MDS review and A/R across a multi-facility skilled nursing group on PointClickCare
10+ remote specialists, a regional SNF operator, MSO, or PE-backed platform running PDPM reconciliation and A/R across many buildings
45 hours of coverage at one flat weekly rate.
For a simple annual comparison, 40 hrs x 52 weeks = 2,080 hours. A Staffingly plan: 45 hrs x 52 weeks = 2,340 hours a year, that is 260 additional hours included in your flat rate. $399/week x 52 = $20,748 a year / 2,340 hours = $8.87 per hour.
Close Your PDPM and A/R Gap This Month
You have seen the whole method. The trial lets you test it on your own MDS and A/R, with a tracker your team can watch every day.
Start My Two-Week Free TrialWant Us to Recover Your Suppressed PDPM Revenue?
Tell us your situation and we will map your MDS coding gaps and the A/R aging behind them. A team member will follow up with next steps.
Frequently Asked Questions
Where the Claims on This Page Come From
Sources & References
- CMS Skilled Nursing Facility Prospective Payment System and PDPM. Federal documentation of how PDPM payment components are calculated from the MDS assessment. cms.gov
- CMS FY 2026 SNF Prospective Payment System Final Rule. Federal rule updating SNF payment and PDPM classification mappings for the fiscal year. cms.gov