Skip to content
Learn more

Rex for Oracle Fusion

Rex runs collections, cash application, and disputes on Oracle Fusion Cloud ERP and writes the result back. Oracle Fusion stays the ledger. This is a different system from Oracle NetSuite.

Rex for Oracle Fusion

Rex runs collections, cash application, and disputes on Oracle Fusion Cloud ERP. Fusion stays the system of record. Rex reads open invoices, customers, and payments, does the work, and writes applied cash, promises, and dispute status back.

Oracle Fusion and Oracle NetSuite are different systems. If your ledger is NetSuite, use the NetSuite page. That is also where the published customer story sits. Synthesia runs NetSuite, not Fusion.

Most teams go live in under two weeks, with no migration. That is the general claim. It is not a Fusion customer timeline.

What stays in Oracle Fusion

Fusion holds the receivables record your close uses: invoices, receipts, credit memos, and the customer account. Rex does not replace that record or ask you to re-implement receivables in another ledger.

Fusion can remind. A scheduled notice does not know that the customer replied, short-paid, or promised a date next Thursday. Someone still has to read the inbox and update Fusion. That is the work Rex takes, and then writes back, so Fusion and the follow-up do not drift apart.

What Rex runs on top

  • Collections. Follow-up on open invoices, stopped when the cash is applied or a dispute is open on that amount.
  • Cash application. Receipts matched to Fusion invoices, including partial payments and short pays. The unpaid remainder stays in collections or disputes instead of vanishing into an unapplied bucket.
  • Disputes and deductions. The reason coded, the evidence gathered, and the status written back to Fusion.
  • Portals and email. Customer AP portals and the AR inbox sit outside Fusion. Rex works them and ties the result to the Fusion customer and invoice.

Both directions matter. Reading Fusion without writing back means every promise and every short pay gets keyed in again. Writing back without reading live means Rex chases an invoice Fusion already cleared.

When Rex fits, and when it does not

Rex fits when Oracle Fusion is the ledger you intend to keep, and the open work is collections, cash application, and exceptions. Agents run those steps. Your team and a Rex finance expert handle what needs a person.

Rex does not fit a team that wants Fusion-native reminders only. It does not fit a program whose goal is one suite across credit, billing, treasury, and the close. Those buyers should compare order-to-cash software vendors and HighRadius alternatives.

SAP is the other ledger in this set: Rex for SAP.

Frequently asked questions

Is Oracle Fusion the same as NetSuite?
No. Oracle Fusion Cloud ERP and Oracle NetSuite are different products. Rex connects to both. This page is Fusion. The NetSuite page covers NetSuite, including the published Synthesia story.
Does Rex replace Oracle Fusion?
No. Oracle Fusion stays the system of record. Rex reads invoices, customers, and payments and writes collections activity, applied cash, promises to pay, and dispute status back. There is no migration off Fusion.
When is a suite a better fit than Rex on Oracle Fusion?
When you want one vendor to cover credit, billing, cash application, deductions, and record-to-report, and you will staff that implementation. Rex fits when Fusion is staying and the gap is the working steps: collections, cash application, and disputes.

Keep reading