<?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>01099nam a22001457a 4500</leader>
  <datafield tag="022" ind1=" " ind2=" ">
    <subfield code="a">ISSN: 2315 - 5671</subfield>
  </datafield>
  <datafield tag="100" ind1=" " ind2=" ">
    <subfield code="a">Uguru, Leonard C.</subfield>
  </datafield>
  <datafield tag="245" ind1=" " ind2=" ">
    <subfield code="a">On The Tax Implications of Capital Flight: Evidence from Nigeria</subfield>
  </datafield>
  <datafield tag="260" ind1=" " ind2=" ">
    <subfield code="b">Journal of Research in Economics and International Finance (JREIF)</subfield>
    <subfield code="c">2016</subfield>
  </datafield>
  <datafield tag="300" ind1=" " ind2=" ">
    <subfield code="a">7p.</subfield>
  </datafield>
  <datafield tag="520" ind1=" " ind2=" ">
    <subfield code="a">This is a study that offers further documentation of the effect of capital flight on tax revenue in Nigeria. After a theoretical and empirical literature review of the subject, an Ordinary Least Square model is employed based on time series data quantifying capital flight under the hot money or balance of payment approach. It is found that a unit increase in capital flight will lead to a 0.02 or 2% decrease in tax revenue. Consequently, policy measures discouraging capital flight, like placing a limit on the repatriating percentage of local profit, would improve tax revenue in Nigeria.</subfield>
  </datafield>
  <datafield tag="650" ind1=" " ind2=" ">
    <subfield code="a">CAPITAL FLIGHT, TAX REVENUE</subfield>
  </datafield>
  <datafield tag="856" ind1=" " ind2=" ">
    <subfield code="u">iffoadatabase.trustafrica.org/iff/on-the-tax-implications-of-capital-flight-evidence-from-nigeria.pdf</subfield>
  </datafield>
  <datafield tag="942" ind1=" " ind2=" ">
    <subfield code="c">CF</subfield>
  </datafield>
  <datafield tag="999" ind1=" " ind2=" ">
    <subfield code="c">474</subfield>
    <subfield code="d">474</subfield>
  </datafield>
</record>
