The Fixed Asset Roll-Forward Is the Cheapest Win in Your Close

Across the 65,000-plus active accounting and finance postings we're tracking right now, 4,260 of them name fixed assets as part of the job, and 3,540 of those - 83% - name Excel in the same listing. Those two numbers sitting next to each other are the whole story. The most rules-driven schedule in the entire close, the one where the math is fully determined by a policy you already wrote down, is still being maintained by hand in a spreadsheet at four out of five employers who mention it.

I think fixed assets is the single most underrated place to start with AI in accounting, and it's underrated precisely because it's boring. Nobody writes conference talks about depreciation. But the boring stuff is exactly where the machine is reliable, because a fixed asset roll-forward is a closed system - beginning balance, additions, disposals, depreciation, ending balance, tie it to the GL - and closed systems are what these tools are actually good at. So let me walk through where I'd draw the line between what you hand over and what you keep.

Who actually owns the fixed asset schedule?

It's spread wider than you'd think. In our data, 23.4% of senior accountant postings name fixed assets, along with 19.5% of staff accountant postings, 17.1% of assistant controller roles, 16.9% of controllers and 16.5% of accounting managers. In raw counts that's 1,044 staff accountant postings and 762 senior accountant postings asking for it.

So this isn't some specialist corner of the profession. Roughly one in five accountants at the doing-the-work level is expected to maintain a fixed asset register, and 85% of those same postings mention reconciliation work in the same breath. The schedule and the tie-out travel together, they always have.

What the roll-forward actually consists of

Strip it down and the monthly work is five things. You capture additions from AP and assign each one a class, a cost and an in-service date. You remove disposals and calculate the gain or loss. You run depreciation. You roll the register forward and prove the ending balance. Then you reconcile the subledger to the general ledger and explain whatever doesn't agree.

Four of those five are mechanical. The judgment lives almost entirely in step one, in the moment you decide whether an invoice becomes an asset or an expense and what life it gets. Everything downstream is your policy executing itself, which is a hell of a thing to be doing by hand every month for years on end.

Where AI genuinely earns its keep here

Start with intake. Hand it the month's capital invoices and it will pull description, vendor, cost, quantity and date, propose an asset class against your policy, and flag the ones that sit near your capitalization threshold for you to look at. That alone kills most of the typing.

Then the mechanical middle. It can generate the depreciation calculation for the period, produce the roll-forward, reconcile the subledger to the GL account and hand you a difference report that names the specific assets driving the variance rather than a number you have to go hunting for. It can cross-check your disposals against AP activity and asset tags to catch the machine that got sold in March and never came off the register - which, if you've ever inherited somebody else's fixed asset file, you know is the classic disaster.

It's also very good at building the support package before the auditors ask. Additions listing with invoice references, disposals with proceeds, depreciation tie-out, the whole thing assembled on a Tuesday instead of during fieldwork. We wrote about that pattern more broadly in our piece on handling PBC requests with AI, and fixed assets is the cleanest possible version of it.

Where you still have to make the call

Capitalize versus expense stays with you, and it should. The IRS tangible property regulations let you elect a de minimis safe harbor of up to $5,000 per invoice or item if you have an applicable financial statement, or $2,500 if you don't, and that election has to line up with a written policy you actually follow. A model can apply your threshold. It cannot decide what your threshold should be or whether a repair extended the asset's useful life.

Useful lives are the same story. Book life reflects how long you expect to use the thing, tax life comes out of the MACRS classes in IRS Publication 946, and those two diverge on purpose. Let AI maintain both schedules once you've set them. Don't let it pick them.

Impairment is firmly yours. ASC 360 asks you to evaluate whether events or changes in circumstances suggest a carrying amount isn't recoverable, and that assessment runs on things a model can't see - a plant going idle, a customer walking, a line of business you know internally is dying. And construction in progress transfers need a human who knows whether the asset is genuinely in service or whether somebody just wants the capex off the CIP account before quarter end.

The part that surprised me in our own data

Fixed asset postings ask for automation MORE than the market average. Of the 4,260 postings naming fixed assets, 1,017 flag automation as part of the role - about 24%, against roughly 18% across all active postings we track. Employers already know this schedule should be automated. They've known for years.

What they haven't done is connect it to AI. Only 275 of those 4,260 postings mention AI at all, around 6.5%, which is slightly BELOW the market average of 7.6%. So the appetite is there and the vocabulary hasn't caught up, and that gap is where you get to be useful. If you show up in an interview able to describe a fixed asset process you rebuilt with an AI assistant, you're answering a question the hiring manager has been circling for two years without quite naming it.

The counterweight, and I'd be lying if I skipped it: fixed asset data is often garbage before you start. Registers inherited across three ERP migrations, assets with no tags, lives that got keyed wrong in 2019 and compounded ever since. AI will happily roll forward a broken register with perfect precision. You have to clean the base year yourself, and that's a genuine multi-week project at most companies, not a weekend.

What I'd do

Pick one asset class. Not the whole register - something with maybe forty items and a clean history, like computer equipment or vehicles. Reconcile that class to the GL manually one last time so you know the base is right. Then wire up the monthly roll-forward for just that class with whatever AI tooling you already have access to, and run it in parallel with your spreadsheet for two months.

You'll find out fast where it breaks, and you'll almost certainly come away irritated at how many hours you've handed to arithmetic over the years. Then extend it to the next class. That's the entire method - the same one that makes rolling reconciliations work, applied to the schedule with the fewest excuses. If you're evaluating tooling rather than building it yourself, our accounting software directory covers the close and reconciliation categories where this lives.

Frequently asked questions

Can AI do a fixed asset roll-forward?

Most of it, yes. AI handles the mechanical work well - extracting asset details from invoices, calculating depreciation, generating the roll-forward, reconciling the subledger to the general ledger and flagging variances by asset. The capitalization decision, useful life determination and impairment assessment still need an accountant.

What should you not automate in fixed assets?

Three things. Whether an expenditure gets capitalized or expensed, what useful life an asset receives, and whether an impairment indicator exists under ASC 360. Each of those depends on facts about your business that don't live in the invoice.

Why do book and tax depreciation differ?

Book depreciation reflects the economic life you expect from the asset under GAAP. Tax depreciation follows the MACRS classes and conventions set out in IRS Publication 946, which are prescribed rather than estimated. Maintaining both schedules is standard, and it's exactly the kind of parallel bookkeeping AI handles without complaint.

How common is fixed asset work in accounting jobs?

Common. Across the active postings in our database, 4,260 name fixed assets, including 23.4% of senior accountant roles and 19.5% of staff accountant roles. If you're job hunting, it's worth having a concrete fixed asset story ready - you can see how often it appears in live listings on our remote accounting jobs board.

Does this overlap with lease accounting?

Quite a bit. Of the postings naming fixed assets, 1,638 also mention leases or ASC 842, since right-of-use assets end up on a similar schedule with similar mechanics. We covered that workflow separately in our post on AI and ASC 842 lease accounting.

Internal figures come from our database of accounting and finance job postings, refreshed daily. Counts reflect active postings as of August 2026.