Why we drop OFAC from the cover sheet — it's marketing, not data
Most business-verification platforms splash an OFAC Specially Designated Nationals List match on their cover sheet. It looks official. It looks thorough. It moves the needle on a sales call. The problem: a small-business entity hit on OFAC is so rare that including it signals you don’t understand what actually matters in a credit decision.
OFAC is not your job anyway
Your bank or lender already runs OFAC screening. Compliance does it. It’s a legal requirement for any entity you lend to, and your compliance team has the real tools, the real refresh rates, and the real liability if a hit gets missed. A third-party business-verification vendor adding an OFAC match to a report is like a tire shop including a brake test on your receipt when you came in for a rotation. It’s not harmful, but it’s not why you’re there, and it muddies the value prop.
An OFAC hit on a small business is mathematically unlikely. The SDN list targets foreign governments, sanctioned entities, terrorist organizations, and known bad actors. A legitimate LLC operating a fleet or a distribution center will not be on it. The false positive rate creeps higher when you’re matching against partial names, but the hit rate itself stays near zero. You are not uncovering hidden risk by scanning it; you are performing security theater.
Your real risk questions don’t live in OFAC
What you actually need to know: Is the entity registered and in good standing? Who owns it? What is their Secretary of State and USDOT history? Are there UCC liens, judgments, or tax liens that tell you the company has borrowed and not repaid? Are the stated officers and addresses consistent across multiple records, or is the entity a shell?
An OFAC match tells you none of that. It tells you whether someone’s legal name appears on a government list of sanctioned parties. For a small-business underwriting decision, that is a yes/no gate, not a risk metric. Either the entity is blocked by law or it is not. If it is, you do not lend. If it is not, you move on to the actual due diligence: ownership structure, payment history, business registration stability, collateral quality.
Including OFAC on a cover sheet crowds the page with a zero-value data point and forces the underwriter to either ignore it (which is fine, but then why is it there?) or to treat it as if it matters when it does not.
The UX cost is real
A cover sheet should answer the highest-confidence, highest-impact questions first. An underwriter opening a verification report needs to see: entity name, registered address, state of incorporation, principal officers or members, USDOT and FMCSA status if relevant, registered agent, and the most recent filing date. Those fields tell you whether the entity is real, who to contact, and whether the basic registration is current.
An OFAC match, when it appears, adds cognitive load. The underwriter has to parse it. They have to decide whether to trust it or run their own check. They have to explain it to the credit committee if they want to ask the borrower about it. It is a data item that consumes report real estate and decision bandwidth without reducing risk or enabling approval.
A cleaner cover sheet with the fields that drive underwriting decisions · entity status, ownership, USDOT history, and liens · makes the document faster to use and more credible. It says: this report answers the questions you actually have.
OFAC screening should live in compliance, not underwriting
If your bank wants an OFAC refresh on small-business entities, that should be a compliance process, not a part of the verification report. Compliance runs it on every borrower at origination and refresh, tied to your real compliance platform and your audit trail. The underwriting team gets a clear statement: “Compliance has screened this entity and found no OFAC match” or “Compliance flagged a potential match; refer to compliance team.” That separates the concern from the credit decision and puts it in the right place.
A verification report that includes OFAC conflates two separate risk controls. It suggests that OFAC screening is part of entity verification when it is not. It is a separate, mandatory control that belongs in your compliance workflow.
Bottom line
OFAC on a cover sheet is a feature designed to impress, not to underwrite. Small-business entities are not sanctioned. Your bank screens OFAC separately. The data point adds noise, not insight. A clean, focused verification report that centers on registration status, ownership, and commercial history will serve your underwriting team better and move deals faster than one that pads the page with low-probability compliance checkboxes. Strip the theater. Keep the data that matters.