Yesterday we set up the item (Round 23). Today the shelf disagrees with the system. Someone dropped a case, a count came back short, or a quantity was keyed wrong last month. Every inventory team knows this moment — and every ERP has a way to fix it. The question is how many decisions stand between “the number is wrong” and “the number is right.”
How You Do It in Dynamics GP
Step 1: Pick the right transaction type. Per Microsoft’s Inventory Control transactions guide, the Item Transaction Entry window handles two distinct types, and they post differently. An adjustment records a miscellaneous increase or decrease and posts to your Inventory and Inventory Offset accounts. A variance records a physical-count difference and posts to Inventory and Variance accounts. Pick the wrong one and your GL tells the wrong story — so the decision matters before you type a single quantity.
Step 2: Open Item Transaction Entry. Inventory > Transactions > Transaction Entry. Choose the document type, enter a document number and date, then the item, site, and quantity — negative for decreases. Serial- or lot-tracked item? The Item Lot Number Entry window opens so you can say exactly which lot shrank. GP’s Inventory Control documentation also lets you attach reason codes to lines, so “damaged” and “cycle count” stay distinguishable — if you set the codes up first.
Step 3: Batch and post. Most GP shops run adjustments through Inventory Batch Entry so a reviewer can check them before posting. Then post the batch — and depending on your posting setup, post it through to General Ledger too.
Step 4: Fixing a keying mistake means backing it out. Posted 8 when you meant 10? GP’s correction method is an adjusting entry that reverses the original — and to build it, you need to know how the first transaction was entered: dates, quantities, and which accounts it hit. It works, but it rewards the person who kept good notes.
For full counts: GP has Stock Count Schedules and Stock Count Entry to manage a physical count and generate the variances for you — a separate cycle with its own windows.
How You Do It in Business Central
Step 1 (the everyday fix): adjust right from the item card. Per Microsoft’s count, adjust, and reclassify guide, when one item’s quantity is simply wrong, you can use the Adjust Inventory action from the item card or item list. Type the quantity that’s actually on the shelf; BC posts the difference. No document type decision, no batch — done.
Step 2 (the standard route): the Item Journal. For multi-line adjustments, open the Item Journal, pick entry type Positive Adjustment or Negative Adjustment, enter item, location, and quantity, and post. The cost side takes care of itself: BC automatically posts inventory value changes to the right inventory and adjustment accounts in the general ledger — no “did that batch post through to GL?” follow-up.
Step 3 (count season): the Physical Inventory Journal. This is where BC pulls ahead. Choose Calculate Inventory and BC fills the journal with expected quantities on its own. Print the count list, send the team to the warehouse, key in the actual counts — BC computes each difference and posts the variances when you post the journal. Expected, counted, difference: one page.
Step 4 (moved, not missing): the Reclassification Journal. If the stock isn’t gone — it’s just in the another location, or tagged with the wrong dimension or lot — the Item Reclassification Journal moves it without faking an adjustment. That keeps your shrinkage numbers honest, and your dimensions clean for reporting.
Side by Side
| Dynamics GP | Business Central |
|---|
| Dynamics GP | Business Central | |
|---|---|---|
| Quick one-item fix | Item Transaction Entry document | Adjust Inventory from the item card |
| Everyday adjustments | Adjustment document type + batch | Item Journal, positive/negative lines |
| Count variances | Variance document type or Stock Count windows | Physical Inventory Journal with Calculate Inventory |
| Expected quantities | You look them up | Calculated into the journal for you |
| GL impact | Depends on type chosen and posting setup | Posted automatically to the right accounts |
| Moved stock | Transfer transaction | Reclassification Journal (location, dimension, lot) |
| Fixing a keyed error | Reverse-and-reenter, from your notes | Adjust to the correct quantity; costs re-adjust |
| Reason tracking | Reason codes (if set up) | Reason codes on journal lines |
Why BC Comes Out Ahead
GP’s inventory transactions are precise, and the adjustment-versus-variance split gives accountants clean GL buckets — when everyone picks the right type every time. That’s the catch: the system depends on the user knowing the difference, remembering the batch, and confirming the GL posting.
Business Central keeps the same accounting rigor but moves the burden off the user. The item card fix handles the everyday “shelf says three” moment in seconds. Calculate Inventory does the expected-quantity homework before a count. And the GL entries land automatically in the right accounts, every time, because the posting setup — not the person typing — decides where values go. Fewer decisions per fix means fewer wrong decisions per year. That’s been the theme of this whole series, and inventory adjustments might be its clearest example yet.
Thinking About the Switch?
Aisling Dynamics helps GP teams keep inventory transactions and stock counts tidy, and helps companies move to Business Central when fixing a quantity should take seconds, not a decision tree. If your cycle counts feel like a second job, meet our team, browse the GP vs. BC hub, or contact us at (251) 293-0555.
Come back tomorrow for Round 25: inquiries and reporting — GP’s SmartLists vs. BC’s list pages, filtering, and Analysis Mode.