Hospice Cap Exposure

wa2

A hospice can run a strong year on paper and still owe money back. Census holds steady, the team is full, the Medicare deposits land on schedule. Then the cap determination comes due after the year closes, and a number that was building quietly for twelve months arrives as a repayment. By then the cash is gone. It paid for nurses, mileage, and medication all year, because it looked like revenue the entire time.

A number that builds for twelve months

The aggregate cap is not a claim edit, and it never shows up on a remittance. It is an annual ceiling on total Medicare payment per beneficiary. For each cap year, a hospice multiplies the published cap amount by its number of Medicare beneficiaries, counted on a patient-by-patient proportional basis, and compares that ceiling to what Medicare actually paid. Everything above the ceiling goes back. For the 2026 cap year the amount is $35,361.44 per beneficiary, up 2.6 percent from $34,465.34 the year before.1

The cap year runs October 1 through September 30. The self-determined determination is filed with your MAC no earlier than three months and no later than five months after the year closes, so between January 1 and the end of February, and any overpayment is due when you file. Miss the window and CMS can suspend payments until the determination is in.2

Why a profitable year turns into a repayment

The cap is a twelve-month accumulation, and most agencies look at it once, at filing. Nothing done in February changes a year that ended in October. The exposure was set months earlier, by admission mix and length of stay, back when the census still looked healthy.

Long lengths of stay are the usual driver. A hospice weighted toward long-stay diagnoses, dementia and debility among them, collects a per-diem day after day against a fixed per-beneficiary ceiling. The ceiling moves with the number of beneficiaries, not with how long each one stays. So two patients who each stay well past a year can absorb the room that a dozen short-stay patients would have left open. The mechanism is plain: payment per patient keeps climbing, the cap room per patient does not, and the gap between them is the repayment.

The agencies that get caught are rarely the ones with obvious problems. They are the ones whose average length of stay drifted up a few weeks a year, unremarked, until the math crossed the line. When the repayment lands, it lands on current cash. It comes out of this month’s deposits, not last year’s, so a liability earned in a good year gets paid in a leaner one. For an agency on thin margin and a tight payroll cycle, a six-figure cap repayment is not a line item. It is a borrowing decision.

There is also a separate inpatient cap, which limits how much of a hospice’s care can be delivered at the inpatient levels. That is a different limit, and not the one that produces the large year-end repayments. When people say a hospice hit the cap, they almost always mean the aggregate cap above.

Carrying the cap as a monthly number

The fix is not a better February. It is treating the cap as a number you carry all year: a running estimate, updated monthly, of payments to date, a projected beneficiary count, and the room left under the ceiling given your current length-of-stay trend. Watch the admission mix and the long-stay tail the way you watch cash, because that is what moves the exposure.

Done that way, the cap stops being a surprise and becomes a forecast. A forecast is something you can act on, by managing admissions, eligibility, and documentation through the year while there is still year left. The earlier you see the number, the more room you have. A cap liability spotted in month four is a set of options. The same liability discovered at filing is a bill.

The billing side

This is the accounting and reporting side of the cap: knowing your exposure and closing the year clean. The claim-level mechanics, how election, levels of care, and the aggregate calculation come together on the bill, we cover on Walters Billing in Understanding the Hospice Aggregate Cap.

You do not want to learn your cap position from the repayment letter. You want to carry it as a number that is current every month, so the year-end determination only confirms what you already knew. If it is not tracked that way now, that is the gap worth closing before this cap year ends.

Speak With a Specialist about a cap and reporting review.

Related reading: Understanding the Hospice Aggregate Cap (Walters Billing)

Appendix: Sources

1. Centers for Medicare & Medicaid Services, FY2026 Hospice Wage Index and Payment Rate Update Final Rule (CMS-1835-F); 42 CFR 418.309, Hospice aggregate cap. The 2026 cap-year amount is $35,361.44 per beneficiary, a 2.6 percent increase over the prior year’s $34,465.34. The aggregate cap equals the cap amount multiplied by the number of Medicare beneficiaries, counted on a patient-by-patient proportional basis.

2. 42 CFR 418.308, Submission of the self-determined aggregate cap determination, and 42 CFR 418.309. The cap accounting year runs October 1 through September 30. A hospice files its self-determined cap determination no earlier than three months and no later than five months after the cap year ends, remitting any overpayment at filing; failure to file timely may result in suspension of payment.

Latest Posts

Watch Our Video

Get a glimpse of what it's like to work with us!
WATCH

Speak with a healthcare accounting specialist about compliance requirements, cost reporting, and financial coordination issues.

"*" indicates required fields

This field is for validation purposes and should be left unchanged.
Name*
Please provide any information that may help us with your inquiry.

Initial consultation. No obligation.

Request Free Audit Consultation Now

"*" indicates required fields

This field is for validation purposes and should be left unchanged.
Examples: Empower, Fidelity, ADP, John Hancock, Principal, Paychex, etc. If you are not sure, you can leave this blank.

"*" indicates required fields

This field is for validation purposes and should be left unchanged.

"*" indicates required fields

This field is for validation purposes and should be left unchanged.

"*" indicates required fields

This field is for validation purposes and should be left unchanged.

"*" indicates required fields

This field is for validation purposes and should be left unchanged.