Back to Blog Supplier Management
11.16.2026

The supplier compliance gaps AP teams catch that nobody else is watching for

By Meredith Grace

Senior Manager Content Marketing at Medius


Odds are, somewhere in your ERP, a supplier’s insurance certificate has already expired. Nobody knows yet. The vendor was approved, the documents were checked, the record was filed, and everyone moved on. That’s what onboarding is supposed to do, and it did it well.

The trouble is what happens next, which is usually nothing, until an invoice shows up. AP tends to be the team that finds the lapse. That isn’t because AP is more careful than procurement, legal, or audit. It’s because AP looks at the supplier record more often than anyone else does. Below, we cover which supplier documents go stale on their own, what it costs when they do, and how to catch a lapse in week one instead of month seven.

Supplier compliance is validated once and assumed indefinitely

Supplier onboarding is usually done well. A new vendor submits a W-9, a certificate of insurance, and banking details. Someone verifies the documents, screens the entity against the relevant watchlists, and approves the record. The checks are real, the people running them are careful, and at the moment of approval the supplier is fully compliant.

The difficulty is that compliance is not a property a supplier has. It is a state that holds on a given date. Insurance policies renew annually and lapse when they are not renewed. Tax forms go out of date when a business changes its entity type or its legal name. Watchlists are republished continuously, and a supplier that was clear in March can appear in September without anything about that supplier changing from the buyer's point of view.

None of this is a failure of the onboarding process. Onboarding answered the question it was designed to answer, which was whether this supplier was compliant then. Nothing in that process was built to answer whether the supplier is compliant now, because answering that question requires looking again, and looking again requires a trigger. In most organizations no such trigger exists between the day a supplier is approved and the day something goes wrong. Keeping suppliers in compliance is treated as an onboarding activity when it is really a monitoring one.

Why do supplier compliance gaps surface at the payment stage?

Because the invoice is the next scheduled moment anyone looks at the supplier record.
It helps to make this explicit, as it is simple to confuse with a statement regarding thoroughness. Accounts payable does not uncover these discrepancies through greater vigilance than other teams. AP catches them simply because it interacts with the vendor profile continuously, whereas no other department has that level of contact. Procurement connects during initial sourcing and contract renewals. Legal becomes involved at contract execution. Risk and internal audit operate on review timelines spanning quarters or years. AP interacts whenever an invoice arrives, which for an active vendor can occur every few weeks or even weekly.

This comes down entirely to frequency. Had internal audit evaluated vendor profiles on a monthly cadence, they would identify these compliance issues first. Ultimately, the team with the highest cadence of reviews detects the lapse first—and within virtually all businesses, that team is accounts payable.

This dynamic demonstrates why compliance lapses are frequently long-standing before being detected. When a certificate of insurance lapses in February, it rarely gets caught in February. Instead, it surfaces only upon the vendor's subsequent invoice submission, which could be March or even August. Consequently, liability emerges on the day of expiration, whereas detection occurs on the processing date. Throughout that intervening stretch, the organization remains completely exposed without realizing it.

Shrinking that timeframe is the core objective. Achieving this begins during supplier onboarding by gathering documentation structured for continuous re-validation instead of static archiving.

The three documents that go stale on their own

Vendor master data drift is the gradual divergence between what a supplier record says and what is currently true about that supplier. Drift is not caused by error. It happens because supplier attributes have expiration dates and supplier records do not.

Three documents drift on predictable schedules, which is what makes them worth monitoring deliberately.

Getting current documents back from suppliers is its own problem, and the reason monitoring often stalls. A system that lets suppliers maintain their own records through supplier conversations removes the step where AP chases a certificate by email.

What the invoice shows that the vendor record doesn’t

Documents are only part of drift. The transaction itself carries signals that no stored record contains, and two of them matter more than the rest.

The first is a change to banking or remit-to details. A request to update payment routing is the single highest-consequence change a supplier record can undergo, and it almost always arrives through AP rather than through procurement, usually attached to or alongside an invoice. It may be entirely legitimate, since suppliers do change banks. It is also the mechanism behind most payment redirection fraud. The difficulty is that a legitimate change and a fraudulent one look identical at the point of request, and the only reliable difference is whether the change was verified through a channel the requester does not control.

The second is dormancy. Supplier records are opened readily and closed rarely. A vendor that has not invoiced in three years usually remains active in the ERP with its original banking details and its original approver, and nobody notices because nothing is happening on it. The record becomes a problem precisely when activity resumes, because a dormant supplier suddenly submitting an invoice is either a genuine re-engagement or an exploited record, and the vendor master cannot tell the difference.

Both signals share a structure worth noticing. Neither is visible in the document set, both appear at transaction time, and both require comparison against prior behavior rather than against a stored value. That is a detection problem rather than a filing problem, and it is the category fraud and risk detection is built for.

You don’t have to be the next fraud statistic.

From duplicate invoices to vendor impersonation, AP fraud comes in more forms than most teams expect. This toolkit helps you identify your risk profile and take action before it costs you.

Assess your risk

What does a stale supplier document actually cost?

The costs differ by document, and only one of them is predictable.

Tax documentation has the most predictable exposure because the consequence is defined by statute. When a payee's taxpayer identification number is missing or incorrect, the payer is required to withhold at 24% of reportable payments under IRS Publication 1281. The complication is timing. The IRS notice that surfaces a mismatch arrives after the payments were already made, so the organization reconciles backward across a period it cannot change.

