Most onboarding checklists were written by the team that pays the vendor. W-9, bank details, certificate of insurance, signed contract, done. Then an examiner, an auditor or a fraud loss asks what the list never did. Who owns this company? Who confirmed that bank account belongs to it? Who decided this vendor could skip a security review, and where is that written down?
Below are ten items that tend to be missing, done late, or done once on paper and never again. They run in the order a clean onboarding runs: tier the vendor first, verify its tax identity and payment details, establish who owns it and screen those owners, then scope the security, anti-bribery, subcontractor and contract work to the tier. The master record comes last because it is where every earlier answer has to land.
Each item names the rule or guidance behind it, what the control looks like when it works, and the evidence to keep. Scope varies by entity type and jurisdiction, so confirm which of these regimes bind you with counsel.
The Short Answer
Regulated enterprises usually collect the W-9, the bank form and the contract. What they miss are the checks no single team owns: inherent risk tiering at intake, TIN matching and bank account verification before the first payment, beneficial ownership and sanctions screening of the owners, a security questionnaire scoped to data access, anti-bribery and conflict declarations, subcontractor disclosure, regulatory contract clauses and duplicate checks on the vendor master.
Why a vendor onboarding checklist breaks in regulated enterprises
One flat list, five different owners
A vendor onboarding checklist usually fails in one of three ways. It is flat, so the office caterer and the cloud provider holding customer records answer the same questions. It belongs to one function, typically accounts payable or procurement, so the items that belong to compliance, security and legal are either absent or reduced to a yes or no box. And it is point-in-time: the bank account verified in March is never checked again when a change request arrives by email in October.
Regulators describe the opposite design. The Interagency Guidance on Third-Party Relationships from the OCC, FDIC and Federal Reserve (88 FR 37920, June 9, 2023) states that "not all third-party relationships present the same level or type of risk and therefore not all relationships require the same extent of oversight or risk management." It also puts the work on you: each banking organization is expected to analyze the risks of each relationship and calibrate its processes to match. That guidance is written for banks, but a life sciences sponsor or a defense prime will recognize the same expectation in its own regime.
So the fix is a different shape of list. A short set of checks every vendor passes, a tier that decides what else applies, and a named owner for each item. Certa's own primer on effective third-party onboarding steps covers the sequence. The ten items here are the ones to add once that sequence exists.
Inherent risk scoring & vendor risk tiering
Tier before you ask anything else
Tiering by spend is the common shortcut, and it gets the answer wrong in both directions. A low-cost API vendor can touch every customer record. A seven-figure facilities contract may touch none. Inherent risk scoring asks what could go wrong before any control is considered, and it needs only a handful of questions the business requester can answer in a few minutes.
- What data will the vendor store, process or see, and how much of it?
- Will it have access to your network, systems or facilities?
- Does it support an activity your regulator would treat as critical or important?
- Does it deal with your customers, patients or government officials on your behalf?
- Where will the work be done, and will any of it be subcontracted?
- How quickly could you replace it?
The Interagency Guidance gives banks the test for the top tier. Critical activities are those that could cause "significant risk if the third party fails to meet expectations," have "significant customer impacts," or have "a significant impact on a banking organization's financial condition or operations." Whatever your scale, write the scoring rule down and record every override. Vendor risk tiering that lives in an analyst's head cannot be defended in an exam, and every item that follows depends on it.
TIN matching against IRS records
A W-9 is a claim, not a check
A signed Form W-9 is a self-certification. It tells you what the vendor says its name and taxpayer identification number are. TIN matching tells you whether the IRS agrees. In the agency's words, the service "lets you validate TIN and name combinations before submitting an information return," and the IRS taxpayer identification guidance limits it to "payers and their authorized agents that submit information returns" who are listed in the IRS Payer Account File.
The mechanics are in IRS Publication 2108. Interactive matching accepts up to 25 name and TIN combinations at a time with results in real time. Bulk files may carry up to 100,000. Each result comes back as a code: 0 means the combination matches IRS records, 2 means the TIN is not currently issued, and 3 means the name and TIN do not match.
Most programs own this control and run it too late. Tax matches the file in the fourth quarter, weeks before 1099s go out, by which time the vendor has been paid all year under a name the IRS does not recognize. A mismatch that reaches a filed return can come back on a CP2100 notice and start the B notice cycle described in Publication 1281, with backup withholding at the current rate of 24 percent if it is not cured. Run the match at onboarding, block activation on anything other than a 0, and send the vendor back to correct the W-9. Vendors that document foreign status on a Form W-8 follow a separate path that your tax team should define.
Bank account verification before first payment
Confirm the account, then confirm it again
The FBI's 2025 IC3 Annual Report counts 24,768 business email compromise complaints and $3,046,598,558 in reported losses for the year. A large share of that story is ordinary: someone in accounts payable received a polite email with new remittance details and keyed them in.
Payment rules now name the pattern. Nacha's fraud monitoring amendments define "False Pretenses" as the inducement of a payment by a person misrepresenting identity, authority or "the ownership of an account to be credited," a definition Nacha says covers business email compromise and vendor impersonation. Phase 1 took effect March 20, 2026 for all ODFIs and for non-consumer originators with 6 million or more ACH originations in 2023. Phase 2, effective June 19, 2026, extends the monitoring requirement to all other non-consumer originators. If your company originates ACH credits to suppliers, you are expected to have risk-based processes aimed at catching payments induced by fraud.
- Bank account verification runs against an account-ownership source, not against a voided check the vendor uploaded.
- A callback goes to a phone number you sourced independently, never one taken from the request itself.
- No bank detail changes on the strength of an email alone, whoever appears to have sent it.
- The person who enters bank details cannot approve them.
- The first payment is held until verification is recorded on the vendor file.
- A change of bank details reopens the same control as a new vendor.
The last line is where mature programs still slip. Verification at onboarding is common. Verification at change is rare, and change is when the fraud happens.

