Manage Receivables Payment Terms
Purpose
Plan, validate, prepare or review an offline package, export, import, monitor,
and verify the catalog-backed Manage Receivables Payment Terms setup task
under Customer Billing. Resolve customer ambiguity from current evidence and
fail closed instead of inventing setup values.
Customer Interaction Contract
A business-language request is sufficient. Do not ask the customer to name the
FSM task, CSV files, APIs, Data Loader, internal services, or database tables.
Infer those mechanics from this skill and the routed FDOS workflow.
Examples of sufficient prompts include:
- "Create a Net 30 payment term."
- "Create a term with 50 percent due in 30 days and 50 percent due in 60 days."
- "Update the discount on Net 10 to match this approved design."
- "End-date our legacy immediate payment term."
- "Import the attached approved payment terms into our test environment."
- "Check the Payment Terms load and verify it."
- "Create these 100 payment terms from the attached approved list."
- "Create the new Net 60 term and update the description of our existing Net 45 term."
Ask only for unresolved business or authorization facts that materially change
the result: payment-term identity, reference data set, effective dates,
installments, print lead days for a split term, tax/freight installment option,
discount basis, discounts, balance-forward behavior, translations, flexfields,
target environment, or the required standalone approval.
For an update, treat the exact existing Name plus resolved reference data set
as the immutable selector. Ask for the exact name when current evidence contains
zero or multiple candidates. Do not interpret a request to rename a term or move
it to another set as an in-place update; explain that this package workflow does
not support that identity change and ask whether the customer wants a separate
create/end-date design.
Ambiguity and Clarification Contract
Never require a customer to know SetCode, CSV column names, FSM task codes, or
loader terminology. Accept business-language identities such as a reference
data set name, the business unit that must use the term, or a stated sharing
intent, and resolve them only through current target evidence.
The normalized JSON blueprint used by the bundled helper is an internal
execution artifact. Never ask the customer to create, edit, or understand that
JSON. Translate every structured blocker returned by the helper into one clear
business question under the contract below.
For every required identity or lookup-backed value, apply this exact contract:
| Evidence result |
Required behavior |
| One exact candidate |
Use it, disclose the resolved business value and source, and continue. |
| No candidate |
Stop before package preparation and ask one business-first question. Show the supplied value, explain why it is required, and provide current valid choices when available. |
| Multiple candidates |
Stop before package preparation and ask the customer to choose. Show distinct display names and codes; never select the first, COMMON, ENTERPRISE, or a fuzzy match. |
| Missing or stale evidence |
In live mode, route a fresh read-only export through the owning workflow. In offline mode, request the current artifact and make no external call. |
| Conflicting request and evidence |
State the conflict and ask which business outcome is intended. Do not silently reinterpret create as update, change a set, or replace a date or schedule. |
Ask one consolidated clarification at a time containing only the unresolved
business decisions. Offer a bounded list of current choices and say when more
choices are available. Re-run all affected rules after the reply; do not reuse
an earlier resolution after the target, artifact, request, or release changes.
When one prompt contains several requested changes, normalize it as one
all-or-nothing locally validated batch of distinct Payment Term operations.
Support mixed create, update, and
end-date operations and up to 100 distinct Name plus resolved-set targets in
one task-scoped package. Do not invent missing names or expand an unspecified
"100 terms" request: accept an attached list or a customer-stated deterministic
name/value pattern, otherwise ask for the missing business design. Resolve and
validate every operation before preview; one unresolved or invalid operation
blocks the entire batch and no partial ZIP is created. If the prompt addresses
the same parent more than once, consolidate compatible changes into one
operation and show the result; if they conflict, ask which outcome is intended.
For a create request, require one evidence-backed base language and a base
translation row before preview. When target evidence contains zero or multiple
possible languages and the customer did not specify one, ask which business
language to use and create no ZIP. Never treat an absent translation request as
permission to omit the base-language row.
For a payment term with more than one schedule line, require a positive
whole-number Print Lead Days value and ask whether tax and freight should be
allocated across all installments or included in the first installment. Do not
infer either business choice from the term name, allocation percentages, or a
different environment. FirstInstallmentCode is mandatory on every header. For
a create with exactly one installment, use and disclose INCLUDE: the only
installment is also the first, so this does not change allocation behavior. For
multiple installments, always require the customer's explicit tax/freight
choice. CalcDiscountOnLinesFlag is also mandatory on every payment-term
header. When no discount rows are requested, use and disclose the product-backed
Invoice Amount value I; when discount rows are requested, require the
customer-selected discount basis. Use the product default Application Date only
for the discount basis date when the customer has not requested another
supported date basis.
Final Design Confirmation Contract
Before generating an offline candidate ZIP, run the bundled preview command
and show one concise business summary containing the action, payment-term name,
reference data set, effective dates, base amount, every installment, discounts,
base/source language, print lead days, installment tax/freight option, discount
basis/date, partial-discount behavior, credit-check/prepayment flags, applied
defaults, and any balance-forward or flexfield behavior. State that BaseAmount
is the installment-ratio denominator, not a currency amount. Then ask the
governing orchestration to capture design confirmation.
For updates, the preview must show a before/after change list, every added row,
and the number of unchanged fields preserved from the current export. Include
the base-language and additional-language descriptions in that preview. An
update preview that shows only the requested header values is incomplete.
For a batch, show the operation count and action counts, then identify every
term by action, exact name, set, dates, and schedule. Show the full detailed
summary for every operation with nondefault flags, discounts, translations,
flexfields, or updates. Bind one orchestration-owned design confirmation to the complete batch
design; never confirm or build a successful subset while another operation is
blocked.
Treat this as confirmation of the normalized local design only. It is not the
Core Data Loader candidate-specific approval required for a later Fusion import and does not authorize
authentication, upload, initiation, or any environment change. Do not infer
the orchestration-owned design confirmation from the original request, a reference-data-set answer, silence, or a
longer message. Bind the confirmation to the preview's design SHA-256 and both
source-package hashes. Any change to the request, resolved value, source ZIP,
blueprint, or target invalidates it and requires a new preview and confirmation.
Keep the archive-generation confirmation envelope in the normalized blueprint
when calling build; it is workflow metadata excluded from the business-design
hash, not a customer field. It must contain only confirmed: true and the exact
preview design_sha256. Never remove it before build, translate its snake-case
key to another spelling, or add approval, timestamp, user, or environment data
to that envelope. Store import approval and other execution metadata only in the
separate orchestration run record.
Setup Task Contract
- Task code:
AR_MANAGE_RECEIVABLES_PAYMENT_TERMS
- Catalog availability:
Y
- Export/import support:
Y
- CSV export/import support:
Y
- Data Loader import mode:
FSM
- Catalog:
knowledge/setup-task-catalog/effective/setupTasksAll.json
Supported Scope
| Customer request |
Handling |
| Create |
Build a new parent payment term and its applicable lines, translations, and discounts after exact-set duplicate checks. |
| Update |
Preserve unchanged export-backed values and package only a supported, reviewed change. |
| End-date |
Update the supported end-date field after current-state and date validation. |
| Mixed or batch request |
Build one all-or-nothing task package for up to 100 distinct parent identities after every operation passes the same create/update/end-date rules. |
| Hard delete |
Refuse; use an evidence-backed update or end-date when appropriate. |
| Export |
Route through shared.setup-export.task-level-export. |
| Validate |
Run shared setup/reference validation, then the compiled task-resource plan. |
| Import |
Route only through core.data-loader; this task skill never chooses or calls an import endpoint or adapter. |
| Monitor |
Route request-ID or data-set status and diagnostics through core.data-loader. |
| Verify |
Run a fresh read-only task export and compare the persisted header, lines, translations, and discounts with the approved preview. |
| Offline prepare |
Preview the normalized design, obtain the orchestration-owned design confirmation, then build a candidate ZIP only from an exact successful task-level template and current baseline using the bundled local helper; make no network call and do not treat design confirmation as import approval. |
| Offline review |
Inspect an attached ZIP locally, report task scope, metadata, rows, relationships, rule results, and SHA-256, and stop without authentication, upload, or approval. |
Business Object Package
Treat the PaymentTerm package as one parent-child unit in the order established
by the current target template and ASM_SETUP_CSV_METADATA.xml.
| Role |
CSV entity |
Required business linkage |
| Header |
AR_PAYMENT_TERM |
Name plus SetCode |
| Installment schedule |
AR_PAYMENT_TERM_LINE |
Parent Name and SetCode, plus unique line SequenceNum |
| Translation |
AR_PAYMENT_TERM_TRANSLATION |
Parent identity plus supported Language and SourceLang |
| Discount schedule |
AR_PAYMENT_TERM_DISCOUNT |
Parent identity plus an existing payment-line sequence; child SequenceNum must equal the referenced line sequence, and DiscountPercent must be unique on that line |
Source-Backed Task Behavior
- A payment term is one parent package containing a header, at least one
installment line, the required base-language translation, and any applicable
discount rows. The parent identity is the exact
Name plus SetCode.
Sources: SRC-FSM-PACKAGE, SRC-INTERNAL-DEV-001.
BaseAmount is the installment-ratio denominator, not a currency amount. The
relative amounts of all installment lines must add exactly to that base
amount; one unresolved or invalid line blocks the complete parent operation.
Sources: SRC-FSM-PACKAGE, SRC-INTERNAL-DEV-001.
- Each installment line has a stable positive
SequenceNum and must use one
complete supported due-date method. A split term requires an explicit
positive whole-number Print Lead Days value and an explicit tax-and-freight
allocation choice before preview.
Sources: SRC-FSM-PACKAGE, SRC-INTERNAL-DEV-001.
- A discount belongs to an existing installment line. Its
SequenceNum must
equal that line sequence, its percentage must be unique on the line, and no
line may contain more than three discount rows.
Sources: SRC-FSM-PACKAGE, SRC-INTERNAL-DEV-001.
- A create must include exactly one evidence-backed base-language translation
where
Language equals SourceLang. Updating the base description changes
both the header and that base translation while preserving every unrequested
non-base translation.
Sources: SRC-FSM-PACKAGE, SRC-INTERNAL-DEV-001.
- Create, update, and end-date operations may be combined in one all-or-nothing
task package for distinct parent identities. A duplicate target, conflicting
operation, unresolved prerequisite, or invalid row blocks the entire package;
no partial candidate is generated.
Sources: SRC-FSM-PACKAGE, SRC-INTERNAL-DEV-001.
- An update is a patch against exactly one current exported parent. Preserve
every unspecified supported header value and child row.
Name and SetCode
are immutable, and omission is not a supported request to delete a line,
translation, discount, or parent.
Sources: SRC-FSM-PACKAGE, SRC-INTERNAL-DEV-001.
LastUpdateDate, LastUpdatedBy, CreationDate, CreatedBy, and
LastUpdateLogin are service-owned. Keep them only as read-only baseline
evidence and emit them blank in every generated import row.
Sources: SRC-FSM-PACKAGE, SRC-INTERNAL-DEV-001.
- Build only from a successful exact-task template and current export whose
environment, Fusion release, entity paths, CSV headers, and metadata agree.
A broader offering or functional-area archive is review evidence, not a
Payment Terms import template.
Source: SRC-FSM-PACKAGE.
Update Mutation Contract
An update blueprint is a patch against exactly one current exported parent, not
a replacement document. Preserve every unspecified supported header field and
every unspecified line, translation, and discount row. Patch children only by
their stable import identity: payment line SequenceNum, translation
Language, and discount parent-line sequence plus DiscountPercent.
Name and SetCode identify the parent for this workflow and are not mutable
update fields. Omitting a child row never means delete: Fusion CSV import does
not provide a safe generic delete-by-omission contract. Refuse requests to
remove an installment, translation, or discount, contract a schedule by
omission, rename a term, or move it between sets. Offer a separately reviewed
create/end-date or supported product workflow instead.
Description is translatable. When the customer changes the base description,
write the same value to the header and the one current base-language translation
row where Language equals SourceLang; preserve every non-base translation
unless it was explicitly supplied. If the base row is missing or ambiguous,
stop before preview and request fresh evidence or a business-language choice.
Reject conflicting header and base-translation descriptions. A structurally
valid ZIP is not sufficient unless its complete rows exactly match the
normalized request plus the preserved baseline state.
Never invent columns, audit values, lookup codes, package order, or metadata.
Treat LastUpdateDate, LastUpdatedBy, CreationDate, CreatedBy, and
LastUpdateLogin as service-owned evidence on every create, update, and
end-date import candidate. Preserve them in the read-only baseline for
diagnosis, but emit them blank in every candidate row.
Derive them from the current target template/data export. Never write directly
to RA_TERMS_B, RA_TERMS_TL, RA_TERMS_LINES, or
RA_TERMS_LINES_DISCOUNTS.
Treat current metadata as an executable contract: compare every CSV header to
its declared XmlAttributeList/XmlAttributeTypeList, and require template and
baseline environment, release, entity contract, and CSV headers to match. Do
not build from mixed-pod or mixed-release exports.
A task-level build template must contain exactly one
ASM_SETUP_CSV_METADATA.xml, declare only the Payment Terms entities, and have
a successful completed process status. Accept either of Fusion's exact
task-export identity shapes: one explicit migration task definition with only
AR_MANAGE_RECEIVABLES_PAYMENT_TERMS selected, or no task-definition rows and
the top-level ObjectShortName equal to that task code with ObjectType equal
to TASK. A broader functional-area or offering package may be reviewed as a
multi-task package, but this task skill must not rewrite its metadata, extract
it into a new import package, or present it as a task-level Payment Terms
archive.
Routed Workflow
- Start through
router/implementation-router/SKILL.md and select the active project and target environment.
- Normalize the business request. Resolve each required identity by the ambiguity contract and ask only one consolidated business clarification when evidence cannot prove one result.
- Determine the requested mode. For offline preparation or review, use only supplied local artifacts. Otherwise export the current task template and, when existing-state comparison is needed, current task data through
shared.setup-export.task-level-export.
- Run
shared.validation.setup-data-validator and shared.validation.reference-data-validator.
- Compile and plan the task-local rules, then evaluate the six resources in the order listed below. Execute every known product constraint in the local validator; a message listed only in documentation is not considered covered.
- For offline preparation, first run
validate --source-evidence on both the exact task-level template and current baseline export. This checks their archive, metadata, task scope, status, CSV presence, and source row counts without applying new-candidate rules to pre-existing target rows. Resolve the create base language and all other ambiguity, then run preview with the normalized blueprint. Show its complete business summary, including update deltas and translated descriptions, and ask for the orchestration-owned design confirmation; create no ZIP yet. After that exact reply, record the returned design SHA-256 in the internal blueprint confirmation and use build. The helper must reject missing or stale confirmation, independently validate the candidate against the current baseline and normalized blueprint, and repeat generation to prove an identical SHA-256. For review of a proposed import package, run validate; when a baseline and blueprint are available, both are mandatory so semantic intent is checked rather than ZIP structure alone. These commands are local and never authorize a Fusion write.
- Treat the build result's
uploadHandoff as a mandatory human/tool handoff. Confirm the filename and SHA-256, target environment and release, and exact task name/code. Never reuse a ZIP from a failed run or choose a similarly named file. If a person performs the upload, they must open the exact Manage Receivables Payment Terms task and use its Import from CSV File action; an offering-level or functional-area-level import page will reject this task-scoped archive.
- For an intended import, hand the exact task context and validated candidate to
core.data-loader. Core Data Loader owns final immutable archive preparation, Task Hook validation, preview, archive SHA-256 binding, execution routing, upload, and initiation.
- Stop after the immutable preview and hand the immutable candidate to Core Data Loader for its candidate-specific approval. Do not infer approval from the original request or a longer message.
- On that separate approval, let Core Data Loader revalidate and submit the unchanged archive once. Do not select a task-local fallback or reconstruct the validation envelope.
- Treat successful initiation as accepted, not as verified setup. For a later generic status request, let Core Data Loader retrieve status, counts, errors, and available logs without resubmitting.
- After successful terminal processing, perform a fresh read-only task export and run the bundled
reconcile comparison against the exact submitted candidate. Mark the setup verified only when every expected header, line, base/additional translation, and discount value matches. System-generated extra translation languages may be reported separately; unexpected extra schedule or discount rows remain mismatches.
Portable Offline Package Workflow
The bundled helper uses only the Python standard library and repository-relative
paths. It reads ZIP/CSV/XML artifacts locally and never reads environment
properties, credentials, tokens, browser state, or laptop-specific paths.
Use the legacy normalized JSON shape with action, header, lines,
translations, and discounts for one operation. For more than one operation,
use operations, where each item contains operation_id, action, header,
lines, translations, and discounts. Never mix the two shapes. Both shapes
may include optional current evidence for reference data
sets, billing cycles, the partial-payment system option, languages, or
flexfield contexts, and an internal archive-generation confirmation added
only after standalone customer confirmation. Reference-data-set evidence may prove a valid empty set
that has no Payment Terms rows in the current task export.
Preserve only template-supported fields. For descriptive flexfields, require
both the exact current target context and the exact template attribute columns
proven for that context; context existence alone does not authorize any
Attribute1 through Attribute15 value. Derive evidence only from the routed
current exports; never ask a customer to fabricate technical evidence. For
update or end-date, supply the current baseline so unchanged export-backed
values are retained.
The helper accepts at most 100 operations, requires a unique operation_id and
resolved Name plus SetCode target for each, combines the four entity CSVs only after all
operations pass, and binds confirmation and deterministic generation to the
entire combined row set. A batch failure reports the operation index and ID.
This is an all-or-nothing local validation and generation guarantee, not a
claim that Fusion import processing is one database transaction. Never hand-edit
a partial batch after validation, and always reconcile every operation after
live processing, including after a failed process that might have persisted a
subset.
For create, apply only these product-backed non-business defaults when their
template columns exist: BaseAmount 100 as the ratio denominator,
CreditCheckFlag N, InUse N, PartialDiscountFlag N, PrepaymentFlag N,
and DiscountBasisDateType APPLICATION_DATE. For a create with one payment
line, also set FirstInstallmentCode to INCLUDE; for a create with no discount
rows, set CalcDiscountOnLinesFlag to Invoice Amount code I. Both entity
attributes are non-null even when their business behavior is not visible in a
simple Net term. Show every applied default in the preview. Never default
PrintingLeadDays or a split-term FirstInstallmentCode, CalcDiscountOnLinesFlag
when discounts exist, reference data set, language, billing cycle, or flexfield
context.
For update, never apply create defaults. Use the current exact export as the
source of truth, merge only fields and child rows explicitly requested, and
retain all other values. A requested base-description change is mirrored into
the current base-language translation row. The helper reports changed, added,
removed, and preserved state; any removed row is a blocker for this workflow.
Service-owned audit columns are the only baseline fields deliberately cleared
from update and end-date candidates; they are not writable business state.
Before writing any candidate row, canonicalize every metadata date value to
ISO YYYY-MM-DD and every dateTime value to ISO date-time. Fusion current
exports can contain slash-separated dates such as 2026/10/01; those values
are valid source evidence, but the Payment Terms CSV loader rejects them when
copied unchanged into an update or atomic-batch import candidate.
python pillars/erp/financials/customer-billing/manage-receivables-payment-terms/scripts/payment_terms_fsm_package.py preview --template <task-template.zip> --baseline <task-data-export.zip> --blueprint <request.json>
python pillars/erp/financials/customer-billing/manage-receivables-payment-terms/scripts/payment_terms_fsm_package.py build --template <task-template.zip> --baseline <task-data-export.zip> --blueprint <request.json> --output <candidate.zip>
python pillars/erp/financials/customer-billing/manage-receivables-payment-terms/scripts/payment_terms_fsm_package.py validate --package <candidate.zip> --baseline <task-data-export.zip> --blueprint <request.json>
python pillars/erp/financials/customer-billing/manage-receivables-payment-terms/scripts/payment_terms_fsm_package.py validate --source-evidence --package <task-template-or-current-data-export.zip>
python pillars/erp/financials/customer-billing/manage-receivables-payment-terms/scripts/payment_terms_fsm_package.py reconcile --candidate <submitted-candidate.zip> --export <fresh-successful-task-data-export.zip>
If required information is absent or ambiguous, return blocked with a single
business clarification and create no ZIP. If the design is complete but not
confirmed, return confirmation_required, show the business summary, and
create no ZIP. An offline success means only that
the candidate passed local package and task rules; it does not prove target
authorization, Fusion acceptance, process completion, or persisted state.
Completion and Evidence Contract
Keep submission, process completion, and persisted-state verification as
separate facts. Do not mark the implementation task complete unless all of the
following are true:
- Submitted bytes match the approved archive SHA-256.
- The external process reaches a successful terminal state.
- Failed rows are zero and warnings are either zero or explicitly accepted.
- Available process status, counts, logs, and diagnostics are retained by the owning workflow.
- A fresh read-only export finds the expected payment-term identity in the approved reference data set.
- Bundled
reconcile reports verified: persisted header, lines, translations, and discounts match the exact approved candidate, with any system-generated extra translation languages disclosed.
If any condition is false or unknown, report the last confirmed state, preserve
safe evidence, and give one next action. Never retry an import automatically.
Current Oracle Documentation
Use documentation for the target release. The following 26C sources were
verified accessible on 2026-08-12 and are the current authoring baseline; check
for and use a newer published release at runtime:
Core Data Loader remains the mandatory import orchestrator even when Oracle
documents the underlying setup-task CSV import service.
Registered Implementation Evidence
The CodeSearch baseline refreshed on 2026-08-12 establishes this ownership
chain:
AR_MANAGE_RECEIVABLES_PAYMENT_TERMS -> PaymentTermMainFlow -> manage/create
pages -> PaymentTermUIAM -> payment-term view/entity objects ->
RA_TERMS_* persistence.
The FSM business-object mapping covers AR_PAYMENT_TERM,
AR_PAYMENT_TERM_LINE, and AR_PAYMENT_TERM_DISCOUNT; the task export also
contains the translation child. Refresh the current accessible CodeSearch
series when behavior or exception coverage must be reconfirmed. Use the
registered FPHDEV series only as labeled fallback provenance, never as a fixed
runtime dependency.
Resource Read Order
- Input validation
- Dependency readiness
- Reference lookups
- Defaulting rules
- Design enforcement
- Error handling
- Generated rule registry
The task resource set follows the current v3 contract. Input collection,
spreadsheet/CSV processing, preview generation, approval, payload construction,
Fusion writes, monitoring, and loader diagnostics remain owned by routed
runbooks and Core Data Loader, not by task-local resource files.
Refusal Rules
- Do not invent a reference data set, billing cycle, language, flexfield context, template column, service route, or accepted value.
- Do not default a missing reference data set to
COMMON, ENTERPRISE, the first exported set, or the set used by a different environment.
- Do not turn a zero-match or many-match lookup into a candidate ZIP; ask one business-first clarification and retain the blocked rule result.
- Do not split a mixed or batch request into an unconfirmed partial package. Validate every operation, cap one package at 100 distinct targets, and require one design confirmation over the complete batch.
- Do not generate arbitrary names or values for a requested count of terms. Require an attached list or an explicit deterministic business pattern that previews every resulting term.
- Do not place two operations for the same Name and resolved reference data set in one batch; consolidate compatible changes or ask about conflicts.
- Do not create a new payment-term ZIP without one evidence-backed base/source language row.
- Do not generate an offline candidate before an orchestration-owned design confirmation bound to the unchanged preview design SHA-256 and source-package hashes.
- Do not strip, rename, or extend the internal
confirmation envelope between preview and build; only confirmed and design_sha256 are allowed, while import approval and execution metadata belong in the separate run record.
- Do not preview or build a split term until positive whole-number Print Lead Days and the tax/freight installment option are explicitly resolved.
- Do not hand off a candidate whose required header fields, current entity string precisions, child links, or discount line/percentage uniqueness have not passed the bundled executable validator.
- Do not hand off a candidate with a nonblank service-owned audit value in any Payment Terms CSV row, including update and end-date packages.
- Do not hand off a candidate containing an export-format slash-separated date. Preserve the semantic date but emit its ISO import-safe representation.
- Do not treat an update blueprint as a replacement. Preserve every unspecified exported field and child row, and reject a candidate that differs from the normalized blueprint plus baseline even when its ZIP and CSV structure are valid.
- Do not change a base description only in
AR_PAYMENT_TERM; mirror it into exactly one base-language AR_PAYMENT_TERM_TRANSLATION row and preserve non-base translations.
- Do not rename a payment term, move it to another reference data set, or delete an installment, translation, or discount by omission through this workflow.
- Do not upload a task-level Payment Terms ZIP from an offering-level or functional-area-level import page, and do not reuse a ZIP that previously failed or whose SHA-256 differs from the current handoff.
- Do not preview or build discounts until the discount basis is explicitly resolved, each discount is complete and unique, and no line has more than three discounts.
- Do not hide a known invalid value behind a missing-business-choice question. Report all offline-detectable value/range errors first, then ask only for still-relevant unresolved decisions.
- Do not build from template and baseline exports whose environment, Fusion release, metadata field contract, or CSV headers differ.
- Do not treat the orchestration-owned design confirmation as Core Data Loader candidate-specific approval, or Core Data Loader candidate-specific approval as permission to skip design confirmation.
- Do not treat a multi-task, functional-area, offering, failed, or stale export as an exact task-level build template.
- Do not use a direct payment-term REST write, SQL, UI automation, or a legacy task-local import route.
- Do not upload or initiate without a current Core Data Loader Task Hook envelope bound to the exact approved archive SHA-256.
- Do not reuse stale approval after any source, archive, environment, task identity, validation, or target change.
- Do not resubmit after a timeout, unknown outcome, or failed import; reconcile status first.
- Do not call the task complete on an accepted request or process status alone.
- Do not call the task complete until a fresh successful export passes the bundled candidate-to-persisted-state reconciliation.
Portability
Resolve repository, project, attachments, environment, release, request IDs,
and CodeSearch series at runtime. Recorded absolute paths, sandbox hostnames,
request IDs, and source revisions are provenance only. This skill requires no
laptop-specific path, credential, token, browser state, or fixed environment.
1---2skill_id: "erp.financials.customer-billing.manage-receivables-payment-terms"3name: manage-receivables-payment-terms-setup-task-guidance4description: "Handles natural-language Oracle Receivables payment-term requests, including one-term, mixed create/update/end-date, and batches of up to 100 distinct terms, plus export, validation, import, migration, monitoring, and verification. Resolves the catalog-backed FSM task, validates the four-entity PaymentTerm package, delegates every import to Core Data Loader, and verifies every persisted term without requiring customers to know task codes, CSV files, APIs, loaders, or database tables."5layer: "pillar"6pillar: "ERP"7offering: "Financials"8functional_area: "Customer Billing"9functional_area_code: "ORA_FIN_CUST_BILL"10task_code: "AR_MANAGE_RECEIVABLES_PAYMENT_TERMS"11task_name: "Manage Receivables Payment Terms"12parent_skill_id: "erp.financials.customer-billing"13available_flag: "Y"14export_import_supported_flag: "Y"15csv_export_import_supported_flag: "Y"16dataloader_import_mode: "FSM"17businessObject: ""18source_catalog: "knowledge/setup-task-catalog/effective/setupTasksAll.json"19type: "planning"20execution_mode: "assisted"21owner_team: "ERP financials pillar team"22version: "0.10.0"23inputs:24 - "implementation_objective"25 - "project_context"26 - "setup_task_scope"27 - "setup_data_artifacts"28outputs:29 - "setup_task_plan"30 - "setup_data_routing"31 - "validation_checkpoints"32 - "offline_package_review"33 - "skill_run_record"34 - "token_usage_record"35depends_on:36 - "shared.setup-export.task-level-export"37 - "shared.validation.setup-data-validator"38 - "shared.validation.reference-data-validator"39 - "core.data-loader"40uses_core:41 - "core.project-mgmt.artifact-version-manager"42 - "core.project-mgmt.artifact-registry-manager"43 - "core.project-mgmt.project-state-manager"44persists_project_state: true45token_usage_tracking:46 enabled: true47 granularity: "per_skill_run"48 artifact_type: "token_usage_record"49 default_location: "project/{project_id}/artifacts/shared/token-usage/current/token-usage-log.md"50 estimation_method: "chars/4 estimate unless exact tokenizer or API accounting is available"51 required_fields:52 - "activity_start_time"53 - "skill_id"54 - "task"55 - "trigger"56 - "artifacts_written"57 - "files_read"58 - "estimated_input_tokens"59 - "estimated_output_tokens"60 - "estimated_total_tokens"61 - "estimation_method"62 - "notes"63state_updates:64 - "setup_task_sequence"65 - "configuration_blueprints"66 - "validation_results"67 - "token_usage_records"68workspace_outputs:69 - artifact_type: "configuration_blueprint"70 default_location: "project/{project_id}/artifacts/pillars/erp/financials/customer-billing/manage-receivables-payment-terms/current/"71 versioning_policy: "major-new-version-minor-confirm-update"72 - artifact_type: "validation_result"73 default_location: "project/{project_id}/artifacts/pillars/erp/financials/customer-billing/manage-receivables-payment-terms/current/"74 versioning_policy: "major-new-version-minor-confirm-update"75 - artifact_type: "skill_run"76 default_location: "project/{project_id}/state/runs/"77 versioning_policy: "append-only"78 - artifact_type: "token_usage_record"79 default_location: "project/{project_id}/artifacts/shared/token-usage/current/token-usage-log.md"80 versioning_policy: "append-only"81applicability:82 industries:83 - "All"84 countries:85 - "All"86 fusion_releases:87 - "Current Oracle Fusion Cloud release"88side_effects:89 - "After Core Data Loader creates an immutable preview and the customer replies with the required standalone approval, the authorized FSM adapter may create, update, or end-date Receivables payment-term setup in the approved Fusion environment."90required_privileges:91 - "AR_SET_UP_RECEIVABLES_PAYMENT_TERM_PRIV or an equivalent seeded role for payment-term setup."92 - "AR_MANAGE_RECEIVABLES_PAYMENT_TERM_DATA or the equivalent reference-data-set data-security grant when enforced by the target environment."93 - "ORA_ASM_FUNCTIONAL_SETUPS_USER_ABSTRACT plus task-specific access for FSM CSV export and import."94 - "A reference-data-set data role that permits the intended payment-term set."95metadata:96 source: https://skillmd.com/skills/oracle/manage-receivables-payment-terms-setup-task-guidance97---9899<!-- fscr-supported-operations: create, update -->100<!-- fscr-create-fields: AR_PAYMENT_TERM::BaseAmount, AR_PAYMENT_TERM::CalcDiscountOnLinesFlag, AR_PAYMENT_TERM::CreditCheckFlag, AR_PAYMENT_TERM::CycleName, AR_PAYMENT_TERM::Description, AR_PAYMENT_TERM::DiscountBasisDateType, AR_PAYMENT_TERM::DueCutoffDay, AR_PAYMENT_TERM::EndDateActive, AR_PAYMENT_TERM::FirstInstallmentCode, AR_PAYMENT_TERM::InUse, AR_PAYMENT_TERM::Name, AR_PAYMENT_TERM::PartialDiscountFlag, AR_PAYMENT_TERM::PrepaymentFlag, AR_PAYMENT_TERM::PrintingLeadDays, AR_PAYMENT_TERM::SetCode, AR_PAYMENT_TERM::StartDateActive, AR_PAYMENT_TERM_DISCOUNT::AR_PAYMENT_TERM.Name, AR_PAYMENT_TERM_DISCOUNT::AR_PAYMENT_TERM.SetCode, AR_PAYMENT_TERM_DISCOUNT::AR_PAYMENT_TERM_LINE.SequenceNum, AR_PAYMENT_TERM_DISCOUNT::DiscountDate, AR_PAYMENT_TERM_DISCOUNT::DiscountDayOfMonth, AR_PAYMENT_TERM_DISCOUNT::DiscountDays, AR_PAYMENT_TERM_DISCOUNT::DiscountMonthsForward, AR_PAYMENT_TERM_DISCOUNT::DiscountPercent, AR_PAYMENT_TERM_DISCOUNT::SequenceNum, AR_PAYMENT_TERM_DISCOUNT::SetCode, AR_PAYMENT_TERM_LINE::AR_PAYMENT_TERM.Name, AR_PAYMENT_TERM_LINE::AR_PAYMENT_TERM.SetCode, AR_PAYMENT_TERM_LINE::DueDate, AR_PAYMENT_TERM_LINE::DueDayOfMonth, AR_PAYMENT_TERM_LINE::DueDays, AR_PAYMENT_TERM_LINE::DueMonthsForward, AR_PAYMENT_TERM_LINE::RelativeAmount, AR_PAYMENT_TERM_LINE::SequenceNum, AR_PAYMENT_TERM_LINE::SetCode, AR_PAYMENT_TERM_TRANSLATION::AR_PAYMENT_TERM.Name, AR_PAYMENT_TERM_TRANSLATION::AR_PAYMENT_TERM.SetCode, AR_PAYMENT_TERM_TRANSLATION::Description, AR_PAYMENT_TERM_TRANSLATION::Language, AR_PAYMENT_TERM_TRANSLATION::Name, AR_PAYMENT_TERM_TRANSLATION::SourceLang -->101<!-- fscr-update-fields: AR_PAYMENT_TERM::BaseAmount, AR_PAYMENT_TERM::CalcDiscountOnLinesFlag, AR_PAYMENT_TERM::CreditCheckFlag, AR_PAYMENT_TERM::CycleName, AR_PAYMENT_TERM::Description, AR_PAYMENT_TERM::DiscountBasisDateType, AR_PAYMENT_TERM::DueCutoffDay, AR_PAYMENT_TERM::EndDateActive, AR_PAYMENT_TERM::FirstInstallmentCode, AR_PAYMENT_TERM::InUse, AR_PAYMENT_TERM::PartialDiscountFlag, AR_PAYMENT_TERM::PrepaymentFlag, AR_PAYMENT_TERM::PrintingLeadDays, AR_PAYMENT_TERM::StartDateActive, AR_PAYMENT_TERM_DISCOUNT::DiscountDate, AR_PAYMENT_TERM_DISCOUNT::DiscountDayOfMonth, AR_PAYMENT_TERM_DISCOUNT::DiscountDays, AR_PAYMENT_TERM_DISCOUNT::DiscountMonthsForward, AR_PAYMENT_TERM_LINE::DueDate, AR_PAYMENT_TERM_LINE::DueDayOfMonth, AR_PAYMENT_TERM_LINE::DueDays, AR_PAYMENT_TERM_LINE::DueMonthsForward, AR_PAYMENT_TERM_LINE::RelativeAmount, AR_PAYMENT_TERM_TRANSLATION::Description, AR_PAYMENT_TERM_TRANSLATION::Name, AR_PAYMENT_TERM_TRANSLATION::SourceLang -->102103# Manage Receivables Payment Terms104105## Purpose106107Plan, validate, prepare or review an offline package, export, import, monitor,108and verify the catalog-backed `Manage Receivables Payment Terms` setup task109under Customer Billing. Resolve customer ambiguity from current evidence and110fail closed instead of inventing setup values.111112## Customer Interaction Contract113114A business-language request is sufficient. Do not ask the customer to name the115FSM task, CSV files, APIs, Data Loader, internal services, or database tables.116Infer those mechanics from this skill and the routed FDOS workflow.117118Examples of sufficient prompts include:119120- "Create a Net 30 payment term."121- "Create a term with 50 percent due in 30 days and 50 percent due in 60 days."122- "Update the discount on Net 10 to match this approved design."123- "End-date our legacy immediate payment term."124- "Import the attached approved payment terms into our test environment."125- "Check the Payment Terms load and verify it."126- "Create these 100 payment terms from the attached approved list."127- "Create the new Net 60 term and update the description of our existing Net 45 term."128129Ask only for unresolved business or authorization facts that materially change130the result: payment-term identity, reference data set, effective dates,131installments, print lead days for a split term, tax/freight installment option,132discount basis, discounts, balance-forward behavior, translations, flexfields,133target environment, or the required standalone approval.134135For an update, treat the exact existing `Name` plus resolved reference data set136as the immutable selector. Ask for the exact name when current evidence contains137zero or multiple candidates. Do not interpret a request to rename a term or move138it to another set as an in-place update; explain that this package workflow does139not support that identity change and ask whether the customer wants a separate140create/end-date design.141142## Ambiguity and Clarification Contract143144Never require a customer to know `SetCode`, CSV column names, FSM task codes, or145loader terminology. Accept business-language identities such as a reference146data set name, the business unit that must use the term, or a stated sharing147intent, and resolve them only through current target evidence.148149The normalized JSON blueprint used by the bundled helper is an internal150execution artifact. Never ask the customer to create, edit, or understand that151JSON. Translate every structured blocker returned by the helper into one clear152business question under the contract below.153154For every required identity or lookup-backed value, apply this exact contract:155156| Evidence result | Required behavior |157|---|---|158| One exact candidate | Use it, disclose the resolved business value and source, and continue. |159| No candidate | Stop before package preparation and ask one business-first question. Show the supplied value, explain why it is required, and provide current valid choices when available. |160| Multiple candidates | Stop before package preparation and ask the customer to choose. Show distinct display names and codes; never select the first, `COMMON`, `ENTERPRISE`, or a fuzzy match. |161| Missing or stale evidence | In live mode, route a fresh read-only export through the owning workflow. In offline mode, request the current artifact and make no external call. |162| Conflicting request and evidence | State the conflict and ask which business outcome is intended. Do not silently reinterpret create as update, change a set, or replace a date or schedule. |163164Ask one consolidated clarification at a time containing only the unresolved165business decisions. Offer a bounded list of current choices and say when more166choices are available. Re-run all affected rules after the reply; do not reuse167an earlier resolution after the target, artifact, request, or release changes.168169When one prompt contains several requested changes, normalize it as one170all-or-nothing locally validated batch of distinct Payment Term operations.171Support mixed create, update, and172end-date operations and up to 100 distinct `Name` plus resolved-set targets in173one task-scoped package. Do not invent missing names or expand an unspecified174"100 terms" request: accept an attached list or a customer-stated deterministic175name/value pattern, otherwise ask for the missing business design. Resolve and176validate every operation before preview; one unresolved or invalid operation177blocks the entire batch and no partial ZIP is created. If the prompt addresses178the same parent more than once, consolidate compatible changes into one179operation and show the result; if they conflict, ask which outcome is intended.180181For a create request, require one evidence-backed base language and a base182translation row before preview. When target evidence contains zero or multiple183possible languages and the customer did not specify one, ask which business184language to use and create no ZIP. Never treat an absent translation request as185permission to omit the base-language row.186187For a payment term with more than one schedule line, require a positive188whole-number Print Lead Days value and ask whether tax and freight should be189allocated across all installments or included in the first installment. Do not190infer either business choice from the term name, allocation percentages, or a191different environment. `FirstInstallmentCode` is mandatory on every header. For192a create with exactly one installment, use and disclose `INCLUDE`: the only193installment is also the first, so this does not change allocation behavior. For194multiple installments, always require the customer's explicit tax/freight195choice. `CalcDiscountOnLinesFlag` is also mandatory on every payment-term196header. When no discount rows are requested, use and disclose the product-backed197Invoice Amount value `I`; when discount rows are requested, require the198customer-selected discount basis. Use the product default Application Date only199for the discount basis date when the customer has not requested another200supported date basis.201202## Final Design Confirmation Contract203204Before generating an offline candidate ZIP, run the bundled `preview` command205and show one concise business summary containing the action, payment-term name,206reference data set, effective dates, base amount, every installment, discounts,207base/source language, print lead days, installment tax/freight option, discount208basis/date, partial-discount behavior, credit-check/prepayment flags, applied209defaults, and any balance-forward or flexfield behavior. State that BaseAmount210is the installment-ratio denominator, not a currency amount. Then ask the211governing orchestration to capture design confirmation.212213For updates, the preview must show a before/after change list, every added row,214and the number of unchanged fields preserved from the current export. Include215the base-language and additional-language descriptions in that preview. An216update preview that shows only the requested header values is incomplete.217218For a batch, show the operation count and action counts, then identify every219term by action, exact name, set, dates, and schedule. Show the full detailed220summary for every operation with nondefault flags, discounts, translations,221flexfields, or updates. Bind one orchestration-owned design confirmation to the complete batch222design; never confirm or build a successful subset while another operation is223blocked.224225Treat this as confirmation of the normalized local design only. It is not the226Core Data Loader candidate-specific approval required for a later Fusion import and does not authorize227authentication, upload, initiation, or any environment change. Do not infer228the orchestration-owned design confirmation from the original request, a reference-data-set answer, silence, or a229longer message. Bind the confirmation to the preview's design SHA-256 and both230source-package hashes. Any change to the request, resolved value, source ZIP,231blueprint, or target invalidates it and requires a new preview and confirmation.232Keep the archive-generation `confirmation` envelope in the normalized blueprint233when calling `build`; it is workflow metadata excluded from the business-design234hash, not a customer field. It must contain only `confirmed: true` and the exact235preview `design_sha256`. Never remove it before build, translate its snake-case236key to another spelling, or add approval, timestamp, user, or environment data237to that envelope. Store import approval and other execution metadata only in the238separate orchestration run record.239240## Setup Task Contract241242- Task code: `AR_MANAGE_RECEIVABLES_PAYMENT_TERMS`243- Catalog availability: `Y`244- Export/import support: `Y`245- CSV export/import support: `Y`246- Data Loader import mode: `FSM`247- Catalog: `knowledge/setup-task-catalog/effective/setupTasksAll.json`248249## Supported Scope250251| Customer request | Handling |252|---|---|253| Create | Build a new parent payment term and its applicable lines, translations, and discounts after exact-set duplicate checks. |254| Update | Preserve unchanged export-backed values and package only a supported, reviewed change. |255| End-date | Update the supported end-date field after current-state and date validation. |256| Mixed or batch request | Build one all-or-nothing task package for up to 100 distinct parent identities after every operation passes the same create/update/end-date rules. |257| Hard delete | Refuse; use an evidence-backed update or end-date when appropriate. |258| Export | Route through `shared.setup-export.task-level-export`. |259| Validate | Run shared setup/reference validation, then the compiled task-resource plan. |260| Import | Route only through `core.data-loader`; this task skill never chooses or calls an import endpoint or adapter. |261| Monitor | Route request-ID or data-set status and diagnostics through `core.data-loader`. |262| Verify | Run a fresh read-only task export and compare the persisted header, lines, translations, and discounts with the approved preview. |263| Offline prepare | Preview the normalized design, obtain the orchestration-owned design confirmation, then build a candidate ZIP only from an exact successful task-level template and current baseline using the bundled local helper; make no network call and do not treat design confirmation as import approval. |264| Offline review | Inspect an attached ZIP locally, report task scope, metadata, rows, relationships, rule results, and SHA-256, and stop without authentication, upload, or approval. |265266## Business Object Package267268Treat the PaymentTerm package as one parent-child unit in the order established269by the current target template and `ASM_SETUP_CSV_METADATA.xml`.270271| Role | CSV entity | Required business linkage |272|---|---|---|273| Header | `AR_PAYMENT_TERM` | `Name` plus `SetCode` |274| Installment schedule | `AR_PAYMENT_TERM_LINE` | Parent `Name` and `SetCode`, plus unique line `SequenceNum` |275| Translation | `AR_PAYMENT_TERM_TRANSLATION` | Parent identity plus supported `Language` and `SourceLang` |276| Discount schedule | `AR_PAYMENT_TERM_DISCOUNT` | Parent identity plus an existing payment-line sequence; child `SequenceNum` must equal the referenced line sequence, and DiscountPercent must be unique on that line |277278## Source-Backed Task Behavior279280- A payment term is one parent package containing a header, at least one281 installment line, the required base-language translation, and any applicable282 discount rows. The parent identity is the exact `Name` plus `SetCode`.283 Sources: SRC-FSM-PACKAGE, SRC-INTERNAL-DEV-001.284- `BaseAmount` is the installment-ratio denominator, not a currency amount. The285 relative amounts of all installment lines must add exactly to that base286 amount; one unresolved or invalid line blocks the complete parent operation.287 Sources: SRC-FSM-PACKAGE, SRC-INTERNAL-DEV-001.288- Each installment line has a stable positive `SequenceNum` and must use one289 complete supported due-date method. A split term requires an explicit290 positive whole-number Print Lead Days value and an explicit tax-and-freight291 allocation choice before preview.292 Sources: SRC-FSM-PACKAGE, SRC-INTERNAL-DEV-001.293- A discount belongs to an existing installment line. Its `SequenceNum` must294 equal that line sequence, its percentage must be unique on the line, and no295 line may contain more than three discount rows.296 Sources: SRC-FSM-PACKAGE, SRC-INTERNAL-DEV-001.297- A create must include exactly one evidence-backed base-language translation298 where `Language` equals `SourceLang`. Updating the base description changes299 both the header and that base translation while preserving every unrequested300 non-base translation.301 Sources: SRC-FSM-PACKAGE, SRC-INTERNAL-DEV-001.302- Create, update, and end-date operations may be combined in one all-or-nothing303 task package for distinct parent identities. A duplicate target, conflicting304 operation, unresolved prerequisite, or invalid row blocks the entire package;305 no partial candidate is generated.306 Sources: SRC-FSM-PACKAGE, SRC-INTERNAL-DEV-001.307- An update is a patch against exactly one current exported parent. Preserve308 every unspecified supported header value and child row. `Name` and `SetCode`309 are immutable, and omission is not a supported request to delete a line,310 translation, discount, or parent.311 Sources: SRC-FSM-PACKAGE, SRC-INTERNAL-DEV-001.312- `LastUpdateDate`, `LastUpdatedBy`, `CreationDate`, `CreatedBy`, and313 `LastUpdateLogin` are service-owned. Keep them only as read-only baseline314 evidence and emit them blank in every generated import row.315 Sources: SRC-FSM-PACKAGE, SRC-INTERNAL-DEV-001.316- Build only from a successful exact-task template and current export whose317 environment, Fusion release, entity paths, CSV headers, and metadata agree.318 A broader offering or functional-area archive is review evidence, not a319 Payment Terms import template.320 Source: SRC-FSM-PACKAGE.321322## Update Mutation Contract323324An update blueprint is a patch against exactly one current exported parent, not325a replacement document. Preserve every unspecified supported header field and326every unspecified line, translation, and discount row. Patch children only by327their stable import identity: payment line `SequenceNum`, translation328`Language`, and discount parent-line sequence plus `DiscountPercent`.329330`Name` and `SetCode` identify the parent for this workflow and are not mutable331update fields. Omitting a child row never means delete: Fusion CSV import does332not provide a safe generic delete-by-omission contract. Refuse requests to333remove an installment, translation, or discount, contract a schedule by334omission, rename a term, or move it between sets. Offer a separately reviewed335create/end-date or supported product workflow instead.336337`Description` is translatable. When the customer changes the base description,338write the same value to the header and the one current base-language translation339row where `Language` equals `SourceLang`; preserve every non-base translation340unless it was explicitly supplied. If the base row is missing or ambiguous,341stop before preview and request fresh evidence or a business-language choice.342Reject conflicting header and base-translation descriptions. A structurally343valid ZIP is not sufficient unless its complete rows exactly match the344normalized request plus the preserved baseline state.345346Never invent columns, audit values, lookup codes, package order, or metadata.347Treat `LastUpdateDate`, `LastUpdatedBy`, `CreationDate`, `CreatedBy`, and348`LastUpdateLogin` as service-owned evidence on every create, update, and349end-date import candidate. Preserve them in the read-only baseline for350diagnosis, but emit them blank in every candidate row.351Derive them from the current target template/data export. Never write directly352to `RA_TERMS_B`, `RA_TERMS_TL`, `RA_TERMS_LINES`, or353`RA_TERMS_LINES_DISCOUNTS`.354355Treat current metadata as an executable contract: compare every CSV header to356its declared `XmlAttributeList`/`XmlAttributeTypeList`, and require template and357baseline environment, release, entity contract, and CSV headers to match. Do358not build from mixed-pod or mixed-release exports.359360A task-level build template must contain exactly one361`ASM_SETUP_CSV_METADATA.xml`, declare only the Payment Terms entities, and have362a successful completed process status. Accept either of Fusion's exact363task-export identity shapes: one explicit migration task definition with only364`AR_MANAGE_RECEIVABLES_PAYMENT_TERMS` selected, or no task-definition rows and365the top-level `ObjectShortName` equal to that task code with `ObjectType` equal366to `TASK`. A broader functional-area or offering package may be reviewed as a367multi-task package, but this task skill must not rewrite its metadata, extract368it into a new import package, or present it as a task-level Payment Terms369archive.370371## Routed Workflow3723731. Start through `router/implementation-router/SKILL.md` and select the active project and target environment.3742. Normalize the business request. Resolve each required identity by the ambiguity contract and ask only one consolidated business clarification when evidence cannot prove one result.3753. Determine the requested mode. For offline preparation or review, use only supplied local artifacts. Otherwise export the current task template and, when existing-state comparison is needed, current task data through `shared.setup-export.task-level-export`.3764. Run `shared.validation.setup-data-validator` and `shared.validation.reference-data-validator`.3775. Compile and plan the task-local rules, then evaluate the six resources in the order listed below. Execute every known product constraint in the local validator; a message listed only in documentation is not considered covered.3786. For offline preparation, first run `validate --source-evidence` on both the exact task-level template and current baseline export. This checks their archive, metadata, task scope, status, CSV presence, and source row counts without applying new-candidate rules to pre-existing target rows. Resolve the create base language and all other ambiguity, then run `preview` with the normalized blueprint. Show its complete business summary, including update deltas and translated descriptions, and ask for the orchestration-owned design confirmation; create no ZIP yet. After that exact reply, record the returned design SHA-256 in the internal blueprint confirmation and use `build`. The helper must reject missing or stale confirmation, independently validate the candidate against the current baseline and normalized blueprint, and repeat generation to prove an identical SHA-256. For review of a proposed import package, run `validate`; when a baseline and blueprint are available, both are mandatory so semantic intent is checked rather than ZIP structure alone. These commands are local and never authorize a Fusion write.3797. Treat the build result's `uploadHandoff` as a mandatory human/tool handoff. Confirm the filename and SHA-256, target environment and release, and exact task name/code. Never reuse a ZIP from a failed run or choose a similarly named file. If a person performs the upload, they must open the exact `Manage Receivables Payment Terms` task and use its `Import from CSV File` action; an offering-level or functional-area-level import page will reject this task-scoped archive.3808. For an intended import, hand the exact task context and validated candidate to `core.data-loader`. Core Data Loader owns final immutable archive preparation, Task Hook validation, preview, archive SHA-256 binding, execution routing, upload, and initiation.3819. Stop after the immutable preview and hand the immutable candidate to Core Data Loader for its candidate-specific approval. Do not infer approval from the original request or a longer message.38210. On that separate approval, let Core Data Loader revalidate and submit the unchanged archive once. Do not select a task-local fallback or reconstruct the validation envelope.38311. Treat successful initiation as accepted, not as verified setup. For a later generic status request, let Core Data Loader retrieve status, counts, errors, and available logs without resubmitting.38412. After successful terminal processing, perform a fresh read-only task export and run the bundled `reconcile` comparison against the exact submitted candidate. Mark the setup verified only when every expected header, line, base/additional translation, and discount value matches. System-generated extra translation languages may be reported separately; unexpected extra schedule or discount rows remain mismatches.385386## Portable Offline Package Workflow387388The bundled helper uses only the Python standard library and repository-relative389paths. It reads ZIP/CSV/XML artifacts locally and never reads environment390properties, credentials, tokens, browser state, or laptop-specific paths.391392Use the legacy normalized JSON shape with `action`, `header`, `lines`,393`translations`, and `discounts` for one operation. For more than one operation,394use `operations`, where each item contains `operation_id`, `action`, `header`,395`lines`, `translations`, and `discounts`. Never mix the two shapes. Both shapes396may include optional current `evidence` for reference data397sets, billing cycles, the partial-payment system option, languages, or398flexfield contexts, and an internal archive-generation `confirmation` added399only after standalone customer confirmation. Reference-data-set evidence may prove a valid empty set400that has no Payment Terms rows in the current task export.401 Preserve only template-supported fields. For descriptive flexfields, require402 both the exact current target context and the exact template attribute columns403 proven for that context; context existence alone does not authorize any404 `Attribute1` through `Attribute15` value. Derive evidence only from the routed405current exports; never ask a customer to fabricate technical evidence. For406update or end-date, supply the current baseline so unchanged export-backed407values are retained.408409The helper accepts at most 100 operations, requires a unique `operation_id` and410resolved `Name` plus `SetCode` target for each, combines the four entity CSVs only after all411operations pass, and binds confirmation and deterministic generation to the412entire combined row set. A batch failure reports the operation index and ID.413This is an all-or-nothing local validation and generation guarantee, not a414claim that Fusion import processing is one database transaction. Never hand-edit415a partial batch after validation, and always reconcile every operation after416live processing, including after a failed process that might have persisted a417subset.418419For create, apply only these product-backed non-business defaults when their420template columns exist: BaseAmount `100` as the ratio denominator,421CreditCheckFlag `N`, InUse `N`, PartialDiscountFlag `N`, PrepaymentFlag `N`,422and DiscountBasisDateType `APPLICATION_DATE`. For a create with one payment423line, also set FirstInstallmentCode to `INCLUDE`; for a create with no discount424rows, set CalcDiscountOnLinesFlag to Invoice Amount code `I`. Both entity425attributes are non-null even when their business behavior is not visible in a426simple Net term. Show every applied default in the preview. Never default427PrintingLeadDays or a split-term FirstInstallmentCode, CalcDiscountOnLinesFlag428when discounts exist, reference data set, language, billing cycle, or flexfield429context.430431For update, never apply create defaults. Use the current exact export as the432source of truth, merge only fields and child rows explicitly requested, and433retain all other values. A requested base-description change is mirrored into434the current base-language translation row. The helper reports changed, added,435removed, and preserved state; any removed row is a blocker for this workflow.436Service-owned audit columns are the only baseline fields deliberately cleared437from update and end-date candidates; they are not writable business state.438Before writing any candidate row, canonicalize every metadata `date` value to439ISO `YYYY-MM-DD` and every `dateTime` value to ISO date-time. Fusion current440exports can contain slash-separated dates such as `2026/10/01`; those values441are valid source evidence, but the Payment Terms CSV loader rejects them when442copied unchanged into an update or atomic-batch import candidate.443444```text445python pillars/erp/financials/customer-billing/manage-receivables-payment-terms/scripts/payment_terms_fsm_package.py preview --template <task-template.zip> --baseline <task-data-export.zip> --blueprint <request.json>446python pillars/erp/financials/customer-billing/manage-receivables-payment-terms/scripts/payment_terms_fsm_package.py build --template <task-template.zip> --baseline <task-data-export.zip> --blueprint <request.json> --output <candidate.zip>447python pillars/erp/financials/customer-billing/manage-receivables-payment-terms/scripts/payment_terms_fsm_package.py validate --package <candidate.zip> --baseline <task-data-export.zip> --blueprint <request.json>448python pillars/erp/financials/customer-billing/manage-receivables-payment-terms/scripts/payment_terms_fsm_package.py validate --source-evidence --package <task-template-or-current-data-export.zip>449python pillars/erp/financials/customer-billing/manage-receivables-payment-terms/scripts/payment_terms_fsm_package.py reconcile --candidate <submitted-candidate.zip> --export <fresh-successful-task-data-export.zip>450```451452If required information is absent or ambiguous, return `blocked` with a single453business clarification and create no ZIP. If the design is complete but not454confirmed, return `confirmation_required`, show the business summary, and455create no ZIP. An offline success means only that456the candidate passed local package and task rules; it does not prove target457authorization, Fusion acceptance, process completion, or persisted state.458459## Completion and Evidence Contract460461Keep submission, process completion, and persisted-state verification as462separate facts. Do not mark the implementation task complete unless all of the463following are true:4644651. Submitted bytes match the approved archive SHA-256.4662. The external process reaches a successful terminal state.4673. Failed rows are zero and warnings are either zero or explicitly accepted.4684. Available process status, counts, logs, and diagnostics are retained by the owning workflow.4695. A fresh read-only export finds the expected payment-term identity in the approved reference data set.4706. Bundled `reconcile` reports `verified`: persisted header, lines, translations, and discounts match the exact approved candidate, with any system-generated extra translation languages disclosed.471472If any condition is false or unknown, report the last confirmed state, preserve473safe evidence, and give one next action. Never retry an import automatically.474475## Current Oracle Documentation476477Use documentation for the target release. The following 26C sources were478verified accessible on 2026-08-12 and are the current authoring baseline; check479for and use a newer published release at runtime:480481- [Guidelines for Defining Payment Terms](https://docs.oracle.com/en/cloud/saas/financials/26c/fairp/guidelines-for-defining-payment-terms.html)482- [Payment Terms and Reference Data Sharing](https://docs.oracle.com/en/cloud/saas/financials/26c/faipp/payment-terms-and-reference-data-sharing.html)483- [Receivables Payment Terms service data object](https://docs.oracle.com/en/cloud/saas/financials/26c/oeswf/receivablespaymentterms-d16553e75248.html)484- [Receivables Payment Terms Translation service data object](https://docs.oracle.com/en/cloud/saas/financials/26c/oeswf/receivablespaymenttermstranslation-d16553e74819.html)485- [Receivables Payment Schedule Discount service data object](https://docs.oracle.com/en/cloud/saas/financials/26c/oeswf/receivablespaymentschedulediscount-d16553e75707.html)486- [Export and Import of CSV File Packages](https://docs.oracle.com/en/cloud/saas/applications-common/26c/oafsm/export-and-import-of-csv-file-packages.html)487- [Setup Task CSV Exports REST endpoints](https://docs.oracle.com/en/cloud/saas/applications-common/26c/farca/api-setup-task-csv-exports.html)488489Core Data Loader remains the mandatory import orchestrator even when Oracle490documents the underlying setup-task CSV import service.491492## Registered Implementation Evidence493494The CodeSearch baseline refreshed on 2026-08-12 establishes this ownership495chain:496497`AR_MANAGE_RECEIVABLES_PAYMENT_TERMS` -> `PaymentTermMainFlow` -> manage/create498pages -> `PaymentTermUIAM` -> payment-term view/entity objects ->499`RA_TERMS_*` persistence.500501The FSM business-object mapping covers `AR_PAYMENT_TERM`,502`AR_PAYMENT_TERM_LINE`, and `AR_PAYMENT_TERM_DISCOUNT`; the task export also503contains the translation child. Refresh the current accessible CodeSearch504series when behavior or exception coverage must be reconfirmed. Use the505registered FPHDEV series only as labeled fallback provenance, never as a fixed506runtime dependency.507508## Resource Read Order5095101. [Input validation](ora-resource/ora_input_validation.md)5112. [Dependency readiness](ora-resource/ora_dependency_readiness.md)5123. [Reference lookups](ora-resource/ora_reference_lookups.md)5134. [Defaulting rules](ora-resource/ora_defaulting_rules.md)5145. [Design enforcement](ora-resource/ora_design_enforcement.md)5156. [Error handling](ora-resource/ora_error_handling.md)5167. Generated [rule registry](ora-resource/ora_rule_registry.json)517518The task resource set follows the current v3 contract. Input collection,519spreadsheet/CSV processing, preview generation, approval, payload construction,520Fusion writes, monitoring, and loader diagnostics remain owned by routed521runbooks and Core Data Loader, not by task-local resource files.522523## Refusal Rules524525- Do not invent a reference data set, billing cycle, language, flexfield context, template column, service route, or accepted value.526- Do not default a missing reference data set to `COMMON`, `ENTERPRISE`, the first exported set, or the set used by a different environment.527- Do not turn a zero-match or many-match lookup into a candidate ZIP; ask one business-first clarification and retain the blocked rule result.528- Do not split a mixed or batch request into an unconfirmed partial package. Validate every operation, cap one package at 100 distinct targets, and require one design confirmation over the complete batch.529- Do not generate arbitrary names or values for a requested count of terms. Require an attached list or an explicit deterministic business pattern that previews every resulting term.530- Do not place two operations for the same Name and resolved reference data set in one batch; consolidate compatible changes or ask about conflicts.531- Do not create a new payment-term ZIP without one evidence-backed base/source language row.532- Do not generate an offline candidate before an orchestration-owned design confirmation bound to the unchanged preview design SHA-256 and source-package hashes.533- Do not strip, rename, or extend the internal `confirmation` envelope between preview and build; only `confirmed` and `design_sha256` are allowed, while import approval and execution metadata belong in the separate run record.534- Do not preview or build a split term until positive whole-number Print Lead Days and the tax/freight installment option are explicitly resolved.535- Do not hand off a candidate whose required header fields, current entity string precisions, child links, or discount line/percentage uniqueness have not passed the bundled executable validator.536- Do not hand off a candidate with a nonblank service-owned audit value in any Payment Terms CSV row, including update and end-date packages.537- Do not hand off a candidate containing an export-format slash-separated date. Preserve the semantic date but emit its ISO import-safe representation.538- Do not treat an update blueprint as a replacement. Preserve every unspecified exported field and child row, and reject a candidate that differs from the normalized blueprint plus baseline even when its ZIP and CSV structure are valid.539- Do not change a base description only in `AR_PAYMENT_TERM`; mirror it into exactly one base-language `AR_PAYMENT_TERM_TRANSLATION` row and preserve non-base translations.540- Do not rename a payment term, move it to another reference data set, or delete an installment, translation, or discount by omission through this workflow.541- Do not upload a task-level Payment Terms ZIP from an offering-level or functional-area-level import page, and do not reuse a ZIP that previously failed or whose SHA-256 differs from the current handoff.542- Do not preview or build discounts until the discount basis is explicitly resolved, each discount is complete and unique, and no line has more than three discounts.543- Do not hide a known invalid value behind a missing-business-choice question. Report all offline-detectable value/range errors first, then ask only for still-relevant unresolved decisions.544- Do not build from template and baseline exports whose environment, Fusion release, metadata field contract, or CSV headers differ.545- Do not treat the orchestration-owned design confirmation as Core Data Loader candidate-specific approval, or Core Data Loader candidate-specific approval as permission to skip design confirmation.546- Do not treat a multi-task, functional-area, offering, failed, or stale export as an exact task-level build template.547- Do not use a direct payment-term REST write, SQL, UI automation, or a legacy task-local import route.548- Do not upload or initiate without a current Core Data Loader Task Hook envelope bound to the exact approved archive SHA-256.549- Do not reuse stale approval after any source, archive, environment, task identity, validation, or target change.550- Do not resubmit after a timeout, unknown outcome, or failed import; reconcile status first.551- Do not call the task complete on an accepted request or process status alone.552- Do not call the task complete until a fresh successful export passes the bundled candidate-to-persisted-state reconciliation.553554## Portability555556Resolve repository, project, attachments, environment, release, request IDs,557and CodeSearch series at runtime. Recorded absolute paths, sandbox hostnames,558request IDs, and source revisions are provenance only. This skill requires no559laptop-specific path, credential, token, browser state, or fixed environment.