Jump to content

Market update: USD/JPY price forecast- uptick in Japanese government bonds lifts the yen

Recommended Posts

Yen picks up late bid as markets digest Ueda’s comments; rising Japanese Government bonds spur on the yen one day after BoJ meeting and USD/JPY turns away from the 150 mark as 146.50 emerges as immediate support.


original-size.webpSource: Bloomberg


 Written by: Richard Snow | Analyst, DailyFX, Johannesburg | Publication date: 

Yen picks up a late bid as markets digest Ueda’s comments

The main takeaway from yesterday’s Bank of Japan (BoJ) meeting was that Ueda still has his eye on an eventual exit from negative rates, despite inflation showing signs of slowing down. Ueda described the likelihood of reaching the 2% target as “increasing” and even said an exit from negative rates is possible in the absence of addressing the current, sub-optimal output gap (difference between potential output and current output).

Markets see April as a live meeting for the BoJ, but currently price in a full 10 basis points (bps) by the June meeting. The BoJ is primarily looking for the continuation of what it refers to as the virtuous cycle between inflation and wages. The wage negotiation process is likely to roundup in March, which has led markets to naturally look to the April meeting for any movement in the interest rate.

Implied basis points priced in by rate markets


original-size.webpSource: Refinitiv

Rising Japanese bond yields spur on the yen

Japanese Government bond yields (10-year) continued to rise today, in the aftermath of the BoJ meeting. Yields are still a long way off the early November peak before inflation pressures revealed signs of slowing, and markets cooled expectations around any imminent rate changes. The higher yield boosts the attractiveness of the yen and typically sees a rise in the local currency.

Japanese government bond yields (10-year)


original-size.webpSource: TradingView

The Yen has broadly risen against a number of major FX currencies (GBP, AUD, EUR, USD) as can be seen below in an equal-weighted index, comprising of the above-mentioned currencies:


original-size.webpSource: TradingView

USD/JPY turns away from the 150 mark as 146.50 emerges as immediate support

USD/JPY found resistance ahead of the 150 marker but failed to reach the psychological level after the BoJ head pointed towards an eventual exit from negative rates with increasing probability.

The short to medium term uptrend has not broken down as of yet, with 146.50 the most immediate level of support, followed by 145.00 and the underside of the longer-term rising channel (highlighted in blue). However, the US dollar may pose a challenge to the yen tomorrow and Friday with US Q4 GDP and PCE data on tap.

Strong PMI data earlier today points to an economy that is growing at a decent pace and this could keep USD supported if inflation concerns build in the upcoming data prints with the resilient December CPI print still fresh in the minds of traders.

USD/JPY daily chart


original-size.webpSource: TradingView

After the BoJ meeting, Japan specific data is rather scarce but US Q4 GD and PCE data on Thursday and Friday ought to provide a lift for intra-day volatility before the weekend.

Better-than-expected PMI data for the month of January suggests the US economy is moving along at a decent canter, but markets will be more focused on backward looking data in tomorrow’s Q4 growth print.

USD/JPY will also maintain plenty of interest next week when the FOMC meet to discuss monetary policy. Before then, US PCE data for December is expected to reveal stubborn headline pressures remain, with another welcome drop in the core measure of inflation.

Economic calander


original-size.webpSource: DailyFX




This information has been prepared by IG, a trading name of IG Australia Pty Ltd. In addition to the disclaimer below, the material on this page does not contain a record of our trading prices, or an offer of, or solicitation for, a transaction in any financial instrument. IG accepts no responsibility for any use that may be made of these comments and for any consequences that result. No representation or warranty is given as to the accuracy or completeness of this information. Consequently any person acting on it does so entirely at their own risk. Any research provided does not have regard to the specific investment objectives, financial situation and needs of any specific person who may receive it. It has not been prepared in accordance with legal requirements designed to promote the independence of investment research and as such is considered to be a marketing communication. Although we are not specifically constrained from dealing ahead of our recommendations we do not seek to take advantage of them before they are provided to our clients.

Link to comment

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • image.png

  • Posts

    • Hi KoketsoIG, Thank you for the clarification on that. Cheers
    • Dear @millennium_falcon, Hey there! Thank you for reaching out. Just a heads-up, you can only have one API key for each environment, either live or demo. No third API key can be created.  Thanks, KoketsoIG
    • To clarify my understanding. From my Usecase, I have three separate programs all operating interdependently from one another. A program to subscribe to tic data on a number of Epics via the LightStream API, another to grab historic on a number of Epics via the REST API, and finally another to manage positions via the REST API. I need to do this on my demo account initially to get API code stabilized. The IG website specifically says that I need separate API key for each distinct program connecting to IG over REST or LightStream. So in my understanding it looks like I need three API keys all for the demo account. Am I missing something or have I misunderstood how to use these API keys? I am aware of the API request limits and this is why I assumed you need a key per program. Currently I have one API key for the demo account and cannot seem to add more keys to the demo account? I have looked at the FAQ and cannot see an answer for my query.
  • Create New...