Validate Employee Record Centre changes | Pixie CRM Help Centre Canonical: https://pixiecrm.com/help-centre/validate-employee-record-centre-changes Publisher: Pixie Technologies LLC Employee Record Centre (https://pixiecrm.com/help-centre/topic/employee-record-centre) & Employee Record Approvals (https://pixiecrm.com/help-centre/topic/employee-record-approvals) · How-to guide Validate Employee Record Centre changes Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on. This guide explains every cross-field and uniqueness validation applied before a v1.3.0 employee amendment is accepted. Audience: HR administrators and authorised managers; Permission: Human Resource Management: View; Module v1.3.0; Where to go Admin Area → Human Resources → Employee Record Centre → Select employee → Current Record 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. Before you start - Access to Admin Area → Human Resources → Employee Record Centre → Select employee → Current Record. - The Human Resource Management: View capability or administrator access. - The correct employee, record, period or authorised evidence. Follow these steps - Complete the intended fields. - Check required names and HR employee number. - Check email, date and number formats. - Check all paired date ranges and student term dates. - Check right-to-work expiry and non-negative hours/pay values. - Enter an amendment reason and save. - Correct the exact field named in any validation response. Fields and options RequiredFirst name, last name and HR employee number. Unique employee numberMust not exist on another profile or master employee. Unique emailPersonal and work email cannot be linked to another profile. Non-negative numbersHours, salary, rate, holiday, visa limit and external hours must be zero or above. Verified RTWCannot have a permission expiry date in the past. Date pairsFixed-term/probation end after start; permission/course end after start. Student termsEach of 12 term pairs must be complete and end on/after start. Date of birthCannot be in the future. What the module checks - The action is permission-aware. - Required values must pass the exact server-side validation. - Verify the saved record and audit/log result. What happens next The module saves the permitted change and records the resulting status, version, delivery or synchronisation evidence. Reopen the relevant register and verify it. Troubleshooting - If the control is missing, confirm the required HRM permission and module version 1.3.0. - If saving fails, correct the exact field or state named in the validation message. - If an email/automation is missing, review the module delivery/audit log and host cron/mail settings. 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: employee record centre (https://pixiecrm.com/help-centre/topic/employee-record-centre)employee record approvals (https://pixiecrm.com/help-centre/topic/employee-record-approvals) Related guides Use the Employee Record Centre (https://pixiecrm.com/help-centre/use-the-employee-record-centre)Complete Governance & Declarations employee fields (https://pixiecrm.com/help-centre/complete-governance-and-declarations-employee-fields)Understand sensitive Employee Record Centre fields (https://pixiecrm.com/help-centre/understand-sensitive-employee-record-fields)