Account transfer management device, account transfer management method, and account transfer management program

Abstract

To automatically configure settings for account transfer by automatically identifying the presence of an account of the contractor in a financial institution from which money has been withdrawn within a past predetermined period, for an application for a contract, thereby eliminating the procedure of account transfer for an additional contract of the same contractor.SOLUTION: An account transfer management apparatus includes repeatable account determination means which is configured to: calculate, for an application for a contract, a reference year and month on the basis of a customer number and a financial institution code designated on a contract input screen; set a repeatable number of months of the designated financial institution code; acquire a contract number from contract basic information using the designated customer number as a key; refer to contract return statement information; determine the presence of a repeatable account when there is a record of "transferred" within the set repeatable number of months including the set reference year and month, for the contract number, in the designated financial institution code; and perform automatic settings for account transfer on the basis of the record of "transferred".SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present invention relates to an account transfer management device, an account transfer management method, and an account transfer management program. [Background technology]

[0002] For example, monthly credit card payments are often made using automatic debit, which is a system in which payments are automatically withdrawn from a designated account on a regular basis. A conventional system relating to automatic debit is disclosed in, for example, Patent Document 1. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Laid-Open No. 2002-32584 Summary of the Invention [Problem to be solved by the invention]

[0004] However, the above Patent Document 1 does not state anything about automatically determining whether, when a contract application is made, the same contract holder has an account at a financial institution from which payments have been withdrawn within a specified period of time in the past.

[0005] The present invention has been made in consideration of the above, and aims to provide an account transfer management device, an account transfer management method, and an account transfer management program that, when a contract application is made, automatically determines whether the same contract holder has an account at a financial institution from which withdrawals have been made within a specified period in the past, and automatically sets up account transfer, thereby making it possible to eliminate the need for account transfer procedures when an additional contract is made for the same contract holder. [Means for solving the problem]

[0006] In order to solve the above-mentioned problems and achieve the object, the present invention provides an account transfer management device equipped with a control unit and a memory unit, wherein the memory unit stores basic contract information including the customer number, contract number, contract holder name, financial institution code, branch code, account number, and depositor name, and contract repayment detail information including the contract number, repayment date and month, repayment amount, financial institution code, branch code, account number, depositor name, deduction amount, and deduction result indicating whether the transfer has been completed or the balance is insufficient, and the control unit is characterized in that when a contract application is made and the customer number and financial institution code are specified on the contract input screen, the control unit calculates the base date and month, sets the number of repeatable months for the specified financial institution code, obtains the contract number from the basic contract information using the specified customer number as a key, and refers to the contract repayment detail information, and if there is a record of ``transfer completed'' for the specified financial institution code for the contract number within the set number of repeatable months including the set base date and month, determines that there is a repeatable account, and automatically sets the account transfer based on the record of ``transfer completed.''

[0007] In addition, according to one aspect of the present invention, the memory unit further stores a withdrawal management master in which the withdrawal request year and month are registered, and the repeatable account determination means may calculate the reference year and month as the withdrawal request year and month registered in the withdrawal management master plus one month.

[0008] In addition, according to one aspect of the present invention, the memory unit further stores a repeat account judgment master in which a financial institution code, a repeat eligibility flag indicating whether or not the account is eligible for repeat, and the number of months for repeat judgment are registered in association with each other, and the repeat-eligible account judgment means may use the specified financial institution code as a key to obtain the repeat eligibility flag and the number of months for repeat judgment from the repeat account judgment master, and if the obtained repeat eligibility flag indicates that the account is eligible for repeat, set the obtained number of months for repeat judgment to the number of months for repeatability for the specified financial institution code.

[0009] In addition, according to one aspect of the present invention, the repeat account determination master includes a default record, and if the specified financial institution code does not exist in the repeat account master, the repeatable account determination means may obtain the repeat target eligibility flag and repeat determination month number of the default record.

[0010] Furthermore, according to one aspect of the present invention, the repeatable account determination means may display the fact that there is a repeatable account if there is a record of a "transfer completed" within the set repeatable number of months.

[0011] Furthermore, according to one aspect of the present invention, the contract input screen may include a repeat account application button that instructs the application of a repeat account, and when the repeat account application button is used to instruct the application of a repeat account, the repeatable account determination means may automatically set up an account transfer based on the record that has a history of ``transfer completed.''

