What is NetSuite Fixed Assets Management (FAM)?

NetSuite Fixed Assets Management, often shortened to FAM, is the SuiteApp that manages fixed assets across their full lifecycle inside NetSuite. It creates and tracks asset records, runs scheduled depreciation, records revaluation and write-downs, and handles transfers and disposal. The purpose is to keep the fixed-asset subledger reconciled to the general ledger automatically, so depreciation is a system task rather than a spreadsheet maintained outside the books. Lightbridge ERP configures and optimizes FAM as part of its in-house NetSuite practice.

What depreciation methods does NetSuite FAM support?

Per Oracle NetSuite documentation, FAM ships several preconfigured depreciation methods, including Straight Line, Declining Balance, Sum of the Years Digits, and Asset Usage, and it supports user-defined methods created with a formula builder. The depreciation method is set on the asset type, so every asset in a category depreciates the same way, which keeps financial reporting consistent. With Multi-Book Accounting, an organization can run parallel book and tax depreciation on the same asset.

How does NetSuite create asset records?

Asset records can be entered directly or proposed and created automatically from source transactions such as purchase orders, vendor bills, and inventory transfers. FAM adds approval controls over asset creation and can merge multiple asset transactions into one record. Automating creation from the transactions that already exist in NetSuite reduces manual data entry, which is where most fixed-asset subledger errors begin. Each record carries the acquisition cost, in-service date, useful life, and depreciation method.

Why do imported mid-life assets often depreciate incorrectly?

When assets are imported into NetSuite partway through their life, usually by CSV during an implementation, the depreciation is only as accurate as the mid-life fields on the import. The common causes of an understated or overstated charge are a wrong current net book value, a wrong last depreciation date or period, misaligned depreciation start and end dates, a missing depreciation-active flag, or an import that ran without server scripts enabled so the history and schedule records were not built correctly. Getting these right on import is the difference between a subledger that reconciles and one that does not.

How do you correctly import mid-life assets into NetSuite FAM?

Prepare the import so the mid-life fields agree with each other: current net book value, last depreciation date, last depreciation period, and the depreciation start and end dates, with the asset flagged as actively depreciating. Run the import with server scripts enabled so the depreciation history and forward schedule are generated. Test in a sandbox before production, then review each asset depreciation schedule before running depreciation. Reconcile the imported register back to the prior fixed-asset records. A careful mid-life import is the single best guard against a subledger that will not tie out later.

Does NetSuite FAM handle revaluation, disposal, and lease accounting?

Yes. FAM records asset revaluations and write-downs and recalculates the remaining depreciation from the adjusted value forward, and it handles transfers and disposal by sale or write-off, stopping depreciation and posting the gain or loss. Per Oracle NetSuite documentation, the FAM SuiteApp also includes a lease accounting capability that helps organizations comply with the ASC 842 and IFRS 16 lease standards, letting an organization record leases and post lease and interest expense on the same platform as its owned assets.

How does Lightbridge ERP work with NetSuite FAM?

Lightbridge ERP is an independent, vendor-neutral ERP advisory firm and a former NetSuite partner, and NetSuite is its in-house delivery flagship. Its team configures and optimizes FAM directly: standardizing asset types and GL mapping, setting depreciation methods, and getting mid-life imports right so the subledger reconciles from day one. Because Lightbridge accepts no vendor kickbacks or reseller quotas, the advice is driven by fit rather than commission. This guide is general information, not accounting, tax, or legal advice.

JH Written by Jully Hayasaka with Robert LabardeeNetSuite Advanced Accounting Lead and Founder and CEO

Last updated July 2026.

NetSuite Fixed Asset Management (FAM): Depreciation and the Asset Lifecycle

Lightbridge ERP defines NetSuite Fixed Assets Management (FAM) as the SuiteApp that manages the full asset lifecycle inside NetSuite: creating asset records, running scheduled depreciation, and recording revaluation and disposal, so the fixed-asset subledger stays reconciled to the general ledger without a separate depreciation spreadsheet.

Talk to an ERP advisor NetSuite modules overview

This guide is general information, not accounting, tax, or legal advice. Lightbridge ERP is an independent, vendor-neutral advisor and a former NetSuite partner. Feature descriptions here follow public Oracle NetSuite documentation.

NetSuite FAM manages the fixed-asset lifecycle without a separate depreciation spreadsheet.

Fixed Assets Management is a SuiteApp that runs inside NetSuite. It holds the asset register, calculates and posts depreciation on a schedule, records revaluation and write-downs, and handles transfers and disposal. The point is a fixed-asset subledger that reconciles to the general ledger by design, so the periodic depreciation charge is a system output rather than a spreadsheet someone maintains alongside the books. For where FAM sits among the other financial modules, see the NetSuite modules overview, and for the platform as a whole, the what is NetSuite guide.

