Integrations
Oracle Integration
Invoices, vendors and payments between Oracle and PTAS AI, by API or file, with status written back.
What moves
What flows between Oracle and PTAS AI
An Oracle integration with AI in front of it moves two things: documents and master data in, payables invoices, attachments and status out. Oracle stays the system of record. The keying stops.
Oracle Fusion Cloud ERP or E-Business Suite
The documents
Your coding rules
PTAS AI
Invoices created, not keyed
One payables invoice per document, distributions coded, the image attached, written only after approval.
Holds and payment status back in the queue
Validation holds and payment status come back on a schedule, so FinSuite knows what is held and what was paid.
A trail on both sides
The Oracle invoice number sits on the FinSuite record; the invoice image sits on the Oracle invoice.
Oracle is a planning example here, not a packaged connector. Whether your instance is Fusion Cloud or E-Business Suite, which objects we write and who approves what are confirmed during assessment.
How FinSuite posts to a ledgerIntegration methods
Four ways to build an Oracle integration
On Fusion Cloud the choice is a live link or a file. E-Business Suite is a different conversation, and usually a shorter one.
Native
What Oracle does itself
Oracle Fusion Payables has its own capture for invoices emailed to it, and leaves what it could not read for a clerk to finish. It does not run your approval policy before the invoice exists in Oracle. We are not listed on Oracle Cloud Marketplace, and nothing here is a packaged connector.
API
Oracle Fusion Cloud ERP REST APIs
REST over HTTPS from a dedicated integration user with its own job roles and data access, limited to the business units in scope. Suppliers, purchase orders, receipts, payables invoices with lines, distributions and attachments, and payments are what we read and write. Our proposal for almost every Fusion Cloud instance.
File
FBDI into Fusion, file exchange into E-Business Suite
Fusion takes an Import Payables Invoices file (FBDI), loaded and imported as a scheduled job, with the import report read back for rejections. E-Business Suite takes the same shape through the Payables Open Interface tables. Both are batches on a schedule with a reconciliation report, not a live link.
Custom
Several business units, or Oracle as one of three systems
Several business units and ledgers, an E-Business Suite instance part way through a move to Fusion, or a procurement system in front of Oracle: these need orchestration on top. One queue, one approval policy, one mapping per business unit, and a cut-over plan that posts nothing twice.
Our default for Fusion Cloud is API integration: the REST resources for reads and writes, and holds and payment status read back on a schedule rather than pushed, unless you already run Oracle Integration and want it to push. The file route is right more often than people expect. A Payables team that already imports a procurement feed has the FBDI pattern and an import schedule in place, and a batch with an import report is easier to operate than another live connection. For E-Business Suite we use Oracle Integration where you have it, or the Open Interface tables. We do not ask you to open the schema for us.
Field mapping
Where each finance object lands in Oracle
The mapping is agreed before build and kept per business unit. This is the starting point we bring to the assessment.
The entry, on both sides · Illustrative example
Field mapping is yours to define. Entries are validated against it before they reach the ERP, not rejected by it afterwards.
Security of the connection
What protects the link to your Oracle instance
Four controls, each one visible to your Oracle security administrator. None of them depends on trusting us.
An integration user, not a person's login
Your Oracle security administrator creates a dedicated integration user, authenticated through your Oracle identity domain, with job roles limited to Payables and Procurement and data access limited to the business units in scope. Credentials are stored encrypted and revocable in Oracle at any time.
Least privilege, written down
No General Ledger posting rights, no payment run rights. The user reads procurement and writes payables invoices, and nothing else. The role set is agreed at assessment and reviewed when the workflow changes.
No database login to E-Business Suite
Invoices go in through the Payables Open Interface; suppliers, purchase orders and payment status come out as scheduled extracts or through Oracle Integration. Files travel over SFTP or HTTPS and are kept with their import report, so a rejected line can be traced to its document.
Writes you can audit
Each invoice we create records who approved it, which document it came from and the invoice number Oracle returned. A test environment with your own data comes before production.
FAQ
Questions Oracle teams ask
Do you work with Oracle Fusion Cloud ERP, E-Business Suite, or both?
Both, but differently. Fusion Cloud has the REST APIs and the FBDI file loads, so the choice is between a live link and a scheduled batch. E-Business Suite is connected through Oracle Integration where you run it, or by file exchange into the Payables Open Interface. If you are part way through a move to Fusion, tell us early; the mapping moves with you.
Where does approval happen, in FinSuite or in Oracle?
In one place, never both. If your Payables already runs Oracle invoice approval, we create the invoice and leave approval there; FinSuite validates, matches and codes, then stops. If approval runs in FinSuite, the invoice reaches Oracle already approved, and your Oracle approval rules are set so this source is not routed a second time.
We have several business units on one Oracle instance. Does that need several integrations?
One integration, one mapping per business unit. Supplier sites, account combinations and approval limits differ by unit, so the mapping is kept per unit and the integration user has data access to exactly those units. The queue is shared, with the business unit as a dimension, so one team can work all of them.
Is this an Oracle Cloud Marketplace app or a partnership with Oracle?
No. The connection is built for your instance, authorised by your administrator and documented for your auditors. We do not claim a marketplace listing or a partnership with Oracle, and we would rather build the mapping to your chart of accounts than ship something generic.
Keep reading
Related integrations
SAP Integration
The other large ERP we plan around: OData, BAPIs, IDocs and flat files.
Read more →NetSuite Integration
The Oracle-owned mid-market suite, connected through its own interfaces, not these.
Read more →FinSuite Integrations
The four integration methods and how FinSuite posts into any ledger.
Read more →All integrations
ERPs, accounting suites, the REST API and webhooks in one list.
Read more →Next step
Bring a month of invoices and your supplier list
An assessment starts with your real documents and a test environment. Nothing is written to Oracle until your Payables team has seen the invoices.