Skip to content
  • There are no suggestions because the search field is empty.

Import Payroll Data And Pay-Cycle Adjustments

What you can see and do here depends on the permission groups you belong to. Ask your admin to check your access in Set Up Roles and Permission Groups.

What It Does And Who It Is For

Plumm has different import routes for employee payroll records, historical payroll information and additions or deductions on a draft cycle. The templates are not interchangeable. Use the correct route and reconcile imported values before approving payroll.

Prerequisites

  • You have the required import and employee-data access.
  • The payroll owner has approved the data, period and import purpose.
  • Download the current template from the route you will use; do not reuse a differently named workbook.
  • Keep source files securely, check employee identifiers and remove template example rows before upload.

Permissions By Role

  • Super Admin: Check the organisation's setup and grant only the access needed for this area.
  • Admin: Carry out the administration steps below only when your permission group includes the relevant feature and people access.
  • Manager: Use team views only for the people and records your permissions allow. Being a manager does not automatically grant administration access.
  • User: Use your own records and assigned actions. Ask your admin if a required page or action is missing.

Admin: Import Employee Payroll Records

  1. Open Admin > Settings > Import.
  2. Use the relevant employee/profile import route. Older guides describe the Import Staff action followed by Import Payroll; the public Payroll Imports guide separates payslip, pay-rate, bonus and compensation imports. [TO VERIFY: the current menu labels and entry point for each employee payroll import.]
  3. Download that route's template.
  4. Complete only the intended fields using authoritative records and the required date format.
  5. Upload through the same import route and review validation errors before submitting.
  6. Reconcile successful and skipped/failed rows to the source file. Check a sample of employee records and financial totals afterwards.

Admin: Import Income Or Deductions Into A Draft

  1. Open the intended draft cycle using Start Pay Run or Continue Pay Run.
  2. Open the three-dot menu and select Import. The public Pay Cycle Import guide describes this menu as requiring Delete Payrun access. [TO VERIFY: the current permission gating; do not grant delete privileges solely to bypass an unavailable import action.]
  3. Download PayrollIncomeOrDeductionTemplate.xlsx from that route.
  4. Complete Email, PayCode and Amount; add Description for the business purpose.
  5. Upload the completed template and review each error before proceeding.
  6. Where an error row offers Skip, understand that skipping does not import that row. Retain a record of excluded rows.
  7. Submit only the reviewed rows, then check employee Income/Deductions lines, row counts and totals in the draft.
  8. Recalculate through the payroll owner's approved process where required and repeat the pre-approval checks.

Admin: Validate Before Retrying

  1. Check the employee identifier and pay-code match.
  2. Confirm amounts use valid numeric formats and dates use the selected format.
  3. Check whether a previous attempt imported any rows before uploading again.
  4. Correct only the intended records; do not repeat a full upload blindly when duplicates may result.

Settings And Options

  • Employee tax/bank details, pay rates, bonus, compensation and historical payslip data have different field sets.
  • Draft-cycle imports use pay-code additions/deductions, not a replacement tax-data template.
  • Workbooks are limited to 1,000 rows. Plumm rejects an empty/header-only workbook, example-only data and different sheet names. [TO VERIFY: these limits and validation messages on each current import route.]
  • A row can fail because the employee or pay code is not found, a required amount is blank or a value has an invalid format.

Limitations

  • Import validation is not a full payroll calculation or professional tax review.
  • Do not import into a completed run as though it were an editable draft.
  • Do not paste employee data into a public knowledge base, chat or troubleshooting screenshot.
  • Re-uploading is not a safe universal correction route; establish what the prior attempt changed first.

FAQs And Troubleshooting

Which Template Should I Use?

Download the template from the exact import route and period you intend to use. A profile payroll import is not a draft-cycle adjustment import.

What Happens To Skipped Rows?

They are excluded from that import. Track and resolve them separately; do not count them as successful records.

Why Is Paycode Not Found Showing?

Check that the code exists for the payroll location and matches the required template value.

Should I Re-Upload The Whole File After An Error?

First check whether any rows were imported. Reconcile counts and values before retrying to avoid duplication.