| name | erp-finance-control-review |
| description | Use this skill for task_group_005 ERP finance API tasks, especially reimbursement-to-AP close reviews, stale AP batch refreshes, vendor onboarding or account-change release controls, prepaid close reconciliations, AP aging, payments, vendors, compliance, claims, bills, GL balances, and close-log checks. Trigger whenever the prompt asks for JSON decisions from the shared ERP finance API, even when local payloads look sufficient, because the API is the system of record and the templates have strict field, ordering, and precision rules. |
ERP Finance Control Review
Use this SOP to solve task_group_005 finance-control tasks from the shared API. The common shape is: a prompt gives a narrow batch, local payloads define scope and output shape, and the remote ERP API supplies current evidence. Local exports can be stale context; do not treat them as authoritative unless the prompt explicitly asks you to compare against them.
First Pass
- Read the prompt, every local input payload, and the answer template before querying. Extract:
- Target IDs only: claim IDs, business IDs, invoice IDs, accounts, periods, entity, as-of date, review date, thresholds, and batch IDs.
- Required top-level keys, enum values, list ordering, and numeric precision.
- Use the runner-provided API base URL. If an environment note is present, prefer that value over prompt examples such as localhost. Do not read local environment source or data directories.
- Start with
/health, /api/health, or /endpoints if the API shape is uncertain. Object-list endpoints return count, data, limit, offset, and total.
- Query only the scoped records. Endpoints support exact-match query parameters by field name plus
limit and offset.
- Treat current API records as the source of truth. Use local CSV or JSON snapshots only for scope, ticket context, stale-row correction labels, or requested metadata.
