# Conditional Payment Review Services > Line-by-line Conditional Payment Letter review against the medical record: each charge classified injury-related or unrelated, cited to its source page. Canonical page: https://medrecords.ai/solutions/lien-resolution-conditional-payments/ --- [Home](https://medrecords.ai/) ›[Solutions](https://medrecords.ai/solutions/) ›[Settlement Compliance](https://medrecords.ai/solutions/settlement-compliance/) ›Lien Resolution and Conditional Payments CONDITIONAL PAYMENT REVIEW SERVICES ## Every line on the Conditional Payment Letter, matched to the record — or disputed. Conditional payment review services read every line of a Conditional Payment Letter against the treatment record: a five-hundred-line CPL against as many as 1,200 pages. Each charge is classified injury-related or unrelated, with the page behind the call, assembled as the line-by-line dispute the recovery contractor answers in writing. [Test a file ](https://medrecords.ai/test-a-file/?src=lien-resolution-conditional-payments) [Book a demo](https://medrecords.ai/demo/?src=lien-resolution-conditional-payments) Click any row → the source page it cites Charge review · Case #IME-4812 cited Adams, Timothy · CPL and treatment production 342 pp / 2 packets received logged 11 duplicate pages removed free p.140 — wrong patient quarantined Pages 342 Packets 2 Cited 100% ### The rulebook is statutory. So is the referee. We do not build for a case type until we can name the standard that defines a correct output and the person who grades the file against it. In Medicare Secondary Payer work both are written down, and the grading happens one line at a time. That is the rare case where an AI read can be checked against something objective: the recovery contractor's written response tells you, charge by charge, whether the read was right. The rulebook and the referee The rulebook - 42 USC §1395y(b) and 42 CFR Part 411 — the Medicare Secondary Payer statute and its recovery rules, including the §411.37 procurement-cost reduction - Arkansas Dept. of Health v. Ahlborn (2006) and Gallardo v. Marstiller (2022), which frame what a Medicaid agency can reach in a settlement - ERISA §502(a)(3) and US Airways v. McCutchen, which put the plan document at the centre of a self-funded plan's reimbursement claim - Section 111 mandatory insurer reporting, which is how the conditional payment file gets opened in the first place The referee - The BCRC or the CRC, which accepts or rejects every disputed line in writing - A five-level appeal ladder above that first written response - An exact per-line accuracy score on every file: a charge either comes off the demand or it does not - Failure to resolve, which exposes the parties to double damages under the MSP statute Conditional payment resolution is priced at $250–$750 flat per claimant, or 20–33% of the reduction obtained Flat 10¢/page here, duplicates free Charge review · Case #IME-4812 cited 100% Production342 pp / 2 packets · 11 deduplicatedlogged Treatment course7 visits, improving since 4/02cited Scan qualityFax-degraded pages, handwritten notesread anyway Wrong-patient pagep.140 pulled out of the charge setquarantined Every charge cited · no dispute filed on your behalf What the file actually looks like ### Hundreds of charge lines against hundreds of pages. A lien file runs 200 to 1,200 pages, around 700 in the middle of the range, and it almost never arrives as one clean production. Provider records come in waves, the payer's charge listing arrives separately, and the two have to be reconciled against each other before a single line can be called related or unrelated. What makes it slow is not the volume so much as the condition: fax-degraded scans, handwritten progress notes, the same discharge summary appearing in three productions, and occasionally a page that belongs to another patient entirely. Scale, estimated An estimated 300,000 to 450,000 lien files a year move through resolution vendors and firm lien departments. Why it recurs Roughly 35% to 45% of mass tort claimants are Medicare or Medicaid beneficiaries, so the same read repeats across the inventory. What we'd build with you ### Four steps, starting with one real file. 01 #### Send one real file A Conditional Payment Letter and the treatment records behind it, in whatever shape they arrived in. In the demo case that is 342 pages across 2 packets, with a wrong-patient page quarantined before the read starts. 02 #### We return the read Every charge line classified injury-related or unrelated, with the date of service, the provider, and the page that supports the call. You check it against what your own analyst would have written. 03 #### We scope the build Charge volumes, how many productions a typical claimant generates, your dispute template, and the export your team already files. If the case type is not buildable at your volumes, we say so at this step. 04 #### You run it Your lien department runs the file at its own volume. Your analysts decide which lines to dispute and sign what goes to the recovery contractor. The platform never files, submits, or negotiates anything. Audit trail · Case #IME-4812 exportable 08:12Production received · 342 pp / 2 packetssystem 08:3111 pages deduplicatedsystem 08:44p.140 flagged — wrong patientsystem 08:54Charge review complete · cited 100%system 09:20Read reviewed · citations verifiedanalyst 09:26Read exported · dispute assembled off-platformanalyst Every access logged · file deleted 30 days after delivery Also in settlement compliance: [MSA record review](https://medrecords.ai/solutions/medicare-set-aside-record-review/) and [rated-age submission packets](https://medrecords.ai/solutions/rated-age-submission-packets/) . Why Medrecords AI ### The rules the platform never breaks. EVERY LINE CITED CASE #IME-4812 · ADAMS, T.342 pp 2/14 — ER visit, right knee p.4 4/18 — arthroscopic surgery p.61 p.140 — wrong patient quarantined Medrecords AI Read every page · cite every line #### HIPAA, under a signed BAA Every file is handled under our Business Associate Agreement, from the first byte. #### Never trains a model Your records are never used to train any AI model — ours or anyone else's. #### Every line cited If we can't cite it, we don't say it. Every sentence links to its source page. #### Deleted after delivery Files are deleted 30 days after delivery, with a full audit log of every access. Powered by the platform ### Four capabilities behind every charge line. The conditional payment read is one deliverable of the same platform that reads, sorts, and cites the whole record. [ #### Claims Billing Ledger Dates of service, providers, and billed lines pulled into one ledger you can sort against the Conditional Payment Letter. IN ACTION · 342 pp / 2 packets → one reconcilable ledger ](https://medrecords.ai/product/claims-billing-ledger/) [ #### Treatment Relatedness Each treatment tied back to the accepted injury or flagged as unrelated, with the page that shows which of the two it is. IN ACTION · every charge → injury-related or unrelated ](https://medrecords.ai/product/treatment-relatedness-compensability/) [ #### Medical Chronology The treatment timeline builds itself from every production, so a charge date always has the visit behind it. IN ACTION · 7 visits, improving since 4/02 ](https://medrecords.ai/product/chronology/) [ #### Verifiable AI Citations If we can't cite it, we don't say it. Every classified line links to the page range it came from. IN ACTION · every disputed line → its source page ](https://medrecords.ai/product/citations/) FAQ ### Conditional payment review, answered. No. We classify each line on the Conditional Payment Letter as injury-related or unrelated against the treatment record, and we cite the page behind every call. That classification is a documented reading of the chart, not a legal determination. Which lines your team actually disputes, and how the dispute is argued to the BCRC or the CRC, stays with the lien resolution team. This page describes the review service: you send the Conditional Payment Letter and the records behind it, and we return the line-by-line read. The same reading runs on the Medrecords AI platform, which you can also license and operate yourself. The output is the same either way, with every charge classified and every classification cited to a source page. Every charge the record does not tie to the accepted injury is flagged as unrelated, with the date of service, the provider, and the page showing what the visit was actually for. Those lines become your dispute packet. Removing them changes the conditional payment total that the 42 CFR 411.37 procurement-cost formula is then applied to, so each one is cited rather than asserted. We assemble the record side of both: the charges tied to the accepted injury, the treatment they document, and the pages behind them. The plan-language argument under ERISA 502(a)(3) and US Airways v. McCutchen, and the allocation argument under Ahlborn and Gallardo, are legal work product. We organize and cite the medical facts; counsel builds the argument. No to both. Medrecords AI does not retrieve records from providers or facilities, and it does not file, submit, or transmit anything to the BCRC, the CRC, a Medicaid agency, or a plan. You bring the Conditional Payment Letter and the records you already have, we return the line-by-line read, and your team files it. ### Send one file. We'll tell you what we can read. No obligation. If the case type is buildable we'll scope it; if it isn't, we'll say so. [Test a file ](https://medrecords.ai/test-a-file/?src=lien-resolution-conditional-payments) [Book a demo](https://medrecords.ai/demo/?src=lien-resolution-conditional-payments) [All settlement compliance work →](https://medrecords.ai/solutions/settlement-compliance/) [See every case type we process →](https://medrecords.ai/solutions/case-types/)