SystemMGAs & Delegated Authority

Delegated Claims Audit

Delegated claims audit on every file a TPA touches, as it moves — not a sample a year after payment

Every delegated claim reviewed, not a sample a year after payment.

See one case, screen by screen ↓
demo15sfrom a TPA payment posted in its claims system to the file reader reading it — 10:41:37 to 10:41:52
demo7checkson every note, reserve change, payment and letter: contact, coverage, reserve, authority, payment, reporting, diary
demo$24,600paid above a TPA’s settlement authority, flagged to the claims manager the minute the check was cut
target100%of delegated file events checked as they land, against a 5–7% audit sample
In short

What is Delegated Claims Audit?

Software that lets a carrier or managing agent oversee the claims its delegated administrators handle under their own authority. Delegated Claims Audit reads every file event a TPA posts — notes, reserve changes, payments, letters — as it lands and runs seven checks on it, instead of sampling files at an annual audit.

How to choose AI solutions for insurance →

Updated

The problem

Why delegated claims oversight finds the problem after the money is gone

When a carrier hands claims authority to a TPA, what comes back is a line on the monthly claims bordereau, not the file. The adjuster’s notes, the reserve history, the invoices and the letters stay in the administrator’s claims system. The carrier sees them when an auditor goes on site and pulls a sample.

That audit reads a few hundred files, months after payment. By then an overpayment has cleared, a contractor has been paid the same line twice, a reserve has sat below paid for a quarter, and a claim that should have been reported as a large loss has never reached the carrier’s desk. The finding goes into next year’s audit letter, and recovery is a negotiation instead of a credit on the next invoice.

typical5–10%of claims paid lost to leakage, today measured on samples
demo6%of one TPA’s files read at its last on-site audit — 240 files
demo≈ 7monthsfrom a reporting trigger to the carrier’s desk when it waits for an audit
Where the days go, from a TPA’s mistake to your decisionestimated
By hand210 days
With the solution2 days
  • Waiting for the next on-site audit180 → 0 d
  • Pulling and reading the sampled file10 → 0 d
  • Writing up the finding and the rule10 → 0 d
  • Getting the administrator’s answer10 → 2 d

Estimated split. The total by hand matches the ≈ 7 months the working solution shows for findings that wait for an audit; with the solution, the hero claim is flagged the morning of the payment and Bramblecrest’s answer is due two days later.

How it works

How a file event moves

Seven agents read every file event a TPA posts and run seven checks on it; the claims manager decides.

What comes in
Files in5 sources · TPA claims feeds, claim files, bordereaux, binders, authority schedules
Agents at work
File readerevent + claim + binder
Then
Coverage checker
Reserve checker
Authority checker
Payment checkerduplicates, deductibles
Then
Reportable-claim finderstarts the 2-day clock
Then
Leakage estimatorprices each finding
A person decides
Delegated claims managerholds, asks, recovers, notifies
What comes out
Flagged claims with reasons
Reportable-claim notices
Leakage and TPA scorecards
One case, step by step

One payment, from posted to held

