# Meter-to-bill validation > Meter-to-bill validation: Reading plausible; bill right Checked: vetoed by code. Produces released or held bills. Source: https://www.sumarity.ai/library/meter-to-bill-validation/ Energy and utilities # Meter-to-bill validation Reads meter readings, bills, consumption history. Produces released or held bills. Code works out every figure, the Judgement Engine answers the narrow questions, and whatever stays uncertain goes to a person. Vetoed by codeBilling and revenue assurance Start from this workflowMore for energy What it decides ## Narrow questions, each with a check behind it. Reading plausible; bill right Vetoed by code: consumption range, history. Code can't prove the answer right, but it can prove it wrong: an amount out of range, an impossible date, a name not on the document. Many settle; the rest go to a person. | Reads | Meter readings, bills, consumption history | Produces | Released or held bills | 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 | Energy and utilities 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. ReadsMeter readings, bills, consumption historyCodeReads, matches, ties out and works out every figure.JudgementReading plausible; bill right. Settles only when it clears the cutoff and no check in code rules it out.A personGets whatever stays uncertain, with the evidence. Their ruling tunes the next run.ProducesReleased or held bills Meter-to-bill validation · example run Example run | Ref | Item | Value | Decided by | M-441 | Reading 12,840 kWhWithin the usual range | | Code · plausible | M-442 | Reading lower than lastMeter replaced 02.09 · 0.95 | | Engine · checked | M-443 | Consumption +300%Heat pump installed · 0.88 | | Engine · checked | M-444 | Estimated 4 times in a rowHold the bill, ask for a reading | | To a person | M-445 | Tariff changeApplied from 01.09 | | Code · applied | 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 codeHealthcare ### Charge capture reconciliation Services delivered vs billed Proven by codeRetail and hospitality ### Supplier rebates and promotional allowances Rebate earned under which agreement Proven by code ### More for energy ### Energy trade confirmation matching Our trade vs the counterparty's confirmation Proven by code ### Renewable certificate reconciliation (REGOs, GOs) Certificates vs generation and sales Proven by code ### Field work order close-out Work done as recorded; billable 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 can't prove the answer right, but it can prove it wrong: an amount out of range, an impossible date, a name not on the document. Many settle; the rest go to 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