Financial Close Support with Codex: API Runtime Pattern
A production playbook for financial close support in cross-industry operations using Codex: api runtime pattern, 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
Package the financial close support instructions as a skill, send spreadsheets, statements, invoices, and reconciliation notes as run-scoped inputs, execute with Codex, poll terminal status, and consume argo.result.v1 instead of parsing a transcript.
Tradeoffs and failure modes
The API boundary forces the workflow to define inputs, terminal states, and result shape before customers depend on it. 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.
Run request
POST /api/skills/<skill_id>/run
provider=codex
workflow=financial-close-support
inputs[]=@./input-pack.zip
result_schema=argo.result.v1
Run this on Argo