<?xml version="1.0" encoding="UTF-8"?>
<collection xmlns="http://www.loc.gov/MARC21/slim">
<record>
  <controlfield tag="001">129808</controlfield>
  <controlfield tag="005">20240705134135.0</controlfield>
  <datafield tag="024" ind1="7" ind2=" ">
    <subfield code="2">doi</subfield>
    <subfield code="a">10.1177/23409444211024645</subfield>
  </datafield>
  <datafield tag="024" ind1="8" ind2=" ">
    <subfield code="2">sideral</subfield>
    <subfield code="a">126302</subfield>
  </datafield>
  <datafield tag="037" ind1=" " ind2=" ">
    <subfield code="a">ART-2021-126302</subfield>
  </datafield>
  <datafield tag="041" ind1=" " ind2=" ">
    <subfield code="a">eng</subfield>
  </datafield>
  <datafield tag="100" ind1=" " ind2=" ">
    <subfield code="a">Andreu, L.</subfield>
    <subfield code="u">Universidad de Zaragoza</subfield>
    <subfield code="0">(orcid)0000-0003-3661-5448</subfield>
  </datafield>
  <datafield tag="245" ind1=" " ind2=" ">
    <subfield code="a">Window dressing in the Active Share scores in publicly reported portfolios</subfield>
  </datafield>
  <datafield tag="260" ind1=" " ind2=" ">
    <subfield code="c">2021</subfield>
  </datafield>
  <datafield tag="506" ind1="0" ind2=" ">
    <subfield code="a">Access copy available to the general public</subfield>
    <subfield code="f">Unrestricted</subfield>
  </datafield>
  <datafield tag="520" ind1="3" ind2=" ">
    <subfield code="a">Using a unique database that includes publicly disclosed fund holdings at the end of the quarter as well as the holdings in all non-publicly disclosed months, we found that some funds could alter their portfolios in publicly disclosed months to artificially increase their Active Share scores and consequently appear more active and take advantage of the positive relationship between Active Share and money flows. We show how, consistent with non-informed trades, these funds erode their future performance. However, these funds reach their objective of increasing future money flows. Moreover, we find that window-dresser funds can be identified by controlling the level of tracking error. The funds with high Active Share scores and low tracking errors have the highest levels of Active Share window dressing and the worst future returns. However, compared with less active funds, they are able to capture higher money flows.</subfield>
  </datafield>
  <datafield tag="536" ind1=" " ind2=" ">
    <subfield code="9">info:eu-repo/grantAgreement/ES/MCIU/RTI2018-093483-B-I00</subfield>
  </datafield>
  <datafield tag="540" ind1=" " ind2=" ">
    <subfield code="9">info:eu-repo/semantics/openAccess</subfield>
    <subfield code="a">by-nc</subfield>
    <subfield code="u">http://creativecommons.org/licenses/by-nc/3.0/es/</subfield>
  </datafield>
  <datafield tag="590" ind1=" " ind2=" ">
    <subfield code="a">4.204</subfield>
    <subfield code="b">2021</subfield>
  </datafield>
  <datafield tag="591" ind1=" " ind2=" ">
    <subfield code="a">MANAGEMENT</subfield>
    <subfield code="b">124 / 228 = 0.544</subfield>
    <subfield code="c">2021</subfield>
    <subfield code="d">Q3</subfield>
    <subfield code="e">T2</subfield>
  </datafield>
  <datafield tag="591" ind1=" " ind2=" ">
    <subfield code="a">BUSINESS</subfield>
    <subfield code="b">95 / 154 = 0.617</subfield>
    <subfield code="c">2021</subfield>
    <subfield code="d">Q3</subfield>
    <subfield code="e">T2</subfield>
  </datafield>
  <datafield tag="592" ind1=" " ind2=" ">
    <subfield code="a">0.751</subfield>
    <subfield code="b">2021</subfield>
  </datafield>
  <datafield tag="593" ind1=" " ind2=" ">
    <subfield code="a">Business and International Management</subfield>
    <subfield code="c">2021</subfield>
    <subfield code="d">Q1</subfield>
  </datafield>
  <datafield tag="593" ind1=" " ind2=" ">
    <subfield code="a">Strategy and Management</subfield>
    <subfield code="c">2021</subfield>
    <subfield code="d">Q1</subfield>
  </datafield>
  <datafield tag="593" ind1=" " ind2=" ">
    <subfield code="a">Business, Management and Accounting (miscellaneous)</subfield>
    <subfield code="c">2021</subfield>
    <subfield code="d">Q1</subfield>
  </datafield>
  <datafield tag="594" ind1=" " ind2=" ">
    <subfield code="a">6.4</subfield>
    <subfield code="b">2021</subfield>
  </datafield>
  <datafield tag="655" ind1=" " ind2="4">
    <subfield code="a">info:eu-repo/semantics/article</subfield>
    <subfield code="v">info:eu-repo/semantics/publishedVersion</subfield>
  </datafield>
  <datafield tag="700" ind1=" " ind2=" ">
    <subfield code="a">Forner, C.</subfield>
  </datafield>
  <datafield tag="700" ind1=" " ind2=" ">
    <subfield code="a">Sarto, J.L.</subfield>
    <subfield code="u">Universidad de Zaragoza</subfield>
    <subfield code="0">(orcid)0000-0001-6078-0465</subfield>
  </datafield>
  <datafield tag="710" ind1="2" ind2=" ">
    <subfield code="1">4002</subfield>
    <subfield code="2">230</subfield>
    <subfield code="a">Universidad de Zaragoza</subfield>
    <subfield code="b">Dpto. Contabilidad y Finanzas</subfield>
    <subfield code="c">Área Economía Finan. y Contab.</subfield>
  </datafield>
  <datafield tag="773" ind1=" " ind2=" ">
    <subfield code="g">27, 3 (2021), 324-345</subfield>
    <subfield code="p">Bus. res. q.</subfield>
    <subfield code="t">BRQ Business Research Quarterly</subfield>
    <subfield code="x">2340-9436</subfield>
  </datafield>
  <datafield tag="856" ind1="4" ind2=" ">
    <subfield code="s">298115</subfield>
    <subfield code="u">http://zaguan.unizar.es/record/129808/files/texto_completo.pdf</subfield>
    <subfield code="y">Versión publicada</subfield>
  </datafield>
  <datafield tag="856" ind1="4" ind2=" ">
    <subfield code="s">2561108</subfield>
    <subfield code="u">http://zaguan.unizar.es/record/129808/files/texto_completo.jpg?subformat=icon</subfield>
    <subfield code="x">icon</subfield>
    <subfield code="y">Versión publicada</subfield>
  </datafield>
  <datafield tag="909" ind1="C" ind2="O">
    <subfield code="o">oai:zaguan.unizar.es:129808</subfield>
    <subfield code="p">articulos</subfield>
    <subfield code="p">driver</subfield>
  </datafield>
  <datafield tag="951" ind1=" " ind2=" ">
    <subfield code="a">2024-07-05-12:45:43</subfield>
  </datafield>
  <datafield tag="980" ind1=" " ind2=" ">
    <subfield code="a">ARTICLE</subfield>
  </datafield>
</record>
</collection>