# Inventory count reconciliation

> Inventory count reconciliation: Why counts differ from the system Checked: proven by code. Produces adjustments, investigations.

Source: https://www.sumarity.ai/library/inventory-count-reconciliation/

Manufacturing and supply chain 

# Inventory count reconciliation

Reads count sheets, system stock, stock movements. Produces adjustments, investigations. Code works out every figure, the Judgement Engine answers the narrow questions, and whatever stays uncertain goes to a person.

Proven by codeReconciliation and matching
Start from this workflowMore for manufacturing  

What it decides

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

Why counts differ from the system
Proven by code: movements explain the difference. 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 | Count sheets, system stock, stock movements 
| Produces | Adjustments, investigations 
| Who signs | A person on your team, with every figure traced to its document and every call on record 
| Process | Reconciliation and matching 
| 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.

ReadsCount sheets, system stock, stock movementsCodeReads, matches, ties out and works out every figure.JudgementWhy counts differ from the system. 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.ProducesAdjustments, investigations  
Inventory count reconciliation · example run Example run  

| Ref | Item | Value | Decided by  
| A-12 | Bolts M8: count 4,980, system 5,000Within tolerance | −20 | Code · tolerance 
| B-04 | Motors: count 18, system 20Two issued to repairs, not booked · 0.92 | −2 | Engine · proven 
| C-09 | Panels: count 140, system 120Receipt booked late · 0.90 | +20 | Engine · proven 
| D-01 | Controllers: count 3, system 9No movement explains it | −6 | To a person 
| E-11 | Cable drums: exactAgrees | 0 | Code · agrees  
|  

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.

### Reconciliation and matching in other work

Finance

### Bank reconciliation

Which ledger entry a bank line is; why a line is unmatched

Proven by codeTestedFinance

### Card and payment-processor settlement reconciliation

Which sales a payout covers; fee and chargeback lines

Proven by codeFinance

### Intercompany reconciliation

Which entries are the two sides of one transaction

Proven by code

### More for manufacturing

### Purchase order confirmation check

Supplier's confirmation vs the PO: price, quantity, date

Proven by code

### Supplier onboarding and certificates

Documents valid, sanctions, bank details

Cross-checked

### Quality non-conformance triage

Defect category, severity, supplier

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