What is Fiscal Period?
A company's defined accounting period (quarter or full year) that may differ from the calendar year, used as the primary temporal key in VectorFin's embedding and signal tables.
In Plain English
Most people think the year ends on December 31. But public companies can define their own fiscal year, the 12-month accounting period that determines when they close their books and file their reports. Many companies align to the calendar year, but many don't.
Apple's fiscal year ends in September. Walmart's fiscal year ends in January. Microsoft's ends in June. This creates a real problem when analyzing companies across industries: a "Q3 2024" report from Apple covers April-June 2024, while "Q3 2024" from a December-fiscal-year company covers July-September 2024. Same name, different actual periods.
This mismatch matters. If you're analyzing supply chain dynamics across the semiconductor industry, comparing Apple's fiscal Q3 (April-June) to Intel's fiscal Q3 (July-September) means you need to be careful, they cover different calendar periods. For companies in the same supply chain, fiscal period alignment shows you whether results come from the same real moment in time or are lagged.
For databases, the fiscal period is the natural primary key for time-series financial data. "AAPL 2024-Q4" uniquely identifies Apple's fourth fiscal quarter of fiscal year 2024 (July-September 2024 on the calendar). Throughout VectorFin's system, every earnings call embedding and every signal tied to a quarterly period is indexed by the (ticker, fiscal_period) key.
Companies are required to disclose their fiscal year end in their SEC filings. Calendar-year companies (FYE December 31) typically have their Q4 earnings calls in January-February of the following calendar year.
Technical Definition
Fiscal period format used by VectorFin: {YYYY}-Q{N}
Where:
YYYY= the company's fiscal year (as labeled by the company)N= quarter number within that fiscal year (1-4)
Examples:
- Apple (FYE September):
2024-Q4= July 1-September 30, 2024 - Microsoft (FYE June):
2024-Q4= April 1-June 30, 2024 - Walmart (FYE January):
2025-Q1= February 1-April 30, 2024 (calendar 2024) - Calendar-year company (FYE December):
2024-Q3= July 1-September 30, 2024
VectorFin stores both fiscal_period (company-labeled) and calendar_quarter (ISO calendar quarter) for cross-company comparisons. When comparing companies in the same supply chain, always align on calendar_quarter, not fiscal_period.
The effective_ts in VectorFin's tables is set to the end date of the fiscal period:
- Fiscal period
2024-Q4for a September FYE company: effective_ts = 2024-09-30 - Fiscal period
2024-Q4for a December FYE company: effective_ts = 2024-12-31
Earnings call timing: companies typically hold their earnings call 2-4 weeks after fiscal quarter end. This gap between fiscal period end (effective_ts) and when VectorFin ingests the transcript (knowledge_ts) is the pipeline lag.
How VectorFin Uses This
The fiscal period is the primary lookup key for embedding time-series in VectorFin's API. Embeddings are indexed by (ticker, fiscal_period), while the flat signals table is keyed by (ticker, date) and scoped with date_from/date_to:
GET https://api.vectorfinancials.com/v1/embeddings/{ticker}?fiscal_period=2024-Q4
GET https://api.vectorfinancials.com/v1/signals/{ticker}?date_from=2024-07-01&date_to=2024-09-30fiscal_period is the one selector on the embeddings endpoint, and each returned record echoes (ticker, fiscal_period, chunk_idx), the vectors only, no passage text. For cross-company analysis you can't lean on the company-labeled fiscal_period directly, because the same label spans different calendar windows. Two equivalent approaches: pull each company's matching fiscal_period and align them yourself, or use the date-keyed signals endpoint where a calendar date_from/date_to window normalizes across fiscal calendars automatically:
GET https://api.vectorfinancials.com/v1/signals/{ticker}?date_from=2024-07-01&date_to=2024-09-30A real-world calendar window lines up companies on the same actual period regardless of fiscal year end, so you can compare companies that keep different fiscal calendars.
Code Example
import requests
import pandas as pd
API_BASE = "https://api.vectorfinancials.com"
API_KEY = "vf_your_api_key_here"
# Cross-company comparison normalized to a calendar quarter window
# (the signals table is keyed by date, not fiscal period, so a date range
# aligns companies on the same real-world period automatically)
tickers = ["AAPL", "MSFT", "NVDA", "GOOGL", "META"]
# July-September 2024 calendar quarter
q_from, q_to = "2024-07-01", "2024-09-30"
print(f"Regime signal for {q_from}..{q_to} (calendar-normalized):")
print(f"{'Ticker':<8} {'Date':<12} {'Regime':<12} {'Confidence'}")
print("-" * 50)
for ticker in tickers:
# A date window aligns companies across fiscal calendars
resp = requests.get(
f"{API_BASE}/v1/signals/{ticker}",
params={"date_from": q_from, "date_to": q_to, "limit": 1},
headers={"X-API-Key": API_KEY},
)
if resp.ok and resp.json().get("signals"):
s = resp.json()["signals"][0]
regime = s.get("components", {}).get("regime", {})
print(f"{ticker:<8} {s.get('date', 'N/A'):<12} "
f"{regime.get('regime', 'N/A'):<12} "
f"{regime.get('regime_confidence', 'N/A')}")
# Note: AAPL fiscal 2024-Q4 and MSFT fiscal 2024-Q1 both cover July-September 2024
# Using a calendar date window ensures you're comparing the same real-world periodRelated Terms
External References
Put Fiscal Period to work in your pipeline
Pull AI-ready embeddings and signals as Iceberg tables or over the REST API.
Get API Access