A NetSuite Fixed Assets Management implementation is ready when finance can explain the opening asset register, reproduce expected depreciation, and process an acquisition, movement, and retirement with complete accounting evidence. Installing the SuiteApp is one milestone. The decisive test is whether the first close produces an asset balance the controller can defend.
This checklist covers implementation acceptance for the Fixed Assets Management SuiteApp, usually called FAM. It does not prescribe capitalization thresholds, tax depreciation, lease accounting, or a company's accounting policies. The responsible accountant must approve those decisions. Detailed historical migration and disposal procedures should have their own work instructions rather than making the implementation checklist unreadable.
The FAM SuiteApp manages acquisitions, depreciation, revaluation, and retirement, with support for imported new and mid-life assets. Confirm the SuiteApp installation, commercial entitlement, available version, and required role access in the actual account. A menu visible to an administrator does not prove the asset accountant can complete the same process.
Create a scope sheet with one row per subsidiary and asset category. Record whether it needs accounting depreciation, alternate methods, multiple accounting books, project-related assets, or physical custody tracking. Mark each requirement as included, deferred, or awaiting a design decision. Keep third-party asset products on separate rows so their functionality is never presented as standard FAM behavior.
Ask the implementation owner to demonstrate the installed process using the operating role. Save the version, form, permissions, and enabled preferences with the test evidence. This makes later release testing much more precise than a general instruction to check fixed assets.
For each asset type, prepare an approved mapping containing the cost account, accumulated depreciation account, expense account, disposal accounts, useful-life convention, residual-value treatment, and depreciation method. Add who may override a default and what supporting evidence is required.
A useful design workshop follows a single purchase from the supplier invoice through capitalization and the first depreciation period. Ask which costs belong to the asset, when it becomes available for use, which department bears the charge, and how a correction would be approved. Resolve these questions before loading a large register.
FAM setup includes general ledger accounts, preferences, transfer accounts, depreciation methods, alternate methods, asset types, and migration. Use that sequence as a dependency map while retaining a named owner for each decision.
The purchase date, receipt date, commissioning evidence, and approved depreciation start date may differ. Preserve these facts rather than forcing them into one date column. For a machine awaiting installation, the invoice alone may not establish the correct start of depreciation under the company's policy.
The asset record has distinct purchase and depreciation start fields. Changing the depreciation end date through CSV import or a script does not recalculate asset lifetime in the same way as an interactive edit. That difference deserves an explicit migration test.
Build a date-review exception list for missing start dates, end dates earlier than start dates, unexpected remaining lives, and assets already fully depreciated. Explain each exception before the first production calculation; a mass replacement of dates can conceal a policy problem.
Asset creation needs a clear owner. Determine which purchases generate proposals, which records are entered directly, and which arrive through an import or integration. A single purchase should have one intended capitalization path.
Use a reconciliation that starts with transactions posted to asset-related accounts and traces them to the register. Then reverse the direction and trace register additions to source evidence. The first direction finds missing assets; the second can reveal duplicate or unsupported assets. Both are necessary because a matching net total can hide equal and opposite mistakes.
For construction or implementation projects, identify the holding accounts and the person who approves movement into the depreciating population. Do not leave an account excluded from asset creation without documenting how its balance is reviewed and cleared.
Select test assets for different failure modes, not merely the five largest purchases. Include a mid-life asset, a fully depreciated asset still in service, a new addition late in a period, an asset awaiting commissioning, and an asset with a department change. Add alternate depreciation and secondary-book cases only where the approved scope requires them.
For each case retain:
The test passes when the result agrees with the approved expectation or a documented accounting decision explains the difference. An import success message proves only that the file was accepted.
Assume a company approves straight-line depreciation for an equipment class, with a cost of 60,000 currency units, zero residual value, and a 60-month life. For this simplified full-month example, expected monthly depreciation is 1,000. The company has already recognized 18 months, so accumulated depreciation is 18,000 and net book value is 42,000 at cutover.
The acceptance pack should prove three separate amounts: 60,000 gross cost, 18,000 accumulated depreciation, and 1,000 for the next full month. Importing 42,000 as a fresh asset may reproduce the opening net balance while producing the wrong gross presentation and future expense.
A second test moves that asset to another department. The reviewer checks which department receives the next charge and whether any transfer journal is expected under the configured preferences. This is an illustrative arithmetic test, not a recommendation for a particular useful life or accounting treatment.
Prepare a fixed-asset rollforward by subsidiary, accounting book where relevant, asset type, and control account. Explain opening balances, additions, approved adjustments, depreciation, transfers, and disposals. Reconcile gross cost and accumulated depreciation separately before relying on net book value.
Record unfinished processing and errors alongside financial differences. The close owner needs to know whether the report reflects completed processing, a forecast, or a partial run. Keep an approved method for isolating failed records; repeatedly rerunning the entire population without understanding the first result increases uncertainty.
Release the implementation only after the asset accountant can complete a rehearsal without administrator intervention, the controller accepts the reconciliation, and the support owner has a recovery procedure. Set an owner and due date for every accepted limitation.
A practical handover allocates responsibility for additions, policy changes, transfers, depreciation processing, and report review. It also names the backup operator and explains where source evidence is retained. These responsibilities should survive staff changes.
For help translating this acceptance pack into account-specific configuration and testing, review CuriousRubik's NetSuite support services. Bring the asset-type map, an opening reconciliation, and representative exceptions to the discussion so the scope can be defined concretely.
Confirm the FAM SuiteApp, entitlement, installation, version, and role permissions for your account. Do not infer availability from a general NetSuite product description or assume a third-party asset application uses the same records.
Approve asset categories, capitalization policy, depreciation methods, useful-life conventions, residual values, account mappings, and exception authority. Technical consultants can configure approved decisions, but configuration does not establish the accounting policy.
No. Cost and accumulated depreciation can be wrong by the same amount. Reconcile both components, remaining life, and the next expected depreciation charge before accepting the migrated population.
Choose examples that exercise different behavior: mid-life, fully depreciated, newly commissioned, transferred, and disposed assets. Include tax methods and additional accounting books when they are in scope, with separate expected results.
Require a completed first-close rehearsal with reconciled balances, approved calculation differences, operating-role access, and named ownership. A successful installation or file import alone leaves important financial and operational questions unanswered.