[0012] In order to solve the above-mentioned problems and achieve the object, the present invention provides an account transfer management method executed by an information processing device having a control unit and a storage unit, wherein the storage unit stores basic contract information including a customer number, a contract number, a contractor's name, a financial institution code, a branch code, an account number, and a depositor's name, and contract repayment details information including a contract number, a repayment year and month, a repayment amount, a financial institution code, a branch code, an account number, a depositor's name, a withdrawal amount, and a withdrawal result indicating whether the transfer has been completed or the balance is insufficient, and the control unit executes the method by which, when a contract application is made, the customer number is input on a contract input screen. When a financial institution code is specified, the process calculates the base year and month, sets the number of repeatable months for the specified financial institution code, obtains the contract number from the basic contract information using the specified customer number as a key, refers to the contract repayment detail information, and if there is a record of ``transfer completed'' for the specified financial institution code for that contract number within the set number of repeatable months including the set base year and month, determines that there is a repeatable account, and automatically sets up account transfer based on the record of ``transfer completed''.

[0013] In order to solve the above-mentioned problems and achieve the object, the present invention provides an account transfer management program to be executed by an information processing device having a control unit and a storage unit, wherein the storage unit stores basic contract information including a customer number, a contract number, a contract holder's name, a financial institution code, a branch code, an account number, and a depositor's name, and contract repayment details information including a contract number, a repayment year and month, a repayment amount, a financial institution code, a branch code, an account number, a depositor's name, a withdrawal amount, and a withdrawal result indicating whether the transfer has been completed or the balance is insufficient, and the control unit, when a contract application is made, displays the customer number and financial institution code on a contract input screen. When specified, the program calculates the base year and month, sets the number of repeatable months for the specified financial institution code, obtains the contract number from the basic contract information using the specified customer number as a key, refers to the contract repayment detail information, and if there is a record of ``transfer completed'' for the specified financial institution code for that contract number within the set number of repeatable months including the set base year and month, determines that there is a repeatable account, and is characterized as an account transfer management program for executing a repeatable account determination process that automatically sets up account transfers based on the record of ``transfer completed''. [Effects of the Invention]

[0014] According to the present invention, when an application for a contract is made, it is automatically determined whether the same contract holder has an account at a financial institution from which payments have been withdrawn within a specified period in the past, and account transfer is automatically set up, thereby achieving the effect of making it possible to eliminate the need for account transfer procedures when an additional contract is made for the same contract holder. [Brief explanation of the drawings]

[0015] [Figure 1] FIG. 1 is a block diagram showing an example of the configuration of an account transfer management device according to this embodiment. [Figure 2] FIG. 2 is a diagram illustrating an example of the configuration of the withdrawal management master. [Figure 3] FIG. 3 is a diagram illustrating an example of the configuration of the repeat account determination master. [Figure 4]FIG. 4 is a diagram illustrating an example of the configuration of the bank master. [Figure 5] FIG. 5 is a diagram illustrating an example of the configuration of the bank branch master. [Figure 6] FIG. 6 is a diagram showing a flow for outlining the repeat-allowed account automatic determination process executed by the repeat-allowed account determination unit of the control unit of the account transfer management device in this embodiment. [Figure 7] FIG. 7 is a diagram showing sample data for explaining a specific example of the processing of the control unit of the account transfer management device in this embodiment. [Figure 8] FIG. 8 is a diagram showing sample data for explaining a specific example of the processing of the control unit of the account transfer management device in this embodiment. [Figure 9] FIG. 9 is a diagram showing sample data for explaining a specific example of the processing of the control unit of the account transfer management device in this embodiment. [Figure 10] FIG. 10 is a diagram showing sample data for explaining a specific example of the processing of the control unit of the account transfer management device in this embodiment. [Figure 11] FIG. 11 is a diagram showing sample data for explaining a specific example of the processing of the control unit of the account transfer management device in this embodiment. [Figure 12] FIG. 12 is a diagram showing sample data for explaining a specific example of the processing of the control unit of the account transfer management device in this embodiment. [Figure 13] FIG. 13 is a diagram showing sample data for explaining a specific example of the processing of the control unit of the account transfer management device in this embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0016] DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS An embodiment of the present invention will be described in detail with reference to the accompanying drawings. However, the present invention is not limited to the embodiment.

[0017] [1. Overview] Normally, if a financial institution has made a withdrawal from an account within a specified period (for example, 13 months), it is possible to request a transfer without having to go through the procedure again. An account that has made a withdrawal from an account within a specified period and that can be used for transfers without going through the procedure is called a "repeatable account."

[0018] However, because automatic determination of repeatable accounts generally requires the past 13 months of account transfer history, systems often do not retain that much history.As a result, even when adding a contract to the same customer, it was necessary to carry out the account transfer procedure each time using the account transfer request form received from the customer.

[0019] Normally, the procedure to set up a direct debit account takes about two weeks, but if there are any incomplete details or seals, it may take several months. This causes the time-consuming process of the direct debit procedure and the problem that the direct debit procedure will not be completed in time for the first payment date.

