Turning inventory records into audit-ready reporting
Work that previously took at least three days could be completed in no more than three minutes.
Publication boundary: This is a proprietary system. This page describes only the parts I worked on and omits confidential implementation details, client access and private project material.
At a glance
- Problem
- The store needed to preserve batch-level purchase prices, trace departmental allocations and prepare accounts and audit reports without rebuilding every figure by hand.
- My contribution
- I built receipt-level costing, department requests and approvals, asset disposal records, permissioned reports, and an intranet deployment that started with its dedicated server.
What the system recorded
These published records show the evidence structure without exposing private screens, client access or project data.
- Purchase record
- Receipt-level batches preserving the price paid for each group of items.
- Allocation record
- Department requests, director approvals and the items each department received.
- Disposal record
- Asset history, eventual sale and the value recovered from disposal.
- Reporting record
- Permissioned books and reports available to store, accounts and audit users.
On this pageContext
Context
Operating situation
Knowing the quantity of an item was not enough. Separate purchases of the same product could have different unit costs, and the remaining stock had to preserve that history. Staff also needed to know which department received an item and how much was recovered when an asset was sold.
The problem
The store needed to account for inventory bought at different prices, items issued to departments, disposed assets and report totals without rebuilding the same records by hand for accounts and auditors.
Operating constraints
- Each purchase batch needed to retain its own price even when it contained the same product as an earlier receipt.
- Departmental requests could not issue stock until the store director approved them.
- Store, accounts and audit users needed different access to the same records and reports.
- The application had to run on the commission’s intranet without depending on a reliable internet connection.
My contribution
- Receipt and purchase-batch records
- Departmental stock requests
- Bulk approval workflow
- Asset and disposal records
- Permissioned books and reports
- Dedicated intranet deployment
How the system worked
I implemented the foundational inventory system around uniquely identified receipts. Items on one receipt represented the same product bought at the same price, so later purchases at another price remained distinguishable in the stock records.
Departments submitted item requests through the system. The store director could review several requests and approve the selected requests together, leaving a traceable record of what each department asked for and received.
The system kept asset records for items such as vehicles and laptops, recorded their eventual sale in the store’s books and retained the amount recovered from the disposal.
Accounts staff received permissioned access to view and print the store’s books. I deployed the application on a dedicated server in the store department and configured it to start with the server for straightforward intranet use.
Important system decisions
- Preserve purchase price at receipt-batch level instead of assigning one current price to every remaining unit of a product.
- Make department requests and director approvals part of the inventory record rather than a separate paper process.
- Record asset disposal and recovered value alongside purchase and allocation history.
- Use a dedicated intranet deployment to meet the organisation’s security and connectivity constraints.
Result
Before the system was installed, the processes took at least three days, with report preparation taking much of that time. Afterwards, the same work took no more than three minutes because purchases, allocations and disposals were already available to the reports.
What this demonstrates
Repeated report preparation often signals that the underlying events are being recorded in one place and reconstructed somewhere else. Capturing those events once in a structured workflow can return substantial time to the people doing the work.