Workday, Fieldglass, and Coupa data disagreed; mapped categories and renewal approvals created one contingent view

Overview

A pharmaceutical company could not see total contingent labor usage because vendor records sat in the Vendor Management System (VMS), worker details lived in Workday, and spend flowed through Procure?to?Pay with different categories. Renewals were approved by email, suppliers onboarded off?cycle, and leaders received conflicting reports. Intelligex integrated the VMS with Workday and the Procure?to?Pay platform, standardized contingent categories and cost centers, and added an approval workflow for extensions and renewals. Managers worked from a single view of contingent headcount and spend, renewals followed a governed path, and leadership discussed capacity and risk instead of debating data—while Workday, the VMS, and the purchasing tools remained in place.

Client Profile

• Industry: Pharmaceuticals (R&D, clinical, manufacturing, and commercial)
• Company size (range): Multi?region enterprise with centralized HR and distributed procurement
• Stage: Workday for employees and contingent worker objects; VMS for staff augmentation and supplier engagement; Procure?to?Pay for requisitions, purchase orders, and invoices; no canonical taxonomy or renewal gating
• Department owner: Human Resources & People Ops (HRIS and Talent Operations)
• Other stakeholders: Procurement, Finance/FP&A, Legal/Compliance, InfoSec, Site Operations, Clinical Quality, IT/Integrations, Security & Privacy, Internal Audit, Supplier Management

The Challenge

Contingent labor decisions ran on partial views. The VMS showed active assignments by supplier, Workday listed some contractors as contingent workers and others as visitors or vendors, and Procure?to?Pay classified spend under varied category codes. Leaders asked simple questions—total contingent headcount by function, renewal exposure by site, or spend by supplier—and received answers that depended on the system queried. Procurement struggled to align statements of work to staff augmentation trends, and HR could not quickly identify managers with repeated extensions or off?system engagements.

Renewals were inconsistent. Managers extended contractors by email, VMS end dates drifted, and purchase orders were amended without HR review. Tenure limits were applied unevenly across functions, co?employment risk reviews were handled ad hoc, and InfoSec approvals for system access lagged behind assignment changes. When audits requested the history behind a long?running engagement, supporting evidence came from inboxes and supplier notes rather than from a single record.

Operational friction grew. Without clear categories and approvals, suppliers routed requests through different channels, invoices landed against unexpected cost centers, and FP&A updated forecasts after the fact. Site leaders needed to see contingent and employee capacity together for planning, but the source data disagreed on who counted as on?site, who was remote, and who should be in safety briefings.

Why It Was Happening

Systems were not speaking a common language. The VMS tracked requisitions and assignments using supplier terms; Workday used contingent worker objects with HRIS job attributes; Procure?to?Pay captured spend under category codes that varied by buyer. Without a canonical mapping of worker type, role, location, cost center, and supplier, the same engagement appeared differently across tools.

Governance lived outside the workflow. Tenure rules, renewal thresholds, and approval matrices were documented but not enforced at the moment a manager clicked to extend a worker or amend a purchase order. Exceptions moved quickly in email, and the resulting data never reconciled back to the VMS, Workday, and purchasing in a consistent way.

The Solution

Intelligex implemented an integration and governance layer that synchronized worker and assignment data between the VMS, Workday, and Procure?to?Pay, standardized categories, and enforced approvals for renewals and extensions. A canonical taxonomy mapped worker type (staff augmentation, independent contractor, statement of work), function, site, cost center, and supplier to a single set of values with effective dates. Renewals triggered routing to HR, Procurement, and Legal as required, and approved changes updated all systems. Dashboards showed contingent headcount and spend by org, site, supplier, and category. The design used Workday integration patterns (Workday Integration Cloud), VMS APIs such as SAP Fieldglass, and Procure?to?Pay interfaces (for example, Coupa Procure?to?Pay).

• Integrations: Bi?directional sync of worker, assignment, and end?date data between the VMS and Workday; Procure?to?Pay linkage to assignments and cost centers; supplier master alignment; identity and site access updates tied to assignment status.
• Taxonomy and mappings: Canonical categories for worker type, function, site, and engagement model; mapping tables for VMS assignment types and purchasing category codes; effective?dated versions under change control.
• Renewal and extension workflow: Approval gates for tenure, rate changes, and budget impact; Legal review for co?employment risk or independent contractor status; Procurement review for supplier terms; automatic updates to VMS, Workday, and purchase orders upon approval.
• Validations and controls: Duplicate detection across systems; rate variance checks against agreed rate cards; exceptions for off?system engagements; supplier compliance checks and required documentation before activation.
• Dashboards and reporting: Headcount and spend by org, function, site, and supplier; renewals coming due; tenure exposure; exceptions and off?system flags; exportable audit packets with assignment history, approvals, and category mappings.
• Security and privacy: Role?based access aligned to HR, Procurement, Finance, and Legal; least?privilege service accounts; immutable logs of changes and approvals; retention aligned to policy.

Implementation

