WO2002065365A1 - Dispositif permettant l'integration de donnees de transaction relatives aux transactions financieres - Google Patents
Dispositif permettant l'integration de donnees de transaction relatives aux transactions financieres Download PDFInfo
- Publication number
- WO2002065365A1 WO2002065365A1 PCT/JP2002/000976 JP0200976W WO02065365A1 WO 2002065365 A1 WO2002065365 A1 WO 2002065365A1 JP 0200976 W JP0200976 W JP 0200976W WO 02065365 A1 WO02065365 A1 WO 02065365A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- transaction information
- data
- record
- aggregated
- interest
- Prior art date
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
- G06Q40/12—Accounting
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
- G06Q40/02—Banking, e.g. interest calculation or account maintenance
Definitions
- the present invention relates to an apparatus for aggregating transaction information relating to financial transactions, a method thereof, a recording medium storing a program for executing the apparatus, and a recording medium storing a program for executing the method. More specifically, transaction information is obtained from a device that stores transaction information on financial transactions, and developed data indicating cash flows is generated based on the data, and the developed data is processed under specified aggregation conditions.
- the present invention relates to a technology capable of supplying aggregated data that accurately represents a cash flow to a risk management system by performing aggregation based on the data. Background technology
- Interest rate risk (margins of interest and the value of assets held Value fluctuation risk), liquidity risk (risk of bankruptcy due to timing of inflow and outflow of funds, mismatch of amounts, etc.), currency risk (funds and liabilities on a yen basis due to fluctuations in exchange rates) It is generally known that the risk of change in value is included.
- risk management systems that analyze cash flow information, calculate the amount of risk, hedges, etc., and support business decisions are introduced and used by many financial institutions.
- An object of the present invention is to aggregate a huge number of pieces of cash flow information of, for example, several hundred thousand units into data that can be processed by a risk management system. Disclosure of the invention
- the present invention has the following features.
- the invention described in claim 1 stores the transaction information from the transaction information storage device. Acquisition, generating a development record indicating the occurrence of a monetary transfer amount based on the transaction information, grouping the development records based on predetermined aggregation conditions, and generating an aggregation record from a plurality of expansion records belonging to the same group I do.
- the money transfer amount refers to the amount of money required for depositing and withdrawing principal, paying interest, and changing the loan balance.
- the invention described in claim 2 has a transaction information aggregating unit provided for each ledger file stored in the transaction information storage device, and each transaction information aggregating unit is stored in the corresponding ledger file.
- the predetermined aggregation condition is determined according to the nature of the financial product being used.
- financial institutions handle a variety of financial products, and cash flows are generated daily for each financial product, but the conditions and content of the cash flows differ for each financial product.
- cash flows are generated daily for each financial product, but the conditions and content of the cash flows differ for each financial product.
- by providing an aggregation unit suitable for each financial product it is possible to collectively process risks for the financial products handled by the financial institution.
- the invention according to claim 3 is characterized in that the transaction information aggregating unit generates a development record storing at least one change date of the principal, interest, and balance and the amount of the change, and Transactions that group expanded records based on aggregation conditions and generate aggregate records by adding at least one of the principal, interest, and balance of the grouped expanded records And information gathering means.
- the development record stores at least one change date of the principal, interest, and balance and the amount of the change, so that it is possible to grasp an accurate cash flow amount on a daily basis.
- the invention according to claim 6 is a development record that acquires transaction information from a transaction information storage device and generates a development record representing at least one change of the principal, interest, and loan balance based on the transaction information.
- the method further comprises: a generation step; and an aggregated record generation step of grouping the expanded records based on a predetermined aggregation condition and generating one aggregated record from a plurality of expanded records belonging to the same group.
- the amount of money transferred refers to the amount of money paid and received, payment of interest, and changes in the loan balance.
- FIG. 1 is a block diagram for explaining a transaction information aggregating apparatus according to the present invention.
- FIG. 2 shows an example of the configuration of the transaction information aggregator according to the embodiment.
- FIG. 3 is a block diagram showing an example of the configuration of the ordinary deposit transaction information aggregating unit.
- FIG. 4 is a diagram showing an example of the structure of a record in an ordinary account ledger file.
- Fig. 5 is a diagram showing a scenario of an example of a transaction on ordinary deposits.
- Figure 6 is a diagram showing the development data of ordinary deposits.
- Fig. 7 is a diagram showing aggregated data of ordinary deposits.
- FIG. 8 is a diagram showing the development data of ordinary deposits.
- Fig. 9 is a diagram showing aggregated data of ordinary deposits.
- FIG. 10 is a diagram showing the ordinary deposit development data.
- Fig. 11 is a diagram showing aggregated data of ordinary deposits.
- FIG. 12 is a diagram showing development data of ordinary deposits.
- Figure 13 is a diagram showing aggregated data of ordinary deposits.
- FIG. 14 is a diagram showing the development data of ordinary deposits.
- Figure 15 shows the aggregated data of ordinary deposits.
- Fig. 16 is a diagram showing the development data of ordinary deposits.
- Fig. 17 shows aggregated data of ordinary deposits.
- FIG. 18 is a diagram showing a configuration example of a time deposit transaction information aggregating unit.
- FIG. 19 is a block diagram showing an example of the configuration of the regular deployment means and the regular aggregation means.
- FIG. 20 shows an example of the structure of a record in a time deposit ledger file.
- Fig. 21 is a diagram showing a scenario of a transaction example relating to term deposits.
- FIG. 22 is a diagram showing time deposit development data.
- Figure 23 is a diagram showing the aggregated data of time deposits.
- '' Fig. 24 shows the time deposit development data.
- Figure 25 is a diagram showing the aggregated data of time deposits.
- Figure 26 is a diagram showing the time deposit development data.
- Figure 27 shows the aggregated data of time deposits.
- Figure 28 shows the time deposit development data.
- Figure 29 shows the aggregated data of time deposits.
- FIG. 30 is a diagram showing time deposit development data.
- Fig. 31 is a diagram showing aggregate data of time deposits.
- FIG. 32 is a diagram showing time deposit development data.
- FIG. 33 is a diagram showing aggregated data of time deposits.
- FIG. 34 is a block diagram showing a configuration example of a foreign exchange contract information processing means.
- FIG. 35 is a diagram showing a scenario of a transaction example regarding time deposits.
- FIG. 36 is a diagram showing an example of the details of the data acquired by the exchange contract data receiving unit from the time deposit ledger file.
- FIG. 37 is a diagram for explaining the calculation performed in the purchase price / sale price calculation section.
- FIG. 38 is a diagram showing an example of aggregated exchange contract information data generated by a purchase price / sale price calculation unit.
- FIG. 39 is a diagram showing an example of aggregating the exchange contract information generated by the purchase price / sale price calculation unit.
- FIG. 40 is a diagram showing an example of aggregated exchange contract information data generated by a purchase price / sale price calculation unit.
- FIG. 41 is a diagram illustrating an example of aggregated data of exchange contract information generated by a purchase price / sale price calculation unit.
- FIG. 42 is a block diagram showing a configuration example of a force-drawing transaction information aggregating unit.
- Figure 43 is a diagram showing a scenario of a transaction example for a force drone.
- FIG. 44 is a conceptual diagram showing an example of transaction information stored in a card loan ledger file.
- FIG. 45 is a diagram showing an example of card loan development data.
- FIG. 46 is a diagram showing an example of card loan aggregated data.
- FIG. 47 is a conceptual diagram showing an example of transaction information stored in a card loan ledger file.
- FIG. 48 is a diagram showing an example of force-drawing development data.
- FIG. 49 is a diagram showing an example of aggregated card loan data.
- FIG. 50 is a conceptual diagram showing an example of transaction information stored in a card loan ledger file.
- FIG. 51 is a diagram showing an example of card loan development data.
- FIG. 52 is a diagram showing an example of a card loan consolidation day.
- Fig. 53 is a block diagram showing a configuration example of the purpose-specific loan / mortgage transaction information aggregator.
- FIG. 54 is a block diagram showing a configuration example of the purpose-specific loan transaction information expanding means.
- FIG. 55 is a block diagram showing a configuration example of the mortgage transaction information expanding means.
- Figure 56 is a diagram showing the scenario of a transaction example of loans by purpose and mortgages.
- FIG. 57 is a diagram showing the contents of the loan account used in the scenario shown in FIG.
- Figure 58 shows development data for fixed interest rates.
- Figure 59 is a diagram showing the development of floating interest rates.
- Figure 60 shows the development of fixed interest rates.
- Figure 61 is a diagram showing development data on floating interest rates.
- FIG. 62 is a diagram showing expanded data relating to Cap.
- FIG. 63 is a diagram showing an example of an aggregated data generated by the expanded data aggregating means for Cap.
- FIG. 64 is a diagram illustrating an example of fixed-part aggregated data generated by the fixed-part aggregated data merger and passed to the risk management system.
- FIG. 65 is a diagram showing an example of aggregated fluctuation data generated by the aggregated fluctuation data merger and passed to the risk management system.
- FIG. 1 is a block diagram for explaining a transaction information aggregating apparatus according to the present invention.
- the transaction information aggregating device 1 is an information processing device such as a computer or a workstation, and is generally connected so as to be able to acquire transaction information from a transaction information storage device 2 including a transaction information file included in an accounting system. Connected to the risk management system 3, the transaction information stored in the transaction information storage device 2 is aggregated and provided to the risk management system 3.
- the information processing device that constitutes the transaction information aggregating device 1 is not necessarily physically one device, but each component is realized by one information processing device, and the transaction is performed as a set of these components.
- the information aggregation device 1 may be configured.
- the transaction information storage device 2 may be composed of a file that is a copy of the transaction information file included in the accounting system. More specifically, the contents of the transaction information file are stored in a file in the transaction information storage device 2 by, for example, a patch process or an online process at the end of a day's transaction. May be duplicated. Further, when the transaction information storage device 2 is configured from a duplicate file of the transaction information file, the duplicate file does not need to be linked to the transaction information file of the accounting system online and in real time, and will be described later. It is only necessary to back up data at intervals necessary for risk management, for example, by batching once a day.
- transaction information refers to information relating to money transactions, and is a concept including, for example, information relating to various deposit transactions handled by banks and information relating to various account transactions.
- transaction information file refers to a file in which transaction information is stored in a readable and writable manner, and is a concept that includes, for example, a general account ledger file, a time deposit ledger file, and various loan ledger files in a banking system.
- risk management system refers to a system that manages risks related to the management of financial institutions, including interest rate risk, liquidity risk, and foreign exchange risk.For example, TSSummit of the United States Summit Inc. This is an example of a risk management system.
- the risk management system 3 processes the aggregated transaction information and other transaction information supplied from the transaction information aggregating device 1 to determine various interest rates, execute simulations for changes in risk, etc. Risk management information is generated and provided by the display device 4 and the printing device 5.
- the transaction information aggregating device 1 has a function of aggregating transaction information for use in risk management based on the transaction information stored in the transaction information storage device 2 and supplying this to the risk management system.
- transaction information is acquired from the transaction information storage device 2, and based on the transaction information, an aggregation reference date (the date on which the transaction information aggregation device executes aggregation, or A development record that indicates the occurrence of cash flows after the cash movement and the aggregation reference date, and a plurality of deployments that are grouped based on predetermined conditions. It has a function to generate one aggregated record from records.
- the transaction information aggregating device 1 functions to accurately store the information contained in one or a plurality of expanded records in the aggregated record, so that accurate information is provided to the risk management system, and the record processed by the risk management system is also processed.
- the number, that is, the data amount can be reduced.
- FIG. 2 is a block diagram showing a configuration example of the transaction information aggregating apparatus 1 according to the present embodiment.
- a transaction information storage device 2 stores a plurality of transaction information files relating to different financial instruments, such as a general deposit ledger file 21, a time deposit ledger file 22, a card loan ledger file 23, and a purpose-specific loan ledger file. 24, has a mortgage ledger file 25.
- the transaction information aggregator 1 has a general deposit transaction information aggregator 26, a term deposit transaction information aggregator 27, a card loan transaction information aggregator 28, and a purpose-specific loan 'home loan transaction aggregator 29'.
- the ordinary deposit ledger file 21 is in the ordinary deposit transaction information aggregator 26, the time deposit ledger file 22 is in the time deposit transaction information aggregator 27, and the card account ledger file 23 is a card loan.
- the transaction information aggregator 28 is connected to the purpose-specific mortgage file 24 and the housing account ledger file 25 to the purpose-specific mortgage / mortgage transaction information aggregator 29.
- Each transaction information aggregator 26 to 29 supplies the risk management system 3 with aggregated data on the financial products handled by the corresponding ledger file.
- the transaction information aggregator is provided for each ledger file because the conditions for generating cash flows differ for each financial instrument. This is to respond to this.
- Each transaction information aggregator has the function of collecting transaction information to be used for risk management based on the transaction information stored in the transaction information file and supplying this to the risk management system 3.
- the configuration and operation of each transaction information aggregator will be described below.
- FIG. 3 is a block diagram showing a configuration example of the ordinary deposit transaction information aggregator 26 applied to the ordinary ledger file 21.
- the ordinary deposit transaction information aggregating section 26 includes ordinary deposit transaction information expanding means 301 and ordinary deposit transaction information aggregating means 302.
- the ordinary deposit transaction information expanding means 310 is composed of an ordinary deposit transaction information acquisition unit 303 connected to the ordinary deposit ledger file 21 and a cash movement connected to the ordinary deposit transaction information acquisition unit 303. It has a processing unit 304 and an interest cash / flow processing unit 303, and an ordinary deposit development data storage unit 300 connected to the processing units 304 and 310.
- the ordinary deposit transaction information acquisition unit 303 has a function of acquiring data necessary for calculating the transfer of money from the ordinary account ledger file 21 for each record constituting the file.
- FIG. 4 shows an example of the structure of a record in the ordinary account ledger file 21.
- the record includes an account number field 401, a customer number field 402, a name field 400, a common management code group field 404, a passbook balance field 405, a last transaction date field 406, Chain address field 4 07, Transaction code field 4 08, Amount field 4 0 9, Handling date field 4 1 0, Description field 4 1 1, Chain address There are fields 4 1 2,.
- the passbook balance field 405 records the balance of the savings account corresponding to the record
- the transaction code field 408 stores deposits and withdrawals for the savings account.
- a code is recorded to distinguish between transactions such as interest.
- the amount field 409 stores the amount of the transaction
- the handling date field stores the date on which the transaction was performed.
- the address of the next part of the record is stored in the chain address 412, and a chain address field 412 is generated from the transaction code field 408 every time a transaction is performed, and is chained one after another. It forms one record.
- the savings transaction information acquisition unit 303 stores data necessary for calculating the transfer of money, for example, the passbook balance field 405, the last transaction date field 406, the transaction code field 408, and the amount field. Acquires the data stored in 409, handling date field 410, etc.
- the cash movement processing unit 304 acquires, for each record in the ordinary deposit ledger file 21, the principal and interest generated on the processing reference date. Generate a deployment record that records the change in
- the interest cash flow processing unit 306 calculates the interest on the next interest day for each record in the ordinary ledger file 21 based on the data acquired by the ordinary transaction information acquisition unit 303 Then, this is stored in the development record and passed to the ordinary deposit development data storage unit 305.
- the ordinary deposit development data storage unit 304 accumulates development records supplied from the cash movement processing unit 304 and the interest cash flow processing unit 303 and accumulates them as ordinary deposit development data.
- Ordinary deposit development data the ordinary deposit transaction information development means 301 21 This is data that is a collection of all the ordinary deposit transaction information development records generated as a result of processing all the records in 1.
- the ordinary deposit transaction information aggregating means 302 includes an aggregation target extraction unit 300 connected to the ordinary deposit development data storage unit 303 and an aggregation content calculation connected to the aggregation target extraction unit 303. It has a unit 308 and an ordinary deposit aggregated data storage unit 309 connected to the aggregated content calculation unit 308.
- the aggregation target extracting unit 307 groups and extracts the group of ordinary deposit expanded data records that can be aggregated from the ordinary deposit expanded data storage unit 305 from the ordinary deposit expanded data storage unit 305.
- “Aggregation” refers to development on the same cash flow date (principal-interest transfer date, prosperity date) and the same currency (yen, US dollar, euro, etc.) Organize records into one group so that they are aggregated into one aggregated record. For example, you can sort explosion records using the cash flow date and currency as keys, and if the cash flow date and currency are different from the previous record, use a different group. And so on.
- the aggregation content calculation unit 308 sums up the transfer of principal, interest, and the next interest day for each group. Then, the data is stored in one aggregated record, and the aggregated record is sent to the ordinary deposit aggregated data storage unit 309. For an expanded record that does not belong to a group, one aggregated record is generated without summing and sent to the ordinary deposit aggregated data storage unit 309.
- aggregated ordinary deposit data which is a set of aggregated records
- the aggregated ordinary deposit data storage unit 309 accumulates the completed aggregated ordinary deposit data and stores the data. It functions to supply aggregated savings data to the risk management system3. It is desirable that the format of the aggregated record be in a format that conforms to the specifications of the risk management system 3.However, an interface (not shown) that converts the aggregate data of ordinary deposits into a format that conforms to the specifications of the risk management system 3 It is also possible to supply the risk management system 3 with the savings account aggregated data via the means.
- Fig. 5 is a diagram showing a scenario of a transaction example regarding ordinary deposits.
- a new account # 1 was opened on March 10, 2000, ⁇ 100,000 was deposited, a new account # 2 was opened, and ⁇ 1,500,000 Is deposited, a new account # 3 is opened, and 5,000, 000 yen is deposited. These rates are 0.05% per year.
- another new account # 4 was opened, 800,000 yen was deposited, and $ 100,000 was purchased from account # 3. US $ 0.00 is deposited as a foreign currency savings account.
- the yen-dollar exchange rate at this time is 109.00 yen / dollar.
- 100,000 yen will be withdrawn from Account # 2 on April 28, but the withdrawal will be canceled the following day on 29th.
- July 15 Account # 1 is closed.
- a prolific day arrives on August 15 and interest is paid to all accounts.
- FIG. 6 shows the data stored in the savings data storage unit 2005 after the processing by the cash and movement processing unit 304 and the interest cash and flow processing unit 303.
- FIG. 7 is a diagram showing the ordinary deposit development data on the day 0, and FIG. 7 shows the ordinary saving development data generated by aggregating the ordinary deposit development data and stored in the ordinary deposit aggregated data storage unit 309; It is a figure which shows a deposit aggregation day.
- the ordinary deposit development data consists of a plurality of development records R 601, R 602, R 603, R 604, R 605, R 606, and each record is an account Number field 6 01, Currency field 6 0 2, CF (cash flow) Occurrence date field 6 0 3, Deposit principal field 6 04, Withdraw principal field 6 0 5, Interest rate field 6 0 6 It has a balance field 607, an interest accumulation field 608, and an interest rate field 609.
- the aggregate data of ordinary deposits shown in Fig. 7 is composed of aggregate records R701 and R702, and the aggregate record is composed of a product type field 711, an aggregate ID field 702, a currency field 703, It has a date field 704, a principal transfer amount field 705, an interest transfer amount field 706, and a balance field 707.
- a code identifying the corresponding financial instrument is entered in the product type field.
- Aggregate ID is an identifier that identifies aggregated savings data.
- the savings data shown in Fig. 6 is generated as follows. First, when the ordinary deposit transaction information acquisition section 303 acquires data from the ordinary account ledger file 21 that records records records relating to accounts # 1 to # 3, the cash movement processing section 304 acquires the account. The fact that # 1 to # 3 were newly opened and payments were made on March 10th respectively was confirmed by the above-mentioned transaction code field 408, amount field 409, and transaction date field 410 (Fig. 4 ), And generate expanded records R601, R602, and R603.
- Data acquired from the ordinary deposit transaction information acquisition unit 303 is stored in the fields of the account number, currency, CF occurrence date, and interest rate of the developed record.
- the deposit amount of each account is stored in the deposit principal field 604 and the balance field 607 of the corresponding record.
- the ordinary deposit transaction information acquisition section 303 determines whether or not it is necessary to enter the interest and interest amount 6 06 and the interest product number 6 08. In this case, it is not necessary, so expand it without entering it.
- the interest cash 'flow processing unit 306 determines from the data of the ordinary deposit transaction information acquisition unit 303 that the account was newly opened on March 10, and since the deposit period is 0 days, the interest 0 yen expansion record R 6 0 4, R 6 0
- R 606 is generated.
- the ordinary deposit expanded data storage unit 304 accumulates ordinary deposit expanded data as shown in FIG. Regarding the amount of principal transfer, etc., which is the amount entered in the fields of the development record, “10” (correct) refers to the amount coming in from the bank, and “1” refers to the amount leaving the bank (Negative).
- the ordinary deposit transaction information expanding means 301 instructs the ordinary ordinary deposit transaction information aggregating means 302 to start processing.
- the aggregation target extracting unit 3007 obtains the ordinary deposit development data from the ordinary deposit development data storage unit 304 and composes the ordinary deposit development data. Grouping and extracting those that can be aggregated from multiple expanded records.
- the grouping condition is that the records have the same CF occurrence date and the same currency development, and records that satisfy the aggregation condition are grouped.
- the aggregation content calculation unit 308 receives, for example, R601 to R603 as one group.
- the data of the deposit principal field 604 and the withdrawal principal field 605 of the three development records R 601 to R 603 are added together, and the principal transfer amount of the aggregated record Generate the data of the field 705, and add the data of the interest payment amount 60.6 field to generate the data of the interest transfer amount 706, and generate the data of the balance field 607.
- the data of the balance field 707 is generated by summing up overnight, and a code is created and stored according to the target financial product and currency by referring to a conversion table (not shown) that indicates the product type and aggregation ID. By doing so, an aggregate record R701 is generated. Similarly, 604, R605, and R606 are made into one group, and these are aggregated as described above to generate an aggregate record R702.
- the aggregated records R701 and R702 are accumulated in the ordinary deposit aggregated data storage unit 309, and supplied to the risk management system 3 as needed.
- FIG. 8 is a diagram showing the expanded data of savings accounts with April 17 as a reference date
- FIG. 9 is a diagram showing aggregated savings data of the same day.
- the transaction information developing means 301 generates the ordinary deposit developing data shown in FIG. 8 in the same manner as the operation described with reference to FIGS.
- the development data of savings account is the development record R 801 of account # 1, which is the development record of the principal and interest movements and the deposit balance on the base date of processing, generated by the cash movement processing unit 304.
- An expansion record R 802 for account # 2 an expansion record R 803 and R 804 for account # 3, and an expansion record R 805 for account # 4.
- the cash movement processing unit 304 stores the CF reference date field 803 of these expanded records in the field “203” indicating the processing reference date April 17, 2000 as “200 000 4 17”. ".
- a new account # 4 was opened and 80,000 yen was deposited. $ 100,000 is purchased from Funds in Account # 3, and $ 100,000 is deposited as a foreign currency savings account.
- the ordinary deposit transaction information expanding means 301 generates an expanded record as follows, thereby reflecting accurate transaction information in the expanded record. First, for the opening of new account # 4, a development record R805 is generated, and a development record R810 representing interest on the next prosperity date (August 15) is also generated. The purchase of $ 100,000 from the funds in Account # 3 is represented by the "1900 000" in the withdrawal principal field in development record R803. Also, a foreign currency savings deposit of $ 100,000 is represented by development record R804. Record R 804 contains the code “USD” in currency field 802 indicating that the currency is the US dollar.
- the interest cash / flow processing unit 300 expands the expansion record R 806 relating to the account # 1, which is the expansion record relating to the next interest day, the expansion record R 807 relating to the account # 2, and the expansion relating to the account # 3.
- the next interest rate day interest is stored in each of the development records R806 to R810 in the interest amount field.
- the interest on the next interest day is equivalent to the interest from the previous interest date (or the account opening date if the first interest date has not yet arrived) to the processing date for the deposit balance on the reference date. I do.
- the interest cash flow processor 306 writes “200000815” representing the next interest date August 15, 2000 in the CF occurrence date field of these records.
- the transaction information aggregating means 302 groups the expanded records of the same currency and the same CF occurrence date in the same manner as described above, and aggregates the grouped expanded records into one aggregated record.
- the savings development data R 8 0 1, R 8 0 2, R 8 0 3, R 8 0 5 that the currency is yen (JPY) and the cash flow occurrence date is April 17 is extracted as the aggregation target
- the group is extracted as a first group by the group, and is aggregated into the aggregate record R 90 # by the aggregation content calculation unit 308.
- the ordinary deposit development data R 804 showing the cash flow on April 1 for the currency “dollar” is extracted as the second group by the aggregation target extraction unit 307, and the aggregation content calculation unit 30 8 aggregated into an aggregated record R 902.
- the general deposit development data showing the cash flow on August 15 R 806, R 807, R 808, R 810 is the aggregation target extraction unit 3 It is grouped and extracted as a third group by 07, and is aggregated into an aggregated record R903 by the aggregated content calculation unit 308.
- the ordinary deposit development data R 809 showing the cash flow on August 15 for the currency “dollar” is extracted by the aggregation target extraction unit 307, and the aggregation record is calculated by the aggregation content calculation unit 308 It is collected in R904.
- FIG. 10 is a diagram showing expanded ordinary deposit data generated by the ordinary deposit transaction information expanding means 301 when the processing reference date is April 28, and
- FIG. 9 is a diagram showing consolidated ordinary deposit data generated by the ordinary deposit transaction information aggregating means 302 from the expanded data.
- the interest cash / flow processing unit 303 calculates interest on the next interest welfare date (August 15) for each of the accounts # 1 to # 4, and develops a development record storing the calculated interest. R1006-R1010 are generated.
- the generated expanded records R 1001 to R 1001 are stored as ordinary deposit expanded data in the ordinary deposit developed data storage unit 305.
- the generation of aggregated savings data shown in FIG. 11 is performed by the grouping unit extracting unit 307 based on the expanded ordinary deposit data stored in the expanded ordinary deposit data storage unit 305 in the same manner as described above. This is performed in the same manner as described above by generating an aggregated record by the conversion and aggregation content calculation unit 308.
- the cash flow of withdrawal of 100,000 yen from account # 2 is reflected in the principal transfer amount field of the aggregated record Rl101.
- FIG. 12 is a diagram showing the ordinary deposit expanded data generated by the ordinary deposit transaction information expanding means 301 when the processing reference date is April 29, and
- FIG. 9 is a diagram showing consolidated ordinary deposit data generated by the ordinary deposit transaction information aggregating means 302 from the expanded ordinary deposit data.
- the interest cash 'flow processing unit calculates the next interest welfare date (August 15) for each of the accounts # 1 to # 4, and a development record R1 206 storing the calculated interest. ⁇ R 1 2 1 0 is generated.
- the generation of aggregated savings data shown in FIG. 13 is performed by the grouping unit 307 based on the expanded ordinary deposit data stored in the expanded ordinary deposit data storage unit 305 in the same manner as described above. This is performed in the same manner as described above by generating the aggregated record by the aggregated content calculation unit 308, and the aggregated records R1301 to R1304 are generated.
- the cash flow of canceling the withdrawal of 100,000 yen from account # 2 is reflected in the principal transfer amount field and balance of the aggregated record R.1301.
- FIG. 14 is a diagram showing the ordinary deposit development data generated when the processing reference date is set to July 15 and
- FIG. 15 is a diagram showing ordinary deposit transaction information from the ordinary deposit development data.
- FIG. 9 is a diagram showing aggregated ordinary deposit data generated by an aggregation unit 302.
- the interest cash flow processor 306 calculates the next interest rate date (August 15) for the accounts # 2 to # 4 excluding the canceled account # 1, and calculates the interest. Generates an expanded record R 1406 to R 1409 in which the generated interest is stored in the outgoing interest amount field. Since the account # 1 has been canceled, the interest cash flow processor 306 does not generate cash flow (interest payment) savings development data for the account # 1.
- the developed records R1401 to R1409 generated as described above are stored as ordinary deposit developed data in the ordinary deposit developed data storage unit 305.
- the generation of aggregated savings data shown in FIG. 15 is performed by the aggregation target extraction unit 307 based on the unfolded ordinary deposit data stored in the unfolded ordinary deposit data storage unit 305 in the same manner as described above. This is performed in the same manner as described above by generating an aggregated record by the grouping and aggregation content calculation unit 308.
- the cash flow of principal payment and interest payment of 100,000 yen from Account # 1 is reflected in the principal transfer amount field of the aggregated record R1551.
- FIG. 16 shows the processing performed by the ordinary deposit transaction information development means 301 when the processing reference date was set to August 15th.
- FIG. 17 is a diagram showing the ordinary deposit development data generated by the ordinary deposit transaction information aggregating means 302 from the ordinary deposit development data. It is.
- August 15 is the prime date when interest is fixed and paid for all savings accounts.
- the ordinary deposit transaction information acquisition unit 304 acquires the data from the ordinary ledger file 21
- the cash movement processing unit 304 determines that the cash flow (interest payment, settlement) has occurred. Then, the development records R 1601, R 1602, R 1603, and R 1604 that store the interest amount paid in the outgoing interest amount field are generated.
- the interest cash flow processing unit 306 sets the development record R 166 5 corresponding to February 15th, 2001, which is the next interest day when the interest amount is stored in the interest amount field. , R 166, R 166, R 166 are generated for the accounts # 2 to # 4.
- the generation of the aggregated savings data shown in Fig. 17 is based on the grouping and aggregation contents by the aggregation target extraction unit 307 based on the ordinary deposit development data stored in the ordinary deposit development data storage unit 305.
- the calculation is performed in the same manner as described above by generating the aggregated record by the calculation unit 308.
- the aggregation content calculation unit 308 performs processing so that the amount in which interest is incorporated into the balance is stored in the balance field of the aggregation record.
- the generated expanded records R1701 to R1704 are stored in the ordinary deposit aggregated data storage unit 309 as ordinary ordinary deposit data.
- aggregated savings data that accurately represents the processing reference date and cash flows to be generated in the future is generated, and the aggregated savings data of the ordinary deposit is significantly larger than the original transaction information in the number of transactions. Data has decreased.
- aggregated data of ordinary deposits it is possible to Any very large number of cash flows can be handled by the risk management system.
- the time deposit transaction information aggregating unit 27 includes time deposit transaction information development means (hereinafter abbreviated as “time development method”) 1801 and time deposit transaction information aggregator (hereinafter referred to as the time deposit information aggregation means). , Abbreviated as “periodical aggregation means”) 1802, and a foreign currency fixed-term deposit exchange reservation information processing means (hereinafter abbreviated as “reservation processing means”) 1803.
- the time expansion means 18001 functions to receive time deposit transaction information data from the time deposit ledger file 22 and generate and output time deposit expansion data based on the transaction information data.
- the term aggregation means 1802 receives the time deposit development data from the time development means 1801, generates the term deposit aggregation data based on the development data, and outputs the data to the risk management system 3. .
- the reservation processing means 1803 receives the foreign exchange deposit data relating to the cancellation of the foreign currency deposit from the time deposit ledger file 22 and generates aggregated foreign exchange information based on the foreign exchange deposit data. Functions to output to management system 3.
- foreign exchange contract means that a certain foreign currency amount is scheduled to be exchanged at the currency exchange rate on a specific day before the maturity date of a foreign currency deposit. If the ledger file does not include a foreign currency deposit, the reservation processing means may not be provided.
- FIG. 19 is a block diagram showing an example of the configuration of the regular deployment means 1801 and the regular aggregation means 1802.
- the periodical expansion means 18001 is composed of a time deposit transaction information acquisition section 1901 connected to the time deposit ledger file 22 and a cash movement processing section 1 connected to the transaction information acquisition section 1901. It has a cash flow processor 9003 and a principal and other cash flow processor 1903, and a developed data storage 1904 connected to the processors 1902 and 1903.
- the transaction information acquisition unit 1901 acquires data necessary for calculating the transfer of money from the time deposit ledger file 22 for each record constituting the file.
- FIG. 20 shows an example of the record structure of the time deposit ledger file 22.
- the record includes a time code field 2001, which indicates the term of the time deposit, automatic cancellation, automatic cancellation, etc. Since it contains the type code field 2000 that indicates the type, the deposit / withdrawal processing unit 32 processes elements specific to time deposits such as the maturity of time deposits, their automatic continuation, and automatic cancellation by referring to these. it can.
- the transaction information acquisition unit 1901 has a function of reading necessary data for each record and passing it to the cash movement processing unit 1902 and the cash flow processing unit 1903 such as principal.
- the cash movement processing unit 1902 records the principal and interest fluctuations that occurred on the base date of processing based on the data acquired by the transaction information acquisition unit 1901, for each record in the time deposit ledger file 22. Generate the recorded time deposit development record.
- the principal and cash processing unit 1903 calculates the principal and interest for each record in the time deposit ledger file 22 based on the data acquired by the transaction information acquisition unit 1901. Funds on the day when the amount fluctuates (maturity, interest payment date) It has the function of calculating the amount of money and interest and the balance of the deposit, storing these in the development record, and passing it to the fixed-term deposit development data storage unit 1904.
- the time deposit development data storage unit 1904 stores the records supplied from the cash movement processing unit 1902 and the principal and other cash flow processing unit 1903 and stores the time deposit development data. To form When the time deposit transaction information developing means 18001 processes all the records in the time deposit ledger file 22, the time deposit expanded data is completed.
- the term deposit transaction information aggregating means 1802 includes an aggregation target extraction section 1905 connected to the time deposit development data storage section 1904 and an aggregation connected to the aggregation target extraction section 1905. It has a content calculator 1906 and a term deposit aggregated data accumulator 1907 connected to the aggregated content calculator 1906.
- the aggregation target extraction unit 1905 has a function of grouping and extracting, from the time deposit expanded data storage unit 1904, records that can be aggregated from the time deposit expanded data records. Aggregation uses development records for the same cash flow date (including principal and interest fluctuation dates, new account opening dates, maturity dates, and interest payment dates) and the same currency (yen, US dollars, unity, etc.). It works to aggregate into one aggregated record.
- the developed records are sorted by cash flow occurrence date and currency, and if the cash flow occurrence date and currency are different from the previous record, another method is used. It is realized by grouping.
- the aggregated content calculation unit 1906 receives the grouped records from the aggregation target extraction unit 1905, the aggregated principal, interest, and deposit balances of each group are summed up, and It is stored in an aggregated record, and functions to send the aggregated record to the term deposit aggregated data storage unit 1907.
- a function to generate one aggregated record without adding them up and send the aggregated record to the time deposit aggregated data storage unit 1907 is provided.
- the processing is performed for all the groups, and the time-deposit consolidated data set, which is a set of consolidated records, is completed. Functions to feed system 3.
- the format of the aggregated record is a format that conforms to the specifications of the risk management system 3 , but an unillustrated interface that converts the aggregate data of time deposits into a format that conforms to the specifications of the risk management system 3 is not shown.
- Aggregated time deposit data may be supplied to the risk management system 3 via one-face means.
- FIG. Figure 21 is a diagram showing a scenario of a transaction example regarding time deposits.
- Account # 1 has a deposit of 1,000,000 yen, a six-month fixed deposit, with an applicable interest rate of 0.12%, and automatic principal and interest renewal type.
- Account # 2 has a deposit of 3,000 , 000 yen, two-year term deposit, 0.15% applicable interest rate, interest payment type, automatic cancellation type.
- Account # 3 is a deposit of 2, '000, 000 yen, a three-month time deposit with a rate of 0.12%, and an automatic principal transfer type.
- New Account # 4 has a deposit of 50,000 yen, a two-year term deposit, an applicable interest rate of 0.15%, and an automatic cancellation type.
- Account # 3 expires and interest payments and principal renewal continue.
- account # 5 was deposited The amount is 1,000,000 yen, March time deposit, applicable rate is 0.12%, and automatic cancellation type.
- Another new account # 6 is a foreign currency term, with a deposit of 100,000 USD, a three-month foreign currency term deposit, an applicable interest rate of 4.45860%, and an automatic cancellation type.
- Account # 1 expires, the account continues to pay interest and interest, Account # 3 also expires and is terminated, and Account # 5 also expires, and the account is terminated. # 6 also expires and will be canceled.
- Account # 1 expires and is terminated, and interest payment is made on Account # 2.
- Account # 2 expires on March 10, 2002, and Account # 4 expires on April 17, 2012.
- FIG. 22 is a diagram showing the time-deployment data generated by the time-deposit transaction information development means 1801 on March 10, 2000
- FIG. 23 is a diagram showing time-deposit transaction information on the same day.
- FIG. 9 is a diagram showing time deposit aggregated data generated by an aggregation means 1 802.
- the time deposit development data shown in Fig. 22 consists of a plurality of development records R2201 to R2207, each of which contains an account number field 2201, a currency field 2202, and CF (cash flow) generation.
- the aggregated time deposit data shown in Fig. 23 is composed of aggregated records R2301 to R2305, and each aggregated record has a product type field 2301, an aggregated ID field 2302, It has a currency field 2303, a date field 2304, a principal transfer amount field 2305, an interest transfer amount field 2306, and a balance field 23007.
- Product Type Feel In the field a code identifying the corresponding financial instrument is entered.
- the aggregation ID is an identifier for identifying the aggregation data.
- the unfolding data shown in Fig. 22 is generated as follows. First, when the time deposit transaction information acquisition unit 1901 acquires data from the ledger file 2 2, the cash movement processing unit 1902 opens accounts # 1 to # 3, and on March 10 It is determined from the record corresponding to each account in the ledger file 22 that the payment has been made, and the developed records R2201, R2202, and R2203 are generated. Account number field 222, currency field 222, CF occurrence date field 2203, and interest rate field 22009 store the data obtained from the ledger file. The amount is stored in the deposit principal field 222 and the balance field 222 of the corresponding record.
- the principal and other cash flow processing section 1903 sets the development record R 2 2 that indicates the cancellation of the maturity date of each account and the payment of interest as the principal and interest fluctuation date of accounts # 1 to # 3. 0 to R2207 are generated.
- the principal and cash flow processing unit 1903 calculates the principal paid by termination, the interest paid upon termination, and the interest paid on the interest payment date. The calculated values are stored in 2 205, Interest Interest Amount Field 220 6, and Balance Field 220 7.
- Each expanded record is passed to the expanded data storage section 1904.
- the expanded data storage unit 1904 accumulates expanded data as shown in FIG.
- the regular deployment unit 1801 instructs the regular aggregation unit 1802 to start processing.
- the regular aggregation means 1802 retrieves the developed data from the developed data storage section 1904 by the aggregation target extracting section 1905.
- the records that can be aggregated among the records included in the expanded data are grouped and extracted.
- development records of the same currency and the same CF occurrence date are grouped.
- the expanded records R2201, R2202, and R2203 have the same currency and the same CF occurrence date, so these three records constitute one aggregated record.
- the aggregated content calculation section 1906 receives these three records as one group, and sums the data of the deposit principal field 2204 and the withdrawal principal field 2205 to form the principal. Generate the data of the transfer amount field 2305, add the data of the interest outflow amount 2 206 field and generate the data of the interest transfer amount 2303, and the balance field 2202
- the data of the balance field 2307 is generated by summing up the data of the balances, and the product type and aggregation ID are created by referring to the conversion table (not shown) and a code is created and stored according to the target financial product and currency. As a result, an expansion record R2301 is generated.
- aggregated records R2301 to R2305 are accumulated as aggregated data in the aggregated data storage unit 1907, and supplied to the risk management system 3 as needed. It is preferable that the format of the aggregated record is a format that conforms to the specifications of the risk management system 3, but the aggregated data is converted to a format that conforms to the specifications of the risk management system 3. Consolidated to risk management system 3 via interface means Data may be supplied.
- Time deposit expanded data is generated by 1801
- time deposit integrated data is generated by time deposit transaction information aggregating means 1802 based on the time deposit expanded data.
- Fig. 24 shows the time deposit development data generated when April 17, 2000 is the processing base time
- Fig. 25 shows the time deposit aggregate data on the same day
- Fig. 26 shows the time deposit development data on June 10, 2000
- Fig. 27 shows the time deposit aggregate data on the same day
- Fig. 28 shows the expanded data of time deposits on September 10, 2000
- Fig. 29 shows aggregated data of time deposits on the same day.
- Fig. 30 shows the time deposit development data on March 10, 2001
- Fig. 31 shows the time deposit aggregation data on the same day.
- Fig. 32 shows the development of fixed-term deposits on April 17, 2001
- Fig. 33 shows the consolidated data of fixed-term deposits on the same day.
- the term deposit aggregated data that accurately represents the cash flow that will occur in the future on and after the processing reference date is generated.
- the number of cases is much smaller than the information.
- FIG. 4 is a block diagram showing a configuration example of a reservation processing means 1803.
- the reservation processing means 1803 receives the exchange reservation data receiving section 3401 which receives data relating to the exchange reservation from the time deposit ledger 'file 22 and the output of the receiving section 3401.
- the received purchase price and sale price calculation unit 3402 and the exchange reservation aggregated data storage unit 3404 that receives the output of the calculation unit 3402 and transfers the foreign exchange summary data to the risk management system 3 Have.
- the Exchange Receipt Data Overnight Receiving Section 3401 reads the data in the time deposit ledger file, and extracts the data related to each exchange contract, such as the maturity date, reserved date, reserved transaction amount (foreign currency), and reserved rate. Then, it has a function to output this.
- the purchase price and sales price calculation section 3402 calculates the purchase price (refers to the reservation transaction amount and its interest amount), sale price (purchase amount, Etc.), and a function to generate a foreign exchange information aggregated record that stores these values for each foreign exchange contract.
- the exchange contract information aggregated data storage unit has a function of accumulating exchange contract information aggregated data that is a collection of aggregated exchange contract information records.
- FIG. 35 is a diagram showing a scenario of a transaction example regarding time deposits.
- the scenario has the following contents. On March 10, 2000, Account # 1 was newly opened with a deposit of US $ 1,000,000. On March 11 the same year, Account # 2 was newly opened with a deposit of $ 500,000. On August 25 of the same year, a foreign exchange reservation was made for Account # 1, with a reservation amount of US $ 10,000 and a reservation rate of 107.50 yen. On August 26, a foreign exchange reservation was made for Account # 2 at a reservation amount of US $ 500,000 and a reservation rate of 106.98 yen. August 27 of the same year A foreign exchange reservation was made for Account # 1 at a reservation amount of US $ 50,000 and a reservation rate of 107.00 yen.
- the exchange reservation data overnight receiving unit 3401 extracts data on the exchange contract from the time deposit ledger file 22 and receives it.
- FIG. 36 shows an example of the contents of the data acquired by the exchange reservation data receiving section 3401 from the time deposit ledger file 22.
- the exchange reservation data receiving unit 340 0 1 uses the currency, deposit amount (foreign currency), exchange rate, interest rate, deposit date, deposit period, expiration date, reservation date, We have received reservation amounts and reservation rates.
- deposit amount foreign currency
- exchange rate interest rate
- deposit date deposit period
- expiration date reservation date
- the purchase price / sale price calculation unit 3402 receives the data on the foreign exchange contract as shown in FIG. 36 from the exchange reservation data overnight receiving unit 3401, and based on the data, Perform calculations, etc.
- FIG. 37 is a diagram for explaining the calculation performed in the purchase price / sales value calculation section 3402.
- the purchase price-sell price calculation unit 3402 creates one record for each exchange contract. Each record consists of a product type field 3701, an aggregate ID field 370, a buy currency field 370, a sell currency field 370, a date field 370, and a purchase amount field 370. 06, with a sales amount field of 3 0 7.
- the purchase price / sale price calculation section 3402 enters the code that identifies the financial instrument corresponding to the product type field, and enters the code in the aggregate ID field. Enter an identifier to identify the foreign exchange reservation information aggregated data, enter a code indicating the type of foreign currency in the Buy Currency field, enter a code indicating Japanese currency in the Sell Currency field, and enter a code in the Buy Amount field. Enter the reservation amount, and in the sales amount field, calculate and enter the amount when the amount entered in the purchase amount field is exchanged for the selling currency at the reservation rate.
- the purchase price / sale price calculation unit 3402 integrates the records to generate exchange reservation information aggregate data.
- the purchase price / sales price calculation unit 3402 which groups and extracts those records that can be aggregated from among the above records, and sums the purchase price and sale price values of records belonging to the same group into one Make an aggregated record.
- the grouping condition is to group records with the same date of occurrence of CF and the same buying currency and selling currency.
- the expanded records R 3 701, R 3 7 0 3, and R 3 7 0 4 have the same currency and the same CF occurrence date, so these three records constitute one group.
- Fig. 38 to Fig. 41 show examples of aggregated data of foreign exchange contract information generated by the purchase price / sales calculation unit 3402.
- Fig. 38 shows the aggregated data of exchange reservation information when the reference date for processing is set to August 25, 2000.
- the purchase price / sale price calculation unit 3402 generates only the record R3701, and this record is subject to aggregation.
- the exchange reservation information aggregated data contains the record R380. Only 0 1 will be included.
- Fig. 39 shows the aggregated data of exchange reservation information when the processing reference date is August 26, 2000.
- the purchase price / sale price calculation section 3402 generates the records R3701, R3702, and these two records are subject to aggregation.
- Fig. 40 shows the aggregated data of exchange reservation information when the processing reference date was August 27, 2000.
- the purchase price / sale price calculation unit 3402 generates records R 3701, R 3702, and R 3703, and these three records are subject to aggregation.
- the exchange contract information aggregated data includes record R4001 in which records R3701 and R3703 are aggregated, and R402 in which records R3702 are aggregated. .
- Fig. 41 shows aggregated data of foreign exchange contract information when the reference date for processing is September 2, 2000.
- the purchase price / sales value calculation unit 3402 generates records R3701, R3702, R3703, and R3704, and these four records are subject to aggregation.
- records R 3101, R 3703 and R 3704 were consolidated, and record R 4101 and record R 3702 were consolidated.
- R4102 will be included.
- These aggregated exchange contract information records are accumulated as aggregated exchange contract data in the aggregate exchange reservation data storage unit 3403, and are supplied to the risk management system 3 as necessary. It is preferable that the format of the aggregated record conforms to the specifications of the risk management system 3, but an interface (not shown) for converting the aggregated data into a format that conforms to the specifications of the risk management system 3.
- the exchange contract aggregation data may be supplied to the risk management system 3 via the.
- aggregated foreign exchange forward contract data that accurately represents the cash flow of both foreign and Japanese currency that will occur in the future (maturity date) is generated, and the aggregated data is much larger than the original transaction information. ⁇ Data volume is decreasing.
- the risk management system can be used for cash flows that are extremely large, such as so-called retail transactions. System.
- a configuration example of the card loan transaction information aggregating unit 28 for aggregating transaction information recorded in the card loan ledger file 23 will be described with reference to FIG.
- the card loan transaction information aggregating unit 28 includes card loan transaction information expanding means (hereinafter abbreviated as “card loan expanding means”) 4201 and card loan transaction information aggregating means (hereinafter referred to as “card loan expanding means”). , Abbreviated as “card loan consolidation means”).
- the force-drawing developing means 4201 functions to receive card loan transaction information data from the card loan ledger file 23, generate and output card loan development data based on the transaction information data.
- the force draw aggregation means 4202 receives the force draw development data from the card loan development means 4201, generates a card loan aggregation data based on the development data, and uses this as a risk. Functions to output to management system 3.
- the card loan developing means 4 201 comprises a card loan transaction information acquisition section 4 203 connected to the card aperture ledger file 23, and a transaction information acquisition section 4 2 Cash / movement processing unit 4 2 0 4 and interest cash flow processing unit 4 206 connected to 0 3, and development data storage unit 4 connected to the processing units 4 204 and 4 206 205.
- the transaction information acquisition section 4203 stores data necessary for calculating the transfer of money from the card loan ledger file 23 as one of the constituent files of the file. For each record.
- the records in the card loan ledger file 23 include account number, interest rate, contract repayment date, repaid amount each time, refund, repayment interest, loan balance, next balance product number, next interest amount, next repayment date, last update Includes days.
- the transaction information acquisition unit 4203 has a function of reading out necessary data for each record and passing the data to the cash movement processing unit 4204 and the interest cash flow processing unit 4206.
- the cash movement processing unit 424 is based on the data acquired by the transaction information acquisition unit 423 for each record in the card loan ledger file 23, and the principal generated on the processing base date. Generates a force-drain deployment record that records interest and interest fluctuations, and the loan balance on the processing reference date.
- the interest cash ⁇ It has the function of calculating the interest amount, storing this in the development record, and passing it to the card-lone development data storage section 425.
- the force drone development data storage unit 4205 stores the records supplied from the cash / movement processing unit 4204 and the interest cash / flow processing unit 4202 and stores the card loan development data. It has the function of storing as.
- the force draw transaction information developing means 4201 processes all the records of the card loan ledger file 23, the card loan developed data is completed.
- the card loan transaction information aggregating means 4 202 is connected to the aggregation target extraction unit 4207 connected to the card loan development data overnight storage unit 4205 and the aggregation target extraction unit 4207. 9 ′, and an aggregated content calculation unit 4208 and a card loan deposit aggregated data storage unit 4209 connected to the aggregated content calculation unit 4208.
- the aggregation target extraction unit 4207 has a function of extracting, from the card loan development data storage unit 4205, the group of records of card loan development data that can be aggregated and extracting them. Aggregation functions to aggregate deployment records for the same cash flow—the date of occurrence (including the base date for processing) —into one aggregation record. As a method of grouping, for example, the development records are sorted using the cash flow occurrence date as a key, and if the cash flow occurrence date is different from the previous record, it is realized by another group.
- the aggregated content calculation unit 4208 receives the group of records from the aggregation target extraction unit 4207, the aggregated principal, interest, and deposit balances of each group are summed up. It is stored in one aggregated record and functions to send the aggregated record to the card loan aggregated data storage unit 4209. For unfolded records that do not form a group, the function is to generate one aggregated record without performing summation and send it to the card loan aggregated data storage unit 4209.
- the processing is performed for all groups, and the aggregated card loan data, which is a set of aggregated records, is completed.
- the aggregated card loan data storage unit 4209 stores the completed aggregated card loan data, and stores the accumulated card loans. It functions to supply the aggregated data to the risk management system 3. It is desirable that the format of the aggregated record be in a format that conforms to the specifications of the risk management system 3.However, an interface means (not shown) that converts the card loan aggregate data into a format that conforms to the specifications of the risk management system 3 is provided.
- the drone aggregated data may be supplied to the risk management system 3 via the Internet.
- Figure 43 is a diagram showing a scenario of a card drone transaction example.
- the amount of borrowing for account # 1 was 200,000 yen
- the contracted interest rate was 9.00%
- the contractual repayment date was 12 days
- each repayment was 20
- a card account with a condition of 000 yen is generated
- the loan amount of loan account # 2 is 100,000 yen
- the contract interest rate is 9.00%
- the contract repayment date is 27 days
- the repayment amount is 20,000 each time.
- a yen is generated, and thereafter, repayment is made on loan account # 1 on the 12th of every month, and repayment is made on account 27 of the monthly account on the 27th of every month.
- FIG. 44 is a conceptual diagram showing an example of transaction information stored in the card loan ledger file 23 on February 10, 2000
- FIG. 45 is a diagram showing card loan development on the same day.
- FIG. 46 is a diagram showing force-drow development data generated by the means 420 1, and FIG. 46 shows a card-row aggregation data generated by the force-drain aggregation means 42 02 on the same day.
- FIG. 46 is a diagram showing force-drow development data generated by the means 420 1
- FIG. 46 shows a card-row aggregation data generated by the force-drain aggregation means 42 02 on the same day.
- the expanded data shown in Fig. 45 consists of a plurality of expanded records R4501, R4502, R4503, and R4504, each of which has an account number field of 4501 and a currency field.
- the card loan aggregate data consists of aggregate records R4601, R4602, R4603, and R4604. Each aggregate record consists of a product type field 4601, an aggregate ID field 4602, and a currency field. 46 03, repayment date code field 46 04, date field 460 5, principal transfer amount field 46 0 6, interest transfer amount field 460 7, balance Field 468. In the product type field, a code identifying the corresponding financial product is entered.
- the aggregation ID is an identifier for identifying the card loan aggregation data.
- the transaction information acquisition unit 4203 acquires the data as shown in FIG. 44 from the drone ledger file 23.
- the cash movement processing unit 4202 determines that a loan with a debt of 200,000 yen has been generated for account # 1, based on the data of the force-drawing transaction information acquisition unit 4203. Then, generate an expansion record R4501. Similarly, it determines that a loan with a borrowed money of 100,000 yen has been generated for account # 2, and generates an expansion record R4502. Corresponding data is entered in the fields of each record by the cache movement processing unit 4202.
- the interest cash 'flow processing unit 4 206 generates an expansion record R 4 0 3 relating to the next repayment date of account # 1, and generates an expansion record R 4 504 relating to the next repayment date of account # 2.
- the interest amount calculated by the interest cash flow processing unit may be entered in the record, and the card account transaction information acquisition unit 4203 may use the ledger file as shown in Fig. 44.
- the interest amount may be obtained from the interest cash and the interest amount may be copied to the record by the flow processing unit.
- the expanded records R 4 501 to R 4504 generated as described above are passed from the processing units 4 204 and 4 206 to the expanded data storage unit 4 205,
- the expanded data storage unit 420 stores this.
- the card loan aggregating means 4202 groups and extracts, from the expanded data storage section 4205, those which can be aggregated among the expanded data record groups by the aggregation target extracting section 4207.
- the development record of the same CF occurrence date, the same currency and the same since there are no two or more expanded records that satisfy this condition, no grouping is performed in the aggregation target extraction unit 4207, and the expanded records R4501, R4502, Aggregated records R4601, R4603, R4602, and R4604 corresponding to R4503 and R4504, respectively, are calculated by the aggregate content calculation unit 4208. It is generated and becomes the force data aggregated data shown in Fig. 46.
- the principal transfer amount and the interest transfer amount are summed up by the consolidation content calculation unit 428, and the principal transfer amount field 460, interest of the consolidated record is added. This is entered in the transfer amount field 4607 and the balance field 4608.
- FIG. 47 is a conceptual diagram showing an example of transaction information stored in the card loan ledger file 23 on March 12, 2000, and FIG. It is a figure which shows the expansion
- FIG. 50 is a conceptual diagram showing an example of transaction information stored in the card loan ledger file 23 on March 27, 2000
- FIG. Fig. 52 is a diagram showing the development data generated by the card loan development means 4201 in Fig. 52.
- Fig. 52 is a diagram showing the card loan aggregation data generated by the card loan aggregation means 4202 on the same day. is there.
- card loan aggregate data that accurately represents the processing reference date and future cash flows for card loan transactions is generated.
- the aggregated data has significantly reduced the number of transactions and data volume compared to the original transaction information.
- a very large number of cash flows such as so-called retail transactions can be processed by the risk management system.
- the purpose-specific loan / housing unit transaction information aggregating unit 29 which aggregates transaction information relating to purpose-built loans such as car loans, pridal's loans, travel loans, and mortgages, will be described.
- FIG. 53 is a block diagram showing an example of the configuration of the purpose-specific loan / housing unit transaction information aggregation unit 29.
- loan-by-purpose ⁇ Mortgage transaction information aggregator 29 is a means for developing loan transaction information by purpose 5 3 0 1 for aggregating transaction information related to loans by purpose 5 0 2, fixed-part development data aggregation means 5 3 0 3, and variable-part development data aggregation means 5 3 0 4, and mortgage transactions to aggregate transaction information on housing units
- Information development means 5 3 0 6, fixed / floating / cap deployment data distribution means 5 3 0 7, fixed-part development data aggregation means 5 3 0 8, and variable-part development data aggregation means 5 3 0 9 And a means for integrating and decompressing the data for the Cap component, and a means for merging the data for fixed-content aggregation 530 and the means for merging the variable-content aggregated data 53011.
- the purpose-specific loan development means 53301 receives the purpose-specific loan transaction data from the purpose-specific loan source file 24 and generates the purpose-specific loan development data based on the transaction information data. And work to output.
- FIG. 54 is a block diagram showing a configuration example of the purpose-specific loan transaction information developing means 5301.
- the development means 5301 is connected to the purpose-specific loan ledger file 24.
- Loan transaction information acquisition unit 5 4 0 1 continued by purpose and the transaction information acquisition unit 5
- the components of the purpose-based loan development means 5310 are that the principal and cash flow processing unit 5404 generates development records for each change in the principal, interest, and deposit balances for each account. Except for, it operates in the same manner as the corresponding components of the card account transaction information expanding means 4201 shown in FIG.
- the fixed / floating spread data distribution means 5302 has a function of dividing the loan development data for each purpose into spread data relating to fixed interest rates and spread data relating to floating interest rates.
- the fixed-volume development data aggregation means 530 3 receives fixed-volume development data for fixed interest rates from the fixed-variation-based development data distribution means 5302, and based on the development data, fixes the development data for each purpose. It functions to generate aggregated loan data by purpose for fixed minutes that aggregates development data related to interest rates, and to output this.
- FIG. 55 is a block diagram showing a configuration example of the mortgage transaction information expanding means 5306.
- the developing means 5306 comprises a mortgage transaction information acquisition section 55001 connected to the mortgage ledger file 25, and a transaction information acquisition section.
- the mortgage development means 5300 receives the mortgage transaction information data from the mortgage ledger file 25, and based on the transaction information data, Functions to generate and output loan development data.
- the respective components of the mortgage transaction information developing means 530, except for the Cap processing unit 550, are the corresponding components of the purpose-specific loan transaction information developing means 5301, shown in FIG. It operates in the same way as.
- variable development data aggregation means 5304 receives fixed development data related to floating interest rates from the fixed / floating development data distribution means 5320, and based on the development data, the floating interest rate of loan development data for each purpose.
- the function is to generate aggregated loan data by purpose, which aggregates development data related to minutes, and output this.
- Fixed / floating / C ap deployment data distribution means 5 3 0 7 divides housing opening development data into development data for fixed interest rates, development data for floating interest rates — development data for evenings and cap Output function.
- the fixed-volume development data overnight aggregation means 530 8 is fixed, variable, and receives the development data related to fixed interest rates from the CAP-specific development data distribution means 5307, and based on the development data, develops mortgage data. It functions to generate and output aggregated fixed-mortgage loan data that aggregates development data related to fixed interest rates.
- Floating data development data aggregation means 503 9 9 is fixed, floating, and development data by Cap.Receives development data on floating interest rates from evening distribution means 530 7 and develops mortgage loans based on the development data. Development related to floating interest rates in data The function is to generate and output aggregated mortgage data for floating rates that summarizes data.
- C ap development data aggregation means 5 3 1 0 is fixed / floating ⁇
- C ap development data distribution means 5 3 0 7 receives development data on C ap part from development data and develops mortgage based on the development data
- the development data about the Cap It functions to generate aggregated data for Cap that summarizes the evening and passes it to the risk management system 3.
- the fixed-part aggregated data merging means 5305 receives the fixed-rate expanded data from the fixed-part expanded data aggregation means 5330 and 5308, respectively, and converts them into one fixed-part aggregated data. Has the function of passing to the risk management system 3.
- variable aggregated data merging means 5 3 1 1 receives the expanded data relating to the variable interest rate from the variable expanded data aggregate means 5 3 4 and 5 3 9, respectively, and combines them into one variable aggregated data. Has the function of passing to system 3.
- Fig. 56 shows a scenario of a transaction example of loans by purpose and mortgages.
- loan accounts # 1 to # 6 having the contents shown in Fig. 57 were opened on February 10, 2000, and thereafter, a predetermined amount of repayment was made for each account on each contract day every month. What happens.
- the purpose-specific loan ledger file 24 includes records R5702, R5703, and R5705 corresponding to accounts # 2, # 3, and # 5.
- the recorded loan transaction information developing means 5301 acquires the record, and generates expanded data relating to the fixed interest rate and the floating interest rate, respectively, from the record.
- the generated expanded data is divided by the distributing means 5302 into expanded data relating to the fixed interest rate and expanded data relating to the variable interest rate.
- Fig. 58 shows the fixed interest rate transferred from the distribution means 5302 to the fixed development data aggregation means 5330.
- FIG. 59 is a diagram showing development data relating to the variable interest rate passed from the distribution means 5302 to the variable development data aggregation means 5304.
- the fixed part expanded data aggregation means 5 3 0 3 and the variable part expanded data aggregation means 5 3 0 4 respectively group the records of the expanded data for each repayment date and for each repayment, and record the records in the same group.
- the principal, interest, and loan balances are combined to generate aggregated data.
- the mortgage ledger file 25 contains records R5701, R5704, R570 corresponding to accounts # 1, # 4, and # 6. 6 is recorded, and the mortgage transaction information expanding means 5330 acquires the record and generates expanded data relating to the fixed interest rate, the floating interest rate, and the Cap, respectively.
- the generated development data is divided into fixed-development data for fixed interest rates, development data for floating interest rates, and expansion data for Cap, by the distribution means 530, respectively. It is passed to the aggregation means 5308, the fluctuation data development data aggregation means 5309, and the Cap development data aggregation means 5310.
- FIG. 60 is a diagram showing expanded data relating to the fixed interest rate passed from the distribution means 530 7 to the fixed development data aggregation means 5308
- FIG. 61 is a view showing the distribution means 530
- FIG. 6 is a diagram showing expanded data relating to the variable interest rate passed from 7 to the variable development data aggregation means 5309
- FIG. 6 2 shows the distribution data aggregation means 5 from the distribution means 5307.
- FIG. 7 is a diagram showing an unfolding process regarding the Cap component passed to 310.
- the fixed-volume development data overnight aggregation means 5330 and the variable-expansion data aggregation means 5309 each group the records of the development data for each repayment date and each payback, and Aggregate data is generated by adding the principal, interest, and loan balance of the record.
- the Cap data expanded data aggregation means 5 3 10 10 groups the records of the expanded data into records having the same repayment and the same S trike, and sums up the balances of the records in the same group to aggregate the data. Produce evening.
- Fig. 63 shows an example of the aggregated data generated by the Cap data expanded data aggregation means 5310.
- the fixed-minute aggregated data merger 5305 receives the fixed-minute aggregated data from the fixed-value-developed data aggregaters 5303 and 5308, generates one fixed-minute aggregated data, and Pass to risk management system 3.
- FIG. 64 shows the fixed-part aggregated data generated by the fixed-part aggregated data management means 5305 and passed to the risk management system 3.
- variable aggregated data merging means 5 311 receives the variable aggregated data from the variable expanded data aggregation means 5 304 and 5309 and generates one fixed aggregated data. This is passed to the risk management system 3.
- FIG. 65 shows an example of a variation aggregated data generated by the variation aggregate data merging means 5 3 11 and passed to the risk management system 3.
Description
Claims
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP02711339A EP1359525A4 (en) | 2001-02-09 | 2002-02-06 | DEVICE FOR INTEGRATION OF TRANSACTION DATA RELATING TO FINANCIAL TRANSACTIONS |
US14/071,133 US20140114821A1 (en) | 2001-02-09 | 2013-11-04 | Apparatus for consolidating financial transaction information |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2001034710A JP4701510B2 (ja) | 2001-02-09 | 2001-02-09 | 金融取引に関する取引情報を集約する装置、及びその方法 |
JP2001-034710 | 2001-02-09 |
Related Child Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/240,967 A-371-Of-International US20030163398A1 (en) | 2001-02-09 | 2002-02-06 | Device for integrating transaction information on finantial transaction |
US14/071,133 Continuation US20140114821A1 (en) | 2001-02-09 | 2013-11-04 | Apparatus for consolidating financial transaction information |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2002065365A1 true WO2002065365A1 (fr) | 2002-08-22 |
Family
ID=18898262
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2002/000976 WO2002065365A1 (fr) | 2001-02-09 | 2002-02-06 | Dispositif permettant l'integration de donnees de transaction relatives aux transactions financieres |
Country Status (5)
Country | Link |
---|---|
US (2) | US20030163398A1 (ja) |
EP (1) | EP1359525A4 (ja) |
JP (1) | JP4701510B2 (ja) |
CN (1) | CN1460219A (ja) |
WO (1) | WO2002065365A1 (ja) |
Families Citing this family (34)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP4701510B2 (ja) * | 2001-02-09 | 2011-06-15 | ソニー株式会社 | 金融取引に関する取引情報を集約する装置、及びその方法 |
US8209246B2 (en) | 2001-03-20 | 2012-06-26 | Goldman, Sachs & Co. | Proprietary risk management clearinghouse |
US8069105B2 (en) * | 2001-03-20 | 2011-11-29 | Goldman Sachs & Co. | Hedge fund risk management |
US8121937B2 (en) | 2001-03-20 | 2012-02-21 | Goldman Sachs & Co. | Gaming industry risk management clearinghouse |
US8140415B2 (en) * | 2001-03-20 | 2012-03-20 | Goldman Sachs & Co. | Automated global risk management |
US9412123B2 (en) | 2003-07-01 | 2016-08-09 | The 41St Parameter, Inc. | Keystroke analysis |
US10999298B2 (en) | 2004-03-02 | 2021-05-04 | The 41St Parameter, Inc. | Method and system for identifying users and detecting fraud by use of the internet |
US8442953B2 (en) | 2004-07-02 | 2013-05-14 | Goldman, Sachs & Co. | Method, system, apparatus, program code and means for determining a redundancy of information |
US8510300B2 (en) | 2004-07-02 | 2013-08-13 | Goldman, Sachs & Co. | Systems and methods for managing information associated with legal, compliance and regulatory risk |
US8762191B2 (en) | 2004-07-02 | 2014-06-24 | Goldman, Sachs & Co. | Systems, methods, apparatus, and schema for storing, managing and retrieving information |
US8996481B2 (en) | 2004-07-02 | 2015-03-31 | Goldman, Sach & Co. | Method, system, apparatus, program code and means for identifying and extracting information |
US10127130B2 (en) | 2005-03-18 | 2018-11-13 | Salesforce.Com | Identifying contributors that explain differences between a data set and a subset of the data set |
US7720822B1 (en) * | 2005-03-18 | 2010-05-18 | Beyondcore, Inc. | Quality management in a data-processing environment |
US8782087B2 (en) | 2005-03-18 | 2014-07-15 | Beyondcore, Inc. | Analyzing large data sets to find deviation patterns |
US7630924B1 (en) * | 2005-04-20 | 2009-12-08 | Authorize.Net Llc | Transaction velocity counting for fraud detection |
US11301585B2 (en) | 2005-12-16 | 2022-04-12 | The 41St Parameter, Inc. | Methods and apparatus for securely displaying digital images |
US8938671B2 (en) | 2005-12-16 | 2015-01-20 | The 41St Parameter, Inc. | Methods and apparatus for securely displaying digital images |
US8151327B2 (en) | 2006-03-31 | 2012-04-03 | The 41St Parameter, Inc. | Systems and methods for detection of session tampering and fraud prevention |
US8210425B2 (en) | 2008-04-25 | 2012-07-03 | Netsuite, Inc. | Multiple rate currency consolidator |
US9112850B1 (en) | 2009-03-25 | 2015-08-18 | The 41St Parameter, Inc. | Systems and methods of sharing information through a tag-based consortium |
US8706615B2 (en) * | 2009-12-04 | 2014-04-22 | Robert A. Merkle | Systems and methods for evaluating the ability of borrowers to repay loans |
US10754913B2 (en) | 2011-11-15 | 2020-08-25 | Tapad, Inc. | System and method for analyzing user device information |
US10796232B2 (en) | 2011-12-04 | 2020-10-06 | Salesforce.Com, Inc. | Explaining differences between predicted outcomes and actual outcomes of a process |
US10802687B2 (en) | 2011-12-04 | 2020-10-13 | Salesforce.Com, Inc. | Displaying differences between different data sets of a process |
US9633201B1 (en) | 2012-03-01 | 2017-04-25 | The 41St Parameter, Inc. | Methods and systems for fraud containment |
US9521551B2 (en) | 2012-03-22 | 2016-12-13 | The 41St Parameter, Inc. | Methods and systems for persistent cross-application mobile device identification |
WO2014019051A1 (en) * | 2012-07-31 | 2014-02-06 | Ftse Tmx Global Debt Capital Markets Inc. | Server and method for processing data records |
EP2880619A1 (en) | 2012-08-02 | 2015-06-10 | The 41st Parameter, Inc. | Systems and methods for accessing records via derivative locators |
WO2014078569A1 (en) | 2012-11-14 | 2014-05-22 | The 41St Parameter, Inc. | Systems and methods of global identification |
US10902327B1 (en) | 2013-08-30 | 2021-01-26 | The 41St Parameter, Inc. | System and method for device identification and uniqueness |
US10091312B1 (en) | 2014-10-14 | 2018-10-02 | The 41St Parameter, Inc. | Data structures for intelligently resolving deterministic and probabilistic device identifiers to device profiles and/or groups |
JP6875200B2 (ja) * | 2017-06-02 | 2021-05-19 | 株式会社Quick | リスク評価システム、リスク評価方法及びリスク評価プログラム |
JP7269022B2 (ja) * | 2019-02-04 | 2023-05-08 | 株式会社オービック | 利息計算装置、利息計算方法および利息計算プログラム |
US11403210B1 (en) * | 2019-07-26 | 2022-08-02 | G4S Retail Solutions (USA) Inc. | Virtual simulation environment for testing functionality of physical cash handling devices |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JPH05225222A (ja) * | 1992-02-10 | 1993-09-03 | Hitachi Ltd | 資金シフトシミュレーションシステム |
JPH1186089A (ja) * | 1997-09-03 | 1999-03-30 | Fujitsu Ltd | 在高管理システム |
JPH11175602A (ja) * | 1997-12-12 | 1999-07-02 | Fujitsu Ltd | 信用リスク計測装置 |
JPH11296610A (ja) * | 1998-04-10 | 1999-10-29 | Bank Of Tokyo Mitsubishi Ltd | 資金管理システム |
Family Cites Families (30)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
GB1351937A (en) * | 1970-06-04 | 1974-05-15 | De La Rue Instr | Cash dispensing apparatus |
US4752877A (en) * | 1984-03-08 | 1988-06-21 | College Savings Bank | Method and apparatus for funding a future liability of uncertain cost |
US4742457A (en) * | 1985-08-27 | 1988-05-03 | Trans Texas Holdings Corporation | System and method of investment management including means to adjust deposit and loan accounts for inflation |
US5812988A (en) * | 1993-12-06 | 1998-09-22 | Investments Analytic, Inc. | Method and system for jointly estimating cash flows, simulated returns, risk measures and present values for a plurality of assets |
US5890140A (en) * | 1995-02-22 | 1999-03-30 | Citibank, N.A. | System for communicating with an electronic delivery system that integrates global financial services |
WO1996030852A1 (en) * | 1995-03-30 | 1996-10-03 | Hogan Systems, Inc. | Method of and system for financial institution budgeting and planning |
US7243081B2 (en) * | 1995-10-30 | 2007-07-10 | Efi Actuaries | Method of determining optimal asset allocation utilizing asset cash flow simulation |
US5963922A (en) * | 1996-02-29 | 1999-10-05 | Helmering; Paul F. | System for graphically mapping related elements of a plurality of transactions |
US5897621A (en) * | 1996-06-14 | 1999-04-27 | Cybercash, Inc. | System and method for multi-currency transactions |
US5878405A (en) * | 1996-09-25 | 1999-03-02 | Coordinated Data Services, Inc. | Pension planning and liquidity management system |
US6009402A (en) * | 1997-07-28 | 1999-12-28 | Whitworth; Brian L. | System and method for predicting, comparing and presenting the cost of self insurance versus insurance and for creating bond financing when advantageous |
US5978780A (en) * | 1997-11-21 | 1999-11-02 | Craig Michael Watson | Integrated bill consolidation, payment aggregation, and settlement system |
US6122623A (en) * | 1998-07-02 | 2000-09-19 | Financial Engineering Associates, Inc. | Watershed method for controlling cashflow mapping in value at risk determination |
JP4240588B2 (ja) * | 1998-07-07 | 2009-03-18 | 株式会社日立製作所 | リスク算出方法および装置ならびにリスク算出プログラムを格納した記憶媒体 |
US6513019B2 (en) * | 1999-02-16 | 2003-01-28 | Financial Technologies International, Inc. | Financial consolidation and communication platform |
US7117172B1 (en) * | 1999-03-11 | 2006-10-03 | Corecard Software, Inc. | Methods and systems for managing financial accounts |
US20010056391A1 (en) * | 2000-01-14 | 2001-12-27 | Schultz Frederick J. | Method and apparatus for managing and optimizing stock options |
US20060020530A1 (en) * | 2000-02-14 | 2006-01-26 | Hsu Phillip K | Systems for providing financial services |
US7006992B1 (en) * | 2000-04-06 | 2006-02-28 | Union State Bank | Risk assessment and management system |
GB2379064A (en) * | 2000-04-14 | 2003-02-26 | Vantage Internat Inc E | Method and system for delivering foreign exchange risk management advisory solutions to a designated market |
US7349875B1 (en) * | 2000-06-29 | 2008-03-25 | Ncr Corp. | Basic and intermediate net interest revenue implementations for financial processing in a relational database management system |
US7146337B1 (en) * | 2000-09-13 | 2006-12-05 | Precept Corporation | System and method for originating loans |
US20020184141A1 (en) * | 2000-10-26 | 2002-12-05 | Jeremy Stein | System and method for estimating cash flow at risk for a non-financial institution |
US20020123949A1 (en) * | 2000-12-15 | 2002-09-05 | Vanleeuwen Michael J. | System and method for financial management and analysis |
US20110131079A1 (en) * | 2000-12-20 | 2011-06-02 | Suzanne Valentine | System and Method for Modeling by Customer Segments |
US20030018548A1 (en) * | 2001-02-07 | 2003-01-23 | Danilo Cattaneo | System for economic-financial planning |
JP4701510B2 (ja) * | 2001-02-09 | 2011-06-15 | ソニー株式会社 | 金融取引に関する取引情報を集約する装置、及びその方法 |
US7398236B2 (en) * | 2001-04-30 | 2008-07-08 | Max Jaffe | Method and medium for budgeting |
US7555451B2 (en) * | 2001-05-17 | 2009-06-30 | Microsoft Corporation | Cash flow forecasting |
US8260699B2 (en) * | 2001-05-30 | 2012-09-04 | Finicity Corp. | Method and system for managing spending through account allocation |
-
2001
- 2001-02-09 JP JP2001034710A patent/JP4701510B2/ja not_active Expired - Lifetime
-
2002
- 2002-02-06 EP EP02711339A patent/EP1359525A4/en not_active Withdrawn
- 2002-02-06 US US10/240,967 patent/US20030163398A1/en not_active Abandoned
- 2002-02-06 CN CN02800782A patent/CN1460219A/zh active Pending
- 2002-02-06 WO PCT/JP2002/000976 patent/WO2002065365A1/ja not_active Application Discontinuation
-
2013
- 2013-11-04 US US14/071,133 patent/US20140114821A1/en not_active Abandoned
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JPH05225222A (ja) * | 1992-02-10 | 1993-09-03 | Hitachi Ltd | 資金シフトシミュレーションシステム |
JPH1186089A (ja) * | 1997-09-03 | 1999-03-30 | Fujitsu Ltd | 在高管理システム |
JPH11175602A (ja) * | 1997-12-12 | 1999-07-02 | Fujitsu Ltd | 信用リスク計測装置 |
JPH11296610A (ja) * | 1998-04-10 | 1999-10-29 | Bank Of Tokyo Mitsubishi Ltd | 資金管理システム |
Non-Patent Citations (3)
Title |
---|
"Facom unios kyotsu capsel III system kaisetsusho zaimu kaikei system", 31 January 1985, FUJITSU LTD., XP002909324 * |
See also references of EP1359525A4 * |
ZAIKEI SHOHOSHA K.K.: "Kin'yu joho system hakusho (heisei 13 nenban)", THE CENTER FOR FINANCIAL INDUSTRY INFORMATION SYSTEMS, 1 December 2000 (2000-12-01), pages 526, XP002909323 * |
Also Published As
Publication number | Publication date |
---|---|
EP1359525A4 (en) | 2006-05-31 |
US20140114821A1 (en) | 2014-04-24 |
EP1359525A1 (en) | 2003-11-05 |
CN1460219A (zh) | 2003-12-03 |
JP4701510B2 (ja) | 2011-06-15 |
US20030163398A1 (en) | 2003-08-28 |
JP2002236800A (ja) | 2002-08-23 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
JP4701510B2 (ja) | 金融取引に関する取引情報を集約する装置、及びその方法 | |
US6216115B1 (en) | Method for multi-directional consumer purchasing, selling, and transaction management | |
US8170936B2 (en) | Method and system for emulating a private label over an open network | |
US8065187B2 (en) | System, program product, and associated methods to autodraw for micro-credit attached to a prepaid card | |
US8341021B2 (en) | System, program product, and method for debit card and checking account autodraw | |
US8131619B1 (en) | Service fee-based payment processing | |
US7379912B1 (en) | System and method for processing loan information | |
US20070185810A1 (en) | System, method, and computer program product for saving and investing through use of transaction cards | |
CN101595506A (zh) | 限制多方交易中的对方风险 | |
WO2009021045A1 (en) | System and method for repaying an obligation | |
US20200219189A1 (en) | JYB-based Barter Transaction Platform | |
WO2019018713A1 (en) | LOAN SYSTEMS AND METHODS BETWEEN INDIVIDUALS BASED ON DISTRIBUTED REGISTER | |
Khiaonarong et al. | Instant Payments: Regulatory Innovation and Payment Substitution Across Countries | |
Herbst-Murphy | Clearing and settlement of interbank card transactions: A mastercard tutorial for federal reserve payments analysts | |
JP2000268119A (ja) | 債権消込処理システム及び債権消込処理方法 | |
JP2002175395A (ja) | 経理処理システム、経理処理方法及びこれを実行するためのプログラムを記録した媒体 | |
US20140006192A1 (en) | Selective escrow of funds based on transaction receipts | |
JPH08255203A (ja) | 資金繰予定シミュレーションシステム | |
AU2016100977A4 (en) | Method and system for automated collection and rebate of a gst taxation | |
TWI343548B (en) | Method and apparatus for automatically transferring interest into investment by use of debit service client | |
JP2004038614A (ja) | 入出金代行処理方法、コンピュータ・プログラム及び記録媒体 | |
Kadam | STUDY OF FINANCIAL OF SERVICES PROVIDED BY COMMERCIAL BANKS | |
JP2006039649A (ja) | 投資信託販売システムおよびコンピュータプログラム | |
CN117011076A (zh) | 一种智能记账系统 | |
CN117057909A (zh) | 分销商应收账款质押下的银行融资定价决策系统及方法 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AK | Designated states |
Kind code of ref document: A1 Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EC EE ES FI GB GD GE GH GM HR HU ID IL IN IS KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NO NZ OM PH PL PT RO RU SD SE SG SI SK SL TJ TM TN TR TT TZ UA UG US UZ VN YU ZA ZM ZW |
|
AL | Designated countries for regional patents |
Kind code of ref document: A1 Designated state(s): GH GM KE LS MW MZ SD SL SZ TZ UG ZM ZW AM AZ BY KG KZ MD RU TJ TM AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2002711339 Country of ref document: EP |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application | ||
WWE | Wipo information: entry into national phase |
Ref document number: 028007824 Country of ref document: CN |
|
WWE | Wipo information: entry into national phase |
Ref document number: 10240967 Country of ref document: US |
|
WWP | Wipo information: published in national office |
Ref document number: 2002711339 Country of ref document: EP |
|
REG | Reference to national code |
Ref country code: DE Ref legal event code: 8642 |
|
WWW | Wipo information: withdrawn in national office |
Ref document number: 2002711339 Country of ref document: EP |