> ## Documentation Index
> Fetch the complete documentation index at: https://docs.nectarclimate.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Oracle Fusion

> Connect Bill Pay to Oracle Fusion Cloud Financials for automated AP posting.

<Tip>Need help in this area? See [Bill Pay FAQ](/platform/bill-pay/faq) or email [support@nectarclimate.com](mailto:support@nectarclimate.com).</Tip>

The Oracle Fusion integration posts coded utility bills from Nectar into **Oracle Fusion Cloud Financials (Payables)**. Nectar authenticates with **OAuth 2.0 client credentials** issued by your **OCI Identity and Access Management (IAM) identity domain**, then creates payables invoices when your routing rules match.

## How the connection works

Nectar delivers invoices to Payables through the Fusion Financials **REST API** — the `invoices` resource (`/fscmRestApi/resources/11.13.18.05/invoices`) for direct creation, or the **Import Payables Invoices** flow (the `payablesInterfaceInvoices` open-interface resource with the `submitImportInvoices` action) for batch loads that run through the standard **Import Payables Invoices** program. Each invoice carries the **business unit**, **supplier** and **supplier site**, invoice number, invoice date, accounting date, and distribution combinations, so it lands in Payables ready for validation and the standard **payment process request**.

Your Oracle administrator registers a **confidential application** in the identity domain and grants it the client-credentials grant; Nectar exchanges the **Client ID** and **Client secret** for a bearer token on each call.

## Connection fields

Configure these fields when you select **Oracle Fusion** in the ERP wizard:

| Field                   | Description                               | Example                                        |
| ----------------------- | ----------------------------------------- | ---------------------------------------------- |
| **Destination name**    | Label for this connection in Nectar       | `Oracle AP Production`                         |
| **Instance URL**        | Your Oracle Fusion application URL        | `https://yourcompany.fa.us2.oraclecloud.com`   |
| **Identity domain URL** | Oracle identity domain for authentication | `https://your-domain.identity.oraclecloud.com` |
| **Client ID**           | OAuth client identifier                   | *(secret)*                                     |
| **Client secret**       | OAuth client secret                       | *(secret)*                                     |

Client ID and client secret are stored as encrypted credentials.

## Set up in Nectar

<Steps>
  <Step title="Open the ERP wizard">
    Go to [**Bill Pay > Destinations**](https://dash.nectarclimate.com/bill-pay/destinations/new/integration), click **AP/ERP Integrations**, and select **Oracle Fusion**.
  </Step>

  <Step title="Enter connection details">
    Provide the destination name, instance URL, identity domain URL, client ID, and client secret.
  </Step>

  <Step title="Review and create">
    Confirm the settings and click **Create integration**.
  </Step>

  <Step title="Add a routing rule">
    Create a [routing rule](/platform/bill-pay/rules) with **Route to AP integration** targeting your Oracle destination.
  </Step>
</Steps>

## What your Oracle team configures

Your Oracle Cloud administrator typically:

1. Registers a **confidential application** in your OCI IAM identity domain with the **client-credentials** grant and access to the Fusion Financials (Payables) REST APIs Nectar uses.
2. Provides the **instance URL**, **identity domain URL**, **Client ID**, and **Client secret**.
3. Confirms **business unit**, **supplier** / **supplier site**, **payment terms**, and **distribution combination** (GL account) mappings for utility invoices.

Validate in a non-production pod or test business unit before pointing production routing rules at the integration. Teams that prefer file-based loads (**FBDI**) instead of REST can raise this during onboarding.

## FAQ

<AccordionGroup>
  <Accordion title="Which Oracle Cloud regions are supported?">
    Any Oracle Fusion Cloud instance reachable from Nectar with valid OAuth 2.0 client credentials. Use your pod-specific instance URL (for example `fa.us2.oraclecloud.com`) and the matching identity domain URL.
  </Accordion>

  <Accordion title="Does Nectar create invoices directly or through the import program?">
    Both are supported. Nectar can create invoices directly through the Payables `invoices` REST resource, or stage them via the `payablesInterfaceInvoices` open interface and trigger the standard **Import Payables Invoices** program with `submitImportInvoices`. Your finance team chooses the approach during onboarding based on validation and volume needs.
  </Accordion>

  <Accordion title="How do I verify delivery?">
    Open the [bill audit trail](/platform/bill-pay/decisions) and check the **Route to AP integration** action status for the Oracle destination.
  </Accordion>
</AccordionGroup>

## Related pages

* [ERP integrations overview](/platform/bill-pay/erp-integrations/overview)
* [SAP S/4HANA](/platform/bill-pay/erp-integrations/sap-s4hana)
* [Destinations](/platform/bill-pay/destinations)