Recherche dans les collections de brevets nationales et internationales
Une partie du contenu de cette demande n'est pas disponible pour le moment.
Si cette situation persiste, contactez-nous auObservations et contact
1. (WO2015179636) PRÉVISION DE LIQUIDITÉ ET SYSTÈME ET PROCÉDÉ DE GESTION
Note: Texte fondé sur des processus automatiques de reconnaissance optique de caractères. Seule la version PDF a une valeur juridique

CLAIMS

What is claimed is:

1. A system for processing liquidity forecasting decisions, the system comprising one or more computer processors configured to execute one or more computer program modules, the program modules being configured to:

receive, via the one or more processors, a forecast for an account at a forecast timestamp; and

identify, via the one or more processors, a forecast rule using attributes from the forecast;

responsive to the forecast rule having a milestone associated therewith:

retrieve, via the one or more processors, a milestone time associated with the milestone;

compare, via the one or more processors, the forecast timestamp to the milestone time; and

apply, via the one or more processors, a forecast decision based on the comparison of the forecast timestamp and the milestone time;

wherein applying the forecast decision comprises determining a confidence level that a transaction associated with the forecast will occur by a given time.

2. The system of claim 1, wherein the program modules are configured to determine, via the one or more processors, a lead forecast to be computed for a transaction, the lead forecast being for one of a plurality of legs of the transaction.

3. The system of claim 2, wherein the program modules are configured to determine the lead forecast based on an association with a nostro account.

4. The system of claim 1, wherein the one or more attributes include one or more of a currency of the transaction, a legal entity initiating the transaction, a nostro account involved in the transaction, a nostro holding country, a transaction type, a source transaction processing system, a transaction status associated with a source transaction processing system, a transaction status associated with an accounting system, a reason for not being final, and an amount materiality.

5. The system of claim 1, wherein applying the forecast decision comprises assigning the forecast to one of a plurality of categories associated with a plurality of confidence levels.

6. The system of claim 5, wherein the plurality of categories include one or more of confirmed, final, projected, tentative, and undecided categories.

7. The system of claim 6, wherein forecast decision assigned undecided category is provided real time forecasting decisions utilizing a machine learning model.

8. The system of claim 7, wherein the machine learning model provides a recommended forecast decision, a level of confidence, and a list of contributing factors in reaching the decision.

9. The system of claim 6, wherein the forecast is taken into position if the assigned one of the plurality of categories is confirmed, final, or projected, and wherein the forecast is left out of position if the assigned one of the plurality of categories is tentative or undecided.

10. The system of claim 6, wherein the undecided category is associated with user selection of another of the one or more categories.

11. The system of claim 1, wherein if the forecast is updated after a threshold time, the forecast is indicated as being a late forecast.

12. The system of claim 1, wherein the one or more processors are configured to reevaluate the category of the plurality of categories into which the forecast is assigned based on time or condition triggers.

13. The system of claim 12, wherein the time or condition triggers comprise one or more of the passage of a predetermined time, a securities settlement deadline, an overall processing deadline, and a market settlement deadline.

14. The system of claim 1, wherein the one or more processors are configured to apply the forecast decision by determining if the status of a source system associated with the transaction indicates that the transaction is an active transaction which has not yet posted.

15. The system of claim 1, wherein the forecast is taken into position when the transaction is an active transaction that has not yet posted, the forecast has not updated after a threshold time associated with being late, and the confidence level is above a defined threshold.

16. The system of claim 1, wherein the forecast has been enriched with data from a plurality of sources that contribute to separate forecasts.

17. The system of claim 1, wherein the transaction has a plurality of forecasts associated therewith.

18. The system of claim 1, wherein when one or more milestones are associated with the forecast rule, the one or more processors are configured to:

identify accounts to which the forecast rule applies;

search for other forecasts that meet the criteria of the identified forecast rule; and

for each identified forecast, apply the forecast decision based on the identified forecast rule with the associated milestone.

19. A computer implemented method for processing liquidity forecasting decisions, wherein the method is implemented in a computer system comprising one or more processors configured to execute one or more computer program modules, the method comprising:

receiving, via the one or more processors, a forecast for an account at a forecast timestamp; and

identifying, via the one or more processors, a forecast rule using attributes from the forecast;

responsive to the forecast rule having a milestone associated therewith:

retrieving, via the one or more processors, a milestone time associated with the milestone;

comparing, via the one or more processors, the forecast timestamp to the milestone time; and

applying, via the one or more processors, a forecast decision based on the comparison of the forecast timestamp and the milestone time;

wherein applying the forecast decision comprises determining a confidence level that a transaction associated with the forecast will occur by a given time.

20. The method of claim 19, further comprising determining, via the one or more processors, a lead forecast to be computed for a transaction, the lead forecast being for one of a plurality of legs of the transaction.

21. The method of claim 20, wherein determining the lead forecast is based on an association with a nostra account.

22. The method of claim 19, wherein the one or more attributes include one or more of a currency of the transaction, a legal entity initiating the transaction, a nostra account involved in the transaction, a nostra holding country, a transaction type, a source transaction processing system, a transaction status associated with a source transaction processing system, a transaction status associated with an accounting system, a reason for not being final, and an amount materiality.

23. The method of claim 19, wherein applying the forecast decision comprises assigning the forecast to one of a plurality of categories associated with a plurality of confidence levels.

24. The method of claim 23, wherein the plurality of categories include one or more of confirmed, final, projected, tentative, and undecided categories.

25. The method of claim 24, wherein forecast decisions assigned undecided category is provided real time forecasting decisions utilizing a machine learning model.

26. The method of claim 25, wherein the machine learning model provides a recommended forecast decision, a level of confidence, and a list of contributing factors in reaching the decision.

27. The method of claim 24, further comprising taking the forecast into position if the assigned one of the plurality of categories is confirmed, final, or projected, and leaving the forecast out of position if the assigned one of the plurality of categories is tentative or undecided.

28. The method of claim 24, wherein the undecided category is associated with user selection of another of the one or more categories.

29. The method of claim 19, wherein if the forecast is updated after a threshold time, the forecast is indicated as being a late forecast.

30. The method of claim 19, further comprising reevaluating the category of the plurality of categories into which the forecast is assigned based on time or condition triggers.

31. The method of claim 30, wherein the time or condition triggers comprise one or more of the passage of a predetermined time, a securities settlement deadline, an overall processing deadline, and a market settlement deadline.

32. The method of claim 19, wherein applying the forecast decision comprises determining if the status of a source system associated with the transaction indicates that the transaction is an active transaction which has not yet posted.

33. The method of claim 19, wherein the forecast is taken into position when the transaction is an active transaction that has not yet posted, the forecast has not updated after a threshold time associated with being late, and the confidence level is above a defined threshold.

34. The method of claim 19, wherein the forecast has been enriched with data from a plurality of sources that contribute to separate forecasts.

35. The method of claim 19, wherein the transaction has a plurality of forecasts associated therewith.

36. The method of claim 19, further comprising, when one or more milestones are associated with the forecast rule:

identifying accounts to which the forecast rule applies;

searching for other forecasts that meet the criteria of the identified forecast rule; and

for each identified forecast, applying the forecast decision based on the identified forecast rule with the associated milestone.