SAP S/4HANA Project System — Part 2: Funded CapEx, Parent Financing, and Multi-GAAP Asset Settlement

This document is Part 2 of a three-part series on SAP S/4HANA Project System in cross-entity CapEx deployments. Part 1 covers the PS structural architecture, Resource-Related Billing, and the cross-instance HR chargeback framework. This document adds the funded CapEx scenario — where Parent receives external financing but the asset is acquired and operated by MFG — and establishes how all three flows (funding, RRB labour chargeback, vendor acquisition) coexist on the same WBS infrastructure. Part 3 addresses the reverse pattern: a centralised AuC built in a central entity and handed out to the operating segment via intercompany asset transfer at capitalisation.

Funded CapEx — Parent Receives Financing, MFG Acquires the Asset

Scenario Overview

Part 1 addresses how costs flow to a project — the PS structure, the CapEx financial flow, and RRB labour chargeback. This section addresses a structurally distinct but complementary scenario: what happens when the capital funding for a project originates in a different legal entity from the one that acquires and operates the asset.

The specific pattern: the Parent entity receives external financing — bank loan, bond issuance, government grant, or internal treasury allocation — and makes that capital available to the MFG entity, which physically acquires the asset, operates it, and carries it on its balance sheet. The RRB labour chargeback framework from Part 1 continues to operate in parallel. Both flows coexist on the same WBS element in MFG.

The Central Principle: Asset Location Follows Control, Not Funding

Under both IFRS (IAS 16) and US GAAP (ASC 360), an asset is recognised by the entity that controls it and from which future economic benefits flow. Funding source is irrelevant to asset recognition.

The fixed asset always lives in MFG’s company code and SAP instance — regardless of which entity provided the capital.

What changes based on the funding instrument is what the Parent holds on its own balance sheet:

Funding Instrument	Parent Holds	MFG Holds	Group Elimination
IC Loan	Loan Receivable — MFG	Loan Payable — Parent	Eliminate AR vs AP; eliminate IC interest
Equity Injection	Investment in Subsidiary	Additional paid-in capital	Eliminate investment vs MFG equity
IM Budget Appropriation	Statistical budget commitment	Budget availability on WBS	No elimination — statistical only
Grant Pass-Through	Deferred Grant Income	Grant subsidy or deferred income	Eliminate IC grant transfer

The Asset Recording Decision Tree

flowchart TD
    classDef structure fill:#fff3e0,stroke:#e65100
    classDef finance fill:#e3f2fd,stroke:#1565c0
    classDef integration fill:#e8f5e9,stroke:#2e7d32
    classDef reporting fill:#f3e5f5,stroke:#6a1b9a

    START["Asset Acquisition Event"]
    Q1{"Who physically controls<br>and operates the asset?"}
    Q2{"Who bears the economic<br>risks and rewards?"}
    Q3{"Is there a lease or<br>service arrangement?"}
    Q4{"Who funded the acquisition?"}

    ANS_MFG["Asset Master in MFG<br>Company Code and Instance<br>AS01 in MFG"]
    ANS_PAR["Asset Master in Parent<br>Company Code and Instance<br>AS01 in Parent"]
    ANS_LEASE["Assess IFRS 16<br>Right of Use Asset<br>in Operating Entity"]

    FUND_A["IC Loan<br>Parent holds Loan AR<br>MFG holds Loan AP<br>Asset still in MFG"]
    FUND_B["IM Budget<br>Statistical only<br>Asset still in MFG"]
    FUND_C["Equity Injection<br>Parent investment increases<br>Asset still in MFG"]
    FUND_D["External Direct<br>MFG borrows directly<br>Asset in MFG"]

    START --> Q1
    Q1 -->|"MFG controls and operates"| Q2
    Q1 -->|"Parent controls and operates"| ANS_PAR
    Q2 -->|"MFG bears risks and rewards"| ANS_MFG
    Q2 -->|"Shared or unclear"| Q3
    Q3 -->|"Lease or service arrangement"| ANS_LEASE
    Q3 -->|"Direct ownership"| ANS_MFG
    ANS_MFG --> Q4
    Q4 -->|"IC Loan from Parent"| FUND_A
    Q4 -->|"IM Budget Release"| FUND_B
    Q4 -->|"Equity from Parent"| FUND_C
    Q4 -->|"MFG external borrowing"| FUND_D

    class START,Q1,Q2,Q3,Q4 structure
    class ANS_MFG,ANS_PAR,ANS_LEASE finance
    class FUND_A,FUND_B,FUND_C,FUND_D integration

The Three Funding Instruments in SAP

Instrument 1 — Intercompany Loan

The most common pattern in corporate CapEx. Parent borrows externally and on-lends to MFG at an arm’s-length interest rate.

Object	Parent Instance	MFG Instance
GL Account	IC Loan Receivable	IC Loan Payable
Transaction	`F-02` / `FF7A` disbursement	`F-02` / `FB50` receipt
Interest Accrual	`FBS1` IC interest income	`FBS1` IC interest expense
Treasury Management	`TM_52` if formal loan agreement	—
Trading Partner	Mandatory on IC loan GL (`FS00`)	Mandatory on IC loan GL (`FS00`)
Consolidation	Loan AR eliminated vs Loan AP	IC interest eliminated both sides

Instrument 2 — Investment Management Budget Appropriation

SAP IM sits directly above PS in the hierarchy. The Parent controls the CapEx envelope via an IM Program; budget is released down to MFG’s WBS elements. No cash changes hands — this is a control and governance mechanism, not a financial instrument.

