JP6722735B2 - Fund transfer/transfer method through scraping, its system and computer program - Google Patents

Description

Embodiments of the present invention relate to a fund transfer/transfer system and method through scraping, and a computer program for the same, and more particularly, to a user's own transfer through scraping without directly accessing a financial institution. Funds can be transferred (transfers) from one account to another, and the transfer and transfer results and results can be managed in cooperation with an enterprise resource planning (ERP) system. The present invention relates to a technology for providing a transfer/transfer service.

In the conventional asset management method used for household household management and corporate accounting management, a method is mainly used in which the customer directly registers the status of the asset and tracks and records the change history. In the conventional method, the user directly confirms the necessary information among the information provided by the financial institution by directly accessing the service web page of the financial institution such as a bank by using his/her ID and password or an electronic certificate. There must be.

Recently, screen scraping collects only necessary information from information displayed on a screen after a client device or a server device accesses a financial institution even if a user does not directly access a web page of the financial institution. Technology has appeared. As an example, Patent Document 1 discloses a deposit management technique without passbook using screen scraping.

However, the scraping technology to date has been utilized only to call the deposit and withdrawal history from internet banking websites such as banks, and the transfer (transfer) of funds and accounting management through the scraping technology are still in full swing. It is a situation that is not utilized. In particular, in corporate accounting, there are many operations in which funds are repeatedly transferred (transferred) to deposit accounts of a limited number of customers. However, in the past, there has been no scraping-based service that reflects these repetitive tasks and facilitates accounting management of companies.

Korean Patent Registration No. 10-0468098

According to one aspect of the present invention, even if a user does not directly access a financial institution, the user can transfer funds from his or her own account to another account through scraping, and transfer (transfer) It is an object of the present invention to provide a fund transfer/transfer system and method through scraping capable of managing execution and result in cooperation with an enterprise resource planning (ERP) system, and a computer program therefor.

A fund transfer/transfer system through scraping according to an aspect of the present invention includes account information from a user, authentication information for transferring (transferring) funds, and transfer (transfer) information including a transfer (transfer) amount. A receiving unit configured to receive; accessing a financial server by a scraping method using the received authentication information, and performing a money transfer (transfer) corresponding to the transfer (transfer) information and the account information; A scraping unit configured to make a request to the server; and a reporting unit that receives transfer (transfer) result information and provides it to the user after the transfer of funds (transfer) by the financial server.

In one embodiment, the scraping unit receives an additional authentication request from the financial server in the process of requesting a transfer of funds to the financial server, and receives additional authentication information from the user as a response to the request. An authentication unit for transmitting to the financial server is further included.

In one embodiment, the authentication unit transmits a two-dimensional code configured to allow the user device to read the authentication code to the user device, and the user device performs authentication corresponding to the two-dimensional code. It is further configured to receive a code as the additional authentication information.

In one embodiment, the account information includes fee-bearing information, the scraping unit determines whether to bear the user's fee using the fee-bearing information, and based on the determined whether or not to bear the fee. It is further configured to selectively request the financial server to pay the user's fees.
In one embodiment, the reporting unit includes a database that stores accumulated transfer results.

In addition, a fund transfer/transfer system through scraping according to another aspect of the present invention analyzes a transfer (transfer) result stored in the database, and transfers a transfer corresponding to a plurality of overlapping transfer (transfer) results. The method further includes an analysis unit configured to generate a regular remittance schedule that defines one or more of a (transfer) date, a transfer (transfer) target account, and a transfer (transfer) amount.

In one embodiment, the analysis unit is configured to generate the scheduled remittance schedule further using accounting information received from an enterprise resource planning system communicating with the fund transfer/transfer system through scraping.

In one embodiment, the reporting unit processes the transfer (transfer) result information into a data format that can be read by an enterprise resource planning system that communicates with the fund transfer/transfer system through scraping, and then the enterprise resource management system. Is further configured to output to.

In addition, a fund transfer/transfer method through scraping according to another aspect of the present invention is such that a fund transfer/transfer system stores account information from a user, authentication information for transferring (transferring) funds, and a transfer (transfer) amount. Receiving the transfer (transfer) information including; a step in which the fund transfer/transfer system accesses the financial server by a scraping method using the received authentication information; the fund transfer/transfer system performs the transfer (transfer) ) Requesting a transfer (transfer) of funds corresponding to the information and the account information to the financial server; after the transfer of funds (transfer) is performed by the financial server, the transfer/transfer system transfers (transfer) Receiving result information from the financial server; and providing the transfer (transfer) result information to the user by the fund transfer/transfer system.

