Financial Close Support with Claude Code: Result JSON Schema

A production playbook for financial close support in cross-industry operations using Claude Code: result json schema, run-scoped inputs, logs, typed results, and artifacts.

Audience: Accounting automation teams

The problem

Accounting automation teams need financial close support to run repeatedly against spreadsheets, statements, invoices, and reconciliation notes. In cross-industry operations, the pain is not one good answer; it is repeatability, auditability, exception handling, and evidence that survives handoff.

Implementation path

Define the outer result contract once, let the financial close support skill own body.data, and reject terminal output that does not match the expected schema.

Tradeoffs and failure modes

Schema enforcement adds upfront design work, but removes prompt parsing from the product surface. For financial close support, the practical test is whether a second run can be debugged, retried, and consumed by a product without reading the raw agent transcript.

Result shape

{
  "schema_version": "argo.result.v1",
  "summary": "financial close support completed",
  "body": { "type": "financial_close_support", "data": {}, "exceptions": [] },
  "artifacts": []
}

Run this on Argo