Five habits that wreck stock ledger accuracy and how to fix them

Every month the stock ledger shows 12,000 kg of polyester yarn on hand, yet the store notebook says 9,500 kg. The gap—phantom stock—distorts purchasing, ties up cash, and triggers write-offs. The cause is not a faulty barcode scanner or a bug in the ERP; it is five everyday habits that break the document chain. Fix the habits, and the ledger and the notebook will agree.

1. Backdating issues and receipts

Operators issue 500 kg of yarn to the dyehouse on Tuesday, but the transaction is posted on Friday with Tuesday’s date. The ledger temporarily shows 500 kg more than the store actually holds. When the dyehouse returns 200 kg of undyed yarn on Wednesday, the return is also backdated, creating a second phantom entry. Over a month, these small lags accumulate into a material gap.

Backdating is often justified as “keeping the books tidy”, but it severs the link between physical movement and ledger entry. The fix is simple: every issue or receipt must be recorded on the day it happens, using the system clock. Fugen ERP enforces this by locking the posting date to the moment the document is saved, so backdating is impossible without an audit trail.

2. Verbal moves between stores

A supervisor tells the storekeeper, “Move 300 kg of viscose from Store A to Store B; I’ll sign the chit later.” The yarn moves, but the ledger does not. Store A still shows 300 kg, and Store B shows nothing. If the chit is never signed, the ledger never catches up. Verbal moves are common when stores are adjacent or when production is under pressure, but they guarantee phantom stock.

Two rules eliminate verbal moves:

• No material moves without a signed transfer note.
• The transfer note must be entered into the system before the material leaves the sending store.

Fugen ERP’s inventory module enforces the second rule by blocking the transfer note if the sending store does not have sufficient stock at the moment of entry. The physical move cannot happen until the ledger is updated.

3. Skipped GRNs on supplier deliveries

A lorry arrives with 1,000 kg of cotton. The storekeeper unloads it, updates the notebook, but does not raise a Goods Received Note (GRN). The purchase invoice is posted directly to the ledger, so the ledger shows 1,000 kg, but the notebook shows only what was physically counted. If the supplier short-shipped 50 kg, the ledger will never know. Over time, skipped GRNs create a permanent overstatement of stock.

The discipline is straightforward: no invoice is posted until a GRN is raised and matched. Fugen ERP’s purchase module enforces this by blocking invoice posting if the GRN is missing or if the quantities do not match. The system also flags GRNs that are raised but never invoiced, so nothing slips through.

4. Unrecorded scrap and rework

In a typical dyeing line, 3 % of fabric is lost to edge trimming, colour bleed, and machine stops. If the line processes 10,000 m in a week, 300 m should be written off. If only 200 m is recorded, the ledger shows 100 m of phantom stock. The same happens in stitching: rejected garments are thrown into a bin, but the bin is not counted until the end of the month. By then, the ledger has already been used for purchasing and planning.

Illustration: a dyehouse runs 5,000 kg of yarn in a week. Expected loss is 150 kg (3 %). Actual loss recorded is 120 kg. The ledger shows 30 kg of phantom stock. If the plant runs 50 weeks a year, the annual phantom stock is 1,500 kg, enough to distort the year-end stocktake.

Two habits fix unrecorded scrap:

• Every shift must record scrap at the point of creation, not at the end of the day.
• The scrap record must be linked to the production order so the ledger is updated immediately.

Fugen ERP’s production module provides a mobile screen on the shop floor for operators to record scrap against the order. The ledger is updated in real time, so phantom stock cannot accumulate.

5. Parallel logs and shadow spreadsheets

Storekeepers keep a paper notebook “just in case” the system goes down. Supervisors keep a spreadsheet of “real” stock. These parallel logs are updated faster than the ERP, so they become the de facto record. When the ERP is updated days later, the numbers never match. The problem is not the ERP; it is the existence of a second record that is treated as more reliable.

The fix is to make the ERP the only record. If the system is down, material movements are recorded on paper forms that are entered into the ERP as soon as it is back up. No spreadsheet or notebook is allowed to persist beyond the outage.

When software is not the answer

If the plant has no document discipline, software will not create it. Fugen ERP can enforce rules, but it cannot force operators to follow them. The first step is to decide that the ledger will be the single source of truth. If management tolerates parallel logs or verbal moves, the ledger will always disagree with the store notebook, no matter how much is spent on software.

What to do next week

Pick one habit to fix. Start with the one that creates the largest gap. For most plants, it is unrecorded scrap or skipped GRNs.

Checklist for the week:

• Walk the shop floor and count how many scrap bins are not recorded at the end of each shift.
• Review the last ten supplier deliveries and verify that every one has a GRN before the invoice is posted.
• Run a report of all transfer notes raised in the last month and check that every one was entered before the material moved.
• Audit the store notebook and any shadow spreadsheets; decide which one will be retired.
• Train storekeepers and supervisors on the new rule: no material moves without a document.

After one week, measure the gap between the ledger and the store notebook. If it shrinks, the habit is fixed. If not, the discipline is not being followed. Repeat until the gap is zero.