A claim being scrubbed line by line before submission
How it works

Connect. Compare. Propose. Approve.

Every claim, every payer, every dollar explained. Four steps, and the last one is always yours.

Step 1

Connect

Upload or connect your claims, remittances and payer contracts.

Works from the files your clearinghouse and EHR already produce (837, 835, 999, 277CA); direct connections are set up and tested with each practice and vendor. Files land in your workspace inside our HIPAA environment on AWS, never on this website.

Connected data sources
Step 2

Compare

Every line checked: expected versus paid.

The expected amount comes from your contract, a published rate table or the payer’s own payment history. When a line pays short you see billed, correct, the variance and the source. When nothing explains the gap, the line is labelled unexplained.

Paid claims reconciled against remittances
Step 3

Propose

We draft the fix, the appeal, or the records packet.

Each proposal carries the reason and the source. When a fact is missing, the ask goes to the right person and the claim is re-checked when the answer comes back.

Flagged claims corrected and resubmitted as clean claims
Step 4

Approve

One inbox. One click. Tracked until the money lands.

Approve commits exactly what you see, and who approved what, and when, is kept on every item. Approved work becomes the file you submit through your own route. We never submit for you.

Documents flowing into an automated claims queue

See what it catches →

The claim cycle, explained

How a claim gets paid, and where it doesn’t

Every rail follows the same basic path from a visit to a payment. Money goes missing at a few predictable points along the way.

  1. Care and documentation

    A service is delivered and documented. The record has to support every code that is billed.

  2. The claim

    The claim goes out in a standard format: the 837P for professional services, the 837I for institutional care, or a state format such as DODD’s eMBS flat file.

  3. The clearinghouse

    Most claims pass through a clearinghouse, which checks the format and routes each claim to the right payer.

  4. The payer decides

    The payer checks eligibility, authorization, coding and its own rules, then decides what to pay.

  5. The remittance

    The answer comes back as an 835 remittance or a return report, with adjustment reason codes (CARC and RARC) for anything not paid in full.

  6. Follow-up

    Underpayments, denials and appeals are worked by hand, each against its own deadline.

Where the money goes missing

Denials nobody reworks

A denied line waits in a queue until someone has time, and the window to fix it closes.

Paid, but short

A line that pays less than the contract looks like a payment, so nobody looks again.

Deadlines that pass

Filing and appeal windows differ by payer and run out quietly.

Authorizations that run out

Care continues after the authorization or referral ends, and those visits are denied.

ClaimYours AI works at three of those points: it checks the claim before it goes out, compares the remittance with what you were owed, and drafts the follow-up while the deadline is still open.

How we work with you

Who does what

ClaimYours AI does the checking, the comparing and the drafting. Your team keeps every decision and every submission.

What your team does

  • Approves every fix, appeal and records packet
  • Submits approved work through your own route
  • Answers a question when a fact is missing

What ClaimYours AI does

  • Checks every line before it goes out, with the rule behind each result
  • Compares what was paid with what was owed
  • Drafts the fix, the appeal or the records packet
  • Tracks each item until the money lands, with a work log of who did what

What we need from you

  • Your claim files (837 or eMBS flat files)
  • Your remittances (835s or return reports)
  • Your payer contracts or the rate tables you are paid from
  • For your rail: authorizations, referrals or EVV visit exports

What we never do

  • Submit a claim for you
  • Touch patient data before the Business Associate Agreement is accepted
  • Use real patient information in the demo
  • Guess a rate we cannot source

Each rail has its own rules and systems: DODD · Behavioral health · VA Community Care · Home health · Any practice

Why providers switch

Three problems every billing office knows

The pain

Claims sit denied for weeks

A denial shows up days after you submit, then waits in a queue until someone has time to work out why.

How we answer it. Claims are checked the moment they arrive, so most problems are found before you submit. Denied lines come back to the work queue with the reason attached.
The pain

Nobody knows which rule failed

A denial code tells you something is wrong. It rarely tells you which rule, or what to change.

How we answer it. Every check shows its result and its source: the rule, what it looked at, and where the rule comes from. Nothing is a black box.
The pain

Adjustments never get filed

Short pays and underbilling are easy to miss, and easy to put off until the window closes.

How we answer it. Recover compares what you billed with the correct rate, shows the variance and its source, and proposes the adjustment claim. A person approves it, and the work log records who did what.
Built for Ohio

Made around the systems Ohio providers actually use

Each rail runs on its own rules, files and agencies, not a generic national rulebook.

Ohio DODD

Waiver claims checked against the service rules in OAC Chapter 5123-9, with corrected files staged for eMBS.

County boards & PAWS

All 88 Ohio counties mapped to their rate categories, and units checked against the PAWS authorization on file.

ODM behavioral health

The ODM Behavioral Health Provider Manual and the Ohio Medicaid BH fee schedule (OAC 5160-27-03), checked before an MCO sees the claim.

Home care programs

PASSPORT, MyCare Ohio and the Ohio Home Care Waiver, matched to your Sandata or HHAeXchange visit records.

VA Community Care

Every claim matched to its HSRM referral and paid against your Community Care Network agreement.

Your payer contracts

For any other practice, each paid line is compared with your contract rate or what that payer has really paid you.

Security & privacy

Patient data stays inside the platform

No patient data on this siteThis site never collects patient information or files.
BAA before any PHIYou accept the Business Associate Agreement before you upload anything.
Hosted on AWSHosted in the United States on Amazon Web Services.
EncryptedEncrypted at rest and in transit.
No PHI on this siteOur forms refuse patient details. Uploads happen only inside your account.

Read how we handle security or HIPAA and the BAA.

How onboarding works

From sign-up to your first checked claim

  1. Sign up

    Create an account, or start with the demo to see the platform first.

  2. Approved

    A person at ClaimYours AI reviews and approves your account.

  3. BAA accepted

    Your practice accepts the Business Associate Agreement inside the platform.

  4. Upload & check

    Upload claims inside your account and see every result with its source.

See how every claim gets checked.

Try the demo yourself, or ask for a walkthrough. No patient information needed.