Working With Multiple Business Units In SunSystems

Introduction

One of the most common requirements for users of systems@work Software is the need to integrate our Expense Management Software – expense@work, Time Recording Software – time@work and Workflow Software – forms@work with multiple Business Units within SunSystems.

There are a number of ways in which this is achieved depending on the specific needs of each client but most commonly the integration is managed through a combination of:

  1. Reference Data – (using Employee, Project and Client Analysis Definitions).
  2. Forms Design (using Activity Analysis Definitions).
  3. Transaction Data (using multiple Ledger Export Profiles).

Within systems@work software, Employees, Projects and Clients can be allocated to SunSystems Business Units. For example we might specify the BU that an Employee belongs to:

 

 

In addition, forms and timesheets can be configured to capture a Business Unit if this is something that is specific to a particular transaction, (for example if an employee from one BU is incurring a cost which needs to be recharged to a different Business Unit.

When it comes to exchanging data with SunSystems, systems@work software can be configured with a variety of export profiles which can filter and target the data held in expense@work, time@work and forms@work so that the correct transactions are posted to the appropriate BU within SunSystems. For example in the screenshot below you can see that there is a separate export routine defined for each of the 3 BU’s and also an export profile to handle some intercompany transactions.