> For the complete documentation index, see [llms.txt](https://docs.xorosoft.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.xorosoft.com/xoroerp-1/configuration/application/default-document-templates/what-is-default-document-templates-module.md). # What is Default Document Templates Module? In the realm of business, frequent exchange of various documents like sales orders, invoices, and bills with customers or vendors is an everyday affair. Whether it's a sales order, an invoice, or a bill, each document carries crucial information that fuels operational processes. Notably, for a single document there can be multiple templates depending on the requirements. For instance, for invoices, there exists a diversity of templates including but not limited to regular invoices, commercial invoices, and invoices specifically designed for apparel. This is where the **Default Document Templates module** plays a pivotal role. The Default Document Templates module allows you to set default documents for sharing with customers or vendors. By mapping a template as the default for a specific document, you can eliminate the need to manually select the template each time you share a document. Additionally, you can also set the email from which documents are shared. This not only saves time but also ensures consistency and accuracy in document sharing, enhancing overall business efficiency. ### Key Benefits of the Default Document Templates Module * **Efficiency:** Significantly reduces manual effort by pre-setting templates for regular use, allowing for faster document preparation and dissemination. * **Consistency:** Ensures a uniform appearance and structure for all outgoing documents, enhancing brand visibility and professionalism. * **Customization:** Offers the flexibility to define specific templates that cater to your business needs for different documents and recipients. * **Streamlined Operations:** Eliminates the possibility of errors related to template selection, contributing to smoother operational workflows. ### Use Cases * **Template Mapping:** Easily map specific document templates as defaults for various processes like sales orders, invoices, and bills. * **Module-Specific Defaults**: Set default documents on a module-by-module basis, ensuring each department or workflow has predefined templates. * **Multiple Template Support**: Accommodate diverse document needs within a single module by supporting multiple templates, catering to various scenarios or requirements. * **Automatic Template Selection:** Once a template is set as default, it automatically applies for the designated action, streamlining document sharing. * **Set Email To Send From:** Apart from setting the default template, you can also set the email (User or Company) from which the particular document will be sent. --- # 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://docs.xorosoft.com/xoroerp-1/configuration/application/default-document-templates/what-is-default-document-templates-module.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.