The contract is redlined, the business sponsor wants the vendor live by quarter end, and screening has just returned something nobody planned for. What your team does in the next 48 hours is what a prosecutor or an examiner will read later. The Department of Justice's Evaluation of Corporate Compliance Programs puts the question in one line: "Does the company track red flags that are identified from due diligence of third parties and how those red flags are addressed?"
Most findings don't end a deal. They get explained, mitigated or priced into the contract. A small set should stop it until someone with authority has looked at the evidence and put their name on the decision. Below are eight of them, each with what it looks like in the file, the test that separates noise from a real problem and the point at which you walk away.
None of this is legal advice. Scope varies by regulator, entity type and jurisdiction, so take the edge cases to counsel.
The Short Answer
Eight due diligence findings should stop a vendor deal until they are resolved: owners nobody will identify, sanctions matches on owners or affiliates, credible fraud or bribery coverage, PEP links with no business rationale, payment requests to unrelated or offshore accounts, going-concern warnings on a critical vendor, a flat refusal to share security evidence, and registration data that points to a shell. Walk away when proceeding would be unlawful or when the vendor refuses to resolve the flag.
What vendor due diligence red flags look like
A finding you can't file & forget
In vendor due diligence, a red flag is a fact that changes what you're willing to believe about a third party until it is resolved. That makes it different from a gap. A missing insurance certificate is a gap: you ask, it arrives, the file closes. An owner nobody will name is a flag, because the silence itself tells you something.
The DOJ compliance program guidance (updated September 2024) tells prosecutors to assess whether a company understands "the qualifications and associations of third-party partners, including the agents, consultants, and distributors that are commonly used to conceal misconduct," and whether it "knows the business rationale for needing the third party in the transaction." It also asks whether the company keeps track of third parties that fail due diligence so they are "not hired or re-hired at a later date." For banks, the Interagency Guidance on Third-Party Relationships (OCC, FDIC and Federal Reserve, June 2023) adds a plain instruction: "If a banking organization uncovers information that warrants additional scrutiny, the banking organization should consider broadening the scope or assessment methods of the due diligence."
Looking away carries its own exposure. The FCPA Resource Guide (DOJ and SEC, Second Edition, July 2020) explains that a person has the requisite knowledge when he is "aware of a high probability of the existence of such circumstance." A flag left unopened in the file is hard to square with that standard.
Nearly all due diligence red flags end in one of three dispositions. Write them into policy before the first hard case arrives.
| Disposition | Use it when | Who signs | What goes in the file |
|---|---|---|---|
| Stop | Proceeding would be unlawful, or the vendor refuses to resolve the flag | Compliance or legal, with the business informed | The finding, the evidence, the decision and a do-not-engage marker |
| Escalate | The flag is real but the facts are incomplete | A named approver above the analyst, with a deadline | Open questions, what was requested and the date it is due |
| Mitigate & proceed | The risk is understood and a control or contract term reduces it | The risk owner and the business sponsor | Residual risk, the control and the trigger that reopens the review |
Hidden or unverifiable beneficial ownership
Nobody will name the owner
Every other check on this list depends on knowing who you are checking. Sanctions, PEP and adverse media screens run against names, and a vendor whose owners are hidden gives you one name to screen: the company's. The interagency guidance puts ownership first under legal and regulatory compliance, describing due diligence that includes "evaluating the third party's ownership structure (including identifying any beneficial ownership, whether public or private, foreign, or domestic ownership)."
The guidance sets no percentage. Many programs borrow the one banks already apply to their own customers. Under FinCEN's customer due diligence rule (31 CFR 1010.230), a beneficial owner is each individual who directly or indirectly "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 opening accounts, not vendor onboarding, so treat 25 percent as a benchmark and go lower for your highest-risk tier.
Don't count on a federal registry to do the work for a U.S. vendor. FinCEN's final rule, effective August 14, 2026, made permanent the exemption of U.S. companies from beneficial ownership information reporting under the Corporate Transparency Act, an exemption first introduced by the interim final rule published March 26, 2025. Only foreign companies registered to do business in the United States still report, and they report only their non-U.S. beneficial owners. A domestic vendor has no BOI filing to hand you, which puts the burden back on your own questionnaire and the documents behind it.
In the file, unverifiable ownership tends to look like one of these:
- The chart stops at a holding company, trust or nominee and the vendor won't go further.
- Percentages that don't total 100, or that differ between the questionnaire and the corporate documents.
- Owners named with no date of birth or country of residence to screen them against.
- A recent change of ownership the vendor did not mention.
A complex structure can be legitimate. A refusal can't be assessed at all, and you can't clear what you can't see.
Sanctions screening matches on owners or affiliates
The hit sits one level up
A direct match on the vendor is the easy case. The matches that end deals late sit on an owner, a parent or an affiliate. The interagency guidance expects due diligence to determine "whether the third party itself or any owners are subject to sanctions by the Office of Foreign Assets Control."
OFAC's 50 Percent Rule is the reason owners matter. Under it, entities "directly or indirectly owned 50 percent or more in the aggregate by one or more blocked persons are considered blocked." The words "in the aggregate" carry the weight. In one of OFAC's own examples (FAQ 401), a blocked person owns 50 percent of two entities that each hold 25 percent of a third, and the third is considered blocked. A name search on the vendor alone will never surface that.
Below 50 percent you are not in the clear. FAQ 398 says the rule "speaks only to ownership and not to control," then adds that OFAC "urges caution" where blocked persons hold a significant minority interest or control an entity by other means, because such entities "may become the subject of future designations or enforcement actions by OFAC." The same FAQ warns against "entering into a contract that is signed by a blocked person." Screen the signatory.
- Confirm the match is real. Compare date of birth, nationality, address and identifiers before anyone calls it a hit.
- Total the stakes of every confirmed blocked person, direct and indirect.
- At 50 percent or more in the aggregate, stop. Counsel decides what happens next.
- Below 50 percent, escalate with the ownership math attached and record the rationale whichever way it goes.
In practice, sanctions screening misses come from process: owners never screened, lists refreshed late, alerts closed without a reason. Certa's May 2023 webinar on navigating the sanctions minefield covers the organizational and technology bottlenecks that make screening difficult and how compliance officers can use technology to run it more efficiently.

