<?xml version="1.0" encoding="UTF-8"?>
<record
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://www.loc.gov/MARC21/slim http://www.loc.gov/standards/marcxml/schema/MARC21slim.xsd"
    xmlns="http://www.loc.gov/MARC21/slim">

  <leader>01073nam a22001337a 4500</leader>
  <datafield tag="100" ind1=" " ind2=" ">
    <subfield code="a">AML Thomson Reuters </subfield>
  </datafield>
  <datafield tag="245" ind1=" " ind2=" ">
    <subfield code="a">2017 Thomson Reuters US Anti-Money Laundering Insights Report</subfield>
  </datafield>
  <datafield tag="260" ind1=" " ind2=" ">
    <subfield code="a">USA</subfield>
    <subfield code="b">AML Thomson Reuters</subfield>
    <subfield code="c">2017</subfield>
  </datafield>
  <datafield tag="300" ind1=" " ind2=" ">
    <subfield code="a">23p.</subfield>
  </datafield>
  <datafield tag="520" ind1=" " ind2=" ">
    <subfield code="a">The 2017 Thomson Reuters U.S. Anti-Money Laundering insights report analyses the survey findings, providing a data-driven framework for AML professionals to make better operational and budgetary decisions. The latter is key as 72 percent of survey participants did not know their organizations&#x2019; dedicated budget for AML/CDD screening. However, the broader goal is to help U.S. institutions stem the estimated $800 billion to $2 trillion laundered every year by the global financial industry, often making it an unwitting financier for terrorist networks, drug cartels and other criminal groups that threaten national security. The AML report revealed compliance leaders&#x2019; fears.</subfield>
  </datafield>
  <datafield tag="650" ind1=" " ind2=" ">
    <subfield code="a">Money Laundering </subfield>
  </datafield>
  <datafield tag="856" ind1=" " ind2=" ">
    <subfield code="u">iffoadatabase.trustafrica.org/iff/2017-aml-insights-survey-report.pdf</subfield>
  </datafield>
  <datafield tag="942" ind1=" " ind2=" ">
    <subfield code="c">CF</subfield>
  </datafield>
  <datafield tag="999" ind1=" " ind2=" ">
    <subfield code="c">1004</subfield>
    <subfield code="d">1004</subfield>
  </datafield>
</record>
