Onboarding & Employee & Right To Work · How-to guide

Record P45 and starter declaration details

Choose the actual P45 or starter statement and record the leaving date when applicable.

Audience: HR administrators, authorised managers and payroll staffPermission: Human Resource Management: Create/Edit/ApproveModule v1.3.0
Exact navigation Admin Area → Human Resources → Employee Onboarding → Step 4
Code-backed scope These instructions follow Human Resource Management v1.3.0. Use only controls visible to your permission level and confirm the saved record or audit entry after every action.

What you need before you start

  • Access to Admin Area → Human Resources → Employee Onboarding → Step 4.
  • The Human Resource Management: Create/Edit/Approve capability or administrator access.
  • The correct employee, record, period or evidence reference before making a change.

How to do it

  1. Open Admin Area → Human Resources → Employee Onboarding → Step 4.
  2. Select the exact employee, period, document, request, rule, queue item or record shown by the screen.
  3. Complete every required field and review the field descriptions below before submitting.
  4. Check the current status and any warning, duplicate, eligibility or permission message.
  5. Click Record P45 and starter declaration details once and wait for the success or validation response.
  6. Return to the register and confirm the new status, reference, audit event and any generated file or downstream record.

Fields and options

Case referenceIdentifies the encrypted onboarding case and must be retained when resuming or reviewing it.
Current step and row versionControls multi-step progress and protects the case from stale overwrites.
Evidence and expiry valuesRecord only evidence actually checked, including dates, references, restrictions and review requirements.
Case statusDraft, submitted, changes requested, rejected and approved states determine which actions remain available.

What the module checks

  • Your assigned HRM capability must permit the action.
  • Required dates, amounts, references and reasons must pass server-side validation.
  • Approval, publishing, locking, voiding, withdrawal and deletion actions are allowed only from the states implemented by that workspace.
  • A success message is not a substitute for checking the register, audit log or generated file.

What happens next

The result remains available from Admin Area → Human Resources → Employee Onboarding → Step 4. Confirm its identifier, status, linked employee or period, dates and audit/activity record before relying on it operationally.

Troubleshooting

  • If the menu or action is missing, confirm the module is active and your HRM capability is assigned.
  • If validation fails, correct the exact field named in the message; do not bypass the rule in another workspace.
  • If a downstream email or automation does not run, check the related delivery/audit log and the host application cron or mail configuration.
HR data safety Restrict identity, right-to-work, payroll, bank, health, disciplinary and document information to authorised staff. Do not place protected values in free-text notes, email recipients or screenshots.
Browse connected topics: onboardingemployeeright to work