OFAC Compliance Reporting
The obligation to file reports with OFAC, including blocked property reports, rejected transaction reports, and the annual blocked property report.
TL;DR
TL;DR: OFAC compliance reporting is the set of filings a business must make when it blocks property or rejects a transaction tied to a sanctioned party. These reports tell OFAC what was blocked, when, and why.
What must be reported
When a screening check flags a counterparty, the response is not just to stop the payment. OFAC requires a blocked property report within 10 business days of blocking, and a report when a transaction is rejected. Holders of blocked property also file an annual report each year. These filings create the paper trail OFAC uses to verify that sanctions are being enforced.
Why it matters for agent payments
An AI agent that screens and then pays a counterparty generates a decision record on every transaction. If the agent blocks a payment, the operator still needs to produce the required report. A screening API that returns an audit-ready result, including the matched list entry and the BLOCK decision, makes that filing straightforward instead of a manual reconstruction.
Reporting requirements in brief
- Blocked property report within 10 business days
- Rejected transaction report when a transaction is refused
- Annual report of property that remains blocked
Timing and accuracy
Timing matters in compliance reporting. A blocked property report filed weeks late, or an annual report that omits blocked accounts, creates its own compliance problem on top of the original transaction. Reports must be accurate enough for OFAC to match them against its own records. Operators of automated payment systems should generate the data for these reports from the screening logs, so the filing reflects what the system actually blocked rather than what a person remembers.