---
title: "Allowing duplicate SSN entries for when Allow Crossover is Disabled"
slug: "allowing-duplicate-ssn-entries-when-allowcrossover-is-disabled"
updated: 2026-05-22T05:56:19Z
published: 2026-05-22T05:56:19Z
canonical: "zenoplesupport.aqore.com/allowing-duplicate-ssn-entries-when-allowcrossover-is-disabled"
stale: true
---

> ## Documentation Index
> Fetch the complete documentation index at: https://zenoplesupport.aqore.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Allowing duplicate SSN entries for when Allow Crossover is Disabled

This feature introduces enhanced SSN validation logic in Zenople to ensure data integrity and privacy while supporting flexible record creation across multiple companies. The update addresses scenarios where duplicate SSNs may occur due to cross-company registrations and apply rules based on the **Allow Cross Over** setting.

### Functionality

**1. Feature Addition**

- **Location:** Applicant Portal, New Hire Portal, and Employee Registration workflows.
- This feature is based on the Allow Cross Over option property at company level where if a Company is selected at the Option Property, it is considered that Crossover has been enabled for that company.

**2. Behavior**

- **When Allow Cross Over is disabled for the Company**
  - The system **allows** creating a new record for the same SSN if the registration is for a different company or office.
  - No duplicate SSN error will be shown in this scenario.
- **When Allow Cross Over is enabled for the Company:**
  - The system **prevents** creating a new record with the same SSN across different companies.
  - Displays an error message: *“Duplicate SSN detected. Cross-company registration is not allowed.”*

**3. Applicability**

- Applies to **Applicant Portal**, **New Hire Portal**, and **Employee Information System (EIS)** modules.
- Excludes CRM and Back Office modules.

### Additional Notes

- Current SSN validation logic has been updated to respect the Allow Cross Over setting.
- No impact on existing records; changes apply only during new registrations.
- Compliance with SSN privacy regulations remains intact.