flowchart TD
    classDef structure fill:#fff3e0,stroke:#e65100
    classDef finance fill:#e3f2fd,stroke:#1565c0
    classDef integration fill:#e8f5e9,stroke:#2e7d32
    classDef reporting fill:#f3e5f5,stroke:#6a1b9a

    subgraph IM_LAYER["Investment Management — Parent"]
        PROG["IM Program<br>Corporate CapEx Budget"]
        POS["IM Program Position<br>MFG Plant Expansion"]
        APP["Appropriation Request<br>Specific Project Approval"]
        BUDGET["Budget Distribution<br>to WBS"]
    end

    subgraph PS_LAYER["Project System — MFG"]
        WBS_TOP["WBS Top Level<br>Project Definition"]
        WBS_EXEC["WBS Exec Level<br>Cost Collector"]
        AUC_WBS["AuC Linked Asset<br>Investment Measure"]
        SETTLE["CJ88 Settlement<br>to AuC"]
        FA_FINAL["Fixed Asset<br>MFG Register"]
    end

    PROG --> POS
    POS --> APP
    APP --> BUDGET
    BUDGET -->|"Budget released to WBS"| WBS_TOP
    WBS_TOP --> WBS_EXEC
    WBS_EXEC --> AUC_WBS
    AUC_WBS --> SETTLE
    SETTLE --> FA_FINAL

    class PROG,POS,APP,BUDGET finance
    class WBS_TOP,WBS_EXEC,AUC_WBS,SETTLE,FA_FINAL structure

Object	Transaction	Purpose
IM Program	`IM01`	Corporate CapEx budget program at Parent level
Program Position	`IM11`	Budget line per MFG project or plant
Appropriation Request	`IMA11`	Individual project approval linked to WBS
Budget Distribution	`IM32` / `IM52`	Releases budget from IM position to WBS
Availability Control	`OIAF`	WBS cannot exceed IM-released budget
Investment Measure Link	`CJBV`	Links WBS to IM appropriation

Instrument 3 — Government Grant Pass-Through

Where Parent receives a conditional grant and passes the economic benefit to MFG:

Parent: recognises deferred grant income as a liability until conditions are met; recognises income when MFG asset is acquired
MFG: receives IC subsidy credit; either reduces asset cost (net presentation) or recognises deferred income amortised over asset life (gross presentation)
SAP: PS milestones on MFG WBS trigger grant recognition events; ABZU / ABCO reduce APC if net presentation is elected; SAP Grants Management (GM) module available for high-volume grant programmes

Coexistence with RRB: The WBS Cost Stack

The WBS element in MFG is the single convergence point for all cost inflows. The RRB labour chargeback and the funded vendor acquisition operate in parallel — not sequentially — on the same cost collector.

flowchart TD
    classDef structure fill:#fff3e0,stroke:#e65100
    classDef finance fill:#e3f2fd,stroke:#1565c0
    classDef integration fill:#e8f5e9,stroke:#2e7d32
    classDef reporting fill:#f3e5f5,stroke:#6a1b9a

    subgraph FUNDING["Funding Layer — Parent"]
        EXT_FUND["External Funding<br>Loan / Grant / Equity"]
        IM_PROG2["IM Program<br>Budget Approval"]
        IC_TRANSFER["IC Fund Transfer to MFG"]
    end

    subgraph LABOUR["Labour Chargeback — RRB"]
        EMP_A["Employees Company A"]
        CATS_A["CATS Time Entry<br>Proxy WBS"]
        DIP_A["DIP Profile DP91"]
        IC_INV_A["IC Invoice<br>Co A to MFG"]
    end

    subgraph MFG_WBS["MFG Instance — WBS CapEx Collector"]
        WBS_MFG["WBS Element<br>Single Cost Collector"]
        COST1["Vendor Invoice<br>PO / GR / MIRO"]
        COST2["IC Labour Invoice<br>RRB from Co A"]
        COST3["IC Funding Applied<br>Budget Offset"]
        AUC_MFG["Asset Under Construction<br>MFG Books"]
        FA_MFG["Fixed Asset<br>MFG Asset Register"]
    end

    subgraph VENDOR_EXT["External Vendor"]
        VND["Vendor<br>Asset Supplier"]
    end

    subgraph CONSOL["Group Consolidation"]
        ELIM_RRB["Eliminate IC Labour<br>AR Co A vs AP MFG"]
        ELIM_FUND["Eliminate IC Funding<br>Loan AR vs AP"]
        NET_BS["Net Balance Sheet<br>Fixed Asset at Group"]
    end

    EXT_FUND --> IM_PROG2
    IM_PROG2 --> IC_TRANSFER
    IC_TRANSFER --> COST3
    EMP_A --> CATS_A
    CATS_A --> DIP_A
    DIP_A --> IC_INV_A
    IC_INV_A --> COST2
    VND --> COST1
    COST1 --> WBS_MFG
    COST2 --> WBS_MFG
    COST3 --> WBS_MFG
    WBS_MFG --> AUC_MFG
    AUC_MFG --> FA_MFG
    IC_INV_A --> ELIM_RRB
    COST2 --> ELIM_RRB
    IC_TRANSFER --> ELIM_FUND
    COST3 --> ELIM_FUND
    FA_MFG --> NET_BS
    ELIM_RRB --> NET_BS
    ELIM_FUND --> NET_BS

    class EXT_FUND,IM_PROG2,IC_TRANSFER finance
    class EMP_A,CATS_A,DIP_A,IC_INV_A integration
    class COST1,COST2,COST3,WBS_MFG,AUC_MFG,FA_MFG structure
    class VND integration
    class ELIM_RRB,ELIM_FUND,NET_BS reporting

WBS Cost Component Breakdown

