Negative balances: a hidden signal in your records system

The records system shows the stock of an item as −12 units. There are no minus units on a shelf, so the entry in the system is wrong. Many people shrug it off as "just how the program behaves": sales go through, work does not stop. But every negative balance is the trace of a problem: a document entered late, an item that left under another name, or a transfer document that was not fully posted. Analyse this signal and you get a ready-made list for improving data quality.

Where negative balances come from

The most common causes:

• A sale was posted before the receipt document: the goods have arrived but the storekeeper has not yet entered them into the system.
• A mix-up: the sale went to another variant, so one item shows minus and its look-alike shows surplus.
• In a transfer between warehouses, the sending side was posted and the receiving side was not.
• A unit of measure was confused: the sale is in pieces while the receipt was entered in cartons.
• A return or write-off was processed with the wrong document.

Example: 38 items

Say the warehouse has 1 200 items and 38 of them have a negative balance: that is 38 ÷ 1 200 ≈ 3.2 percent. The negatives add up to −7.2 million so'm and the positives to 430 million. The system shows a total of 430 − 7.2 = 422.8 million: the negatives quietly reduce the overall sum. The five largest items account for 4.1 million, about 57 percent of the negative total.

By cause, the 38 cases break down as follows: 14 late-entered receipts, 11 mix-ups, 7 unfinished transfers, 4 unit-of-measure errors, 2 unknown. The last two cases with no known cause cannot simply be left either: they have to be identified by a count. Of the 38, 25, nearly two thirds, come from late documents and mix-ups, and both can be fixed through the process.

Finding the pair is easy: look for a positive item with a similar name next to the negative one. For instance, if "Cable 2 m" shows −12 while "Cable 1 m" shows 12 units more in the records than really exist, this is a classic mix-up: the total is zero, but both records are wrong. You close such a pair with one document and the balance becomes right on both records.

Why this does harm

• Analysis is distorted. Turnover and days of stock are calculated from a sum reduced by the negatives.
• Cost becomes unreliable. When goods with no balance are sold, many systems calculate cost imprecisely, so the margin also comes out wrong.
• The paired positive balance is hidden. In a mix-up one side goes into minus while the other gets an artificial plus, so the value of inventory is wrong too.
• The purchase plan breaks. A negative balance enters the formula with a minus sign and inflates the order.
• Counting gets confused. You cannot count −12: it is unclear what part of a count difference comes from the records.

A weekly routine

1. Export from the system the list of items with a balance below zero.
2. Sort each by cause and look for the paired positive balance.
3. Correct the error with a document: post a late receipt with the actual date, and a mix-up with a separate document.
4. Assign an owner and a deadline to each group, for example three working days.
5. Track the measure: the number, share and value of negative items should head towards zero.

Prevention

If the system lets you forbid selling beyond the balance, switch it on. Then a receipt must be entered as soon as goods arrive, otherwise sales stop: this enforces discipline. Enter receipts on the day of arrival and close transfers on both sides the same day. Spell out responsibility: who enters the document and who confirms it. For similar goods, scanner confirmation reduces mix-ups.

Add one line to the monthly report: the share of items with a negative balance. The aim is simple: the figure should fall from month to month. When the figure is visible to management, discipline in entering documents on time grows too.

Conclusion

A negative balance reveals the error, not hides it. Take the list every week, find the cause and correct it with a document. CountLab compares count results with the records, uses discrepancy analysis to separate negative balances and their paired surpluses by cause, and gives a short list for data quality.