> For the complete documentation index, see [llms.txt](https://help.pickyassist.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.pickyassist.com/whatsapp-commerce/invoice/faqs.md).

# FAQs

#### What's the difference between Draft and Approved?

Every new order gets an invoice in Draft immediately. It's promoted to Approved (and sent, if Step 6 is on) once the order reaches the status you chose in Step 5. A Draft invoice can still be downloaded or sent manually at any time.

#### Why didn't an invoice send automatically?

Either the order hasn't reached the status you set under "When should the invoice be approved?" yet, or the WhatsApp send failed — use Download Invoice / Send Invoice from the order to handle it manually.

#### Will editing my Business Profile, layout, signature or notes change invoices I've already sent?

No. Those changes apply only to invoices generated after you save them.

#### Can two catalogs share the same invoice prefix and starting number?

No, Picky Assist blocks a duplicate combination across catalogs, even if the other catalog isn't currently active.

#### What does Include Tax / Exclude Tax actually control?

Whether the prices on your products already have GST built in (Include Tax) or GST is calculated and added on top (Exclude Tax). Set this to match how you actually price your products, so invoice totals come out right.

#### Which countries are supported?

India only, for now.


---

# 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://help.pickyassist.com/whatsapp-commerce/invoice/faqs.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.
