Why this page matters most

Before claiming a finding is real, you must try to destroy it. This page documents every alternative explanation we tested — including some that genuinely challenge our conclusions.

Finding a statistical pattern is not the same as finding a cause. The pre-payday run-up could be an artifact of FOMC meetings, options expiration, inflation data releases, or the well-known turn-of-month effect. If the signal disappears once we control for these confounds, then the "payday effect" was never real — it was just a proxy for something else.

We tested three known calendar anomalies directly, engaged with two academic studies that challenge our hypothesis, confronted the turn-of-month overlap problem, and flagged several alternatives we could not test. What follows is the full accounting.

Known calendar anomalies

Three well-documented market events share calendar overlap with our payday run-up window. For each, we added a dummy variable to the regression and checked whether the payday signal (βrun) survived.

1. FOMC pre-announcement drift

What it is: The Federal Open Market Committee meets roughly eight times per year. A well-documented anomaly shows that equities rise +25 to +50 basis points in the 24 hours before the announcement (Lucca & Moench, 2015). Traders position ahead of expected rate decisions, creating a systematic upward drift before the meeting.

Why it could explain our signal: FOMC meetings are clustered in the middle and end of the month. If FOMC announcement days overlap with our lag+7/lag+8 settlement window, our signal could be FOMC drift in disguise — we would be measuring a well-known central-bank effect and calling it a payday effect.

The overlap: In the lag+7/lag+8 window, FOMC meeting days are actually under-represented — only about 40% of FOMC dates fall in the run-up window, compared to the ~57% you would expect by chance. The pattern is not being inflated by FOMC overlap; if anything, it is being diluted.

The controlled result:

EraLagBaseline βrunWith FOMC controlChange
2000–2019+8 +0.115% (p=0.017)* +0.118% (p=0.015)* +0.003% (negligible)
Full 1960–2026+8 +0.055% (p=0.019)* +0.055% (p=0.021)* -0.001% (negligible)

Verdict: SIGNAL SURVIVES — the FOMC control has essentially zero impact on the payday coefficient.

In plain English: We checked whether the Federal Reserve's meeting schedule was secretly creating our pattern. It isn't. FOMC meetings don't overlap much with the payday window, and adding a control for them doesn't change the result at all.

2. Options expiration

What it is: Monthly options expiration occurs on the third Friday of every month — a date when massive derivatives positions are unwound, delta-hedging adjustments spike, and trading volume surges. This creates well-documented end-of-day price movements as market makers rebalance.

Why it could explain our signal: The third Friday frequently lands near the 15th of the month, creating mechanical overlap with semi-monthly pay dates. If you get paid on the 15th, lag+7 often lands near the 22nd — close to the third Friday. More importantly, our signal is 100% Friday-dependent, and OpEx is a Friday event. This is the closest mechanical confound.

The overlap: Approximately 20–25% of our lag+7/lag+8 dates coincide with the 3-day OpEx window (Thursday through the following Monday of expiration week).

The controlled result:

EraLagBaseline βrunWith OpEx controlChange
2000–2019+8 +0.115% (p=0.017)* +0.115% (p=0.017)* +0.000% (none)
Full 1960–2026+8 +0.055% (p=0.019)* +0.055% (p=0.019)* -0.000% (none)

Verdict: SIGNAL SURVIVES — the OpEx dummy absorbs some variance but does not diminish the payday coefficient. However, see Section 2 below for why this verdict is more complicated than it appears.

In plain English: When we flag all options-expiration days and let the regression separate their effect from ours, the payday signal holds. But as we will explain shortly, the fact that our signal ONLY exists on Fridays means the OpEx question is not truly settled.

3. CPI release dates

What it is: The Bureau of Labor Statistics releases the Consumer Price Index (CPI) — the main inflation gauge — typically between the 10th and 13th of each month. CPI surprises can move markets sharply: a hotter-than-expected print sends stocks down, a cooler print sends them up. These releases create directional moves that could contaminate any same-window analysis.

