Transaction Types. Sage Evolution Standard

Below you will find brief information for software Evolution Standard. This user guide will help you to understand the basic functionality of the software which includes features like inventory management, sales and purchases, accounting, and contact management.

PDF

Document

182

• Setting up Inventory and Order Entry

Chapter 9 – Inventory and Order Entry

Transaction Types

Transaction types are critical elements of your processing. Each transaction type determines the sign of the transaction, whether it is a debit or credit, as well as the general ledger accounts into which the system writes balances.

Storing this information in the transaction type makes actual transaction processing a simple data entry process. Very little knowledge or experience is required in order to enter the transactions.

Transaction types also let you group similar transactions together. This is useful for reporting, because you can view similar transactions together. For example, you can create one or more transaction types for exceptional transactions such as processing stock losses. If you do this, you can easily extract these transactions and review them.

You should spend some time deciding on how many transaction types you need. If you create too few, then transaction enquiries will contain so many transactions the process becomes very tedious. If you create too many, then transaction enquiries will yield too few transactions to be meaningful.

When you create a company database, the system creates default transaction types for you. We list these at the end of this section. You should use these transaction types wherever possible.

You access this function via the Maintenance...Inventory...Transaction Types menu option, or via the system tree Accounts Receivable...Inventory...Transaction Types function:

You can link another transaction type to this one. You usually use this to issue inventory when invoicing.

In the Tax check box, specify whether the transaction is subject to tax.

Select the applicable tax group from the drop down menu.

In the General Ledger Accounts frame, you set the debit and credit general ledger accounts for the transaction. Note, however, that you can override these accounts in the inventory group.

The Sage Evolution Standard does not include force options.

Key features

Inventory management
Sales and purchases
Accounting
Contact management

Frequently asked questions

You can create a new company database using the System Manager. To do so, click on the "New Database" button and follow the on-screen instructions. The software will guide you through the process of creating a new database and setting up your company's information.

You can back up your database using the Database Management Console. To do so, click on the "Backup" button and select the database you want to back up. The software will then allow you to choose a location to save your backup file.

You can create a new customer by going to the "Customers" tab in the "Accounts Receivable" module. Click on the "New" button and fill in the customer's information. The software will then create a new customer record.

To process a sales order, go to the "Sales Orders" tab in the "Order Entry" module. Click on the "New" button and fill in the order details. The software will then create a new sales order.

User questions

Michael Y.

Is it possible to add new custom columns or User Defined Fields to document lines or transaction batches, such as Accounts Payable batches, in Sage Evolution Standard?

Adding new custom columns (User Defined Fields) to document lines or transaction batches, like Accounts Payable batches, is not a supported feature in Sage Evolution Standard. While existing grid columns can be customized for display (visibility, width, and sequence), entirely new custom columns cannot be added.

John N.

Is it possible to assign incidents to user groups?

Based on the provided document, you can assign agents to agent groups, which could be a way to manage incidents by grouping users. According to the manual, you use agent groups to group agents together by their function and set access control per group instead of per agent. This could streamline the process of managing incidents by assigning them to a group of users with similar roles or responsibilities. However, the document does not explicitly confirm assigning incidents directly to user groups, but managing access and permissions through agent groups is mentioned.