Menu

Individual skill

erp-finance-review

ERP finance close and review operations using a shared REST API. Use when working with finance review tasks that involve cross-referencing claims, AP bills, payments, vendors, compliance records, prepaid schedules, GL balances, or close logs to produce structured release, close, or reconciliation decisions. Triggers include: (1) Reimbursement or AP claim close review, (2) Vendor onboarding or account-change release review, (3) Prepaid expense close reconciliation against GL balances, (4) Stale AP snapshot reconciliation against current system records, (5) Any task requiring multi-endpoint finance API cross-referencing to classify items into decision categories and produce JSON output matching a supplied answer template.

experiments/codex_skill_creator_comparison_deepseek_v4_pro_max/reports/skills/task_group_005/fewshot/deepagents/fewshot_attempt_01/SKILL.md

Read pinned source

Source commit 5082a777379156a048881e94940d640702e5e09a

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Instructions only
Last checked
Nov 6, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
121
Repository last updated
Oct 29, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# ERP Finance Review

## Core Workflow

When executing a finance review task, follow this sequence:

1. **Gather context**: Read the task prompt to identify candidate IDs, any local payloads (snapshots, CSVs, JSON batches), the review date/period, and the target answer template. Do not assume values from local payloads are current.
2. **Discover API surface**: Hit `GET /api/endpoints` to confirm available endpoints. Use the runner-provided `<TASK_ENV_BASE_URL>` as the base URL.
3. **Pull current records**: Query each relevant endpoint for data covering the candidate IDs. When both short-path (`/claims`) and `/api/*` (`/api/claims`) variants exist, prefer the `/api/*` path for consistency. Use query parameters or iterate IDs as needed.
4. **Cross-reference evidence**: Join records across endpoints by their shared keys. Claims join to bills and payments on `claim_id`. Business entities join across vendor and compliance endpoints on `business_id`. Prepaid invoices join to GL balances on account code. Always treat the API response as the system of record.
5. **Apply decision framework**: Classify each item using the task-appropriate framework (close review, release review, or reconciliation). Document the evidence chain that supports each decision.
6. **Produce output**: Return JSON only, matching the supplied answer template exactly. Apply the output conventions from [output_conventions.md](references/output_conventions.md).

## API Patterns