Separate company or process levels in exisiting company?

 4 Replies
 0 Subscribed to this topic
 226 Subscribed to this forum
Sort:
Author
Messages
abassett
New Member
Posts: 4
New Member
    We are adding 4 small "companies" to our exisiting Lawson population. We were planning to set up 1 new company (because that has been the practice) with 4 process levels, but I wonder if that makes sense. All 4 of these new groups are actually part of the existing Company 1 organization and each has a separate tax id.

    Any thoughts on pros/cons of creating/not creating a new company for this?

    Thanks for any input!
    John Henley
    Posts: 3353
      moving to HR forum...
      Thanks for using the LawsonGuru.com forums!
      John
      stephanie
      Veteran Member
      Posts: 330
      Veteran Member
        The answer depends on your own business practices - do you need to easily report all companies together? Although you can merge company data using Crystal, HR Writer, Add-Ins, etc., standard Lawson reports generally don't allow that. A bigger consideration - do your employees move between companies (term in one, get hired in the other), or work in both? If so, you'll be better served setting up process levels instead of companies. Except for a few codes, if you use multiple companies you'll need to set up positions, job codes, benefits, personnel actions, etc. etc. separately, which can be a maintenance nightmare. Since you can set up different tax IDs by PL, I've always been a fan of keeping one company instead of multiple ones.
        abassett
        New Member
        Posts: 4
        New Member
          Thanks so much Stephanie for your input - that is pretty much what I was thinking too.
          John-thanks for getting my message to the right place.
          MARCO3535
          Advanced Member
          Posts: 25
          Advanced Member
            Stephanie,


            My thinking exactly. My previous employer had a 2 company setup- instead of 1 company and 2 P/L .

            It was a reporting nightmare, as well as the inconsistencies in the dept code, pay codes, job codes, not to mention the headaches - when a current ee 'transfers' between companies - 'terming' in 1 company and 'hiring' into the other company.

            Eventually, we went to a 1 company setup, some prep work, lots of testing, but definitely worth it.

            Later

            Marco3535