Monday 12 October, 10:42. Bramblecrest Claims Services, a Tampa TPA handling the Coastal Habitational Property program for Harrowgate Specialty, issues a $68,400 check on a water-damage claim. Here is what happens next, screen by screen, in the working solution.

  1. 01Morning

    Five administrators, one live file stream

    Claire Whitcombe · Head of delegated claims

    Claire opens the file stream: every note, reserve, payment and letter her five administrators post, checked as it lands. The strip above it counts the file events checked today, 37 claims flagged this week and 9 reportable claims open, 3 of them overdue. Beside each TPA sits its live score per check over the last 30 days and its leakage estimate for 2026.

    “Agents read and check · you decide every hold, referral and finding.”

  2. 0210:42

    A $68,400 payment arrives, and the badges turn

    File reader and the six checkers

    Bramblecrest pays Gulfline Restoration LLC $68,400 on invoice GR-11402 — the rebuild of units 3B, 2B and 1B at Linden Court Apartments, claim HB-26-08812. Seven badges evaluate on the row in front of her. Contact, coverage and diary pass. Reserve, payment and report turn red, and the authority check is still running.

    Authority checker: “$74,600 paid against $50,000 · no referral, no Harrowgate approval on file.”

  3. 03One click

    The file note behind the red badge

    Claire Whitcombe · Head of delegated claims

    Claire clicks the authority badge. The drawer shows the payment ledger entry with “referral to carrier: none” highlighted, the adjuster’s 10:38 note — “Supervisor approved full invoice.” — the numbers, and the rule it applied: binder HSI-BA-2026-0417 §3.2, $50,000 indemnity per claim, anything above referred for prior written approval.

    “$74,600 is now paid on this claim — $6,200 on 2 Jul and $68,400 today — against $50,000 of settlement authority.”

  4. 04The claim file

    Paid against authority, reserve and estimate

    Reserve checker · Reportable-claim finder

    The claim opens on its money: $74,600 paid, $24,600 above authority, the indemnity reserve still $45,000 and $29,600 below paid. Gulfline’s $71,250 rebuild estimate of 2 Oct implies at least $83,650 incurred. The same estimate took the claim over the $35,000 large-loss notice threshold; the notice was due Tue 6 Oct and never came.

  5. 05Next

    Invoice against invoice: one line paid twice

    Payment checker

    The payment checker matched all six lines of GR-11402 against the two earlier invoices. Line 4 — structural drying, 6 days, 9 air movers, 3 dehumidifiers, $6,200 — is the same line paid on GR-10977 on 2 Jul. The leakage estimator adds $6,200 to Bramblecrest’s 2026 estimate, now $412,300.

    “Same line, paid twice. Structural drying for the same 6 days, the same 9 air movers and 3 dehumidifiers — $6,200 on 2 Jul and again today.”

  6. 06Minutes later

    A payment hold, and a request to the TPA

    Claire Whitcombe · Head of delegated claims

    Claire places a payment hold: any new payment on HB-26-08812 now needs her approval before Bramblecrest issues it. Then she opens the request drafted from the file, to Tom Gaffney, Bramblecrest’s claims team lead: a written referral, a corrected indemnity reserve and Gulfline’s credit for the duplicate drying line, by Wed 14 Oct.

    Drafted from the file — she edits it before it is sent.

  7. 0710:55

    The large-loss notice, built from the file

    Reportable-claim finder

    The notice is already drafted: policy, binder, loss, $74,600 paid, the $45,000 reserve against $83,650 incurred implied by the file, both triggers — likely above $35,000 since Fri 2 Oct, above authority today — and the open items. Claire logs it to Harrowgate claims, with a copy for Priya Raman in reserving.

    The finder drafts every notice. It never sends one without the claims manager.

  8. 08Same morning

    The duplicate, priced and on the leakage ledger

    Leakage estimator · Claire Whitcombe

    Claire records the $6,200 duplicate for recovery, and it tops the findings ledger: Linden Court, duplicate payment, “GR-11402 line 4 repeats GR-10977 line 1”. The 2026 estimate now stands at $1,083,500 on $47.8M paid through five administrators, with $312,800 recovered. Only findings the claims manager accepted are counted.

  9. 09Every day

    Every claim that must be reported to you

    Claire Whitcombe · Head of delegated claims

    The reportable list carries the nine open claims with their trigger, the date it was met, the notice due date and who it goes to. Linden Court now shows its notice logged. Cypress Hollow — a suit filed 29 Sep — and Marigold Café — open more than six months — are still overdue; two reinsurance notices for Ashgrove Re are drafted and waiting.

  10. 10Every month

    A scorecard that moves with the files

    Deshawn Ellery · Claims auditor

    The scorecards show each administrator’s pass rate per check, days to close, reserve accuracy and leakage as a share of paid. Bramblecrest’s within-authority score has dropped to 98% after today’s payment, and every one of its files is reviewed — the last on-site audit read 6%.

Who it’s for

Built for everyone who answers for a delegated claim.

The same claim, seen by the carrier’s head of delegated claims, its auditor, its reserving analyst — and the TPA’s own team lead.

