A periodic depreciation posting run takes the depreciation calculated for relevant fixed assets and posts the applicable amounts to Financial Accounting, with account assignments and ledger treatment driven by the configuration. Finance should run checks, investigate errors, post the intended period and reconcile the results rather than treating a scheduled job as automatic proof of close.
What changes during the run?
Depreciation terms and keys determine planned depreciation for individual assets. The posting run transfers the appropriate values into accounting documents for a specified company code and period. In SAP S/4HANA Asset Accounting, SAP Learning identifies FAA_DEPRECIATION_POST as the posting program; the relevant user interface and job scheduling depend on the deployment and release.
The run may include ordinary depreciation, applicable special or unplanned depreciation, and other supported value categories. It does not replace the need to validate the underlying asset master data, posting periods, account determination or controlling assignments.
Illustrative month-end scenario
A machine with a hypothetical depreciable base of ₹12,00,000 and a four-year straight-line life would produce ₹25,000 per month if the relevant policy and date conventions support equal monthly depreciation. That amount is a teaching illustration, not a prediction of any particular SAP depreciation key. An incorrect capitalization date, locked cost center or missing account assignment may change or block the actual posting.
The finance controller runs a test, reviews the error list, resolves the approved exceptions and repeats the validation before the productive posting. The resulting run log and accounting documents are retained as evidence.
Four checks that make the run trustworthy
- Master and configuration: confirm depreciation area, key, dates and G/L determination.
- Test-run evidence: inspect blocked account assignments, missing settings and unexpected values.
- Posting control: confirm the correct company code, fiscal period, permissions and job result.
- Reconciliation: compare posted depreciation, asset subledger values, expense accounts and accumulated depreciation with the period-close expectations.
A successful job status is not by itself proof that every relevant asset was valued correctly. Close sign-off should connect the posting log to reviewed exceptions and financial balances.
Related N2i Knowledge
- How depreciation keys calculate asset values
- Unplanned depreciation and exceptional changes
- Asset impairment versus normal depreciation
Official SAP References
SAP Learning — Depreciation Posting · SAP Help — Low-Value Asset Depreciation Context