What it means
Define the transfer first, because an internal reassignment, an inter-site move and a third-party loan have different evidence requirements. Oracle documentation describes changing asset assignments and transferring assets between locations or employees, but a software transfer entry is not physical receipt.
Begin with the asset's physical ID, old custodian, destination and agreed handoff point, and verify the serial or asset tag against the item being handed over. Choose a start event that can be verified, such as a signed release or dispatch scan, because a drafted transfer request should not start the same clock as an actual physical handover.
The end event requires recipient acknowledgment or another approved proof of receipt that identifies the specific device or tool, its condition, accessories and location, since a generic "received" reply to a mixed pallet leaves individual asset custody uncertain. A finance-system location edit can support reconciliation, but it does not show that the receiving person has the item.
A transfer can have a carrier and tracking reference before the new user takes custody, and delivery to building reception may precede acceptance by the assigned employee, so report each milestone separately. The shipping team, carrier and receiving custodian can each hold different responsibilities under policy or contract, and this metric does not decide liability.
For shared equipment the destination may be a controlled storeroom, so confirm the storeroom custodian and shelf or bin, not merely the building name, and treat customs and security approvals on cross-border moves as separate from missing confirmation. Record damage or missing accessories at handover rather than assuming acceptance, and when an asset travels with keys, probes, chargers or documents, specify which components belong to the handoff.
If the receiving team rejects a damaged or wrong serial-numbered item, the transfer remains disputed, so do not close the lag using an acknowledgment of the discrepancy. Keep the old custody in place until an unclear handoff is resolved, and treat it as an exception with an assigned investigator.
Credentials and company data on devices need separate controls during transfer, and physical receipt does not establish that account access was removed from the former user. Photos and electronic signatures may be acceptable for remote receipt under policy but need reliable identity, and loaned equipment may need return dates, insurance and contractual authority.
A finance-book transfer and an operations transfer can refer to one physical movement, so avoid duplicate records. On-site handoffs and international shipping need different reasonable clocks, and repeated transfers of the same asset should form an ordered history because a second move does not erase an unresolved first handoff.
Auditing older moves can expose an asset that was never actually delivered, and long-lag cases reveal ambiguous ownership, carrier delays and stale location fields. Use a separate location accuracy measure, since confirmation alone does not prove ongoing location, and remember that the goal is accountable physical custody, not a faster status click.
In practice
Real-world examples.
Example
A scanner is dispatched on Monday and acknowledged by the receiving site on Wednesday, a two-day lag. The acknowledgment names the serial number and notes that the charger arrived with it.
Example
A recipient sees the wrong serial number and rejects the handoff rather than signing. The transfer stays open and the old custodian remains responsible until the discrepancy is resolved.
Example
A loaned device has its receipt recorded by the borrower, while its scheduled return is tracked separately. The two clocks answer different questions, so they are not combined into one figure.
Formula
Calculation
Lag = Receiving-custodian confirmation timestamp - Defined transfer start timestamp. Show open transfers and the late tail alongside the average.
Worked example. A scanner is dispatched at 9:00 on Monday and acknowledged at 15:00 on Wednesday, which is 2 days and 6 hours, or 54 hours. Across five transfers the lags are 24, 30, 54, 72 and 288 hours.
- Total lag: 24 + 30 + 54 + 72 + 288 = 468 hours
- Average lag: 468 / 5 = 93.6 hours
- Median lag: 54 hours
- The 288-hour case (12 days) is the late tail that explains why the average is far above the median, and it is the one to investigate first.Case study
Seen in the real world.
This entirely fictional case follows Fieldstone Design. A camera was marked moved in the register, but the new team had not received its charger or confirmed the serial. The coordinator kept the handoff open until both were checked and acknowledged.
In this illustrative story, the studio then reviewed every transfer open for more than ten days and found two items that had never left a storeroom. It added a required serial confirmation to the receipt form. The example does not determine legal title or liability.
Watch out
Common mistakes.
- Using a location-field edit as proof of physical receipt.
- Closing a rejected or damaged handoff without resolution.
- Mixing domestic and cross-border move times without context.
Questions
People also ask.
Can a scan prove receipt?
Only if the scan captures the right item and authorized receiver under policy.
Who owns an in-transit item?
Use the company handoff and carrier terms; do not infer from the metric.
What about lost assets?
Keep them open and investigate under the loss process.
From the founder's library
Take it further with the book.
Build your financial confidence beyond this definition. Shihan's full-length guide, Accounting Fundamentals, takes the same plain-English approach and turns it into a complete, practical playbook for non-finance managers, business owners and students - with chapter-end quiz answers and presentation slides included.
25% off with code MMHQ25, applied at checkout. Priced in USD - checkout may show the equivalent in your local currency.
View the book and save 25%Related