KabuForge
Menu
GitHub日本語

J-Quants Financial Data: Periods and Units

Financial data has a reporting period and a disclosure timeline.

Read the two financial timelines

Financial data has a reporting period and a disclosure timeline. Keeping only one date loses both the measurement context and the information-availability context.

The official V2 client has summary and detailed financial interfaces. Do not assume that every value describes a standalone quarter; determine the period and document context first.

Distinguish cumulative and standalone values

Suppose a fictional company reports first-quarter sales of 100 and cumulative half-year sales of 240. A standalone second quarter is 140 only if both observations share the same measurement definition.

Check consolidation, accounting basis, period length and revision status before subtraction. Preserve both source records and the transformation rule so the derived quarter can be inspected.

Record units per field

Currency amounts, per-share values, ratios and share counts have different units. Confirm the official unit and preserve any scaling performed for research.

If fictional sales are displayed in millions while a price uses yen, align the scale before calculating a ratio. Keep missing values distinct from zero; absence of disclosure is not evidence of a zero amount.

Separate results and forecasts

Reported results and company forecasts are different observations even when they refer to the same fiscal year. Specify value type and target year in the feature definition.

For a fictional forecast-revision study, retain earlier and later releases separately. Applying the final forecast to all past dates introduces information that did not exist before the revision.

Keep design separate from import support

These financial checks are general research design guidance. The public KabuForge daily-bar course does not establish support for importing financial summaries or detailed statements.

A financial experiment needs its own validated definitions of periods, units, releases, transformations and availability. Consult the applicable software version before asserting an import capability.

Further reading and official references

Continue with Disclosure Times and Financial Revisions, Adjusted Prices and Stock Splits, Data Storage and Reproducible Research 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