Contingent Workforce
SAP Fieldglass: A Staffing Supplier's Guide to How It Works
Most SAP Fieldglass guides are written for the enterprise buying contingent labor. This one is for the agency supplying it. Here is what Fieldglass is, how a requisition moves through it, and where suppliers quietly lose margin inside the portal.
Written by: Saply Team
SAP Fieldglass is a cloud vendor management system (VMS) that enterprises use to source, engage, and pay their external workforce. For the staffing agency on the other side, it is the portal where your client’s requisitions arrive, where you submit candidates, and where every timesheet and invoice is approved. You do not choose Fieldglass. Your client does, and then you work inside it.
That distinction is the whole point of this guide. Almost everything published about Fieldglass explains it to the company buying labor. This is written for the supplier submitting into it, because the platform behaves very differently depending on which side of the requisition you sit on.
What SAP Fieldglass actually is
Fieldglass sits inside SAP’s spend management suite. The enterprise treats contingent labor the same way it treats any other category of external spend: something to be requisitioned, competed, approved, and paid through one controlled system. When a hiring manager needs a contractor, they raise a requisition in Fieldglass rather than emailing three agencies. The system distributes that requisition to approved suppliers, collects submissions, routes approvals, tracks the worker’s time, and generates the invoice.
For the buyer, that is spend control and compliance. For you, it means the relationship that used to run on phone calls and trust now runs through a structured workflow with fixed fields, rate rules, and deadlines. If you are new to the category, start with the broader explainer on what a vendor management system is, then come back here for the Fieldglass specifics.
The mental shift that trips up new suppliers. In direct staffing you sell to a person. In Fieldglass you compete inside a process. The buyer may never see your cover note, your reputation, or your relationship history. They see a shortlist of profiles that all cleared the same gates. Winning inside the VMS is about getting through the process cleanly, fast, and formatted the way the system expects.
How a requisition moves through Fieldglass
Every engagement follows the same lifecycle. Understanding where you have leverage and where you do not is the difference between a supplier who wins fill rate and one who burns hours on requisitions they were never positioned to win.
1. The requisition is released
The buyer, sometimes through a managed service provider (MSP) running the program on their behalf, releases a requisition to a tier of approved suppliers. You often do not receive it first. Many programs distribute in tiers or in timed waves, so a preferred supplier sees the role hours or days before you do. Knowing your tier tells you how much of a head start the competition already has.
2. You submit the candidate
This is the step suppliers get wrong most often. Submission is not attaching a CV. It is completing the profile fields the requisition gates on, entering a bill rate inside the allowed range, and uploading a CV in the format the program expects. Miss a mandatory field and the submission will not save. The mechanics are worth learning cold, and we walk through them in the guide to submitting a CV to SAP Fieldglass.
3. Shortlisting and scoring
Before a human reads anything, Fieldglass scores your candidate against the requisition’s weighted qualifications. That score, plus your rate, plus how completely you filled the profile, decides whether you make the shortlist. This is why two agencies can submit the same contractor and get different visibility. The full logic is broken down in how Fieldglass ranks candidates.
4. Engagement and onboarding
A shortlisted, interviewed, and selected candidate becomes a work order. Onboarding tasks, compliance documents, and start-date confirmation all run through the platform. This is where a sloppy submission comes back to bite you: data you skipped at submission usually has to be entered now anyway.
5. Time, expenses, and invoicing
The worker logs time in Fieldglass. Approved timesheets generate the invoice automatically. There is no separate billing conversation, which removes disputes but also removes flexibility: what the system captured is what you get paid for.
What Fieldglass changes for a staffing agency
The platform does not just add a portal. It reshapes the economics of the desk. Three changes matter most.
| What changes | Direct staffing | Inside SAP Fieldglass |
|---|---|---|
| Who you sell to | The hiring manager | The requisition, then the score |
| Rate | Negotiated per placement | Constrained to a published range |
| CV format | Your template | The program’s required format |
| Data entry | Your ATS only | Your ATS and the VMS |
| Speed pressure | Hours to days | Often a same-day submission window |
The most expensive of these is the double entry. Your candidates live in your ATS. The requisition and submission live in Fieldglass. Without a connection between them, a recruiter rekeys the same profile twice, and that rekeying is pure margin leakage on rates the VMS has already compressed. This is the problem VMS integration exists to solve, and it is worth reading before you accept that copy-paste is just the cost of doing VMS business.
A candid caveat. Fieldglass rewards process discipline, not relationship selling, and that is genuinely bad news for agencies whose edge was a warm relationship with the hiring manager. If your differentiation was access, the VMS erases it. If your differentiation is speed, quality of match, and clean submissions, the VMS actually plays to your strengths, because it makes those things measurable.
Fieldglass in the wider VMS landscape
Fieldglass is one of several enterprise VMS platforms. Your larger clients may run different ones, which is how a staffing firm ends up managing three to five VMS logins at once. The two you will meet most often alongside Fieldglass are Beeline and Coupa.
The differences matter less to the buyer than to you. On the supplier side, submission mechanics, rate entry, and how the shortlist is scored vary enough that habits from one portal do not transfer cleanly to another. We compare the two heavyweights directly in Beeline vs Fieldglass.
One term to keep straight: a VMS is not an MSP. Fieldglass is software. An MSP is the team, sometimes a third party, that runs the contingent program on the client’s behalf and often sits between you and the buyer inside that software. The distinction changes who you build a relationship with, and it is explained in VMS vs MSP.
Why the contingent category is worth the effort
The friction is real, so it is fair to ask whether the category justifies the work. It does, because this is where a growing share of enterprise hiring now happens. In 2024 the EU had 22.1 million employees in temporary jobs, 11.0% of the working-age population, according to Eurostat. A large slice of that external workforce at enterprise scale is sourced and paid through VMS platforms like Fieldglass. If your agency wants enterprise clients, being fluent inside their VMS is not optional, it is the ticket to the requisition.
There is a GDPR dimension too. Every candidate profile you push into a VMS is personal data under the GDPR, and so is every CV sitting in your ATS. Where that data is processed and stored is a question your enterprise clients’ data protection officers will ask, so it is worth knowing your own tooling’s answer before they do.
How to operate well as a Fieldglass supplier
The suppliers who win inside Fieldglass treat it as an operational discipline, not an inbox. In practice that means four habits.
- Submit complete, every time. A fully populated profile scores higher and saves rework at onboarding. Half-filled submissions lose on the score and cost you time later.
- Match the required CV format on the first pass. Reformatting a candidate’s CV into the program’s template by hand is slow and error-prone. Automating CV formatting into the required layout turns a fifteen-minute job into seconds and keeps every submission consistent.
- Kill the double entry. Connect the VMS to your ATS so a recruiter is not the integration. See the ATS integration options for how the sync works in practice.
- Submit the right candidate, not just a candidate. Because scoring is weighted, submitting your best match beats submitting fastest. Strong candidate matching upstream means the profile you send is the one most likely to clear the shortlist.
None of this requires abandoning how your desk already works. It requires removing the manual steps the VMS silently added, so your recruiters spend their time on judgment, not data entry. For a broader playbook on winning work across VMS platforms, see the guide to VMS staffing.
Frequently asked questions
Is SAP Fieldglass an ATS or a VMS?
It is a VMS, a vendor management system. It runs the buyer’s contingent workforce program: distributing requisitions, collecting submissions, tracking time, and handling invoicing. It is not an applicant tracking system and it does not replace yours. Your ATS is still where your candidate database lives; Fieldglass is where you submit into a specific client’s roles.
Who pays for SAP Fieldglass, the agency or the client?
The enterprise client licenses and runs Fieldglass. Suppliers are not charged a license fee to use it, though some programs apply a supplier funding fee or margin adjustment that effectively passes a cost of the program back to the agency. Read the program terms, because that fee comes straight off your rate.
How do I get access to SAP Fieldglass as a new supplier?
You cannot self-register. Access follows a commercial relationship: the enterprise or its MSP approves your agency as a supplier for a specific program and then provisions your login. If you want into a program, the conversation is with the client or the MSP running it, not with SAP.
Does Fieldglass integrate with my ATS?
Yes, through the platform’s connectors or middleware, so requisitions and submissions can sync instead of being rekeyed. The depth varies by program and by your ATS. The practical levels of integration, and the one gap the connector usually does not close, are covered in the guide to VMS integration.
Why do my candidates score differently in Fieldglass than I expect?
Because the shortlist is driven by weighted qualification scoring, your rate, and how completely you filled the submission, not by your relationship with the buyer. A strong candidate submitted with a thin profile can score below a weaker one submitted completely. The scoring logic and the submission habits that move a candidate up are detailed in how Fieldglass ranks candidates.