Adverse media screening hits for fraud or bribery
Allegations tied to the people you'd pay
Adverse media screening produces the noisiest queue in the program. Common names collide, decade-old stories resurface, and a regional news item about a different company with a similar name lands on your vendor. The job is triage, and four questions do most of it.
- Is it them? Match on more than the name before reading further.
- What stage? An allegation, a charge, a settlement and a conviction are four different facts.
- How recent? And are the people involved still owners or officers today?
- Does it touch the service you're buying? Invoice fraud at a payments vendor weighs more than a zoning dispute.
For bribery, the FCPA Resource Guide lists common red flags associated with third parties. They include "excessive commissions to third-party agents or consultants," "unreasonably large discounts to third-party distributors" and a consultant "in a different line of business than that for which it has been engaged." A news hit that lines up with one of those patterns in your own deal deserves more weight than the headline would get by itself.
False positives are where the analyst hours go. Certa's Adjudicate Agent gives confidence-scored, explainable calls on sanctions and adverse media hits, so analysts stop chasing false positives, and the Certa ABAC module runs anti-bribery due diligence and questionnaires on the same compliance platform as sanctions, PEP and adverse media screening. The AI works as an agent that does the triage, shows the rationale and the decision stays with a person. This matters for abac compliance because of the requirement to show who cleared the hit and why.
Concealment is often the stronger signal. A vendor that disclosed a 2019 settlement and can show the compliance program it built afterward is a different case from one you caught.
Politically exposed person links without a clear rationale
A connection nobody can explain
A politically exposed person in a vendor's ownership is a fact to understand before it is a reason to decline. U.S. bank regulators and FinCEN made the point in their joint statement of August 21, 2020: BSA/AML regulations "do not define PEPs," the term commonly refers to "foreign individuals who are or have been entrusted with a prominent public function, as well as their immediate family members and close associates," and "not all PEPs are automatically higher risk."
That statement addresses bank customers. For a vendor, the sharper lens is anti-corruption. Two of the FCPA Resource Guide's red flags describe this exact situation: "the third party is related to or closely associated with the foreign official" and "the third party became part of the transaction at the express request or insistence of the foreign official." DOJ's guidance turns the same point into a question for you: "How does the company ensure there is an appropriate business rationale for the use of third parties?"
So get the rationale in writing. Three answers settle most cases:
- Who proposed this vendor, and how was it selected over the alternatives.
- What the PEP-linked person does in the business day to day.
- Whether the official they are connected to has any say over your licenses, contracts, inspections or payments.
Ordinary answers are common. A retired official on the board of a long-established supplier that won a competitive bid is a file note and a monitoring flag. Certa's guide to enhanced due diligence processes covers when PEP involvement calls for a deeper review and what to request, including source of funds. The deal stops when nobody on your side can state the rationale in two sentences, or when the vendor arrived on the recommendation of the official whose decision you need.
Unusual payment terms & offshore bank accounts
Money routed away from the work
This one usually surfaces after everyone thinks due diligence is finished, when the vendor setup form reaches accounts payable. The FCPA Resource Guide names it without qualification: "the third party requests payment to offshore bank accounts." It sits in the same list as "third-party 'consulting agreements' that include only vaguely described services."
DOJ's guidance frames the control as four checks on a third-party contract: that "the contract terms specifically describe the services to be performed, that the payment terms are appropriate, that the described contractual work is performed, and that compensation is commensurate with the services rendered." Unusual terms fail one of the four.
- A bank account in a country where the vendor is neither registered nor doing the work.
- An account holder name that differs from the contracting entity, or payment to an individual.
- A request to split one fee across several accounts or companies.
- A large upfront payment, success fee or commission out of line with the market for that service.
- New bank details sent by email shortly before the first payment.
Some of these have ordinary explanations. Group treasury centers exist, and a subsidiary may invoice from a regional hub. What matters is whether the vendor can document the explanation and whether the account verifies against the legal entity on the contract. If it can't, and the vendor still insists, stop. Then tell accounts payable, because the request will come back as an invoice.

