USD/CAD to Face BoC Rate Decision, Monetary Policy Report (MPR)

  


Canadian Dollar Talking Points

USD/CAD attempts to retrace the decline following Canada’sEmployment report as it struggles to extend the series of lower highs and lows from the monthly high (1.2590), but the exchange rate may face range bound conditions ahead of the Bank of Canada (BoC) interest rate decision as the central bank is slated to update its quarterly Monetary Policy Report (MPR).

USD/CAD to Face BoC Rate Decision, Monetary Policy Report (MPR)

USD/CAD seems to be staging another attempt to test the 200-Day SMA (1.2642) on the back of US Dollar strength, and the BoC rate decision may do little to curb the advance from earlier this month as the central bank is expected to retain the current course for monetary policy.

Image of DailyFX economic calendar for Canada

It remains to be seen if the BoC will respond to 230.7K rise in Canada employment as the participation rate widens to 65.2% from 64.6% in May to reflect discouraged workers returning to the labor force, and signs of a more robust recovery may encourage Governor Tiff Macklem and Co. to make further adjustments in 2021 as the central bank expects to achieve the 2% target for inflation on a sustainable basis “sometime in the second half of 2022.”

As a result, the BoC may draw up an exit strategy after tapering its quantitative easing (QE) program in April, and the updated MPR may spark a bullish reaction in the Canadian Dollar if the central bank shows a greater willingness to normalize monetary policy over the coming months.

Until then, USD/CAD may consolidate as it struggles to extend the series of lower highs and lows from the monthly high (1.2590), but the tilt in retail sentiment persists as traders have been net-long the pair since May 2020.

Image of IG Client Sentiment for USD/CAD rate

The IG Client Sentiment report shows 66.79% of traders are currently net-long USD/CAD, with the ratio of traders long to short standing at 2.01 to 1.

The number of traders net-long is 13.84% higher than yesterday and 5.73% lower from last week, while the number of traders net-short is 9.22% higher than yesterday and 8.70% higher from last week. The decline in net-long position comes as the advance from earlier this month failed to spur a test of the 200-Day SMA (1.2642), while the rise in net-short position has done little to alleviate the crowding behavior as 66.53% of traders were net-long at the start of July.

With that said, the rebound from the yearly low (1.2007) may turn out to be a correction in the broader trend rather thana change in USD/CAD behavior amid the ongoing tilt in retail sentiment, and the BoC rate decision may fuel the decline from the monthly high (1.2590) if the central bank takes additional steps to normalize monetary policy.

USD/CAD Rate Daily Chart

Image of USD/CAD rate daily chart

Source: Trading View

  • The broader outlook for USD/CAD remains tilted to the downside as it slipped to a fresh yearly low (1.2007) in June, with the 200-Day SMA (1.2642)still tracking the negative slope carried over from the previous year.
  • The Relative Strength Index (RSI) highlighted a similar dynamic as it pushed below 30 in May for the first time in 2021, but since then, the oscillator established an upward trend, with the indicator flashing the first overbought reading since March 2020.
  • USD/CAD seems to be stage another attempt to test the 200-Day SMA (1.2642) as it struggles to extend the series of lower highs and lows from the monthly high (1.2590), with a move above the 1.2510 (78.6% retracement) region bringing the 1.2620 (50% retracement) to 1.2650 (78.6% expansion) area back on the radar.
  • Need a break/close below the Fibonacci overlap around 1.2410 (23.6% expansion) to 1.2440 (23.6% expansion) to open up the 1.2360 (100% expansion) region, with the next area of interest coming in around 1.2250 (50% expansion) to 1.2260 (38.2% expansion).

— Written by David Song, Currency Strategist

Follow me on Twitter at @DavidJSong

element inside the element. This is probably not what you meant to do!
Load your application’s JavaScript bundle inside the element instead.



Read More…