Menu

Individual skill

erp-finance-control-review

0upvotes

Use this skill for task_group_005-style ERP finance control work: reimbursement-to-AP close batches, stale AP reimbursement exports, vendor onboarding or account-change release reviews, and prepaid close reconciliations that require reading local scope/template payloads and current shared JSON API records. Trigger whenever the user asks for finance-risk release decisions, AP payment posture, claim close status, prepaid schedule versus GL variance, compliance hard stops, or JSON answers against the task_group_005 ERP environment.

experiments/codex_gpt5_5_xhigh/reports/skills/task_group_005/self/self_attempt_02/SKILL.md

Read pinned source

Source commit 5082a777379156a048881e94940d640702e5e09a

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
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 Control Review

Use this skill to turn scoped local payloads plus current ERP API evidence into a strict JSON answer. The recurring trap in these tasks is trusting a local snapshot or source status too much. Treat local files as scope, stale context, or schema, and treat the shared API as the system of record.

## Start With Scope And Schema

1. Read the prompt, every local payload under the task input, and the answer template before fetching API data.
2. Identify the requested population exactly: claim IDs, business IDs, prepaid invoice IDs, accounts, period, entity, review date, and any variance threshold.
3. Copy the response shape from the answer template. Respect required keys, allowed enum values, precision, and ordering notes.
4. Use the shared API described in `environment_access.md` or the runner-provided base URL. Prefer `/api/...` endpoints when both legacy and `/api` paths exist.
5. Do not read local environment source or hidden data directories. Local CSV/JSON files in the task input are allowed only as task inputs.

Useful API habits:
Back to top