Match smarter. Work faster. Protect data.
Resource Matching helps you work confidently by making it easier to prevent duplicate records, keep candidate information accurate, and protect the integrity of every workflow you touch. Whether you’re adding resources as a supplier or reviewing candidates as part of a program office team, you get clear, timely information so you can make confident decisions and move forward without rework.
You benefit from this feature because it:
- Cuts down on fixing issues like duplicate profiles and mismatched IDs.
- Flags DNR candidates early to prevent compliance problems.
- Supports accurate tenure tracking and smoother downstream processes.
- Improves decision‑making by showing consistent identifiers and, where enabled, providing similarity scoring that highlights the most likely match.
Whether you're a supplier or part of a program office, Resource Matching helps you quickly confirm the right record, keep data accurate, and move work forward without interruption.
This topic provides technical details and terms to know.
Technical behaviors
- Beeline ID persistence: When a program office user selects a match, the Beeline ID associated with that individual is retained across suppliers and industries.
- Beeline ID uniqueness enforcement: Program settings may automatically append a number to maintain uniqueness when conflicts exist.
- Resource and Security User alignment: Linking through the dialog updates both records to maintain accurate onboarding and user identity.
Key terms to understand
As an individual is associated with requisitions, assignments and transactions processed through Enterprise, data points about them are collected and associated with their profile and database record. Identification information is stored in multiple records to help track and identify individuals as they move through different stages in your Enterprise VMS. These elements play a part in resource matching.
| Term | Description |
|---|---|
| Beeline ID | Aka Private ID or Resource ID A system-generated unique identifier used to match resources across records. The ID is based on the information provided by a supplier for the individual’s Initial Personal ID. The format is typically: “First Initial” + “Last Name” + “MMDD” or the last four digits of the government ID. The format can be set up to meet your program requirements. For example, your program might use a format of “MMDD” +the last four digits of the government ID. |
| Initial Personal ID | The resource's unique external identifier. It’s unique to each supplier and used to identify individuals in a supplier’s resource pool. The ID is manually added by a supplier or program office user when creating a Resource record. The format is typically MMDD OR ####; where MMDD are the digits for the month and day of birth and where #### are the last four digits of the government ID (social security number, National ID, or other). Your site may support a different format if required. The Initial Personal ID is used to generate a contractor’s Beeline ID. |
| Private ID | Also called Beeline ID or Resource ID. |
| Profile | The information that makes up the user in the Beeline platform, including their roles and user types in the Enterprise VMS. |
| Resource ID | Also called Beeline ID or Private ID. |
| Resource record | Created by suppliers; contains a contractor’s personal information, work history, and tenure. Resource records and profiles are created by suppliers for a specific industry when they add a resource to their resource pool. |
| Security User record | Created during onboarding; contains a contractor’s username and their Enterprise access settings. |
Troubleshooting
- Shared Security User record: Cancel the assignment → deactivate resource → recreate with a unique Beeline ID.
- Duplicate Beeline IDs: Update conflicting IDs to restore uniqueness.
- Overlapping offer and assignment dates: Update the Beeline ID on the newly submitted record.
Here are scenarios you may encounter as you progress through candidate processing and interact with the Resource Matching feature.
| Shared Security User Record | The result of a previously incorrectly matched resource. Cancel the assignment, deactivate the resource, and recreate the resource with a unique Beeline ID. |
|---|---|
| Duplicate Beeline ID Error | This can occur when a resource is onboarded, and the Beeline ID exactly matches the Beeline ID of two or more existing Security User records. Update the existing Security User records and make sure they don’t have the same Beeline IDs. |
| Beeline ID must be unique for a Resource | This can occur when you’re onboarding a resource, and you select a matching Resource record from the Matching Resources dialog that meets these criteria:
In the Resource record for the resource you’re onboarding, update the Beeline ID to match the Beeline ID of the existing Security User record. Or update the Beeline ID in the matching Security User record to match the Beeline ID in the Resource record for the resource you’re onboarding. |
| Offer dates overlap current Assignment Dates | This can occur when a new resource is submitted with an offer on a requisition has the same, exact Beeline ID as an existing contractor with an active assignment that overlaps the dates on the new requisition.
|
| Persona Clients, program office users, suppliers | Modules Contingent Staffing Services Procurement Resource Tracking Artificial Intelligence | Documentation release Beeline Enterprise | Q1 2026 | Feedback? Email us: |