Posting Logic (SAP Library

Posting Logic

Purpose

The posting-relevant Treasury information is transferred to Financial Accounting via an interface. The posting logic is based on the flow types generated and the Account assignment reference of the transaction as well as user-specific account determination.

You can generally post the individual flows via G/L accounts or on the debit side. The posting of payment activities usually takes place on corresponding clearing accounts. The items from these clearing accounts are usually processed further via Cash Management (account statement) or Financial Accounting (payment program). For Money Market, Foreign Exchange and Derivatives, you can also use an enhanced payment program (payment request). To do this, Payment requests are firstly generated from Treasury so that they can later be paid individually or collectively via the payment program. For individual payments, there are four combinations:

Number for posting logic	Payment activity	Payment request
G/L accounts without payment requests	No	No
G/L accounts with payment requests	No	Yes
Customers without payment requests	Yes	No
Customers with payment requests	Yes	Yes

Process Flow

1. G/L accounts without payment requests:

You post the flows from a G/L account to a bank clearing account and clear the flows either via the manual or electronic account statement. This passive procedure is especially useful for incoming flows where payments are automatically initiated by the bank i.e active initiation of payment is not required.

Procedure:

G/L account to Bank clearing account

- Bank clearing account to bank account

Example:

Incoming interest payments from Money Market transactions with your house bank are a typical example.

2. G/L accounts with payment requests:

If the transaction is not carried out with a House bank or there is no Account debit agreement or if transactions are to be netted, the payment must be actively initiated. Firstly, a payment request is generated per flow and the posting is carried out on the payment request clearing account. If the payment program is then called up, it generates the corresponding forms (e.g Transfers) according to the payment method. The payment run that takes place will bring the payment requests together if necessary (netting) and carry out the posting on the bank clearing account. After receipt of the bank statement, the Bank account is reconciled with the Bank clearing account again.

Procedure:

G/L account to Bank clearing account
Payment request clearing account to bank clearing account
- Bank clearing account to bank account

Examples

Transactions that you have not concluded with your house bank are typical examples.
You can also use this procedure if you wish to settle transactions grouped together through netting (payment netting) to save transaction costs.

3. Customers without payment requests:

Instead of posting via G/L accounts, you can post via customer accounts. The customer payment program processes data and initiates active payment. Open items are generated in the customer account and are paid via the payment program.

Procedure:

- G/L account to customer account
- Customer account to bank clearing account
- Bank clearing account to bank account

Examples

This procedure is useful if you wish to use administrative functions in the customer area. This is the case if a qualified receivables evaluation (interest or repayment) may be possible.
You can also use this procedure for active loans to initiate the payment of the credit amount.

4. Customers with payment requests:

Postings take place as in 3., with the difference that the payment program for payment requests is used. This allows you to use multi-level payment methods. Netting is not possible here.

Procedure:

- G/L account to customer account
- Customer account to bank clearing account
- Bank clearing account to bank account

Example:

Customer payment (with additional advantages of the payment program).