"So You're a Revenue Cycle Company?" A Day-One Reflection From the SNP Alliance Fall Forum
by Dr. Prince Baawuah, Head of Medicare Advantage Solutions
Last week, on the exhibit floor at the National PACE Association Annual Conference, the question was "So you're a TPA?".
This week, at the SNP Alliance Annual Fall Forum, the question changed:
"So you're a revenue cycle company?"
Different conference, different audience, same instinct. People hear "payment," "837s," "error resolution," and "recovering dollars," and they reach for the nearest category they already know. At NPA it was administration. Here, among D-SNP, C-SNP, I-SNP, FIDE-SNP, and HIDE-SNP leaders, it was revenue cycle.
It is a fair guess. And it points at something true.
Why "Revenue Cycle" Is the Natural Guess
In most of healthcare, revenue cycle management means the provider side of the money: capture the charge, code it, submit the claim, work the denial, collect the balance. The question it answers is "Did the payer pay us for this claim?"
Falcon does some of what that sounds like. We run the full MA encounter data submission pipeline: converting 837 claims, paper and electronic, into 837 MA encounter data records, running pre-submission validations, submitting to CMS, and resolving errors. Watch our team work with a health plan to resolve a rejected MA encounter, and it looks a lot like denial management.
But there is one difference that changes everything about the work.
An MA encounter is not a bill. Nobody pays for it.
It is a record of service. CMS's Encounter Data Submission and Processing Guide describes an encounter data record as a report to CMS about the medical items or services a beneficiary received while enrolled in an MA plan.
When a plan submits an encounter to CMS, no check comes back for that visit. The record is evidence. It tells CMS who the member is, what services they received, when and where, from which provider, and how sick they are. Together, those records tell the member's clinical story. Part of that story flows into a risk score, which flows into a payment, which may be adjusted months later.
The revenue is real. The cycle is real. It just does not run the way a provider's does.
A Plan's Revenue Cycle Runs Backward
A provider's revenue cycle moves forward: service, claim, payment, done.
A SNP's revenue settles backward. CMS pays prospectively each month, then keeps revising what it paid. Dual status and Medicaid eligibility move retroactively. Institutional and ESRD status may change mid-month. Mid-year and final sweeps redraw risk scores the plan already booked. Every one of those changes lands in a different CMS file, on a different cycle, in a different format.
Picture a single member. She is made up, but her story will be familiar to anyone who works in a D-SNP. She is a full-benefit dual eligible with diabetes and heart failure. In the spring, her Medicaid redetermination paperwork goes missing in the mail, and her Medicaid eligibility lapses. In the summer, it is restored retroactively. In the fall, after a hospitalization, she moves into a nursing facility.
Three events. Each one changes what her plan should be paid for her. And none of them arrives as a single, clean answer:
- Did the restored Medicaid eligibility ever reflow into her dual status, and her payment, for the months she lost?
- Did CMS recognize her institutional status, and pay the plan for it?
- Did the diagnoses her doctors documented this year reach her risk score, or did they stop somewhere between the clinic, the clearinghouse, and CMS?
No denial letter will ever tell the plan those answers. There is no claim to appeal. If nobody goes looking, the gap is silent, and it stays silent.
What People Mean When They Ask "Revenue Cycle"
At the booth, I heard the question as practical shorthand: Will you help us find money we are owed, and keep us from leaving it on the table?
Yes. But for a plan, that is only half the job. Reconciliation has to run both directions:
- The leakage you never see. The retroactive dual status change that never reflowed. The institutional status CMS never paid. The submitted diagnosis that never landed on a risk score.
- The overpayments you have to return. The member whose status changed and whose payment did not. The diagnosis that will not hold up in RADV.
A revenue cycle company is built to collect. A plan has to be able to explain: what CMS paid, why it changed, and what evidence stands behind every dollar it keeps.
Where Falcon Fits
The clearest way to place Falcon is by role:
| Primary job | The question it answers | Where Falcon is different | |
|---|---|---|---|
| Revenue cycle management | Get the provider's claims paid; work denials and A/R | Did the payer pay us for this claim? | Falcon works the plan side, where no single claim carries the payment |
| TPA or payment administration | Process transactions and delegated administrative work | Was this transaction processed? | Falcon explains the full payment chain behind the transaction |
| Falcon Health | Reconcile what CMS paid against what it should have paid, member by member, in both directions | What were we paid for this member, and why did it change? | All 70+ CMS files (MMR, MOR, MAO-004, DTRR, Part D MOR) in one system, tied to the member and the evidence |
The Member Is the Unit of Work
Last week I wrote that a PACE participant is not a row on a report. The same is true here, maybe more so.
SNPs serve the highest-acuity members in Medicare Advantage: people living with multiple chronic conditions, people in institutions, people whose coverage depends on two programs that rarely move in step. Their revenue is the hardest in MA to get right because their lives are the most complicated in MA to serve.
A revenue cycle is organized around the claim. Falcon is organized around the member. When a plan can see one member whole, her eligibility, her status, her encounters, her risk score, and her payment, in one place, the question stops being "Did we get paid?" and becomes "Are we being paid correctly to care for her?"
That second question is the one that protects the plan in an audit. It is also the one that protects the money meant for her care.
The Category Question Is a Good Sign
Two conferences, two categories: TPA, then revenue cycle. I take both as good news. Leaders are not asking us for another abstract AI promise. They are trying to place Falcon on the real map of their organizations, next to the vendors they already trust.
So here is the answer I gave, again and again, at the booth. Falcon can do some of what people expect from a revenue cycle company. But a plan's revenue cycle runs backward, through dozens of CMS files and months of retroactive change, and it ends with a member, not a claim.
Every file. Every member. Every dollar. Reconciled.
See Falcon in Action
If your team is asking what CMS actually paid you for your members, and why it changed, we'd like to show you what that answer looks like for your plan.
Schedule a conversation with Falcon Health
More reflections from the SNP Alliance Fall Forum to come.