• Assets and equipment · EAM
    • CFO / Finance, Accounting / Analytics, Plant / Operations Director, Operations Manager
    • Manufacturing, Retail and branch networks, Logistics and warehousing, Services and offices, Public sector

    The day after the asset count: why the register still does not match

    5 min read · Remanently team

    In short

    The register still does not match the day after an asset count because the signed report and the register are two separate documents, and nobody updated the second. Differences stay unresolved, moves during the year were never recorded and results sit in a file instead of in the record. Close the gap by treating the register correction as part of the count, assigning owners to differences and cutting the manual steps between confirming an item and updating the register.

    The picture on Monday morning

    The count ended Friday. The report is signed by the committee. The binder or the PDF is filed. On Monday, someone from accounting opens the register to prepare month-end and finds the same wrong locations, the same users who left last year and the same lines marked "not found".

    Nothing is broken in the sense of a mistake. The count was done. The report is correct about what was found on that day. It simply did not change the register, because the report and the register are different files owned by different people.

    Five reasons the register stays wrong

    1. The report is the deliverable. The count is treated as done when the report is signed. Nobody is assigned to update the register line by line.
    2. Differences are explained, not closed. A note says "probably transferred to the second site". The note sits in the report. The register still shows the old location.
    3. Results are retyped. Counts on paper or in a spreadsheet must be keyed into the register. It is slow, it gets postponed and then it gets forgotten.
    4. Moves during the year went unrecorded. So the differences have no evidence to settle them, and explanations depend on memory.
    5. Nobody owns the leftovers. A difference without a named owner and a due date does not get worked on.

    What to do on the day after

    1. Make a list of everything still open

    Export all differences into one table: item, kind of difference, owner, due date, status. If the list does not exist, build it from the count sheets today.

    2. Close the easy lines immediately

    Items found in a different room or with a different user need only a register edit. Do these first. They are often more than half of the differences and clearing them shrinks the problem fast.

    3. Assign owners to the hard ones

    Each remaining item needs one person and a date. Not a team. Ask the owner what evidence they will look for: documents, history, a call to the last known user.

    4. Set a closing date for the whole list

    Without a date, the list becomes background noise. Review it weekly until it is empty.

    5. Record what caused the differences

    Write one line for each group: moves not recorded, handover forms not filed, equipment sent for service without a ticket. These lines become next year's corrective actions.

    An illustration with made-up numbers

    Imagine a distribution company with six branches that closes its count on Friday. On Monday, finance sees 41 differences. Eighteen are wrong rooms inside the same branch, nine are laptops that changed users, eight are items found but not in the register, and six are not found. The branch leads fix the first group in an hour. Handover forms settle the laptops. Purchase documents explain most of the unrecorded items. Of the six not found, three turn up as items lent to a supplier. Three are confirmed shortages and go to the accountant. By Friday the register matches. The work was not hard. It needed owners and a date.

    What to tell the board

    Management usually wants one number: the amount to write off. Resist the urge to give it on Monday. Give a status instead: how many differences in total, how many closed, how many open with owners and dates, and which ones may become shortages. The amount can change as open lines close, and a number given too early gets quoted for months. When the list is closed, finance presents the final figure with the evidence behind it.

    Role by role: who does what on Monday

    Accounting collects the list and tracks status. Area owners close wrong locations and users in their own areas. The operations director reviews items with no trail and sets the escalation date. IT makes sure the register can be edited by the people who need to, and that every change leaves a record. Keep the weekly review short: open items, new decisions, blockers.

    A count is closed when the register is corrected

    This is the test that separates a ceremony from a control. Ask three questions after every count:

    • Does every difference have an owner and a due date?
    • Will the register actually be updated, or will the result end up only in the report?
    • How many manual steps separate physical confirmation of an item from a corrected register?

    If the third answer is "five", the register will lag. If it is "one", it will not.

    Reducing the lag permanently

    Record moves when they happen, not at count time. A transfer between branches, a handover to an employee and a return from service each take a minute to record if the process is simple. Without that, the next count will repeat the same Monday.

    In Remanently Assets the count result is compared with the register in the system, without retyping. Differences are listed by kind, history of location and responsibility is kept for each asset, and the register is corrected from the same place. Moves during the year are kept as history, so you start the next count with fewer unknowns. The asset count checklist turns these questions into 17 items to review before counting.

    Next steps: how to resolve asset count differences, who signs off a difference and how to run a physical asset inventory. For fields of the list itself, see the fixed asset register template.

    Frequently asked questions

    Why does the register still not match after the count is signed?

    Because the signed report and the register are separate documents. Unless someone updates the register line by line, the old locations and users stay.

    What should we do first the day after a count?

    Build one list of all open differences with owner, due date and status. Close the easy ones, such as wrong location and wrong user, right away.

    Who is responsible for updating the register?

    Name one person per difference and one coordinator for the whole list. The coordinator reports progress until the list is empty.

    How long should closing take?

    Agree a date at the end of the count. Simple corrections close in days, while items without a trail may need longer and an escalation point.

    How can we prevent the same gap next year?

    Record moves and handovers as they happen, keep an owner for each asset and review recurring causes. Cut the retyping between the count and the register.

    What do we tell the CFO when the board asks about the write-off amount?

    Share the list of differences with status: how many are closed, how many remain and who owns them. Treatment of shortages in the books is a decision for the accountant.

    Close the gap between count and register
    Book a short demo and we will show a count result turning into a corrected register on a sample of your own assets.

    Book a short Remanently demo See pricing

    Module: Remanently Asset Management (EAM) · Pricing · Contact · Get started