Practical guide
How auto dealers can screen buyers for OFAC matches
Run an OFAC check for each required buyer, connect potential matches to the deal file, and handle purchaser changes before the next sales checkpoint.
On this page
Start with the legal buyer on the deal
Use SanctionsKit at the sale, delivery or payment checkpoint your dealership has chosen. Gather the buyer's legal name, known identity details and deal reference. Add a co-buyer or purchasing company when your approved procedure requires it. A credit pull is not evidence that this sanctions check happened.
Open New screening. Rehearse with invented buyers in Sandbox, which uses synthetic records. Actual checks need authorized Production access and the required available sources.
Give each required party its own result
Enter the subject type and reliable facts that distinguish the buyer. Keep a partial birth date at its known precision. For a fleet purchase, screen the company separately from an employee when both are required.
Under Save for future checks, use Create a saved profile for an ongoing customer and enter a deal-and-party ID in External reference. For a one-time check, select This screening only. Choose the approved policy or permitted OFAC sources, then Run screening. Save the result ID in the deal file.
Pass a possible match to the reviewer
Open candidates in the Review queue. Compare each source entry with the buyer's reliable dates and identifiers. Record an identity finding and reason for each candidate; a name score cannot make the decision.
For a fictional buyer with a common name, a full birth date may help distinguish them. If the source has no date, that is a gap rather than a conflict. Keep the deal at its agreed checkpoint while evidence or approval is outstanding. Failed checks remain incomplete.
Keep the deal record useful to the next employee
Use Screening history to retrieve the result and source versions. Link any required case, review findings and separate business decision from the deal file.
Keep original ID documents in approved storage. An administrator configures Settings → Organization documents, and reviewers use Link original document. SanctionsKit keeps that reference, not the scan. Cash-payment reporting, credit and fraud checks remain separate work.
Check a changed purchaser or refund recipient
Suppose a fictional fleet order switches to a different legal purchasing company. Screen the new company and retain both result references with the amendment. Apply the same rule to a new refund recipient when required; another party's no-match cannot cover it.
Use Monitoring for continuing commercial customers selected by policy. For a one-time sale, finish the case and retain evidence under the approved rules. Test the sales-to-review handoff with a fictional deal before relying on it.
Sources and references
Authority and technical sources
SanctionsKit documentation
Frequently asked questions
Does a dealership credit pull replace an OFAC check?
A credit pull does not by itself show which sanctions sources and parties were checked. Verify any included service's actual scope and evidence, then complete the checks your dealership's approved procedure requires.
How should I screen a company buying a fleet vehicle?
Use the legal purchasing company as an organization subject. Screen a representative or other required person separately. Keep each result linked to the deal and to the party it actually describes.
What happens if a buyer match is unresolved at delivery?
Keep the deal at the checkpoint required by your procedure and give the reviewer the missing identity question. Record evidence and approval before the authorized decision. Do not lower a threshold simply to remove the candidate.
Can I reuse the buyer result for a different refund recipient?
No. A result describes the submitted buyer, not every party connected to the deal. Identify the new recipient and run its required check, keeping both references in the deal history.