JP2008077607A - Business support system, control method thereof, and program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a bisiness support system for reducing troublesome operation when changing loan relating to a commitment line contract into term loan contract. <P>SOLUTION: A computer 202 executes the following steps: a step for receiving an input of a deal number for identifying a specific loan, a step for extracting contract information corresponding to the received deal number from a contract table 601, a step for receiving a contract change instruction from a user relating to the extracted contract information, a step for receiving the input of contract change date according to the received contract change instruction, a step for extracting a loan date of the loan corresponding to the received deal number, and a step for changing the commitment line contract to the term loan contract based on a result of comparing the loan data with the contract change date. <P>COPYRIGHT: (C)2008,JPO&INPIT

Description

  The present invention relates to a business support apparatus, a control method thereof, and a program, and more particularly, to a business support apparatus, a control method thereof, and a program capable of reducing a work load accompanying a contract change in a syndicated loan.

  In recent years, syndicated loans have become widespread as a new form of financing. FIG. 22 shows a conceptual diagram of a syndicated loan.

  In FIG. 22, a syndicated loan refers to a funding needs of the borrower 101, in which a plurality of participating investors 105, such as financial institutions, form a co-financing group (syndicated) 104, and lending with the same pledge. It is a form of financing that provides credit. Participating investors 105 are generally called participating banks, lenders, or part-in. In this form of financing, first, the arranger 102 is in charge of creating a financing project (conclusion of a contract).

  The participating investor 105 participates in the syndicate 104 and executes financing, and the agent 103 that manages the syndication between the syndicate 104 and the borrower 101 manages fund collection. Here, for the agent 103 and the participating investor 105, in order to prevent accidents, the management of the due date of bills and the management of special provisions (covenants) are important tasks for a long period from the execution of loans to the collection of funds. Is required to manage contract information accurately.

  However, even when systematized to accurately manage the contract information, the contract renewal and the contract condition change work associated therewith are particularly troublesome for the input operator and the like. In addition, since the billing amount, due date, and the like may be changed in complex with changes in the contract, complicated input operations must be performed in order to manage them correctly. For this reason, a contract information management system has been proposed that aims to reduce various types of change work of users accompanying changes in contract contents and to automate the billing summation process (see, for example, Patent Document 1).

In addition, in syndicated loans, there is a loan form called a commitment line contract that allows a borrower to borrow within a certain range by setting a certain lending limit frame between participating investors and the borrower in advance. . The borrower can obtain a loan at any time within the period set in the commitment line contract and within the loan limit.
JP 2001-195472 A

  However, the above-mentioned prior art can cope with a simple change in billing amount, but it cannot deal with a change in consideration of necessary interest and payment conditions, and is the most important special contract in agent and part-in management. The provisions may not be fully managed.

  The present invention has been made in view of the above problems, and a first object of the invention is to alleviate complicated work when changing a loan related to a commitment line contract to a term loan contract.

  A second object of the present invention is to make it possible to determine whether or not two selected loans can be settled when creating a difference settlement form, and to automatically calculate the difference settlement. .

  In order to achieve the above object, the business support apparatus according to claim 1 includes an identification information receiving unit that receives an input of identification information for identifying a specific loan among a plurality of funds lending, and the received identification information. Contract information extraction means for extracting contract information corresponding to the contract information, contract change instruction reception means for receiving a contract change instruction for the extracted contract information, and input of a contract change date according to the received contract change instruction. A received contract modification date receiving means, a loan due date extracting means for extracting a loan due date corresponding to the received identification information, a comparison means for comparing the received contract modification date with the extracted loan due date; And a control means for changing a contract according to the comparison result.

  In order to achieve the above object, the business support device according to claim 6 includes an identification information receiving means for receiving an input of identification information for identifying a specific loan among a plurality of funds lending, and the received identification information. A lending list extracting means for extracting a lending list corresponding to the above, a determining means for determining whether or not two loans selected by the user among the extracted lending lists can be settled in difference, and according to the determination result And a control means for performing a difference settlement between the two selected loans.

  In order to achieve the above object, the business support device according to claim 7 includes an identification information receiving unit that receives an input of identification information for identifying a specific loan among a plurality of funds lending, and the received identification information. Covenants management information extracting means for extracting covenants management information corresponding to the above, covenants management information management means for deleting or changing covenants management information selected by the user from the extracted covenants management information, and selecting by the user And covenants management information registration means for registering covenants management information including the new contents.

  In order to achieve the above object, a method for controlling a business support apparatus according to claim 8 includes an identification information receiving step for receiving an input of identification information for identifying a specific loan among a plurality of funds loan, and the reception A contract information extraction step for extracting contract information corresponding to the identified identification information, a contract change instruction reception step for receiving a contract change instruction for the extracted contract information, and a contract change date according to the received contract change instruction The contract modification date reception step for receiving the input, the loan date extraction step for extracting the loan due date corresponding to the received identification information, and the comparison for comparing the received contract modification date with the extracted loan date And a control step of changing a contract according to the comparison result.

  In order to achieve the above object, a method for controlling a business support apparatus according to claim 13 includes an identification information receiving step for receiving an input of identification information for identifying a specific loan among a plurality of funds loan, and the reception A lending list extracting step for extracting a lending list corresponding to the identification information, a determining step for determining whether or not two loans selected by the user among the extracted lending lists can be settled by the difference, and the determination And a control step of performing difference settlement of the two selected loans according to the result.

  In order to achieve the above object, a method for controlling a business support apparatus according to claim 14 includes an identification information receiving step for receiving an input of identification information for identifying a specific loan among a plurality of funds loans, and the reception A covenant management information extracting step for extracting covenant management information corresponding to the identification information; a covenant management information managing step for deleting or changing the covenant management information selected by the user from the extracted covenant management information; and A covenant management information registration step of registering covenant management information including new contents selected by the user.

  According to the present invention, input of identification information for identifying a specific loan out of a plurality of funds is received, and contract information corresponding to the received identification information is extracted. Then, a contract change instruction is accepted for the extracted contract information, and an input of the contract change date is accepted according to the accepted contract change instruction. Then, the lending date of the lending corresponding to the received identification information is extracted, the lending date is compared with the contract change date, and the contract is changed according to the comparison result. Thereby, for example, it is possible to reduce troublesome work when changing a loan related to a commitment line contract to a term loan contract.

  In addition, according to the present invention, the contract change date is compared with the extracted loan date, and if it is determined that there is at least one loan whose loan date is after the contract change date, the contract change date I do. Thereby, at the time of contract change, only the loan which can change a contract can be changed selectively.

  According to the present invention, an input of identification information for identifying a specific loan among a plurality of fund loans is accepted, and a loan list corresponding to the received identification information is extracted. Then, it is determined whether or not the two loans selected by the user in the extracted loan list can be settled, and the settlement of the difference between the two selected loans is performed according to the determination result. Thus, when creating the difference settlement form, it is possible to determine whether or not the two selected loans can be settled, and the difference settlement can be automatically calculated.

  According to the present invention, input of identification information for identifying a specific loan among a plurality of fund loans is received, and covenant management information corresponding to the received identification information is extracted. Then, the covenant management information selected by the user among the extracted covenant management information is deleted or changed. Also, covenant management information including new contents selected by the user is registered. As a result, work related to covenants management can be reduced.

  Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings.

