It's in the register. But do you know where it really is and what happened to it?
Remanently adds operational context to the register: location, responsible person, handover, movement, batch, deadline and stock-take result. The ERP can remain the source of accounting data, while the physical process supplies the information needed to explain discrepancies.
Easy to manage
3x more efficient operations
The most time-consuming part is not counting assets. It's explaining why the result differs.
„In the system it's at headquarters, physically it works at the branch.”
„The equipment has a department owner, but someone else uses it.”
„The warehouse shows a stock level that isn't on the shelf.”
„Every department keeps its own spreadsheet.”
„It's unclear when and why the location changed.”
„The discrepancy is only visible during the stock take.”
Data is useful when you can trace a line in a report back to the real object.
Asset Management
What the company owns and where it is
The register, identification, location, person and handover history help reconcile the physical state.
See the asset process →Stock take
Focus on explaining exceptions
You check the actual state, then focus on the discrepancies found.
See the first process →WMS
What, how much and where it is in the warehouse
Stock can be analysed in the context of product, warehouse, batch, location and record type.
See warehouse data →Movement history
Where the change comes from
WMS keeps the batch history from receipt through subsequent operations to issue.
See batches and movement →CMMS
What happened to the device
A machine stays connected to reports, inspections, work orders and technical history.
See asset history →Trade Marketing
How the cost of terms was created
Budgets, price lists, turnover, promotions and bonuses create the context needed to settle profitability.
See reporting →Don't rewrite the balance. Record the change where it actually happens.
Accounting values, documents and registers can stay in the source system. Before implementation you need to establish which data is imported, where the operational change happens, and what result feeds back into further settlement.
Which reconciliation do you need?
Asset ledger ↔ physical state
Location, user, identification and stock-take discrepancies.
Asset Management →Stock level ↔ location contents
Product, batch, stock type, movement and count result.
WMS →Device ↔ cost and activity history
Reports, inspections, repairs and parts used.
CMMS →Turnover ↔ cost of promotions and bonuses
Customer, product, term, execution and budget usage.
Trade Marketing →Identify the documents, registers and events that should link accounting records with the operational state.
First decide which discrepancy you want to explain faster.
You already know where the object is. But do you know what happened to it?
State is the start. History explains the change. Link processes when the next report needs context from the previous one.
The asset has been found. Which technical actions concerned it?
Link the device to reports, inspections and repairs.
See technical history →A part left the warehouse. What was it used for?
Link the stock issue to the machine and specific repair.
See parts in CMMS →Sales grew. What was the cost of the terms?
Set turnover against promotions, discounts, free items and bonuses.
See profitability →Questions before reconciling data.
Show us the one discrepancy that takes the most time to explain today.
Let's establish the source record, the operational event and the data needed for reconciliation.