Importing historical payslips

Importing historical payslips

When you start using KAMI part-way through a tax year, import the payslips you already paid in your old system. KAMI then has the year-to-date wages, other payments, contributions and tax it needs to withhold tax correctly for the rest of the year and to produce complete year-end reports and certificates.

Where:

  • From a batch: More › Import payslips
  • Directly: Bulk Import / Export › Payslips

You need: the Payroll Processor (Edit & Calculate) right

Why it matters more than it looks

KAMI works out tax on a year-to-date basis. Without the earlier months, the first KAMI payslips are taxed as though nothing was earned before, and every later payslip inherits the wrong basis. Contributions with annual caps and year-end certificates have the same problem. In KAMI's words: "All historical payslips for current tax year must be imported to allow for accurate end-of-year tax reporting."

⚠️ If you go live mid-year without importing history, your first year-end will not reconcile and employees' certificates will understate their earnings. It is the migration step most often skipped and the most expensive to fix later.

Which one, when

You areDo this
Moving to KAMI mid-year from another payroll systemImport historical payslips
Recording a joiner's pay from a previous employerPrevious-employer income on their profile
Correcting tax on a payslip KAMI already producedThe Tax adjustment import, or Manual tax adjustments
Correcting any other KAMI payslipRecalculate it, or add an adjustment

Historical import is for payslips KAMI did not calculate. Do not use it to fix payslips it did.

Before You Start

Create a batch in KAMI for each past period. Every imported payslip goes into an existing batch, named by its Batch ID. The batch must belong to a batch cycle. Create it with + Create batch on the dashboard, using the old period's dates.

Copy each batch's ID. Open the batch and click the Batch ID badge in its header to copy it.

Reconcile the source data. Whatever you import becomes the year-to-date record, and errors carry through silently.

How to import

  1. Open the batch for the first past period and click More › Import payslips. Bulk Import / Export opens.
  2. In the Payslips section, click Get a sample template and download it.
  3. Fill in one row per employee per period: the employee ID, the Batch ID, and their wages, other payments, contributions, tax and total payable.
  4. To give an other payment a description, add a Details column next to it. Name it Details followed by the part of the other payment column after OP, copied exactly: for OP[Fixed Allowances]Rice subsidy, use Details[Fixed Allowances]Rice subsidy. Up to 255 characters. A Details column that matches no other payment column rejects the whole file; details for an empty or zero amount are ignored.
  5. Upload the file with Import.
  6. Check Import History for errors, fix the file and import again until it is clean.
  7. Open the batch and check a sample of payslips against the old system.
  8. Repeat for every past period of the tax year, then check the year-to-date totals.
⚠️ KAMI's warning: "Import of payslips shall OVERWRITE any existing payslips that overlap for such periods!" Importing a row replaces that employee's payslip in that batch, including one KAMI calculated.

What Happens Next

  • Each imported payslip is saved as Paid and marked Imported. The batch's status updates to match.
  • Imported payslips count towards year-to-date totals, annual tax estimation and contribution caps.
  • They appear in the year-end reports for the year they belong to.
  • Later KAMI payslips are calculated on a year-to-date basis that includes them.

Tips

  • Import before your first live payroll in KAMI. Importing afterwards means recalculating the live payslips so their tax uses the full year.
  • Reconcile totals before and after: gross, tax and contributions for the whole workforce. If KAMI's totals do not match the source, stop and find out why.
  • Check your highest earner. Tax brackets and contribution caps bite at the top, so a missing period shows there first.
  • Import whole periods only. A half-imported month looks complete and is worse than none.
  • Keep the source files. They are the evidence behind your first year-end in KAMI.

Troubleshooting / FAQ

Q: The import says the payroll does not exist. The Batch ID in the file is wrong, or the batch belongs to another company. Copy it again from the batch header.

Q: The import says the payroll has no batch cycle. Create the batch from a batch cycle on the dashboard, then use that batch's ID.

Q: The import says a Details column is not valid or matches no OP column. The part after Details must match an other payment column character for character, including case and spaces. Copy it from the other payment column's header.

Q: Tax on the first KAMI payslip looks wrong. Check that every earlier period of the tax year was imported. A missing month makes the year-to-date figure too low.

Q: Year-to-date figures do not match the old system. Reconcile period by period. A missing or partly imported period is the usual cause.

Q: Can we import after going live? Yes. Then recalculate the live payslips that are still Open or Pending so their tax uses the full year.

Q: Does this replace previous-employer income? No. Historical import is for your own company's payslips from another system. Previous-employer income is for pay a joiner earned elsewhere.

Related articles