Insurance is the opposite. The cost is nothing at all until there is a claim, at which point it is the full value of the claim. A contractor working uninsured on a site produces no symptoms and no variance in any report. The exposure is discovered by an incident, and the gap between lapse and incident is pure luck.

Sanctions exposure sits in between. A payment to a designated party is not corrected by returning the funds, and OFAC's published enforcement record shows penalties reaching into the millions against non-financial companies. The relevant point for AP is that screening performed once does not stay performed, because the list it was performed against keeps changing.

Across all three, the common cost is the length of the interval rather than the severity of the single event. A lapse found in week one is an email to a supplier. The same lapse found in month seven is a remediation project with a backward-looking scope.

Continuous validation beats a better onboarding checklist

The instinct when a gap is found is to strengthen onboarding, usually by adding documents to the intake list. That improves the quality of the snapshot. It does not change how quickly the snapshot goes out of date, and a more thorough check performed once a year still leaves most of the year unmonitored.

What closes the interval is treating validation as a recurring state check tied to transaction events rather than a gate at the start of the relationship.

A certificate filed as a PDF is a document. A certificate whose expiration date sits in a field is a monitorable state. Only the second can trigger anything.

Because the list changes rather than the supplier, the only screening that stays meaningful is screening repeated against the current list.

Checking supplier status when an invoice arrives catches drift at the earliest moment the organization has a reason to care, and it scales with activity, so active suppliers get checked more often than dormant ones.

Confirm a remit-to change through a known contact method on file, never through the channel the request arrived on. This is a workflow rule rather than a technology feature, and it prevents more loss than any other item here.

A supplier returning to activity after a long gap should route for confirmation rather than straight to payment.

Most document decay persists because refreshing a certificate requires someone in AP to notice, ask, and follow up. Removing that manual step is usually the difference between a policy that exists and one that runs.

Medius supports this by holding supplier data as structured, monitorable fields rather than stored attachments, so expiration and status become conditions the workflow can act on. Fraud and risk detection handles the transaction-level half, flagging banking changes and dormant-record reactivation against prior behavior at the point the invoice arrives rather than in a later review.

You’re responsible for what you can’t see.
Let’s fix that.

Operational risk hides in manual workflows, unreviewed vendors, and disconnected systems. This practical toolkit helps you identify the gaps and build better controls before something goes wrong.

Get the toolkit

Compliance that holds between onboarding and payment

Nothing described here requires a department to have been negligent. It requires only that validation happened once and time continued to pass. The organizations that handle this well are not the ones with stricter onboarding. They are the ones that stopped treating compliance as a status a supplier was granted and started treating it as a condition that has to be true on the day a payment goes out.

A reasonable first step is to pull every active supplier record and check two things: how many have a document on file that has already expired, and how long ago the most recent watchlist screening ran. Both answers are usually worse than expected, and both are measurable today without changing a single process.

See how Medius helps AP teams keep supplier compliance current between onboarding and payment.

Frequently asked questions about supplier compliance

By storing the expiration date as a field in the supplier record rather than relying on the document itself, then scheduling a check against that field. A certificate filed as an attachment is a document someone has to open and read. An expiration date held as data is a condition a workflow can test automatically and act on before the lapse happens.

Frequency should follow each document's own cycle rather than a single calendar rule. Certificates of insurance typically carry a 12-month validity and should be checked ahead of their stated expiration. Tax forms need re-verification when a supplier's legal name or entity type changes, which suppliers do not always report. Sanctions screening is the exception, since the list changes rather than the supplier, so it needs to run on a recurring schedule regardless of supplier activity.

The payer becomes responsible for backup withholding at 24% of reportable payments, a rate set in IRS Publication 1281. For a missing TIN the obligation begins immediately and continues until a TIN is received. For an incorrect TIN, withholding must begin no later than 30 business days after the IRS issues a CP2100 or CP2100A notice, which typically arrives well after the payments were made.

Yes, because a screening reflects the list as it existed on the day it ran. Watchlists are updated continuously, and designations added later do not propagate backward into a supplier record, so a vendor approved two years ago was checked against a list that no longer exists.

Both, at different points in the supplier lifecycle. Procurement validates compliance when a supplier is selected and onboarded. AP validates it at transaction time, when the supplier is paid. Neither replaces the other, and gaps usually appear not because one function failed but because no check was scheduled between them.

Medius Financial Census 2026

87% of finance pros have ignored suspected fraud. That's just one finding. See what 2,386 finance leaders revealed about fraud, late payments, AI, and the profession's future.

Get the report

Ardent Partners' State of AP in 2026

AI is changing what AP teams can do, and fast. Get leading analysts at Ardent Partners' take on where the industry is headed.

Get the report

Webinar: Preparing for agentic AI in AP

In this webinar with SSON, see how leading finance teams are moving from automation to autonomous AP, with real governance built in.

Watch the webinar

Discover accounts payable benchmarks

Learn the efficiency metrics that matter for AP teams and the benchmarks derived from thousands of Medius customers around the globe.

Get the report

Questions about AP automation?

Let's talk through it. A 30-minute conversation with a Medius expert costs you nothing and might save you a lot.

Book a consult

Ready to transform your AP? 

Book a Demo Contact Us