> For the complete documentation index, see [llms.txt](https://kb.logicerp.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kb.logicerp.com/logic-erp-learning-hub-tutorials-and-best-practices/order-processing/delivery-note-against-purchase-orders/dn-against-po-configuration/dn-date-should-be-greater-than-the-challan-invoice.md).

# DN Date should be greater than the Challan/Invoice

**YouTube:** [How to Ensure the Delivery Note Date Is Greater Than the Challan or Invoice Date?](https://youtu.be/1pWSkwnOUMs)

## How to Ensure the Delivery Note Date Is Greater Than the Challan or Invoice Date?

In this tutorial, we will learn how to prevent users from entering a **Challan or Invoice Date** that is later than the **Delivery Note (DN) Date**. This validation helps maintain chronological accuracy and ensures document dates remain consistent during Delivery Note entry.

***

### Objective of This Feature

* Prevent incorrect document dates.
* Ensure the Challan/Invoice Date is not later than the Delivery Note Date.
* Maintain chronological consistency in transactions.
* Improve document accuracy and compliance.
* Reduce data entry errors.

***

### Access to the Configuration

* Open the **Configuration** window.
* Navigate to the **Other Settings** section.
* Locate and enable the option labeled as:

> **"DN Date should be greater than the Challan/Invoice"**

<figure><img src="https://4031188996-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXMVkjt8zqHBQX1c9QvFS%2Fuploads%2F4OHxHfcpbDZLPSAUP5jF%2FCNF.png?alt=media&amp;token=2517a1e9-cd56-4da2-9539-1aafc8ee3d67" alt=""><figcaption></figcaption></figure>

* Save the configuration.

***

### Create a New Delivery Note

* Initiate a **New Delivery Note** entry.
* Enter the **Delivery Note Date**.
* Select the Supplier.
* Enter a **Challan or Invoice Date** that is later than the Delivery Note Date.
* Complete the remaining header details.
* Click **Next**.

**Retrieve Items**

* Select the required Purchase Order.
* Retrieve the Items.
* Click **Refresh**.
* Scan or enter the required Item quantities.
* Click **Save**.

<figure><img src="https://4031188996-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXMVkjt8zqHBQX1c9QvFS%2Fuploads%2FPmns199e9Lg9jr2Ob3kz%2FError.png?alt=media&amp;token=bb1cc562-568c-47b8-84ba-3d14444964f9" alt=""><figcaption></figcaption></figure>

**Result**

The software restricts the transaction and displays an error message indicating that the **Challan/Invoice Date cannot be greater than the Delivery Note Date**.

The document cannot be saved until the date is corrected.

***

### Correct the Date

* Modify the Challan/Invoice Date so that it is **equal to or earlier than** the Delivery Note Date.
* Click **Save** again.

**Result**

The software successfully saves the Delivery Note once the date validation is satisfied.

***

### Key Benefits

* Prevents invalid document dates.
* Maintains chronological consistency between documents.
* Reduces manual data entry mistakes.
* Improves document accuracy and audit readiness.
* Ensures reliable transaction records.

***

### Best Practice Tips

* Always verify the Delivery Note Date before entering the Challan or Invoice Date.
* Enable this validation to enforce consistent document sequencing.
* Review date-related errors before saving transactions to avoid processing delays.

***

### Final Outcome

After enabling **"DN Date should be greater than the Challan/Invoice"**, Logic ERP validates the Challan or Invoice Date during Delivery Note entry. If the entered date is later than the Delivery Note Date, the system restricts the transaction and displays an error message. Once the date is corrected, the Delivery Note can be saved successfully.


---

# 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://kb.logicerp.com/logic-erp-learning-hub-tutorials-and-best-practices/order-processing/delivery-note-against-purchase-orders/dn-against-po-configuration/dn-date-should-be-greater-than-the-challan-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.
