AJILY SOFTWARE PROCUREMENT GROUP

• SanctionsRecords foundSanctioned by 1 authority: OFAC. Confirmed present in a source snapshot within the last 90 days.
• Debarment & exclusion— Checked, nothing found16 sources read, none holding a record for this company.
• Ownership & controlRecords found2 designated individuals recorded in connection with this company: Mohammed Saeed AJILY, Mohammed Reza REZAKHAH.
• People— Not assessedNothing has been read for this company on this dimension.
• Identity & registration— Not assessedNothing has been read for this company on this dimension.
• JurisdictionRecords foundIran is named on a jurisdiction designation list — European Commission, EU list of high-risk third countries (AMLD Art. 9), section II: “High-risk third countries which have provided a high-level political commitment to address the identified deficiencies, and have decided to seek technical assistance in the implementation of the FATF Action Plan, which are identified by FATF Public Statement.” The designation is of the jurisdiction, not of this record.
• Court records— Not assessedNothing has been read for this company on this dimension.

• OFACActive

  TCO

  Designation date not published by this authority · OFAC SDN

Legal name

AJILY SOFTWARE PROCUREMENT GROUP

Also known as

AJILY SOFTWARE PROCUREMENT GROUP

Jurisdiction

IR

First recorded here

28 Aug 2026

1. Subsidiary recorded: ANDISHEH VESAL MIDDLE EAST COMPANY

   11 Sept 2026 · OFAC SDN

2. Sanctioned individual connected by OFAC: Mohammed Reza REZAKHAH

   28 Aug 2026 · OFAC SDN

3. Sanctioned individual connected by OFAC: Mohammed Saeed AJILY

   28 Aug 2026 · OFAC SDN

4. Sanction listed: OFAC — TCO

   28 Aug 2026 · OFAC SDN

5. Alias recorded: AJILY SOFTWARE PROCUREMENT GROUP

   28 Aug 2026 · OFAC SDN

6. First recorded: AJILY SOFTWARE PROCUREMENT GROUP

   28 Aug 2026 · OFAC SDN

No ownership test is on file for this company. The test reads who holds a company's shares from its shareholder register, and it is run each day for companies with a number in Estonia's, Latvia's or Poland's register. For a company anywhere else, no register read here states its shareholders, so the test cannot be run.

None recorded with a stated ownership stake or control method.

2 companies, 1 recorded links, up to two steps from this record. Open the full graph ›

No address has been read for this company, so this was never checked — which is not the same as finding nothing.

Each reading is kept with the methodology version that produced it. A later reading is not a correction of an earlier one — it is a different question asked of more sources.

• Fact

  ajily software procurement group

  Legal name

  Evidence

  22697

  Read 28 Aug 2026

  Source

  OFAC SDN

  Primary source ↗

• Fact

  IR

  Jurisdiction

  Evidence

  22697

  Read 28 Aug 2026

  Source

  OFAC SDN

  Primary source ↗

• Fact

  OFAC — TCO

  Designation

  Evidence

  22697

  Read 28 Aug 2026

  Source

  OFAC SDN

  Primary source ↗

Records from these sources are matched into one company only on a shared identifier, or by a human reviewer — never on name similarity alone. How this works. Not legal or compliance advice: check the originals before acting on anything here.

TRUE

A source states it. Rendered as a fact, with the source attached.

FALSE

A source explicitly denies it. Rare, and never inferred from silence.

UNKNOWN

Checked, nothing found. Rendered as an em dash, never as 0 or "no".

NOT_ASSESSED

Never checked — nothing was read here. Excluded from coverage, and not counted as clean.

4 records on this company — identifiers, aliases, officers, listings, figures — each carry the source that wrote them and are shown beside their own entries. The fields above are different: the entities table has no source column, so what is shown is every source whose stored payload contains the value verbatim. That is strong evidence, not proof of which write landed it, and where nothing contains the value the row says so instead of naming a plausible source.