> For the complete documentation index, see [llms.txt](https://docs.charted.com/ap-automation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.charted.com/ap-automation/~/revisions/5mWfap1wj08VLBd4NLdS/charted-features/payment-automation/creating-bill-payments-in-netsuite.md).

# Creating Bill Payments in NetSuite

### Abstract <a href="#mqubdg22s2c9" id="mqubdg22s2c9"></a>

This guide explains how to create a bill payment in *NetSuite* that can be picked up by *Payments Automation*.

By following the correct sequence, users can ensure that payments flow seamlessly into the **Ready for Release** queue, reducing manual work and maintaining consistency with financial controls.

### Create a Bill Payment in NetSuite <a href="#gleswlaky37n" id="gleswlaky37n"></a>

Creating a bill payment in *NetSuite* triggers data into **Payments Automation**. By saving a standard payment record, the system recognizes the transaction and routes it to the **Ready for Release** queue for further processing.

Follow these steps to create a bill payment:<br>

1. First, hover over the **Transactions** menu, then go to **Payables** and select **Pay Bills**. This will take you to the **Bill Payments** page:\ <br>

   <div align="left"><figure><img src="https://4244775538-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FDi74GwuQpTYzdGbZQFpz%2Fuploads%2FUskicNJfcADjpbe6D4Od%2Fimage.png?alt=media&amp;token=98522b16-2e6a-491b-af05-97c99407b5b8" alt="" width="492"><figcaption></figcaption></figure></div>

   <div align="left"><figure><img src="https://4244775538-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FDi74GwuQpTYzdGbZQFpz%2Fuploads%2Fvf0kXmqE4QoaJnJZxTzl%2Fimage.png?alt=media&amp;token=f44186d7-7bb9-4069-983c-740df32279c5" alt=""><figcaption></figcaption></figure></div>

   \
   \
   **Payments Automation** listens for bill payment records created in *NetSuite***.** This is standard *NetSuite* functionality. It reflects how customers handle payments without Payments Automation — the solution simply sits on top of that process.<br>
2. Once on the **Bill Payments** page, all bills that have been saved and not tagged to a payment will appear in the **Customize** queue:\ <br>

   <br>

   <div align="left"><figure><img src="https://4244775538-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FDi74GwuQpTYzdGbZQFpz%2Fuploads%2FetmU60l7gEOqPzS3pRxA%2Fimage.png?alt=media&amp;token=9e25fa2e-48d8-4ed0-a409-cc9822253d55" alt=""><figcaption></figcaption></figure></div>

   <br>
3. As an example, create a **$1,000** payment tied to the vendor **Delta Consultants**, drawing from the **Checking** **GL** account, selected from the **ACCOUNT** drop down:\ <br>

   ![](https://4244775538-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FDi74GwuQpTYzdGbZQFpz%2Fuploads%2FqojeM8wIIl0WfFnvOgEO%2F3.png?alt=media\&token=18f8f32e-eccf-4397-9509-bf302e6492fc)

   \
   \
   Be sure to select an account that is tied to a funding source in **Charted**, assuming all configuration and implementation checklist steps have been completed. Additionally, confirm that the vendor is added to **Payments Automation**.\ <br>
4. Next, click the **Save** button to apply the changes:\ <br>

   <div align="left"><img src="https://4244775538-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FDi74GwuQpTYzdGbZQFpz%2Fuploads%2FTiSPX5s2MLP5FLXmqacl%2F4.png?alt=media&amp;token=a244a945-9316-47ef-81ae-efaaa4eee0e0" alt=""></div>

   <br>
5. After saving, **Payments Automation** will detect the event, and the **$1,000** payment will appear in the Ready for Release queue:\ <br>

   <div align="left"><img src="https://4244775538-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FDi74GwuQpTYzdGbZQFpz%2Fuploads%2FgkGyfbbmRws3rPOW4GMQ%2F5.png?alt=media&amp;token=2bdfaaa6-5f9d-4832-a3ce-cb187b221470" alt=""></div>

\
This concludes the process of creating bill payments.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.charted.com/ap-automation/~/revisions/5mWfap1wj08VLBd4NLdS/charted-features/payment-automation/creating-bill-payments-in-netsuite.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
