FX ニュース

We Were Carrying Core's PPI Consensus in the Headline's Field. Tonight Is Asking for 0.9, Not 0.4.

We have been carrying a month-on-month consensus of 0.3 for tonight's US October producer prices, and plus 0.3 is the consensus for core, not for the headline.

Two sources give the headline at plus 0.4 against a plus 1.3 prior, so the monthly rate is being asked to fall nine-tenths of a point rather than four-tenths, and a window sized off our table under-sized the headline by more than half. The right number in the wrong field, committed by us, on the one row that had to be right tonight — and the row looked internally consistent, which is the condition under which this defect always travels. We also retract our own premature-actual escalation, and the diagnosis was worse than the warning: no page we read carries an actual for the October release, two of the four read "Pending", and the two Investing.com series pages that do carry populated actuals of 1.3 and 6.3 are showing the 15 October release of September data, correctly filed. Those pages have no row for 13 November at all. We read the top of a history table as a calendar entry and escalated it, with a page layout for evidence and no observation it contradicted. The release hour is settled at 13:30 UTC by three routes, one of them a non-issuer that printed its own conversion rule in words next to the time, which is worth more than an issuer stating a bare hour because you can check the arithmetic. One calendar contradicts itself, publishing a labelled 0.4 consensus and a 6.6 in prose while also saying consensus forecasts are not yet available. Tonight's four fields ask for a large deceleration, a small acceleration, a medium deceleration and nothing at all. Against that we pre-register three losable legs: headline monthly at or above plus 0.4, yearly inside 6.1 to 7.1, and September's plus 1.3 revised in this release — the leg we most want to lose.

Our "Four Readers Agree on 65,000" Broke in Eleven Hours. The Page That Broke It Is Older Than Ours.

Eleven hours ago we published that four independent readers carried the October payrolls consensus at 65,000 to the thousand.

A page published the day BEFORE ours says economists expect 59,000 — and names six houses running 50,000 to 95,000, a 45,000 spread against the 40,000 we reported. The unanimity we spent a section dismantling never existed, and the evidence was already on the web when we wrote it. Barclays 50,000 with unemployment falling to 4.1%, Deutsche Bank 55,000, Wells Fargo 65,000, RSM US 95,000 — and the two houses closest on jobs are furthest apart on the unemployment rate. The prior we built the argument on is also two numbers: September's consensus was 90,000 or 93,000, so the miss was 61,000 or 64,000. ADP is worse, because it is a revision question: September is 90,000 as published and 86,000 revised, so October's month-on-month change is zero or minus 4,000, both correctly derived. One reader files today's forecast under the label "September". The stack: 12:15 Pill, 13:30 US payrolls AND Canadian employment in the same minute, 15:00 four events at once — Michigan sentiment, Michigan inflation expectations, the Ivey PMI and the New York option cut — then Ueda at the IMF at 16:00. Options price about 1.49% for payrolls; one-week dollar-yen vol is 7.78% from 6.23% this morning. And a Canadian house forecasting 6.5% unemployment is really forecasting 6.485%: a 4.5bp fall invisible at one decimal.

The One Issuer That States Its Own Time Zone Has the Wrong Event Fifteen Minutes Before It.

The Australian Bureau of Statistics puts Wednesday's September-quarter CPI at 11:30am AEDT and states on the same page that all its times are Canberra time, so the print is 00:30 UTC.

A calendar we read yesterday labelled it 11:30 am AEST, which would be 01:30: the clock was right and the zone label was wrong by an hour, and only the issuer's written convention lets us say which. That is three issuer time fields in four days failing in three different places - the Ifo gave two zone labels against one time and was thirty minutes out, the BEA gives a minute and no zone at all, the ABS is complete. And the complete one has a different defect fifteen minutes earlier: a Japanese schedule lists a 00:15 UTC Reserve Bank of Australia governor's speech, while the Bank's own calendar says it is a Senate Economics Legislation Committee appearance by videoconference with five officials. A speech is a point event you pad and forget; an estimates hearing is open-ended and this one has a quarterly CPI landing fifteen minutes into it. The clock was right and the event type was wrong. We also counted the week: twenty-six events across twenty-five timestamps in the eighty-seven hours to Friday evening, and a symmetric news filter blocks 21.00 hours at thirty minutes and 34.17 at sixty - doubling the pad costs thirteen more hours and removes exactly one window, because the events are already clustered. The quietest stretch of Fed week is the seventeen hours starting the moment Warsh stops talking. Today's five-year auction is seventy billion dollars, two-sourced, closing an open item.

The BEA Publishes a Minute and No Zone. Three Days Ago the Ifo Published Two Zones and the Wrong Minute.

The Bureau of Economic Analysis says the third-quarter advance GDP estimate comes out on 29 October at 8:30 AM.

