SharePoint vendor management system

A SharePoint vendor management system with one register and a named owner

One list for every approved vendor your company does business with, with the fields, onboarding intake, compliance tracking, expiry alerts and permissions that turn a spreadsheet of suppliers into something a person in procurement, finance or operations actually owns. Built for an ordinary company managing its own vendors — not for a procurement outsourcing firm. One written scope, one fixed price agreed before work starts, typical delivery in 2–4 weeks with 30 days of hypercare.

Free, no-obligation consultation · Reply within one business day

  • Fixed-fee scoped projects
  • Senior US-based engineers
  • Typical 2–4 week delivery
  • 30 days of hypercare
Revenue Overview Revenue$4.2M Margin38% Orders12.4k Churn2.1% Monthly performance By segment 64%

Sample dashboard. Illustrative data, not a client’s numbers

What you get

Six working parts, delivered as one system

Each of these exists in most companies already — scattered across a spreadsheet, a shared drive, two inboxes and somebody’s calendar. The build puts them in one place and gives the whole of it an owner.

One vendor register, and only one

Every approved vendor in a single list: suppliers, subcontractors, service providers, consultants. The point is not tidiness. It is that a question about a vendor has exactly one place to be answered from, and nobody has to ask which spreadsheet has the current list.

Onboarding intake that routes itself

A Microsoft Form or Power App captures the vendor details at first contact: legal name, tax ID, insurance certificate upload, category, and the person requesting the relationship. That intake triggers the approval route rather than sitting in an inbox waiting for somebody to notice.

Alerts before certificates expire

An expired insurance certificate or a missing W-9 does not warn you; it simply becomes a compliance gap. A scheduled flow reads the expiry dates every morning and tells the named owner while there is still time to request a renewal, not after an auditor has already found it.

New-vendor approval that routes itself

A new vendor goes to the people who have to approve it, in the order they have to see it, with the decision and the comments written back to the record. The mechanics are ordinary Power Automate approvals; what we add is the routing your company actually uses.

Compliance documents attached and current

Each vendor record holds its W-9, insurance certificate, SOC report, NDA and whatever else your business requires. The current version is the one that shows; expired ones are flagged rather than buried in a folder.

Access shaped to the org chart

Operations sees the vendors behind its own projects. Finance sees what it has to pay against. The full register stays with the people who are supposed to hold it. Designed as a permissions model rather than assembled from one-off shares.

How it works

Three steps from a spreadsheet of vendors to a system somebody runs

  1. 1

    Agree the fields and the owner

    A working session with whoever will run this decides what a vendor record must carry, which compliance documents are required, who approves a new vendor, and who is allowed to see which vendors. The answers are written down before anything is built.

  2. 2

    Build the register, the forms and the flows

    The vendor list, the required fields, the onboarding form, the views each team opens, the expiry alerting schedule, the approval routes and the permissions are configured in your own tenant, then tested against real vendors with the people who will use them.

  3. 3

    Load the existing vendors and hand over

    Current vendors move in waves with their detail filled in, the old spreadsheets are closed rather than left as a second source of truth, and the owner gets a walkthrough plus 30 days of hypercare while the habits set.

Why vendors need their own register rather than a spreadsheet

Vendors behave differently from the rest of a company’s records, which is why they outgrow a spreadsheet first. They have compliance deadlines that expire silently, contacts that change without notice, and a small number of people who are allowed to approve a new one. A spreadsheet can list them; it cannot tell you which insurance certificates expire in the next sixty days, who owns the relationship, or whether the W-9 on file is still the current version. That is the gap this build closes, on the Microsoft 365 licenses you already pay for rather than on a separate platform with its own seats and its own login.

This is a narrower engagement than our general SharePoint intranet and document management consulting, which designs the information architecture for a whole company’s content. Here there is one named system, one named owner in procurement, finance or operations, and a scope that ends at a working vendor register with onboarding, alerting, approval routing and access rules around it. Where the agreements themselves — the signed contracts with those vendors — are the system you need, that is what our SharePoint contract management system engagement builds. Many companies run both: one tracks the vendor, the other tracks what was signed with them.

The fields decide whether any of it works

Everything downstream — the alerts, the views, the reporting, the access rules — is only as good as the fields on each record. Get them agreed in a room in an afternoon and the rest is configuration. Skip that conversation and you get a list with a search box, which is the spreadsheet again with extra steps. In SharePoint these fields are columns on a list, and Microsoft’s guidance on adding columns to a SharePoint list (opens in new tab) covers the mechanics, including making a column required so a record cannot be saved without it.

