How Can You Get the Best Results from Payments Agent?
Payments Agent works best when prompts include clear business context and are aligned with the assistant capability being used.
Use the following guidelines to improve the relevance of responses and streamline your interactions with Payments Agent.
| Area | Guidance | Example |
| Getting started | Begin by reviewing Insights, selecting a Suggested Prompt, or entering a natural language request in the Ask Oracle bar. Suggested Prompts help you quickly start common payment activities. | Select a Suggested Prompt such as "Show PPRs requiring attention" to begin investigating payment execution issues. |
| Scope | Payments Agent returns a limited set of records optimized for conversational review. Include additional filters to narrow the results and focus the analysis. | Instead of: "Show payment runs" use: "Show PPRs requiring attention for Vision Operations in USD." |
| Review and export larger result sets | Payments Agent displays a limited number of records in the conversational response. When additional records are available, open the results in Canvas view for a more comprehensive review. Use Export to Excel when you need the complete filtered population for offline analysis or sharing. |
“Show payments rejected or failed this month for Vision Operations.” Expand the result in Canvas, and use Export to Excel when you need the complete filtered population. |
| Prompt format | Use quotation marks for multi-word business values when referencing Business Units, suppliers, templates, or payment process requests. | "Show payment outflow for Business Unit 'Vision Operations' in USD for the next 6 weeks." |
| One request at a time | Ask about one thing per message. Requests that mix different objects, contain conflicting filters, or combine supported and unsupported requests may require clarification rather than being partially answered. | Ask for payment files, then ask for payments, rather than requesting both in one message. |
| Payment Options inputs | Payment optimization analysis works best when both Business Unit and currency are provided. | "What financing programs are available for evaluating upcoming payments for USD and Vision Operations business unit?" |
| Analysis horizon | If no time horizon is specified, Payment Options analysis defaults to 6 weeks. You can select a different horizon to meet your analysis needs. Specify the time horizon explicitly when you need a different analysis period. | "Show payment outflow for Vision Operations in USD for the next 9 weeks." |
| Payment Execution review | Payment Execution results may include information from both payment process requests and payment files. Use filters and related status details when investigating operational issues. | "Show payment files pending acknowledgment." or "Show PPRs requiring attention." |
| Failure analysis | After identifying a failed payment run or payment file, ask the Payment Execution Assistant why it failed. The assistant can analyze the underlying scheduled-process execution evidence and explain the failure instead of requiring you to review the logs directly. | “Why did payment process request PPR-10025 fail?” |
| Insight drilldown | Insights provide a starting point for investigation. If additional detail is required, continue the analysis in the appropriate assistant using more specific filters and queries. | After opening a Payments rejected or failed insight, ask: "Show payments rejected or failed this month for Vision Operations." |
| Offer review | Always review the offer preview before confirming. The assistant acts on the offers presented in the preview, so verify the supplier, amount, rate, terms, and recipient before confirmation. | Review the offer details before entering “Confirm.” |
| Sending offers | When both shortlisted offers and suppliers with newly eligible invoices are presented, specify which population you want to send. | Use “Send shortlisted offers” instead of the less-specific “Send offers.” |
| Virtual Card offers | Confirm the payment instrument alias and proposed payment terms for each supplier before creating an offer, particularly when more than one card arrangement qualifies. Include the Business Unit and currency when filtering Virtual Card offers by payment instrument alias. | “Change the payment term to Net 15 for Supplier A” before confirming the offer. |
| Program candidates | Add suppliers as financing program candidates from the analysis that identified the opportunity so that the candidate information reflects the opportunity you reviewed. | “Add these suppliers to the Global Discount Program at the program default rate.” |
| Standing enrollments | Specify the rate and effective date when creating or changing a standing enrollment, and review each supplier site in the preview before confirming. | “Change the standing-offer APR for Supplier A to 8.75% starting 1 November.” |
| Remittance advice | Provide the payment file reference and, when the default format isn't appropriate, specify the remittance advice format. | “Send separate remittance advice for payment file 41677 using format [Format Name].” |
| Confirmation language | The assistant interprets confirmation within the context of the current action. Respond clearly to the confirmation request displayed by the assistant. | Use a clear response that confirms the action shown in the current confirmation request. |