Reading a MACRS depreciation schedule

Search for a MACRS depreciation schedule and you get two entirely different documents, both
correctly named.

One is a set of percentage tables published by the IRS in Publication 946 — the rate applied to an
asset's basis in each year of its recovery period. The other is the multi-page listing a tax suite
prints, one row per asset, showing what a specific client owns and what each item has taken.

They answer different questions, and which one you need depends on why you are asking. If you are
checking whether a figure is right, you want the tables. If you have just inherited a client and are
trying to get ninety assets into your own software without re-keying them, you want the listing —
and the tables will not help you at all.

This is about both, but mostly the second, because the second is the one that arrives as a PDF from
someone else and has to be read rather than looked up.

Two different documents share the name

The percentage tables are generic. Appendix A of Publication 946 gives, for each property class
and convention, the percentage of basis deductible in each year. They contain no client information
and never change for a given year and class.

The printed schedule is specific. It is generated from the preparer's fixed asset module and
lists real assets: description, date placed in service, cost, method, life, what has been taken in
prior years, and what is taken this year. It usually subtotals by activity and foots to a grand
total.

Only the second is a record of anything. The first is a lookup.

A useful consequence: the printed schedule is the document that carries forward between preparers,
and it is the only place per-asset history exists outside the software that produced it. A filed
return will not substitute for it — Form 4562 collapses every asset
placed in service in an earlier year into a single figure on line 17, with no descriptions, dates,
methods or lives behind it.

What the system fixes, and what the page has to print

MACRS determines an annual deduction from four things, plus the date the asset was placed in
service:

• The property class, which sets the recovery period — 3, 5, 7, 10, 15, 20 or 25 years under the general depreciation system, 27.5 years for residential rental property, 39 years for nonresidential real property placed in service after the relevant date, with 31.5 applying to older nonresidential real property.
• The method — 200% declining balance switching to straight line for the shorter classes, 150% declining balance for the 15- and 20-year classes and wherever elected or required, and straight line for the 25-year class and for real property.
• The convention — half-year, mid-quarter or mid-month, which decides how much of the first and last years count.
• The basis for depreciation, business or investment use only.

Everything else on the page is derived from those. That is why the same five or six fields turn up
as the required columns of every import format, and why a schedule missing one of them cannot be
imported no matter how complete it otherwise looks.

Note what is not in the list: nothing about MACRS depends on what the asset is called. The
description column is for humans and for matching rows against the client's records. It carries no
weight in the computation, which is why suites treat it so casually — truncating it, wrapping it
across lines, or printing an internal asset number instead.

Why a 5-year asset appears on the schedule for six years

This is the single most common confusion when someone reads a printed schedule for the first time,
and the answer is the convention rather than an error.

Under the half-year convention, an asset is treated as placed in service at the midpoint of the
year regardless of the actual date. Half a year's depreciation in year one leaves half a year to
recover at the end, so the recovery spills into one extra tax year. The published percentages make
this visible:

Year	3-year	5-year	7-year	10-year
1	33.33	20.00	14.29	10.00
2	44.45	32.00	24.49	18.00
3	14.81	19.20	17.49	14.40
4	7.41	11.52	12.49	11.52
5	—	11.52	8.93	9.22
6	—	5.76	8.92	7.37
7	—	—	8.93	6.55
8	—	—	4.46	6.55
9	—	—	—	6.56
10	—	—	—	6.55
11	—	—	—	3.28

Those are the half-year columns of the general depreciation system table for the declining-balance
classes. The 15- and 20-year classes run on 150% declining balance and have their own columns in the
same IRS appendix; the mid-quarter and mid-month conventions each have separate tables again. The
canonical source is Publication 946, Appendix A, and it is worth reading there rather than from a
copy — including this one.

Under mid-quarter, first-year percentages differ by the quarter the asset was placed in service, so
four separate tables exist. Under mid-month, used for residential rental and nonresidential real
property, they differ by month, so the first-year rate depends on which of twelve columns applies.

