Fixed-asset master data capture: which data items for a newly purchased asset could a well-designed application obtain automatically from existing sources and policies?

Introduction / Context:
Modern fixed-asset systems integrate with purchasing, accounts payable, and policy tables. When an asset is capitalized, the application can prefill many fields to reduce manual entry and enforce consistency. The question asks which of the listed items can be captured automatically by a well-designed application.

Given Data / Assumptions:

• Purchasing and AP modules provide structured data such as vendor, PO, invoice amount, and in-service date.
• Policy tables store standard useful lives, depreciation methods, and salvage rate assumptions by asset class.
• “Estimated disposal data” means predicted end-of-life parameters derived from policy, not an actual future sale date.

Concept / Approach:
First cost is read from the approved invoice or purchase order. Source information (vendor/PO) is directly linked in integrated ERP systems. Estimated disposal data (such as useful life and salvage assumptions) is determined automatically from the asset class and corporate policy. Because all three can be system-derived, the comprehensive choice is correct.

Step-by-Step Solution:

Verification / Alternative check:
ERP fixed-asset modules routinely use policy defaults and purchase integrations to minimize manual entry and ensure compliance.

Why Other Options Are Wrong:
Choosing a single item underestimates the capability of integrated systems; “None” contradicts standard ERP practice.

Common Pitfalls:
Confusing “estimated disposal data” with a literal known sale date; here it refers to policy-based end-of-life assumptions.

Final Answer:
All of the above