• Discovery: Cataloged VMS assignment fields, Workday contingent worker attributes, and Procure?to?Pay categories; inventoried suppliers and rate cards; reviewed tenure rules, renewal thresholds, and approval matrices; sampled renewals and long?running engagements; gathered Legal, InfoSec, and Audit requirements.
• Design: Authored the canonical taxonomy and mapping tables; defined renewal and extension gates by category; designed validation checks and exception types; planned bi?directional updates and sequence of record; outlined dashboards, alerts, and audit exports; set access tiers and logging.
• Build: Integrated VMS assignments with Workday contingent worker objects; linked Procure?to?Pay requisitions, purchase orders, and invoices to assignments and cost centers; implemented renewal approvals and exception routing; built validation checks and identity/site access updates; instrumented dashboards and audit logging.
• Testing/QA: Ran in shadow mode to reconcile active assignments and spend; validated taxonomy mappings and rate checks; exercised renewal workflows with tenure, rate, and budget scenarios; piloted with selected functions and suppliers; tuned messages, thresholds, and routing from feedback.
• Rollout: Enabled read?only dashboards for HR, Procurement, and Finance; turned on renewal approvals for pilot groups; expanded coverage across functions and sites in waves; retained email approvals as a controlled fallback early on; tightened checks and mandatory fields as adoption stabilized.
• Training/hand?off: Delivered guides for managers on renewal requests and reason codes; trained HR, Procurement, and Legal on approvals and exceptions; briefed Finance on dashboards and tie?outs; updated SOPs for onboarding, renewals, and offboarding; transferred ownership of taxonomy, mappings, and dashboards to HRIS/Procurement under change control.
• Human?in?the?loop review: Established a recurring council with HR, Procurement, Finance, and Legal to review exceptions, supplier patterns, and tenure exposures; recorded decisions with rationale and effective dates; fed updates into mappings, approvals, and validation rules.

Results

Leaders saw a consistent picture of contingent headcount and spend. Assignments appeared with the same categories across systems, renewals surfaced in time with clear approvals, and supplier usage patterns were visible by function and site. FP&A tied forecasts to actuals without reconciling separate decks, and conversations centered on capacity planning, supplier mix, and tenure exposure.

Managers followed a predictable renewal path. Extension requests routed to the right reviewers, co?employment risk and rate changes were considered in?flow, and approved updates synchronized to Workday, the VMS, and purchasing. Audits referenced a single packet showing assignment history, approvals, and category mappings. The company kept Workday, the VMS, and Procure?to?Pay; the change was a taxonomy, integration, and governance layer that made contingent labor visible and controlled.

What Changed for the Team

• Before: VMS, HRIS, and purchasing reports didn’t match. After: A canonical taxonomy and mappings aligned categories and cost centers across tools.
• Before: Renewals happened by email. After: Extensions followed an approval workflow with tenure and rate checks and synchronized updates.
• Before: Supplier usage and spend were hard to summarize. After: Dashboards showed headcount and spend by org, site, and supplier with renewals coming due.
• Before: Off?system engagements slipped through. After: Exceptions were flagged, reviewed, and either onboarded properly or closed.
• Before: Audits stitched emails and screenshots. After: Exportable packets included assignment history, approvals, and validations.
• Before: FP&A updated forecasts after surprises. After: Plan and actuals reconciled through the same categories and cost centers.

Key Takeaways

• Standardize the language first; define contingent categories, sites, and cost centers under change control.
• Make approvals part of the flow; renewals and extensions should route through tenure, rate, and risk checks.
• Synchronize systems; approved changes must update the VMS, Workday, and purchasing together.
• Validate early; detect duplicates, off?system engagements, and rate variances before invoices arrive.
• Show one view; dashboards aligned to the taxonomy reduce reconciliation and speed decisions.
• Integrate, don’t replace; keep Workday, the VMS, and Procure?to?Pay—add mappings, workflows, and evidence between them.

FAQ

What tools did this integrate with? The solution synchronized assignments between the VMS (for example, SAP Fieldglass) and Workday via Workday Integration Cloud, and linked Procure?to?Pay transactions to assignments through standard interfaces (for example, Coupa Procure?to?Pay). Identity and site access updates followed assignment status, and dashboards ran on the existing analytics stack.

How did you handle quality control and governance? The taxonomy and mapping tables were versioned with owners in HRIS and Procurement. Renewal approvals captured reason codes and approvers, and validations checked for duplicates, rate variances, missing documents, and off?system engagements. Every change wrote to immutable logs, and dashboards included tie?outs and release notes for definition updates.

How did you roll this out without disruption? The integration ran in shadow mode to reconcile active assignments and spend while existing processes continued. Read?only dashboards launched first, followed by renewal approvals for pilot functions. Email approvals remained as a controlled fallback during early waves. As accuracy and adoption held, gates tightened and coverage expanded site by site.

How were co?employment risk and tenure limits handled? Tenure limits and independent contractor checks were encoded as policy rules that triggered Legal review when thresholds or flags were met. Approvals captured rationale and documents, and decisions synchronized back to all systems. Long?running engagements surfaced in dashboards for proactive planning.

How did you treat SOW work vs staff augmentation? The taxonomy separated statement?of?work engagements from time?and?materials staff augmentation. SOWs linked to milestones and deliverables in purchasing, while staff augmentation linked to rate cards and timesheets in the VMS. Both appeared in dashboards under the same category and cost center framework.

How did you protect vendor and worker data? Role?based access limited who could view supplier details and personal data. Service accounts used least?privilege scopes, and data moved over encrypted channels. Dashboards masked sensitive fields and exposed only the attributes needed for planning and approvals. All access and exports were logged for audit.

What if a manager engages a contractor outside the VMS? Off?system detections flagged unmatched invoices or supplier records. The workflow routed these cases to HR and Procurement to either onboard properly through the VMS or terminate the engagement, with reason codes recorded and dashboards updated to reflect resolution.