# Charge capture reconciliation > Charge capture reconciliation: Services delivered vs billed Checked: proven by code. Produces missing charges, corrections. Source: https://www.sumarity.ai/library/charge-capture-reconciliation/ Healthcare # Charge capture reconciliation Reads services delivered, charges billed. Produces missing charges, corrections. Code works out every figure, the Judgement Engine answers the narrow questions, and whatever stays uncertain goes to a person. Proven by codeBilling and revenue assurance Start from this workflowMore for healthcare What it decides ## Narrow questions, each with a check behind it. Services delivered vs billed Proven by code. Code proves the answer from the data itself: totals tie, a match is exact, the quote is on the document. Most of these judgements settle without a person. | Reads | Services delivered, charges billed | Produces | Missing charges, corrections | Who signs | A person on your team, with every figure traced to its document and every call on record | Process | Billing and revenue assurance | Industry | Healthcare See it run ## Every line, decided where it's safest. An example run. Each stage lights up as a line is decided there; pick a stage to see its lines. ReadsServices delivered, charges billedCodeReads, matches, ties out and works out every figure.JudgementServices delivered vs billed. Settles only when it clears the cutoff and code proves it.A personGets whatever stays uncertain, with the evidence. Their ruling tunes the next run.ProducesMissing charges, corrections Charge capture reconciliation · example run Example run | Ref | Item | Value | Decided by | DAY-0912 | Services recorded vs billed212 of 214 billed | | Code · tied | SVC-41 | Infusion not billedCharge missing · 0.95 | 480.00 | Engine · proven | SVC-42 | Supply item not billedBillable for this payer? · 0.70 | 35.00 | To a person | SVC-43 | Duplicate chargeSame service twice | 120.00 | Code · removed | SVC-44 | Late charge entryBelongs to visit 0911 · 0.92 | 260.00 | Engine · proven | Settled 4 To a person 1 Settled wrong 0 Illustrative lines. Amber rows are the Judgement Engine's calls; each settles only above its cutoff and when its check agrees. What it could save ## Your volumes in. Your hours out. In our tests, between 24% and 42% of items still went to a person after tuning. Set your own share; a pilot measures it on your data. Items per run Runs per month Minutes per item by hand Cost per hour Share of items that still need a person: 30% By hand today80 ha month With Sumarity24 ha month, for the items people decide Saved56 hCHF 53,760 a year Related ## Start from what's closest. ### Billing and revenue assurance in other work Asset management ### Management and performance fee check Fee basis, rates, periods Proven by codeRetail and hospitality ### Supplier rebates and promotional allowances Rebate earned under which agreement Proven by codeEnergy ### Meter-to-bill validation Reading plausible; bill right Vetoed by code ### More for healthcare ### Remittance posting and payer reconciliation (835s) Which claims a remittance pays; adjustments Proven by code ### Claim denial management and appeals Denial reason, appealable, evidence Checked by the outcome ### Prior authorisation Criteria met from the record Cross-checked Questions ## What buyers ask What happens when Sumarity isn't sure? Nothing settles below the cutoff, or when the check disagrees. The item goes to a person in the inbox with what the engine saw, its best answer and the runner-up. The person's ruling is kept and tunes the next run. How are its judgements checked? Code proves the answer from the data itself: totals tie, a match is exact, the quote is on the document. Most of these judgements settle without a person. Can we change it to fit how we work? Yes. Start from this workflow and describe your differences in plain words. The design assistant revises it, the validator checks it, your expert reviews it on the canvas, and your admin publishes it. Does it read our files as they are? Yes: spreadsheets and CSV in any layout, PDFs, bank formats and e-mail attachments. Sumarity suggests how each column maps, proves the mapping on a sample and remembers it once a person confirms it. Where does our data go? Sumarity runs in Zurich. Your data, backups and logs are stored in Switzerland. How does it get better? Your team's rulings become an answer key. Better questions and cutoffs are proposed, tested on data they haven't seen, and published only when your admin approves. It improves itself, with permission. ## Start from this workflow. Run it on your data. A pilot runs alongside your own process for a few weeks, at our cost, and ends in a line-by-line comparison. Talk to usBack to the library