In one embodiment, the step of requesting the fund transfer (transfer) from the financial server includes the step of the fund transfer/transfer system receiving an additional authentication request from the financial server; Receiving additional authentication information from the user as a response to the request; and the fund transfer/transfer system transmitting the additional authentication information to the financial server.

In one embodiment, the step of receiving the additional authentication information includes transmitting a two-dimensional code to the user device, the two-dimensional code configured to allow the fund transfer/transfer system to read the authentication code using the user device. And a step in which the fund transfer/transfer system receives an authentication code corresponding to the two-dimensional code from the user device as the additional authentication information.

In one embodiment, the account information includes fee burden information, and the step of requesting the fund transfer (transfer) to the financial server is performed by the fund transfer/transfer system using the fee burden information to charge a user fee. Determining whether or not to bear the burden; and, when the fund transfer/transfer system determines that the user bears the fee in the step of determining whether or not to bear the fee, the payment of the user's fee to the financial server Including steps to request.

In one embodiment, the fund transfer/transfer system includes a database that stores accumulated transfer (transfer) results, and at this time, the fund transfer/transfer method through scraping is performed by the fund transfer/transfer system including the database. Analyze the transfer (transfer) result stored in, and select one of the transfer (transfer) date, the transfer (transfer) target account, and the transfer (transfer) amount according to the transfer (transfer) result that is duplicated multiple times. The method further includes generating a remittance schedule that defines one or more.

In one embodiment, the step of generating the regular remittance schedule further comprises using the accounting information received from an enterprise resource planning system in which the fund transfer/transfer system communicates with the fund transfer/transfer system through scraping. Includes generating a remittance schedule.

In one embodiment, the method for transferring and transferring funds through scraping is such that the transfer and transfer system transfers the transfer to a data format that can be read by an enterprise resource planning system that communicates with the transfer and transfer system through scraping. The method further includes the step of processing the transfer result information; and the step of the fund transfer/transfer system outputting the processed transfer (transfer) result information to the enterprise resource planning system.

Furthermore, a computer program according to another aspect of the present invention can be recorded in a computer-readable medium so as to perform the fund transfer/transfer method through scraping according to the above-described embodiments in combination with hardware. ..

According to a fund transfer/transfer system and method through scraping according to an aspect of the present invention, a user can transfer funds from his/her own account to another account through scraping without directly accessing a financial institution. ) Can be performed, and all the procedures involved in transfer (transfer) can be performed through the fund management program, such as setting the fee burden condition when transferring (transferring) funds and performing additional authentication. The efficiency of is improved.

Further, according to a fund transfer/transfer system and method through scraping according to another aspect of the present invention, through the transfer of the fund transfer/transfer system through scraping and the enterprise resource planning (ERP) system of the company, Generate a regular remittance schedule based on the accounting information of the company, allow the user to check the peculiar history such as accounts receivable before the transfer of funds (transfer), and execute the transfer (transfer) ERP There is an advantage that the execution and the result of the fund transfer (transfer) such as being reflected in the system can be operated in cooperation with the ERP system.

Block diagram schematically showing a fund transfer/transfer system through scraping according to an embodiment. A flowchart showing a procedure of a fund transfer/transfer method through scraping according to an embodiment. An exemplary screen view showing a user interface (User Interface; UI) displayed on a user device by a fund transfer/transfer method through scraping according to an embodiment. Another exemplary screen view showing a UI displayed on a user device by a fund transfer/transfer method through scraping according to an embodiment. Yet another exemplary screen view showing a UI displayed on a user device by a fund transfer/transfer method through scraping according to an embodiment. The flowchart which shows the procedure of the money transfer / transfer method through scraping which concerns on other embodiment. An exemplary screen view showing another UI displayed on the user device by the fund transfer/transfer method through scraping according to one embodiment.

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

FIG. 1 is a block diagram schematically showing a fund transfer/transfer system through scraping according to an embodiment.
Referring to FIG. 1, a fund transfer/transfer system 2 according to this embodiment is configured to be communicable with a user device 1 and a financial server 3 via a wired and/or wireless network. In one embodiment, the fund transfer/transfer system 2 is configured to be communicable with an enterprise resource planning (ERP) system 4 of a company via a wired and/or wireless network.

