> 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/purchase/purchase-inward-workflow-process/gate-pass-entry-against-l.r./gate-pass-entry-against-l.r.-configuration.md).

# Gate Pass Entry Against L.R. - Configuration

## How to set up gate pass prefixes and the checks a purchase makes against a gate pass?

The **Configuration** of **Gate Pass Entry Against L.R.** controls two things:

* the **prefixes** offered for the gate pass number,
* which gate pass details a **Purchase Challan or Purchase Voucher** must match when it quotes the gate pass number as its **GPN Number**.

**This configuration is shared with Inventory\Gate Pass Manager\Issue Against New Gate Pass.** A change saved here also applies there, and the other way round.

***

### **Before you start**

* You need the **configuration** right on Gate Pass Entry Against L.R. Without it the **Configuration** button cannot be used.

***

### **Step 1: Open the configuration**

* Go to **Purchase\Gate Pass Entry Against L.R.**
* Click **Configuration**. The **Gate Pass Configuration Settings** window opens.
* The same settings can also be opened from the **Configuration** button of **Inventory\Gate Pass Manager\Issue Against New Gate Pass**.

***

### **Step 2: Set the document prefixes**

* In **Document Prefixes As**, type the prefixes you want to use, separated by commas with no spaces, as the hint shows: **(Example: GP,GPD)**.
* Prefixes are shown in capitals. Keep each one short.
* On the gate pass screen, the **Document No.** prefix list shows these prefixes together with any prefix already used on an earlier gate pass.
* Each prefix has its own running number. Gate passes made here and in Gate Pass Manager share that number series.

***

### **Step 3: Choose what a purchase must match**

**Validate Selected Gate Pass Fields against Purchase Document** has three ticks:

| Tick             | What the purchase checks                                                                                                                                   |
| ---------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Challan No.**  | The gate pass's **Challan No.** must equal the purchase's supplier **Bill No.**                                                                            |
| **Challan Date** | The gate pass's **Challan Date** must equal the purchase's **Bill Date**.                                                                                  |
| **Branch**       | The gate pass must belong to the **same branch** as the purchase. Without this tick, a gate pass of the same number and party from any branch is accepted. |

These ticks take effect only when the purchase's own configuration has **Validate Purchase Bill Amount against Gate Pass Entry** switched on and the purchase screen uses the **GPN Number** field. When that option is on, the purchase always checks two things, whatever is ticked here:

* a gate pass with the typed GPN Number exists for the purchase's party (so the GPN Number cannot be left blank),
* the gate pass amount equals the purchase's **net amount**.

On Gate Pass Entry Against L.R.:

* each gate pass gets the **invoice number** it was saved for as its **Challan No.** So the Challan No. check passes when the purchase's Bill No. is the same as that invoice number on the L.R.,
* the **Challan Date** is the date entered on the gate pass (today by default). For the Challan Date check, enter the supplier's bill date there,
* the gate pass amount is the total of **all the invoices ticked in that save**. A gate pass made with **PO Selection** carries no amount.

***

### **Step 4: Save**

* Click **Save** to keep the settings, or **Close** to leave without saving.
* Click **New** on the gate pass screen, or open it again, so the prefix list shows the new prefixes.

***

### **Settings you will see but that this screen does not use**

* **Default Item** and **Size Group** appear in the window but have no effect on Gate Pass Entry Against L.R. They are used by Gate Pass Manager.
* **Print Design** opens the gate pass print layout used by Gate Pass Manager. Gate Pass Entry Against L.R. does not print.
* Some Gate Pass Manager settings are hidden when the window is opened from this screen: **Required Document Selection As**, **Skip Box Count Validation**, **Allow Duplicate Item Category**, **Require Bill Amount For Entry** and **Implement New Gate Pass**. Saving here keeps their current values.

***

### **Messages a purchase may show**

These appear on the Purchase Challan or Purchase Voucher when it is saved with a GPN Number and the check is on.

| Message                                                                             | Cause                                                                                                                                          |
| ----------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------- |
| Gate Pass Entry No. ... not found.                                                  | The GPN Number is blank, or no gate pass with that number exists for the purchase's party. The branch is also checked if **Branch** is ticked. |
| Gate Pass Entry Amount :... not match with Bill Amount : ... Cannot allow saving..  | The gate pass amount differs from the purchase's net amount.                                                                                   |
| Gate Pass Entry Bill No. :... not match with Bill No. : ... Cannot allow saving..   | **Challan No.** is ticked and the gate pass Challan No. differs from the purchase Bill No.                                                     |
| Gate Pass Entry Bill Date :... not match with Bill Date : ... Cannot allow saving.. | **Challan Date** is ticked and the gate pass Challan Date differs from the purchase Bill Date.                                                 |

***

> **Example - matching the bill number and date**
>
> In the configuration, Document Prefixes As is **G**, and **Challan No.** and **Challan Date** are ticked.
>
> L.R. **LR-40** of Sunrise Footwear carries one invoice, **SF-140** (Rs 18,000, dated 02/10/2026). At the gate only SF-140 is ticked, with Challan Date set to 02/10/2026. The save makes gate pass **G150**: its amount is Rs 18,000, and its Challan No. and Challan Date are SF-140 and 02/10/2026.
>
> The Purchase Voucher for Sunrise Footwear has Bill No. **SF-140**, Bill Date **02/10/2026**, net amount **Rs 18,000**, GPN Number **G150** and a GPN Date. It saves.
>
> If the Bill No. had been typed as SF-0140, the save would stop with "Gate Pass Entry Bill No. :SF-140 not match with Bill No. : SF-0140 Cannot allow saving..".


---

# 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/purchase/purchase-inward-workflow-process/gate-pass-entry-against-l.r./gate-pass-entry-against-l.r.-configuration.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.
