> ## Documentation Index > Fetch the complete documentation index at: https://docs.slash.com/llms.txt > Use this file to discover all available pages before exploring further. # Invoices > Bill your customers and get paid into your Slash account. Send a customer an invoice and Slash emails it with a PDF and a payment page, reminds them as the due date approaches, and records the money against the invoice when it arrives. Issue, schedule and edit invoices. Match deposits and record payments. Bill a customer on a schedule. Invoicing has to be turned on for your business; customers work either way. ## Customers Every invoice is billed to a customer: the business or person you invoice, and the email address invoices and reminders go to. [Create a customer](/api-reference/customers/create) once and reuse it on every invoice and series. An invoice keeps the billing details it was issued with. After you [update a customer](/api-reference/customers/update), existing invoices pick up the change only when you edit them. [Archive](/api-reference/customers/archive) customers you no longer bill; their invoices are left as they are. ## Invoice lifecycle You never set an invoice's `status`. Creating, sending and voiding move it, and once it's sent Slash recomputes it from its payments whenever one is recorded, removed or returned. Invoice lifecycle Invoice lifecycle * An invoice can be edited while it's `scheduled` or `unpaid`. Once it has a payment, void it and issue a new one instead. * An invoice past its due date with money still owed is flagged `overdue`; its `status` doesn't change. * `void` is final. A voided invoice can't be paid, edited or reminded. Each invoice's PDF is a [document](/api-reference/documents/retrieve): `documentId` points to the current version, and every edit renders a new one. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.