Integrating [email protected] Software with Infor’s SunSystems

Introduction

[email protected]’s Integration Framework enables users of [email protected], [email protected] and [email protected] to seamlessly exchange data with Infor’s SunSystems Financial Software.

[email protected] is the leading provider of Time Recording and Expense Management solutions for SunSystems and over the last 15 years we have integrated our solutions with hundreds of SunSystems implementations around the world.

 

 

SunSystems Versions

Irrespective of the version of SunSystems being used, [email protected] software allows deep level integration which can be customised to suit clients specific transactional and reference data requirements.

We have developed tools and processes which provide robust and scaleable integration options for SunSystems users and enable information flows which support management information needs, financial reporting requirements and statutory & regulatory obligations.

Transaction Exports

The [email protected] Ledger Export module selects transactions and fields from the [email protected] ledgers and formats them for import into SunSystems.

While the process is seamless and fast, the following notes provide some background information on the many automated steps which take place as part of this process, including:

  • The selection of transactions for export.
  • The selection of fields for export from the selected transactions.
  • The renaming of fields.
  • The preparation of transactions for import into SunSystems.

This last step, the preparation of transactions for import into SunSystems, itself involves many steps, including:

  • The creation of at least two, and often three, rows of a journal from one [email protected] ledger transaction. For example:
    • In the case of an invoice, a debtor row, a tax row and a revenue row.
    • In the case of an expense claim, a creditor row, a tax row and a nominal expense row.
  • The summarising of values for a particular row (for example, an invoice journal will usually contain just one debit to the debtor account, a credit for each tax category to the tax account, and as any revenue credits to the revenue account to populate the analytical fields that are required for management reporting from the general ledger, such as employee, project, profit centre, etc.).
  • The elimination from each type of debit or credit of unnecessary fields.
  • The insertion of additional field values not present in [email protected], such as a Journal Type.
  • The formatting of a file. This may be a text file, or an XML file or various other types of file such as SunSystems NDF or SAF.