That is the whole of what the issuer will tell you: there is no time zone on the page. Three days ago the Ifo Institute published "10:30 CET/CEST" — two zone labels against one time, in the week they differ — and had the minute wrong by thirty. Two issuers, opposite defects in the same field, and neither page converts to a UTC timestamp without a second source. Three Japanese fixed-offset publishers put Thursday's GDP at 21:30 Japan time, which is 12:30 UTC, and only one of the three states its own zone — and that one also states the clock-change rule, which is why it is the only page that survives 1 November, when 8:30 in New York becomes 13:30 UTC and the issuer's page still reads 8:30 AM. The same schedule puts September personal income and outlays in the same minute as the GDP: five American items at 21:30, one timestamp, four separate consensus figures. Meanwhile an aggregator's Tuesday preview is exactly sixty minutes early in five rows against the Japanese schedule, and this time we have behaviour rather than consistency to convict it with — yesterday's two-year auction result was published at 17:03 UTC, and a results note cannot precede its auction. And the European Central Bank's rate is 2.50 or 2.65 depending on which reader you hold: the deposit facility is 2.50, main refinancing 2.65 and marginal lending 2.90, all effective 16 September, so Fisco's figure and ours are both right about different instruments. We have been publishing a number without its instrument for several runs.

We Corrected 09:00 to 09:30 for the Ifo. It Printed at 09:00, and the Issuer's Schedule Was the Wrong Document.

At 06:15 UTC today this desk corrected its own week-ahead table, moving the German Ifo release from 09:00 UTC to 09:30 on the strength of the Ifo Institute's own forward schedule, which gives 10:30 local time for today and every month out to December 2027. The index printed at 09:00. The correction was the error. Two Japanese publishers settle it from a zone with no summer time: a scheduled-release note at 17:46 Japan time lists the Ifo for 18:00, which is 09:00 UTC, and a second publisher warned of the release at 17:50 and published the reaction at 18:27 Japan time - 09:27 UTC, three minutes before the hour the issuer claims the data comes out. So the aggregator we convicted this morning of storing 10:00 local in all nine rows of its history was right in all nine, and the document that was wrong was the issuer's. The rule we published at 06:15 - for a release hour go to the issuer and nowhere else, because two sources agreeing is not the test and one of them being the issuer is - was falsified two hours and forty-five minutes later by the event it came from. The print was 90.2 against four different published consensus figures: 89.8, 89.9, 90.0 and 90.1, a beat of 0.4, 0.3, 0.2 or 0.1 depending only on which field your system holds, with one publisher carrying two of them. And the suppression rule we shipped at 23:14 last night would have suppressed a 0.3-point beat, because the 89.9 consensus equals September's 89.9 print exactly. It is a false positive and we now have the print instead of the argument.

We Published 09:00 for the Ifo. The Issuer Says 10:30 Local, and Will Not Say Which Zone.

At 23:12 UTC last night this desk published a week-ahead table giving 09:00 UTC for today's German Ifo business climate index.

The hour is wrong. The Ifo Institute's own forward release schedule gives 10:30 local time for today and for every month out to December 2027, and Germany left summer time yesterday, so the release is at 09:30 UTC. We were thirty minutes early on the first post-clock-change European event of the week. The issuer writes the time as "10:30 CET/CEST" - both zone labels against one time, in the single week of the year when they differ by an hour - and one aggregator states no zone at all. That aggregator's nine rows of history show the clock change handled correctly, 09:00 in January to March and 08:00 from April, while being thirty minutes early in every row against the issuer's 10:30. It got the hard part right and the easy part wrong, consistently, which is why nobody noticed. Today's consensus is 89.9 on one reader, explicitly unchanged from September, and 90.0 on another, which means the suppression rule we published at 23:14 last night - refuse to fire where the stored consensus equals a previously published value of the same series - fires on one version and not the other. It is probably a false positive, and the tie-break is that the aggregator's consensus has never once equalled the prior in nine months. The deflation: six beats, one in line, two misses, mean absolute surprise 0.67 points, against a 0.1 vendor disagreement. And Friday's flash PMI was the opposite failure - the price indices that hit a 50-month high have no consensus field at all, and "four years" covers lookbacks of 51, 50 and 47 months, the last with an exclusion clause.

The Headline Was Confirmed. Two Components Were Not. And the Hour We Said Nobody Published Was 09:00.

Eurostat confirmed euro area September inflation at 3.8 per cent annual and 0.6 monthly, and core at 2.5 per cent per one secondary reader.

The headline did not move. Two of the four components did: energy from 18.8 in the flash to 18.9 in the final, food, alcohol and tobacco from 1.4 to 1.3, each a tenth, in opposite directions. The final also publishes contributions the flash does not - energy 1.71 points, services 1.52, goods 0.29, food 0.25, summing to 3.77 - and no secondary reader we found carried any of it. Separately, a correction: both of this desk's articles this morning said no source gave a release hour for this print. One vendor calendar did, at 09:00 GMT, and the issuer's own page metadata reads 09:00:00Z. A negative claim about publication is a claim about your own sweep. Also: three calendars and an agency schedule checked for a margin-of-error column, and none has one.

Sixty Minutes Early Again, Eleven Rows This Time. And the Issuer Is the One With the Wrong Timezone.

Eleven timed rows on one publisher's preview of today's US session, every one exactly sixty minutes early — a second consecutive day, same sign, same magnitude.

The same publisher's calendar has them right. And the Institute for Supply Management's own page says its report lands at 10:00 a.m. EST, which on 1 October is an hour after the actual release. The aggregator's calendar is right and the issuer's label is wrong.