Oracle Fusion 26C AI Agents for Receivables: What Each One Does, Needs and Leaves Out

Oracle announced the Collectors Workspace in April with a promise to help finance teams collect cash faster, lower days sales outstanding and lift promise-to-pay conversion. The 26C release notes are where Oracle documents the Oracle Fusion 26C AI agents for receivables in detail, and they are more specific than the press release about what the agents do and what they need.

This guide reads those notes for a CFO or collections manager deciding whether to switch them on. For each agent: what it does, what Oracle’s own feature table says about enabling it, who gets access, and what it explicitly leaves out. Receipt application through the API, and when your environment gets 26C, are covered in the Oracle Fusion 26C cash application guide. What changes next is in the 26D receivables guide.

Which Oracle Fusion 26C AI agents touch receivables?

Oracle’s 26C Financials feature summary lists dozens of features. Three AI features sit on the credit-to-cash path, and the “Action to Enable” column already tells you most of the rollout plan:

Two other 26C agents sound relevant and are not. The Payments Agent works on supplier payments, and the second Cash Processing Agent covers cash positioning for treasury. The one non-AI receivables change in 26C is small but useful for audit: a Rebill Source Transaction field that ties a rebill invoice to the original, on by default.

Collector Workspace: an AI worklist for collectors

The Collector Workspace agent replaces the search a collector does before every call with two screens. The first is a prioritised customer list, ranked by signals your collections policy defines, such as overdue balances, with the reason each account is near the top and a recommended next action. The second is a drill-down per customer: aging, overdue balance, payment history, disputes, promises to pay and prior collections activity in one place.

Around those two screens, the agent can:

• Recommend next steps such as requesting a promise to pay or calling the customer.
• Answer questions about an account in plain language.
• Read incoming customer emails and pull out the intent, such as a promise to pay.
• Draft replies and follow-ups using the account context.
• Surface call scripts, create call notes and capture promises.

What switching it on involves

Oracle marks it Setup Required, and the setup is real work for whoever administers Fusion:

1. Set the profile option that exposes AI Agent Studio through Quick Actions, at site level.
2. Fill in Oracle’s collections policy template with your own rules and upload it, as DOCX or PDF, through the Collections Policy Execution Assistant, then approve it.
3. Copy the Collections Email Response Assistant template for each mailbox you want read. One copy can watch only one email account.
4. Give collectors the Collections Workspace Assistant duty role, enable permission groups on the role, and run the two security synchronisation processes.
5. Check data access and collector assignments, because each collector sees only the customer accounts assigned to them on the account profile.

What it leaves out

The tips section is where the scope is drawn. Sending dunning letters is out of scope, so your existing dunning setup keeps running. Aging uses fixed buckets: current, 1 to 5, 6 to 10, 11 to 30, 31 to 60, 61 to 90 and over 90 days. Broken promises only show up if collectors record promises consistently and the promise reconciliation program runs. The agent does not bypass dispute controls, approval rules or write-off controls, and it does not replace standard Receivables setup or dispute resolution.

That is a reasonable shape for a first release: the collector stays in charge, and the agent removes the searching. It does mean the policy document matters from day one, because the ranking and the recommendations follow it. In 26D, that same policy starts governing actions the agent takes without a collector, which is the subject of the 26D guide.

The Cash Processing Agent: unapplied cash in one conversation

The Cash Processing Agent is the one receivables agent that arrives on. It has two contexts, and users switch between them:

• Receipts, for receipt creation exceptions from bank statements and Lockbox and for remittance advice data after it is read, with a link from each exception to its correction flow.
• Cash Application, for unidentified and unapplied receipts. A user can search payment details such as the originator name or wire number, unmatched remittances, open and disputed invoices, and promises to pay, then apply the receipt once they confirm.

