During normal business operations, thousands of transactions can be processed. When working with this volume of transactions, standard processes might be inadvertently changed or unintended entries made and posted. As a result, the payables or receivables balances on a General Ledger trial balance report might not match the corresponding balance on trial balance reports printed in Payables Management or Receivables Management. Some specific examples might include the following.
- A transaction is posted to-but not through-General Ledger and is deleted before it’s posted in General Ledger.
- A transaction is posted to General Ledger, but the amounts are changed before it’s posted in General Ledger.
Use the Reconcile to GL window to generate a Microsoft Excel spreadsheet that can help you match transactions in General Ledger with the originating transactions in Payables Management and Receivables Management. This spreadsheet can provide information that helps you enter adjusting transactions that reconcile any discrepancies.
1. Open the window at Microsoft Dynamics GP>>Tools>>Routines>> Financial>>Reconcile to GL.
2. Select either Payables Management or Receivables Management as the module.
3. Enter a Date range to reconcile transactions for. Only transactions for which the General Ledger posting date is within the specified range will be included in the list that is generated.
4. Enter the Accounts to be included in the reconcile process. For example, if you’re reconciling Payables Management, enter all the accounts in your general ledger that represent your accounts payable balance in your sub ledger.
5. Click Process to begin generating the report.
Once the report is run, the data will be presented in one of 3 categories:
Matches – Transactions from Receivables Management or Payables Management are “matched” using the transaction source code, document number, transaction date, and transaction amount.
Potentially Matched – Transactions are identified as “potentially matching” if some, but not all the information matches. For example, if the source document code for the transaction in Receivables Management or Payables Management matches the code in General Ledger, but the transaction dates or amounts don’t match, the transactions are considered a potential match. Similarly, the transaction dates and amounts might match, but the source document codes can be different. In this case, the transactions are listed in the spreadsheet as potentially matched.
Unmatched – If a transaction exists in General Ledger, but not Receivables Management or Payables Management-or vice versa-the transaction is considered “unmatched.” For example, a transaction might have been posted in Receivables Management, but not have been posted in General Ledger. Transactions in Work tables aren’t included in the reconcile process.
Although the reconcile routine doesn’t change data automatically, even if unmatched transactions are identified, it will save you a lot of time in tracking down the source of the discrepancies.
Tip: Turning off Allow Account Entry for control accounts like cash, AR and AP will do more to simplify month end GL to sub ledger balancing than any other single thing. This setting in the chart of accounts prevents direct GL entry and requires transactions using these accounts to flow through a sub ledger, thereby preventing rogue GL entries.
~Content Contributed by Pamela Close