How Ad Hoc Payments Are Made
The Manage Ad Hoc Payments page is used to transfer ad hoc funds from an internal bank account to an external payee bank account. Ad hoc payments may require an approval process prior to processing the payment.
Processing the payment goes through formatting validation prior to transmission.
The following table lists the elements for making an ad hoc payment and the possible statues that may result with actions to take to correct issues.
|
Field Name |
Required |
Description |
|---|---|---|
|
Payment Number |
Yes, the payment reference is generated by the application. |
The unique payment reference number. |
|
Payment Number |
Yes |
The bank account initiating the payment. |
|
Payee |
Yes |
Name of the payee. |
|
Payee Account |
Yes |
The payee bank account receiving the payment. |
|
Payment Date |
Yes |
Date of payment, application date defaults. |
|
Amount |
Yes |
Amount to pay. |
|
Currency |
Yes |
Payment currency. |
|
Status |
Yes, if Approvals are enabled. |
Status of the payment. Valid values are:
|
The Payment Status can be either nonactionable or actionable. The following table lists the possible statuses:
|
Nonactionable Status |
Description |
|---|---|
|
Formatted |
The payment has been formatted but transmission isn't needed. |
|
Transmitted |
The payment has been formatted and transmitted. |
|
Terminated |
The payment has been terminated by the user. |
|
Actionable Status |
Description |
|---|---|
|
Pending action to address document validation errors. |
Correction or missing data needed. |
|
Pending action to address payment validation errors |
Correction or missing data needed. |
|
Failed validation and pending action |
Correction or missing data needed. |
|
Formatted and ready for transmission |
Passed validation and ready to be transmitted. |
|
Failed formatting and pending action |
Correction or missing data needed. |
|
Transmission failed |
Correction or missing data needed. |