Beneficial ownership verification for every entity
Know who is behind the legal name
Banks are told to do this in plain terms. Due diligence under the Interagency Guidance may include "evaluating the third party's ownership structure (including identifying any beneficial ownership, whether public or private, foreign, or domestic ownership)." Outside banking, the anti-bribery and sanctions items further down this list cannot be done without it. You cannot screen owners you have not identified.
For a threshold, most teams borrow from FinCEN's customer due diligence rule at 31 CFR 1010.230. It defines a beneficial owner as each individual who owns "25 percent or more of the equity interests" of a legal entity customer, plus "a single individual with significant responsibility to control, manage, or direct" it. That rule governs covered financial institutions and their customers, not your suppliers. It is still the definition examiners and auditors already know, which makes it a defensible place to start.
Two gaps recur. One is collection without verification: the vendor types names into a form and nobody compares them with a corporate registry, a formation document or a commercial data source. Beneficial ownership verification means that comparison happened and you can show what it was compared against. Don't expect a federal filing to do it for you. FinCEN's beneficial ownership page now states that U.S. companies are exempt from BOI reporting, so for a domestic vendor the declaration you collect is the record.
The other gap is coverage. Ownership gets checked for the entity that signed the master agreement and not for the affiliate that invoices you or the remit-to entity that receives the money. Check every legal entity you contract with or pay. Depth can scale with tier. Coverage should not. For the wider identity picture, see Certa's KYC verification essentials.
Sanctions screening on owners, not just the company
The entity can be clean & still be blocked
Screening the vendor's legal name against the SDN List answers a narrower question than the law asks. OFAC's 50 Percent Rule, in the wording of FAQ 401, treats as blocked the property of "entities directly or indirectly owned 50 percent or more in the aggregate by one or more blocked persons." The entity does not have to be listed. Ownership alone does it.
Read "in the aggregate" and "indirectly" slowly. Two blocked persons holding 25 percent each add up to 50. A blocked person who owns half of a holding company that owns half of your vendor makes the vendor blocked, which is the first worked example in the FAQ. That arithmetic is the practical reason to collect owners at 25 percent rather than at a majority stake.
Control is treated differently, and it still matters. FAQ 398 says an entity controlled but not 50 percent owned by blocked persons is not automatically blocked. OFAC nonetheless "urges caution" and warns against "entering into a contract that is signed by a blocked person." So screen the signatory and the directors too.
Among the root causes of violations listed in OFAC's Framework for OFAC Compliance Commitments is "improper or incomplete due diligence" on customers, "such as their ownership," and the Framework expects the same diligence on supply chain partners and counterparties. For banks, the Interagency Guidance says the same thing from the other side: determine "whether the third party itself or any owners are subject to sanctions." Sanctions screening at onboarding is a snapshot, so rescreen when lists update and when ownership changes. Keep the rationale for every cleared hit. Other regimes, including the EU's and the UK's, apply their own ownership and control tests, so confirm thresholds with counsel.
Information security questionnaire scoped to data access
Ask what the access justifies
Two failures share one cause. Either every vendor receives the same long questionnaire, so the landscaper is asked about its key management practices and the queue backs up for weeks. Or the questionnaire is triggered by spend, so a small vendor with production access never receives one. Both come from scoping on the wrong variable.
The right variable is access. The Interagency Guidance frames security due diligence around "access to a banking organization's systems and information" and "the extent to which the third party applies controls to limit access to the banking organization's data and transactions." Let the intake answers from the tiering step choose the question set.
| Access profile | What the information security questionnaire should cover |
|---|---|
| No data, no system access | A short attestation. No full questionnaire. |
| Confidential business data held in the vendor's environment | Core controls: access management, encryption, incident response, resilience, plus an independent report such as a SOC 2 Type II where one exists. |
| Personal or regulated data (for example protected health information) | The core set plus privacy, retention, breach notification and the vendor's own subcontractors. For protected health information, a business associate contract under 45 CFR 164.504(e). |
| Access to your network, systems or privileged credentials | The core set plus identity, multifactor authentication, endpoint and remote access controls, and offboarding of the vendor's staff. |
| Covered defense information on a DoD contract | The NIST SP 800-171 requirements that DFARS 252.204-7012 applies to covered contractor information systems, and the cyber incident reporting duty. |
Scoping shortens the list. Pre-filling shortens the wait. A vendor that has already published a trust page or answered you last year should not start from a blank form, which is the idea behind Certa's SmartFill AI form completion, a capability the platform now describes as a Pre-Fill Agent that drafts answers for a person to review.
Anti-bribery & conflict of interest declarations
Two declarations, one from each side
The Justice Department's Evaluation of Corporate Compliance Programs (updated September 2024) tells prosecutors that a well-designed program "should apply risk-based due diligence to its third-party relationships," with particular attention to "the agents, consultants, and distributors that are commonly used to conceal misconduct." It then asks whether there is "an appropriate business rationale for the use of third parties" and whether "compensation is commensurate with the services rendered."
Most onboarding flows capture half of this. The vendor signs a code of conduct. What is missing is the set of specific declarations that would change your decision, and the declaration from your own side of the table.
- From the vendor: any government official or close relative among its owners, directors or key staff. Whether it will deal with officials on your behalf. Whether it uses sub-agents. Any bribery or corruption investigation in a stated look-back period. Confirmation that it maintains its own anti-bribery policy.
- From the requester: no financial interest in the vendor, no family or close personal relationship with its owners, no gifts or hospitality received during selection, and a written business rationale for choosing this vendor.
The requester declaration is the one that gets skipped, and it is the cheapest control on this list. A yes answer shouldn't block the vendor. It should route to compliance with the facts attached.
Fourth parties & subcontractor disclosure
Ask who else touches the work
Your vendor's vendors are your exposure without being your counterparties. The Interagency Guidance asks banks to evaluate "the volume and types of subcontracted activities and the degree to which the third party relies on subcontractors," including "how the third party selects and oversees its subcontractors." It adds two considerations onboarding forms rarely capture: the geographic location of a subcontractor and "dependency on a single provider for multiple activities."
The agencies were careful about the limit. In the preamble they acknowledge the concern that banks would be "expected to assess or oversee all subcontractors of a third party," and say they revised the text to focus on evaluating the third party's own processes for overseeing them. You are assessing how your vendor manages its chain. You are not onboarding the chain.
Sector rules go further where the data is sensitive. Under DORA Article 30(2)(a), a financial entity's ICT contract must indicate whether subcontracting of a service supporting a critical or important function is permitted and on what conditions. HIPAA's business associate contract terms require the associate to ensure that subcontractors handling protected health information "agree to the same restrictions and conditions." DFARS 252.204-7012(m) requires contractors to include the clause in subcontracts that involve covered defense information.
At onboarding, that comes down to three things to collect: who the subcontractors are, where they operate, and how you will be told when either answer changes. Compare the disclosed list across your critical vendors and you have a first view of concentration risk at no extra cost.
Regulatory clauses in the onboarding contract
Check the clauses before the signature
Contracts get signed on the vendor's paper while the risk review is still open. Six months later the security team asks for an audit and finds there is no right to one. Here the fix is a matter of order: the tier decides which clauses are mandatory, and the vendor cannot go active until legal has confirmed them or someone with authority has accepted the gap in writing.
| Regime | Clauses to confirm before signature |
|---|---|
| Interagency Guidance (US banking organizations) | Right to audit and require remediation. Notice of, or consent to, subcontracting. Default and termination. A statement that the activity is subject to regulatory examination and oversight. |
| DORA, Regulation (EU) 2022/2554, Article 30 (applies from January 17, 2025) | For all ICT contracts: service description, data processing and storage locations, data return on exit, incident assistance, cooperation with authorities, termination rights. For critical or important functions, add access, inspection and audit rights and an exit strategy with a transition period. |
| HIPAA, 45 CFR 164.504(e) | Business associate contract terms: permitted uses and disclosures, safeguards, breach reporting, and the same restrictions flowed to subcontractors. |
| DFARS 252.204-7012 (DoD contracts) | The clause itself flowed down where covered defense information or operationally critical support is involved, including the duty to rapidly report cyber incidents, defined in the clause as within 72 hours of discovery. |
The table is a starting point and no substitute for the texts. The guidance uses "may" and "typically" for banks. DORA Article 30 uses "shall." Your counsel decides which language is negotiable.
Clean vendor master data & duplicate checks
One legal entity, one record
Every check above produces a fact about a legal entity. If that entity exists three times in the ERP under three spellings, the facts attach to one record and the payments flow through another. Duplicates are how a vendor that failed screening gets paid, and how a fraudulent bank change lands on a record nobody is watching.
Duplicates start at the new vendor setup form. A requester who can't find "Acme Industrial Supply LLC" under "ACME Ind. Supply" creates a new one. So the duplicate check belongs in the form itself, before the record exists.
- Normalize the legal name (case, punctuation, entity suffix) and compare it with existing records.
- Match on tax ID and on bank account number. Either one matching an existing record stops creation and routes to the vendor master owner.
- Match on address and web domain to catch the same company registered under a trading name.
- Link each record to its parent, and hold remit-to addresses as children of the legal entity, not as separate vendors.
- Assign an owner to each field group: tax to tax, bank to treasury, risk tier to third-party risk.
- Deactivate records with no activity inside your retention policy's window, so dormant vendors cannot be revived without rechecks.
There is a regulatory reason as well. The Interagency Guidance calls out "maintaining a complete inventory" of third-party relationships as the basis for knowing whether risks have changed. Clean vendor master data is that inventory. If it is wrong, every report built on it is wrong in the same direction.
Automating the vendor onboarding process with Certa
Checks that run while the vendor registers
Ten checks, five owners and one impatient business sponsor is a coordination problem before it is a compliance problem. The usual result is a vendor onboarding process that runs in sequence, with each team waiting for the last to finish, and a file assembled afterward from inboxes.
The Certa supplier onboarding module runs them as one flow. The vendor is invited to a self-service form in its own language and registers itself. Tax and banking details are verified live as it registers. Sanctions, UBO and risk-domain screening run automatically, and each vendor is scored across multiple risk domains. On Certa's supplier onboarding page the result is stated as "reducing fraud and payment rejections by 95%" within live tax + banking checks." Sanctions and adverse media hits go to Certa's Adjudicate Agent, which returns confidence-scored, explainable calls for an analyst to accept or override.
Whatever tooling you use, this is the table to hold your own program against. If a row has no evidence or no owner, that is your gap.
| Checklist item | Evidence to keep | Typical owner |
|---|---|---|
| Inherent risk tier | Scored intake, tier, override rationale | Third-party risk |
| TIN match | Result code and date with the W-9 | Tax or AP |
| Bank account verification | Verification result, callback record | AP or treasury |
| Beneficial ownership | Declaration and what it was verified against | Compliance |
| Owner sanctions screening | Lists, date, disposition and reasoning per hit | Compliance |
| Scoped security questionnaire | Scoping answers, responses, findings | Information security |
| Anti-bribery and conflict declarations | Both declarations, escalations | Ethics and compliance |
| Subcontractor disclosure | Disclosed list, notification terms | Third-party risk |
| Regulatory clauses | Clause checklist, exception approvals | Legal |
| Vendor master record | Duplicate check, change log | Vendor master owner |
Done well, supplier onboarding ends with a vendor that is approved, payable and already documented for the next exam.
Sources
- OCC, FDIC and Federal Reserve, Interagency Guidance on Third-Party Relationships: Risk Management, 88 FR 37920 (June 9, 2023)
- IRS, Taxpayer Identification Number (TIN) Matching
- IRS, Publication 2108, Federal Agency TIN Matching Program (Rev. 11-2024)
- IRS, Publication 1281, Backup Withholding for Missing and Incorrect Name/TIN(s) (Rev. 12-2023)
- IRS, Backup withholding
- FBI Internet Crime Complaint Center, 2025 IC3 Annual Report
- Nacha, Risk Management Topics: Fraud Monitoring Phase 1 (effective March 20, 2026, with Phase 2 on June 19, 2026)
- FinCEN, 31 CFR 1010.230, Beneficial ownership requirements for legal entity customers
- FinCEN, Beneficial Ownership Information Reporting (alert updated August 11, 2026)
- OFAC, FAQ 401, Entities Owned by Blocked Persons (50% Rule)
- OFAC, FAQ 398, control and the 50 Percent Rule
- OFAC, A Framework for OFAC Compliance Commitments
- U.S. Department of Justice, Criminal Division, Evaluation of Corporate Compliance Programs (updated September 2024)
- Regulation (EU) 2022/2554 (DORA), Articles 30 and 64, EUR-Lex
- 45 CFR 164.504(e), business associate contracts (eCFR)
- DFARS 252.204-7012, Safeguarding Covered Defense Information and Cyber Incident Reporting (MAY 2024), Acquisition.gov
Vendor onboarding questions from compliance teams
Four vendor onboarding questions that come up whenever a compliance team reviews a checklist it inherited from accounts payable.
What Should a Vendor Onboarding Checklist Include?
It should include a baseline every vendor passes and a tiered set that depends on inherent risk. The baseline is legal identity, a matched tax ID, a verified bank account, beneficial ownership, sanctions screening of the entity and its owners, a conflict of interest declaration and a duplicate check on the vendor master. The tiered set adds a scoped security questionnaire, anti-bribery due diligence, subcontractor disclosure and regulatory contract clauses. Give every item a named owner and a defined piece of evidence.
How Long Should Supplier Onboarding Take?
No regulator sets a number, so the honest answer depends on tier. Low-risk vendors that pass the baseline checks should clear in days, and high-risk vendors take longer because the security, ownership and contract work is real. As one reference point, Certa reports that Quantcast's vendor onboarding was "cut to a 7-day cycle for high-risk and 5 days for low-risk." Measure your own cycle time by tier and by step, because the delay usually sits in handoffs between teams and rarely in the checks themselves.
Who Approves a New Vendor Setup Form?
At least two people, and neither should be able to pay the vendor alone. The business requester confirms the need and the rationale, procurement or the vendor master owner confirms the record is complete and not a duplicate, and bank details are approved by someone other than the person who entered them. Higher tiers add compliance, security and legal sign-off before activation. Record each approval on the vendor file with a name and a date.
Do Low-Risk Vendors Need the Full Checklist?
No. The Interagency Guidance says plainly that "not all relationships require the same extent of oversight or risk management." Low-risk vendors still need the checks that protect payments and legal exposure: tax ID, bank account, ownership, sanctions and the duplicate check. They can skip the full security questionnaire and the deeper anti-bribery work, provided the tier that excuses them is documented.
Vendor Risk Management Articles
Keep reading

Vendor Risk Management
8 Due Diligence Red Flags That Should Stop a Vendor Deal
Certa · November 19, 2026

Vendor Risk Management
How to Review a Vendor's SOC 2 Report
Certa · November 19, 2026

Vendor Risk Management
How to Tier Vendors by Risk: A Criticality Model for Regulated Enterprises
Certa · November 19, 2026