Cost Component	Source	SAP Posting	Capitalised into APC?
Vendor asset purchase	External vendor via PO/GR/MIRO	Dr WBS / Cr GR-IR / Cr Vendor AP	Yes
IC labour — engineering	Co A RRB via DP91/VF01/MIRO	Dr WBS / Cr IC Vendor AP	Yes — directly attributable under IAS 16.17
IC labour — project management	Co A RRB via DP91/VF01/MIRO	Dr WBS / Cr IC Vendor AP	Depends — assess direct attributability
IC installation services	Co A RRB via DP91/VF01/MIRO	Dr WBS / Cr IC Vendor AP	Yes — installation is capitalised
Capitalised overhead	CO assessment via `KSS2`	Dr WBS / Cr Cost Centre	Yes — if directly attributable to construction
IC loan proceeds	Parent via `FB50`	Dr Cash / Cr IC Loan AP	No — funding offset, not a cost
Interest during construction	IC loan interest — IAS 23	Dr Interest Expense WBS / Cr IC Interest AP	Potentially — qualifying asset test applies

The Three-Flow Sequence: Funding, RRB, and Vendor Acquisition

sequenceDiagram
    participant EXT as External Funder
    participant PRNT as Parent Instance
    participant CPI as Integration Layer
    participant COA as Company A Instance
    participant MFG as MFG Instance
    participant VND as External Vendor
    participant GRP as Group Consolidation
    Note over PRNT,MFG: FLOW 1 - FUNDING
    EXT->>PRNT: External loan or grant received
    PRNT->>PRNT: IM Program budget loaded via IM32
    PRNT->>CPI: IC loan disbursement notification
    CPI->>MFG: IC loan posted via FB50 and IDoc
    PRNT->>MFG: Budget released to WBS via CJ32
    MFG->>MFG: WBS budget availability active
    Note over COA,MFG: FLOW 2 - RRB LABOUR CHARGEBACK
    COA->>COA: CATS time entry via CAT2 or Kronos or Workday
    COA->>COA: CATSCO transfer to ACDOCA
    COA->>COA: DP91 DIP billing request generated
    COA->>COA: VF01 IC invoice raised
    COA->>CPI: IDoc INVOIC02 transmitted
    CPI->>MFG: IC AP invoice received
    MFG->>MFG: MIRO posted to WBS
    Note over MFG,VND: FLOW 3 - VENDOR ASSET ACQUISITION
    MFG->>VND: PO raised via ME21N account assignment A
    VND->>MFG: Asset delivered
    MFG->>MFG: MIGO GR movement type 101 to AuC
    VND->>MFG: Vendor invoice submitted
    MFG->>MFG: MIRO invoice verification
    Note over MFG,GRP: PERIOD END - CAPITALISATION AND CONSOLIDATION
    MFG->>MFG: CJ88 WBS settlement to AuC
    MFG->>MFG: AIAB line item settlement
    MFG->>MFG: AIBU capitalisation to fixed asset
    MFG->>MFG: AFAB depreciation run
    MFG->>GRP: ACDOCA extract via BW4HANA
    COA->>GRP: ACDOCA extract via BW4HANA
    PRNT->>GRP: ACDOCA extract via BW4HANA
    GRP->>GRP: IC loan elimination
    GRP->>GRP: IC labour AR and AP elimination
    GRP->>GRP: Fixed asset retained on group balance sheet

Asset Master Configuration in MFG

Field	Value	Notes
Company Code	MFG company code	Always MFG — never Parent
Asset Class	AuC during construction; final class at capitalisation	AuC class has no depreciation; final class triggers depreciation start
Profit Centre	MFG profit centre	Drives segment P&L attribution
Cost Centre	MFG cost centre	Receives depreciation postings after capitalisation
WBS Element	MFG WBS element	Links asset to project during construction
Investment Profile	Linked to IM appropriation	Enables budget availability check
Depreciation Areas	Local GAAP area 01, IFRS area 15, Tax area 30	All defined in MFG company code
Capitalisation Date	Date of `AIBU` run	Depreciation start date derived from this

IAS 23 Borrowing Cost Capitalisation

When the IC loan is specifically drawn for this project, interest during the construction period becomes part of APC under IAS 23 and ASC 835-20. This adds a dedicated configuration layer:

Object	Transaction	Purpose
Cost Element — Borrowing Costs	`KA01`	Separate primary CE for capitalised interest
WBS Account Assignment for Interest	`OKB9`	Routes IC interest expense to WBS during construction
Settlement Rule — Interest Component	`CJ20N`	Includes borrowing cost CE in AuC settlement scope
Depreciation Area Control	`OADB`	Area 15 (IFRS) capitalises; Area 30 (Tax) expenses — different APC per area
Capitalisation Suspension	WBS status management	Stop capitalisation when construction is suspended

The tax depreciation area must not capitalise IC interest. Under IRC 163 (US) and equivalent provisions in other jurisdictions, interest remains a deductible expense in the tax area. The settlement rule must be depreciation-area-aware.

Multi-GAAP Treatment of IC Cost Components

Cost Component	Area 01 — Local GAAP	Area 15 — IFRS	Area 30 — Tax
Vendor asset purchase	Capitalise — APC	Capitalise — APC	Capitalise — APC
IC labour — engineering	Capitalise if directly attributable	Capitalise — IAS 16.17	May expense depending on jurisdiction
IC labour — project management	Typically expense	Expense unless directly attributable	Expense
IC interest — IAS 23	Capitalise if qualifying asset	Capitalise — IAS 23 mandatory	Do not capitalise — deduct as interest
Capitalised overhead	Capitalise if directly attributable	Capitalise if directly attributable	Typically expense
Installation services	Capitalise	Capitalise	Capitalise

