NetSuite Fixed Assets Management: Depreciation, Disposal, and the Fixed Assets Module

For any organisation carrying property, plant, and equipment on its balance sheet, the accuracy of asset records directly determines the reliability of financial statements. NetSuite fixed assets management gives finance teams a structured, auditable way to track every asset from the moment it is capitalised through every depreciation run until final disposal. This article walks through the full lifecycle, configuration, depreciation methods, disposal mechanics, mid-year adjustments, and the reporting suite, so you can get the most out of the module and close your books with confidence.

Fixed assets sit at the intersection of accounting, tax, and operations. Errors here ripple into net income, tax filings, insurance schedules, and board-level capital reporting. Getting the setup right from the beginning saves months of remediation later. As part of broader NetSuite financial management, the Fixed Assets module connects directly to the general ledger and integrates with purchasing, so that asset records stay in sync with actual spend rather than living in a separate spreadsheet.

What Is the NetSuite Fixed Assets Module?

NetSuite’s Fixed Assets Management (FAM) module is a purpose-built add-on that extends the core ERP to handle the full asset lifecycle. Unlike basic GL tracking, it maintains individual asset records with their own depreciation schedules, book values, and transaction histories. Every depreciation run, revaluation, and disposal posts directly to the general ledger through journal entries that are fully traceable.

The module is distinct from simply recording an asset purchase against a fixed asset GL account. Without FAM, companies often track depreciation in spreadsheets and import journal entries manually, a process prone to formula errors, version conflicts, and audit gaps. FAM replaces that with a single source of truth inside NetSuite.

When Should You Enable It?

FAM makes sense when any of the following conditions apply:

• You carry more than a handful of capitalised assets and need individual-level tracking rather than pooled balances.
• Your tax jurisdiction requires specific depreciation methods, MACRS in the US, declining balance variants in other regions, that differ from your book depreciation.
• You need to maintain multiple depreciation books simultaneously (for example, GAAP, tax, and an internal management book).
• Auditors require a detailed asset register with acquisition cost, accumulated depreciation, and net book value per asset.
• You have assets subject to revaluation under IFRS or local GAAP.

If you are managing fewer than ten assets with identical depreciation profiles, a manual GL approach may be sufficient. For most growing businesses, however, FAM pays for itself quickly in time saved at period close and audit-readiness maintained throughout the year.

Setting Up the Fixed Assets Module: Asset Types, Books, and Numbering

Solid configuration at the outset eliminates most recurring problems. The three foundational elements are asset types, depreciation books, and asset numbering conventions.

Asset Types

Asset types group assets that share the same accounting treatment. Each type defines the default GL accounts for cost, accumulated depreciation, and depreciation expense, along with the default depreciation method and useful life. Creating a well-considered hierarchy of asset types, Computers, Vehicles, Leasehold Improvements, Manufacturing Equipment, Furniture, means that when a new asset is created, the right defaults populate automatically and the chance of misclassification drops significantly.

Think carefully before creating too many types. A type for “Laptop, 3 year” and another for “Laptop, 4 year” creates unnecessary complexity. Instead, use one type for computers and override useful life at the individual asset level where needed.

Depreciation Books

A depreciation book is a complete set of depreciation parameters applied to an asset. Most companies need at least two books: one for financial reporting (book depreciation) and one for tax purposes (tax depreciation). Under NetSuite FAM, you can maintain as many books as required. Each book calculates independently, so the same asset can carry a different net book value in each book without any manual reconciliation.

When configuring a book, you specify:

• The depreciation method (straight-line, declining balance, MACRS, units of production, and others).
• Whether the book posts to the GL or is a memo-only book for reporting.
• The fiscal calendar the book follows.
• How the module handles partial periods in the first and last year of an asset’s life.

Separating book and tax depreciation into distinct books gives you the clean data needed for deferred tax calculations at year-end, without any manual bridging.

Asset Numbering

NetSuite can generate asset numbers automatically using a configurable prefix and sequence. Standardising this from day one avoids the classic problem of assets numbered by different people in incompatible formats. A sensible convention might prefix by asset class, VEH-0001 for vehicles, IT-0001 for computers, so that the asset register is immediately readable without filtering.

Linking Asset Creation to Procurement

One of the most powerful aspects of FAM is its integration with the purchase order and vendor bill workflow. When a vendor bill includes a line item coded to a fixed asset GL account, NetSuite can automatically generate a draft asset record populated with the vendor, acquisition date, and cost. This tightens the link between NetSuite Accounts Payable and the asset register, reducing the risk of assets being expensed rather than capitalised or capitalised without a corresponding asset record.

