Revenue Cycle · Payment reconciliation · Medicare Advantage

Check every month's CMS payment, member by member.

CMS pays a plan for each member each month, then goes on correcting those payments for months afterwards. Vernier reads the files CMS sends, works out what should have been paid, and turns each difference into a case with a cause and an owner.

Revenue Cycle · Payment reconciliation
Vernier Revenue Cycle dashboard: the month's expected and paid amounts, what CMS owes the plan, what the plan owes CMS, and open cases by cause
How it works

Three CMS files in, a worked queue out.

The plan already receives everything this needs: the Monthly Membership Report, the Transaction Reply Report and the Part C Model Output Report. Nothing is re-keyed and nothing is estimated.

Reads the files as delivered

The file says what it is

The fixed-width layouts from CMS's Plan Communications User Guide, read byte for byte. A file loaded twice, a second MMR for a month already loaded, or a file for another contract is refused whole. A bad row is refused with its line number and the rest loads.

Prices every member-month

What CMS should have paid

The plan's rate times the member's risk factor, plus the rebates, for Part A and Part B, with the hospice, ESRD and Medicare Secondary Payer rules applied. Every expected dollar traces to a rate and a factor on screen.

Explains each difference

Twelve causes, and the split adds up

Enrollment, hospice, ESRD, Medicaid status, county, benefit package, rate, risk score and the rest. Where two facts disagree, each gets its share, and the shares always sum to the variance exactly.

Paid to date, not paid that month

A month is not settled when it is paid.

CMS pays a month prospectively and corrects it later with adjustment rows in subsequent files, sometimes more than once. What was paid for March is the March payment plus every adjustment since that covers March. Vernier keeps that running total for every member and month.

  • One case per member and cause, however many months it spans.
  • A case closes itself when a later adjustment pays it back, and records which file and reason code did it.
  • What CMS owes the plan and what the plan owes CMS are reported separately and never netted.
  • A CMS reply that changes what the plan expects waits for a person to apply or dispute it. Nothing is applied automatically.
Revenue Cycle · A case
A discrepancy case in Vernier Revenue Cycle showing what the plan's record says, what CMS is paying on, the evidence and the month-by-month ledger
What the plan sees

Eight views, one reconciliation.

DashboardThe latest month's expected and paid amounts, the two outstanding balances, open cases by cause, how long they have been open, and the cases nobody owns.
DiscrepanciesThe working queue: each case with what the plan's record shows, what CMS is paying on, the months affected, the amount, the owner and the status.
Transaction repliesWhat CMS has told the plan on the TRR, with the ones that disagree with the plan's own record waiting for a decision.
Payment monthsEach coverage month: paid at the time, adjusted since, still underpaid, still overpaid, by cause and by benefit package.
MembersThe plan's record of a member beside every payment row CMS has sent for them.
Risk scoresThe conditions the plan expects for each member against the ones CMS scored on its Model Output Report.
CMS filesEvery file loaded, what it held, what was refused and why, and any adjustments reaching back to earlier payment years.
Audit trailEvery file load, reply decision, case change and export, with who did it.
Numbers that hold up

Checked against a real CMS file, and honest about what is not.

Read a real MMR cleanly

A real Monthly Membership Report parsed without a rejected row. On every prospective row, the rate times the risk factor reproduced CMS's own amount to the cent, and every multi-month adjustment behaved as the reconciliation assumes.

What is not reconciled is stated

Adjustments reaching back to earlier payment years are counted and shown on the file's page, not silently left out. A month with no MMR loaded is flagged on the dashboard before anyone works the queue.

Not yet

  • Part D reconciliation. The amounts are stored.
  • The Plan Payment Report, and the tie-out to the bank deposit.
  • Premium billing and payment posting.
  • Rebate, hospice and MSP arithmetic confirmed against a Medicare Advantage plan's own file.

See a month reconciled live.