Regulatory Reporting

Reporting drafts turn approved evidence into a narrative your team can put in a board pack, a regulator pack, or an internal SAR workpaper. Eridian does not transmit to a regulator.

Draft

POST /v1/risk/reports
Authorization: Bearer eridian_sk_...
Idempotency-Key: rpt-cse-0912-v1

{
  "project_id": "prj_risk_001",
  "case_id": "cse_0912",
  "template_id": "tpl_fc_narrative_v2",
  "model": "gpt",
  "audience": "internal_committee",
  "evidence_ids": ["evd_01", "evd_02", "evd_03"]
}

Required scope: risk:write. evidence_ids is required. The template cannot "see" the rest of the case unless you list it.

{
  "id": "rpt_0912",
  "object": "eridian.risk.report",
  "status": "draft",
  "model": "gpt",
  "title": "Desk PX-12 outbound burst, August 2026",
  "needs_approval": true,
  "eridian": { "route": "gpt", "region": "eu-west-1" }
}

Approve

Reports with needs_approval: true (the default on Enterprise) require a second principal:

POST /v1/approvals

{
  "project_id": "prj_risk_001",
  "action": "risk.report.approve",
  "resource": "rpt_0912",
  "justification": "Citations match evd_01-03. No filing recommended this week."
}

See Risk Approvals. Until approved, GET returns status: draft and download may be denied to keys without risk:write.

Export

GET /v1/risk/reports/rpt_0912/content?format=pdf
Authorization: Bearer eridian_sk_...

Formats: pdf, docx, json. PDFs include a footer with report_id, region, eridian.route, and template version.

What never happens

• SMTP to a supervisor mailbox as "the filing."
• A webhook to a government endpoint.
• Auto-disposition of the case to sar_filed because a report was drafted.

Set case disposition yourself after your filing system returns an id. You may store that id on the case as external_id.

Templates

Committee templates live in Prompt Templates. Publish requires eval and dual control when evals_required is true. Pin gpt.

See Evidence Export for the pack that accompanies a report in an exam.