[First Embodiment]
FIG. 1 is a block diagram illustrating a configuration example of a system including a business support apparatus according to the first embodiment of the present invention.

  In FIG. 1, a system 201 is a business support system used by the participating investor 105 in FIG. A computer 202 is a business support apparatus that is communicably connected to an MFP (Multi Function Printer) 202 via a network 203. The computer 202 and the MFP 203 are not limited to the illustrated example, and a plurality of computers may be installed.

  The MFP 202 is a digital multifunction machine having a printing function, a FAX function, a scanning function, and the like. Upon receiving a print instruction from the computer 202 via the network 203, the MFP 203 can print the instructed print data. In addition, various forms can be printed.

  The system 201 may be a business support system used by the agent 103 in FIG. In this case, the MFP 202 used by the agent 103 can digitize various forms using the scan function and transmit the digitized form data to the MFP of the participating investor 105. When the MFP of the participating investor 105 receives the form data or the like, it can print the form data or the like using the print function.

  Similarly, the form data and the like digitized using the FAX function or the like can be transmitted from the MFP of the participating investor 105 to the MFP of the agent 103.

  FIG. 2 is a block diagram showing a configuration of the computer 202 of FIG.

  In FIG. 2, the CPU 301 controls each device connected to the system bus 304 based on a program stored in the ROM 302 or the external memory 311, and controls the entire computer 202. A RAM 303 functions as a main memory, work area, and the like for the CPU 301.

  The input controller 305 controls input from a pointing device such as a keyboard 309 or a mouse. The video controller 306 controls display on the CRT monitor 310. The CRT monitor 310 is configured by a CRT (Cathode Ray Tube), an LCD (Liquid Crystal Display), or the like, but may be a display device of another form.

  The memory controller 307 controls access to the external memory 311. A communication interface (I / F) controller 308 controls communication with the MFP 203 and other devices connected via the network 204.

  The external memory 311 includes a recording medium such as a hard disk (HD) or a flexible disk (FD). The external memory 311 is configured with a database that stores various tables to be described later. Some or all of the information stored in the database stored in the external memory 311 may be stored in the RAM 303.

  Next, contract change processing for changing “contract information”, “loan” and the like when changing from a commitment line contract to a term loan contract in the system 201 of FIG. 1 will be described with reference to FIGS.

  FIG. 3 is a flowchart showing contract change processing executed by the computer 202 of FIG. This process is a process executed by the CPU 301 based on a program stored in the ROM 302 or the external memory 311.

  In FIG. 3, when the program is activated, the CPU 301 displays the main menu screen 401 shown in FIG. 4 on the CRT monitor 310 via the video controller 306 (step S401). On the main menu screen 401, various function buttons such as a contract button 402, an interest cash flow button 403, a master registration button 404, and a form creation button 405, which will be described later, are arranged.

  Next, when the CPU 301 detects that the user presses the contract button 402 (step S402: YES), the CPU 301 switches from the main menu screen 401 to the contract information screen 701 shown in FIG. S403). On the contract information screen 701, a handling number input field 702, an inquiry button 703, a contract change button 704, a contract category input field 705, a confirmation button 706, a covenant management 707, and the like are arranged.

  Next, when the CPU 301 detects that the handling number is entered in the handling number input field 702 by the user and the inquiry button 703 is pressed, the contract information corresponding to the handling number is extracted from the database (step S404). At this time, the input handling number is stored in the RAM 303. Assume that the database is stored in the external memory 311 or the RAM 303.

  The processing in step S404 will be specifically described. The CPU 301 extracts contract information corresponding to the input handling number from the contract table 601 shown in FIG. For example, when the user inputs “101” as the handling number and presses the inquiry button 703, the CPU 301 stores data for each item corresponding to the handling number 101 in the contract table 601 (contract number: “100”, contract category: “ Commitment line ”, lending frame:“ ¥ 30,000,000 ”, contract start date:“ 2006.01.01 ”, etc.) are extracted as contract information. The contract number is a number assigned when a syndicated loan is contracted, and is a single number even if there are a plurality of loans. The commitment line contract is a loan form in which the loan amount can be financed at any time within the contracted loan period.

  Next, the CPU 301 displays the contents of the extracted contract information on the contract information screen 701 (step S405).

  Next, when the CPU 301 detects that the contract change button 704 has been pressed and determines that there is a contract change instruction (step S406: YES), the contract change date input screen 901 shown in FIG. It is displayed (step S407). The contract change date input screen 901 is displayed as a pop-up screen, for example. On the contract change date input screen 901, a contract change date input field 902 and an OK button 903 are arranged.

