canonical: https://jentic.com/apis/oraclecloud.com/oraclecloud

# Oraclecloud Supplier

The Supplier API onboards suppliers into Oracle Fusion Cloud Financials through the fscmRestApi resources, covering the steps Payables needs before a supplier can be paid. It creates the supplier record with fields such as Supplier, SupplierType, BusinessRelationship, and TaxOrganizationType, then adds a supplier address, a supplier site, and the site's business unit assignment. On the payments side it registers bank branches and external bank accounts, looks up external payees, and assigns a bank account as the supplier's payment instrument for disbursements. This spec targets a test Fusion instance and its child-resource paths are written against fixed supplier and site ids.

## For AI agents

Create suppliers in Oracle Fusion Cloud, add their address, site, and business unit assignment, register their bank branch and external bank account, and assign that account as the payment instrument for supplier disbursements.

## Scope

Does not create invoices, run payment batches, issue purchase orders, or post general ledger journals. Use for onboarding Oracle Fusion suppliers and their bank payment instruments only.

## Capabilities

- Create a supplier record with Supplier, SupplierType, BusinessRelationship, and TaxOrganizationType through the suppliers resource
- Add a supplier address, a supplier site with its CommunicationMethod and Email, and a site assignment to BillToBU and ClientBU business units
- Register a bank branch with BankName, BankBranchName, and BranchNumber through cashBankBranches
- Create an external bank account for a supplier with BankAccountName, BankAccountNumber, and AccountType
- Look up external payees with the paymentsExternalPayees finder and assign a bank account as a DISBURSEMENTS payment instrument

## Use cases

### Agent-run supplier onboarding

A procurement agent onboards a vendor approved in another system by calling the Oracle Fusion supplier resources through Jentic in sequence: create the supplier, add its address, create a site, and assign the site to the paying business unit. Jentic returns each operation's input schema, so the agent fills fields like BusinessRelationship and BillToBU correctly, and your own Jentic One instance injects the Fusion username and password at call time.

Example prompt: POST `/fscmRestApi/resources/latest/suppliers` with Supplier 'Acme Pte Ltd', SupplierType 'Supplier', BusinessRelationship 'Spend Authorized', and TaxOrganizationType 'Corporation', then report the created supplier record

### Supplier bank account setup for payment runs

Before Payables can disburse funds, the supplier needs a bank account tied to it as a payment instrument. The flow registers the bank branch through cashBankBranches, creates the external bank account through externalBankAccounts, and then posts an instrumentAssignments record with PaymentFlow DISBURSEMENTS and PaymentInstrumentType BANKACCOUNT linking the account to the payee's PaymentPartyId.

Example prompt: POST `/fscmRestApi/resources/11.13.18.05/externalBankAccounts` with BankAccountName 'Acme SG', BankAccountNumber '8830023556', and AccountType 'SAVINGS', then POST `/fscmRestApi/resources/11.13.18.05/instrumentAssignments` with Intent 'Supplier', PaymentFlow 'DISBURSEMENTS', PaymentInstrumentType 'BANKACCOUNT', and the new PaymentInstrumentId

### Payee and instrument lookups

Finance teams checking why a supplier payment failed need to confirm the payee exists and which instrument it uses. The paymentsExternalPayees operation searches payees with its finder and q parameters, and the instrumentAssignments read operation lists the assignments a finder matches, so an agent can report whether a bank account is attached before a payment run.

