Bank Payment Register
Understanding the information captured in a payment run
Written by Jarrad Sonnenberg
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 RAPS Change Order Mode
- AP - Automated Invoice Workflow
- AP - Payment Approval Management
- Global Upload Program (GUP)
- Document Register (DocReg)
- Rotables / Component Changeout
- PSA Mining Report Suite
- Standard Pronto Modules
- PSA HelpDesk
The payment approval process in PSA Air will store the details of every payment made to every vendor in a customized table. This table is called the Bank Payment Register (ZUIT M022).
Within Bank Master (SYS M054) a ‘Details’ mode allows the bank account to be defined as XML Enabled. This needs to be turned on for every bank that will be going through the bank payment register. Enable XML field needs to be set to Y=yes.
The following Alert Intelligence (AI) should also be set up on the server and activated for the relevant companies.
This AI will update the bank payment register screen for every payment that is run on bank codes with the above setup.
The following information is available on the bank payment register;
Status and Description
This is the status of the file based upon transmission.
- 10 is awaiting approval
- 30 is approved
- 80 is transmitted to the bank
- 80+ is a range of different status codes depending on the bank that will confirm the completion of the payment, rejection of the payment or settlement status of the payment.
- 99 is cancelled.
Batch
This is the batch number the payment run was processed under in Pronto.
Document Number
This is the unique identifier or payment number for the payment to the vendor.
Bank Code
This is the bank account used to make the payment.
Date
The date of the payment
Account Code and Short Name
This indicates the vendor code and name for the recipient of the payment.
Local Amount / Currency / Foreign Amount
This is the currency of the payment as per local dataset currency, the currency code used if any and then the foreign amount being paid.
Payment Selection
This is based upon the supplier master, and is typically W for Wire, A for ACH, C for distributed Check or E for EFT.
Our Bank Account and Routing
These are the bank details for OUR account as the sender. They are stored in the bank mased upon the details tab for the bank account;
Fees Cost
This is a field required by the bank. It is either OUR for our cost, BEN for cost of beneficiary or SHA for shared cost.
Vendor Bank details
The vendor bank information is more comprehensive and shows;
- Full name of the account
- Routing code
- Account number
- SWIFT Code
- Account type
- Bank Name
Error Code
This field will provide feedback from the bank in the event the payment is rejected.
These modes are available on the screen;
Find
The find function allows a user to search by the batch number. It is recommended that filtering is used to filter down to more granular detail.
Transactions
The transactions mode simply shows the invoices being paid by the payment run to that vendor only. The reference column shows the invoice number;
Supplier Transactions
The supplier transactions mode will show the total being paid to the vendor with drill down capability to the cre-trans records paid in the payment run.
Selecting TRANS allows the user to drill down into the transactions for the payment run;
Enq Supplier
This is a conditional mode. If the user only has enquiry access it will open supplier enquiry for the selected vendor. If the user has maintenance access it will open supplier maintenance for the selected vendor;
Cancel Payment
Cancel payment will perform the standard system payment cancellation. This will reverse the AP and GL entries and cancel the payment status in the grid. This is useful if the bank rejects a payment file.
View File
View file allows the user to open the XML that was sent to the bank. It is ONLY AVAILABLE after the payment has been approved.
Templates
This is for system set up only and allows the XML template to be added and edited over time. This is documented in the Bank Integration page.
Refresh
Refresh will refresh the data-grid.
Document Register
The document register mode will open up the document register record for the selected vendor payment. The folder is indexed based upon the payment number, not the batch number;
Most commonly, the user will review the document register which creates the payment pack for each payment.
This is outlined further in this article - DocReg Payment Pack