The communication method via a wired and/or wireless network may include all communication methods by which objects and objects can be networked, and may include wired communication, wireless communication, 3G, 4G, or other methods. It is not particularly limited. For example, a wired and/or wireless network may be a LAN (Local Area Network), a MAN (Metropolitan Area Network), a GSM (Global System for Mobile Network), an EDGE, a registered trademark (Enhanced GSM). (High Speed Downlink Packet Access), W-CDMA (Wideband Code Division Multiple Access), CDMA (Code Division Multi-Blues (registered trademark) Multiple Access) (TDMA(Time Multiple Access) (TDMA(Time Multiple Access)). Zigbee), Wi-Fi, VoIP (Voice over Internet Protocol), LTE Advanced, IEEE802.16m, WirelessMAN-Advanced, HSPA+, 3GPP Long TermEvertEvolE(LTE, EvolE), 3GPP Long Term EliteLeon Evol. UMB (former EV-DO Rev.C), Flash-OFDM, iBurst and MBWA (IEEE 802.20) systems, HIPERMAN, Beam-Division Multiply Multiple Access (BDMA), Wi-MAX Multiple Access (BDMA), Wi-MAX (Wi-MAX). A communication network according to one or more communication methods selected from the group consisting of sound wave-assisted communication can be referred to, but is not limited thereto.

The fund transfer/transfer system 2 includes a receiving unit 21, a scraping unit 22, and a reporting unit 23. In one embodiment, the fund transfer/transfer system 2 further includes an analysis unit 24. In addition, the scraping unit 22 may include a scraping engine 221 and an authentication unit 222. Further, the reporting unit 23 may include a database (DB) 230 in which the result of fund transfer (transfer) is stored.

The fund transfer/transfer system 2 according to the embodiment may have an aspect of being entirely hardware, or partially hardware and partially software. For example, each unit included in the fund transfer/transfer system 2 is referred to as hardware and software related thereto for processing data of a specific format and content or/and further transmitting and receiving by electronic communication. be able to. In the present specification, terms such as “unit”, “module”, “device”, “terminal”, “server”, or “system” refer to a combination of hardware and software driven by the hardware. Intended. For example, the hardware may be a data processing device that includes a CPU or other processor. The software driven by the hardware can also refer to a processor that is executing, an object, an executable file, a thread of execution, a program, and the like.

Further, the respective constituent elements of the fund transfer/transfer system 2 according to the present embodiment are not necessarily intended to refer to different devices that are physically separated from each other. That is, the receiving unit 21, the scraping unit 22, the reporting unit 23, the analyzing unit 24, and the like shown in FIG. 1 functionally configure the hardware configuring the fund transfer/transfer system 2 according to the operation performed by the hardware. It is only a division, and each section does not necessarily have to be provided independently of each other. Of course, depending on the embodiment, it may be realized by another device in which one or more of the receiving unit 21, the scraping unit 22, the reporting unit 23, and the analyzing unit 24 are physically separated from each other.

In one embodiment, the fund transfer/transfer system 2 is configured to perform the function of the application by communicating with the application executed on the user device 1. For example, the fund management program is installed in the user device 1, and the fund transfer/transfer system 2 receives a transfer (transfer) request from the fund management program of the user device 1, and in response to this, the fund transfer/transfer system 2 Transfer (transfer) can be performed by a server scraping method through communication with the financial server 3, and an execution result of the transfer (transfer) can be transmitted to the fund management program of the user device 1.

However, this is merely an example, and in another embodiment, the fund transfer/transfer system 2 itself can be realized in the form of a user device. In this case, the other user device 1 shown in FIG. 1 is unnecessary, and the user device in which the fund management program is installed corresponds to the fund transfer/transfer system 2. In addition, the fund transfer/transfer system 2 transfers (transfers) by a client scraping method via communication with the financial server 3 in response to a transfer (transfer) request input by a user, and transfers (transfers). The execution result of (1) can be received from the financial server 3 and output so that the user can view it.

