Did you run the correct general ledger report?
Use Ledger Report (GL290) to balance Invoice Accrual Reconciliation (AP136). The general ledger trial balance report lists transactions posted to a specific general ledger account.
Did you run Ledger Report (GL290) and Invoice Accrual Reconciliation (AP136) with the same cut-off date?
Run both reports with the same cut-off date to include and exclude the same information.
Did you post transactions through the end of the period?
Run Journal Posting (GL190) to post transactions written to the General Ledger Transaction file through the period end. If you do not, Invoice Accrual Reconciliation (AP136) might show transactions as paid or posted, but Ledger Report (GL290) will not show the unposted transactions.
Do accounts payable transactions remain unposted?
Run Journal Edit Listing (GL240) with All in the JE Status field to list unposted transactions. If any transactions with a current posting date remain in the file, the balance shown on Ledger Report (GL290) is incorrect. Run Journal Posting (GL190) to post the transactions.
You can also use Journal Control (GL45.1) to list journal entries. Use the filter to view only Accounts Payable entries that are released.
Does Invoice Accrual Reconciliation (AP136) show transactions paid and not posted?
Normally, transactions appear as posted and not paid. If the report shows transactions paid and not posted, check the posting date on the report. If the transaction has a current posting date, ensure you have run Payment Closing (AP170), Invoice Distribution Closing (AP175), and Invoice Reinstatement (AP190) to write transactions to the General Ledger Transaction file and run Journal Posting (GL190) to post the transactions. If the transaction has a future posting date, ensure you specified the correct date. If the report shows many transactions with incorrect posting dates, consider setting up system control in General Ledger. For more information about system control, see the General Ledger User Guide. You can use AP Inquiries (AP90) and AP Distribution Inquiry (AP95) to review invoice, payment, and distribution details.
Does Invoice Accrual Reconciliation (AP136) show old due dates on transactions posted and not paid?
Check the due dates on the report for transactions posted and not paid. If a transaction shows an old due date, find out why the invoice has not been paid or if it was paid with a future payment date. You can use AP Inquiries (AP90) and AP Distribution Inquiry (AP95) to review invoice, payment, and distribution details.
Does Invoice Accrual Reconciliation (AP136) show transactions partially paid?
Use AP Inquiries (AP90) and AP Distribution Inquiry (AP95) to review transactions that show the posted amount not equal to the invoice amount. Invoices are never partially distributed. Ensure partially paid transactions are correct.
Does Ledger Report (GL290) show a higher or lower balance than Invoice Accrual Reconciliation (AP136)?
A higher balance on Ledger Report (GL290) often indicates that a Payment Closing (AP170) or Invoice Distribution Closing (AP175) canceled transaction was not posted. A higher balance on Invoice Accrual Reconciliation (AP136) often indicates an Invoice Distribution Closing (AP175) or Period Closing (AP190) transaction was not posted. The reason for not balancing might be due to a combination of these and other issues.
Did all transactions with a system code other than AP, AD, and AC get backed out of the Ledger Report (GL290) balance?
Invoice Accrual Reconciliation (AP136) shows only accounts payable transactions. The Ledger Report (GL290) balance might include transactions with a GL source code. For example, if you ran Payment Closing (AP170) and it ended in error, it will not write transactions to the General Ledger Transaction file. You must create a journal entry in General Ledger to debit the accrual account. This transaction should remain in the Ledger Report (GL290) balance because Invoice Accrual Reconciliation (AP136) lists the transactions as paid.
Did you use the accrual account as an expense account during invoice entry?
If you post an invoice with the accrual account specified as an expense account, the accrual account is understated. Run Invoice Distribution History (AP275) for your accrual account to find out if this happened.
Did you use the invoice accrual code on prepayments or employee advances and expenses?
Consider defining an invoice accrual code and account to use on prepayments and employee advances only. When you pay prepayments and advances, make the debit entry to a prepaid asset account, not the accrual account. If you use the same invoice accrual code, the accrual account might be severely understated. Ensure you specify offsetting invoices and employee expenses with the same invoice accrual code as the prepayment or employee advance.
Did the posting date on an invoice accrual account transaction change?
If you changed a transaction posting date in Journal Control (GL45), Invoice Accrual Reconciliation (AP136) will not reflect the new posting date. For example, an Accounts Payable transaction might have posted with a date of 06/01/00, but you later changed the date in General Ledger to 07/01/00. This transaction would appear in Accrual Reconciliation (AP136) for June and in Ledger Report (GL290) for July.
Did you select the same accrual account on more than one invoice accrual code?
Ledger Report (GL290) shows the total accrual account balance. If you run an individual Invoice Accrual Reconciliation (AP136) report for each invoice accrual code, the sum of the reports shows the total accrual account balance.
Was the general ledger accrual balance converted?
If the accrual balance was converted, the accounts payable detail must also be converted for Invoice Accrual Reconciliation (AP136) to accurately reflect the balance. If the accounts payable detail was not converted, subtract the original balance from the ending balance on the Ledger Report (GL290) report.