[0020] Therefore, in this embodiment, if the same customer has a bank account with a history of withdrawals within a specified period of time (for example, 13 months), the system automatically determines that there is a "repeatable account" and automatically sets up an account transfer for the bank account with a history of withdrawals.

[0021] This eliminates the need for account transfer procedures when additional contracts are made for the same contract holder, which has the benefit of reducing the risk of initial non-payment for credit companies, and also reduces the hassle of procedures for contract holders.In addition, as account transfer is the mainstream method of collecting payment for services in Japan, this can contribute to promoting the value of the solution to other industries.

[0022] That is, according to this embodiment, for example, credit companies do not need to carry out account transfer procedures. Also, since account transfer procedures are no longer necessary, collection by account deduction becomes possible from the first billing.

[0023] The account transfer management device of the present invention can be applied to all business types and industries that use account transfers for billing.

[0024] [2. Configuration] Fig. 1 is a block diagram showing an example of the configuration of an account transfer management device 100 according to this embodiment. In Fig. 1, the account transfer management device 100 comprises a control unit 102, a communication interface unit 104, a memory unit 106, and an input / output interface unit 108. The units comprised in the account transfer management device 100 are connected to each other so as to be able to communicate with each other via any communication path.

[0025] The communication interface unit 104 communicably connects the account transfer management device 100 to the network 300 via a communication device such as a router and a wired or wireless communication line such as a dedicated line. The communication interface unit 104 has a function of communicating data with other devices via the communication line. Here, the network 300 has a function of connecting the account transfer management device 100 and the server 200 so that they can communicate with each other, and is, for example, the Internet or a LAN (Local Area Network).

[0026] An input device 112 and an output device 114 are connected to the input / output interface unit 108. The output device 114 may be a monitor (including a home television), a speaker, or a printer. The input device 112 may be a keyboard, a mouse, a microphone, or a monitor that functions as a pointing device in cooperation with a mouse. Note that hereinafter, the output device 114 may be referred to as the monitor 114.

[0027] Various databases, tables, files, etc. are stored in the storage unit 106. Computer programs that work in conjunction with an OS (Operating System) to issue commands to a CPU (Central Processing Unit) to perform various processes are recorded in the storage unit 106. The storage unit 106 can be, for example, a memory device such as a RAM (Random Access Memory) or a ROM (Read Only Memory), a fixed disk device such as a hard disk, a flexible disk, an optical disk, etc.

[0028] The memory unit 106 includes a withdrawal management master 106a, a repeat account determination master 106b, a bank master 106c, a bank branch master 106d, and a data table 106e. Fig. 2 is a diagram showing an example of the configuration of the withdrawal management master 106a. Fig. 3 is a diagram showing an example of the configuration of the repeat account determination master 106b. Fig. 4 is a diagram showing an example of the configuration of the bank master 106c. Fig. 5 is a diagram showing an example of the configuration of the bank branch master 106d.

[0029] The debit management master 106a is a master for storing the debit request date, as shown in FIG.

[0030] As shown in Figure 3, the repeat account determination master 106b can be composed of a table that associates and registers the bank code (financial institution code), a repeat target flag indicating whether or not the account is eligible for repeat ('0: possible' if eligible, '1: not possible' if not eligible), and the number of months for repeat determination.

[0031] The bank master 106c can be configured as a table in which bank codes and bank names are registered in association with each other, as shown in FIG.

[0032] As shown in FIG. 5, the bank branch master 106d can be configured as a table in which bank codes, branch codes, and branch names are registered in association with each other.

[0033] The data table 106e is a table for storing data such as basic contract information and contract repayment details information.

[0034] The basic contract information may include contract information (customer number, contract number, contract holder name) and direct debit bank account (financial institution code, financial institution name, branch code, branch name, account number, depositor name).

[0035] The contract repayment details information may include contract information (contract number), repayment schedule (repayment year and month, repayment amount), and account transfer history (financial institution code, branch code, account number, depositor name, withdrawal amount, and withdrawal result).

[0036] The control unit 102 is a CPU or the like that performs overall control of the account transfer management device 100. The control unit 102 has an internal memory for storing control programs such as an OS, programs that define various processing procedures, required data, etc., and executes various information processing operations based on these stored programs.

[0037] The control unit 102 is configured to be able to access the withdrawal management master 106a, the repeat account determination master 106b, the bank master 106c, the bank branch master 106d, the data table 106e, and the like, which are stored in the memory unit 106. Note that the withdrawal management master 106a, the repeat account determination master 106b, the bank master 106c, the bank branch master 106d, and the data table 106e may be provided in another location (for example, the server 200), as long as they are accessible by the control unit 102.

[0038] The control unit 102 conceptually includes a contract input unit 102a, a repeatable account determination unit 102b, a master maintenance unit 102c, and a screen display control unit 102d.