SAP handles the area-specific differences via transaction types on asset postings, area-specific depreciation keys (AFAMA), and depreciation area-specific settlement rules on the WBS.

Transfer Pricing on IC Labour in CapEx

The IC labour rate set in VK11 is not just a billing mechanic — it directly determines MFG’s depreciable asset base and is subject to transfer pricing scrutiny in every jurisdiction where cross-border IC charges flow.

Element	Requirement	SAP Config Point
Arm’s length rate	IC labour rate must reflect what an unrelated party would charge	`VK11` condition record locked; change requires authorisation
Cost-plus markup	Home entity cost plus overhead burden plus arm’s length markup	DIP profile cost pass-through plus SD surcharge condition type
Documentation	Transfer pricing study required for cross-border IC charges	External to SAP — governance
Withholding tax	Some jurisdictions require WHT on IC service payments	`WTMIG` / WHT config on IC vendor master in MFG
VAT / GST	IC services may attract indirect tax	Tax procedure on IC billing doc type
Permanent establishment risk	Extensive work by Co A employees in MFG jurisdiction may create PE exposure	Governance and legal — informs whether RRB or formal secondment is the correct structure

Complete Period-End Calendar — All Instances

flowchart TD
    classDef structure fill:#fff3e0,stroke:#e65100
    classDef finance fill:#e3f2fd,stroke:#1565c0
    classDef integration fill:#e8f5e9,stroke:#2e7d32
    classDef reporting fill:#f3e5f5,stroke:#6a1b9a

    subgraph WEEK1["Week 1 - Company A and Parent"]
        W1A["Co A: CATSCO<br>Transfer approved time to CO"]
        W1B["Co A: KSII<br>Actual activity rate calculation"]
        W1C["Co A: KSS2<br>Overhead distribution to WBS"]
        W1D["Parent: IM32<br>Confirm budget releases"]
        W1E["Parent: FBS1<br>Accrue IC interest income"]
    end

    subgraph WEEK2["Week 2 - Company A Billing"]
        W2A["Co A: DP91<br>RRB billing request generation"]
        W2B["Co A: VF04<br>IC invoice creation"]
        W2C["Co A: FI period close<br>Company A books closed"]
        W2D["Co A to MFG: IDoc INVOIC02<br>IC invoice transmitted"]
    end

    subgraph WEEK3["Week 3 - MFG"]
        W3A["MFG: MIRO<br>IC AP invoice posted to WBS"]
        W3B["MFG: MIRO<br>Vendor invoices verified"]
        W3C["MFG: FBS1<br>Accrue IC interest expense"]
        W3D["MFG: CJ88<br>WBS settlement to AuC"]
        W3E["MFG: AIAB and AIBU<br>Capitalise completed assets"]
        W3F["MFG: AFAB<br>Depreciation run"]
        W3G["MFG: FI period close<br>MFG books closed"]
    end

    subgraph WEEK4["Week 4 - Parent Final and Consolidation"]
        W4A["Parent: FI period close<br>Parent books closed"]
        W4B["All: BW4HANA extraction<br>ACDOCA delta all instances"]
        W4C["Consolidation: IC loan elimination"]
        W4D["Consolidation: IC interest elimination"]
        W4E["Consolidation: IC labour AR and AP elimination"]
        W4F["Consolidation: CapEx additions<br>Fixed asset on group balance sheet"]
        W4G["SAC: Group reporting published"]
    end

    W1A --> W1B --> W1C
    W1D --> W1E
    W1C --> W2A
    W1E --> W2A
    W2A --> W2B --> W2C --> W2D
    W2D --> W3A
    W3A --> W3B --> W3C --> W3D --> W3E --> W3F --> W3G
    W3G --> W4A
    W4A --> W4B
    W4B --> W4C --> W4D --> W4E --> W4F --> W4G

    class W1A,W1B,W1C,W1D,W1E structure
    class W2A,W2B,W2C,W2D finance
    class W3A,W3B,W3C,W3D,W3E,W3F,W3G integration
    class W4A,W4B,W4C,W4D,W4E,W4F,W4G reporting

Group Consolidation: What Each Entity Reports and What Survives Elimination

Balance Sheet Line	Parent Standalone	MFG Standalone	Group Consolidated
External Loan Payable	$10M	—	$10M — retained
IC Loan Receivable	$10M	—	Eliminated
IC Loan Payable	—	$10M	Eliminated
Fixed Asset	—	$9.1M (modeled estimate)	$9.1M — retained
IC Interest Receivable	$0.1M	—	Eliminated
IC Interest Payable	—	$0.1M	Eliminated
IC Labour AR	$2.0M	—	Eliminated
IC Labour AP	—	$2.0M	Eliminated

The group balance sheet shows the real economic position: an asset funded by external debt, operated by MFG, with no intercompany noise. Depreciation flows through MFG’s P&L and rolls up into the group P&L unmodified.