The columns a printed schedule actually carries

Across the suites that produce these documents — Lacerte, ProSeries, UltraTax and Fixed Assets CS,
Drake, Sage — the column inventory is broadly the same, with real variation in naming and in what
gets omitted:

What it is	Printed as	Notes
Description	Description, Asset, Property	Often truncated; sometimes an internal asset number
In-service date	Date in Service, Acquired, Placed in Service	Format varies by suite and by locale
Cost	Cost, Basis, Acquired Value, Cost/Other Basis	"Basis" may already be net of §179 or bonus
Business use	Bus %, Business Use %	Frequently absent entirely
Method	Method, Meth, Depr Method	See below — four spellings of the same thing
Life	Life, Recovery, Rec Per, Yrs	Sometimes merged into the method column
Convention	Conv, Convention, HY/MQ/MM	Sometimes merged into the method column
Prior depreciation	Prior Depr, Accumulated, Current Accum Depreciation	The naming here causes real errors
Current depreciation	Current, This Year, Depreciation	The column that ties to the return
§179	Sec 179, 179 Exp	Current year, prior year, or both, depending on the print
Bonus	Special Depr Allowance, SDA, Bonus	Same

Two of those rows deserve flagging.

Prior depreciation naming is genuinely dangerous. A header reading "Current Accum" above
"Depreciation" is accumulated depreciation as of the report date — prior depreciation — and reads
naturally as the current year's figure. Getting that backwards moves a large number into the wrong
field for every row on the page at once, and because both are legitimate dollar amounts, nothing
downstream objects.

The prior §179 and prior bonus columns are the ones most often absent. Some prints separate
them; some fold all three components into one combined prior depreciation figure. The combined
figure is the correct total, so the page still foots — the loss is invisible. That specific failure,
and what it costs on a disposal, is covered in
what Lacerte's summary schedule leaves out.

The method column, and the several ways to write the same thing

The method column is short, and that is the problem. The same treatment appears as 200DB,
200 DB, DDB, MACRS, M200, 200DB/HY, or as a bare %. Straight line appears as SL,
S/L, or Straight Line. Some suites print method, life and convention as three columns; others
compress all three into one string like 5.0 200DB HY.

None of that is ambiguous to a preparer reading the page. It becomes ambiguous the moment it has to
become a value in an import file, because the destination does not accept free text. Intuit's
imports — used by both the Lacerte Fixed Asset Import and
the ProConnect depreciation template — want a numeric code from a
fixed table, and that code carries the life and the method together:

Code	Meaning
34 / 35	3-year, declining balance / straight line
53 / 54	5-year, declining balance / straight line
57 / 58	7-year, declining balance / straight line
66 / 67	15-year, declining balance / straight line
85	27.5-year straight line, residential real estate
87	31.5/39-year straight line, nonresidential real estate
91 / 92 / 93	Straight line / 200% DB / 150% DB, outside a recovery class

So "5-year, 200DB" resolves cleanly to one code. Several printed strings do not resolve at all, and
the honest ones are worth knowing:

A method printed without a life. The code table is indexed by both. A method column reading
200DB with an empty life column does not identify a row.

A life the destination's table has no entry for. Schedules occasionally carry lives that the
import's method table does not enumerate.

Anything on five-year property that looks like a vehicle. There are four different 5-year codes
covering vehicles — with luxury-auto limits, without, trucks under 6,000 pounds, vehicles over
6,000 pounds — and a printed schedule almost never states which applies. The page says 5.0 200DB
and the weight of the truck is not on it.

Drake's 4562 import takes a different route, a positional spreadsheet
of 104 columns rather than coded values, but the underlying requirement is identical: the facts have
to be unambiguous before the file is built.

Conventions, abbreviated to two letters

HY, MQ and MM are half-year, mid-quarter and mid-month. They appear in their own column, in
the method string, or not at all.