[0039] When a contract application is made, the contract input unit 102a inputs basic contract information and contract repayment details information in response to, for example, an operator's operation on the contract input screen displayed on the monitor 114, and registers them in the data table 106e.

[0040] When a customer number and financial institution code are specified on the contract input screen, the repeatable account determination unit 102b calculates the base year and month, sets the number of months that can be repeated for the specified financial institution code, obtains the contract number from the basic contract information using the specified customer number as a key, refers to the contract repayment detail information, and if there is a record of ``transfer completed'' for the specified financial institution code for that contract number within the set number of months that can be repeated, including the set base year and month, it determines that there is an account that can be repeated, and automatically sets up account transfer based on the record with that ``transfer completed'' record.

[0041] The repeatable account determination unit 102b may calculate the reference date as the withdrawal request date registered in the withdrawal management master 106a plus one month.

[0042] In addition, the repeatable account determination unit 102b may use the specified financial institution code as a key to obtain a repeat target flag and the number of months for repeat determination from the repeat account determination master 106b, and if the obtained repeat target flag indicates that the account is a repeat target, set the obtained number of months for repeat determination to the number of months for repeatability for the specified financial institution code.

[0043] In addition, if the specified financial institution code does not exist in the repeat account determination master 106b, the repeat-enabled account determination unit 102b may obtain the repeat target flag and repeat determination months of the default record.

[0044] Furthermore, the repeatable account determination unit 102b may display the fact that there is a repeatable account if there is a record of "transfer completed" within the set repeatable number of months.

[0045] The contract input screen may be provided with a repeat account application button that instructs the application of a repeat account, and when the application of a repeat account is instructed using the repeat account application button, the repeatable account determination unit 102b may automatically set up account transfer based on records that have a history of ``transfer completed.''

[0046] The master maintenance section 102c is used to input, add, change, update, etc. data into the withdrawal management master 106a, repeat account judgment master 106b, bank master 106c, bank branch master 106d, and data table 106e in response to operator operations on a master maintenance screen (not shown).

[0047] The screen display control unit 102f controls the display of various screens (for example, a master maintenance screen or a contract input screen) displayed on the monitor 114 and the reception of inputs.

[0048] [3. Specific Examples] A specific example of the processing performed by the control unit 102 of the account transfer management apparatus 100 in this embodiment will be described with reference to FIGS.

[0049] (3-1. Automatic repeat account determination process) Figure 6 is a diagram showing a flow for outlining the repeat-allowed account automatic determination process executed by the repeat-allowed account determination unit 102b of the control unit 102 of the account transfer management apparatus 100 in this embodiment. The repeat-allowed account automatic determination process executed by the repeat-allowed account determination unit 102b will be described with reference to Figure 6.

[0050] When the customer number and financial institution code (bank code) are entered on the contract input screen, the repeatable account determination unit 102b executes the repeatable account determination process shown in FIG.

[0051] 6, the repeatable account determination unit 102b first calculates the base year and month (step S1). Specifically, the base year and month is calculated as the withdrawal request year and month in the withdrawal management master 106a plus one month.

[0052] The repeat-enabled account determination unit 102b determines the repeat-enabled financial institutions and the number of months for which repeats are permitted (step S2). Specifically, using the financial institution code as a key, it obtains the repeat target flag and the number of months for which repeats are permitted from the repeat account determination master 106b, and determines whether the target financial institution is a repeat-enabled account target and the number of months for which repeats are permitted.

[0053] If the account is eligible for repeat payment, the repeat-enabled account determination unit 102b determines whether or not the account is eligible for repeat payment (step S3). Specifically, the unit obtains the contract number from the basic contract information in the data table 106e using the specified customer number as a key, and refers to the contract repayment details information in the data table 106e. If the contract number has a record of "transfer completed" within the number of months eligible for repeat payment including the set base year and month, the unit determines that the account is eligible for repeat payment (the account with a record of "transfer completed" is identified as the repeat-enabled account).

[0054] The repeatable account determination unit 102b automatically sets the account of the direct debit bank (step S4). Specifically, if "repeatable account available", by selecting the "repeat account application button" on the contract input screen, the bank account for withdrawal of a separate contract is initially set (automatically set).

[0055] (3-2. Sample data) 7 to 13 are diagrams showing sample data for explaining a specific example of the processing by the control unit 102 of the account transfer management apparatus 100 in this embodiment. A specific example of the processing by the control unit 102 of the account transfer management apparatus 100 in this embodiment will be explained with reference to Figs. 7 to 13.

[0056] (Prerequisite data) It is assumed that data such as those shown in FIGS. 7(A) to 7(F) is registered in advance in the storage unit 106.

