SAP Asset accounting

AA manages the fixed-asset lifecycle: acquiring assets (capitalising cost), calculating and posting periodic depreciation, handling transfers and revaluations, and retiring/selling assets. It maintains asset values under one or more valuation views (e.g. local GAAP and IFRS) and feeds the balance sheet.

The reason it is a sub-ledger rather than a set of general ledger accounts is volume and detail. A business with ten thousand assets needs each one tracked individually, with its own acquisition date, useful life and history, while the general ledger only needs the totals. Asset accounting holds the detail and posts the summary, which is the same relationship payables and receivables have with their reconciliation accounts.

• Asset master & asset classes: categorising assets and their rules.
• Depreciation areas: parallel valuations (book, tax, IFRS).
• Depreciation run: periodic posting of depreciation.
• Acquisition, transfer, retirement transactions.

One term worth defining because it appears constantly: the net book value is the acquisition value less accumulated depreciation, and it is what the asset is worth on the balance sheet today. Retiring an asset writes off whatever net book value remains, which is why disposing of an asset early produces a loss the business may not expect.

AS01 creates an asset master, AS02 changes it and AS03 displays it. AS11 creates a sub-asset, which is how a component is tracked separately under a parent.

Postings: F-90 acquires an asset directly, though most acquisitions arrive through a purchase order in materials management instead. ABAVN retires an asset by scrapping, F-92 retires it by sale. AB01 posts other movements.

AFAB is the depreciation run, and it is periodic rather than per transaction, which catches people out: acquiring an asset posts its value, and depreciation only appears when the run executes for that period.

AW01N is the asset explorer, the single most useful screen: values, planned and posted depreciation, and every transaction against the asset, per depreciation area.

The tables are ANLA for the asset master, ANLC for values and ANEP for transactions.

An asset does not have one value. It has one per depreciation area, and understanding that explains most of the module.

A depreciation area is a valuation view. Area 01 typically follows the local statutory rules. Another might follow IFRS, another the tax rules, another an internal management view. Each has its own depreciation method, useful life and net book value for the same physical asset.

This exists because the same machine legitimately depreciates over five years for tax and eight for reporting, and both numbers must be produced from one record rather than from a spreadsheet.

Areas post differently. Some post to the general ledger in real time, some only periodically, and some do not post at all and exist purely for reporting. Which is which is configuration, and it is why a depreciation figure can appear in one report and not another without anything being wrong.

The asset class is what makes this manageable. It groups assets of a kind, and it carries the default depreciation terms and the account determination, so creating a vehicle produces the right depreciation and the right accounts without the person creating it deciding anything.

Half an hour, and it covers the asset lifecycle end to end.

1. Create an asset with AS01 in a class such as machinery. Note the depreciation areas and terms it inherited.
2. Acquire it with F-90 for a value. Check AW01N: acquisition value posted, depreciation planned but not yet posted.
3. Run AFAB for the period. Now depreciation is posted, and the accounting document debits depreciation expense and credits accumulated depreciation.
4. Look at AW01N again and compare two depreciation areas. Different values, same asset.
5. Retire it with ABAVN. The remaining net book value is written off, and the accounting shows the disposal.

Step three is the one to remember: depreciation is a periodic run, not an automatic consequence of acquisition. An asset acquired and never depreciated usually means the run was not executed for that company code. See FI closing for where that run sits in month end.

AA integrates with MM (asset purchases via purchase orders), FI-G/L (depreciation and asset postings), and CO (depreciation as a cost). In S/4HANA, new Asset Accounting posts in real time to the universal journal, aligning asset values across valuations.

The purchase order route is the common one and worth understanding. An asset is bought with account assignment category A on the purchase order line, referencing the asset number. The goods receipt then posts the acquisition directly to the asset, so procurement, finance and asset accounting are one flow rather than three entries. See accounts payable for the invoice side.

Asset accounting has its own rhythm inside the wider close, and the sequence matters.

Acquisitions and retirements posted. Everything that happened in the period has to be in before depreciation runs, because depreciation is calculated on what exists.

Assets under construction settled. Costs collected on a construction order or WBS element are settled to the finished asset, which is when it starts depreciating. Left unsettled, the asset does not exist yet and the value sits in the wrong place.

Depreciation run. AFAB, per company code, per period. It can be repeated for a period if something was missed, and the repeat posts only the difference.

Reconciliation. The asset sub-ledger against its reconciliation accounts. A difference means a posting bypassed the sub-ledger, which should be impossible and occasionally is not.

At year end there is an additional step: the fiscal year change opens the new year for assets, and the year-end closing program checks that depreciation is complete for every asset before closing the old one. That check is why an asset with an incomplete depreciation posting blocks the whole company code from closing, and finding it is a matter of running the report rather than guessing.

• How many asset classes. Enough to give each type its own depreciation terms and accounts, and no more, because every class is configuration to maintain.
• Which depreciation areas. Local statutory is mandatory; IFRS, tax and management views are added where they are genuinely reported. Each area is another set of values to explain.
• Low value assets. Whether items below a threshold are capitalised individually, collectively, or expensed. It is a tax rule and it saves a great deal of master data.
• Assets under construction. Collected on internal orders or on projects, and settled when complete. Which of the two follows from whether the business runs projects formally.

• Wrong asset class, incorrect depreciation rules.
• Missed/incorrect depreciation runs.
• Parallel valuation errors (book vs tax vs IFRS).

• Wrong asset class. It sets depreciation terms and accounts, and correcting it after postings exist means a transfer rather than an edit.
• Depreciation run missed for a company code. Silent until somebody compares the expense to last month.
• Assets under construction never settled. Value sits in the wrong class and never starts depreciating. See bank accounting for another sub-ledger with its own periodic rhythm.

• Capitalising costs that should be expensed. It is a judgement made when the purchase order is raised, by whoever chose account assignment A, and finance sees it afterwards.

Posting an acquisition is straightforward, and configuring asset classes, depreciation areas and account determination so both the tax and reporting views come out right is the part you do in the course.

The screen to reach for is AW01N. It shows every value, every posted and planned depreciation and every transaction for one asset across all areas, and it answers most asset questions without opening anything else.