{
  "data": [
    {
      "type": "bar",
      "name": "Parent standalone",
      "x": [
        "External Loan Payable",
        "IC Loan Receivable",
        "IC Loan Payable",
        "Fixed Asset",
        "IC Interest Receivable",
        "IC Interest Payable",
        "IC Labour AR",
        "IC Labour AP"
      ],
      "y": [
        10,
        10,
        0,
        0,
        0.1,
        0,
        2.0,
        0
      ],
      "marker": {
        "color": "#2D1B69"
      },
      "hovertemplate": "%{x}<br>Parent: $%{y}M<extra></extra>"
    },
    {
      "type": "bar",
      "name": "MFG standalone",
      "x": [
        "External Loan Payable",
        "IC Loan Receivable",
        "IC Loan Payable",
        "Fixed Asset",
        "IC Interest Receivable",
        "IC Interest Payable",
        "IC Labour AR",
        "IC Labour AP"
      ],
      "y": [
        0,
        0,
        10,
        9.1,
        0,
        0.1,
        0,
        2.0
      ],
      "marker": {
        "color": "#7C4DFF"
      },
      "hovertemplate": "%{x}<br>MFG: $%{y}M<extra></extra>"
    },
    {
      "type": "bar",
      "name": "Group consolidated",
      "x": [
        "External Loan Payable",
        "IC Loan Receivable",
        "IC Loan Payable",
        "Fixed Asset",
        "IC Interest Receivable",
        "IC Interest Payable",
        "IC Labour AR",
        "IC Labour AP"
      ],
      "y": [
        10,
        0,
        0,
        9.1,
        0,
        0,
        0,
        0
      ],
      "marker": {
        "color": "#00E5CC"
      },
      "hovertemplate": "%{x}<br>Group: $%{y}M<extra></extra>"
    }
  ],
  "layout": {
    "title": "Balance Sheet by Entity — Standalone vs Group Consolidated ($M)",
    "barmode": "group",
    "bargap": 0.35,
    "bargroupgap": 0.12,
    "yaxis": {
      "title": "Amount ($M)",
      "rangemode": "tozero",
      "gridcolor": "#e5e5ea"
    },
    "xaxis": {
      "tickangle": -20
    },
    "legend": {
      "orientation": "h",
      "y": -0.28
    },
    "margin": {
      "t": 60,
      "r": 20,
      "b": 110,
      "l": 60
    },
    "plot_bgcolor": "#ffffff",
    "paper_bgcolor": "#ffffff",
    "font": {
      "family": "Inter, Segoe UI, Helvetica, Arial, sans-serif"
    }
  }
}

Figure: Balance sheet by entity. Intercompany positions (loan, interest, labour) net to zero on consolidation; only the external loan payable and the real fixed asset survive on the group balance sheet. Figures are illustrative ($M).

Risk and Control Matrix

#	Risk	SAP Control	Process Control
1	IC labour rate above arm’s length — APC inflated	`VK11` rate locked; authorisation required to change	Annual transfer pricing study review
2	IC invoice arrives after MFG period close	Late posting window in FI variant; MFG accrual posting	Coordinated close calendar; advance billing notification
3	Borrowing costs double-counted across depreciation areas	Separate cost element for IAS 23 interest; area-specific settlement rule	Treasury confirms qualifying asset period and suspension dates
4	WBS proxy mismatch cross-instance	`BAPI_CATS_CREATE` validation; `API_PROJECT_V3` WBS sync	WBS naming convention enforced; monthly reconciliation report
5	IC loan not eliminated at consolidation	Trading partner field mandatory on IC GL; automatic elimination rule	Consolidation reconciliation before publish
6	Asset capitalised in wrong company code	`AS01` company code validation in MFG; `AIBU` requires MFG authorisation	Asset accounting review at every `AIBU` run
7	IM budget exceeded without control	Availability control on WBS via `OIAF`; tolerance set to hard error	Monthly IM vs WBS actual variance report
8	Tax area incorrectly capitalises IC interest	Area 30 excluded from borrowing cost settlement rule	Tax team reviews depreciation area config at go-live and annually
9	IAS 23 capitalisation continues after asset ready for use	WBS status management suspends capitalisation on status change	Project controller confirms and documents completion date
10	VAT and WHT not applied on IC billing	Tax procedure on IC billing doc type; WHT on IC vendor master	Tax team reviews IC billing structure per jurisdiction annually

Configuration Delta — What the Funded CapEx Scenario Adds

On top of the RRB configuration established in Part 1, the funded CapEx scenario requires the following additional objects:

Parent Instance

Object	Transaction	Purpose
IM Program	`IM01`	Corporate CapEx budget program
IM Program Positions	`IM11`	Budget line per MFG project
Appropriation Request	`IMA11`	Project approval linked to MFG WBS
IC Loan Receivable GL	`FS00`	Long-term receivable — trading partner mandatory
IC Loan Posting	`F-02` / `FB50`	Initial disbursement to MFG
Interest Accrual	`FBS1`	Periodic IC interest income
Treasury Loan Management	`TM_52`	If formal loan agreement managed in SAP Treasury

MFG Instance

Object	Transaction	Purpose
IC Loan Payable GL	`FS00`	Long-term payable — trading partner mandatory
IC Loan Receipt	`F-02` / `FB50`	Received IC loan proceeds
WBS Budget from IM	`CJ32` / `IM52`	Budget released from IM program
Asset Account Assignment on PO	`ME21N` account category A	Routes GR posting directly to AuC
AuC Asset Class	`OAOA`	No depreciation during construction
Investment Measure Link	`CJBV`	Links WBS to IM appropriation
Borrowing Cost Element	`KA01`	Tracks IAS 23 capitalised interest on WBS
Depreciation Key per Area	`AFAMA`	Method and useful life per depreciation area
Account Determination	`AO90`	Maps asset class and transaction type to GL per area
Multi-Component Settlement Rule	`CJ20N`	Distributes WBS costs to multiple asset classes and depreciation areas
Capitalisation Date Control	`OAYB`	Controls how capitalisation date is derived

Consolidation Layer

Object	Transaction / Tool	Purpose
IC Loan Elimination Rule	SAP Group Reporting	Eliminates Parent loan AR vs MFG loan AP
IC Interest Elimination Rule	SAP Group Reporting	Eliminates Parent interest income vs MFG expense
CapEx Addition Report	BW/4HANA InfoProvider	Fixed asset additions by entity, project, asset class
Trading Partner on IC Loan GL	`FS00`	Required for automatic IC elimination
Consolidation Unit	`CX1`	MFG and Parent as separate consolidation units

