Control a NetSuite asset disposal or transfer by confirming the business event first, choosing the correct Fixed Assets Management process, and reconciling the asset history with the resulting accounting. A location change, an intercompany movement, a sale, and a write-off require different evidence. Treating them as interchangeable record edits can leave ownership or balances wrong.
This article addresses event-level controls for the FAM SuiteApp. It does not cover inventory transfer orders or determine tax treatment, transfer pricing, impairment, or derecognition policy. Those decisions require the responsible accountant and, where relevant, tax advisers. The goal is to make the approved treatment traceable through NetSuite.
Use an event form with four questions. Is the asset still controlled by the same legal entity? Is physical custody changing? Is ownership moving to another entity? Is the asset leaving the business through sale, scrapping, loss, or another approved event?
A machine moved between buildings may require a location update through the supported transfer process. A machine sold to another group company needs a broader review of legal ownership, intercompany balances, and consolidation consequences. A machine temporarily lent to a contractor may need custody tracking without being disposed of.
Keep the effective date separate from the date finance receives the request. A late notification can change which period needs review. Do not backdate automatically to make the operational record appear tidy; obtain approval for any accounting correction and period implications.
FAM supports transfers across asset types, subsidiaries, classes, departments, and locations. Subsidiary transfers require valid asset transfer account records. Inline editing does not perform the full asset transfer: it does not transfer cost and cumulative depreciation or create the associated journals.
This means a record showing the new department is insufficient evidence that the event was processed correctly. Review the transfer operation, relevant history, processing status, and ledger effect expected for the configured account.
Keep asset-type changes distinct from other transfers where the supported workflow requires separate operations. Test the sequence in a nonproduction environment before attempting a complex movement. Confirm that the receiving owner, segment values, and accounts are valid for the receiving context.
A transfer request should identify the asset, old and new custody, location, legal entity, effective date, and business reason. Include evidence such as a signed handover, transport confirmation, or internal authorization when relevant to company policy.
Finance should approve the accounting impact separately from the operational handover. The warehouse team can confirm a machine arrived, but that does not establish whether ownership transferred or which intercompany accounts should be used.
For assets with multiple methods or books, define the review population explicitly. A successful accounting-method transfer does not establish that every reporting requirement has been satisfied. Where functionality differs by method, document the approved supporting process and reconcile its result.
A disposal by sale needs evidence of the buyer, proceeds, transaction currency, relevant charges, and collection or receivable status. A write-off needs evidence that supports retirement and the approved treatment of the remaining carrying value. An instruction to remove an asset from a dashboard is not disposal approval.
FAM has separate sale and write-off processes, and disposal produces history for accounting and tax methods. Review both populations when alternate methods are used.
Check whether a disposal is full or partial. A group asset representing ten identical units cannot always be treated as a single indivisible object when only two units are sold. Agree the quantity, cost, and depreciation allocation before processing; keep the surviving population traceable to the original record.
Assume a machine has cost of 80,000 currency units and accumulated depreciation of 56,000 at the approved disposal date. Its carrying value is 24,000. In a simplified sale example with proceeds of 29,000 and no selling costs, tax, or other adjustments, the arithmetic indicates a gain of 5,000.
The control sheet should independently establish each component: 80,000 removed from gross cost, 56,000 removed from accumulated depreciation, 29,000 supported by the sale record, and 5,000 explained as the difference. A balanced journal alone cannot prove the proceeds are genuine or the asset was actually sold.
If the same machine is instead scrapped with no proceeds, the remaining 24,000 needs the accountant's approved write-off treatment. These are hypothetical comparisons, not instructions to post a universal journal. Account configuration, applicable policy, and event-specific costs may change the entries.
Determine the last completed depreciation run and the treatment of the event period under approved policy. The event date may interact with acquisition or disposal conventions, partial-period calculations, and pending background work.
Calculate an expected carrying value at the event date before reviewing the transaction. If the output differs, compare dates, last depreciation information, approved method, and pending processing. Avoid adjusting proceeds or adding an unexplained journal simply to force the disposal calculation to match an old spreadsheet.
After a transfer, verify where the next depreciation charge should appear. After disposal, verify that the retired portion is no longer included in the future depreciation population. These checks connect the one-time event to the following close.
For a department movement within one entity, define whether a journal is expected under the account's preferences, then inspect the result. A no-journal result is not automatically a failure; it needs to agree with the configured design and reporting objective.
For a subsidiary movement, reconcile the sending and receiving positions separately. Identify the linked asset information, transfer date, relevant accounts, currencies, and any intercompany balances. In the consolidated review, confirm that the approved treatment does not leave unexplained group-level value or depreciation changes.
Keep this work separate from inventory in transit. Fixed-asset records and inventory transfer orders serve different populations and should not be substituted for one another merely because both involve physical movement.
Useful exceptions include a transfer request with no receiving acknowledgment, a disposal with no sale evidence, proceeds recorded without an asset retirement, a retired asset still depreciating, and an asset moved by a field edit without the expected transfer history.
For each exception, record the asset identifier, amount at risk, affected period, responsible owner, and next action. Resolve the business evidence first, then determine the supported correction. Restrict irreversible retirement actions and preserve the original event trail rather than deleting records to simplify the register.
The monthly review should also compare disposal approvals with register removals in both directions. This catches events that were approved but never processed and records that disappeared without a valid request.
A complete event packet includes the request, accounting decision, pre-event values, processing result, post-event reconciliation, and reviewer approval. Use it as a repeatable test when preferences, forms, scripts, or FAM versions change.
For help investigating a transfer or disposal mismatch, CuriousRubik's NetSuite support services provide a place to scope the account-specific work. Start with one affected asset and its evidence rather than a blanket request to repair the entire register.
Inline editing does not execute the complete FAM transfer. Use the supported transfer process and review cost, accumulated depreciation, history, and any expected journal effect.
The expected accounting depends on configuration and the specific event. Confirm the relevant preferences and test the supported process. The record change and the journal expectation should both be documented.
Match the approved event to the asset's carrying value, sale evidence, proceeds, disposal history, and ledger result. Confirm collection or receivable status separately; disposal processing alone does not prove cash was received.
Identify the retired quantity and obtain approval for the related cost and depreciation allocation. Reconcile the retired and surviving portions back to the original asset, using the supported partial-disposal design.
The responsible accountant should approve the entity, currency, transfer-pricing, and consolidation treatment, with tax advice where needed. The implementation team should then demonstrate that configuration produces that approved result.