Summary

PayGlobal can import or export data to any application that supports flat file (ASCII text) format.

Synchronising data:

• Saves installation time spent entering data.
• Allows for complete third party integration.
• Ensures consistency when merging data between the PayGlobal host and remote sites.

ASCII files

ASCII files are text files that can be read without the aid of any software to transform or interpret the file's contents. An ASCII file contains only ASCII characters (for example, keyboard characters, the alpha-numeric characters and common keyboard symbols).

Import or 
Export from

Synchronisation allows data to be imported to or exported from either an entity table or a non-entity table (for example, a makeup tables like Employee Rates). This data can be imported to or exported from:

• All of your existing applications, including Precedent.
• Any other applications capable of flat file ASCII data import or export.
• Other PayGlobal WorkGroups or Host/Remote sites.

Function of Synchronisation

Synchronisation can be useful for:

• Converting data from another application during the initial PayGlobal system setup.
• Merging data between WorkGroups including the host and any remote sites.
• Using the PayGlobal HR module with other payroll systems.
• Exporting your data to be analysed or viewed in any other application capable of opening ASCII text files.

Synchronisation Process

Synchronisation involves the following steps:

1. Prepare the data.

   For Import, this involves exporting data from the source and converting it to a text-based, space delimited format.
   For Export, this involves identifying which tables and fields in PayGlobal are to be exported.

2. Create synchronisation tables.

   This can be done either manually or automatically, depending on whether an existing PayGlobal product is involved.

3. Initiate the Import or Export command. Check that the data has synchronised correctly.

Notes

When importing or exporting data PayGlobal relies on the existence of the required fields, as listed below.

Code field: For entity tables.

Record ID field: For non-entity tables.

By default if your synchronisation criteria does not contain a required field, PayGlobal will automatically search for and insert this when the Import or Export is run.

In the case of importing data from a non-entity table, if the import file does not contain the record ID column, then all records will be automatically inserted as new records in the non-entity table.

If the import file contains the record ID column then records will either be inserted or edited depending on the presence of an ID value. This means that if the record ID field in the import file is blank that record will be inserted.  If the record ID field is not blank this record will replace the corresponding record in the PayGlobal database.

Important: The record ID field is a system generated ID used by PayGlobal as a reference tool only. Do not, under any circumstances, edit this value or create a value of your own as this will result in data corruption.

Importing of Employee Status Codes during Synchronisation

Employee Status codes will be overridden on import if the following condition is met in a customer database:

The following Employee Status codes are all present : FULL, PART, TEMPFULL, TEMPPART, UTEMPFULL, CASUAL

In that case, when importing any data containing an Employee Status Code, (for example Employee data) then the following Employee Status code mappings will occur when creating or updating a record:

1. Imported status code starts with F - mapped to FULL
2. Imported status code starts with P - mapped to PART
3. Imported status code starts with T - mapped to TEMPFULL
4. Imported status code starts with U - mapped to UTEMPFULL
5. Imported status code starts with CF - mapped to CASUAL

These mappings will override whatever values are present in the import file.