> 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/understanding-payment-terms.md).

# Understanding Payment Terms

Payment terms dictate when you need to pay a bill or invoice completely. Essentially, payment terms outline when you need to make a payment, taking into account things like discounts and due dates. These help to manage the cash flow efficiently and establish clear expectations regarding financial transactions.

For example, 'NET 30' payment term indicates that the full payment is due within 30 days.

### Payment Term Types

Payment terms are often denoted in a standardized format, typically comprising a combination of numbers and abbreviations. Let's break down some common payment terms:

<table><thead><tr><th width="307">Payment Term</th><th>Description</th></tr></thead><tbody><tr><td>COD</td><td>COD, or Cash On Delivery term means that the payment is required at the time of delivery. If the payment is not made, the goods are not delivered.</td></tr><tr><td>CIA</td><td>CIA, or Cash In Advance term means that the payment must be made before goods or services are provided. This term is often used to reduce credit risk.</td></tr><tr><td>Net 30, Net 45, Net 60, Net 90, etc.</td><td>These payment terms dictate that the full payment must be made within 30, 45, 60, or 90 days, respectively.</td></tr><tr><td>2% Net 30</td><td>This payment term means that if the payment is made within 30 days, you receive a 2% discount.</td></tr><tr><td>2% 30 Net 60</td><td>This payment term means that if the payment is done within 30 days, you receive a 2% discount, and the full payment has to be made within 60 days.</td></tr><tr><td>FOLLOWING 25TH</td><td>This payment term dictates that the payment should be made by the 25th day of the month following the issue date. For example, if an invoice is issued on any day of April, the full payment would be due by May 25th.</td></tr><tr><td>2% 20 MONTH FOLLOWING</td><td>This payment term means that if the payment is done within 20 days after the next month from when you got the invoice or bill, you get a 2% discount. For example, if you got the bill in April, you'd need to pay by May 20th to get the discount. If you pay later, you don't get the discount, and you have to pay the full amount of the bill.</td></tr><tr><td>Split Term</td><td><p>Used when invoices or bills must be divided into multiple scheduled payments. The system creates a parent invoice or bill and automatically generates child invoices or bills based on the defined split structure. For parent invoices, a non-inventory offset line is added to balance the transaction. For parent bills, an offset expense line is added in the <strong>Expenses</strong> tab.</p><p></p><p>In linked (child) invoices and bills, users are restricted from modifying item and expense lines to maintain consistency with the parent document. However, users can add and update <strong>Tax Adjustment</strong> lines and modify textual fields such as <strong>Memo</strong>.</p></td></tr></tbody></table>

{% hint style="info" %}
The **Split Term** payment term automatically divides an invoice or bill into multiple scheduled child invoices or bills based on the configured split structure (for example, 2-part split, 3-part split, etc.). This is a payment-term-based split, not a manual "Split Invoice" action from the Invoice screen.
{% endhint %}


---

# 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.xorosoft.com/xoroerp-1/admin/company/payment-term/understanding-payment-terms.md?ask=<question>&goal=<endgoal>
```

`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.
