How to Make an Inventory Adjustment in EDGEBIC

To make an inventory adjustment in EDGEBIC, you post a signed delta that corrects on-hand after a physical count, not a new total. In EDGEBIC by User Solutions an adjustment is the one manual movement that takes a positive or negative value, and it becomes a permanent entry rather than an edit to the balance. This post covers exactly what number to enter, why it is a delta and not a count, and how to undo one cleanly.

An adjustment sits alongside receipts and issues as a manual movement type. For all three together, read how to record receipts, issues and adjustments. This post narrows to the count correction. Availability varies by installation, so check which inventory features your build exposes.

An adjustment is a one-line action with weighty consequences, which is why the sign and the comment carry so much of the load. Because the ledger never forgets, the entry you post today is the record a controller or a future planner reads to understand why on-hand moved. Two habits keep that record clean: post the gap between physical and system, never the counted total, and name the count and its location in the comment. Do both and cycle counting becomes a self-explaining trail rather than a scatter of unexplained deltas that someone has to reconstruct months later. The stakes are quiet but real: an adjustment posted with the wrong sign or the wrong magnitude does not error out, it simply moves on-hand to the wrong place, and every projection, days-of-cover reading, and replenishment suggestion downstream inherits that error until someone notices and corrects it.

Before You Start

• You have a physical count for the product and the current system on-hand to compare it against.
• You have worked out the difference and its direction: physical higher than system is a positive delta, physical lower is a negative delta.
• You have a short label for the count, such as the date and the location, to put in the comment.

Post the Adjustment

1. Click Inventory in the left navigation.
2. Select the counted product in the dropdown at the top of the view.
3. Open the Adjustments sub-pane.
4. In the Qty field, enter the signed delta. Positive if the physical count is above the system figure, negative if it is below.
5. Type a Comment that names the count, such as "Cycle count 2026-07-20, aisle B".
6. Click Post Adjustment.

The number you enter is the gap, not the shelf total. If the system says 52 and you counted 47, you enter minus 5, not 47. Getting this wrong is the single most common error, and it compounds because the ledger keeps the mistake.

Posting an Adjustment From the Matrix

You can also correct a count from the On-Hand Matrix: switch the lens to on-hand, double-click the product cell, choose Adjustment in the movement dialog, and enter the signed delta. One thing to know up front: an adjustment posted this way always stamps the current date. It ignores the column's bucket date, unlike a receipt or issue from the same dialog. The correction applies as of now.

What Changes When You Save

A new ledger entry is appended with an adjustment type and the signed delta exactly as you typed it. On-hand recalculates from the full ledger sum inside the same transaction, so it moves by the delta and nothing else. Every pane on the Inventory view refreshes, and the projected balance rows shift to reflect the corrected on-hand.

A non-zero delta is required. A zero adjustment is rejected, because it would record nothing and clutter the ledger.

Where Adjustments Fit in Cycle Counting

An adjustment is the posting step at the end of a cycle count, and treating it that way keeps the ledger readable. A disciplined process counts a location, compares the count to the system figure, and posts one adjustment per part for the gap, with a comment that names the count run and the location. Done this way, a quarter of adjustments reads as a clean sequence of reconciliations rather than a scatter of unexplained deltas. The comment is doing real work here: six months on, "Cycle count 2026-07-20, aisle B" tells an auditor exactly which count produced the correction, while a blank comment leaves them guessing.

There is a useful side effect. If the on-hand cache has drifted away from the true ledger sum, posting any movement, including an adjustment, recomputes on-hand inside the same transaction and heals the drift. So a cycle-count adjustment both corrects the physical discrepancy and refreshes the cache in one action. The plant-wide anomaly report flags cache drift on a full scan, and a routine of counting and adjusting keeps that check clean.

How to Check It Worked

1. Open the Transaction History pane for the product.
2. Confirm a new row appears with an adjustment type, your comment, and the signed delta.
3. Read the Balance After column on that row: it should equal your physical count.
4. Glance at the KPI strip. Current On-Hand should now match the shelf, because it sums the authoritative ledger.

If Balance After does not equal your physical count, you almost certainly entered the total instead of the delta. Post an equal and opposite adjustment to unwind it, then re-enter the correct gap.

Common Mistakes

• Entering the counted total instead of the delta. The field is the difference between physical and system, signed by direction. Entering the shelf count subtracts far too much.
• Getting the sign backward. Physical above system is positive; physical below system is negative. A backward sign doubles the error in the wrong direction.
• Expecting a matrix adjustment to sit on the count date. An adjustment always timestamps to now and ignores the cell's bucket date. Only receipts and issues from the matrix honor the column date.
• Trying to delete a bad entry. There is no delete. To undo an adjustment, post an equal and opposite one. Both rows stay in the ledger and net to zero, which is the audit trail working as designed.
• Posting many tiny adjustments instead of one. A single reconciling entry per part per count reads cleanly. Breaking the same correction into a handful of small deltas clutters the history and makes the trail harder to follow later, with no benefit.

When an adjustment is not enough and you need to unwind an engine-posted movement, read how to reverse an inventory transaction. For the reasoning behind append-only corrections, read the inventory ledger explained, and browse every task in the EDGEBIC how-to library.