Bulk Imports, All of Them
Every spreadsheet-in door in TriblockHR, what each one is for, and the habits that keep imports boring.
The import map
| Import | Use it for | Where |
|---|---|---|
| Hours / Allowances / Deductions into a pay run | This run only: commissions, one-off deductions, hours from a spreadsheet | Pay run → Import menu |
| Hours from a clock system | Recurring third-party clock exports (TimeForce, uAttend, Deputy…) that become timesheets | Time → Import Hours |
| Time-off balances | Migrations and year-start corrections, many employees at once | Balance Adjustments → Import Balances |
| Schedule shifts | A whole schedule's shifts from a filled template | Schedule → Import schedule |
| Bulk employee changes | Not a file import, but the same job: mass field changes via filters | People → Bulk Updates |
| Documents in bulk | Batch-uploading files against employees | Settings → Documents → Bulk Upload |
The habits that keep imports boring
- Always start from the downloaded template. Every import offers one; headers that don't match are the top cause of file-level rejections. Paste your data into the template rather than renaming your own columns.
- Plain numbers, real identifiers. No currency symbols or thousands separators in amount columns, and match employees by the identifier the template asks for — misspelled names and stale employee numbers are the top cause of row-level errors.
- Read the preview like it's the real thing. Every import previews before applying — valid-row counts, per-row errors with names and reasons. Nothing touches data until you apply, so cancel freely and fix the file.
- Know each import's blast radius before applying. Schedule import replaces all shifts in the schedule. Balance import warns it "cannot be undone in bulk". Pay-run imports recalculate the run. Bulk timesheets overwrite existing ones for the period. The preview tells you the counts; believe them.
- Reconcile counts after. Rows in file vs rows applied vs people you expected. The hours-import exception panel (missed punches) and the pay run's coverage numbers are your built-in checks.
One-off vs standing
Pay-run imports affect that run only. If the amount should recur every period, it belongs as a standing allowance or deduction on the employee — importing it monthly is the manual labor the standing setup exists to remove.
▶ Video placeholder
Import habits in practice (4 min)
Screen recording using the pay-run allowance import as the example: download template, paste data with one deliberate header typo and one bad amount, show both error classes in the preview, fix, apply, reconcile the counts. Close with the import map table as a slide.
Save as: how-to__bulk-imports__vid1.mp4