NetSuite Fixed Asset Depreciation Methods Explained

Choosing the right depreciation method is not purely a technical configuration decision, it affects reported earnings, tax liability, and balance sheet ratios. NetSuite supports the full range of methods used across major jurisdictions.

Straight-Line (SL)

Straight-line depreciation allocates an equal amount of cost to each accounting period over the asset’s useful life. It is the default for most GAAP and IFRS financial reporting books because of its simplicity and predictability.

Annual depreciation = (Cost – Residual Value) / Useful Life in Years

In NetSuite, you configure the useful life in months and the residual (salvage) value on the asset record. The module calculates the periodic charge and posts it on each depreciation run date.

Declining Balance (DB) and Double Declining Balance (DDB)

Declining balance methods apply a fixed percentage to the remaining net book value each period, front-loading depreciation into the earlier years of an asset’s life. Double declining balance uses twice the straight-line rate.

These methods are common for assets that lose economic value quickly, vehicles, certain technology equipment, and in tax books where accelerated deductions are permitted.

NetSuite supports both DB and DDB, and allows you to configure an automatic switch to straight-line in the year when straight-line would produce a higher charge than the declining balance calculation, preventing the asset from never fully depreciating.

MACRS (Modified Accelerated Cost Recovery System)

MACRS is the US federal tax depreciation system mandated for most tangible property placed in service after 1986. It combines declining balance and straight-line, with IRS-defined recovery periods (3, 5, 7, 10, 15, 20, 27.5, and 39 years depending on asset class) and a half-year convention for most property.

NetSuite’s FAM module includes pre-built MACRS tables for both the General Depreciation System (GDS) and Alternative Depreciation System (ADS). You select the recovery period and convention when setting up the tax book, and the module applies the correct IRS percentage table automatically. This eliminates the need to maintain MACRS tables externally and manually verify annual percentages. The underlying percentages are published in IRS Publication 946, which is the definitive reference for recovery periods and conventions.

Sum of the Years’ Digits (SYD)

SYD is another accelerated method that allocates depreciation based on a fraction whose numerator is the remaining useful life and whose denominator is the sum of all years’ digits. It produces a more moderate front-loading than double declining balance. NetSuite supports SYD natively.

Units of Production (UOP)

Units of production ties depreciation to actual usage rather than time. You define the total estimated production capacity, machine hours, kilometres driven, units manufactured, and NetSuite calculates the depreciation charge for each period based on actual usage entered for that period.

UOP is appropriate for manufacturing equipment and vehicles where wear correlates with use rather than elapsed time. The configuration requires you to record actual usage figures each period before running depreciation, which adds a data entry step but produces depreciation that genuinely matches economic consumption.

Depreciation Method Comparison

Running Depreciation: Manual Schedules, Automation, and Period-Close

Once assets and books are configured, the monthly depreciation run is the core recurring process in FAM. NetSuite gives you both manual and automated options, and the right choice depends on the size of your asset register and your preference for control versus efficiency.

Manual Depreciation Run

For smaller organisations or those that want explicit approval before posting, the manual process works as follows:

1. Navigate to Fixed Assets > Depreciation > Propose Depreciation.
2. Select the period and depreciation book(s) to include.
3. Review the proposed journal entries, asset by asset if required.
4. Approve and post. NetSuite generates a single consolidated journal entry (or asset-level entries, depending on your configuration) that debits depreciation expense and credits accumulated depreciation.

The proposal step is valuable because it lets you catch anomalies, assets with zero book value that still appear on the schedule, assets approaching end of life, or newly added assets with incomplete setup, before anything posts to the GL.

Automated Depreciation Schedules

For larger asset registers, manual review of every asset each month is impractical. NetSuite supports scheduled depreciation runs that execute automatically on a defined date. The system posts journal entries without manual intervention, and exceptions, assets flagged with errors or requiring review, are surfaced in a report for follow-up.

Automation works well when your asset types and depreciation books are configured consistently and you have a downstream review process (such as a GL account analysis) that would catch any anomalies in the posted entries.

Period-Close Integration

Depreciation is almost always one of the first steps in a period-close checklist. The journal entries it generates feed directly into income statement accounts (depreciation expense) and balance sheet accounts (accumulated depreciation). Until depreciation is posted, any interim financial statements are incomplete.

NetSuite’s period locking controls ensure that once depreciation is posted and the period is closed, no further changes can alter the posted amounts without a formal reopening. This creates the audit trail that controllers and auditors rely on. After depreciation posts, reconciling the accumulated depreciation accounts against the asset register is a key step alongside NetSuite bank reconciliation and other balance sheet tie-outs in the month-end workflow.

