> 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/invoice-ai/inbox-labels-and-columns.md).

# Inbox labels and columns

This page covers how you set up the Bills Inbox for your team: the labels reviewers can apply to documents, and the columns every reviewer sees. You set both once, for the whole account.

Both live on the **Inbox Configuration** tab of the Invoice AI Settings page. Open **Charted > AP Automation > Settings**, press **Settings** in the left navigation under **Invoice Automation**, then open the **Inbox Configuration** tab.

You need the NetSuite Administrator role to change either. Other users see your configuration but cannot change it.

{% hint style="warning" %}
Nothing takes effect until you press **Save** at the bottom of the Invoice AI Settings page.
{% endhint %}

## Labels

A label is a tag your team applies to a document to record something Invoice AI cannot know, such as that it is urgent or missing a purchase order (PO). A status says what Invoice AI has done with a document; a label says what your team has decided about it. A document can carry any number of labels.

No labels exist until you create them.

### Creating a label

1. In the **Label Configuration** section, press **Add Label**.
2. Enter a name of up to 100 characters.
3. Press the check mark to add the label, or the **X** to discard it.
4. Repeat for each label, then press **Save** at the bottom of the page.

Invoice AI assigns each label a color from a fixed palette. You cannot choose or change it.

Keep names short. Long names are cut off when they appear on an inbox row.

### Renaming and deactivating a label

<table><thead><tr><th width="120">Control</th><th>What it does</th></tr></thead><tbody><tr><td>Pencil</td><td>Renames the label. It keeps its color and stays on documents that already carry it.</td></tr><tr><td>Toggle</td><td>Deactivates or reactivates the label</td></tr></tbody></table>

Deactivating removes a label from the picker, so no one can apply it to new documents. It stays on documents that already carry it.

{% hint style="info" %}
Renaming a label changes it everywhere, including on documents tagged in the past. If a label's meaning has changed, not just its wording, deactivate it and create a new one so earlier tagging stays accurate.
{% endhint %}

### Choosing your labels

We recommend a small set, applied consistently, that describes exceptions: a missing purchase order, a disputed amount, an expedited payment. Do not create labels that repeat a status Invoice AI already shows, such as Ready or Duplicate.

For how reviewers apply labels and filter by them, see [Managing your inbox](https://docs.charted.com/ap-automation/charted-features/invoice-ai/managing-your-inbox.md).

## Columns

Column configuration decides which columns appear in the Bills Inbox, and in what order, for every user. It applies to the **For Review** and **Processed** tabs, not to the Not Submitted or Not Approved screens.

### Showing, hiding and reordering columns

The **Column Configuration** section lists every available column in its current order.

* Turn a column's toggle off to hide it for everyone. Its data is unaffected, and you can show it again at any time.
* Drag a column to a new position. Columns appear from left to right in the order listed.

Press **Save** at the bottom of the page.

We recommend putting the columns your team acts on most, such as **Vendor**, **Bill Status** and **Invoice #**, first so they are visible without scrolling sideways, and hiding the ones nobody uses.

### Adding a custom column

Add a custom column and choose a field from the picker. You can hide and reorder it like any other column.

| Source record               | Fields it offers                                                             |
| --------------------------- | ---------------------------------------------------------------------------- |
| Automate OCR Vendor Invoice | Fields on the invoice document record, including values Invoice AI extracted |
| Vendor                      | Fields on the vendor record, such as payment terms or vendor category        |
| Purchase Order              | Fields on the linked purchase order                                          |

The picker shows which record each field comes from, so you can tell fields with similar names apart. A custom column is empty for any document with no value in that field.

{% hint style="info" %}
You can sort by a custom column but not filter by it. To let your team pick out a group of documents, use a label instead.
{% endhint %}

Fields on any other record cannot be added. If your team needs one, contact your Charted Customer Success Manager.

### Resetting columns to the defaults

Press **Reset to Defaults** in **Column Configuration**, then press **Save**. This restores the original columns and order, and removes any custom columns you added.

## Next

[AI Directions](https://docs.charted.com/ap-automation/charted-configuration/invoice-ai/ai-directions.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/invoice-ai/inbox-labels-and-columns.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.
