Customer Billing Implementation Guidance
Purpose
Provides ERP Financials implementation guidance for the Customer Billing functional area.
When to Use
Use this functional-area skill after Financials scope is confirmed and the project needs customer billing setup planning, baseline export, import sequencing, or validation checkpoints.
Catalog Metadata
- Pillar:
ERP - Offering:
Financials(XLE_FINANCIALS_JUR) - Functional area / Setup Object:
Customer Billing(ORA_FIN_CUST_BILL)
Setup Tasks
- Manage Transaction Types (
AR_MANAGE_TRANSACTION_TYPES) - Manage Transaction Sources (
AR_MANAGE_TRANSACTION_SOURCES) - Manage AutoInvoice Grouping Rules (
AR_MANAGE_AUTOINVOICE_GROUPING_RULES) - Manage Receivables Payment Terms (
AR_MANAGE_RECEIVABLES_PAYMENT_TERMS) - Manage Remit to Addresses (
AR_MANAGE_REMIT_TO_ADDRESSES) - Manage AutoAccounting Rules (
AR_MANAGE_AUTOACCOUNTING_RULES)
Customer Natural-Language Routing
Route business-language requests about customer payment terms to the nested Manage Receivables Payment Terms skill. Route business-language requests about remittance destinations and their receipt-from coverage to the nested Manage Remit to Addresses skill. Route business-language requests about Receivables default account derivation and AutoAccounting segment sources to the nested Manage AutoAccounting Rules skill. The customer does not need to know FSM task codes, CSV entity names, Data Loader, setup export/import services, or physical tables.
Examples include:
- "Create a Net 30 payment term."
- "Make half due in 30 days and half due in 60 days."
- "End-date our legacy immediate payment term."
- "Move these approved payment terms into our test environment."
- "Check whether the payment terms load completed correctly."
- "Create a remit-to address for our California receipts."
- "Add a new receipt-from postal-code range to an existing remit-to address."
- "Derive the receivable account company segment from the transaction type."
- "Use a constant for the unearned revenue account segment."
Inputs
implementation_objectiveproject_contextcustomer_billing_scopecustomer_billing_requirements
Outputs
functional_area_setup_planconfiguration_guidancevalidation_checkpointsskill_run_recordtoken_usage_record
Implementation Notes
Use the generated nested setup-task skills for task-level planning, sequencing, setup-data routing, and validation. Track token usage for any generated project artifact or skill-run record using the manifest policy. When a request actively includes Manage Transaction Sources and another setup task, name the separate task scopes and ask the implementor to confirm those scopes and which task to prepare first. Stop before task preparation until that scope decision is answered; field-level details alone do not establish scope confirmation. If the implementor already explicitly limits the request to Manage Transaction Sources, treat other tasks in an attached document as context and do not reopen the excluded scope.