Billing Invoice Reconciliation with Codex: API Runtime Pattern
A production playbook for billing invoice reconciliation in billing operations using Codex: api runtime pattern, run-scoped inputs, logs, typed results, and artifacts.
Audience: Billing operations teams
The problem
Billing operations teams need billing invoice reconciliation to run repeatedly against invoices, contracts, usage exports, payment records, and dispute notes. In billing operations, the pain is not one good answer; it is repeatability, auditability, exception handling, and evidence that survives handoff.
Implementation path
Package the billing invoice reconciliation instructions as a skill, send invoices, contracts, usage exports, payment records, and dispute 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 billing invoice reconciliation, 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=billing-invoice-reconciliation
inputs[]=@./input-pack.zip
result_schema=argo.result.v1
Run this on Argo