Payment Run (PYR)

The Payment Profile code that determines the selection criteria for the payment run, any run time selection criteria, and the payment output and posting requirements. This code is defined using Payment Profiles Setup (PYP). The payment profile must have a Payments/Debits field set to Payments.

Select Yes to generate and post the payment transactions, produce a payments file, set the allocation marker to Paid (or Paid Unmatched) on the selected transactions, produce the payment run details report and optionally produce a bank transfer file. If provisional postings are optional, you can choose to post the transactions as provisional. If this option is mandatory, then the transactions are always posted as provisional.

Select No to only produce the payment run details report showing the items selected for payment.

Select this option to summarize the transactions on the payment run details report. If this option is not selected, the payment run details report shows the payment and discount allowed on individual transactions. If this option is chosen, a summary report is produced showing the total amount selected for payment from each account.

Transactions are selected for payment if they are eligible for discount on or before this date. See 'Taking Discounts and Adjusting the Tax'.

The date to be used as the transaction date for transactions generated during this run. The default is today's date.

The date you expect to run the next payment run using this payment profile. If transactions are still eligible for the same discount on this date, they will not be selected for this run. Transactions with a Force allocation marker are selected regardless of the date entered in this field.

The period to which the transactions generated during this run are to be posted. The default is the current period.

Up to 5 run time selection criteria may be displayed. These criteria are determined payment profile which is defined using Payment Profiles Setup. For example, you may be asked to enter a range of accounts and journal sources. A transaction must meet all of these selection criteria to be included in the payment run.

The bank details record, as set up in Bank Details (BNK), for your own bank account. When you enter a valid bank details code, the Payment Account field (below) displays the relevant chart of accounts record for your bank account.

This field is mandatory for payments where the Payment Method is set to Bank on the payment profile. If there is no Bank Details Code on the payment profile, and the Payment Method is set to Bank, then you must enter it here.

The subcode, if used, on the bank details record identified in the field above. Otherwise leave blank.

The chart of accounts code to which the balancing, cash transactions for the payment are to be posted. It would normally be a bank account. You cannot select a memo account. A default account can be set for the payment profile.

If you are producing payments in more than one transaction currency, the payment account identified for each currency in Currency Codes (CNC) is used. If a payment account has not been defined for a currency, the account you enter here is used.

You may be warned if there are insufficient funds in this account to meet the generated payments. See 'Can a Payment Account Become Overdrawn?'

The chart of accounts code to which the balancing transactions for generated discount taken on debit transactions are posted. You cannot select a Memo account.