Screen every payment and party against applicable watchlists in real time, resolve potential matches with the contextual detail adjudicators need, and prepare blocking and reporting documentation, with every clearing decision made by a human who can defend it.
















































The Uptiq Sanctions / OFAC Screening Agent screens every payment and party against applicable sanctions watchlists in real time before settlement, assembles contextual match resolution packages for adjudicator review, and prepares blocking and reporting documentation for confirmed match cases, presenting every action package for compliance officer authorization before submission. A designated human adjudicator makes every clearing decision; the agent screens and resolves, but it does not clear, block, or file autonomously. The agent is built for payment volume scale: screening and context assembly are automated, so adjudicator time goes to genuine match risk rather than data gathering, and every alert carries the audit trail that OFAC and BSA/AML examinations look for. For institutions where payment volume growth has outpaced adjudicator capacity, the combination of real-time screening and automated context assembly is what allows the program to remain current with volume without proportional headcount growth.
The agent screens against the sanctions lists configured for your institution: the OFAC SDN list and sectoral programs, the OFSI consolidated list for UK activity, the EU and UN consolidated lists, and any supplemental lists you maintain. Lists come from your chosen provider, and updates follow the provider's publication cycle.
The match resolution package assembles, in a single structured document, the information an adjudicator needs to make a defensible determination on a potential match alert: the matched watchlist entry with the full SDN or list record, the specific matching basis, name similarity score, identifier match, address overlap, or ownership linkage, the transaction party's complete profile including known identifying information, the relationship history between the party and the institution, any prior screening alerts for this party and how they were resolved, and the available disambiguating information, date of birth, nationality, business registration, or other identifiers, that supports a true match or false positive determination. The assembly is what changes adjudication from a research task to a judgment task. An experienced adjudicator manually gathering this context for each alert in a high-volume payment environment typically spends significantly more time on data collection than on the determination itself. When the context is assembled automatically, the adjudicator applies their judgment to the determination immediately, which is what allows high-volume programs to maintain the adjudication quality that examination requires without the adjudicator headcount that manual context assembly demands.
When a human adjudicator determines that a potential match constitutes a true match requiring blocking, the agent assembles the complete blocking and reporting documentation package: the blocked transaction record with the full transaction details, the matched SDN or list entry with the matching basis, the blocking action timestamp, the adjudicator's determination and rationale, and the OFAC reporting form populated with the required fields for the transaction type. The package is presented to the designated compliance officer for review and submission authorization. The report is not submitted to OFAC until the authorized compliance officer has reviewed the package and approved the submission. Every prepared reporting package carries its compliance timeline, including OFAC's requirement that blocked transactions be reported within ten business days, so the deadline is in front of the compliance officer from the moment the block is recorded.
Deployment is scoped with your team during discovery. Uptiq handles payment system integration, watchlist source configuration, matching logic tuning, and adjudication workflow setup. Matching thresholds are configured with your team during deployment, balancing false positive volume against miss risk. Many institutions begin by deploying the screening and match resolution capabilities against their highest-volume payment channels, then extend to additional channels in subsequent phases. For institutions replacing a legacy screening filter, we recommend a parallel run so your team validates match detection before cutover.
Yes. The Uptiq platform is SOC 2 audited, with encrypted data handling, role-based access controls that restrict screening results and match resolution packages to authorized BSA/AML and compliance personnel, and comprehensive audit logging of every screening event, match determination, and reporting action. Transaction and party data are handled within the institution's configured data environment, and the complete audit trail for each alert, from initial screening through adjudication to any blocking and reporting action, is retained for the examination periods required by applicable BSA and OFAC recordkeeping regulations. The per-alert audit trail is built to the evidentiary standard OFAC looks for when reviewing a sanctions compliance program: for every alert, the examination should be able to identify what was screened, which list was matched, what resolution context was reviewed, who made the clearing or blocking determination, when that determination was made, and what reporting action was taken. The agent's audit trail produces this record automatically as a byproduct of the normal screening workflow rather than requiring separate documentation assembly for examination preparation.
Legacy OFAC filters and rule-based screening systems apply name-matching algorithms to produce alerts and surface the raw match result: the name, the list entry, and a similarity score. They do not assemble the resolution context that adjudicators need to make defensible determinations; they do not manage reporting deadlines for confirmed blocks, and they typically do not maintain the per-alert audit trail in the format that examination scrutiny requires. Alert handling after the initial match is left to the adjudication team to manage manually. The agent replaces the manual steps that legacy systems leave for adjudicators with automated context assembly and structured workflows, but it does not replace the adjudicator's judgment, which remains the essential human element of a sanctions compliance program. The combination of comprehensive real-time screening, automated match resolution context, and managed reporting workflows is what allows an institution to operate a high-quality sanctions program at the payment volumes that modern institutions process, without either compromising adjudication quality by pressuring adjudicators to clear alerts faster or expanding the adjudication team proportionally with payment volume growth.
Our team handles deployment end-to-end, from configuration to go-live. Most financial institutions are live within days, not months.

