Quick answer
Translate reviewed Medicare Advantage terms into rules keyed by facility, exact plan product and effective service period. Keep network verification, authorization, contracted payment and Medicare informational reporting separate. Validate a contract amendment against before-and-after dates and an unaffected facility. The worked matrix uses invented terms to expose configuration mistakes without treating Original Medicare PDPM as a universal MA rate.
Key the matrix to the relationship that actually exists
The minimum key is facility identity + plan product + effective period. Add service category when the contract distinguishes it. A payer brand, corporate name or insurance-card image is insufficient to select a rate.
CMS SNF Billing Reference directs providers to verify MA eligibility, coverage and payment with the plan. Accordingly, the matrix below translates already reviewed terms into operational behavior. It does not interpret a contract or decide coverage for a resident.
A filled matrix reveals what a blank template hides
Assume two fictional facilities, North and South, and a fictional plan product P. Qualified contracting staff have confirmed the following flat per-diem terms. There are no other adjustments in this deliberately simplified pricing test.
| Configuration row | Facility/product | Service-date range | Invented daily amount | Evidence and deployment scope |
|---|---|---|---|---|
| N1 | North/P | Through November 14, 2026 | $500 | Reviewed original terms; retain for historical work |
| N2 | North/P | From November 15, 2026 | $525 | Reviewed North-only amendment |
| S1 | South/P | Entire test period | $480 | Existing South terms; amendment does not apply |
Expected outputs follow directly:
- North, November 14: $500. North, November 15: $525.
- South on either date: $480.
- North, November 14–16: one day at $500 plus two at $525 = $1,550.
- South for the same three dates: 3 × $480 = $1,440.
If a shared payer-profile edit charges South 3 × $525 = $1,575, it introduces an unsupported $135 change. If North's whole period uses the new rate, its $1,575 estimate is $25 too high for these assumptions. A successful import is therefore insufficient: the boundary and unaffected facility must both pass.
Store the interpretation approval separately from the implementation check. Contracting can approve N2 correctly while a system administrator deploys it incorrectly to South.
Add operational terms without confusing them with the rate
Each matrix row also needs a reviewed source for billing destination, identifiers, authorization process, required documentation and amendment handling. Where terms are unknown, use an unresolved state with a specific question. Do not let an unconfirmed product inherit the nearest familiar profile.
Network status is a separate evidence field. Verify the same facility/product combination and date; retain conflicting sources until resolved. An agreement for North does not prove South participates. An authorization decision does not by itself establish the contract rate or resolve a network discrepancy.
A concise configuration record can identify the source clause, approved operational meaning, local setting, test case and result. Confidential terms belong in the authorized working record, not an unrestricted demonstration packet.
Keep the two claim purposes separate
Noridian SNF and Medicare Advantage Plans describes a payment claim to the MA plan and an informational claim to the MAC for covered MA SNF stays, supporting benefit-period information. Its detailed instructions point to Claims Processing Manual Chapter 6, section 90. Use the applicable MAC process for actual submissions.
| Work item | Expected cash in this model | What establishes completion |
|---|---|---|
| Plan payment claim | Based on reviewed contract and adjudication | Plan response, remittance and relevant reconciliation |
| Required MAC informational claim | $0 | Its own required processing evidence |
A paid plan account can still have an open reporting task. Conversely, MAC information-only processing does not show that the plan received a payable claim. Count both as work items where appropriate; do not add both to the cash forecast.
Apply a late plan change without rewriting history
Suppose new product Q evidence arrives November 18 with a reviewed November 16 effective date. Preserve the date learned and the effective date separately. Identify November 16-and-later service records, open authorizations, estimates and submitted versions for the relevant review.
The old submission remains what was actually sent. Its correction follows the appropriate process; updating today's payer cannot retroactively transmit that correction. Do not assume an earlier authorization transfers or disappears automatically—continuity protections and plan facts require their applicable review.
The deliverable for finance is a dated selection record that can explain North's $1,550 and South's $1,440, plus any unresolved transition or reporting work. That is a concrete prerequisite for consistent contract billing across facilities.
Questions & answers
Can one corporate payer profile represent every SNF contract?
Only when the reviewed scope is actually shared. Facility identity, exact product, service date and amendments can produce different applicable terms.
Does an MA plan payment close all Medicare reporting work?
No. Applicable MAC informational reporting has a separate purpose and needs its own processing evidence, independent of the plan payment.
Should a new contract rate reprice old service dates?
Only if the reviewed amendment supports that effective scope. A current rate default should not silently replace the terms used for historical services.
Primary sources
Use the cited source and its applicable version when making a facility-specific decision. These guides explain operational evaluation methods; they are not individualized clinical, coding, or legal advice.