> 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/accounting/recurring-transactions/what-is-a-recurring-transaction.md). # What is a Recurring Transaction? Recurring transactions are designed to save time and minimize errors in financial record-keeping. They automate repetitive tasks such as journal entries, invoicing for subscription-based customers, or the routine writing of checks and entering bills. By setting up these transactions to occur automatically, you can ensure consistency and reliability in their financial operations without the manual input traditionally required. ### Key Benefits * **Time Efficiency**: Setting up recurring transactions automates routine financial tasks, freeing up valuable time for focusing on strategic financial planning and analysis. * **Reduced Errors**: Recurring transactions minimize the risk of human error in manual data entry, ensuring more accurate financial records. * **Consistency**: Recurring transactions guarantee that payments, invoices, and entries are made consistently, aiding in better financial management and planning. --- # 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/accounting/recurring-transactions/what-is-a-recurring-transaction.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.