Ask most procurement teams if their vendors are onboarded, the answer is yes. Ask if they are prequalified, and the answer gets a lot less certain. That gap – between having a vendor’s details and knowing who you’re working with – is where a lot of supply chain risk quietly lives.
In this blog post, we break down what onboarding and prequalification means, why treating them as separate steps create risk you can’t see until it’s too late, and what changes when the two are connected.
Prequalification vs onboarding – what’s the difference?
The two terms get used loosely across the industry, sometimes as if they mean the same thing. They don’t.
Here’s how we see this distinction, as the market blurs it:
- Onboarding answers one question – can we pay this business? The onboarding stage is where obtain the company name, ABN, contact details, bank details – the entity-level basics. It’s why so many finance tools and ERPs bolt on an ‘onboarding’ feature and call it done.
- Prequalification answers a different question: Can this business deliver what they’re proposing they supply, safely and to a standard? It’s contextual – tied to a scope of work, the risk involved, and the category the vendor sits in.
Two different questions. But in a lot of organisations, they’re never asked together – vendors get onboarded and nothing else, or onboarding and prequalification live in entirely separate tools with no connection between them.
Which means there’s a gap. ‘Vendor onboarded’ isn’t the same as ‘vendor understood.’
The problem with treating onboarding as a checkbox
Many ERPs and finance tools offer onboarding as a bolt-on feature – good enough to capture the basics and get a vendor paid, not to tell you whether they should be trusted with the work. Prequalification was never part of the brief.
They treat onboarding as a one-time gate: Get the business details, tick the box, move on.
That works fine until:
- You operate in a high-risk industry where your supply chain needs compliance and insurances validated every year, not just at the start
- A subcontractor you onboarded two years ago is still ‘approved’ but nobody has checked whether their safety record still holds up
- You want to know how a vendor is performing over time, and realise this hasn’t been tracked since the day they onboarded
- An auditor asks how you know your supply chain is still compliant, and ‘we checked once’ isn’t an answer
And then the onboarding tool was never built to ask the right questions, and it shows up in moments like:
- A high-risk vendor sailed through the same generic form as low-risk suppliers, no extra scrutiny, because the onboarding form doesn’t know the difference
- A client wants current safety statistics (like LTIs) on your high-risk vendors, and you realise this was never captured in the first place
- You go looking for what a vendor’s category qualifies them to do, and realised the question was never asked at all
Not every vendor carries the same risk – so why ask them about the same requirements?
ERP and finance onboarding tools work off the same limited set of questions, applied to every vendor, regardless of what they do or how much risk they carry. It's simple to build and simple to use. It's also blind to the thing that actually matters: not every vendor needs the same level of scrutiny.
A fixed question set and same treatment for vendor regardless of risk – this is where blanket onboarding breaks down. And because these tools weren’t built for this in the first place, there’s usually a hard ceiling on how many questions you can ask. And it’s not just onboarding tools – plenty of prequalification approaches fall into the same trap. A one-size-fits-all questionnaire get applied across the board, one-dimensional and generic, regardless of risk category. The result is the same either way: high-risk vendors get under-checked, low-risk vendors get over-asked, and nobody’s time is well spent.
Risk-based, category-driven prequalification works differently. Not all vendors are equal, and the prequalification requirements shouldn’t be either. The category a vendor sits in tells you exactly what to ask of them – a high-risk supplier gets asked about licensing and insurance, a low-risk supplier might not. The scope of work defines the risk, and the risk defines what information needs to be gathered. Relevant, not blanket.
What happens when onboarding lives in its own silo
Structured onboarding runs into a wall if it lives in a separate system from everything else. The data gets captured once, at the start, and then goes nowhere.
Take a common scenario: onboarding sits inside a finance tool, because that's where the ABN and bank details need to end up. That’s fine if the finance team is the only team who needs these details. But the stakeholders engaging vendors day to day - estimators, project teams, procurement teams – don’t live in finance tools. If they don’t have access to this information, they don't use it, and instead keep their own spreadsheets, ask their own questions, make their own calls on who to bring on.
And that brings operational risk. Without adequate access to a supplier record, decentralised teams don’t stop engaging vendors – they just do it their own way. More suppliers, more volume, less visibility over who they are working with or what has been checked. You lose buying power as nobody’s looking at the full picture, and you end up exposed to vendors who were never properly assessed in the first place – the exact risk this whole process was supposed to catch.
Even where onboarding and prequalification technically both happen, if they're not connected, you end up re-entering the same vendor information more than once – to get them paid, to engage them, to run tenders, to report, or to onboard them into a new project or category. Any risk profile that changes after the fact has nowhere to go; nothing downstream is watching for it.
The result is a record that's accurate on the day it's created and stale from the day after. Onboarding becomes a static entry in a database, not a live view of who you're working with.
The compounding value of connecting onboarding and prequalification
When onboarding and prequalification are connected, the value isn’t just avoiding the problems above – it compounds.
Here’s the benefits and what that looks like:
1. Access to better buying decisions
When the right stakeholders have access to up-to-date supplier information – categories, buying behaviour, not just entity details – procurement decisions improve across the board. You're buying based on a live picture of your supply chain, not whatever's in someone's spreadsheet.
2. Reduced operational risk
When supplier information is accessible to the teams engaging vendors – not locked in a finance tool only one team can see – decentralised teams stop working around the system. Fewer shadow spreadsheets, fewer vendors engaged without proper checks, less exposure sitting outside anyone's view.
3. Category management and insights
Vendor pools become visible by category. You can see coverage and risk exposure at a glance – where you're strong, where you're thin, where you're overexposed to a handful of suppliers – instead of piecing it together from multiple systems.
4. Downstream decisions
Sourcing decisions get informed by prequalification data that's already sitting there – not re-collected every time it's needed. Information gathered once flows naturally into the next decision, instead of everyone starting from scratch.
5. Performance monitoring
A vendor isn't assessed once and left alone. Because the record's connected, performance can be tracked against what was declared at onboarding – so changes show up, instead of sitting unnoticed until the next audit or renewal.
6. Faster, lower-effort requalification
Because the profile evolves rather than resetting, reassessing a vendor doesn't mean starting over. What's already known carries forward, and only what's changed needs checking.
The self-check: How connected is your supply chain?
If any of these questions give you some uncomfortable answers, it might be a sign that your onboarding and prequalification aren’t as connected as they should be.
On the onboarding experience itself
- Do all vendors go through the same prequalification requirements, regardless of the risk they pose or the work they'll do?
- Have you hit a ceiling on how many questions or fields you can capture – or had to cut questions to keep the process usable?
- Do stakeholders across your business have access to a prequalified, approved vendor list?
- When a vendor needs sign-off, does it go to the person who knows the risk area?
On what happens to the data after onboarding
- Once a vendor is onboarded, does that information get manually re-entered anywhere else in your systems?
- Are your compliance documents (insurance, licences, certifications) tracked separately from where they were originally collected – and does anyone get notified when they expire?
- If a vendor's risk profile changes after onboarding, does anything downstream reflect that?
On visibility and reporting
- If someone asked how a vendor has performed over time, could you answer in a few clicks, or would it take some digging?
- If you were asked to prove your supply chain is still compliant, could you – or would it mean chasing documents across multiple places?
- If an auditor asks for proof your high-risk vendors are still compliant, how long would that take you?
- Could you produce a full compliance history for a vendor, without going back to them to re-supply anything?
Where Felix fits
Felix Vendor Management treats onboarding and prequalification as one connected process, not two separate steps in two separate systems. Instead of a static record, you have a vendor profile that’s risk-based, built around a vendor’s category and scope of work, and it evolves as the vendor relationship does.
With Felix, you can turn manual processes into a single source of truth for onboarding, prequalification, vendor management, compliance and performance evaluation. Procurement activity feeds straight back to the vendor profile, so compliance records and historical performance sit against that vendor, not scattered across systems, driving better business decisions.
Felix integrates with ERP systems, finance tools such as Eftsure, and due diligence tools such as CreditorWatch, and Fiable – pulling entity verification and risk data straight into the profile instead of asking your team to chase and re-key it manually. From there, prequalification requirements are automatically driven by category and risk. And because it's all one system, that data doesn't dead-end at onboarding – it feeds vendor insights, sourcing and tendering decisions, and ongoing performance monitoring, all built on the same connected record.
The result: vendor risk management becomes a system, not a series of standalone tasks.
Connected in practice: proof it works
Don’t just take our word for it – here’s how two business closed the gap, in their own words:
CV Services Group
CV ran into a familiar problem at scale: after growing through acquisitions, the business had vendors sitting as separate records across multiple systems, and prequalification was handled manually over email - with no consistent way to capture compliance data. Bringing onboarding and prequalification into Felix, it allowed for one connected record – a single source of truth for supplier information, compliance and governance across the whole business.
Read case study
Altrad Services
Altrad Services faced a similar challenge in a higher-risk industry. Operating across oil, gas and mining, manual processes and scattered data made vendor management difficult and audits stressful. Moving to Felix let Altrad Services prequalify suppliers and maintain a consistent standard of compliance across the entire group, giving them confidence that every supplier and subcontractor they engage is capable and compliant to do the work.
Watch case study
It’s time to see who you’re working with
Onboarding and prequalification were never meant to be two separate jobs – they’re two halves of the same question: who are you letting into your supply chain?
If you're ready to bring them together, request a demo and see how Felix connects the two. Or if you'd rather talk it through first, get in touch with the team.
.jpeg)
