> 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/inventory/warehouse-management-features-and-configuration-in-logic-erp/wms-mobile-app/verify-box-invoice.md).

# Verify Box - Invoice

## WMS App – Verify Box - Invoice

In this tutorial, we will learn how a warehouse operator uses the **VERIFY BOX-INV** option of the WMS app to check, box by box, that every packing box of a **Sale Bill** is physically present.

The boxes listed for a Sale Bill are the packing boxes of the **Delivery Orders** that the bill was made from. Only a Sale Bill made from Delivery Orders can be verified. See **Assign Stock to Delivery Order and Box Printing** for how the packing boxes are created, and **Sales Order to Dispatch Process** for the full flow.

***

### Find the Sale Bill

* Open the WMS app and tap **VERIFY BOX-INV**.
* In **Sale Bill No. :** scan or type the Sale Bill number and tap **Fetch Data**. With a handheld scanner, the bill is fetched as soon as it is scanned. On a phone, tap the scanner icon in the box to scan with the camera.
* The bill is shown with its **Party Name**, **Bill No.** and **Bill Date**.
* Tap the bill to start verifying its boxes.

The Sale Bill must belong to the branch you are logged in to and to the current financial year.

If you had already started this bill on your phone and not uploaded it, the app asks *"Data found against Sale Bill No. : '…'. Tap 'Yes' to recover data, else 'No' to start again."* Tap **Yes** to carry on where you left off, or **No** to discard the earlier scans.

**Messages you may see**

| Message                                 | Meaning                                                                                                                  |
| --------------------------------------- | ------------------------------------------------------------------------------------------------------------------------ |
| *Unable to found Sale Bill No. : …*     | No Sale Bill with this number was found in this branch and financial year, or the bill was not made from Delivery Orders |
| *You have to provide Camera permission* | Allow the app to use the camera, then try again                                                                          |

***

### Scan the Boxes

The **SCAN** screen lists every **Packing Box No.** of the bill. Boxes still to be scanned are shown as *Pending*.

* Scan the barcode of each packing box.
* Each scanned box is marked *Received Complete* and moves below the boxes that are still pending.
* Your scans are saved on the phone after every box, so you can leave the screen and come back later.

If **Tap-To-Scan** is on in the app settings, tapping a box counts as scanning it.

**Messages you may see**

| Message                            | Meaning                                                                                            |
| ---------------------------------- | -------------------------------------------------------------------------------------------------- |
| *No record found with barcode : …* | The scanned box does not belong to this Sale Bill                                                  |
| *Already scanned...*               | This box has already been scanned for this bill, or was verified in an earlier upload of this bill |

***

### Scan All

If you have checked all the boxes without scanning them one by one:

* Tap **Scan All**.
* The app asks *"Are you sure to update all records?"*. Tap **Yes**.
* All the boxes are marked as scanned and the app shows *"Done! Data updated successfully..."*.

***

### Upload the Verification

* Tap **Upload**.
* The app asks *"Are you sure to submit record?"*. Tap **Yes**.
* The app shows *"Data submitted successfully..."* and returns to the Sale Bill screen.

You do not have to scan every box before uploading. Only the boxes you have scanned are recorded. To verify the remaining boxes later, fetch the same Sale Bill again, scan them and upload again.

**Messages you may see**

| Message                | Meaning                     |
| ---------------------- | --------------------------- |
| *Nothing to upload...* | No box has been scanned yet |

**Result:** In Logic ERP, each scanned box is recorded as verified against the Sale Bill. Uploading the same bill again adds only the newly scanned boxes; boxes already recorded stay as they are.

***

> **Example — Verifying a bill in two rounds**
>
> Sale Bill **SB-245** was made from two Delivery Orders packed in boxes **BX-501**, **BX-502** and **BX-503**. Ravi taps **VERIFY BOX-INV**, scans the bill number and taps the bill. He scans BX-501 and BX-502. When he scans BX-502 again by mistake, the app shows *Already scanned...*. BX-503 is still being loaded, so Ravi taps **Upload** and **Yes** for the two boxes. Later he fetches SB-245 again, scans BX-503 and uploads again.

***

#### Final Outcome

Using **Verify Box - Invoice**, the warehouse operator confirms by scanning that every packing box of a Sale Bill is present, and Logic ERP keeps a record of the boxes verified against that bill.


---

# 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/inventory/warehouse-management-features-and-configuration-in-logic-erp/wms-mobile-app/verify-box-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.
