An intracompany asset transfer moves a fixed asset, or an identified part of it, from a sending asset master to a receiving asset master within the same company code. It is not a sale to another company, and the posting must preserve the appropriate acquisition and depreciation values.
Why would a business transfer an asset?
A plant may discover that a packaging machine was originally assigned to the wrong asset class. Because the asset class is not simply changed on an existing SAP asset master, finance can transfer the value to an appropriately classified receiving asset. Another reason is to divide one capitalized project into independently managed asset records.
The company code stays the same. The physical machine might not move at all: the event can be a classification correction, not a warehouse move. Conversely, moving a machine between departments may require organizational master-data maintenance rather than a value transfer, depending on the record and purpose.
Sending and receiving records
The source asset has historical acquisition and production cost, accumulated depreciation and valuation-area information. The receiving asset must have the correct class and other master data. An authorized transfer posts the sending-side retirement and receiving-side acquisition relationship, subject to the relevant transfer variant, transaction types, and depreciation-area configuration.
SAP documentation distinguishes an intra-company transfer from an intercompany transfer. For a single company code, SAP describes automatic and manual posting approaches; transfer behavior also depends on how valuation areas and date fields are mapped. A finance reviewer should inspect the actual generated documents, not assume the balance sheet total always stays identical in every area.
Example: correcting a packaging-machine class
Assume an asset was recorded in a general equipment class with acquisition value of ₹8,00,000 and accumulated depreciation of ₹1,20,000. Finance identifies a different machine-specific asset class as appropriate. After approval, a receiving asset is prepared and the transfer is posted using company-approved settings.
The example's net book value is ₹6,80,000 before considering any additional adjustments. That is an explanatory arithmetic example, not a promise that SAP posts one net journal entry for this transaction. The actual gross versus other valuation treatment, dates, account determination and depreciation-area impacts must be reviewed in the system.
Controls and troubleshooting
Confirm the sending and receiving company code, asset identity, accounting principle, transfer date and whether all or only part of an asset is transferred. Review depreciation-area coverage and whether the receiving asset can retain the required capitalization and depreciation history. Capture the business justification and approval.
If the transfer cannot be posted, inspect source values, receiving master validity, transaction type and transfer variant rather than bypassing controls. Reconcile the asset history sheet and general ledger after posting. A consultant should distinguish a classification correction from a physical movement or an intercompany sale.
Related Knowledge
Asset classes · Asset acquisition posting · Depreciation areas · AuC settlement. Return to SAP FI / FICO.