What Postings are Generated by Payment Run?

Payment Run (PYR) generates the following payment transactions, providing the Post Transactions option is set to Yes:

  • a payment transaction for each creditor/payables account, or client account, for the net amount paid which is the gross amount less discount.
  • one or more transactions to post the total payment amount for each creditor to the payment accounts. This is the bank account posting. The supplier code and description are included in the journal line description.
  • optionally, a discount transaction (including any tax) is generated for the discount account, and another transaction is generated to post the tax on any settlement discount to the tax account. A separate discount transaction is posted to the supplier account for each invoice. See Taking Discounts and Adjusting the Tax.

The payment transactions generated have a journal type of SYSTM and a journal source of PAYMT. The settlement discount transactions generated have the journal source PAYDS.

Each transaction that is paid, and the payment transaction itself, is given the allocation marker of Paid. They are assigned the next allocation reference, and the current allocation date and period. If you specify Single Payments as the payment method for the Payment Run, a separate allocation reference is generated for each payment.

Note:  If the Non Match of System Payments option is set in Ledger Setup (LES), an authorized user can choose not to match the transactions. In this case the allocation marker is set to Paid Unmatched on all of the transactions, including the payment transaction. These transactions must be matching using any of the matching functions, for example Account Allocations (ACA).

Payments are not generated for transactions in future periods.

The Payment Account Posting

The payment account to which the payments are posted can be entered on Payment Run. Alternatively, it can be preset for a payment run in the payment profile using Payment Profiles (PYP). In a multi-currency environment, separate payment accounts may be used for different currencies using Currency Codes (CNC).

A separate payment account posting is made for each creditor/payables account payment. It identifies the supplier in the transaction description.

If you are making payments using the Bank payment method, the payment account posting is summarized into a single transaction for the entire payment run, if you set the Single Transaction to Payment Account option.

Analysis Codes

Normally SunSystems consolidates all transactions belonging to a particular creditor/payables account, regardless of the analysis codes, and posts a single balancing payment transaction to the creditor account for the payment amount.

If you click Amend Consolidation, you can consolidate the postings according to selected ledger transaction analysis codes. You can also use the Consolidation form to assign analysis codes to the payment transaction. Similarly, click Bank Analysis to assign analysis codes to the bank (payment account) transaction.

You can also use Business Rules to set or validate analysis codes on the generated transactions. If you use both Consolidation and Business Rules for this function, the analysis codes validated and set by Business Rules are definitive, and if different, override the codes set by Consolidation.

Payment Stamps

If payment stamps are used to group the transactions for payment within a creditor/payables account, a separate payment and payment account posting is generated for each set of transactions with the same payment stamp. The payment stamp from the transactions is also added to the payment transaction. For more information about this facility see the Stamping Payment Transactions section in the Financials User Guide / Help.

Provisional Postings

If provisional postings are mandatory for the business unit, all of the postings made by Payment Run are provisional. If provisional postings are optional, you must choose to post the transactions as provisional or permanent.

A feature associated with provisional ledgers, but which can be used independently, is the ability to record a sequence code and number for each transaction line or reference in a journal. This is a useful feature, which helps to ensure data integrity. The sequence data is held on a ledger transaction analysis code.

Sequencing can be applied to system generated transactions, including those generated by Payment Run. See Understanding Ledger Sequence Numbering.