[0057] 7(A) is a diagram showing an example of basic contract information data. The basic contract information includes items such as contract information (customer number, contract number, contract holder name) and direct debit bank account (financial institution code, financial institution name, branch code, branch name, account number, depositor name).

[0058] In the example shown in the figure, the first line contains customer number "10," contract number "100," contract holder name "Yamada Taro," customer number "0089," financial institution code "0089," financial institution name "XX Bank," branch code "001," branch name "Honten," account number "1234567," and depositor name "Yamada Taro."

[0059] 7(B) is a diagram showing an example of contract repayment details information data. The contract repayment details information has the following fields: contract information (contract number), repayment schedule (repayment year and month, repayment amount), and account transfer history (financial institution code, branch code, account number, depositor name, withdrawal amount, and withdrawal result).

[0060] In the example shown in the figure, the first line contains the contract number "100," repayment date "2021 / 6," repayment amount "40,000," financial institution code "0089," branch code "001," account number "1234567," depositor name "Yamada Taro," withdrawal amount "40,000," and withdrawal result "0: Transferred."

[0061] 7(C) is a diagram showing an example of data in the debit management master 106a. The debit management master 106a registers the debit request year and month. In the example shown in the figure, the debit request year and month is "2022 / 9."

[0062] 7(D) is a diagram showing an example of data in the repeat account determination master 106b. The repeat account determination master 106b includes items such as a financial code (bank code), a repeat target flag indicating whether the account is eligible for repeat verification (for example, "0: possible" if eligible, "1: not possible" if not eligible), and the number of months for repeat verification.

[0063] The first line is the default record setting, with the bank code "9999", repeat target availability "0: possible", and the number of months for repeat determination "13". If the target bank code does not exist, the bank code "9999" will be set.

[0064] 7(E) is a diagram showing an example of data in the bank master 106c. The bank master 106c has fields for bank code and bank name. In the example shown in the figure, the third line contains the bank code "0089" and the bank name "XX Bank."

[0065] 7(F) is a diagram showing an example of data in the bank branch master data 106d. The bank branch master data 106d has fields for bank code, branch code, and branch name. In the example shown in the figure, the first line contains the bank code "0089," the branch code "001," and the branch name "Honten."

[0066] (Contract entry) Figure 8 is a diagram showing an example of the display of the contract input screen. The following explains the case where an application was made by Yamada Taro in XX month of 2022, and the necessary information is entered in the contract input. When the customer number and financial institution code are entered on the contract input screen, the repeatable account automatic determination process (automatic determination logic for repeatable accounts) is executed.

[0067] As shown in Figure 8, the contract input screen 400 has an area 401 for entering contractor information (customer number, contract number, contractor name, loan amount), an area 402 for entering direct debit bank account (financial institution code, financial institution name, branch code, branch name, account number, depositor name), an area 403 for entering repayment schedule (repayment year and month, repayment amount), a repeat account application button, a checkbox 404 for setting whether to apply a repeat account (checked: apply, unchecked: not apply), and a registration button 405.

[0068] In the example shown in FIG. 8, a case where the customer number "10" and the financial institution code "0089" are entered will be described.

[0069] (S1: Base year and month calculation) A specific example of calculating the base year and month will be explained with reference to Figure 9. Figure 9(A) shows an example of data from the debit management master 106a. The repeatable account determination unit 102b obtains the debit request year and month from the debit management master 106a and calculates the base year and month. Specifically, the base year and month is calculated as the debit request year and month in the debit management master 106a + 1 month. In this example, 2022 / 9 + 1 month = 2022 / 10. The "1 month" is fixed.

[0070] (S2: Determine repeatable financial institutions and number of months) A specific example of determining repeat-eligible financial institutions and the number of months will be described with reference to Figure 9. Figure 9(B) is a diagram showing an example of data in the repeat account determination master 106b. The repeat-eligible account determination unit 102b uses the financial institution code as a key to obtain the repeat eligible flag and the number of months for repeat determination from the repeat account determination master 106b, and determines whether the target financial institution is eligible for a repeat account and the number of months for repeat eligible accounts.

[0071] In this example, since the financial institution code "0089" does not exist in the repeat account determination master 106b, the default record of "9999" is adopted, and since the bank code "9999" has the repeat target eligibility "0: Possible" and the repeat determination number of months "13 months", it is determined to be a repeatable account and the repeatable number of months "13 months" is obtained.

[0072] If the financial institution code is "0099", the third row of the repeat account determination master 106b is used, so the number of months for repeat determination is "12 months".

[0073] (S3: Determine whether or not a repeat account is available) A specific example of determining whether or not a repeatable account exists will be described with reference to Fig. 10. Fig. 10(A) is a diagram showing an example of data for basic contract information, and Fig. 10(B) is a diagram showing an example of data for contract repayment details information.

