Correcting Credit Memo Application Errors in Dynamics GP: A Voiding Guide

Table of Contents

Managing accounts payable efficiently is crucial for any business. In Microsoft Dynamics GP, the Payables Management module provides robust tools for handling vendor invoices and credit memos. However, situations can arise where a credit memo is incorrectly applied to an invoice. This can occur through manual user error, where a credit memo is mistakenly linked to the wrong invoice during the application process. It can also happen automatically during processes like check runs if existing unapplied credit memos are configured to be automatically applied. Furthermore, a common misconception is that voiding a check will automatically unapply any associated credit memos, which is not the case in Dynamics GP.

When a credit memo is applied to the wrong invoice, it misrepresents the outstanding balances for both the vendor and the specific documents involved. Correcting this requires a specific process to unapply the credit memo so it can be correctly applied to the intended invoice. The primary method to achieve this in Dynamics GP is by voiding the incorrectly applied credit memo. The process for voiding a credit memo differs slightly depending on whether the credit memo was fully or only partially applied to the incorrect invoice(s).

Understanding these distinct scenarios and the correct steps to void the credit memo is essential for maintaining accurate financial records and ensuring correct vendor balances within Microsoft Dynamics GP. This guide outlines the procedures for voiding both fully and partially applied credit memos, enabling users to rectify application errors and regain control over their payables transactions. Adhering to these steps helps prevent compounding errors and ensures that credit memos are available for correct application to the appropriate outstanding vendor obligations. Proper handling of these situations contributes significantly to the integrity of financial data and streamlines the accounts payable workflow within the system.

Voiding a Fully Applied Credit Memo¶

When a credit memo has been completely applied to one or more invoices, the process to correct the application error involves voiding the credit memo itself. Voiding a historical transaction like a credit memo that has been fully applied will effectively reverse the application and mark the credit memo as voided in the system. This makes the original credit memo amount available again, although it is now represented by the voided transaction and typically a corresponding voided credit memo or adjustment. The voiding process ensures that the system’s records accurately reflect the reversal of the transaction and its application history.

The steps to void a fully applied credit memo are straightforward and utilize the historical transaction voiding functionality within Payables Management. This function is specifically designed for transactions that have already been posted and potentially applied or paid. By selecting the credit memo for voiding, the system handles the unapplication and reversal simultaneously.

1. Navigate to the Void Historical Transactions window. Access this by selecting Transactions from the main menu, pointing to Purchasing, and then selecting Void Historical Transactions. This window is specifically designed for handling transactions that have been posted and are no longer open.
2. In the Void Historical Payables Transactions window, locate the credit memo that was applied incorrectly. This window displays historical transactions for vendors. You will need to identify the specific credit memo document number or voucher number.
3. Once the credit memo is located, select the Void checkbox next to the relevant line item. This action flags the transaction for voiding.
4. After selecting the credit memo(s) to be voided, select the Void button within the window. The system will then process the voiding operation.
5. Upon selecting Void, you will typically be prompted to print posting journals related to this transaction. These journals provide an audit trail of the voiding activity. Select the appropriate destination for the reports (e.g., screen, printer, file) and then select OK.
6. After the voiding process is complete and journals are handled, close the Void Historical Payables Transactions window. The credit memo is now voided, and its amount should be available to be applied correctly. Note that the original credit memo will be marked as voided, and a corresponding voiding transaction may be created depending on your system setup.

This process effectively cancels the credit memo and its incorrect application. The original amount of the credit memo is now available for correct application, although you might need to issue a new credit memo depending on company policy regarding voided documents. It is crucial to verify the vendor’s balance and the status of the related invoice(s) after completing this process to ensure the desired outcome was achieved. The voiding journals should be reviewed and filed for audit purposes, providing documentation of the correction made within the system. This method is clean and direct when the entire credit memo amount was applied and needs to be reversed.

Voiding a Partially Applied Credit Memo¶

Correcting an error where a credit memo was only partially applied to an incorrect invoice presents a more complex scenario in Dynamics GP. The system does not allow voiding a historical transaction if it still has an open or unapplied balance. Therefore, to void a credit memo that is partially applied, its entire balance must first be applied, effectively closing it out. Only then can it be treated as a fully applied historical transaction and voided using the method described above. This workaround involves creating a temporary, or “dummy,” invoice to absorb the remaining unapplied balance of the credit memo, allowing the credit memo to be fully applied and subsequently voided.

This technique ensures that the credit memo reaches a fully applied status, satisfying the system’s requirement for voiding historical applied documents. Once the credit memo is fully applied (partially to the original incorrect invoice, and partially to the dummy invoice), the standard voiding process for fully applied transactions can be utilized. After the credit memo is successfully voided, the dummy invoice, which served only as a placeholder, must also be voided to clean up the vendor’s open transactions and remove the temporary entry.

