Canonical vine copulas in the context of modern portfolio management: Are they worth it?

Rand Kwong Yew Low*, Jamie Alcock, Robert Faff, Timothy Brailsford

*Corresponding author for this work

Research output: Contribution to journalArticlepeer-review

107 Citations (Scopus)

Abstract

In the context of managing downside correlations, we examine the use of multi-dimensional elliptical and asymmetric copula models to forecast returns for portfolios with 3-12 constituents. Our analysis assumes that investors have no short-sales constraints and a utility function characterized by the minimization of Conditional Value-at-Risk (CVaR). We examine the efficient frontiers produced by each model and focus on comparing two methods for incorporating scalable asymmetric dependence structures across asset returns using the Archimedean Clayton copula in an out-of-sample, long-run multi-period setting. For portfolios of higher dimensions, we find that modeling asymmetries within the marginals and the dependence structure with the Clayton canonical vine copula (CVC) consistently produces the highest-ranked outcomes across a range of statistical and economic metrics when compared to other models incorporating elliptical or symmetric dependence structures. Accordingly, we conclude that CVC copulas are 'worth it' when managing larger portfolios.

Original languageEnglish
Pages (from-to)3085-3099
Number of pages15
JournalJournal of Banking and Finance
Volume37
Issue number8
DOIs
Publication statusPublished - Aug 2013

Bibliographical note

Funding Information:
The support of the Australian Research Council is gratefully acknowledged (DP0770081).

Keywords

  • Asymmetric dependence
  • Canonical vine
  • Clayton copula
  • Conditional value-at-risk
  • Portfolio management
  • Vine copula

ASJC Scopus subject areas

  • Finance
  • Economics and Econometrics

Fingerprint

Dive into the research topics of 'Canonical vine copulas in the context of modern portfolio management: Are they worth it?'. Together they form a unique fingerprint.

Cite this