Skip to content

PROGRESS SOFTWARE CORP /MA: operating cash flow

Operating cash flow for PROGRESS SOFTWARE CORP /MA. Inspect selected reporting periods, original units and SEC filing links; download the financial history.

All PROGRESS SOFTWARE CORP /MA financial histories

What this measure means

Cash generated or used by operating activities. Working-capital timing can make this differ substantially from reported income.

Exact concept: us-gaap:NetCashProvidedByUsedInOperatingActivities. 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 2007-12-01 to 2025-11-30. The SEC response was captured on 2026-09-20.

Selected filing history

Operating cash flow in original reported units, latest-filed observation per period
Period startPeriod endValueUnitFiledSource filing
2024-12-012025-11-30235,187,000USD2026-01-2010-K · 0000876167-26-000008
2023-12-012024-11-30211,494,000USD2026-01-2010-K · 0000876167-26-000008
2022-12-012023-11-30173,920,000USD2026-01-2010-K · 0000876167-26-000008
2021-12-012022-11-30192,160,000USD2025-01-2110-K · 0000876167-25-000010
2020-12-012021-11-30178,530,000USD2024-01-2610-K · 0000876167-24-000031
2019-12-012020-11-30144,847,000USD2023-01-2710-K · 0000876167-23-000036
2018-12-012019-11-30128,484,000USD2022-01-2710-K · 0000876167-22-000038
2017-12-012018-11-30121,352,000USD2021-01-2710-K · 0000876167-21-000030
2016-12-012017-11-30105,686,000USD2020-01-2710-K · 0000876167-20-000027
2015-12-012016-11-30102,845,000USD2019-01-2810-K · 0000876167-19-000026
2014-12-012015-11-30104,540,000USD2018-01-2610-K · 0000876167-18-000008
2013-12-012014-11-30107,694,000USD2017-01-3010-K · 0000876167-17-000007
2012-12-012013-11-304,580,000USD2016-01-2910-K · 0000876167-16-000060
2011-12-012012-11-30104,115,000USD2015-01-2910-K · 0000876167-15-000009
2010-12-012011-11-30126,294,000USD2014-01-2910-K · 0000876167-14-000013
2009-12-012010-11-3096,201,000USD2013-01-2910-K · 0000876167-13-000010
2008-12-012009-11-3062,758,000USD2012-01-3010-K · 0001193125-12-029136
2007-12-012008-11-3087,182,000USD2011-01-3110-K · 0000950123-11-007372

Related financial histories

Inspect the source

Entity
PROGRESS SOFTWARE CORP /MA / CIK 0000876167
Captured
2026-09-20T05:01:03.141Z
SEC response SHA-256
592c4ab20b131eb2c5bb5d877954ed53f9129d6de9dfd3a7a53bff0fa7b2e007

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.

Read the published dataset with Python
import json
from urllib.request import urlopen

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