# Payments Implementation Guidance

> Provides ERP Financials implementation guidance for the Payments functional area.

- Skill: `oracle/payments-implementation-guidance` (Agent Skill)
- Install (CLI): `npx get-skill add oracle/payments-implementation-guidance`
- Raw SKILL.md: https://api.skillmd.com/api/skills/oracle/payments-implementation-guidance/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: Oracle (https://skillmd.com/u/oracle)
- Updated: 2026-11-18
- Page: https://skillmd.com/skills/oracle/payments-implementation-guidance

---


# Payments Implementation Guidance

## Purpose

Apply [the core Data Loader execution contract](../../../../core/data-loader/SKILL.md)
to tasks with a supported FSM route. Route setup creates and changes through
`core.data-loader`; UI inspection remains read-only. Missing prerequisites block
execution, and Data Loader's approval workflow must not be duplicated.

Provides ERP Financials implementation guidance for the Payments functional area.

## When to Use

Use this functional-area skill after Financials scope is confirmed and the project needs payments setup planning, baseline export, import sequencing, or validation checkpoints.

## Catalog Metadata

- Pillar: `ERP`
- Offering: `Financials` (`XLE_FINANCIALS_JUR`)
- Functional area / Setup Object: `Payments` (`ORA_FIN_PAYMENTS`)

## Setup Tasks

1. [Manage Formats](manage-formats/SKILL.md) (`IBY_MANAGE_FORMATS`)
2. [Manage Payment Systems](manage-payment-systems/SKILL.md) (`IBY_MANAGE_PAYMENT_SYSTEMS`)
3. [Manage Payment Codes](manage-payment-codes/SKILL.md) (`IBY_MANAGE_PAYMENT_CODES`)
4. [Manage Disbursement System Options](manage-disbursement-system-options/SKILL.md) (`IBY_MANAGE_DISBURSEMENT_SYSTEM_OPTIONS`)

## Inputs

- `implementation_objective`
- `project_context`
- `payments_scope`
- `payments_requirements`

## Outputs

- `functional_area_setup_plan`
- `configuration_guidance`
- `validation_checkpoints`
- `skill_run_record`
- `token_usage_record`

## Implementation Notes

Use the generated nested setup-task skills for task-level planning, sequencing, setup-data routing, and validation. Track token usage for any generated project artifact or skill-run record using the manifest policy.

## Task Selection

Resolve the exact requested FSM task through the effective catalog and the
project-objective classifier before choosing a nested task workflow. The authored
child-skill list above is an implementation inventory, not a complete Payments task
catalog or a default task selection. For a vague request such as "configure Payments
setup using standard values", ask which exact setup task is intended; keep task
selection pending until the user resolves that scope. Resolve offering ambiguity
under the classifier's existing offering-scope rules as well.

When several tasks are explicitly requested, retain their separate identities and
route each through its owning guidance. An MPS package contains only the exact MPS
task; missing guidance for another task is a separate readiness gap.

