Troubleshoot Customer Aging report

Some transactions might not have been imported correctly.

Solution: Determine if any transactions are missing from the originally imported transactions. Depending on what you find, take one of the following actions:

• If transactions are missing: Import the missing transactions as historical transactions.
• If transactions are not missing: Add a journal entry to make the GL beginning balance match the amount of the originally imported transactions.

Possible causes: 

• If the payments are made before the Invoice date and the Aging report is run between the Payment date and Invoice date, the payment amount is not reflected in the aging report.
  Example

  For example, a transaction has the Invoice date of 01/01/2022 and the payment date is 12/31/2020. Now, if the Aging report is run on 12/31/2020 the payment amount does not appear for the Aging report.

  Solution

   Go to Accounts Receivable > Setup > Configuration and scroll down to Enable functionality. Remove the checkmark from the Payment dates must be greater than their invoice dates option. Run the report again.

• Reversals done in the wrong period. Check your reversals to see if the transaction date matches the reversal date. If not, the transaction was probably reversed in an incorrect period.
  Solution 

  Make a journal entry to remove the reversal from the incorrect period. Then, make another journal entry to add the reversal to the correct period.

• Accounts Receivable misconfigured.
  Solution 

  • Verify that the configuration is correct, and correct if needed. On the Configure Accounts Receivable page, check the following:
  • Correct aging periods. For the first line of the Aging period range, leave the Minimum range blank and set the Maximum range to 0.
  • Make sure to the checkbox for Display reversals as historical transactions is checked.

Typically, this means that you are running the aging report at the entity level and the customer you selected is restricted to the top level. While you can view aging for customers who are restricted to the top level, you cannot access their information records from the entity level.

Solution: Run the aging report from the top level.

If the customer is restricted to the top level, their transactions appear in the aging report only when it is not filtered by location.

Solution: Customize the report to clear the Location filter.

This is expected behavior. Journal entries made directly to the Accounts Receivable GL account do not flow to the Accounts Receivable subledger.

Solution: Manually reconcile and track direct journal entries to ensure the GL ties to the AR aging report.

If the journal entries are coded to the incorrect GL accounts, edit the journal entries to fix the coding.

Some accounts might not be configured as overriding the GL accounts in AR or might have been configured after the override was set.

Solution:  Configure the use of overriding GL accounts in the AR configuration and select the correct accounts to be overridden. Transactions created after that change are included in the aging report.

This is expected behavior when the transaction has met the criteria for removal:

• The age due date is reached for the transaction (for example, it’s day 31 on a 0-30 day report)
• The AR sales invoice is paid
• A credit or advance is applied to the AR sales invoice
• The AR sales invoice is deleted or reversed

Solution: Re-run the report to see any late changes.

The Aging report is based on the GL posting date, but the Select date you chose causes a mismatch if a payment was received before the AR sales invoice date.

Solution: Use either of the two following procedures to tie the balances:

• Make journal entries to:
  1. Clear the payment.
  2. Add the payment in the right period, by using the AR sales invoice date or any date thereafter.
• Within the AR application:
  1. Reverse the payment.
  2. Re-create the payment (select the AR sales invoice for payment again).

Example: You create AR sales invoice on December 1 and erroneously recorded that payment was made on November 15. When you make a journal entry to add the payment or select the AR sales invoice for payment again, use December 1 or any date thereafter as the payment date.

Solution: Determine the amount of the transactions that were imported as historical and make a journal entry to balance the AR account.

The exchange rate type might be populating the amounts to the Intacct daily rate, causing the report to revaluate based on the daily rate.

Solution: Make sure that no default exchange rate is selected. (The Exchange rate field is blank.)

The Exchange Rate Type field must be set manually to see information from Entities with Base Currencies other than the one you selected in the Reporting Currency field.

You might be running the Aging report based on the GL posting date and AR GL report based on the Document date.

Solution: Run the AR Subledger and Customer Aging reports based on the GL posting date to tie the balances to the GL.

Solution: Advances and overpayments can be tracked in separate GL accounts from other receivables. For many companies, these transactions are tracked in a GL account associated with Cash Management, such as a deposit liability account. Depending on how your account groups and financial reports are set up, this can cause your balance sheet to differ from your AR aging.

If your balance sheet does not tie to AR aging:

1. Review the GL accounts selected for Customer advances and Overpayment in your AR configuration.
2. Review the account groups used to represent Accounts Receivable in your balance sheet report.