> 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/integrations/accounting.md). # Accounting Connect PaintScout to your accounting software for invoice and payment workflows. Connect PaintScout to your accounting software to reduce double entry and keep invoice activity aligned with your books. PaintScout currently supports accounting integrations for **QuickBooks Online** and **Xero**. Each setup has its own workflow and options, so start with the guide for the platform you use today. ## In This Section * [QuickBooks Online](/support/integrations/accounting/quickbooks-online-integration.md) — Export invoices, handle deposits, and sync payments automatically * [Xero](/support/integrations/accounting/xero-integration.md) — Export quotes, invoices, and payments to Xero ## How to choose the right setup ### QuickBooks Online Use QuickBooks Online if you want a mature workflow for invoices, deposits, and payment syncing. It includes more setup options for item handling, deposit invoices, surcharge behavior, and invoice timing. ### Xero Use Xero if your accounting team already runs in Xero and you want estimates, invoices, and payments exported from PaintScout. Xero is currently in beta, so you may need support to have it enabled before setup. --- # 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/integrations/accounting.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.