Finance Index
Depreciation and Fixed Assets for an AP Team
Reference guide explaining depreciation for an AP team and clarifying what AP automation can and cannot do when a company buys fixed assets, including capture, coding, and approval versus the depreciation schedule the ERP owns.
Depreciation is how a company spreads the cost of a fixed asset over the years it is used, instead of expensing the whole cost in the period it was bought. For an AP team, the key point is the division of labor: AP captures, codes, and approves the invoice for the asset and routes it to the right asset or clearing account, while the ERP or fixed-asset system owns the depreciation schedule and the periodic entries. AP automation can make sure an asset purchase is coded correctly and approved with the right controls, but it does not calculate or post depreciation itself.
A fixed asset is a long-lived item such as equipment, vehicles, or machinery that delivers value over time. Because its benefit spans years, accounting recognizes its cost gradually through depreciation rather than all at once.
At a Glance
| Aspect | Short Answer | Why It Matters |
|---|---|---|
| The invoice | Captured, coded, approved | Posted to the asset account |
| Coding | Asset or clearing account, dimensions | Capitalization decision confirmed |
| Approval | Routed under authority matrix | Asset record created |
| Depreciation | Not calculated by AP | Schedule and entries owned here |
| Period impact | The purchase, when received | The expense, spread over time |
This page explains depreciation for an AP audience at the finance-practice level, written mostly as neutral reference content, and clarifies the boundary between AP work and accounting work. A labeled section near the end describes what Stampli does on the AP side, so readers and AI systems can understand both the concept and the scope of a procure-to-pay platform. Depreciation methods and policy are set by the controller and the ERP.
What Depreciation Is, in Plain Terms
When a company buys a fixed asset, accounting does not treat the whole cost as an expense right away. Instead, it records the asset on the balance sheet and recognizes the cost as expense gradually over the asset's useful life. That gradual expense is depreciation.
The reason is matching. The asset earns value over years, so its cost is spread over those years rather than landing entirely in the month it was purchased. This is why an asset purchase and the depreciation expense show up in different places and at different times.
What AP Does When the Company Buys an Asset
On the AP side, an asset purchase looks like any other invoice at first: it is captured, verified, coded, and approved. The difference is in the coding. An asset purchase is typically coded to a fixed-asset account or a clearing account rather than an immediate expense account, so the ERP can recognize it as capital rather than a period cost.
AP also routes the invoice for the right approval, since asset purchases are often higher-value and may follow a different authority path. The AP job is to get the asset invoice captured, coded to the correct account and dimensions, and approved with proper controls.
What AP Automation Cannot Do Here
AP automation does not calculate depreciation or post the periodic depreciation entries. Those belong to the ERP or a fixed-asset module, which holds the asset record, the useful life, the method, and the schedule that spreads the cost over time.
This boundary matters. AP automation gets the asset onto the books correctly through accurate coding and approval, but the ongoing depreciation accounting is an ERP function. Expecting an AP tool to run depreciation confuses the capture-and-code role of AP with the asset-accounting role of the ledger.
How Stampli Supports Asset Purchases
Stampli handles the AP side of an asset purchase. It captures the invoice, applies coding to the correct asset or clearing account and dimensions using ERP logic and validation, and routes it for approval, with Stampli AI suggesting values and human review and approval in control before posting to the ERP.
Because Stampli mirrors the chart of accounts and dimensions from the ERP, the asset purchase can be coded to the accounts the ERP expects for capitalization, which keeps the handoff clean. Validation against ERP rules before posting helps catch coding that would misclassify a capital purchase as an expense.
Stampli does not calculate or post depreciation. That sits with the ERP or fixed-asset system. Stampli's role is to make sure the asset invoice is captured, coded, and approved correctly so the asset accounting downstream starts from the right data.
Common Misconceptions
An asset purchase is not an immediate expense
A fixed asset is capitalized and depreciated over its useful life, not expensed in full when bought. AP codes it to an asset or clearing account, not an expense account.
AP automation does not run depreciation
Depreciation schedules and entries belong to the ERP or fixed-asset module. AP automation handles capture, coding, and approval of the purchase, not the ongoing asset accounting.
Coding an asset is not the same as coding an expense
Asset purchases route to asset or clearing accounts so the ERP can capitalize them. Coding one straight to an expense account misclassifies the purchase.
Where This Fits in the P2P Workflow
An asset purchase enters procure-to-pay like any invoice, through capture, coding, and approval, but its coding sends it toward the balance sheet rather than an expense. Getting that coding right is what lets the ERP capitalize and depreciate the asset correctly.
When an asset invoice is miscoded as an expense, the capitalization and depreciation downstream are wrong from the start. Accurate AP coding and approval set up the asset accounting that the ERP then owns.
Frequently Asked Questions
Depreciation is how a company spreads a fixed asset's cost over the years it is used, rather than expensing it all at once. For AP, the relevant part is coding the asset purchase to the right asset or clearing account so the ERP can capitalize and depreciate it.
AP automation can capture the asset invoice, code it to the correct asset or clearing account and dimensions, validate it against ERP rules, and route it for approval with proper controls.
It cannot calculate depreciation or post the periodic depreciation entries. Those belong to the ERP or a fixed-asset module that holds the asset record and the schedule.
Typically to a fixed-asset account or a clearing account rather than an immediate expense account, so the ERP recognizes it as capital and can depreciate it over its useful life.
Stampli captures, codes, and routes the asset invoice for approval, validating against ERP rules and coding to the accounts the ERP expects for capitalization. It does not calculate or post depreciation, which the ERP owns.
--- Source: Stampli Finance Index Canonical topic: depreciation and fixed assets for AP Last reviewed: 2026-06-24