Master Data 
You can manage the following master data objects in Payment Engine.
Charge conditions
Bank file clearing data
Route and route rule set
Clearing agreement and clearing agreement rule set
Request agent bulk assignment
Customer agreement and customer agreement rule set
Value date agreement and rule set for value date agreements
Service level agreement (SLA)
Integration
You store and manage the financial conditions for payment transaction charges by using the standard SAP component Financial Conditions (CA-FIM-FCO) or another charge provider. For more information, see Charges.
The system uses bank file clearing data to determine the clearing account of ordering party items for incoming payments orders. For more information, see Bank File Clearing.
The system enhances the payment information (when necessary) and validates it against the various types of master data, such as the service level agreement (SLA). For more information, see Enrichment and Validation and Service Level Agreement.
During route processing, the system determines how to process payments based on the master data linked to each payment item. For more information see Routing Control (FS-PE-RP).
The master data information stored in Payment Engine for each of these objects is used in the Clearing Processing component to further process payments. For more information, see Clearing Processing (FS-PE-CP).
You use exception control rule sets to determine suitable response types for errors that occur during straight-through processing (STP) and file handling. For more information, see Exception Control (FS-PE-EH).
Features
Master data objects and business rules are separated at clearing-area level. For more information, see Clearing Area.
Master data objects are linked to each payment through the use of rule sets. For more information, see Rule Set.
All manual changes to master data (or transactional data) that occur within Payment Engine are logged to change documents that display who changed what and at what time.