School District Medicaid Cost Settlement Reconciliation

School district Medicaid cost settlement reconciliation ties the annual SBHS cost report to interim fee-for-service payments, the final settlement notice or 835 remittance, the general ledger posting, and the audit workpaper file. A defensible reconciliation keeps the reporting year, cost pool, RMTS allocation support, interim paid amount, Medicaid-allowable cost, federal and local share, payable or recoupment result, and current-year posting account in one spreadsheet.

That matters because the deposit is not the reconciliation. A district may receive one lump-sum payment, one recoupment notice, or one 835 transaction for services from a prior school year, but the support behind that number is spread across cost report schedules, RMTS quarter results, CPE certifications, interim payment ledgers, settlement backup, and fund restrictions. The finance office has to turn those documents into an entry that a reviewer can trace without rebuilding the Medicaid cost report from scratch.

States use different program names. A district may call the workflow SBHS, SBAP, SEMI, SHARS, LEA-BOP, SSHSP, MSBS, IEP DSCS, or simply school-based services. The forms and vendor portals vary, but the accounting problem is consistent: interim Medicaid payments during or after the service year are reconciled later to allowable cost, and the resulting payable or recoupment must be posted with its cost-pool detail intact.

This annual workflow is separate from monthly R&S or 835 claim reconciliation. Monthly work explains which claims were paid, denied, adjusted, or still pending. Annual cost settlement explains whether the district's provisional payments matched the cost methodology after payroll, contracted service, RMTS, CPE, and state settlement calculations were applied.

How Interim Payments Become a Final Settlement

Many school-based Medicaid programs do not wait until the final cost report is complete before any money moves. The district may receive interim FFS payments, monthly rates, quarterly rates, roster-based amounts, or another provisional payment during the cost reporting period. Those payments help cash flow during the year, but they are not the final measure of what the Medicaid program owes for the service period.

CMS school-based services cost reconciliation guidance says reconciled cost methodologies for school-based Medicaid services may pay interim amounts during the cost reporting period, then reconcile those interim payments to the cost of providing Medicaid services through a cost report and final cost reconciliation. In district accounting terms, the cost report is the point where provisional payment activity is compared with the allowable cost methodology.

The practical tie-out is straightforward, even when the state schedule is not. Medicaid-allowable cost, after the state's allocation methodology is applied, is compared with the interim paid amount. If allowable cost is higher, the district may receive a payable settlement. If interim payments were higher than the final allowable cost, the schedule may show a recoupment, offset, or amount due back through a later payment cycle.

CPE programs add another layer because the district or other public agency certifies eligible public expenditures that support the nonfederal share. That does not change the need for a clean reconciliation workpaper. It means the support file also has to preserve the certified public expenditure basis, the federal share, the state or local share, and the link between the cost report and the settlement calculation required by the state methodology.

District staff should treat state manuals, settlement instructions, and auditor requests as controlling for their own posting and support requirements. The reconciliation workpaper is not a substitute for that guidance; it is the finance-office record that shows how the district applied it to the documents in hand.

Build the Cost-Pool Bridge Before Reviewing the Settlement Letter

The cost settlement schedule is easier to review when the district has already organized the cost report by pool. Most programs separate some version of direct service costs, administrative costs, and, where allowed, specialized transportation costs. Direct service pools may include salaries or contracted costs for speech-language pathologists, occupational therapists, physical therapists, nurses, school psychologists, social workers, behavior staff, and aides. Administrative pools usually sit closer to Medicaid outreach, referral, coordination, or program administration. Transportation may have its own mileage, route, aide, or equipment support depending on the state.

RMTS results are the bridge between employee cost pools and Medicaid-allocable cost. A quarterly result does not just sit in the file as compliance evidence; it changes the dollars in the cost report. If a direct-service salary pool, allowable benefit cost, indirect cost component, and RMTS percentage are applied together, the settlement reviewer should be able to see how the resulting Medicaid share was calculated. When payroll support says one thing, RMTS staff rosters say another, and the cost report uses a third category, the later settlement entry becomes hard to defend.

