Payors / payment integrity

Stop Paying and Chasing

Pay-and-chase finds the money months after it’s gone. Ana checks every claim against your contracts, edits and payment history before the payment run — and hands reviewers the evidence with the flag.

[ the difference ]

Pay and Chase, or Check and Pay

today
  • Claims paid first, checked months later
  • A sample reviewed; the rest go out unread
  • Reviewers open five systems to build one case
  • New checks wait in the rules-engine queue
with textql
  • Every claim checked before the payment run
  • The whole population screened on every run
  • Each flag arrives with the claim’s history attached
  • New checks written in plain English, reviewed like code
[ 01 screen ]

Every Claim, Not a Sample

Ana runs your checks across the whole population on the cadence your claim flow allows — contract variance, duplicates, NCCI and MUE edits, level-of-care drift — and surfaces only the few that need a person.

  1. Prepay ahead of the payment run, or post-pay across history
  2. Every flag scored and routed to the right review queue
  3. New checks written in plain English and reviewed like code
prepay screen · this week 0 claims  /  0 flagged
clm-2291 · paid on expired rate
screened flagged for review
[ 02 prove ]

The Evidence Comes With the Flag

The payment record alone says clm-2291 was paid within the fee schedule. The contract history says the schedule had expired. Every flag arrives with the claim, its adjustments and the terms in force on the date of service already joined.

  1. Contract terms matched to the date of service
  2. The query that found it logged beside the finding
  3. Evidence exported for the provider letter or appeal
case · clm-2291
Knee replacement paid at $38,400
flagged
  1. 03/04 Claim received — CPT 27447 clm-2291 · northwest ortho $41,000
  2. 03/11 Paid on the fee schedule on file pmt-7781 $38,400
Paid within the fee schedule. No edit fired. $38,400
[ 03 clear ]

False Flags Close as Fast as They Open

A screen that buries reviewers in noise gets switched off. The same history that proves a finding clears the ones that aren’t — a reversal isn’t a duplicate, and the reviewer sees why in one view.

  1. Reversals and resubmissions followed automatically
  2. Cleared flags tune the check, so they stop recurring
  3. Every decision logged for audit
case · clm-1042
Two $840 payments on one claim
flagged
  1. 01/12 Payment — office visit clm-1042 · pmt-01 $840
  2. 01/19 Payment — corrected claim clm-1042-a · pmt-02 $840
Two payments, one claim. Looks like a duplicate. $1,680
[ the retro scan ]

Start With the Claims You Already Paid

The first run looks back, so the findings are in dollars before anything in the payment run changes. The checks that hold up then move ahead of it.

Run a Retro Scan

Bring a year of paid claims and the checks your team suspects most. We run them inside your cloud and work the flagged cases with your reviewers.

  1. 01A 30-minute call to pick the checks and the claims in scope
  2. 02We connect inside your cloud under a BAA — nothing leaves your environment
  3. 03Your reviewers work the flagged cases with us, on real claims
[ use cases ]

The Checks Plans Run First

  • 01 Duplicate and corrected claims

    Separate true duplicates from reversals, replacements and resubmissions by following the adjustment history — before anyone sends a letter.

  • 02 Contract and fee-schedule variance

    Compare every paid amount with the rate in force on the date of service, including amendments and carve-outs, and total what is recoverable by provider group.

  • 03 Upcoding and level-of-care drift

    Find providers whose E/M levels or inpatient admissions drift above specialty peers, with the member mix accounted for.

  • 04 Unbundling and code edits

    Apply NCCI and MUE edits across the history, not just the claim in hand, and catch the patterns a line-level edit misses.

  • 05 Coordination of benefits

    Spot members with other coverage from eligibility, pharmacy and claims signals, and pay in the right order.

  • 06 Recovery reconciliation

    Match recovery letters to receipts and offsets, and see exactly what is still open and with whom.

[ faq ]

What Teams Ask Before They Start

Read access, inside your environment, to paid claims, the contracts and fee schedules in force, the provider master and your edit policy. Your team picks the checks; we run them and work the flagged cases with your reviewers.

[ try textql ]

Bring Us Your Hardest Problem