Next, when the CPU 301 detects that the contract change date is input in the contract change date input field 902 and the OK button 903 is pressed (step S408: YES), the CPU 301 corresponds to the handling number stored in the RAM 303. All lending dates (final deadlines) are extracted from the lending table 801 shown in FIG. 8 (step S409). Here, the lending date is a collection date when the lending balance (lending amount) becomes “0 (zero)”.
Further, the CPU 301 stores the input contract change date in the RAM 303.

  The processing of step S409 will be described with reference to FIG. 8. For example, when the input handling number is 101, the CPU 301 sets “2008.06.30” and “2008.07” as the lending date (final date). .31 "is extracted.

  Next, the CPU 301 compares all the loan due dates (final due dates) extracted in step S409 with the contract modification date input by the user (step S410). Here, the relationship between the contract change date and the lending date is compared. When there are multiple loan dates, a comparison is made for each loan date.

  Next, when the CPU 301 determines that there is at least one loan whose loan date is later (late) than the contract change date (step S411: YES), the CPU 301 changes (integrates) the commitment line contract to the term loan contract. Is performed (step S412), and this process is terminated. Thereby, at the time of contract change, only the loan which can change a contract can be changed selectively.

  On the other hand, if the CPU 301 determines that there is no (late) loan after the contract change date (step S411: NO), the CPU 301 displays an error message (not shown) indicating that the contract cannot be changed. 310 is displayed (step S413), and this process ends.

  With the above processing, it is possible to easily determine whether or not the commitment line contract can be changed to the term loan contract, and it is possible to reduce troublesome work when the contract is changed.

  Next, detailed processing in step S412 in FIG. 3 will be described.

  FIG. 9 is a flowchart showing details of step S412 in FIG.

  In FIG. 9, the CPU 301 assigns a new handling number in accordance with the contract change (step S501). Here, the CPU 301 generates a unique handling number.

  Next, the CPU 301 inputs the handling number assigned in step S501 in the handling number input field 702 on the contract information screen 701 displayed on the CRT monitor 310. Also, a term loan is input in the contract category input field 705 to display the contract information screen 701 (step S502). The contract category input field 705 is a drop-down list, and a term loan may be selected from the displayed list.

  Next, when detecting that the confirmation button 706 is pressed by the user (step S503: YES), the CPU 301 stores the contract information displayed on the contract information screen 701 as a new record in the contract table 601 of FIG. . As a result, a new record is generated in the contract table 601 in which the handling number assigned in step S501 is “102” and the contract classification is “term loan”. Note that a process of selecting one or a plurality of loans from one or a plurality of loans of the commitment line contract may be added between step S502 and step S503. As a result, it is possible to change one or more loans selected from one or more loans in the commitment line contract as a new loan in the term loan contract.

  Next, the CPU 301 stores the handling number assigned in step S501 and the date guide date (not shown) stored in the external memory 311 or the like in the date management table 1001 shown in FIG. 10 (step S505). The date guidance date is a specified value stored in advance in the external memory 311 or the like.

  Next, the CPU 301 duplicates the “participating row number” and the “lending frame” corresponding to the handling number input by the user from the participating row-specific contract table 1101 shown in FIG. 11, and the handling numbered in step S501. It is associated with the number and stored as a new record in the contract table 1101 for each participating row (step S506). Participating row-specific contract table 1101 stores information indicating the lending frame for each participating investor (hereinafter also referred to as “participating row”).

  Next, the CPU 301 adds together the loan amounts having the same handling number in the loan table 801 shown in FIG. 8 (step S507). Then, the CPU 301 generates a new record in the lending table 801, and stores the handling number assigned in step S501 and the lending amount calculated (summed) in step S507 (step S508).

  Next, the lending information is extracted from the lending table 801, the lending information screen 1201 shown in FIG. 12 is displayed on the CRT monitor 310 (step S509), and the process returns.

  In this specification, “loan” is used in the same meaning as “loan”, and either term may be used. That is, “lending” and “lending” are expressed as “lending” or “lending”.

  Next, cash flow (CF) change processing associated with the contract change described above will be described with reference to FIGS. As for the cash flow changing process, there are “principal cash flow” and “interest cash flow”. Since the same process is performed in any case, “interest cash flow” will be described.

  FIG. 13 is a flowchart showing a cash flow change process executed by the computer 202 of FIG. This process is a process executed by the CPU 301 based on a program stored in the ROM 302 or the external memory 311.

  In FIG. 13, when the program is started, the CPU 301 displays the main menu screen 401 of FIG. 4 on the CRT monitor 310 (step S1301).

  When the CPU 301 detects that the interest cash flow button 403 has been pressed (step S1302: YES), the CPU 301 displays the interest cash flow screen 1401 shown in FIG. 14 on the CRT monitor 310 (step S1303). When the principal cash flow button is pressed on the main menu screen 401, the principal cash flow screen 1501 shown in FIG. 15 is displayed.

  Next, when the CPU 301 detects that the handling number has been input by the user in the handling number input field 1402 on the interest cash flow screen 1401 and the inquiry button 1403 has been pressed, the loan execution date specified by the handling number or Lending information such as the lending date (final deadline) and the lending amount is extracted from the lending table 801 (step S1304).

  Next, the CPU 301 displays the contents of the loan information extracted in step S1304 on the interest cash flow screen 1401 (step S1305).

  Next, when the user inputs information necessary for calculating the cash flow such as the repayment date and the repayment amount and the generation button 1404 is pressed, the CPU 301 detects that the generation button 1404 is pressed ( Step S1306: YES). Then, the CPU 301 calculates and generates a cash flow based on the loan information extracted in step S1304 and information such as the payment date input by the user (step S1307).

  Next, when the CPU 301 detects that the save button 1405 is pressed by the user (step S1308: YES), the cash flow table 1601 and the lending table 801 shown in FIG. (Step S1309), and the process is terminated. With this process, for example, the user can easily change the cash flow that occurs when the contract is changed from a commitment line contract to a term loan, and the complicated work can be reduced.

  The cash flow table 1601 illustrated in FIG. 16 includes a handling number, an interest payment date, a principal amount, an interest rate (base rate), a calculation start date, and a calculation end date. For example, the interest amount is calculated by the following formula.

