Multi-Company Features

1. Multi-Company Features TEAM SOFTWARE, INC.

2. Objectives • Primary desire – to share employees within a multi-company environment • Not overpay Payroll taxes • Calculate overtime correctly • Share Chart of Accounts • Separate financials • Consolidated financials

3. Primary Ownership Rules • An employee is owned by one Company • A Job is owned by one Company • A bank account is owned by one Company • An inventory warehouse is owned by one Company • An accounts payable invoice transaction is owned by one Company

4. Secondary Ownership Rules • A fixed asset is owned by one Company (via the Primary Job) • An accounts receivable invoice transaction is owned by one Company (via the Service Location Job) • A transaction for a deposit to the bank is owned by one Company (via the selected bank account)

5. Secondary Ownership Rules - Continued • An accounts payable payment is owned by one Company (via the selected bank account) • A payroll check payment transaction is owned by one Company (via the selected bank account of the batch) • A labor distribution transaction is owned by one Company (via the selected Timekeeping Job)

6. Secondary Ownership Rules - Continued • An other compensation transaction is owned by one Company (via the selected Job) • An other deduction transaction is owned by one Company (via the selected Job) • An inventory transaction is owned by one Company (via the selected warehouse)

7. Secondary Ownership Rules - Continued • An adjusting journal entry is NOT owned by one Company; rather the individual distribution rows are associated to a Company (via the selected Job)

8. This is how you set up a Company in the system. Note that the “Balance Sheet Job Number” is usually set to be the same as the “Company Number”.

9. An employee is owned by one Company always

10. A Job is owned by one Company always

11. A bank account is owned by one Company always

12. A warehouse is owned by one Company always

13. An accounts payable liability is explicitly set to one Company. Note in the GL Distribution grid that other companies can be allocated

14. A Fixed Asset is owned by one Company via the Job Number. The Accumulated Depreciation each month will be given to this Company. Note you can still allocate depreciation to multiple Jobs and if those Jobs belong to different companies the system will create a due to / due from transaction automatically.

15. On the GL Distribution tab of an AR Invoice you can overwrite and edit the distribution to include Jobs belonging to companies differing from the Service Location Company on the General tab.

16. A deposit is owned by one Company. The Company Number is validated to the GL Cash Account to avoid posting to the wrong Company. If a paid invoice belongs to Company #2 and the deposit is made to a cash account belonging to Company #1; then a Due to / Due From transaction is automatically created.

17. At the time the checks are created the Company # and the GL Cash Account are identified. If one Company is paying an invoice for another Company, then a Due To / Due From transaction is automatically created.

18. Another example of an Accounts Payable payment. This shows how the entire batch is selected and paid. You can pay for invoices for another Company. Note on the next slide you can process a batch of invoices for only one Company.

19. When processing a payment batch you can limit it to one Company.

20. When you print payroll checks you select the Company # and the GL Cash Account #; both are validated by the system together, so that you cannot post payments for a checking account to the wrong Company. Payments made for another Company’s employee will automatically create a Due To / Due From transaction.

21. A singular Company’s employees can be selected for a payroll batch run. If the employee works for another Company, then a Due To / Due From transaction is automatically created.

22. This is an example of an employee working for multiple different Jobs. The wages are automatically distributed to the appropriate Company and Due To / Due From transactions will be created.

23. This is an example of an employee set up within Company 4, but the Other Compensations are being charged to different companies (via the Job Numbers). The appropriate Due To / Due From transactions are automatically created.

24. This is an example of an employee set up within Company 1, but the Other Deductions are being charged to different companies (via the Job Numbers). The appropriate Due To / Due From transactions are automatically created.

25. This is an example of an Inventory Usage transaction for a warehouse owned by Company #1, but the Job # belongs to Company #2.

26. In adjusting entries the Company is determined by the individual rows of a distribution grid.

27. This is another example of a journal entry BEFORE the update to the general ledger. On the next slide you will see how it differs AFTER the update to the general ledger has been completed.

28. After the posting to the general ledger the journal entry now includes the needed intercompany Due To / Take From entries.

29. Sharing Rules - Pick from List • User Security • Vendors • Customers • Chart of Accounts • Inventory Items

30. Users can be limited to access only certain companies information.

31. Vendors can be limited to use within certain companies.

32. Customers can be limited to use within certain companies.

33. Chart of Accounts can be limited to use within certain companies. In this example, the selected row (Other Misc Receivables is limited to be used in Companies 2 and 3).

34. Inventory Items can be limited to use within certain companies.

35. Financial Statements • Pick from List for Companies • More Flexibility • Automatic Consolidation • Profit and Loss Statements • Balance Sheets

36. Certain companies can be picked.

37. By selecting this check box a consolidated total will print for companies one and two.