A user is reconciling transaction balances in the closing process. Why would the user run the Invoice Exceptions Report?
-
A. to identify transactions that do not appear in the Aging report
-
B. to identify order lines with workflow stuck
-
C. to identify transactions that do not appear in the Transaction Register
-
D. to identify unposted transactions
The Invoice Exceptions Report specifically identifies transactions that are missing from the Aging report, often due to data inconsistencies or timing issues. This helps close process discrepancies. It does not identify workflow-stuck orders, Transaction Register missing items, or unposted transactions.
The Invoice Exceptions Report is used during period-close reconciliation to flag transactions that should appear in the Aging report but don't — often due to setup issues or data problems — helping ensure the aging and transaction registers stay consistent. It's not primarily about workflow-stuck order lines or unposted transactions, which are surfaced by other diagnostic reports.