RESULTS
These are not hypothetical scenarios. They are real dental practices, real numbers, and real consequences of missing upstream financial controls.
Every dollar in these stories was already earned.
Revenue Protection Architecture in Practice
01
OVER-90 AR RECOVERY
The 846,230 Tuesday Morning
Wake-Up Call
It was a regular Tuesday. The kind of Tuesday where you grab your coffee, check your messages, and — if you happen to be a dental practice owner — discover that over $846,000 is sitting in your over-90 insurance aging report.
To his credit, he called immediately. That is not always what happens.
What we found
nicknames, transposed dates of birth, wrong subscriber numbers, incorrect payer IDs, and unverified carrier addresses.
and claims that did not match the clinical note. The claim said one thing. The chart said another.
who refused to pay. This is what happens when insurance verification is skipped.
The owner had no idea. Experience is not the same as correct. It is not the same as compliant. And it is not the same as defensible.
Recoverable portion collected. $25,000 properly written off. Policies established. Every financial control point verified.
The owner now reviews his AR every single week.
RPA Pillars Involved
This case study shows, in one view, how upstream data integrity and controls turn a terrifying AR number into a recoverable, structured outcome.
02
When the Numbers Don't Add Up — and Someone Knows Why
FRAUD DETECTION
“Confusion is not a character flaw. Ignoring confusion is.”
No panic call. No massive AR report. Just a doctor who kept looking at her bank account, looking at her production numbers, and quietly thinking:
something is not right.
She was correct.
What We Found
but the adjustments were confusing and the money in the bank did not reflect the work being completed.
Fee schedules were correct. The employee was writing off patient responsibility balances — selectively.
refunds being issued to credit cards that did not belong to the patients on the accounts.
caught early only because the doctor was confused enough to ask for help. Had she not asked, this would have continued.
Outcome
Employee terminated. Forensic Accountant notified. Software access controls restructured — no single employee retained unchecked ability to post payments, apply adjustments, and process refunds.
The doctor now reviews her adjustment report every single day.
RPA Pillars Involved
This case shows how your system turns vague “something’s off” into concrete controls and daily owner review.
03
THE ORIGIN STORY
The Frustrated Office Manager — and the Case That Started Everything
This is the case I think about most. Not because the numbers were the largest. Not because the fraud was the most sophisticated.
Because this case is the reason Revenue Protection Architecture exists.
“I didn't know” is not a legal defense.
It has never been a legal defense.
And the insurance carriers do not accept it as one.
What we found
-
The office manager knew the rules. She knew what was right, wrong, and defensible.
-
She was overruled every day by a doctor with one philosophy: "This is my office. My rules."
-
Patients learned quickly — skip the front desk, go directly to the doctor, and he would offer a discount.
-
Co-pay waivers, courtesy discounts, family and friend reductions, ad hoc reductions for anyone who asked.
-
$6,700 in adjustments — all traceable to the doctor's generosity.
-
None of it disclosed on the claim form.
-
When a practice participates with an insurance carrier, it enters a contract.
-
Waiving patient responsibility without disclosure is not kindness. It can be fraud and is at the least overbilling
The doctor was shocked. And then, to his enormous credit, he was receptive. Not every doctor responds that way.
Outcome
Policies put in place governing how discounts are applied, documented, and reflected on claim forms.
The office manager — who had been carrying this alone — finally had the backing she needed.
The doctor stopped the ad hoc discount conversations entirely.