A user is reconciling transaction balances in the closing process. Why would the user run the Invoice Exceptions Report?

Question

Options

• Ato identify unposted transactions
• Bto Identify AutoInvoice validation errors
• Cto Identify order lines with workflow stuck
• Dto identify order lines with a back order credit hold
• Eto identify transactions that do not appear In the Aging report
• Fto identify transactions that do not appear In the Transaction Register

• A
  3% (1)
• B
  7% (2)
• C
  3% (1)
• D
  14% (4)
• E
  72% (21)

Explanation

During the closing process, reconciling AR balances requires that every open transaction appears in the Aging report - if it doesn't, the balances won't tie out. The Invoice Exceptions Report is specifically designed to surface transactions that are missing from the Aging report (E), which is precisely the gap a user needs to investigate when reconciling.

Why the distractors are wrong:

• A - Unposted transactions are found via the Unposted Items or Journal Entry reports, not the Invoice Exceptions Report.
• B - AutoInvoice validation errors are surfaced in the AutoInvoice Execution Report during the import process, not during closing reconciliation.
• C & D - Workflow holds and back-order credit holds are Order Management concepts tracked in OM, not AR closing reports.
• F - The Transaction Register is a separate report; the Invoice Exceptions Report targets the Aging report discrepancy, not the Transaction Register.

Memory tip: Think "exceptions = missing from Aging." If a transaction isn't aging, it's an exception - and the Invoice Exceptions Report is your tool to catch it before you close the period.

No community discussion yet for this question.