Interest amount = principal amount x interest rate x (calculation end date-calculation start date) / 365
According to the first embodiment, the computer 202 accepts input of a handling number from the user, and extracts contract information corresponding to the accepted handling number from the contract table 601. Then, a contract change instruction is received from the user for the extracted contract information, and an input of the contract change date is accepted on the contract change date input screen 901 in accordance with the contract change instruction. Then, all the lending dates corresponding to the accepted handling numbers are extracted from the lending table 801, and all the lending dates are compared with the entered contract modification date. Then, a change process from a commitment line contract to a term loan contract is performed according to the comparison result. Thereby, the troublesome work at the time of changing the loan related to the commitment line contract to the term loan contract can be reduced.

[Second Embodiment]
The business support apparatus according to the second embodiment of the present invention has the same configuration (FIGS. 1 and 2) as that of the first embodiment, and the same parts as those of the first embodiment are the same. The description thereof will be omitted using the reference numeral. Only the differences from the first embodiment will be described below.

  FIGS. 17 and 18 are flowcharts showing the difference settlement form creation processing executed by the computer 202. This process is a process executed by the CPU 301 based on a program stored in the ROM 302 or the external memory 311.

  In FIG. 17, when the program is started, the CPU 301 displays the main menu screen 401 of FIG. 4 on the CRT monitor 310 (step S1401).

  Next, when detecting that the user has pressed the form creation button 405 (step S1402: YES), the CPU 301 causes the CRT monitor 310 to display a form creation screen 1901 shown in FIG.

  Next, when the CPU 301 detects that a handling number has been input by the user in the handling number input field 1902 on the form creation screen 1901 and the difference settlement has been selected from the drop-down list 1903 (step S1403: YES), FIG. The lending list corresponding to the handling number is extracted from the lending table 801 and the lending list 2002 is displayed on the interest cash flow screen 2001 shown in FIG. 20 (step S1404). Here, the lending list is information indicating the contents of lending, and in this embodiment, includes at least a lending execution date, a lending date, and a lending amount. The loan list 2002 displays an execution date (lending execution date), a due date (lending date), and a loan amount (lending amount).

  Next, when the CPU 301 detects that one loan record (hereinafter referred to as “loan A”) is selected by the user from the loan list 2002 displayed on the CRT monitor 310 (step S1405), the selected loan. The “contract category” of A is extracted from the contract table 601 using the input handling number as a key, and the contract category is acquired (step S1406).

  Next, the CPU 301 determines whether or not the contract classification acquired in step S1406 is a commitment line contract (step S1407). As a result of this determination, if the CPU 301 determines that it is a commitment contract (step S1408: YES), the process proceeds to step S1408 in FIG. On the other hand, if the CPU 301 determines in step S1408 that the contract is not a commitment line contract (step S1408: NO), an error screen indicating that the difference cannot be settled is displayed on the CRT monitor 310 (step S1409). After the CPU 301 displays an error screen in step S1409, the process proceeds to step S1405.

  In FIG. 18, in step S 1408, a list of loans for performing difference settlement with the loan selected by the user in step S 1405 is displayed.

  In step S1408, the CPU 301 extracts all loans except the loan selected in step S1405, which are the same as the loan handling number selected by the user in step S1405, from the loan table (FIG. 21). (Difference settlement) screen 2101 is displayed. On the loan list screen 2101, a difference loan button 2102 and the like are arranged.

  Next, the CPU 301 selects one loan record (hereinafter referred to as “loan B”) from the loan list screen 2101 displayed on the CRT monitor 310 in step S1408 and the difference loan button 2102 is pressed. (Step S1410: YES), the process proceeds to step S1411.

  Next, the CPU 301 extracts “loan execution date” and “loan date (final deadline)” in the loan A selected in step S1405 and the loan B selected in step S1411 from the loan table 801, and The process proceeds to step S1412.

  Next, the CPU 301 compares the loan execution date of the loan A acquired in step S1411 with the loan due date (final deadline) of the loan B (step S1412), and when it is determined to be the same day (step S1412: YES), the loan B is determined to be a loan (old loan) before loan A. Then, the CPU 301 calculates difference settlement using the loan B as the previous loan (step S1413), and proceeds to step S1417.

  On the other hand, as a result of the determination in step S1412, when it is determined that it is not the same day (step S1412: NO), the lending date (final time limit) of the loan A is compared with the loan execution date of the loan B (step S1414). As a result of the determination, when it is determined that the date is the same day (step S1414: YES), the CPU 301 determines that the loan A is a loan before the loan B. Then, the CPU 301 calculates the difference settlement with the loan A as the previous loan (old loan) (step S1415), and proceeds to step S1417.

  On the other hand, if the CPU 301 determines in step S1414 that the lending date (final deadline) of the loan A and the loan execution date of the loan B are not the same day (step S1414: NO), an error message indicating that the difference cannot be settled is CRT. The information is displayed on the monitor 310 (step S1416), and this process ends.

  In step S1417, the CPU 301 prints out the difference settlement calculation result calculated in step S1413 or step S1415 on a form, and ends this process.

  According to the above embodiment, the computer 202 accepts the input of the handling number, extracts the lending list corresponding to the accepted handling number from the lending table 801, and displays it. Then, it is determined whether or not the two loans selected by the user in the extracted loan list can be settled, and the settlement of the difference between the two selected loans is performed according to the determination result. In the commitment line contract described above, the work related to the creation of the difference settlement form is also a cumbersome work for the user. Therefore, when creating the difference settlement form, it is possible to determine whether or not the two selected loans can be settled. Difference settlement can be calculated automatically.

