Picture an internal auditor sending Procurement a one-line request: give us the complete record for asset 10493.
That should take an afternoon. The purchase order exists. So do the maintenance invoices and the disposal approval. They just live in three systems and two spreadsheets, and the asset tag on the disposal form doesn’t quite match the serial number on the receiving slip.
Nobody skipped a step. Every event left a trace. Your team can’t prove those traces belong to the same asset because purchasing, receiving, operations, and finance never shared a record during handoffs.
Quick disclosure before I go further: I lead sales at EZO, and we own two of the platforms below. Weigh my view accordingly. My aim is to give you a test you can run on every vendor, us included.
When you shortlist asset lifecycle management software, the most defensible platform isn’t the one with the longest audit log. It’s the one that keeps an unbroken chain of evidence from purchase approval to retirement.
Procurement needs a defensible chain of evidence
“Audit trail” gets used for four different things. Separate them before a demo blurs them together.
Asset record. What exists today: the item, its tag, location, assigned user, and status.
Audit history. What changed on that record: a field edited, a status updated, a user reassigned.
Lifecycle evidence. What happened to the asset itself: requested, received, assigned, moved, repaired, returned, retired.
Procurement evidence chain. Why it happened, who approved it, who supplied it, and what it cost.
An audit log records changes to a record. Lifecycle history records what happened to the asset. Your auditor, your finance reviewer, and your internal audit team need both, tied back to the purchase that started it. Call that connected record the asset evidence chain:
Approval → PO → vendor → receipt → asset → custodian and location → maintenance → costs → change → retirement
If any link needs a spreadsheet lookup or an inbox search, you have a traceability gap. The asset may be well managed. You just can’t defend the record.
The evidence chain starts before the asset exists
Most asset systems begin when someone creates an asset record. For Procurement, that’s already late.
The chain starts with the request: who asked for the asset, and what need did it serve? Then the approval: who signed off, at what threshold, and is that decision kept somewhere other than an email? Then the vendor: which supplier, under which contract or terms. Then the purchase order. Then the receipt: what arrived, when, and where.
If that procurement data is detached when the asset record is created, the audit gap opens on day one.
Receiving should turn a purchase into a traceable asset
Receiving is where a PO line becomes a physical thing with an identity. It’s also where evidence chains quietly break. The PO sits in the purchasing system, and someone else creates the asset somewhere else days later.
The handoff looks different by estate. For operations teams, it’s equipment arriving at a warehouse, yard, or job site. For IT, it’s a laptop being received, tagged, and assigned before it reaches a new hire.
Ask what happens at that handoff:
- Does PO line data become asset data, or does someone retype it?
- Does the asset record retain the vendor?
- Does the purchase cost follow the asset?
- Are serial numbers and asset tags captured at receipt?
- Is the receiving location documented?
In Microsoft Dynamics 365 Asset Management, for example, teams can create assets from purchase order lines and wait to post a product receipt before doing so.
A convincing answer is a live demo where the vendor receives a PO line, and the asset appears with vendor, cost, serial number, and location attached. A weaker answer is “our import handles that.” Imports work, but someone still has to run them, check them, and fix them. Find out who on your team is responsible.
Custody history is part of financial accountability
Custody belongs on Procurement’s list because custody gaps show up as procurement problems: unexplained losses, duplicate purchases of equipment nobody can confirm was available, disposals nobody can verify, and no clear owner when something goes wrong.
The evidence you want is a dated record of assignments, check-ins and check-outs, transfers between sites or departments, returns, and location changes. Each entry should show who held the asset and who authorized the handoff. For IT, the hardest version is offboarding: when an employee leaves, can you show which devices were assigned to them and when each one came back?
What has the asset actually cost you?
The PO tells you what you paid to acquire an asset. It says nothing about what the asset has cost since.
A defensible cost record builds up over the asset’s life:
- Acquisition: purchase price, freight, and installation.
- Maintenance labor: internal hours and the rates behind them.
- Parts: components and consumables used in work orders.
- External vendors: outside service and contractor work.
- Contracts and warranties: what was covered, and whether covered repairs got billed anyway.
- Retirement and disposal: decommissioning, data wiping, recycling, or resale.
Finance leans on the same record for depreciation and utilization decisions, so the cost history can’t live in a separate workbook. ServiceNow’s Asset Total Cost of Ownership feature is a useful reference: for serialized assets, it adds the capital cost once and treats every later expense line as operational cost. The test: can you see the full cost of one serialized asset without building a pivot table?
History only matters if you can trust it
This is where the audit log earns its place: proving nobody has rewritten the chain.
For any record in the chain, you should be able to see who changed it, what changed (old and new values), and when. Then ask two harder questions. Can historic records be altered or deleted, and by whom? Are approvals and transaction records protected from post-facto edits?
IBM Maximo is a fair benchmark. You can enable electronic audit at the object and attribute level, saving the changed data, the user, and the change type. Its electronic signature option can require a password and a reason before saving a change. Someone has to configure it all, so decide before you sign who sets, reviews, and maintains those controls.
One caution: no platform passes an audit for you. A system provides records and controls that may support your audit evidence requirements. Your organization’s controls do the rest. Be wary of any vendor, mine included, that promises more.
Five platforms, five operating models
These enterprise asset management (EAM) and IT asset management (ITAM) platforms aren’t direct substitutes. Notes come from vendor documentation checked October 22, 2026. EZO EAM and AssetSonar are EZO products.
| Platform | Operating model | Where the chain is strongest |
| EZO EAM | Physical asset lifecycle, procurement, and maintenance across sites and teams | Tracks purchase orders, vendors, maintenance histories, and lifetime costs from procurement to retirement; its Availability Calendar shows assets as available, reserved, checked out, or under maintenance |
| IBM Maximo | Enterprise EAM with deep configuration | Electronic audit and electronic signature, enabled and configured by an administrator |
| ServiceNow HAM | IT hardware procurement inside a broader service platform | Procurement view of requests, purchase orders, sourcing tasks, receiving slips, and spend by vendor; Asset TCO from Hardware Asset Management 10.0.0 |
| Microsoft Dynamics 365 Asset Management | Asset management inside Dynamics 365 Supply Chain Management | Assets created from purchase order lines, optionally after product receipt |
| AssetSonar | ITAM for hardware, software, and SaaS licenses | A completed PO creates or updates the asset record with model, serial number, vendor, order date, and price; software orders create license records with seat count and per-seat cost |
If your environment genuinely needs Maximo’s depth or tight Dynamics 365 finance integration, the implementation effort may be worth it. Just put the configuration work and admin staffing in the business case alongside the subscription.
Don’t ask whether you have an audit trail
Almost every vendor says yes. Swap weak RFP questions for ones that force a demo.
| Weak question | Better procurement question |
| Do you have audit logs? | Show every change made to this asset record during the last year. |
| Do you track vendors? | Show every PO, contract, service record, and cost associated with this vendor and asset. |
| Do you track costs? | Show acquisition plus lifecycle costs for one serialized asset. |
| Do you support lifecycle management? | Reconstruct this asset from receipt to retirement. |
| Are you compliant? | Show which controls and records support the specific evidence requirements we have defined. |
Have Procurement, Finance, and internal audit hear the answers; each will spot a different gap.
Run the one-asset audit before you sign
Skip the audit log tour with your finalists. Give each one asset and ask them to reconstruct its life.
Use a real asset from your records, or script one: “This forklift was bought four years ago. Show us who approved it, which vendor sold it, what we paid, when it arrived, where it moved, who maintained it, what those repairs cost, whether it was under warranty, and what happened when it was retired.” For an IT estate, swap in a laptop and add who it was assigned to, which software it carried, and how it was recovered at offboarding.
Give every finalist the same story and have them walk it in order:
- Request
- Approval
- Purchase
- Vendor
- Receipt
- Asset creation
- Custody
- Service
- Cost
- Retirement
No slides. No generic dashboard. Use the product.
While they work, keep score. Count the modules they open, the missing evidence, the outside systems they need, the manual joins and exports, the records that stay editable when they shouldn’t, and any gap they can’t explain. Then estimate the administrator time each manual step would cost you every month, and add it to the price.
Which platform fits your procurement environment?
Choose a deeper enterprise EAM when procurement runs tightly through ERP, complex contracts matter, and you have the people for extensive configuration.
Choose an integrated mid-market EAM, such as EZO EAM, when custody, availability, maintenance, and cost across sites sit at the center of the work.
Choose ITAM, such as AssetSonar, when laptops, licenses, renewals, and IT vendor purchasing dominate your estate. Judge it against other ITAM platforms, not a traditional EAM.
Make the audit boring
When purchasing, receiving, custody, maintenance, and retirement all write to the same chain, a request for the complete record of asset 10493 stops being a project. Audit preparation becomes retrieval, not reconstruction.
So take one question into your next demo: can this vendor reconstruct one asset’s life, from approval to retirement, without leaving the product? If the answer involves a spreadsheet, you’ve found the gap before your auditor does.
