Odoo Asset Management and Depreciation Guide for Finance

The Spreadsheet That Runs Your Balance Sheet

Ask a finance manager where the fixed asset register lives and the answer is often a file name. Ask who maintains it and the answer is often one person. Ask what happens if that file is wrong, and the answer involves the balance sheet, the tax computation and the audit file, in that order.

This is not negligence. The asset register is one of those things that works perfectly well as a spreadsheet right up until the point it does not. And the point it does not is usually an audit, a disposal nobody recorded, or the discovery that depreciation has been running on an item that was scrapped two years ago.

This article covers what a proper register holds, how asset accounting works once it sits inside the ERP rather than beside it, the capitalisation policy that has to exist before any of it, the events that quietly break registers, and how to migrate an existing one without importing its errors. It is written for finance managers, controllers and CFOs, particularly those who have just had a question from an auditor they could not answer quickly.

The Business Problem: A Material Balance Managed Informally

Six symptoms, and most businesses running a spreadsheet register have at least four.

• Depreciation is calculated outside the system and posted as a manual journal. Every month, someone opens the file, reads a total, and types it into the ledger. The ledger and the register agree because a person made them agree, not because they are connected.
• The register and the general ledger drift apart. Usually slowly, usually by small amounts, and usually discovered at year-end when the reconciliation does not work and nobody can say when it stopped working.
• Disposals are recorded late or not at all. An item is scrapped, sold or written off, and the event reaches the register whenever someone remembers to mention it. Until then, the business is depreciating something it no longer owns.
• Nobody can trace an asset to a physical item. No tags, no location field maintained, no custodian. The register says there are forty-two laptops; nobody can show you forty-two laptops.
• There is one spreadsheet and one person who understands it. Formulas that have evolved over years, assumptions nobody has revisited, and a key-person dependency that becomes visible at the worst moment.
• Tax and accounting depreciation are muddled. Where the two differ, the register typically holds one and the tax computation is adjusted outside it, in a second file, maintained by a second process.

What the Spreadsheet Register Actually Costs

• Audit time, every year. A register that cannot be reconciled quickly becomes an audit query, and audit queries become fee adjustments. The cost is both the fee and the finance team’s time during the busiest period of its year.
• Misstated depreciation, in both directions. Assets still depreciating after disposal overstate the charge; assets capitalised late or missed entirely understate it. Neither is dramatic in a month and both accumulate.
• Tax exposure. Where tax depreciation follows different rules from accounting depreciation, an informal register makes the computation harder to support. The risk is less about getting it wrong and more about being unable to demonstrate how you got it right.
• Insurance mismatch. Cover is usually set from the register. A register that overstates what exists means paying for cover you do not need; one that understates it means discovering a gap at claim time.
• Capital decisions made blind. Without reliable age, cost and location data, replacement planning is guesswork. The question “what is the average age of our plant at the Pune site?” should take a minute, and in a spreadsheet-run business it takes a day.
• Key-person risk. The most underrated of all. A register maintained in one person’s formulas is a register that becomes unmaintainable the moment they leave.

What a Proper Asset Register Holds

Worth listing explicitly, because the gap between this and a typical spreadsheet is where most problems come from.

• Identity. A unique reference, a description that distinguishes similar items, and (critically) a link to the physical item, usually through a tag or serial number.
• Acquisition. Purchase date, supplier, invoice reference, cost, and any directly attributable costs capitalised with it. The link back to the purchase document is what makes audit straightforward rather than archaeological.
• Classification. Asset category, which should drive the default depreciation treatment rather than leaving it to be chosen per asset.
• Depreciation parameters. Method, useful life, residual value, and the date depreciation starts, which is the date the asset was available for use, not necessarily the date it was invoiced.
• Position. Accumulated depreciation to date, net book value, and the remaining schedule.
• Location and custodian. The site, the department, and who is responsible. Without this, physical verification is impossible and no amount of accounting discipline fixes it.
• Lifecycle events. Transfers between sites or departments, revaluations, impairments, and disposals with their date, proceeds and resulting gain or loss.
• The accounting links. Which asset account, which accumulated depreciation account, which expense account. Set at category level, so individual assets inherit rather than being configured one at a time.

How Asset Accounting Works in Odoo

The structural change when the register moves into the ERP is not that depreciation gets calculated; a spreadsheet does that. It is that the register and the ledger stop being two things that have to be reconciled.