[Third Embodiment]
The business support apparatus according to the third embodiment of the present invention has the same configuration (FIGS. 1 and 2) as that of the first embodiment, and the same parts as those of the first embodiment are the same. The description thereof will be omitted using the reference numeral. Only the differences from the first embodiment will be described below. In addition, this embodiment not only reduces the cumbersome work when changing a loan related to a commitment line contract to a term loan contract, but it is also effective when the commitment line contract is changed and updated. Needless to say, both will be described here separately.

  FIG. 23 is a flowchart showing the covenant management process executed by the computer 202. This process is a process executed by the CPU 301 based on a program stored in the ROM 302 or the external memory 311.

  In FIG. 23, when the program is activated, the CPU 301 displays the main menu screen 401 of FIG. 4 on the CRT monitor 310 (step S1601).

  Next, when detecting that the user presses the contract button 402 (step S1602: YES), the CPU 301 displays the contract information screen 701 shown in FIG. 5 on the CRT monitor 310 (step S1603).

  Next, when detecting that the return button 708 on the contract information screen 701 has been pressed by the user (step S1604: YES), the CPU 301 returns to step SS1601 and displays the main menu screen 401 again.

  On the other hand, when the CPU 301 detects that the handling number is entered in the handling number input field 702 by the user and the covenant management button 707 is pressed (step S1605: YES), the CPU 301 proceeds to the processing of step S1606.

  In step S1606, the CPU 301 extracts all covenant management information corresponding to the handling number from the covenant management information table based on the inputted handling number. Here, the “covenant management information” is information identifying the covenant and information including the covenant. Specifically, the item “handling number” in the covenant management information table 2701 shown in FIG. Data stored for “restriction clause ID”, “serial number”, “restriction clause”, “confirmation item”, “remarks”, “confirmation month 1”,..., “Confirmation month 12”, respectively. . Here, covenants refer to special provisions (restrictions) described in the contents of the contract for financing.

  Next, all the covenant management information extracted in step S1606 is displayed on the CRT monitor 310 as a covenant management information registration screen 2401 shown in FIG. 24 (step S1607). For example, “restriction clause”, “confirmation item”, “confirmation month”, “remarks”, and the like are displayed in the display column 2402.

  Next, when it is detected on the covenants management information registration screen 2401 that the covenant item selection button 2405 is pressed by the user (step S1608: YES), the process proceeds to covenant registration processing (step S1611) described later.

  On the other hand, the CPU 301 selects one covenant management information from the covenant management information displayed on the covenant management information registration screen 2401 (step S1609: YES), and when the delete button 2406 is not pressed. (Step S1610: NO), the process proceeds to a covenant changing process (step S1613) described later. On the other hand, when it is detected that the delete button 2406 is pressed (step S1610: YES), the process proceeds to covenant deletion processing (step S1612).

  FIG. 25 is a flowchart showing details of the covenant registration process in step S1611 of FIG.

  In FIG. 25, the CPU 301 displays a covenant item selection screen 2601 shown in FIG. 26 on the CRT monitor 310 (step S1701). Next, the CPU 301 extracts all “restriction clauses” stored in the covenant item master table 2703 shown in FIG. 27C (step S1702), and displays the extracted restriction clauses on the covenant item selection screen 2601. A list is displayed in the field 2602 (step S1703). The covenant management table 2702 is shown in FIG.

  Next, the CPU 301 determines that one or more restriction items are selected by the user from the restriction clauses displayed in a list in step S1703 (step S1704: YES), and the OK button 2103 is pressed (step S1705). : YES), the selected restriction clause and data related to the restriction clause (restriction clause ID, serial number, confirmation item, remarks, etc.) are displayed on the covenants management information registration screen 2401 (step S1706), and the return To do. At this time, the displayed data is stored in the RAM 303. Here, the “restriction clause” is information that can be uniquely specified by the “restriction clause ID” and the “serial number”. That is, if the “handling number”, “restriction clause ID”, and “serial number” uniquely assigned to each loan are known, it is possible to uniquely identify what restriction clause in which loan. In the present embodiment, the “handling number”, “restriction clause ID”, and “serial number” are collectively referred to as “restriction clause identification information”.

  FIG. 28 is a flowchart showing details of the covenant changing process in step S1613 of FIG.

  28, when the CPU 301 detects that the covenant management information displayed on the covenant management information registration screen 2401 in FIG. 24 has been changed by an input device such as a mouse (not shown) or the keyboard 309, the CPU 301 has changed. Covenant management information is stored in the RAM 303. For example, when the confirmation month of the covenant management information displayed in the display field 2402 is changed to January, a check is input to the check box 2404 for January by the user. Upon detecting this, the CPU 301 stores the changed covenant management information (including at least the restriction clause specifying information and the changed data (in this case, the confirmation month)) in the RAM 303. Here, a process for adding or updating the covenant management information or the covenant management information stored in the RAM 303 by the covenant management process to the covenant management information table will be described.

  When the CPU 301 detects that the change button 2407 on the covenant management information registration screen 2401 has been pressed (step S1801: YES), the covenant management information stored in the RAM 303 is the covenant management information shown in FIG. A search is made as to whether or not the table 2901 already exists, and a determination process described later is executed (step S1802). Specifically, it is searched whether or not the restriction clause specifying information stored in the RAM 303 already exists in the covenant management information table 2901 shown in FIG. 29A, and a determination process described later is executed.

  Next, when the CPU 301 determines that the restriction clause specifying information stored in the RAM 303 is already stored in the covenant management information table 2901 (step S1802: YES), it is already stored in the covenant management information table 2901. The covenant management information being stored is replaced with the covenant management information stored in the RAM 303 and updated (step S1803), and the process proceeds to step S1804.

  On the other hand, when the CPU 301 determines that the restriction clause specifying information stored in the RAM 303 is not stored in the covenant management information table 2901 (step S1802: NO), a new record is additionally generated in the covenant management information table 2901. Then, the covenant management information stored in the RAM 303 is stored in the generated record (step S1807), and the process proceeds to step S1806.

  In step S1804, the CPU 301 searches the covenant management table 2902 shown in FIG. 29B for whether or not the restriction clause specifying information of the changed or updated covenant management information is stored, and determines that it has already been stored. If so (step S1804: YES), the process proceeds to step S1805. On the other hand, if it is determined that it is not stored (step S1804: NO), the process proceeds to step S1806.

  In step S1805, the CPU 301 first searches the covenant management table 2902 for “confirmation date” of “NULL” (empty data) and “confirmation date” whether there is data after the current date. If there is such data, it is deleted and the process proceeds to step S1806.

  In step S1806, the CPU 301 executes processing for newly adding changed or updated information to the covenant management table 2902, and then returns. In step S1806, for example, when the confirmation month is additionally set to January, the CPU 301 generates a new record in the covenant management table 2902 based on the restriction clause specifying information stored in the RAM 303 and the confirmation date. Then, the generated record is stored. The covenant item master table 2903 is shown in FIG.

  FIG. 30 is a flowchart showing details of the covenant deletion process in step S1612 of FIG.

  In FIG. 30, the CPU 301 retrieves the selected restriction clause specifying information (covenant data) (step S1901), and when it is determined that there is applicable data (step S1902: YES), FIG. The corresponding data (all applicable records) is deleted from the indicated covenants management information table 3101 (step S1904). As a result, the covenant management information table 3101 is updated to the covenant management information table 3102.

  Next, the CPU 301 deletes data (all applicable records) corresponding to the restriction clause specifying information from the covenants management table 3103 (step S1905), and returns. As a result, the covenant management table 3103 is updated to the covenant management table 3104. Further, the covenant item master table 3105 remains as shown in FIG.

  On the other hand, if the result of determination in step S1902 is that there is no corresponding data (step S1902: NO), an error message indicating that there is no data corresponding to the selected covenant is displayed (step S1903), and the process returns.

  According to the third embodiment, the computer 202 receives an input of a handling number, and extracts all covenant management information corresponding to the received handling number from the covenant management information table 2701. Then, the covenant management information selected by the user among the extracted covenant management information is deleted or changed. Also, covenant management information including new contents selected by the user is registered. As a result, work related to covenants management can be reduced.

  In the first to third embodiments, the embodiment has been described in which the computer 202 executes various processes as a single business support apparatus. However, the present invention may be applied to a client server system. For example, a case where the client side computer executes the above-described screen display processing, input processing, and the like, and main contract change processing, difference settlement form creation processing, and the like are executed on the host computer side.

  The object of the present invention is achieved by executing the following processing. That is, a storage medium that records a program code of software that realizes the functions of the above-described embodiments is supplied to a system or apparatus, and a computer (or CPU, MPU, etc.) of the system or apparatus is stored in the storage medium. This is the process of reading the code. In this case, the program code itself read from the storage medium realizes the functions of the above-described embodiments, and the program code and the storage medium storing the program code constitute the present invention.

  Moreover, the following can be used as a storage medium for supplying the program code. For example, floppy (registered trademark) disk, hard disk, magneto-optical disk, CD-ROM, CD-R, CD-RW, DVD-ROM, DVD-RAM, DVD-RW, DVD + RW, magnetic tape, nonvolatile memory card, ROM or the like. Alternatively, the program code may be downloaded via a network.

  Further, the present invention includes a case where the function of the above-described embodiment is realized by executing the program code read by the computer. In addition, an OS (operating system) running on the computer performs part or all of the actual processing based on an instruction of the program code, and the functions of the above-described embodiments are realized by the processing. Is also included.

  Furthermore, a case where the functions of the above-described embodiment are realized by the following processing is also included in the present invention. That is, the program code read from the storage medium is written in a memory provided in a function expansion board inserted into the computer or a function expansion unit connected to the computer. Thereafter, based on the instruction of the program code, the CPU or the like provided in the function expansion board or function expansion unit performs part or all of the actual processing.

  Further, the present invention includes a case where the functions of the above-described embodiments are realized by executing the program code read by the computer. In addition, there is a case where the OS running on the computer performs part or all of the actual processing based on the instruction of the program code, and the functions of the above-described embodiments are realized by the processing. In this case, the program is supplied by downloading directly from a storage medium storing the program or from another computer or database (not shown) connected to the Internet, a commercial network, a local area network, or the like.

