Skip to main content
Article thumbnail
Location of Repository

Currency hedging strategies using dynamic multivariate GARCH

By Chia-Lin Chang, LydiaGonzález-Serrano and Juan-AngelJimenez-Martin

Abstract

This paper examines the effectiveness of using futures contracts as hedging instruments of: (1) alternative models of volatility for estimating conditional variances and covariances; (2) alternative currencies; and (3) alternative maturities of futures contracts. For this purpose, daily data of futures and spot exchange rates of three major international currencies, Euro, British pound and Japanese yen, against the American dollar, are used to analyze hedge ratios and hedging effectiveness resulting from using two different maturity currency contracts, near-month and next-to-near-month contract. We estimate four multivariate volatility models (namely CCC, VARMA-AGARCH, DCC and BEKK), and calculate optimal portfolio weights and optimal hedge ratios to identify appropriate currency hedging strategies. The hedging effectiveness index suggests that the best results in terms of reducing the variance of the portfolio are for the USD/GBP exchange rate. The empirical results show that futures hedging strategies are slightly more effective when the near-month future contract is used for the USD/GBP and USD/JPY currencies. Moreover, the CCC and AGARCH models provide similar hedging effectiveness, which suggests that dynamic asymmetry may not be crucial empirically, although some differences appear when the DCC and BEKK models are used

Topics: Multivariate GARCH, Exchange Rates, Hedging
Year: 2014
DOI identifier: 10.1016/j.matcom.2012.02.008
OAI identifier: oai:ir.lib.nchu.edu.tw:11455/85221
Download PDF:
Sorry, we are unable to provide the full text but you may find it at the following location(s):
  • http://dx.doi.org/10.1016/j.ma... (external link)
  • http://hdl.handle.net/11455/85... (external link)
  • Suggested articles


    To submit an update or takedown request for this paper, please submit an Update/Correction/Removal Request.