How to Correct an Over-Reported Production Quantity in EDGEBIC

To correct an over-reported production quantity in EDGEBIC by User Solutions, post a compensating inventory adjustment for the excess, or reopen the manufacturing order to reverse every entry pegged to it. There is no un-report button, and the ledger is append-only by design.

Over-reporting is allowed rather than blocked: the dialog warns and lets you proceed. This article covers what it costs and how to put it right. The wider feature is in production confirmation explained, and the whole task library is at the EDGEBIC how-to hub.

What an Over-Report Actually Breaks

Less than people fear on the schedule side, and more than they expect on the inventory side.

The schedule is safe. The remaining build is held at zero rather than going negative. A job for 100 with 500 reported schedules no work center operations, which is the same outcome as reporting exactly 100. It does not create phantom capacity or negative hours.

Inventory is overstated. The confirmation posted a receipt for the full reported quantity, so on-hand is high by the excess. Those 400 units do not exist.

Nothing flags it. There is no automated check for confirmations exceeding the order quantity. The only record is the ledger, so the correction has to be initiated by a person.

Which means: treat an over-report as an inventory problem with a scheduling side effect, not the other way round.

Before You Start

• You know the correct total. Work out what the confirmed quantity should be before deciding which correction to use.
• You know whether the problem is one entry or the whole job. That is the entire decision below.
• You have the permissions for whichever route you pick. Manual adjustments and reopening orders are different rights.
• You are prepared to re-schedule afterwards, because the plan reflects the last run.

Option 1: A Compensating Adjustment

Right when one entry carried the wrong number and everything else about the job is fine.

1. Open the product's inventory transactions and confirm the size of the excess. Use how to audit the inventory ledger for a part.
2. Post a manual adjustment against the product for the excess quantity, in the direction that brings on-hand back to the truth.
3. Write a comment that names the job and the reason. "Corrects over-report on job J-1042" is the difference between a legible ledger and a mystery in three months. Transaction types are listed in inventory transaction types in the EDGEBIC ledger.
4. Re-check on-hand. It should now match the physical count.
5. Re-schedule the job if the remaining build should change. Note the caveat below.

One important limitation. A manual adjustment fixes stock, not the confirmed quantity. The confirmed figure is the sum of confirmation entries, and an adjustment is a different kind of entry, so the job still reads as having that quantity confirmed and will still plan the reduced build. If the plan needs to grow back, Option 2 is the instrument.

Option 2: Reopen the Order

Right when the whole job's inventory position needs unwinding, or when the remaining build has to be restored.

1. Reopen the manufacturing order.
2. Every inventory entry pegged to that job is reversed, confirmations included. Each original is flagged as reversed and an inverse entry is written pointing back at it, so both rows survive in the audit and the pair cancels to zero.
3. The confirmed quantity drops to zero on its own. Nothing has to be cleaned up, because the quantity was never stored anywhere except as the sum of those entries.
4. Re-report the correct quantity if part of the job genuinely is made.
5. Re-schedule. The build is now sized against the corrected figure.

Deleting the order has the same reversal effect, and is the wrong tool unless you intended to delete the order.

Choosing Between Them

Why There Is No Edit

The ledger is append-only. Entries are never edited or deleted; they are reversed by writing an inverse row that points back at the original. Both remain, and the pair sums to zero.

That discipline is what makes the confirmed quantity safe to derive rather than store. Because the number is the sum of the non-reversed confirmation entries, three useful properties follow for free:

• Nothing can drift. There is no cached copy to fall out of step with the transactions.
• Reschedules preserve it automatically. A reschedule reverses consume issues and leaves receipts alone, so confirmations survive and re-summing gives the same answer.
• Reversal needs no cleanup. Reopen or delete the order and the sum falls to zero by itself, with no orphaned quantity pointing at a dead job.

An editable quantity field would have needed invalidating on every one of those paths, and the first missed one would desync silently. Related reading: why actuals are immutable.

Common Mistakes

Assuming the schedule is wrong. It is not. The build is held at zero, not driven negative. Look at inventory.

Adjusting stock and expecting the build to return. An adjustment does not remove a confirmation. If the job needs to plan those units again, reopen the order.

Posting the adjustment with no comment. Two entries of the same size in opposite directions, weeks apart, with no note, is the ledger equivalent of an unexplained credit.

Re-reporting the difference to "balance it out". Confirmations accumulate, so reporting more only makes the total larger. There is no negative report.

Correcting an over-report on a sub-assembly the same way as an end product. The corrections are the same, but the impact is not: an over-reported sub-assembly inflates component stock and under-builds that branch, so the parent will be short at assembly. See confirming a sub-assembly versus the end product.

Next Steps

Prevention is cheaper than either correction. The dialog shows the quantity already reported and the remaining figure before you commit, so the two habits that avoid this entirely are reading the header before typing and reporting increments rather than restated totals. Both are covered in how to report produced quantity on a job.

If on-hand and the ledger disagree after any of this, my on-hand quantity does not match the inventory ledger is the diagnostic route.

The takeaway

An over-report is an inventory error, not a scheduling one, and it will not announce itself. Fix the stock with a commented adjustment when one number was wrong, and reopen the order when the job's whole position needs unwinding. Either way the ledger keeps both sides of the story, which is exactly why the confirmed quantity can be trusted after the fact. See the platform at EDGEBIC.