Accumulated depreciation, and the column header that gets it read as this year's

Two figures on a depreciation schedule describe the same asset and are not remotely the same number. One is what the asset has depreciated since it was placed in service. The other is what it depreciated this year.

On a well-printed schedule they sit in adjacent columns with unambiguous headings, and nobody confuses them. On a schedule where the heading is stacked across two lines, or abbreviated, or where the report was printed for book rather than tax purposes, they are one careless read apart.

The result of that read is not a small error. It is one year's deduction replaced by a decade of them, in a figure that looks entirely normal sitting in a spreadsheet cell.

Three terms that overlap and are not synonyms

Accumulated depreciation is the total depreciation taken on an asset from its placed-in-service date to a stated point. It is a running balance, and it is the accounting vocabulary — it is what reduces the asset on a balance sheet.

Current-year depreciation is the deduction for the year the report covers. A single year's slice.

Prior depreciation is a tax fixed-asset term for the accumulated total through the end of the previous year. It excludes the current year, which appears in its own column beside it.

So accumulated depreciation and prior depreciation are the same kind of quantity measured to different dates, and whether a given "accumulated" figure includes the current year depends entirely on what the report was printed to show. A book-oriented asset register typically includes it. A tax depreciation schedule typically does not, which is why it labels the column prior rather than accumulated — and what the prior column carries is the field an import actually needs.

Reading an accumulated figure into a prior field overstates prior by one year. Reading it into the current-year field overstates the year by everything before it.

Why a printed schedule makes them easy to swap

Three properties of real prints, none of which is a defect in the software that produced them.

Stacked headers. Column headings on a dense report wrap. A heading reading Current Accum Depreciation — a Sage FAS convention — occupies two lines, and whichever word sits on the top line looks like the header if you read the top line as the header row. The column holds accumulated depreciation. The word above it says Current.

Abbreviation. Prior Dep, Accum Depr, Depr Allowed, Depreciation to Date all appear, and none of them says on its face whether the current year is inside.

Book selectors. Sage prints a Depreciation Expense Report against a named book, and a header line stating something like Book = Internal tells you the figures are the internal book treatment rather than the tax one. That line is easy to skim past, and the columns beneath it look exactly like tax columns.

The failure is silent, and it is proportional to the asset's age

Consider an asset placed in service eight years ago, cost 90,000, depreciating a little over 11,000 a year. Accumulated depreciation is around 89,000. Current-year is 11,000.

Swap them and this year's deduction becomes 89,000 — eight times what it should be — while the accumulated figure carried forward becomes 11,000, leaving the asset showing 79,000 of basis it does not have. Neither number is impossible. Neither triggers a rejection on import. The return computes, the schedule prints, and the error compounds into every subsequent year until somebody sells the asset.

The oldest assets on a schedule are the ones where the swap is largest, which is the opposite of where anyone is looking by the time they reach row 140.

What a totals check catches, and what it does not

Tie the extracted rows against the totals the schedule printed, per group and in grand total, at a dollar's tolerance. That is the check that verifies a transcription and it does catch a large class of column errors — if accumulated values were read into the current-year column, the current-year total will not match the printed current-year total.

Where it stops is more interesting.

If a reader misidentifies the column and takes the printed subtotal from the same misidentified column, both sides move together and the comparison passes. The transcription is then internally consistent and describes the wrong quantity.

And a specific compound failure worth naming: if the misread also leads to a conclusion that the document has no prior depreciation column — because the column that held it was consumed as something else — then every row of that section carries a claim that the source omitted the figure. That claim is checkable, and it is false whenever the same page prints a total for the column said to be missing. A print cannot total a column it does not have.

Reading the header before reading the rows

Read the whole header block, not the top line. Stacked headings are common on dense reports. Where a heading occupies two lines, the second line often carries the noun that decides the meaning.

Find the report title and any book selector. A report naming an internal or book treatment is not the federal tax figures, however familiar the columns look.

Count the depreciation columns. A schedule with one depreciation column is telling you something different from one with two. If there are two, one of them is a running total and one is a year, and the totals line will usually make clear which is which — a current-year total is small relative to cost, an accumulated total approaches it.

Sanity-check the oldest asset. For an asset near the end of its recovery period, accumulated depreciation should approach cost. If the figure in the column you took as accumulated is a small fraction of cost, you have the year, not the total.

What we do with it

The extraction reports which columns a print does not carry, once per excerpt rather than per row, because that is what keeps the cost of a conversion proportional to the number of assets. The consequence is that a single misread header would otherwise land on every row that excerpt produced.

So an absent-column claim is refused when the same excerpt reports a printed total for that column, for the three figures the reconciliation compares. A page that prints a prior depreciation total demonstrably has a prior depreciation column, and the honest report is that the transcription is damaged — flagged unreadable — rather than that the source omitted the data.

The distinction matters because of what a preparer would do next. Told that a source genuinely does not print a column, they can clear the flag and move on, because they know a Lacerte summary schedule really does omit columns. Told the same thing falsely, they would clear it and export a file booking accumulated depreciation as the current year. Both stories block the download. Only one of them is true.

Both arrive as part of the same job: turning a new client's prior year depreciation schedule into something your software will accept.

FAQ

What is accumulated depreciation on a fixed asset schedule?

The total depreciation taken on the asset from its placed-in-service date to a stated point. Whether that point includes the current year depends on the report — book-oriented registers usually include it, tax schedules usually print prior depreciation through the end of the previous year with the current year in a separate column.

Is accumulated depreciation the same as prior depreciation?

They are the same kind of running total measured to different dates. Prior depreciation on a tax schedule stops at the end of the previous year; an accumulated figure on a book report typically includes the current year, so reading one as the other overstates by a year.

How does accumulated depreciation get transcribed as the current year?

Most often through the header. Dense reports stack column headings across two lines, so a heading such as Current Accum Depreciation reads as Current if only the top line is taken as the header row, while the column beneath holds the accumulated total.

Will tying out the totals catch a swapped column?

Usually. The current-year total will not match if accumulated values were read into it. It will not catch the case where the subtotal was taken from the same misidentified column, because then both sides of the comparison moved together.

How can I tell quickly which column is which?

Compare against cost on the oldest asset in the list. Accumulated depreciation on an asset near the end of its recovery period approaches its cost; a current-year figure is a small fraction of it.

The schedule says Book equals Internal at the top. Does that matter?

It indicates the report was printed for a named book rather than the federal tax treatment. The columns look the same and the figures are not, so the report title and any book selector are worth reading before the rows.