KabuForge
Menu
GitHub日本語

J-Quants Disclosures: Times and Financial Revisions

A reporting period ends before its results are published.

Period end is not publication

A reporting period ends before its results are published. Joining a financial value to the period-end trading decision can therefore introduce unpublished information.

If a fictional March report is announced on May 10 in the evening, it cannot inform a March decision or the May 10 opening decision. Availability must be compared with the decision cutoff.

Separate disclosure and receipt

V2 summary records include disclosure date and time fields. A disclosure timestamp alone does not prove that a particular local input was delivered or validated at that time.

Record time conventions and decision cutoffs. When a timestamp is unknown, do not assign a convenient midnight value; any conservative delay is an explicit assumption rather than historical proof.

Preserve revisions as history

A corrected number is a new information state. If fictional profit changes from 100 to 90, replacing every historical observation with 90 prevents reconstruction of the earlier decision.

Do not remove changing releases as identical duplicates. Select the version available at each decision cutoff, and identify final-restated analysis as a separate experimental condition.

Distinguish plans from releases

An earnings schedule describes an expectation, whereas a released report describes an actual information event. They belong to different feature definitions.

If a fictional Friday release is postponed, retain the original schedule and when the postponement became known. The final calendar cannot automatically reconstruct the earlier event expectation.

Respect the course's evidence boundary

KabuForge's public course uses selected price history and remains research-only. It does not automatically certify financial disclosure histories or historical data delivery.

Before extending a study to disclosures, build a separate availability table linking period, release version, cutoff and receipt evidence. Unknown availability should remain an explicit limitation.

Further reading and official references

Continue with Designing Inputs for Japanese Equity Backtests, J-Quants and Point-in-Time Research, What Is J-Quants? Research Uses and Limits to connect input definitions, availability and evaluation. All numerical and company examples in this article are fictional teaching examples. For real input, prioritize the documentation for your version and your own acquisition and execution records.

Check the official KabuForge GUI research course for documented workflow scope, and J-Quants: official V2 financial implementation, J-Quants: official V2 column definitions for provider documentation or current official implementation. Confirm exact units and access limits against the applicable official specification and contract. General research design guidance does not establish that every proposed check is implemented in the GUI.

This article is educational and does not recommend securities or trades, or guarantee returns. Historical research in the public course does not fully establish that only historically available information was used. Read the disclaimer.

Continue this topic

Explore the j-quants learning path

Applies to: main source candidate (unpublished) · Public source docs/en_US/GUI_RESEARCH_COURSES.md

Reviewed · KabuForge