Last reviewed: 10 October 2026. Product details reflect this review date. Availability and behavior can vary by account, role and release.
Editorial ink illustration: A colleague checks an equipment record against a physical asset.
A machine has been purchased and appears in the fixed-asset register. Its cost and useful life look correct. At month-end, however, the expected depreciation is absent from the ledger.
The asset’s existence is only one part of the evidence chain. The team also needs to verify the acquisition treatment, depreciation setup, processing result and posting status. A correct master record does not prove every later stage completed.
NetSuite Fixed Assets Management, or FAM, is a SuiteApp that supports asset acquisition, depreciation and other lifecycle activity. This lesson follows one asset through the process and explains where to investigate a difference. Capitalization, useful life, residual value and depreciation method remain accounting-policy decisions for qualified finance personnel.
Identify the acquisition evidence: the relevant invoice, receipt, approved journal or other source record used by the organization’s process. Record what was acquired, its cost, the owning entity and the dates needed for accounting treatment.
Then confirm whether the item meets the organization’s approved capitalization policy. The fact that something is expensive, physical or used for several years is not enough for a software tutorial to determine its accounting treatment.
Useful life and residual value also require an approved basis. Do not select a convenient life simply because it produces a round monthly charge. The asset’s business use, policy and applicable reporting requirements belong in the decision.
Keep the policy decision separate from the system setup that implements it. The reviewer should be able to explain both: why finance approved the treatment and which values the system uses to calculate it.
If the source is a supplier transaction, the purchasing and vendor bill lesson provides useful background on the accounting evidence behind the acquisition.
FAM is separately configured. Confirm that it is installed and set up for the intended account, and that the relevant asset types, accounts and methods have been reviewed.
The SuiteApp provides a Fixed Assets Management role that can serve as a reference when configuring appropriate access. Custom roles need the necessary permissions for the SuiteApp and its custom records. Showing the Fixed Assets tab alone does not prove that every required action is available.
Have the administrator review the permissions needed for the person’s responsibilities. A reviewer who inspects asset values does not automatically need the same authority as someone who changes methods or runs depreciation.
Where subsidiaries, multiple accounting books or alternate tax methods are used, identify the relevant scope before the exercise. A single asset can participate in more than one reporting context, and the treatment should not be assumed identical across them.
For training, use a permitted test environment and prepared data. Running depreciation can create accounting entries; it is not a harmless button to press repeatedly while exploring a screen.
FAM supports manual asset creation, CSV import and creation from supported transactions. Choose the route that matches the approved business process and the evidence already recorded.
For transaction-based creation, the source type and posting accounts matter. The SuiteApp can identify supported transactions posting to fixed-asset accounts. Asset Proposal and Asset Creation involve background processing, so a source transaction’s presence does not necessarily mean an asset record has already been created.
The documented processing-status route is Fixed Assets > Background Processing > Status. An authorized reviewer can use status evidence to distinguish a pending job from a failed or completed one before attempting another creation.
Avoid mixing routes without a reconciliation. If an asset was already created from a source, importing or manually adding it again can duplicate the register. Check the asset identifier and source relationship before creating a replacement for something that appears to be missing.
Also distinguish a reference from a calculation. Linking an existing asset to a transaction line for reference does not automatically mean that the system has recalculated or revalued that asset. Confirm the documented purpose of the linkage used by your process.
The asset record brings together information needed for the asset’s lifecycle. Review the cost, relevant dates, method, useful life or period settings, residual value and associated accounting context.
Check the asset type and any defaults it supplied. Defaults make entry easier, but they still need to fit the specific asset. A default chosen for one class of equipment may not be appropriate for another.
Confirm required classifications such as department, class or location where applicable. If the account makes these classifications mandatory and the asset lacks them, depreciation processing can fail to create the expected history and journals.
Establish the last recorded depreciation position as well. A newly acquired asset and a mid-life asset migrated from another system need different starting evidence. The latter already has accumulated history that must reconcile with the approved opening position.
A useful review worksheet lists each material value, its source and its approver. This is a practical control aid, not a claim that FAM has a built-in screen containing that exact worksheet.
Assume a fictional machine with a cost of 6,000, zero residual value and an approved straight-line life of 60 months. For this illustration, use one currency and assume the configured dates and conventions produce equal full-month charges without other adjustments.
The depreciable amount is 6,000 minus zero. Dividing 6,000 by 60 gives an illustrative charge of 100 per month.
This is arithmetic under stated assumptions. It is not a recommendation to use a five-year life for a real machine, and it is not a guarantee that the first FAM period will calculate 100. Actual start dates, partial periods, method settings, currency treatment, book or tax rules and existing history can change the result.
The reviewer first confirms that the approved test configuration implements the assumptions. They then inspect the calculated depreciation and compare it with the expected amount. If it differs, they identify which assumption is false before changing the asset.
Suppose the asset’s depreciation start date produces a partial first period. A different first charge may be consistent with the configured convention. Suppose instead the wrong method was assigned. That is a setup issue requiring the approved correction process. The same numerical difference can have different explanations.
Do not change the original cost or residual value simply to force a desired monthly amount. Those fields represent independent accounting facts and judgments.
A planned or calculated schedule helps explain expected depreciation. Periodic Asset Depreciation processing determines the eligible assets and creates the related accounting output.
The documented processing page is Fixed Assets > Transactions > Asset Depreciation. Its scope includes asset types, relevant subsidiaries and the date through which depreciation is to be processed. The selected cutoff matters: a run can include several periods since the last depreciation, rather than only a single month.
Before an authorized run, verify its scope and expected output. Afterward, review processing status and any exceptions. A submission acknowledgement is not proof that all assets completed successfully.
Then inspect depreciation history and the generated journals. Approval requirements depend on the journal configuration and account preferences. A journal waiting for required approval has not yet provided the final posting evidence.
There are also legitimate cases where a journal is absent. For zero depreciation, FAM can create a zero-value history record without a journal. Identify the expected result for the asset rather than treating every missing journal as the same failure.
For the selected period and scope, connect the depreciation result to the journal and ledger. Confirm the account, amount, posting period, subsidiary and book where relevant.
A journal date and an intended depreciation period are related but distinct facts to check. If period controls prevent the expected posting, investigate the applicable behavior and approval process. The lesson on locked and closed periods explains why changing access is not a universal solution.
Compare the asset register and accumulated depreciation with the relevant general-ledger balances using a consistent scope. Where journals summarize several assets, use the supporting detail rather than expecting every asset to have a unique standalone entry.
Preserve the result of the reconciliation and any remaining difference. A process-status message cannot replace an explanation of why the register and books agree.
FAM can import mid-life assets and their depreciation history. That supports continuity, but imported asset values are not automatically posted to fixed-asset general-ledger accounts.
The finance team must reconcile the imported register and history with the approved opening ledger position and arrange any required accounting entries. Do not create new entries blindly if the conversion balances have already been posted through another process.
For a migrated asset, record the cost, accumulated depreciation, remaining position and last processed period as of the agreed cutover date. Check that the next depreciation run starts from the intended position and does not repeat history already recognized.
The CSV import and validation guide covers a related data-handling discipline. Asset-specific import requirements still need their own review.
If an asset is missing, inspect source eligibility, proposal or creation status, and whether another route already created it. Do not assume the purchase must be entered again.
If depreciation differs, check cost, residual value, dates, method, useful life, prior history and processing cutoff. Resolve the actual cause before changing values.
If the asset record looks correct but the ledger does not, inspect processing completion, required classifications, journal creation, approval and actual posting scope.
If an asset is transferred, revalued or disposed of, use the approved lifecycle process. Deleting a record from the register is not a substitute for accounting for the business event.
For supporting change evidence, see NetSuite audit evidence for journal and master-data changes.
For help building a repeatable review around the asset lifecycle, explore CuriousRubik NetSuite training and adoption. Start with one asset and follow its evidence all the way to the posted result.