Why it could explain our signal: CPI releases fall between the 10th and 13th, landing near the middle of the month — close to where our 15th-of-month payday's lag+0 window sits. If CPI releases systematically create positive returns on those dates, we could be measuring an inflation-announcement effect.

The overlap: CPI release dates are modestly represented in the run-up window but with no systematic direction — CPI can push the market up or down depending on the surprise.

The controlled result:

EraLagBaseline βrunWith CPI controlChange
2000–2019+8 +0.115% (p=0.017)* +0.115% (p=0.017)* +0.001% (negligible)
Full 1960–2026+8 +0.055% (p=0.019)* +0.055% (p=0.019)* -0.000% (none)

Verdict: SIGNAL SURVIVES — CPI releases have no measurable effect on the payday coefficient.

In plain English: Inflation reports come out near the same time each month, and they can move the market. But they are not what is creating our pattern. Adding a CPI control changes nothing about the result.

Combined robustness check

The definitive test: add all three controls simultaneously. If the payday signal is really just a combination of FOMC drift, options-expiration effects, and CPI reactions, it should collapse when we throw everything in at once.

Era:
βrun (%) across control specifications — semi-monthly lag +8
Grouped bars show the run-up coefficient under baseline and four control specifications. Asterisks indicate statistical significance. Toggle the era pills above to compare the mature 401(k) era (2000–2019) vs. the full 65-year sample.
After controlling for ALL THREE alternatives simultaneously:
2000–2019: βrun = +0.120% (p = 0.014)* — actually slightly stronger than baseline.
Full sample: βrun = +0.055% (p = 0.022)* — virtually unchanged.
The signal is robust to all three confounds individually and combined.

The Friday-OpEx tension

The controlled regressions above tell a clean story: add OpEx, signal survives. Case closed? Not quite. Our Friday deep-dive uncovered a finding that puts the OpEx verdict in tension with itself.

Here are the two findings side by side:

Finding A: Dummy control
Adding an OpEx dummy variable to the regression does not diminish the payday coefficient. The signal "survives" the control.
Finding B: Friday dependency
When ALL Fridays are removed from the dataset, the entire signal vanishes — every significant lag becomes insignificant.

The problem: OpEx happens on the 3rd Friday. Our signal only exists on Fridays. A dummy variable flags specific OpEx dates, but if the signal is ONLY active on Fridays, the dummy might simply be saying "OpEx Fridays are no different from other Fridays" — while the real question is why Fridays matter at all.

The specific test we have not done: Is the payday signal stronger on 3rd Fridays (OpEx Fridays) compared to 1st, 2nd, 4th, and 5th Fridays of the month? If the answer is yes, OpEx is contributing to the effect. If no, then OpEx and the payday effect are genuinely independent Friday phenomena.

Until that test is run, the two findings coexist awkwardly:

Open question: The OpEx-Friday interaction is NOT fully resolved. Our dummy-variable approach tested whether flagging OpEx dates explains the payday coefficient — it does not. But we have not tested whether OpEx Fridays carry a disproportionate share of the signal compared to non-OpEx Fridays. This remains an open question for future work.

Academic challenges

Two published studies directly engage with the "payday anomaly" hypothesis. We tested both.

3a. Ma & Pratt — "The Payday Anomaly"

Ma & Pratt (SSRN 3257064) studied day-of-month effects and found that the 16th of the month outperforms all other calendar days. Their hypothesis: semi-monthly paychecks typically arrive on the 15th, leading to 401(k) purchases on the 16th, which creates same-day buying pressure.

This is the closest academic parallel to our work. If Ma & Pratt are right, the effect should appear as a day-of-month phenomenon at day 16 — no clearing lag needed. We ran the same day-of-month regression on our 65-year dataset.

Our replication: NOT CONFIRMED

