Remittance posting and payer reconciliation (835s)
Reads remittance files (835), claims billed, bank deposits. Produces posted payments, underpayments. Code works out every figure, the Judgement Engine answers the narrow questions, and whatever stays uncertain goes to a person.
Narrow questions, each with a check behind it.
Which claims a remittance pays; adjustments
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 | Remittance files (835), claims billed, bank deposits |
| Produces | Posted payments, underpayments |
| Who signs | A person on your team, with every figure traced to its document and every call on record |
| Process | Reconciliation and matching |
| Industry | Healthcare |
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.
| Ref | Item | Value | Decided by |
|---|---|---|---|
| 835-1201 | Payer A remittance, 42 claimsSum ties to the deposit | 18,402.60 | Code · tied |
| CLM-8812 | Paid at the contract rateMatches the fee schedule | 240.00 | Code · matched |
| CLM-8820 | Contractual adjustment CO-45Expected for this payer · 0.95 | −60.00 | Engine · proven |
| CLM-8833 | Underpaid by 85.00Below the contract rate | 155.00 | To a person |
| CLM-8840 | Patient responsibility PR-2Coinsurance as per plan · 0.93 | 40.00 | Engine · proven |
|
Settled 4
To a person 1
Settled wrong 0
| |||
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.
Start from what's closest.
Reconciliation and matching in other work
Bank reconciliation
Which ledger entry a bank line is; why a line is unmatched
FinanceCard and payment-processor settlement reconciliation
Which sales a payout covers; fee and chargeback lines
FinanceIntercompany reconciliation
Which entries are the two sides of one transaction
More for healthcare
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.