> 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-version-release-notes/october-2026/purchase/enter-l.r.-details.md).

# Enter L.R. Details

Logic ERP has corrected several issues in **Enter L.R. Details**. L.R.s picked against a **Way Bill No** can now be saved, the **G.R. No.** is checked again on Save, and the **Document Amount** now keeps the freight, insurance and docket amounts together.

***

### **Step 1: Open the Screen**

* Navigate to **Purchase** and select **Enter L.R. Details**.

***

### **What's corrected**

* **Way Bill No:** a new L.R. with **Way Bill No** selected and a way bill picked under **Select Document** can now be saved. Earlier Save stopped with "Please Select Document.." even after the way bill was picked. Save still stops with this message when no way bill has been picked.
* **Duplicate G.R. No.:** when **Restrict Duplicate Bill No. for Same Supplier** is ticked in the L.R. configuration, the **G.R. No.** is now checked again when you click **Save**, not only when you leave the field. If the same supplier already has an L.R. with this G.R. No. in the current financial year, Save stops with "GR No. Already Exists".
* With this setting ticked, an existing L.R. whose G.R. No. already repeats another L.R. of the same supplier must now be given a different G.R. No. before it can be saved again. This is intended.
* **G.R. No. with an apostrophe** (for example **GR'2041**) is now checked correctly for duplicates when this setting is ticked. Earlier leaving such a G.R. No. showed an error and it was not checked.
* **Document Amount** (when freight is worked out from the **Freight Rate**):
  * Changing **Insurance Amount** or **Docket Amount** now keeps the freight in the Document Amount even when **Actual Weight** is blank. A blank Actual Weight is taken as 1, the same as when the Freight Rate is entered.
  * Changing **Actual Weight** or **Freight Rate** now keeps the **Insurance Amount** and **Docket Amount** in the Document Amount. Earlier they were dropped.
  * In these cases the Document Amount will be higher than before. This is intended.
* **Document Date:** the Document Date of a new L.R. must now fall within the current financial year. Otherwise Save stops with "Document Date not within financial year".
* **No. Of Boxes:** when an L.R. of type **Purchase Order** or **PI Category Basis** has **No. Of Boxes** blank or 0, Save now stops with the clearer message "Invalid value for No. Of Boxes" and the cursor moves to **No. Of Boxes**. Earlier Save stopped with "Total box count does not match the invoice box count." Such an L.R. could not be saved before either.
* **To Pay** has been removed from the screen. It was never saved with the L.R.
* **Modify** no longer shows an error and an empty screen on some installations when an L.R. is picked. On those installations, picking documents under **Select Document** also no longer shows an error, and the selected document numbers are shown next to it.
* The field settings for **No. Of Boxes**, **Docket Amount** and **Packing Unit** now apply to those fields. Earlier the No. Of Boxes and Docket Amount settings were applied to **Document Amount**, and the Packing Unit setting to no field.
* Message wording corrected:
  * "Gate Pass Entry exists against this L.R. Modification not allowed."
  * "Gate Pass Entry exists against this L.R. Deletion not allowed."
  * "Please Enter Valid Document Date..."
  * "Invoice Date cannot be later than the L.R. Document Date"
  * "Invoice Number already exists"


---

# 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-version-release-notes/october-2026/purchase/enter-l.r.-details.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.
