# Duplicate and erroneous payment check > Duplicate and erroneous payment check: Whether two payments are the same obligation Checked: vetoed by code. Produces payments stopped or recovered. Source: https://www.sumarity.ai/library/duplicate-and-erroneous-payment-check/ Finance and accounting # Duplicate and erroneous payment check Reads payment runs, the supplier ledger, invoices. Produces payments stopped or recovered. Code works out every figure, the Judgement Engine answers the narrow questions, and whatever stays uncertain goes to a person. Vetoed by codePayables, receivables and payments Start from this workflowMore for finance What it decides ## Narrow questions, each with a check behind it. Whether two payments are the same obligation Vetoed by code: different supplier, amount or invoice proves not. 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 | Payment runs, the supplier ledger, invoices | Produces | Payments stopped or recovered | Who signs | A person on your team, with every figure traced to its document and every call on record | Process | Payables, receivables and payments | Industry | Finance and accounting 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. ReadsPayment runs, the supplier ledger, invoicesCodeReads, matches, ties out and works out every figure.JudgementWhether two payments are the same obligation. 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.ProducesPayments stopped or recovered Duplicate and erroneous payment check · example run Example run | Ref | Item | Value | Decided by | PAY-5512 | Helvetia Druck AG · INV 7710Same supplier, invoice and amount paid on 12.08 | 2,140.00 | Code · matched | PAY-5519 | Nord Logistics · INV 0921Different invoice numbers, same amount · 0.96 · different delivery notes | 870.00 | Engine · checked | PAY-5520 | Alpina Services · INV A-118No earlier payment to this invoice | 4,300.00 | Code · cleared | PAY-5524 | Keller AG · INV 2207 / 2207-1Re-issued invoice or a second order? · 0.68 | 1,980.00 | To a person | PAY-5530 | Fischer Bau · INV 3341Bank details differ from the master | 15,600.00 | 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. ### Payables, receivables and payments in other work Finance ### Cash application Which open invoices a receipt pays; short-pays and deductions Proven by codeFinance ### AP invoice processing with two- and three-way match Which PO and receipt an invoice is for; price and quantity differences Proven by codeFinance ### Collections and dunning Which accounts to chase and how; dispute or delay Checked by the outcome ### More for finance ### Bank reconciliation Which ledger entry a bank line is; why a line is unmatched Proven by codeTested ### Card and payment-processor settlement reconciliation Which sales a payout covers; fee and chargeback lines Proven by code ### Cash application Which open invoices a receipt pays; short-pays and deductions Proven by code 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