> ## 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.

# NetSuite

> Connect Bill Pay to NetSuite 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 NetSuite integration posts coded utility bills from Nectar into your NetSuite account as **vendor bills**. Nectar connects through **SuiteTalk REST web services** using the credentials configured in the Bill Pay destination wizard.

## How the connection works

Nectar creates each bill through the SuiteTalk **REST record service** — `POST /services/rest/record/v1/vendorBill` — against your account-specific domain (`{accountId}.suitetalk.api.netsuite.com`). Each `vendorBill` record references the **entity** (vendor), **subsidiary**, **currency**, and posts either **item** or **expense** sublists coded to the correct **GL account** and classification (department, class, location) from your [GL coding rules](/platform/bill-pay/rules). Where a bill relates to a purchase order, Nectar can use the PO **transform** endpoint (`/purchaseOrder/{id}/!transform/vendorBill`) to preserve the PO-to-bill link for three-way matching.

Nectar authenticates with **token-based authentication (TBA)** — your integration record's consumer key/secret plus a token ID/secret — or **OAuth 2.0** where your account is configured for it.

## Connection fields

Configure these fields when you select **NetSuite**:

| Field                | Description                         | Example       |
| -------------------- | ----------------------------------- | ------------- |
| **Destination name** | Label for this connection in Nectar | `NetSuite AP` |
| **Account ID**       | Your NetSuite account ID            | `1234567`     |
| **Client ID**        | Integration client ID               | *(secret)*    |
| **Client secret**    | Integration 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 **NetSuite**.
  </Step>

  <Step title="Enter connection details">
    Provide the destination name, account ID, client ID, and client secret from your NetSuite administrator.
  </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 NetSuite destination.
  </Step>
</Steps>

## What your NetSuite team configures

Your NetSuite administrator typically:

1. Enables **SuiteTalk (REST Web Services)** and **Token-Based Authentication** under **Setup > Company > Enable Features (SuiteCloud)**.
2. Creates an **integration record** and a **role** with permission to create vendor bills, then issues the credentials (consumer key/secret and token ID/secret for TBA, or an OAuth 2.0 client).
3. Provides the **account ID**, client ID, and client secret to your Nectar administrator.
4. Confirms **subsidiary**, **vendor (entity)**, **currency**, and **GL account** / classification (department, class, location) mappings for utility invoices.

Validate in a sandbox account before enabling production routing rules. Note that Oracle is steering new integrations toward OAuth 2.0; Nectar supports both, so choose the method your security model prefers.

## FAQ

<AccordionGroup>
  <Accordion title="Which NetSuite editions are supported?">
    Any NetSuite account where you can enable SuiteTalk REST web services and provision integration credentials (TBA or OAuth 2.0) with permission to create vendor bills. Use your production or sandbox account ID as appropriate — each has its own account-specific SuiteTalk domain.
  </Accordion>

  <Accordion title="Can Nectar link a vendor bill to a purchase order?">
    Yes. Where a utility bill maps to an existing purchase order, Nectar can create the vendor bill via the PO transform endpoint so the PO-to-bill relationship is preserved for three-way matching. Discuss PO matching requirements during onboarding.
  </Accordion>

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

## Related pages

* [ERP integrations overview](/platform/bill-pay/erp-integrations/overview)
* [Destinations](/platform/bill-pay/destinations)
* [Bill audit](/platform/bill-pay/decisions)