fiscal.anomaly_detected

Constanza AI detected an unusual pattern in an organization's financial data (z-score outlier, Benford violation, duplicate transaction, timing anomaly, etc.). Routed to Camino for CRM health alerts and to Colectiva so the Brain can factor fiscal anomalies into business intelligence.

Senders

• constanza

Receivers

• camino
• colectiva

Data schema

Each field maps to a type hint. | null indicates an optional field.

{
  "organizationId": "string",
  "anomalyType": "string (amount_outlier|timing_unusual|frequency_spike|benford_violation|pattern_break|cross_platform_mismatch|ratio_anomaly|duplicate_detection|round_number_suspicious)",
  "severity": "string (medium|high|critical)",
  "title": "string",
  "description": "string",
  "score": "number (0-100 confidence)",
  "affectedPeriod": "object { startDate: string (ISO), endDate: string (ISO) }",
  "detectedAt": "string (ISO datetime)",
  "relatedTransactions": "string[] (optional)",
  "suggestedActions": "string[] (optional)"
}

Example payload

The following is a synthetic payload that matches the schema. Production payloads are signed with HMAC-SHA256 and delivered to each receiver's registered webhook endpoint.

{
  "organizationId": "example-organizationId",
  "anomalyType": "amount_outlier",
  "severity": "medium",
  "title": "example-title",
  "description": "example-description",
  "score": 0,
  "affectedPeriod": {},
  "detectedAt": "2026-04-17T12:00:00.000Z",
  "relatedTransactions": [
    "example-relatedTransactions"
  ],
  "suggestedActions": [
    "example-suggestedActions"
  ]
}

See also

• Events registry index
• Webhooks integration guide
• Errors & retries

---

Generated from ecosystem-sdk/packages/mcp-server/src/registry/events.json. Do not edit by hand.