SystemCommercial

Chargeback Processing

Chargeback processing where agents read every claim packet, fixed rules decide, and a person approves every payment

Every chargeback claim read first, each verdict with its rule and evidence

See one case, screen by screen ↓
demo2,480claimsin the October cycle, every one read by agents before anyone opened it
demo64exceptionsstopped at a rule on the sample cycle — $412,860 held until a person decides
demo2.6minmedian from packet to a verdict with its rule and evidence
demo1.2millionpast claim lines since 2021 searched for duplicates and purchase-order totals
The problem

Why chargeback exceptions leak money

A manufacturer sells to a distributor at WAC. The distributor sells to a hospital at the lower price its purchasing-group contract gives it, then claims the difference back as a chargeback. Most EDI 844 lines clear automatically against the contract, the roster and the price file. The rest land in an exception work list, where an analyst opens the PDF packet — claim form, invoices, purchase orders, delivery notes — looks up the contract term, the tier and the member's eligibility by hand, and answers line by line on the EDI 849 within a short window.

The leakage sits in what the EDI check cannot see. A quantity pasted over an invoice. A purchase order already used up by three earlier claims. An invoice line paid once and claimed again, by the same distributor or another. A contract price claimed two days after the term ended. Nothing is remembered from one cycle to the next, so cumulative and duplicate checks are close to impossible by hand.

typical416$ billionin gross-to-net reductions for brand drugs in 2025, a total that chargebacks are part of
typical4%of chargebacks estimated to be in error, leaking revenue and delaying cash
typical30–60dayscommon resubmission windows for a rejected claim
Where an exception claim's hours goestimated
By hand3.5 days
With the solution0.5 days
  • Sorting the packet and matching pages to claim lines0.5 → 0.1 d
  • Looking up contract term, tier price and roster on the invoice date1 → 0.1 d
  • Searching past claims for duplicates and purchase-order totals1 → 0.1 d
  • Checking supporting files for edits and arithmetic0.5 → 0.1 d
  • Deciding, reason codes and the response to the distributor0.5 → 0.3 d

Estimated split for one stopped claim packet, worked by hand and with the solution.

How it works

How a packet moves

Five agents read and check every packet; seven fixed rules decide; a reviewer approves every payment.

What comes in
Packets in3 channels · claim, invoices, contracts
Agents at work
Intake agentsorts the files
Then
Extraction agentlines + citations
Then
Validation agent
History agent
Then
Rules agent7 rules + clause
A person decides
Chargeback reviewerapproves payment
What comes out
Verdict + evidence
Credit or reply
History kept
One case, step by step

One packet that stops at the rule it broke

