Search HansaManuals.com HansaManuals Home >> Standard ERP >> Nominal Ledger >> Settings Previous Next Entire Chapter in Printable Form Search This text refers to program version 4.0 Autotransactions - Example The following example shows a template which distributes an amount across four Objects on a percentage basis after an amount has been entered to the Transaction. It might be used to allocate shares of overhead costs to 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 the Autotransaction is specified in a Transaction, the amount of 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 has been entered to the Debit field of the Autotransaction. In other words, the original figure entered will be reduced by 90%. The Object specified will be entered to the Object field of the Transaction row and the Description 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. The # sign in the Account and Description fields signifies that the Account and Description originally specified are to be used in the new line, which will contain "DEPT2" in its Object field. The third and fourth lines of the Autotransaction will have a similar effect, creating new lines in the Transaction with different Objects and percentages to the original figure. The fifth line calculates VAT from the original figure at the standard rate of 17.5% and places it in a new row in the Transaction, posting to the VAT Inputs 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. When a Transaction is entered, begin by entering the Account code for the relevant expense category, and the amount excluding VAT. On the second row, enter the code of the Autotransaction in the Account field. The example Autotransaction is designed to be used from the Nominal Ledger and is therefore double-sided to produce a balancing Transaction. It may be that many overhead costs will be entered from the Suppliers' Purchase Invoices in the Purchase Ledger. Autotransaction Codes can be entered 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 used in this situation should be single-sided: it should not have the final balancing line posting to the Bank Account. When the Purchase Invoice is posted to the Nominal Ledger, a balancing posting to a Creditor Account will be made automatically as normal. Payment will reach the Bank Account when the Purchase Invoice is paid. In addition, any Autotransaction used in the Purchase Ledger will not need to calculate VAT because that will be handled by the VAT Code. Single-sided Autotransactions can also be entered to the Account field of a Sales Invoice row. |