> 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/whole-invoice-directions-translation-and-page-range-control.md).
# Whole-Invoice Directions: Translation & Page-Range Control
### Abstract
Whole-invoice directions allow administrators to apply broad instructions that affect the way *Invoice AI* interprets and processes an entire invoice. This is especially useful for cases where invoices require language translation, examples need to be provided to ensure proper interpretation, or when only specific pages of a multi-page document should be scanned. By using the *Whole-Invoice Directions* box and the *Page Start/Page End* fields, organizations can control the scope and behavior of invoice scanning before data is imported into *NetSuite*.
This article explains how to configure whole-invoice directions within the *Invoice AI* interface. It covers how to apply invoice-wide translation, control page range scanning, and prevent unnecessary supporting documents from being processed into invoice lines.
### Applying Whole-Invoice AI Directions
Whole-invoice directions allow you to define instructions that apply to the entire invoice during scanning. This includes tasks like translation, providing examples, and expected output to increase accuracy, and controlling which pages are included in the scan. These directions are entered in the **AI Directions** box on the **Create AI Direction** page.
Follow these steps to configure whole-invoice directions:
1. On the **Create AI Direction** page, locate the main box labeled **AI Directions**:\
\
\
This field is used to enter an overall prompt that applies to the entire invoice. One of the most common use cases for this box is invoice translation. You can translate content from the language in which the invoice is written into a different language.\
2. To apply this to the full invoice, enter a direction like **"Translate into Spanish"** in the **AI Directions** box:\
\
\
When the invoice is scanned, all of its text will be translated and brought into *NetSuite* in *Spanish*.\
3. In addition to translation, you can define where scanning starts and stops by using the **Page Start** and **Page End** fields:\
\
\
This is useful when invoices contain extra pages, such as supporting documentation after the first page. Scanning those additional pages can create extra lines in your invoice document when reviewed in *NetSuite* — lines you don’t actually need.
4. For example, with **Delta Consultants**, if you need only the first 2 pages of the invoice. In this case, scanning should stop after page 2. To stop scanning after the second page, enter **2** in the **Page End** field:\
This concludes the overview of how to apply whole-invoice AI directions in *NetSuite*.
---
# 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-configuration/invoice-ai/whole-invoice-directions-translation-and-page-range-control.md?ask=&goal=
```
`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.