Guidewire Software, Inc.: diluted earnings per share

What this measure means

Reported earnings or loss per share under dilution rules. Antidilutive instruments may be excluded. A diluted value can equal the basic value without implying no potential dilution.

Exact concept: us-gaap:EarningsPerShareDiluted. Each value covers an annual-duration reporting interval, shown with both start and end dates. Different units remain separate; no currency conversion or interpolation is applied.

Coverage of this history

Selected reporting periods run from 2009-08-01 to 2026-07-31. The SEC response was captured on 2026-09-20.

Selected filing history

Related financial histories

• Guidewire Software, Inc.: total assets
• Guidewire Software, Inc.: total liabilities
• Guidewire Software, Inc.: stockholders equity
• Guidewire Software, Inc.: cash and cash equivalents
• Guidewire Software, Inc.: operating cash flow
• Guidewire Software, Inc.: capital expenditure payments
• Guidewire Software, Inc.: revenue
• Guidewire Software, Inc.: contract revenue excluding tax
• Guidewire Software, Inc.: financing cash flow
• Guidewire Software, Inc.: investing cash flow
• Guidewire Software, Inc.: retained earnings or deficit
• Guidewire Software, Inc.: basic weighted-average shares
• Guidewire Software, Inc.: diluted weighted-average shares
• Guidewire Software, Inc.: basic earnings per share
• Guidewire Software, Inc.: income tax expense or benefit
• Guidewire Software, Inc.: net property, plant and equipment
• Guidewire Software, Inc.: share-based compensation expense
• Guidewire Software, Inc.: operating income or loss
• Guidewire Software, Inc.: current assets
• Guidewire Software, Inc.: interest expense
• Guidewire Software, Inc.: current liabilities
• Guidewire Software, Inc.: current accounts payable
• Guidewire Software, Inc.: goodwill carrying amount
• Guidewire Software, Inc.: net finite-lived intangible assets
• Guidewire Software, Inc.: net current accounts receivable
• Guidewire Software, Inc.: common-stock repurchase payments
• Guidewire Software, Inc.: operating expenses
• Guidewire Software, Inc.: gross profit
• Guidewire Software, Inc.: cost of revenue
• Guidewire Software, Inc.: research and development expense

Inspect the source

Entity

Guidewire Software, Inc. / CIK 0001528396

Captured

2026-09-20T09:15:42.304Z

SEC response SHA-256

1bcfe0669ef1e428cae9f4f40ded456766c027e1e669ce68608dc5b0e725e4b3

Current SEC company facts · Download the original response snapshot (gzip) · Download the selected JSON

Latest-filed annual-report facts per unit and reporting period at capture time. Duration facts cover 300 to 400 days. This selection can include restatements and is not a point-in-time backtest dataset. Missing concepts are omitted, never zero-filled. Values retain original units and are not currency converted. Extended concepts require compatible unit shapes and at least three reporting ends with changing values within one unit. Constant or incompatible added histories are omitted.

Public company accounting reference, not market prices, returns, an investment recommendation, or ALPHAC performance. Validate a separately constructed return series with the validation API; accounting values are not returns.

Use this in research

A financial period ends before its results become public. Use the filing date as a minimum availability boundary, inspect amendments, and retain the original filing vintage when testing historical signals. This latest-filed selection can contain information unavailable at the time.

These pages do not supply prices, total-return histories, corporate-action adjustments or a tradable universe. Build those inputs separately before evaluating a strategy. A profitable backtest can still reflect selection bias or costs that were left out.

Research methodology · Execution and cost assumptions · Check backtest overfitting

Build with the open-source tools

Use these accounting records as inspectable inputs. When you have constructed a return series, the validation tools can help test its statistical evidence and preserve the result with its limitations.

• Get an API key and run your first validation
• Connect the MCP server to your coding assistant
• Inspect the ALPHAC engine on GitHub
• Read the MCP server source and integration examples

import json
from urllib.request import urlopen

with urlopen("https://canlicapital.com/company-data/0001528396.json") as response:
    record = json.load(response)
print(record["fetched_at"])
print(record["policy"])
for concept in record["concepts"]:
    print(concept["tag"], next(iter(concept["observations"])))