Weak financials or going-concern warnings
Solvent for the whole contract term
Financial vendor due diligence asks a narrower question than a credit analyst would: can this company keep performing the activity for the life of the contract? The interagency guidance points to "audited financial statements, annual reports, and filings with the U.S. Securities and Exchange Commission (SEC), among others," and, where relevant and available, to "access to funds, expected growth, earnings, pending litigation, unfunded liabilities, reports from debt rating agencies."
The loudest signal is a going-concern disclosure. Under U.S. GAAP (ASU 2014-15, Subtopic 205-40), as the Center for Audit Quality summarizes it, substantial doubt exists when it is probable that the entity "will be unable to meet obligations when due within one year of the date that the financial statements are issued or are available to be issued." For public companies, an auditor who concludes under PCAOB AS 2415 that substantial doubt remains adds an explanatory paragraph to the audit report. Read the notes and the audit report before you read the ratios.
Quieter signals count too. Audited statements that arrive late or never, a change of auditor with no explanation, covenant waivers, cash shrinking while payables grow, one customer carrying most of the revenue.
Of the eight, this flag is the one most often mitigated, and the tier decides. A low-risk vendor you could replace in a month can proceed with a monitoring trigger. For a critical activity, stop unless real protection goes into the contract and the plan:
- A parent guarantee or escrow arrangement.
- Short payment cycles and no large prepayments.
- A tested exit plan with a named substitute.
- Financial reporting covenants and a right to terminate on deterioration.
Refusal to share security evidence or audit reports
No report, no reason, no alternative
A refusal on its own doesn't make a red flag. A large cloud provider won't send you its raw penetration test, and it shouldn't. The interagency guidance anticipates this: a third party "may not share (or be permitted to share) information that a banking organization requests," and in that case the organization should "identify and document any limitations of its due diligence, understand the risks from such limitations, and consider alternatives as to how to mitigate the risks."
The guidance then spells out the alternatives. A bank may "obtain alternative information to assess the third party, implement additional controls on or monitoring of the third party to address the information limitation, or consider using a different third party." That sentence is the decision tree.
| What the vendor says | Read it as | Next move |
|---|---|---|
| "Our SOC 2 Type II is available under NDA" | Normal | Sign the NDA, then check scope, period and exceptions |
| "We can't share the pen test, but here is the summary and remediation status" | An acceptable limitation | Document it and add a contract right to updated summaries |
| "We're working toward certification" | No independent assurance yet | Compensating controls, limited data access and a dated commitment in the contract |
| "We don't share security documentation with customers" | A red flag | Escalate, and stop for any vendor that touches sensitive data or systems |
Watch also for evidence that arrives but doesn't cover what you're buying: a report scoped to a different product, a review period that ended more than a year ago, a certificate issued to a different legal entity. The guidance tells banks to consider "whether the scope and the results of the SOC reports, certifications, or assessments are relevant to the activity to be performed."
Inconsistent registration data & shell company signs
Paper company, real invoice
KYB starts with a simple match: does the entity on the contract exist, in the form it claims, where it claims? Most vendors pass in minutes. The ones that don't tend to fail on several small points at once.
- A legal name, registration number or tax ID that doesn't match the registry record.
- A formation date weeks before the engagement, set against a claimed ten-year track record.
- A registered address shared with many unrelated companies, with no operating address offered.
- No verifiable employees, premises or prior customers.
- A status of inactive, dissolved or not in good standing.
- A bank account name that differs from the registered entity.
One mismatch is usually clerical. A trading name, an old address, a recent rebrand. Ask for the certificate of incorporation and a current registry extract and most of them close.
A cluster is different. The FCPA Resource Guide's list of third-party red flags includes the case where "the third party is merely a shell company incorporated in an offshore jurisdiction," and a shell with a politically connected introducer and an offshore account is three flags from this list in one vendor. Holding companies and special-purpose entities are legal and common. A counterparty with no substance that is about to receive your money should not be approved on paperwork alone.
Catching red flags earlier with Certa
Found at intake, not at signature
Every flag above costs less to find in week one than in week six. Late discovery is mostly a sequencing problem: screening runs after the business has committed, ownership is collected after screening, and bank details arrive last. A sound vendor due diligence process front-loads the checks that can end the deal.
| Red flag | Check that finds it | When to run it | Default disposition |
|---|---|---|---|
| Hidden ownership | UBO declaration with supporting documents | Intake | Stop on refusal |
| Sanctions on owners | Screen the entity, owners and signatories, then total blocked ownership | Intake, then continuously | Stop at 50 percent or more |
| Fraud or bribery coverage | Screen the entity and principals, then run the four-question triage | Intake, then continuously | Escalate |
| PEP link | PEP screen plus a written business rationale | Intake | Escalate |
| Payment terms | Bank account verification against the legal entity | Before signature | Escalate, stop if unexplained |
| Weak financials | Audited statements, going-concern note, financial health data | Due diligence, then monitored | Mitigate by tier |
| Withheld security evidence | SOC report or documented alternative | Due diligence | Escalate |
| Registration mismatch | Registry and tax ID match, evidence of operations | Intake | Escalate on a cluster |
Certa runs that sequence on one record. Screening covers sanctions, PEP, adverse media and UBO, with KYC/KYB and AML checks built into onboarding, screening data via Castellum.AI and company data via Middesk. Between reassessments the platform pulls live data from BitSight, Black Kite, Rapid Ratings and Interos to keep vendor risk profiles current, so a flag that appears in month nine reaches you in month nine. Certa's post on automated vendor due diligence walks through what changes when the collection work stops being manual.
The record is the other half. DOJ asks whether you track red flags and how they were addressed, and on Certa every screen, adjudication and disposition is captured with documented rationale, citations and timestamps, immutable and exportable on demand. Speed doesn't have to suffer for it. Quantcast automated financial, legal, privacy and infosec checks across vendors and cut onboarding to a 7-day cycle for high-risk vendors and 5 days for low-risk ones.
Your team then works by exception: the vendors that tripped a flag, with the evidence already attached.
Sources
- U.S. Department of Justice, Criminal Division, Evaluation of Corporate Compliance Programs (updated September 2024)
- DOJ and SEC, A Resource Guide to the U.S. Foreign Corrupt Practices Act, Second Edition (July 2020)
- OCC, FDIC and Federal Reserve, Interagency Guidance on Third-Party Relationships: Risk Management, 88 FR 37920 (June 9, 2023)
- OFAC, FAQ 401, Entities Owned by Blocked Persons (50% Rule) (August 13, 2014)
- OFAC, FAQ 398, Entities Owned by Blocked Persons (50% Rule)
- FinCEN, 31 CFR 1010.230, Beneficial ownership requirements for legal entity customers
- FinCEN, Beneficial Ownership Information reporting (final rule effective August 14, 2026)
- Federal Reserve, FDIC, FinCEN, NCUA and OCC, Joint Statement on Bank Secrecy Act Due Diligence Requirements for Customers Who May Be Considered Politically Exposed Persons (August 21, 2020)
- Center for Audit Quality, Going Concern: Management and Auditor Responsibilities (April 2020)
Vendor deal red flag questions
Short answers on red flags in due diligence, where third party due diligence ends and KYB begins, and who makes the call.
What Are Red Flags in Due Diligence?
Red flags in due diligence are facts that undermine your confidence in a third party until they are resolved. The common ones are owners who can't be identified, sanctions or PEP links, credible fraud or bribery coverage, payment requests that don't match the entity, signs of financial distress, withheld security evidence and registration data that doesn't reconcile. They differ from ordinary gaps because a document alone doesn't close them. Each needs a recorded disposition: stop, escalate or mitigate.
When Should a Red Flag Stop a Vendor Deal?
Stop when proceeding would be unlawful, or when the vendor refuses to resolve the flag. Confirmed blocked ownership of 50 percent or more under OFAC's 50 Percent Rule is the first kind. A refusal to name owners, explain an offshore payment request or provide any security evidence is the second. Other flags get escalated, then either mitigated through contract terms and monitoring or declined by a named approver.
How Does Third-Party Due Diligence Differ From KYB?
KYB verifies that a business exists and who owns and controls it: registration, tax ID, beneficial owners, and sanctions and PEP screening on those names. Third-party due diligence includes that and goes further, into the areas the Interagency Guidance lists for banks, such as financial condition, information security, operational resilience and reliance on subcontractors. KYB tells you who the vendor is. Due diligence tells you whether it can do the work safely.
Who Owns the Decision to Reject a Vendor?
Your policy should name the role, and it should not be the business sponsor alone. A workable split gives compliance or legal the veto on integrity flags (sanctions, bribery, ownership), gives the risk function the call on financial and security flags, and leaves the commercial consequence with the business. For banks, the Interagency Guidance makes management responsible for developing and implementing third-party risk management practices, with the board holding ultimate oversight. Keep a record of rejected vendors so they aren't re-engaged later, which DOJ's guidance asks about directly.
Vendor Risk Management Articles
Keep reading

Vendor Risk Management
10 Vendor Onboarding Checklist Items Regulated Enterprises Miss
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


