> 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/charted-configuration/payment-automation/configuration-overview.md).

# Configuration overview

This page covers turning Payment Automation on, where each setting lives, how Payment Automation works inside NetSuite, and what to do before go-live.

## Turning Payment Automation on

Before you start:

* Log in to NetSuite as an Administrator, or with a role that has equivalent full access.
* Your NetSuite account must have access to Payment Automation. If it does not, contact Charted support at <softwaresupport@charted.com>.
* Subsidiaries, the chart of accounts, and vendor and employee records must already exist in NetSuite.

Open **Charted > AP Automation > Settings**. Under **Features**, find **Payment Automation** and press **Enable**.

<figure><img src="https://4244775538-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FDi74GwuQpTYzdGbZQFpz%2Fuploads%2FSh0idstcaVnderJM5JT4%2Fpa-settings-features-enabled.png?alt=media" alt="Settings, Features, with Payment Automation enabled"><figcaption></figcaption></figure>

Payment Automation then appears in the Charted navigation, on **Home** and on **Settings**.

## Where the settings live

| To change                                                            | Page                                                                                                                              | Where                                                                        |
| -------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------- |
| A business entity, its verification, contact details, prefix or logo | [Business entities](https://docs.charted.com/ap-automation/charted-configuration/payment-automation/business-entities.md)         | Charted > AP Automation > Settings > Payment Automation > Business Entities  |
| Whether an entity pays by ACH, check or both                         | [Payment methods](https://docs.charted.com/ap-automation/charted-configuration/payment-automation/payment-methods.md)             | Business Entities, then the entity                                           |
| A bank account, its verification or check numbering                  | [Funding sources](https://docs.charted.com/ap-automation/charted-configuration/payment-automation/funding-sources.md)             | Charted > AP Automation > Settings > Payment Automation > Funding Sources    |
| Which general ledger (GL) account draws on which bank account        | [Linking bank accounts](https://docs.charted.com/ap-automation/charted-configuration/payment-automation/linking-bank-accounts.md) | Charted > AP Automation > Settings > Payment Automation > Link Bank Accounts |
| Who can do what                                                      | [User permissions](https://docs.charted.com/ap-automation/charted-configuration/payment-automation/user-permissions.md)           | Charted > AP Automation > Settings > Permissions                             |
| Payees and invitations                                               | [Importing payees](https://docs.charted.com/ap-automation/charted-configuration/payment-automation/importing-payees.md)           | Charted > AP Automation > Home, then **Payees**                              |
| Exclusions and remittance                                            | [General settings](https://docs.charted.com/ap-automation/charted-configuration/payment-automation/general-settings.md)           | Charted > AP Automation > Settings > Payment Automation > Settings           |

## How Payment Automation works inside NetSuite

Payment Automation allows you to pay vendors and employees, including expense report reimbursements, by ACH (Automated Clearing House) transfer or outsourced check from within NetSuite. Payment Automation collects, encrypts and stores payee data securely.

| NetSuite controls                                                                          | Payment Automation controls                                    |
| ------------------------------------------------------------------------------------------ | -------------------------------------------------------------- |
| Creating bill payments in **Pay Bills**, which works as it does without Payment Automation | Picking up each saved bill payment and holding it for release  |
| The bank account (GL account) on the bill payment                                          | Which funding source that GL account draws on                  |
| Vendor and employee records                                                                | Payee onboarding, payment methods and preferences              |
| Voiding a bill payment, which reopens its bills                                            | Releasing, cancelling and tracking payments                    |
| NetSuite's own inactive status on a vendor                                                 | Payment Automation's own payee deactivation, which is separate |

Payment Automation writes back to the NetSuite bill payment: **Charted Release Status** and **Charted Transfer Status** on the **Custom** subtab, the ACH ID at the end of the **Transaction Memo**, and the check number for outsourced checks.

A bill payment never reaches Payment Automation if its GL account is not linked to a funding source, or if one of the exclusions in [General settings](https://docs.charted.com/ap-automation/charted-configuration/payment-automation/general-settings.md) applies.

## Before go-live

* **Configure in Production.** Business entities, funding sources and verification do not carry over from Sandbox, so everything done there must be repeated, including identity verification. Sandbox simulates onboarding and verification. No micro-deposits are sent, and you can enter any amounts to complete verification. A small Sandbox setup with a single business entity or funding source is enough to get familiar with the product. See [Can we test Payment Automation in Sandbox?](https://docs.charted.com/ap-automation/charted-faqs/payment-automation/can-we-test-payment-automation-in-sandbox.md)
* **Create your Charted account in each environment.** Install the Charted SuiteApp and create a Charted account in both Sandbox and Production. Accounts are not shared between environments.
* **Set up DKIM.** Charted sends email through NetSuite, so you must set up DomainKeys Identified Mail (DKIM) in NetSuite before user acceptance testing. Without it, email delivery is intermittent. See SuiteAnswers for step-by-step instructions for setting up DKIM.
* **Authorize Charted's originator ID with your bank.** Your bank must allow ACH debits from originator ID 945440567 followed by one blank space. If it does not, your payments fail from the first day. This is the most common cause of failed payments in production. See [Funding sources](https://docs.charted.com/ap-automation/charted-configuration/payment-automation/funding-sources.md).
* **Assign permissions,** including balance transfer permissions, before your first payment run.
* **Send a test check** if you use outsourced checks. See [Payment methods](https://docs.charted.com/ap-automation/charted-configuration/payment-automation/payment-methods.md#testing-a-check-before-go-live).

## What to change yourself and what to raise with us

| Change it yourself                                          | Contact Charted Support                                      |
| ----------------------------------------------------------- | ------------------------------------------------------------ |
| Permissions, payees, invitations, preferred payment methods | Changing the next check number on an existing funding source |
| General settings, remittance columns and logos              | Cancelling an ACH payment more than 60 seconds after release |
| Adding business entities and funding sources                | Verification that has not completed                          |

Email <softwaresupport@charted.com>.

## Next

[Business entities](https://docs.charted.com/ap-automation/charted-configuration/payment-automation/business-entities.md)


---

# 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/charted-configuration/payment-automation/configuration-overview.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.
