We are looking at setting up multi-company. I want to ask the experts what best practices (or less pain points) for setting up the database’s. Would you recommend one database or have a separate database for each company?
1 Like
Kinetic is natively multi-company. and using it for that would gain you a lot of benefits, unless your companies are singularly individual and do not transact amongst themselves. Even if that’s true, the ability to control the Chart of accounts, suppliers/customers, and a number of other ‘code’ data across all of your companies form a single point of control - this is handled by the multi-company setup and background processes.
This set up would create a very homogeneous environment where every company used the same basis for operations - plus GL consolidations would almost be automatic. Plus, inter-company transactions such as PO/SO could be done automatically and there would only be one database to manage, even if you have multiple app servers servicing those companies.
I suggest you grab the Multi-Company technical reference for your version and do some reading.
We do this, and I would be glad to discuss it further with you.
3 Likes
FYI, you can create many companies in Kinetic WITHOUT the multi-company (multi-site) license.
If you do it that way, the companies are unable to communicate. But if that’s OK, it’s an option.
Sounds like you have already ruled out multiple sites? Just asking because someone always has to. 
2 Likes