Funded CapEx as a Standard Process Flow

The funded CapEx pattern — instrument selection through capitalisation in MFG and group elimination — as a BPMN 2.0 process:

<?xml version="1.0" encoding="UTF-8"?>
<bpmn:definitions xmlns:bpmn="http://www.omg.org/spec/BPMN/20100524/MODEL"
                  xmlns:bpmndi="http://www.omg.org/spec/BPMN/20100524/DI"
                  xmlns:dc="http://www.omg.org/spec/DD/20100524/DC"
                  xmlns:di="http://www.omg.org/spec/DD/20100524/DI"
                  id="Defs_Ps2FundedCapex"
                  targetNamespace="https://docs.sajivfrancis.com/bpmn">
  <bpmn:process id="Process_FundedCapex" name="Funded CapEx — Parent Financing, MFG Acquisition" isExecutable="false">
    <bpmn:startEvent id="Start_Approved" name="CapEx approved in IM programme">
      <bpmn:outgoing>Flow_1</bpmn:outgoing>
    </bpmn:startEvent>
    <bpmn:exclusiveGateway id="Gw_Instrument" name="Funding instrument?">
      <bpmn:incoming>Flow_1</bpmn:incoming>
      <bpmn:outgoing>Flow_2</bpmn:outgoing>
      <bpmn:outgoing>Flow_3</bpmn:outgoing>
      <bpmn:outgoing>Flow_4</bpmn:outgoing>
    </bpmn:exclusiveGateway>
    <bpmn:task id="Task_Loan" name="Disburse IC loan (Parent → MFG; arm's-length interest)">
      <bpmn:incoming>Flow_2</bpmn:incoming>
      <bpmn:outgoing>Flow_5</bpmn:outgoing>
    </bpmn:task>
    <bpmn:task id="Task_Budget" name="Release IM budget to MFG WBS (IM32 / IM52)">
      <bpmn:incoming>Flow_3</bpmn:incoming>
      <bpmn:outgoing>Flow_6</bpmn:outgoing>
    </bpmn:task>
    <bpmn:task id="Task_Equity" name="Equity injection (investment in subsidiary)">
      <bpmn:incoming>Flow_4</bpmn:incoming>
      <bpmn:outgoing>Flow_7</bpmn:outgoing>
    </bpmn:task>
    <bpmn:exclusiveGateway id="Gw_Join">
      <bpmn:incoming>Flow_5</bpmn:incoming>
      <bpmn:incoming>Flow_6</bpmn:incoming>
      <bpmn:incoming>Flow_7</bpmn:incoming>
      <bpmn:outgoing>Flow_8</bpmn:outgoing>
    </bpmn:exclusiveGateway>
    <bpmn:task id="Task_Acquire" name="Accumulate costs on MFG WBS (vendor invoices + RRB labour)">
      <bpmn:incoming>Flow_8</bpmn:incoming>
      <bpmn:outgoing>Flow_9</bpmn:outgoing>
    </bpmn:task>
    <bpmn:task id="Task_Settle" name="Settle WBS to AuC (CJ88)">
      <bpmn:incoming>Flow_9</bpmn:incoming>
      <bpmn:outgoing>Flow_10</bpmn:outgoing>
    </bpmn:task>
    <bpmn:task id="Task_Capitalise" name="Capitalise in MFG (AIAB / AIBU)">
      <bpmn:incoming>Flow_10</bpmn:incoming>
      <bpmn:outgoing>Flow_11</bpmn:outgoing>
    </bpmn:task>
    <bpmn:task id="Task_Consolidate" name="Eliminate IC funding pair at group">
      <bpmn:incoming>Flow_11</bpmn:incoming>
      <bpmn:outgoing>Flow_12</bpmn:outgoing>
    </bpmn:task>
    <bpmn:endEvent id="End_Live" name="Asset live in MFG; funding on Parent balance sheet">
      <bpmn:incoming>Flow_12</bpmn:incoming>
    </bpmn:endEvent>
    <bpmn:sequenceFlow id="Flow_1" sourceRef="Start_Approved" targetRef="Gw_Instrument" />
    <bpmn:sequenceFlow id="Flow_2" name="IC loan" sourceRef="Gw_Instrument" targetRef="Task_Loan" />
    <bpmn:sequenceFlow id="Flow_3" name="IM budget" sourceRef="Gw_Instrument" targetRef="Task_Budget" />
    <bpmn:sequenceFlow id="Flow_4" name="Equity" sourceRef="Gw_Instrument" targetRef="Task_Equity" />
    <bpmn:sequenceFlow id="Flow_5" sourceRef="Task_Loan" targetRef="Gw_Join" />
    <bpmn:sequenceFlow id="Flow_6" sourceRef="Task_Budget" targetRef="Gw_Join" />
    <bpmn:sequenceFlow id="Flow_7" sourceRef="Task_Equity" targetRef="Gw_Join" />
    <bpmn:sequenceFlow id="Flow_8" sourceRef="Gw_Join" targetRef="Task_Acquire" />
    <bpmn:sequenceFlow id="Flow_9" sourceRef="Task_Acquire" targetRef="Task_Settle" />
    <bpmn:sequenceFlow id="Flow_10" sourceRef="Task_Settle" targetRef="Task_Capitalise" />
    <bpmn:sequenceFlow id="Flow_11" sourceRef="Task_Capitalise" targetRef="Task_Consolidate" />
    <bpmn:sequenceFlow id="Flow_12" sourceRef="Task_Consolidate" targetRef="End_Live" />
  </bpmn:process>
  <bpmndi:BPMNDiagram id="Diagram_Process_FundedCapex">
    <bpmndi:BPMNPlane id="Plane_Process_FundedCapex" bpmnElement="Process_FundedCapex">
      <bpmndi:BPMNShape id="Shape_Start_Approved" bpmnElement="Start_Approved">
        <dc:Bounds x="202" y="242" width="36" height="36" />
      </bpmndi:BPMNShape>
      <bpmndi:BPMNShape id="Shape_Gw_Instrument" bpmnElement="Gw_Instrument" isMarkerVisible="true">
        <dc:Bounds x="365" y="235" width="50" height="50" />
      </bpmndi:BPMNShape>
      <bpmndi:BPMNShape id="Shape_Task_Loan" bpmnElement="Task_Loan">
        <dc:Bounds x="500" y="80" width="120" height="80" />
      </bpmndi:BPMNShape>
      <bpmndi:BPMNShape id="Shape_Task_Budget" bpmnElement="Task_Budget">
        <dc:Bounds x="500" y="220" width="120" height="80" />
      </bpmndi:BPMNShape>
      <bpmndi:BPMNShape id="Shape_Task_Equity" bpmnElement="Task_Equity">
        <dc:Bounds x="500" y="360" width="120" height="80" />
      </bpmndi:BPMNShape>
      <bpmndi:BPMNShape id="Shape_Gw_Join" bpmnElement="Gw_Join" isMarkerVisible="true">
        <dc:Bounds x="705" y="235" width="50" height="50" />
      </bpmndi:BPMNShape>
      <bpmndi:BPMNShape id="Shape_Task_Acquire" bpmnElement="Task_Acquire">
        <dc:Bounds x="840" y="220" width="120" height="80" />
      </bpmndi:BPMNShape>
      <bpmndi:BPMNShape id="Shape_Task_Settle" bpmnElement="Task_Settle">
        <dc:Bounds x="1010" y="220" width="120" height="80" />
      </bpmndi:BPMNShape>
      <bpmndi:BPMNShape id="Shape_Task_Capitalise" bpmnElement="Task_Capitalise">
        <dc:Bounds x="1180" y="220" width="120" height="80" />
      </bpmndi:BPMNShape>
      <bpmndi:BPMNShape id="Shape_Task_Consolidate" bpmnElement="Task_Consolidate">
        <dc:Bounds x="1350" y="220" width="120" height="80" />
      </bpmndi:BPMNShape>
      <bpmndi:BPMNShape id="Shape_End_Live" bpmnElement="End_Live">
        <dc:Bounds x="1562" y="242" width="36" height="36" />
      </bpmndi:BPMNShape>
      <bpmndi:BPMNEdge id="Edge_Flow_1" bpmnElement="Flow_1">
        <di:waypoint x="238" y="260" />
        <di:waypoint x="365" y="260" />
      </bpmndi:BPMNEdge>
      <bpmndi:BPMNEdge id="Edge_Flow_2" bpmnElement="Flow_2">
        <di:waypoint x="390" y="235" />
        <di:waypoint x="390" y="120" />
        <di:waypoint x="500" y="120" />
      </bpmndi:BPMNEdge>
      <bpmndi:BPMNEdge id="Edge_Flow_3" bpmnElement="Flow_3">
        <di:waypoint x="415" y="260" />
        <di:waypoint x="500" y="260" />
      </bpmndi:BPMNEdge>
      <bpmndi:BPMNEdge id="Edge_Flow_4" bpmnElement="Flow_4">
        <di:waypoint x="390" y="285" />
        <di:waypoint x="390" y="400" />
        <di:waypoint x="500" y="400" />
      </bpmndi:BPMNEdge>
      <bpmndi:BPMNEdge id="Edge_Flow_5" bpmnElement="Flow_5">
        <di:waypoint x="620" y="120" />
        <di:waypoint x="730" y="120" />
        <di:waypoint x="730" y="235" />
      </bpmndi:BPMNEdge>
      <bpmndi:BPMNEdge id="Edge_Flow_6" bpmnElement="Flow_6">
        <di:waypoint x="620" y="260" />
        <di:waypoint x="705" y="260" />
      </bpmndi:BPMNEdge>
      <bpmndi:BPMNEdge id="Edge_Flow_7" bpmnElement="Flow_7">
        <di:waypoint x="620" y="400" />
        <di:waypoint x="730" y="400" />
        <di:waypoint x="730" y="285" />
      </bpmndi:BPMNEdge>
      <bpmndi:BPMNEdge id="Edge_Flow_8" bpmnElement="Flow_8">
        <di:waypoint x="755" y="260" />
        <di:waypoint x="840" y="260" />
      </bpmndi:BPMNEdge>
      <bpmndi:BPMNEdge id="Edge_Flow_9" bpmnElement="Flow_9">
        <di:waypoint x="960" y="260" />
        <di:waypoint x="1010" y="260" />
      </bpmndi:BPMNEdge>
      <bpmndi:BPMNEdge id="Edge_Flow_10" bpmnElement="Flow_10">
        <di:waypoint x="1130" y="260" />
        <di:waypoint x="1180" y="260" />
      </bpmndi:BPMNEdge>
      <bpmndi:BPMNEdge id="Edge_Flow_11" bpmnElement="Flow_11">
        <di:waypoint x="1300" y="260" />
        <di:waypoint x="1350" y="260" />
      </bpmndi:BPMNEdge>
      <bpmndi:BPMNEdge id="Edge_Flow_12" bpmnElement="Flow_12">
        <di:waypoint x="1470" y="260" />
        <di:waypoint x="1562" y="260" />
      </bpmndi:BPMNEdge>
    </bpmndi:BPMNPlane>
  </bpmndi:BPMNDiagram>
