Importing leave data
When you move to KAMI mid-year, people arrive with leave already earned and leave already taken. Two imports bring that across. Get them wrong and the same days are counted twice, so read how balances are calculated before you fill in a template.
Where: Settings › Bulk Data › Import / Export
You need: the Bulk Data right
Two different imports
| Import | What it loads | What it does to the balance |
|---|---|---|
| Leave Balances | Carry over from the previous year, and manual additions or deductions | Adds or deducts the figure in each row |
| Leave Events | Leave already taken, with dates | Creates approved leave, which is deducted from the balance |
Leave Balances does not set a balance. Each row is an addition or deduction on top of what KAMI has calculated. Awarded leave is applied automatically from your leave policies, so do not import it as well.
How KAMI adds it up
A balance is awards from the leave policy, plus Leave Balances rows, minus leave taken. Each employee's Leave Policy Automation Date decides what counts:
- Policy awards start from that date.
- Leave Balances rows dated before it are ignored.
- Leave events dated before it appear in KAMI but are not deducted.
Before You Start
- Create the leave types and leave policies first. A row naming a leave type that does not exist fails.
- Check each employee's Leave Policy Automation Date. It decides which rows count, as above.
- Choose one source for each day, so nothing counts twice:
- If you import leave events dated on or after the automation date, those days are deducted. Do not also deduct them in a Leave Balances figure. - If your Leave Balances figure includes days earned after the automation date, KAMI awards those days again from the policy.
- Check the EmployeeID column. Rows are matched on EmployeeID.
⚠️ One bad row rejects the whole file. If any row has an error, such as an unknown EmployeeID or leave type, nothing in that file is imported. The result email lists the row numbers. Fix them and import again.
How to import
- Open Settings › Bulk Data › Import / Export.
- Choose Leave Balances or Leave Events.
- Select Get a sample template. It downloads as an Excel file with one example row.
- Fill it in, following the template's columns exactly. Each column is explained below.
- Save it as a CSV file. The upload accepts CSV only.
- For Leave Events, choose Append or Overwrite. Leave Balances is always append.
- Select Browse file, choose your CSV file, then select Import.
- Wait for the result. KAMI imports in the background, then sends you a notification and an email. The email lists any rejected rows and skipped rows.
- To check past imports, select Import History at the top of the page.

Append skips a row that overlaps existing approved leave or a pending leave request. Overwrite cancels the overlapping leave and pending requests, and replaces them.
⚠️ Importing the same Leave Balances file twice adds the days twice. It never overwrites. To undo a row, import or enter the opposite deduction.
What Happens Next
- Imported rows show in the Time Off Balances report. See Leave balances and accrual.
- Imported leave events are approved straight away, with no approval step, and appear on the team calendar.
- Import History shows each import with In Progress, Success, Failed or Partial Success, who imported it, when, and the file. The row errors are in the email, not on this page.
- Accrual carries on from the leave policy at the leave type's interval.
Tips
- Import a small group first. Ten people you can check by hand will surface a template or identifier problem that four hundred will only hide.
- Reconcile a sample deliberately. Pick a long-serving employee, a new joiner, someone in probation, someone who has taken a lot of leave and someone who has taken none. Check each against your old system.
- Do it before the first payroll run in KAMI, not after. Leave affects pay.
- Keep the source file. When someone disputes a balance later, it shows where the opening number came from.
Leave Balances columns
| Column | What to enter |
|---|---|
| EmployeeID | The employee's ID in KAMI. Required. |
| Employee Name | For your reference only. KAMI ignores it. |
| Activity | The leave type, spelled as in KAMI. Capitals do not matter. Required. |
| Addition/Deduction | Days to add, or a negative number to deduct, such as -2. Required. |
| Notes | Optional. Shown as the comment on the adjustment. |
| Date | The date the row applies from. Use your company's date format or YYYY-MM-DD. If empty, the row is dated the day you import. |
| Carryover | TRUE for days carried over from the previous leave year. Leave blank for a normal addition or deduction. |
Carryover rows are treated as days carried into the employee's first leave year in KAMI, so they follow the leave type's carry-over expiry. Like every row, they count only if dated on or after the Leave Policy Automation Date.
Leave Events columns
| Column | What to enter |
|---|---|
| EmployeeID | The employee's ID in KAMI. Required. |
| Employee Name | For your reference only. KAMI ignores it. |
| Activity Name | The leave type, with exactly the spelling and capitals used in KAMI. Required. |
| Period | Full day, Half day, Partial day or Range. Required. |
| Start Date | The first day of leave. Required. |
| End Date | The last day. If empty, it is the same as Start Date. It cannot be before Start Date. |
| Start Time / End Time | HH:MM, such as 08:00. Fill in both or neither. Required for Partial day. Not allowed with Range. The leave can be at most 23 hours. |
| Length | Days to deduct, from 0.1 to 365. Required. KAMI deducts this figure as given and does not recount rest days or holidays. |
| Description / Comment | Optional notes saved on the leave. |
Troubleshooting / FAQ
Q: Nothing was imported. A row had an error, so the whole file was rejected. The email for that import lists each error by row number.
Q: Some leave events are missing after an Append import. They overlapped leave that was already there, so they were skipped. The email lists the skipped rows. Import them again with Overwrite if the new rows should replace the old ones.
Q: Balances are too high. Check whether your Leave Balances figures include days KAMI also awards from the policy after the automation date. Correct them with a deduction.
Q: Balances are too low. Check whether leave was deducted twice, once inside a Leave Balances figure and again as an imported leave event.
Q: An imported row made no difference to the balance. Check its date against the employee's Leave Policy Automation Date. Earlier rows are not counted.
Q: Imported leave does not show on the calendar. Leave Balances rows do not create calendar entries. Only Leave Events does.
Q: Can I export leave balances from Bulk Data? No. Leave Balances and Leave Events are import only. To download balances, export the Time Off Balances report.