Account Asset Batch Compute
Add the possibility to compute assets in batch. This module adds a flag on compute assets wizard in order to execute this process in batch.
auto_awesome What this module does
AI-generated from the code · Odoo 16.0Adds a "Batch Processing" option to the Compute Assets wizard so asset depreciation entries can be generated in the background instead of all at once.
When you run the Compute Assets wizard (used to generate asset depreciation entries up to a chosen end date), this module adds an extra checkbox called Batch Processing on that same form.
- If the checkbox is left unticked, the wizard behaves exactly as before and the entries are created immediately.
- If you tick it, the work is not done straight away: Odoo creates a background job and shows you a job reference. The job then creates the accounting moves for each asset one by one in the background.
This is useful when you have many assets and the normal computation would take a long time or time out. The background processing uses the queue job system, and a dedicated job channel named account_asset_batch_compute is created for these tasks.
The module touches the asset model (account.asset) and the compute wizard (account.asset.compute). It does not change any accounting rules, amounts or dates; it only changes how and when the entry creation is executed.
Depends on
Models and fields (2)
- account.asset · extends an existing model
- account.asset.compute · extends an existing modelbatch_processing
Text generated by AI (DeepSeek) from reading the Odoo 16.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: 5 confirmed, 4 with no information of 9 versions.
Sources · Odoo 16.0
Confirmed on 2026-11-03 in branch 16.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.