</bpmn:definitions>

Recommendation

Eight decisions govern the entire architecture. None of them can be deferred to the build phase.

1. Single WBS as the convergence point in MFG. Do not create separate WBS hierarchies per cost source. One WBS element per asset acquisition collects vendor costs, IC labour costs, and is the object against which IM budget availability is checked. All flows settle together to AuC.

2. CO area design is the first and most consequential decision. If MFG and Co A are on the same instance, a single CO area spanning both company codes eliminates the need for proxy WBS and simplifies the CATS posting path substantially. If cross-instance, the proxy WBS pattern with CPI routing is the correct architecture. This decision gates every other integration design choice.

3. RRB via DIP profile — not manual journals. Manual IC journal entries for labour are not auditable, not tied to actual hours, and do not flow correctly into APC. RRB via DIP profile sourcing ACDOCA (S/4HANA 2022+) is the only mechanism that produces a legally clean, auditable, transfer-pricing-defensible IC labour charge that correctly capitalises into the fixed asset.

4. IC loan as the preferred funding instrument over equity injection. An IC loan produces a cleaner audit trail, is easier to eliminate at consolidation via matched AR/AP, and supports IAS 23 borrowing cost capitalisation. Equity injections are harder to trace to specific asset acquisitions and create consolidation complexity around the investment elimination.