Tuesday 6 October 2026, the October claim cycle for September sales at Halvern Medical, a maker of devices and disposables sold through six distributors. At 09:52 three packets arrive. Here is what happens next, screen by screen, in the working solution.

  1. 0109:52

    The whole cycle on one line

    Dana Okafor · Chargeback reviewer

    Dana's home screen is the packet line: Read by agents, Rules decide, People approve, Paid. This cycle 2,480 packets have come in; 64 are stopped at a rule with $412,860 held, 18 are ready to approve for $286,430, and 2,397 are decided. The panel on the right already shows the highest-scoring stopped packet, CB-88213 from Meridale, held at rules 5 and 7.

    “Agents read and cite. They never give a verdict.”

  2. 02One click

    Run the 09:52 intake

    Intake agent

    The intake agent picks up 3 packets: Summit Ridge by EDI 844 with 9 PDFs, and Crestline through the portal with 6 files. The extraction agent reads 6 lines and 72 fields, each cited to its page. The validation agent checks invoices, contracts and rosters and notes that invoice SRD-60458 is dated Oct 2. The history agent searches 1.2 million past lines.

    Median per packet: intake 6 s · extraction 1.6 min · validation 41 s · history 9 s.

  3. 03At the gate

    One passes, one was already paid

    Rules agent

    Each packet passes the rules gate: seven rule lights, and no model decides. CB-88249 from Summit Ridge passes all 7 rules and moves to People approve. CB-88250 from Crestline stops at rule 4, Not claimed before: invoice line CHD-121577 was already paid on credit memo CM-42794.

    Line log: “Rules agent stopped CB-88250 at rule 4 · CHD-121577 already paid on CM-42794.”

  4. 04Seconds later

    CB-88252 stops at rule 3, Contract in force

    Rules agent

    Summit Ridge Distribution claims two lines for Granite Falls Medical Center. Line 1, invoice SRD-60458, 60 boxes of hydrophilic guidewires, is priced on contract CHP-2023-0144. The agents read the invoice date (Oct 2, 2026), the contract on the claim form, the contract end (Sep 30, 2026) and the contract register (no extension), each with its source and confidence. The rule compares the dates and fails: $5,520.00 held, $1,960.00 payable, score 84.

    “Oct 2, 2026 > Sep 30, 2026 — FAIL · Fixed logic · rule 3 (C-03) v1.6 · owner Omar Haddad · no model decides.”

  5. 05The clause

    The contract clause, right under the rule

    Dana Okafor · Chargeback reviewer

    Below the comparison sits the clause the rule enforces: Cedarline agreement CHP-2023-0144, §3.1 Term. Granite Falls signed the renewal, CHP-2025-0207, but it starts Nov 1, 2026. Line 2, invoiced Sep 28, is inside the term and passes. The suggestion: reject the held line with reason C-03 and pay the clean line.

    “This Agreement begins October 1, 2023 and ends September 30, 2026, unless extended in writing under §3.2. Contract prices apply only to products invoiced during the Term (§7.4).”

  6. 06Her decision

    Reject the held line, with a reason code and her signature

    Dana Okafor · Chargeback reviewer

    The reject dialog has C-03, Contract not in force on the invoice date, already ticked among the seven reason codes. Dana rejects the held line only, $5,520.00, rather than the whole claim at $7,480.00. The note to Summit Ridge is drafted from the evidence, and her e-signature carries its meaning.

    “Dana Okafor · Chargeback reviewer · meaning: rejected after reviewing the evidence.”

  7. 07Done

    The clean line is credited, the response goes back

    Dana Okafor · Chargeback reviewer

    The line log records it: Dana Okafor rejected the CB-88252 held line, C-03, e-signed, $1,960.00 credited. The response goes to Summit Ridge and the Paid station moves to 2,398. The panel moves on to the next stopped packet, CB-88250, for her to decide.

    “CB-88252: held line rejected (C-03) · response sent to Summit Ridge · $1,960.00 credited.”

  8. 08On the record

    The packet keeps every page and the decision

    Dana Okafor · Chargeback reviewer

    Opened from the claims list, CB-88252 shows the invoice with every cited value highlighted, the claim form, delivery note, price list and claim history. On the right: line 1 rejected with C-03, one clean line approved for credit, the response file sent, Dana's e-signature, and rule 3 with its evidence, the clause and the comparison.

  9. 09The hardest one

    CB-88213: 80 over the order, and an edited invoice

    Validation and history agents

    Meridale Medical Supply claims $70,070.00. Purchase order SAMC-PO-77120 covers 400 drug-coated balloon catheters; 360 were already claimed in July, August and September, so 120 more makes 480, 80 over. The delivery note shows 20 received. The invoice was created Sep 2 and modified Sep 30, 28 days later, with “120” placed over “20”, and the subtotal still reads $21,700.00 for 20 units. Rules 5 and 7 fail: score 92, $43,800.00 held, 5 clean lines worth $26,270.00 can be paid.

    “360 + 120 = 480 > 400 ordered → fail”

  10. 10End of the cycle

    The integrity report, signed by the controller

    Omar Haddad · Controller

    Each cycle the reporting agent writes the integrity report: what was claimed, what was held and why, and which distributors to talk to. September's covers 2,512 packets and 71 claims held, worth $468,120. Reviewers upheld 67 holds; 4 were paid after the distributor sent a corrected invoice. Omar Haddad signed it on Oct 3.

    “Meridale Medical Supply — 6 claims over a blanket purchase order, most of them balloon catheters.”

Who it’s for

Built for everyone who touches a chargeback.

The same claim cycle, seen by the four people who carry it — what their month looked like, and what it looks like now.

DO
Dana OkaforChargeback reviewer · approves payments, owns rules 4, 5 and 7
Chargeback reviewer
Before
Clears the stopped packets each morning by opening PDFs and looking up contract terms, rosters and past claims by hand.
Now
Opens a packet already stopped at the rule it broke, with the values the agents read, the comparison and the contract clause, and decides.
SP
Sam PatelChargeback reviewer · works Crestline and Northpoint, owns rule 6
Chargeback reviewer
Before
Hunts for lines already paid once, in his own distributors' claims and everyone else's, with no memory from one cycle to the next.
Now
Sees every claim with its verdict, issue, stage and reply clock, filtered by distributor and rule, and approves the clean ones in a batch.
OH
Omar HaddadController · second approver on overrides and claims over $50,000
Controller
Before
Needs to know what was held, why, and that it stood up — and has to piece it together at month end.
Now
Reads one integrity report per cycle, written from decided claims with the patterns and distributors to talk to, and signs it.
LO
Lena OrtizContracts manager · contracts, price lists and rosters
Contracts manager
Before
Loads contracts, price revisions and roster changes, knowing the checks are only as right as the dates she gives them.
Now
Sees each rule with the clause it enforces and the data it reads — contract terms, extensions, price lists, rosters — and its holds this cycle.
Built on the engine

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

