> 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/customization/templates-and-presets/invoice-settings.md). # Invoice Settings Configure invoice due dates and enable automatic invoice generation when estimates are accepted in PaintScout. Invoice settings in PaintScout let you configure default due dates and enable automatic invoice generation when estimates are accepted. These settings apply account-wide, so every user on your team gets the same defaults. ## How to Access Your Invoice Settings 1. Click the person icon in the top right of your page and go to your **Account Settings** 2. Navigate to the **Invoices** section
Screenshot showing the Account Settings navigation to the Invoices section
*** ## Invoice Due Date The due date setting adds a payment deadline to every invoice you send. 1. Enable the **Invoice Due Date** toggle. 2. Enter your timeframe, calculated from when an invoice is sent (e.g. invoices will be due 7 days from when they are sent, or 1 month etc)
Screenshot showing the Invoice Due Date toggle and timeframe input field
*** ## Automatic Invoice Generation When enabled, PaintScout automatically creates an invoice every time an estimate is accepted — whether accepted by the customer via email link, on-site via preview mode, or manually by you.
Screenshot showing the Automatic Invoice Generation toggle for auto-creating invoices from accepted estimates
### How it works * The invoice is created instantly when the estimate status changes to **Accepted** * All accepted line items, areas, pricing, and contact information carry over from the estimate * The invoice is created but **not sent** — you still need to review and send it manually * If deposits via credit card are enabled, the invoice also generates when a customer pays their deposit ### When to use automatic generation * **Turn it on** if you always invoice after acceptance and want to save a step * **Leave it off** if you sometimes do additional work or adjustments between acceptance and invoicing, or if you don't invoice every accepted estimate *** ## Common Questions ### Can I override these settings on individual invoices? The due date text set here is the default. You cannot override it per-invoice, but you can communicate different terms in your email when sending the invoice. ### Do settings changes affect existing invoices? No. Changes to invoice settings only apply to invoices created **after** the change. Existing invoices keep whatever settings were in place when they were created. ### I enabled automatic generation but the invoice wasn't created. Make sure the estimate status actually changed to **Accepted**. If you manually set the status to Accepted (rather than the customer accepting via email/preview), the automatic invoice should still generate. If it doesn't, contact . {% hint style="info" %} Want to learn about invoicing in PaintScout? [Check out this article](/support/invoicing-and-payments/invoices/invoicing-with-paintscout.md). {% endhint %} ## Related articles
Create and Send an InvoiceCreate invoices from estimates manually or automatically, then send them to customers for payment.Create and Send an Invoice
QuickBooks OnlineConnect QuickBooks Online to export invoices, handle deposits, and sync payments automaticallyQuickBooks Online
XeroConnect Xero accounting software to export quotes, invoices, and sync payments from PaintScoutXero
--- # 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/customization/templates-and-presets/invoice-settings.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.