Required Roles and Access

Payments Agent uses Oracle Fusion Cloud Financials security roles, permission groups, and business unit data access controls to manage administrative and runtime access.

The following roles are typically required to implement and use Payments Agent.

Role	Role Code	Purpose
Application Implementation Consultant	ORA_ASM_APPLICATION_IMPLEMENTATION_CONSULTANT_JOB	Configures Payments Agent features, profile options, lookups, financing programs, business unit access, and scheduled processes.
Security Manager	ORA_FND_IT_SECURITY_MANAGER_JOB	Creates custom roles, enables permission groups, assigns users, and manages security configurations.
Payment Specialist	ORA_AP_PAYMENT_SPECIALIST_JOB	Primary runtime role for Payments Agent users. Provides access to payment execution, payment optimization, and supplier offer management capabilities.
Financials Intelligent Agent Administrator Duty	ORA_DR_FAI_GENERATIVE_AI_AGENT_FIN_ADMINISTRATOR_DUTY	Grants administrative access required to manage Payments Agent configurations and financing program intelligence documents in AI Agent Studio.
Payment Program Manager (custom job role)	Customer-defined	Provides access to the Buyer Onboarding Assistant. Your administrator must create this job role and add the Buyer Assistant Management Duty (ORA_AP_BUYER_ASSISTANT_MANAGEMENT_DUTY).

Business Unit Data Access

In addition to role assignments, grant users access to the appropriate business units using the Manage Data Access for Users task. Payments Agent enforces Oracle Fusion Cloud Financials business unit security. Users can access only the payment, supplier, and financing data associated with their assigned business units.

Users who access the Buyer Onboarding Assistant also require the appropriate business unit data access.

After assigning business unit access, run the Process Permission Group Policies action to synchronize data access policies and ensure that Payments Agent applies the appropriate business unit security controls.