Q/C Technologies, Inc.: net inventory

What this measure means

Inventory carrying amount after applicable valuation and LIFO reserves. It does not establish realizable selling proceeds or inventory turnover without other inputs.

Exact concept: us-gaap:InventoryNet. 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 2013-12-31 to 2020-12-31. The SEC response was captured on 2026-09-20.

This selected history ends more than two years before capture. Do not treat its final value as a current balance or current annual result. More recent filings may use another accounting tag; inspect the filings before drawing conclusions about the company.

Selected filing history

Related financial histories

• Q/C Technologies, Inc.: total assets
• Q/C Technologies, Inc.: total liabilities
• Q/C Technologies, Inc.: stockholders equity
• Q/C Technologies, Inc.: cash and cash equivalents
• Q/C Technologies, Inc.: net income or loss
• Q/C Technologies, Inc.: operating cash flow
• Q/C Technologies, Inc.: capital expenditure payments
• Q/C Technologies, Inc.: revenue
• Q/C Technologies, Inc.: contract revenue excluding tax
• Q/C Technologies, Inc.: financing cash flow
• Q/C Technologies, Inc.: investing cash flow
• Q/C Technologies, Inc.: retained earnings or deficit
• Q/C Technologies, Inc.: basic weighted-average shares
• Q/C Technologies, Inc.: diluted weighted-average shares
• Q/C Technologies, Inc.: basic earnings per share
• Q/C Technologies, Inc.: diluted earnings per share
• Q/C Technologies, Inc.: net property, plant and equipment
• Q/C Technologies, Inc.: share-based compensation expense
• Q/C Technologies, Inc.: operating income or loss
• Q/C Technologies, Inc.: current assets
• Q/C Technologies, Inc.: current liabilities
• Q/C Technologies, Inc.: current accounts payable
• Q/C Technologies, Inc.: net finite-lived intangible assets
• Q/C Technologies, Inc.: net current accounts receivable
• Q/C Technologies, Inc.: gross profit
• Q/C Technologies, Inc.: cost of revenue
• Q/C Technologies, Inc.: research and development expense

Inspect the source

Entity

Q/C Technologies, Inc. / CIK 0001321834

Captured

2026-09-20T07:52:16.579Z

SEC response SHA-256

650911107997d4fe6608e0ae58ad39761d501fd8f1fd4f6834a4ff8e84fd08b6

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