<?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>01109nam a22001457a 4500</leader>
  <datafield tag="100" ind1=" " ind2=" ">
    <subfield code="a">Kwaramba,M , Mahonye, N and Mandishora, L</subfield>
  </datafield>
  <datafield tag="245" ind1=" " ind2=" ">
    <subfield code="a">Capital Flight and Trade Misinvoicing in Zimbabwe</subfield>
  </datafield>
  <datafield tag="250" ind1=" " ind2=" ">
    <subfield code="a">Policy Brief</subfield>
  </datafield>
  <datafield tag="260" ind1=" " ind2=" ">
    <subfield code="a">Zimbabwe</subfield>
    <subfield code="b">The Zimbabwe Economic Policy Analysis and Research Unit (ZEPARU)</subfield>
    <subfield code="c">2017</subfield>
  </datafield>
  <datafield tag="300" ind1=" " ind2=" ">
    <subfield code="a">2p.</subfield>
  </datafield>
  <datafield tag="520" ind1=" " ind2=" ">
    <subfield code="a">This paper estimates trade misinvoicing in Zimbabwe from major trading partners using the Morgenstern (1963) methodology. Trade misinvoicing is done for several reasons such as tax evasion, quota avoidance, smuggling, money laundering, or for other unknown reasons. Zimbabwe is an interesting case due to its changing macroeconomic environment, which presented opportunities for capital flight. The main objective of the study was to investigate the relationship between natural resources, particularly mineral resources and capital flight, taking into account the institutional environment of Zimbabwe. </subfield>
  </datafield>
  <datafield tag="650" ind1=" " ind2=" ">
    <subfield code="a">Capital Flight</subfield>
  </datafield>
  <datafield tag="856" ind1=" " ind2=" ">
    <subfield code="u">iffoadatabase.trustafrica.org/iff/Policy-Brief-Capital-flight-and-trade-misinvoicing-in-Zimbabwe.pdf</subfield>
  </datafield>
  <datafield tag="942" ind1=" " ind2=" ">
    <subfield code="c">CF</subfield>
  </datafield>
  <datafield tag="999" ind1=" " ind2=" ">
    <subfield code="c">909</subfield>
    <subfield code="d">909</subfield>
  </datafield>
</record>
