What Is a Depreciation Schedule?

A depreciation schedule is a table that lists each fixed asset a business owns together with its cost, depreciation method, useful life, the depreciation expense charged in each period, accumulated depreciation to date, and the remaining book value. It is the working document that turns the accounting concept of depreciation into actual numbers: what was charged this year, what will be charged next year, and what every asset is still worth on paper.

Most people searching for the term are not looking for a definition - they are trying to build one. This page covers the column list a template needs, a step-by-step build, a multi-asset worked example with a totals row, the part-year and disposal rules that break home-made schedules, and how the book schedule differs from the tax schedule.

What you will learn

• What a depreciation schedule contains
• The columns a depreciation schedule template needs
• How to build a depreciation schedule, step by step
• Choosing a method - and what it does to the schedule
• A worked example
• Part-years, disposals and fully depreciated assets
• Typical useful lives by asset class
• Book schedule vs tax schedule
• Why the schedule matters
• Where depreciation schedules go wrong
• Keeping the schedule and the register in sync
• Spreadsheet or system?
• A note on property depreciation schedules
• FAQ

What a depreciation schedule contains

A usable schedule has one row per asset and, at minimum, these columns:

• Asset description and ID - enough detail to match the row to a real laptop, machine, or vehicle.
• Cost basis - the purchase price plus anything needed to bring the asset into use, such as delivery, installation, or non-recoverable duty.
• Depreciation method - most often straight-line for its simplicity, sometimes declining balance for assets that lose most of their value early.
• Useful life and salvage value - how long the asset is expected to serve, and what it should be worth at the end.
• Depreciation per period and accumulated depreciation - this period’s expense plus everything charged so far.
• Closing net book value - cost minus accumulated depreciation, the figure that flows into the balance sheet.

Depreciation is a non-cash expense. The money left the business when the asset was bought and sits in investing activities; the annual charge is an accounting entry that reduces profit and reduces the carrying amount on the balance sheet without moving any cash. That is why it gets added back in cash-flow analysis, and why a business can be loss-making on paper while still generating cash.

The columns a depreciation schedule template needs

If you are building a template rather than reading one, this is the full field list. Treat it as a checklist - most home-made schedules are missing three or four of these, and each omission causes a specific problem at year-end.

Two things a single-asset example never shows. First, a real schedule is multi-asset with subtotals per class - IT equipment, vehicles, plant and machinery, fixtures and fittings - because those subtotals map to the fixed-asset note in the accounts. Second, there is a totals row, and that row is the control: total depreciation for the period must equal what was posted to the ledger, and total closing net book value must equal the fixed-asset carrying amount on the balance sheet. If they do not tie, the schedule is wrong or the ledger is.

Spreadsheets provide built-in functions for the common methods - SLN for straight-line, DDB for double-declining balance, SYD for sum-of-the-years’ digits - so you rarely need to write the arithmetic by hand. What they do not provide is the part-year logic or the discipline of keeping the asset list current, which is where the real work sits.

How to build a depreciation schedule, step by step

1. Set a capitalisation threshold first. Decide the cost line below which purchases are expensed straight to the profit and loss account rather than capitalised. Without one, the schedule fills up with cables, mice and keyboards, and you spend an afternoon a year depreciating €30 items. Write the threshold into the accounting policy so it is applied consistently.
2. List every capitalised asset with its cost basis. The basis is the purchase price plus the costs of getting the asset into working condition: delivery, installation, commissioning, non-recoverable duty. It is not routine repairs, extended warranties billed separately, or training - those are period costs. Where one purchase covers several items, split it into separate rows.
3. Record the date placed in service, not the invoice date. A machine invoiced in November but commissioned in February starts depreciating in February. This one column drives every part-year calculation downstream, and getting it from a purchase order rather than from the person who unpacked the crate is how schedules drift.
4. Set useful life and residual value per asset class. Use a documented policy per class rather than a judgement call per purchase. Both estimates are reviewed at least annually - see useful economic life for how the estimate is arrived at and revised.
5. Pick the method per class. Straight-line for most things; something accelerated where the value genuinely falls fastest early; units of production where wear tracks output rather than time. Consistency within a class matters more than optimising each asset.
6. Apply a part-year convention in the first and last year. Pro-rata by month is the most defensible. Whatever you choose, apply it to every asset and document it.
7. Roll the schedule forward each period and reconcile. Carry closing net book value into next period’s opening, add the period’s purchases, remove disposals, then reconcile in two directions: against the asset register (does every row still exist physically?) and against the ledger (do the totals agree?). This roll-forward is the whole discipline. Everything else is arithmetic.

