WO2016157252A1 - 与信事務管理システムおよびその方法 - Google Patents
与信事務管理システムおよびその方法 Download PDFInfo
- Publication number
- WO2016157252A1 WO2016157252A1 PCT/JP2015/001866 JP2015001866W WO2016157252A1 WO 2016157252 A1 WO2016157252 A1 WO 2016157252A1 JP 2015001866 W JP2015001866 W JP 2015001866W WO 2016157252 A1 WO2016157252 A1 WO 2016157252A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- credit
- storage unit
- control card
- check
- document
- 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
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/22—Payment schemes or models
- G06Q20/24—Credit schemes, i.e. "pay after"
-
- 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/42—Confirmation, e.g. check or permission by the legal debtor of payment
-
- 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
Definitions
- the present invention relates to a credit administration system and method. More specifically, the present invention uses the control card that enables the secretariat to visualize the matters to be checked at each stage and the progress status in the credit workflow, thereby enabling the entire credit business to be visualized.
- the present invention relates to a system and method for improving efficiency and strengthening an internal management system.
- a sales department person in charge of a specific branch negotiates with a customer, and creates an approval document based on the customer negotiation.
- the sales clerk at the same branch checks the format of the approval document created by the sales clerk and checks the contents of necessary documents.
- the person in charge of the examination department at the head office approves the approval document created by the person in charge of the sales department.
- the sales department and the credit office staff at the same branch confirm the satisfaction of the loan conditions, such as matching the approved approval document and contract documents.
- the sales department, the credit administration department, and the account department in charge of the branch carry out the lending execution.
- Patent Document 1 includes a customer information database that centrally manages information related to customers subject to loan examination, and a plurality of tasks for processing a series of tasks necessary for loan examination using the customer information database.
- a loan screening system is disclosed that includes processing means and processing status management means for displaying the processing status of each business processing means in a list.
- the status of each business of loan screening is managed in a database according to the processing order, so that employees at the head office and each branch can share information.
- the sales department person in charge of the branch a in Country A negotiates with the customer and prepares the approval document.
- the sales department clerk belonging to the branch a confirms the contents of the approval document.
- the person in charge of the examination department belonging to the b branch in Country B approves the approval document.
- the credit office staff member who belongs to the c branch in country C confirms the approved approval document and the contract documents, and finally the account office staff member who belongs to the c branch office performs the lending process. Is assumed.
- Patent Document 1 the process of creating the approval document, which is a process upstream of the credit service, is subdivided and the processing status is managed, and the history up to the approval document draft is in charge, other employees in the branch, branch manager The staff of the head office examination department can confirm.
- the process performed by the credit clerk who follows the credit operation does not mention the necessity of management and the advantage of promoting the visualization of check items.
- the object of the present invention is to provide a credit card by using a control card that makes it possible to visualize matters to be checked at each stage and their progress in the credit flow. It is to provide a system and method for improving the efficiency of the entire business and strengthening the internal management system.
- a credit administration system includes an approval document code, a scheduled signature date, a scheduled credit execution date, a status, and a check completion flag for a plurality of in-line rule items for each predetermined period in association with a control card code.
- the approval code the conditions when the approval document is approved with conditions, the approval condition part including the deadline, and the loan condition part including the conditions necessary for lending
- a control card creation unit for registering a record in the control card storage unit, wherein, based on the approval condition part and the lending condition part, an item to be checked is not checked among the plurality of in-line rule items.
- a control card creation unit for storing a value indicating completion.
- a credit administration method in accordance with a control card code, an approval code, a scheduled signature date, a scheduled credit execution date, a status, and a check completion flag for a plurality of in-line rule items for each predetermined period.
- the credit card management system having a control card storage unit for storing the credit card management system includes a approval card code, a condition when the approval document is approved with a condition, and a deadline Receiving a deliberation condition part and a lending condition part including conditions necessary for lending, and a step in which the control card creating unit registers a record in the control card storage unit based on the received information.
- the approval condition part and the lending condition part Of the inner regulations item, it stores a value indicating the unfinished items to be checked, to perform the steps.
- control card that allows the administrative department to visualize the matters to be checked at each stage and the progress status thereof, double management of local regulations items and regions It can avoid situations that lead to deterioration in business efficiency, such as responding to regulatory inquiries, and can improve the overall efficiency of credit operations and strengthen the internal management system.
- FIG. 1 shows an exemplary overall network configuration according to the present invention.
- FIG. 2 shows a system configuration of an exemplary credit business management system according to the present invention.
- FIG. 3 is a functional block diagram of an exemplary credit business management system according to the present invention.
- FIG. 4 shows an example of information stored in an exemplary person-in-charge DB according to the present invention.
- FIG. 5 shows an example of information stored in the exemplary approval document DB according to the present invention.
- FIG. 6A shows an example of information stored in an exemplary control card DB according to the present invention.
- FIG. 6B shows an example of information stored in an exemplary control card DB according to the present invention.
- FIG. 6C shows an example of information stored in an exemplary control card DB according to the present invention.
- FIG. 1 shows an exemplary overall network configuration according to the present invention.
- FIG. 2 shows a system configuration of an exemplary credit business management system according to the present invention.
- FIG. 3 is a functional block diagram of an exemplary credit
- FIG. 6D shows an example of information stored in an exemplary control card DB according to the present invention.
- FIG. 6E shows an example of information stored in an exemplary control card DB according to the present invention.
- FIG. 7 shows an example of information stored in an exemplary regional regulation DB according to the present invention.
- FIG. 8 shows an example of information stored in the exemplary contract condition check DB according to the present invention.
- FIG. 9 shows an example of information stored in the exemplary collateral / guarantee check DB according to the present invention.
- FIG. 10 shows an example of information stored in an exemplary document check DB according to the present invention.
- FIG. 11 shows a processing flow for creating a control card.
- FIG. 12 shows an example of a control card screen displayed on the client computer.
- FIG. 13 shows an example of a contract check screen displayed on the client computer.
- FIG. 14 shows an example of a control card screen displayed on the client computer.
- control card is used to describe a group of information that enables the secretariat to visualize the matters to be checked at each stage and the progress status in the credit workflow.
- FIG. 1 shows an exemplary overall network configuration according to the present invention.
- a credit management system 100 a client computer 111 installed in a branch in country A, a client computer 112 installed in a branch in country B, and a client computer 113 installed in a branch in country C are shown.
- And are communicably connected via an in-line network or the Internet 120.
- the credit administration system 100 includes a person-in-charge database (DB) 101 that stores information related to bankers belonging to the bank 1, an approval document database (DB) 102 that stores approval documents, and a contract database (DB) that stores contracts. 103 and a control card database (DB) 104, and manages credit operations processed between branches around the world.
- DB person-in-charge database
- DB approval document database
- DB contract database
- DB contract database
- DB control card database
- the client computer 111 is a client computer installed in the country A branch office.
- the person in charge at the branch a can access the credit administration system 100 via the client computer 111 and store the created approval document in the approval document DB 102.
- the person in charge of the branch a can access the credit administration system 100 via the client computer 111 and store the created contract in the contract DB 103.
- the client computer 112 is a client computer installed at a branch b in Country B.
- the person in charge of the examination department of the branch b can access the credit administration system 100 via the client computer 112 and browse the approval document stored in the approval document DB 102.
- the client computer 113 is a client computer installed in the c branch in country C.
- the person in charge of middle back at branch c can access the credit administration system 100 via the client computer 113 and update the information in the control card DB 104.
- FIG. 2 shows the system configuration of the credit administration system 100.
- the credit office management system 100 includes a CPU 201, a RAM 202, a ROM 203, a storage 204, a connection interface 205, and a network interface 206.
- the components 201 to 206 are connected via a bus 210 so that they can communicate with each other.
- the connection interface 205 is an interface for connecting various devices to the credit office management system 100.
- a display, a keyboard, a mouse, an external storage device, and the like can be connected to the credit office management system 100 via the connection interface 205.
- the network interface 206 is connected to the local network or the Internet 120 through a communication line.
- the network interface 206 controls data input / output between the intra-bank network or the Internet 120 and the credit administration system 100 based on the control of the CPU 201.
- the connection between the network interface 206 and the in-line network or the Internet 120 may be a wired connection or a wireless connection.
- FIG. 3 is a functional block diagram of the credit administration system 100.
- the credit administration system 100 includes a person-in-charge DB 101, an approval document DB 102, a contract document DB 103, a control card DB 104, a regional regulation DB 301, a contract condition check DB 302, a collateral / guarantee check DB 303, a document check DB 304, a document DB 305, and an approval document data management unit.
- 310 a control card creation unit 311, a contract condition setting unit 312, a collateral / guarantee setting unit 313, and a document setting unit 314.
- the person-in-charge DB 101 stores information on bank employees belonging to the bank 1.
- the person-in-charge DB 101 includes a person-in-charge code, a person-in-charge name, an affiliated branch code, an affiliated branch name, and a role (“0: Other”, “1: Front”, “2: Screening Department”, “3: Middle Back”, “4: Back”) are stored.
- the approval document DB 102 stores information related to the approval document.
- the approval document DB 102 stores information on the person in charge (responsible branch code, person code) who created the approval document in association with the approval document code that uniquely identifies the approval document.
- a plurality of parts including information constituting the approval document (approval condition part, loan condition part, credit information part, case summary part, and market part), approval flag ("0: before approval", "1: approved”) ) And an electronic approval document file are stored.
- each part stores a structured document such as XML.
- XML structured document
- the approval condition part includes the conditions when the approval document is approved under certain conditions, the answer written when the conditions are satisfied, and the expiration date.
- the lending condition part includes conditions necessary for lending such as obligor information, credit type, credit amount, credit execution date, credit execution country, collateral / guarantee.
- the credit information part includes the credit information of the debtor.
- the case summary part includes credit transaction history information.
- the market part includes market information related to credit transactions.
- the contract DB 103 stores an electronic contract file in association with a contract code that uniquely identifies the contract.
- the contract document DB 103 is not provided, and an electronic contract document file can be stored in a document DB 305 described later.
- Approval approval identifies whether the approval request has been approved by the Examining Department.
- the credit administration system 100 stores “1: Complete” in the approval document approval.
- the contract check identifies whether the consistency check between the finalized approval document and the contract has been completed.
- the credit administration system 100 stores “1: Complete” in the contract check.
- the document identifies whether the document has been requested.
- the credit administration system 100 sets the document as one of a pre-signature document, a post-signature document, or a post-credit execution document according to the document acquisition deadline set in the document check DB 304. To do. Thereafter, in this embodiment, when the document check DB 304 described later confirms the collection of all the documents for which the acquisition deadline is set for a predetermined period (before signature, after signature, or after execution of credit), the credit administration system 100 Stores “1: Complete” in a document for a predetermined period.
- Local regulations identify whether local regulatory items have been observed.
- the credit administration system 100 stores “1: Complete” in the regional regulations.
- the signature identifies whether the contracting party has signed the contract. In the present embodiment, when all the signatures are confirmed in the contract condition check DB 302 described later, the credit administration system 100 stores “1: Complete” in the signature.
- the contract condition check DB 302 stores check items set based on the lending conditions of the approval document.
- the contract condition check DB 302 includes the obligor information, the guarantor information, the credit type, the credit amount, the credit execution date, the credit in association with the loan code of the control card DB 104.
- Execution country and signature information are stored.
- the signature information the signer name or “1: confirmed” is stored, and in each check item excluding the signature information, “0: unconfirmed” or “1: confirmed” is stored.
- the credit office management system 100 stores “1: confirmed” in the check item.
- the collateral / guarantee check DB 303 stores collateral / guarantee information included in the lending conditions of the proposal.
- the collateral / guarantee check DB 303 includes a collateral / guarantee name, a confirmation flag (“0: unconfirmed”, “1: confirmed”) associated with the loan code of the control card DB 104. )) And the fulfillment deadline are stored.
- the credit office management system 100 stores “1: confirmed” in the confirmation flag.
- the document check DB 304 stores information on collected documents.
- the document check DB 304 includes a collection document name, a confirmation flag (“0: unconfirmed”, “1: confirmed”) associated with the loan code of the control card DB 104, And the acquisition deadline is stored.
- the credit administration system 100 upon receiving a document confirmation instruction from the client computer 111 or the like, stores “1: confirmed” in the confirmation flag.
- the approval document data management unit 310 also transmits the approval document code, the approval condition part, the lending condition part, and the designation information of the related department to the control card creation unit 311.
- the control card creation unit 311 registers a record in the control card DB 104 in response to receiving the approval document code, the approval condition part, the lending condition part, and the related department designation information from the approval document data management unit 310.
- the control card creation unit 311 refers to the credit execution country included in the lending condition part and registers the number of records corresponding to the number of credit execution countries. For example, when there is one credit execution country, one record is registered, and when there are two credit execution countries, two records are registered. When registering a record, the control card creation unit 311 generates and stores a control card code corresponding to the approval document code and a loan code that can uniquely identify a plurality of loans in the same control card code.
- control card creation unit 311 stores the received approval code, the middle back branch code included in the designated information of the related department, the credit execution country, the expected signature date, and the expected credit execution date included in the loan condition part, respectively. To do. About the person-in-charge code, the control card creation unit 311 can set based on debtor information included in the lending condition part.
- the control card creation unit 311 sets a symbol (“ ⁇ ”) for the satisfaction of the condition that does not match the expiration date based on the received approval condition part. When the conditions for approval of approval are not set, the control card creation unit 311 sets a symbol (“-”) for all the condition satisfaction.
- the control card creation unit 311 sets a symbol (“ ⁇ ”) for the collateral / guarantee that does not match the fulfillment deadline based on the collateral / guarantee included in the received lending condition part.
- the control card creation unit 311 After registering the record in the control card DB 104, the control card creation unit 311 sets the contract code in the record of the control card DB 104 in response to receiving the contract creation data.
- the contract document creation data includes a loan code and a contract code.
- the contract condition setting unit 312 registers a record in the contract condition check DB 302 based on the lending condition part.
- the contract condition setting unit 312 registers a record in association with the loan code created by the control card creation unit 311.
- the contract condition setting unit 312 sets “0: unconfirmed” for the item included in the lending condition part, and sets the symbol “ ⁇ ” for the item not included in the lending condition part.
- the contract condition setting unit 312 sets the party name of the contract specified in the lending condition part.
- the collateral / guarantee setting unit 313 registers a record in the collateral / guarantee check DB 303 based on the collateral / guarantee included in the lending condition part.
- the collateral / guarantee setting unit 313 registers a record based on the collateral / guarantee name and the fulfillment deadline included in the lending condition part in association with the loan code created by the control card creation unit 311. At this time, “0: unconfirmed” is set as an initial value in the confirmation flag.
- the collateral / guarantee setting unit 313 determines whether different collateral / guarantees are set for each loan to each credit execution country. When different collateral / guarantee is set, the collateral / guarantee setting unit 313 registers a corresponding collateral / guarantee record for each loan code corresponding to the loan to each credit executing country.
- the collateral / guarantee setting unit 313 registers a collateral / guarantee record only for any one loan code.
- the selection of the loan code can be performed by any method, for example, giving priority to the loan code handled by the middle back of the same branch code as the front or depending on the size of the branch designated as the middle back. .
- the collateral / guarantee setting unit 313 registers a corresponding collateral / guarantee record for each loan code corresponding to a loan to each credit executing country. To do. After that, on the collateral / guarantee check screen described later, the person in charge in any one of the multiple credit execution countries sends a satisfaction confirmation instruction by selecting the check field via the client computer 111 or the like. In response to this, the credit administration system 100 stores “1: confirmed” in the confirmation flag of the collateral / guarantee check DB 303 for all of a plurality of credit executing countries for which the same collateral / guarantee is set. . Thereby, in all the plurality of credit execution countries, the result registered by the person in charge of any one of the plurality of credit execution countries can be shared.
- the document setting unit 314 registers a record in the document check DB 304 in response to receiving the document list update data from the client computer 111 or the like.
- the document list update data includes a loan code, a collection document name, and an acquisition deadline.
- the document setting unit 314 registers a record based on the document list update data. At this time, “0: unconfirmed” is set as an initial value in the confirmation flag.
- the document setting unit 314 also sets “0: Incomplete” to the document of the control card record that matches the acquisition deadline based on the document list update data.
- Control card creation process The control card creation process will be described with reference to FIG. FIG. 11 shows a processing flow for creating a control card. Assume that the person-in-charge DB 101 of the credit administration system 100 stores the records shown in FIG. It is assumed that the record shown in FIG. 7 is also stored in the regional regulation DB 301 of the credit administration system 100.
- the approval document data management unit of the credit administration system 100 registers a record in the approval document DB 102 in S1102 in response to receiving the approval document related data from the client computer 111 or the like.
- the branch code to which the person in charge of creating the approval document belongs the person in charge code, information constituting the approval document divided into a plurality of parts, and all information constituting the approval document are used.
- the agenda data management section 310 Upon receiving the agenda-related data including the electronic agenda file created and the designated information (examination department, middle back, back) of the related departments related to the target award, the agenda data management section 310 receives the agenda data.
- a book code (3333333) is created, and a record is registered in the approval document DB 102. At this time, “0: before approval” is set as an initial value in the approval flag.
- control card creation unit 311 registers a record in the control card DB 104 based on the information received from the approval document data management unit 310.
- the control card creation unit 311 receives the approval code (3333333) and the middle information included in the designation information of the related department.
- 3333333 One record based on back branch code (333), credit execution country (country C) included in the loan condition part, signature date (April 10, 2015), credit execution date (April 24, 2015) sign up.
- control card creation unit 311 When registering a record, the control card creation unit 311 generates and stores a control card code (C3333333) and a loan code (C3333) corresponding to the approval code.
- the control card creation unit 311 sets the person-in-charge code (333-22222) based on the obligor information included in the lending condition part, and sets the status to “0: before signature” as the initial value.
- control card creation unit 311 sets a symbol (“-”) for the condition satisfaction that does not match the satisfaction deadline based on the received approval condition part.
- control card creation unit 311 displays a symbol (“-”) in the satisfaction condition before the signature and the satisfaction condition after the execution of credit. ) Is set.
- control card creation unit 311 sets a symbol (“ ⁇ ”) for the condition fulfillment that does not match the fulfillment deadline based on the collateral / guarantee included in the received lending condition part.
- control card creation unit 311 searches the regional regulation DB 301 based on the credit execution country included in the received lending condition part, and sets the symbol “-” in the regional regulation when there is no regional regulation item. .
- the contract condition setting unit 312 of the credit office management system 100 registers a record in the contract condition check DB 302 based on the lending condition part.
- the contract condition setting unit 312 registers the record shown in FIG. 8 in association with the loan code (C3333) created by the control card creation unit 311.
- C3333 loan code
- a lending condition part that does not include guarantor information is received, and the symbol “-” is set in the guarantor information.
- signature information signature 1, signature 2, signature 3
- the contract condition setting unit 312 sets the signer 1 to the signature 1. Then, the sign “ ⁇ ” is set for the signature 2 and the signature 3.
- the collateral / guarantee setting unit 313 of the credit administration system 100 registers a record in the collateral / guarantee check DB 303 based on the collateral / guarantee included in the lending condition part.
- the document setting unit 314 of the credit administration system 100 registers a record in the document check DB 304 in response to receiving the document list update data from the client computer 111 or the like. Subsequently, in S1110, the document setting unit 314 sets “0: Incomplete” to the document of the control card record that matches the fulfillment deadline based on the document list update data.
- the document setting unit 314 receives the document list update data including the loan code (C3333), the collection document name (document 6), and the expiration date before signature (2015/4/9). Assume that the indicated record has been registered. Subsequently, it is assumed that the document setting unit 314 sets “0: Incomplete” to the document before the signature of the control card record based on the document list update data.
- control card creation unit 311 sets the contract code in the record of the control card DB 104 in response to receiving the contract creation data.
- the contract card creation data 311 including the loan code (C3333) and the contract code (32345) is received, and the control card creation unit 311 sets the contract code of the control card DB 104.
- FIGS. 12 and 14 show examples of control card screens displayed on the client computer.
- FIG. 13 shows an example of a contract check screen displayed on the client computer.
- the person-in-charge DB 101, the approval document DB 102, the control card DB 104, the regional regulation DB 301, the contract check DB 302, the collateral / guarantee check DB 303, and the document check DB 304 of the credit administration system 100 are respectively shown in FIGS. 4, 5, and 6A. Assume that the records shown in FIGS. 7, 8, 9, and 10 are stored.
- the person in charge 2 transmits authentication information including a person-in-charge code (111-22222) and a password to the credit administration system 100 via the client computer 111 and succeeds in authentication based on the authentication information.
- the credit management system 100 can display a list of control cards handled by the person who succeeds in the authentication based on the control card DB 104.
- the credit administration system 100 provides the client computer 111 with a list including two control cards handled by the person in charge (person in charge 2) who has been successfully authenticated, and is specified by the loan code (X1111). 12 is received from the client computer 111, and the control card screen shown in FIG. 12 is provided to the client computer 111.
- a document list related to the control card is displayed.
- the front person in charge can upload a document in association with a loan code at any timing after the creation of the control card record, and can view the uploaded document from the document list.
- the approval document approval in the column 1201 is stored in the approval flag of the record specified by the approval document code (2222222) of the approval document DB 102 shown in FIG. Thus, “1: Complete” is already stored.
- the credit administration system 100 displays the approval document screen ( (Not shown) can be provided.
- the provided approval request screen is displayed by selecting some or all of the plurality of parts constituting the approval request in accordance with the role of the person in charge who has logged in. For example, when the front person in charge who created the approval document is logged in, a screen including all the parts constituting the approval document is displayed. On the other hand, when the person in charge of middle back is logged in, only the parts necessary for credit affairs are selected and displayed.
- the credit administration system 100 displays the approval document condition screen (FIG. Not shown).
- the approval document condition screen includes information on the approval condition part.
- the contract check in the column 1201 stores “0: Incomplete” as shown in FIG.
- the person in charge 2 selects the contract check (“0: Incomplete”) in the column 1201 shown in FIG. 12 via the client computer 111
- the credit administration system 100 is shown in FIG.
- a contract condition check screen as shown in FIG. 13 can be provided.
- Person in charge 2 confirms the consistency between the contents displayed in the approval document-lending conditions on the contract condition check screen and the contents of the contract.
- the person in charge 2 selects, for example, the document list 1203 on the control card screen displayed in FIG. 12 via the client computer 111 and selects a contract from the document list. Check the consistency while browsing the stored electronic contract file.
- the credit administration system 100 when the person in charge 2 transmits a consistency confirmation instruction by selecting a check column via the client computer 111, the credit administration system 100 adds “1” to the corresponding check item in the contract condition check DB 302. : Confirmed ”is stored. As described above, in the present embodiment, when the consistency of all the contract conditions except for the signature information is confirmed in the contract condition check DB 302, the credit administration system 100 performs “1” for the contract check in the control card DB 104. : Complete ”is stored.
- the document check screen includes a request document name and a check field, and the person in charge 2 displays the document list displayed when the request document displayed on the document check screen is selected as the document list 1203 on the control card screen. To make sure that it is present within.
- the credit administration system 100 when the person in charge 2 transmits a request for confirming the selection by selecting the check column via the client computer 111, the credit administration system 100 sets “1: Confirmation” to the corresponding check item in the document check DB 304. "Completed” is stored. As described above, in this embodiment, when the document check DB 304 confirms the collection of all the documents whose acquisition deadlines are set for a predetermined period (before signature, after signature, or after execution of credit), the credit administration system 100 stores “1: Complete” in the document for a predetermined period in the control card DB 104.
- the area regulation in the column 1201 stores “0: Incomplete” as shown in FIG.
- the credit administration system 100 displays the regional regulation check screen (FIG. Not shown).
- the region regulation check screen includes a region regulation item name and a check column, and the person in charge 2 confirms that the contract contents comply with the region regulation item displayed on the region regulation check screen.
- the credit administration system 100 sets “1: Complete” as the regional regulation of the control card DB 104. Store.
- the control card record specified by the loan code (X1111) in the control card DB 104 has all the in-line rule items before signature as “1: Complete” as shown in FIG. 6B.
- the person in charge 2 presses the status change button 1204 on the screen of the control card shown in FIG.
- the status of the control card record specified by the loan code (X1111) is updated from “0: before signature” to “1: after signature” as shown in FIG. 6C.
- the credit administration system 100 when the status of the control card record is updated from “0: before signature” to “1: after signature”, the credit administration system 100, as shown in FIG.
- the client computer 111 is provided with a screen of the control card including the later in-line rule items.
- the signature in the column 1401 stores “0: Incomplete” as shown in FIG.
- the person in charge 2 selects the signature (“0: Incomplete”) in the column 1201 shown in FIG. 14 via the client computer 111
- the credit administration system 100 will receive the contract conditions shown in FIG. 8.
- a signature check screen (not shown) can be provided.
- the signature check screen includes a signer name and a check field
- the person in charge 2 confirms that any number of signers displayed on the signature check screen have signed the contract.
- the person in charge 2 selects, for example, the document list 1203 on the control card screen displayed in FIG. 14 via the client computer 111 and selects a contract from the document list. Confirm the signature by browsing the stored electronic contract file.
- the credit administration system 100 when the person in charge 2 transmits a signature confirmation instruction by selecting a check column via the client computer 111, the credit administration system 100 adds “1:” to the corresponding check item in the contract condition check DB 302. “Confirmed” is stored. As described above, in this embodiment, when all the book titles are confirmed in the contract condition check DB 302, the credit office management system 100 stores “1: Complete” in the signature of the control card DB 104.
- the collateral / guarantee after signature in the column 1401 stores “0: Incomplete” as shown in FIG.
- the credit administration system 100 displays A collateral / guarantee check screen (not shown) can be provided based on the collateral / guarantee check DB 303 shown in FIG.
- the collateral / guarantee check screen includes a collateral / guarantee name and a check column, and the person in charge 2 confirms that the collateral / guarantee displayed on the collateral / guarantee check screen is satisfied.
- the credit administration system 100 sets “1” in the corresponding confirmation flag of the collateral / guarantee check DB 303. : Confirmed ”is stored.
- the collateral / guarantee check DB 303 confirms the satisfaction of all the collateral / guarantees for which the fulfillment deadline is set for a predetermined period (before signing, after signing, or after executing credit)
- the credit office management system 100 stores “1: Complete” in the collateral / guarantee for a predetermined period in the control card DB 104.
- the control card record specified by the loan code (X1111) in the control card DB 104 has all in-line rule items “1: Complete” as shown in FIG. 6D.
- the status change button 1402 on the screen of the control card shown in FIG. 14 through the client computer 111 in a state where all the in-line rule items are “1: Complete” As shown in FIG. 6E, the status of the control card record specified by the loan code (X1111) is updated from “1: after signature” to “2: business completion”.
- control card that enables the administrative department to visualize the matters to be checked at each stage and the progress status thereof, double management of the in-line rule items that have conventionally occurred It can avoid situations that lead to deterioration in business efficiency, such as responding to inquiries and local regulations, and can improve the efficiency of the entire credit business and strengthen the internal management system.
- the product-specific regulations identify whether or not the in-line rules to be checked have been observed according to the products (contract type) provided by the bank 1.
- the credit administration system 100 stores “1: Complete” in the product-specific regulations.
- the credit office management system 100 further includes a product-specific check DB 306 and a product-specific setting unit 315.
- the product-specific check DB 306 stores information on items to be checked for specific products based on the lending conditions of the approval document.
- the item-specific check DB 306 stores an item name and a confirmation flag (“0: unconfirmed”, “1: confirmed”) in association with the loan code in the control card DB 104.
- the credit administration system 100 upon receiving a confirmation instruction from the client computer 111 or the like, stores “1: confirmed” in the confirmation flag.
- the product-specific setting unit 315 registers a record in the product-specific check DB 303 based on the lending condition part.
- the product-specific setting unit 313 associates the loan code created by the control card creation unit 311 with the item to be checked in the product to which the contract corresponds and registers the record.
- “0: unconfirmed” is set as an initial value in the confirmation flag.
- the product-specific setting unit 315 can set the implementation of an environmental assessment as an item to be checked in the product to which the contract corresponds.
- the present invention can take an embodiment as, for example, a system, apparatus, method, program, or storage medium.
Landscapes
- Business, Economics & Management (AREA)
- Accounting & Taxation (AREA)
- Engineering & Computer Science (AREA)
- Finance (AREA)
- Physics & Mathematics (AREA)
- Strategic Management (AREA)
- General Business, Economics & Management (AREA)
- General Physics & Mathematics (AREA)
- Theoretical Computer Science (AREA)
- Economics (AREA)
- Marketing (AREA)
- Technology Law (AREA)
- Development Economics (AREA)
- Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
Description
図11を参照して、コントロールカード作成処理について説明する。図11は、コントロールカードを作成する処理フローを示す。与信事務管理システム100の担当者DB101には、図4に示されるレコードが格納されているものとする。与信事務管理システム100の地域規制DB301にも、図7に示されるレコードが格納されているものとする。
次に、図12~14を参照して、コントロールカード更新処理について説明する。図12、14は、クライアントコンピューターに表示される、コントロールカードの画面の一例を示す。図13は、クライアントコンピューターに表示される、契約書チェック画面の一例を示す。与信事務管理システム100の担当者DB101、稟議書DB102、コントロールカードDB104、地域規制DB301、契約書チェックDB302、担保・保証チェックDB303、およびドキュメントチェックDB304には、それぞれ、図4、図5、図6A、図7、図8、図9、および図10に示されるレコードが格納されているものとする。
追加の実施形態では、コントロールカードDB104は、行内規程項目として、さらに商品別規制を格納することができる。
Claims (16)
- コントロールカードコードに関連付けて稟議書コード、署名予定日、与信実行予定日、ステータス、および所定期間ごとに複数の行内規程項目のチェック完了フラグを格納するコントロールカード記憶部と、
稟議書コード、条件付きで稟議書が決裁される場合の条件、および充足期限を含む稟議条件パート、および貸出に必要な条件を含む貸出条件パートを受信することに応答して、前記コントロールカード記憶部にレコードを登録するコントロールカード作成部であって、前記稟議条件パートおよび前記貸出条件パートに基づいて、前記複数の行内規程項目のうち、チェックすべき項目に未完了を示す値を格納する、コントロールカード作成部と
を備えた、与信事務管理システム。 - 前記コントロールカード記憶部は、貸付コードおよび与信実行国をさらに格納し、
前記コントロールカード作成部は、前記貸出条件パートに含まれる与信実行国を参照して、与信実行国の数に応じた数のレコードを前記コントロールカード記憶部に登録する、請求項1の与信事務管理システム。 - 貸出実行がなされる地域ごとに遵守すべき項目を格納する地域規制記憶部をさらに備え、
前記コントロールカード作成部は、前記貸出条件パートに含まれる与信実行国に基づいて前記地域規制記憶部を検索して、前記複数の行内規程項目に含まれる地域規制項目を設定する、請求項1または2の与信事務管理システム。 - 稟議書コードに関連付けて、稟議書を構成する情報を含む複数のパートを格納する稟議書記憶部と
役割を含む担当者情報を格納する担当者記憶部と
をさらに備え、
前記与信事務管理システムは、前記担当者記憶部の前記役割に応じて、前記複数のパートの一部または全部を選択して提供する、請求項1乃至3のいずれかに記載の与信事務管理システム。 - 稟議書の貸出条件に基づいて設定されるチェック項目を格納する契約条件チェック記憶部と、
前記貸出条件パートに基づいて、前記契約条件チェック記憶部にレコードを登録する契約条件設定部と
をさらに備え
前記与信事務管理システムは、前記契約条件チェック記憶部において設定された、決裁済稟議書と契約書の整合性を確認するためのすべてのチェック項目の整合性が確認されると、前記コントロールカード記憶部の契約書チェックに関する行内規程項目に完了を示す値を格納する、請求項1乃至4のいずれかに記載の与信事務管理システム。 - 稟議書の貸出条件に含まれる担保・保証の充足情報を格納する担保・保証チェック記憶部と、
前記貸出条件パートに基づいて、前記担保・保証チェック記憶部にレコードを登録する担保・保証設定部と
をさらに備え、
前記与信事務管理システムは、前記担保・保証チェック記憶部において所定期間に充足期限が設定されたすべての担保・保証の充足が確認されると、前記コントロールカード記憶部の当該所定期間の担保・保証に関する行内規程項目に完了を示す値を格納する、請求項1乃至5のいずれかに記載の与信事務管理システム。 - 徴求書類の情報を格納するドキュメントチェック記憶部と、
徴求書類の情報を含むドキュメントリストアップデータに基づいて、前記ドキュメントチェック記憶部にレコードを登録するドキュメント設定部と
をさらに備え、
前記与信事務管理システムは、前記ドキュメントチェック記憶部において所定期間に入手期限が設定されたすべてのドキュメントの存在が確認されると、前記コントロールカード記憶部の当該所定期間のドキュメントに関する行内規程項目に完了を示す値を格納する、請求項1乃至6のいずれかに記載の与信事務管理システム。 - 特定の商品においてチェックすべき項目の情報を格納する商品別チェック記憶部と、
前記貸出条件パートに基づいて、前記商品別チェック記憶部にレコードを登録する商品別設定部と
をさらに備え、
前記与信事務管理システムは、前記商品別チェック記憶部において設定されたすべての項目のチェックが確認されると、前記コントロールカード記憶部の商品別に関する行内規定項目に完了を示す値を格納する、請求項1乃至7のいずれかに記載の与信事務管理システム。 - コントロールカードコードに関連付けて稟議書コード、署名予定日、与信実行予定日、ステータス、および所定期間ごとに複数の行内規程項目のチェック完了フラグを格納するコントロールカード記憶部を備えた与信事務管理システムにおいて、
前記与信事務管理システムのコントロールカード作成部が、稟議書コード、条件付きで稟議書が決裁される場合の条件、および充足期限を含む稟議条件パート、および貸出に必要な条件を含む貸出条件パートを受信するステップと、
前記コントロールカード作成部が、前記受信した情報に基づいて、前記コントロールカード記憶部にレコードを登録するステップであって、前記稟議条件パートおよび前記貸出条件パートに基づいて、前記複数の行内規程項目のうち、チェックすべき項目に未完了を示す値を格納する、ステップと
を実行する、方法。 - 前記コントロールカード記憶部は、貸付コードおよび与信実行国をさらに格納し、
前記登録するステップは、前記貸出条件パートに含まれる与信実行国を参照するステップを含み、与信実行国の数に応じた数のレコードを前記コントロールカード記憶部に登録する、請求項9の方法。 - 前記与信事務管理システムは、貸出実行がなされる地域ごとに遵守すべき項目を格納する地域規制記憶部をさらに備え、
前記登録するステップは、前記貸出条件パートに含まれる与信実行国に基づいて前記地域規制記憶部を検索するステップと、前記複数の行内規程項目に含まれる地域規制項目を設定するステップとをさらに含む、請求項9または10の方法。 - 前記与信事務管理システムは、
稟議書コードに関連付けて、稟議書を構成する情報を含む複数のパートを格納する稟議書記憶部と
役割を含む担当者情報を格納する担当者記憶部と
をさらに備え、
前記与信事務管理システムが、前記担当者記憶部の前記役割に応じて、前記複数のパートの一部または全部を選択して提供するステップをさらに実行する、請求項9乃至11のいずれかに記載の方法。 - 前記与信事務管理システムは、稟議書の貸出条件に基づいて設定されるチェック項目を格納する契約条件チェック記憶部をさらに備え、
前記与信事務管理システムの契約条件設定部が、前記貸出条件パートに基づいて、前記契約条件チェック記憶部にレコードを登録するステップと、
前記契約条件チェック記憶部において設定された、決裁済稟議書と契約書の整合性を確認するためのすべてのチェック項目の整合性が確認されると、前記与信事務管理システムが、前記コントロールカード記憶部の契約書チェックに関する行内規程項目に完了を示す値を格納するステップと
をさらに実行する、請求項9乃至12のいずれかに記載の方法。 - 前記与信事務管理システムは、稟議書の貸出条件に含まれる担保・保証の充足情報を格納する担保・保証チェック記憶部をさらに備え、
前記与信事務管理システムの担保・保証設定部が、前記貸出条件パートに基づいて、前記担保・保証チェック記憶部にレコードを登録するステップと、
前記担保・保証チェック記憶部において所定期間に充足期限が設定されたすべての担保・保証の充足が確認されると、前記与信事務管理システムが、前記コントロールカード記憶部の当該所定期間の担保・保証に関する行内規程項目に完了を示す値を格納するステップと
をさらに実行する、請求項9乃至13のいずれかに記載の方法。 - 前記与信事務管理システムは、徴求書類の情報を格納するドキュメントチェック記憶部をさらに備え、
前記与信事務管理システムのドキュメント設定部が、徴求書類の情報を含むドキュメントリストアップデータに基づいて、前記ドキュメントチェック記憶部にレコードを登録するステップと、
前記ドキュメントチェック記憶部において所定期間に入手期限が設定されたすべてのドキュメントの存在が確認されると、前記与信事務管理システムが、前記コントロールカード記憶部の当該所定期間のドキュメントに関する行内規程項目に完了を示す値を格納するステップと
をさらに実行する、請求項9乃至14のいずれかに記載の方法。 - 前記与信事務管理システムは、特定の商品においてチェックすべき項目の情報を格納する商品別チェック記憶部をさらに備え、
前記与信事務管理システムの商品別設定部が、前記貸出条件パートに基づいて、前記商品別チェック記憶部にレコードを登録するステップと、
前記ドキュメントチェック記憶部において設定されたすべての項目のチェックが確認されると、前記与信事務管理システムが、前記コントロールカード記憶部の商品別に関する行内規定項目に完了を示す値を格納するステップと
をさらに実行する、請求項9乃至15のいずれかに記載の方法。
Priority Applications (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201580078640.7A CN107430746B (zh) | 2015-03-31 | 2015-03-31 | 信贷事务管理系统及其方法 |
PCT/JP2015/001866 WO2016157252A1 (ja) | 2015-03-31 | 2015-03-31 | 与信事務管理システムおよびその方法 |
JP2016516113A JP5963998B1 (ja) | 2015-03-31 | 2015-03-31 | 与信事務管理システムおよびその方法 |
US15/563,244 US20180122003A1 (en) | 2015-03-31 | 2015-03-31 | Credit administration management system and method therefor |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/JP2015/001866 WO2016157252A1 (ja) | 2015-03-31 | 2015-03-31 | 与信事務管理システムおよびその方法 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2016157252A1 true WO2016157252A1 (ja) | 2016-10-06 |
Family
ID=56558021
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2015/001866 WO2016157252A1 (ja) | 2015-03-31 | 2015-03-31 | 与信事務管理システムおよびその方法 |
Country Status (4)
Country | Link |
---|---|
US (1) | US20180122003A1 (ja) |
JP (1) | JP5963998B1 (ja) |
CN (1) | CN107430746B (ja) |
WO (1) | WO2016157252A1 (ja) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP6356362B1 (ja) * | 2017-03-30 | 2018-07-11 | 株式会社三井住友銀行 | 銀行システムおよび銀行システムによって実行される方法 |
Families Citing this family (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN109146665A (zh) * | 2018-08-03 | 2019-01-04 | 中国电力财务有限公司 | 一种信息处理方法及装置 |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2002157422A (ja) * | 2000-11-20 | 2002-05-31 | Fujitsu Ltd | 与信方法および記録媒体 |
JP2003248754A (ja) * | 2002-02-22 | 2003-09-05 | Hachijuni Bank Ltd | 資産査定支援システム |
JP2003296572A (ja) * | 2002-03-29 | 2003-10-17 | Japan Research Institute Ltd | 融資支援システム、情報端末装置、融資支援方法およびその方法をコンピュータに実行させるプログラム |
US7742980B1 (en) * | 2002-11-15 | 2010-06-22 | Imx, Inc. | Automated loan approval system |
Family Cites Families (10)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6088686A (en) * | 1995-12-12 | 2000-07-11 | Citibank, N.A. | System and method to performing on-line credit reviews and approvals |
US5933816A (en) * | 1996-10-31 | 1999-08-03 | Citicorp Development Center, Inc. | System and method for delivering financial services |
US8489498B1 (en) * | 2003-12-01 | 2013-07-16 | Fannie Mae | System and method for processing a loan |
US7636742B1 (en) * | 2004-04-01 | 2009-12-22 | Intuit Inc. | Automated data retrieval |
US10395264B2 (en) * | 2007-04-30 | 2019-08-27 | Visa U.S.A. Inc. | Payment account processing which conveys financial transaction data and non financial transaction data |
CN101923695A (zh) * | 2010-02-09 | 2010-12-22 | 苏州德融嘉信信用管理技术有限公司 | 基于熟人社会模式的融资服务方法 |
EP2710545A4 (en) * | 2011-05-18 | 2014-12-31 | Credibility Corp | SYSTEM AND METHODS FOR CREATING A FEEDBACK LOOP FOR CREDIT |
CN102903056A (zh) * | 2011-07-27 | 2013-01-30 | 刘金衢 | 一种基于电子商务平台的借贷担保方法及系统 |
US8996447B2 (en) * | 2012-05-22 | 2015-03-31 | Sap Se | Decision service manager |
CN103942718A (zh) * | 2014-04-14 | 2014-07-23 | 中国人民银行征信中心 | 企业信贷信息采集整合方法 |
-
2015
- 2015-03-31 WO PCT/JP2015/001866 patent/WO2016157252A1/ja active Application Filing
- 2015-03-31 CN CN201580078640.7A patent/CN107430746B/zh active Active
- 2015-03-31 JP JP2016516113A patent/JP5963998B1/ja active Active
- 2015-03-31 US US15/563,244 patent/US20180122003A1/en not_active Abandoned
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2002157422A (ja) * | 2000-11-20 | 2002-05-31 | Fujitsu Ltd | 与信方法および記録媒体 |
JP2003248754A (ja) * | 2002-02-22 | 2003-09-05 | Hachijuni Bank Ltd | 資産査定支援システム |
JP2003296572A (ja) * | 2002-03-29 | 2003-10-17 | Japan Research Institute Ltd | 融資支援システム、情報端末装置、融資支援方法およびその方法をコンピュータに実行させるプログラム |
US7742980B1 (en) * | 2002-11-15 | 2010-06-22 | Imx, Inc. | Automated loan approval system |
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 |
---|---|
US20180122003A1 (en) | 2018-05-03 |
CN107430746A (zh) | 2017-12-01 |
JPWO2016157252A1 (ja) | 2017-04-27 |
CN107430746B (zh) | 2022-03-18 |
JP5963998B1 (ja) | 2016-08-03 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US10372733B2 (en) | Systems and methods for secure storage of user information in a user profile | |
US20070067234A1 (en) | Mortgage loan system and method | |
US20160343072A1 (en) | Method and system for business customer on-boarding | |
JP6188655B2 (ja) | 情報管理システムおよびコンピュータプログラム | |
US20080183627A1 (en) | Filtered healthcare payment card linked to tax-advantaged accounts | |
WO2018063659A1 (en) | Systems and methods for generating customized reports based on operational stage rules | |
US9582785B2 (en) | Mindmap illustrator | |
US20140244346A1 (en) | Real estate transaction management platform | |
JP5963998B1 (ja) | 与信事務管理システムおよびその方法 | |
US20180197240A1 (en) | Banking system, method and computer-readable storage medium for credit management for structured finance | |
US8832120B2 (en) | Methods and systems for analyzing weirdness of variables | |
US20190392018A1 (en) | Displaying Data Using Enhanced Functionality | |
US20160307161A1 (en) | Benefits enrollment server system and method | |
US20180197160A1 (en) | Dashboard patient self service product enhancement | |
JP2009070028A (ja) | 投資契約支援装置、投資契約支援プログラム | |
JP6750080B1 (ja) | 運用支援装置及び運用支援プログラム | |
JP6898384B2 (ja) | 保険契約管理システム、保険契約管理方法、及びプログラム | |
JP6670780B2 (ja) | 取引先名称確認装置、取引先名称確認方法及びプログラム | |
JP5646097B1 (ja) | 情報管理システムおよび情報管理方法 | |
Tuncer et al. | Bridging pre-trade and post-trade processes with the Legal Entity Identifier for a more efficient trade and client life-cycle management | |
WO2023137289A2 (en) | Digital consolidation | |
CA3139311A1 (en) | System and method for ledger analytics and application of digital tax stamps | |
Abdullah et al. | Data Mining Driven Rule Based Expert System for Medical Billing Compliance: A Case Study | |
National Research Council | Social security administration electronic service provision: a strategic assessment | |
Guyton et al. | Transforming the revenue cycle: tighter accountability, reduced variability, better information management, and more comprehensive integration will fuel the transformation |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
ENP | Entry into the national phase |
Ref document number: 2016516113 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: 15887409 Country of ref document: EP Kind code of ref document: A1 |
|
WWE | Wipo information: entry into national phase |
Ref document number: 15563244 Country of ref document: US |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 15887409 Country of ref document: EP Kind code of ref document: A1 |