What Is a Ledger Reversal in Inventory?

A ledger reversal is an inverse entry that cancels a prior inventory receipt or issue without deleting it, so the original and its reversal both remain in the ledger and net to zero. It is how an append-only record corrects itself: never by erasing a line, always by adding an offsetting one.

This entry defines the ledger reversal and shows how it reads inside EDGEBIC by User Solutions. For the wider index of terms, see the manufacturing glossary; for the record it operates on, see what is an inventory ledger; and for the count correction it is often confused with, see inventory adjustment.

How it works

An inventory ledger is append-only, which means no entry is ever changed or removed once written. That rule is what makes the ledger trustworthy as the authoritative on-hand: the balance is the sum of every signed entry, and history cannot be quietly rewritten. But mistakes and cancellations still happen, so the ledger needs a way to undo a movement without breaking the rule.

The reversal is that way. It appends an inverse entry: a receipt of plus 50 is cancelled by a reversal of minus 50, an issue of minus 80 is cancelled by a reversal of plus 80. The original is stamped as reversed, and the reversal entry links back to it by reference. Both lines stay forever, and together they net to zero, so the balance ends where it would have been if the original had never posted.

A reversal differs from an adjustment. An adjustment corrects a count to match the shelf and pegs to no order. A reversal cancels a specific prior movement and links directly to it. One says the shelf differs from the record; the other says this exact transaction should not have counted.

A concrete example

A from-stock job posts an issue of minus 50 to satisfy an order, dropping the balance from 70 to 20. Later, the job is deleted. The system finds that issue, marks it reversed, and appends an inverse entry of plus 50 that links back to it, restoring the balance to 70.

Both lines survive. Entry 3 is the original consumption, now marked reversed; entry 4 is its cancellation, pointing back at entry 3. The ledger tells the whole story: 50 units were consumed, then that consumption was undone, and the stock is back on the shelf. Nothing was erased.

The same pattern makes reschedules safe. On each run, the engine reverses the order's existing consume issue first, then reads on-hand, then posts one fresh issue for the current build quantity. Reschedule three times and you get issues and reversals in pairs, but only a single live consumption ever stands.

How EDGEBIC uses it

In EDGEBIC, reversals are posted through the inventory service whenever a manufacturing order is deleted, reopened, or rescheduled. Delete or reopen triggers a full reversal of both the order's receipts and its issues; reschedule reverses the order's consume issue before the engine reads on-hand, which is what keeps rescheduling idempotent. The link from a ledger entry back to its order is preserved even if the order is later hard-deleted, so the ledger rows never orphan.

Both the original and the reversal survive as a complete audit trail. Because the authoritative on-hand is the ledger sum, a diagnostic watches for a negative authoritative balance on a stocked product, which would mean more issues than receipts posted, so a missing reversal cannot silently push stock below zero.

To see the receipts and issues reversals cancel, read EDGEBIC inventory ledger explained and inventory issue transaction. To understand the reschedule cycle that drives automatic reversals, continue with EDGEBIC rescheduling explained.