Oracle Fusion Cloud ERP and Twilio integration

What moves between them

Finance events originate in Oracle Fusion Cloud ERP and flow outbound to Twilio. ml-connector polls Oracle Fusion Cloud ERP for invoices, payment records, and purchase orders on a configurable interval, filters them by amount or approval status, and triggers SMS or voice messages to pre-configured phone numbers through Twilio. Twilio delivers the notification and reports back the delivery status (sent, delivered, failed) via webhook callbacks. The data moves one direction: Oracle Fusion Cloud ERP as the source, Twilio as the notification delivery channel.

How ml-connector handles it

ml-connector stores both credential sets encrypted: the OAuth 2.0 client ID and secret for Oracle Fusion Cloud ERP, and the Twilio Account SID and Auth Token. It polls Oracle Fusion Cloud ERP at your chosen interval (e.g., every 10 minutes) using a LastUpdateDate filter to retrieve only newly created or changed transactions. When an invoice, payment, or purchase order matches your alert rule (amount threshold, approval status, supplier category), ml-connector formats a human-readable message and sends it via Twilio SMS or voice call to the alert recipient phone numbers. Twilio reports delivery status asynchronously; ml-connector listens for the status callbacks and logs them to the audit trail. If a Twilio send fails (e.g., invalid phone number, carrier rejection), ml-connector retries with exponential backoff and tracks the failure so you can investigate. Oracle Fusion Cloud ERP and Twilio credentials are refreshed as needed; the OAuth token is renewed before expiry, and Twilio API keys are rotated per your security policy.

A real-world example

A mid-sized manufacturing company runs Oracle Fusion Cloud ERP for all finance and procurement. The accounts payable team needs to know immediately when invoices from key suppliers arrive and when large payments are processed, so they can flag discrepancies or coordinate with operations. Before the integration, the AP manager checked the system multiple times per day or relied on email notifications from Oracle Fusion Cloud ERP, which often arrived hours later. With Oracle Fusion Cloud ERP and Twilio connected, the AP manager and controller receive an SMS alert within minutes of an invoice exceeding 25,000 USD or a payment clearing over 100,000 USD. The team responds faster, month-end closes sooner, and supplier issues are caught before they escalate.

What you can do

• •Alert stakeholders via SMS when invoices exceed a configured amount threshold, with the invoice number, supplier name, and amount included.
• •Send voice call notifications for high-priority purchase orders awaiting approval, allowing escalation without leaving the office.
• •Track all alert delivery status (sent, delivered, failed) in ml-connector's audit log for compliance and troubleshooting.
• •Filter alerts by supplier, cost center, or invoice type so each team member receives only the notifications relevant to their role.
• •Retry failed SMS and voice messages with exponential backoff, preventing alerts from being lost due to temporary carrier or network issues.

Questions

How does ml-connector know when a new invoice or payment arrives in Oracle Fusion Cloud ERP?

Oracle Fusion Cloud ERP has no outbound webhook system for external connectors. ml-connector polls the Oracle Fusion Cloud ERP REST API on a schedule you set (typically every 5 to 15 minutes) and filters for transactions created or updated since the last poll using the LastUpdateDate parameter. When ml-connector finds a matching transaction (an invoice over your threshold, a payment in a watched status), it immediately sends an SMS or voice alert via Twilio.

What happens if a Twilio SMS delivery fails or times out?

Twilio reports the delivery status asynchronously via webhook callbacks. If an SMS is rejected by the carrier, marked as failed, or the phone number is invalid, ml-connector logs the failure to the audit trail with the reason. ml-connector then retries the message with exponential backoff (e.g., 1 second, then 2, 4, 8 seconds) up to a maximum of three attempts. If all retries exhaust, the failed alert is flagged in the audit log so you can investigate and correct the phone number or alert rule.

Which Oracle Fusion Cloud ERP transactions can trigger alerts, and how do I configure the thresholds?

ml-connector can trigger alerts on invoices, payments, and purchase orders. You configure thresholds by amount (e.g., alerts for invoices over 50,000 USD), approval status (e.g., new POs awaiting buyer approval), or supplier category. Each threshold links to one or more Twilio phone numbers, so invoices might alert the AP manager while large POs alert the procurement director. Thresholds are set during flow configuration and can be changed without redeploying the connector.