Finance: Expense Audit Review with Codex: API Runtime Pattern

A production playbook for expense audit review in finance operations using Codex: api runtime pattern, run-scoped inputs, logs, typed results, and artifacts.

Audience: Finance teams auditing employee expenses

The problem

Finance teams auditing employee expenses need expense audit review to run repeatedly against receipts, policy docs, card transactions, and reimbursement requests. In finance operations, the pain is not one good answer; it is repeatability, auditability, exception handling, and evidence that survives handoff.

Implementation path

Package the expense audit review instructions as a skill, send receipts, policy docs, card transactions, and reimbursement requests 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 expense audit review, 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=finance-expense-audit
inputs[]=@./input-pack.zip
result_schema=argo.result.v1

Run this on Argo