[0074] The repeatable account determination unit 102b obtains the contract number from the basic contract information in data table 106e using the specified customer number as a key, and refers to the contract repayment details information in data table 106e for the specified financial institution code.If there is a record of ``0: Transferred'' for the contract number within the repeatable number of months including the set base year and month, it determines that there is a repeatable account and displays this on the contract input screen.

[0075] In the example of basic contract information in Figure 10(A), the contract number "100" of the same customer is obtained from the basic contract information using the customer number "10" as a key, and the contract repayment details information in Figure 10(B) is referenced. For contract number "100," since the specified financial institution code "0089" has an account transfer record of "Transferred" in "2021 / 11" after "2021 / 10," which is "13 months" before the repeat judgment number for the base year and month "2022 / 10," (record on line 6), it is determined that there is a "repeatable account," this record is obtained, and furthermore, "repeatable account exists" is displayed on the contract input screen (see Figure 11(B)).

[0076] In this example, there are two records (lines 5 and 6) from "2021 / 10" onwards, but whether or not there has been a withdrawal is determined by the "Withdrawal Result" (if it says "0: Transferred", it is a withdrawal). If multiple records apply, the record with the longest repayment date (i.e. the most recent) (line 6) is used.

[0077] (S4: Automatic setting of bank account for direct debit) A specific example of automatic setting of an account transfer bank account will be described with reference to Figures 11 to 13. Figure 11 is a diagram showing how the acquired contract repayment detail information record is set on the contract input screen. Figure 12 is a diagram showing an example of basic contract information data to be registered. Figure 13 is a diagram showing an example of contract repayment detail information data to be registered.

[0078] If "repeatable account available" is selected, the repeatable account determination unit 102b automatically sets (initializes) the bank account for withdrawals for a separate contract based on the record of the contract repayment details information acquired on the contract input screen.

[0079] Fig. 11(A) is a diagram showing an example of contract repayment detail information data. Fig. 11(B) is a diagram showing an example of a contract input screen display. Fig. 11(C) is a diagram showing an example of bank master data 106C, and Fig. 11(D) is a diagram showing an example of bank branch master data 106d.

[0080] On the contract input screen shown in Figure 11(B), as described above, if it is determined that there is a "repeatable account," "repeatable account available" is displayed. When "repeatable account available" is displayed, a check box 404 for setting whether or not to apply a repeatable account becomes checkable. When the check box 404 is checked, the direct debit bank account is automatically displayed (automatically set) based on past direct debit records.

[0081] Specifically, the name of the financial institution corresponding to the financial institution code of the record obtained from the contract repayment detail information shown in Figure 11(A) is obtained from the bank master 106c shown in Figure 11(C), and the branch name corresponding to the financial institution code and branch code of the obtained record is obtained from the bank branch master 106d shown in Figure 11(D). As shown in Figure 11(B), the direct debit bank account on the contract input screen displays the branch code, account number, and depositor name of the obtained record, the financial institution name obtained from the bank master 106c, and the branch name obtained from the bank branch master 106d. In this way, the direct debit bank account (financial institution, branch, account number, depositor name) is automatically set based on past direct debit records.

[0082] When the register button 405 is pressed, the contract input unit 102a registers (updates) in the data table 106e the basic contract information according to the input contents of the contractor information and direct debit bank account on the contract input screen, and the contract repayment details information according to the input contents of the repayment schedule. In the example shown in Figure 11(B), when the register button 405 is pressed, the basic contract information as shown in Figure 12 and the contract repayment details information as shown in Figure 13 are registered (updated).

[0083] In the example of basic contract information shown in Figure 12, the following data has been updated on the second line: Customer number "10", contract number "101", contract holder name "Yamada Taro", financial institution code "0089", financial institution name "XX Bank", branch code "001", branch name "Honten", account number "1234567", and depositor name "Yamada Taro". The contract number "101" is automatically assigned.

[0084] In the example of contract repayment details information shown in FIG. 13, data on the repayment date and repayment amount for contract number "101" has been updated on lines 7 to 12.

[0085] As explained above, according to this embodiment, when a contract application is made and the customer number and financial institution code are specified on the contract input screen, the base date is calculated, the number of repeatable months for the specified financial institution code is set, the contract number is obtained from the basic contract information using the specified customer number as a key, and the contract repayment detail information is referenced. If there is a record of "transfer completed" for the specified financial institution code for that contract number within the set number of repeatable months including the set base date, it is determined that a repeatable account exists, and based on the record with the "transfer completed" record, a repeatable account determination unit 102b is provided which automatically sets up account transfer.Therefore, when a contract application is made, it is automatically determined whether or not there is an account at a financial institution where the same contract holder has a history of debits within a specified period in the past, and account transfer is automatically set up, making it possible to eliminate the need for account transfer procedures when an additional contract is made for the same contract holder.

