# Proof of delivery against invoice

> Proof of delivery against invoice: Delivered as invoiced Checked: proven by code. Produces matched deliveries, disputes.

Source: https://www.sumarity.ai/library/proof-of-delivery-against-invoice/

Logistics and transport 

# Proof of delivery against invoice

Reads proofs of delivery, invoices. Produces matched deliveries, disputes. Code works out every figure, the Judgement Engine answers the narrow questions, and whatever stays uncertain goes to a person.

Proven by codePayables, receivables and payments
Start from this workflowMore for logistics  

What it decides

## Narrow questions, each with a check behind it.

Delivered as invoiced
Proven by code: quantities, signatures. 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 | Proofs of delivery, invoices 
| Produces | Matched deliveries, disputes 
| 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 | Logistics and transport    

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.

ReadsProofs of delivery, invoicesCodeReads, matches, ties out and works out every figure.JudgementDelivered as invoiced. 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.ProducesMatched deliveries, disputes  
Proof of delivery against invoice · example run Example run  

| Ref | Item | Value | Decided by  
| DL-401 | 40 cartons delivered, 40 invoicedSigned POD |  | Code · matched 
| DL-402 | Signature unreadableCustomer confirmed receipt · 0.92 |  | Engine · proven 
| DL-403 | 38 delivered, 40 invoicedCredit 2 cartons |  | Code · short 
| DL-404 | Delivered to the wrong siteInvoice or not? |  | To a person 
| DL-405 | Damaged on arrival notedDamage claim opened · 0.90 |  | 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.

### 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

### Duplicate and erroneous payment check

Whether two payments are the same obligation

Vetoed by code

### More for logistics

### Freight invoice audit

Charges vs rate card and shipment

Proven by code

### Carrier damage and loss claims

Liability, amount, evidence

Cross-checked

### Fuel card audit

Fill plausible for the vehicle and route

Vetoed 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 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