Analytic Account - Intercompany Fix
by Odoo DevHouse https://apps.odoo.com/apps/modules/browse?author=Odoo%20DevHouse$ 60.00
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Invoicing (account) • Purchase (purchase) • Sales (sale_management) |
| Lines of code | 102 |
| Technical Name |
account_analytic_intercompany |
| License | OPL-1 |
| Website | https://apps.odoo.com/apps/modules/browse?author=Odoo%20DevHouse |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Invoicing (account) • Purchase (purchase) • Sales (sale_management) |
| Lines of code | 102 |
| Technical Name |
account_analytic_intercompany |
| License | OPL-1 |
| Website | https://apps.odoo.com/apps/modules/browse?author=Odoo%20DevHouse |
Analytic Distribution - Intercompany Fix
Automatically propagate analytic accounts across intercompany Sales Orders, Purchase Orders, and Invoices . Never lose analytic traceability when transactions cross company boundaries - global analytic accounts are forwarded and merged with Company B's default distribution rules automatically.
- SO -> PO Analytic Propagation: Analytic distribution from Sales Order lines automatically forwarded to auto-generated Purchase Order lines
- PO -> SO Analytic Propagation: Analytic distribution from Purchase Order lines automatically forwarded to auto-generated Sales Order lines
- Invoice -> Bill Analytic Propagation: Customer Invoice analytic data carried to auto-generated Vendor Bill
- Smart Merge with Company B Defaults: Company B's default distribution model takes priority on conflicts
- Multi-Analytic Plan Support: Full support for multi-analytic plan system and composite keys
1. Before:analytic account Not appeared in destination intercompany orders/invoices.
1. Create Sale Order in Company A with Analytic Distribution
Set analytic distribution on order lines in Company A. Ensure analytic account has no company restriction (global account).
2. Confirm Sale Order - PO Auto-Generated in Company B
Confirm SO in Company A. Switch to Company B - the auto-generated PO now carries the same analytic distribution on every line.
3. Post Invoice in Company A - Bill Auto-Generated in Company B
Post customer invoice in Company A with analytic distribution. Company B's auto-generated vendor bill inherits the analytic data.
Installation & Configuration
- Install the Module: Copy module folder to addons path and install via Apps menu
- Configure Inter-Company Settings: Go to Settings -> General Settings -> Inter-Company Transactions and enable required rules
- Set Up Global Analytic Accounts: Ensure analytic accounts to share have Company = empty (global)
- Optional - Company B Default Distribution: Configure Accounting -> Configuration -> Analytic Distribution Models
- Test: Create SO with global analytic account in Company A, confirm, verify PO in Company B carries analytics
Step 1: Configure Global Analytic Accounts
Navigate to Accounting -> Configuration -> Analytic Accounts.
For each analytic account you want to share across companies, ensure the
Company field is empty. Accounts with a company set are
intentionally excluded from intercompany propagation to avoid access errors.
Step 2: Configure Inter-Company Settings
Go to Settings -> General Settings -> Inter-Company Transactions.
Enable the required options and fill all fields (Intercompany User, Journal, Document State).
Repeat for every company involved in intercompany transactions.
Step 3: Configure Company B Default Distribution (Optional)
In Company B, navigate to Accounting -> Configuration -> Analytic Distribution Models.
Define default distributions per product, product category, or partner. When an SO/PO/invoice
is generated in Company B, this module merges Company B's defaults with the forwarded global
accounts - Company B's defaults always win on key conflicts.
Step 4: Create Sale Order in Company A with Analytics
Switch to Company A. Create a Sales Order and set an Analytic Distribution on one or more order lines.
- Only global analytic accounts (Company field empty) will be forwarded
- Section and note lines are skipped - only product lines carry analytics
- Multi-plan composite distributions are fully supported
Step 5: Confirm the Sale Order
Click Confirm on the Sale Order. The intercompany rule triggers automatically. Switch to Company B and open Purchase -> Requests for Quotation - the auto-generated PO will carry the same analytic distribution on every line.
Step 6: Invoice Flow - Post Invoice in Company A
Post a customer invoice in Company A that has analytic distribution on its lines. Switch to Company B and open Accounting -> Vendors -> Bills - the auto-generated vendor bill will carry the analytic distribution, merged with any Company B default distribution rules.
Pro Tip - Priority Rules
The merge priority is: Company B's default distribution model wins over forwarded Company A analytics on any key conflict. This means your business rules always take precedence. Company A analytics fill in only what Company B has not explicitly configured.
Multi-Entity Groups
Holding companies with multiple subsidiaries need cost allocation to flow correctly across every intercompany transaction.
Project-Based Organizations
Assign project analytic accounts in Company A's SO and they automatically appear on Company B's PO lines.
Multi-Department Companies
Track costs by department or cost centre across intercompany flows - every document is already tagged.
Accurate Cost Allocation
Every intercompany transaction is properly attributed to the correct analytic account. No missing costs.
Time Savings
Eliminate manual post-generation edits to add analytic data. Analytics flow automatically.
Audit-Ready Traceability
Complete audit trail with full analytic distribution on every intercompany document from creation.
Accurate Management Reporting
Departmental P&L and project profitability reports include all intercompany transactions.
Do You Need Assistance or Have a Feature Request?
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