Creating outgoing banking transactions
When a user approves invoicing documents paid by direct debit or when he creates payment requests for customers, Zero Friction will automatically mark these as Ready for payment collection.
Selecting these invoices and execute the Add all to payment request transaction action will create an outgoing banking transaction file. This file which will be in PAIN format has to be downloaded and then subsequently be uploaded to the bank.
The outgoing banking transaction file will get the status: To confirm by bank.
Changing collection dates
The user can easily modifiy the collection date of the outgoing banking transaction files.
The general settings of the collection date are set up in the configuration menu of the organisation. The user can specify the number of days after approval of the invoice that the amount will be collected from the customer's account. For each type of invoicing document (advance, invoice, end note, correction note...) the user can specify the SDD payment delay.
Still, if the user wants to manually override the collection date of an outgoing bank transaction, this can be done on its detail page.
Overriding bank confirmation manually
It is possible to manually override the state of the payment request file if it is in the state of To confirm by bank. The payment request file will be Closed and all the transactions will be processed as being paid. The customer's balance will be adjusted accordingly and the related invoices will be marked as paid.
Impact on customer balance
When an outgoing banking transaction file is confirmed by the bank, the paid transactions will reduce the customer's balance and write off the related invoice(s). If a reversal has taken place (the customer refuses the direct debit payment for whatever reason), the invoice remains unpaid and the customer's balance is not reduced. The user can see on the customer's detail page if a payment has been reversed together with the reason for its reversal.
Different statuses
An outgoing payment request file can have different states:
Created: When a payment request file is created.
Closed: When a payment request file is confirmed by the bank and processed.
To confirm by bank: When a payment request file is awaiting confirmation by the bank.
Cancelled: When a user decides to cancel the payment request file (the user can delete the file afterwards).
Ready to send: This means the file can be downloaded and then uploaded to the bank for processing.
Resolve issues: When information is missing. This could happen when the bank account of the customer is missing or there is no active mandate.
Date expired: When the collection date has expired on the file. The collection date can still be adjusted manually to a future date. The file will get the state Ready to send again.
Partially closed: When the payment request is not completely processed yet.
Relevant configuration
SDD delay/retry settings