Importing Leave Into Figgo

Background information

If you want, you can occasionally import past or future absences into Figgo to avoid doing it by hand. This operation is completed in the ‘Manage the schedule’ > ‘Import leaves’ module.

Important: you cannot cancel an import, so we recommend you try the import using your test database first.

Importing leave

Retrieve the import file template

Sign in to your test database.

The import file for leave is found in the ‘Import leaves’ tab. Simply click on ‘Upload template file’

mceclip0.png

Fill in the import file’s columns

Next, fill in the following information in the document for each employee:

EXCEL_KBYSXFwfX6.png

  • legalEntity: the employee’s legal entity
  • employeeNumber: the employee’s unique employee number for payroll
  • lastName: the employee’s surname
  • firstName: the first name
  • accountID: this is the code for the absence account in question. You can find it in Figgo > Configure > Accounts. For example, if the employee has leave planned on their 2018-2019 annual leave account, you must enter the code 1218 in the import file:

mceclip1.png

  • startDate: the first day of leave (DD/MM/YYYY format)
  • flagStartDate: indicate whether the leave began in the morning (AM) or afternoon (PM)
  • endDate: the last day of leave (DD/MM/YYYY format)
  • flagEndDate: indicate whether the leave ended in the morning (AM) or afternoon (PM)
  • isApproved: put ‘yes’ if the absence is approved and ‘no’ if not (mandatory for absences subject to approval, leave blank otherwise)

Testing the file

When you have finished filling out the import file, you can test the import. Simply drop your file into the field provided for this or upload it, then click on ‘Test file’.

mceclip2.png

This test phase will call your attention to any errors detected in the file. Such errors could be overlapping leave days for the same employee or unrecognised employee numbers; similarly, if you indicated leave on a Saturday and the account you want to import the leave to is configured in business days in Figgo, you will get this error message:

mceclip4.png

Once the file is corrected, you can test the import again.

Note: you can also click on ‘Ignore errors and continue’

Next, and before importing, Figgo will suggest recrediting the absence accounts in question during the import.

  • If you simply want to import a record of leaves but these were already deducted in your payroll, you can leave the box ticked:

mceclip5.png

  • If you import future leaves that should be deducted, you can untick this box so that account balances are modified accordingly.

Lastly, click on ‘Import absences’—that’s it, you’re done! You can verify leave in ‘View schedule’.

After the test database import, if you are happy with the leaves that appear in Figgo as well as employee balances, you can import this same file into your production database.

Page content

Was this article helpful?
0 out of 0 found this helpful