Depreciation itself is an accounting concept, not a NetSuite invention: it spreads the cost of a long-lived asset across the periods that benefit from it. FAM is the mechanism that carries that concept through the ledger accurately and repeatedly. The feature descriptions on this page follow public Oracle NetSuite documentation; Lightbridge ERP configures and optimizes the module in-house as part of its NetSuite practice.

NetSuite FAM covers the asset from creation to disposal.

A fixed asset moves through a predictable lifecycle: it is created, it depreciates over its useful life, it may be revalued or transferred, and eventually it is disposed of. FAM handles each stage on one platform. These are the building blocks a well-run FAM configuration is built from.

Asset creation and proposal

An asset record carries the acquisition cost, in-service date, useful life, and depreciation method. NetSuite FAM can propose or create asset records automatically from source transactions such as purchase orders, vendor bills, and inventory transfers, with approval and merge controls, which reduces the manual entry that seeds most subledger errors.

Depreciation methods

Per Oracle NetSuite documentation, FAM ships preconfigured methods including Straight Line, Declining Balance, Sum of the Years Digits, and Asset Usage, plus user-defined methods built with the formula builder. Method is set by asset type, so a category depreciates consistently across every asset assigned to it.

Depreciation schedules and runs

Each asset carries a depreciation schedule that lays out the periodic charge across its life. Depreciation is posted through periodic runs aligned to the financial calendar. Running it on a consistent cadence keeps the subledger and the general ledger in step and removes the month-end scramble of a manual calculation.

Asset types and GL mapping

Asset types group similar assets and define the general ledger accounts they post to. Setting the accounts at the type level rather than per asset keeps posting consistent and makes new-asset creation faster and less error-prone. It is the single most useful piece of standardization in a FAM setup.

Revaluation and write-down

FAM records asset revaluations and write-downs and recalculates the remaining depreciation from the adjusted carrying value forward. This keeps the net book value and future charges consistent after a value change, rather than leaving the schedule stale against a number the balance sheet no longer reflects.

Transfers and disposal

Assets move between locations and subsidiaries, and they leave the books through sale or write-off. Recording transfers and disposals in FAM stops depreciation at the right point, posts the gain or loss, and keeps the asset register a faithful mirror of what the organization actually holds.

Mid-life asset imports are the most common cause of wrong depreciation.

Most fixed-asset subledger problems in a new NetSuite implementation trace back to one event: importing assets that are already partway through their life. Before go-live, those assets were depreciated manually or in another system. On import, usually by CSV, NetSuite has to be told exactly where each asset sits in its life so it can post the right charge from the next period forward. When the mid-life fields are wrong, or the import runs without the background scripts that build the schedule, depreciation comes out understated or overstated, and the register fails to reconcile.

A simple illustration makes the risk concrete. These figures are illustrative only, not a real engagement. Consider an asset with a useful life of several years that was placed in service two years before go-live and has already been depreciated straight-line during that time. Its remaining value has to be spread over the periods that are left, not the full life. If the import records the full original cost as the base and misses the two years already taken, NetSuite schedules too much depreciation across too many periods, and every future charge is wrong. The fields below are where that goes right or wrong.

Current net book value

The imported net book value is original cost less accumulated depreciation and any write-downs to date. If it is wrong on import, every future period is calculated from a wrong base, so the charge is understated or overstated from the first run onward.

Last depreciation date and period

These tell NetSuite where the asset already sits in its life. The last depreciation date is the most recent charge posted before go-live; the last depreciation period is its position within the asset lifetime. Get either wrong and the schedule left to run is misaligned with reality.

Depreciation start and end dates

The start and end dates bound the full schedule. When they do not agree with the useful life and the in-service date, NetSuite spreads the remaining value across the wrong number of periods, distorting each periodic charge.

Depreciation active flag

An imported mid-life asset has to be flagged as actively depreciating for the system to schedule future charges. A missed flag leaves a live asset sitting dormant with no schedule at all, which surfaces only when the register fails to reconcile.

Server scripts during import

The FAM subledger relies on background scripts that build depreciation history and the forward schedule. If the CSV import runs without server scripts enabled, the history and schedule records are not generated correctly, and the numbers look wrong even when every field value was right.

The disciplined path is to prepare the import so these fields agree with each other, run it with server scripts enabled, test in a sandbox before production, review each asset depreciation schedule before the first live run, and reconcile the imported register back to the prior records. Because Lightbridge ERP is staffed by senior finance professionals (CPAs, controllers, and former CFOs), the import is built around how the fixed-asset subledger actually has to tie out.