Field What it lets you do Where the value usually has to come from
Legal name Pull every record and payment for one vendor before an audit or a dispute The vendor’s W-9 or articles of incorporation — not what the requester typed from memory
Tax ID / EIN Match the vendor to the 1099 at year-end without a reconciliation project The W-9; stored as text to preserve leading zeros
Category Separate IT vendors from facilities from subcontractors, and apply different approval rules to each A short agreed picklist; long lists are where classification quietly stops happening
Internal owner Give every alert a person to go to, and make an unowned vendor visible as a gap A people field, reviewed when someone leaves — the single most common cause of a missed renewal
Insurance expiry date Answer “is this vendor still covered?” without opening the certificate The certificate of insurance; the field people most often assume they will remember
W-9 date Know whether the tax form on file is current or from a previous fiscal year The W-9 itself; annual refresh is a common policy
Status Keep prospective, approved, on-hold and terminated vendors distinguishable in one list Set by the workflow rather than typed, so it stays honest

Know which situation matches your vendor register? Tell us, and we’ll send a written scope with one fixed price.

Scope my project →

Two fields do most of the compliance work and both are frequently missing: insurance expiry date and W-9 date. An expired certificate does not send its own reminder. Storing the expiry as a date rather than as a note in a comment field is what lets a flow do that arithmetic for you every morning.

Onboarding: the first impression sets the standard

The onboarding intake is where the register either stays honest or starts to decay. If a new vendor arrives as an email to one person’s inbox with a PDF attached, the fields will be incomplete and the approval will be verbal. If it arrives through a form that requires the legal name, the tax ID, the category and the insurance upload before it can be submitted, the record is already useful the moment it lands in the register.

Mechanically the form is a Microsoft Form or a Power App, depending on whether you need conditional logic. The submission creates a list item with status set to “pending approval” and triggers a Power Automate approval flow (opens in new tab). The approver sees the vendor details and the attached documents in one view, and the decision is written back to the record. If you want to understand the approval mechanics before you buy anything, our guide to replacing email approvals with Power Automate walks through building one step by step. Where approvals across the business are the wider problem rather than vendor onboarding specifically, that is the remit of our Power Automate consulting engagement.

The expired certificate you did not know about

The expensive failure in vendor management is rarely a lost document. It is a subcontractor who worked on your site with expired insurance, a vendor paid on a 1099 whose W-9 was three years old at audit time, or a supplier whose SOC report lapsed and nobody noticed until a customer asked for it. All of these are calendar failures, and all of them are what the alerting exists to prevent.

Mechanically it is a scheduled cloud flow: it runs on a recurrence you set in Power Automate (opens in new tab), reads the vendor list, and selects the records whose insurance or W-9 expiry falls inside the warning window. The judgement is in the design, not the plumbing: how far ahead the first warning goes out, whether there is a second and a third, who is copied when the owner does not respond, and what happens to a vendor whose documents lapse past a hard deadline. We set those with you, and we write the escalation path down rather than relying on the first email being read.

One production note worth insisting on: the flow’s connections should be owned by a service account rather than by whoever built it, so the alerting survives that person leaving. It is a five-minute decision at build time and an outage nine months later if it is skipped.

Who sees which vendors

This is the part that takes the longest to agree and the least time to build. Vendors are one of the few record sets where “everyone in the company” is the wrong answer and “three people in finance” is also the wrong answer. The workable pattern is usually a restricted list holding the full register, filtered views that give each department its own vendors, and a written list of the exceptions you decided to make deliberately.

What makes that maintainable is groups rather than individuals, which is also what keeps it reviewable a year later. Microsoft’s reference on permission levels in SharePoint (opens in new tab) sets out how inheritance flows from site to list to item and what each level actually grants. If the wider estate already has years of broken inheritance and stale sharing links behind it, that is a separate and larger job: our SharePoint governance consulting services deal with the estate-wide version, and it is worth doing first if the vendor list would otherwise inherit the mess.

What your licenses already cover, and what does not

All of this system runs on things you are already paying for. The vendor list, the form, the approval routing and the alerting are standard SharePoint and Power Automate capabilities available with the Business and Enterprise plans companies typically hold. There is no per-vendor fee, no per-transaction charge, and no additional platform to learn.

Component How it is delivered Cost beyond the licenses you hold
Vendor register, fields and views A SharePoint list with a vendor content type and per-team views None — part of the SharePoint entitlement in standard Microsoft 365 business and enterprise plans
Onboarding intake form A Microsoft Form or a Power App that captures vendor details and triggers the approval route None on standard connectors; a premium connector or Dataverse-backed form is a licensing question we raise in scoping
Compliance expiry alerting A scheduled Power Automate flow reading insurance and W-9 dates, emailing the named owner None where the build stays on the standard connectors your plan includes
New-vendor approval routing Power Automate approval actions, sequential or parallel, writing the decision back to the record None on standard connectors
Compliance document storage Attachments or a linked document library per vendor, holding W-9s, insurance certificates and SOCs None — stored in SharePoint against the tenant’s existing storage allocation
Reporting on the vendor base SharePoint views for day-to-day questions; a Power BI report where leadership wants the whole picture Views cost nothing; a published Power BI report needs the relevant Power BI licensing, which we flag before building one

When a dedicated product is the better buy

