> For the complete documentation index, see [llms.txt](https://docs.xorosoft.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.xorosoft.com/xoroerp-1/admin/company/payment-term-centre/payment-term-centre-fields.md).

# Payment Term Centre Fields

The Payment Term Centre offers users different options to facilitate users with processes related to Payment Terms. It provides direct access to the **Payment** **Term** module facilitating the modification process of Payment Terms. 

### Header Options

**Batch Delete:** This allows users to Batch Delete the selected Payment Terms. This option comes in handy in case a specific term has become obsolete or is not required anymore.

### Header Icons

These functionalities are designed to meet diverse needs, ensuring users experience seamless navigation and effective management of customer information.

1. **Refresh:**
   * This empowering functionality allows users to refresh search results based on selected criteria, ensuring the displayed information is consistently up-to-date.
2. **Save:**
   * The Save feature preserves updated user interface (UI) settings, delivering a personalized and consistent experience for future interactions within the module.
3. **Advanced Search:**
   * Elevating customer information retrieval, the Advanced Search option enables users to conduct sophisticated searches by specifying criteria like Column Name, Operator, and Value. This facilitates precise and tailored information retrieval.
4. **Columns:**
   * Representing customizable criteria, Columns empower users to refine their searches further. The options in the dropdown menu for Columns dynamically adjust based on the active tab, ensuring relevance and convenience.

**Options in Columns Dropdown Menu:**

* **Name:** This is the name of the payment term.
* **Type**: This shows the type of payment term. This field simply acts as a label, it does not affect the calculated discount and due date.
* **Is Active:** This shows whether the Payment Term is Active or not.
* **Discount Days**: This shows within how many days the invoice or bill is eligible for a discount.
* **Discount Factor**: This shows the amount of discount given from the original amount due (e.g. 0.1 is 10% off).
* **Discount Month Offset**: Offset the bill or invoice’s discount date by these many months.
* **Net Days**: This field shows after how many days the invoice or bill is due.
* **Net Month Offset**: Offset the bill or invoice’s due date by these many months.
* **Due Date**: This is the due date for the Bill or Invoice.
* **Discount Date**: This is the date for the discount.
* **Customer Message**: This is the message for the customer in case of an Invoice.
* **Vendor Message**: This is the message for the vendor in case of a Bill.

5. **Download:**

* This versatile feature allows users to export and download data in various file formats, providing a summarized overview for quick reference. Options include CSV, TXT, MS-Word, MS-Excel, PDF, and MS-Excel(.xlsx), catering to diverse user preferences and use cases.


---

# 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.xorosoft.com/xoroerp-1/admin/company/payment-term-centre/payment-term-centre-fields.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.