BENCHMARK ELECTRONICS, INC.: current liabilities

What this measure means

Obligations classified as current under the operating-cycle or one-year boundary. The balance includes more than short-term borrowing.

Exact concept: us-gaap:LiabilitiesCurrent. Each value is a balance at the reporting date, not a flow earned over a year. Different units remain separate; no currency conversion or interpolation is applied.

Coverage of this history

Selected reporting periods run from 2009-12-31 to 2025-12-31. The SEC response was captured on 2026-09-20.

Selected filing history

Related financial histories

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

Inspect the source

Entity

BENCHMARK ELECTRONICS, INC. / CIK 0000863436

Captured

2026-09-20T04:59:53.119Z

SEC response SHA-256

a6a3b7a3f63104f5e58d78fc9b3116e5556afd9d67e43307f790593473a97a4c

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