Irvine Analytics Get in touch
Analytics Catalog/Workday/Financials/Assets and expenses/Depreciation run
Explore the catalogModulesAssets and expensesThe registerTrial balance
Workday · Financials · Report

The monthly charge, computed in the open

Depreciation should be boring. May divides 10,890,000.00 of basis by four stated lives, charges 187,500.00, and posts it to both ledger rows. Every cell above is one division, and the run can prove it.

RulePost depreciation from a run that shows its arithmetic: basis over life per class, straight line, additions joining the month after they go into service.
Neveraccept a charge the run cannot rebuild. A number that will not divide back into cost and life is an adjustment wearing a journal’s clothes.
Basis 10,890,000.00 what was depreciating in May Cost over life straight line, exact 187,500.00 posted the ledger’s own row
Depreciation is the plainest number in the close. When the run divides in the open, the ledger row needs no defending.
◆ The May runfour divisions, one posted charge.
ClassBasis in the runLife, monthsMay charge
Computers2,700,000.003675,000.00
Office equipment1,440,000.006024,000.00
Leasehold improvements5,040,000.008460,000.00
Vehicles1,710,000.006028,500.00
May run10,890,000.00187,500.00

The basis is the roll-forward’s opening cost, because May’s additions start charging in June. The 187,500.00 lands as the trial balance’s depreciation debit and its accumulated depreciation credit, one figure on both sides. Sample values are illustrative, never client data.

◆ Where runs go wrongat the edges, invisibly.

Runs fail at the edges: an asset past its life still charging, an addition charging from the wrong month, a life shortened without a catch-up. Each is visible the month it happens when the run is a table you can subtract from last month’s, and invisible for years when it is not.

◆ The owned answerthe charge recomputes from stored months.

The monthly asset rows on the module star keep basis, life, and charge per asset. The run recomputes from storage, so a wrong charge is a row someone can name instead of a variance someone can only smell.

Use case
Problem
Depreciation posts as one opaque number, nobody can say which assets produced it, and a life change or a late addition surfaces as an audit adjustment a year later.
What we build
The run as landed rows: basis over life per asset, straight line shown in the open, the posted charge recomputed from storage every night.
What you get
A depreciation number that defends itself: every charge divisible back to an asset, edge cases caught in their month, and a clean tie to the ledger’s two rows.
Can your depreciation number rebuild itself?
We build the run that recomputes from stored asset months.
Talk to us
Terms on this page
straight line
The same charge every month: cost divided by life.
basis
The cost actually depreciating this month.
in service
When use begins; charging starts the month after, here.
catch-up
The correction posted when a life changes mid-stream.