When the convention is not printed, it is not always recoverable from the rest of the row. Mid-month
follows from real property, so a 27.5- or 39-year life implies it. Half-year and mid-quarter both
apply to the same property classes, and which one governs depends on the aggregate of everything
placed in service that year — more than 40% of the year's basis in the final quarter switches the
whole year to mid-quarter. That is a fact about the client's year, not about the asset, and a
per-asset row cannot carry it.

Which means: a schedule that omits the convention column has omitted information that cannot be
reconstructed from the page. It can be recovered from the prior preparer's software, or from the
year's Form 4562 where column (e) of Part III, Section B states it for current-year additions.

What a schedule is missing more often than preparers expect

Ranked by how often it bites, in the real prints we have read:

The prior §179 and prior bonus split, folded into a combined prior depreciation figure.

Business use percentage, absent from the print entirely — and, separately, absent from some
destinations' import formats even when the source does state it.

The convention, as above.

State treatment. Where a state decouples from federal bonus depreciation, the asset has a second
basis and a second accumulated figure. Most federal depreciation schedules print one treatment;
where the state amounts exist, they are usually on a separate schedule that nobody thinks to ask
for.

Disposal information for assets sold during the year, which some prints show in a separate
section and others drop from the listing altogether.

None of these are printing errors. Each one is a deliberate choice about what a particular report
variant includes, made by whoever clicked print, and none of it is visible from the page you
received. If you are moving a client between suites, the practical move is to ask for the detailed
variant and the fixed-asset export before assuming the PDF is complete — the mechanics of that are
on the switching tax software page.

What we do with it

This tool reads what a schedule prints and writes the import file the destination accepts. It does
not compute a rate, apply a table, or decide a method.

Where the printed method and life resolve to exactly one code, they are transcribed. Where they do
not — a missing life, a life with no entry in the destination's table, a five-year vehicle whose
variant the page does not state — the field comes back empty with the reason attached, and the flag
blocks the download until you resolve it. The same applies to prior components a summary print never
separated.

Before any of that, the totals printed on the PDF are compared against the sum of the extracted
rows, per activity and in grand total. If they disagree, there is no file.

FAQ

What is a MACRS depreciation schedule?

The term covers two documents. One is the IRS percentage tables in Publication 946, Appendix A,
giving the deductible percentage of basis for each year of a property class under a given
convention. The other is the per-asset listing a tax suite prints for a specific client, showing
description, in-service date, cost, method, life, prior depreciation and current depreciation.

Why does a 5-year asset show six years of depreciation?

The half-year convention treats the asset as placed in service at the midpoint of the first year, so
only half a year is taken then and the remaining half falls into an additional tax year at the end.
The same effect gives 3-year property four years, 7-year property eight, and 10-year property
eleven.

What are the three MACRS conventions?

Half-year, mid-quarter and mid-month, printed as HY, MQ and MM. Mid-month applies to residential
rental and nonresidential real property. Mid-quarter applies where more than 40% of the year's basis
was placed in service in the final quarter, which is a fact about the whole year rather than about
any single asset.

Can I tell the convention from a schedule that does not print it?

Only partly. A 27.5- or 39-year life implies mid-month, because real property uses it. Half-year and
mid-quarter apply to the same property classes and are distinguished by the aggregate of everything
placed in service that year, which no single row carries. Column (e) of Part III, Section B of that
year's Form 4562 states it for current-year additions.

Why do imports want a numeric method code instead of the printed method?

Intuit's spreadsheet imports accept values from a fixed table rather than free text, and each code
carries the recovery period and the method together — 53 is five-year declining balance, 54 is
five-year straight line. A printed string like "200DB" identifies a code only in combination with a
life, which is why a schedule that prints the method but omits the life cannot be mapped.

What does a printed schedule most often leave out?

The split between prior regular depreciation, prior §179 and prior bonus, folded into one combined
figure; business use percentage; the convention; and state amounts where the state decouples from
federal bonus. All of these leave a page that still foots correctly, which is what makes them easy
to miss.