Show TOC

Process documentationProcessing of Active Returns Locate this document in the navigation structure

 

You use this process when the system has posted the ordering party item of a payment order, but the recipient items have to be returned (active return). Payment Engine supports the following scenarios:

  • The system has successfully posted the ordering party item and the invalid recipient item has not been posted.

  • The system has successfully posted the ordering party item and the recipient item has also been posted.

Note Note

You typically use this process to return payments in the context of the Single Euro Payments Area (SEPA).

End of the note.

Prerequisites

  • You have defined a payment order type for active returns in Customizing for Payment Engine under   Payment Order   Define Payment Order Types  .

  • You have defined the transaction type groups used for processing active returns in exception handling in Customizing for Payment Engine under   Payment Items   Transaction Types and Transaction Type Groups   Define Transaction Type Groups for Exception Control  .

  • You have defined a response type for active returns in Customizing for Payment Engine under   Exception Control   Define Response Types   Response Types: Payment Item   Define Response Types for Active Returns  .

  • You have defined the settings for active returns, for example, the return reasons and intermediary accounts, in Customizing for Payment Engine under   Exception Control   Active Returns  .

  • You have defined transaction types for active return payment items under   Exception Control   Active Returns   Maintain Transaction Type for Active Return  .

    Note Note

    If this information is missing, the system uses the transaction types defined for active returns under   Payment Items   Transaction Types and Transaction Type Groups   Maintain and Assign Transaction Types for Payment Items  . If these are not defined, the system uses the offsetting transaction type defined under   Payment Items   Transaction Types and Transaction Type Groups   Assign Offsetting Transaction Types to Transaction Types  .

    End of the note.
  • You have mapped the formats required to create incoming messages and outgoing messages in Customizing for Payment Engine under   File Handler   SEPA   Format Converter   : Map PE Internal Return Reason to Outgoing ISO Code and Map Incoming ISO Code to PE Return Code.

Process

The system has successfully posted the ordering party item and the invalid recipient item has not been posted.

  1. The return is initiated in one of the following ways:

    • From outside the system over the Create Active Return BAPI (/PE1/BAPI_ACTIVE_RETURN_CREATE).

    • As a result of an error using the corresponding exception handling response.

      For more information about exception handling, see Exception Control (FS-PE-EH).

    • Manually using the Create Active Return Order function on the Payment Order and Payment Item Overview (transaction /PE1/PO_EXPERT).

  2. The system validates the recipient item and determines that an active return can be created.

    Note Note

    If the result is that no active return can be triggered, for example, if the recipient item has already been returned, a final response type is determined.

    End of the note.
  3. The system reroutes the recipient item to an intermediary account.

  4. The system creates:

    • A new active return payment order

    • An active return ordering party item that reverses the posting of the redirected recipient item

    • An active return recipient item that reverses the posting of the original ordering party item (could be an external customer)

    Note Note

    The new recipient item contains a reference to the original ordering party item and the new ordering party item references the original recipient item.

    End of the note.
  5. The system updates the status of the original recipient item to Returned.

  6. Depending on the settings defined in Customizing, the system triggers correspondence and sends an interbank notification and a customer notification to the originator bank.

  7. The system submits the created business objects to straight-through-processing.

The system has successfully posted the ordering party item and the recipient item has also been posted.

  1. The return is initiated from outside the system over the Create Active Return BAPI (/PE1/BAPI_ACTIVE_RETURN_CREATE).

  2. The system validates the recipient item and determines that an active return can be created.

    Note Note

    If the result is that no active return can be triggered, for example, if the recipient item has already been returned, a final response type is determined.

    End of the note.
  3. The system creates:

    • A new active return payment order

    • An active return ordering party item that reverses the posting of the original recipient item

    • An active return recipient item that reverses the posting of the original ordering party item (could be an external customer)

      Note Note

      The new recipient item contains a reference to the original ordering party item and the new ordering party item references the original recipient item.

      End of the note.
  4. The system updates the status of the original recipient item to Returned.

  5. Depending on the settings defined in Customizing, the system triggers correspondence and sends an interbank notification and a customer notification to the originator bank.

  6. The system submits the created business objects to straight-through-processing.

Result

The amount in the recipient item is returned to the ordering party of the originator bank.