Troubleshooting Inventory
Inventory troubleshooting calls, item setup, quantity/value issues, linked accounts, serial/location behavior, transaction history, builds, moves, and escalation.
🔎 Keyword Search
📚 Converted Guide Sections
1How to Use This Guide
How to Use This Guide
This guide is designed as an internal playbook for inventory troubleshooting calls. It is meant to give reps a repeatable way to think, ask questions, test safely, and know when to escalate.
Core principle |
Do not jump straight to an answer. Inventory cases often look like a bad report, bad serial number, or bad item count at first, but the real cause is usually transaction history: imported items with no history, purchases recorded in the wrong order, sales entered before stock existed, builds or adjustments recorded incorrectly, location movement issues, or historical edits that changed value without fixing quantity. |
|---|
| What this guide covers | Why it matters for inventory cases |
|---|---|
| Inventory discovery and call control | Inventory issues often sound simple at first, but the actual cause may be item setup, transaction order, locations, serial numbers, linked accounts, or historical adjustments. |
| Question phase and evidence gathering | The rep needs to separate quantity problems from value problems, and reporting problems from transaction-entry problems, before changing anything. |
| Troubleshooting/testing workflow | Most inventory cases require tracing the item through purchases, receipts, bills, inventory journals, adjustments, builds, moves, and sales until the break point is found. |
| Real CRM case patterns | The case examples show recurring inventory patterns: negative value with positive quantity, imported items without history, serial/location mismatches, and blocked deletions. |
2Table of Contents
Table of Contents
• 1. Support Mindset for Inventory Calls
• 2. The Four-Phase Inventory Investigation Framework
• 3. Inventory Baseline Discovery Checklist
• 4. Fast Triage Matrix: Symptoms, Causes, and First Checks
• 5. Deep-Dive Modules: How to Troubleshoot Inventory Issues
• 6. Real-World Case Library and Coaching Notes
• 7. Escalation Standards and Supervisor Hand-Off Format
3Support Mindset for Inventory Calls
1. Support Mindset for Inventory Calls
Inventory support is different from general how-to support. Customers are often under pressure because inventory affects sales, purchasing, fulfillment, margins, and financial reporting. A rep should sound calm, structured, and curious. The goal is not to prove the customer wrong; the goal is to prove the item history and setup trail.
What reps must assume at the start
| Assumption | What the rep should do |
|---|---|
| The customer may be correct that the quantity, value, or report is wrong. | Take the concern seriously and ask for the exact item, location, report, transaction, and date range where the issue is visible. |
| The cause may not be in the window the customer is looking at. | Trace the item through Item Information, linked accounts, history, purchases, receipts, bills, inventory journals, adjustments, builds, moves, and sales. |
| Quantity issues and value issues are not always the same problem. | Separate on-hand quantity, average cost, and current inventory value before deciding on a fix. |
| Serial/location issues may be broader than one item. | Ask whether the same mismatch appears on other items, then collect the full affected list before escalating. |
| General ledger entries do not repair item history. | Distinguish between fixing inventory records in the inventory subsystem and posting a separate accounting entry for the CPA. |
Few things that reps should not do during applicable scenarios
Do not tell the customer to type the final desired on-hand count directly into the Quantity field in Adjust Inventory. That field expects the change amount, not the ending balance.
Do not promise that importing an item list will also import quantity on hand or inventory value. Those come from transactions, opening balances, receipts, builds, or adjustments.
Do not delete a purchase, bill, or inventory journal before checking for later sales, payments, serial usage, or other dependent inventory transactions.
Do not use both Adjust Inventory and a separate General Journal to book the same shrinkage or loss unless the accountant explicitly wants two different purposes handled.
Rep coaching point
A useful inventory support phrase goes something like: “Let’s trace what AccountEdge is reading from. We’ll compare the item setup, the current item card, and the transaction history before we decide whether this is setup, workflow, historical entry, or file-specific.”
4The Four-Phase Inventory Investigation Framework
2. The Four-Phase Inventory Investigation Framework
All inventory cases should move in this order: Discovery, Question Phase, Troubleshooting/Testing, and Implement Solution.
| Phase | Goal | Rep actions | Exit criteria |
|---|---|---|---|
| 1. Discovery of issue | Understand exactly what the customer sees and where they see it. | Get the product/build, OS, item number, item type, location, serial/lot context, current quantity/value, error message, sample report, sample transaction, and whether the issue is historical or current. | Rep can restate the issue in one sentence and name the exact AE window, report, or error involved. |
| 2. Question phase | Clarify setup, transaction order, and what changed so the possible causes get smaller. | Ask whether this affects one item or many, one location or all locations, quantity or value or both, serial-tracked or not, and whether a purchase, receipt, bill, adjustment, build, move, or sale was entered earlier. | Rep has a short list of likely causes and knows which report or window will confirm each one. |
| 3. Troubleshooting/testing | Prove the cause before altering live data. | Compare current item state against transaction history, run the right report, test in a sample file when possible, and only record reversible tests in the customer file if necessary and understood. | Rep can explain why AccountEdge is showing the current result, or can clearly justify why file research is needed. |
| 4. Implement solution | Apply the confirmed fix and verify the downstream effect. | Make the adjustment, reverse and re-record dependent transactions when needed, update setup or preferences if required, or escalate with a clear hand-off and supporting evidence. | Customer sees the corrected result or receives a precise next step with known limits and expectations. |
Phase 1: Discovery of Issue
Discovery is where the rep collects enough evidence to avoid guessing. For inventory calls, one screenshot is rarely enough. The rep needs both the current result and the transaction path that created it.
| Discovery item | Ask / verify | Why it matters |
|---|---|---|
| Product and build | Pro or NE? Mac or Windows? Current build? Is the file local or hosted? | Inventory menus, diagnostic options, and environmental issues can vary by version and deployment. |
| Affected item scope | One item, one group of items, one location, one vendor workflow, or all inventory? | A single-item issue points toward item setup or transaction history; a multi-item issue may point toward process, data health, or file-wide behavior. |
| Quantity vs value vs report | Is the problem wrong on-hand quantity, wrong current value, wrong average cost, wrong serial availability, or a report expectation issue? | These are different problems with different correction paths. |
| Transaction chain | Was there a purchase order, receive items, bill, inventory adjustment, build/auto-build, move items, sale, return, or deletion before the issue appeared? | Inventory problems are often caused by sequence, not just by setup. |
| Linked accounts and preferences | Check Setup > Linked Accounts > Inventory Accounts and Setup > Preferences > Inventory. | Incorrect linked accounts or preferences can change how transactions behave and how users interpret the result. |
Phase 2: Question Phase
The question phase is where the rep turns a complaint into a testable sequence.
| Issue type | Best questions to ask |
|---|---|
| Cannot record a sale or invoice | Is quantity on hand positive? Is inventory value negative? Was the item previously sold with insufficient on-hand quantities allowed? Did prior adjustments change value without fixing quantity? |
| Imported items show no quantity/value | Did the customer only import the item list? Were opening balances entered? Were purchases or inventory adjustments ever recorded for these items? |
| Serial numbers show as available but cannot be selected | Was the source PO received or converted properly? Is the item serial-tracked? Are the serials tied to a different location or transaction state? |
| Location quantity does not match serial availability | Does the issue affect one location or several? One item or many? Were items moved between locations? Did Optimize/Verify find anything? |
| Auto-Build / Build issue | Are the components inventoried items? Do they have positive on-hand quantities and value? Did the customer enter a build quantity or a desired ending quantity? |
| Cannot delete purchase, bill, or inventory journal | Were later sales, serial assignments, payments, or other IJs posted against the same item? Is the item already at zero on hand? |
Phase 3: Troubleshooting and Testing
Testing should be disciplined. Change one variable at a time and avoid irreversible edits until the break point is clear.
Always test in the widgets file FIRST if possible BUT…
| Safe testing rule | When testing in the customer file, prefer reports, item history, and other non-posting steps first. If recording is necessary, explain what will be recorded, verify it is reversible, and delete the test transaction immediately afterward. |
|---|
1. Replicate the setup in a sample file when possible.
2. Compare the affected item against a similar working item when that helps isolate setup vs history.
3. Open the item card and check Quantity On Hand, Current Value, Average Cost, and History before changing data.
4. Use the smallest useful report first, then broaden the range only after the base result is understood.
5. When multiple items are involved, collect the full affected list before escalating.
Phase 4: Implement Solution
Implementation should include the fix, a verification step, and a customer-facing explanation.
| Fix type | What to explain to the customer |
|---|---|
| Inventory adjustment | Explain whether the adjustment changes quantity, value, or both, and confirm the account being used. Make sure the customer understands the adjustment amount versus the desired ending balance. |
| Transaction reversal and re-record | Explain which dependent transactions must be reversed first, why the current sequence blocks the change, and whether future reports will be cleaner after re-entry. |
| Linked account or preference change | Explain that linked-account and preference changes usually affect future behavior. Historical transactions may still need to be deleted and re-recorded if the customer wants them to display differently. |
| Manual accounting workaround | State clearly what the workaround affects in the general ledger versus the inventory subsystem, and tell the customer to confirm account selection with their CPA when support is outside accounting advice. |
| Escalation / file research | Do not promise a bug. State what was verified, what remains unknown, what assumptions still exist, and what file or screenshots are required to confirm the root cause. |
5Inventory Baseline Discovery Checklist
3. Inventory Baseline Discovery Checklist
Many inventory calls get easier once the rep confirms what kind of history actually exists in the file. Customers often think item setup, item import, opening balances, purchases, receipts, and inventory adjustments are interchangeable. They are not.
| Inventory setup distinction | An item import creates item records. It does not create the purchase, receipt, bill, build, or adjustment history that drives quantity on hand and inventory value. |
|---|
| Checklist area | Rep should verify | Red flag (incorrect process or assumption) |
|---|---|---|
| Item profile setup | Lists > Items > open item > Profile/Buying Details/Selling Details. Confirm I Buy This Item, I Sell This Item, I Inventory This Item, and any serial/location settings. | The wrong item type or missing inventory flag changes the entire troubleshooting path. |
| Linked inventory accounts | Setup > Linked Accounts > Inventory Accounts and the item’s own linked asset/cost/income accounts. | Customers often expect old transactions to display under a new tracking account, but linked-account changes usually do not rewrite history. |
| Import and opening-balance history | Confirm whether the customer only imported items or also entered opening balances, purchases, receipts, or adjustments. | An item list import creates records, not item history. Quantity and value still have to be created. |
| Purchase receipt workflow | Confirm whether inventory was added through Purchases > Enter Purchases, Receive Items, or Bills. | Receipt state matters for availability, especially with serial-tracked items and PO/Bill timing. |
| Current item state | Open the item and compare Quantity On Hand, Current Value, Average Cost, History, and location detail. | The current card tells you whether you are dealing with a quantity issue, a value issue, or both. |
| Reports first | Run the smallest useful report first: Items List (Summary), Inventory Value Reconciliation, Sales Detail, Serial Number Transactions, or Item Movement. | Good report selection prevents blind changes and reduces rework. |
6Fast Triage Matrix: Symptoms, Causes, and First Checks
4. Fast Triage Matrix: Symptoms, Causes, and First Checks
| Customer symptom | Likely causes | First checks |
|---|---|---|
| Sale or invoice says the transaction would leave you with positive quantity and negative inventory value | Past negative sales, value-only adjustments, or incorrect historical inventory value. | Open the item card and compare Quantity On Hand to Current Value. Review recent Inventory Journal entries and prior sales/adjustments. |
| Imported item has no quantity or amount | Item list import created the item record only; transaction history was never entered. | Confirm whether opening balances, purchases, receive items, or inventory adjustments were recorded after the import. |
| Auto-Build quantity is wrong after build | Build quantity misunderstood, or customer entered the desired final count instead of the adjustment amount. | Review the built quantity and then use Inventory > Adjust Inventory for the difference only. |
| Need to change quantity on hand | Customer really needs either a purchase/receipt or an inventory adjustment. | If the stock truly arrived, use the purchase workflow; if it is a correction, use Adjust Inventory. |
| Need transactions for a non-inventoried item | Find > Items is not the right path for that case. | Go to Reports > Index to Reports > Sales > Items > Sales Detail > Customize and filter the item. |
| Need an aged inventory report | There is no direct aged inventory report in AccountEdge. | Use Inventory Value Reconciliation as of a date, then export and filter if the customer wants to remove zero items. |
| Serial numbers available but missing from selection list | Receipt/bill state, serial assignment timing, location mismatch, or deeper file issue. | Run Serial Number Transactions for the serial, inspect the source PO/receipt/bill, and compare the item/location state. |
| Location on-hand quantity does not match serial availability | Possible multi-item file pattern, location history issue, or serial data inconsistency. | Collect all affected items, run Optimize/Verify, and prepare the file for escalation if the issue is broad. |
7Deep-Dive Modules: How to Troubleshoot Inventory Issues
5. Deep-Dive Modules: How to Troubleshoot Inventory Issues
Module A - Item Setup, Linked Accounts, and Preferences
When a customer says “inventory issue,” start by anchoring the conversation to the item record.
1. Open Lists > Items and confirm whether the item is bought, sold, inventoried, serial-tracked, or using multiple locations.
2. Review Setup > Linked Accounts > Inventory Accounts and compare them to the item’s asset, cost of sales, and income accounts.
3. Check Setup > Preferences > Inventory when the customer’s expectation sounds workflow-related rather than history-related.
4. If the customer only wants to change pricing or setup, edit the item record instead of altering historical transactions.
| Real case link: SCA2606828 The customer wanted transactions for a non-inventoried item. Find > Items was not the right path, so support redirected the customer to Sales Detail filtered by item. |
|---|
Module B - Quantity vs Value: Imports, Opening Balances, and Adjust Inventory
A large percentage of inventory calls come from mixing up item setup with transaction history.
1. First decide whether the customer is fixing quantity, fixing value, or establishing missing opening history.
2. Use opening-balance workflows when the file is being set up; use Inventory > Adjust Inventory when the file is being corrected.
3. Remind the customer that the Quantity field in Adjust Inventory expects the adjustment amount, not the final desired balance.
4. If the question is really an accounting entry for shrinkage or insurance, separate that from the physical stock correction.
| Real case links: SCA2606430 and SCA2605841 One customer expected quantity and value to come in with the item import; another needed an auto-build count corrected with Adjust Inventory using the difference only. |
|---|
Module C - Negative Inventory, Cost of Sales, and Value Errors
Inventory quantity and inventory value can drift apart when sales, receipts, and adjustments were entered in the wrong order.
1. Compare Quantity On Hand, Current Value, and Average Cost before changing anything.
2. Review prior sales with insufficient stock and any value-only adjustments that could have pushed value below zero.
3. Use Item History / Inventory Journal to identify the transaction that broke the value trail.
4. Do not edit old IJs blindly if the proposed change would make current value impossible for today’s quantity.
| Real case links: SCA2605720 and SCA2601966 In one case, quantity was positive but current value was negative, which blocked invoicing until support entered a value adjustment. In another, changing an old IJ would have made current value impossible for the item’s positive quantity. |
|---|
Module D - Serial Numbers and Locations
Serial-tracked and multi-location files require tighter troubleshooting discipline.
1. Confirm serial tracking is enabled, then trace how the serials were entered on the purchase side and how they are being selected on the sales side.
2. Use Serial Number Transactions and the item’s history to trace the source transaction and current availability.
3. If location quantities and serial availability do not match, determine whether the issue is one item or many before changing data.
4. For broad mismatches, require the affected item list, Optimize/Verify results, and the company file before escalation.
| Real case links: SCA2605041 and SCA2510710 One customer had multiple items where location quantities and available serials did not agree, so support required the full affected list and file-health steps before escalation. In another, support traced unavailable serials back to the source transaction state and re-tested the workflow. |
|---|
Module E - Build Items, Auto-Build, and Component Availability
Build cases usually fail because the components are not set up correctly, do not have usable quantity/value, or the customer is using the build window to try to correct a final balance.
1. Use Build Items / Auto-Build only when the finished good and its components are true inventoried items with usable quantity and value.
2. For Build Items, enter the quantity to build and let AccountEdge calculate the out-of-balance amount to the built item.
3. For Auto-Build, verify the component list and explain that restocking alerts apply to the auto-built item, not its components.
4. If the customer only needs a final count correction after building, use Adjust Inventory for the difference.
| Real case link: SCA2605841 The customer needed help with an auto-build item and then asked how to reduce the on-hand count after the build. Support guided the build quantity first and then used Adjust Inventory for the remaining difference. |
|---|
Module F - Deleting or Modifying Purchases, Bills, and Inventory Journals Safely
Deletion problems are almost never solved by clicking Delete again. They are solved by tracing dependencies.
1. Start with dependency tracing: payments, receive-items flow, later sales, serial usage, and Inventory Journal entries.
2. If a bill or purchase will not delete, identify every later transaction that touched the same item quantity or value.
3. Reverse dependent transactions in order before deleting the original purchase/bill.
4. Explain clearly when historical transactions must be re-recorded to change how they display in the register or reports.
| Real case links: SCA2511119 and SCA2604060 In one case, a bill could not be deleted because later Inventory Journal activity was still tied to the item. In another, the customer wanted a different account to appear in the register and learned that historical display often requires re-recording. |
|---|
Module G - Reports, Finding Transactions, and Working Around Missing Reports
Report questions should be translated into the real business question first.
1. Match the report to the question: item transactions, serial history, valuation as of date, stock alerts, or reconciliation.
2. For non-inventoried item transactions, use Sales Detail rather than Find > Items.
3. For valuation by date, use Inventory Value Reconciliation and set the As Of date carefully.
4. If the customer asks for an aged inventory report, explain the limitation and offer export/filter as the closest workflow.
| Real case links: SCA2605129 and SCA2507203 One customer wanted an aged inventory report; support explained there is no direct aged inventory report and offered Inventory Value Reconciliation plus export/filter as the closest path. Another wanted a second stock-alert feature, but support confirmed the current restocking alert workflow is the supported option. |
|---|
8Real-World Case Library and Coaching Notes
6. Real-World Case Library and Coaching Notes
| Case | Customer issue | Root cause / outcome | Coaching note |
|---|---|---|---|
| Temple did it! negative value block - SCA2605720 |
Customer could not record an invoice because the item had quantity on hand but a negative current inventory value. | The item had been sold when no stock was on hand and the file allowed that workflow. Support corrected the negative value with a positive inventory adjustment, which let the invoice record again. | Always separate quantity from value. A customer may have stock on hand and still be blocked because the current value is below zero. |
| Imported items without qty/value - SCA2606430 |
Customer imported items and expected quantity on hand and amount to come in with the list. | Support explained that quantity and value come from transactions, not from the item import alone. The customer was directed to create the history manually, including inventory adjustment/opening-balance options. | Translate import limits early so the customer does not assume the file is missing data that was never created. |
| Auto-Build quantity correction - SCA2605841 |
Customer was building an item and then wanted the final on-hand balance changed from 6628 to 6625. | Support had the customer enter the built quantity correctly, then use Adjust Inventory with -3 to reduce the balance. | The Quantity field in Adjust Inventory is the change amount, not the desired ending balance. |
| Location/serial mismatch across items - SCA2605041 |
Customer saw location quantities that did not match available serial numbers, including negative location balances, across many items. | Support collected sample evidence, requested the full affected item list, asked for Optimize/Verify and file-size checks, and required the company file for deeper research before PD escalation. | When the pattern spans multiple items, your first job is to define the full scope and file-health evidence package. |
| Serials available but not selectable - SCA2510710 |
Customer could see serial numbers in inventory but could not select them from the list on the sales side. | Support traced the serial through Serial Number Transactions and the source PO/receipt state, then re-tested the workflow until the serials became selectable again. | When serials seem to exist but do not show in the selector, inspect the source transaction state before assuming data loss. |
| Deleting bill blocked by later item history - SCA2511119 |
Customer wanted to delete a bill and move the payment to a new PO, but the bill would not delete. | Later Inventory Journal activity and zero on-hand quantities were still tied to the items. Once the dependent IJ was removed, the bill could be deleted and the payment reapplied. | Do not start with deletion. Trace every later transaction touching that item first. |
| Editing old IJ would force impossible value - SCA2601966 |
Customer tried to change an old inventory adjustment after entering the wrong unit cost and received an error. | Support determined that the proposed edit would reduce current inventory value below what was possible for the item’s positive on-hand quantity. Without the file, only assumptions were possible, so the company file was requested. | If an old value change would make today’s inventory impossible, stop and verify the full transaction chain before changing history. |
| No direct aged inventory report - SCA2605129 |
Customer wanted an aged inventory report and also wanted to hide zero items. | Support explained there is no direct aged inventory report, suggested Inventory Value Reconciliation as the closest valuation report, and recommended export/filter for removing zeros. | Be direct about report limits and give the nearest supported workflow instead of overpromising. |
Case coaching pattern: how to teach reps to think
| Customer statement | Rep translation | Next move |
|---|---|---|
| “The quantity is wrong.” | Which item, which location, what is the expected on-hand, and where is the wrong number visible? | Compare the item card, item history, and the most recent purchase/sale/adjustment chain. |
| “The value is wrong.” | Need to separate current value from quantity on hand and review historical value changes. | Open Item Information, review Inventory Journal history, and check whether the proposed fix would force value below zero. |
| “The serial number is available but I can’t pick it.” | The serial may exist in history but not be available in the current transaction state or location. | Run Serial Number Transactions and inspect the source PO/receipt/bill and the current location context. |
| “I imported the items already.” | An item import is not the same as transaction history. | Ask how quantity and value were established after the import: opening balances, purchases, receipts, builds, or adjustments. |
| “I just need to delete the purchase.” | Later transactions are probably tied to that item already. | Trace payments, bills, receive-items flow, inventory journals, sales, and serial usage before deleting anything. |
9Escalation Standards and Supervisor Hand-Off Format
7. Escalation Standards and Supervisor Hand-Off Format
A good escalation lets a supervisor reproduce the issue quickly. A bad escalation that says “inventory is wrong” creates a longer time for the investigation to take place. Use the format below for your inventory escalations.
| Hand-off field | Required detail |
|---|---|
| Customer / case | Customer name, case ID, product, build, OS, and whether the file is local, NE, or hosted. Avoid unnecessary personal data in Teams. |
| Issue statement | One sentence naming the item(s), location(s), report/window, and exact failure. Example: “For item X at location Y, On Hand shows 2 but only 1 serial is available in Serial Number Transactions.” |
| Expected result | Customer’s expected quantity, value, availability, or report output, and where that expectation came from. |
| Actual result | The exact current AE result, with screenshots, report filters, item numbers, serial numbers, and transaction numbers. |
| What was checked | Item profile, linked accounts, preferences, item history, Inventory Journal entries, related bills/sales, location settings, serial reports, and any report filters. |
| Testing performed | Sample-file testing, affected vs unaffected item comparison, reversible test entries, Data Repair steps, and whether any test transaction was deleted afterward. |
Escalation trigger
Escalate when the rep cannot safely explain the result after checking item setup, linked accounts, preferences, transaction order, item history, location/serial scope, and the relevant reports; or when multiple items show the same unexplained mismatch.
File research requirements
Request a copy of the company file when screenshots or a short remote session are not enough.
For serial/location issues across many items, require the full affected item list, not just one example.
Ask the customer to run Optimize and Verify first when appropriate, and capture any errors.
Do not promise an ETA or a bug fix before the file has been researched.
10Customer Communication Scripts
8. Customer Communication Scripts
| Scenario | Script |
|---|---|
| Opening the call | I want to trace this from the item setup and transaction history instead of guessing. Inventory issues usually depend on the item record, transaction order, linked accounts, location/serial details, and prior adjustments. I’m going to first confirm what you’re seeing, then we’ll compare the current item state to the history that created it. |
| Customer says it is a bug | It may be a software issue, but before I call it that, I need to rule out the setup and transaction-history items that directly control this result. If those check out, I’ll document the evidence and escalate it with the exact item, report, and transaction chain. |
| Issue is caused by history | The issue may not be in the window you’re looking at right now. A previous purchase, adjustment, build, or sale can change the inventory result you see later. Let’s trace the item history and identify where the numbers first stop making sense. |
| Workaround is needed | AccountEdge may not have a direct one-click workflow for that exact request, but we can usually separate the inventory correction from the accounting or reporting need. I want to be clear about what the workaround will affect and what it will not affect before you rely on it. |
| Need a file copy | Based on the screenshots, we can make an educated guess, but we cannot verify the transaction history safely without reviewing the file or seeing the data live. A copy of the company file lets us confirm what actually happened instead of relying on assumptions. |
| Customer wants to edit an old adjustment right now | I understand the customer wants to correct the old entry, but if we edit that transaction blindly we may create a new inventory problem in the current period. Let’s confirm what happened after that adjustment before changing historical value. |
11Source Notes and KB Reference Links
Source Notes and KB Reference Links
This guide was built from CRM case data, public AccountEdge Knowledge Base data & This guide was created using CRM case data, public AccountEdge Knowledge Base resources, and established internal support knowledge.
AccountEdge KB and website references used
Inventory overview: Inventory overview
Inventory Adjustments: Inventory Adjustments
Advanced Inventory Features and Troubleshooting: Advanced Inventory Features and Troubleshooting
Inventory Value Less Than $0: Inventory Value Less Than $0
Build Items: Build Items
Receive Items: Receive Items
Enter Inventory Opening Balances: Enter Inventory Opening Balances
Inventory Locations: Inventory Locations
Serial Number Setup and Tracking: Serial Number Setup and Tracking
Cost of Sales: Cost of Sales
Final trainer note The focus of this guide is to help spark thinking further and should be used with judgment. Reps should always verify the current KB article, confirm the customer’s exact workflow, and document the item history before changing data. This is not a one size fits all type of guide, every case is different, this is more of a blueprint on whichquestions to ask, where to verify data and how to coordinate your work flow while troubleshooting. |
|---|
12One-Page Inventory Call Checklist
One-Page Inventory Call Checklist
| Step | Check |
|---|---|
| 1 | Can I restate the issue in one sentence with the item number, location, report/window, and exact symptom? |
| 2 | Have I verified AE product, build, OS, and whether the file is local, NE, or hosted? |
| 3 | Did I separate quantity, value, serial/location, and reporting expectations before proposing a fix? |
| 4 | Did I check the item record: Profile, Buying Details, Selling Details, linked accounts, locations, and serial settings? |
| 5 | Did I compare the current item card to the transaction history: purchases, receipts, bills, adjustments, builds, moves, and sales? |
| 6 | If the customer imported items, did I confirm how quantity and value were actually created afterward? |
| 7 | If value looks wrong, did I open the Inventory Journal / item history and check whether current value can support the proposed change? |
| 8 | If serials or locations are involved, did I run the relevant report and determine whether one item or many items are affected? |
| 9 | Did I test safely using reports, sample files, or reversible steps before altering live data? |
| 10 | Did I explain whether the fix changes current inventory only, future workflow, or historical transactions as well? |
🧭 Best Path / Rep Call Flow
- Discovery: identify exactly what the customer sees, where they see it, and the date/report/window involved.
- Question phase: narrow whether this is setup, transaction history, workflow, reporting, or file-specific behavior.
- Troubleshooting/testing: test one variable at a time, use safe non-posting evidence first, and avoid irreversible changes.
- Implement or escalate: apply the confirmed fix, verify the result, or hand off with clear evidence.