SNF Medicare CHOW: Assignment, Enrollment and the Billing Transition

Three dates that should not be collapsed

A fictional buyer plans to take over Harbor Nursing on December 1. The purchase documents use that date, the software project calls it go-live, and the cash forecast assumes Medicare receipts will continue without interruption. The enrollment file, however, contains only a contractor acknowledgement.

The CFO needs a dependency schedule that separates transaction closing, Medicare participation and cash servicing. This original example illustrates administrative preparation; it does not classify a real transaction or advise a buyer whether to accept an agreement.

42 CFR 489.18 distinguishes specified ownership changes from other corporate transactions. Assignment carries applicable conditions of the existing provider agreement. The current CMS enrollment manual, sections 10.6.1.1 onward, describes the CHOW processing route and the separate new-provider path when assignment is not accepted.

Get the classification decision into the file

Begin with the executed or proposed transaction documents, current operator and purchaser legal entities, facility identifiers and the intended provider-agreement treatment. Ask the responsible adviser to state the classification, its supporting provisions and any unresolved facts. Record the contractor's written direction where clarification is required.

For Harbor, assume the qualified review concludes that the proposed arrangement follows the CHOW route with assignment. That assumption lets the team build the remaining schedule. It does not establish that another asset sale, stock transfer, lease or merger follows the same route.

A single field labeled “new owner” is inadequate. It cannot explain whether the enrolled legal entity changes, what happens to the existing agreement, or whether the requested transition matches the legal documents.

Compare three structures before selecting the path

The regulation supplies useful contrasts for initial triage. These are simplified structures for education; actual documents, entity law and CMS processing determine a real transaction.

Merger direction matters: the regulation distinguishes another corporation merging into the provider corporation from the provider corporation merging into another. The current manual also explains that rejection of assignment moves the entity to the new-provider enrollment path rather than transferring the existing agreement. Neither a transaction's marketing label nor an unchanged facility name decides these branches.

Reconcile the buyer and seller workstreams

Use one transaction identifier across the two organizations' records, while preserving separate responsibility for their submissions. The buyer should not mark the seller's work complete based on a verbal assurance.

This table prevents two common forecasting errors: treating application receipt as approval and treating a servicing arrangement as authority to bill. CMS describes a sequence involving contractor review, state recommendation and CMS enrollment actions. The exact transaction file determines where Harbor sits in that sequence.

Keep the cash bridge separate from the approval schedule

The fictional closing ledger contains $420,000 of pre-closing receivables. The transaction agreement assigns economic ownership of those receivables to the seller, while the buyer expects to perform collection work. Those are commercial assumptions for the exercise, not Medicare rules.

Create a servicing ledger with the original claim identifier, service period, legal entity, remittance, bank receipt, economic owner and settlement status. Suppose $70,000 arrives after closing for pre-closing services and $4,000 is recouped against that deposit. The bank movement is $66,000, but the servicing record must preserve the $70,000 gross receipt and $4,000 recovery separately. The parties' reviewed agreement determines the intercompany settlement; the deposit date alone does not.

Meanwhile, the buyer's forecast should show a range for cash timing while enrollment processing remains unresolved. It should not recognize a second receivable simply because the account was imported into a new system. Reconcile the old and new ledgers to one population before opening collections queues.

Define the release evidence

Harbor's readiness record needs the confirmed transaction treatment, required completed submissions, program approval and effective-date evidence, approved billing configuration, and reconciled cash-servicing responsibilities. If a date changes, re-evaluate the affected claim population and operational dependencies rather than editing every date to match the purchase agreement.

The finance director can now make a concrete decision: the software import may proceed in a controlled test environment, but the current evidence does not support marking Medicare participation and production billing ready. The open seller submission and disclosure branch have named owners; the cash plan remains provisional.

During a platform evaluation, use this case to test whether service dates, legal entities, claim history and payment ownership survive a transition without creating duplicate balances. The separate multi-facility rollout guide addresses technical cutover. Neither a successful migration nor this administrative schedule substitutes for the actual Medicare determination.