Storing the mapping for future use

In order to prevent the user re-entering mapping data on each upload it is a good idea to store the mapping for future use. It is advisable that the mapping is stored against the BrightPay organisationId/employerId. Storing against the organisationId/employerId will also help around the turn of the financial year.

Storing the default mapping against the organisationId/employerId makes sense as multiple users of the Timesheet application may process the data into BrightPay. Therefore, it is helpful to let a user load the last mapping (whether they set it up or not).

Below is an example of a mapping file:

• The TimeSheetEmployeeId is the Timesheet Employee id

• The BrightEmployeeId is the Employee.employeeId returned from the Payroll API

• The TimeSheetHourlyRate is the Timesheet application’s hourly rate

• The BrightHourlyRate is the HourlyRate.rateName returned from the Payroll API

{
"Employees": [
    {
        "TimeSheetEmployeeId": "1", 
        "BrightEmployeeId": "2d206d32-58f2-40d6-9e57-fa1bf6364772",
    },
    ...
    ...
    {
        "TimeSheetEmployeeId":"5",
        "BrightEmployeeId":"2b8f00da-aff8-49ec-adb6-65f1cd96dcdf",
        }
],
"HourlyRates": [
    {
        "TimeSheetHourlyRate":"Default Rate",
        "BrightHourlyRate":"Standard rate"
    },
    ...
    ...
    {
        "TimeSheetHourlyRate":"OT Rate 1",
        "BrightHourlyRate":"OT Standard"
    }
]
}