Choosing a method - and what it does to the schedule

The method changes the shape of the book value curve, not the total charged. Every method ends at the same place - cost minus residual value - it just gets there differently. Straight-line gives predictable annual costs and easy budgeting. Accelerated methods better match assets whose resale value collapses in the first two years, and they push more expense into early periods. Units of production is the honest answer for equipment whose life is measured in hours rather than years, but it needs a usage figure per period, which means someone has to read the meter.

A worked example

Start with the simple case. A laptop bought for €1,500 with a three-year useful life and a €300 salvage value, depreciated straight-line, carries annual depreciation of (1,500 - 300) / 3 = €400:

After year three the laptop sits at its salvage value and no further depreciation is charged, even if it stays in service.

A real schedule is a page of rows like that, in different methods, with a totals row that ties to the accounts. Here is year two of a small schedule covering three assets: the laptop above, a delivery van placed in service on 1 October of year one (€36,000, five-year life, €6,000 residual, straight-line, so €6,000 a year and three twelfths of that - €1,500 - in year one), and a press depreciated on units of production (€48,000 cost, €4,000 residual, 20,000 expected machine hours, so €2.20 an hour; it ran 3,000 hours in year one and 3,500 in year two).

The totals row is the point. €14,100 is the depreciation expense posted for the year; €62,900 is the fixed-asset carrying amount that must agree with the balance sheet; and €85,500 minus €22,600 proves the internal arithmetic. Any schedule where those three numbers do not reconcile to the ledger has a problem somewhere in the rows.

Part-years, disposals and fully depreciated assets

Part-years. A full-year charge is almost never right for a mid-year purchase. Pro-rata by month is the clearest approach: the van above earned three months of its annual charge in year one. Some tax regimes instead use conventions - treating every purchase as if it arrived at the mid-point of the year, so a half-year charge is taken regardless of the actual date. Either is defensible; mixing them asset by asset is not.

Disposals. When an asset is sold, scrapped or written off, three things happen. Charge depreciation up to the disposal date for the part-period the asset was in use. Remove the cost and the accumulated depreciation together, in the same entry - removing only one side is how phantom balances appear in the fixed-asset note. Then compare the proceeds to the net book value at that moment: proceeds above book value give a gain, proceeds below give a loss, and both land in the profit and loss account. See asset disposal for the full sequence and asset write-off for the case where there are no proceeds at all.

Fully depreciated assets still in use. The charge stops when net book value reaches residual value, but the row does not leave the schedule. It stays, at its residual value, flagged as in service, until the asset is actually disposed of. Book value zero and asset gone are two different states, and a schedule that deletes rows at the end of useful life loses the record of what the business still owns - which is exactly the information a fixed asset audit needs.

Revised estimates. If a five-year life turns out to be seven, you do not restate prior years. The change is prospective: take the current net book value, subtract residual value, and spread the remainder over the revised remaining life from now on. The same applies when residual value is revised. A permanent fall in value below carrying amount is a different event - that is impairment, recognised immediately rather than spread.

Typical useful lives by asset class

These are common accounting conventions, not rules. They are a starting point for a policy, and local tax rules will often prescribe something different.

Two sanity checks on any life estimate. Does it match how long the business actually keeps the asset? A three-year hardware refresh cycle with a five-year depreciation policy guarantees you will keep writing off residual book value early. And does it match how the asset is used? A van doing motorway miles and a van doing town deliveries do not wear at the same rate, even though they are the same asset class.

Book schedule vs tax schedule

Most businesses effectively run two schedules from the same purchase facts, and they rarely agree.

The book schedule follows the accounting standard. Under IAS 16 - and equivalently under FRS 102 and similar national frameworks - the depreciable amount, cost minus residual value, is allocated systematically over the asset’s useful life, with method, life and residual value reviewed at least annually. Where a significant part of an asset has a different life to the whole, it is depreciated separately: an aircraft engine, a lift in a building, a machine’s tooling. That is component depreciation, and it is what makes a book schedule more granular than a tax one.