A well-run NetSuite FAM setup follows a handful of durable practices.

The difference between a FAM configuration that runs itself and one that generates month-end firefighting is standardization done up front. Record complete asset data on every record: acquisition cost, in-service date, useful life, and maintenance detail. Define clear asset types and set the depreciation method and GL accounts at the type level, so every asset in a category posts and depreciates consistently. Automate asset creation from the source transactions rather than keying records by hand.

Then run the mechanics on a rhythm. Post depreciation on a consistent cadence aligned to the financial calendar, record transfers and disposals as they happen, and run the FAM reports regularly to reconcile the subledger. For organizations with leased assets, FAM includes a lease accounting capability that supports ASC 842 and IFRS 16, so owned and leased assets live on one platform. Lightbridge ERP operates to ISO 27001 and SOC 2 controls, with certification in progress, and configures FAM in-house as part of its NetSuite practice.

NetSuite Fixed Assets Management: frequently asked questions

What is NetSuite Fixed Assets Management (FAM)?: NetSuite Fixed Assets Management, often shortened to FAM, is the SuiteApp that manages fixed assets across their full lifecycle inside NetSuite. It creates and tracks asset records, runs scheduled depreciation, records revaluation and write-downs, and handles transfers and disposal. The purpose is to keep the fixed-asset subledger reconciled to the general ledger automatically, so depreciation is a system task rather than a spreadsheet maintained outside the books. Lightbridge ERP configures and optimizes FAM as part of its in-house NetSuite practice.
What depreciation methods does NetSuite FAM support?: Per Oracle NetSuite documentation, FAM ships several preconfigured depreciation methods, including Straight Line, Declining Balance, Sum of the Years Digits, and Asset Usage, and it supports user-defined methods created with a formula builder. The depreciation method is set on the asset type, so every asset in a category depreciates the same way, which keeps financial reporting consistent. With Multi-Book Accounting, an organization can run parallel book and tax depreciation on the same asset.
How does NetSuite create asset records?: Asset records can be entered directly or proposed and created automatically from source transactions such as purchase orders, vendor bills, and inventory transfers. FAM adds approval controls over asset creation and can merge multiple asset transactions into one record. Automating creation from the transactions that already exist in NetSuite reduces manual data entry, which is where most fixed-asset subledger errors begin. Each record carries the acquisition cost, in-service date, useful life, and depreciation method.
Why do imported mid-life assets often depreciate incorrectly?: When assets are imported into NetSuite partway through their life, usually by CSV during an implementation, the depreciation is only as accurate as the mid-life fields on the import. The common causes of an understated or overstated charge are a wrong current net book value, a wrong last depreciation date or period, misaligned depreciation start and end dates, a missing depreciation-active flag, or an import that ran without server scripts enabled so the history and schedule records were not built correctly. Getting these right on import is the difference between a subledger that reconciles and one that does not.
How do you correctly import mid-life assets into NetSuite FAM?: Prepare the import so the mid-life fields agree with each other: current net book value, last depreciation date, last depreciation period, and the depreciation start and end dates, with the asset flagged as actively depreciating. Run the import with server scripts enabled so the depreciation history and forward schedule are generated. Test in a sandbox before production, then review each asset depreciation schedule before running depreciation. Reconcile the imported register back to the prior fixed-asset records. A careful mid-life import is the single best guard against a subledger that will not tie out later.
Does NetSuite FAM handle revaluation, disposal, and lease accounting?: Yes. FAM records asset revaluations and write-downs and recalculates the remaining depreciation from the adjusted value forward, and it handles transfers and disposal by sale or write-off, stopping depreciation and posting the gain or loss. Per Oracle NetSuite documentation, the FAM SuiteApp also includes a lease accounting capability that helps organizations comply with the ASC 842 and IFRS 16 lease standards, letting an organization record leases and post lease and interest expense on the same platform as its owned assets.
How does Lightbridge ERP work with NetSuite FAM?: Lightbridge ERP is an independent, vendor-neutral ERP advisory firm and a former NetSuite partner, and NetSuite is its in-house delivery flagship. Its team configures and optimizes FAM directly: standardizing asset types and GL mapping, setting depreciation methods, and getting mid-life imports right so the subledger reconciles from day one. Because Lightbridge accepts no vendor kickbacks or reseller quotas, the advice is driven by fit rather than commission. This guide is general information, not accounting, tax, or legal advice.

Make the fixed-asset subledger reconcile from day one.

Lightbridge ERP configures and optimizes NetSuite FAM in-house: standardized asset types, correct depreciation methods, and mid-life imports that tie out. Independent, vendor-neutral, senior finance talent.

Talk to an ERP advisor What is NetSuite