Skip to main content
Solved

Cross-Tenant Transactions


Forum|alt.badge.img
  • Varsity I
  • 20 replies

Hey everyone, 

 

We’re looking to onboard a customer with about 4-6 companies, each with their own chart of accounts. Likely, they’ll have to run on different tenants because of the chart of accounts difference. I’m looking into 6 tenants, each with each other as vendors. This means, they’ll be running cross-company transactions across tenants. Any easy way to go about this besides my vendor solution?

 

Thank you!

Best answer by jsheehan56

Nothing out of the box. Tenants are entirely separate databases with no crossover. This is an intentional design decision.

You could certainly have a series of export scenarios, import scenarios and windows macros that could satisfy the functionality that the built in Intercompany Document processing workflow acheive within a single Acumatica tenant, but I'd push back on the clients need for separate tenant databases and try to acheive this in a single tenant. Do they really need that or do they just want that because that is what they are used to?

 

Restriction groups for GL accounts can be tricky to implement and keep updated, but it can allow the functionality of having “separate GL Accounts” per company. 

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

6 replies

Laura02
Captain II
Forum|alt.badge.img+19
  • Captain II
  • 3135 replies
  • February 23, 2023

I think the customer has much to gain by creating a combined chart of accounts, having companies in one tenant, and using automatically balancing Inter-company entries.  One tenant is the easy way; many tenants is the difficult way, in my opinion.


Laura02
Captain II
Forum|alt.badge.img+19
  • Captain II
  • 3135 replies
  • February 23, 2023

Hello @gusl ,

I noticed another post on the same topic; did you already read this one?

 


Forum|alt.badge.img
  • Varsity II
  • 85 replies
  • Answer
  • February 23, 2023

Nothing out of the box. Tenants are entirely separate databases with no crossover. This is an intentional design decision.

You could certainly have a series of export scenarios, import scenarios and windows macros that could satisfy the functionality that the built in Intercompany Document processing workflow acheive within a single Acumatica tenant, but I'd push back on the clients need for separate tenant databases and try to acheive this in a single tenant. Do they really need that or do they just want that because that is what they are used to?

 

Restriction groups for GL accounts can be tricky to implement and keep updated, but it can allow the functionality of having “separate GL Accounts” per company. 


  • Freshman I
  • 2 replies
  • April 26, 2023

We have a customer with multiple companies that do completely different things. They cannot share a chart of accounts. Also, they are currently using an ERP that allows multiple companies with different charts, but still have intercompany so going to Acumatica would take away functionality. Is there any future for intercompany at the tenant level?


Doug Johnson
Community Manager
Forum|alt.badge.img+4
  • Acumatica VP, Product Management
  • 585 replies
  • April 26, 2023

@lyearty45 we plan to enhance inter-company capabilities within a single tenant. Across tenants, we support a consolidation process, but that is designed to consolidate period-level financials on a single set of reports. We recommend including all your companies inside a single tenant.

Some customers have written customer-specific import and export scenarios in each tenant to automate the process.


  • Freshman I
  • 2 replies
  • April 26, 2023

You already have intercompany within a single tenant. I found a third party that might work.


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