It is a block diagram which shows the structural example of the system containing the work assistance apparatus which concerns on the 1st Embodiment of this invention. It is a block diagram which shows the structure of the computer of FIG. It is a flowchart which shows the contract change process performed with the computer of FIG. It is a figure which shows an example of a main menu screen. It is a figure which shows an example of a contract information screen. It is a figure which shows an example of a contract table. It is a figure which shows an example of a contract change date input screen. It is a figure which shows an example of a rental table. It is a flowchart which shows the detail of step S412 in FIG. It is a figure which shows an example of a date management table. It is a figure which shows an example of the contract table classified by participation line. It is a figure which shows an example of a loan information screen. It is a flowchart which shows the change process of the cash flow performed with the computer of FIG. It is a figure which shows an example of an interest cash flow screen. It is a figure which shows an example of a principal cash flow screen. It is a figure which shows an example of a cash flow table. It is a flowchart which shows the difference settlement form creation process (the 1) performed with a computer. It is a flowchart which shows the difference settlement form preparation process (the 2) performed with a computer. It is a figure which shows an example of a form creation screen. It is a figure which shows an example of the interest cash flow screen on which the loan list was displayed. It is a figure which shows an example of a loan list (difference settlement) screen. It is a conceptual diagram which shows the relationship in a syndicated loan. It is a flowchart which shows the covenants management process performed with a computer. It is a figure which shows an example of a covenants management information registration screen. It is a flowchart which shows the detail of the covenants registration process in step S1611 of FIG. It is a figure which shows an example of a covenant item selection screen. It is a figure which shows an example of the table information in a covenant registration process, (a) Covenant management information table, (b) Covenant management table, (c) shows a covenant item master table. It is a flowchart which shows the detail of the covenants change process in step S1613 of FIG. It is a figure which shows an example of the table information in a covenant change process, (a) Covenant management information table, (b) Covenant management table, (c) shows a covenant item master table. It is a flowchart which shows the detail of the covenant deletion process in step S1612 of FIG. It is a figure which shows an example of the table information in a covenant deletion process, (a) Covenant management information table, (b) Covenant management table, (c) shows a covenant item master table.

