SoftTech AI Registry
Oracle · Oracle Fusion Cloud Receivables

Cash Processing Agent for Receipt Processing and Cash Application

Oracle's conversational Cash Processing Agent surfaces receipt creation and cash application exceptions in Oracle Fusion Cloud Receivables, lets users investigate unidentified and unapplied receipts, remittances, open invoices, disputes and promises to pay in natural language, and applies a receipt to an invoice after receiving explicit user confirmation.

Recorded characteristics

Function
Oracle documents (Update 26C) a conversational agent with two contexts. The Receipts context covers receipt exploration and receipt creation exceptions for Bank Statement and Lockbox and supports resolving remittance advice data after ingestion. The Cash Application context covers unidentified and unapplied receipt investigation, open invoices, open promise-to-pay commitments, remittance information review, and "the user-confirmed Apply Receipt flow". Documented runtime chain: bank statement / lockbox / remittance data already ingested and receipts created by earlier, separately documented automation -> the user opens the Cash Processing Agent from its navigation menu entry -> Overview page insights (refreshed every four hours) or predefined/natural-language prompts surface receipt creation exceptions, unidentified receipts and unapplied receipts -> the user asks natural-language questions and the agent retrieves supporting receipt, customer, remittance, invoice, dispute and promise-to-pay context while maintaining conversational context -> the agent gives "context-aware recommendations for the next best actions to support further review and cash application" -> the user confirms -> "The agent applies the receipt to an invoice after receiving user confirmation." For receipt creation exceptions the agent does not itself correct data: it provides "a direct link to the correction flow", where the user searches the batch, enters the valid missing value and submits the correction job through spreadsheet upload. Cash application here means the Receivables accounting application of an existing receipt to an invoice, producing a receipt application against the transaction; it is not a bank transfer, payment execution, refund or money movement. Oracle states that existing Receivables validations, authorizations, segregation-of-duties controls and audit requirements are enforced for all actions performed through the agent.
Data access
Documented access, as of Update 26C: bank, source document, statement line, remittance reference, receipt method and exception reason; document-level processing status and exception summaries; source file, impacted amount; receipt source information such as payment channel, bank, originator name and wire number; unmatched remittances filtered by amount, date, currency or customer; open invoices including whether any are in dispute; open or past promise-to-pay commitments; receipt activity including previous applications, partial applications and unapplied receipts; receipt creation exception, unidentified receipt and unapplied receipt insights. Oracle states access is governed by Receivables assistant duty roles, permission groups and the user's data security access; no unrestricted financial-record access is documented.
Actions
Can take actions
External actions
No
Human confirmation
Required
Permission basis
User permissions
Administrative control
Documented controls: the agent is enabled by default, but security access must be configured before users can reach it from the new navigation menu entry. Administrators edit the applicable Receivables job role in Security Console and turn on Enable Permission Groups; for custom job roles they add the Cash Receipt Generation Assistant (ORA_AR_CASH_RECEIPT_GENERATION_ASSISTANT_DUTY), Cash Application Assistant (ORA_AR_CASH_APPLICATION_ASSISTANT_DUTY) and Cash Receipts Inquiry Assistant (ORA_AR_CASH_RECEIPTS_INQUIRY_ASSISTANT_DUTY) under both Roles and Privileges and Roles and Permission Groups, and add Cash Processing Agent Insights (ORA_AR_CASH_PROCESSING_INSIGHTS_DUTY) for insights; Oracle-provided predefined Receivables job roles (Accounts Receivable Specialist / Specialist Segregated Role / Manager / Manager Segregated Role) already include the required assistant roles once permission groups are enabled. Administrators must ensure appropriate user and data security access, and run Import User and Role Application Security Data and Retrieve Latest LDAP Changes. Apply Receipt specifically is controlled by the Cash Application Assistant role and AR_CASH_APPLICATION_INTENT_PRIV. Separate controls documented for upstream, non-agent automation: Manage Bank Accounts > Controls > Create Receipts from Bank Statement, Receipt Creation Start Date, Default Receipt Method, Manage Receipt Classes and Methods, email-forwarding rules to the provisioned pod email address for remittance advice, and scheduling Apply Receipts Using AutoMatch with Include Remittance set to Yes.
Default state
Conditional
Availability
Documented for Oracle Fusion Cloud Financials Update 26C, which as of the 2026-09-21 verification date is the current quarterly update rolling out by cohort. Oracle's 26C Feature Summary lists the feature as an AI agent with impact "None" and Action to Enable "Setup Required", while the 26C feature documentation states "The Cash Processing Agent is enabled by default" and requires only the described security access configuration. Oracle's ERP features-with-AI list records "Cash Processing Agent for Receipt Processing and Cash Application" as Update 26C and a further "Cash Processing Agent for receipt processing and cash application" entry as Update 26D.
Licensing
Not separately established. Oracle documents the agent as part of Oracle Fusion Cloud Financials / Receivables; no separate licence, add-on or SKU is stated in the reviewed documentation.
External model or provider
Not established. Oracle does not identify a model or provider specifically for the Cash Processing Agent in the reviewed documentation; generic AI Agent Studio model options were not imported.
Limitations and uncertainty
Temporal boundary: Oracle's 26D documentation describes additional authority - applying receipts in full or for a specified amount, applying one receipt across multiple selected transactions, assigning a customer to an unidentified receipt, and refunding eligible unapplied receipt amounts, plus enhanced customer identification from bank statement details. As of the 2026-09-21 verification date 26D is the next quarterly update and not established as generally deployed, so none of that functionality is recorded as current authority; the 26D document also carries Oracle's forward-looking-statement disclaimer. Not established for 26C: the exact applied amount semantics (full versus partial), whether more than one transaction can be selected, the resulting receipt/transaction status values and field-level names of the application record, retry, rollback and atomicity behaviour, behaviour when the invoice cannot accept the receipt, the amount is invalid, authorization fails, the receipt is already applied or customer identification is ambiguous, the concrete audit artefacts (Oracle states audit requirements are enforced but does not describe an immutable log, actor/timestamp fields or conversation retention), the model/provider, and whether the agent has any runtime identity distinct from the invoking user. Whether customer/invoice matching is AI-ranked or deterministic is not established: Oracle describes natural-language search plus "context-aware recommendations", not an autonomous matching decision. Receipt creation from bank statement lines and remittance ingestion by Document IO are earlier, separately documented automation and are not attributed to this agent. Cash positioning, Payments Agent, Payables Agent and Document IO are boundaries, not part of this capability.

Evidence