Resolve Gl Errors in Altru - A mapping does not exist for...

When performing various tasks that involve revenue, you may encounter an error message such as the one here. This is an error message that is related to the General Ledger and indicates that this transaction is not mapped in your account system. This video will entail how to troubleshoot these error messages and resolve them. While this error message can occur in several places, the process to troubleshoot the problem is exactly the same no matter where it happens. This scenario involves adding a payment from a Constituent record. Let’s begin troubleshooting. All transaction mapping errors follow the same structure; they are broken down by the type of office and parts of the transaction. Altru will list all parts of the transaction in the error. We will want to use this error message as a guide to find the transaction that must be mapped. We will begin by using the beginning of the error message to isolate what office this corresponds to, in this case, this is the Development Office. To access the Development Office, we’re going to go to Administration, General Ledger Setup, go to our account system, then, as Altru let us know in the error message that this is an error related to the mappings, we will click Define Transaction Mappings, Let’s briefly refer back to the error message again. Recall how the beginning of the message dictated which office requires a mapping - as the message indicates “Development,” let’s go into the Development Office. Now that we are in the appropriate office, let’s look at the Revenue type, Application type, and Payment method type contained in the error message. Looking first at the Revenue Type, we will notice that this corresponds to the tabs listed at the top. So in this scenario, we will want to ensure that we are on the “Payment” tab as indicated in the error message. Now that we are under the correct Revenue Type, the error message will now guide us to the appropriate Application Type. Our different Application Types are shown in the first column. Per the error message, this transaction falls under the Application Type of “Donation.” Note that it is possible to have more than one Application Type of the same value. Altru allows us to have different payment methods going to different accounts that fall under the same application type. This can be useful in certain scenarios. For example, donations of cash, checks, and direct debits can credit and debit certain accounts, while donations with payment methods of credit cards can go to different accounts. As we refer back to the error message, we see that Altru has also shown us the appropriate Payment Method that is to be mapped. Our payment methods are found in the second column. With regards to the error message, this scenario entails a payment method of “Other.” Notice that we already have that payment listed in the second column beside our Application Type of "Donation." Let’s click on this transaction and click “Edit.” Here we are able to adjust the credit and debit codes and account strings if they are not already correct. Notice that in this box we can see the Application Type, Payment Method, and subtypes. Again, using the error message as our guide, we see the final portion of the unmapped transaction, the Other subtype of Money Order. Notice that Money Order is not listed as one of our Other subtypes. We can add this by clicking on the box with the arrow. This will bring up a list of the mapped Other subtypes. We can add the value of “Money Order” to the table. After we click OK, then Save, we will now be able to add our payment without the error. Remember, simply use the error message as your guide, and you can’t go wrong when troubleshooting these errors! Thanks for watching!