Wrap payment reconciliation: the working method.
Every qualifying Medicaid encounter entitles an FQHC to its certified PPS rate. The MCO pays less. The state owes the gap. This guide is the working method for finding every encounter where that gap was never paid: the mechanism, the four failure modes, and the five-step worksheet that pulls the money back.
The mechanismOne encounter. Two payers. One entitlement.
The wrap exists because federal law protects the FQHC payment floor. An FQHC is entitled to its state-certified Prospective Payment System rate for every qualifying encounter. When a Medicaid managed care organization is in the middle, the MCO pays its contracted fee schedule first. That contracted amount is almost always below the PPS rate. The state Medicaid agency owes the difference, the wraparound payment, for each qualifying encounter.
Two properties of this mechanism cause almost all the trouble. First, the two payments arrive on different clocks: the MCO interim typically posts within weeks of the visit, while the state wrap settlement can land two to four quarters later, in a different remittance format, rarely matched to the same encounter ID. Second, the entitlement is per encounter, not aggregate. If a qualifying encounter never enters the state's reconciliation pool, its wrap is not delayed. It is simply never paid.
Same entitlement, different plumbing.
How the state pays the wrap differs by state. Some settle claim by claim as wrap claims are submitted; others run quarterly or annual reconciliations against MCO encounter data; lookback and appeal windows differ too. The method in this guide is state-agnostic: it produces an encounter-level variance file you can feed into whichever settlement process runs. Confirm your state's cadence and deadlines against its Medicaid provider manual before you submit.
Where the money leaksThe four failure modes behind missed wrap.
Wrap underpayment is rarely one dramatic error. It is four quiet mechanisms compounding. Every wrap recovery engagement we have run maps its findings back to these four.
Encounters never submitted for wrap.
The bundled encounter claim, commonly T1015, is rejected by the MCO because its adjudication system is built for fee-for-service and does not understand a bundled encounter. The visit never enters the MCO's encounter data, so the state never sees it, and the FQHC loses the interim and the wrap together.
MCO encounter data mismatches.
Your billing system, the MCO's encounter submission to the state, and the state's reconciliation file are three different datasets. Encounter IDs, member IDs, and service dates drift between them. Every row the state cannot match to your claim is wrap that silently drops out of the settlement.
Retro eligibility churn.
Medicaid eligibility changes retroactively. A member is reassigned between MCOs, or between managed care and fee-for-service, after the visit happened. The encounter gets attributed to the wrong payer bucket, the original payment is recouped, and the wrap calculation runs against a payer that no longer owns the encounter.
Rate-year boundary errors.
The PPS rate changes at the rate-year boundary and can be adjusted for change of scope. Encounters near the boundary get settled against the prior year's rate, and the underpayment per encounter is small enough that nobody flags it. Across thousands of encounters, small per-visit deltas become material dollars.
The working methodFive steps. One variance file.
This is the reconciliation run as a worksheet, in order. Each step produces a concrete artifact. The final artifact, the encounter-level variance file, is what you submit, appeal, and track until it becomes cash.
Build the encounter universe.
Pull every claim and remittance for the reconciliation window from your 837 submission files and 835 remittance data. Filter to qualifying encounters: bundled encounter lines (commonly T1015 plus qualifying visit codes) for Medicaid managed care members. This list, not your charge report, is the denominator for everything that follows.
Match MCO payments to encounters.
Attach every MCO payment, adjustment, and recoupment from the 835s to its encounter row. Flag the rows with no payment at all: those are usually rejected T1015 lines that never entered the wrap pool, your failure mode 01 population. Re-run eligibility as of date of service on anything that looks misattributed.
Compute the per-encounter shortfall.
For each encounter, subtract total MCO payment from the certified PPS rate for that site and that rate year. Then compare the computed wrap against what the state actually settled for that encounter, if anything. The difference is your variance. Positive variance is money the state still owes.
Submit and appeal the variances.
Route each variance to its fix: resubmit encounters missing from the state's pool, appeal MCO rejections with payer-specific templates, rebill retro-eligibility encounters to the payer of record, and file the corrected wrap reconciliation with the state for each open rate year within its lookback window.
Track by rate year, forever.
Wrap reconciliation is not a project, it is a cadence. Keep the worksheet keyed by rate year so late settlements land against the right entitlement, watch the T1015 denial rate weekly, and report NCR against PPS by payer class to leadership. When the engine runs weekly, backlogs stop forming.
The arithmeticA worked example, one quarter, one site.
Here is the whole method in one clean ledger. The numbers are deliberately round so the mechanics are visible. They are illustrative only: your PPS rate, MCO schedules, and volumes will differ.
| L1Certified PPS rate, this site, this rate year | $185.00 |
| L2Average MCO payment per qualifying encounter | $92.40 |
| L3Wrap owed per encounter (L1 minus L2) | $92.60 |
| L4Qualifying encounters this quarter | 1,000 |
| L5Wrap entitlement this quarter (L3 × L4) | $92,600 |
| L6Encounters missing from the wrap pool (8% of L4: rejected T1015, mismatches, retro churn) | 80 |
| L7Wrap silently lost this quarter (L6 × L3) | ($7,408) |
| Annualized leak if nobody reconciles (L7 × 4) | $29,632 |
The measurement lensWhy GCR hides the wrap.
Most billing dashboards lead with gross collection rate: collections divided by charges. For an FQHC under PPS, that lens is distorted by design, because charges have no fixed relationship to the PPS entitlement. A center can post a comfortable GCR while a third of its wrap goes uncollected.
Collections vs charges
Charges are an artifact of the chargemaster, not of the entitlement. PPS reimbursement makes GCR structurally noisy for FQHCs: it moves when the chargemaster moves, and it cannot distinguish a paid encounter from an encounter whose wrap never arrived. A missed wrap payment barely dents it.
Collections vs entitlement
Net collection rate against the PPS entitlement, by payer class, measures what you collected against what the law says you are owed. Interim plus wrap, divided by encounters times PPS rate. When wrap goes missing, this number drops immediately and points at the payer class where the leak is.
This framing is developed in full, with the report definitions and the payer-class breakdowns, in our FQHC NCR framework white paper.
Proof it worksThe method, run for real: $2.1M back in 11 weeks.
A 7-site FQHC network was carrying an 18-month wrap backlog its CFO had largely written off as bad debt. ASP-RCM ran exactly this method: audit and map, rebuild the encounter ledger, appeal the T1015 rejections, and resubmit the state wrap files for the trailing two years. The client is anonymized under a reciprocal confidentiality agreement; the numbers are real.
Go deeperThe rest of the FQHC shelf.
FQHC revenue cycle services
What ASP-RCM runs for FQHCs: PPS and wrap, sliding fee, 340B-adjacent billing, credentialing, and reporting.
VISIT /FQHC/ →The FQHC PPS rate in 2026
Where the certified rate comes from, how change of scope moves it, and why the rate year matters to every wrap dollar.
READ THE GUIDE →The FQHC NCR framework
The full measurement framework: NCR against PPS by payer class, and why GCR misleads FQHC boards.
READ THE PAPER →$2.1M of wrap recovered
The anonymized 7-site engagement behind this guide: the 11-week plan, the T1015 fix, and the scorecard.
READ THE CASE →Common questionsWrap payments, answered.
What is a wrap payment?
How is the wrap amount calculated?
How often should FQHCs reconcile wrap payments?
What causes wrap underpayment?
How far back can you recover missed wrap?
Want to know what your unclaimed wrap is worth?
Send 6 months of remittance data, your T1015 encounter log, and your state wrap reconciliation reports. We run steps 1 through 3 of this method and return a written wrap revenue review: unpaid wrap dollars by MCO, root causes, and a recovery plan by rate year. Yours to keep.