[ Oracle Fusion / Receivables ]

Oracle Fusion collections, followed up daily

engini reads open receivables invoices from Oracle Fusion Cloud ERP every morning, and an AI agent sends each customer the reminder that fits the stage, reads the replies, and records promises to pay and disputes where your team works. Sales sees the overdue balance in Salesforce or HubSpot before calling.

Oracle Fusion Cloud ERPOutlook or GmailSlackSalesforceHubSpot
See the Oracle Fusion Cloud ERP integration →
The morning collections run
  1. Every weekday at 7:00schedule trigger
  2. Oracle Fusion Cloud ERP logo
    Read receivables invoicesopen, past due
  3. Agent writes remindersstage, amounts, invoice numbers
  4. Reply read"disputed: wrong quantity"
  5. Slack logo
    Routed to the owner#collections
Illustration of the flow on this page, not a product screen.
What it does
Daily reminders from Oracle receivables, replies read and routed
Systems
Oracle Fusion Cloud ERP, Outlook or Gmail, Slack or Teams, Salesforce or HubSpot
Built with
A scheduled workflow with an AI agent step
Your control
Read access is enough; wording and stages are yours
[ 01 / The problem ]

The ERP knows who is late. Nobody follows up.

Blurred landscape photo with the words Collections and the labels Read, Remind, Listen, Share

Oracle Fusion holds every open receivables invoice. The follow-up still runs on email and spreadsheets: who was reminded, who promised to pay on the 15th, which line is disputed and who can fix it. Meanwhile the account team works in the CRM and does not know the customer is overdue.

Where collections time goes

  • Pulling past-due invoices and deciding who to contact.
  • Writing reminders with the right invoices and amounts.
  • Reading replies and logging promises and disputes.
  • Telling sales before they call the customer.

What the agent does

A scheduled engini workflow reads open receivables invoices from Oracle Fusion, and an AI agent step writes each customer a reminder in the tone for that stage, reads the replies, and records promises to pay and disputes in your collections sheet and in Slack or Teams. If you use Salesforce or HubSpot, the overdue balance goes onto the account. This flow only reads Oracle, so the access is simple to approve.

[ 02 / How it works ]

Read Oracle, reach the customer, route the answer

01 / Read

Past-due invoices

A scheduled workflow reads open, past-due receivables invoices from Oracle Fusion.

02 / Remind

One email each

An AI agent step writes each customer one reminder with the invoice numbers and amounts.

03 / Listen

Replies become notes

Promises to pay and disputes go to your collections sheet and to the owner in Slack or Teams.

04 / Share

Sales sees it

The overdue balance is written to the Salesforce account or HubSpot company.

This is the flow you will build. Start free and connect your systems.

[ 03 / What the agent reads and writes ]

What the agent reads and writes

SystemRecordsAccess
Oracle FusionReceivables invoicesRead
Outlook or GmailReminders and repliesSendRead
Google Sheets or ExcelCollections logWrite
Salesforce or HubSpotOverdue balance on the account (optional)Update

Connect these systems in engini and give the agent only these tools.

[ 04 / Build it with the engini skill ]

Describe it in plain words. The engini skill builds the workflow.

engini skills is engini’s plugin for Claude Code and Codex. Its workflow agent, Flo, turns a plain-language request into an engini workflow: it designs the steps, dry-runs them against your own engini account, shows you a proposal, and creates the workflow only after you approve it, always turned off. You check it in the engini designer and turn it on.

Blurred landscape photo with the Oracle logo, the engini mark and a frosted tile joined by a thin line, labeled receivables: past due, reminder, reply routed

Editorial image: a daily collections route.

Claude Code: install once
/plugin marketplace add engini/skills
/plugin install skills@engini
Then ask for this solution
Build a workflow in my engini account: every weekday at 7:00, read open past-due receivables invoices from Oracle Fusion Cloud ERP, group them by customer, send each customer one reminder email from Outlook listing the invoice numbers and amounts, and add a row per customer to the "Collections" Google Sheet.
  1. You need an engini account, the engini CLI (npm i -g @engini/cli) and a workspace-scoped API key, ideally a dedicated least-privilege one.
  2. Connect the systems this flow uses in engini first. Flo never creates or changes a connection and never handles your key; it tells you which command to run.
  3. Flo checks your login and workspace, searches the tool catalog, compiles the plan and shows a proposal table with every step. It creates the workflow only when you approve that proposal, and it creates it turned off.
  4. Open it in the engini designer, fill anything it left for you, and turn it on.
engini skills for Claude Code and Codex →
What the skill will never do on its own →
[ 05 / Agent Policy ]

The agent does only what you allow. Every run is on the record.

Agent Policy is how you govern agents in engini: the tools each agent may call, the account each tool uses, and a record of every call.

Toolsets

Scope every call

Hand the agent a toolset: only the tools it needs, each on the connection you choose, for example read only. engini enforces it on the server for CLI, SDK and REST API calls; a call outside the toolset is refused. An MCP server exposes only the connections and tools chosen when you set it up.

Identity

Acts with the account you connect

engini acts with the permissions of the connected account. Connect a person’s own account and it acts as that person; use a shared integration account and it acts as that account. Every run is recorded under the user who triggered it.

Audit

History and audit log

Each tool call and workflow run is recorded in History and the audit log, which supports export and streaming to your SIEM. Your agent never needs your credentials: engini stores them and adds them when it runs each call.

SOC 2 Type IIISO 27001GDPRHIPAA compliant
[ 06 / Try it now ]

Build it on your own data today

Start free, connect Oracle Fusion Cloud ERP, and build this flow with the engini skill, in Workflow Studio, or from your own agent.

  • 01Workflow Studio. Build the flow on a visual canvas, with an AI agent step where judgment is needed. Start free →
  • 02Your own agent. Give Claude, ChatGPT or Cursor an engini MCP server with only these tools. MCP client setup →
  • 03The engini skill. Ask Flo in Claude Code or Codex and review its proposal. Install the skill →
[ 07 / Questions ]

Questions buyers ask before they start

Can an AI agent read receivables from Oracle Fusion?

Yes. engini’s Oracle Fusion Cloud ERP connector covers receivables invoices, and a read-only Oracle user is enough for this flow.

Does it record payments in Oracle?

No. This flow only reads receivables invoices. Payments are recorded in Oracle the way you do it today.

How often does it refresh?

On the schedule you choose, typically every morning. engini has no documented Oracle Fusion triggers yet.

Can sales see overdue balances?

Yes. The workflow writes the overdue balance and last note to the Salesforce account or HubSpot company.