> For the complete documentation index, see [llms.txt](https://help.paintscout.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.paintscout.com/support/invoicing-and-payments/invoices.md). # Invoices Create invoices from estimates, send them to customers, and track payments in PaintScout. Invoices help you turn accepted estimates into billable documents and track payments. This section covers invoice creation, payment requests, payment tracking, updates to the payments experience, and common invoicing questions. {% hint style="success" %} **Start here:** Begin with [Create and Send an Invoice](/support/invoicing-and-payments/invoices/creating-invoices.md) for the step-by-step workflow. {% endhint %} ## In this section * [Why PaintScout Invoicing](/support/invoicing-and-payments/invoices/invoicing-with-paintscout.md) — Learn how invoices, payment requests, online payments, and payment tracking work together * [Create and Send an Invoice](/support/invoicing-and-payments/invoices/creating-invoices.md) — Create invoices from accepted estimates manually or automatically, then send them to customers * [Payments Table Overview](/support/invoicing-and-payments/invoices/payments-table-overview.md) — Find the right workflow for each payment task * [What’s New in Payments](/support/invoicing-and-payments/invoices/payments-table-overview/whats-new-in-payments.md) — Explore the updated Payments Table, refunds, payment statuses, and reporting * [Invoicing FAQ](/support/invoicing-and-payments/invoices/invoicing-faq.md) — Find answers about creating, editing, and managing invoices --- # 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.paintscout.com/support/invoicing-and-payments/invoices.md?ask=&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.