5. IM program for budget governance regardless of funding instrument. Even when the funding instrument is an IC loan rather than a budget appropriation, the IM program should still be configured to govern the CapEx envelope. IM and the IC loan operate in parallel — IM controls the budget, the IC loan controls the cash. Without IM, there is no availability control mechanism to prevent WBS overspend.

6. DIP profile must source ACDOCA in S/4HANA 2022+. The legacy COEP-based DIP source path is in compatibility scope. Any new deployment on S/4HANA 2022 or later must configure the DIP profile to use the Universal Journal as source. This ensures RRB and asset accounting read from the same data.

7. Transfer pricing and tax must be resolved in the design phase. The IC labour rate in VK11 and the IC loan interest rate are both transfer pricing instruments. They must be set before go-live based on a transfer pricing study. Retrospective adjustments to asset values are operationally and technically complex in SAP FI-AA and should not be treated as a post-go-live cleanup item.

8. Depreciation area configuration is the most technically complex element of the funded CapEx scenario. The multi-GAAP treatment of IC labour and IC interest across depreciation areas requires explicit settlement rules, transaction types, and account determination per area. It should be the first configuration element validated in build — not the last.

Design Decision Summary

Decision	Options	Recommendation
Are both entities on the same S/4HANA instance?	Same instance vs. separate instances	Determines whether proxy WBS is needed and whether CO area can be shared
Is there a single CO area spanning both company codes?	Single CO area vs. separate CO areas	Single CO area if same instance; proxy WBS if cross-instance
What is the enterprise time system?	Kronos, Workday, Fieldglass, SAP CAT2, or combination	Whichever is enterprise standard — all produce the same CATSDB record via BAPI
Is HR on SAP HCM or SuccessFactors?	SAP HCM on-premise vs. SuccessFactors Employee Central	Determines PERNR resolution strategy
What is the IC pricing model?	Cost pass-through vs. fixed rate vs. marked-up rate	Must be transfer-pricing defensible before go-live
Are contractors in scope?	Employees only vs. employees and contractors	Determines whether Fieldglass SES path is included in DIP profile
What is the capitalisation trigger?	Periodic settlement vs. milestone-driven vs. project completion	Determines CJ88 and AIBU scheduling
What is the consolidation tool?	SAP Group Reporting vs. BPC vs. BW/4HANA and SAC	Determines IC elimination mechanism and cross-instance extract design

Implementation Sequence

Phase	Duration	Activities
1 — Foundation	Weeks 1–4	CO area, company code config, trading partner, activity types, cost centre master data
2 — HR and CATS	Weeks 3–6	CATS profiles, employee groupings, activity type defaults, PERNR mapping in CPI, CATSCO batch
3 — PS Structure	Weeks 4–8	Project profiles, WBS hierarchy, proxy WBS naming convention, budget profiles, settlement profiles
4 — IM Program	Weeks 4–7	IM program, positions, appropriation requests, investment measure links, availability control
5 — RRB and DIP	Weeks 7–10	DIP profile build (ACDOCA source), material determination, IC pricing procedure, VK11 condition records
6 — IC SD Setup	Weeks 8–11	IC sales org, IC order and billing types, IC customer and vendor master, output type for IDoc
7 — Integration	Weeks 9–13	CPI iFlows for time routing, PERNR resolution, WBS sync, IC invoice transmission; IDoc partner profiles
8 — FI-AA	Weeks 10–13	AuC asset class, depreciation areas, multi-GAAP settlement rules, AIAB/AIBU config, IAS 23 cost element
9 — Testing	Weeks 12–16	End-to-end: time entry through CATSCO through DIP through IC invoice through WBS through AuC through capitalisation through BW extract
10 — Reporting	Weeks 14–17	BW/4HANA datasources from all instances, IC elimination logic, SAC CapEx dashboard
11 — Cutover	Weeks 16–18	Open WBS balance migration, AuC balance transfer, proxy WBS population, go-live

Continue to Part 3 — Centralised AuC with Intercompany Asset Transfer at Capitalisation, which addresses the structurally opposite pattern: the AuC is built in a central entity and the finished asset is transferred to the operating segment at completion — covering the IAS 16.7 / ASC 360 control test, ABT1N and the cross-instance disposal-plus-acquisition pattern, net vs gross transfer methods, and the unrealised-profit elimination at group.