Skip to main content

Acumatica ERP supports Multi-Organization Setup, Consolidation Hub, and Intercompany Transactions

  • February 15, 2025
  • 2 replies
  • 114 views

saifalisabri
Jr Varsity II
Forum|alt.badge.img

Acumatica ERP supports Multi-Organization Setup, Consolidation Hub, and Intercompany Transactions through its Financial Management module. Below is an overview of where each of these features is configured and managed in Acumatica:

1. Multi-Organization Setup (Multi-Company / Multi-Branch)

Acumatica allows you to configure multiple legal entities or branches within the same tenant.

Where to Set It Up?

  • Navigate to Configuration → Organization → Companies (CS101500) to create multiple companies.
  • Go to Configuration → Organization → Branches (CS102000) to create multiple branches under a company.

Key Features:

✔ Supports multiple legal entities within the same tenant.
✔ Each company can have separate financials and chart of accounts (optional).
✔ User-based security roles restrict access to specific companies or branches.
Shared master data (customers, vendors, employees) is optional.

2. Consolidation Hub (Financial Consolidation)

Acumatica provides financial consolidation for organizations with multiple legal entities.

Where to Set It Up?

  • Navigate to Finance → General Ledger → Companies (CS101500).
  • Use Finance → General Ledger → Inter-Company Accounting (GL104500) to configure consolidation.
  • Use Finance → General Ledger → Consolidation (GL304500) to set up reporting ledgers and data mapping.

Key Features:

✔ Consolidates financials from multiple companies into a single reporting entity.
✔ Supports different base currencies (automatic currency conversion).
✔ Uses Consolidation Ledger to manage eliminations and adjustments.
✔ Data can be manually or automatically imported from subsidiaries.

3. Intercompany Transactions

Acumatica supports automated intercompany transactions, allowing transactions between different companies or branches.

Where to Set It Up?

  • Navigate to Finance → General Ledger → Inter-Company Accounting (GL104500).
  • Set up Inter-Company Account Mapping to define accounts for transactions between companies.

Key Features:

✔ Supports automatic due-to / due-from journal entries.
✔ Enables intercompany sales and purchases between entities.
✔ Allows shared vendors/customers between multiple companies.
✔ Works with Accounts Payable (AP), Accounts Receivable (AR), and General Ledger (GL).

Summary

Feature Setup Location Key Functionality
Multi-Organization Setup Companies & Branches (CS101500, CS102000) Manages multiple legal entities or branches within a single tenant.
Consolidation Hub Financial Consolidation (GL304500) Merges financial data from multiple entities for reporting.
Intercompany Transactions Intercompany Accounting (GL104500) Automates financial transactions between different entities.

If you're looking to implement any of these features, let me know, and I can guide you through the specific configurations!

Did this topic help you find an answer to your question?

2 replies

aaghaei
Captain II
Forum|alt.badge.img+10
  • Captain II
  • 1201 replies
  • February 15, 2025

Great summary. Just a clarification that to the best of my knowledge, Acumatica has a centralized Chart of Accounts not Company/Branch specific CoA. You may limit access to Accounts but accounts are shared across all companies.


saifalisabri
Jr Varsity II
Forum|alt.badge.img
  • Author
  • Jr Varsity II
  • 44 replies
  • February 17, 2025

Reza Aghaei :Thank you for your insightful comment!
You’re absolutely correct that accounts are shared across all companies in Acumatica ERP, which is a key feature for maintaining consistency and streamlining financial management in a multi-organization setup.

To address your point about limiting access to accounts, Acumatica provides robust role-based access control (RBAC). While accounts themselves are shared, you can restrict access to specific accounts or financial data by configuring user roles and permissions. For example:

  1. Role Restrictions: Assign roles that limit access to certain modules, such as the General Ledger or specific subledgers.

  2. Branch and Company Access: Use branch and company-level security to control which users can view or modify data for specific entities.

  3. Row-Level Security: Implement row-level security to restrict access to specific accounts or financial records based on user roles.

This way, even though accounts are shared, you can ensure that users only see and interact with the data relevant to their responsibilities.


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings