Separate COA or Restrict GL Account Access by Branch/Company

Hello, 

Version 2024 R2 provides only one Chart of Accounts per tenant . Companies and Branches in one tenant share the same COA. 

Restriction Groups (also called Line-Level Security) may be used to connect Companies and Branches to the Accounts they are allowed to use in posting. Conversely, it’s also possible to hide accounts that each Company or Branch may not use from each Company and Branch. 
 

The upside to Restriction Groups is reducing posting errors and being able to share one COA and one tenant. The downside to Restriction Groups is, they require ongoing maintenance when new accounts are added to the COA. Best practices include limiting the number of staff who may add new Account and making sure they are trained to alter Restriction Groups after each Account addition.

Laura

Hi Laura,

Thank you for your input. While Restriction Groups by GL Account provide robust user-level access control, they do not prevent system configurations or automated processes from posting to these accounts.

The type of control I am looking for is one that ensures a specific GL Account cannot be part of a particular company's COA. This would provide a stronger layer of separation, ensuring that certain accounts are completely excluded from the scope of a specified company’s operations, rather than relying on user access restrictions alone.

Best regards,

Wilson

Hello ​@wilson71 

Is this helpful to your concern?

Restrict Visibility of GL Account and Subaccount by Company/Branch | Community

Did you vote for your idea in the thread below?  Please add the reasons, your specific Use Case explaining why Restriction Groups are not strong enough protection for your company.

Laura

I’m not sure what I clicked, but the solution provided doesn’t address my question. It’s the same solution Laura shared earlier. The suggested solution only restricts user access to GL accounts, which is primarily useful for limiting access to sensitive information. However, it doesn’t achieve the separation of GL accounts needed to create distinct COAs for different companies, in the same tenant

Kind regards

Wilson

Hello ​@wilson71 ,

​@Chris Hackett , Community Manager, or an Acumatica Moderator will be in later and will Un-select the Best Answer for you.

Once the accidental Best Answer is corrected, your thread will return to the Unanswered (Help Others) list for additional input from community members.

Laura

Hi ​@wilson71 were you able to find a solution? Thank you!

While each mindset of centralized or company specific CoA provide their advantages and disadvantages, for group of companies requiring consolidation, centralized CoA works best. This is a fundamental design change and my personal thoughts is that Acumatica cannot and will never go the route of setting up multiple CoA. I personally have worked with both types of ERPs, and centralized CoA is my favorite as Acumatica does. When each company sets up its own CoA like what MS D365 does, and you have multiple companies, it is really a nightmare. I have experienced it. Centralized CoA along with the security is best practice in my opinion.