Payment Order

Business object in Account Management (FS-AM) that maps an order to a bank, such as to execute a bank transfer or a debit collection. For more information about debit collections, see Direct Debit Order and Collection Authorization.

A payment order consists of one or more payment items, representing an ordering party item and one or more recipient items. Payment orders with one recipient item are called individual payment orders, payment orders with multiple recipient items are called collective payment orders.

The account currency of the recipient can be different from the account currency of the ordering party. For more information about the prerequisites and procedure, see Currency Exchange.

Payment operations that are based on a payment order can be very different from a posting perspective. The system differentiates between these payment operations using transaction types. This is illustrated in a simplified form in the following table.

Payment operation (transaction type)	Elements of a payment order
Bank transfer	Paying party	Payment recipient
Debit memo, check	Payment recipient	Payer
General	Ordering party	Order recipient

There are different types of payment orders.

Internal payment orders:
Payment orders whose order recipient is also managed in Account Management (FS-AM). In this case, one internal payment item is generated each for the ordering party item and the order recipient item and posted to the respective account specified in the payment order.
External payment orders
Payment orders whose order recipient is managed outside of Account Management (FS-AM) . In this case, the payment order data is retrieved using Business Add-Ins BAdI: Connection of the Payment Transaction System at the Check Event and BAdI: Connection of the Payment Transaction System at the Save Event for an external payment transaction system that then forwards the postings to the relevant subledger. In Account Management (FS-AM), in this case, a payment item is only generated for the ordering party and updated on the ordering party's account. In addition, the Customizing activity Connect Payment Transaction System for Outgoing Payment Transactions is available to you. You can use this to establish a system connection (Remote Function Call RFC) between your SAP system and another SAP system, to which a payment transaction system is already connected by means of the above-mentioned BAdIs. In the case of collective orders, a combination of internal and external recipients is also possible.

External payment orders can be collected in the dispatcher for outgoing payments and then transferred to the payment transaction system via the payment order proxy in a mass run. To use the payment order proxy, the Customizing activity Define Number Range Interval for Payment Order (PO Proxy) is available to you. You also need the payment order proxy for processes that are outside of Account Management that create a payment order.

Note
Payment orders for SEPA direct debits are always transferred to an external payment transaction system.

End of the note.

Note Note

If you do not wish to execute a payment order immediately, but at a defined time in the future, use the functions provided by forward orders.

End of the note.

Structure

The structure description of the payment order is divided into methods and customer enhancements.

Methods

In Account Management (FS-AM), you can use one of the following channels for processing objects:

Dialog
Business Application Programming Interface (BAPI)
Direct Input (DI)

The following overview shows which payment order methods you can call up via which channel:

Method	Channel
Method	Dialog	BAPI	DI
Create payment order	x	x
Display payment order (BAPI: get data only)	x	(x)
Change payment order	x
Delete payment order	x
Reverse payment order	x	x
Transfer payment orders to PT system again	x
Select payment orders	x1	x2

The methods can change the status and the release status of the payment order. For more information, see Status and Release Status of Payment Order.

(1) In the dialog, you can select payment orders using a selection screen. In addition, you can define dynamic selections.

(2) Using this BAPI you can only select payment orders according to the bank details of the ordering party.

Dialog

You can call up the following transactions in dialog mode:

Transaction Code	Short Description
BCA_PO_CREATE	Create payment order
BCA_PO_DISPLAY	Display payment order
BCA_PO_CHANGE	Change payment order
BCA_PO_DELETE	Delete payment order
BCA_PO_REVERSE	Reverse payment order
BCA_PO_RESEND_EXTERN	Transfer payment orders to PT system again

Business Application Programming Interface (BAPI)

You can call up the following methods using the BAPI Explorer:

Method*	Short Description
PaymentOrder.Cancel	Reverse payment order
PaymentOrder.Create	Create payment order
PaymentOrder.GetDetail	Read payment order
PaymentOrder.GetListByAccount	Select payment orders

* The first two methods are writing methods. You can also execute them in a test run.

Direct Input

Direct input is not implemented for payment orders. However, you can carry out external data transfer (EDT) for the individual payment items of payment orders. For more information, see Payment Item..

Customer Enhancements

For the Business Add-Ins (BAdIs) that are available to you for payment orders, see Customizing for Account Management (FS-AM) under Start of the navigation path Order Management Next navigation step Payment Order Business Add Ins (BAdIs) General BAdIs End of the navigation path and BAdIs for BAPIs.

Integration

Customizing

You make the settings for payment orders in Customizing for Account Management (FS-AM) under Start of the navigation path Order Management Next navigation step Payment Order End of the navigation path in the following Customizing activities:

Connect Payment Transaction System for Outgoing Payment Transactions
Assign Number Range Interval for Payment Order to a Payment Transaction Area
Define Number Range Interval for Payment Order (PO Proxy)
Assign Offsetting Transaction Types (PO Dialog)
Assign Offsetting Transaction Types (Internal Processes)
Define Display of Change Documents
Set Account Identification /Addition Fields: Recipient
Create Customer Fields
Select Trigger for Event-Controlled Bank Statement
Assign Transaction Types and Medium/Payment Method to a Payment Directive Type

