Employee import in BYTE: update many staff records from one file, with a preview
Changing bank details or managers for many people one by one takes time. BYTE updates staff records from a spreadsheet: each row is matched by employee number, a preview shows every change before anything is written, and a refused row gets its reason.
Last updated: 17 November 2026
What it covers
- The staff import page offers three options: add new staff, update staff already on file, and attach scans of documents.
- Each row is matched to a staff member by employee number. Only the number column is required.
- A blank cell changes nothing. A file leaves the fields it does not mention as they are; clearing a field is done on the employee page.
- The preview shows the old and the new value for each row. Unchanged rows are listed and not sent. Nothing is written before Import.
- Rows are sent one at a time, in order. A refused row gets its own reason, and the run carries on.
- When the file has bank columns, the pay and bank record is updated with the rest of the row.
- If a request gets no answer, the record is read again before anything is resent, so a change is not applied twice.
How it works
- Open the staff import page and choose Update staff on file.
- Upload the file. Each row is matched by its employee number.
- Check the preview: each change shows the old value and the new one.
- Import. Refused rows are listed with their reasons, and the rest are saved one at a time.
A worked example
A file of 12 staff rows: 10 rows change a bank account or a manager, one row has no change, and one row has an employee number that is not in the organisation. The figures are examples.
| Result | Rows | What happens |
|---|---|---|
| Updated | 10 | Saved, one row at a time |
| No change | 1 | Listed, not sent |
| Refused | 1 | Its reason is shown; the rest carry on |
The refused row carries its reason on the screen. The other eleven rows are unaffected.
At a glance
Built means the feature is in BYTE's current build. BYTE is coming soon, so ask us for the status of anything you need.
| Area | What BYTE does | Status |
|---|---|---|
| Modes | Add new staff, update staff already on file, or attach scans, on the same page | Built |
| Matching | Each row matched by employee number; only that column is required | Built |
| Blank cells | Change nothing; the fields a file does not mention stay as they are | Built |
| Preview | Old and new value for each row; nothing written before Import | Built |
| One row at a time | A refused row carries its reason; the run carries on | Built |
| Pay and bank | Updated with the row when the file has bank columns | Built |
Ask us before you decide
- Ask which staff details change most often, and in how many rows.
- Ask whether your staff already have employee numbers.
- Ask who in your team imports staff changes, and who checks the preview.
Questions about employee import in BYTE
Can I update staff already in BYTE from a file?
Yes. Choose Update staff on file. Each row is matched by employee number.
What must the file contain?
At least the employee number column. The other columns are optional, and a blank cell changes nothing.
Can a file clear a field?
Clearing a field is done on the employee page. A blank cell in the file leaves the field as it is.
Do I see the changes before they are saved?
Yes. The preview shows the old and the new value for each row. Nothing is written before you choose Import.
What happens to a row that is refused?
It is listed with its reason, and the other rows carry on.
Can I update bank details this way?
Yes, when the file has bank columns. The pay and bank record is updated with the rest of the row.