Recurring Transactions table
In the recurring Transactions table, you can enter all the transactions that are repeated every month. In order to avoid rewriting the same texts each time, it is possible to store transaction groups in the Recurring transactions table (Actions menu). These groups are identified with a code and can be retrieved and entered into the Transactions table just by entering the corresponding code.
When positioned on the Doc column of the Transactions table, the program proposes the list of the recurring transactions, grouped by code. If one of these codes is selected:
- the program enters the recurring rows that have the same code
- the program completes the entered rows with the date and other values that have been entered earlier
- the program enters the progressive number in the Doc column (based on earlier entered values)
Entering recurring transactions
For repetitive operations, causal codes can be created for automatic data recovery.
- You need to enter into the Recurring transactions table (or copy from the Transactions table) the transaction rows that should be retrieved regularly.
- A code is assigned to each Recurring transaction.
- Enter the code related to the recurring transactions group into the Doc column.
Rows with the same group code will be retrieved together (transaction on multiple rows).
Progressive numbering of "docnum" documents
If, when retrieving recurring transactions, you wish to have a Doc number different to the automatic one, 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.
The recurring transactions table does not allow for saving your own view settings, but takes over the views and settings of the columns from the Transactions table.
Retrieving the recurring transactions into the Transactions table
- Enter the date and other columns that should remain unchanged.
- In the Doc column, choose one of the codes defined in the Recurring Transactions table and press Enter:
- The program enters all the transactions with the same code, repeating the data column and other already entered values.
- In the Doc column, a progressive number is being inserted or the one specified in the docnum column.
- Or indicate the code in the Doc column and press F6.
Copying transaction rows into the Recurring Transactions table
In order to copy rows from the Transactions table into the Recurring transactions table:
- 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.
Formatting columns and views
The Recurring transactions table uses the same formats and displays as the Transactions table.
It is not possible to have a separate format for the Recurring transactions table only.
It is however possible, from the Transactions table, to add a new View, setup a new columns format, and use this same view in the Recurring transactions table.
Creating rules to autocomplete transactions
In the Recurring transactions table you can create rules that automatically categorise transactions for you when you import them from your bank statement. See the Auto categorization of transactions page.