Reconstructing an In-Use Date When Finance Learns About an Asset Late
Reconstruct late-reported asset readiness using dated operational and technical evidence while separating first use, availability and accounting decisions.
How can finance establish a supported date for an asset reported after operations began?
Build a dated evidence timeline from commissioning, technical acceptance and operational records, distinguishing readiness for intended use from the first recorded activity and the date finance was notified. Document conflicting evidence and let finance determine the accounting consequences. Do not use the notification date simply because it is the first date visible in the asset team's inbox.
A new generator may have supported a facility for several weeks before the register team receives its handover documents. The purchase invoice, commissioning certificate and first operating log show different dates. Resolving the issue requires a documented chronology and technical context, not a request for someone to choose one convenient date retrospectively.
Collect independent date evidence
Request commissioning and acceptance records, operating logs, maintenance entries, delivery evidence and relevant project correspondence. Record the purpose of each document and when it was created. Delivery shows arrival; a test log may show a trial; a routine operating log may show actual use. None should be relabelled to mean something it does not establish.
Ask the technical owner to explain when the asset reached the condition and location needed for its intended function. Under GRAP 17, depreciation begins when an asset is available for use. First actual use may provide evidence, but it is not automatically identical to availability. Finance should assess the dates in the context of the applicable reporting framework.
Investigate contradictions rather than averaging dates
If a certificate is signed after the date it describes, preserve both the issue date and the event date. Ask what contemporaneous evidence supports the earlier event. If the operating log predates acceptance, establish whether it reflects testing, temporary use under restrictions or normal operation. A short technical explanation can resolve ambiguity that a date field cannot.
Record a range or unresolved question where the evidence does not support a precise conclusion. Do not average competing dates or choose month-end to simplify calculations. Identify what additional evidence could narrow the uncertainty and who can provide it. Finance can then evaluate the significance and appropriate treatment instead of receiving false precision.
Document the decision and repair the reporting route
Prepare a decision note with the asset identity, intended function, evidence timeline, technical conclusion and finance approval. Keep any calculation or correction arising from late notification with that note. The register team's completed investigation does not, by itself, settle whether earlier financial information requires correction; that assessment belongs to finance.
Identify why the handover arrived late and add a practical notification trigger to the project process. A commissioning milestone or operational acceptance step can alert the register team before the final project file is assembled. Test the next handover against that trigger so the improvement is demonstrated in a real case rather than left as a recommendation.
Practical Example
Illustrative example: a generator is delivered on 4 May, completes commissioning on 12 May and first supports a planned outage on 20 May. Finance receives the file in June. The technical owner explains the readiness evidence, and finance evaluates the appropriate date and consequences. The team does not automatically use delivery, first operation or inbox receipt as the accounting date.
Action Checklist
- 1.Gather commissioning, acceptance and operating records with their original dates.
- 2.Distinguish delivery, testing, availability, first actual use and finance notification.
- 3.Investigate certificates issued after the events they describe.
- 4.Document the technical conclusion and finance's separate accounting decision.
- 5.Add and test a project notification trigger that reaches the register team earlier.
Prepare a supported chronology for late asset handovers with Audit-Ready Asset Management.