CW
Claire WhitcombeHead of delegated claims, Harrowgate Specialty
Decides
Before
“By the time the audit finds it, the money is gone and the reserve was wrong for a year.”
Now
Sees an authority breach the morning the check is cut, with the file note and the rule, and places the hold herself.
DE
Deshawn ElleryClaims auditor
Owns the contact, coverage, payment and diary checks
Before
“I read 6% of the files and sign for 100% of them.” Four TPA audits a year, about 250 files each.
Now
Owns the checks that read every file event, and tests a change on last month’s events before it runs.
PR
Priya RamanReserving analyst
Owns the reserve check
Before
“I need to know the day a TPA’s reserve stops matching its own estimate.” Reviews reserves by program each quarter.
Now
Sees a reserve below paid, or more than 15% off the latest estimate, the day it happens — and is copied on the large-loss notice.
TG
Tom GaffneyClaims team lead, Bramblecrest Claims Services
The administrator
Before
“Tell me in the week, not in next year’s audit letter.” Runs 11 adjusters on two property programs.
Now
Gets the reason the carrier sees, drafted from his own file, with a date to answer by.
Built on the engine

7 agents. Each with one job, and hard limits.

Seven agents read every file event a TPA posts and run seven checks on it; the claims manager decides.

File reader

Reads every note, reserve change, payment, letter and report the administrators post, and the monthly claims bordereaux; ties each event to its claim, policy and binder.

  • Read-only on administrator systems
  • Never edits the administrator’s file
Coverage checker

Confirms the policy was in force on the loss date, the cause of loss is covered under the binder, and deductibles and sublimits are applied; flags reservations of rights, declinations and declined tenders made without the carrier’s agreement.

  • Never takes a coverage position
  • Never denies or reserves rights
Reserve checker

Watches reserves against the latest estimate, demand or report in the file: initial reserve within 5 business days, within 15% of the latest estimate, reviewed within 10 business days of new information, never below paid. Computes the incurred the file implies.

  • Never writes to reserves
Authority checker

Sums paid and reserved indemnity and expense per claim, compares them with the administrator’s authority for that binder, and looks for a referral or carrier approval on the file.

  • Cannot approve or release payments
  • Never approves a payment above authority
Payment checker

Checks the payee against the vendor list, the invoice arithmetic, the deductible, and every invoice line against every prior payment on the claim.

  • Never places a hold — only the claims manager does
Reportable-claim finder

Applies the reporting triggers — likely above the notice threshold, above authority, coverage dispute, suit, open more than six months — starts the 2-business-day clock and drafts the notice from the file.

  • A person sends every notice
Leakage estimator

Prices each finding — duplicate, deductible, outside coverage, vendor rate, missed subrogation, expense above guidelines — and sums leakage per administrator and cause.

  • Counts only findings the claims manager accepted
Delegated claims manager

Decides; a second approver changes authority. The agents propose; a named person decides.

Ask in plain words

Ask about any claim, administrator or check

Ask in plain words about a claim, an administrator, a check or the leakage. Every answer cites the file.

Why did Bramblecrest’s authority badge turn red on Linden Court?

At 10:41 Bramblecrest paid $68,400 to Gulfline Restoration on invoice GR-11402. With the $6,200 paid on 2 Jul, $74,600 is now paid on HB-26-08812 against $50,000 of settlement authority on binder HSI-BA-2026-0417 — $24,600 over. No referral or Harrowgate approval is on the file; the adjuster’s note says the supervisor approved the full invoice.

Which claims should have been reported to us and weren’t?

Three are overdue. Linden Court — Gulfline’s $71,250 estimate on 2 Oct passed the $35,000 large-loss threshold; notice was due 6 Oct. Cypress Hollow — a suit filed 29 Sep was posted to the file on 2 Oct. Marigold Café — open six months on 3 Oct.

Where is Caldera’s leakage coming from this year?

Caldera’s estimate is $121,700, 2.97% of $4.1M paid — the highest share of the five. The biggest cause is deductibles not taken: 31 payments, $46,500. Today’s Saffron Table spoilage payment is another: $4,950 paid with no $1,000 deductible.

