Importing loan data

If you are moving to KAMI with loans already running, importing them brings the outstanding balances and schedules across so repayment continues without a gap. It is a migration task, done once, and worth doing carefully.

Where: Benefits › Team loans › Import You need: benefits rights including loan creation, and the bulk data right

Before You Start

Reconcile the source data. Whatever you import becomes the debt of record. An outstanding balance imported wrongly is money you either over-collect or never collect.

Decide the loan type each imported loan belongs to. The type carries the terms, and imported loans need somewhere to sit.

Do it before the first payroll run in KAMI, so instalments start on schedule rather than being missed for a period.

The three checks an import can bypass

Import settings are configured per loan type, and they exist because historical loans often do not satisfy the rules you would apply to a new one:

Setting	Allows importing a loan where
Allow maturity beyond contract expiry	The loan runs past the employee's contract end date
Allow loan in probation period	The employee is still on probation
Allow loan without wage	The employee has no wage recorded

⚠️ These bypass real validations. They are appropriate for migrating history — the loan already exists and the employee is already repaying it. They are not a way to create loans you would otherwise refuse. Turn them on for the migration and consider turning them off afterwards.

How to import

Configure the import settings on the relevant loan type.
Prepare the file: one row per loan, with the employee, the type, the original amount, the outstanding balance, and the schedule detail.
Open Benefits › Team loans › Import and upload.
Read the validation output before committing.
Import.
Compare the imported count against your file — rows whose employee does not match are skipped, and the import still reports success for the rest.
Check a sample of loans: outstanding balance, instalment amount, next instalment date.

What Happens Next

Imported loans appear alongside natively created ones and are marked as imported.
Their schedules drive payroll deductions from the next payroll run, exactly like any other loan.
Outstanding balances appear in benefit reports and on final pay for leavers.

Tips

Reconcile the total outstanding before and after. The sum of imported balances must match your source system. If it does not, stop and find out why before running payroll.
Check the next instalment date on a sample. The commonest import error is a schedule that restarts from the beginning rather than continuing.
Import ten first. A column or date-format problem is obvious on ten and invisible on two hundred.
Tell employees their loans have moved. A deduction appearing from a new system without warning generates avoidable alarm.
Turn the bypass settings off after migrating, so new loans face the normal checks.

Troubleshooting / FAQ

Q: Some loans did not import. Their employee identifiers did not match. Compare the imported count against your file.

Q: A loan imported but the schedule looks wrong. Check the outstanding balance and remaining term in the source row — a schedule generated from the original amount rather than the balance will be too long.

Q: An import was rejected because the employee is on probation. Enable the probation bypass on that loan type for the migration.

Q: Deductions did not start. Check the loans are Live and that payroll was calculated after the import.

Q: Can we re-import to correct errors? Correct the affected loans directly rather than importing again — a second import risks duplicating them.