Freight Technologies, Inc.: net current accounts receivable

What this measure means

Current customer receivables after the allowance for credit loss. The balance is not cash collected or a guarantee of collection.

Exact concept: us-gaap:AccountsReceivableNetCurrent. 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 2016-12-31 to 2025-12-31. The SEC response was captured on 2026-09-21.

Selected filing history

Related financial histories

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

Inspect the source

Entity

Freight Technologies, Inc. / CIK 0001687542

Captured

2026-09-21T17:25:15.381Z

SEC response SHA-256

d5c17d29c41bf881537825b59ffb33350eda46302a2f0a3a80d45ca7cd4f7312

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