# Manage Payment Terms Setup Task Guidance

> Provides task-specific setup guidance for Manage Payment Terms under the Payables functional area.

- Skill: `oracle/manage-payment-terms-setup-task-guidance` (Agent Skill, multi-file: 14 files)
- Install (CLI): `npx get-skill add oracle/manage-payment-terms-setup-task-guidance`
- Raw SKILL.md: https://api.skillmd.com/api/skills/oracle/manage-payment-terms-setup-task-guidance/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Productivity
- Author: Oracle (https://skillmd.com/u/oracle)
- Updated: 2026-11-18
- Page: https://skillmd.com/skills/oracle/manage-payment-terms-setup-task-guidance

---


# Manage Payment Terms Setup Task Guidance

## Purpose

Provides task-specific setup planning, routing, export, import, and validation guidance for `Manage Payment Terms` under `Payables`.

## Supported Operations

This task supports creating and updating Payment Terms setup records. It does not support delete or end-date operations. Only the operation-specific fields documented in [Input Validation](ora-resource/ora_input_validation.md) and [Design Enforcement](ora-resource/ora_design_enforcement.md) are permitted; all other fields remain blocked.

## Task Behavior

<!-- fscr-supported-operations: create, update -->
<!-- fscr-create-fields: AP_TERM_HEADER::Name, AP_TERM_HEADER::EnabledFlag, AP_TERM_HEADER::DueCutoffDay, AP_TERM_HEADER::Type, AP_TERM_HEADER::StartDateActive, AP_TERM_HEADER::EndDateActive, AP_TERM_HEADER::Rank, AP_TERM_HEADER::AttributeCategory, AP_TERM_HEADER::Attribute1, AP_TERM_HEADER::Attribute2, AP_TERM_HEADER::Attribute3, AP_TERM_HEADER::Attribute4, AP_TERM_HEADER::Attribute5, AP_TERM_HEADER::Attribute6, AP_TERM_HEADER::Attribute7, AP_TERM_HEADER::Attribute8, AP_TERM_HEADER::Attribute9, AP_TERM_HEADER::Attribute10, AP_TERM_HEADER::Attribute11, AP_TERM_HEADER::Attribute12, AP_TERM_HEADER::Attribute13, AP_TERM_HEADER::Attribute14, AP_TERM_HEADER::Attribute15, AP_TERM_HEADER::Description, AP_TERM_HEADER::GlobalAttributeCategory, AP_TERM_HEADER::GlobalAttribute1, AP_TERM_HEADER::GlobalAttribute2, AP_TERM_HEADER::GlobalAttribute3, AP_TERM_HEADER::GlobalAttribute4, AP_TERM_HEADER::GlobalAttribute5, AP_TERM_HEADER::GlobalAttribute6, AP_TERM_HEADER::GlobalAttribute7, AP_TERM_HEADER::GlobalAttribute8, AP_TERM_HEADER::GlobalAttribute9, AP_TERM_HEADER::GlobalAttribute10, AP_TERM_HEADER::GlobalAttribute11, AP_TERM_HEADER::GlobalAttribute12, AP_TERM_HEADER::GlobalAttribute13, AP_TERM_HEADER::GlobalAttribute14, AP_TERM_HEADER::GlobalAttribute15, AP_TERM_HEADER::GlobalAttribute16, AP_TERM_HEADER::GlobalAttribute17, AP_TERM_HEADER::GlobalAttribute18, AP_TERM_HEADER::GlobalAttribute19, AP_TERM_HEADER::GlobalAttribute20, AP_TERM_HEADER::GlobalAttributeDate1, AP_TERM_HEADER::GlobalAttributeDate2, AP_TERM_HEADER::GlobalAttributeDate3, AP_TERM_HEADER::GlobalAttributeDate4, AP_TERM_HEADER::GlobalAttributeDate5, AP_TERM_HEADER::GlobalAttributeNumber1, AP_TERM_HEADER::GlobalAttributeNumber2, AP_TERM_HEADER::GlobalAttributeNumber3, AP_TERM_HEADER::GlobalAttributeNumber4, AP_TERM_HEADER::GlobalAttributeNumber5, AP_TERM_LINE::AP_TERM_HEADER.Name, AP_TERM_LINE::SequenceNum, AP_TERM_LINE::DuePercent, AP_TERM_LINE::DueAmount, AP_TERM_LINE::DueDays, AP_TERM_LINE::DueDayOfMonth, AP_TERM_LINE::DueMonthsForward, AP_TERM_LINE::DiscountPercent, AP_TERM_LINE::DiscountDays, AP_TERM_LINE::DiscountDayOfMonth, AP_TERM_LINE::DiscountMonthsForward, AP_TERM_LINE::DiscountPercent2, AP_TERM_LINE::DiscountDays2, AP_TERM_LINE::DiscountDayOfMonth2, AP_TERM_LINE::DiscountMonthsForward2, AP_TERM_LINE::DiscountPercent3, AP_TERM_LINE::DiscountDays3, AP_TERM_LINE::DiscountDayOfMonth3, AP_TERM_LINE::DiscountMonthsForward3, AP_TERM_LINE::AttributeCategory, AP_TERM_LINE::Attribute1, AP_TERM_LINE::Attribute2, AP_TERM_LINE::Attribute3, AP_TERM_LINE::Attribute4, AP_TERM_LINE::Attribute5, AP_TERM_LINE::Attribute6, AP_TERM_LINE::Attribute7, AP_TERM_LINE::Attribute8, AP_TERM_LINE::Attribute9, AP_TERM_LINE::Attribute10, AP_TERM_LINE::Attribute11, AP_TERM_LINE::Attribute12, AP_TERM_LINE::Attribute13, AP_TERM_LINE::Attribute14, AP_TERM_LINE::Attribute15, AP_TERM_LINE::FixedDate, AP_TERM_LINE::Calendar, AP_TERM_SUBSCRIPTION::AP_TERM_HEADER.Name, AP_TERM_SUBSCRIPTION::SetCode, AP_TERM_HEADER_TRANSLATION::AP_TERM_HEADER.Name, AP_TERM_HEADER_TRANSLATION::Name, AP_TERM_HEADER_TRANSLATION::Description, AP_TERM_HEADER_TRANSLATION::Language, AP_TERM_HEADER_TRANSLATION::SourceLang -->
<!-- fscr-update-fields: AP_TERM_HEADER::EnabledFlag, AP_TERM_HEADER::DueCutoffDay, AP_TERM_HEADER::Type, AP_TERM_HEADER::StartDateActive, AP_TERM_HEADER::EndDateActive, AP_TERM_HEADER::Rank, AP_TERM_HEADER::AttributeCategory, AP_TERM_HEADER::Attribute1, AP_TERM_HEADER::Attribute2, AP_TERM_HEADER::Attribute3, AP_TERM_HEADER::Attribute4, AP_TERM_HEADER::Attribute5, AP_TERM_HEADER::Attribute6, AP_TERM_HEADER::Attribute7, AP_TERM_HEADER::Attribute8, AP_TERM_HEADER::Attribute9, AP_TERM_HEADER::Attribute10, AP_TERM_HEADER::Attribute11, AP_TERM_HEADER::Attribute12, AP_TERM_HEADER::Attribute13, AP_TERM_HEADER::Attribute14, AP_TERM_HEADER::Attribute15, AP_TERM_HEADER::Description, AP_TERM_HEADER::GlobalAttributeCategory, AP_TERM_HEADER::GlobalAttribute1, AP_TERM_HEADER::GlobalAttribute2, AP_TERM_HEADER::GlobalAttribute3, AP_TERM_HEADER::GlobalAttribute4, AP_TERM_HEADER::GlobalAttribute5, AP_TERM_HEADER::GlobalAttribute6, AP_TERM_HEADER::GlobalAttribute7, AP_TERM_HEADER::GlobalAttribute8, AP_TERM_HEADER::GlobalAttribute9, AP_TERM_HEADER::GlobalAttribute10, AP_TERM_HEADER::GlobalAttribute11, AP_TERM_HEADER::GlobalAttribute12, AP_TERM_HEADER::GlobalAttribute13, AP_TERM_HEADER::GlobalAttribute14, AP_TERM_HEADER::GlobalAttribute15, AP_TERM_HEADER::GlobalAttribute16, AP_TERM_HEADER::GlobalAttribute17, AP_TERM_HEADER::GlobalAttribute18, AP_TERM_HEADER::GlobalAttribute19, AP_TERM_HEADER::GlobalAttribute20, AP_TERM_HEADER::GlobalAttributeDate1, AP_TERM_HEADER::GlobalAttributeDate2, AP_TERM_HEADER::GlobalAttributeDate3, AP_TERM_HEADER::GlobalAttributeDate4, AP_TERM_HEADER::GlobalAttributeDate5, AP_TERM_HEADER::GlobalAttributeNumber1, AP_TERM_HEADER::GlobalAttributeNumber2, AP_TERM_HEADER::GlobalAttributeNumber3, AP_TERM_HEADER::GlobalAttributeNumber4, AP_TERM_HEADER::GlobalAttributeNumber5, AP_TERM_LINE::DuePercent, AP_TERM_LINE::DueAmount, AP_TERM_LINE::DueDays, AP_TERM_LINE::DueDayOfMonth, AP_TERM_LINE::DueMonthsForward, AP_TERM_LINE::DiscountPercent, AP_TERM_LINE::DiscountDays, AP_TERM_LINE::DiscountDayOfMonth, AP_TERM_LINE::DiscountMonthsForward, AP_TERM_LINE::DiscountPercent2, AP_TERM_LINE::DiscountDays2, AP_TERM_LINE::DiscountDayOfMonth2, AP_TERM_LINE::DiscountMonthsForward2, AP_TERM_LINE::DiscountPercent3, AP_TERM_LINE::DiscountDays3, AP_TERM_LINE::DiscountDayOfMonth3, AP_TERM_LINE::DiscountMonthsForward3, AP_TERM_LINE::AttributeCategory, AP_TERM_LINE::Attribute1, AP_TERM_LINE::Attribute2, AP_TERM_LINE::Attribute3, AP_TERM_LINE::Attribute4, AP_TERM_LINE::Attribute5, AP_TERM_LINE::Attribute6, AP_TERM_LINE::Attribute7, AP_TERM_LINE::Attribute8, AP_TERM_LINE::Attribute9, AP_TERM_LINE::Attribute10, AP_TERM_LINE::Attribute11, AP_TERM_LINE::Attribute12, AP_TERM_LINE::Attribute13, AP_TERM_LINE::Attribute14, AP_TERM_LINE::Attribute15, AP_TERM_LINE::FixedDate, AP_TERM_LINE::Calendar, AP_TERM_HEADER_TRANSLATION::Name, AP_TERM_HEADER_TRANSLATION::Description, AP_TERM_HEADER_TRANSLATION::SourceLang -->

- Take every `AP_TERM_*` CSV header and its order from the exact FSM template
  for this task. Reject short or long rows, and keep explicit trailing blank
  fields. See `ora-resource/ora_input_validation.md` and
  `ora-resource/ora_rule_registry.json`.
- Build the package with these keys:
  `AP_TERM_HEADER.Name`; `AP_TERM_LINE.AP_TERM_HEADER.Name + SequenceNum`;
  `AP_TERM_SUBSCRIPTION.AP_TERM_HEADER.Name + SetCode`; and
  `AP_TERM_HEADER_TRANSLATION.AP_TERM_HEADER.Name + Language`. Fusion resolves
  the root alternate key and derives internal parent keys. Never put an
  internal ID in the CSV. See `ora-resource/ora_design_enforcement.md`.
- For every create or update of an `AP_TERM_LINE`, `AP_TERM_SUBSCRIPTION`,
  or `AP_TERM_HEADER_TRANSLATION` row, include the matching `AP_TERM_HEADER`
  row in the same FSM archive. Unless an explicit header operation supplies
  it, copy the parent unchanged from the fresh current-data export and blank
  all audit fields. Include each parent only once. Block generation if the
  parent is absent from both the explicit operations and the fresh baseline;
  validation must reject missing or changed supporting parents.
  Fusion can mark a child-only archive as successfully imported while skipping
  its update. The non-production `AP_TERM_LINE` test proved this behavior:
  a child-only `DueDays` change remained unpersisted after a successful import.
- A new `AP_TERM_HEADER` must include at least one explicitly requested
  `AP_TERM_LINE` installment for that same header in the package. This applies
  to enabled and disabled new terms. A set assignment or translation does not
  replace an installment. Stop before preview or ZIP generation with
  `AP_AT_LEAST_ONE_CHILD` and ask for installment details; never invent a line.
  For an existing term, a header update or child create/update does not require
  adding another installment. Keep its existing installments unchanged unless
  the user requests a change.
- For a create with `AP_TERM_HEADER_TRANSLATION` rows, use the header key
  as the logical target. Fusion may display and export the explicit US
  translation name instead of that key. Derive this alias only from the
  candidate's US translation row, use it for reconciliation and UI proof, and
  record the header-key-to-display-name mapping. A KO row is translation
  evidence, not another payment-term header.
- For a new payment-term header, default an omitted or blank `EnabledFlag` to `Y`, `Type` to `STD`, and `StartDateActive` to the package-builder system date in `YYYY/MM/DD`; record each applied value as an explicit default and serialize it into the CSV. A supplied `Type` must be exactly `STD`; reject every other Type before package generation. Other explicit request values override their corresponding defaults. See `ora-resource/ora_defaulting_rules.md`.
- When preparing an import ZIP, use the date format shown in the fresh export for new or changed dates. Keep unchanged dates exactly as exported.
- Validate header dates and Rank before package generation. Dates must use the supported calendar-date format, and `EndDateActive` cannot precede `StartDateActive`. Rank is compared globally across Payment Terms, must be a whole numeric value of at most 18 digits, and must not duplicate another header's numeric Rank; do not invent a positive or minimum Rank rule. See `ora-resource/ora_input_validation.md`.
- Validate every effective payment-term line before package generation. Require exactly one due basis (`DuePercent` or `DueAmount`) and exactly one complete due-date method (`DueDays`, `DueDayOfMonth` with `DueMonthsForward`, `FixedDate`, or `Calendar`). Percentage lines for a term must total exactly 100; amount lines must include a zero-amount line; and one term cannot mix percentage and amount bases. Enforce the documented day/month ranges, nonnegative due values, complete discount pairs, and ordered discount dates and percentages. See `ora-resource/ora_input_validation.md` and `ora-resource/ora_design_enforcement.md`.
- Accept a set code, a set name, or an unspecified "set" in the user's request.
  Keep an explicit code unchanged. For a name, look up `SetName` and get its
  `SetCode`. For an unspecified set, search both fields and count distinct
  SetCodes. One distinct code allows processing; multiple codes require the
  user to choose; no matches stop ZIP/import. Never guess a code, change its
  case, or substitute a different set. Show any name-to-code mapping in the
  preview. See [Reference Lookups](ora-resource/ora_reference_lookups.md).
- Run `scripts/resolve_reference_prerequisites.py` before normalization. It
  accepts `setReference` input and fills the subscription's `SetCode` only
  after a complete, clear lookup. A supplied code or Calendar is checked by a
  read-only GET: a readable result allows processing, no rows stop it, and
  malformed responses stop it. The calendar query joins its name and type
  filters with `and`.
- For an uploaded ZIP containing set assignments or installment Calendars, run the same reference helper
  with `--package` before `validate-upload`. Pass its saved results using
  `--reference-evidence`. These results must cover every SetCode and nonblank installment Calendar
  in that exact ZIP. Missing results, no matches, or malformed responses stop validation.
  An unavailable API follows the supplied-value warning rule below.
- If a check for an explicit code or Calendar is unavailable, record
  `validation_skipped` and keep the supplied value for the separately approved
  import. HTTP 400 also records a `resolver_contract_issue` for maintenance.
  If a name or unspecified set cannot be fully looked up, stop and ask for the
  Set Code; do not use the skipped-check rule to invent a required value.
- Keep template-required audit columns as technical package behavior. Do not ask an implementation user to invent audit values; preserve non-requested values and rows from the fresh current export. See `ora-resource/ora_defaulting_rules.md` and `ora-resource/ora_input_validation.md`.
- Keep all adapter package construction and validation offline. Live export, preview, import, monitoring, persisted-state verification, commit, push, merge, and publication require their separate approvals. See `e2e-adapter.json` and `ora-resource/ora_design_enforcement.md`.

## Setup Task Skill Contract

- task_code: `AP_MANAGE_PAYMENT_TERMS`
- task_name: `Manage Payment Terms`
- parent_skill_id: `erp.financials.payables`
- pillar: `ERP`
- offering: `Financials`
- functional_area: `Payables`
- functional_area_code: `FIN_PAYABLES_DEPLOYED`
- available_flag: `Y`
- export_import_supported_flag: `Y`
- csv_export_import_supported_flag: `Y`
- dataloader_import_mode: `FSM`
- businessObject: ``
- source_catalog: `knowledge/setup-task-catalog/effective/setupTasksAll.json`

## Usage

Use this skill when planning, sequencing, exporting, importing, or validating setup data for `Manage Payment Terms` under `Payables`.

## Setup Task Metadata

- Task name: `Manage Payment Terms`
- Task code: `AP_MANAGE_PAYMENT_TERMS`
- Available: `Y`
- Export/import supported: `Y`
- CSV export/import supported: `Y`
- CSV export/import routing: `supported`
- Data Loader import mode: `FSM`
- Business Object: ``

## CSV Export, Import, and Validation Workflow

`CSVExportImportSupportedFlag` is `Y` for this task, so route task setup data work through the relevant skills:

1. Export setup task data with `shared.setup-export.task-level-export`.
2. Validate setup task data with `shared.validation.setup-data-validator`.
3. Validate reference data with `shared.validation.reference-data-validator`.
4. Import setup task data with `core.data-loader`.

Use this task metadata when invoking those skills:

- Offering: `Financials`
- Functional area / Setup Object: `Payables`
- Setup task name: `Manage Payment Terms`
- Setup task code: `AP_MANAGE_PAYMENT_TERMS`




## Inputs

- `implementation_objective`
- `project_context`
- `setup_task_scope`
- `setup_data_artifacts`

## Outputs

- `setup_task_plan`
- `setup_data_routing`
- `validation_checkpoints`
- `skill_run_record`
- `token_usage_record`

## Implementation Notes

Use the parent functional-area skill `erp.financials.payables` for functional-area sequencing and scope decisions. Track token usage for any generated project artifact or skill-run record using the manifest policy.

## Verifying Changes After Import

`reconcile` can report `PASS` only after the workflow has observed a successful
import and a later completed export from the same task and environment. Supply
`--verification-evidence <observations.json> --environment <selected-environment>
--base-url <selected-https-origin> --import-request-id <completed-import-request>`
along with the baseline, approved candidate, blueprint, requirements and export.
Missing, stale or mismatched evidence leaves verification `PENDING`; say that
saved changes have not yet been verified.

For an offline file comparison, use `reconcile --compare-only`. Its result is
`MATCH` or `DIFFERENT`, with `persistenceVerification=NOT_PERFORMED`. A file match
does not prove that an import occurred. Package building and import approval
are unchanged. See [Error Handling](ora-resource/ora_error_handling.md#reconciliation-evidence)
for the required observations.


## Reference Lookup Evidence

When a design or uploaded ZIP uses lookup receipts, follow
[Reference evidence provenance](references/reference-evidence-provenance.md).
Keep the selected target separate from evidence, require matching environment
and HTTPS origin, and rerun preflight for missing, malformed, future, or
more-than-24-hour-old observations. The same provenance checks apply to
unavailable lookup warnings. An offline receipt does not authorize a live call
or prove that Fusion imported the ZIP.


## Uploaded Package Compatibility

Before reporting an uploaded ZIP as valid, supply `validate-upload` with
`--target-context <selected-target.json>` from the independently selected
workflow target. Both baseline and uploaded metadata must match its environment
and release. Read [Uploaded package compatibility](references/uploaded-package-compatibility.md)
for the contract and migration boundary. Matching schemas alone do not establish
source/target compatibility.


## Source Manifest Labels and Origins

When producing a source manifest or verifying post-import observations, follow
[Manifest labels and HTTPS origins](references/manifest-labels-and-origins.md).
A source manifest's environment must match its ZIP metadata; keep migration
destination information separate. Use a credential-free HTTPS origin without
an API path, query or fragment. A template-only label requires an empty package.

