Payments

This determines the basis on which transactions are selected for payment. The following options are available:

• Force only selects transactions with an allocation marker of Force.
• Due Date selects transactions with a due date on or before the Base Date for Payment you enter at run time. Any transactions with an allocation marker of Force are always included. Transactions with a Withhold marker or any numeric markers (0-9) are excluded.
• Allocation Marker in Payment Run selects transactions with the allocation markers you choose at run time. You must choose Allocation Marker as a run time selection option to prompt the user to enter the range of markers required.
• Allocation Marker and Due Date selects transactions according to the range of allocation markers and due date you select. A transaction must have an allocation marker in the chosen range, and a due date on or before the Base Date for Payment you enter at run time. This option allows you to preset the range of allocation markers for the profile in the Allocation Marker From/To fields. You can also allow the user to choose the range of markers at run time by selecting Allocation Marker as one of the run time selection criteria.
• Allocation Marker Only allows you to select transactions by allocation marker, ignoring the due date. This option allows you to preset the range of allocation markers for the profile in the Allocation Marker From/To fields. You can also allow the user to choose the range of markers at run-time by selecting Allocation Marker as one of the run-time selection criteria.

See Using Allocation Markers to Select Transactions for Payment and What are the Payment Run Time Selection Criteria?

If either the Allocation Markers Only or Allocation Marker and Due Date option is chosen above, this is the range of allocation markers to be used to select transactions. This allows you to preset the allocation markers if the same range is required for every run.

This option determines whether the payment profile is to be used for payments or for payment collections, as follows:

• Collection must be set if the profile is to be used by Payment Collection Run (PYC)
• Payment must be set if the profile is to be used by Payment Run (PYR).

This option determines whether or not a single, summarized ledger transaction is posted to the payment or collection account for the payment or collection run.

Three options are available:

• Mandatory forces a single transaction only to be posted to each payment account
• Prohibited posts individual payment transactions to the payment accounts
• Optional allows the choice to be made at run time using the corresponding field in Payment Run or Payment Collection Run.

This determines the payment method for the payment profile. When you define a customer or supplier, you select a payment method of Cheque, Bank, Single Payment or Not Specified. Here you select the payment method to be used for this payment run. See How is the Payment Method Used? If the Bank payment method is used, you must create a bank details record for your own bank account in Bank Details Setup (BNK).

Note that an account is only selected for payment, if the corresponding supplier or customer details reference this payment method. See How Transactions are Selected for Payment or Collection.

The bank subcode to be used for this profile, if the payment method is Bank. If you leave it blank and the payment method is Bank, all customers or suppliers are selected. Bank subcodes are defined using Bank Details Setup (BNK) and assigned to a supplier or customer using Supplier (SUS) or Customers (CUS).

See How is the Payment Method Used? for more information on the Bank payment method.