VMS Operations
How to Submit a CV to SAP Fieldglass: A Supplier's Guide
Submitting a candidate into SAP Fieldglass is not the same as emailing a CV. This guide walks a staffing supplier through the job-seeker workflow, the profile fields that gate a submission, how rate entry works, and what the buyer actually sees on the other side.
Written by: Saply Team
Submitting a CV to SAP Fieldglass means creating a structured job-seeker record against an open requisition, not attaching a document to an email. As a staffing supplier you open the job posting in the Fieldglass portal, select Submit Job Seeker, enter the candidate’s details and rate, attach the CV where the buyer requires it, and submit. The candidate then moves to a Submitted status and appears in the buyer’s review queue as a workforce record.
That distinction is the whole game. Most agencies lose Fieldglass placements not on candidate quality but on submission mechanics: a missing qualification rating, a rate entered against the wrong rate type, or a CV that does not match the format the buyer’s hiring manager expects to skim. This guide is written for the supplier side, the staffing firm feeding candidates into a Vendor Management System that was designed around the buyer’s procurement team.
The Fieldglass submission workflow, step by step
Every supplier submission runs through the same sequence. Fieldglass validates each stage before it lets you advance, so an incomplete field earlier in the flow blocks the submit button at the end.
Fieldglass documents each of these stages, from the Submit Job Seeker action through attachment handling, qualification ratings, and rate entry, in its supplier help material on the SAP Help Portal. If your buyer runs a configuration you have not seen before, that portal is the authoritative reference, not a peer’s screenshot from a different program.
The profile fields that gate a submission
A Fieldglass submission is a form, and the buyer decides which fields are mandatory. Miss a required one and the system will not let you submit. The common fields, and where suppliers trip:
| Field | What it is | Where suppliers slip |
|---|---|---|
| First and last name | The candidate identity on the record | Legal name vs preferred name mismatches with later checks |
| Security ID | Optional identifier, config dependent | Left blank when the program requires it |
| Available date | When the candidate can start | Set to today by reflex, not the real date |
| CV attachment | The resume file, often mandatory | Wrong format, or a generic CV not tailored to the role |
| Qualification ratings | Buyer-defined skills scored per candidate | Rushed self-ratings that the interview then contradicts |
| Rate information | Pay or bill rate for the engagement | Entered against the wrong rate type |
The qualification ratings deserve attention because they are the closest thing Fieldglass has to structured matching data. When a buyer defines required qualifications on the requisition, your ratings against them become part of how the candidate is compared to others in the queue. Inflating them to clear a filter is a short-term win that becomes a credibility problem the first time an interviewer sees the gap.
The CV attachment is not a formality. Fieldglass standardizes the worker profile fields, but the buyer’s hiring manager still opens the attached document to make the shortlist decision. A CV that arrives in your agency’s raw template, with your logo and a candidate photo, undercuts the neutral procurement framing Fieldglass is built to enforce. Reformat to the client’s expectations before you attach.
How rate entry actually works
Rate is where Fieldglass submissions go wrong most often, because the rate you enter has to match the rate type the requisition was built on. Fieldglass supports several, and entering a bill rate where the system expects a markup, or a pay rate where it expects a unit bill rate, produces a submission that looks fine to you and wrong to the buyer.
Depending on the program’s configuration and your role permissions, the buyer may be allowed to see the supplier-entered pay rate, and Fieldglass can carry the supplier-presented rate forward so it defaults into the work order as the final rate. In plainer terms: the number you enter can become the number that governs the placement, and the buyer may see your margin assumptions. Enter it deliberately, not from muscle memory, and confirm the rate type with the program office if the requisition is new to you.
What the buyer sees on the other side
Once you submit, Fieldglass creates a workforce record visible to both you and the buyer, and the candidate appears in the buyer’s review area with a Submitted status. The buyer sees a normalized profile: name, available date, qualification ratings, the rate where their configuration exposes it, and your attached CV. They compare that against every other supplier’s submission for the same requisition, side by side, in the same layout.
That last point is why Fieldglass rewards discipline over relationship. In a direct email submission you can lead with a phone call and a paragraph of context. Inside the VMS, your candidate is one row in a grid, and the two things that differentiate you are the qualification ratings you entered and the CV the manager opens. Everything persuasive about your desk collapses into those fields. This is the same buyer-side framing we cover in the Beeline vs Fieldglass comparison: the platform decides what the client grades you on, and it is rarely your pitch.
Working across multiple VMS platforms
Most staffing suppliers do not submit into one VMS. They submit into Fieldglass for one client, Beeline for another, and a Bullhorn-fed requisition for a third, each with its own login, its own required fields, and its own template expectations. The operational cost is real: a recruiter juggling three portals reformats the same candidate three ways and re-keys the same data three times.
The pattern that scales is to keep one clean, structured version of each candidate in your own system, then adapt the output per portal at submission time. Reformatting a CV to the client’s expected template, anonymizing it where the program requires blind screening, and re-keying core fields are the three tasks that repeat on every VMS submission. Automating those is where an agency claws back time, not in the submission clicks themselves.
This is where a formatting layer earns its place in a VMS workflow. Saply reformats a parsed CV into the template a given client expects before you attach it in Fieldglass, and can strip identifying fields for programs that require blind submission, so the document you upload matches the buyer’s framing rather than your agency’s house style. The honest limitation: Saply does not submit into Fieldglass for you, and no tool should promise to, because the VMS is the buyer’s system of record and the field mapping is theirs to define. What a formatting tool removes is the reformatting and redaction work that sits in front of every submission, not the submission itself. For the broader picture of competing as a supplier inside these systems, our guide to VMS staffing covers the supply-side economics, and the CV formatting page shows the template step in detail.
Frequently asked questions
How do I submit a CV to SAP Fieldglass?
Open the distributed job posting in your supplier portal, select Submit Job Seeker, and complete the profile: name, available date, the CV attachment, any required qualification ratings, and the rate information for the requisition’s rate type. Fieldglass validates the form and highlights missing fields; once everything passes, submit, and the candidate moves to a Submitted status in the buyer’s review queue. The exact required fields depend on how the buyer configured that program.
Is the CV attachment mandatory in Fieldglass?
It depends on the buyer’s configuration. Many programs make the resume or CV attachment mandatory, and some route candidates through a prequalification template first. Even when it is technically optional, the attached CV is what the hiring manager opens to make the shortlist decision, so treat it as required and reformat it to the client’s expected template before attaching.
How does Fieldglass rank supplier candidates?
Fieldglass presents submitted candidates to the buyer as workforce records in a comparable grid, including qualification ratings against the requisition’s defined skills and, where configuration allows, the supplier-presented rate. The buyer, not the platform, makes the shortlist and selection decision from that normalized view. The structured fields you enter, especially qualification ratings, are what drive the comparison, which is why accuracy there matters more than a strong cover note.
Can the buyer see the rate I enter?
Sometimes. Depending on the program configuration and your role permissions, the buyer can be allowed to see the supplier-entered pay rate, and Fieldglass can carry the supplier-presented rate forward as the default final rate on the work order. Enter rates deliberately and confirm the rate type with the program office when a requisition is unfamiliar, because the figure you submit may govern the placement.
How do I manage submissions across Fieldglass, Beeline, and other VMS platforms?
Keep one structured version of each candidate in your own system, then adapt the output for each portal at submission time. The repeating work is reformatting the CV to each client’s template, anonymizing it where blind screening is required, and re-keying core fields into each VMS form. Automating the formatting and redaction steps is the practical way to cut the per-portal overhead; the submission itself stays inside each buyer’s platform. See our contingent workforce management strategy guide for the operating model around this.