> 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/approval-automation/installing-the-approval-automation-bundle.md).
# Installing the Approval-Automation Bundle
### **Abstract**
To streamline vendor bill approvals in *NetSuite*, administrators must install the *Charted* **Approval-Automation Bundle**. This bundle enables automated routing of vendor bills for internal review and sign-off, reducing manual oversight and improving accountability. The feature is especially useful for finance departments that manage a high volume of vendor bills or require role-based approval logic before payment can proceed.
This article outlines the installation process for the *Approval-Automation Bundle*.
### **Installing the Approval-Automation Bundle from the SuiteBundler**
To enable vendor bill approval automation, administrators must install the **Charted Approval-Automation Bundle** using *NetSuite's SuiteBundler* tool. The steps below guide you through locating the correct bundle using its ID, initiating installation, handling confirmation prompts, and verifying the bundle’s successful deployment. This process ensures that the automation feature is available and functional before configuration begins.
Follow these steps to install the **Approval-Automation** bundle:
1. To begin the installation, make sure you are logged into *NetSuite* with an **Administrator** role or an equivalent full-access role:\
2. From the *NetSuite* home screen, go to **Customization** at the top navigation bar, hover over **SuiteBundler**, and click **Search & Install Bundles**:\
3. When the **Search and Install Bundles** page opens, locate the **Keywords** field and initiate the search. Type **310718** and click the **Search** button:\
\
\
Then, after the search is complete, click the **Charted Approval Automation** bundle from the results:\
4. Once the **Bundle Details** page of the **Charted: Approval Automation** appears, click the **Install** button to begin the installation process:\
\
\
When prompted with a confirmation pop-up, click **OK** to continue:\
5. After confirming, wait for the **Preview Bundle Install** screen to appear:\
6. To finalize the installation, click **Install Bundle,** and click **OK** once more in the follow-up pop-up window:\
7. Once the installation starts, you may wait for the automatic page refresh or click the **Refresh** button manually to view the update of the **Installed Bundles** page:\
8. To verify a successful installation, look for a green check mark (✔️) on the **Status** column of **Charted: Approval Automation** bundle:\
\
This concludes the installation of the **Approval-Automation bundle**.
---
# 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/approval-automation/installing-the-approval-automation-bundle.md?ask=&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.