Is the Linden Court reserve adequate?

No. The indemnity reserve is $45,000 and $74,600 is already paid. Gulfline’s 2 Oct estimate of $71,250 has $9,050 not yet invoiced, so the file implies at least $83,650 incurred. The schedule wanted a review within ten business days of the estimate and never a reserve below paid.

Every screen

The working solution, as it ships.

13 screens from the working solution, on its sample data. Pick one to see it large.

The file streamEvery file event from five administrators with its seven check badges, today’s counts above, and each TPA’s live score per check beside it.
Checks as the event landsThe $68,400 Linden Court payment arrives and its badges evaluate in front of you: reserve, payment and report red, authority still running.
The file note behind a badgeWhat the check found, the payment and adjuster’s note with the sentence highlighted, the numbers, and the authority schedule rule it applied.
The claim filePaid against authority, reserve and the incurred the file implies; the file event by event; and each agent’s check on the 10:42 payment.
Invoice against invoiceGR-10977 and GR-11402 side by side, the structural drying line paid twice marked in red, with the claims manager’s decisions beside it.
The request to the TPADrafted from the file to Bramblecrest’s team lead: the referral, a corrected reserve and the credit for the duplicate, with a date to answer by.
The large-loss noticeBuilt from the TPA’s file: policy, binder, loss, paid, reserve against the incurred the file implies, both triggers and the open items — logged by the claims manager.
Flagged claims37 claims with a red or amber check this week, one reason each in plain words, the amount at stake, and filters by check and administrator.
Reportable claimsEvery claim an administrator must report — threshold, authority, coverage dispute, suit, six months — with the date met, the notice due and who it goes to.
LeakageThe 2026 leakage estimate by administrator and by cause, with recoveries, and a ledger of every finding the claims manager accepted.
Administrator scorecardsPass rate per check, days to close, reserve accuracy, leakage as a share of paid and files reviewed for each TPA, with its trend and open flags.
The seven checksEach check’s definition, the agreement clause it applies, the sources it reads, its owner, and how many claims it flagged this week.
Authority and clocksClaims authority and notice thresholds by binder, the clocks and tolerances, what happens on a red check, the people and the administrator feeds.
Governance

Built for delegated authority: cited, decided by a person, on the record.

Every badge cites the fileClick any badge to see the file note, payment or invoice that set it, with the sentence highlighted and the rule from the authority schedule or claims administration agreement quoted beside it.
The TPA’s system is read, never changedThe agents have read-only access to the administrators’ claims systems. Nothing is written back into a TPA’s file; reserves, payments and coverage positions stay theirs to change.
A person places every holdHolding payments automatically is off by policy. Holds, referral requests, accepted leakage findings and notices are the claims manager’s decisions, and each is recorded with her name and the time.
Authority changes need a second approverChanges to authority, clocks and thresholds are saved as drafts until a second person approves them — at Harrowgate, Martin Oyelaran, VP Claims.
The TPA sees the same reasonOnce the claims manager agrees, the administrator gets the same reason the carrier sees, drafted from its own file — so a finding is argued on the facts, not rediscovered at audit.
Every step on the claim’s trailEach agent finding and each human decision is listed in the claim’s audit trail, with who, what and when — from the reserve checker reading the estimate on 2 Oct to the hold on 12 Oct.
Configuration

Your binders and your schedules, not ours

Authority, clocks and thresholds are set per binder, from each claims administration agreement. Changes are drafts until a second person approves them.

SettingDefaultChoose from
Indemnity authority per claim$50,000 — Bramblecrest, Coastal Habitational PropertySet per binder: $35,000 to $75,000 across the six binders
Large-loss notice threshold$35,000Set per binder: $25,000 to $50,000
First contact1 business day from noticeAny number of business days
Initial reserve5 business days from noticeAny number of business days
Reserve review after new information10 business daysAny number of business days
Reserve tolerance15% against the latest estimateAny percentage
Diary limit30 days without activityAny number of days
Hold payments automaticallyNever — a person places every holdOff by policy
Connections

