Fix matching errors quickly and restore clean, accurate data.
Even with careful review, Resource Matching issues can occur and often require manual correction. These issues typically appear as system errors or unexpected behavior after a match is selected or a candidate is processed.
✅ Fix issues quickly and validate data to keep your program accurate and compliant. Use this guide to identify the issue and take the correct action.
Want to prevent this next time? See: Avoid common mistakes
Why this matters
Unresolved issues can:
- Break data consistency across records
- Impact assignments, invoicing, and reporting
- Create duplicate or conflicting IDs
- Require time-consuming manual fixes
✅ Resolve issues quickly to keep workflows moving.
Start here: identify the issue
To help prevent identity and Beeline ID issues:
- Always review potential matches before proceeding.
- Confirm identity using multiple identity signals.
- Do not rely solely on skills, experience, or resume similarity.
- Preserve existing Beeline IDs when linking records that represent the same individual.
- Review duplicate and conflict warnings carefully before continuing.
✅ Correctly maintaining Beeline IDs, Resource Records, and Security User Records helps preserve identity continuity and reduces downstream onboarding, reporting, and access-management issues.
Common errors at a glance
| Issue | What it means |
|---|---|
| Duplicate Beeline ID error | Multiple records share the same identifier |
| Beeline ID must be unique for a Resource | Resource and Security User records are misaligned |
| Shared Security User record | Incorrect match linked two profiles |
| Offer dates overlap | Two records with the same ID have overlapping assignments |
Resolve each issue
🔷 Duplicate Beeline ID error
At-a-glance
| Category | Details |
|---|---|
| What you see | Error indicating the Beeline ID already exists |
| Why it happens | Multiple records use the same ID |
| Impact | The system cannot uniquely identify the resource |
Who does what
| Role | Responsibility |
|---|---|
| Program office user | Correct duplicate IDs across records |
| Supplier | Submit resources using the correct or unique ID |
Resolve the issue
Program office users
- Locate all records using the duplicate Beeline ID
- Identify which record is correct
- Update incorrect record(s) with a unique Beeline ID
- Save and continue the workflow
Suppliers
- Review the submitted resource
- Confirm whether the resource already exists
- If duplicate: use the existing record
- If new: update to a unique Beeline ID
Result
Each resource has a unique Beeline ID, and processing can continue.
🔷 Beeline ID must be unique for a Resource
At-a-glance
| Category | Details |
|---|---|
| What you see | System blocks onboarding due to ID conflict |
| Why it happens | Resource and Security User records have different IDs |
| Impact | Records cannot be linked correctly |
Who does what
| Role | Responsibility |
|---|---|
| Program office user | Align IDs across records |
| Supplier | Ensure correct record is used or ID is unique |
Resolve the issue
Program office users
- Locate the existing Security User record
- Compare the Beeline ID with the Resource record
- Determine the correct ID
- Update one record so both match
- Save and continue
Suppliers
- Confirm whether the resource already exists
- If yes: resubmit using the existing record
- If no: submit with a unique Beeline ID
Result
The Resource and Security User records share a consistent Beeline ID.
🔷 Shared Security User record
At-a-glance
| Category | Details |
|---|---|
| What you see | Multiple resources linked to the same user/account. You may also notice unexpected assignment history, user-account conflicts, or worker information appearing on the wrong record.
Symptoms may include:
|
| Why it happens | Incorrect matching decisions or identifier conflicts can cause multiple resources to become associated with the same user account. |
| Impact | Assignment history and data are merged incorrectly |
Who does what
| Role | Responsibility |
|---|---|
| Program office user | Perform full correction and rebuild record |
| Supplier | Support with correct data if needed |
Resolve the issue
Program office users
- Locate the affected assignment
- Cancel the assignment
- If timesheets exist:
- Set them to Not Submitted
- Go to Resource Pool
- Delete the incorrect Resource record
- Recreate the resource with correct identifiers
- Re-onboard the resource
Suppliers
- Notify the program office
- Do not reuse the incorrect record
- Provide correct resource details if resubmission is required
Result
Each resource has a separate, accurate record and user association.
🔷 Offer dates overlap current assignment dates
At-a-glance
| Category | Details |
|---|---|
| What you see | Error indicating overlapping assignment dates |
| Why it happens | Same Beeline ID used across active assignments |
| Impact | Assignment conflict prevents processing |
Who does what
| Role | Responsibility |
|---|---|
| Program office user | Resolve ID conflict across assignments |
| Supplier | Confirm correct resource identification |
Resolve the issue
Program office users
- Review both assignments
- Confirm whether they represent the same individual
- If not:
- Update the Beeline ID for the new resource
- Save and continue
Suppliers
- Confirm whether the resource is new or existing
- If new: provide a unique Beeline ID
- If existing: reuse the correct record
Result
Assignments are tied to the correct unique resource, with no overlap.
🔷 When to escalate
| Situation | Action |
|---|---|
| You cannot determine the correct record | Contact program administrator |
| Multiple records conflict across systems | Request data audit |
| Issue persists after updates | Contact support |
| Duplicate-ID or matching issues continue after records are corrected | Contact your system administrator to review Resource Matching configuration settings. |
Identity continuity behaviors
Resource Matching helps maintain identity continuity across suppliers, assignments, onboarding activities, and user records. Understanding these behaviors can help explain why certain matching outcomes occur and how identity relationships are preserved across the platform.
Beeline ID persistence
When records are correctly matched, Resource Matching helps preserve the existing Beeline ID associated with the individual.
Maintaining the same Beeline ID across suppliers, assignments, and workflows helps support:
- Accurate tenure tracking
- Consistent reporting
- Identity continuity across program activities
- Reuse of existing resource records when appropriate
If an expected Beeline ID is not retained, review the selected match and associated identity information to confirm that the correct records were linked.
Beeline ID uniqueness enforcement
Beeline IDs are intended to uniquely identify individuals within the program.
Depending on program configuration, uniqueness controls may be applied when potential identifier conflicts are detected. In some cases, the system may append an additional value to maintain uniqueness when a new resource is added and an existing identifier combination already exists.
These controls help:
- Prevent duplicate identity records
- Reduce identifier conflicts
- Maintain accurate resource tracking across workflows
If you encounter a Beeline ID-related error, review existing records for potential duplicates or conflicting identifiers.
Resource and Security User alignment
Resource Matching helps maintain alignment between:
- Resource Records, which contain workforce identity, assignment, and tenure information
- Security User Records, which contain usernames and access-management information
Accurate matching helps ensure that:
- User access remains associated with the correct individual
- Onboarding information remains accurate
- Identity relationships remain consistent across workflows
- Shared-user-record scenarios are minimized
When records become misaligned, onboarding, access-management, and reporting issues can occur. Reviewing match decisions carefully helps maintain accurate relationships between Resource Records and Security User Records.
Important
Identity continuity depends on consistent identifiers and accurate matching decisions.
To reduce identity-management issues:
- Review potential matches carefully before proceeding
- Confirm identity using multiple identity signals
- Preserve existing identity relationships whenever appropriate
- Investigate duplicate or conflicting identifier warnings before continuing
✅ Correctly maintaining Beeline IDs, Resource Records, and Security User Records helps reduce downstream onboarding, reporting, access-management, and data-quality issues.
🔷 Prevent future issues
| Best practice | Why it helps |
|---|---|
| Keep worker records up to date | Reduces matching errors caused by outdated or incomplete information. |
| Verify unique identifiers before onboarding | Helps prevent duplicate records and incorrect worker matches. |
| Review potential matches before creating new records | Avoids creating duplicate worker profiles when a matching record already exists. |
| Follow username entry procedures | Ensures Resource Matching validation runs correctly and helps prevent duplicate records. |
| Follow established procedures when creating or managing usernames | Inconsistent username handling can contribute to identity and matching issues that require manual correction |
| Persona Clients, program office users, suppliers | Modules Artificial Intelligence Contingent Staffing Services Procurement Resource Tracking | Documentation release Beeline Enterprise | Q2 2026 | Feedback? Email us: |