Transactions that originate in other modules must be voided in the other modules to maintain accurate accounting records in Microsoft Dynamics GP. If you use Bank Reconciliation to void a transaction that was entered in another module, you receive a warning message that suggests that you void the transaction in the other module. You may continue through this message. However, the original transaction remains in the module in which the transaction was created.
The following conditions must be true before a transaction can be voided:
- The transaction must be fully distributed.
- The transaction cannot be flagged for reconciliation.
- The transaction cannot be reconciled or previously voided.
- The transaction must exist in the CM Transaction file.
- The checkbook that is assigned to the transaction must exist, and the cash account must be assigned to the checkbook.
- Click Transactions, point to Financial, and then click Bank Transactions.
- In the Option list, click Void Transaction to void checks, withdrawals, and adjustments.
- Click the lookup button next to the Checkbook ID field, and then double-click the checkbook ID of the checkbook that is used for the transaction that you want to void.
- Click the lookup button next to the Number field, and then double-click the transaction that you want to void.
Note If you enter a duplicate document number, the first document will be displayed. If you void a transaction that originated in another module,enter the offset accounts and the amounts to reverse in the original distributions.
- Click Void.The distributions in the scrolling window are posted, the checkbook will be updated, and the distribution amounts are posted to the general ledger.
- When you close the Bank Transaction Entry window, the Bank Transaction Posting Journal is printed. Transactions that have been voided since you opened the window are marked with an asterisk (*) on the report.
Article ID: 858473 - Last Review: 14 Jul 2011 - Revision: 1