CVM Filing Change Detector

Compare two consecutive Brazilian CVM annual financial filings and receive an exact, source-linked account of what changed.

This is a filing-to-filing comparison tool, not a general financial-data extractor. It answers a narrower question: were the same fiscal-year figures presented differently in the following annual filing?

What this Actor does

• Downloads annual DFP archives directly from CVM open data.
• Selects the latest submitted version for each requested year.
• Compares the original period with the corresponding prior-period figures in the following annual filing.
• Reports numeric changes, added or removed accounts, and description changes.
• Preserves document IDs, received dates, official URLs, units, scales, and SHA-256 hashes.
• Returns a clear no-change result when the selected statements match.
• Returns a structured rejection when the source, schema, period, or units do not permit a reliable comparison.
• Optionally preserves both official ZIP archives in the run key-value store.

Common uses

• equity research and portfolio monitoring;
• corporate credit review and covenant monitoring;
• compliance, risk, and audit trails;
• accounting reconciliation;
• M&A and financial due diligence;
• structured evidence for internal agents and automations.

Why this is different

Most financial-data tools return the latest statements, ratios, or a time series. This Actor compares two official document snapshots and retains the identity of each source. The output distinguishes:

• a numeric restatement from a newly added or removed account;
• a changed account description from a changed value;
• a verified no-change result from a comparison that could not be completed reliably.

Input

{
  "companyCnpj": "33.228.024/0001-51",
  "baselineYear": 2016,
  "comparisonYear": 2017,
  "referenceMonthDay": "12-31",
  "scope": "con",
  "statements": ["BPA", "BPP", "DRE"],
  "preserveSourceArchives": true
}

Field	Type	Default	Purpose
companyCnpj	string	required	CNPJ exactly as represented in CVM open data
baselineYear	integer	required	Year containing the original figures
comparisonYear	integer	required	Immediately following annual filing
referenceMonthDay	string	12-31	Fiscal year-end shared by both filings
scope	string	con	Consolidated (con) or individual (ind) statements
statements	string array	BPA, BPP, DRE	Statements included in the comparison
preserveSourceArchives	boolean	true	Save both official archives with the run
timeoutSeconds	integer	30	Timeout for each archive download
maxArchiveBytes	integer	40000000	Maximum accepted size for each archive

The comparison year must immediately follow the original year. This keeps the period mapping explicit: the original exercise is compared with the same exercise shown as the prior period in the following DFP.

Output

The Actor writes one report to the default dataset and to the REPORT key in the run key-value store.

{
  "schemaVersion": "1.0",
  "recordType": "filing_change_report",
  "status": "verified_change",
  "companyCnpj": "33.228.024/0001-51",
  "baselineYear": 2016,
  "comparisonYear": 2017,
  "difference": {
    "summary": {
      "numericChanges": 36,
      "addedRows": 2,
      "removedRows": 0,
      "descriptionChanges": 1
    }
  }
}

Possible statuses:

• verified_change: at least one observable difference was found;
• verified_no_change: all requested rows matched;
• rejected: the requested comparison could not be completed reliably; inspect error.code and error.message.

Every numeric difference includes the account code and description, old and new values, absolute and percentage change, currency, and scale. Added and removed rows retain their full source identity.

Source preservation

When preserveSourceArchives is enabled, the Actor stores the downloaded archives under BASELINE_SOURCE and COMPARISON_SOURCE. The report records a SHA-256 hash for each archive, even when preservation is disabled.

The run key-value store groups these records as Comparison report, Original CVM archive, and Following CVM archive so each output remains easy to identify in the Apify Console.

API and agent use

Run the Actor from Apify Console, REST API, schedules, tasks, or webhooks. The output is deterministic JSON suitable for a human review queue, an audit record, or an agent that must cite the exact source and changed lines.

Pricing

• Verified filing comparison: US$ 0.10 for one completed report with status verified_change or verified_no_change.
• Actor start: US$ 0.00005 per run.
• A report with status rejected remains visible for diagnosis and does not trigger the verified-comparison charge.
• Platform usage is included rather than charged separately.

A standard successful run therefore costs US$ 0.10005 before any Apify account-level discounts.

Boundaries

This Actor identifies observable differences between official filings. It does not determine accounting materiality, explain the economic cause of a change, provide an audit opinion, make an investment or credit recommendation, give legal advice, or allege misconduct.

Coverage is currently limited to annual DFP archives and the BPA, BPP, and DRE statements. Source availability and update timing are controlled by CVM. A first observation cannot reconstruct a file version that is no longer available from the official source unless it was previously preserved.