> For the complete documentation index, see [llms.txt](https://docs.umbraco.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.umbraco.com/umbraco-commerce/add-ons/payment-providers/invoicing.md). # Invoicing Getting Started with the Invoicing payment provider for Umbraco Commerce. The Invoicing payment provider is a "pass-through" payment provider that doesn't capture payment information directly. It allows orders to be processed in an Authorized state, assuming payments will be handled manually in an external system. Once the payment is captured, the order status can be updated to Captured via the backoffice. Before you begin, ensure that you have an Umbraco website set up and Umbraco Commerce installed. If not, see the [Umbraco Commerce Documentation](/umbraco-commerce/readme.md) to get started. ## Install Invoice By default, Umbraco Commerce includes the Invoice payment method. If the package has been removed from your implementation, see the [Installing Umbraco Commerce](/umbraco-commerce/getting-started/install.md) article to reinstall it again. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.umbraco.com/umbraco-commerce/add-ons/payment-providers/invoicing.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.