> For the complete documentation index, see [llms.txt](https://helpdocumentation.gitbook.io/user-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://helpdocumentation.gitbook.io/user-documentation/integrations/tally/create-and-send-a-sales-invoice-via-whatsapp.md).

# Create and Send a Sales Invoice via WhatsApp

#### Step 1: Verify Prerequisites

Before creating a sales invoice, ensure that:

* WhatsApp Business API is configured.
* WhatsApp templates are synced.
* Event Mapping is configured correctly.

#### Step 2: Create a Sales Invoice

* Go to **Vouchers**.
* Select **Sales** to create a new Sales Invoice.

#### Step 3: Select the Customer Ledger

* Choose the customer ledger.
* Ensure the ledger contains the customer's WhatsApp number.

#### Step 4: Enter Invoice Details

* Add the required sales details, such as:
  * Sales Ledger
  * Stock Item
  * Quantity
  * Rate
  * Amount
* Verify the invoice details.

#### Step 5: Save the Invoice

* Accept and save the Sales Invoice.
* The invoice PDF will be generated automatically.

#### Step 6: Send the Invoice on WhatsApp

* Wait for the process to complete.
* A success message will confirm that the WhatsApp message has been sent.

#### Step 7: Verify the Message

* Open WhatsApp.
* Confirm that the customer has received:
  * The approved WhatsApp template.
  * The invoice PDF with the correct details.

{% embed url="<https://www.youtube.com/watch?v=NlirfJeX6ng>" %}


---

# 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://helpdocumentation.gitbook.io/user-documentation/integrations/tally/create-and-send-a-sales-invoice-via-whatsapp.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.