> 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/accrual-automation/general-ledger-segmentation.md).

# General Ledger Segmentation

### Abstract <a href="#id-83p6je90qdbe" id="id-83p6je90qdbe"></a>

*General Ledger Segmentation* within *Accrual Automation* allows administrators to include or exclude specific line-level segments — such as Department, Class, Location, or custom fields — in their accrual processes. An example use case would be organizations that need to track a custom “Deal” field at the line level for revenue recognition or detailed expense tracking.

This article explains how to configure *General Ledger Segmentation* so that you can manage which line-level segments (standard or custom) appear on the *Accrual Worksheet*.

### Adjusting the GL Segmentation for the Accrual Worksheet <a href="#ac2ufrdogplh" id="ac2ufrdogplh"></a>

Before customizing the *Accrual Worksheet*, it is essential to understand that *Accrual Automation* pulls segment data directly from the line-level fields. By default  Department, Class, Location will be displayed. If you want only relevant segments — like a subset of Department, Class, Location, or custom fields — to appear on your accruals, you must configure them here.

To configure **General Ledger Segmentation** follow these steps:<br>

1. First, you have to access the **Charted Platform Features,** then click the **Settings** link under the **Accrual Automation** section:\ <br>

   <div align="left"><figure><img src="https://4244775538-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FDi74GwuQpTYzdGbZQFpz%2Fuploads%2FZLkBVSIZsTVXLjm89PgH%2Fimage.png?alt=media&amp;token=c3328f31-1fe6-489b-9f18-00df99186cba" alt=""><figcaption></figcaption></figure></div>

   <br>
2. Once the **Accrual Automation** **Settings** screen is opened, locate the **GL Segmentation** under **Advanced Settings**:\ <br>

   <div align="left"><img src="https://4244775538-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FDi74GwuQpTYzdGbZQFpz%2Fuploads%2Ffd8WAfxKErQ18w9Xekc4%2Fimage.png?alt=media&amp;token=c01dfb8c-7c71-43d0-8fa4-941fd6c87a1d" alt="
   "></div>

   \
   Note: When you see that the **GL Segmentation** setting is blank, recognize that it will default to *NetSuite’s* standard segments — **Department**, **Class**, and **Location** — on the **Accrual Worksheet**.<br>
3. To remove a particular segment (e.g., **Location**), enter only the segments you want to appear in the **GL Segmentation** setting field:<br>
4. Now, to add a custom segment (e.g., a custom field named “Deal”), ensure that it’s available as a line-level field in *NetSuite* before specifying it in the **GL Segmentation** setting:\ <br>

   <div align="left"><img src="https://4244775538-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FDi74GwuQpTYzdGbZQFpz%2Fuploads%2FQPGjgz2bEmtXMNRXpAJE%2Fimage.png?alt=media&amp;token=d6d7ae78-fcd2-4f7e-8c4c-998ba8bd9785" alt="
   "></div>
5. After you’ve updated the **GL Segmentation** setting with the final list of segments, click the **Submit** button to confirm your changes.

This concludes the process of configuring *General Ledger Segmentation* within *Accrual Automation* 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 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/accrual-automation/general-ledger-segmentation.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.