Five agents read and check every packet; seven fixed rules decide; a reviewer approves every payment.

Intake agent

Picks up packets from the EDI 844 feed, the claims mailbox and the distributor portal, groups every file that belongs to one claim and sorts its pages into claim form, invoices, purchase orders, delivery notes and price lists.

  • Keeps the original file untouched, with its fingerprint
  • Flags packets with missing invoices
Extraction agent

Reads every claim line and its supporting documents — invoice number, date, customer HIN, item, quantity, unit, contract and prices — and cites each value to the page it came from, with a confidence.

  • Every value carries a citation
  • Low-confidence fields go to a person
Validation agent

Checks the documents against each other and against the contract: price and tier on the invoice date, roster membership, units, and whether a file was edited after it was created.

  • Reports evidence only — never a verdict
History agent

Searches the permanent claim history — 1,214,380 lines since 2021, from every distributor — for the same invoice line, and adds up every quantity claimed against the same purchase order.

  • Reads history only; writes nothing back until a person decides
Rules agent

Runs the seven fixed rules over the cited evidence and returns a verdict — Pass, Partial or Hold — with the rule, the evidence, the contract clause and a score. The same evidence always gives the same verdict.

  • Deterministic — no model call decides a verdict
  • Payment-affecting verdicts wait for a person
Chargeback reviewer

Approves every payment. The agents propose; a named person decides.

Ask in plain words

Ask about any claim, rule or distributor

Ask why a packet stopped, filter the claims, or change who approves — in plain words. Every answer cites the document it came from.

Why did CB-88252 stop at Rules?

Rule 3 compares the invoice date with the contract term. CB-88252 from Summit Ridge prices invoice SRD-60458, dated Oct 2, 2026, on contract CHP-2023-0144, which ended Sep 30, 2026 (§3.1) and was not extended. Granite Falls' renewal starts Nov 1. The agents read the two dates; the rule compared them — $5,520.00 held, the Sep 28 line can be paid.

Why is CB-88213 on hold?

Two of the seven rules failed on line 1. Rule 5: purchase order SAMC-PO-77120 covers 400 units; 360 were already claimed July–September, so 120 more makes 480, and the delivery note shows 20 received. Rule 7: the file was edited on Sep 30, 28 days after it was created; “120” sits on top of the original “20”. Score 92; $43,800.00 is held and the other 5 lines ($26,270.00) are clean.

Show me every claim with an altered document

5 claims this cycle have a supporting file edited after it was created, and the claims list is filtered to them. The highest score is CB-88213 (92). The check reads the file properties, the text layers and the invoice arithmetic — no guesswork about intent; a person decides.

Hold claims over $50,000 for a second approver

Done. Claims over $50,000 now need Omar Haddad (Controller) as second approver before payment. It applies from the next approval — 3 claims in this cycle are affected, including CB-88213 ($70,070.00). The change is under Settings → Approvals and on the audit trail.

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 packet lineEvery packet on one line — read by agents, rules decide, people approve, paid — with the stopped packets under the rules gate and the selected one explained on the right.
Agents reading the intakeNew packets at the first station, each with its sort, read, check and history steps, and the median time per agent.
Stopped at the ruleWhat the agents read with source and confidence, the comparison the rule made, the contract clause, the money held and payable, and the suggestion.
Reject with a reasonReason codes sent to the distributor, held line or whole claim, the drafted note and the reviewer's e-signature with its meaning.
After the decisionThe clean line credited, the response sent, the line log updated and the next stopped packet ready.
ClaimsEvery claim with its distributor, packet, amount, verdict and score, the issue found, stage and reply date — filtered by status, distributor or rule.
A decided packetThe invoice with each cited value highlighted beside the decision, the signature, the failed rule, its evidence and the contract clause.
Packet reviewDocuments on the left; on the right the verdict and score, each failed rule with evidence chips, the clause and the comparison.
Side by sideThe invoice as received next to the claim history for its purchase order: 360 of 400 already claimed, this claim 80 over.
The seven rulesEach rule with what it checks, the clause it enforces, the data it reads, its holds this cycle, its owner and last change.
DashboardClaims per cycle and exception rate, issue patterns with amounts held, the verdict split and time per agent.
Integrity reportsOne report a cycle — patterns found, distributors to talk to, rule and roster changes — signed by the controller.
SettingsWho approves, rejects and overrides, the hold score and its effect on this cycle, the claim window and where packets come from.
Governance

Built for gross-to-net risk: cited, ruled, signed.

