# Warranty claim validation > Warranty claim validation: In warranty, covered failure, parts Checked: proven by code. Produces approved or rejected claims. Source: https://www.sumarity.ai/library/warranty-claim-validation/ Manufacturing and supply chain # Warranty claim validation Reads warranty claims, serial numbers, sales records, warranty terms. Produces approved or rejected claims. Code works out every figure, the Judgement Engine answers the narrow questions, and whatever stays uncertain goes to a person. Proven by codeClaims, disputes and exceptions Start from this workflowMore for manufacturing What it decides ## Narrow questions, each with a check behind it. In warranty, covered failure, parts Proven by code: serial, dates. 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. Cross-checked: terms. A second source has to agree: a register, a contract, a list. When it does the judgement settles; when it doesn't, a person decides. | Reads | Warranty claims, serial numbers, sales records, warranty terms | Produces | Approved or rejected claims | Who signs | A person on your team, with every figure traced to its document and every call on record | Process | Claims, disputes and exceptions | Industry | Manufacturing and supply chain 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. ReadsWarranty claims, serial numbers, sales records, warranty termsCodeReads, matches, ties out and works out every figure.JudgementIn warranty, covered failure, parts. 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.ProducesApproved or rejected claims Warranty claim validation · example run Example run | Ref | Item | Value | Decided by | WC-11 | Pump, serial 88120Sold 14 months ago, 24-month warranty | | Code · in warranty | WC-12 | Bearing failureCovered failure mode · 0.94 | 380.00 | Engine · proven | WC-13 | Water damageMisuse excluded · 0.90 | | Engine · proven | WC-14 | Serial not foundNot sold by us? | | To a person | WC-15 | Labour hours 6.0Standard time is 2.5 | | To a person | Settled 3 To a person 2 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. ### Claims, disputes and exceptions in other work Finance ### Customer deductions and short-pay disputes Valid deduction (promotion, damage) or not Proven by codeBanking ### Payment exceptions and investigations Why a payment failed or is queried; the action Proven by codeBanking ### Card disputes and chargebacks Network reason code; evidence enough to fight Cross-checked ### More for manufacturing ### Purchase order confirmation check Supplier's confirmation vs the PO: price, quantity, date Proven by code ### Inventory count reconciliation Why counts differ from the system Proven by code ### Supplier onboarding and certificates Documents valid, sanctions, bank details 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