limitedDistribution · Industry Research
Fixed-Asset Capitalization and Depreciation Require an Evidence Workflow
At period close, the controller may find an invoice in the general ledger, an asset description in a purchase order, an acceptance date in an
Fixed-Asset Capitalization and Depreciation Require an Evidence Workflow
At period close, the controller may find an invoice in the general ledger, an asset description in a purchase order, an acceptance date in an email, and a capitalization decision waiting in someone’s inbox. Depreciation software can calculate a schedule, but only after finance establishes what the asset is, when it entered service, its basis, and which policy applies. The central problem in fixed-asset capitalization and depreciation is therefore not arithmetic. It is assembling decision-ready evidence before posting—and retaining that evidence after approval.
For property depreciated under MACRS, the IRS identifies seven core inputs: depreciation system, property class, placed-in-service date, basis, recovery period, convention, and method. The General Depreciation System alone contains nine property classifications. These requirements concern federal tax depreciation rather than book depreciation, but they illustrate why an incomplete asset record cannot safely become an automated schedule. See IRS Publication 946, How To Depreciate Property.
Where fixed-asset capitalization and depreciation breaks
The general ledger supplies structured transaction data, while invoices, purchase orders, receiving documents, contracts, and project records provide semi-structured evidence. Unstructured email or approval comments may explain whether costs belong to one asset, several components, or an expense. This is a mixed-data problem because structured transactions must be reconciled with documentary evidence and exception context before capitalization is safe to execute. When identifiers differ, dates conflict, or approval history is detached from the record, these failures can delay recognition or lead to posting based on incomplete assumptions.
The risk becomes more pronounced when information crosses organizational boundaries. In a 2025 review, GAO found errors in 116 of 270 sampled contractor-managed asset records and identified 917 assets worth approximately $109 million that had not been timely delivered or entered into the accountable property system. GAO described the sample as nongeneralizable, so the result is not an industry error rate. It is direct evidence that unclear responsibility, inaccurate attributes, and delayed handoffs can leave assets outside the system of record. See GAO’s review of contractor-acquired property.
The fixed-asset control point is not the depreciation calculation; it is the moment fragmented evidence becomes an approved accounting decision.
Build a governed path from evidence to posting
A target workflow should reduce manual assembly without allowing uncertain classifications to pass silently:
- Capture the evidence. Ingest transaction data and supporting documents; associate them using purchase order, project, vendor, location, and asset identifiers.
- Validate and reconcile. Confirm required fields, normalize descriptions, detect duplicate costs, and compare invoice, receipt, project-completion, and placed-in-service dates.
- Apply policy and route exceptions. Map complete records to approved capitalization thresholds, asset classes, useful lives, and book or tax treatments. Route missing fields, conflicting evidence, or unsupported policy deviations for review.
- Approve and deliver. Preserve the decision, reviewer, rationale, and supporting evidence before sending a system-ready asset record and depreciation attributes to the fixed-asset subledger or ERP.
Automation should stop when conflicting evidence could change asset classification, basis, useful life, or placed-in-service date beyond the organization’s approval threshold. The controller or delegated accounting owner should receive the conflicting source values, underlying documents, proposed treatment, and applicable policy; the permitted actions should be approve, return for evidence, or reject—not post by default.
Calculation automation also requires independent validation. GAO identified a deficiency in the IRS’s monitoring of automated depreciation calculations and recommended periodic recalculation and reconciliation for selected assets. GAO also concluded that the identified deficiencies did not individually or collectively constitute a significant deficiency in internal control over financial reporting as of September 30, 2024. The lesson is appropriately narrow: automated calculations still need testable controls. See GAO’s IRS financial-reporting controls review.
StarDox Intelligence can serve as the enterprise automation and decision-intelligence layer across this workflow. It can standardize and orchestrate fixed-asset capitalization and depreciation across counterparties and core systems, with automated validation, decisions, and exception handling. It does not replace accounting policy or the controller’s judgment; it supports a consistent evidence workflow, decision path, and output.
Three actions for the controller
The immediate objective is to measure where evidence becomes disconnected from decisions—not to begin with a software selection.
- Map source authority for asset description, ownership, basis, placed-in-service date, class, useful life, and approval rationale.
- Baseline first-time-right processing by tracking records returned for missing evidence, conflicting fields, or incorrect system mapping.
- Define the automation boundary by documenting which conflicts, value thresholds, and policy deviations require controller approval.
A focused next step is a 30-day workflow assessment covering one asset class from invoice capture through subledger posting.
Sources
See ROI in 12 weeks
Stargo users see measurable return and operational profitability gains in just 12 weeks, with non-disruptive implementation in 4 weeks or less.