For payers, programs and the contractors who protect them
Stop the payment that should not move. Prove why you stopped it.
Detection is everywhere. Proof is rare. JIL learns from the payments you have already made, checks every new one before it moves, and seals the reason for each decision so it holds up with providers, auditors and courts.
Pre-payment holds
Payments that fail a check are held with the reason attached, before the money leaves. Your team confirms the hold or releases the payment.
Recoveries that hold
The same checks sweep backward across what has already been paid. Findings arrive with the record, the rule and the version used, ready for the provider and the appeal.
Evidence by default
Each decision produces its own evidence record, read against the provider's full integrity profile, without anyone building it by hand.
Fraud is the small slice. Waste, abuse and error are most of the dollars.
Flagged dollars in this run by category (synthetic)
Fraud goes to investigators. Waste, abuse and error can be stopped at the source, if the evidence comes with the decision.
What changes for your organization
Today compared with Payment Integrity in place
| Moment | Today | With JIL |
|---|---|---|
| Before payment | Edits catch some errors; the rest is paid and chased | Every payment checked; failures held with the reason |
| After payment | Separate look-back tools, separate rules | The same rules sweep paid claims, so both agree |
| Provider disputes | The answer lives in a spreadsheet and an analyst's memory | The record, the rule and its version, sealed at the decision |
| Appeals and audits | Evidence rebuilt by hand, months later | Evidence produced with every decision |
How a pilot works
Bring us a year of paid claims. We will show you what should have been stopped.
Share a historical extract
A year of paid claims is enough to start. Read-only; nothing in your systems changes.
Patterns are learned
Which providers, codes, members and combinations went wrong, and how.
A written view of what we find
Every finding with the evidence attached, walked through with your team.
Guard the gate
The same checks run on new payments before release.
Stop it before it moves. Prove it when it is questioned.
A historical extract is enough to start. A written view of what we find, with the evidence attached.
Analyst workbench
Before the money moves, and after it has.
The pre-payment guard shows today's payments that failed a check and are waiting on your decision. The look-back sweep runs the same rules across claims already paid. Open any item to see the claim, the rule and its version, and the provider's context. Your decision is sealed with its reason.
| Amount | Claim and provider | Status |
|---|
Activity on this session
- No decisions yet. Confirm a hold, release a payment or open a recovery to see it recorded here.
Architecture
Learn from the past. Guard the future. Seal both.
Five stages run inside your own environment. One rule set serves both directions, so the look-back and the guard at the gate always agree. Checks are deterministic and versioned. AAVAE ranks and explains; people decide. JIL never moves money: a hold is a signal into your existing pend queue.
Ingest your payment history, read-only.
Patterns of fraud, waste, abuse and error become versioned checks.
Every new payment checked before release; failures pended with a reason.
The same checks sweep paid claims.
Each hold, release or finding sealed with its record and rule version.
Check catalog in this demo
A representative subset. Your catalog is built from your own payment history and policies.
| Rule | Category | What it checks | Version |
|---|
What an evidence record holds
Sample from this demo. Make a decision in the Functional view to generate a live one.
Design rules
| One rule set | Pre-payment and look-back run the same checks, so they never disagree. |
| Version pinned | Every decision records the rule version and the record as it stood. |
| People decide | Checks hold; analysts confirm, release or open a recovery. |
| No money movement | JIL returns a hold signal to your claims system. It never pays or recoups. |
| Sealed as it stood | Each record is fingerprinted (SHA-256) so it can be reproduced later. |
| Referral-ready | Bundles are oriented to FRE 902(14). A court decides admission. |
| Your environment | Runs in your own cloud data account. Data stays where your agreements require. |
Security and compliance status
| Item | Detail | Status |
|---|---|---|
| SOC 2 Type 1 and Type 2 | Independent audit by Johanson Group LLP. Targeted for February 2027. No report has been issued. | In progress |
| HITRUST | Targeted for April 2027. | In progress |
| HIPAA | Covered within the same Johanson Group LLP engagement. | In progress |
| FedRAMP | Not held. | Not held |
| Patents | Patent claims are filed and pending; none granted. | Pending |