For analysts who build their own models

Know what changed.
See what it affects.

You can already find the number. The hard part is knowing everything it touches. SourceState connects filings to the models built on them. When a number moves, you see each cell it reaches and the evidence behind it. Nothing changes until you approve it.

See it work

  1. BacklogSep 10 · Press release

    $638Bbecame

    The headline everyone saw. On its own, it lifts your FY2027E floor by $3.12B.

  2. Due within a yearSep 11 · 10-Q note

    12%became

    One sentence in a note, with no headline. It lifts the floor by another $6.64B.

  3. Your FY2027E revenueAffected

    $76.56Bbecame

    The note moved your forecast more than twice as much as the headline.

Oracle Corporation: earnings release (Form 8-K) on September 10, 2026, Form 10-Q on September 11. Forecast from a sample analyst workbook. Select a figure to see where it comes from.

Friday, September 11, 2026

Oracle files its 10-Q.

Your fiscal 2027 revenue forecast rests on Oracle's contracted backlog. Yesterday's press release gave the headline. Today's 10-Q adds the detail your forecast depends on, in one sentence of a note. Here is what SourceState does next.

01

Detect. Three things need your attention.

SourceStateOracle · sample workbookSince your last version

3 items need attention

New filing: Form 10-Q for the quarter ended August 31, 2026

  1. 1

    FY2027E revenue sits below management guidance

    Your forecast is now $86.32B. Management guided to “at least $90 billion” the day before.

    Management guidanceModel!G12

  2. 2

    The growth assumption may be stale

    Q1 revenue grew 29.6% year over year. Your model assumes 10% for the year.

    Your assumptionInputs!C5

  3. 3

    Two inputs strengthened

    Backlog rose from $638B to $664B, and the share due within a year from 12% to 13%.

    Reported factInputs!C7Inputs!C8

Product preview10-Q, filed 2026-09-11
Step 1 of 5
02

Connect. Each change, traced to the cells it moves.

SourceStateOracle · sample workbookImpact of the 10-Q
G12fx=MAX(F12*(1+Inputs!C5), Inputs!C7*Inputs!C8)
ACFGHWhat moved it
InputFY26AFY27EFY28E
5Revenue growth, FY2027E10%Your assumption Q1 grew 29.6%
7Remaining performance obligations, $M664,000Reported fact was 638,000
8Share due within 12 months13%Reported fact was 12%
12Total revenues, $B67.3686.3294.95Calculated was 76.56, 84.22
14Operating income, $B25.90Calculated was 22.97
  1. 10-Q noteBacklog $664B
  2. InputsC7 and C8
  3. FY2027E revenueG12 $86.32B
  4. FY2028E revenueH12 $94.95B
Product preview10-Q, filed 2026-09-11
Step 2 of 5
03

Challenge. The strongest case against the new number.

SourceStateOracle · sample workbookChallenge an assumption

Is 33.6% growth credible?

Inputs!C5 proposed at 33.6%, the growth that “at least $90 billion” implies

  1. At $90 billion, the $76.56B contracted floor would cover 85% of FY2027 revenue. From FY2019 to FY2025 it covered 53% to 68%.

    SourceState inference

  2. Q1 grew 29.6%, below the 33.6% the year would need, so the remaining quarters must grow faster.

    Calculated

  3. The 33.6% rests on a single management statement. No reported full-year figure supports it yet.

    Weakest support
57%FY1957%FY2058%FY2153%FY2263%FY2367%FY2468%FY2585%FY27E
Backlog due within a year, as a share of the next year's revenue. FY27E at management's $90 billion.
Product preview8-K EX-99.1, filed 2026-09-10
Step 3 of 5
04

Decide. You approve each change, or write your own.

SourceStateOracle · sample workbookReview proposed changes

From the 10-Q

C7Remaining performance obligations, $M638,000664,000, was 638,000Accepted
C8Share due within 12 months12%13%, was 12%Accepted

From the 8-K guidance

C5Revenue growth, FY2027E10%33.6%proposed30%You entered 30%

Recalculated before you approve

G12FY2027E revenue$86.32B$87.56B, was $86.32B
H12FY2028E revenue$94.95B$96.32B, was $94.95B