A compact row model helps: cost pool total multiplied by the RMTS or other state allocation factor gives Medicaid-allowable cost; Medicaid-allowable cost less interim paid gives the payable or recoupment; the settlement schedule then splits that result into federal share, state or local share, and the GL posting line.

State naming does not remove the need for that bridge. NJ SEMI, TX SHARS, PA SBAP, CA LEA-BOP, NY SSHSP, OR SBHS, IL SBHS, WA SBHS, MA SBMP, MO IEP DSCS, NM MSBS, and AR SBMS all have their own manuals, portals, and timing rules. Some programs differ in cost-report cadence, interim-payment structure, or certification mechanics, such as separate SHARS cost-report timing or LEA-BOP cost-report and CPE support, but the workpaper still needs the same source-to-settlement trail from cost pool to allocation support to final payable or recoupment.

Vendor and state-system formats add another source of confusion. PCG, Fairbanks, EMS, and in-house state platforms may label the same practical concept differently, split schedules across pages, or place federal share and local share detail in separate reports. The finance office should normalize those labels in the workpaper while preserving the original source-document reference. The same discipline applies in related workflows such as school district related-services invoice review, where the accounting record is only as good as the document trail behind it.

Turn the Settlement Packet Into a Posting Workpaper

The settlement workpaper should be built as a bridge from source documents to posting. It should not be a copy of the state's PDF, a pasted screenshot of the settlement letter, or a cash receipt schedule with one line for the deposit. The useful version breaks the packet into rows that explain what the district is posting and why.

At minimum, the spreadsheet should preserve reporting year, settlement date, program name, service or cost pool, interim paid amount, Medicaid-allowable cost, federal share, state or local share, payable or recoupment, fund, account, cost center, posting date, source-document reference, reviewer, and exception status. Those columns let the finance office connect the settlement notice, 835 or remittance advice, cost report schedule, RMTS support, CPE certification, and interim payment ledger without forcing a reviewer to flip through PDFs and guess which line became the journal entry.

For one direct-service pool, the row might read like this in substance: fiscal year 2024 direct service cost pool, RMTS allocation applied, Medicaid-allowable cost calculated, interim FFS received, final payable or recoupment, federal share, local share, current-year revenue or receivable account, and the settlement schedule page that supports the line.

The reporting year and posting date need separate fields. A settlement may arrive 18 to 24 months after the services closed, so the district may post cash or recoupment activity in the current fiscal year while preserving the service year for audit support. Combining those two dates into one field makes the entry easier to post but harder to defend.

Lump-sum settlement deposits need the same treatment. A single 835 amount may contain several cost-pool components, federal and local share detail, prior-year offsets, and adjustments. Posting only the cash receipt hides the settlement logic. The workpaper should unpack the remittance into the same categories the cost report and settlement schedule use, then show the GL fund, account, and cost center for each posting line.

This is where document extraction is useful in a narrow, practical way. A district can use Invoice Data Extraction to upload settlement letters, cost-report schedules, remittance backup, and related financial documents, describe the fields needed in a prompt, and download structured Excel, CSV, or JSON output. The goal is to extract Medicaid settlement schedules into a reconciliation spreadsheet so the finance office is not rekeying multi-page backup before applying review judgment.

The same control mindset behind school district invoice three-way match controls applies here: the spreadsheet should connect the source document, the accounting decision, and the approval record. Medicaid settlement work has different documents than purchase-order matching, but the finance risk is similar when a posting line cannot be traced back to support.

Reconcile the Entry to the GL Without Losing the Service Year

The settlement posting should preserve two truths at once: the accounting activity may be recorded in the current fiscal year, while the Medicaid services, cost report, and interim payments belong to an earlier reporting year. A clean workpaper lets both remain visible. The journal entry can follow the district's current-year posting process without erasing the service-year basis that the auditor will ask for later.