Creating a Dummy Invoice¶

The first step in voiding a partially applied credit memo is to create a temporary invoice equal to the unapplied amount of the credit memo. This dummy invoice will serve as the document to which the remaining credit memo balance will be applied. The purpose is to bring the credit memo’s status to ‘fully applied’ so it can be voided. This invoice should be created for the same vendor as the credit memo to facilitate the application process.

1. Open the Payables Transaction Entry window. You can access this by selecting Transactions from the main menu, pointing to Purchasing, and then selecting Transaction Entry. This is the standard window used for entering new payables documents.
2. In the Payables Transaction Entry window, create a new invoice transaction for the vendor associated with the credit memo you need to correct. Ensure the transaction type is ‘Invoice’.
3. Enter a clear and distinct document number for this dummy invoice, perhaps including “DUMMY” or “VOIDHELP” in the number, along with the date, to easily identify it later. This is crucial for tracking and voiding the dummy invoice.
4. In the Purchases field, enter the exact amount of the remaining unapplied balance on the credit memo. This ensures that applying the dummy invoice will fully consume the credit memo’s remaining value. Leave the Batch ID field blank unless your system requires batches for single transactions; leaving it blank allows for immediate posting.
5. Review the entry for accuracy, ensuring the vendor ID and amount are correct. Then, select Post to finalize the creation of the dummy invoice.
6. Upon posting, you will be prompted to print posting journals. Select the appropriate destination and then OK to print them.
7. Close the Payables Transaction Entry window. The dummy invoice now exists as an open transaction for the vendor with a balance equal to the credit memo’s unapplied amount.

This dummy invoice now sits as an open payable for the vendor. It doesn’t represent a real liability but serves a critical technical purpose in the voiding process. It provides a target for the remaining portion of the credit memo to be applied against, thus transitioning the credit memo to a fully applied status. It is important to document this dummy transaction well so it is not mistaken for a legitimate invoice later.

Applying the Dummy Invoice to the Credit Memo¶

With the dummy invoice created, the next step is to apply the remaining unapplied balance of the credit memo to this dummy invoice. This action will change the status of the credit memo from partially applied to fully applied, enabling the subsequent voiding step. The application process is performed using the standard Payables Documents application window.

1. Access the Apply Payables Documents window. Navigate by selecting Transactions from the main menu, pointing to Purchasing, and then selecting Apply Payables Documents. This window is used to link credit memos, payments, and returns to outstanding invoices.
2. In the Vendor ID list, select the vendor associated with the credit memo and the dummy invoice.
3. In the Document No. list, select the specific credit memo that was partially applied and needs to be corrected. The window will then display the open transactions for this vendor, including the dummy invoice you just created, and show the remaining unapplied amount of the selected credit memo.
4. Locate the dummy invoice in the list of open documents. Select the apply checkbox that is next to the dummy invoice. The system will propose applying the remaining unapplied amount of the credit memo to this invoice.
5. Confirm that the amount being applied is the full remaining balance of the credit memo, effectively making the credit memo’s unapplied amount zero. Select OK to process the application. The system will record this application link.

At this point, the credit memo is now considered fully applied within Dynamics GP. It has been applied partly to the original incorrect invoice(s) and partly to the dummy invoice. This status change is key, as it now allows the credit memo to be voided using the historical transaction voiding utility, treating it as a fully applied document. The dummy invoice will now have a zero balance or a balance reduced by the credit memo amount, depending on whether the credit memo’s remaining balance exactly matched the dummy invoice amount.

Voiding the Credit Memo¶

Now that the credit memo is fully applied (due to the application against the dummy invoice), you can proceed to void it using the same historical voiding process as described for a fully applied credit memo. Voiding the credit memo will reverse its application against both the original incorrect invoice(s) and the dummy invoice.

1. Return to the Void Historical Transactions window. (Transactions > Purchasing > Void Historical Transactions).
2. Find the credit memo document number that you want to void. It should now appear in this window because it is in a fully applied state (even though partially applied to the dummy).
3. Select the Void checkbox next to the credit memo.
4. Select the Void button. The system will confirm you want to void the transaction and will unapply it from all documents it was linked to, including the original incorrect invoice(s) and the dummy invoice.
5. As prompted, print the posting journals, selecting the appropriate destination (screen, printer, file) and clicking OK.
6. Close the Void Historical Payables Transactions window.

The credit memo is now voided in Dynamics GP. It is unapplied from the original incorrect invoice(s) and the dummy invoice. The amount is effectively reversed. The original credit memo document is marked as voided in the system. The incorrect invoice(s) will revert to their state before the partial credit memo application, showing their full outstanding balance again.