Every value cited to its pageWhat the agents read is shown with its source — the invoice, the claim form, the contract register, the claim history — and a confidence. Low-confidence fields go to a person.
Fixed rules decide, not a modelSeven versioned rules turn the evidence into a verdict, each with its owner and the contract clause it enforces. The same packet always gets the same answer.
A person approves every paymentEvery payment needs a reviewer's approval, and every rejection carries a reason code and an e-signature with its meaning. Paying against a failed rule needs a second approver.
Originals and history kept unchangedOriginal packet files are kept with their fingerprint. The claim history is permanent and cannot be edited, and nothing is written to it before a person decides.
Rule changes are tested firstA rule can be tested on last cycle's claims against the decisions people made, and a new rule waits for approval before it is used.
Every step on the audit trailThe line log records each agent step and each decision in order, with who and when. The integrity report uses numbers only from decided claims and is signed by the controller.
Configuration

Your approvals and holds, not ours

Who signs what, when a claim is held and where packets come from are settings, saved and recorded in the audit trail.

SettingDefaultChoose from
Paying a claimDana OkaforDana Okafor · Sam Patel · Omar Haddad
Rejecting a lineAny chargeback reviewerAny chargeback reviewer · Dana Okafor · Omar Haddad
Overriding a held verdictOmar HaddadOmar Haddad · Lena Ortiz
Hold at score70Step up or down; the effect on this cycle is shown beside it
Claim window180 days after invoice90 · 180 · 365 days after invoice
Pay clean lines when one line is heldOnOn · Off
Where packets come fromEDI 844 every 15 minutes, claims mailbox, distributor portalEach source connected or off
Send response files after approvalOn — EDI 849 with reason codesOn · Off
Connections

Works with the files a chargeback already runs on

EDI 844 claim filesdistributor claim files, checked every 15 minutes
PDF claim packetsclaim forms, invoices, purchase orders and delivery notes, by mailbox or portal
Contracts and price listspurchasing-group contracts, tiers, terms, extensions and price revisions
Purchasing-group rostershospitals by HIN and GLN, their tier and the dates they joined or left
Claim historyevery claim line decided since 2021, with its credit memo
EDI 849 and credit memosline-by-line responses with reason codes, and the credit for clean lines
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
2,500
claims a month read first by agents
of packets read before anyone opens one
proven
7
issue patterns checked on every claim
7 fixed rules
from 62,000 past claims
target
2.6min
median from packet to a verdict with rule and evidence

“demo” = seen in the working solution, on its sample claim cycle · “estimated” = our estimate · “typical” = published figures (Drug Channels Institute, as cited by BioXconomy — about $416 billion in brand-drug gross-to-net reductions in 2025; Chronicled whitepaper, 2021 — about 4% of chargebacks in error; Pramata — resubmission windows of 30–60 days). The seven rules reflect a prior analysis of 62,000 claims. People, companies, hospitals, contracts and products named on this page are fictional — characters and sample data in the working solution.

Questions

What contract and pricing teams ask us.

What is chargeback processing software?

Software that takes a distributor's chargeback claim from the EDI 844 file and its supporting documents to a decision, a credit memo and an EDI 849 response. Chargeback Processing adds agents that read the PDF packet behind each claim and cite every value to its page, seven fixed rules that decide the verdict, and a reviewer who approves every payment.

What does it check on every claim?

Seven rules: contract price for the customer's tier on the invoice date, customer eligible on the roster, contract in force, not claimed before, within the ordered quantity, unit of measure, and document unaltered. They match the seven patterns found in a prior analysis of 62,000 claims.

How does it catch duplicate chargebacks?

The history agent searches the permanent claim history — every line since 2021, from every distributor — for the same invoice number, item and quantity. If the line was already credited, rule 4 holds it and shows the earlier claim and its credit memo.

Can it tell when an invoice has been edited?

The validation agent reads the file properties, the text layers and the invoice arithmetic. On the sample packet CB-88213 it found the file modified 28 days after it was created, with “120” placed over “20” and a subtotal that still matched 20 units. Rule 7 holds the line; a person decides.

Does AI decide which claims get paid?

No. Agents read and cite; they never give a verdict. Seven fixed, versioned rules decide, and the same evidence always gives the same verdict. A person approves every payment, every rejection carries a reason code and an e-signature, and paying against a failed rule needs a second approver.

Can we set our own approvers, hold score and claim window?

Yes. Who approves payments, rejections and overrides, the hold score, the claim window, paying clean lines when one is held, the packet sources and sending EDI 849 response files are all settings. Rule changes are tested on last cycle and wait for approval.

How long does it take to go live?

The Agentic Solution Engine builds and deploys it from your requirements and documents — your distribution agreements, purchasing-group contracts, price lists, rosters and a sample of past claim packets — and it goes live once every quality gate has passed. We will walk you through it on your own claims first.

See it on
your claims.

We'll run Chargeback Processing on a sample of your own past claim packets.