Capex Case

Standard Operating Procedure: CAPEX Case

1. Document Control & Revision History

---

2. Executive Summary & Scope

This SOP establishes the rigorous framework for the evaluation, justification, and submission of Capital Expenditure (CAPEX) cases. It ensures that all investments align with institutional strategic objectives, maintain fiscal solvency, and comply with GAAP/IFRS standards.

Scope: This procedure applies to all departmental requests for tangible assets, intangible assets, and infrastructure upgrades exceeding the $5,000 capitalization threshold. It covers the full lifecycle from financial modeling to Post-Implementation Review (PIR).

---

3. Prerequisites & Tool Requirements

• Software Access: ERP Module (SAP/Oracle/NetSuite) with Finance-Module write permissions.
• Documentation: Access to the "CAPEX Financial Modeling Template" (Master Excel Workbook).
• Certifications: Mandatory completion of "Fiscal Stewardship & Procurement Ethics" training.
• Data Inputs: Current-year budget variance reports and three (3) vendor competitive bids (or a sole-source justification memo).

---

4. Roles & Responsibilities (RACI Matrix)

---

5. Step-by-Step Operational Procedure

Phase I: Financial Modeling & Justification

• Conduct NPV (Net Present Value) and IRR (Internal Rate of Return) analysis for the investment.
• Map the investment to at least one Strategic Institutional Pillar.
• Obtain formal quotes from three (3) vetted vendors; execute Sole-Source Justification if applicable.

Phase II: Submission & Audit

• Upload the business case package (Modeling + Quotes + Justification) to the ERP portal.
• Trigger the electronic signature workflow to Department Lead and Financial Controller.
• Verify that the request is tagged to the correct G/L (General Ledger) cost center.

Phase III: Approval & Procurement

• Receive digital "Approval to Proceed" notification from the Finance Office.
• Issue Purchase Order (PO) via ERP procurement module.
• Secure delivery receipt and asset tagging confirmation upon physical arrival of the asset.

---

6. Quality Assurance & Verification Criteria

• Data Integrity: All financial projections must be cross-verified against the master department budget.
• Tolerance Thresholds: IRR must exceed the institutional Weighted Average Cost of Capital (WACC) by at least 200 basis points.
• Acceptance Benchmarks: Case is rejected if total expenditure exceeds the budget variance margin by >5%.
• Audit Trail: Every phase requires a digital timestamp; manual bypass of the electronic workflow constitutes a compliance violation.

---

7. Practical Troubleshooting Scenarios

Scenario A: Vendor quote exceeds the initial budget estimate by 15%

• Corrective Action: Immediate hold on submission. The requester must submit an "Incremental Spend Memo" explaining the variance. Finance must perform an impact analysis on the current fiscal year CAPEX pool before re-approving the workflow.

Scenario B: Procurement system downtime prevents submission before Quarter-End deadline

• Corrective Action: Initiate the "Emergency Contingency Protocol." Email the offline CAPEX Intake Form to the CFO’s office with the Financial Controller copied. Once the system restores, the requester must retroactively input the data within 24 hours.

Scenario C: Discrepancy between Asset Tag and ERP Inventory Entry

• Corrective Action: Flag the asset as "Non-Compliant" in the ERP module. Operations must reconcile the physical asset tag with the PO number via a visual audit within 48 hours to ensure tax depreciation schedules are accurate.