Handling Late Additions and Catch-Up Depreciation

If an asset is added to the system after its actual in-service date, common when procurement and accounting are not perfectly synchronised, NetSuite can calculate catch-up depreciation for the missed periods. The module looks at the asset’s in-service date, compares it to the current period, and posts the accumulated backlog in the next depreciation run. You can control whether this posts as a single catch-up entry or is spread across the intervening periods through a prior-period adjustment.

Asset Disposal in NetSuite: Write-Offs, Sales, and Partial Disposals

Disposal is where many manual fixed asset processes break down. Removing an asset from the books requires reversing the cost and accumulated depreciation, recognising any gain or loss on disposal, and, if the asset was sold, recording the cash proceeds. NetSuite FAM handles all of this through its disposal workflow, which generates the required journal entries automatically.

Full Write-Off (Retirement)

When an asset reaches end of life and is scrapped with no proceeds, the disposal posts:

• Debit: Accumulated Depreciation (to clear the balance).
• Debit: Loss on Disposal (for any remaining net book value).
• Credit: Fixed Asset Cost account (to remove the gross cost).

In NetSuite, you navigate to the asset record, select Dispose, choose the disposal type (retirement/write-off), enter the disposal date, and the system generates the journal entry. The asset status changes to Disposed and it drops off the active asset register but remains in the historical record.

Sale of an Asset

When an asset is sold, you enter the proceeds alongside the disposal. NetSuite calculates the gain or loss:

Gain / (Loss) = Sale Proceeds – Net Book Value at Disposal Date

The journal entry credits the proceeds to a disposal clearing or cash account, removes the cost and accumulated depreciation, and posts the difference to a gain or loss account. The accounts used for gain and loss on disposal are configurable by asset type, so you can route manufacturing equipment disposals to a different P&L line than IT disposals if your reporting requires it.

Partial Disposal

Partial disposal applies when you dispose of a component of an asset rather than the whole asset. This is particularly relevant under component accounting required by IAS 16 for assets with significant parts that have different useful lives. You specify the proportion of the original cost being disposed of, and NetSuite calculates the proportional accumulated depreciation and net book value, posting only the relevant portion while leaving the remainder of the asset record intact and continuing to depreciate.

Disposal Reporting

After disposal, the asset is flagged in the register with its disposal date, method, and any gain or loss. The Disposal Report within FAM gives a complete list of disposed assets for any date range, which supports both audit requests and management reporting on capital recycling.

Mid-Year Additions, Bonus Depreciation, and Revaluation

Mid-Year and Mid-Quarter Conventions

For assets placed in service partway through a period, the first-year depreciation charge depends on the convention applied. NetSuite supports the following:

• Half-year convention: The asset receives half a year’s depreciation in the year of acquisition regardless of the actual in-service month. This is the MACRS default for most personal property.
• Mid-quarter convention: Required under MACRS when more than 40% of all personal property acquisitions occur in the final quarter of the tax year. The asset is treated as placed in service at the midpoint of the quarter it was acquired.
• Actual days: Depreciation calculated from the precise in-service date, common in financial reporting books.

You configure the convention at the depreciation book level, so your GAAP book and tax book can use different conventions simultaneously without any manual override.

Bonus Depreciation and Section 179

US tax filers using bonus depreciation (currently under the phase-down schedule introduced by the Tax Cuts and Jobs Act) or Section 179 expensing can handle these within the tax depreciation book. Bonus depreciation allows an immediate deduction of a percentage of the asset’s cost in the year of acquisition, with the remainder depreciated under MACRS.

In NetSuite, you can configure a bonus depreciation amount or percentage at the asset level when creating the tax book entry. The module applies the bonus deduction in the first period and then depreciates the remaining basis over the standard MACRS recovery period. This gives you an accurate tax basis and the correct depreciation schedule for subsequent years without manual adjustments.

Revaluation Under IFRS

Companies reporting under IFRS have the option (under IAS 16: Property, Plant and Equipment) to carry certain asset classes at revalued amounts rather than historical cost. NetSuite FAM supports revaluation through an upward or downward adjustment to the asset’s carrying amount. Upward revaluations credit a revaluation reserve in equity (other comprehensive income); downward revaluations that reverse previous upward movements reduce the reserve, while any excess charges to the income statement.

After a revaluation, the module recalculates the future depreciation schedule based on the new carrying amount and remaining useful life. This is particularly important for property portfolios and infrastructure assets where market values diverge significantly from historical cost over time.

