Transaction Types Workspace

Use this workspace to create, edit, and delete transaction types.

Maconomy uses a number of posting journals such as General Journals, Vendor Invoice, and so forth. You can use these journals to create transactions. These transactions are identified by their transaction numbers and their transaction types.

Different journals can support different transaction types. You can define different transaction types for different companies and different users. You can configure which transactions are allowed in which journals by creating different transaction type groups.

You cannot delete a transaction type that is used in a transaction group or in entries. You cannot rename transaction types. Maconomy provides a number of predefined transaction types. If you plan to change them, it is a very good idea to do this before you start using transaction types, because you cannot rename or delete transaction types after they are in use.

Setting Up Transaction Types, Transaction Type Groups and Journal Setups

Transaction Types, Transaction Type Groups, Journal Setups, and Posting Period Setups are all related. You must understand these relationships and plan what your needs are before you start setting any part of this up.

Together, Transaction Types, Transaction Type Groups, and Journal Setups enable you to specify very complex setups, where different companies use different transaction types and transaction number series, or where users have differentiated access to posting in journals, and so forth. On the other hand, if you do not need the more complex functionality, Maconomy provides standard functionality that works "out of the box."

The easiest way to explain and understand the relationship is to begin at the top, at the company level. When you implement a setup, however, you must start the setup at the lowest level, by creating Transaction Types.

In the Company Information workspace, you select a Journal Setup for the company. When you create a company, Maconomy suggests the Standard journal setup by default. If other journal setups exist, you can select one of those.

In the Journal Setup workspace you can create and change journal setups. A journal setup represents a setup of all posting journals in Maconomy. Therefore, a journal setup consists of a header part (consisting of the number and name, as well as the access level of the setup), and a table part that has exactly one line for each posting journal type in Maconomy. You can select a Transaction Type group for each of these journal types. There is also some information about the journal type displayed here that can otherwise be difficult to get an overview of (basically, whether the journal type uses a transaction number series, and whether you set the transaction manually or you must specify a default transaction type.)

Maconomy provides the Standard default journal setup. You cannot delete or rename it. When you create (and save) a journal setup, Maconomy adds a line to the Journal Setup Lines sub-tab of the Journal Setup workspace for each journal type. You cannot rename or delete those lines. You must then specify a transaction type group for each of these journal types. If you want to create a journal setup that is similar to an existing journal setup, copy the existing journal setup and change the relevant transaction type groups.

You define the transaction type groups in the Transaction Type Groups workspace. The header part is quite similar to the header of the journal setup: you must give the transaction type group a number and name, and you can set an access level.

In the Transaction Type Group Lines sub-tab of the Transaction Type Groups workspace, you can add lines. Each line corresponds to a transaction type. There can be as few or as many transaction types in a transaction type group as you need. However, a transaction type group must have at least one transaction type.

Additionally, you can (but are not required to) set a Username and Transaction Number Series, and you can specify whether this is the default transaction type for the username, or whether the transaction type has a default transaction number series.