Recurring Transactions Table

The Recurring transactions table is used to store transactions that are used repeatedly:

• Recurring transactions stored via the Doc column in the Transactions table. 
  They have in the Doc column an identification code without the exclamation mark '!'.
• Rules for completing imported transactions.
  They are used to define how imported trasnactions are to be completed. 
  They have the code "!Rule" or "RuleSplit" in the Doc column.
• Automatic transactions with recurring deadlines. 
  They are used to automatically generate transactions that are repeated at a certain frequency, for example, monthly, quarterly, half-yearly or yearly.  
  They are registered in the Doc column the code '!Auto'.

Display Recurring transactions table

The Recurring transactions table is displayed from the Actions menu → Recurring transactions.

Columns and views arrangement 

The Recurring transactions table does not allow you to save your own view settings, but takes over the views and column settings of the Transactions table.
However, it is possible to:

•  Add a new view in the Transactions table
•  In the Transactions table, arrange the columns for the new view you have added.
•  When viewing the recurring transaction, choose the preset view.

Entering Recurring transactions in the Doc column

For repetitive operations, codes can be created for automatic data recovery.

• If the 'End Date' column is present (see Automatic Transactions), you can also indicate a date after which this entry is no longer taken up in the Transactions table. 
  Transactions that are no longer used must be deleted manually.

Progressive numbering of "docnum" documents 
If, when retrieving recurring transactions, you wish to have a Doc number different to the automatic one in the Transactions table, you need to create a row containing the code "docnum" in the Doc column, and your desired text in the Description column. For the following rows, the text specified in the Description column will be used.

• "0" when no automatic numbering is required.
• "1" progressive numbering.
• "cash-1" progressive numbering with the prefix "cash-" (cash-2, cash-3).
  The program replaces the number indicated at the end of the text with the next progressive number.
   
• If you wish the program to suggest just one row per code, the description has to be preceded by:
  • An "*": displays just this row and not the others with the same code.
  • An "**" displays just this row, but doesn't retrieve this row (only title row).
  • An "\*" allows the user to start the description with an asterisk, without it being interpreted as a command.

Retrieving recurring transactions in the Doc column into the Transactions table

In the Transactions table, you can resume the rows defined in the Recurring Transactions table:

• In the Transactions table, enter the date in the transaction row and display any other columns that are missing from the Recurring transactions table.
• In the Doc column in the Transactions table, choose one of the codes defined in the Recurring transactions table and press Enter:
  • The programme inserts repetitive rows that have the same code.
  • IIf you need to modify or complete any values, you can always do so.
• Rows stored in the Recurring transactions table can be resumed by entering the code in the Doc column and pressing the F6 key.

Copying transaction rows from the Transactions table into the Recurring transactions table

In order to copy rows from the Transactions table into the Recurring transactions table, you need to:

• In the Transactions table, select the rows that need to be copied.
• Edit menu → Copy rows.
• Go to the Recurring transactions table.
• Edit menu → Insert copied rows.