What an inventory application audit actually covers
The work starts from the quantity the application claims, then asks whether receipts, issues, and counts in the period support that claim.
When a plant controller in Johor Bahru asks us to “audit the WMS,” they often mean two jobs at once. One is a general IT visit. The other is an examination of how the live inventory application recorded stock in a named period. We only take the second job.
The letter names the site, the application, and the period. From on-hand we work backwards: which receipt posted the quantity, which bin the system assigned, which issue or transfer reduced it, and who could adjust it after the count freeze. A vendor feature list is not in scope.
If your team keys a variance in a spreadsheet and pastes it into the inventory ledger, that overlay is in scope. If a scanner user can post a negative issue without a reason code, that gap is a finding. We do not redesign the warehouse layout. The value of the work is a written view of the application as it actually ran — the same view an external auditor standing at the dock can follow.