[ Oracle Fusion / Accounts payable ]

Oracle Fusion payables, without the keying

engini reads each supplier invoice that arrives by email, checks it against the purchase order in Oracle Fusion Cloud ERP, and records the payables invoice when they agree. When they do not, an AI agent tells the buyer exactly what is off. Oracle Fusion stays your system of record, with its own approvals and controls.

Oracle Fusion Cloud ERPOutlook or GmailSlackengini AI Tools
See the Oracle Fusion Cloud ERP integration →
A supplier invoice, into Oracle Fusion
  1. Supplier invoice arrivesap@ inbox, PDF, PO number
  2. AI reads the invoicesupplier, lines, totals
  3. Oracle Fusion Cloud ERP logo
    Purchase order checkedOracle Fusion: PO lines and amounts
  4. Oracle Fusion Cloud ERP logo
    Payables invoice recordedmatched to the PO
  5. Slack logo
    Or the gap, explained#ap: price differs on line 3
Illustration of the flow on this page, not a product screen.
What it does
Supplier invoices checked against the PO and recorded in Oracle Fusion
Systems
Oracle Fusion Cloud ERP, Outlook or Gmail, Slack or Teams
Built with
A workflow with engini AI Tools and an AI agent step
Your control
Your Oracle user and roles; Oracle approvals still apply
[ 01 / The problem ]

Enterprise ERP, manual invoice entry

Blurred landscape photo with the words Accounts payable and the labels Trigger, Read, Check, Act

Companies move to Oracle Fusion Cloud ERP for a modern finance core, and still have AP clerks keying supplier invoices from PDFs. Each one means finding the supplier, opening the purchase order, checking quantities and prices, and entering the payables invoice line by line.

Where AP time goes

  • Reading invoices in every supplier’s format.
  • Comparing each line with the purchase order.
  • Emailing buyers about price and quantity differences.
  • Answering suppliers who ask whether an invoice arrived.

What the agent takes over

engini AI Tools reads the invoice, and an AI agent step reads the purchase order from Oracle Fusion and compares lines and amounts. When they agree, the workflow records the payables invoice through the connection you set up, so the Oracle user’s roles and your Oracle approval rules apply as usual. When they do not, the agent posts a short, specific note to the buyer in Slack or Teams.

engini has no documented Oracle Fusion triggers yet, so the flow starts from the invoice email, and anything waiting on Oracle is re-checked on a schedule. Every tool the connector offers, and whether it reads or writes, is listed in the engini Tool Catalog.

[ 02 / How it works ]

Invoice to Oracle Fusion in four steps

01 / Trigger

The invoice arrives

A new email in the AP inbox starts the workflow.

02 / Read

AI reads it

engini AI Tools extracts the supplier, PO number, lines and totals.

03 / Check

Against the PO

An AI agent step reads the purchase order from Oracle Fusion and compares lines and amounts.

04 / Act

Record or explain

It records the payables invoice when they agree, or posts the gap to the buyer in Slack or Teams.

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 FusionPurchase orders, suppliersRead
Oracle FusionPayables invoicesCreate
Outlook or GmailThe AP inbox and PDF invoicesRead
Slack or TeamsNotes to buyers about differencesWrite

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 purchase order: invoice, check, payables

Editorial image: invoice, purchase order, payables.

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: when a supplier invoice PDF arrives in ap@ in Outlook, read it with engini AI Tools, read the purchase order it names from Oracle Fusion Cloud ERP, and if the lines and amounts agree, record the payables invoice in Oracle Fusion. If they differ, post the differences to #ap in Slack and record nothing.
  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 AI record payables invoices in Oracle Fusion Cloud ERP?

Yes. engini’s Oracle Fusion connector covers payables invoices. An AI agent checks each invoice against the purchase order first, and the workflow records it through the Oracle user you connect.

Do our Oracle approvals still apply?

Yes. engini acts through the Oracle user behind the connection, with that user’s roles, so your Oracle approval rules apply as usual. engini adds no approval step of its own.

Why does the flow start from the email?

engini has no documented Oracle Fusion triggers yet, so the invoice email starts the flow and anything waiting on Oracle is re-checked on a schedule.

Is there a setup guide?

The help-center guide is being written. The engini Tool Catalog lists every Oracle Fusion tool and the permissions it needs, and the team helps with the first setup.

Is this the Oracle Database connector?

No. Oracle Database is a separate engini connector for databases: rows, stored procedures and custom SQL.