OFAC's August 28 two-record action needs separate match decisions

Ingest the action as two distinct list records

The direct answer is to parse the August 28 action into two separately identifiable sanctioned parties and preserve the official source version. OFAC lists an individual and a trading company in the same release, but their identity fields, tags and relationship annotations differ. Capture action date, page URL, retrieval and ingestion time, source list and version, add operation, full party name, original script where available, alternate name, entity type, addresses, birth and identity numbers for the individual, establishment and registration facts for the company, program tags, and any explicit linked-to statement. Do not substitute a press-release summary for the actual listed-entry fields.

Treat Taeedi's [SDGT] and [IFSR] as annotations on one named person, not two duplicate persons, and Bank Melli Iran as an explicit 'Linked To' field that needs its own context. Treat Kameng Trading Limited as a separate Hong Kong entity with [IRAN-EO13902], not a subsidiary or counterpart of Taeedi on the strength of the same action date. An address, geographic mention, or entity suffix is a matching clue, not an ownership, control or prohibition conclusion. Preserve confidence, source fields and negative evidence when resolving candidates.

Screen actual transaction parties at the correct grain

Map the transaction to applicant, customer, consignee, end user, supplier, manufacturer, broker, bank, intermediaries, beneficial owners or controllers where relevant, logistics parties and any other party required by the organization's program. Use legal-entity and person-specific identifiers, names, aliases, addresses and relationships with dates. A similar trading name deserves adjudication; it should not trigger an automatic finding against an unrelated corporation. A bank-linked individual need not be a contracting party in every transaction, but if encountered the exact person and role require a documented determination.

Each potential hit needs the authoritative list entry, subject record version, matched and mismatched fields, identity uncertainty, relationship source, transaction role, program and jurisdiction analysis, applicable license or exception if any, reviewer and legal escalation, hold state, decision reason, effective timestamp, and downstream enforcement receipt. Separate 'potential match', 'confirmed identity', 'scope determination', 'hold', 'authorized release' and 'rejected or blocked' so a software alert cannot silently become a completed legal or operational decision.

Test dual tags, updates and independent disposition

Use a synthetic transaction with one near-name individual lacking the published birth and passport details, a second person matching multiple identifiers, two companies called Kameng in different jurisdictions, a bank relationship of uncertain scope, and one earlier approved order. Ingest the official delta and verify the matching system creates one Taeedi party with two program tags and one Kameng entity, preserves each source field, surfaces true and false matches, and holds only affected records under approved policy while reviewers determine actual scope.

A prior screen is not a durable clearance when a new list entry takes effect, but this August action predates the September 14 release cutoff and is not evidence of a new post-cutoff semantic change. Keep the action date, ingest receipt, rescreen population, exemptions and queues, each case decision, approvals, notifications, and transaction write state separately. A daily HTTP Last-Modified or content hash observation cannot prove the action's legal effective time or that an entity has since been removed; check any later official actions before a live disposition.

Evidence boundary and non-collision

The OFAC August 28 recent-action page directly establishes the two named additions, their published identifiers and tags, the explicit bank-link annotation and the 'None' administrative-change line. It does not establish a particular buyer's list completeness, aliases, ownership network, screening accuracy, transaction exposure, licensing or legal conclusion. The article is a process test based on official record anatomy, not notice of a September 15 designation.

Unlike the prior OFAC ransomware action about the full screening operation, the UK week-of-list-changes rescreening process, Moody's association flags, or ComplyAdvantage joint-case disposition, this article's unit is one official two-party delta with a dual-tag individual and separately tagged company. Reconstructing its entry-level identities prevents the action headline or shared date from flattening two independent match decisions.

Enterprise buyer test

Translate this change into the exact population, record type, workflow stage, decision owner, effective date, and evidence that could be affected. Ask current or prospective providers to demonstrate the named workflow with representative data and an exception—not a polished feature tour. Record what official documentation establishes, what a provider states, what the team observes, and what remains unresolved.

A defensible review also identifies the dependency outside the product. Authority interpretation, policy configuration, data quality, integrations, human judgment, approval rights, release governance, training, and retained evidence may remain customer or service responsibilities. The evaluation should preserve those boundaries instead of treating a technology claim as the complete operating model.

What we will watch next

Trade Controls Brief will watch the named source and affected market records for later evidence that changes status, scope, availability, implementation timing, workflow consequence, or the limits of the initial report. A later announcement does not silently overwrite this dated account; the change ledger preserves the sequence.