Fundamental Data Report Lags

A company's fiscal Q1 ends on March 31st, but its Q1 earnings report doesn't come out until several weeks later — large US companies typically file within 40 to 45 days of quarter-end, smaller companies get longer, and companies in some other jurisdictions can take considerably longer than that. A database that labels a row "Q1 2024 revenue" and lines it up as if it were known on March 31st is quietly assuming the report lag doesn't exist. Any backtest built on that assumption is trading on information before the market actually had it.

The idea

Report lag is simply the time between the end of the period a financial figure describes and the date that figure was actually released to the public. It varies by company size, jurisdiction, and filing type — annual reports typically take longer to prepare than quarterly ones, and smaller or foreign-listed companies often have longer statutory deadlines than large domestic ones. A backtest needs the filing date, not the period-end date, to determine when a piece of fundamental data could actually have been used to inform a trade, and the two dates can be six to ten weeks apart.

Worked example

A value strategy ranks stocks by trailing price-to-earnings and rebalances on the first trading day of each month, using "last quarter's" earnings. If the backtest aligns Q1 earnings (period ending March 31st) with the April 1st rebalance, it's assuming the market knew Q1 earnings the instant the quarter ended — but a company that reports on May 10th hadn't told anyone its Q1 numbers yet on April 1st. The correct backtest uses Q4 (the prior quarter's already-reported and filed) earnings for the April 1st rebalance, and only switches to using Q1 figures once each company's actual filing date has passed — meaning different stocks in the same rebalance can legitimately be using different fiscal quarters' data, since they report on different schedules.

What this means in practice

Ignoring report lag is one of the more common and consequential point-in-time mistakes in fundamental-data backtests, because it's easy to build a data pipeline that only tracks period-end dates and never captures filing dates at all. The fix requires a data source that records actual filing or release timestamps, and a backtest rule that uses only fundamentals filed strictly before the trade date for each individual security.