WO2016207931A1 - ストラクチャードファイナンスの与信管理のための銀行システム、方法およびプログラム - Google Patents
ストラクチャードファイナンスの与信管理のための銀行システム、方法およびプログラム Download PDFInfo
- Publication number
- WO2016207931A1 WO2016207931A1 PCT/JP2015/003236 JP2015003236W WO2016207931A1 WO 2016207931 A1 WO2016207931 A1 WO 2016207931A1 JP 2015003236 W JP2015003236 W JP 2015003236W WO 2016207931 A1 WO2016207931 A1 WO 2016207931A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- information
- credit
- approval
- control card
- entity
- Prior art date
Links
Images
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/02—Banking, e.g. interest calculation or account maintenance
-
- 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/03—Credit; Loans; Processing thereof
-
- 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
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
- G06Q20/34—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using cards, e.g. integrated circuit [IC] cards or magnetic cards
-
- 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
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/38—Payment protocols; Details thereof
- G06Q20/389—Keeping log of transactions for guaranteeing non-repudiation of a transaction
Definitions
- the present invention relates to a bank system, method and program for credit management of structured finance. More particularly, the present invention provides information about a credit transaction management unit that has customer information that can be shared by multiple entities and can handle one or more credit stores and one or more debtors.
- a banking system for credit management of structured finance which can extract one or more related parties associated with a specific financing case and can identify the progress of related operations in credit transactions , Methods and programs.
- a bank headquarters is generally located in the country of the bank, but headquarters can be established in other countries and regions. As an example, some of the major banks have divided the world into multiple regions and set up headquarters in each region (eg, European headquarters, Asia Pacific headquarters, Americas headquarters, and the like) Managing branches and local subsidiaries in other countries.
- SPC special purpose company
- SPC is a paper company invested and established by a plurality of companies involved in a project (for example, oil field development, etc.), and SPC becomes a debtor of the loan.
- Several companies involved in the project are involved in the project as stakeholders but are not debtors. The number of such structured finance is increasing in internationally active banks.
- Banks have developed various banking systems for many years. If the business area of the company that is the customer is domestic only, the bank has already created a system for managing customer information, an approval system for making loan decisions, and a system for credit management. Was operated as a domestic banking system. As already mentioned, as corporate activities expand globally, the banking system is required to meet the needs of companies operating globally. Banks should handle corporate finance and / or structured finance in the context of an increase in the number of corporate finance and structured finance for companies operating globally, and the number of overseas headquarters, branches and local subsidiaries. There was a need to build a new system that could and could involve multiple offices in the bank.
- Patent Document 1 simply discloses a system for making a fund settlement between a plurality of countries
- Patent Document 2 discloses a system for applying for structured finance.
- the conventional banking system is only known as a system that focuses on a specific overseas business, and is a system for performing customer information management, project management, and loan determination in overseas credit. Did not exist.
- An object of the present invention is a banking system for credit management of structured finance that can involve a plurality of offices in a bank, which can provide the progress of credit-related business and can be used for a specific customer. It is possible to provide a banking system that can extract a loan item associated with a specific loan item and extract one or more related parties associated with a specific loan item. This banking system can handle both domestic and overseas credit.
- the bank system for credit management of structured finance as one aspect of the present invention is a first storage means for storing customer information, wherein the customer information can be shared by a plurality of entities.
- the debtor is a second storage means associated with the customer information, and a third storage means for storing information on related parties associated with the debtor.
- the debtor is established for the structured finance by the related party, and the related party is associated with the customer information;
- the control card includes a control card generating means for indicating a progress status of a related business of the credit transaction described in the approval document.
- the customer information is maintained by a plurality of entities associated with the related party, and the information about the credit transaction management unit and the related party information are maintained by the first entity.
- a method executed in a bank system for credit management of structured finance as another aspect of the present invention is to update customer information, and the customer information can be shared by a plurality of entities. And updating information about a credit transaction management unit, wherein the information about the credit transaction management unit includes one or more credit store information and one or more debtor information,
- the obligor is associated with the customer information and updates related party information associated with the obligor, wherein the obligor
- the related party is associated with the customer information
- Acquiring customer information, information about the credit transaction management unit, and information on the related parties generating a first signal, and generating a control card in response to the first signal
- the control card includes a progress status of the related business of the credit transaction described in the approval document.
- the customer information is maintained by a plurality of entities associated with the related party, and the information about the credit transaction management unit and the related party information are maintained by the first entity.
- the bank system can extract a loan item associated with a company by searching Deal information or SL information based on a customer ID of a company with poor performance.
- the bank system can identify related parties based on the SL information, and extract the loan cases of the identified related parties.
- the bank system can provide the progress of credit-related business.
- FIG. 1 is a diagram illustrating a bank system and a plurality of bank terminals, and a network that connects the bank system and the plurality of bank terminals so that they can communicate with each other.
- FIG. 2 is a diagram for explaining the system configuration of the bank system.
- FIG. 3 is a functional block diagram of the customer information management subsystem.
- FIG. 4 is a functional block diagram of the case information management subsystem.
- FIG. 5 is a functional block diagram of the user management subsystem.
- FIG. 6 is a functional block diagram of the approval subsystem.
- FIG. 7 is a functional block diagram of the credit management subsystem.
- FIG. 8A is a diagram illustrating a flow of credit-related work in the first case.
- FIG. 8B is a flowchart for explaining in detail the flow of operations in the first case.
- FIG. 9A is a diagram illustrating a flow of credit-related work in the second case.
- FIG. 9B is a flowchart for explaining in detail the flow of operations in the second case.
- FIG. 10A is a diagram illustrating a flow of credit-related work in the third case.
- FIG. 10B is a flowchart illustrating in detail the operation flow in the third case.
- FIG. 11 shows an example of structured finance.
- FIG. 12 illustrates an example of a processing flow of access control performed in the bank system.
- FIG. 13 shows an exemplary format of the request for approval.
- FIG. 14 shows an exemplary risk factor registration screen.
- FIG. 15 shows an example of a control card.
- Overseas credit A loan made to a bank customer by an overseas branch of the bank or a local corporation related to the bank. There are facilities and exposures as terms equivalent to credit. The former is used to refer to individual credits, and the latter is used to refer to the overall credit to the customer.
- Overseas credit management Managing the credit status of a loaned company in overseas credit management.
- Lending Office Branch or local corporation responsible for credit. In cases where multiple branches or local corporations do business with a single customer, the primary credit store (PLO) is the office that centrally manages customer information and performs debtor evaluation. (SLO: Secondary Lending Office) refers to an office other than the main credit store.
- Global company A company that operates in many regions and needs to be managed by multiple credit stores.
- SL Synonymous with structured finance (SF).
- SF structured finance
- Bank 1 may have branch offices and local subsidiaries associated with bank 1 in multiple countries and regions.
- Bank 1 divides the world into multiple regions and establishes headquarters in each region (eg, European headquarters, Asia Pacific headquarters, Americas headquarters, and the like) and Can manage local subsidiaries. Headquarters, branches and local corporations may be referred to as “entities”.
- 1 shows a bank system 10 and a plurality of bank terminals 20 that can be used by the bank 1, and a bank system 10 and a plurality of bank terminals 20a, 20b,... 20n (in this specification, collectively referred to as “bank terminal 20”).
- 1 is a diagram showing an in-line network or the Internet 30 (referred to as “network 30” in the present specification) to which communication is possible.
- the bank system 10 is a system that can handle deposit business, loan business, domestic exchange business, foreign exchange business, and the like. For purposes of explanation, the present description describes the functions and processes associated with credit management for businesses operating in one or more countries and regions, among the major functions of the banking system 10.
- the bank terminal 20 is a terminal that can access the bank system 10 via the network 30 and use functions provided by the bank system 10.
- the bank terminal 20 may be a terminal that can be used by bank employees, and is not particularly limited.
- the bank terminal 20 may include a personal computer (PC), laptop, tablet terminal, or any other type of device that can operate in a wired or wireless environment.
- the network 30 may be a well-known network capable of mutual communication, including the Internet, a dedicated line, and the like, and is not particularly limited.
- FIG. 2 is a diagram for explaining the system configuration of the bank system 10.
- the bank system 10 can include a processor 21, a main storage device 22, an auxiliary storage device 23, an interface device 24, and an output device 25.
- the devices 21 to 25 can be connected to each other by a bus 26 or the like.
- the processor 21 controls each component in the bank system 10 and calculates data, and can read various programs stored in the auxiliary storage device 23 to the main storage device 22 and execute them.
- the main storage device 22 can store various transmission / reception data, computer-executable instructions, and data after arithmetic processing by the instructions.
- the auxiliary storage device 23 is a storage device such as an HDD (Hard Disk Drive) or an SSD (Solid State Drive), and can store data and programs for a long period of time.
- FIG. 2 illustrates an embodiment in which the processor 21, the main storage device 22, and the auxiliary storage device 23 are provided in the same computer.
- the bank system 10 is configured to implement parallel distributed processing with a plurality of computers by using a plurality of processors 21, a main storage device 22 and an auxiliary storage device 23. Is also possible.
- the interface device 24 serves as an interface for transmitting and receiving data to and from other systems and devices.
- the interface device 24 can provide an interface for receiving various commands and input data (for example, data of various master files) from the system operator.
- the output device 25 can display data processed by the processor 21 and / or data read from various databases and files.
- the output device 25 can provide a function for printing data displayed on the display.
- the bank system 10 can include a customer information management subsystem 11, a case information management subsystem 12, a user management subsystem 13, an approval subsystem 14, and a credit management subsystem 15.
- the subsystems 11 to 15 can include a processor, a main storage device, an auxiliary storage device, an interface device, and an output device that can be connected to each other by a bus or the like, and these devices have the same functions as the devices 21 to 25. Can have.
- the customer information management subsystem 11 is used to manage customer information used in the credit management process.
- the customer information used in the present invention can be used not by each credit store but by a plurality of departments and credit stores in the bank, and is different from the customer information in the conventional customer information file (CIF).
- Customer information in CIF was created and maintained by each credit store. When a certain company has transactions with multiple credit stores in the bank, each credit store has created and maintained customer information, so centralized information management within the bank 1 is not performed. It was.
- customer information is referred to as a “corporate card” in order to distinguish it from a conventional CIF.
- the project information management subsystem 12 is used to manage project information (Deal) related to financing.
- the case information management subsystem 12 can handle both corporate finance and structured finance deals.
- the Deal can include factual information such as the background and reasons for the funding requirements of the client company, as well as the use of the funds and the loan period.
- the user management subsystem 13 can provide a system function accessible by the logged-in user and an access control function for controlling data, and an inspection function for monitoring a user log. Access control functions allow only specific users to access specific system functions and data.
- the inspection function can collect and store a log of a specific operation among user operations performed in the bank system 10. The specific operation for which the logs are to be collected can be predetermined.
- the approval subsystem 14 is a system for creating an approval document for overseas credits, circulating it to the related departments, and obtaining approval from the approval authority.
- the approval subsystem 14 can hold the corporate card and Deal at the time of reviewing the contents of the approval document.
- the held corporate card and Deal can be made at the start of the approval document and / or at the time of approval.
- the approval subsystem 14 can generate and store a copy of the approval document when the approval document is circulated from one entity to another.
- the credit management subsystem 15 can support credit business management, and can strengthen cooperation and internal management between related departments and credit stores.
- the credit management subsystem 15 can provide a function of checking whether the business before the loan execution and the business after the loan execution are appropriately executed.
- FIG. 3 is a functional block diagram of the customer information management subsystem 11.
- the customer information management subsystem 11 can include customer information 31, financial information 32, financial analysis 33, credit monitoring 34, transaction bank 35, and competition comparison 36.
- the elements 31 to 36 are data shared in the bank system 10 and can be collectively referred to as “corporate cards”.
- the corporate card can be shared by a plurality of departments and credit stores, and thus is customer information different from the conventional CIF.
- the customer information 31 is a customer profile, for example, customer ID, company name, head office location, year of establishment, number of employees, factory and / or branch location (country and city name), stock information, shareholders, group Attribute information such as structure, business history, relationship with bank 1, key person, business division, segment by region, major customers, major suppliers can be included.
- Financial information 32 may include a client's income statement, balance sheet, cash flow statement, and the original data for those financial information.
- the financial information 32 can include data for multiple calendar years.
- Financial information 32 can include performance and forecast data.
- the financial analysis 33 can include an analysis result based on information stored in the financial information 32.
- the financial analysis is performed by the person in charge of the bank 1, and the analysis result can be used for credit judgment.
- the credit monitoring 34 can include monitoring information such as the credit rating of the debtor, the debtor status (excellent, caution, etc.), the debtor grade (high, medium, low, etc.).
- the content of the monitoring information can be determined based on criteria established by the bank 1 and / or can be information obtained from a rating agency.
- the transaction bank 35 can include information such as all financial institutions borrowed by the debtor and the borrowing amount from each financial institution.
- the competition comparison 36 can store information (for example, financial information) of the debtor's competitor. The choice of competitors is determined based on information from other obligors in the same business area or by a person in charge of bank 1.
- Access control for information stored in the elements 31 to 36 is performed by the user management subsystem 13. After access information is identified, this access control is used by the access user's organization, credit position and role information, compliance information for the country and region where the entity is managing customer data, and other entities. This is done according to whether the customer has agreed to refer to the customer data.
- the customer information management subsystem 11 can have information on whether or not the customer has agreed to share the information stored in the elements 31-36.
- the entity can indicate each department of the headquarters of the bank 1, a branch, and a local corporation associated with the bank 1.
- FIG. 4 is a functional block diagram of the case information management subsystem 12.
- the case information management subsystem 12 can handle information for a credit transaction management unit (Deal).
- the case information management subsystem 12 can include a Deal Profile 41, credit details information 42, collateral details information 43, and SL information 44.
- the elements 41 to 44 may be collectively referred to as “deal information”.
- the case information management subsystem 12 can handle transactions involving a plurality of credit stores and / or transactions involving a plurality of debtors.
- Deal Profile 41 can store a profile of project information.
- the information stored in the Deal Profile 41 can be associated with information stored in the credit details information 42 and the collateral details information 43 using the case information identifier (Deal number).
- the Deal Profile 41 includes basic information 411 (Deal number, Deal name, Deal owner, one or more credit shops, one or more debtors), a Deal summary 412, a Deal background 413, a lending structure 414, and a support sharing 415 (see FIG. Not shown).
- Basic information 411 may include a Deal number for identifying Deal, a name indicating Deal, one or more credit shops, and customer IDs of one or more debtors.
- Deal summary 412 may include a summary of the transaction.
- Deal Summary 412 states, “The purpose of the loan is working capital for a business company headquartered in India. The loan period is one year and the loan amount is $ 10 million. New Delhi (NDL) and Singapore (SNG's credit shop will provide $ 5 million each).
- Deal Background 413 can include background circumstances and reasons for making this loan.
- the lending structure 414 can include a diagram describing the financing scheme and its description.
- the support allocation 415 can indicate the support ratio of each financial institution (for example, Bank A 40%, Bank B 35%, Bank C 25%).
- the credit details information 42 may include detailed information of the loan such as the details number, debtor, credit type, currency, and loan amount.
- the collateral details information 43 can include detailed information on this Deal collateral. When a plurality of credit stores are involved in Deal, the credit detail information 42 can indicate a combined extreme that combines the extremes set in the respective credit stores.
- the credit details information 42 and the collateral details information 43 can include information of a plurality of debtors.
- the SL information 44 stores information specific to SL (Specialized Lending) when the type of financing is structured finance (for example, financing for a special purpose company (SPC) for a certain project).
- structured finance for example, financing for a special purpose company (SPC) for a certain project.
- FIG. 11 An example of structured finance is shown in FIG. In FIG. 11, an SPC that executes a project for the construction of a thermal power plant is established by the parties involved in the project. The banking group will finance this SPC.
- Sponsors Company B and Company C provide technical support and sales support.
- Company D which sells electricity, concludes a power sale contract and purchases electricity from a thermal power plant.
- Company E a fuel supplier, supplies fuel to the thermal power plant.
- Company F a power plant builder, will build a thermal power plant.
- structured finance is finance based on assets held in a specific business and cash flows generated from the business, and a plurality of stakeholders can be involved.
- the SL information 44 can include an SL number 421, an asset profile 422 (project summary, structure, milestone, etc.), a contract number 423, financial information 424, one or more related parties 425 (not shown).
- SL number 421 is a number for identifying structured finance.
- the asset profile 422 may include information such as project summaries, schemes (structures), and schedules and milestones.
- Contract number 423 indicates identification information of a contract associated with structured finance.
- the financial information 424 indicates project financial information (such as a profit and loss statement, a balance sheet, and a cash flow statement).
- the related party 425 can include one or more stakeholders of the project, and the stakeholders are indicated by the customer ID of the customer information 31.
- Related party 425 may include a role in a stakeholder project.
- roles can include borrowers, guarantors, sponsors, underlying asset owners, buyers, sellers, and the like.
- a credit store having jurisdiction over the SPC can maintain the SL information 44.
- one or more related parties involved in the project can be identified. This makes it possible to identify affected customers when damage occurs in the project.
- FIG. 5 is a functional block diagram of the user management subsystem 13.
- the user management subsystem 13 includes, as a database or file, user information 51, access control 52 based on insider information, access control 53 for data and applications, relationship 54 between department stores, access control 55 based on information categories, and log data. 56 can be provided.
- the user management subsystem 13 can include a user information generation unit 57 and a log data collection unit 58 as processing components.
- User information 51 can include user information and access control information that can be used in the bank system 10.
- the user information 51 can include a user ID 521, a belonging organization 522, a credit position 523, a role 524, and a system operation authority 525 (not shown).
- the user ID 521 is an ID for identifying a user who uses the bank system 10 and the subsystems 11 to 15.
- affiliated organization 522 indicates a user's department (for example, the examination department of the headquarters, the sales department of the Singapore branch, etc.).
- the credit position 523 is a position for determining credit, and indicates positions such as a group manager and a branch manager. These positions are determined based on formal personnel information.
- a role 524 indicates a role (for example, front, front middle, middle back, back, examination unit, etc.) that plays a role related to credit.
- the system operation authority 525 can define a business application that can be operated based on information such as a user's department and credit position in order to prevent unnecessary operations by the user. For example, in a case where a loan appraisal made in a country in Southeast Asia is mistakenly routed to the London Examining Department, a person belonging to the London Examining Department does not need to refer to such an approval document. It is not possible to access the approval document data outside the predetermined area.
- the access control 52 based on insider information includes setting information for permitting access only to a designated user with respect to confidential information such as a corporate card (elements 31 to 36) of a company planning merger and acquisition (M & A). Can be stored.
- the access control 53 for data and applications is for user access to information such as information 31 to 36 in the customer information management subsystem 11, Deal Profile 41, SL information 44 for complicated transactions such as the presence of multiple obligors. Availability information can be included.
- the relationship 54 between department stores may include information on departments, credit stores, and local corporations that need to share customer information of other departments, credit shops, and local corporations.
- the Americas Department needs to refer to customer information associated with entities it manages (eg, branches in the United States). For this reason, the relationship 54 between department stores can contain the information of the entity referred to and the entity referred to.
- the access control 55 based on the information category has a range that can be disclosed according to the type of information, and thus can indicate a disclosure range according to the type of information. For example, since the disclosure range of the information differs depending on the consent / disagreement of the customer for information disclosure, the country where the entity managing the information is located, etc., the access control 55 based on the information category provides Can be included.
- the user information generation unit 57 extracts personnel information (affiliation organization, position, role, etc.) of each user from the personnel information system used in the bank system 10, and extracts the extracted personnel information, a position table (not shown), and The user information 51 can be generated by matching information stored in the change information table.
- the position table defines the access authority to the system for each position of each department store, and the change information table defines the access authority information obtained by changing the default authority set from the position of personnel.
- the log data collection unit 58 can collect a log of a specific operation among user operations performed in the bank system 10.
- the specific operation for which the logs are to be collected can be predetermined. For example, when update data is stored in the customer information 31 in the customer information management subsystem 11, log data related to the operation, for example, user ID, operation date and time, operation terminal, operation type (addition, correction, deletion, etc.) ), Pre-operation data and post-operation data are transmitted to the user management subsystem 13 by the customer information management subsystem 11.
- the log data collection unit 58 can store the transmitted log data in the log data 56.
- the user management subsystem 13 acquires the affiliated organization 522, the credit position 523, the role 524, and the system operation authority 525 based on the user ID 521 of the login user.
- the user uses the bank terminal 20 to try to access certain information.
- the user management subsystem 13 checks the laws and regulations of the country or region where the credit store that manages the referenced information is located. For example, when the credit store that manages the referenced information is located in Singapore, the user management subsystem 13 reads the laws and regulations of Singapore among the laws and regulations of each country held in the subsystem 13.
- the regulation can be, for example, the following three patterns.
- the user management subsystem 13 makes an inquiry to the customer information management subsystem 11 to determine whether or not the customer has agreed that the referenced information is shared. If there is customer consent, the process proceeds to step 1206. If there is no customer consent, the process proceeds to step 1205.
- the user management subsystem 13 determines the legal regulation pattern of the country where the credit store that manages the referenced information is located. If the determined pattern is pattern 3, the process proceeds to step 1206. If the determined pattern is pattern 1 or pattern 2, the process proceeds to step 1208.
- the user management subsystem 13 determines whether the user has an appropriate position and role to access the information. If it has an appropriate position and role, the process proceeds to step 1207. If it does not have an appropriate position and role, processing proceeds to step 1208.
- the user can access the information and can refer to the information.
- the user has limited access to the information or cannot access the information.
- FIG. 12 illustrates the access control based on the information stored in the user information 51, but the access control of the present invention can be implemented in other embodiments. Other embodiments use one or more of user information 51, access control 52 based on insider information, access control 53 for data and applications, relationships 54 between departments, and access control 55 based on information categories. Access control can be implemented.
- FIG. 6 is a functional block diagram of the approval subsystem 14.
- the approval subsystem 14 can include a corporate card 61, deal information 62, an approval document 63, static information 64, and a contract 65 as a database or file.
- the approval subsystem 14 can include an information acquisition unit 66, a static information generation unit 67, and a sending unit 68 as processing components.
- the corporate card 61 is a copy of the information of the “corporate card” at the time of drafting the approval document, ie, customer information 31, financial information 32, financial analysis 33, credit monitoring 34, bank 35, and competitive comparison 36. Can be stored.
- the deal information 62 can store a copy of the “deal information” at the time of drafting the approval document, that is, the information of the deal profile 41, the credit details information 42, the collateral details information 43, and the SL information 44.
- the Deal information 62 can include status information.
- the status information indicates “Pending” before the approval document is approved, and indicates “Fixed” after the approval.
- the approval document 63 can store the approval document data.
- the approval document can include the approval document ID, the contents shown in FIG. 13, and the status.
- the approval document ID indicates an identifier of the approval document, and the status indicates the status of examination (for example, “before approval”, “approved”).
- the request for approval can be associated with the corporate card 61 and the deal information 62.
- the approval document can have an approval document ID and an identifier of the corporate card 61 and the deal information 62 associated with the approval document ID, the approval document is associated with the corporate card 61 and the deal information 62. be able to.
- FIG. 13 shows an exemplary format of the request for approval. This format includes case summaries and conclusions, loan term and condition summaries, guarantees and collateral, profitability, exposure and integrity status, Deal Profile 41 and SL information 44, Corporate Card 61, repayment potential, and key risk factors Can be included.
- the risk factor indicates a risk factor (for example, crude oil market price, Middle East situation, partner company, specific project, etc.) that can affect the management of the customer.
- the bank system 10 can identify the affected Deal and the customer associated with the Deal using the categorized risk factor registered in the corporate card or Deal information.
- FIG. 14 shows an exemplary risk factor registration screen.
- the risk factor registration screen shows the risk type (for example, High-Middle-Low) that takes into account the risk type (for example, Commodity), an indicator that can be a risk factor (for example, WTI), the debtor's financial status, and risk mitigation measures (for example, High-Middle-Low). Information about risk content and mitigation measures for risk.
- the static information 64 can store the static information of the approval document at the time of approval after being approved by the head of the entity with the approval document and before being sent to other entities.
- the static information may be PDF data or the like.
- the contract 65 can store contract signed data created after the approval of the approval document.
- the information acquisition unit 66 can acquire the “corporate card” and “deal information” at the time of drafting the approval document from the customer information management subsystem 11 and the case information management subsystem 12.
- the static information generation unit 67 can generate static information of the approval document at the time of approval after being approved by the head of a certain department and before being sent to other departments. In more detail, when the approval button is pressed to approve the approval document, static information of the approval document is generated. The generated static information is stored in the static information 67.
- the sending unit 68 can notify the confirmer selected by the drafter of the request for approval and the approval authority that there is a request for confirmation.
- the confirmer and the decision-making authority refer to the contents of the approval document stored in the approval document 63, optionally enter a comment, and register approval or rejection.
- the drafter can select the name of the entity in place of or in addition to the confirmer and authorizer. When the name of the department is selected, the department that has received the approval document can select the confirmer and approver of the approval document.
- the approval subsystem 14 can also obtain corporate card information and / or deal information at the time the approval document is approved. Since the information on the corporate card and / or the deal information can be updated with time, the approval subsystem 14 can additionally acquire and hold change information from the time of drafting the approval document to the time of approval.
- the approval subsystem 14 can send a signal indicating creation of the approval document to the credit management subsystem 15 after the approval document is drafted (for example, after the save button is pressed). This signal is the trigger that generates the control card.
- FIG. 7 is a functional block diagram of the credit management subsystem 15.
- the credit management subsystem 15 can include a corporate card 71, deal information 72, approval document 73, contract information 74, and control card 75 as a database or file.
- the credit management subsystem 15 can include an information acquisition unit 76 and a control card (C / C) generation unit 77 as processing components.
- the credit management subsystem 15 can indicate the progress of credit operations that need to be executed.
- the content of the credit business that needs to be executed and the department (role) in charge of the credit business can be determined based on the deal information and the route information of the approval document.
- the department in charge of the credit service can perform the credit service according to the assigned role and can input the result to the credit management subsystem 15.
- the corporate card 71 and deal information 72 include only a part of information included in the corporate card 61 and deal information 62.
- the contract information 74 can include the same information as the information included in the contract 65.
- the approval document 73 can include the same contents as the approval document 63.
- the information acquisition unit 66 extracts predetermined information from the corporate card 61 and the deal information 62 in response to receiving the signal indicating the creation of the approval document, and uses the extracted information as the corporate card 71 and the deal information 72. Can be stored in each.
- the standard of information extraction is whether or not the information is necessary for the credit service. For example, information such as loan background and company performance that is not necessary for checking credit operations is not stored in the corporate card 71 and the deal information 72.
- the control card generation unit 77 can generate a control card in response to receiving a signal indicating creation of the approval document and a signal indicating approval of the approval document from the approval subsystem 14.
- the control card generation unit 77 can generate a control card including a credit service performed before the approval of the approval document based on the signal indicating the generation of the approval document.
- the control card generation unit 77 can generate a control card including a credit service performed after the approval of the approval document based on the signal indicating the approval of the approval document.
- Each of the generated control cards can be combined and used as one control card.
- the control card generation unit 77 can generate one control card in response to a signal indicating the creation of a request for approval, and in one control card according to the approval status of the request for approval. Confirmation items can be increased.
- the control card can include the contents of the credit business that needs to be executed and the department (role) responsible for the credit business.
- the content of the credit business that needs to be executed and the department (role) in charge of the credit business can be determined based on the deal information and the route information of the approval document. For example, a loan for a project in the United States and a loan to a business company headquartered in India have different credit cards and responsible departments and branches that need to be executed, so different control cards are used.
- the control card may be referred to herein as “C / C”.
- FIG. 15 shows an example of the control card 1500.
- the control card 1500 can include a control card number 1501, a responsible entity and role 1502, a document list 1503, a status change button 1504, and a credit service 1505.
- the control card 1500 can further have an associated approval document ID, an identifier for the corporate card 71, and an identifier for the deal information 72.
- the control card number 1501 is a number for identifying the control card.
- Responsible entity and role 1502 may indicate an entity (department, branch, etc.) and role that should be responsible for credit operations.
- the responsible entity and role 1502 may further indicate a user ID and a user name.
- the document list 1503 displays a list of contracts and related documents associated with the control card.
- the credit management subsystem 15 can display the selected data.
- the status change button 1504 is used to shift to the next status when all credit operations that need to be executed indicate “Complete”.
- the status may include “preparation from contract before contract (Pre-Signing)”, “post-signing” and “Available to Drawdown”.
- post-acquisition items can be managed and post-mortem collateral and guarantee satisfaction can be managed.
- the control card 1500 includes a credit service for each loan, and can indicate whether each of the credit services is completed.
- the control card 1500 can include two loans.
- the loan number “X111” indicates that the loan application has been made in Singapore, is in the “Pre-Signing” stage, and the loan name is “Bridge for 364 days”. Indicates "loan”.
- the control card 1500 can include “Application”, “Condition”, “Terms Check”, “Guarante / Collatal”, “Document”, and “Ancillary Process” as credit services related to each loan.
- Credit work “Application” indicates whether the format check of the approval document and / or the approval of the approval document has been completed.
- the credit service “Condition” indicates whether or not the response to the condition given by the examination department at the time of approval of the approval document is completed.
- “Terms Check” indicates whether the inspection of the contract contents described in the contract has been completed.
- the credit service “Guarantee / Collateral” indicates whether guarantees and / or collateral are satisfied.
- the credit service “Document” indicates whether or not a necessary request (various documents) has arrived.
- the credit service “Ancillary Process” indicates whether an accompanying process required before signature is completed.
- the credit management subsystem 15 can have a control card for each proposal, which can indicate the progress of all credit operations that need to be performed.
- the control card 1500 shown in FIG. 15 is merely an example, and the control card 1500 may include other than the credit service shown in this specification.
- the user information 51 can include the user ID 521, the affiliated organization 522, the credit position 523, the role 524, and the system operation authority 525.
- a person's organization and position are assistant managers in the sales department of the Singapore branch, and the person's role is front middle because he is engaged in sales office work.
- another person's organization and position is a senior staff member of the Singapore branch's loan affairs department, whose role is middle back because he is engaged in loan affairs.
- the roles and positions used in this specification are shown in Table 2, but the roles and positions in the bank 1 are not limited to these.
- the first case illustrates the completion of a credit-related business within a single entity of bank 1 (eg, Singapore branch).
- bank 1 eg, Singapore branch
- Singapore may be abbreviated as “SNG”.
- FIG. 8A is a diagram illustrating a flow of credit-related work in the first case.
- Customer ABC Corporation in Singapore applies for a loan at the Singapore branch of Bank 1.
- the Singapore branch front maintains the corporate card, generates deal information, and creates a request for approval.
- the front middle of the Singapore branch checks the format of the request for approval and confirms the necessary documents and necessary procedures.
- the front middle of the Singapore branch will update the control card after inspection and confirmation.
- the front middle of the Singapore branch asks the Asian examination department of the Singapore branch to approve the approval document.
- the Asian Examining Department reviews the request for approval, determines the loan conditions, and approves the loan.
- the Singapore branch front requests the middle management of the Singapore branch for condition management and administrative procedures.
- the Singapore branch's middleback reviews the approved proposals and contracts. After the review, the Singapore branch's middleback will update the control card. (4) The middle branch of the Singapore branch sets the credit limit in the ABC Corporation account in the Singapore branch after the review.
- the credit limit means a credit (ie, loan) limit set for the customer. After that, the back of the Singapore branch is credited to the ABC Corporation account.
- Table 3 shows examples of credit operations for each role described above, but the credit operations are not limited to these operations.
- FIG. 8B is a flowchart for explaining in detail the flow of operations in the first case.
- the front of the Singapore branch of the bank 1 can input the latest customer information to the customer information management subsystem 11 via the bank terminal 20 in response to receiving the loan application from ABC Corporation. It can.
- the customer information management subsystem 11 can provide an application for inputting customer information.
- the input customer information can be stored in the customer information 31, financial information 32, financial analysis 33, credit monitoring 34, transaction bank 35, and competition comparison 36 according to the content of the information.
- the front of the Singapore branch can input an outline of the loan desired by ABC Corporation into the project information management subsystem 12.
- the case information management subsystem 12 can provide an application for inputting a loan summary.
- the input information can be stored in the Deal Profile 41, the credit details information 42, and the collateral details information 43 according to the contents of the information.
- the information stored in the credit details information 42 and the collateral details information 43 is in a pending state until the loan is approved. Since the first case is for corporate finance, the SL information 44 is not used.
- the front of the Singapore branch accesses the approval subsystem 14 via the bank terminal 20 and creates an approval document.
- the Singapore branch front can optionally set a risk factor for the corporate card and Deal information.
- the information acquisition unit 66 of the approval subsystem 14 uses the latest data stored in the customer information 31, financial information 32, financial analysis 33, credit monitoring 34, transaction bank 35 and competitive comparison 36 associated with the approval document as the customer. It can be acquired from the information management subsystem 11.
- the acquired data is stored in the corporate card 61 in the approval subsystem 14.
- the information acquisition unit 66 of the approval subsystem 14 can acquire the latest data stored in the Deal Profile 41, the credit details information 42, and the collateral details information 43 associated with the approval document from the case information management subsystem 12. .
- the acquired data is stored in the Deal information 62 in the approval subsystem 14.
- the approval subsystem 14 can associate the customer information at the time of the creation of the approval document and the information on the loan project with the approval document.
- the approval subsystem 14 can transmit a signal indicating the creation of the approval document to the credit management subsystem 15.
- this signal is received by the credit management subsystem 15, a control card including a credit service to be performed before the approval of the approval document is generated.
- the front of the Singapore branch selects the department (and order) of the person who examines the created approval document on the approval subsystem 14.
- the approval subsystem 14 can record the selected route in association with the approval document and forward the approval document according to the route.
- the front middle of the Singapore branch checks the format of the approval document and completes the confirmation of the contents, the completion of the confirmation can be registered on the approval subsystem 14.
- the items “Application” and “Condition” in the control card are automatically updated from “Incomplete” to “Complete”.
- the Asian examination department of the Singapore branch can access the approval subsystem 14 via the bank terminal 20 and approve the distributed approval document.
- the approval subsystem 14 can send a signal indicating the approval to the credit management subsystem 15 in response to the approval of the approval document.
- the credit management subsystem 15 acquires customer information from the approval subsystem 14 and stores it in the corporate card 71, and also relates to the loan contents from the case information management subsystem 12. Information to be acquired and stored in the Deal information 72.
- the credit management subsystem 15 dynamically generates a control card including a credit service performed after the approval of the approval document according to the approved approval document content (for example, lending conditions), and generates the generated control card as a control card. 75 can be stored.
- the Singapore branch's front desk After approving the request for approval, the Singapore branch's front desk prepares a contract according to the content of the request for approval. After the created contract is signed, it is stored in the contract 65 of the approval subsystem 14. In response to the fact that the contract document is stored in the contract document 65, the approval subsystem 14 transmits the contract contents to the credit management subsystem 15, and the transmitted contract contents information is stored in the contract information 74. . As for the information stored in the contract information 74, only information necessary for checking the credit service can be referred to by each role.
- the middle branch of the Singapore branch reviews the approved approval document and the created contract, and determines whether the predetermined check items are satisfied.
- the middle branch of the Singapore branch accesses the control card 75 of the credit management subsystem 15 and updates the status of the check item determined to be satisfied from “Incomplete” to “Complete”.
- the middle back of the Singapore branch can set a credit limit on the ABC Corporation account in the Singapore branch after reviewing the contract. This credit limit can be determined based on the loan terms stated in the contract.
- the back of the Singapore branch performs a deposit operation on the bank system 10 via the bank terminal 20 in accordance with information such as the set credit limit and the deposit date / time of the contract. Funds based on credit limits are deposited into ABC Corporation accounts.
- the second case illustrates that the credit-related business is performed by a plurality of entities of the bank 1 (for example, the Singapore branch, the Hanoi branch, and the headquarters in Tokyo).
- Hanoi may be abbreviated as “HNI”
- Tokyo may be abbreviated as “TKY”.
- FIG. 9A is a diagram illustrating a flow of credit-related work in the second case.
- a customer XYZ Corporation in Singapore applies for a loan to the Singapore branch of Bank 1.
- the Singapore branch front maintains the corporate card, generates deal information, and creates a request for approval.
- the front middle of the Singapore branch checks the format of the request for approval and confirms the necessary documents and necessary procedures.
- the front middle of the Singapore branch will update the control card after inspection and confirmation.
- the Singapore branch's front middle will ask the headquarters screening department to approve the approval document.
- the examination department at the headquarters reviews the approval document, determines the loan conditions, and approves the loan.
- the Singapore branch front will request condition management and administrative procedures from the Hanoi branch in Vietnam.
- the Hanoi branch's middleback reviews approved approvals and contracts. After the review, the middle branch of Hanoi branch will update the control card. (4) The middle branch of the Hanoi branch sets a credit limit in the XYZ Corporation account in the Hanoi branch after the review.
- the credit limit means a credit (ie, loan) limit set for the customer. After that, the back of the Hanoi branch is credited to the account of XYZ Corporation.
- FIG. 9B is a flowchart for explaining in detail the flow of operations in the second case.
- the front of the Singapore branch of the bank 1 can input the latest customer information to the customer information management subsystem 11 via the bank terminal 20 in response to receiving a loan application from XYZ Corporation. it can.
- the customer information management subsystem 11 can provide an application for inputting customer information.
- the input customer information can be stored in the customer information 31, financial information 32, financial analysis 33, credit monitoring 34, transaction bank 35, and competition comparison 36 according to the content of the information.
- the front of the Singapore branch can input an outline of the loan desired by XYZ Corporation into the project information management subsystem 12.
- the case information management subsystem 12 can provide an application for inputting a loan summary.
- the input information can be stored in the Deal Profile 41, the credit details information 42, and the collateral details information 43 according to the contents of the information.
- the information stored in the credit details information 42 and the collateral details information 43 is in a pending state until the loan is approved. Since the second case is for corporate finance, the SL information 44 is not used.
- the front of the Singapore branch accesses the approval subsystem 14 via the bank terminal 20 and creates an approval document.
- the Singapore branch front can optionally set a risk factor for the corporate card and Deal information.
- the information acquisition unit 66 of the approval subsystem 14 uses the latest data stored in the customer information 31, financial information 32, financial analysis 33, credit monitoring 34, transaction bank 35 and competitive comparison 36 associated with the approval document as the customer. It can be acquired from the information management subsystem 11.
- the acquired data is stored in the corporate card 61 in the approval subsystem 14.
- the information acquisition unit 66 of the approval subsystem 14 can acquire the latest data stored in the Deal Profile 41, the credit details information 42, and the collateral details information 43 associated with the approval document from the case information management subsystem 12. .
- the acquired data is stored in the Deal information 62 in the approval subsystem 14.
- the approval subsystem 14 can associate the customer information at the time of the creation of the approval document and the information on the loan project with the approval document.
- the approval subsystem 14 can transmit a signal indicating the creation of the approval document to the credit management subsystem 15.
- this signal is received by the credit management subsystem 15, a control card including a credit service to be performed before the approval of the approval document is generated.
- the front of the Singapore branch selects the department (and order) of the person who examines the created approval document on the approval subsystem 14.
- the approval subsystem 14 can record the selected route in association with the approval document and forward the approval document according to the route.
- the front middle of the Singapore branch checks the format of the approval document and completes the confirmation of the contents, the completion of the confirmation can be registered on the approval subsystem 14.
- the items “Application” and “Condition” in the control card are automatically updated from “Incomplete” to “Complete”.
- the examination unit of the headquarters can access the approval subsystem 14 via the bank terminal 20 and approve the distributed approval document.
- the approval subsystem 14 can signal a signal indicating approval to the credit management subsystem 15 in response to the approval of the approval document.
- the credit management subsystem 15 acquires customer information from the approval subsystem 14 and stores it in the corporate card 71, and also relates to the loan contents from the case information management subsystem 12. Information to be acquired and stored in the Deal information 72.
- the credit management subsystem 15 dynamically generates a control card including a credit service performed after the approval of the approval document according to the approved approval document content (for example, lending conditions), and generates the generated control card as a control card. 75 can be stored.
- the Singapore branch's front desk After approving the request for approval, the Singapore branch's front desk prepares a contract according to the content of the request for approval. After the created contract is signed, it is stored in the contract 65 of the approval subsystem 14. In response to the fact that the contract document is stored in the contract document 65, the approval subsystem 14 transmits the contract contents to the credit management subsystem 15, and the transmitted contract contents information is stored in the contract information 74. . As for the information stored in the contract information 74, only information necessary for checking the credit service can be referred to by each role.
- the middle branch of the Hanoi branch reviews the approved approval document and the created contract, and determines whether the predetermined check items are satisfied.
- the middle branch of the Hanoi branch accesses the control card 75 of the credit management subsystem 15 and updates the status of the check item determined to be satisfied from “Incomplete” to “Complete”.
- the middle branch of Hanoi branch can set the credit limit in the account of XYZ Corporation in Hanoi branch after reviewing the contract. This credit limit can be determined based on the loan terms stated in the contract.
- the back of the Hanoi branch performs a deposit operation on the bank system 10 via the bank terminal 20 in accordance with information such as the set credit limit and the deposit date and time of the contract. Funds based on credit limits are credited to XYZ Corporation accounts.
- the third case illustrates that credit-related operations are performed by multiple entities of bank 1 (eg, London branch, New York branch, Tokyo branch, Dubai branch, Tokyo headquarters examination department).
- bank 1 eg, London branch, New York branch, Tokyo branch, Dubai branch, Tokyo headquarters examination department.
- London may be abbreviated as “LDN”
- New York may be abbreviated as “NYC”
- DBI DBI
- FIG. 10A is a diagram illustrating a flow of credit-related work in the third case.
- the third case illustrates financing for a natural gas purification facility construction project as an example.
- Company B the sponsor of the project
- Company C the contractor
- Company D a customer
- a Corporation is an SPC established by Company B, Company C and Company D for the project and is a customer of the London branch. In that project, A Corporation is the debtor.
- a Corporation in London (LDN) applies for a loan to Bank 1's London branch. The front of the London branch updates the corporate card of A Corporation and generates Deal information.
- the application for financing is notified to the New York, Tokyo and Dubai branches in charge of Company B, Company C and Company D, the parties involved in the project.
- the front desks of New York branch, Tokyo branch and Caribbean branch renew corporate cards of company B, company C and company D.
- the front desk of the London branch prepares a request for approval in response to the application for the loan.
- the London branch's front middle checks the format of the request for approval and confirms the required documents and required procedures.
- the front middle of the London branch will update the control card after inspection and confirmation.
- the front middle of the London branch asks the review department of the Tokyo headquarters to approve the approval document.
- the examination department at the headquarters reviews the approval document, determines the loan conditions, and approves the loan.
- the London Branch front desk requests condition management and administrative procedures from the London Branch Middle Back.
- the London branch's middleback reviews approved approvals and contracts. After the review, the London branch's middleback will update the control card.
- the London branch middleback sets a credit limit for the A Corporation account in the London branch.
- the credit limit means a credit (ie, loan) limit set for the customer. Thereafter, the back of the London branch deposits money into the A Corporation account.
- FIG. 10B is a flowchart for explaining in detail the operation flow in the third case.
- step S1001 the front of the London branch of the bank 1 can input the latest customer information to the customer information management subsystem 11 via the bank terminal 20 in response to receiving a loan application from A Corporation. it can.
- the customer information management subsystem 11 can provide an application for inputting customer information.
- the inputted customer information of A Corporation can be stored in customer information 31, financial information 32, financial analysis 33, credit monitoring 34, transaction bank 35 and competitive comparison 36 in accordance with the contents of the information.
- the front of the London branch can input an outline of the loan desired by A Corporation into the project information management subsystem 12.
- the case information management subsystem 12 can provide an application for inputting a loan summary.
- the input information can be stored in the Deal Profile 41, the credit details information 42, the collateral details information 43, and the SL information 44 according to the contents of the information.
- the information stored in the credit details information 42 and the collateral details information 43 is in a pending state until the loan is approved. Since the third case targets structured finance, the SL information 44 is used.
- the SL information 44 stores identifiers of the companies B, C, and D that are the stakeholders of the project.
- the project information management subsystem 12 can notify the New York branch, the Tokyo branch, and the Caribbean branch in charge of companies B, C, and D, which are parties involved in the project, for a loan application.
- the fronts of the New York branch, Tokyo branch, and Caribbean branch access the customer information management subsystem 11 via the bank terminal 20, and the latest customers of Company B, Company C, and Company D, respectively.
- Information can be entered.
- the inputted customer information of Company B, Company C, and Company D may be stored in customer information 31, financial information 32, financial analysis 33, credit monitoring 34, transaction bank 35, and competitive comparison 36 according to the content of the information. Is possible.
- the front of the London branch accesses the approval subsystem 14 via the bank terminal 20 and creates an approval document.
- the London branch front can optionally set risk factors for corporate cards and Deal information.
- the information acquisition unit 66 of the approval subsystem 14 uses the latest data stored in the customer information 31, financial information 32, financial analysis 33, credit monitoring 34, transaction bank 35 and competitive comparison 36 associated with the approval document as the customer. It can be acquired from the information management subsystem 11.
- the acquired data is stored in the corporate card 61 in the approval subsystem 14.
- the information acquisition unit 66 of the approval subsystem 14 acquires the latest data stored in the Deal Profile 41, the credit details information 42, the collateral details information 43, and the SL information 44 associated with the approval document from the matter information management subsystem 12. can do.
- the acquired data is stored in the Deal information 62 in the approval subsystem 14.
- the approval subsystem 14 can associate the customer information at the time of the creation of the approval document and the information on the loan project with the approval document.
- the approval subsystem 14 can transmit a signal indicating the creation of the approval document to the credit management subsystem 15.
- this signal is received by the credit management subsystem 15, a control card including a credit service to be performed before the approval of the approval document is generated.
- the front desk of the London branch selects the department (and order) of the person who examines the created approval document on the approval subsystem 14.
- the approval subsystem 14 can record the selected route in association with the approval document and forward the approval document according to the route.
- the front middle of the London branch inspects the format of the approval document and confirms the contents, the completion of the confirmation can be registered on the approval subsystem 14.
- the items “Application” and “Condition” in the control card are automatically updated from “Incomplete” to “Complete”.
- the examination unit of the headquarters can access the approval subsystem 14 via the bank terminal 20 and approve the distributed approval document.
- the approval subsystem 14 can send a signal indicating the approval to the credit management subsystem 15 in response to the approval of the approval document.
- the credit management subsystem 15 acquires customer information from the approval subsystem 14 and stores it in the corporate card 71, and also relates to the loan contents from the case information management subsystem 12. Information to be acquired and stored in the Deal information 72.
- the credit management subsystem 15 dynamically generates a control card including a credit service performed after the approval of the approval document according to the approved approval document content (for example, lending conditions), and generates the generated control card as a control card. 75 can be stored.
- the front desk of the London branch After approving the request for approval, the front desk of the London branch prepares a contract according to the contents of the request for approval. After the created contract is signed, it is stored in the contract 65 of the approval subsystem 14. In response to the fact that the contract document is stored in the contract document 65, the approval subsystem 14 transmits the contract contents to the credit management subsystem 15, and the transmitted contract contents information is stored in the contract information 74. . As for the information stored in the contract information 74, only information necessary for checking the credit service can be referred to by each role.
- the London branch middle back reviews the approved approval document and the created contract, and determines whether or not a predetermined check item is satisfied.
- the middle branch of the London branch accesses the control card 75 of the credit management subsystem 15 and updates the status of the check item determined to be satisfied from “Incomplete” to “Complete”.
- the London branch middleback may set a credit limit on the A Corporation account in the London branch after reviewing the contract. This credit limit can be determined based on the loan terms stated in the contract.
- the back of the London branch performs a deposit operation on the bank system 10 via the bank terminal 20 in accordance with information such as the set credit limit and the deposit date and time of the contract. Funds based on credit limits are credited to A Corporation's account.
- the bank system 10 can extract a loan item associated with a company by searching for Deal information or SL information based on a customer ID of a company with poor performance. According to the present invention, when a certain project causes a large loss, the bank system 10 can identify related parties based on the SL information, and can extract the loan cases of each identified related party. According to the present invention, since the bank system 10 can provide the progress status of credit-related business, more efficient credit management can be performed.
- the present invention can take the form of, for example, a system, apparatus, method, program, or storage medium.
Landscapes
- Business, Economics & Management (AREA)
- Engineering & Computer Science (AREA)
- Accounting & Taxation (AREA)
- Finance (AREA)
- Physics & Mathematics (AREA)
- Theoretical Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Strategic Management (AREA)
- General Business, Economics & Management (AREA)
- Development Economics (AREA)
- Technology Law (AREA)
- Marketing (AREA)
- Economics (AREA)
- Microelectronics & Electronic Packaging (AREA)
- Computer Networks & Wireless Communication (AREA)
- Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
Description
本明細書において使用される以下の用語の意味について定義される。
図8Aおよび図8Bを参照して、コーポレートファイナンスのための第1のケースが説明される。第1のケースは、銀行1のただ一つのエンティティ(例えば、シンガポール支店)内で与信関連業務が完結することを例証する。本明細書および図面において、シンガポールは、「SNG」と略されてもよい。
(1)シンガポールにある顧客ABCコーポレーションが、銀行1のシンガポール支店において融資を申し込む。
(2)シンガポール支店のフロントは、融資の申込を受けたことに応答して、コーポレートカードをメンテナンスし、Deal情報を生成し、稟議書を作成する。シンガポール支店のフロントミドルは、稟議書の形式を点検し、必要書類および必要な手続きを確認する。シンガポール支店のフロントミドルは、点検および確認の後、コントロールカードをアップデートする。シンガポール支店のフロントミドルは、シンガポール支店のアジア審査部に稟議書の決裁を求める。アジア審査部は、稟議書をレビューし、貸出条件を決定し、融資を承認する。
(3)決裁後、シンガポール支店のフロントは、シンガポール支店のミドルバックに条件管理および事務手続を依頼する。シンガポール支店のミドルバックは、承認された稟議書および契約書をレビューする。レビュー後、シンガポール支店のミドルバックは、コントロールカードをアップデートする。
(4)シンガポール支店のミドルバックは、レビュー後、シンガポール支店内のABCコーポレーションの口座に与信限度額を設定する。与信限度額は、顧客に対して設定する与信(すなわち、融資)の限度額を意味する。その後、シンガポール支店のバックは、ABCコーポレーションの口座に入金する。
図9Aおよび図9Bを参照して、コーポレートファイナンスのための第2のケースが説明される。第2のケースは、銀行1の複数のエンティティ(例えば、シンガポール支店、ハノイ支店、東京の本部の審査部)によって与信関連業務が行われることを例証する。本明細書および図面において、ハノイは「HNI」と略されてもよく、かつ東京は「TKY」と略されてもよい。
(1)シンガポール(SNG)にある顧客XYZコーポレーションが、銀行1のシンガポール支店に融資を申し込む。
(2)シンガポール支店のフロントは、融資の申込を受けたことに応答して、コーポレートカードをメンテナンスし、Deal情報を生成し、稟議書を作成する。シンガポール支店のフロントミドルは、稟議書の形式を点検し、必要書類および必要な手続きを確認する。シンガポール支店のフロントミドルは、点検および確認の後、コントロールカードをアップデートする。シンガポール支店のフロントミドルは、本部の審査部に稟議書の決裁を求める。本部の審査部は、稟議書をレビューし、貸出条件を決定し、融資を承認する。
(3)決裁後、シンガポール支店のフロントは、ベトナムのハノイ支店のミドルバックに条件管理および事務手続を依頼する。ハノイ支店のミドルバックは、承認された稟議書および契約書をレビューする。レビュー後、ハノイ支店のミドルバックは、コントロールカードをアップデートする。
(4)ハノイ支店のミドルバックは、レビュー後、ハノイ支店内のXYZコーポレーションの口座に与信限度額を設定する。与信限度額は、顧客に対して設定する与信(すなわち、融資)の限度額を意味する。その後、ハノイ支店のバックは、XYZコーポレーションの口座に入金する。
図10Aおよび図10Bを参照して、ストラクチャードファイナンスのための第3のケースが説明される。第3のケースは、銀行1の複数のエンティティ(例えば、ロンドン支店、ニューヨーク支店、東京支店、ドバイ支店、東京の本部の審査部)によって与信関連業務が行われることを例証する。本明細書および図面において、ロンドンは「LDN」と略されてもよく、ニューヨークは「NYC」と略されてもよく、かつドバイは「DBI」と略されてもよい。
(1)ロンドン(LDN)にあるAコーポレーションが、銀行1のロンドン支店に融資を申し込む。ロンドン支店のフロントは、Aコーポレーションのコーポレートカードを更新し、Deal情報を生成する。融資の申込があったことは、そのプロジェクトの関係当事者であるB社、C社およびD社を担当するニューヨーク支店、東京支店およびドバイ支店に通知される。ニューヨーク支店、東京支店およびドバイ支店の各フロントは、B社、C社およびD社のコーポレートカードを更新する。
(2)ロンドン支店のフロントは、融資の申込を受けたことに応答して稟議書を作成する。ロンドン支店のフロントミドルは、稟議書の形式を点検し、必要書類および必要な手続きを確認する。ロンドン支店のフロントミドルは、点検および確認の後、コントロールカードをアップデートする。ロンドン支店のフロントミドルは、東京の本部の審査部に稟議書の決裁を求める。本部の審査部は、稟議書をレビューし、貸出条件を決定し、融資を承認する。
(3)決裁後、ロンドン支店のフロントは、ロンドン支店のミドルバックに条件管理および事務手続を依頼する。ロンドン支店のミドルバックは、承認された稟議書および契約書をレビューする。レビュー後、ロンドン支店のミドルバックは、コントロールカードをアップデートする。
(4)ロンドン支店のミドルバックは、レビュー後、ロンドン支店内のAコーポレーションの口座に与信限度額を設定する。与信限度額は、顧客に対して設定する与信(すなわち、融資)の限度額を意味する。その後、ロンドン支店のバックは、Aコーポレーションの口座に入金する。
Claims (17)
- ストラクチャードファイナンスの与信管理のための銀行システムであって、
顧客情報を格納する第1の格納手段であって、前記顧客情報は、複数のエンティティによって共有可能である、第1の格納手段と、
与信取引の管理単位についての情報を格納する第2の格納手段であって、前記与信取引の管理単位についての情報は、1または複数の与信店の情報および1または複数の債務者の情報を有し、前記債務者は、前記顧客情報に関連付けられている、第2の格納手段と、
前記債務者に関連付けられている関係当事者の情報を格納する第3の格納手段であって、前記債務者は、前記関係当事者によって前記ストラクチャードファイナンスのために設立され、前記関係当事者は、前記顧客情報に関連付けられている、第3の格納手段と、
稟議書に記載された与信取引の実行を承認する承認手段であって、前記承認手段は、前記稟議書の作成時の、前記顧客情報、前記与信取引の管理単位についての情報、および前記関係当事者の情報を有し、前記稟議書の作成時に第1のシグナルを生成する、承認手段と、
前記第1のシグナルに応答してコントロールカードを生成するコントロールカード生成手段であって、前記コントロールカードは、前記稟議書に記載された与信取引の関連業務の進捗状況を示す、コントロールカード生成手段と
を備え、
前記顧客情報は、前記関係当事者に関連付けられた複数のエンティティによってメンテナンスされ、
前記与信取引の管理単位についての情報および前記関係当事者の情報は、第1のエンティティによってメンテナンスされる、
銀行システム。 - 前記コントロールカードによって示される関連業務の一部は、前記稟議書が承認される前は不可視である、請求項1の銀行システム。
- 前記承認手段は、前記稟議書の承認時に第2のシグナルを生成し、
前記コントロールカード生成手段は、前記第2のシグナルに応答して第2のコントロールカードを生成し、前記第2のコントロールカードは、前記コントロールカードに結合されうる、請求項1の銀行システム。 - 前記コントロールカードは、第2のエンティティによって更新され、
前記第1のエンティティは、第1の役割を有し、前記第2のエンティティは、第2の役割を有する、請求項1の銀行システム。 - 前記第1の役割はフロントであり、前記第2の役割はミドルバックである、請求項3の銀行システム。
- 前記コントロールカードは、第1のエンティティによって更新され、
前記第1のエンティティは、第1の役割および第2の役割を有する、請求項1の銀行システム。 - 前記第1の役割はフロントであり、前記第2の役割はミドルバックである、請求項6の銀行システム。
- 前記第1のエンティティは主たる与信店(PLO)である、請求項1の銀行システム。
- 前記顧客情報、前記与信取引の管理単位についての情報、前記関係当事者の情報および前記コントロールカードへのアクセス制御を行うアクセス制御手段をさらに備え、
前記アクセス制御は、ユーザの所属エンティティ、与信職位および役割に少なくとも基づいて行われる、請求項1の銀行システム。 - 前記稟議書は、1または複数のリスクファクターを含み、
前記リスクファクターに関連付けられた与信取引を抽出する抽出手段をさらに備えた、請求項1の銀行システム。 - ストラクチャードファイナンスの与信管理のための銀行システムにおいて実行される方法であって、前記方法は、
顧客情報を更新することであって、前記顧客情報は、複数のエンティティによって共有可能である、ことと、
与信取引の管理単位についての情報を更新することであって、前記与信取引の管理単位についての情報は、1または複数の与信店の情報および1または複数の債務者の情報を有し、前記債務者は、前記顧客情報に関連付けられている、ことと、
前記債務者に関連付けられている関係当事者の情報を更新することであって、前記債務者は、前記関係当事者によって前記ストラクチャードファイナンスのために設立され、前記関係当事者は、前記顧客情報に関連付けられている、ことと、
稟議書の作成に応答して、前記顧客情報、前記与信取引の管理単位についての情報、および前記関係当事者の情報を取得し、並びに第1のシグナルを生成することと、
前記第1のシグナルに応答してコントロールカードを生成することであって、前記コントロールカードは、前記稟議書に記載された与信取引の関連業務の進捗状況を示す、ことと
を備え、
前記顧客情報は、前記関係当事者に関連付けられた複数のエンティティによってメンテナンスされ、
前記与信取引の管理単位についての情報および前記関係当事者の情報は、第1のエンティティによってメンテナンスされる、
方法。 - 前記コントロールカードによって示される関連業務の一部は、前記稟議書が承認される前は不可視である、請求項11の方法。
- 前記稟議書の承認に応答して、第2のシグナルを生成することと、
前記第2のシグナルに応答して第2のコントロールカードを生成することであって、前記第2のコントロールカードは、前記コントロールカードに結合されうる、ことと
をさらに備える、請求項11の方法。 - 前記コントロールカードは、第2のエンティティによって更新され、
前記第1のエンティティは、第1の役割を有し、前記第2のエンティティは、第2の役割を有する、請求項11の方法。 - 前記コントロールカードは、第1のエンティティによって更新され、
前記第1のエンティティは、第1の役割および第2の役割を有する、請求項11の方法。 - 前記顧客情報、前記与信取引の管理単位についての情報、前記関係当事者の情報および前記コントロールカードへのアクセス制御を行うことであって、前記アクセス制御は、ユーザの所属エンティティ、与信職位および役割に少なくとも基づいて行われる、ことをさらに備える、請求項11の方法。
- プロセッサによって実行される時に、請求項11乃至16のいずれか一項に記載の方法をコンピュータに実行させるプログラム。
Priority Applications (5)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US15/739,035 US20180197240A1 (en) | 2015-06-26 | 2015-06-26 | Banking system, method and computer-readable storage medium for credit management for structured finance |
JP2016516102A JP5963997B1 (ja) | 2015-06-26 | 2015-06-26 | ストラクチャードファイナンスの与信管理のための銀行システム、方法およびプログラム |
CA3029295A CA3029295A1 (en) | 2015-06-26 | 2015-06-26 | Banking system, method and program for credit control for structured finance |
PCT/JP2015/003236 WO2016207931A1 (ja) | 2015-06-26 | 2015-06-26 | ストラクチャードファイナンスの与信管理のための銀行システム、方法およびプログラム |
CN201580081259.6A CN107924534A (zh) | 2015-06-26 | 2015-06-26 | 用于结构性融资的信贷管理的银行系统、方法以及程序 |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/JP2015/003236 WO2016207931A1 (ja) | 2015-06-26 | 2015-06-26 | ストラクチャードファイナンスの与信管理のための銀行システム、方法およびプログラム |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2016207931A1 true WO2016207931A1 (ja) | 2016-12-29 |
Family
ID=56558022
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2015/003236 WO2016207931A1 (ja) | 2015-06-26 | 2015-06-26 | ストラクチャードファイナンスの与信管理のための銀行システム、方法およびプログラム |
Country Status (5)
Country | Link |
---|---|
US (1) | US20180197240A1 (ja) |
JP (1) | JP5963997B1 (ja) |
CN (1) | CN107924534A (ja) |
CA (1) | CA3029295A1 (ja) |
WO (1) | WO2016207931A1 (ja) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP6356362B1 (ja) * | 2017-03-30 | 2018-07-11 | 株式会社三井住友銀行 | 銀行システムおよび銀行システムによって実行される方法 |
Families Citing this family (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN112785280B (zh) * | 2021-02-05 | 2022-06-14 | 福建省农村信用社联合社 | 一种基于二级法人模式的推送存款产品的装置 |
CN113327159B (zh) * | 2021-04-23 | 2022-06-10 | 福建省农村信用社联合社 | 一种银行端助贷交易系统及其方法 |
CN115545948B (zh) * | 2022-10-19 | 2023-12-12 | 国家电投集团财务有限公司 | 一种融资管理方法及装置 |
Citations (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2002352087A (ja) * | 2001-05-23 | 2002-12-06 | Sumitomo Mitsui Banking Corp | ストラクチャードファイナンス申し込みシステム |
JP2003296572A (ja) * | 2002-03-29 | 2003-10-17 | Japan Research Institute Ltd | 融資支援システム、情報端末装置、融資支援方法およびその方法をコンピュータに実行させるプログラム |
JP2003296554A (ja) * | 2002-04-02 | 2003-10-17 | Hachijuni Bank Ltd | 取引先要項システム |
US20040088246A1 (en) * | 2002-11-05 | 2004-05-06 | Global Student Loan Corp. | System and method for loan application generation |
JP2004318869A (ja) * | 2003-03-31 | 2004-11-11 | Kagoshima Bank Ltd | 融資管理システム |
JP2005134937A (ja) * | 2002-10-15 | 2005-05-26 | Kagoshima Bank Ltd | 融資審査システム及び融資審査プログラム |
Family Cites Families (22)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5375055A (en) * | 1992-02-03 | 1994-12-20 | Foreign Exchange Transaction Services, Inc. | Credit management for electronic brokerage system |
US6985883B1 (en) * | 1992-02-03 | 2006-01-10 | Ebs Dealing Resources, Inc. | Credit management for electronic brokerage system |
US7181427B1 (en) * | 1995-09-12 | 2007-02-20 | Jp Morgan Chase Bank, N.A. | Automated credit application system |
US7010607B1 (en) * | 1999-09-15 | 2006-03-07 | Hewlett-Packard Development Company, L.P. | Method for training a communication link between ports to correct for errors |
US7249075B1 (en) * | 1999-09-16 | 2007-07-24 | Morgan Stanley | System and method for administering principal protected equity linked financial instruments |
US8504438B2 (en) * | 2000-03-21 | 2013-08-06 | James D. Bennett | Online purchasing system supporting lenders with affordability screening |
US20080021802A1 (en) * | 2001-05-14 | 2008-01-24 | Pendleton Mark R | Method for providing credit offering and credit management information services |
US9710852B1 (en) * | 2002-05-30 | 2017-07-18 | Consumerinfo.Com, Inc. | Credit report timeline user interface |
US7472090B1 (en) * | 2002-12-31 | 2008-12-30 | Capital One Financial Corporation | Method and system for providing a higher credit limit to a customer |
US20040153396A1 (en) * | 2003-01-31 | 2004-08-05 | Harald Hinderer | Telecommunications credit management system and method |
US7986630B1 (en) * | 2004-02-09 | 2011-07-26 | Lsi Corporation | High performance architecture for fiber channel targets and target bridges |
US7797230B1 (en) * | 2005-06-02 | 2010-09-14 | The Pnc Financial Services Group, Inc. | Systems and methods for credit management risk rating and approval |
US20060277126A1 (en) * | 2005-06-06 | 2006-12-07 | Intel Corporation | Ring credit management |
US7908210B2 (en) * | 2006-04-20 | 2011-03-15 | Finance Express, Llc | Systems and method for managing dealer information |
WO2007135683A2 (en) * | 2006-05-23 | 2007-11-29 | Perspective D.S.S Ltd. | Credit management system and method |
US20080177655A1 (en) * | 2007-01-23 | 2008-07-24 | David Zalik | Systems and methods of underwriting business credit |
JP5186197B2 (ja) * | 2007-12-19 | 2013-04-17 | 株式会社エヌ・ティ・ティ・データ | 評価装置、評価方法及び評価プログラム |
US20090240609A1 (en) * | 2008-03-19 | 2009-09-24 | Soogyung Cho | System and method for tracking and analyzing loans involved in asset-backed securities |
US20130080223A1 (en) * | 2011-09-25 | 2013-03-28 | Redbox Automated Retail, Llc | System and method for management of credit subscriptions |
US9870589B1 (en) * | 2013-03-14 | 2018-01-16 | Consumerinfo.Com, Inc. | Credit utilization tracking and reporting |
CN104573937A (zh) * | 2014-12-26 | 2015-04-29 | 广州科亚信息科技有限公司 | 一种企业信用网站系统 |
US10296383B2 (en) * | 2015-07-10 | 2019-05-21 | Samsung Electronics Co., Ltd. | Computing system with resource management mechanism and method of operation thereof |
-
2015
- 2015-06-26 CN CN201580081259.6A patent/CN107924534A/zh active Pending
- 2015-06-26 WO PCT/JP2015/003236 patent/WO2016207931A1/ja active Application Filing
- 2015-06-26 CA CA3029295A patent/CA3029295A1/en active Pending
- 2015-06-26 US US15/739,035 patent/US20180197240A1/en not_active Abandoned
- 2015-06-26 JP JP2016516102A patent/JP5963997B1/ja active Active
Patent Citations (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2002352087A (ja) * | 2001-05-23 | 2002-12-06 | Sumitomo Mitsui Banking Corp | ストラクチャードファイナンス申し込みシステム |
JP2003296572A (ja) * | 2002-03-29 | 2003-10-17 | Japan Research Institute Ltd | 融資支援システム、情報端末装置、融資支援方法およびその方法をコンピュータに実行させるプログラム |
JP2003296554A (ja) * | 2002-04-02 | 2003-10-17 | Hachijuni Bank Ltd | 取引先要項システム |
JP2005134937A (ja) * | 2002-10-15 | 2005-05-26 | Kagoshima Bank Ltd | 融資審査システム及び融資審査プログラム |
US20040088246A1 (en) * | 2002-11-05 | 2004-05-06 | Global Student Loan Corp. | System and method for loan application generation |
JP2004318869A (ja) * | 2003-03-31 | 2004-11-11 | Kagoshima Bank Ltd | 融資管理システム |
Cited By (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP6356362B1 (ja) * | 2017-03-30 | 2018-07-11 | 株式会社三井住友銀行 | 銀行システムおよび銀行システムによって実行される方法 |
WO2018179290A1 (ja) * | 2017-03-30 | 2018-10-04 | 株式会社三井住友銀行 | 銀行システムおよび銀行システムによって実行される方法 |
CN108990424A (zh) * | 2017-03-30 | 2018-12-11 | 株式会社三井住友银行 | 银行系统以及由银行系统执行的方法 |
Also Published As
Publication number | Publication date |
---|---|
JPWO2016207931A1 (ja) | 2017-06-22 |
JP5963997B1 (ja) | 2016-08-03 |
CA3029295A1 (en) | 2016-12-29 |
CN107924534A (zh) | 2018-04-17 |
US20180197240A1 (en) | 2018-07-12 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US20190295164A1 (en) | Information processing apparatus, information processing method, and recording medium | |
Foley et al. | eGovernment and the transformation agenda | |
JP5952518B1 (ja) | コーポレートファイナンスの海外与信管理のための銀行システム、方法およびプログラム | |
US20150302406A1 (en) | Methods and systems for improving accurancy of merchant aggregation | |
JP5963997B1 (ja) | ストラクチャードファイナンスの与信管理のための銀行システム、方法およびプログラム | |
JP2020154347A (ja) | 信用分析支援方法、信用分析支援システム、およびノード | |
JP2023074500A (ja) | 情報処理装置及びプログラム | |
Simmons | Securities operations: a guide to trade and position management | |
JP2018195137A (ja) | 与信管理システム、方法及びプログラム | |
JP6133529B1 (ja) | 電子稟議書の更新方法およびシステム | |
Nwogugu | Complex Systems, Multi-Sided Incentives and Risk Perception in Companies | |
Walker | Digital Money & Central Bank Digital Currency | |
JP6356362B1 (ja) | 銀行システムおよび銀行システムによって実行される方法 | |
JP2002007703A (ja) | インターネットによる金融取引システム | |
JP6130979B1 (ja) | 与信管理システム、方法、およびプログラム | |
Ngo | Formulation of strategic plan for a financial technology startup company | |
JP2005050375A (ja) | 電子手形管理システム及びその方法 | |
JP6698228B2 (ja) | 案件および企業グループベースのリスク管理方法、コンピュータおよびプログラム | |
Islam | An Analysis of Automated Trading System of Dhaka Stock Exchange Ltd | |
Baer et al. | The national credit bureau: A key enabler of financial infrastructure and lending in developing economies | |
JP2002109209A (ja) | 情報処理装置、ネットワークシステム、運営管理システム、運営管理方法、及び記憶媒体 | |
Gericke et al. | Institutional Background | |
JP2014146295A (ja) | でんさい支払不能者管理システム | |
Tomitz | The technical and legal implementation of a crowdfunding platform | |
JP2005032278A (ja) | 電子手形管理システムとその方法 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
ENP | Entry into the national phase |
Ref document number: 2016516102 Country of ref document: JP Kind code of ref document: A |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 15896255 Country of ref document: EP Kind code of ref document: A1 |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 15896255 Country of ref document: EP Kind code of ref document: A1 |
|
ENP | Entry into the national phase |
Ref document number: 3029295 Country of ref document: CA |