How to read this table: We ran a regression with a dummy variable for each calendar day of the month (1st through 31st). The "extra daily return" shows how much the market outperforms on that day compared to the average day, after controls. A positive green number means the market does better than normal. The confidence column indicates whether we can trust the finding is not random noise.
Calendar day What Ma & Pratt found What we found Confidence
Day 1 Not highlighted +16.4 bps (strongest day) High
Day 16 Outperforms — payday anomaly -4.58 bps Low (p = 0.485)

The 16th shows a negative coefficient in our data, and the p-value of 0.485 means we have essentially no confidence this is anything other than noise. The strongest day in our data is the 1st of the month — the classic turn-of-month effect.

Why the disagreement: Ma & Pratt used different controls, a different sample period (1980–2010), and different methodology. Our regression includes Monday, Friday, January, pre-holiday, AR(1), and volatility controls that theirs may not have included. The 16th's outperformance in their data may be absorbed by our more extensive control set. This does not necessarily mean they are wrong — it means the effect is sensitive to specification. The same data, analyzed with slightly different methods, yields different conclusions. This is a cautionary example for anyone claiming calendar anomalies.

3b. Sabbatucci — Stock Demand and 401(k) Plans

Sabbatucci (AEA 2024) asked a clever cross-sectional question: if 401(k) flow is what drives the turn-of-month effect, then stocks that are more heavily held by 401(k) plans should show a bigger turn-of-month effect. She sorted stocks by their 401(k) exposure and compared.

Her finding: High-401(k)-exposure stocks do NOT show a stronger turn-of-month effect. If anything, the effect is slightly weaker for high-exposure stocks — though the difference is not statistically significant.

This is a genuine challenge to the "401(k) flow causes the pattern" hypothesis. Three reasons it does not entirely invalidate our finding:

  1. Different calendar anchor: Sabbatucci tested the classic turn-of-month window (last 1 + first 3 trading days). Our signal is at lag+7-8 from semi-monthly paydays — different calendar dates. Her null result applies to the traditional turn-of-month, not necessarily to the clearing-lag window.
  2. Index fund mechanism: Most 401(k) equity investments go through S&P 500 index funds, which buy ALL constituent stocks proportionally. A cross-sectional test (comparing individual stocks by 401(k) exposure) would not detect an effect that hits all stocks equally through index purchases. The signal would appear in index-level returns but be invisible in stock-by-stock comparisons.
  3. We do not claim exclusivity: We never claimed 401(k) flow is the SOLE cause of the turn-of-month effect. Multiple mechanisms — salary payments, dividend reinvestment, pension rebalancing — may contribute. Our hypothesis is that 401(k) flow is one contributor, not the only one.

But: even with those caveats, Sabbatucci's finding weakens the broad "401(k) flow drives market patterns" claim. If the mechanism were as strong as a simple flow-based story suggests, you would expect to see some cross-sectional variation — even with index funds in the mix, not all 401(k) money goes to the S&P 500. Target-date funds, sector funds, and active funds would create some differential exposure.

Honest assessment: Sabbatucci's finding does not disprove our specific clearing-lag finding (different anchor, different mechanism), but it weakens the broad claim that "401(k) flow drives market patterns." The truth is likely that 401(k) flow is ONE contributor among several to a broader payment-cycle phenomenon — and its individual contribution may be smaller than we initially suggested.

The turn-of-month question

Perhaps the most important "alternative" is the one our own data ultimately pointed to: the well-documented turn-of-month effect itself.

Our component decomposition showed three signals that may all be measuring the same thing from different angles:

Payday anchor Signal location βrun p-value What calendar dates this actually represents
End of month lag+0 (the day itself) +0.056% 0.004** Last trading day of month — the classic turn-of-month
15th of month lag+16 to lag+18 +0.056% 0.005** ~1st-3rd of next month — also the turn-of-month window
Semi-monthly (combined) lag+7 to lag+8 +0.055% 0.019* A composite of both anchors' contributions

