FREQUENCY ELECTRONICS, INC.: selling, general and administrative expense

What this measure means

Selling and general administrative costs reported under this concept. It is an expense category, not a substitute for total operating expenses.

Exact concept: us-gaap:SellingGeneralAndAdministrativeExpense. 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 2010-05-01 to 2026-04-30. The SEC response was captured on 2026-09-19.

Selected filing history

Related financial histories

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

Inspect the source

Entity

FREQUENCY ELECTRONICS, INC. / CIK 0000039020

Captured

2026-09-19T11:13:22.083Z

SEC response SHA-256

31cb544ef74abbc783e9468f228dfdda0bdc60698657b582c8b6e273a589a468

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/0000039020.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"])))