"Closed Without Payment" Under Scrutiny: What the Senate Letters Mean for Your Closing Notes
On October 2, 2026, Sens. Elizabeth Warren and Josh Hawley sent letters to several of the largest US personal lines insurers asking for 10 years of homeowners and auto claims data. Letters to State Farm, Allstate, USAA, Liberty Mutual, Farmers and American Family are posted on the Senate Banking Committee website. The focus is a single number: how many claims close without a payment, and why.
For adjusters, this goes beyond Washington politics. The letters ask about closing reasons, reversals after a dispute and incentive plans tied to claim outcomes. Those are things that show up in your file notes. Here is what happened, how the industry is pushing back, and how to write closing documentation that holds up when someone outside the claim reads it.
General information, not legal advice. Policy language, state law and your carrier's guidelines control.
What the senators asked for
The State Farm letter is a good template for the whole set. It asks the company, by October 16, 2026, for:
- Yearly counts and percentages of homeowners and auto claims paid versus closed without payment over 10 years, broken down by peril and by reason for nonpayment: below deductible, policy exclusion, formal denial, policyholder withdrawal, or other.
- How many unpaid or denied claims were appealed or disputed, and how many of those were later paid or reversed.
- The main factors behind the rise in unpaid claims, with a quantified estimate of each.
- Material changes to claims-handling guidelines since 2015, and the reasons for them.
- Any compensation, bonus or performance programs for employees, contractors, adjusters or managers that use metrics tied to payments, severity, loss ratios or denial rates.
- How AI, predictive analytics or automated tools are used in claims, and what safeguards are in place.
- Whether the company will commit to publicly reporting annual claims data.
Note who appears in item 5: contractors and adjusters, not only staff. If you work on an IA firm's fee schedule or a carrier's vendor scorecard, the general topic of how claim outcomes connect to pay is now part of a congressional inquiry.
As of October 29, 2026, we have not found any public carrier responses to the letters. State Farm told Insurance Journal it was reviewing the letter and that a claim closed without payment doesn't necessarily mean coverage was denied.
The number behind it: 44%
The letters lean on Wall Street Journal reporting. As the senators summarize it, a WSJ analysis found that several large insurers, State Farm among them, did not pay on 44% of homeowners claims resolved the prior year, up from 36% a decade earlier. An August WSJ analysis put the auto figure at 45% for closed liability and medical claims.
The industry's response
NAMIC and the Insurance Information Institute argue the figure blends very different outcomes. According to Insurance Journal's reporting, NAMIC's position is that a closed claim is not a denied claim. Many unpaid closures are below the deductible, involve likely-excluded flood losses, are withdrawn, are filed twice or are missing documents. NAMIC said insurers closed 7.35 million homeowners claims with payment in 2024. In a letter about the WSJ's auto analysis, its CEO also argued that the method counted claims paid by another driver's insurer and left out claims still open at year-end.
Both sides are making a point about the same thing: the closing reason. If "closed without payment" is going to be a public metric, the reason code on each file is what separates "insured withdrew a duplicate" from "carrier said no."
Florida just showed how this plays out
Hurricane Isaias is a live example. In Florida OIR data reported in mid-October, about 12% of Isaias claims had closed, nearly all without payment. The most common reason was a new OIR category this year, "administrative reasons," which can cover withdrawn claims, duplicates and insureds the carrier couldn't reach. By the late-October snapshot, nearly 8,500 claims had closed without payment against just over 3,500 closed with payment. We broke down those numbers in Hurricane Isaias by the numbers.
Much of that was likely legitimate: below-deductible damage and tree claims where the tree never hit the house. But a catch-all category is exactly the kind of number that draws questions, and the only thing that answers them is the documentation on the individual file.
Oklahoma: closing practices in court
Oklahoma shows the same scrutiny moving from data requests to litigation. These cases involve allegations, not findings.
- State Farm. On June 24, 2026, Attorney General Gentner Drummond filed suit in Cleveland County District Court. The AG's release alleges an internal "Hail Focus Initiative" designed to reduce roof replacement approvals, undisclosed internal standards and outcome-oriented engineering reviews. Separately, in private bad-faith litigation against State Farm, internal documents unsealed by a Comanche County judge reference "touchless claims" plans using AI and automation. State Farm rejects the allegations, calls the plaintiffs' characterizations false and says each claim is evaluated on the facts of the loss and the coverage purchased. Local outlets reported a trial is scheduled for December.
- Allstate. In July 2026 the AG sued Allstate, alleging a "Disaster Payment Minimization Scheme" that relied on third-party inspectors and restrictive standards not disclosed to policyholders. Allstate did not provide a public statement in early coverage.
The practical point for IAs: when litigation targets internal guidelines, the people who applied them, including field and third-party inspectors, may be asked what they saw and why they concluded what they did. Your notes are your best witness.
How to write closing and denial documentation that holds up
None of this changes the policy or the facts of a loss. What it changes is who might read your file later: a regulator, a congressional staffer reviewing aggregate data, an appraisal panel or a plaintiff's attorney. Write for that reader.
Use the right reason, and only one primary reason
Pick the closing reason that is actually true, and don't let "administrative" or "other" absorb files that have a better answer. If damage was below the deductible, close it as below deductible. If it's an exclusion, name the exclusion.
A reason-by-reason checklist
| Closing reason | What the file should show |
|---|---|
| Below deductible | The deductible amount and type (flat or percentage), the covered estimate (RCV and ACV), the math, and a statement that the estimate was shared with the insured |
| Exclusion or limitation | The specific policy provision by form and section, the facts that trigger it, and photos tying the damage to the cause |
| No covered damage found | What you inspected, how (roof walk, interior, test squares), what you found, and photos of both the claimed areas and the comparison areas |
| Withdrawn by insured | Who withdrew it, the date, the method (call, email, portal), and ideally a written confirmation sent back to the insured |
| Duplicate | The surviving claim number and a note that the files were merged or linked |
| Unable to contact | Every attempt with date, time, method and number or address used, plus any closing letter sent |
Separate what you observed from what a guideline says
Write what you saw, then what the policy says, then your conclusion. If a carrier guideline influenced the decision (for example, a repairability standard), say so plainly and note that you applied it. Don't present a guideline's output as your own field observation.
Document your review of any automated output
If a photo-triage tool, aerial report or AI scope fed into the decision, note that you reviewed it and whether you agreed. The senators asked specifically about AI safeguards, and regulators in several states expect a human to own consequential claim decisions.
Note disputes and reversals honestly
If the insured disputes the decision and new information changes the outcome, document what changed. A reversal backed by new facts is good claims handling, not an admission. The letters treat reversal rates as a data point, and the file should show why each one happened.
Be consistent
Consistency across files is what makes your work defensible in aggregate. Standardized estimate structures help with this; it's one reason many adjusters build or buy Xactimate macros and templates rather than starting each scope from scratch.
What to watch next
- Carrier responses. The deadline was October 16. Watch for the senators to publish summaries or follow-up letters.
- Public reporting. The letters ask carriers to commit to annual public claims data. Any carrier that agrees, or any state that requires it, would make closing codes a public scorecard.
- Florida OIR updates. Watch how the "administrative reasons" bucket changes as Isaias files mature.
- Oklahoma. The AG cases and the private State Farm litigation are worth following for what internal claims standards come out in testimony.
For context on how pressure on carriers is reshaping who handles files, see our earlier piece on the quiet crisis in US property claims.
Status as of October 29, 2026. General information, not legal advice; policy language and state law control.