> For the complete documentation index, see [llms.txt](https://learn.doubletick.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://learn.doubletick.io/settings/how-to-manage-billing-and-invoices/steps-to-request-a-missing-invoice.md).

# Steps to Request a Missing Invoice

**🧾 How to Request a Missing Invoice**

If you haven’t received your monthly invoice or need a copy for any past billing cycle, here’s how you can request it.

1. Send an email to **<finance@quicksell.co>**
2. Email must be sent from your **registered email ID**
3. Mention:
   * Your **DoubleTick API Number**
   * Month(s) or transaction(s) for which the invoice is missing

📨 **Email Format (Sample)**:

To: **<finance@quicksell.co>**

**Subject: Request for Missing Invoice – \[Month/Transaction ID]**

Dear Team,

I am writing to request a copy of the missing invoice(s) for our DoubleTick account.

Company Name: \[Your Company Name]

DoubleTick API Number: \[Your API Number]

Invoice Period: \[e.g., July 2025]

Transaction ID (if available): \[Optional]

Please share the invoice(s) on this email at your earliest convenience.

Best regards,

\[Your Name]

**📝 Notes:**

* For faster service, always use your **registered email ID**.
* You can request invoices for **any past month** provided the transaction was completed.


---

# 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://learn.doubletick.io/settings/how-to-manage-billing-and-invoices/steps-to-request-a-missing-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.