Editing Payment and Deposit Exception Report

'''Location'''

REPORTS > Management Report > Exception Reporting


'''Purpose'''

The Payment & Deposit Exception Report lists payments and deposits that do not appear to have been processed normally. Use this report to see transactions that may cause higher credit card rates or problems in reconciling your Daily Business Report.


'''Options'''

:Credit card transactions not swiped – If this box is checked, credit card transactions that do not have swipe data will be shown.
:Voice authorized credit card transactions – If this box is checked, credit card transactions that were voice authorized will be shown.
:Different report/received dates – If this box is checked, transactions that have a report date and a received date that are not equal will be shown.
:Sort By – The records can be sorted by the employee who created the transaction or by the date that the transaction was received.


'''Data Selection'''

Payment transactions are selected by the following rules:
:*	The transaction’s report date or received date is within the report’s date range.
:*	The transaction’s report location is selected in the reporting lists.
:*	The contract’s product is selected in the Product list.
:*	The transaction’s swipe data is blank and the "Credit card transactions not swiped" option is selected.
:*	The transaction was voice authorized and the "Voice authorized credit card transactions" option is selected.
:*	The transaction’s report and received dates are different and the "Different report/received dates" option is selected.

Note for Protobase users: This report determines if a transaction was voice authorized or not by looking at the data returned from ProtoBase. If the authorization code (line 0006) is blank, then the transaction was voice authorized.
[[Category:Bluebird]]