Customer Case:
The customer notices that the same asset appears to be charged at multiple locations and wants to understand whether this is possible in ON!Track Asset Cost Reporting (ACR). They are concerned that the asset costs may be duplicated or calculated incorrectly.
The customer notices that the same asset appears to be charged at multiple locations and wants to understand whether this is possible in ON!Track Asset Cost Reporting (ACR). They are concerned that the asset costs may be duplicated or calculated incorrectly.
How does ON!Track work?
An asset can only be actively charged at one location at a time.
An asset can only be actively charged at one location at a time.
When an asset is transferred into a location, ON!Track creates a charge entry and records the Date Arrived. The Date Left remains empty while the asset is still assigned to that location.
When the asset is transferred to another location:
- ON!Track records the Date Left for the previous location.
- The charge entry for the previous location is closed.
- A new charge entry is created for the new location with a new Date Arrived.
This process ensures that an asset is only actively charged at a single location at any given time.
In the Asset Cost Report, there should normally be only one open charge entry for an asset, meaning only one record where the Date Left field is blank.
If multiple charge entries exist for the same asset with a blank Date Left, this is not expected behavior. It may indicate that a transfer was not processed correctly, resulting in the previous charge entry remaining open when a new one was created.
Recommendation and workaround (optional):
If the Asset Cost Report shows multiple open charge entries for the same asset, create a support ticket for the Customer Advocate team. The issue can typically be corrected through a backend data adjustment to ensure the asset history and cost calculations are accurate.
If the Asset Cost Report shows multiple open charge entries for the same asset, create a support ticket for the Customer Advocate team. The issue can typically be corrected through a backend data adjustment to ensure the asset history and cost calculations are accurate.