The uncomfortable implication: the end-of-month signal at lag+0 IS the turn-of-month effect. The 15th's signal at lag+16-18 points to the SAME calendar dates from a different starting point. The combined semi-monthly signal at lag+7-8 is a composite that only reaches significance when both anchors are combined.

So is our "payday effect" just a different measurement of the turn-of-month?

Partially, yes. But the historical evidence provides an important distinction:

This means the clearing-lag component appears to be a NEWER, Friday-concentrated addition to the broader turn-of-month phenomenon — potentially representing the contribution of 401(k) settlement flow to a pre-existing calendar pattern.

The relationship: Think of it like geological layers. The turn-of-month effect is the bedrock — it has been there since at least the 1960s, driven by salary payments, pension disbursements, and other monthly payment cycles (Ogden, 1990). The clearing-lag effect at lag+7-8 is a newer layer deposited on top, appearing after 1978 and concentrated on Fridays. Our "payday effect" at lag+7-8 is not the whole turn-of-month phenomenon — it is one component of it that emerged with the 401(k) system.

Untested alternatives

Intellectual honesty requires acknowledging what we did not test. Four plausible alternative explanations remain untested, each for specific reasons:

How to read this table: "Threat level" is our subjective assessment of how likely this alternative could explain part of our signal. High = we think it might genuinely contribute. Low = we think it is unlikely to be a major factor.
Alternative What it is Why we did not test it Threat level
Dividend reinvestment (DRIP) Companies pay dividends on regular schedules. Automatic reinvestment programs (DRIPs) buy shares on ex-dividend dates, creating small buying pressure. Would need ex-dividend date data for all S&P 500 constituents across 65 years — data not readily available in our dataset. Moderate — DRIPs are a real source of predictable buying flow, but they are scattered across the month with no fixed calendar anchor.
Window dressing Fund managers buy winning stocks and sell losers at quarter-end to make their portfolios look better in quarterly reports. Primarily a quarter-end phenomenon — only 4 of 24 semi-monthly paydays per year coincide with quarter-end. Low — too infrequent to drive a twice-per-month signal.
Treasury auctions The U.S. Treasury sells bonds on a regular schedule. Large auctions can temporarily depress equity prices as capital shifts to bonds, then reverses. Would need the complete Treasury auction schedule across decades. Auction timing has changed significantly over the sample period. Moderate — Treasury auctions are calendar-driven and could overlap with our window, but the mechanism (capital rotation) differs from direct equity buying.
IRA contributions Individual Retirement Account contributions can be made any time during the tax year. Some investors contribute monthly from bank accounts. Too diffuse — IRA contributions can happen any time during the year and lack a fixed calendar. No reliable data on timing. Low — contributions are too spread out and individually small to create a systematic pattern.

Where this leaves us

The honest summary:

The signal survives FOMC, OpEx, and CPI controls — individually and combined. None of these three well-known calendar events explain the payday run-up.

But the picture is complicated by several factors that prevent a clean, simple conclusion:
  • Friday dependency: The entire signal is carried by Friday trading days. Remove Fridays and every significant result vanishes.
  • Component decomposition: Neither the 15th nor the end-of-month anchor is individually significant at lag+7-8. The signal only reaches significance when both are combined, doubling the measurement opportunities.
  • The OpEx-Friday tension: Our dummy control says the signal is independent of options expiration, but the signal only exists on Fridays — the same day OpEx occurs. The interaction remains untested.
  • Sabbatucci's cross-sectional finding: High-401(k)-exposure stocks do not show a stronger turn-of-month effect, weakening the direct flow story.
  • Turn-of-month overlap: The 15th's signal at lag+16-18 points to the same calendar dates as the end-of-month's lag+0, suggesting partial measurement of the same underlying effect.
The honest conclusion: There IS a real, statistically significant pattern of elevated returns in a specific post-payday window. The clearing-lag component at lag+7-8 emerged with 401(k) growth and was not present before 1978. But its cause is more likely structural settlement mechanics — Friday-concentrated clearing flow from multiple sources — rather than a simple, single-factor "401(k) flow" story.