General instructions and tips on preparing import files can be found on the Docs → Account → File imports page of the support centre.
During the run of a leave sync file, matches will be found based on a combination of staff, type, start date and end date. Existing leave requests that are not matched exactly will be removed (when running in ‘delete’ mode). Matches found with a new status will have their status updated in the system.
|Column||Field Name||Data Type||Length Limit||Example||Description|
|A||Staff*||Reference||20||ST10001||The staff this leave is attached to. Must match the ID of an existing non-deleted staff.|
|B||Type*||Reference||20||LT10001||The type of leave. Must match the ID of a non-deleted leave type that is turned on for the staff within their award.|
|C||Start date*||String||2014-12-06||The first date the leave request affects. Enter in YYYY-MM-DD format.|
|D||End date*||String||2014-12-09||If the leave request spans multiple days, select the last day it affects. If it is a single day, this will be the same as the start date. Enter in YYYY-MM-DD format.|
|E||Hours||String||4,3||7.5||The total hours (per day) of the leave. This field will be ignored if the leave is mutli-day.|
|F||Manager notes||Long String||Fine with me if we can get one of the others to take on some extra hours.||A notes field only managers can see and edit.|
|G||Status||String||Approved||The current status of the leave.If the leave is 'Pending' approval, it can be changed to 'Approved' or 'Rejected'.|
* Mandatory 1 Enterprise Only