Skip to Content

ERC Intercompany Journal Entries & Transactions

by

23.84

19.0 0
Live Preview
Required Apps Discuss (mail)
Invoicing (account)
Manufacturing (mrp)
Purchase (purchase)
Inventory (stock)
Technical Name erc_intercompany_je
License OPL-1
You bought this module and need support ? Click here!
Technical Name erc_intercompany_je
License OPL-1
ERC Logo
Global Ready: 50+ Idioms Supported 4-Journal Architecture BOM-Aware Routing

Why This Module?

Global Intercompany Accounting & Governance for Odoo 19

The Problem

Native Odoo intercompany syncs transactions but posts everything to the same GL accounts as third-party operations. Auditors cannot distinguish IC from external revenue or expenses.

The Solution

Dedicated accounts, dedicated journals, and smart routing that auto-classifies by product type. Zero manual work after initial setup. BOM detection for manufactured vs. resale goods.

Enterprise Result

Clean consolidated P&L with IC eliminations at a glance. Auditors filter by journal prefix (ICS/ISS/ICP/ICE) to see all intercompany activity instantly.

Try Our Live Demo

URL: https://erc-implementors.me/web/database/selector

Database: erc_intercompany_je_us

Login: ERC_ME

Password: demo

ERC Intercompany Accounting & Governance — Process Overview

Automated Persistence & Daily Realignment

Set it once, forget it forever. The module maintains its infrastructure automatically.

On Install

Creates all 7 GL accounts, 4 journals, seeds country profiles, and links partner accounts. One click — full infrastructure.

On Upgrade

Migration scripts detect missing journals or accounts and create them. Existing data is preserved — only gaps are filled.

Daily Cron

Every day, re-evaluates all draft SO/PO across HQ and branches. If a journal assignment is wrong (e.g., product type changed), it auto-corrects.

Configuration at a Glance

Three sections in Settings → General Settings, all company-dependent.

1. Journals
  • Intercompany Sales Journal (ICS)
  • Intercompany Services Sales Journal (ISS)
  • Intercompany Purchase Journal (ICP)
  • Intercompany Services Expenses Journal (ICE)

Toggle Intercompany Journal on Orders to show journal selector on SO/PO forms.

2. Demo Products
  • Checkbox: Install Intercompany Demo Products
  • Button: Install Demo Products
  • Creates 4 products + 1 BOM
  • Tests all 3 routing paths

One-time action. Button disappears after install. Safe to use in production — creates test data only.

3. Account Segregation
  • Enforce Segregation — block invoices if accounts missing
  • Sync Partner AR/AP — auto-assign IC receivable/payable
  • BOM → Production Account — route manufactured goods
  • 7 account fields (3 revenue, 2 cost/expense, AR, AP)

Buttons: Analyze COA Proposal , Auto-Create Accounts , Setup For Company Group .

Key Product Highlights

Everything your group needs for compliant intercompany accounting — out of the box.

Zero-Config Account Setup

On install, automatically creates 7 dedicated GL accounts (3 revenue, 2 cost/expense, AR, AP) and 4 journals (ICS, ISS, ICP, ICE) per company, using your Chart of Accounts style and country-specific seed codes.

Smart Journal Routing New

Add a service to an IC order → journal switches to ISS/ICE. Add goods → journal switches to ICS/ICP. Mix both? The module blocks it with a clear message. No manual journal selection ever needed.

50+ Country Profiles

Pre-loaded seed codes for Brazil, Portugal, Angola, USA, and 47 more countries. Account codes and labels are generated in the correct format for each localization, with names translated to the local language.

BOM-Aware Revenue Routing New

Products with a Bill of Materials automatically use the Production Income Account on the ICS journal. Regular goods use Resale. Both accounts visible on the journal for full audit transparency.

Partner Auto-Sync

Mark a partner as “Intercompany” and the module instantly assigns dedicated AR/AP accounts, links IC journals, and auto-selects the correct journal on every new Sale or Purchase Order for that partner.

Draft Review & Enforcement

See the assigned IC journal and account routing while orders are still in Draft. Enable “Enforce Segregation” to block invoice creation if any required intercompany account is missing — preventing GL contamination before it happens.

4-Journal Architecture New in v6

Separate journals for goods and services — on both the seller and buyer side. Each journal has its own numbering sequence, default accounts, and audit trail.

Seller Side (Revenue)
ICS — Intercompany Sales

Default: Resale Sales IC

BOM Products: Production Sales IC


ISS — Intercompany Services Sales

Default: Service Sales IC

Buyer Side (Cost / Expense)
ICP — Intercompany Purchases

Default: Cost of Goods Sold IC


ICE — Intercompany Services Expenses

Default: Services Expenses IC

All journal codes (ICS, ISS, ICP, ICE) are auto-generated. If a code is already taken, the module increments automatically (ICS → IC2 → IC3).

Smart Journal Routing New in v6

The journal is determined automatically when product lines are added — not when the partner is selected.


Select IC Partner
No journal set yet

Add Product Lines
Module detects type

Journal Auto-Selected
ICS/ISS or ICP/ICE
Product Type Inventory Classification Sale Journal Income Account Purchase Journal Expense Account
Goods (no BOM) Consumable / Storable ICS
Resale Sales IC
ICP
COGS IC
Goods (with BOM) Consumable / Storable + BOM ICS
Production Sales IC
ICP
COGS IC
Service Service ISS
Service Sales IC
ICE
Services Expenses IC
Mixed Goods + Services on same order Blocked — user must create separate orders for goods and services

