> For the complete documentation index, see [llms.txt](https://learn.withessential.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://learn.withessential.com/revenue/invoices/set-payment-terms-and-the-due-date-on-an-invoice.md).

# Set payment terms and the due date on an invoice

Every invoice needs payment terms before it can be saved. Choose them in the Payment Terms field, which sits below the Invoice date. You can pick Due on Receipt or a Net option (for example Net 15, 30, 45, 60, or 90), or enter a custom number of days.

The due date is calculated from the invoice date plus the terms and shown right below as the Overdue on date. Payment terms come from Customer Billing or Property Billing, so they're often filled in already, and changing the property can update them. To review the billing details that apply to this invoice, open the editor's **Context** tab (see [See property, customer, and deficiency context while quoting or invoicing](/revenue/quotes/see-context-while-quoting-or-invoicing.md)).

> **Where to find it:** On the open invoice, the Payment Terms field (below the Invoice date)

## Related guides

* [Add a line item to an invoice](/revenue/invoices/add-a-line-item-to-an-invoice.md)
* [Apply a discount to an invoice](/revenue/invoices/apply-a-discount-to-an-invoice.md)
* [Attach files or reports to an invoice](/revenue/invoices/attach-files-or-reports-to-an-invoice.md)
* [Can I reverse a payment I recorded?](/revenue/invoices/can-i-reverse-a-payment-i-recorded.md)
* [Charge a customer's saved card for an invoice](/revenue/invoices/charge-a-customers-saved-card-for-an-invoice.md)


---

# 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://learn.withessential.com/revenue/invoices/set-payment-terms-and-the-due-date-on-an-invoice.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.