A practical tie-out sequence starts with the cash receipt, 835, remittance advice, or recoupment notice. That amount should agree to the settlement total. The settlement total should agree to cost-pool detail. The cost-pool detail should agree to the cost report. The cost report should trace back to RMTS quarter support, CPE certification where applicable, payroll or contracted-service support, and the interim payment ledger. The final journal entry should then map each posting line to the fund, account, cost center, and source-document reference in the workpaper.

Payable and recoupment treatment depends on the state's instructions and the district's accounting policies, so the workpaper should avoid burying sign conventions. Negative settlement lines, prior-year offsets, state withholds, and future-payment recoupments should be labeled plainly. If a recoupment is netted against a later payment, the workpaper should still show the gross settlement result and the offset path rather than treating the reduced cash receipt as the only fact.

Fund restrictions and board reporting can also be state-specific. Some districts need to preserve restricted-account deposit support or show how Medicaid revenue was allocated across programs. Others need a board-facing explanation that separates current cash activity from prior service-year calculations. A related school finance example is BOCES bill to state-aid claim reconciliation for NY districts, where the posting is only complete when the claim support and accounting trail can be read together.

The reviewer should be able to start with the GL entry and move backward through the settlement letter, RA or 835, cost report schedule, RMTS support, CPE certification, interim payment ledger, and fund-restriction support. If that path breaks at any point, the issue belongs in the exception column before the entry is approved.

Separate Annual Cost Settlement From Monthly Claim Reconciliation

Annual cost settlement reconciliation and monthly Medicaid remittance reconciliation use some of the same source documents, but they answer different questions. Monthly school district Medicaid R&S and 835 extraction work is claim-level: which claims were paid, denied, adjusted, reversed, or left pending, and what follow-up is needed. Annual settlement work is cost-methodology-level: did the district's allowable Medicaid cost, after allocation and certification, exceed or fall short of the interim payments already received?

That distinction matters because the same payment can appear in both workflows. An interim FFS payment may be reconciled monthly to a claim file, then later included in the annual cost settlement comparison. The monthly file explains why the money arrived. The annual workpaper explains how that money was treated when the state reconciled the district's total Medicaid-allowable cost for the reporting year.

Related-services invoices and regional service agency bills can also feed the support file without becoming the settlement. A speech therapy invoice, BOCES bill, intermediate unit charge, or AEA statement may support payroll, contracted-service, or AP activity that ultimately contributes to a cost pool. That is different from the state settlement schedule that calculates payable or recoupment. Districts that process those documents separately still benefit from consistent extraction and review habits, as in a district AP extraction workflow for BOCES, IU, and AEA monthly bills.

The annual settlement workflow starts with the cost report and support schedules, then follows the state's settlement calculation to the GL entry and audit file. Keeping that boundary clear prevents the workpaper from turning into a broad Medicaid billing tracker that is too cluttered to support the final posting.

What to Review Before the Settlement Entry Is Approved

Before approval, the district should review the settlement entry from both directions. From the GL side, the posting should show the correct fund, account, cost center, posting date, and payable or recoupment sign. From the Medicaid support side, the same entry should trace back to the reporting year, settlement notice, RA or 835, cost report, RMTS and CPE support, interim payment ledger, and any state-required restriction or certification documents.

The highest-risk errors are usually not subtle writing problems in the workpaper. They are mismatches: the settlement total does not agree to the cash or 835 support, cost-pool detail does not agree to the cost report, interim paid amounts do not agree to the ledger, RMTS support is referenced by quarter but not retained, CPE certification is named but not tied to the schedule, or the service year disappears once the posting date is entered.

Sign conventions deserve their own review. A payable, recoupment, offset, and negative adjustment can look similar when they are collapsed into one settlement row. The workpaper should make clear whether the district is recognizing additional revenue, reducing a receivable, recording an amount due back, or documenting an offset against a later payment. Any exception that affects the entry should have a reviewer note before approval, not a memory of a hallway conversation.

The finished file should let a future reviewer trace school district Medicaid cost settlement reconciliation without recreating the settlement from PDFs. If the reviewer can follow the entry from GL line to source document, cost pool, RMTS or CPE support, interim payment comparison, and final settlement result, the district has a usable audit workpaper rather than a cash-posting note.