Works with what your administrators already send

Administrators’ claims systemsa feed from each TPA, every 30 seconds
Claims bordereauxthe monthly bordereau, reconciled to the file events
Claim filesnotes, reserves, payments, invoices, letters and reports
Binders and authority schedulessettlement authority, notice thresholds and coverage terms
Policy forms and endorsementswhat the coverage checker reads against the loss
Vendor list and rate guidelinesapproved payees, vendor rates and litigation guidelines
What it changes

The difference, in numbers.

Every figure is labelled: a target the solution is built to, an estimate, a typical published result, or a proven one.

target
100%
of delegated file events checked as they land, against a 5–7% audit sample
Audit sample≈ 6% of files
With agentsevery event
target
Sameday
an authority breach or a missed notice reaches the claims manager
Day 1, not month 7
from trigger to the carrier's desk
typical
5–10%
of claims paid lost to leakage, today measured on samples
SampledEvery file

“demo” = seen in the working solution, on its sample carrier, administrators and claims · “target” = the design goal, measured in the live solution · “estimated” = our estimate · “typical” = published figures (claims leakage issue briefs put leakage at 5–10% of claims paid; Insurance Thought Leadership cites 7–14%). Context: FCA, home and travel claims handling good and poor practice (2025); NAIC Managing General Agents Act (Model 225), as enacted (e.g. NC GS 58-34-2); Lloyd’s, Delegated Claims Administrators; LMA Delegated Claims Standards (LMA20-036). People, carriers, administrators, insureds and vendors named on this page are fictional — characters and sample data in the working solution.

Questions

What delegated claims teams ask us.

What is delegated claims audit software?

Software that lets a carrier or managing agent oversee the claims its delegated administrators handle under their own authority. Delegated Claims Audit reads every file event a TPA posts — notes, reserve changes, payments, letters — as it lands and runs seven checks on it, instead of sampling files at an annual audit.

How does it check a TPA’s settlement authority?

The authority checker sums paid and reserved indemnity and expense on the claim, compares the total with the authority schedule for that binder, and looks for a referral or carrier approval on the file. On the hero claim it found $74,600 paid against $50,000 of authority with no referral, the minute the check was cut.

Does it catch duplicate payments and missed deductibles?

Yes. The payment checker matches every invoice line against every prior payment on the claim, and checks the payee and the deductible. In the working solution it found a $6,200 structural drying line paid twice and a $1,000 deductible not taken on a spoilage payment, and the leakage estimator priced both.

How does it find claims the TPA should have reported?

The reportable-claim finder applies the triggers in each binder’s claims authority schedule — likely above the notice threshold, above authority, a coverage dispute, a suit, open more than six months. Several of these, such as a coverage dispute or a claim open more than six months, are also on the state MGA laws’ list of claims an administrator must report to the insurer. It starts the 2-business-day clock the day a trigger is met and drafts the notice.

Can the agents hold a payment or send a notice on their own?

No. Holding payments automatically is off by policy, and the agents have read-only access to the administrators’ systems. The claims manager places every hold, sends every request and notice, and accepts every leakage finding; authority changes need a second approver.

How do we know the checks are right?

Every badge cites the file note and the rule it applied, and the same event always gets the same answer. Before a change runs, a check can be tested on last month’s events: in the working solution, September’s 36,904 events were compared with the 412 files the claims auditor reviewed — none missed, six flagged in error, all six referrals sent by email and attached late.

Which systems does it work with?

A feed from each administrator’s claims system, the monthly claims bordereaux, the claim files, your binders and claims authority schedules, policy forms and endorsements, and your vendor list and rate guidelines. In the working solution each TPA feed refreshes every 30 seconds.

How long does it take to go live?

The Agentic Solution Engine builds and deploys it from your requirements and documents — your binders, authority schedules, claims administration agreements and a sample of your administrators’ files — and it goes live once every quality gate has passed. We will walk you through it on your own TPAs’ files first.

See it on
your TPAs’ files.

We’ll run Delegated Claims Audit on a month of your own administrators’ file events.