Bank Details Entry/Approval Segregation - NEW
How it is possible to separate responsibility over bank detail management.
Written by Reece Taylor
Updated at March 19th, 2025
-
Requisition Approval Processing Suite (RAPS)
RAPS Setup RAPS Utilities RAPS Requisition Entry RAPS Requisition Approval RAPS Convert Approved Reqs RAPS Purchase Order Cancel RAPS Delegation Maintenance RAPS Contract Module RAPS Expediting Module RAPS Pre-Revision Quotation Module RAPS - ATC Process (Approval to Commit) RAPS Enquiry by PSA Air Department RAPS Cost Controllers RAPS Unbudgeted/Budgeted
- AP - Automated Invoice Workflow
- AP - Payment Approval Management
- Global Upload Program (GUP)
- Document Register (DocReg)
- Rotables / Component Changeout
- Standard Pronto Modules
- PSA HelpDesk
Overview
An important function of all organizations is to segregate the access users have to banking information. PSA Air allows this through security set up and an approval process on updated bank accounts. To initiate this, ensure the following Air MFF is set to Y=yes.
The banking details of a vendor can be entered for new suppliers or can be updated for existing suppliers from the supplier master record, using the mode ‘Banking Details’. When there are any changes made a table in the backend of Pronto will toggle the Bank Details Approved flag to N=no. This table is ‘z-air-cre-master-extra’.
If a supplier has their payment type set to E=EFT, and the Bank Details Approved flag is set to N, then no records will be available to use in any payments runs to this supplier.
If that supplier's payment type is set to anything other than E=EFT, then records will be available to create a payment run, but those payment runs will not trigger any files that can be transmitted to the bank. This is only available as an option if a payment needs to be recorded in the system, and eliminates the risk of un-approved bank details being used to be transmitted to the bank.
When the bank details are approved, the field Bank Detail Approved in the ‘z-air-cre-master-extra’ table will be set to Y=yes, and records will be available to pay again.
The access is controlled by these three module/function codes;
S001
Will allow a user to enter in a new supplier, enter their bank details, but the supplier status will go to O on creation of a new supplier, or editing of an existing supplier.
S002
Will allow a user to approve the changed and uploaded bank details from “PSA Air - Bank Details Approve” ( ZUIT.M032 ).
S003
Will simply allow a user to enquire on the banking details of the vendor. No correction or approvals allowed by users with this access.
Entering or Updating Bank Details
From this supplier master record you can enter or update the relevant bank information, including bank name, routing code, bank account number, SWIFT code, etc.
Primary modes on this screen include
Correct
Correct the existing or missing bank details
Remove
Remove the current bank details
Bank Details
This mode is NOT used
Document Register
This mode allows you to attach documentation relevant to the entry or update of bank details for that supplier.
Approving Bank Details
When a new vendor is set up with banking details, or the banking details have changed, a user with ZBNK.S002, can approve these changes from Bank Details Approval (ZUIT.M032);
An email alert is generated by AI below.
This email alert will show the user previous bank details compared to the new bank details. Example below;
The primary information on this screen includes all of the new bank details for each specific supplier.
The primary modes on this screen are outlined below
Approve
Approving the entry, will set the PAYMENT TYPE for the vendor to E from O, and the vendor can now be paid through the normal banking approval process.
DocReg
This will bring you DocReg path to review any documents related to this vendor's banking details (new or changing).
