US Capital-Expenditure
Capital-Expenditure (CapEx) Request & ROI Approval with NPV / IRR / payback, budget control and asset creation
Capital-Expenditure (CapEx) Request & ROI Approval with NPV / IRR / payback, budget control and asset creation
Key Features
CapEx request form with a unique sequenced reference,
CapEx request form with a unique sequenced reference, requestor, spend category, currency, useful life, discount rate and salvage value.
Cash-flow schedule (year 0..N) capturing the projected inflo
Cash-flow schedule (year 0..N) capturing the projected inflows and outflows of the investment, with a computed net cash flow per year.
Real financial mathematics computed in pure Python
Real financial mathematics computed in pure Python:
Net Present Value (NPV)
Net Present Value (NPV)
Internal Rate of Return (IRR) solved numerically with
Internal Rate of Return (IRR) solved numerically with a Newton-Raphson method that falls back to bisection, plus a flag that reports when the IRR is mathematically undefined (no sign change).
Simple and discounted payback periods with fractional interp
Simple and discounted payback periods with fractional interpolation.
Profitability Index (PV of future flows / initial
Profitability Index (PV of future flows / initial investment).
Total (undiscounted) ROI percentage
Total (undiscounted) ROI percentage.
Multi-level approval workflow (draft -> submitted -> level-1
Multi-level approval workflow (draft -> submitted -> level-1 approved -> approved / rejected) where the number of required approval levels is driven by configurable amount thresholds (tiers). Every decision is recorded in an immutable appro
Budget control
per fiscal-year / category budgets with a live remaining-budget computation. Final approval is blocked when the request would exceed the remaining budget, with an explicit override flag for authorised managers.
Asset creation on approval
a lightweight CapEx asset record is created and linked when a request is fully approved, ready to be picked up by your fixed-asset process.
Screenshots
Why Choose This Module
A complete, self-contained capital-expenditure request and approval workflow for finance teams that need to justify investments with real return-on-investment metrics before money is committed.
Specifications
- Compatible: Odoo 18.0 / 19.0
- License: OPL-1
- Languages: English
- Author: Pokutsoft
- Dependencies: base, mail
- Support: support@pokutsoft.com
Update date: 2026-07-05
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
Discuss (mail)
|
| Lines of code | 1525 |
| Technical Name |
us_capital_expenditure_request_roi_approval |
| License | OPL-1 |
| Website | https://pokutsoft.com |
Odoo Proprietary License v1.0 This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file). You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one). It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software. The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Please log in to comment on this module