2027 Medicare Same-Day Payment Proposal: Test Your Practice Exposure
The 2027 Medicare same-day payment proposal calls for a claim-level exposure test before a practice changes its budget. Identify potentially affected visits and procedures, compare their current allowances with a proposed-policy scenario, and document the difference. Keep this planning exercise separate from current billing instructions, booked revenue, and patient scheduling decisions.
Why now: the comment window has closed
CMS's 2026-07-14 proposed-rule fact sheet describes a payment reduction when a separately identifiable office or outpatient evaluation and management visit accompanies a procedure with a 0-, 10-, or 90-day global period, involving the same physician or practice on the same day. The highest-valued service would receive full payment; other affected services would receive half. These are proposed changes, not instructions to change today's claims.
The CMS regulation record, published 2026-07-16, lists September 14, 2026 as the comment deadline. For a practice preparing its next operating budget, September 15 is a useful checkpoint: establish exposure, identify unresolved interpretation questions, and assign someone to update the model when final policy becomes available.
The finance question is specific: how much of the practice's expected activity consists of combinations that could receive different payment? A total Medicare revenue number cannot answer it. Neither can a list of procedure codes without the visits, dates, clinicians, and payment history needed to interpret those codes.
The workflow below is a suggested management planning method. It starts with a reproducible population of encounters and ends with an approved sensitivity. It does not establish claim eligibility or replace coding review. Its purpose is to give the administrator a number whose assumptions can be inspected before staffing, spending, or distribution decisions depend on it.
Build an encounter population that a reviewer can reproduce
Start with a recent, sufficiently mature service period. Three months may be a workable first pass, but the revenue cycle manager should determine whether the claims have developed enough payment history. Record the first and last service dates, extraction date, included entities, payer scope, and treatment of unresolved claims. A report with changing boundaries cannot support a stable comparison.
Request claim-line identifiers, a protected patient linkage key, service date, billing group, rendering clinician, procedure code, modifiers, units, place of service, payer, allowed amount, and adjudication status. Keep identifiable claim detail in the approved billing environment. The finance summary usually needs encounter counts and aggregated dollars, with controlled references back to supporting records.
Group activity before calculating a reduction
A candidate encounter group should bring together relevant services for the same patient and service date within the reviewed practice scope. Don't assume one claim number contains every related service. Conversely, don't combine every encounter within a corporate parent merely because several practices share an accounting owner. Ask the coding lead to document the grouping boundaries.
Use modifiers as review signals rather than a complete population definition. Have the coding lead identify potentially relevant visit and procedure combinations and distinguish clear inclusions, exclusions, and unresolved cases. A modifier search can accelerate discovery, but it cannot establish all the conditions required for a reliable payment simulation.
Deduplicate corrected submissions, reversals, and resubmissions. Retain the original identifiers and show which record represents the current adjudication. Otherwise, a single encounter can appear several times and inflate the number of exposed services. Make unresolved or partially paid encounters visible in a separate queue instead of silently treating them as zero-value services.
Keep the baseline and exclusions visible
Reconcile the selected claim population to the billing system's control totals. Explain differences caused by date basis, payer filters, corrected claims, or immature adjudication. Then connect the billing summary to the accounting period through the normal revenue reconciliation. A service-date report and a posting-date ledger will often require a bridge.
Give excluded populations names and amounts. For example, a practice might keep commercial contracts, unreviewed payer arrangements, and unresolved claims outside the first sensitivity. Their exclusion means the estimate is bounded, not that they have no possible exposure. Include an owner and resolution date for every material open population.
Calculate the incremental effect with a worked example
Use the same underlying activity in the baseline and proposal scenario. First isolate the payment interaction being tested. Keep volume, service mix, and other rate assumptions constant so that the result answers one question. Broader reimbursement and volume changes can be layered into the operating budget afterward with separate explanations.
The following fictional example illustrates arithmetic only. It uses invented dollar amounts, assumes the coding lead has confirmed the combination belongs in the modeled population, and ignores other payment adjustments. It is not a fee schedule, claim-pricing instruction, or estimate of the effect on a particular specialty.
| Illustrative service | Baseline allowance | Scenario treatment | Scenario allowance | Change |
|---|---|---|---|---|
| Higher-valued procedure | $200 | 100% of modeled allowance | $200 | $0 |
| Accompanying visit | $100 | 50% of modeled allowance | $50 | -$50 |
| Total encounter | $300 | Combined result | $250 | -$50 |
For this example, the encounter reduction is $50, or 16.7% of its $300 baseline. If the practice expects 120 identical, reviewed encounters in a month, the modeled allowance difference is $6,000. It would be incorrect to reduce all practice revenue by 50%, because the calculation concerns a defined service combination.
It would also be incorrect to assume every historical accompanying visit currently receives the full modeled amount. Actual claims may already reflect adjustments. Build the real comparison from the reviewed current-payment baseline and an explicitly defined proposed-payment method. If a simple formula cannot represent an interaction, place that case in the exception queue for specialist review.
Separate exposure from confidence
Report at least three quantities: the value of the reviewed population, its modeled incremental difference, and the value still awaiting interpretation. A single total hides how much of the result depends on unresolved cases. Management can then judge whether the estimate is sufficient for a provisional contingency or needs more work.
Do not multiply a short sample by twelve without checking seasonal activity, clinician availability, and expected service mix. Build the annual extension from planned monthly encounter counts. Preserve the original sample result so that changes caused by annualization remain distinguishable from changes caused by payment assumptions.
A useful output might read: 'Reviewed combinations imply a $6,000 monthly allowance reduction at unchanged activity; unresolved combinations are excluded and listed separately.' That sentence communicates a bounded sensitivity. It does not imply the proposal is final, the estimate is a booked loss, or every dollar of allowance would otherwise have been collected.
Accounting controls: source data, calculation, review, and decision
Assign four separate responsibilities even when a small practice has only two people performing them. The billing team owns source data. The analyst owns the calculation. The coding lead and controller perform review within their specialties. The administrator or finance leader owns the budget decision. Record each person's name and approval date in the exposure register.
Source data: preserve the reconciliation
Keep extraction parameters, row counts, amount totals, and a reference to the approved source report. Maintain a clear link between every modeled encounter and its claim lines. If an updated extract changes the population, reconcile additions, removals, and corrections before replacing the earlier version. Retaining only the latest spreadsheet makes later questions harder to answer.
Separate gross charges, allowed amounts, payer payments, patient responsibility, contractual adjustments, and cash receipts. They represent different measures. Decide which amount drives each stage of the model and label it plainly. Mixing a gross-charge baseline with a net-payment scenario can create a large apparent reduction that is unrelated to the proposal.
Calculation: make the method repeatable
Use documented formulas or a controlled script, with stable grouping keys and explicit assumptions. Reconcile encounter totals back to service-line totals. Mark missing values as unresolved rather than substituting zero. Show negative scenario differences consistently as reductions in the planning report, and prevent presentation changes from reversing their meaning.
Test representative cases: one unaffected encounter, one simple affected combination, a corrected claim, multiple potentially related services, and an unresolved case. The expected result should come from independent review of each case. A total that looks plausible is not evidence that the population or formula is correct.
Review: separate billing interpretation from accounting treatment
The coding lead reviews scope, grouping, and payment interactions. The controller reviews reconciliation, completeness, sign conventions, and the transition into the budget. For broader review design, the existing guide to accounting controls during the close provides useful context for assigning evidence and review responsibilities.
A forecast for services not yet delivered is not an accounts receivable balance. Do not credit receivables or debit an expense simply because the model shows lower future allowances. Current transactions, revenue estimates, and receivable measurement require their own accounting assessment. Any resulting entry should have a separate rationale and approval trail.
Decision: approve a response and a revisit trigger
The decision record should state the approved scenario, contingency amount, unresolved exposure, owner, and next review trigger. Suitable triggers include final policy, a corrected source file, or a material change in planned activity. Management should be able to explain both why it acted and what evidence would cause it to reconsider.
Carry the sensitivity into the budget without losing its meaning
Present the proposed-policy difference as a separate budget assumption. Keep the existing operating plan available for comparison and show how the sensitivity affects each practice or department. Teams preparing group reports can use the same discipline described in consolidated budget versus actual reporting: consistent definitions, entity ownership, and an explainable bridge.
Separate policy effects from planned volume growth, clinician recruitment, payer mix, and collection performance. If all assumptions change together, a reviewer cannot tell which one drives the result. An optimistic volume assumption should not silently offset payment exposure. Give each assumption its own owner and supporting evidence.
Translate allowance differences into cash only after considering payer and patient collections. Cash timing depends on when services occur, when claims are processed, and when balances are collected. Apply the practice's observed collection pattern to the appropriate modeled amounts. Keep beginning receivables separate so that collections from earlier services do not receive a future-service reduction.
Monthly revenue and monthly receipts are flows over a period. Receivables and bank balances are balances at a date. The scenario should explain how those measures connect rather than adding them together. A budget can show reduced future revenue before a corresponding cash effect appears, depending on the assumptions used.
Use a short implementation cycle
In the first working session, agree on scope and extract the claims. In the second, reconcile the population and review representative combinations. In the third, calculate the sensitivity and list exceptions. Finish with a management review that decides whether the evidence supports a contingency, further investigation, or no immediate budget action.
Keep operational responses proportionate to the evidence. Review discretionary spending, forecast assumptions, and information gaps before making commitments based on a provisional estimate. Clinical scheduling and coding decisions need their own professional and compliance review; the finance sensitivity is not an instruction to change how care is delivered.
The practical deliverable is a compact management package: the reconciled population, calculation method, worked cases, unresolved items, and signed decision. When final policy arrives, update the assumptions and show the change from this version. That comparison turns September's preparation into a reusable control rather than an abandoned spreadsheet.
Frequently Asked Questions
Is the 2027 Medicare same-day payment proposal final?
No. As of September 15, 2026, CMS identifies CMS-1848-P as a proposed rule. Keep the exposure model separate from current billing instructions and replace assumptions when final policy is available.
Should we reduce all Medicare revenue by 50%?
No. Identify potentially affected service combinations, confirm their scope with the coding lead, and compare each combination with its current payment baseline. A blanket reduction would include unrelated revenue.
Can we calculate exposure from QuickBooks alone?
A general ledger total cannot identify same-patient, same-date service combinations. Use claim detail for the exposure calculation and reconcile summarized results to the accounting records.
Should the proposal trigger a journal entry?
A modeled reduction for future services does not by itself create a current journal entry. The controller should assess actual transactions and applicable accounting policy separately from planning scenarios.
To connect your reviewed practice assumptions with financial reporting across entities, explore FinBoard.
