Deciding Whether Two Similar Register Rows Represent One Asset
Resolve suspected duplicate asset rows using identity evidence, transaction history and a reviewed decision trail before changing the register.
When should similar asset rows be treated as duplicates?
Treat similar rows as duplicate candidates until physical identity and transaction history show that they represent the same controlled item. Matching descriptions or purchase amounts are screening clues. The decision needs a documented explanation of which record survives, what happens to associated history, and who approves any financial correction.
A municipal register may contain two entries called office printer, both purchased in the same month. Deleting the shorter row looks efficient, but the entries could represent two machines or a separately recorded component. A small decision worksheet helps the register team investigate the pair without turning a data cleanup into an unsupported accounting adjustment.
Build a pair file before comparing values
Give the suspected pair a review reference and preserve both original rows. Collect the tag, manufacturer serial, purchase reference, latest observed location and any earlier verification evidence. Record where each piece of evidence came from. A serial copied between spreadsheets is weaker than a serial observed on the machine, even when both fields contain identical text.
Compare the underlying purchase lines rather than only the invoice number. One invoice can contain several identical units. Conversely, an asset may have accumulated expenditure across multiple invoices. If the records have different acquisition histories, investigate that difference before accepting a similarity score produced by a spreadsheet or migration tool.
Distinguish duplication from a relationship
Ask whether one record describes a whole item and the other a component, attachment or later improvement. Obtain the approved register structure and ask finance to explain the intended treatment. An operational parent-child relationship can be appropriate even when the descriptions sound repetitive. The field team should identify the objects; finance should determine the effect on financial records.
Use three decisions: confirmed separate, confirmed duplicate, and unresolved. Write a short reason specific to the pair. For an unresolved case, state the missing evidence and the next investigation step. Do not create a false deadline by forcing every candidate into a definitive answer simply to finish the cleanup spreadsheet.
Close the correction without losing history
For a confirmed duplicate, propose a surviving identifier and map the retired record to it. Review photographs, movements, maintenance entries and attachments before changing references. Keep the old identifier searchable so a later auditor can follow an older document. Where values are affected, refer the proposed correction through the entity's accounting review process.
After the approved change, search both identifiers in the live register and linked reports. Check that one operational item appears, historical evidence is still reachable, and totals changed only as authorised. Report candidate pairs separately from confirmed removals. A high candidate count is a workload measure, not proof that the register was overstated.
Practical Example
Illustrative example: two printer rows share an invoice reference and model. Inspection finds different serials in separate offices, while the invoice lists two units. The reviewer retains both records and improves their descriptions. A third row repeats one observed serial and the same purchase line; that row remains a candidate until finance confirms its origin and approves the correction.
Action Checklist
- 1.Preserve both original rows and assign a single investigation reference to the suspected pair.
- 2.Compare observed identifiers with invoice quantities and individual purchase lines, recording evidence conflicts.
- 3.Ask finance whether the records represent a component relationship before proposing a merge.
- 4.Map retained history to the surviving identifier and test searches using the retired identifier.
Resolve suspected duplicate pairs with evidence-led support from Fixed Asset Register Reconciliation.
