> 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-faqs/invoice-ai/how-do-i-identify-vendors-for-auto-creation.md).

# How do I identify Vendors for Auto-Creation?

Charted's SuiteQL Playground lets you run a pre-built query that surfaces vendors your environment has already identified as strong candidates for touchless invoice processing (auto-creation). The query looks back 180 days and returns a count of eligible bills per vendor, broken out by whether they were tied to a purchase order. Use this data to decide which vendors to enable for auto-creation.

{% hint style="info" %}
**Prerequisites:** You must be logged in to NetSuite as an Administrator, and the SuiteQL Playground feature must be enabled in Charted. If you have not enabled it yet, follow Steps 1–2 below.
{% endhint %}

{% stepper %}
{% step %}

## Enable the SuiteQL Playground

If SuiteQL Playground is already enabled in your account, skip to [Step 3](#step-3-run-the-touchless-vendor-query).

1. Navigate to **Charted > AP Automation > Settings**. Make sure you are in the **Administrator** role.
2. On the Settings page, locate **SuiteQL Playground** under the **My Features** section in the middle of the screen.
3. Click **Enable** and confirm when prompted.

> **Optional:** To allow other users to run queries in the SuiteQL Playground, go to the **Permissions** tab in the sidebar and grant the **Use SuiteQL Playground** permission to the appropriate employees or roles.
> {% endstep %}

{% step %}

## Open the SuiteQL Playground

1. Return to the Charted homepage via **Charted > AP Automation > Home** in the NetSuite Center.
2. Click **SuiteQL Playground** in the Charted sidebar. It appears as the last item in the sidebar.
   {% endstep %}

{% step %}

## Run the touchless vendor query

1. In the SuiteQL Playground, paste and run the following query:

```sql
SELECT
  e.entityid                            AS vendor_name,
  COUNT(DISTINCT v.id)                  AS total_touchless_bills,
  COUNT(DISTINCT CASE
    WHEN ptll.previousdoc IS NOT NULL
    THEN v.id END)                      AS touchless_with_po,
  COUNT(DISTINCT CASE
    WHEN ptll.previousdoc IS NULL
    THEN v.id END)                      AS touchless_without_po
FROM transaction v
  INNER JOIN CUSTOMRECORD_SW_INVOICE_DOC doc
    ON doc.id = v.custbody_sw_vendor_invoice_doc
  INNER JOIN entity e
    ON e.id = v.entity
  LEFT JOIN transactionline vl
    ON vl.transaction = v.id
    AND vl.mainline = 'F'
  LEFT JOIN PreviousTransactionLineLink ptll
    ON ptll.nextdoc = vl.transaction
    AND ptll.nextline = vl.id
    AND ptll.linktype = 'OrdBill'
WHERE
  v.type = 'VendBill'
  AND v.createddate >= SYSDATE - 180
  AND doc.custrecord_sw_touchless_invoice = 'T'
GROUP BY e.entityid
ORDER BY total_touchless_bills DESC
```

2. Review the query results that appear at the bottom of the screen. The results show:
   * **Vendor Name** – the vendors Charted has identified as candidates.
   * **Total Touchless Bills** – bills in the past 180 days where no manual changes were made before saving.
   * **Touchless with PO** – touchless bills tied to a purchase order.
   * **Touchless without PO** – touchless bills without a purchase order.

{% hint style="warning" %}
If the query returns no results, or you see an error message, there may be no vendor bills in the last 180 days that meet the touchless criteria. This is expected for new environments or accounts with low invoice volume.
{% endhint %}
{% endstep %}

{% step %}

## Export and act on the results

1. To share results with someone who does not have access to the SuiteQL Playground, click **Export to CSV**.
2. Use the results to decide which vendors to enable for auto-creation:
   * **Auto-Create PO-Backed Bills:** Enable this global setting to automatically generate bills when invoice quantities match what is available for billing on a purchase order.
   * **Auto-Create Non-PO Bills (per vendor):** Enable this on a vendor-by-vendor basis for vendors with consistent, recurring invoices such as utilities or subscriptions.
     {% endstep %}
     {% endstepper %}

### Related topics

* [Invoice AI](https://docs.charted.com/ap-automation/charted-features/invoice-ai) – feature overview and workflow summary
* [Advanced Invoice AI Settings](https://docs.charted.com/ap-automation/charted-configuration/invoice-ai/advanced-invoice-ai-settings) – OCR defaults, PO settings, and touchless configuration
* [Configuring Vendor Override Settings](https://docs.charted.com/ap-automation/charted-configuration/invoice-ai/configuring-vendor-override-settings) – vendor-specific auto-creation behavior
* [Charted Support](https://docs.charted.com/ap-automation/charted-support) – if you need technical or configuration help


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.charted.com/ap-automation/charted-faqs/invoice-ai/how-do-i-identify-vendors-for-auto-creation.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.