> 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/creating-recurring-transactions.md).

# Creating Recurring Transactions

Recurring transactions can be set up for invoices, bills, or journal entries. Creating a journal entry involves entering the essential details, such as the name, recurring frequency, next occurrence date, and end date. 

Once a recurring transaction is created, you can view the transaction's details and status in the Recurring Transaction Centre.

{% hint style="info" %}
To create a recurring transaction, open the specific bill, invoice, or journal entry and go to **Options > Create Recurring Transaction**.
{% endhint %}

#### Recurring Transaction Fields

<table><thead><tr><th width="214">Field</th><th>Description</th></tr></thead><tbody><tr><td>Origin Reference Type</td><td>This field is auto-filled and indicates the source of the transaction. This could be from an invoice, bill, or journal entry.</td></tr><tr><td>Name</td><td>This field allows you to assign a name or identifier for the recurring transaction to easily differentiate it from others.</td></tr><tr><td>Description</td><td>This field allows you to add a description to provide additional details about the transaction.</td></tr><tr><td>Group Name</td><td></td></tr><tr><td>Recurring Frequency</td><td>This field allows you to specify how often the transaction occurs, e.g., daily, weekly, bi-weekly, monthly, yearly, etc.</td></tr><tr><td>Next Occurence Date</td><td>This field allows you to select the date when the next instance of the recurring transaction is scheduled to occur.</td></tr><tr><td>End Date</td><td>This field allows you to select the date when the recurring transaction will stop.</td></tr><tr><td><a href="#creating-recurring-bills-in-advance">Days In Advance*</a></td><td>This field allows you to specify how many days before the Next Occurrence Date you want the system to generate recurring bills.</td></tr></tbody></table>

Once all the details are set, click on "Save" to create the recurring transaction.

### Creating Recurring Bills in Advance

XoroERP allows you to create recurring bills in advance, ensuring timely payments and smoother financial management. This feature is available based on the app config, "**Use Days in Advance for Recurring Bills".** This config is available under the Accounting section in app config module.

<figure><img src="https://3188343778-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fkf8DNCjEfcSm64PCPcmf%2Fuploads%2F0ChOS4MFlfces8VXoN70%2Fimage.png?alt=media&amp;token=4e7bb4e5-1489-4be7-96b8-a0fc710f2a48" alt=""><figcaption></figcaption></figure>

Once the app config is enabled, the field, "Days In Advance" is enabled when defining Recurring Criteria. Users can specify the number of days in advance they want to generate recurring bills.&#x20;

For instance, setting it to generate bills "2 days in advance" for a weekly recurring bill will trigger the bill generation 5 days in advance, while keeping the next occurrence date unchanged.&#x20;

The primary benefit of this feature is its ability to facilitate timely payments without disrupting the existing bill payment cycle. By allowing users to proactively create bills in advance, it ensures that payment deadlines are met efficiently and effectively.

### Recurring Transaction Statuses

Two primary statuses govern the execution and lifecycle of recurring transactions:

* **Active:** This status signifies that the recurring transaction is ongoing and scheduled to be executed again. It means that the transaction has not yet reached its end date or the total number of occurrences set.
* **Completed:** This status indicates that the recurring transaction has completed its execution cycle. Once a transaction reaches its end date or fulfills the predetermined number of occurrences, it changes to this status and won't be executed 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 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/creating-recurring-transactions.md?ask=<question>&goal=<user_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.