An intercompany asset transfer moves a fixed asset or part of its value from a sending asset in one company code to a receiving asset in another. SAP Asset Accounting supports automatic or separate retirement/acquisition postings, subject to company relationships, transfer variants and valuation settings.
Why company code boundaries change the accounting
Moving a machine from one cost center to another is not necessarily an intercompany asset transfer. Here the company code itself changes, so asset value, accumulated depreciation and potentially separate legal-entity accounts need attention. SAP distinguishes intracompany movement within one company code from intercompany movement between company codes; the relationship of the two codes can also affect the chosen valuation method.
Company codes may belong to the same corporate group or to legally independent entities. Transfer variants and account determination influence the retirement and acquisition sides; neither a physical relocation nor a group relationship alone establishes the correct financial postings.
Automatic or manual transfer: what is the decision?
SAP documents an automatic intercompany process that combines sending-side retirement and receiving-side acquisition. A separate manual approach makes the two postings independently, useful when the accounting scope or valuation requirements cannot be covered by the automatic variant. The configured posting date, asset value date, transfer variant and depreciation-area requirements matter to the result.
Do not assume that the transfer creates an Accounts Receivable invoice, a tax document or a bank payment automatically. For specific automatic transfer scenarios, SAP describes clearing-account postings rather than integrated AP/AR postings. The accounting team must separately determine the contractual and tax treatment.
Example: moving a production machine
A group moves one packaging machine from company code 1100 to company code 2200. The sending asset has illustrative acquisition cost of ₹12,00,000 and accumulated depreciation of ₹3,00,000. The ₹9,00,000 net book value is only a starting point for discussion, not a guaranteed transfer posting. Depending on legal relationship, accounting principles and transfer variant, the receiving company may recognize a different valuation basis.
Finance prepares the receiving master and confirms classification, capitalization terms, effective dates and depreciation-area coverage. Both ledgers are checked after posting and intercompany balances are reconciled. Any realized gain/loss, clearing amount or consolidation adjustment must reflect actual policy and the generated documents.
Controls before the posting
- Document sending and receiving company codes, asset identifiers and ownership transfer approval.
- Confirm whether the companies are legally separate and select the approved valuation/transfer method.
- Check asset value date, fiscal periods, transfer variant and depreciation-area requirements.
- Reconcile retirement/acquisition amounts, clearing balances and receiving master data.
- Retain evidence for tax, consolidation and physical-custody stakeholders where relevant.
Consultant thinking
Ask whether the business wants to shift a physical machine, change the legal owner, split asset values or simply correct cost-center responsibility. Each question leads to a different process. SAP FI-AA transfer design follows the legal and valuation decision rather than determining it.
Related N2i Knowledge
Official SAP References
SAP Help — Automatic Intercompany Asset Transfer · SAP Help — Company Code Relationship Type · SAP Help — Manual Intercompany Asset Transfer