GL mappings are used to default GL distributions on transactions. This prevents data entry users from having to enter GL information.
How you choose to map transactions to accounts and account codes depends upon your organization’s needs. You may broadly define accounts or account codes for revenue or cash. In other cases, your organization may be more specific and want to define an account for contributions revenue or benefits revenue. You may further define your account codes for specific payment methods, benefits, or other criteria. Each category in the Transaction Mappings area is tailored for that category’s unique situation. For example, when you map account codes for Development Office payments, you have the option to define payment methods like cash or credit card. If you choose credit card, you can also define which credit card subtypes.
We recommend that you evaluate your accounts and account codes before you map them. Keep track of which criteria you need for each combination. This will not only help you to determine the appropriate mapping, but also help you to avoid situations where you are unable to save a transaction. Account codes are always present in account numbers. Since GL distributions are created before a transaction is saved, you must define the mapping in order to save a transaction.
To define transaction mappings, click Define Transaction Mappings on the General ledger setup page. In the Category column of the Transaction mappings grid, select the office you want to work with. When you select an office, the Transaction mappings page for that office appears.
| • | Map Transactions for Development Office |
| • | Map Transactions for Ticketing Office |
| • | Map Transactions for Fixed Assets Office |
| • | Map Transactions for Treasury Office |
Map Transactions for Development Office
Map Transactions for Ticketing Office