Recurring transactions help you manage repetitive journal entries and payment vouchers by using reusable transaction templates and schedules.
A recurring transaction has two main components:
- Transaction template: Defines the transaction details and identifies which users receive notifications.
- Schedule: Determines when notifications for the transaction appear.
Before you can schedule a recurring transaction, you must create a transaction template and assign it to one or more schedules.
Transaction templates
You can create transaction templates for journal entries or payment vouchers. A template stores the static details of a transaction so Juris can prepopulate the appropriate information when the transaction is due.
The schedule assigned to the template determines when the transaction notification appears.
Common examples include:
- A journal entry template for accumulated depreciation.
- A payment voucher template for a recurring monthly expense, such as insurance or rent.
Schedules
Schedules determine when notifications for recurring transactions appear.
Juris uses the notification list in the transaction template to determine which users to notify. A schedule should include at least one transaction template, but it can include multiple templates.