Catalyst Calendar

Oracle Corporation [ORCL]

Oracle Corporation [ORCL] — Catalyst Calendar

No date in this file is invented. Where a date is not announced it is shown as an ESTIMATE with the prior-year basis stated. A fabricated catalyst date is worse than an absent calendar.

Fiscal year ends 31 May. Reporting cadence over the last three years: Q1 in the second week of September, Q2 in the second week of December, Q3 in the second week of March, Q4/FY in the second week of June.

Date	Status	Event	What it tests	Why it matters to the analysis
~9–11 Sep 2026	ESTIMATE (2025-09-09, 2024-09-09, 2023-09-11 actuals)	Q1 FY2027 results	RPO balance and duration; OCI revenue against the published $32bn FY2027 path; the first full quarter of the FY2027 depreciation step-up	The single most important print. Three separate load-bearing inputs land at once.
~15 Jul 2026 (passed)	actual	Preferred dividend paid ($1,625/sh on Series D)	—	Confirms the preferred is being serviced in cash, not stock
~24 Jul 2026 (passed)	actual	Common dividend $0.50/sh paid	—	—
Continuous, FY2027	announced, undated	$20bn at-the-market equity issuance	Share count; the price at which Oracle chooses to issue	~5.8% dilution at $120. Issuing into a 1st-percentile multiple is value-destructive; the pace is the signal
Calendar 2026 remainder	announced as a negative	"Oracle does not expect to issue additional debt in calendar year 2026"	Whether this holds	If Oracle issues debt anyway before 31 Dec 2026, the funding plan has slipped and the equity issuance will be larger
~9–11 Dec 2026	ESTIMATE (2025-12-10, 2024-12-09, 2023-12-11)	Q2 FY2027 results	Same three tests; first read on whether Q1's RPO recognition rate held	—
~9–11 Mar 2027	ESTIMATE (2026-03-10, 2025-03-10, 2024-03-11)	Q3 FY2027 results	Same	—
~9–12 Jun 2027	ESTIMATE (2026-06-10, 2025-06-11, 2024-06-11)	Q4/FY2027 results and the FY2028 guide	Whether the $90bn FY2027 revenue guide was met, and the FY2028 OCI number against the published $73bn	End of the 12-month target window
Autumn 2026, undated	NOT ANNOUNCED	Financial Analyst Meeting	Whether the five-year OCI path (32 / 73 / 114 / 144) is reaffirmed, raised or cut	Oracle held one in October 2025 at which the five-year path was introduced. A 2026 edition is not announced and is listed as a possibility, not a date

What is NOT on this calendar, and why

No RPO-concentration disclosure event. There is no filing requirement that would force Oracle to publish a single-counterparty RPO percentage, and none is scheduled. The load-bearing unknown in this memo has no dated resolution. That is the most important line in this file.
No counterparty financing dates. The three Q1-FY2026 counterparties are unnamed, so their capital-raising calendars cannot be tracked from Oracle's filings. Any monitoring of this risk has to be done outside the issuer's disclosure.
No product launch dates. Oracle names the "Oracle AI Database" and an AI version of the Cerner patient-care system in its releases; neither carries a stated availability date in any filing read for this memo, so neither is dated here.
No annual meeting date. The FY2026 proxy was not read for this memo.
No analyst-day, conference or investor-event dates beyond the above.

Monitoring checklist, per print

RPO balance, and the 12/34/34/20 duration split — a fall in the next-12-month percentage is the earliest visible sign that the book is lengthening away from cash.
OCI (IaaS) revenue against $32bn for FY2027.
Capex and free cash flow — the FY2027 number against the ~$55–60bn implied.
Depreciation, absolute and as a percentage of revenue — the margin compression in ORCL_Valuation.md §2 is testable quarterly.
Contract liabilities (deferred revenue) against the $75bn "prepaid and customer supplied" claim — if genuine cash prepayment is rising, contract liabilities must rise with it.
Share count, for ATM progress.
Any change to the "no single customer accounted for 10% or more of total revenues" sentence.

Generated from each name's analysis.json. Figures are research output, not investment advice. Gaps are shown as “—” rather than filled: a missing input is recorded as indeterminate, never estimated.