Liquidity Threshold Notification for Payment Systems

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In the context of electronic transaction systems, institutions face challenges in managing liquidity levels, particularly during periodic cycles, which can be inflexible and lead to difficulties in handling high-value transactions, resulting in the need for careful monitoring and potential liquidity shortages.

Innovation Solution

A method and apparatus that automatically notify institutions when the difference between transaction values exceeds a predetermined liquidity threshold, allowing for proactive management of liquidity levels by filtering and sorting instructions to reduce processing requirements and delay notifications to minimize false alerts.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If institutions carefully monitor liquidity levels during periodic cycles, then liquidity management reliability is improved, but device complexity and processing requirements increase

Engineering Contradiction:
Improveliquidity management reliabilityVSAvoidprocessing complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system performs preliminary actions by calculating projected liquidity positions in advance based on received transaction instructions before the periodic settlement cycle. This allows institutions to know their projected liquidity status ahead of time and take corrective actions if needed, improving reliability without requiring complex real-time monitoring during the settlement period.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system introduces an intermediary notification mechanism that acts as a mediator between transaction processing and liquidity monitoring. Instead of directly monitoring all transactions, the system uses threshold-based notifications to alert institutions only when projected liquidity positions exceed predetermined thresholds, simplifying the monitoring complexity while maintaining reliability.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Loss of time

If the periodic cycle is set to a long duration, then processing time is reduced, but liquidity requirements increase

Engineering Contradiction:
Improveprocessing timeVSAvoidliquidity requirement
Core Design Contradiction:
Loss of timeVSQuantity of substance

Solution Approach 1:

The system performs preliminary calculations of projected liquidity positions throughout the periodic cycle based on received instructions. This allows institutions to anticipate liquidity needs in advance and arrange funding beforehand, enabling longer periodic cycles without requiring excessive liquidity buffers, thus reducing both processing time losses and liquidity requirements.

Inventive Principle:
Principle #10Preliminary action

3Reliability

If automatic notification is implemented when liquidity threshold is exceeded, then liquidity management reliability is improved, but data processing requirements increase

Engineering Contradiction:
Improveliquidity management reliabilityVSAvoiddata processing efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The system changes the parameter of notification triggering from continuous monitoring to threshold-based triggering. Instead of continuously analyzing all transaction data, the system calculates projected liquidity positions and only generates notifications when these positions exceed predetermined thresholds. This maintains reliability by ensuring notifications are sent when needed while significantly reducing data processing requirements by avoiding unnecessary notifications during normal operations.

Inventive Principle:
Principle #35Parameter changes

4Reliability

If institutions require high liquidity levels to cover potential high-value transactions, then transaction reliability is improved, but productivity and flexibility decrease

Engineering Contradiction:
Improvetransaction reliabilityVSAvoidprocessing productivity
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The system performs preliminary assessment of projected liquidity positions based on received transaction instructions before settlement. This allows institutions to identify potential liquidity shortfalls in advance and take corrective actions such as arranging intraday credit or adjusting transaction timing, thereby maintaining transaction reliability without requiring institutions to hold excessive liquidity buffers that would reduce productivity and flexibility.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentEP3621014A1A method, computer program product and an apparatus
Publication Date: 2020.03.11 VOCALINK INT LTD
  • EP3621014A1 patent drawingFigure 1
  • EP3621014A1 patent drawingFigure 2
  • EP3621014A1 patent drawingFigure 3

AI summary

A method comprising: receiving a first instruction from a first user, the first instruction being an instruction to transfer to a first value from a first institution to a second institution; receiving a second instruction from a second user, the second instruction being an instruction to transfer a second value from the second institution to the first institution, wherein the first value is greater than the second value; calculating the difference between the first value and the second value; and comparing the calculated difference to a predetermined amount, wherein if the calculated difference is greater than the predetermined amount, the method comprises: automatically notify the second institution.