In FIG. 1, the user device 1 is shown in the form of a notebook computer, but the form of the user device is not limited to this, and the user device may be a mobile communication terminal such as a smart phone or a personal computer ( It can also be realized in the form of an arbitrary computer device such as a personal computer, a PDA (Personal Digital Assistant), a tablet, a set-top box for Internet Protocol Television (IPTV), and the like.

The receiving unit 21 is configured to receive account information from a user, authentication information for transferring (transferring) funds, and transfer (transfer) information including a transfer (transfer) amount. For example, in the case of the server scraping method, the receiving unit 21 can receive the information from the user device 1. Alternatively, in the case of a client scraping method in which the fund transfer/transfer system 2 itself is realized in the form of a user device, the fund transfer/transfer system 2 directly receives account information, authentication information, transfer (transfer) information, etc. through input from a user. be able to.

The scraping unit 22 is configured to access the financial server 3 by a scraping method using the received authentication information and request the financial server to transfer money (transfer) corresponding to transfer (transfer) information and account information. To this end, the scraping unit 22 includes a scraping engine 221 for accessing the financial server 3 and extracting data, user authentication information (eg, ID, password, digital certificate, etc.) and processing for additional authentication. The authentication unit 222 for performing the above can be included.

The reporting unit 23 plays a role of receiving transfer (transfer) result information and providing it to the user after the transfer of funds (transfer) by the financial server 3. For example, in the case of the server scraping method, the reporting unit 23 can transmit the transfer (transfer) result information to the user device 1. Alternatively, in the case of the client scraping method in which the fund transfer/transfer system 2 itself is realized in the form of a user device, the reporting unit 23 outputs the transfer (transfer) result on the fund transfer/transfer system 2 so that the user can confirm the result. You can

In one embodiment, the transfer (transfer) execution result is accumulated in the DB 230 of the reporting unit 23. At this time, the analysis unit 24 can generate a regular remittance schedule based on the transfer (transfer) execution result accumulated in the DB 230, or can propose a schedule generation to the user. The regular remittance schedule defines one or more of the transfer (transfer) date, the transfer (transfer) target account, and the transfer (transfer) amount according to the transfer (transfer) results that overlap multiple times, and next time When transferring (transferring), it is to easily or automatically transfer (transfer) to the same account.

In one embodiment, the analysis unit 24 communicates with the ERP system 4 by the customer information corresponding to the target of fund transfer (transfer), and/or the payment history, the unpaid history, the collection history, and the unpaid money related to each customer. It is possible to receive accounting information including history and the like, generate a regular remittance schedule based on the received information, and request the user to confirm the unique history in the process of transferring (transferring). To this end, the ERP system 4 may include a human resource management unit 41 in which customer information and user information are stored, and an accounting information management unit 42 in which accounting information is stored.

In addition, in one embodiment, the ERP system 4 may include a report generation unit 43 that generates a fund management report for correlating the accounting information and the fund transfer (transfer) result. The money management report is generated based at least in part on the result of the money transfer (transfer) performed by the money transfer/transfer system 2. Therefore, the reporting unit 23 of the fund transfer/transfer system 2 can process the transfer (transfer) result information into a form (for example, a data format) that can be read by the ERP system 4 and transmit the processed result information to the ERP system 4.

FIG. 2 is a flowchart showing a procedure of a fund transfer/transfer method through scraping according to an embodiment. For convenience of description, a fund transfer/transfer method through scraping according to the present embodiment will be described with reference to FIGS. 1 and 2.

First, the user can register the information of the target account for transferring (transferring) the funds to the fund transfer/transfer system 2 (S11). For convenience of description, the user is described as the subject of the action in FIG. 2, but the operation of transmitting information to the fund transfer/transfer system 2 by the user is performed using the user device 1 as shown in FIG. A person skilled in the art can easily understand that this can be done. Alternatively, when the fund transfer/transfer system 2 itself is implemented in a user device provided with a fund management program, the user can directly input account information to the fund transfer/transfer system 2 via the user device 1. ..

FIG. 3 is an exemplary screen view showing a user interface (User Interface; UI) displayed on a user device according to a fund transfer/transfer method through scraping according to an embodiment, showing a process of registering a user's account. Show.

As shown in FIG. 3, the user can input the input account number and the transaction category (purchase or sales) related to it, the supplier name, the contact information, etc. as the account number. Also, the account information can include fee sharing information. The fee-bearing information is payee information about whether the user of the user (ie, our company) or the recipient of the fund (ie, the other party) will bear the fee information for the transfer (transfer) of funds. Therefore, when the transfer (transfer) is performed through scraping, the user may or may not bear the fee for the transfer (transfer) amount based on this information.

Referring again to FIG. 1 and FIG. 2, the user can input authentication information and transfer (transfer) information for transferring (transferring) funds to the fund transfer/transfer system 2 via the user device 1 (S12). .. The authentication information includes a user ID, a password, a digital certificate, a transfer (transfer) confirmation password, etc., which is required for the user to log in to the homepage of the internet banking of the financial server 3 using the fund transfer/transfer system 2. Can be included. Further, the transfer (transfer) information can include withdrawal account and transfer account information for transferring (transferring) funds, transfer (transfer) amount information, withdrawal passbook display information, and deposit passbook display information.

FIG. 4 is another exemplary screen view showing a UI displayed on a user device by a fund transfer/transfer method through scraping according to an embodiment, based on transfer (transfer) information input by a user. Display the withdrawal bank, withdrawal account, deposit bank, deposit account, payee name, transfer (transfer) amount, recipient of fees, etc., and enter the transfer (transfer) confirmation password by the user to transfer (transfer) 5 shows a UI screen for requesting execution.

Referring again to FIGS. 1 and 2, the fund transfer/transfer system 2 logs in to the financial server 3 based on the scraping technology using the authentication information (S13), and the login result indicating that the login is successful is sent from the financial server 3 to the login result. It can be received (S14). Next, the fund transfer/transfer system 2 requests the financial server 3 to execute the transfer (transfer) by transmitting the transfer (transfer) information input by the user to the financial server 3 based on the scraping technique (S15). ).