• Assets are created from the source transaction. Rather than typing an asset into a separate file after the invoice is posted, the asset originates from the purchase it came from. The audit trail from invoice to asset to depreciation entry exists because it was never broken, not because somebody reconstructed it.
• Categories carry the defaults. Depreciation method, useful life and the relevant accounts are set once per category. A new asset in that category inherits them, which is what stops a register from accumulating inconsistent treatment over time.
• Depreciation posts to the ledger directly. The schedule generates the entries and they post. The register and the ledger agree by construction rather than by a monthly act of typing.
• The schedule is visible in advance. Future depreciation is a known, reportable figure rather than something recalculated when budgets are being prepared.
• Disposal is an accounting event, not a deletion. Recording a disposal stops the depreciation, removes the carrying value and recognises the gain or loss in one step, with the history retained.

An important caveat to establish early. Accounting capability in Odoo differs by edition. Odoo’s own comparison lists accounting, including comprehensive accounting, among the items where the editions differ. What is available to you therefore depends on your edition and version, and that is a question to settle with your partner before scoping the work rather than after.

The Capitalisation Policy You Need First

This is the step that gets skipped, and skipping it is why registers become inconsistent.

• Set a capitalisation threshold and apply it. Below the threshold, expense. Above it, capitalise. Without a written threshold, the decision gets made per invoice by whoever is posting, and the register fills with items that should have been expensed while genuine assets get missed.
• Define what is capitalised with the asset. Delivery, installation, commissioning, directly attributable professional fees. Being explicit prevents both the understatement of cost and arguments at audit.
• Agree component treatment. Where parts of an asset have materially different useful lives, they may need separating (for IFRS reporters, IAS 16 sets out this component approach). This is an accounting judgement rather than a software setting, and it should be agreed with your auditor rather than decided by whoever builds the register.
• Fix the useful lives by category, and write down the reasoning. Not asset by asset. The reasoning matters more than the number, because it is what you will be asked for.
• Decide the depreciation start convention. From the date available for use, from the start of the following month, or pro-rata from the acquisition date. Any is defensible; inconsistency is not.
• State how tax depreciation is handled. Where tax rules differ from accounting treatment, decide whether the difference is tracked in the system or computed separately, and document the position. Confirm the specific rules for your jurisdiction with your tax adviser; this article does not attempt to state them.
• Define the physical verification cycle. How often assets are physically checked against the register, by whom, and what happens to differences. A register nobody verifies is a list, not a control.

Disposals, Transfers and the Events Nobody Records

Registers rarely fail at acquisition. They fail at everything afterwards.

• Disposals are the main offender. An asset is sold, scrapped, traded in or written off. Operationally the event is complete; accounting-wise nothing has happened until somebody tells finance. The gap between those two moments is where a register goes wrong, and it is a process problem rather than a system one: somebody in operations needs an obligation to report disposals, with a route to do it.
• Transfers between sites or departments. Not an accounting event in most cases, but a register event, and if location is not maintained, physical verification becomes impossible within a couple of years.
• Assets in use but not yet capitalised. Equipment commissioned and running while the final invoice is outstanding. It needs recognising, and the common failure is capitalising only on invoice receipt, which can defer the start of depreciation beyond the date the asset was actually available for use.
• Partial disposals. Part of a larger asset is removed or replaced. Requires judgement and should be agreed with your auditor rather than improvised.
• Impairment. An asset that is still there but no longer worth its carrying value. Requires an assessment, and the trigger for that assessment should be defined rather than waiting for the auditor to raise it.

The practical control: a short, scheduled exception report listing assets fully depreciated but still on the register, assets with no location, assets with no custodian, and assets not seen in the last verification. Reviewed quarterly, it catches most of what would otherwise reach the auditor first.

Migrating an Existing Register

The migration is where you either fix the register or import its problems permanently.

• Reconcile the spreadsheet to the ledger before you move anything. If they do not agree today, migrating will not make them agree; it will freeze the difference. Find and explain the variance first.
• Verify physically before you migrate, not after. This is the single most valuable step and the one most often postponed. A register migrated without verification carries forward every asset that no longer exists.
• Normalise categories. Most spreadsheet registers have accumulated more categories than the business needs, with inconsistent lives inside them. Migration is the moment to consolidate, because it will not be politically possible later.
• Decide the cut-over date and the opening position. You are migrating cost, accumulated depreciation and net book value as at a specific date, with the remaining schedule computed from there. Agree that date with your auditor.
• Keep the old register as a read-only archive. The history matters for audit even once it is superseded.
• Run one month in parallel. Generate the depreciation posting in both the new system and the old method, compare, and reconcile every difference before relying on the new one. Differences at this point are nearly always a useful-life or start-date inconsistency, and finding them in parallel is far cheaper than finding them at year-end.

Spreadsheet, Odoo and Specialist Software Compared

