The documentation
General Presentation
• Transactions
Account transaction list
Transaction line states
Transaction properties
Printable Version
To contact the editor
Download
the documentation
| Transactions | |
In this section we are going to look in detail at everything surrounding transactions.
As you will see, it's a vast subject... You are going to finally understand why Ma Tirelire is THE software for your everyday needs... | |
| • Account transaction list | |
|
The start of the line (in inversed colours) gives the name of the database and the name of the account, abridged due to lack of space. The 3 icons in the top right let you rapidly access: • The padlock controls the locking/unlocking of the flagging and clearing functions. If the background is clear it is possible to flag and clear transactions, if it is black then these 2 functions are locked. • The arrows with a 1 and + let you rapidly access those actions that you defined in the preferences menu. |
|
Tapping on the triangle (inverse colours) at the beginning of the line opens this menu from which you may: • Go up a level to the account list. (first menu item) • Change account in the database. • Access the current selected account properties. (last menu item) |
|
• The first line always shows the account name and balance (in inverse colours) above the transactions. • Each line corresponds to one transaction and it breaksdown into the following elements:  For the visual aspect of the lines please refer to transaction line states.– The date on which the transaction will be accounted for. It will be the validity date if the option "show the validation date" is selected in database properties. Otherwise it will be the date when the transaction was entered.– Transaction description (the name). – Transaction value. |
|
The bottom line consists of: • 2 buttons for added a transaction, the + for a credit, the - for a debit. The transaction sign can be changed in the transaction properties.• A list at bottom middle ("All" in the image) which allows you to change the sum on the righthand side. (See the function sum type.) • An amount on the right which indicates the balance at the date desired. (For more info, see the function sum type.) • An black arrow on the right is used to mask or reveal this line. |
top of the page  | |
| • Transaction line states | |
|
In Ma Tirelire the transaction lines can take several on several aspects, depending on the assigned parameters, and as a picture says a thousand words, here are some simple examples. You can modify the aspect (colour, font,...) of the lines to differentiate between debits and credits, for example. For more information take a look at the preferences on the "Lists" tab. | |
|
Let's start with a basic transaction with no special symbols. |
|
The date in inversed colours indicates that the transaction is dated today |
|
The small arrow at bottom left of the date indicates that a validity date has been set for this transaction (see below in transaction properties in the "Main" tab) |
|
The double square before the name indicates that this transaction has associated repeat rules (see below in transaction properties in the "Repeat" tab) |
|
The alarm clock before the name indicates that this operation has an associated alarm (see below in transaction properties) |
|
The small triangle at the bottom right of the amount indicates that the transaction has been flagged (see below in transaction properties in the "Main" tab) To (un)flag a transaction you only have to tap on the cents/pennies of the amount. The padlock must have a clear background. |
|
The amount shown in inversed colours indicates that this transaction has been cleared. To (un)clear you only have to tap on the non-cents/pennies part of the amount. The padlock must have a clear background. |
|
An example of a transaction that has been both flagged and cleared. |
|
Examples of transactions where the amount is too long to be shown in full in the list view. To better recognise them in the list their amounts are shown in bold. Firstly the decimals are removed from the list view, or a unit is given before the Millions. The amount used for calculations is visible in the transaction properties. |
|
And this line defies description... |
| top of the page | |
| • Transaction properties | |
|
• The alarm lets you set an alarm for a transaction. If the background is clear then there is no alarm set, if it is black then a message provides you with the set date. • Date : This is the date and time of the transaction, which by default is the date of entry. The two small arrows let you change the date without opening the calender.• Desc : lets you define a name for the transaction which will be displayed in the transaction list. Tapping on the arrow to the left of 'Desc' opens the descriptions list (see the function Description / Macro)• Credit / Debit tap on the text (or +/-) changes the transaction sign. • The amount do I have to say more? • The sign allows you to define which currency you wish to make this transaction (see the chapter on Currencies). |
|
• Mode allows you to change the payment mode used for the transaction. To create a payment methods list got to the chapter on payment modes. This field can be filled in automatically with the aid of the Macro function. • # is useful if you need to use a cheque. Tapping on "#" launches an automatic cheque number function from the information stored in the "chequebook" tab in account properties. This field can be filled in automatically with the aid of the Macro function.• On same day lets you define a validity date (=date on which the payment is accounted for) for the transaction. This field can be filled in automatically with the aid of the Macro function.• The tick box allows you to flag a transaction. • Type lets you set the category. To create your category type list, see the chapter on operation types. This field can be filled in automatically with the aid of the Macro function.• Statemt lets you enter the number of the relevant banck statement on which this transaction appears. • Cleared lets you mark this transaction as cleared on a statement. For more information on this subject go to clearing.• Transfer, as its name suggests, lets you transfer money from one account to another. If you click on "None" the list of accounts in the database appears and then you only have to chose the correct target account for the transfer. A corresponding transaction will be automatically created in the destination account. This field can be filled in automatically with the aid of the Macro function. |
|
The "Repeat" function lets you set up an automatic repetition of this transaction at a regular interval. For example, if you pay rent every month, or a loan, or a mobile phone sub, etc. you will already have grasped the importance of this function. | |
|
• Repeat is set to "Never" as a default. |
|
If you tap on "Never", the list of possible intervals appears and then you only have to chose your desired repetition frequency. |
|
Once a frequency is defined you can tap on End at to define a rule for your repeats, such as: • end at a predefined date. • unlimited end point. • a defined number of occurrences: Ma Tirelire will calcule the end date as a function of the specified number of occurrences. Tapping directly on "occurence(s) to be" gives you the same effect. |
|
How to calculate a repeat (creation of the next occurrences of a repeating transaction): 1 - Automatically when starting Ma Tirelire; you only need to activate the option in database properties. 2 - Manually; using a menu entry Misc." ("Divers" in the beta) or the shortcut/ R. Ma Tirelire creates the occurrences of a transaction which are included between the current date and the numbers of days indicated in the "View repeats" parameter (see database properties). Lets use an example for clarification: On the 8th September you create a transaction called "Salary", set for that date and with a repeat set for "Every 2 weeks". The next occurrences of this transaction will therefore be the 22nd September, the 6th October, the 20th October, the 3rd November, etc. (if you haven't set an end date). To complete our example, you also defined "View repeats XX days before". If you execute your repeats manually the you will see the following appear in the transaction list: • if XX = 10 : 1 "Salary" transaction, that of 8th September. • if XX = 20 : 2 "Salary" transactions, those of 8th and 22nd September. • if XX = 50 : 4 "Salary" transactions, those of 8/09, 22/09, 6/10 and 20th October. Only the last occurrence of the transaction will carry the repeat parameter. | |
|
Not yet implemented...
|
|
Not yet implemented...
|
|
The 3 buttons speak for themselves... |
| top of the page | |