Quick answer
Freeze the reviewed cost-report version, reconcile the electronic file with its signed certification and supporting schedules, and submit through the applicable filing route. Retain the full package and receipt, then monitor MAC acceptance or rejection separately. Successful transmission starts the acceptance review; it does not establish that the report was accepted or that its costs are allowable.
A finished workbook is not a finished filing
A fictional SNF's preparer completes its annual cost report on Monday. The officer signs the certification on Tuesday. On Wednesday, a late payroll correction changes the electronic cost report, but the filing team attaches Tuesday's signature page. The package now contains two versions even though every file is individually readable.
The annual filing task should therefore have a controlled release point after preparation and review. The CMS MCReF overview states that successful submissions are immediately received by the MAC and begin a 30-day acceptance process. Receipt, acceptance and later settlement are different milestones.
Confirm the period and the package
Start with the facility identifier, cost-report beginning and ending dates, applicable form version and filing obligation. The qualified preparer confirms the due date and any supported exception or extension. The business office should not derive the annual due date from an internal monthly-close calendar.
The following original release record makes the fictional mismatch visible:
| Package component | Saved version | Release finding | Resolution |
|---|---|---|---|
| Reviewed trial balance and adjustments | Version 4 | Matches final reviewer notes | Freeze reference |
| Electronic cost report | Version 5 after payroll correction | Differs from signed package | Reconcile changed values |
| Signature page | Version 4 | Does not correspond to final ECR | Obtain correct certification |
| Bad-debt support | Version 3 | Unchanged; matches final report | Retain reconciliation |
| PS&R support | Dated final extract | Cutoff and exceptions explained | Retain parameters and bridge |
The CMS MCReF FAQ requires the ECR encryption code on the signed page. The reviewer compares the actual generated file and certification rather than accepting matching filenames as proof.
Resolve a late change before signing off
Assume the payroll correction changes reported salary cost by $12,000. The preparer documents the affected worksheets, checks downstream totals and updates the review record. The officer reviews the completed package and signs the corresponding certification through the permitted process.
The filing team now has one definitive submission version. Earlier versions remain in the controlled archive with their status clearly marked. A later reader can identify the report that was actually filed without guessing whether “final,” “final2” or “signed-final” is authoritative.
Supporting schedules also need consistency. A bad-debt total that matches an obsolete report can be wrong even if its arithmetic is correct. The release check compares schedule totals and period identifiers to the final ECR, then records any intentionally explained difference.
Follow receipt through acceptance
The submitter retains the outgoing package, submission timestamp and receipt. The filing register then opens a separate acceptance task. A portal acknowledgement answers whether a transmission arrived; it does not answer whether the MAC accepted the package.
If the MAC rejects it, link the rejection reason to the affected component, assign the correction and record the replacement submission. Determine the consequences and applicable timing with the preparer and contractor. Do not assume that every rejection preserves timely-filing status or that an internal completion date substitutes for a valid filing.
If the MAC accepts it, save that evidence and close the acceptance task. Keep future audit requests and settlement decisions in separate records linked to this filed version. This prevents a later amended report from silently replacing the original record of what the officer certified.
Test retrieval, not just upload
A useful platform demonstration asks a colleague to retrieve the filed ECR, matching signature, supporting schedule, receipt and acceptance evidence. Then introduce a fictional amendment and confirm that the original package remains identifiable.
The completed output is a period-correct, internally consistent filing archive with a documented acceptance outcome and clear unresolved items. It supports the preparer's work and later reimbursement review; it does not certify that every claimed cost is allowable or predict the final settlement.
Questions & answers
Does successful MCReF submission mean the cost report was accepted?
No. CMS says successful submission reaches the MAC and begins its 30-day acceptance process. Preserve the later acceptance or rejection result.
What if the preparer changes the report after the officer signs?
Reconcile the changed electronic file and signature evidence before release. The signed page must correspond to the submitted ECR version; an old signature page should not be attached to a newly generated file.
Does acceptance settle the reimbursement amount?
No. Acceptance concerns the filing package. Audit and settlement can produce later adjustments and determinations.
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.