 Introduction to Settings in the Nominal Ledger
Account Classification Types
Account Classifications
Account Short Codes
Account Transfers
Accounting Periods
Auto Eliminations
Autotransactions
- Entering, Inspecting and Changing Autotransactions
- Example in Transactions and Simulations
- Example in Purchase Invoices and Expenses
- Example Automatic Autotransactions (Subsystem Autotransactions)
- Deleting an Autotransaction
Bank Transactions
Brought Forward Balances
Budget Classes
Budget Keys
Calculation Formulae
Electronic VAT Declaration
Fiscal Years
Income & Expense Book
Liquidity Report Info
N/L Accruals
Number Series - Simulations
Number Series - Transactions
Presentation of Balances
Rate Gain/Loss
Rate Gains/Losses
Reconciliation Codes
Reconciliation Settings
Report Settings
Sub Systems
Sub-ledger Control Accounts
Tag/Object Type Control
Tag/Object Types
Tax Account Groups
Tax Accounts
Tax Reports
Tax Templates
Tax Transactions
Tax Trans Fields
Tax Trans Maps
Tax Trans Settings
Template Transactions, Template Transactions - Accounts
Transaction Settings
VAT Code Control
VAT Code on Transaction Rows
VAT Codes
VAT Declarations
XBRL Reporting Elements, XBRL Reporting Settings
 Tutorials for Standard Accounts
Search HansaManuals.com HansaManuals Home >> Standard ERP >> Nominal Ledger >> Settings Eelmine Järgmine Prindi kogu peatükk Otsi Juhend HansaWorld Enterprise'i versioonile 8.5 Autotransactions - Example in Transactions and Simulations The Autotransactions feature in Standard ERP:
This page illustrates the use of Autotransactions in Transactions and Simulations using an example. In this example, we will use an Autotransaction that distributes an amount to four Tags/Objects on a percentage basis after you have entered that amount in a Transaction row. You might use such an Autotransaction to allocate shares of overhead costs to four departments.
The second row in the Autotransaction will add a new row to the Transaction. It will again calculate a percentage from the original amount, placing the result in the new row on the same side (debit or credit) as the original. The # sign in the A/C, Description and VAT Code fields signifies that the Account, Description and VAT Code originally specified will be used in the new row, which will contain "DEPT2" in its Tag/Object field. The third and fourth rows in the Autotransaction will have similar effects, adding new rows to the Transaction with different Tags/Objects and percentages of the original figure. The fifth line calculates VAT from the original figure at the standard rate of 20% and places it in a new row in the Transaction, posting to the Input VAT 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 Transaction rows (i.e. a balancing amount) 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 or Simulation, begin by entering the Account Number for the relevant expense category and the amount excluding VAT in the first row. In the second row, enter the Code of the Autotransaction in the Account field:
If you would like to be warned if you try to change the Autotransaction on the next row, select the Warn on Overwrite of Autotransaction option in the Transaction Settings setting. --- Settings in the Nominal Ledger:
|