At this time, the amount actually paid by the user in connection with the transfer (transfer) can be determined based on the fee sharing information of the account information. That is, if the fee burden information of the target account information to be transferred (transferred) is confirmed and the fee bearer is the user's affiliated company, the amount of money input by the user (transfer) is transferred to the financial server 3. On the other hand, the user requests the financial server 3 to pay the fee to the financial institution, and conversely, when the recipient of the fee is the other party, only the transfer (transfer) of the transfer amount (transfer) entered by the user Can be requested to the financial server 3.

In one embodiment, the financial server 3 requests the user's additional authentication from the fund transfer/transfer system 2 before the transfer (transfer) other than the login process using the authentication information (S16). The additional authentication is for secondly authenticating whether or not a transfer (transfer) request is made by the user by a means different from the authentication information, such as authentication using biometric information such as a fingerprint, a mobile communication terminal of the user, or the like. Can be referred to as authentication using a device, a one-time password authentication using an OTP (One-Time Password) device, and an authentication number-based authentication using an automatic text message or an automatic answering telephone.

The fund transfer/transfer system 2 can receive input of additional authentication information from the user (S17) and transmit the received additional authentication information to the financial server 3 (S18). In the financial server 3, the additional authentication information is temporary information issued by the financial server 3 (for example, OTP or authentication number), or user information stored in the financial server 3 (for example, the birth date of the user). Whether the personal information, the biometric information, or the password set in advance by the user) is verified, and if it is verified, the requested fund transfer (transfer) can be performed (S19). ).

FIG. 5 is another exemplary screen view showing a UI displayed on a user device according to a fund transfer/transfer method through scraping according to an embodiment, in which additional authentication of a user uses a two-dimensional code. The form which is performed is shown.

Referring to FIG. 5, as a part of the additional authentication process, the financial server 3 can transmit the two-dimensional code 300 with a specific authentication code inserted therein to the fund transfer/transfer system, and the fund transfer/transfer system receives it. The two-dimensional code 300 can be displayed so that the user can see it, as shown in FIG. The two-dimensional code 300 is a type of OTP, and in order to read the OTP, a reader (that is, a reading program) to which a unique code of each user is added can be distributed to the user. For example, the reader may have a form of an application (so-called application) operated on a mobile communication terminal such as a smartphone of a user.

The user can restore the authentication code by reading the two-dimensional code on the screen of the user device or the fund transfer/transfer system using a reader. At this time, the unique code of the user is given to each reader, and the reader is configured to output different values depending on the given unique code even if the same two-dimensional code 300 is read. In the financial server, the user receives the value read by the user from the two-dimensional code 300 using his or her reader, and the value input by the user is used as the two-dimensional code 300 by using the unique code of the user stored in the financial server. It is possible to authenticate whether or not the user is the user himself based on whether or not the value matches the value obtained when the is read.

However, the additional authentication method described with reference to FIG. 5 is an example, and uses another additional authentication method that is publicly known or will be developed in the future for authenticating whether or not the user is the user. You can also

Referring again to FIG. 1 and FIG. 2, when the transfer (transfer) is performed after the additional authentication is successful, the financial server 3 transmits the result information to the fund transfer/transfer system 2 (S20), and transfers or transfers the fund. The system 2 can provide the transfer (transfer) result to the user device 1 (S21). The step of providing the transfer (transfer) result to the user (S21) may refer to transmitting the transfer (transfer) result information to the user device when the fund transfer/transfer system 2 performs server scraping, or the fund. When the transfer/transfer system 2 is implemented in the form of a user device to perform client scraping, it may be referred to as outputting the transfer (transfer) result on the fund transfer/transfer system 2 so that the user can see the result. it can.