If you create correspondence and wish to levy charges for it, you must also make the following settings:

Create Charge Key
Assign Transaction Type to Charge Key
Create Payment Notes Text for Correspondence Charges

For SEPA direct debits, you can also make the following settings:

Define Lead Days for SEPA Direct Debits
Assign Payment Notes Type to Process Result Category/Payment Method

If you want to use the dispatcher for outgoing payments for external payment orders, you must also make the following settings:

Define Processing Priorities
Assign Account Symbol for Reconciliation Account
Assign Processing Priority for Recipient Item

If you wish to use the release process, you must also make the following settings:

Assign Release Procedure to Release Object
Assign Rules to Release Steps
Assign Release WF and Release Procedure WF to Release Procedures
Define Rejection Reasons

If you wish to archive the payment orders, you must also carry out the following Customizing activity:

Define Residence Time for Payment Order (Object PAYMORDER)

You also need to make the settings for the object Payment Item in Customizing for Account Management (FS-AM).

Checks Made by the System

Authorization check
Depending on the transaction types of the payment order, you can have an authorization check made for the following activities: Create (post), change, display, delete, reverse payment order, and also force posting. The check for the respective activity also depends on the transaction type of the ordering party of the payment order.

Note
In addition to this authorization check using the SAP authorization object for payment orders, you also have the option of making your own authorization checks. In Customizing for Account Management (FS-AM) under Order Management Payment Order Business Add-Ins , the Business Add-In BAdI: Definition of Authorization Check is provided for this purpose. For more information, see Authorization Administration.

End of the note.
Release check
The system also makes checks for the release-relevance, meaning it checks whether a payment order is forwarded to the release workflow on the basis of the characteristic values of its release attributes.

If the system identifies a payment order as being relevant for release, it forwards it to the release workflow. Payment orders that are relevant for release must be released by an authorized employee before being processed further. For more information, see Release Object PAOR (Payment Order).
Checks when posting a payment order
Various checks are made when a payment order is posted. Some of these checks depend on the business transaction and the transaction types involved. You can set which checks are made for which business transactions in Customizing. On this subject, read the section in Customizing under Item Management Basic Functions Transaction Types and Transaction Type Groups Maintain and Assign Transaction Types for Payment Items .
- Check for formal checks to which posting control can be applied, and for formal checks to which posting control cannot be applied
  The system first makes formal checks for all payment items (ordering party and recipient items). These checks depend on the channel via which a payment order is edited and also on the Customizing settings. The system does not only make these checks when you try and make or simulate a posting, but also when you change tab pages. Formal checks must be corrected, or posting is not possible. The only alternative is to terminate processing.
  
  Once all formal checks have been completed successfully, the system then checks formal errors to which posting control can be applied. If the system finds formal errors to which posting control can be applied, you can only process a payment order in accordance with the posting control rules set in Customizing for Account Management (FS-AM). Possible settings include rejection by the system, postprocessing, or posting the payment order, for example.
  
  For more information, see the documentation for Define Main Set of Rules in Customizing under Item Management Posting Control Rules . You also have the option of terminating processing.
- Check for material errors
  Once the checks for formal errors and formal errors to which posting control can be applied have run successfully, the system makes material checks, first for the ordering party/beneficiary side.
  
  If the system detects material errors, you can force the posting of the payment order. A payment order can also be processed in accordance with the posting control rules set in Customizing for Account Management (FS-AM). Possible settings include rejection by the system, postprocessing, or posting the payment order, for example.
  
  For more information, see the documentation for Define Main Set of Rules in Customizing under Item Management Posting Control Rules . You also have the option of terminating processing.
Once the material checks for the item of the order initiator have run successfully, if there are only external order recipients, the check is complete. If there are other internal order recipients, the system makes more material checks. If the material checks for internal order recipient items fail, you can either force the posting of these items, or proceed in accordance with the settings for the posting control rules. The second option excludes rejection by the system as a setting. You also have the option of terminating posting of the entire payment order.

Archiving

You can define whether payment orders are archived or deleted physically from the database once a certain period of time has expired. You define the time frame for each payment transaction area, product category, and product in Customizing for Account Management (FS-AM) under Start of the navigation path Order Management Next navigation step Payment Order Archiving Define Residence Time for Payment Orders (Object PAYMORDER) End of the navigation path .

To display archived payment orders, on the SAP Easy Access screen, choose Start of the navigation path Account Management Next navigation step Archiving Data Display Payment Orders (Archiving Object PAYMORDER) End of the navigation path .

For more information about the archiving object Payment Order, see Customizing for Account Management in the Customizing activity Technical Documentation for Account Management under Start of the navigation path Account Management (FS-AM) Next navigation step Concepts and Guidelines Archiving End of the navigation path .