The honest position: specialist asset management software earns its place where the asset estate is large, mobile, or subject to regulatory inspection regimes. For the majority of mid-market businesses, the decisive advantage of handling assets in the finance system is simply that there is no interface to maintain and no second reconciliation to perform.

Best Practices

1. Write the capitalisation policy before you build anything: threshold, what is capitalised with the asset, component treatment, useful lives by category, start convention, and the tax position.
2. Set depreciation defaults at category level, never asset by asset.
3. Create assets from the source transaction so the audit trail exists rather than being reconstructed.
4. Physically verify before migrating. The one step that makes the new register trustworthy from day one.
5. Maintain location and custodian. Without them, verification becomes impossible within two years.
6. Give operations an obligation and a route to report disposals, because that is a process gap, not a system gap.
7. Run a quarterly exception report: fully depreciated but still held, no location, no custodian, not verified.
8. Run one month in parallel before relying on the new postings.
9. Agree the cut-over date and opening position with your auditor rather than choosing it internally.
10. Schedule the physical verification cycle with a named owner, or it will not happen.

Common Mistakes

• Migrating without verifying. You import every asset that no longer exists and make the error permanent.
• No capitalisation threshold. The register fills with items that should have been expensed, and the inconsistency is impossible to unwind later.
• Useful lives set per asset. Within two years the same class of asset carries three different lives and nobody can explain why.
• Treating disposal as a deletion. The history disappears and the gain or loss never reaches the ledger properly.
• Capitalising only on invoice receipt. Depreciation starts late on assets that were available for use months earlier.
• Ignoring location and custodian because they are not accounting fields. They are the fields that make the register verifiable.
• Leaving tax depreciation undocumented. The computation becomes unsupportable even when it is correct.
• No parallel run. Differences in useful life and start convention surface at year-end instead of during implementation.
• Assuming capability without checking the edition. Accounting depth differs by Odoo edition; confirm before scoping.

An Illustrative Scenario: A Manufacturer With Three Sites

The following is a composite illustration drawn from patterns common to this kind of migration. It is not an account of a specific Techvaria client, and no figures below come from any real engagement.

Consider a manufacturer operating three sites, with plant and machinery, vehicles, IT equipment and leasehold improvements. The register is a workbook maintained by the financial controller, with a tab per category and depreciation posted monthly as a single journal.

The Trigger

An audit query. The auditor asked for a reconciliation between the register and the ledger and for evidence supporting the disposal of a machine listed as sold during the year. The reconciliation took three days and produced a difference nobody could explain fully. The disposal evidence existed, but the machine had continued to depreciate for four months after it left the site.

What the Review Found

Items on the register that no longer existed at any site, including equipment scrapped during a line reconfiguration that had never been reported to finance. Three different useful lives in use for materially identical equipment, applied at different times by different people. No location field maintained beyond the site name, and no custodian recorded anywhere. And a second workbook, maintained separately, holding the tax depreciation computation.

What Was Implemented

The policy came first: a written capitalisation threshold, what is capitalised alongside the asset, useful lives agreed by category with the reasoning documented, and a start convention. Agreeing the useful lives took longer than expected, because the differences in the old register turned out to reflect genuine disagreement that had never been resolved, only recorded.

A physical verification ran before migration, site by site, using the existing register as the starting list. It took three weeks and removed a number of items that no longer existed. Assets were tagged during the same exercise, which was the only practical opportunity to do it.

Categories were consolidated, defaults set at category level, and the register migrated at an agreed cut-over date with cost, accumulated depreciation and net book value as at that date. One month ran in parallel; the differences that emerged were start-convention inconsistencies on assets acquired mid-month, which were resolved before switching.

A disposal reporting route was created (a short form from site management to finance, required before equipment leaves a site) and a quarterly exception report was scheduled.

After Two Quarters

The month-end depreciation journal stopped being a manual step. The reconciliation the auditor had asked for became a report rather than a project. The controller’s own summary was that the system change was the smaller half of the benefit: the verification and the written policy were what fixed the register, and the system was what kept it fixed.

Industry Use Cases

• Manufacturing. The heaviest asset base and the most frequent unreported disposals, because equipment is scrapped and replaced as part of normal operations. See manufacturing solutions.
• Logistics and transport. Vehicles and handling equipment, where location changes constantly and the register’s location field is the hardest to keep meaningful. See logistics solutions.
• Healthcare. Medical equipment with service and calibration obligations attached, where the asset record and the maintenance record need to refer to the same item. See healthcare solutions.
• Education. Dispersed IT and laboratory equipment across campuses, typically with weak custodian tracking and a high rate of informal redeployment. See education solutions.
• Construction. Plant moving between sites, where transfers are frequent and the distinction between an asset and a consumable needs a clear threshold. See construction.