An Insights page lists receipt creation exceptions, unidentified receipts and unapplied receipts together, so the queue is visible without running a report. Underneath it, Oracle’s document ingestion reads bank files and remittance advices from customer emails, as PDFs, email bodies or images, with no extra enablement. Receipt creation from bank statements is still switched on per bank account, with a start date that can go back up to 30 days.

Two practical points. Access is the only setup: the agent’s duty roles sit inside four predefined Receivables job roles, but permission groups must be enabled in the Security Console, and custom job roles need the roles added. And the classic receipt pages stay, so specialists can still work the way they do today. Oracle’s tip to schedule AutoMatch with Include Remittance set to Yes, and why application rules matter for unapplied cash, are covered in the 26C cash application guide.

The Customer Billing Agent: answers here, actions elsewhere

The Customer Billing Agent answers billing questions in natural language: invoice details, payment status, billing history, disputes, credit memos, tax, currency, approvals and accounting. For a billing team fielding “which invoices are still open on this PO?” all day, that removes a lot of navigation.

Oracle is explicit about its limits. It is for inquiry and summarisation, and any change continues in the normal Receivables page or workflow. Its Billing Inquiry context has no Insights page and no predefined prompts, and answers are better when a question names an invoice, customer, account, PO or date range. Access comes through a duty role inside the Billing Manager and Billing Specialist segregated roles, once permission groups are enabled.

Press release versus release notes

Oracle’s April announcement describes the Collectors Workspace in outcome terms: faster cash, lower DSO, more promises kept. The 26C release notes describe the mechanism, and in 26C that mechanism is guidance. The agent ranks, summarises, recommends and drafts; a collector decides and acts. The Cash Processing Agent applies a receipt only after a user confirms. The Customer Billing Agent changes nothing.

That gap is normal for a first release, and Oracle is closing it quickly: 26D adds automatic execution within policy. For planning, though, the release notes are the document to budget against. If the business case for switching on the 26C agents assumes a smaller collections team in the first quarter, it assumes something the 26C agents do not do.

What Oracle’s 26C agents do not do

Pulled together from the three feature pages, the boundaries for 26C are:

• They do not send dunning letters.
• None of the three feature pages describes contacting a customer without a person, or taking a payment from one.
• Cash application happens only after a user confirms.
• The billing agent does not change data.
• Each user sees only what their data access and, for collectors, their account assignments allow.

Do you still need an AR automation layer with Oracle 26C?

It depends on what the bottleneck is. If your collectors already contact every account on time and lose most of their day to searching across Oracle screens, the 26C agents address exactly that. Start with Collector Workspace for the collectors and the Cash Processing Agent for the cash application team.

If the bottleneck is that accounts do not get contacted at all, because there are more invoices than collectors, the 26C agents help less. They make each collector faster; they do not contact the account the collector never reaches. That is the work an autonomous AR layer takes on: reaching every customer on schedule, and taking payment inside the message.

Finero is that kind of layer for Oracle Fusion. It reads invoices and installments from Oracle, contacts customers across email, SMS and chat, puts a payment link through your existing processor in every reminder, and posts each payment back to Oracle as a Standard Receipt carrying the installment reference, so it reaches the Cash Processing Agent already identified. Collectors then spend their Collector Workspace time on the accounts that need a person. The one thing to settle is ownership: decide which system contacts which customers, so nobody hears from two. See how Finero works with Oracle Fusion and how collections automation reduces DSO.

How to roll out the Oracle 26C AI agents

1. Map who holds the predefined Receivables, Collections and Billing job roles, and which custom roles need the assistant duty roles added.
2. Enable permission groups on those roles and run the security synchronisation.
3. Write the collections policy before switching on Collector Workspace: priorities, escalation rules and the accounts that need sign-off before any contact.
4. Decide which mailboxes the email assistant reads, one agent copy per mailbox.
5. Clean up collector assignments on customer account profiles, or collectors will open an empty workspace.
6. Confirm the promise reconciliation program runs, or broken promises will not appear.
7. Pilot in a test environment with one team before production, and keep dunning running as it is.