How to understand Request Statuses in Confirm
UPDATED: September 13, 2017
In Confirm® Request Statuses define the life of a Request, from the first entry to the final payment. For each Status a set of flags is set to indicate what processes can be carried out on Requests with this Status.
|Status Code:||Up to four alphanumeric characters|
|Name:||Up to 30 characters|
|Follow Up:||The minimum time that must elapse before the Request can move on to the next Status. The drop down list references the Follow Up Lookup.|
|Checked:||Tick this box for Statuses assigned to Requests that have been through the Request Check procedure.|
|Suspended:||Tick this box for Statuses assigned to Requests that have been through the Request Check procedure, and found to be outside the Contract Tolerances.|
|Authorised:||Tick this box for Statuses assigned to Requests that have been authorised for payment.|
|Closed:||Tick this box for Statuses assigned to Requests that are on a committed Payment Batch.|
|Job Notes mandatory…:||When this is ticked any Job being set to this Status must have Notes entered before the record can be saved. If there are multiple Jobs linked to a Payment Request they must all have Notes before the Status can be changed.|
Be vigilant on the effects that Follow Ups on Request Statuses may have on the payment process at your organisation. For example Jobs on Payment Requests having Statuses with a one-day follow-up may meant that you would need to wait until the next day for the Request Authorisation process to work.
Product feature: Payment Processing
- No Downloads