For more information about archiving, see Data Archiving and Deletion in Account Management (FS-AM).

Objects Generated or Derived by the System

Payment Transaction Area

When you enter a payment order, the system derives the relevant payment transaction area from the bank details of the order initiator. Exactly one payment transaction area is assigned to every bank-specific bank key. The payment transaction area maps the organizational responsibilities for payment transactions within a bank in Account Management (FS-AM).

You create payment transaction areas in Customizing under Start of the navigation path Basic Settings Next navigation step Organization Define Payment Transaction Areas End of the navigation path . You also have to make the required entries under Basic Settings Organization Assign Bank Key to a Payment Transaction Area .

Payment Order Number

Using the payment transaction area, the system derives a payment order number from the corresponding number range. You create number ranges in Customizing for Account Management (FS-AM) under Start of the navigation path Order Management Next navigation step Payment Order Assign Number Range Interval for Payment Orders to a Payment Transaction Area End of the navigation path . A payment order in Account Management (FS-AM) is defined uniquely by the payment transaction area and the payment order number.

If you use the payment order proxy, create the number ranges in Customizing for Account Management (FS-AM) under Start of the navigation path Order Management Next navigation step Payment Order Define Number Range Interval for Payment Order (PO Proxy) End of the navigation path .

Change Document

The system generates a change document that meets auditing requirements. All changes you make to payment order data are logged in change documents. You call these up in all payment order transactions - with the exception of the transaction Create Payment Order - under Start of the navigation path Extras Next navigation step Change Documents End of the navigation path .

You can configure the display of the change documents in Customizing for Account Management (FS-AM), under Define Display of Change Documents. For more information, see Change Documents.

Correspondence

Note Note

Before correspondence can be generated, you have to make settings for the correspondence tool in Customizing for Account Management under Start of the navigation path Tools Next navigation step Correspondence Tool End of the navigation path . For more information, see Correspondence in Account Management.

End of the note.

You can create the following types of correspondence for payment orders.

Confirmation of execution
When posting a payment order or transferring it to the payment transaction system (for example, for SEPA direct debits), the system creates a confirmation of execution if you make the following settings:
- For individual payment orders: On the Ordering Party Details tab page of the corresponding standing order, you have selected the Confirmation of Execution checkbox.
- General settings for all payment orders: In Customizing for Account Management under Order Management Payment Order Correspondence Assign Transaction Type to Charge Key , you have selected the relevant checkboxes for the transaction types used.
  
  Note
  You define the formulation of the payment note text to identify this charge in correspondence in Customizing for Account Management (FS-AM), under Order Management Payment Order Correspondence Create Payment Notes Text for Correspondence Charges .
  
  End of the note.
In Customizing for Account Management (FS-AM) under Order Management Payment Order Business Add-Ins , the BAdI: Creation Control for Confirmation of Execution is available to you for the data to be included in the confirmation of execution. In the standard system delivered, this contains the connection to the Correspondence Tool.
Confirmation of Non-Execution
The system always creates a confirmation of non-execution if a payment order cannot be created due to material or formal checks to which payment control can be applied, and the processor has rejected it, either in the Create Payment Order dialog, or in the context of postprocessing. The procedure for the correspondence charges that you can levy is the same as for a confirmation of execution.

Charges for Correspondence and for Processing Payment Orders

If you always want charges levied for the creation of correspondence, on the SAP Easy Access screen, you must have chosen Start of the navigation path Financial Services Next navigation step Account Management (FS-AM) Current Settings Financial Conditions Condition Group Edit Condition Group End of the navigation path , and set relevant standard conditions. If you want to set individual conditions, you do so for the account in question on the Financial Conditions tab page.

In addition, you must have made the following Customizing settings for the charge calculation:

Product Management Financial Conditions Define Condition Type
Order Management Payment Order Correspondence Create Charge Key
Order Management Payment Order Correspondence Create Charge Key Assign Transaction Type

For more information, see Financial Conditions and the documentation for the relevant Customizing activities.

Payment Items

When you execute a payment order, the system generates payment items.

Items in Future

In the payment order dialog, the system always determines the posting date on the basis of the posting date set for the bank posting area. For more information about setting this date, see Setting the Posting Date.

However, a posting date can also be preset by other applications (such as standing order) or channels (such as BAPI) that generate payment orders. In this case, the system checks whether payment items can be generated for this date. This is the case if the posting date is not before the last date for which this bank posting area is closed. If the date is after the current date for payment transactions, the system generates items in the future.

Event-Controlled Bank Statement

The system creates an event-controlled bank statement when a payment order is not executed, provided the prerequisites for creating a confirmation of non-execution are met and you have made both the Customizing settings for the bank statement and also the following settings in Customizing for Account Management (FS-AM):

Item Management Basic Functions Define Rejection Reasons
Order Management Payment Order Select Trigger for Event-Controlled Bank Statement