PERVASIVE SOFTWARE INC: filings
Every PERVASIVE SOFTWARE INC annual and quarterly report in the SEC record with the published financial measures it tagged, 6 filings, each linked to its SEC index.
Filing record ends 2013-01-31
The latest filing in this captured record is a 10-Q filed 2013-01-31. No later filing is in the SEC companyfacts record captured on 2026-09-22. PERVASIVE SOFTWARE INC may have stopped filing, merged, or changed its reporting entity; nothing on this page describes its current status. Values are as reported at the time.
Filings with published measures
Each page shows what one filing reported, as tagged in that filing, with the periods it covered. Later filings can restate a value; the company overview shows the latest-filed value per period.
| Form | Filed | Fiscal period | Measures | Facts | SEC accession |
|---|---|---|---|---|---|
| 10-Q | 2013-01-31 | fiscal Q2 2013 | 34 | 94 | 0001193125-13-031896 |
| 10-Q | 2012-11-01 | fiscal Q1 2013 | 34 | 69 | 0001193125-12-445630 |
| 10-K | 2012-09-04 | fiscal FY 2012 | 40 | 108 | 0001193125-12-379356 |
| 10-Q | 2012-05-09 | fiscal Q3 2012 | 30 | 80 | 0001193125-12-221109 |
| 10-Q | 2012-01-26 | fiscal Q2 2012 | 30 | 80 | 0001193125-12-025081 |
| 10-Q | 2011-11-03 | fiscal Q1 2012 | 30 | 62 | 0001193125-11-295173 |
Inspect the source
- Entity
- PERVASIVE SOFTWARE INC / CIK 0001042821
- Captured
- SEC response SHA-256
3c67dfefdaf5a48b17cb2a76f424faf988b23a175c651b169b220abecf787b99
Current SEC company facts · Download the original response snapshot (gzip) · Download the selected JSON
Every published concept a filing tagged, with the periods it covered, as reported in that filing at capture time. Forms 10-K, 10-K/A, 10-Q, 10-Q/A, 20-F, 20-F/A, 40-F, 40-F/A. A filing page needs at least 8 published concepts. Later filings can restate these values; the company history pages show the latest-filed value per period.
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
Read the published dataset with Python
import json
from urllib.request import urlopen
with urlopen("https://canlicapital.com/company-data/0001042821.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"])))