Example prompt: GET `/fscmRestApi/resources/11.13.18.05/paymentsExternalPayees` with a finder for the supplier's party, then GET `/fscmRestApi/resources/11.13.18.05/instrumentAssignments` with a finder for that payee and report the assigned instrument

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/fscmRestApi/resources/latest/suppliers` | Create a supplier |
| POST | `/fscmRestApi/resources/latest/suppliers/300000004876298/child/sites` | Create a supplier site |
| POST | `/fscmRestApi/resources/11.13.18.05/cashBankBranches` | Create a bank branch |
| POST | `/fscmRestApi/resources/11.13.18.05/externalBankAccounts` | Create an external bank account |
| GET | `/fscmRestApi/resources/11.13.18.05/paymentsExternalPayees` | Search external payees |
| POST | `/fscmRestApi/resources/11.13.18.05/instrumentAssignments` | Assign a payment instrument |

## Key resources

- **Suppliers** — Create supplier records and their child addresses, sites, and site business unit assignments
- **Bank branches and external bank accounts** — Register bank branches and create supplier bank accounts used for payments
- **Payees and instrument assignments** — Look up external payees and assign bank accounts as payment instruments for disbursements

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 0 / 100
- **Maturity:** Non-Ready
- **Dimensions:**
  - Foundational Compliance: 99 / 100
  - Developer Experience & Jentic Compatibility: 75 / 100
  - AI-Readiness & Agent Experience: 33 / 100
  - Agent Usability: 94 / 100
  - Security: 10 / 100
  - AI Discoverability: 0 / 100
- **View full report:** https://jentic.com/apis/oraclecloud.com/oraclecloud/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **Setup:** Wiring Oracle Fusion by hand means Basic auth against your pod's host, versioned fscmRestApi resource paths, and chaining supplier, site, bank account, and instrument calls in the right order. Through Jentic you install once, import the Supplier API from the API Directory, store the credentials once, and your agent calls it.
- **Permission scoping:** Each step of supplier onboarding is a separate operation, so a rule can let your agent read payees and instrument assignments while leaving supplier creation and bank account creation out. The target records travel in request bodies or finder queries, so rules bound which operations the agent may call, not which supplier.
- **Credential handling:** Your Fusion username and password are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'create a supplier bank account' or 'assign a payment instrument', and Jentic returns the matching Fusion operation with its input schema so the agent sends the right fields without browsing Oracle's REST reference.

## Related APIs

- **BILL AP Vendor management** — Vendor onboarding with bank account details inside BILL accounts payable
- **Xero Accounting API** — Small-business accounting with contacts, invoices, and payments
- **Holded API** — ERP with contacts, products, treasuries, and invoicing

## FAQ

### What authentication does the Oracle Fusion Supplier API use?

This Supplier spec declares HTTP Basic authentication: a Fusion username and password sent in the Authorization header. Through Jentic those credentials are stored encrypted by your own Jentic One instance and injected at call time, so they never enter the agent's prompt or logs.

### Can I set up a supplier's bank account for payments with this API?

Yes. Register the branch through cashBankBranches if it does not exist, create the account through externalBankAccounts with fields such as BankAccountName, BankAccountNumber, and AccountType, then link it with an instrumentAssignments POST that sets PaymentFlow to DISBURSEMENTS, PaymentInstrumentType to BANKACCOUNT, and the payee's PaymentPartyId.

### Why do some paths in this spec contain fixed numeric ids?

The address, site, and site assignment paths are written against one supplier id (300000004876298) and one site id (300000004876565) from a test Fusion instance, rather than as path parameters. To work with a different supplier, the equivalent Oracle Fusion resource paths take that supplier's own id in the same position.

### How do I onboard a supplier in Oracle Fusion through Jentic?

Install Jentic One, add the Supplier API from the Jentic API Directory, and store your Fusion username and password once. Your agent searches for 'create a supplier in Oracle Fusion', gets the suppliers create operation with its input schema, and posts the supplier, then continues with the site and bank account operations. To run it on your own infrastructure, install Jentic One from its GitHub repo.

### Is there an Oracle Fusion Supplier MCP server?

You don't need an MCP server to give your agent the Oracle Fusion Supplier API. Jentic connects it directly from the API Directory: import it, store your credential once, and your agent calls it, discovering operations on demand instead of loading extra tool definitions into its context.

### Can I limit what my agent is allowed to do with the Oracle Fusion Supplier API?

Yes. For a lookup-only agent, write a rule that allows just the paymentsExternalPayees and instrumentAssignments read operations: it can check payees and their instruments but cannot create suppliers or bank accounts. Add the create operations only for an onboarding agent, and every call is logged by your own Jentic One instance.