ANZ Direct Debit Dishonours

An ANZ direct debit file can be exported from the batch to upload and process in your bank. When these direct debits are processed, some are returned as dishonoured when the payment attempt has been unsuccessful, and this file can be imported to Vega to update the payments.

This process can be done from Money > Bank Transactions

The next screen will give you two options:

Click Import and then select ANZ Transactions from the dropdown and Import Transactions:

You will then be able to upload your direct debit dishonour file:

Vega will load the transactions from your banking file into the import view. These should all show as Transaction Match, as the payments already exist in Vega and you will see that the amount is imported as a negative for this file type.

The payments will all be selected as default and you can then click the button Create Batch From Selected Transactions to load the pop-up shown below:

You can select an existing un-posted batch (this would usually be the batch that the payments have been initially created in) or New from the dropdown to create a new batch and move the payments to this.

The batch code is the name of your batch.

The options for Pay Type, GL Code, Campaign, Receipt Document, and Send By are not required for this type of import, as they only apply to new payments being created.

Click Post to Batch to update the payments.

The specific Dishonour reason is imported, and the payment's pay details will be updated based on this code, including the reason as shown below:

DISHONOUR-01 - Unauthorised

DISHONOUR-02 - No Account

DISHONOUR-03 - Insufficient Funds

DISHONOUR-04 - Payment Stopped

DISHONOUR-05 - Authority Cancelled

DISHONOUR-06 - Account Closed

Payments with dishonour reasons 01, 02, 04, 05, or 06 will be updated to suspend the recurrence automatically as these will not be able to generate successful payments without the details being updated.

All Suspended recurrences can be checked from Money > Recurring Payments > Suspended. You can also setup a workflow to automatically notify the donor or an admin user of these suspended recurrences so that they can be contacted to update the details.

You can now go to your selected batch to see the updated payments as shown below:

The dishonour reason has been updated, and the status is now Payment Declined.

The connected recurrences for these payments will also be updated based on the specific recurring retry settings applicable, as long as this is the most recent payment for the recurrence.

See the article, Recurring Payments auto-generated processing for full details on how the recurrence will be updated.