Search HansaManuals.com HansaManuals Home >> Discontinued Products >> Books by HansaWorld >> Settings Previous Next Entire Chapter in Printable Form Search This text refers to program version 6.2 Settings in the General Ledger - Autotransactions Autotransactions are accounting templates that you can use to simplify the entering of General Ledger Transactions and Purchase Invoices.When a certain type of Transaction occurs repeatedly, you can create a template in which you can store the recurring data, e.g. a particular combination of debit and credit Accounts. Whenever you need to enter a Transaction of this type, you can use the automatic function. This will create a ready-made Transaction, except for the data that is unique for each particular entry. Examples might include rent payments, salary payments and recurring journals. Autotransactions can thus save labor and ensure that you use the correct Accounts every time. Creating a new Autotransaction
When you need to use an Autotransaction in a Transaction, you will do so by entering the Autotransaction Code in the Account field in a Transaction row. When you press Tab or Return, the Autotransaction will be applied to the Transaction. Usually, the result of the first row of the Autotransaction will appear in the Transaction row where you entered the Autotransaction Code. The exception is when the Account field in the first Autotransaction row contains !. In this case, the result of the first row of the Autotransaction will appear in the Transaction row above the one where you entered the Autotransaction Code, overwriting what was previously there. The results of the other rows of the Autotransaction will appear in new Transaction rows underneath. Each Autotransaction row will therefore generate a corresponding Transaction row. There is an example towards the end of this page.
The following example shows a template that distributes an amount across four Accounts on a percentage basis after you have entered that amount in a Transaction row. You might use such a template to allocate shares of overhead costs to Accounts representing four departments. The first row contains an exclamation mark in the Account field and a percentage in the Debit field. The exclamation mark indicates that when you use the Autotransaction in a Transaction, the debit or credit amount in the previous row of the Transaction is to be overwritten by a figure determined by the application of the Autotransaction (in this case, by a percentage of the original figure). That figure will be on the same side (debit or credit) as the original, as the percentage is in the Debit field of the Autotransaction. In other words, the original figure will be reduced by 90%. The # sign in the Description and Tax Code fields signifies that the original Description and Tax Code will be retained. The second line of the Autotransaction will again refer to the original figure and calculate a percentage from it, on the same side (debit or credit) as the original, using a new line in the Transaction. This figure will be posted to Account 61061. The Description and Tax Code fields are empty, meaning that the defaults (in the Account record for 61061) will be used. The third and fourth lines of the Autotransaction will have a similar effect, creating new lines in the Transaction with different percentages of the original figure, posting to Accounts 61062 and 61063 respectively. The fifth line calculates Tax from the original figure at the standard rate of 4.00% and places it in a new row in the Transaction, posting to the Sales Tax Receivable Account on the same side (debit or credit) as the original figure. The final line of the Autotransaction contains an Account number and an equal sign (=) in the Credit field. This signifies that the sum of the previous lines of the Transaction is to be posted to that Account. The posting will be on the opposite side (debit or credit) to the original figure, since the equal sign is in the Credit field. This is an example of a double-sided Autotransaction. The = in the final row means that when you use it in a Transaction, the result will be a Transaction that balances. You can also use a single-sided Autotransaction in a Transaction, in which case you will need to ensure the Transaction balances yourself before you save it. When you enter a Transaction, begin by entering the Account Number for the relevant expense category, and the amount excluding Tax. On the second row, enter the code of the Autotransaction in the Account field. If you know that when you use a particular Account in a Transaction, it will always be in combination with the same Autotransaction, enter that Autotransaction in the Auto.Trans. field in the Account record: When you enter the Account in a Transaction and press Tab or Return, the Autotransaction Code will be brought in to the next row automatically: Enter the amount on the first row as normal, then press Return twice. The Autotransaction will be applied to the Transaction as previously described. Example - Autotransactions in Purchase Invoices You can also use Autotransactions in Purchase Invoices. For example, it may be that you will enter many overhead costs in Accounts Payable from your Vendors' Purchase Invoices. You can enter Autotransaction Codes to the Account field of a Purchase Invoice row in the same way as illustrated above for Transactions, so in our example Purchase Invoices can also be distributed across departments. However, the Autotransaction that you use in this situation should be single-sided: it should not have the final balancing line posting to the Bank Account. When you post the Purchase Invoice to the General Ledger, a balancing posting to a Creditor Account will be made automatically as normal. Payment will reach the Bank Account when you pay the Purchase Invoice. In addition, any Autotransaction used in Purchase Invoices will not need to calculate Tax because that will be handled by the Tax Code. An example single-sided Autotransaction is shown below: The second line of the Autotransaction will again refer to the original figure and calculate a percentage from it, on the same side (debit or credit) as the original, using a new line in the Purchase Invoice. This figure will be posted to Account 61061. The Description and Tax Code fields are empty, meaning that the defaults (in the Account record for 61061) will be used. The third and fourth lines of the Autotransaction will have a similar effect, creating new lines in the Purchase Invoice with different percentages of the original figure, posting to Accounts 61062 and 61063 respectively. When you enter a Purchase Invoice, begin by entering the Account Number for the relevant expense category, and the amount excluding Tax. On the second row, enter the code of the Autotransaction in the Account field. Deleting an Autotransaction
--- In this chapter:
|