Fixed Asset Reporting in NetSuite

The reporting suite within FAM gives finance teams the visibility they need for financial close, audit support, and management review.

Asset Register

The Asset Register is the master list of all assets: asset number, description, asset type, in-service date, acquisition cost, accumulated depreciation, and net book value as of a selected date. It can be filtered by subsidiary, department, location, or asset type. For multi-entity organisations, subsidiary-level registers give each entity its own view while the consolidated register aggregates across the group.

The register is a key deliverable for annual audits, auditors typically request it as part of their fixed asset substantive testing to agree the total cost and accumulated depreciation to the GL trial balance.

Depreciation Schedule

The Depreciation Schedule report shows, for each asset, the depreciation charge posted in each period of a selected date range. It lets you verify that no periods were skipped, that assets acquired mid-year received the correct partial-period charge, and that fully depreciated assets show zero charge. The report is filterable by depreciation book, so you can view your GAAP schedule and tax schedule independently.

Net Book Value Report

The Net Book Value (NBV) report provides a point-in-time snapshot of each asset’s carrying amount. As a balance sheet reconciliation tool, it should agree to the net fixed asset balance on the trial balance after removing land and any assets not managed through FAM. Any difference between the FAM NBV total and the GL balance is a reconciling item requiring investigation.

Gain/Loss on Disposal Report

This report lists all disposals in a period with the gross cost removed, accumulated depreciation cleared, proceeds received, and the resulting gain or loss. It feeds directly into the income statement analysis and supports the disclosure requirements in financial statement notes relating to property, plant, and equipment movements.

Audit Trail

Every action in FAM, asset creation, depreciation posting, revaluation, disposal, is timestamped and attributed to a user. NetSuite’s system notes and GL audit trail mean that for any asset, you can reconstruct the complete history of changes. This satisfies both internal control requirements and external audit requests for evidence of completeness and accuracy.

Custom Saved Searches for Fixed Assets

Beyond the standard reports, NetSuite’s saved search functionality lets you build custom asset analyses. Common examples include:

• Assets fully depreciated but still in service (to flag candidates for write-off or useful life extension).
• Assets acquired in the current year, sorted by cost, for capital expenditure tracking against budget.
• Assets by location or department for insurance schedule preparation.
• Assets with residual values above a threshold for management review.

Saved searches can be scheduled to email results to specific users, turning ad hoc analysis into a systematic monitoring process.

Common Pitfalls and How to Avoid Them

Even with a well-configured FAM module, certain issues recur across organisations. Being aware of them in advance saves remediation time.

Assets Expensed Rather Than Capitalised

When a purchase order or vendor bill is coded to an expense account rather than a fixed asset account, no asset record is created and the cost flows directly to the income statement. The fix requires a journal entry to reclassify the cost, followed by manual asset creation with the correct in-service date. Prevention is better: configure approval rules in your procurement workflow that flag items above your capitalisation threshold for accounting review before the bill is posted.

Depreciation Runs Missed During System Migration

When companies migrate from a legacy system to NetSuite, they often import assets with their accumulated depreciation as of the migration date but fail to configure the in-service dates correctly. This causes the module to recalculate depreciation from inception rather than continuing from the migration point. Always validate a sample of migrated assets by running a trial depreciation schedule before go-live and comparing it to the legacy system output. A thorough ERP data migration checklist should include fixed asset in-service date verification as a mandatory step before cutover.

Fully Depreciated Assets Left on the Register

An asset with zero net book value and zero residual value has technically completed its depreciation. If it remains in service, it should stay on the register with a zero balance to maintain the gross cost disclosure. If it has been scrapped, it should be formally disposed. Leaving fully depreciated assets that are no longer in use on the register inflates gross asset values and can create confusion during audits or insurance renewals.

Multiple Books Not Reconciled at Year-End

If you maintain both GAAP and tax books, the difference between them creates a temporary difference for deferred tax purposes. This reconciliation is often left to the tax team working outside NetSuite, but running both book schedules from FAM and exporting them gives the tax team clean source data, reducing the risk of errors in the deferred tax calculation.

Inadequate Useful Life Reviews

IAS 16 and ASC 360 both require that useful lives and residual values be reviewed at each annual reporting date. In practice, the useful life assigned at asset creation is rarely revisited. A saved search showing assets with less than 12 months of remaining useful life (but which are still actively in use based on department or location tagging) gives finance managers a trigger for annual useful life reviews before they become a last-minute audit issue.