> 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-installation-configuration-and-troubleshooting-solutions/faqs/sales/create-a-copy-of-a-sale-bill.md).

# Create a Copy of a Sale Bill

**YouTube:** [How to Create a Copy of a Sale Bill?](https://www.youtube.com/watch?v=P2Dh8oq4cKs)

## How to Create a Copy of a Sale Bill?

In this tutorial, we’ll guide you through the **process of creating a bill copy** in Logic ERP.

***

### Access a Previously Created Bill

* The system currently shows the existing bill number as **240**.
* To open a previous bill, first **unhide the Modify button**:
  * Turn **off the Num Lock key** on your keyboard.
  * Press **Alt + Insert**.
* As you can see, the **Modify button** is now visible on the screen.

<figure><img src="https://4031188996-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXMVkjt8zqHBQX1c9QvFS%2Fuploads%2FCeRcnlyxXcN7Fr3CRQp9%2FModify.png?alt=media&amp;token=1b6eb05a-09a3-4d84-af31-a5caf779b352" alt=""><figcaption></figcaption></figure>

You can:

* **Left click** the Modify button to directly enter the bill number you want to open.
* Or **right-click** the Modify button to display a **list of all previously created bills**.

***

### Copy a Previous Bill

* Let’s **right-click** on the Modify button to display the list of bills.
* Select the bill you want to copy — for example, **GST-237**.
* Open the selected bill.
* Now, **right-click on the “New Bill” option**.
* The system will prompt a confirmation message:\
  *“Do you want to change the currently open bill to a new bill?”*
* Click **Yes** to confirm.

<figure><img src="https://4031188996-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXMVkjt8zqHBQX1c9QvFS%2Fuploads%2F2iE5wBTPHPu2rfh8SlB9%2FNew%20Bill%20Prompt.png?alt=media&amp;token=6a7e5162-2050-428a-b26f-e4da3a053710" alt=""><figcaption></figcaption></figure>

***

### Outcome Summary

* The selected bill (**GST-237**) is successfully copied to the new bill, which is created as **GST-240**.

<figure><img src="https://4031188996-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXMVkjt8zqHBQX1c9QvFS%2Fuploads%2FI2MakDQ2VhKAV1xaI2Fr%2FGST%20240.png?alt=media&amp;token=17bc36e0-7213-4022-821c-a794e12f1868" alt=""><figcaption></figcaption></figure>


---

# 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-installation-configuration-and-troubleshooting-solutions/faqs/sales/create-a-copy-of-a-sale-bill.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.