Further, the fund transfer/transfer system 2 can process the transfer (transfer) result information into a form of data that can be read from the company ERP system 4 to which the user belongs and transmit the information to the ERP system 4 (S22). ). In the ERP system 4, the transfer (transfer) result information received from the fund transfer/transfer system 2 is reflected in the accounting information managed by the ERP system 4, or regularly or irregularly based on the transfer (transfer) result information. The transfer (transfer) result information can be used for purposes such as generating a large fund management report.
FIG. 6 is a flowchart showing a procedure of a fund transfer/transfer method through scraping according to another embodiment.

Referring to FIG. 6, in the present embodiment, the user requests fund transfer (transfer) to the fund transfer/transfer system 2 via the user device 1 (S31), and the fund transfer/transfer system 2 is connected to the financial server 3. Transfer (transfer) is performed by a scraping method through communication (S32). This is the same as the fund transfer (transfer) process of the embodiment described above with reference to FIG. 2, so detailed description will be omitted.

On the other hand, in the fund transfer/transfer system 2, the fund transfer (transfer) result information can be stored in the database of the fund transfer/transfer system 2 (S33). Further, the fund transfer/transfer system 2 can receive the accounting information from the ERP system 4 (S34). The accounting information can include payment history by supplier, unpaid history, collection history, uncollected history, and the like, which are recorded in the ERP system 4 in association with each customer of the company to which the user belongs. Like the transfer (transfer) result information, the received accounting information can be stored in the database of the fund transfer/transfer system 2, or not stored in the fund transfer/transfer system 2 and received from the ERP system 4 as necessary. You can also do it.

At this time, the fund transfer/transfer system 2 can generate a regular remittance schedule based on the transfer (transfer) result information accumulated in the database and/or the accounting information received from the ERP system 4 (S35). ). For example, when a transfer (transfer) result or accounting information causes a transfer (transfer) of funds to the same supplier on the same day or on an adjacent day each month, the fund transfer/transfer system 2 executes such a repeated transaction. A regular remittance schedule can be created for the processes that occur on a daily basis. Or, when the unpaid history related to a particular customer is confirmed from the accounting information, the fund transfer/transfer system 2 regularly transfers the fund transfer (transfer) process in which the unpaid history is paid to the customer according to the remittance schedule of the accounting information. It can also be generated on a schedule. Alternatively, the target account of the regular remittance schedule, the transfer (transfer) schedule, and the transfer (transfer) amount can be determined by other different methods.

In the fund transfer/transfer system 2, the regular remittance schedule automatically generated as described above is proposed to the user device 1 (S36), the user accepts the proposed schedule (S37), and the regular remittance schedule is set according to the schedule. It can be carried out. Of course, in addition to the automatic transfer by the fund transfer/transfer system 2, the user can directly input the target account information and transfer (transfer) information to generate the regular remittance schedule.

FIG. 7 is an exemplary screen view showing another UI displayed on a user device by a fund transfer/transfer method through scraping according to an embodiment, showing a UI screen for performing a regular remittance schedule. ..

As shown in FIG. 7, a list of suppliers, deposit account numbers, transfer (transfer) amounts, deposit passbook display history, withdrawal passbook display history, etc. corresponding to the regular remittance schedule is displayed to the user. In addition, for each regular remittance history, the content further specified by the user or automatically generated by the fund transfer/transfer system 2 based on the accounting information (for example, office rent, office administration fee, etc.) is further displayed to the user. You can also do it. The user can perform the bulk transfer (transfer) as it is by looking at the regular money transfer history list, or can perform the bulk transfer (transfer) after modifying some or all of the information as necessary. When performing transfer (transfer), the transfer (transfer) process, the additional authentication process, and the like are the same as the processes in the other embodiments described above.

In one embodiment, the fund transfer/transfer system 2 confirms the accounting information from the company ERP system 4 before performing the regular remittance (S38), and if the confirmed accounting information has a preset peculiar history, respond to this. A confirmation can be requested to the user (S39). The preset unique history is whether or not there is a fund transfer (transfer) that has been done after a long period of time after the remittance has not been performed for a fixed period of time among remittances, and mutual purchase is made for a certain period of time based on accounting information Whether or not there is a fund transfer (transfer) to a business partner for which no sales or sales have occurred, or whether there is an account receivable history of the business partner corresponding to the target account of the fund transfer (transfer) in the accounting information, etc. When the user confirms, the term refers to arbitrary information with the possibility of suspending or stopping the fund transfer (transfer).

