> 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/invoice-intake.md).

# Invoice intake

This page covers the two intake paths you set up: the email capture address, which lets vendors and staff send invoices without logging in, and e-invoice subscriptions, which let suppliers send electronic invoices (e-invoices) straight to NetSuite. Uploading by drag and drop needs no setup beyond [permissions](https://docs.charted.com/ap-automation/charted-configuration/invoice-ai/permissions.md).

## Email intake

You enable email intake through a NetSuite plug-in, separately from the Invoice AI settings. You need the NetSuite Administrator role, and the plug-in appears only once the Charted SuiteApp is installed.

### Turning on the capture address

1. Go to **Customization > Plug-ins > Manage Plug-ins**.
2. In the **Email Capture** plug-in section, find **Automate OCR Email Upload**.
3. Enable it and press **Save**.
4. Copy the email address shown below the label.

{% hint style="warning" %}
Your account may show several capture addresses, one for each plug-in. Copy the address shown for **Automate OCR Email Upload**. Invoices sent to any other address will not reach Invoice AI.
{% endhint %}

That address is your capture address. Invoice AI adds anything emailed to it to the Bills Inbox, provided the file is a PDF or a type you have allowed in **Allowed File Types** on [Invoice AI settings](https://docs.charted.com/ap-automation/charted-configuration/invoice-ai/invoice-ai-settings.md).

### Distributing the address

NetSuite generates an address that is a string of numbers and letters, so give your vendors something readable instead. Ask your IT team to set up one of these:

| Approach        | How it works                                                                                           |
| --------------- | ------------------------------------------------------------------------------------------------------ |
| Forwarding rule | Your existing accounts payable (AP) mailbox forwards messages with attachments to your capture address |
| Alias           | A readable address points at your capture address                                                      |

{% hint style="warning" %}
Your capture address differs between sandbox and production. Repoint your forwarding rule or alias when you move to production, or your invoices will keep arriving in the wrong environment.
{% endhint %}

Engage your IT team early. Setting up the forwarding rule is the step most likely to delay your go-live.

### Testing email intake

1. Email a Portable Document Format (PDF) invoice to your capture address.
2. Open the Bills Inbox and confirm Invoice AI added it as a new row.
3. Email a file of a type your account has not allowed, such as a ZIP archive, to the same address.
4. Confirm Invoice AI emailed the employee nominated in **Email Exception Notifications** on [Invoice AI settings](https://docs.charted.com/ap-automation/charted-configuration/invoice-ai/invoice-ai-settings.md). Invoice AI does not add the unsupported file to the Bills Inbox.

Invoice AI sends that notification for any email it cannot process: one carrying a file type your account has not allowed, and one with no attachment at all.

{% hint style="info" %}
In a sandbox account Invoice AI generates exception emails but NetSuite does not send them. This is standard NetSuite behavior for this kind of email, not a fault. To confirm one was generated, go to **Setup > Company > Sent Email** and find the notification. It records the file name of the unsupported attachment.
{% endhint %}

When an expected invoice never arrives, see [Why didn't my invoice appear in the inbox?](https://docs.charted.com/ap-automation/charted-faqs/invoice-ai/why-didnt-my-invoice-appear-in-the-inbox.md)

## Invoices from vendors who use NetSuite

NetSuite's own inbound email plug-in blocks email sent from another NetSuite account, to stop two NetSuite accounts looping messages between them. So an invoice a vendor sends straight from their NetSuite account can be rejected before it reaches your capture address.

The fix is an intermediate mailbox outside NetSuite. Your vendors send invoices to that mailbox, and it forwards them to your capture address.

### In Outlook

Create a rule that automatically forwards to your capture address every message carrying the **X-NetSuite** header. Checking for that header forwards only messages that came from NetSuite, on the assumption that your other mail is already forwarded by a separate rule.

### In Gmail

Gmail's built-in forwarding does not deliver messages that came from a NetSuite account, so use a short Google Apps Script instead.

1. Confirm your Gmail inbox already forwards email to your capture address. Set that up first if it does not.
2. At [script.google.com](https://script.google.com/), create a project named **Forward NetSuite Emails**.
3. Replace the default code with the script below, changing `netsuite-inbound-email@your-account.email.netsuite.com` to your capture address.
4. In the Apps Script editor, press **+** next to **Services** and add the **Gmail API**.
5. Press **Run** to test the script. When asked to authorize it, press **Review permissions** and select your account. If Google warns that the app is unverified, press **Advanced** and continue to **Forward NetSuite Emails**.
6. Open **Triggers** and press **Add Trigger**. Choose the function **forwardNetSuiteEmails**, the deployment **Head**, the event source **Time-driven**, the type **Hours timer**, and the interval **Every hour**.

```javascript
function forwardNetSuiteEmails() { 

  var forwardAddress = "netsuite-inbound-email@your-account.email.netsuite.com"; 

  var forwardedLabel = GmailApp.getUserLabelByName("Forwarded") || GmailApp.createLabel("Forwarded"); 

  var threads = GmailApp.search("in:inbox newer_than:1d -label:Forwarded"); 

  threads.forEach(function(thread) { 

    thread.getMessages().forEach(function(message) { 

      if(message.getHeader("X-NetSuite")) { 

        var fromEmail = message.getFrom(); 

        var originalSubject = message.getSubject(); 

        var newSubject = originalSubject + " (from: " + fromEmail + ")"; 

        message.forward(forwardAddress, { subject: newSubject }); 

        forwardedLabel.addToThread(thread); 

      } 

    }); 

  }); 

} 
```

Every hour, the script looks for messages from NetSuite received in the past 24 hours, forwards them to your capture address, and labels them **Forwarded**. It skips anything already labeled, so nothing is forwarded twice.

## E-invoice subscriptions

An E-Invoice Subscription registers one legal entity to receive e-invoices through the Pan-European Public Procurement Online (PEPPOL) network. Your organization can receive e-invoices for an entity as soon as Charted has verified its subscription.

E-invoicing is available for entities registered in Belgium, Denmark, Finland, France, Germany, Italy, the Netherlands, Norway, Poland, Romania and Sweden. Finnish entities receive on the PEPPOL network, not on the local Finvoice network. For the identifiers each country accepts and their expected formats, see [Which countries are supported for e-invoicing?](https://docs.charted.com/ap-automation/charted-faqs/invoice-ai/which-countries-are-supported-for-e-invoicing.md)

### What to gather for each entity

Each NetSuite subsidiary that will receive e-invoices needs its own subscription.

| Item                        | Detail                                                                          |
| --------------------------- | ------------------------------------------------------------------------------- |
| Legal business name         | As it appears in the entity's value added tax (VAT) or corporate registration   |
| Registered business address | As it appears in that registration                                              |
| Network identifier          | Usually the VAT number, including its country code prefix, such as BE0123456789 |

{% hint style="info" %}
Your details must match the entity's official registration. Small formatting differences in the name and address are accepted, but the VAT number must be exact.
{% endhint %}

### Creating a subscription

1. Open **Charted > AP Automation > Settings**, then press **E-Invoicing** in the left navigation, under **Invoice Automation**.
2. On the **E-Invoice Subscriptions** list, press **Create Subscription** at the top right.
3. In **Subsidiary**, select the NetSuite subsidiary for the legal entity you are registering.
4. In **Legal Business Name**, enter the entity's full registered legal name. Abbreviations such as BV, NV or Ltd are accepted.
5. In **Country of Registration**, select the country where the entity is registered. This decides which identifier types you can choose next.
6. Enter the registered address: **Registered Address**, **Address Line 2** if needed, **City / Locality**, **State / Province / Region** if applicable, and **Postal Code**.
7. In **Network Identifiers**, choose the identifier **Type**, such as VAT, enter the **Identifier**, and press **Add Identifier**.
8. Press **Save**.

{% hint style="warning" %}
Enter the legal name the VAT registry holds, not a trading name. Charted checks the name against public VAT registries, and a name the registry does not recognize fails verification.
{% endhint %}

At least one network identifier is required. If you are unsure which identifier type to use, ask your Charted Implementation Consultant.

Where your address can be written in more than one language, such as French or Dutch in Belgium, either version is accepted.

### Verification and statuses

Charted checks your details against public VAT registries, usually within one business day.

| Status       | What it means                                                                                                    |
| ------------ | ---------------------------------------------------------------------------------------------------------------- |
| Not Verified | Submitted and waiting for Charted's review                                                                       |
| Verified     | Your details are confirmed and the entity is registered on the PEPPOL network. Suppliers can send it e-invoices. |

In most countries, suppliers can send e-invoices as soon as the subscription shows **Verified**. In France, registrations take effect the next day.

To confirm the registration yourself, search for the entity's name or identifier in the public [Peppol Directory](https://directory.peppol.eu/public/locale-en_US/menuitem-search).

If Charted cannot verify your details, your Implementation Consultant contacts you with what needs correcting. You can update the subscription and save it again at any time.

{% hint style="info" %}
If the status has not changed one business day after you submit, contact your Charted Implementation Consultant or email <softwaresupport@charted.com>. See [What do I do if my E-Invoice Subscription cannot be verified?](https://docs.charted.com/ap-automation/charted-faqs/invoice-ai/what-do-i-do-if-my-e-invoice-subscription-cannot-be-verified.md)
{% endhint %}

Once an entity is registered, reviewers handle the e-invoices suppliers send it like any other invoice. See [Adding invoices to the inbox](https://docs.charted.com/ap-automation/charted-features/invoice-ai/adding-invoices-to-the-inbox.md).

## Next

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