Practical guide
OFAC screening for auto dealers: a deal-file workflow
Build a dealership OFAC review process for buyers and business customers, with useful identity comparisons, exception handling, and retained decisions.
On this page
Start with the buyer, not just the search box
An OFAC check at a dealership is a sanctions identity comparison, not a credit decision, fraud assessment, or cash-reporting determination. Establish which party is purchasing the vehicle and which additional parties your policy requires the team to check. A trading name on an invoice may not identify the legal buyer.
OFAC obligations are not confined to banks. Their application depends on jurisdiction and the activity, while the design of a screening workflow depends on the business. Do not invent a federal requirement to run one named commercial search before every vehicle sale.
Collect the facts that can resolve a common name
Use identity information obtained through the dealership’s authorized process. For an individual, a known birth date and reliable identifiers can be more useful than repeatedly changing a similarity threshold. For a business, record the legal name, jurisdiction, and registration details that are actually available.
Keep the original information and its provenance. A missing birth date in the source record is not evidence that the buyer has a different birth date. Never enter a guessed date simply to make a form pass validation.
Place the check at a defined deal checkpoint
Decide when a deal needs a completed check, who can resolve a candidate, and what happens when a required source or service is unavailable. A salesperson should not have to infer whether a timeout counts as approval.
Attach the screening reference to the internal deal record. Where your process requires a later check before delivery or payment, retain that new result rather than overwriting the first search. This is a policy design example, not a prescribed universal screening frequency.
Review the candidate before deciding the deal outcome
Synthetic example: a fictional buyer and an SDN record share a common name. The buyer has a verified full birth date; the source gives a different, reliable birth year. The reviewer records the conflict, the evidence used, and any remaining ambiguity. A name similarity percentage alone cannot settle the identity.
Keep an unresolved match assigned to the appropriate reviewer. A confirmed identity needs a separate assessment of the applicable restriction and business action; a cleared candidate does not approve financing or replace other deal controls.
Keep cash reporting separate
The IRS explains Form 8300 reporting for cash payments over $10,000 under the applicable rules. That is a separate control from sanctions screening. A completed OFAC search does not answer whether a payment is reportable, and a filed cash report does not resolve a sanctions candidate.
Use approved document storage for original identity records. SanctionsKit retains screening evidence, review decisions, notes, and supported document references; it does not store the original bytes of externally referenced documents.
A workable dealership checklist
A useful file lets the next reviewer understand the check without repeating the entire sale. See the auto dealer solution for the product workflow and the false-positive guide for identity analysis.
- Record the deal reference and exact legal parties selected under policy.
- Preserve source scope, completed result, and screening timestamp.
- Assign potential matches and incomplete checks instead of treating them as clear.
- Record per-candidate reasoning and the separate authorized business decision.
- Retain the supporting references and apply the documented retention trigger.