Check Point Software Technologies Ltd.: current accounts payable

At a glance

Check Point Software Technologies reported current accounts payable of $27.6 million at 2025-12-31, down 49.6% from $54.8 million a year earlier. From 2009 to 2025 it grew at a compound 7.4% a year, from $8.86 million to $27.6 million. Across the last five reported years it ranged from $9.80 million (2021-12-31) to $54.8 million (2024-12-31). That was 0.4% of total assets ($7.81 billion) at the same date.

Computed from the values in the table below, in USD; each links to the filing it came from.

What this measure means

Current amounts owed to suppliers for goods and services received. This is one component of current liabilities, not all accrued obligations.

Exact concept: us-gaap:AccountsPayableCurrent. 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 CHECK POINT SOFTWARE TECHNOLOGIES LTD. histories

• Total liabilities
• Current liabilities
• Accrued current liabilities
• Operating lease liability
• Other noncurrent liabilities
• Total assets
• Stockholders equity
• Revenue

All 54 Check Point Software Technologies histories

Inspect the source

Entity

CHECK POINT SOFTWARE TECHNOLOGIES LTD. / CIK 0001015922

Captured

2026-09-20 05:12 UTC

SEC response SHA-256

34ca1832a7100e11f5e3e5fe58c94e6e46e9a230d46806d9f305e5453f632e49

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

The MCP server is free and MIT-licensed: npx -y canli-mcp. If these records help your research, a star on GitHub helps other researchers find them.

import json
from urllib.request import urlopen

with urlopen("https://canlicapital.com/company-data/0001015922.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"])))