> 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/bill-custom-date-field.md).
# Bill Custom Date Field
### Abstract
*Accrual Automation* in *NetSuite* ensures that costs are recognized accurately, reflecting an organization’s true financial obligations at any given point. Administrators will want to configure accrual settings to define how vendor bill dates are captured, particularly if a custom date field is used instead of *NetSuite’s* standard transaction date.
This article guides you through the configuration of *Accrual Automation* related to *GL Account Types* and the *Bill Custom Date Field*.
### Configuring the Bill Custom Date Field
Some organizations track bill dates in a custom field rather than using *NetSuite’s* default *Tran Date*. This preference often stems from specialized reporting requirements or unique internal processes. By specifying a custom date field for accrual calculations, you ensure that entries align with your internal timeline for recognizing transactions.
To configure the **Bill Custom Date Field**, here are the steps to follow:
1. To rely on a custom bill date field instead of the standard transaction date, locate the **Bill Custom Date Field** setting within the **Advanced Settings** section:\
2. Next, if your organization stores the bill date in a user-defined field, enter the field ID of that custom date field into the corresponding **Bill Custom Date Field** box:
3. If you prefer to revert to *NetSuite’s* standard **trandate**, simply clear the **Bill Custom Date Field** box and click the **Submit** button so that the accrual process defaults back to the standard date:
This concludes the process of configuring *GL Account Types* and *Bill Custom Date Field* within *Accrual Automation* in *Nesuite.*
---
# 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/bill-custom-date-field.md?ask=&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.
