
Treasury Correspondence Integration with SWIFT Network (3QM)
This scope item uses SAP Multi-Bank Connectivity to integrate treasury correspondence with the SWIFT network.
SWIFT messages for treasury OTC transactions can be delivered to the counterparty's SWIFT code using SAP Multi-Bank Connectivity. SAP Multi-Bank Connectivity acts as a hub and forwards the message to the SWIFT network.
Meanwhile, the SWIFT messages can be sent back from their counterparty via SAP Multi-Bank Connectivity, and relevant incoming correspondence objects are generated automatically in the SAP client. Once the incoming correspondence object is matched with the outgoing correspondence object with confirmation, the OTC transaction is settled accordingly. This function currently covers MT300 for Foreign Exchange instruments and MT320 for Debt and Investment instruments.
Key Process Steps Covered
- Create outbound correspondence object and outbound SWIFT message
- Status check of outbound correspondence object
- Sending outbound SWIFT message to MBC
- Pull acknowledgment message from MBC
- Check outbound correspondence object status
- Pull inbound SWIFT message from MBC
- Create incoming correspondence object and match it with outgoing object
- Check matching of correspondence objects
- Check transaction status
Benefits
- Integrate SWIFT messages in correspondence framework
Additional Information
- This scope item requires an additional SAP S/4HANA Cloud license
- This scope item is excluded from the default activation
This scope item is nonstandard and is not activated by default. The customer can request to activate it on demand if they want to use MT300/MT320. This requires additional licenses of for Treasury and Risk Management and SAP Multi-Bank Connectivity (MBC).
Where is Treasury Correspondence Integration with SWIFT Network(3QM) being used?
This Scope item is used in the following way:
- As a support function of Treasury Management within Finance Scope Item Group