The tax schedule follows whatever the local tax code prescribes, which is a policy instrument rather than an attempt to reflect economic reality. In the UK, capital allowances and writing-down allowances replace accounting depreciation entirely, and accounting depreciation is added back in the tax computation. In the US, statutory recovery periods and conventions apply, alongside first-year expensing provisions. Elsewhere in the EU, statutory linear or degressive rates per asset class are common.

The practical consequence: the same machine can carry an eight-year book life and a much shorter tax write-down period, so profit before tax and taxable profit diverge. The difference is one of timing, not amount - both schedules eventually relieve the same cost - which is precisely why it has to be tracked and reconciled rather than ignored. This page is not tax advice, and rates change; the point is structural. Both schedules need the same underlying facts - cost basis, date placed in service, asset class - so they must be fed from one register rather than assembled separately from invoices. Fixed asset accounting covers how the two reconcile.

Why the schedule matters

Three different jobs lean on the same table.

Accounting. The accountant needs the period’s total depreciation expense for the profit and loss account and the closing net book values for the balance sheet, plus the movement analysis - opening balance, additions, disposals, charge for the year, closing balance - that goes into the fixed-asset note. The schedule is where all of that comes from.

Tax. Cost, class and in-service date feed the tax computation even where tax rules apply their own rates and conventions, as above.

Replacement planning. This is the one operations cares about and it is usually the most underused. A schedule sorted by remaining life is a forward view of capital expenditure: which laptops fall due next year, which vehicles are close to the end of their economic life, which machines are already fully depreciated and running on borrowed time. Budgeting replacements from that table is far cheaper than budgeting them from a surprise failure, and it turns a compliance artefact into a planning tool. Pair it with real service history and you can see which assets are consuming maintenance spend faster than the schedule assumes - the classic signal that total cost of ownership has outrun the replacement case.

Where depreciation schedules go wrong

• Ghost assets. Symptom: the schedule keeps charging depreciation on a laptop that was scrapped eighteen months ago. Fix: reconcile the schedule against a physical inventory count at least annually. These are ghost assets, and they overstate both the balance sheet and the expense.
• No capitalisation threshold. Symptom: hundreds of rows for cables, adapters and mice, each depreciating €4 a year. Fix: set a threshold, expense below it, and clear the existing clutter in one pass.
• Cost basis wrong. Symptom: a machine on the schedule at its invoice price with the €4,000 installation expensed separately, or a €900 repair capitalised into an existing asset. Fix: a written rule on what enters cost basis, applied at purchase rather than at year-end.
• Inconsistent part-year rules. Symptom: some assets get a full first-year charge, others a monthly pro-rata, depending on who added the row. Fix: one documented convention, applied by formula rather than by hand.
• Never reconciled. Symptom: the schedule totals and the ledger disagree by an amount nobody can explain, and year-end becomes archaeology. Fix: reconcile every close, not every year - see asset reconciliation.
• No owner. Symptom: an asset leaves the building and nobody tells finance. Fix: make disposal a process with a step that updates the register, rather than a decision someone makes in a skip.

Keeping the schedule and the register in sync

The classic failure mode is divergence: the schedule lives in the accountant’s spreadsheet while the equipment list lives with operations, and within a year the two disagree. Disposed assets keep depreciating, new purchases never get a row, and the year-end reconciliation becomes archaeology.

The fix is a single source of truth for purchase date, price, supplier, and expected useful life, reviewed against reality whenever assets are bought, transferred, retired, or written off. The schedule is then derived from the register rather than maintained alongside it - which also means the person who knows an asset has gone is the person who records it, instead of finance discovering it a year later. Whatever the tool, the habit is the same: when an asset leaves the building, its row leaves the schedule.

Spreadsheet or system?

A spreadsheet is genuinely fine below roughly a hundred assets, with one method, one site and an annual close. SLN does the arithmetic, a totals row does the control, and the whole thing takes an hour a year.

It stops being fine when part-year conventions have to be applied across many different purchase dates, when management accounts are monthly rather than annual, when assets move between sites and departments, when you need an audit trail of who changed a life estimate and when, or when the register is kept by operations while the schedule lives with finance. At that point the spreadsheet is not the problem - the second, uncontrolled copy of the asset list is. Two lists always diverge, and the schedule is the one that ends up wrong, because operations has no reason to update it. Why Excel fails for asset tracking covers the failure modes in more detail; start with a simple asset register covers what to do first if you have neither.

A note on property depreciation schedules