[0086] [4. Contribution to the United Nations-led Sustainable Development Goals (SDGs)] This embodiment can contribute to improving business efficiency and promoting appropriate management decisions by companies, thereby contributing to the achievement of SDGs Goals 8 and 9.

[0087] Furthermore, this embodiment can contribute to reducing waste and promoting paperless and electronic systems, thereby contributing to the achievement of SDGs Goals 12, 13, and 15.

[0088] Furthermore, this embodiment can contribute to strengthening control and governance, which can contribute to the achievement of Goal 16 of the SDGs.

[0089] 5. Other Embodiments The present invention may be implemented in various different embodiments other than those described above within the scope of the technical concept set forth in the claims.

[0090] For example, among the processes described in the embodiments, all or part of the processes described as being performed automatically can be performed manually, or all or part of the processes described as being performed manually can be performed automatically using known methods.

[0091] Furthermore, the processing procedures, control procedures, specific names, information including parameters such as registered data and search conditions for each process, screen examples, and database configurations shown in this specification and drawings can be changed as desired unless otherwise specified.

[0092] Furthermore, with regard to the account transfer management device 100, the components shown in the figures are functional concepts, and do not necessarily have to be physically configured as shown in the figures.

[0093] For example, all or any part of the processing functions of the account transfer management device 100, particularly the processing functions performed by the control unit, may be realized by a CPU and a program interpreted and executed by the CPU, or may be realized as hardware using wired logic. The program is recorded on a non-transitory computer-readable recording medium containing programmed instructions for causing the information processing device to execute the processes described in this embodiment, and is mechanically read by the account transfer management device 100 as needed. That is, a computer program for cooperating with the OS to issue instructions to the CPU and perform various processes is recorded in a storage unit such as a ROM or HDD (Hard Disk Drive). This computer program is executed by being loaded into RAM, and cooperates with the CPU to form the control unit.

[0094] In addition, this computer program may be stored in an application program server connected to the account transfer management device 100 via any network, and it is also possible to download all or part of it as needed.

[0095] Furthermore, the program for executing the processes described in this embodiment may be stored in a non-transitory computer-readable recording medium or configured as a program product. Here, the term "recording medium" includes any "portable physical medium" such as a memory card, a Universal Serial Bus (USB) memory, a Secure Digital (SD) card, a flexible disk, a magneto-optical disk, a ROM, an Erasable Programmable Read Only Memory (EPROM), an Electrically Erasable and Programmable Read Only Memory (EEPROM (registered trademark)), a Compact Disk Read Only Memory (CD-ROM), a Magneto-Optical disk (MO), a Digital Versatile Disk (DVD), and a Blu-ray (registered trademark) disc.

[0096] Furthermore, a "program" is a data processing method written in any language or description method, regardless of the format, such as source code or binary code. Note that a "program" is not necessarily limited to a single structure, but also includes a structure that is distributed as multiple modules or libraries, or a structure that achieves its function by cooperating with a separate program, such as an OS. Note that the specific configuration and reading procedure for reading a recording medium in each device shown in the embodiments, as well as the installation procedure after reading, can use well-known configurations and procedures.

[0097] The various databases stored in the memory unit are storage means such as memory devices such as RAM and ROM, fixed disk devices such as hard disks, flexible disks, and optical disks, and store various programs, tables, databases, and web page files used for various processes and providing websites.

[0098] The account transfer management device 100 may be configured as an information processing device such as a known personal computer or workstation, or may be configured as the information processing device to which any peripheral device is connected. The account transfer management device 100 may also be realized by installing software (including programs or data) that causes the device to realize the processing described in this embodiment.

[0099] Furthermore, the specific form of distribution and integration of the devices is not limited to that shown in the drawings, and all or part of them can be configured by functionally or physically distributing and integrating them in any unit depending on various additions or functional loads. In other words, the above-described embodiments can be implemented in any combination, or embodiments can be implemented selectively. [Explanation of symbols]

[0100] 100 Account transfer management device 102 Control section 102a Contract input section 102b Repeatable Account Judgment Section 102c Master Maintenance Department 102d Screen display control unit 104 Communication interface unit 106 Storage section 106a Withdrawal Management Master 106b Repeat Account Judgment Master 106c Bank Master 106d Bank branch master 106e Data Table 108 Input / Output Interface Section 112 Input Device 114 Output Device 300 Network

Claims

