Scheduled transactions

Overview

There is a group of transactions which happen very regulary (eg. salary, bills etc.). To not bother with them everytime they occur you can create the scheduled transactions. They are just normal transactions which are automatically inserted into transactions registry in a periodic manner.

Each scheduled transaction has five properties, which are described below.

  1. Amount has just the same meaning like in the normal transactions. It tells how much money is to be transfered between accounts.

  2. AccFrom states which account is to be debited.

  3. Very similiar to the above is AccTo which specifies which account is to be credited.

  4. The Next Date just tells the time of the next occurence of the scheduled transaction (or the first one if you are creating a new scheduled transaction).

  5. The Frequency specifies how often does the transaction occur. It can be in one of four states: Daily, Weekly, Monthly, Yearly.

  6. If you want to approve every insertion of the transaction, you can set Prompt property for this. If this is checked, than upon every insertion a new transaction dialog appears so you can check if everything is alright or edit some properties of this particular insertion. If Prompt is unchecked than scheduled transactions are inserted into transactions registry unnoticably.

  7. As with normal transactions, you can use Description property to provide additional information about a transaction.

Tip: If Amount and/or Description properties vary from time to time, there is a simple solution. Just check Prompt to True and edit values with every insertion of the transaction.

How does it work? Whenever a data file is loaded into Emma, the program browses through scheduled transactions and checks if it is time to insert them to the main transactions registry. It looks at the current data and the Next Date property of the scheduled transaction, and if today happens to be after next occurence date, the transaction is inserted (with your interaction if Prompt property is on). Then the Next Date property is updated according to the Frequency state and it is compaired again with the current date. The process is repeated until the scheduled transaction requires no insertion.

Editing commands

FIXME. Describe editing commands here.