The same phrase means something different in property investment. In Australia especially, a “tax depreciation schedule” is a report on an investment property prepared by a qualified quantity surveyor, itemising the building’s construction cost and the plant and equipment within it so the owner can claim deductions over time. It is commissioned once, from an external professional, for a single property.

The business fixed-asset depreciation schedule described on this page is a different document: prepared in-house, covering every capitalised asset the business owns, rolled forward every accounting period, and derived from the fixed asset register. Same words, different artefact.

FAQ

What is the difference between a depreciation schedule and an asset register? The asset register records everything about an item - owner, location, serial number, condition, service history. The depreciation schedule is the financial slice of that data: cost, method, useful life, the expense charged each period, and the remaining book value. The two should be fed by the same purchase information, otherwise the accounts end up depreciating assets the business no longer owns.

How often should a depreciation schedule be updated? At minimum once a year, as part of preparing year-end accounts. If the business produces monthly or quarterly management accounts, the schedule is updated on the same rhythm. It also needs a touch whenever something changes mid-year: a new purchase, a disposal, a write-off after damage, or a revised estimate of an asset’s useful life.

Do small businesses need a depreciation schedule? If the business owns depreciable assets and prepares accounts, yes - though it can be a simple spreadsheet. One row per asset with cost, purchase date, useful life, salvage value, and a straight-line calculation covers most small fleets of laptops, tools, and furniture. The discipline that matters is keeping it in step with what the business actually still owns.

What should a depreciation schedule template include? One row per asset with: description, asset ID, category, date placed in service, cost basis, method, useful life, residual value, the charge for the current period, accumulated depreciation to date, closing net book value, and a status flag (in use, disposed, fully depreciated) with disposal date and proceeds where relevant. Add subtotals per asset class and a totals row, because the totals are what get reconciled to the general ledger.

What is the difference between a book depreciation schedule and a tax depreciation schedule? The book schedule follows the accounting standard: the depreciable amount is allocated systematically over the asset’s useful life, and the life and residual value are reviewed each year. The tax schedule follows whatever the local tax code prescribes - capital allowances in the UK, statutory recovery periods and conventions in the US, fixed linear or degressive rates elsewhere. The same machine can carry an eight-year book life and a much shorter tax write-down period, so most businesses run both schedules from one set of purchase facts and reconcile the timing difference.

How do you depreciate an asset bought part-way through the year? You charge a part-year amount, not a full year. The common approaches are pro-rata by month (an asset placed in service on 1 October gets three twelfths of the annual charge) or a convention such as treating every purchase as if it arrived mid-year and charging half. Pick one approach, apply it to every asset consistently, and use the date the asset was placed in service rather than the invoice date. The final year then picks up the remaining part-period so the total charged still equals cost minus residual value.

The takeaway

A depreciation schedule is one row per capitalised asset, carrying cost basis, in-service date, method, life, residual value, the period charge, accumulated depreciation and closing net book value, with subtotals per class and a totals row that ties to the ledger. The arithmetic is the easy part - spreadsheets have functions for every method. What separates a schedule that works from one that quietly rots is the discipline around it: a capitalisation threshold so only real assets get rows, a consistent part-year rule, disposals that remove cost and accumulated depreciation together, and a reconciliation against what the business physically still owns. Build the schedule from the asset register, not beside it, and the year-end stops being archaeology.

Related terms

• Depreciation - the accounting concept the schedule puts numbers on
• Straight-Line Depreciation - the simplest method, an equal charge each year
• Declining Balance Depreciation - an accelerated method front-loading the expense
• Salvage Value - the estimated worth at the end of useful life
• Book Value - cost minus accumulated depreciation at any point in time
• Fixed Asset Register - the master list the schedule should be derived from
• Capitalisation Threshold - the cost line that decides what gets a row at all
• Asset Disposal - what happens to the row when the asset goes
• Ghost Asset - the asset still depreciating that no longer exists

Tools that make this easier

AMPthilly keeps the facts a depreciation schedule runs on directly on each asset record: purchase price and purchase date, supplier and invoice number, warranty start and end dates, expected useful life, depreciation context and replacement value. Because the same record carries owner, location and status, a retired or transferred asset is visible to finance rather than discovered at year-end, and the full audit history of transfers and status changes stays on the record. CSV export hands finance the underlying data to build or reconcile the schedule from the same register the rest of the organisation uses. Asset valuation and depreciation sit on the Pro plan. Start free - no credit card required - or talk to us about your setup.