1. An account transfer management device that includes a control unit and sets up a transfer account for a new contract, The control unit Withdrawal management master in which the withdrawal request date is registered, A repeat account determination master that associates and registers the financial institution code, the repeat target flag indicating whether or not the account is a repeat target, and the number of months for repeat determination; Basic contract information including customer number, contract number, contract holder name, financial institution code, branch code, account number, and depositor name; Contract repayment details information including the contract number, repayment year and month, repayment amount, financial institution code, branch code, account number, depositor name, withdrawal amount, and withdrawal result indicating whether the transfer has been completed or the balance is insufficient; It is configured to be accessible to When a new contract is applied for and the customer number and financial institution code are specified on the contract input screen, the base year and month are calculated by adding one month to the debit request year and month registered in the debit management master, the repeat account eligibility flag and the number of months for repeat judgment are obtained from the repeat account judgment master using the specified financial institution code as a key, and if the obtained repeat eligibility flag indicates that the account is a repeat eligible account, the repeat judgment number is set as the number of months for repeatability for the specified financial institution code, the contract number is obtained from the basic contract information using the specified customer number as a key, and by referring to the contract repayment detail information, if there is a record of ``transfer completed'' for the specified financial institution code for the contract number since the year and month before the number of months for repeatability set in the calculated base year and month, the repeat eligible account is determined to exist, and a transfer account is set based on the financial institution code, branch code, account number, and depositor name of the record with a record of ``transfer completed'' in the contract repayment detail information.

2. The repeat account determination master includes a default record, The account transfer management device described in claim 1, characterized in that if the specified financial institution code does not exist in the repeat account determination master, the repeat eligible / indeterminate flag and the number of months for repeat determination of the default record are obtained.

3. The account transfer management device according to claim 1, characterized in that the repeatable account determination means displays that there is a repeatable account if there is a record of ``transfer completed'' within the set repeatable number of months.

4. An account transfer management method executed by an account transfer management device that includes a control unit and sets up a transfer account for a new contract, The control unit Withdrawal management master in which the withdrawal request date is registered, A repeat account determination master that associates and registers the financial institution code, the repeat target flag indicating whether or not the account is a repeat target, and the number of months for repeat determination; Basic contract information including customer number, contract number, contract holder name, financial institution code, branch code, account number, and depositor name; Contract repayment details information including the contract number, repayment year and month, repayment amount, financial institution code, branch code, account number, depositor name, withdrawal amount, and withdrawal result indicating whether the transfer has been completed or the balance is insufficient; It is configured to be accessible to The control unit executes a repeat-enabled account determination step of: when a new contract application is made and the customer number and financial institution code are specified on the contract input screen, calculating the base year and month by adding one month to the debit request year and month registered in the debit management master; obtaining a repeat target flag and the number of months for repeat determination from the repeat account determination master using the specified financial institution code as a key; if the obtained repeat target flag indicates that the account is a repeat target, setting the obtained number of months for repeat determination as the number of months for which repeat is possible for the specified financial institution code; obtaining a contract number from the basic contract information using the specified customer number as a key; referring to the contract repayment detail information, determining that a repeat-enabled account exists for the specified financial institution code if there is a record of ``transfer completed'' for the contract number since the year and month before the number of months for which repeat is possible that is set as the calculated base year and month; and setting up a transfer account based on the financial institution code, branch code, account number, and depositor name of the record with a ``transfer completed'' record in the contract repayment detail information.

5. An account transfer management program to be executed by an account transfer management device that includes a control unit and sets up a transfer account for a new contract, The control unit Withdrawal management master in which the withdrawal request date is registered, A repeat account determination master that associates and registers the financial institution code, the repeat target flag indicating whether or not the account is a repeat target, and the number of months for repeat determination; Basic contract information including customer number, contract number, contract holder name, financial institution code, branch code, account number, and depositor name; Contract repayment details information including the contract number, repayment year and month, repayment amount, financial institution code, branch code, account number, depositor name, withdrawal amount, and withdrawal result indicating whether the transfer has been completed or the balance is insufficient; It is configured to be accessible to The control unit and when a customer number and financial institution code are specified on the contract input screen when a new contract is applied for, the program calculates the base year and month by adding one month to the debit request year and month registered in the debit management master, obtains a repeat target flag and the number of months for repeat determination from the repeat account determination master using the specified financial institution code as a key, and if the obtained repeat target flag indicates that the account is a repeat target, sets the obtained number of months for repeat determination as the number of months for which repeat is possible for the specified financial institution code, obtains the contract number from the basic contract information using the specified customer number as a key, and refers to the contract repayment detail information, and if there is a record of ``transfer completed'' for the specified financial institution code for the contract number since the year and month before the number of months for which repeat is possible that is set as the calculated base year and month, determines that there is a repeatable account, and sets up a transfer account based on the financial institution code, branch code, account number, and depositor name of the record with a ``transfer completed'' record in the contract repayment detail information.

Images