For example, the fund transfer/transfer system 2 is a fund targeting a customer whose transfer (transfer) has not been performed for a long period of time as a peculiar history, or whose purchase or sales have not been issued for a long period of time. When the transfer (transfer) is going to be performed, the user device is set as a peculiar history with the content of inquiring whether the fund transfer (transfer) is omitted once or the fund transfer (transfer) is deleted from the periodic remittance history. 1 can be transmitted. As another example, the fund transfer/transfer system 2 uses the transfer (transfer) amount entered by the user when the receivable history of the customer corresponding to the account for the fund transfer (transfer) is confirmed from the accounting information. It is also possible to adjust the transfer (transfer) amount so as to transfer (transfer) the amount after deducting the unpaid amount, or to transmit to the user device 1 the content asking whether to cancel the transfer (transfer) as a peculiar history. ..

After the user confirms the unique history, the transfer (transfer) amount and whether or not the transfer (transfer) is performed are corrected, or the user performs the transfer (transfer) despite the existence of the unique history. When the command is given (S40), the fund transfer/transfer system 2 can perform the fund transfer (transfer) corresponding to the regular remittance through the financial server 3 according to the command of the user (S41). Further, the fund transfer/transfer system 2 can provide the transfer (transfer) result information to the user device 1 (S42), and process the transfer (transfer) result information into a data format that can be read by the ERP system 4. It can also be transmitted to the ERP system 4 (S43).

According to the fund transfer/transfer system and method through scraping according to the above embodiment, the user can transfer (transfer) funds from his/her own account to another account through scraping without directly accessing the financial institution. It is possible to set the fee burden condition when transferring (transferring) funds, and perform all the procedures involved in transfer (transfer) such as additional authentication through the fund management program, which improves the efficiency of work There is. Further, through the communication between the fund transfer/transfer system through scraping and the company ERP system according to the embodiment, a regular remittance schedule is generated based on the accounting information of the company, or the unpaid amount of the business partner before the transfer of funds (transfer). The advantage that the user can check the peculiar history such as money and reflect the execution result of the transfer (transfer) to the ERP system, and execute the transfer of the fund (transfer) and the result in cooperation with the ERP system. There is.

The operation of the fund transfer/transfer method through scraping according to the above-described embodiment is realized at least partially by a computer program and can be recorded in a computer-readable recording medium. A program for realizing an operation by the fund transfer/transfer method through scraping according to the embodiment is recorded, and a computer-readable recording medium is a recording device of all types in which data readable by the computer is recorded. Including. For example, computer-readable recording media include ROM, RAM, CD-ROM, magnetic tape, floppy disk, optical data storage device, and the like. Further, the computer-readable recording medium may be distributed to computer systems connected via a network, and the computer-readable code may be stored and executed in a distributed manner. Further, a functional program, a code, and a code segment for realizing the present embodiment can be easily understood by a person having ordinary skill in the art to which the present invention belongs.

Although the above description has been made with reference to the embodiments shown in the drawings, this is merely an example, and a person having ordinary skill in the art can use this for various modifications and other equivalent implementations. The form is possible. Such modifications are within the technical protection scope of the present invention. The technical protection scope of the present invention is defined by the technical idea of the appended claims.

1 User Device 4 ERP System 21 Receiving Section 24 Analyzing Section 22 Scraping Section 222 Authentication Section 221 Scraping Engine 23 Reporting Section 41 Human Resource Management Section 42 Accounting Information Management Section 43 Report Generation Section

Claims (11)

