Finance: Revenue Recognition Evidence Review with Claude Code: SKILL.md Template
A production playbook for revenue recognition evidence review in finance operations using Claude Code: skill.md template, run-scoped inputs, logs, typed results, and artifacts.
Audience: Revenue accounting teams
The problem
Revenue accounting teams need revenue recognition evidence review to run repeatedly against contracts, invoices, usage exports, amendments, and recognition policy. In finance operations, the pain is not one good answer; it is repeatability, auditability, exception handling, and evidence that survives handoff.
Implementation path
Put the operating procedure in SKILL.md, keep examples beside the skill, attach contracts, invoices, usage exports, amendments, and recognition policy per run, and let Argo turn the folder into a repeatable Claude Code execution.
Tradeoffs and failure modes
A skill folder is less flexible than an open chat, but it gives the product a versioned workflow that can be tested and rolled back. For revenue recognition evidence review, the practical test is whether a second run can be debugged, retried, and consumed by a product without reading the raw agent transcript.
SKILL.md starter
# SKILL.md
You run revenue recognition evidence review using Claude Code.
Read only /skill/.argo/inputs.
Write artifacts to /skill/output/artifacts.
Return argo.result.v1 with body.type = "finance_revenue_recognition".
Run this on Argo