There is a real line here and we would rather draw it than argue past it. A category of vendor management and procurement products exists, and for some companies they are the right purchase. Buying one is sensible when the requirements below describe you; building this is sensible when they do not.

If this describes you The honest answer
You need purchase orders, three-way matching, and integrated invoicing against vendor records Buy a procurement product. That is genuinely specialised financial workflow and rebuilding it natively would cost more than licensing it
You run competitive bidding, RFPs and scoring matrices as part of vendor selection Buy. The sourcing and bid-evaluation tooling will earn its keep at that volume
You need vendor performance scorecards with automated data collection from multiple systems Buy, or scope something considerably larger than this engagement with clear eyes about what it will take
You mainly need to know who your vendors are, whether their compliance documents are current, and who approved them Build it here. This is the common case, and it runs on licenses you already hold with no new vendor, no new login and no per-seat cost
You are not sure yet, and the current system is a spreadsheet Build this first. It is faster to stand up, and the field discipline it forces is exactly the requirements document you would need before buying anything

Who this fits, and who it does not

The usual fit is a company of roughly 20 to 500 people already on Microsoft 365, managing somewhere between a few dozen and a few hundred active vendors, where one person in procurement, finance or operations has inherited the job of knowing who is approved and who is not. The trigger is almost always a specific event: a compliance audit that took a week to answer, a subcontractor found working with expired insurance, an insurer asking for a vendor list nobody could produce, or a departure that took the only mental index of the vendors with it.

Two adjacent cases are worth naming so nobody buys the wrong build. If the records that need tracking are the agreements themselves — renewal dates, notice periods and signed contracts — rather than the vendor entity, the structure is different and our SharePoint contract management system engagement is the one that fits. And if what you need is a quality management system with supplier qualification and audit modules as part of ISO compliance, that is the broader engagement our SharePoint quality management system page covers.

Everything produced is yours from day one: the list, the fields, the flows and the documentation live in your own Microsoft 365 tenant, never in ours. The system is ordinary SharePoint and ordinary Power Automate, so any competent Microsoft partner — or your own team, after the walkthrough — can change it later without us. How the fixed fee is set and what is agreed before work starts is spelled out on our fixed-fee process page.

You approve the price before we begin

A fixed fee is attached to the outcome and agreed in writing before work begins, so the incentive to work efficiently sits with us. Scope changes are agreed in writing first. 30 days of hypercare after handover are included.

Get my fixed-price proposal →

FAQ

Questions people ask before booking

A single list holding every approved vendor your company does business with, with agreed fields on each one: legal name, tax ID, primary contact, category, internal owner, insurance expiry date, W-9 date and compliance status. On top of that sit an onboarding intake form, a new-vendor approval route, scheduled expiry alerts for certificates and tax forms, and permissions that decide who sees which vendors.

Usually not. The vendor register, the fields, the views, the onboarding form, the approval routing and the expiry alerting all run on licenses most companies already hold. No extra seats, no per-vendor fees, no new login for your team.

A scheduled flow runs each morning, reads the vendor list, and picks up every vendor whose insurance certificate or W-9 falls inside your warning window. It emails the named owner, posts to a Teams channel where you want one, and writes the reminder date back to the item so nobody gets chased twice.

Yes, and it is the decision that deserves the most thought in the whole build. Most companies land on a restricted list for the full register, filtered views for each team, and a short list of deliberate exceptions recorded in writing. We agree that model with you before anything is configured.

They load in waves, active vendors first and inactive ones last or not at all. Someone on your side has to supply the detail that is not in the accounting system, because insurance expiry dates and internal owners often live in a spreadsheet or in one person's memory. We plan that work rather than assume it is free.

A contract system manages executed agreements: renewal dates, notice periods, signed documents. A vendor system manages the suppliers themselves: onboarding, compliance documents, categories, contacts, performance notes. Many companies need both. The contract system tracks what you signed with a vendor; this system tracks whether the vendor itself is still approved to do business with you.

Ready for a fixed price on your vendor register?

A senior US-based engineer talks it through with you first, at no cost. If there is work worth doing, you get a written scope with one price, and you approve it before anything starts.

Free consultation · Written fixed price before any work starts · Reply within one business day

Book a free consultation

See what your SharePoint project would take

Tell us what you’re trying to fix. We reply within one business day, and you get a written fixed-fee proposal to approve before any work begins.

Step 1 of 2: What do you need?

How can we help? Pick one

Tap to add, or type your own:

Step 2 of 2: Where should we reply?

Used only to contact you about this inquiry.

We reply within one business day. Fixed price approved before any work begins. We don’t sell your information.

Tell us what you’re trying to fix — a report, an approval process, an intranet, a Copilot rollout. We scope it as a fixed-fee project, you approve, and a senior engineer delivers in 2–4 weeks.

  • Fixed-fee scope agreed before any work starts
  • Senior, US-based Microsoft engineers — no handoffs
  • Typical 2–4 week delivery
  • 30 days of post-delivery hypercare included
Book my free consultation