You create a recurring template to save time by automatically generating journal entries for transactions that consistently and repeatedly occur over time, such as rent payments or finance payments. The journal entry that you set up in a recurring template is automatically generated for the periods that you set up in the template. If journal entries apply to after the period range that you set up, these entries can be generated in future periods as you create those periods. A batch job generates the journal entries for recurring templates.
Recurring templates post generated journal entries to the GL on dates that you specify and at frequencies that you designate. You can set up a recurring template to generate a journal entry for the transactions once each period at the beginning or the middle of the period. Also, you can set up a recurring template to generate a journal entry at a specific frequency, such as the beginning of every quarter, the 15th of every month, every other Friday, and so on.
If a recurring transaction is always the same amount—such as a rent payment—you can enter that amount in the template lines, and an accounting entry for that amount is automatically generated. If a recurring transaction is always a different amount—such as a utility payment—you can leave the amount in the template lines blank, and enter it each time you receive an invoice.
Before you create recurring templates, verify the following items are created:
To learn more about Recurring Template fields, see Recurring Template Field Descriptions.
Recurring Template detail page is displayed.
To learn more about Recurring Template Lines fields, see Recurring Template Line Field Descriptions.
After you create recurring templates, you might create journal entries that use those templates. To learn more, see Journal Entries.
You can make simple changes to a recurring template—such as changing the amount or the transaction date—at any time. However if there's an error in the original setup of the template, you must create a new template with the correct information, and also change the end date of the prior, incorrect template to the first day of the earliest open period. The correct journal entries begin to automatically generate from that day forward.
In addition, you must make adjustments to the incorrect journal entries, regardless of whether those entries are in a closed, open, or future period. Decide whether to make a journal entry adjustment in the current period for the incorrect journal entries in past periods, or whether to re-open any period that is not in a permanent close state, and make adjustments to the original journal entries.
Note: If you change the end date of the template to a date in an open period, any recurring journal entry that is after the new end date is automatically changed to a cancelled status. Changing the status of a journal entry to cancelled automatically deletes its corresponding accounting entry.
The following table lists the fields that Kenandy provides. Your system administrator selects the fields that are displayed on your user interface.
| Field | Description |
|---|---|
| Autonumber | An auto-generated ID that identifies the recurring template. |
| Company | The company applicable to the journal entries that the recurring template generates. |
| Currency | The currency in which the journal entry is recorded. This field is automatically populated with the functional currency, if any. |
| Description | A description of the recurring template. |
|
|
The period in which the recurring template stops creating and posting journal entries. |
| Exceptions Count | The number of exceptions (errors) associated with the recurring template. |
| Frequency |
How often the transactions that apply to the template occur. The options include:
The value in the Recurring Transaction Start Date field determines the specific date and time when the journal entries are generated for each time interval. For example, if you enter a transaction start date for the 10th a month and select a monthly frequency, then a journal entry is generated on the 10th of each month. |
| Has Exceptions | An indication of whether the recurring template has one or more exceptions. |
| isJECreated | An indication of whether a journal entry is created for the recurring template. |
| Line Exceptions | The number of exceptions that are associated with the lines in the recurring template. |
| Recurring Template | The name of the recurring template. This field can be up to 80 characters long. |
|
|
The date and time that the first journal entry for the template is generated. If the value in the Frequency field is Beginning of Period, this field value is automatically populated with the first day of the period, and you cannot change this value. If the value in the Frequency field is Middle of Period, this field value is automatically populated with the date in the middle of the period, and you cannot change this value. |
|
|
The period in which the recurring template begins creating and posting journal entries. |
| Status | The status of the recurring template. Select Draft for templates that are incomplete or saved, and select Active for templates that are complete and generating journal entries. The status automatically changes to Closed after the template end date. |
| Template End Date | The date and time the recurring template no longer generates journal entries. If you want the template to generate journal entries indefinitely, leave this field blank. |
| Total Credit | The total credits on the lines of the recurring template. |
| Total Debit | The total debits on the lines of the recurring template. |
| Total Number Of Lines | The total number of lines for the recurring template. |
| Type | The type of transaction that is automatically created from the template—for example, journal entry. |
The following table lists the fields that Kenandy provides. Your system administrator selects the fields that are displayed on your user interface.
| Field | Description |
|---|---|
| Amount CR | The credit amount for the template line. |
| Amount DR | The debit amount for the template line. |
| Autonumber | An auto-generated ID that identifies the recurring template line. |
| Bank Account | The bank account for the template line. |
| Company | The company applicable to the journal entry line that the recurring template line generates. |
| Exceptions Count | The number of exceptions (errors) associated with the recurring template line. |
| GL Account | The general ledger account for the template line. |
| Has Exceptions | An indication of whether the recurring template line has one or more exceptions. |
| Recurring Template | Then name of the recurring template for the template line. |
|
|
The automatically-generated reference for the template line. |
_________________________________
To search the KnowledgeBase and documentation, ask a question, or log a case, please visit the Kenandy Community. To access our online training, visit the Kenandy Learning Center.
Version: Spring 2017