Introduction
Wondering how an asset under construction (AuC) in SAP turns into a completed, depreciating asset, and why some balances stay on the books long after the equipment is running? This guide covers the full path. An AuC collects qualifying investment costs until they are transferred to completed assets, and SAP provides settlement processes to move those costs across.
We cover the key terms, the two investment routes, the settlement options by edition, and the difference between settling costs and certifying readiness. A worked case then shows how readiness evidence ties back to the source costs. Those balances often linger because nobody recorded the go-live date, which is the gap SAP asset tracking software closes by capturing readiness on site.
In this guide, you will learn:
- What SAP AuC and CWIP mean, how direct acquisitions differ from WBS and internal-order investment routes, and where costs accumulate before capitalization.
- How periodic and event-based settlement work, including edition-specific configurations and options for allocating costs across multiple completed assets.
- Why settling costs to AuC does not require readiness, while transferring costs to completed assets requires certified availability-for-use evidence and documented cost lineage.
- How to identify ready-but-not-capitalized assets, assign exception owners, reconcile remaining AuC balances, and prevent delayed depreciation through readiness tracking and approval controls.
AuC, CWIP and completed assets: terms and scope
AuC (asset under construction) is SAP’s term for an asset record that accumulates investment costs before completion; CWIP (capital work in progress) is the accounting world’s name for the same balance. In SAP, AuC records sit in their own asset class, receive settled costs from project objects, and are later settled onward to one or more completed assets.
The following sections cover SAP-specific processes and related control requirements. The accounting concepts, including definitions, IFRS treatment, and eligible costs, apply to assets under construction, while CWIP to fixed asset transfer readiness depends on project completion, supporting evidence, and capitalization approvals.
Direct acquisition versus WBS/internal-order investment routes
Small direct purchases post straight to a completed asset; built or project-delivered assets travel through a project object and an AuC first.
Route | How costs flow | Typical use | Where capitalization happens |
|---|---|---|---|
| Direct acquisition | Purchase posts to the final asset record | Off-the-shelf equipment, no construction phase | At acquisition, when the purchase posts to the asset record in SAP asset accounting |
| Investment WBS element | Project costs settle from the WBS to the AuC, then onward to completed assets | Construction projects, multi-vendor capex, phased builds | At settlement to completed assets, when sub-assets are ready |
| Internal order | Order collects costs and settles to AuC / completed assets under its settlement rule | Smaller investment measures and internal projects | At settlement to completed assets |
Periodic and event-based settlement: edition and configuration caveats
Periodic settlement allocates eligible WBS costs to receivers AuC among them at period close, under the project’s settlement rules. Settlement onward to completed assets supports summary and line-item modes, and selected line items can be distributed to completed assets without settling everything at once.
Event-based settlement, where configured, posts investment costs to AuC at line-item level with source references an S/4HANA capability for small investment projects with specific prerequisites. Which mode your landscape runs is an edition and configuration question for your FI-AA/PS team label the release before following any walkthrough.
Evidence for periodic cost settlement versus readiness for completed-asset capitalization
Here is the distinction the whole SERP misses. Periodic WBS-to-AuC cost settlement is an accounting allocation that runs on schedule it needs valid cost assignment and settlement rules, and it does not require the asset to be ready for use. Readiness is not a blanket prerequisite for moving project costs into AuC.
Completed-asset capitalization is different: transferring an AuC balance to a depreciating asset asserts the asset is available for intended use. That assertion needs evidence a certified readiness date, not an invoice date, because an invoice proves purchase, not availability. Frameworks such as IAS 16 tie depreciation start to availability for use, subject to your applicable policy.
Worked readiness-and-cost lineage case
A bottling plant runs one investment WBS for a new line: two sub-assets a filling unit and a packaging conveyor plus shared installation costs. Costs settle periodically from the WBS to the AuC all year; nothing about that settlement asks whether either unit is ready.
Milestone 1 (filling unit, ready in March): The site certifies readiness with photos, commissioning report and a placed-in-service date; the unit’s direct costs plus its share of installation are identified against the certified sub-asset; Finance reviews the evidence and executes the settlement to a completed asset in SAP. Depreciation starts from availability for use while the conveyor’s costs legitimately remain in AuC.
Milestone 2 (conveyor, ready in June): Same sequence certification, cost identification, Finance review, settlement. The AuC balance that remains afterwards is zero, and every movement carries an owner, evidence and a date. The same case traced without evidence shows the failure mode: both units running since March, full balance still in AuC in September, depreciation late not because SAP could not settle, but because no one captured readiness.
Download Now
Quantity, components, ancillary costs, and separate readiness milestones
Real projects complicate the clean case: one settlement may need to form several assets or components, ancillary costs (freight, installation, testing, duties) need documented allocation, and different components reach readiness on different dates. The control principle holds throughout: each separately identifiable asset carries its own readiness evidence and its own cost lineage, and Finance decides the formation under your policy.
Teams running this in AssetCues manage it as project-linked capitalization cases: candidates tied to the WBS, order and AuC references, sub-asset readiness certified from the site with evidence, cost-line references documented, and approved instructions handed to SAP for processing. Formation decisions stay with Finance; the workflow keeps them evidenced and consistent.
Manage ready-not-capitalized exceptions
Aged AuC is two populations wearing one balance: construction genuinely in progress, and ready assets waiting for evidence or approval. The first is legitimate; the second is a control failure with accounting consequences: late depreciation and an overstated construction balance.
- Make readiness visible: A ready-not-capitalized queue, fed by site certifications, with aging thresholds.
- Name the owner: Every aging case carries a person project lead for missing certification, Finance for pending review.
- Escalate on SLA: Reminders and escalation replace month-end email chases; in AssetCues this runs as the exception workbench with reason codes and history.
What stays out of scope here: write-offs, impairment and policy questions remain Finance decisions in SAP an aged balance is a signal to investigate, never an automatic accounting action.
SAP execution and post-update reconciliation
Execution depends on SAP functionality and the configured system design. Settlement rules determine how costs are allocated, while full, partial, or line item settlement transfers eligible costs under FI-AA controls. Procedures may vary by SAP edition and release, so implementation details should align with the relevant SAP documentation and system configuration.
After the posting, reconcile: the completed asset exists with the right value and start date, the AuC balance equals the remaining unsettled milestones, and the readiness evidence is filed against the case. That last check is easier when the evidence and the approval already sit on the same record, which is how asset capitalization software is typically used alongside SAP.
Key takeaways
- An asset under construction (AuC) in SAP accumulates qualifying costs until transfer to completed assets. CWIP represents the same economic concept.
- SAP supports two investment routes: WBS elements and internal orders. Both support periodic settlement and configured event-based settlement.
- Periodic WBS-to-AuC settlement runs on schedule without readiness requirements. Completed-asset capitalization requires readiness evidence.
- An invoice date alone does not prove readiness. Physical evidence must confirm availability for intended use, as required by IAS 16.
- Aged AuC often indicates two problems: ongoing construction or completed assets awaiting evidence or approval. Only the latter is fixable through workflow.
Conclusion
An asset under construction in SAP (AuC) accumulates eligible project costs until it becomes ready for its intended use. SAP transfers costs from a WBS element or internal order to AuC, then settles them to completed assets once the team documents and approves readiness. Aligning cost records, readiness evidence, and settlement postings helps prevent aged AuC balances and depreciation delays.
SAP AuC and CWIP FAQs
Q1. Are AuC and CWIP the same thing?
And: Economically, yes: both name the balance of capital costs accumulated before an asset is completed. AuC (asset under construction) is the SAP object and term; CWIP (capital work in progress) is the general accounting term. In SAP you work with AuC records in their own asset class.
Q2. What is the AuC process in SAP?
And: Investment costs collect on a WBS element or internal order, settle to the AuC typically through periodic settlement and, when sub-assets are ready, settle onward to completed assets under the configured rules. Capitalization and depreciation then run in FI-AA.
Q3. Does an asset need to be ready before costs settle to AuC?
And: No. Periodic WBS-to-AuC cost settlement is a scheduled accounting allocation and does not require readiness. Readiness evidence is required when transferring AuC costs to a completed asset that is ready for depreciation.
Q4. When should an AuC be capitalized to a completed asset?
And: When the asset (or a separately identifiable sub-asset) is available for its intended use, supported by evidence such as a certified readiness date and commissioning proof. An invoice date alone does not establish availability for use; your accounting policy governs the treatment.
Q5. Can part of an AuC be settled while construction continues?
And: Yes, SAP supports settling selected line items or sub-assets to completed assets while the rest of the project continues, under the configured settlement design. The control requirement is to provide readiness evidence and cost lineage for each sub-asset being settled.
Q6. What is SAP CWIP settlement?
Ans: SAP CWIP settlement follows the same process under the CWIP name. It transfers accumulated capital-work-in-progress costs from AuC to completed assets, either fully or partially, according to the project’s settlement rules.
CA Sunny Shah
