Skip to content
Hypamoon

For teams that run on Planday

Planday payroll checked before you export it

Planday's payroll checklist asks you to confirm six things before you create the payroll report: salary identifiers, a wage or salary for each employee, employee changes, salary codes, approved shifts and leave requests that are answered. Each one sits on its own page.

How it goes today

  1. Open the schedule and look for shifts that are not approved yet.
  2. Check the leave requests for the pay period one by one.
  3. Open employee profiles to confirm wage, salary and salary identifier.
  4. Export the payroll report and check it in a spreadsheet before sending it on.

How it can go

One list of what to fix before the pay run, two days ahead.

Two days before the period ends you get one list per department: shifts that are not approved, leave requests still waiting, employees with shifts but no wage, salary or salary identifier, shifts without a salary code, and employees whose details changed since the last pay run. Each line names the employee and the date, so you know where to look in Planday.

Say this in ChatGPT, Claude or Copilot

Your chat gets connected to Hypamoon first, with this request filled in. Planday works with a sign-in instead of a key: you sign in to Planday once to give access, never in the chat.

Your request

With Hypamoon, two days before each pay period ends, check our Planday data and email me one list per department: shifts not approved yet, leave requests still waiting, employees with shifts but no wage, salary or salary identifier, shifts without a salary code, and employees whose details changed since the last pay run. Name the employee and the date on each line.

An administrator creates an API app of your own in Planday under Settings, Integrations, API access, and authorises it once. Planday's help lists open API access on the Plus and Pro plans. It stays yours.