The Payment Failures Dashboard is an easy way to track issues with online payment processing. If you are using online payments, you should check the report every day. There are two versions of the report: one for AR (incoming payments from tenants) and one for AP (outgoing payments to vendors made with Bill Pay), described in this article.
To run the Payment Failures report (AP)
Go to Reporting > Electronic Payments > Payment Failures.
Select the AP tab (if not already selected).
The dashboard appears.
By default, the dashboard shows alerts for all bank accounts. If you want to limit it to a specific bank account, complete the Bank field and click Go.
The Alerts show any errors that occur in online payment processing.
Click a number to view details; for example, when you click the number for Incomplete Payee Setup, Breeze displays a list of payments with that error.
Click a payment in the table to open the Payment Information screen, where you can view the payment in question.
For the Incomplete Payee Setup report, you can also click the Missing Fields button to help you complete the payee setup.
Breeze displays a short report that describes what is missing.
Types of Alerts
Failed Payments | The number of payments that failed and that were returned from the service provider. Usually there is some indication of what went wrong, similar to a standardized bank return code. |
NSF Payments | The number of payment transactions that failed because the property’s bank (not the payee’s bank) didn't have sufficient funds. Transactions in this category were sent to the service provider and subsequently returned by the service provider. |
Incomplete Payee Setup | The setup was not completed for the payee. Possible missing information includes bank account information, payee address, email address, or other contact information. Click the Missing Fields button to view a report indicating which fields are missing information. |
Other Returned Items | The number of payment transactions that failed for a reason other than NSF. One example of why a payment may fail is the payee’s bank account is closed. Transactions in this category were sent to the service provider and subsequently returned. |
Bill Pay Pull Failed | The number of payment transactions that encountered a problem during the daily pull of payments from the database. These payment transactions were not successfully pulled by Payable Processor and will not be sent to the service provider unless the reason why they failed is resolved. |
Last Bill Pay Batch | Shows the most recently pulled batch of payments upon selection. If you are using the check printing service, there are two pulls and, depending on which time of day you view this report, the report contains either ACH transactions or check transactions. Check transactions are pulled during the morning and ACH transactions are pulled during the afternoon. |
Expired Transactions | Lists any payment transactions that are older than 14 days. Bill Pay does not process expired transactions. |
Unsent Transactions | The number of payment transactions that were created but have not been sent to the service provider yet. This report allows you to view the payments that are queued up for Bill Pay. |