Explanation of symbols

202 Computer 301 CPU
310 CRT monitor 401 Main menu screen 601 Contract table 701 Contract information screen 801 Lending table 901 Contract change date input screen 1001 Due date management table 1101 Contract table by participating line

Claims (17)

Identification information receiving means for receiving input of identification information for identifying a specific loan among a plurality of funds loan;
Contract information extracting means for extracting contract information corresponding to the received identification information;
Contract change instruction accepting means for accepting a contract change instruction for the extracted contract information;
A contract change date receiving means for receiving an input of a contract change date according to the received contract change instruction;
Lending date extraction means for extracting a lending date of lending corresponding to the received identification information;
A comparison means for comparing the accepted contract modification date with the extracted lending date;
A business support apparatus comprising: control means for changing a contract according to the comparison result. The control means includes identification information generating means for generating new identification information in accordance with the contract change,
A loan amount extraction means for extracting a loan amount of the loan corresponding to the received identification information;
If there are a plurality of the extracted loan amounts, the loan amount calculation means comprising a sum of the loan amounts and a new loan amount,
The business support apparatus according to claim 1, wherein the generated identification information and the new loan amount are stored in association with each other.   The comparison unit compares the received contract modification date with the extracted loan date, and the control unit determines that there is at least one loan whose loan date is later than the contract modification date. 3. The business support apparatus according to claim 1, wherein the contract is changed when the contract is made.   The control means changes one or a plurality of loans selected by the user from one or a plurality of loans corresponding to the received identification information to a new one. The business support device according to any one of the above.   The business support apparatus according to claim 1, wherein the control unit changes a cash flow in accordance with the contract change. Identification information receiving means for receiving input of identification information for identifying a specific loan among a plurality of funds loan;
A lending list extracting means for extracting a lending list corresponding to the received identification information;
Judgment means for judging whether or not two loans selected by the user among the extracted lending lists can be settled by a difference amount;
A business support apparatus comprising: control means for performing a difference settlement between the two selected loans in accordance with the determination result. Identification information receiving means for receiving input of identification information for identifying a specific loan among a plurality of funds loan;
Covenant management information extracting means for extracting covenant management information corresponding to the received identification information;
Covenants management information management means for deleting or changing the covenants management information selected by the user from the extracted covenants management information;
A business support apparatus comprising covenant management information registering means for registering covenant management information including new contents selected by the user. An identification information receiving step for receiving input of identification information for identifying a specific loan among a plurality of funds loans;
A contract information extraction step for extracting contract information corresponding to the received identification information;
A contract change instruction receiving step for receiving a contract change instruction for the extracted contract information;
A contract change date reception step for receiving an input of a contract change date according to the received contract change instruction;
A lending date extracting step for extracting a lending date of lending corresponding to the received identification information;
A comparison step of comparing the accepted contract modification date with the extracted lending date;
And a control step of changing a contract according to the comparison result. The control step includes an identification information generation step for generating new identification information in accordance with the contract change,
A loan amount extraction step of extracting a loan amount of the loan corresponding to the received identification information;
A loan amount calculation step of adding a loan amount to a new loan amount when there are a plurality of the extracted loan amounts; and
9. The business support apparatus control method according to claim 8, wherein the generated identification information and the new loan amount are stored in association with each other.   The comparison step compares the order relationship between the received contract modification date and the extracted loan date, and the control step determines that there is at least one loan whose loan date is later than the contract modification date. 10. The business support apparatus control method according to claim 8, wherein the contract is changed when the contract is changed.   The control step changes one or a plurality of loans selected by the user from one or a plurality of loans corresponding to the received identification information to a new one. A method for controlling the business support apparatus according to any one of the above.   12. The business support apparatus control method according to claim 8, wherein the control step changes a cash flow in accordance with the contract change. An identification information receiving step for receiving input of identification information for identifying a specific loan among a plurality of funds loans;
A lending list extracting step of extracting a lending list corresponding to the received identification information;
A determination step of determining whether or not two loans selected by the user in the extracted loan list can be settled;
And a control step of performing a difference settlement of the two selected loans according to the determination result. An identification information receiving step for receiving input of identification information for identifying a specific loan among a plurality of funds loans;
A covenant management information extracting step for extracting covenant management information corresponding to the received identification information;
Of the extracted covenant management information, a covenant management information management step of deleting or changing the covenant management information selected by the user;
A covenant management information registration step of registering covenant management information including new contents selected by the user.   A computer-readable program for causing a computer to execute the control method according to any one of claims 8 to 12.   A computer-readable program for causing a computer to execute the control method according to claim 13.   A computer-readable program for causing a computer to execute the control method according to claim 14.

Images