This module is used to create the assets from expense.
auto_awesome What this module does
AI-generated from the code · Odoo 14.0Lets you turn an employee expense into a fixed asset. On an expense line you pick an Asset Profile, and when the expense is posted Odoo creates the asset automatically and links it to the accounting entry.
This module connects employee expenses with the asset management feature, so a purchase made through an expense report can become a tracked fixed asset instead of a simple cost.
- On an expense line (and in the expense sheet lines) an "Asset Profile" field appears for accounting users, placed next to the expense account.
- Choosing an expense account that already has an asset profile automatically fills in that profile; choosing a profile automatically fills in its linked asset account.
- When the expense is posted, the accounting entry line that uses the asset account is tagged with the asset profile.
- If the profile is set to create one asset per item, the line is split into as many lines as the expense quantity, each named with the expense name plus a number, with the amount converted to company currency.
- When the journal entry is created, Odoo builds the asset from those lines, copies the analytic tags onto the asset, and links the asset back to the entry line.
- A message is posted on the journal entry listing the assets that were created.
It touches the expense and expense sheet screens and the accounting entry and asset records behind them.
Depends on
Models and fields (1)
- hr.expense · extends an existing modelasset_profile_id (Asset Profile)
Text generated by AI (DeepSeek) from reading the Odoo 14.0 code on GitHub; it may contain mistakes, so check the code before deciding. View the code on GitHub
Availability by version
Reviewed: 2026-11-03Confirmation status: 1 confirmed, 8 with no information of 9 versions.
Sources · Odoo 14.0
Confirmed on 2026-11-03 in branch 14.0 of OCA/account-financial-tools.
terminal Installation and usage
No verified informationInstallation instructions, the distribution package, dependencies and configuration steps are not shown because they have not yet been verified in the module documentation for any version.
Data imported from GitHub: this sheet reflects the latest catalog review, not a live lookup. Always check the module documentation and staging before installing in production.