Voiding the Dummy Invoice¶

The dummy invoice served its purpose by allowing the partially applied credit memo to be fully applied and subsequently voided. It is not a real liability and should be removed from the open payables to maintain data cleanliness. Since it is an open transaction (even if its balance is now zero due to the application reversal when the credit memo was voided), it needs to be voided using the ‘Void Open Transactions’ functionality.

1. Navigate to the Void Open Transactions window. Access this by selecting Transactions from the main menu, pointing to Purchasing, and then selecting Void Open Transactions. This window is used for voiding transactions that are still open and have not been moved to history.
2. In the Vendor ID list, select the vendor for whom you created the dummy invoice.
3. Locate the dummy invoice in the list of open transactions. Remember the distinct document number you assigned earlier.
4. Select the Void checkbox for the dummy invoice.
5. Select the Void button. The system will process the voiding of this open invoice.
6. You will be prompted to print posting journals for this voiding activity. Select the appropriate destination and select OK.
7. Close the Void Open Payables Transactions window.

The dummy invoice is now voided and removed from the open payables list. At this point, the original credit memo is voided and unapplied, the original incorrect invoice(s) have their full balance restored, and the temporary dummy invoice has been voided. The state of the vendor’s account and the relevant documents should now reflect the situation before the incorrect credit memo application occurred, minus the voided credit memo.

Removing the Dummy Invoice from History (Optional but Recommended)¶

The dummy invoice, while voided, still exists in the historical payables tables. To completely remove this temporary transaction from the system’s history and prevent it from cluttering historical inquiries and reports, you can use the Remove Transaction History utility. This step is optional but recommended for data hygiene.

1. In Microsoft Dynamics GP, go to the main menu. Select Microsoft Dynamics GP, point to Tools, then Utilities, then Purchasing, and finally select Remove Transaction History.
2. In the Remove Payables Transaction History window, you need to specify the transaction(s) to remove. To remove only the dummy invoice, use the Ranges section. In the Ranges list, select either Voucher Number or Document Number, depending on which identifier you used and prefer to filter by.
3. In the From and To fields that appear, type the exact voucher number or document number of the dummy invoice you created and voided. This restricts the removal process to only this specific transaction.
4. In the Remove section, select the appropriate checkboxes to ensure all related data for the dummy invoice is removed. Select Transactions to remove the main transaction record and Distributions to remove the associated GL distribution records. You might also consider removing Apply records if the dummy invoice had any applications against it, though voiding usually handles this.
5. It is highly recommended to print a report of the transactions being removed before processing. Select the Report checkbox in the Reports section (if available/applicable in your version) and then select Process.
6. Confirm the removal when prompted. When you are prompted to print the removal report, select the appropriate destination and select OK. This report serves as documentation of the removed data.
7. Close the Remove Payables Transaction History window.

The dummy invoice is now permanently removed from your Payables history tables. This leaves your data clean, containing only legitimate transactions. This final step completes the process of correcting the partially applied credit memo error without leaving unnecessary temporary transactions in the system.

Best Practices and Considerations¶

• Test in a Test Environment: Before performing these steps in a live production environment, it is strongly recommended to practice and confirm the process in a test or development environment using a backup of your live data. This allows you to understand the impact of each step without risking your actual financial records.
• User Permissions: Ensure the user performing these actions has the necessary security permissions in Dynamics GP for Payables Transaction Entry, Apply Payables Documents, Void Historical Transactions, Void Open Transactions, and Remove Transaction History utilities.
• Audit Trail: Always print and review the posting journals and removal reports. These documents provide a crucial audit trail for changes made to transactions, which is vital for internal control and external audits.
• Communication: If the original incorrect application or the need for correction involves multiple departments (e.g., Accounts Payable and Purchasing), ensure clear communication about the steps being taken.
• Preventing Errors: Implement internal controls and training to minimize incorrect applications in the future. Encourage users to double-check vendor IDs, document numbers, and amounts during manual application processes. Reviewing the automatic application settings during check runs is also advisable.
• Alternative Approaches: While voiding the credit memo is the standard method to reverse an application and make the amount available again, depending on the specific business scenario and policy, issuing a new credit memo might sometimes be considered if voiding the original is problematic (e.g., due to strict document numbering or audit requirements). However, this adds complexity and potentially duplicates documentation.

Successfully navigating these steps ensures that incorrect credit memo applications can be rectified in Dynamics GP. By understanding the distinction between fully and partially applied credit memos and following the appropriate voiding process, businesses can maintain accurate accounts payable records and facilitate correct future transactions.

---

We hope this detailed guide helps you effectively correct credit memo application errors in Microsoft Dynamics GP. Have you encountered similar issues? Do you have any alternative methods or tips you’d like to share? Please leave a comment below!