# Corporate-Action Status and Effective-Date Reconciliation

`D02-F04-A05` · Corporate Actions and Security Master Data → Point-in-Time Universe · archetype `record-transform` · difficulty 4/5 · verification **verified**

Full page: https://docs.thefintechbuilder.com/corporate-actions-and-security-master-data/point-in-time-universe/corporate-action-status-and-effective-date-reconciliation/
Agent skill: `npx skills add IslamBaraka90/Fintech-Algorithms-Library` — https://docs.thefintechbuilder.com/guides/agent-skill/

## Install and import

```bash
npm install fintech-algorithms
```

```ts
import { reconcileCorporateAction } from "fintech-algorithms/corporate-actions-and-security-master-data/point-in-time-universe/corporate-action-status-and-effective-date-reconciliation";
```

## Signature

```ts
reconcileCorporateAction(input)
```

Reconstructs the highest-authority corporate-action state knowable at an as-of time while preserving conflicts and terminal messages.

## Parameters

| Name | Type | Required | Notes |
| --- | --- | --- | --- |
| `input` | `object` | yes | Topic-specific point-in-time audit contract. |

## Returns

`object`

Structured state, audit rows, diagnostics, and provenance.

## Complexity

Time `O(n log n)`, space `O(n)`.

## Worked example

Captured by running this function on the input its own test provides. Real output of real code — but not asserted against a published figure.

### Input

`input`:

```json
{
  "event_reference": "CA-77",
  "security_id": "SYNTH-XYZ",
  "event_type": "stock-split",
  "as_of": "2026-07-05T12:00:00Z",
  "records": [
    {
      "message_id": "P-1",
      "event_reference": "CA-77",
      "security_id": "SYNTH-XYZ",
      "event_type": "stock-split",
      "source": "provider-feed",
      "source_rank": 1,
      "version": 1,
      "available_at": "2026-07-01T09:00:00Z",
      "announcement_date": "2026-07-01",
      "effective_date": "2026-07-15",
      "status": "preliminary",
      "function": "new",
      "supersedes": null
    },
    {
      "message_id": "E-1",
      "event_reference": "CA-77",
      "security_id": "SYNTH-XYZ",
      "event_type": "stock-split",
      "source": "exchange-notice",
      "source_rank": 2,
      "version": 1,
      "available_at": "2026-07-03T11:00:00Z",
      "announcement_date": "2026-07-01",
      "effective_date": "2026-07-16",
      "status": "confirmed",
      "function": "new",
      "supersedes": null
    },
    {
      "message_id": "I-2",
      "event_reference": "CA-77",
      "security_id": "SYNTH-XYZ",
      "event_type": "stock-split",
      "source": "issuer-notice",
      "source_rank": 3,
      "version": 2,
      "available_at": "2026-07-04T09:00:00Z",
      "announcement_date": "2026-07-01",
      "effective_date": "2026-07-16",
      "status": "confirmed",
      "function": "replacement",
      "supersedes": "I-1"
    }
  ]
}
```

### Call

```ts
reconcileCorporateAction(input)
```

### Returns

object with 10 fields: event_reference, security_id, event_type, as_of, state, selected, applicable, conflicts, …

```json
{
  "event_reference": "CA-77",
  "security_id": "SYNTH-XYZ",
  "event_type": "stock-split",
  "as_of": "2026-07-05T12:00:00Z",
  "state": "reconciled-with-conflicts",
  "selected": {
    "message_id": "I-2",
    "source": "issuer-notice",
    "source_rank": 3,
    "version": 2,
    "available_at": "2026-07-04T09:00:00Z",
    "announcement_date": "2026-07-01",
    "effective_date": "2026-07-16",
    "status": "confirmed",
    "function": "replacement",
    "supersedes": "I-1"
  },
  "applicable": false,
  "conflicts": [
    {
      "type": "status-conflict",
      "selected": "confirmed",
      "other": "preliminary",
      "other_source": "provider-feed"
    },
    {
      "type": "effective-date-conflict",
      "selected": "2026-07-16",
      "other": "2026-07-15",
      "other_source": "provider-feed"
    }
  ],
  "eligible_message_ids": ["E-1", "I-2", "P-1"],
  "future_message_ids": []
}
```

## Verification and provenance

Tier: **verified** (via D).

The worked example below is the figure published in this algorithm's article, replayed and asserted by the test suite on every build. The arithmetic cannot drift without the build failing.

Both tiers guarantee the signature. Full explanation: https://docs.thefintechbuilder.com/guides/verification/

Generated from the docs.json payload shipped inside fintech-algorithms@0.13.1.
The signature and parameter list are checked against the compiled implementation at build time,
so a description that contradicts the code fails the build rather than reaching this file.

## Links

- Article (how it works, step by step): https://thefintechbuilder.com/corporate-actions-and-security-master-data/point-in-time-universe/corporate-action-status-and-effective-date-reconciliation/
- Implementation source: https://github.com/IslamBaraka90/Fintech-Algorithms-Library/blob/main/src/corporate-actions-and-security-master-data/point-in-time-universe/corporate-action-status-and-effective-date-reconciliation/impl.ts
- Package on npm: https://www.npmjs.com/package/fintech-algorithms
- Domain index for agents: https://docs.thefintechbuilder.com/corporate-actions-and-security-master-data/llms.txt