Nothing is written until you approve. Formulas stay formulas. A rejected item leaves the workbook untouched.

Product preview
Step 4 of 5
05

Preserve. Months later, the reasoning is still there.

SourceStateOracle · sample workbookResearch history
  1. v1
    Anchor FY2027 revenue to contracted backlog

    From the FY2026 10-K. G12 becomes the larger of the growth path and the contracted floor, $76.56B.

  2. v2
    Refresh the floor from the Q1 10-Q

    Backlog $638B to $664B, due within a year 12% to 13%. G12 $76.56B to $86.32B.

  3. v3
    Revise the growth assumption

    10% to 30%, edited from a proposed 33.6%. G12 to $87.56B.

Inputs!C5Why is this 30%?

You changed it from 10% in v3. SourceState had proposed 33.6%, the growth management's guidance implies, and named its weakest support. You entered 30%.

Evidence
8-K guidance; Q1 revenue up 29.6%
Approved
By you, edited before accepting
Compare
v2 and v3, each changed cell with its reason
Product preview
Step 5 of 5Why this matters

A model is more than its formulas.

Excel knows that G12 depends on four cells. It cannot tell which came from today's filing, which is your own estimate, or which the filing has just put in doubt. SourceState keeps that part of the model.

Model!G12FY2027E revenue $86.32B=MAX(F12*(1+Inputs!C5), Inputs!C7*Inputs!C8)
CellWhat Excel seesWhat SourceState sees
C7664,000Remaining performance obligationsReported in the 10-Q, notes to the financial statementsChanged today, was 638,000
C813%Share due within 12 monthsReported in the same sentence of the 10-QChanged today, was 12%
F1267,357Total revenues, fiscal 2026Reported in the fiscal 2026 10-KUnchanged
C510%Revenue growth, fiscal 2027Your estimate. No filing stands behind itIn question: Q1 grew 29.6%

When a number changes, the model keeps why: the filing, the challenge, your decision. Ask months later and the answer is there.

Down to the sentence.

The 13% at the top of this page comes from this sentence. The press release never mentioned it. Every value SourceState holds keeps the company's own words, the XBRL fact that tags them, the period, and its place in the filing.

Oracle Corporation · Form 10-Q · Notes to condensed consolidated financial statementsOpen the filing
Remaining performance obligations were $664 billion as of August 31, 2026, of which we expect to recognize approximately 13% as revenues over the next twelve months, 37% over the subsequent month 13 to month 36, 34% over the subsequent month 37 to month 60 and the remainder thereafter.
us-gaap:RevenueRemainingPerformanceObligation664,000,000,000 USDAs of 2026-08-31
us-gaap:RevenueRemainingPerformanceObligationPercentage0.13 Share due in the twelve months from 2026-09-01

No number without a source.

Every figure in a SourceState answer comes from a filing or a document you supply, or from a calculation SourceState runs in code on those figures. The model writes the explanation. It never supplies a number of its own.

The data foundationAs reportedBeneath the statementsComparable across companiesBetween filings

Inside the workbook you already use.

Select a cell and SourceState knows the company, the line, the period and the filing behind it. Ask a question, open the source or propose a change without leaving Excel.

Excel add-in · Preview

For developers

The same values, each with the filing it came from, over a JSON API. Statements, series, single values and the facts behind them.

JSON API · Early access

GET /api/v1/companies/ORCL/values/revenue?period=FY2026

"value": 67357000000,
"source": {
  "nature": "reported",
  "form": "10-K",
  "accession": "0001193125-26-277521",
  "filed_date": "2026-06-22"
}

The details behind the numbers.

All Reference articles
Backlog Is Not Revenue

How to read RPO, backlog and deal value without treating them as the same thing.

What Changed in the Filing?

Separate disclosure edits from changes with economic meaning.

ARR Is Not ARR

Why a shared KPI label does not always mean a comparable measure.

Get new updates by email

New Reference articles and news about SourceState. No other use of your address.

Research should be able to show its work.

We're opening SourceState to a small number of research teams. Request access and we'll walk you through this Oracle case, live in the product.

[email protected]