PAYREQ - Payment Request

Payment Requests can be generated in ITAS to be picked up by a customer's middleware. The required information is stored on the payreq (payment request) table. Details are located from the associated accounting transactions. Data will be prompted when the Payment Request is generated. There is a process that enables subsequent removal of transactions from a Request and the complete deletion of a Request.  To assist viewing of PAYREQ transaction status, the user can include txx_traceid in their customised view and CLIST will show any txx_traceid.

Create Payment Request.
The user selects the Client/Supplier account and optionally a currency code to restrict view of the posted accounting records which are unmatched credit values for the selections made. The standard accounting transaction filter is also available for filtering viewed transactions.   Unmatched includes any CASH pre-match selected transactions.
The view is:-

• Tick 'Inc' for Payment Request transmission. Once selected the Value Date, Percentage to Pay, Amount, Alternate Payee, Bank Account, Netting Flag, Payment Block can be amended
• Current Payment Request Status. Static. Indicates if a Payment Request has been generated already. Currently process prevents the ticking of a transaction that has already been flagged for payment
• Document Reference. Locked data element
• SAP Document Number. Locked data element
• Department. Locked data element
• Document Date. Locked data element
• Value Date. can be amended.
• Client Reference. Locked data element
• Contract Reference. Locked data element
• Narrative. Locked data element
• Expense Code. Locked data element
• Percentage to Pay. If entered the amount is calculated based on accounting transaction value.
• Ccy code. Locked data element
• Amount to Pay. can be amended (reduced only) for part payment
• Netting Flag. Is payment for Netting. Y/N
• Payment Block. Is payment to be blocked Y/N 
• Alternate Payee. If Supplier is not the Payee
• Bank Account. Supplier Bank Account/Alternate Payee Bank Account if alternative payee is entered as maintained in CLI/View/Banks. Default may be located from entry in Invoicing applications for the supplier, if maintained.

Upon ‘save’ the transactions selected for transmission will be updated which will enable an alert(s) (ex AUDIT) to be sent.  The transactions will be grouped for a payment request where they match on:-

• Currency
• Value date
• Payee
• Payee bank details
• Block flag
• Netting flag

If the amount of the transaction is reduced the amount to pay will be split from the original transaction leg and updated with the modified details, thereby leaving the residue value on the same document reference with its' data elements intact.  The selected transaction will be marked with any revised Value Date and Amount and its Payment Request Sent flag.
Payee, Payee Bank Account, Netting Flag, Payment Block, Payment Amount will be used to update the payreq table. Technical note, the Payment Request on the payreq table is joined to the accounting transaction by payreq_id = txx_traceid

Unmark/Delete Payment Request
This is the process for transactions to be removed from the payment request marking:
1. click/tick the "Unmark" column to remove that transaction from a payment request i.e. remove PAYREQ marking (txx_traceid)
2. click/tick the "Del." column to delete the payment request completely. If you delete a payment request, all transactions included in that payment request will have their PAYREQ marking removed.

Ancillary Processes
When the customer's middleware backflows the cash document for subsequent matching of cash and associate accounting, it may have utilised the PAYREQ ID to locate the relevant transactions to complete the matching process.  MAT, CASH and CLISPLIT can have been applied by ITAS users that could invalidate the backflow of cash and its matchings i.e. MAT & CASH can have applied user-side matching and CLISPLIT may have applied splitting the client transaction.

Technical Notes:
The table 'payreq'  records all of the Payment Request details.
The payreq_id column is an identity column which has its value system generated when the record is created. One payreq record can cover, theoretically, several invoices selected for payment. The link between accounting transaction and Payment Request is txx_traceid = payreq_id. When the Payment Request is created the existing transactions that have been selected for payment or the new splits for the transactions for part payment will be updated with the ID i.e. txx_traceid

The payreq table contains all Payment Request data.

• Id – system generated
• Account - payee (can be override payee)
• Ccy - currency of invoices
• Paymethod – not used
• Duedate – payment due date
• Status – status of payment request. Not currently used.
• Amddate, amdinit – who updated the record and when
• Submitdate, submitby – not used currently
• Approveddate, approvedby – not used currently
• Text – free format, max 4000
• Bankname – from payee
• Bankaccnum – from payee
• Amounttopay – amount of payment request
• Netting - is payment for Netting. Y/N
• Block - is Payment to be Blocked. Y/N

The update of the audit table with the new Payment Requests will trigger an alert(s) which will be picked up by the customer's subscribers