> 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/account-settings/subscription-and-billing/how-to-see-your-billing-history.md). # Billing History Access and download previous PaintScout invoices from your billing history through the account settings billing section. You can view and download past PaintScout invoices from the Billing History section in your Account Settings. ## How to View Your Billing History 1. Open your **Account Settings** and navigate to the **Billing** section. 2. Click on **Plan Details** and select **Manage Billing**
Screenshot showing the Plan Details section with the Manage Billing button
3. In the pop-up, choose **Billing History.**
Screenshot showing the billing management pop-up with the Billing History option
4. A list of previous invoices from PaintScout will appear. To get a copy of the invoice, click the **Download** button.
Screenshot showing the list of previous invoices with the Download button
## Related articles
Update Payment InformationUpdate your credit card or add new payment methods for your PaintScout subscription through the billing management section.Update Payment Information
Start Your SubscriptionBegin your PaintScout subscription by selecting a plan, choosing monthly or annual billing, and entering payment details.Start Your Subscription
--- # 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/account-settings/subscription-and-billing/how-to-see-your-billing-history.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.