> For the complete documentation index, see [llms.txt](https://docs.agilecase.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.agilecase.com/administrator-documentation/company-settings/adding-new-payment-terms.md).
# Adding new payment terms
This lesson will cover adding new payment terms as well as editing existing terms on your system.
### Adding new payment terms
To add a new payment term, click the "Add Payment Term" button above the default setting.
### Entering new payment terms
Set a new payment term by filling in the text fields. You must name your new payment term and set a duration in days in which the invoice must be paid. Clicking the "Default" checkbox will make this new payment term your default for all cases.
### Editing existing payment terms
To edit an existing payment term, click the "Edit" button on the dropdown menu opposite the option you want to edit. You can then fill in the text boxes exactly as you would if creating a new payment term.
---
# 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.agilecase.com/administrator-documentation/company-settings/adding-new-payment-terms.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.