A Medicare SNF unsolicited response is an automatic message from the Common Working File (CWF), Medicare’s national claims history database, to a Medicare Administrative Contractor (MAC). It fires when a skilled nursing facility (SNF) posts a Part A claim (Medicare’s SNF and hospital coverage) that overlaps a Part B claim (Medicare’s professional and outpatient coverage) already paid to an outside provider.
The MAC then adjusts the Part B claim without human review and recoups it, which means it takes the payment back. The vendor loses revenue, and the invoice often lands on your desk.
Most guides explain this from the vendor’s side. This one explains it from yours, because your claim triggers it.
Quick Summary
SNF consolidated billing (CB) makes the SNF responsible for billing most services a resident receives during a covered Part A stay. When your Part A claim posts, Medicare finds any separately paid Part B claims for those services and recoups them automatically. Two triggers exist: a bundled procedure code, and, since July 2025, a professional claim billed with place of service (POS) 32 during a covered stay. The vendor fixes it with a corrected claim or an appeal. You prevent it by telling vendors about the stay on admission day.
Table of Contents
What is a Medicare SNF unsolicited response, and how is it different from a voluntary refund?
Consolidated billing is the Medicare rule that makes the SNF bill for most services a resident receives during a covered Part A stay. Outside suppliers must look to the SNF for payment on bundled services (CMS Claims Processing Manual, Pub. 100-04, Chapter 6, §10.1 and §10.4).
An unsolicited response is how Medicare enforces that rule after the fact. When an SNF’s Part A claim posts, CWF searches paid claims history for Part B claims that overlap the stay. CWF sends the MAC an unsolicited response, the MAC adjusts the claim at the line level, and a demand letter with appeal rights follows (Chapter 6, §110.2.1). Neither the SNF nor the vendor requests this. The claim posting triggers it.
Do not confuse this with the “unsolicited overpayment refund” that a Google search for the same phrase returns. That term describes a provider voluntarily returning money Medicare overpaid it (CMS Financial Management Manual, Chapter 3, §170.6). Here, nobody volunteers anything: the system finds the overlap and acts.
What triggers a Part B takeback: bundled codes and the POS 32 edit
The first trigger is the long-standing one. An outside provider bills Part B for a service whose HCPCS code (the standard code set for medical services) falls inside the consolidated billing bundle. Medicare pays it because no SNF claim exists yet. When your claim posts, the overlap surfaces and the takeback starts.
The second trigger is newer. Place of service (POS) is the two-digit code on a professional claim that shows where care happened. POS 31 is an SNF stay covered by Part A. POS 32 is a nursing facility, or an SNF where Part A coverage is exhausted or absent.
Under CMS Change Request (CR) 13767, effective July 1, 2025, CWF rejects professional claims billed with POS 32 that overlap a covered Part A stay. For claims already paid, a new unsolicited response adjusts POS 32 to 31, and the MAC recoups through its normal process (Transmittal 13073; MLN MM13767).
A third event is scheduled. CMS CR 14582 (Transmittal 13995, issued October 8, 2026) orders a one-time reprocessing of POS 32 claims with service dates from May 11, 2023 through December 31, 2024 that overlap Part A stays. It takes effect April 1, 2027, and MACs will reprocess and recoup. Vendors that billed POS 32 in that window may see takebacks tied to stays you billed years ago.
The vendor’s payment is provisional until your Part A claim posts. CMS has SNFs bill monthly and in sequence (Chapter 6, §40), so weeks can pass between the service and the detection. The takeback fires on your billing date, not the service date.
What does an overpayment recoupment look like, and why can't an SNF stop it?
On the vendor’s remittance, a consolidated billing denial typically carries claim adjustment reason code (CARC) 109 and remittance advice remark code (RARC) MA101, with Medicare Summary Notice (MSN) message 13.9. A POS 32 adjustment under CR 13767 carries CARC 58 and MSN message 13.10. The demand letter follows.
The process is automatic. The unsolicited response flows from CWF into the MAC’s system, and no one approves each one. The WPS webinar on reading the CMS files stated the remedy plainly: an appeal or a rebill, not a phone call asking someone to override it.
Consolidated billing follows the procedure code, not the location. A resident who rides to a physician’s office for a bundled service is still inside the SNF’s bundle. An ambulance trip to a physician’s office for a Part A resident bundles to the SNF as well.
Which services stay bundled, and how does modifier 26 or TC split billing work?
Medicare publishes bundled and excluded codes in annual consolidated billing files. The Part A files group services into major categories. The Part B files list bundled codes for Part A residents in four parts:
- File 1: global and professional physician services
- File 2: codes with a professional and a technical component
- File 3: ambulance services
- File 4: physical, occupational and speech therapy
File 2 is where split billing happens. The professional component (PC) is the physician’s interpretation of a test. The technical component (TC) is the equipment and staff that perform it. For these codes, the physician bills Medicare with modifier 26, a two-digit code that marks a professional-component-only claim, and the TC goes to the SNF.
If the physician bills the global code instead, Medicare pays first and recoups later. An emergency room (ER) visit bundles back into the stay unless the ER claim carries revenue code 045X. Check your Part A MAC’s update page every year, because the files change.
Is POS 31, POS 32 or POS 11 correct for a Part A resident?
Use POS 31 for a resident in a covered Part A stay. Use POS 32 after Part A ends or is exhausted. CMS CR 13767 addresses POS 32 specifically, and the Claims Processing Manual treats an SNF Part A resident as a registered inpatient for place-of-service purposes (Chapter 26, §10.5).
The hard case is a resident seen in a physician’s office. WPS guidance in the webinar says an office visit code (CPT 99202 to 99215, billed with POS 11) for a Part A resident is taken back. The correct claim uses a nursing facility evaluation and management (E/M) visit code with POS 31. Noridian’s Jurisdiction F place-of-service article also points to POS 31 when a Part A resident is seen in the office.
We did not find a CMS edit written specifically for POS 11, and coding forums disagree. Confirm the rule with your MAC before telling a vendor how to bill.
The mistake most SNFs make with consolidated billing takebacks
The most common wrong fix: a vendor gets the takeback, files a reconsideration saying the resident was seen in the clinic, and loses. Location was never the test. Stay status was.
The right fix depends on what happened. If the code was bundled, the vendor bills the SNF, not Medicare. If the code is a split code, the vendor submits a corrected claim with modifier 26, and the correction after recoupment goes through a formal redetermination (per CGS guidance). If the POS was wrong, the vendor corrects it to 31.
A recouped vendor claim is not a vendor problem. It is an invoice addressed to you. Medicare’s rule makes the vendor look to your facility for payment, so a takeback you ignored becomes a bill you did not budget for.
How does an outside provider confirm a Part A SNF stay?
Often it cannot. A MAC’s provider portal shows SNF spell dates, remaining co-pay days and billing NPI only after the SNF’s first claim for the stay processes. A vendor who looks up a new admission on day three sees nothing.
The portal cannot report a stay you have not billed. For every new admission, the only source of the stay information during the first weeks is your own staff.
The best practice from the webinar holds up. The vendor asks the patient, “Are you temporarily staying somewhere else?” and documents the answer. If the patient names a skilled nursing facility, the vendor calls to confirm whether the stay is Part A.
When you take that call, you are also telling the vendor whether to bill you. Document who asked, who answered and when.
For the coverage rules behind this, see our guide to Medicare Part A SNF eligibility requirements. For the verification steps, see how to check Medicare eligibility as a provider.
How can SNFs prevent the next recoupment at admission?
Put a written Part A stay notice into your admission workflow. Send it to the vendors that serve your residents: the visiting physician group, the mobile imaging provider, the lab and the ambulance company. This is a process step, and it works with any system.
If no one tells a vendor about the stay, you have scheduled the takeback yourself.
The first step in that workflow is confirming coverage. Our Medicare coverage verification module checks active Medicare coverage from the resident’s Medicare Beneficiary Identifier (MBI) and keeps a dated, searchable record with reference number, resident name, MBI, birth date and status. That record shows what you knew and when. It does not determine whether a stay is covered under Part A, which comes from your admission documentation, and it does not notify vendors for you.
Admissions teams that already track referral dates and documents in one place find the notice easy to add. Our SNF admission process software tracks referral and insurance acceptance with received dates and document completion.
Frequently Asked Questions
It is an automatic message from the Common Working File to the MAC, sent after an SNF's Part A claim posts. It identifies Part B claims for the same period that were paid separately but belong in the SNF's bundle. The MAC adjusts them and sends a demand letter with appeal rights.
The resident was most likely in a covered Part A stay when the visit happened. Medicare paid the physician first because no SNF claim existed. When the facility billed Part A, the system found the overlap and recouped.
No. The adjustment is automatic and has no manual override. The vendor's options are a corrected claim, a billing arrangement with the SNF, or an appeal on the correct grounds.
POS 31 is correct. POS 32 applies once Part A coverage has ended or is exhausted. Since July 1, 2025, CMS edits reject POS 32 claims that overlap a covered Part A stay.
Often only because someone tells them. The MAC portal shows stay data after the SNF's first claim processes. A written Part A notice to vendors at admission removes the guesswork.
Is LTC Apps right for your facility?
LTC Apps is built for you if:
- You operate a skilled nursing facility or small regional SNF group
- You want to reduce eligibility denials, streamline admissions, or fix your scheduling workflow without replacing your entire clinical system
- You are evaluating modular operations software and want something built for SNFs, not adapted from hospital or home health platforms
This is not the right fit if:
- You are looking for a full clinical EHR with physician-facing charting
- You need software for assisted living only (no skilled nursing component)
- You require an enterprise contract with a dedicated implementation team from day one
Here is what happens when you request a demo:
- A member of our team reaches out within 1 business day to schedule a call
- We run a 30-minute live walkthrough of the modules most relevant to your facility
- You get access to pricing specific to your facility size and module selection
Most facilities have a clear picture of fit and pricing within one week of reaching out.
Common questions before booking a demo: no long implementation timelines, since most facilities are live on their first module within 2 to 4 weeks. No minimum facility size, since we work with single-facility operators and regional groups. If you are mid-contract with another vendor, we can run a parallel evaluation so you are ready to switch at contract end.
Ready to Streamline Your SNF Operations?
If you operate a skilled nursing facility and want to stop losing revenue to eligibility errors, admission delays, or scheduling gaps, LTC Apps was built for exactly this. Our SNF software gives skilled nursing teams modular, integrated workflows without the cost and complexity of an enterprise EHR.