BOM-Aware Production Account New in v6.5

The ICS journal carries two income accounts. Auditors see both — no hidden overrides.

ICS Journal — What Auditors See
Default Income Account Resale Sales IC
Default Production Income Account Production Sales IC

Both accounts are visible directly on the journal form. No hidden logic — full traceability.

How It Works
  1. User adds a product with BOM to an IC Sale Order
  2. Module detects the BOM via mrp.bom lookup
  3. Invoice line picks from the journal's Production Income Account
  4. Regular goods (no BOM) use from the journal's Default Income Account

Configurable: A company-level checkbox ( BOM Products Use Production Revenue Account ) controls this behavior. Disable it to route all goods through Resale regardless of BOM.

Built-In Demo Products New

Opt-in example products to test every routing scenario. Enable with one checkbox in Settings.

Goods Intercompany

Consumable (Resale)

Services Intercompany

Service type

Product Intercompany

Consumable + BOM

Material BOM

Component (purchase only)

Demo products are never installed automatically . Go to Settings → Intercompany Demo Products → check the box → click Install Demo Products .

Complete GL Account Map

Seven dedicated accounts created per company. Codes adapt to your country profile.

Code (US) Account Name Side Type Used When
Production Sales Intercompany Seller Income Goods with BOM (manufactured)
Resale Sales Intercompany Seller Income Goods without BOM (resale)
Service Sales Intercompany Seller Income Service-type products
Cost of Goods Sold Intercompany Buyer Direct Cost Goods purchases (any)
Services Expenses Intercompany Buyer Expense Service purchases
Intercompany Receivable AR Receivable IC partner invoices
Intercompany Payable AP Payable IC partner bills

Codes shown are for the US profile. Brazilian companies use 3.01.xx, Portuguese use 71xx, etc. The module reads your Chart of Accounts and adapts automatically.

Visual Product Tour

Enterprise control for Odoo 19 multi-company environments.

1. Dedicated Intercompany Sequences

Dedicated Intercompany Sequences

[SCREENSHOT_SEQUENCES]

* Document Series and Use Documents fields are available depending on your localization (e.g., LATAM countries).

2. Global Localization Sync

50+ Country Localization Profiles

3. Smart Account Segregation

Smart Account Segregation

[SCREENSHOT_SEGREGATION]

4. 4-Journal Architecture

4-Journal Architecture

[SCREENSHOT_4_JOURNALS]

5. Intercompany Partner Config

Intercompany Partner Configuration

6. Journal & Account Mapping

Intercompany Journal and Account Mapping

7. Demo Products & Test Routing

Intercompany Demo Products Installed

* One-click install of example products (Goods, Services, Manufactured with BOM) to test all routing scenarios.

Mixed Order Protection New in v6

Services and goods require different journals and GL accounts. Mixing them on a single IC order would break the audit trail.

Blocked

Adding both a Service and a Consumable/Storable product to the same intercompany Sale or Purchase Order.

Intercompany orders cannot mix services and goods.

Please create separate orders:
• One for services (→ journal ISS)
• One for goods/products (→ journal ICS)
Correct Approach

Create two separate orders for the same IC partner:


SO #1
Goods only
ICS

SO #2
Services only
ISS

Professional Support

WhatsApp Support
+55 11 92207 9570
Email Inquiry
[email protected]

Corporate Identity

  • CNPJ: 12.353.398/0001-29
  • Owner: Benedito Monteiro
  • Website: erc-implementors.com

Rua Professora Gioconda Mussolini, 239. Jd Rizzo, Sao Paulo - SP, Brazil

What’s New in v7.0 Phase 2

Seven enhancements that add visibility, validation, and batch operations to the intercompany setup workflow.

Setup Status Dashboard

Live status badge in Settings shows Not Configured , Partial , or Complete with missing account count and last setup run date. Know instantly which companies need attention.

Pre-Setup Validation

Before creating any accounts, the module checks that the company has a fiscal country and an active chart of accounts . Missing prerequisites trigger a clear danger notification — no silent failures.

Chatter & Audit Trail

Country profile seed code changes are tracked in chatter . Every setup run posts a detailed summary to the company partner’s chatter with a PDF report auto-attached .

Auto-Clear on Unflag

Toggle a partner’s Intercompany flag off and the module automatically clears IC journal and account pointers. No stale references left behind. Property AR/AP accounts are preserved for posted invoice history.

PDF Setup Summary

QWeb PDF report bound to res.company showing all 7 GL accounts, 4 journals, their status, and country profile seed codes. Generated on demand or auto-attached after every setup run.

Invoice Journal Alignment

When an IC invoice is posted on the wrong journal (e.g., ICS instead of ISS for services), a chatter warning is posted. Never blocks posting — just flags the mismatch for review.

Batch Setup Wizard

Run intercompany account setup across all companies in your group from a single wizard. Preview what will be created, skip already-configured companies, or force re-alignment. One click, entire group done.

ERC Logo
ERC IMPLEMENTORS LTDA

Professional Odoo Solutions & Localization Experts

Odoo 19 Enterprise Ready 50+ Countries

© 2026 ERC Implementors. All Rights Reserved. | CNPJ: 12.353.398/0001-29

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.