A receiving unit configured to receive account information, authentication information for transferring (transferring) funds, and transfer (transfer) information including a transfer (transfer) amount from a user;
Scraping configured to access the financial server by a scraping method using the received authentication information, and request the financial server to transfer money (transfer) corresponding to the transfer information and the account information. Part; and
A report unit including a database that receives the transfer (transfer) result information and provides it to the user after the fund transfer (transfer) by the financial server, and stores the accumulated transfer (transfer) result; and
The transfer (transfer) result stored in the database is analyzed, and the transfer (transfer) date, the transfer (transfer) target account, and the transfer (transfer) amount are calculated according to the transfer (transfer) result that is duplicated multiple times. Including an analysis unit that generates a remittance schedule that defines one or more,
The analysis unit is
Using the transfer information (transfer) stored in the database or the accounting information received from the enterprise resource planning system that communicates with the fund transfer/transfer system through scraping, the regular remittance schedule creates a preset unique history. Decide whether to include,
When the regular remittance schedule includes the peculiar history, it is configured to request the user to confirm the peculiar history,
As for the peculiar history, the transfer (transfer) has not been performed for a preset period or more, or the fund transfer (transfer) to a customer who has not made purchases or sales, or the receivable history is confirmed from the accounting information. Fund transfer/transfer system through scraping, which includes transfer (transfer) of funds to business partners . The scraping unit receives an additional authentication request from the financial server in the process of requesting a transfer of funds to the financial server, receives additional authentication information from a user as a response to the request, and transmits the additional authentication information to the financial server. The fund transfer/transfer system through scraping according to claim 1, further comprising an authenticating unit. The authentication unit transmits to the user device a two-dimensional code configured to read the authentication code using the user device, and the user device issues an authentication code corresponding to the two-dimensional code to the additional authentication. The money transfer/transfer system through scraping according to claim 2, further configured to be received as information. The account information includes fee burden information,
The scraping unit determines whether or not to bear the user's fee using the fee sharing information, and selectively requests the financial server to pay the user's fee based on the determined whether or not to bear the fee. The fund transfer/transfer system through scraping according to claim 1, further configured. The reporting unit processes the transfer (transfer) result information into a data format that can be read by an enterprise resource planning system that communicates with the fund transfer/transfer system through scraping and outputs the processed result information to the enterprise resource planning system. The fund transfer/transfer system through scraping according to claim 1, which is further configured. A step in which a fund transfer/transfer system receives account information, authentication information for transferring (transferring) funds, and transfer (transfer) information including a transfer (transfer) amount from a user;
The fund transfer/transfer system accesses the financial server by a scraping method using the received authentication information;
A step in which the fund transfer/transfer system requests the fund transfer (transfer) corresponding to the transfer information and the account information to the financial server;
The fund transfer/transfer system receives transfer (transfer) result information from the financial server after the fund transfer (transfer) is performed by the financial server; and
The fund transfer/transfer system includes a step of providing the transfer (transfer) result information to a user,
The fund transfer/transfer system includes a database that stores accumulated transfer (transfer) results,
The fund transfer/transfer system analyzes the transfer (transfer) results stored in the database, and in accordance with the transfer (transfer) results that are duplicated multiple times, the transfer (transfer) date, the transfer (transfer) target account, and Further comprising the step of generating a regular remittance schedule defining any one or more of the transfer (transfer) amounts,
The step of generating the regular remittance schedule comprises:
The regular remittance schedule using the transfer information (transfer) stored in the database or the accounting information received from the enterprise resource planning system that communicates with the fund transfer/transfer system through scraping. Determining whether includes a preset singular history; and
When the regular money transfer schedule includes the peculiar history, the fund transfer/transfer system includes a step of requesting the user to confirm the peculiar history,
As for the peculiar history, the transfer (transfer) has not been performed for a preset period or more, or the fund transfer (transfer) to a customer who has not made purchases or sales or the receivable history is confirmed from the accounting information. A method of transferring and transferring funds through scraping, which includes transfer (transfer) of funds to business partners . The step of requesting the transfer of funds (transfer) from the financial server includes:
The fund transfer/transfer system receives an additional authentication request from the financial server;
The funds transfer/transfer system receives additional authentication information from a user in response to the request; and
The fund transfer/transfer system includes a step of transmitting the additional authentication information to the financial server.
A fund transfer/transfer method through scraping according to claim 6 . The step of receiving the additional authentication information comprises:
Transmitting the two-dimensional code to the user device, wherein the fund transfer/transfer system is configured to read the authentication code using the user device; and
The funds transfer/transfer system includes a step of receiving an authentication code corresponding to the two-dimensional code from the user device as the additional authentication information.
A fund transfer/transfer method through scraping according to claim 7 . The account information includes fee burden information,
The step of requesting the transfer of funds (transfer) from the financial server includes:
The fund transfer/transfer system determines whether to bear the user's fee using the fee sharing information; and
And a step of requesting the financial server to pay the user's fee when the user determines that the user should bear the fee in the step of determining whether or not to bear the fee.
A fund transfer/transfer method through scraping according to claim 6 . Processing the transfer (transfer) result information in a data format that the fund transfer/transfer system can read by an enterprise resource planning system that communicates with the fund transfer/transfer system through scraping; and
The method further includes the step of the fund transfer/transfer system outputting the processed transfer (transfer) result information to the enterprise resource planning system.
A fund transfer/transfer method through scraping according to claim 6 . A computer program recorded on a computer-readable medium for performing the fund transfer/transfer method through scraping according to any one of claims 6 to 10 in combination with hardware.

Images