User reported two UX problems after the Enterprise uninstall:
1. Each Fusion sub-module showed up as its own standalone app in the
launcher (Bank Reconciliation, Financial Reports, Asset Management,
Customer Follow-ups, Fusion AI). Should look like ONE Accounting app.
2. Clicking the 'Fusion Accounting' app still opened the migration
wizard even though Enterprise had been uninstalled and there was
nothing to migrate.
Fix:
- Move all Fusion sub-module roots under the Community account.menu_finance
hierarchy:
* Bank Reconciliation \u2192 Accounting > Bank Reconciliation
* Asset Management \u2192 Accounting > Asset Management
* Financial Reports \u2192 Reporting > Financial Reports
* Follow-ups \u2192 Customers > Follow-ups
* Fusion AI \u2192 Configuration > Fusion AI
* Migrate from Ent. \u2192 Configuration > Migrate from Enterprise
- Rename Community's 'Invoicing' top-level menu to 'Accounting' (what
Enterprise's accountant module did). Set the Fusion icon on it. This
rename lives in the meta-module so it only fires when the full suite
is installed.
- Add second computed group 'group_fusion_show_when_enterprise_present'
(inverse of the existing 'absent' group). Migration menus are gated
by this group, so they auto-hide once Enterprise is uninstalled.
- _fusion_recompute_coexistence_group now maintains both groups in lockstep.
- Meta-module now also depends on l10n_ca, hr_payroll, ocr, documents
(the Phase 6/7 sub-modules) for one-click full-suite install.
- Fusion AI menu's old parent ('accountant.menu_accounting') was deleted
with the Enterprise uninstall \u2014 reparented under Configuration.
Result: single 'Accounting' top-level menu containing the standard
V19 Community structure (Dashboard / Customers / Vendors / Accounting /
Reporting / Configuration), with all Fusion features slotted into the
appropriate sub-section. Verified live on westin-v19: 6 separate
Fusion top-level menus collapsed to 1; coexistence groups recomputed
(absent=10 users, present=0 users); 604/604 tests pass.
Version bump: all touched modules \u2192 19.0.1.1.0.
Made-with: Cursor
fusion_accounting_assets
AI-augmented fixed asset management for Odoo 19 Community — a
Fusion-native replacement for Enterprise's account_asset module.
What it does
- Three depreciation methods: straight-line, declining balance, and units-of-production
- Asset lifecycle state machine: draft → running → paused → disposed
- Editable depreciation board with full schedule recompute
- Disposal flow (sale, scrap, donation) plus partial-sale wizard
- Daily cron for posting periodic depreciation
- AI augmentation:
- Anomaly detection — variance vs expected schedule, low utilization
- Useful-life suggestion — LLM-driven from invoice context, with a keyword-based templated fallback so the feature still works offline
- Coexists with Enterprise
account_asset(Enterprise wins by default; the Fusion menu only appears when Enterprise is uninstalled) - Migration-aware: bootstrap step backfills
fusion.assetfrom existingaccount.assetrows so the AI has memory from day 1
Quick start
# Install
odoo --addons-path=... -i fusion_accounting_assets
# Open the dashboard (when Enterprise's account_asset is NOT installed)
# Apps -> Asset Management -> Assets
# When Enterprise IS installed: use Enterprise's UI; the engine + AI tools
# are still available via the AI chat.
Configuration
- Local LLM (LM Studio, Ollama):
fusion_accounting.openai_base_url=http://host.docker.internal:1234/v1fusion_accounting.openai_model= your local model namefusion_accounting.openai_api_key=lm-studio(anything non-empty)fusion_accounting.provider.asset_useful_life=openai
Public API (engine)
fusion.asset.engine is the single write surface. See CLAUDE.md for
the full 7-method signature list.
See also
CLAUDE.md— agent contextUPGRADE_NOTES.md— Odoo version anchoring