SimpleVMS Multi-Vendor Mapping

SimpleVMS mapping ensures seamless data synchronization between SimpleVMS and AviontéBOLD by aligning jobs, contacts, companies, and skills across both platforms. Proper mapping configuration is essential for accurate job distribution, talent placement, and reporting.

This article walks you through the complete setup process, from locating the SimpleVMS Settings utility to configuring vendor relationships, company assignments, and field mappings. Whether you're setting up a new integration or managing multiple vendor accounts, these mappings control how information flows between your VMS and BOLD systems.

Locating SimpleVMS Settings

User Permissions Required: Users must have Utilities and SimpleVMS Admin access to view and configure these mappings.

• Utilities: Provides access to the Utilities page

• SimpleVMS Admin: Provides visibility to the SimpleVMS Settings tile and the ability to administer SimpleVMS settings

1. Click Account & Settings, then Utilities
   
2. Type 'SimpleVMS' in the search bar and click on the SimpleVMS Settings Utility
   

Vendor to Office Mapping

For organizations that manage multiple vendor accounts within SimpleVMS, the Vendor to Office Mapping feature enables you to map each SimpleVMS vendor account to specific BOLD offices.

User Permission Required: Users must have the appropriate permissions to configure vendor mappings.

• SimpleVMS Vendor Mapping Admin: Allows users to manage vendor mapping in SimpleVMS

Why Vendor Mapping Matters:

Some organizations operate multiple vendor accounts in SimpleVMS to support different business structures, such as separate Federal Employer Identification Numbers (FEINs) or distinct business divisions. BOLD's multi-vendor capability allows you to manage these vendor relationships within a single tenant while maintaining proper data segmentation.

Vendor mapping provides the following benefits:

• By having vendors mapped to BOLD offices, we can ensure users only have access to their vendor mapping, based on the user's office access.
• Gives the ability to have unique company, contact, job, and placement mappings per vendor.

To configure Vendor to Office Mapping:

1. From the SimpleVMS Settings utility, navigate to the Vendor to Office Mapping screen
2. Select a SimpleVMS vendor account from the list

3. Map the vendor to the appropriate BOLD office(s). 

   Note: You will only be able to map offices you have access to.
4. Repeat for each vendor account that needs to be configured

Company Mapping​

All VMS companies associated to the staffing agency vendor account in SimpleVMS, will be displayed in the Company Mapping screen. There are two approaches to mapping SimpleVMS companies to receive jobs in BOLD:

1. Direct Company Mapping: Map the VMS company directly to a BOLD company
2. Worksite-Only Mapping: Use "Map by Worksite" without mapping the parent VMS company

If needed, you can create a new BOLD company from this screen.

Default Job Owners must be configured for each mapped BOLD company.

Map by Worksite: This feature allows mapping individual worksites to different BOLD companies, and can be used in two ways:

• With parent VMS company mapped: When mapping worksites to BOLD companies, if the parent VMS company is also mapped to a BOLD company, then jobs associated to unmapped worksites will be created under the parent VMS company's mapped BOLD company.
• Without parent VMS company mapped: When mapping worksites to BOLD companies, if the parent VMS company is NOT mapped to a BOLD company, then jobs associated to unmapped worksites will not be created in BOLD.

Manually Create Placements:

• By checking "Manually Create Placements" - Once the talent is hired on the job in SimpleVMS, the talent's nomination stage would be updated to 'Hired' and then it would be the HCM user's responsibility to manually place the talent on the job in BOLD.
• By leaving unchecked - Once the talent is hired on the job in SimpleVMS, the talent's nomination stage would be updated to 'Hired', and then the talent would be automatically placed on the job in BOLD.

Job Template Override: This allows for job details coming from SimpleVMS, to be overridden by job details on a BOLD template, when jobs are created in BOLD.

• If a default job template at the company level is selected, and Job Template Override is checked, then the default template will be applied for newly created jobs for those companies.
• If no default job template is selected at the company level, and Job Template Override is checked, then the template where the template name exactly matches the job title of the job, will be applied for newly created jobs.

Contact Status Mapping

Each SimpleVMS manager status must be mapped to a BOLD contact status.​

Job Skill Mapping

Each SimpleVMS job skill must be mapped to a BOLD skill code.​

When a new SimpleVMS job is created in BOLD, the BOLD job will then have the mapped skill codes based on the job skill mapping configuration. This is vital for the purposes of job matching and distribution through 24/7.​

Job Type Mapping

Each SimpleVMS job type must be mapped to a BOLD job type.​

Job Status Mapping

Each SimpleVMS job status must be mapped to a BOLD job status.​

Placement End Reason Mapping

Each SimpleVMS worker end reason must be mapped to a BOLD placement end reason.​

Vendor Mapping Audit Log

View history of all of the changes on the SimpleVMS Vendor Mapping Page

1. Locate and click the Info Icon from the SimpleVMS Vendor Mapping to launch the Vendor Mapping Audit Log

2. Select a Vendor from the dropdown (Required)
3. Choose a User(s) from the dropdown (Required)
   • Default = All 
   • An Individual User can also be selected
4. Pick a Date Range from the dropdown (Required)
   • 30, 60, 90 Days
   • 6, 9 Months
   • 1 Year
5. Select the Mapping Type from the dropdown (Optional)
   • Default = All Mapping Types
   • Company Mapping
   • Contact Status Mapping
   • Job Skill Mapping, Job Type Mapping, Job Status Mapping
   • Placement End Reason Mapping
   • Worksite Mapping
6. Click Search to run the Audit

Viewing Audit History

When you click the Search button, you'll see a detailed history of all changes made to your SimpleVMS integration settings.

What you'll see:

The audit records show which user made changes and when. The most recent changes appear first, organized by date and user.

For each change, you'll see:

• Type of change: Whether a value was added, updated, or removed
• Where the change was made: The specific area of your integration settings, such as:
  • Vendor mapping
  • Company mapping (including manual placements and job template overrides)
  • Worksite mapping
  • Job type mapping
  • Job status mapping
  • Job skill mapping
  • Contact status mapping
  • Placement end reason mapping
• What changed: The specific field that was modified, showing the previous value and the new value in an "Old → New" format

This audit trail helps you track configuration changes over time and identify who made updates to your integration settings.