Before choosing a number, understand why the records disagree.

A stock spreadsheet says 120. The warehouse record says 168. The order team says 144. Choosing the newest or largest number would miss the actual distinction: the records may describe different moments, units, or states.

Start by writing the question in business terms. Do you need physical stock at a particular cut-off, stock available after reservations, or an amount you can promise a customer now? Those are not interchangeable.

The same discipline applies to booked versus recognized revenue, leads versus signed clients, and accepted invoices versus paid invoices. A shared column heading is not enough to establish a shared definition.

1. Identity. Confirm the entity, product, location, account, and identifiers. Preserve leading zeros and the original code alongside any mapped name.
2. Time. Record each source’s business cut-off, not just when someone downloaded it. Identify the interval that needs explaining.
3. Definition. Separate states such as reserved, dispatched, accepted, or paid. Decide which states belong in the requested measure.
4. Unit. Check cases versus individual items, currencies, tax treatment, and rounding. Show the conversion and its source.
5. Completeness. Establish which movements or documents should exist. A few matching records do not prove that nothing is missing.
6. Ownership. Name the person who can confirm an exception and authorize a change. Keep the original and the explanation together.

Treating a blank as zero. A receiving reference without its document cannot establish how many cases arrived. Keep the current balance unknown until the accepted quantity is supported.

Counting the same change twice. An order reservation and a later shipment may describe successive states of the same stock. Subtracting both without the correct state transition can understate availability.

Trusting a copied total as an independent source. A spreadsheet that repeats another spreadsheet’s value is not a second confirmation. Follow the dependency to the original, and mark any unavailable upstream record.

Overwriting the discrepancy. A corrected number without its original version, date, explanation, and reviewer creates another future investigation. A source amendment should invalidate the affected review.

AI can help identify document types, extract candidate fields, locate related records, and draft an explanation of a difference. A useful interface lets the reviewer inspect the original field and its source, rather than accepting a fluent summary as proof.

Identifiers, unit conversions, totals, and allowed state transitions need explicit rules and checks. Source permissions, document versions, and missing records remain visible. A model’s confidence is not a substitute for a receiving record or a complete reporting period.

Keep the action boundary separate from the explanation. Preparing a reconciled record should not automatically adjust inventory, change a financial entry, or promise stock to a customer. Those actions need the company’s defined authorization and controls.

For the next recurring discrepancy, prepare a short reconciliation brief:

• The decision this number is meant to support.
• The measure’s definition, unit, entity, and cut-off.
• The original values and exact source versions.
• The calculation or state change explaining the difference.
• Any missing evidence, its owner, and what must wait for it.
• The reviewer, authorized next action, and retained original.

If the team cannot complete those fields, start with the evidence gap. Automating an unexplained number simply moves the uncertainty faster.

Bring the recurring discrepancy and the workflow it affects. Do not include confidential source records in your initial inquiry.