How does the platform run AR collections without losing money in the 90+ bucket?

The problem

AR over 90 days is where margin goes to die. Most operators discover a problem account when a CFO asks about a single resident — not when the aging crosses a threshold three months earlier. Industry medians for SNF AR > 90 sit in the 18–25% range.

How the platform runs it

AR aging is computed nightly per resident, per payer, and per community. Aged balances trigger collection tasks routed by owner — front-office for private-pay, billing for Medicare and managed Medicaid, and operations for self-pay disputes. Every collection touchpoint logs on the resident record. Statements, payment plans, and writeoffs flow through one approval workflow with full audit trail.

On the shift

The Tuesday AR review opens with the > 90 bucket sorted by payer and reason. Three private-pay accounts hit 91 days overnight — the system has already routed them to the business-office manager with the statement history and a payment-plan template attached. The largest aged Medicaid balance is a known pending application; the social worker who is managing it sees it on her dashboard with the next action due Friday. Writeoff requests route to the CFO with full documentation; the audit trail captures every approval.

What the outcome looks like

Expected outcome: AR teams using this module reduce AR > 90 days by 20–35% within two quarters and recover writeoffs that would otherwise have aged out silently. Private-pay portfolios see less compression than Medicare/Medicaid-heavy SNFs — segment matters.

What goes wrong without it

Without a structured collections workflow, the AR review is a printout from accounting that the business office promises to work "when there is time." The 91-day private-pay account becomes a 240-day account because nobody owned it. The pending Medicaid application stalls because the social worker is not looking at AR. Writeoffs happen in batches with thin documentation; the auditor flags them.