Voucher processing support method, Voucher processing support system, and Voucher processing support device

Abstract

To improve the efficiency of work associated with bringing in a large number of slips by agents and to appropriately suppress various costs.SOLUTION: In a slip work support system 10 of the present invention, a slip work support device 100 holds authentication information and case information that associates registered information about an authenticated corporation with information about a slip transaction approved by an administrator of the corporation in a storage device, and distributes a code indicating the case information to a person-in-charge terminal 300; an ATM 500 transmits information indicated by the code displayed on a screen of the person-in-charge terminal 300 to the slip work support device 100; and the slip work support device 100 uses the information transmitted from the ATM 500 as a key to identify the case information from the storage device, and performs authentication by comparing authentication information input by a person in charge with the authentication information held in the storage device.SELECTED DRAWING: Figure 1

Description

[Technical field]

[0001] The present invention relates to a slip processing support method, a slip processing support system, and a slip processing support device. [Background technology]

[0002] In many cases, corporate clients who visit a bank branch are agents. The cases brought in by such corporate clients tend to be time-consuming and time-consuming, and are assumed to be handled at the counter. In addition, when a transaction is made by an agent, the counter must verify that the transaction has been approved by the corporate representative by comparing the power of attorney from the corporate representative with the company seal affixed to the transaction slip.

[0003] Regarding such transactions by persons other than the customer, there are conventional technologies that attempt to improve operational efficiency, security, etc. For example, a method and system for opening a temporary account (see Patent Document 1) has been proposed that allows customers to dispel their anxiety and reluctance about unauthorized use by notifying others of the account they normally use, and also allows the account to be opened through simple procedures.

[0004] This technology is characterized by the fact that when a customer inserts a cash card of a parent account set up at a financial institution into an ATM device, the card information is read, and the host computer verifies that the customer is a legitimate transactor by inputting authentication information.Furthermore, the necessary temporary account information, including information input by the customer regarding the period for which the temporary account is open, is stored in a customer information database, and then a temporary account card is issued as a cash card capable of transferring funds, automatically withdrawing funds, and making deposits and withdrawals.

[0005] In addition, when customers go through various procedures at financial institutions' counters, they are required to bring their personal seals and passbooks with them, and considering the risk of these being lost or stolen, traditional services are not necessarily secure. In addition, customers are required to select and fill out the documents required for various procedures themselves, which can lead to customers selecting the wrong documents or making incomplete entries. Technologies have also been proposed to solve these issues (see Patent Document 2).

[0006] This technology is a server computer that executes processing related to a transaction contract with a customer at a counter of a financial institution, and is configured to receive application content data, which is data related to the application content of the transaction contract, from a first computer, receive authentication data of the customer from the first computer or a second computer, and if there is no problem in the comparison result between the authentication data and pre-registered master data, create transaction contract data, which is data related to the execution content of the transaction contract, based on the application content data and the authentication data, and execute processing related to the transaction contract based on the transaction contract data.

[0007] Also, a technology has been proposed for realizing a store visit system that provides a counter clerk with store visitor information that identifies an individual store visitor in advance (see Patent Document 3).

[0008] This technology comprises an information processing device that holds a customer file in which personal data is registered, a visitor reception device that is connected to the information processing device via a communications network and has an input unit whereby customers input their account identifiers and a customer recognition unit that recognizes the customers' biometric characteristics, and a counter terminal that is installed at the customer counter and connected to the communications network, and is characterized in that the visitor reception device assigns reception numbers to customers in the order in which they are received, obtains the personal data from the information processing device based on the account identifier, identifies the customer based on the obtained personal data and the recognized biometric characteristics of the customer, and transmits visitor information of the identified customer together with the reception number to the counter terminal. [Prior art documents] [Patent documents]

[0009] [Patent Document 1] JP 2005-352526 A [Patent Document 2] JP 2017-211874 A [Patent Document 3] JP 2004-151862 A Summary of the Invention [Problem to be solved by the invention]

[0010] None of the conventional techniques can adequately handle the tasks involving the bringing in of a large number of transaction slips by agents of corporate clients. Therefore, the staff at the branch are overwhelmed with the task of processing such transaction slips, which places a heavy burden on them. The same is true for the authentication procedures performed by agents at the time of transactions, and the personnel and time costs associated with the task tend to remain high.

[0011] SUMMARY OF THE PRESENT DISCLOSURE An object of the present invention is to provide a technique for improving the efficiency of the operations associated with agents bringing in large volumes of slips and for appropriately reducing various costs. [Means for solving the problem]

[0012] In order to solve the above problems, the present invention links case information related to a slip transaction with a person in charge of the slip transaction. To this end, the present invention executes the slip transaction using authentication information such as temporary transaction information and a PIN number, and a code indicating case information.

[0013] A more specific configuration of the present invention is a method for supporting invoice processing using an invoice processing support device, which stores case information that links registration information related to an authenticated corporation with information related to invoice transactions approved by an administrator of the corporation in a storage device, and stores the case information or authentication information provided for each corporation. Temporary transaction information is used for limited authentication when executing the slip transaction, and is provided for each of the case information by input from a person in charge of the slip transaction.storing the above in the storage device, generating a code indicating the case information, and The person in charge the code displayed on the screen of the terminal used by the financial institution, and the code is read by a terminal device used at the financial institution's branch office, and the case information is identified from the storage device using the obtained information as a key; The specified case information is delivered to the terminal device, and a display is made to prompt the person in charge to input the temporary transaction information. In response to the display prompting the person in charge to input the temporary transaction information, The person in charge entered Temporary information for trading and stored in the storage device. Temporary information for trading If the authentication is successful, Based on the delivered case information, The method is a slip processing support method that enables slip transactions indicated by case information to be carried out.

[0014] The present invention also includes a slip processing support system for implementing the slip processing support method and a slip processing support device constituting the same. Effect of the Invention

[0015] According to the present invention, it is possible to improve the efficiency of a large volume of slip transaction work performed by an agent such as a person in charge, and to appropriately reduce various costs. [Brief description of the drawings]

[0016] [Figure 1] 1 is a diagram showing a network configuration including a slip processing support device according to an embodiment of the present invention; [Diagram 2] FIG. 2 is a diagram illustrating an example of a hardware configuration of the slip operation support device according to the present embodiment. [Diagram 3] FIG. 2 is a diagram illustrating an example of a configuration of a customer management DB according to the present embodiment. [Figure 4] FIG. 2 is a diagram illustrating an example of the configuration of a case management DB according to the present embodiment. [Diagram 5] FIG. 2 is a diagram showing an example of a flow of a slip processing support method according to the present embodiment. [Figure 6] FIG. 2 is a diagram showing an example of a flow of a slip processing support method according to the present embodiment. [Figure 7A] FIG. 2 is a diagram showing a first example of a flow of a method for supporting invoice operations when issuing invoices in this embodiment. [Figure 7B]FIG. 11 is a diagram showing a second example of a flow of the method for supporting invoice operations when issuing invoices in this embodiment. [Figure 8A] FIG. 2 is a diagram showing a first example of a flow of a method for supporting slip operations during slip transactions in this embodiment. [Figure 8B] FIG. 11 is a diagram showing a second example of a flow of the method for supporting slip operations during slip transactions in this embodiment. [Figure 8C] FIG. 13 is a diagram showing a third example of a flow of the method for supporting slip operations during slip transactions in this embodiment. [Figure 9] FIG. 4 is a diagram showing an example of a screen in the present embodiment. [Figure 10] FIG. 4 is a diagram showing an example of a screen in the present embodiment. [Figure 11] FIG. 4 is a diagram showing an example of a screen in the present embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0017] <Network configuration> An embodiment of the present invention will be described in detail below with reference to the drawings. Fig. 1 is a network configuration diagram including a slip operation support device 100 of this embodiment. The slip operation support device 100 shown in Fig. 1 is a computer that makes it possible to streamline operations associated with the delivery of a large number of slips by agents and appropriately reduce various costs.

[0018] As shown in Fig. 1, in this embodiment, slip process support device 100 is communicably connected via network 1 to manager terminal 200, staff terminal 300, teller terminal 400, ATM 500, and accounting system 600. Therefore, all of these devices or multiple devices including slip process support device 100 may be collectively referred to as slip process support system 10. Note that network 1 may be composed of multiple network systems in addition to the example shown in Fig. 1.

[0019] Invoice processing support device 100 of this embodiment can be said to be a service provider that appropriately handles invoice transactions that corporate customers wish to process and improves the efficiency of those transactions. Of course, it may be integrated with any of the devices included in invoice processing support system 10 described above. Invoice processing support device 100 can be realized by a computer (information processing device) such as a server.

[0020] The administrator terminal 200 is a terminal operated by the manager or the accounting department manager of the corporate client described above. Specifically, a smartphone, a tablet terminal, a personal computer, or the like can be envisioned.

[0021] The accounting department manager or the like will view, on this administrator terminal 200, the multiple invoice transactions that the corporation's staff are attempting to register, and decide whether or not to approve the registration (in the invoice processing support device 100).

[0022] Similarly, the person in charge terminal 300 is a terminal operated by a person in charge at the corporate client mentioned above. Specifically, it can be a smartphone, a tablet terminal, a personal computer, etc. Note that the person in charge terminal 300 used for the invoice issuing process (FIG. 6) and the invoice work support method (FIGS. 8A to 8C) may be different devices. In particular, it is desirable that the person in charge terminal 300 be a terminal used in a corporate office such as a PC for the invoice issuing process, and a portable terminal such as a smartphone or tablet for the invoice work support method.

[0023] The person in charge inputs information on invoice transactions that have occurred in relation to the business of the corporation into the person in charge terminal 300, and transmits the information as an approval request to the manager terminal 200 via invoice business support device 100.

[0024] The staff member terminal 300 acquires from the invoice processing support device 100 and stores the code 310 (e.g., a two-dimensional barcode) that the invoice processing support device 100 generates for each invoice transaction. This code 310 is displayed on the screen of the staff member terminal 300 or printed on an appropriate medium by the staff member's operation. The code 310 can be read by the teller terminal 400 or ATM 500 at the branch (not only those within the branch, but also ATMs 550 outside the branch), or by other specified devices (e.g., cash handling machines such as ticket vending machine 560, which is another example of a customer service terminal). There are also cases where a single code 310 is generated for multiple invoice transactions collectively.

[0025] It is also possible that the staff terminal 300 may consist of two separate terminals: one for the staff member to input the above-mentioned slip transaction information, and the other for acquiring, storing, and displaying the code 310 on a screen.

[0026] On the other hand, the teller terminal 400 is a terminal installed in a branch of a financial institution and is a terminal for a teller in charge of slip transactions. Also, the ATM 500 is an automated teller machine installed in a branch. Both the teller terminal 400 and the ATM 500 are equipped with a code reader such as a digital photographing device for reading the above-mentioned code 310.

[0027] The accounting system 600 is one of the core systems of the financial institution described above, and manages the account information of each customer and all financial transactions in the account. The basic configuration itself is the same as that of existing accounting systems.

[0028] However, accounting system 600 of this embodiment accepts an application to use the service from a user of the invoice processing support method provided by invoice processing support device 100, i.e., from the administrator's administrator terminal 200. In addition, in response to this application, accounting system 600 performs corporate authentication processing based on the account information of the corporate customer and its authentication information. These points are uniquely implemented by accounting system 600 of this embodiment.

[0029] <Hardware configuration> The hardware configuration of slip processing support device 100 of this embodiment is as shown in FIG.

[0030] That is, slip processing support device 100 comprises storage device 101 , memory 103 , arithmetic device 104 , and communication device 105 .

[0031] Of these, the storage device 101 is configured with an appropriate non-volatile storage element such as an SSD (Solid State Drive) or a hard disk drive.

[0032] The memory 103 is composed of a volatile storage element such as a RAM.

[0033] The arithmetic unit 104 is a CPU that reads out the program 102 stored in the storage unit 101 into the memory 103 and executes the program, controls the device itself, and performs various types of judgment, calculation, and control processing.

[0034] The communication device 105 is assumed to be a network interface card or the like that is connected to the network 1 and handles communication processing with the manager terminal 200 , the person in charge terminal 300 , the teller terminal 400 , the ATM 500 , and the accounting system 600 .

[0035] When slip processing support device 100 is a stand-alone machine, it is preferable that it further comprises an input device for accepting key input or voice input from the user, and an output device such as a display for displaying processing data.

[0036] Furthermore, in addition to program 102 for implementing the functions required for form processing support device 100 of this embodiment, at least a customer management database 125 and a case management database 126 are stored in storage device 101. Details of these databases will be described later. Case management database 126 may be implemented in an external device separate from form processing support device 100, and may be configured to be operated so that it can be accessed appropriately by form processing support device 100.

[0037] <Data structure example> Next, a description will be given of various types of information used by slip processing support device 100 of this embodiment. An example of customer management DB 125 in this embodiment is shown in FIG.

[0038] The customer management DB 125 of this embodiment is a database that stores information on each corporate customer. This customer management DB 125 is a collection of records that link data such as the customer account information, manager information, and person in charge information, using a customer ID that uniquely identifies the corporate customer as a key.

[0039] A personal identification number, which is a password issued for the corporate customer, may be set in customer management DB 125. This authentication pass may be a password required when using the invoice process support service provided by invoice process support device 100. This personal identification number may be used instead of the temporary transaction information used in Figs. 8A to 8C described later.

[0040] The account information includes the branch number, account title, account number, and PIN number of the account held by the corporate customer.

[0041] The manager information is information such as the attributes and contact information of managers, such as the president or the head of the accounting department of the corporate client.

[0042] The person in charge information is information such as the attributes and contact information of the person in charge (e.g., a person involved in accounting work within the corporation who may be entrusted with processing invoice transactions) approved in advance by the administrator of the corporate customer. The contact information may be an email address, a telephone number, etc.

[0043] Next, a description will be given of various types of information used by slip processing support device 100 of this embodiment. An example of case management DB 126 in this embodiment is shown in FIG.

[0044] The case management DB 126 of this embodiment is a database that stores various information related to slip transactions that occur at corporate clients.

[0045] This case management DB126 is a collection of records that link data such as customer ID, corporate authentication results, target invoice, transaction details, approved information, person in charge, identity verification information, login information, and temporary transaction information, using a case ID that uniquely identifies a case of invoice transaction work as a key.

[0046] Among these, the customer ID is identification information that uniquely identifies the corporate customer that requested the project.

[0047] The corporate authentication result is the authentication result obtained in the accounting system 600 for the corporate customer.

[0048] Furthermore, the target invoice is the invoice number of one or more invoices included in this case.

[0049] The transaction details are information about the details of the financial transaction in the above-mentioned target slip (e.g., transfer, transfer destination ***, transfer amount).

[0050] The approved information is information necessary for financial transactions, such as a personal identification number for a bank account held by a corporate client, and is necessary for the operation of slip transactions at the teller terminal 400 or ATM 500 .

[0051] The person in charge information is information such as the attributes and contact information of the person in charge (e.g., a person involved in accounting work within the corporation who may be entrusted with processing invoice transactions) approved in advance by the administrator of the corporation. The contact information may be an email address or a telephone number.

[0052] The personal identification information is authentication information obtained from the person in charge terminal 300 regarding the person in charge (of the corporation) who is to be in charge of the case. Such personal identification information may be, for example, biometric information such as the face, iris, and veins of the person in charge, or a separately determined password. Note that this personal identification information may be omitted.

[0053] In the case management DB 126, the identity verification information may be registered as follows. For example, the following process is performed when sensing the approach of a closing date such as the end of the month or in response to a request from the person in charge terminal 300. That is, the slip work support device 100 refers to the address of the person in charge in the "person in charge information" column of the record of the case registered in the case management DB 126, and delivers a request to register the identity verification information to the address. At this time, it is preferable to extract from the case management DB 126 one or more cases for which identity verification information has not been obtained by today, which is the closing date, and to make the above-mentioned registration request for these cases collectively. Next, the slip work support device 100 obtains identity verification information from the person in charge terminal 300 of the above-mentioned person in charge, and stores it in the "identification information" column of the corresponding record in the case management DB 126.

[0054] The login information is information used by a person in charge to log in to the invoice processing support system 10 for invoice transactions at a branch or for application for use. The login information can be realized, for example, by a combination of ID (Identification) and PW (Password), a personal identification number, or biometric information.

[0055] The temporary transaction information is information for temporarily linking information about the slip transaction (case information) with the person in charge or the person in charge information. The information about the slip transaction is preferably the target slip. The temporary transaction information is information used for limited authentication when executing a slip transaction, and can be realized by a character string or a symbol. This limited authentication means specialization to the slip transaction in question, and a time restriction such as an expiration date may be set. The temporary transaction information is set by input by the person in charge. Biometric information, like login information, may also be used. It is also preferable to record the validity period of the temporary transaction information in the case management DB 126.

[0056] In the example of case management DB 126 shown in FIG. 4, case ID "00001" indicates that two vouchers have been approved by the administrator and registered in case management DB 126. The person in charge who will actually visit the branch to handle the transactions for these vouchers has also been determined, and their identity verification information has also been registered. Furthermore, for the target voucher "D01001" for case ID "00001," the temporary transaction information has also been set to "1234" by the person in charge. However, the temporary transaction information for the target voucher "D01002" is "not set."

[0057] On the other hand, case ID "00002" indicates that each of the 30 slips has been approved by the administrator and registered in case management DB 126. In addition, the person in charge who will actually visit the branch for the transactions of these 30 slips has also been decided, and their identity verification information has also been registered. Furthermore, the temporary transaction information of the target slip "D02401" of case ID "00002" is "ABC". As described above, the temporary transaction information differs from that of the target slip "D01001" in the number of digits and character type. As described above, the temporary transaction information can be freely set by the person in charge. Furthermore, the temporary transaction information of the target slip "D02402" is "DFGH". As described above, the temporary transaction information can be freely set for each slip.

[0058] On the other hand, case ID "00003" indicates that only one slip has been approved by the administrator and has been registered in the case management DB 126. In addition, the person who will actually visit the branch for the transaction of this one slip has already been decided, but the person's identity verification information has not yet been registered.

[0059] In addition, in the case ID "00004", the invoice has not yet been registered or approved, and the authentication result for the corporate customer has simply been registered. In other words, this is the state in which subsequent processes such as the registration and approval of invoices, the selection of a person in charge, and the acquisition and registration of personal identification information will take place.

[0060] <Flow example: When applying for use> The actual steps of the method for supporting invoice processing in this embodiment will be described below with reference to the drawings. The various operations corresponding to the method for supporting invoice processing described below are realized by a program that is read into memory or the like and executed by invoice processing support device 100. This program is made up of code for carrying out the various operations described below.

[0061] 5 is a diagram showing an example of the flow of the slip processing support method in this embodiment. Here, it is assumed that the administrator of the corporate client mentioned above applies for use of the slip processing support service (provided by slip processing support device 100).

[0062] In this case, administrator terminal 200 operated by the administrator receives an application for use that includes information on the corporation's account, its authentication information (such as a personal identification number), and contact information for a person who may be in charge of invoice transactions (see FIG. 9). Then, administrator terminal 200 transmits this to invoice processing support device 100.

[0063] Invoice processing support device 100 receives the application for use sent by manager terminal 200 (s1).

[0064] In addition, slip processing support device 100 references the account information and its authentication information from the application for use obtained in s1, and transmits an authentication request based on this information to accounting system 600 (s2).

[0065] In response to the authentication request, accounting system 600 determines whether the set of account information and its authentication information matches the information held in account management DB 625 for the account held by the corporate customer, and executes authentication processing. Accounting system 600 returns the result of this authentication processing to slip operation support device 100.

[0066] On the other hand, if the authentication result in accounting system 600 indicates a successful authentication (s3: Y), invoice process support device 100 generates a customer ID for the above-mentioned corporate customer. Then, invoice process support device 100 registers this information together with the above-mentioned account information, authentication information, and contact information of the person in charge in customer management DB 125 (s4). On the other hand, if the above-mentioned authentication result indicates an authentication failure (s3: N), invoice process support device 100 ends this flow.

[0067] <Flow example: When creating a document> 6 is a diagram showing an example of a flow of the invoice processing support method in this embodiment. Here, assume a situation in which a person in charge of invoice transaction processing in the accounting department of the above-mentioned corporate client starts to collect a large number of invoices to be registered in the case management DB 126 and register them as a case.

[0068] In this case, the staff terminal 300 operated by the staff member described above accepts the multiple slip content information and temporary transaction information entered by the staff member (s5). As will be described later, a personal identification number can be used instead of the temporary transaction information. In this case, the acceptance of the temporary transaction information in s5 can be omitted. As described above, in this embodiment, the temporary transaction information and a personal identification number are used as examples of authentication information used to authenticate slip transactions. This authentication information is case information or information set for each corporation. The authentication information is not limited to these, and biometric information, etc. can also be used. In particular, for the personal identification number, information in various data formats other than numbers can also be used.

[0069] The staff member terminal 300 then transmits an approval request, including the invoice content information and temporary transaction information obtained in s5, to the invoice processing support device 100 (s6), and the process ends.

[0070] <Flow example: When creating a document> 7A and 7B are diagrams showing example flows of a method for supporting invoice processing when issuing invoices in this embodiment. First, FIG. 7A is a diagram showing a first example flow of a method for supporting invoice processing in this embodiment. Then, it is a flow for executing a first example flow (FIG. 8A) and a second example flow (FIG. 8B) during invoice transactions, which will be described later. First, FIG. 7B is a diagram showing a second example flow of a method for supporting invoice processing in this embodiment. Then, it is a flow for executing a third example flow (FIG. 8C) during invoice transactions, which will be described later.

[0071] In this example, it is assumed that invoice processing support device 100 and manager terminal 200 cooperate with each other in response to an approval request sent from person in charge terminal 300 as a result of the flow of Figure 6 described above. First, Figure 7A will be described below.

[0072] In this case, invoice processing support device 100 receives an approval request for multiple invoice transactions from the corporate customer's staff terminal 300, and transmits this to the manager's terminal 200 (s7). Note that invoice processing support device 100 transmits invoice content information to the manager's terminal 200, but it may or may not transmit temporary transaction information to the manager's terminal 200.

[0073] Meanwhile, the manager terminal 200 receives the above-mentioned approval request (s8) and displays it to the manager. The manager checks the information on multiple vouchers (see FIG. 10) that is the content of the approval request sent from the person in charge terminal 300 via the invoice processing support device 100, and judges whether or not to register it. The manager terminal 200 also accepts input of the manager's judgment result, i.e., approval or non-approval, and responds to the invoice processing support device 100 (s9). Note that when the approval or non-approval is input, a PIN number may be a condition. In particular, when a PIN number is used instead of the temporary transaction information in FIGS. 8A to 8C, it is preferable to accept the PIN number in s9. Furthermore, when a PIN number is used instead of the temporary transaction information in FIGS. 8A to 8C, the acceptance of the temporary transaction information in s5 can be omitted. Furthermore, in s8 or s9, the invoice processing support device 100 may create a code indicating the case information of the approval request target, and display this on the manager terminal 200.

[0074] When performing each of the above processes, administrator terminal 200 uses the customer ID and authentication pass issued for the corporate customer to access the invoice confirmation screen (see FIG. 10 above) provided by invoice process support device 100. In other words, invoice process support device 100 uses customer management DB 125 to control access through authentication processing for the corporate customer that is the operator of administrator terminal 200.

[0075] Next, slip processing support device 100 acquires the administrator's decision on whether or not to approve each slip transaction from administrator terminal 200 (s10).

[0076] If the above-mentioned judgment result indicates approval (s11: Y), the invoice work support device 100 links the information on the invoice transaction to be approved, the temporary transaction information, and the registration information, and stores them as case information in the case management DB 126 (s12). The information on the invoice transaction corresponds to information such as the invoice number and transaction details. The registration information corresponds to information such as the case ID generated by the invoice work support device 100 for this case, and account information (including PIN). Of these, the account information becomes "approved information."

[0077] Then, the slip work support device 100 codes the case information. That is, the slip work support device 100 creates a code indicating the case information (s13). More specifically, the slip work support device 100 codes the case information such as the case ID of the target case and the slip number of the target slip using a predetermined code generation application or the like. At this time, this code may be distributed to the staff terminal 300 described above. However, more preferably, it is distributed at the time of slip transaction as described later with reference to FIG. 8A and FIG. 8B. Also, at this time, cases to which the above-mentioned code has not been distributed by today, which is the closing date, may be extracted from the case management DB 126, and case information such as the case ID and slip number may be collectively coded. From the perspective of the staff who receives this code and performs the work, it is because one code can process slips of multiple cases collectively. Note that the order of s12 and s13 may be reversed, and s13 may be executed at the time of slip transaction described later. This concludes the explanation of FIG. 7A, and next, FIG. 7B will be explained.

[0078] In FIG. 7B, steps s7 to s12 are the same as those in FIG. 7A, and therefore their description will be omitted. Then, slip work support device 100 issues a code for the case information and / or notifies staff member terminal 300 of a URL (Uniform Resource Locator) for displaying the code. This notification can be realized, for example, by using SMS (Short Message Service) or email. The URL is a type of storage information that indicates the storage location of the case information in case management DB 126. Therefore, information other than a URL may be used as long as the case information can be specified. The notification destination can be specified using the case information or staff member information in management DB 126. The URL is a type of input information for displaying the code on staff member terminal 300. Furthermore, slip work support device 100 may be configured to notify at the time of a slip transaction, which will be described later.

[0079] <Flow example: When making a voucher transaction> Next, assume that a case registered in case management DB 126 is visited by a corporate client's staff member at a branch office to actually process the case. Figs. 8A to 8C are diagrams showing examples of flows for a method of supporting slip operations during slip transactions in this embodiment. These diagrams show different variations in the distribution and display of codes. Below, slip transaction processing will be explained using these diagrams.

[0080] First, FIG. 8A is a diagram showing a first example of a flow of the invoice work support method in this embodiment. This example shows a basic invoice work support method. First, when a person in charge visits a branch to carry out invoice transactions, he or she operates the person in charge terminal 300 that he or she has brought with him or her. Specifically, the person in charge inputs login information into the person in charge terminal 300. The person in charge terminal 300 accepts the login information from the person in charge. Then, the invoice work support device 100 receives the login information from the person in charge terminal 300, and performs authentication by comparing the login information with the login information in the case management DB 126 (s20).

[0081] Note that s20 may be executed on the person in charge terminal 300 side. In this case, a search request using the login information received by the person in charge terminal 300 as a key is sent to the invoice process support device 100. Then, invoice process support device 100 searches for the login information from the case management DB 126 and sends it to the person in charge terminal 300. As a result, s20 can be executed on the person in charge terminal 300. Note that in addition to the person in charge terminal 300, each process of this flow including the above-mentioned process may also be executed on the teller terminal 400, ATM 500, or ATM 550. Furthermore, the person in charge terminal 300, that is, the above-mentioned process, can be executed on various terminal devices used in the business branches of financial institutions.

[0082] If the authentication in s20 is successful (s21:Y), the invoice processing support device 100 distributes the code created in s13 (FIG. 7A) to the person in charge terminal 300 (s22). As a result, the person in charge terminal 300 displays the code. On the other hand, if the authentication is unsuccessful (s21:N), the process ends. Note that the code displayed in this process is preferably a two-dimensional code as shown in FIG. 11, but may be a code in another format. Note that in this embodiment, s22 is executed conditional on s21, but s22 may be executed independently of login.

[0083] Based on the code displayed on person in charge terminal 300, slip work support device 100 searches case management DB 126 to identify case information (s23). To do this, the person in charge first holds the code displayed on person in charge terminal 300 over the ATM 500. As a result, the ATM 500 reads the code displayed on the screen of person in charge terminal 300 to obtain the case information, and sends a search request to slip work support device 100 using the case ID and slip number indicated by the case information as keys. As a result, slip work support device 100 is able to perform a search based on the information read from the code received from ATM 500.

[0084] Then, slip process support device 100 distributes the specified case information to ATM 500 and causes it to execute a display prompting the input of temporary transaction information. In response, ATM 500 accepts input of temporary transaction information from the person in charge (s24). Then, ATM 500 transmits this to slip process support system 10.

[0085] Invoice process support device 100 performs authentication by comparing the transmitted temporary transaction information with the temporary transaction information included in the identified case information. Invoice process support device 100 then returns the authentication result to ATM 500 (s25). To perform this process, ATM 500 may directly access case management DB 126 and transmit the temporary transaction information. In this case, case management DB 126 may perform these processes instead of invoice process support device 100. For example, this processing may be performed when case management DB 126 is implemented as an external device separate from invoice process support device 100. When a personal identification number is used, the personal identification number received in s24 is compared with the personal identification number in customer management DB 125 to perform authentication.

[0086] If the authentication in s25 is successful (s26:Y), the ATM 500 cooperates with the slip processing support system 10 to carry out multiple corresponding slip transactions with the accounting system 600 and the like based on the above-mentioned case information (s27), and ends the process. On the other hand, if the authentication is unsuccessful (s26:N), the process ends. Note that when the slip processing support device 100 ends the slip transaction, it may delete the corresponding temporary transaction information from the case management DB 126.

[0087] In this embodiment, in addition to or instead of authentication using login information and authentication information, identity verification processing may be performed on the person in charge using identity verification information. This processing is preferably performed between s26 and s27, but may be performed at any other timing before s27. The details of the identity verification processing will be described below. The following identity verification processing will be described using a face image as an example.

[0088] Invoice processing support device 100 transmits the identity verification information (facial image) of the case information specified in s23 to teller terminal 400. In addition, a camera connected to teller terminal 400 captures an image of the face of the person in charge to obtain a facial image. Note that this camera is preferably installed in the branch, particularly ATM 500 or ATM 550.

[0089] Then, teller terminal 400 displays the facial image from receipt work support device 100 and the facial image captured by the camera. As a result, the teller compares these to confirm whether the visitor is the person in charge. Furthermore, teller terminal 400 accepts this result from the teller and determines whether identity verification was successful. If identity verification is successful, it allows the receipt transaction. If identity verification is unsuccessful, the process ends. Note that whether the visitor is the person in charge may be determined using image processing technology in devices such as teller terminal 400 or ATM 500. Furthermore, identity verification may be performed by the teller comparing the visitor's face with the facial image from receipt work support device 100 without using a camera installed in the branch.

[0090] Furthermore, in this flow, if authentication is successful, the distributed code is displayed (s21, s22). However, if authentication is successful, slip operation support device 100 may create a code or distribute the created code.

[0091] This concludes the explanation of Fig. 8A, and another example of the process flow during slip transactions will now be explained. Fig. 8B is a diagram showing a second example of the process flow of the slip operation support method during slip transactions in this embodiment. In Fig. 8B, s20 and s21 are the same processes as in Fig. 8A, so their explanation will be omitted.

[0092] On the condition of authentication in s21, invoice process support device 100 delivers a one-time password (OTP) to person in charge terminal 300 (s202). This OTP is a type of input information for displaying a code on person in charge terminal 300, and can be treated as second authentication information with an expiration date. Note that s202 may be executed independently without s21 being a condition. For example, invoice process support device 100 may execute s202 by sending an OTP issuance request received from a person in charge to person in charge terminal 300.

[0093] As a result, the OTP can be displayed on the person in charge terminal 300. The OTP may be delivered to other devices such as the teller terminal 400 or the ATM 500. The OTP may be text information, audio, an image, or a so-called CAPTCHA.

[0094] In response to this, the person in charge inputs the OTP into person in charge terminal 300. Then, person in charge terminal 300 transmits the input OTP to invoice work support device 100. As a result, invoice work support device 100 performs authentication using the transmitted OTP (s203). If the authentication in s203 is successful (s204:Y), invoice work support device 100 performs the processes from s22 onwards. These processes are the same as those in FIG. 8A, and therefore their description is omitted. On the other hand, if the authentication is unsuccessful (s204:N), the process ends. As with s25, these processes may be performed by case management DB 126 instead of invoice work support device 100. For example, such processes may be performed when case management DB 126 is implemented as an external device separate from invoice work support device 100.

[0095] Furthermore, in this flow, the distributed code is displayed when authentication using login information and authentication using OTP are successful (s21 to s204). However, when authentication using login information and / or authentication using OTP are successful, slip process support device 100 may create a code or distribute the created code.

[0096] This concludes the explanation of Fig. 8B, and another example of the process flow during slip transactions will now be explained. Fig. 8C is a diagram showing a third example of the process flow of the slip operation support method during slip transactions in this embodiment. Fig. 8C differs from Fig. 8A and Fig. 8B in that it is a process following Fig. 7B.

[0097] First, slip process support device 100 receives a specification for a URL from person in charge terminal 300 (s211). This is realized when the person in charge specifies the URL notified in s14, and person in charge terminal 300 notifies slip process support device 100 accordingly.

[0098] The slip processing support device 100 encodes the case information stored in s12, that is, creates a code. This process can be realized by the same process as s13.

[0099] The following process from s22 to s27 is the same as in Figures 8A and 8B, so the explanation will be omitted. According to the process in Figure 8C, the login work in s20 can be omitted, and the person in charge can carry out slip transactions more easily. This concludes the explanation of Figure 8C.

[0100] Although the best mode for carrying out the present invention has been specifically described above, the present invention is not limited to this, and various modifications can be made without departing from the spirit and scope of the present invention.

[0101] According to this embodiment, it is possible to improve the efficiency of the operations associated with agents bringing in large volumes of slips, and to appropriately reduce various costs.

[0102] The description of this specification makes at least the following clear: That is, in the invoice processing support method of this embodiment, the information processing device may further execute a process of receiving an approval request for the multiple invoice transactions from a terminal of a person in charge of the corporation, transmitting information of the approval request to a terminal of an administrator of the corporation, and, if the administrator's decision on whether to approve the request indicates approval, linking information on the invoice transactions with the registration information and storing the linked information in a storage device as the case information.

[0103] This makes it possible to streamline the registration of a large number of invoice transactions by the person in charge of the corporation and the processing by the manager who makes the approval decision on the transaction, and to appropriately handle the transaction. In turn, it makes it possible to further streamline the work associated with the delivery of a large number of invoices by agents, and appropriately reduce various costs. [Explanation of symbols]

[0104] 1 Network 10. Billing support system 100 Bill handling support device 101 Storage device 102 Programs 103 Memory 104 Arithmetic unit 105 Communication equipment 125 Customer management DB 126 Item management DB 200 Administrator terminal 300 Personnel terminal 310 Code 400 Teller terminal (customer service terminal) 500 ATMs (customer service terminals) 550 ATMs outside of business branches 560 Ticket vending machines (cash handling machines) 600 Accounting Systems 625 Account Management DB

Claims

1. In a slip operation support method using a slip operation support device, Registration information on authenticated legal entities and transaction details approved by the administrator of said entities The case information linked to the information to be processed is stored in a storage device. the authentication information is provided for each of the case information or the corporation, and is used for limited authentication when the voucher transaction is executed, and temporary transaction information provided for each of the case information is stored in the storage device by input from a person in charge of the voucher transaction; creating a code indicating said case information; Distributing the code to a staff terminal used by the staff member; Using a terminal device used in a branch of the financial institution, the code displayed on the screen of the terminal of the person in charge is read by the terminal device, and using the information obtained as a key, case information is identified from the storage device; delivering the specified case information to the terminal device and displaying a message prompting the person in charge to input the temporary transaction information; By performing authentication by comparing the temporary transaction information input by the person in charge in response to a display prompting the person in charge to input the temporary transaction information with the temporary transaction information stored in the storage device, If the authentication is successful, the invoice transaction indicated by the case information can be carried out based on the distributed case information.

2. The temporary transaction information is 2. The method for supporting slip operations according to claim 1, wherein the personal identification number is a password set for each corporation.

3. The slip operation support device, Delivering input information for displaying the code to the staff terminal; 2. The method for supporting slip operations according to claim 1, further comprising the step of displaying said code on a screen of said staff member's terminal on the condition that said staff member's terminal is input in accordance with said input information.

4. the input information is storage information indicating a storage location of the case information, 4. The method of claim 3, wherein said slip processing support device displays said code when said stored information is specified.

5. The slip operation support device, 5. The method for supporting slip operations according to claim 1, further comprising the steps of: receiving login information from the person in charge; and displaying the code on a screen of the person in charge terminal when authentication is successful using the login information.

6. A slip operation support system having a slip operation support device for executing a slip operation support method and a terminal device used at a branch of a financial institution, The slip operation support device, storing case information in a storage device that links registration information related to the authenticated corporation with information related to the invoice transaction approved by the administrator of the corporation; the authentication information is provided for each of the case information or the corporation, and is used for limited authentication when the voucher transaction is executed, and temporary transaction information provided for each of the case information is stored in the storage device by input from a person in charge of the voucher transaction; creating a code indicating said case information; Distributing the code to a staff terminal used by the staff member; The terminal device reads the code displayed on the screen of the staff terminal with the terminal device, and transmits the obtained information to the slip operation support device; The slip operation support device, Identifying case information from the storage device using the information transmitted from the terminal device as a key; delivering the specified case information to the terminal device and displaying a message prompting the person in charge to input the temporary transaction information; By performing authentication by comparing the temporary transaction information input by the person in charge in response to a display prompting the person in charge to input the temporary transaction information with the temporary transaction information stored in the storage device, If the authentication is successful, the invoice processing support system enables the invoice transaction indicated by the case information to be carried out based on the distributed case information.

7. The temporary transaction information is 7. The slip processing support system according to claim 6, wherein the personal identification number is set for each said corporation.

8. The slip operation support device, Delivering input information for displaying the code to the staff terminal; 7. A slip processing support system according to claim 6, further comprising: a display unit that displays said code on a screen of said staff member's terminal on the condition that said staff member's terminal is input in accordance with said input information.

9. the input information is storage information indicating a storage location of the case information, 9. The system according to claim 8, wherein said slip processing support device displays said code when said stored information is specified.

10. The slip operation support device, 10. The slip processing support system according to claim 6, further comprising: receiving login information from the person in charge; and displaying the code on a screen of the person in charge terminal when authentication is successful using the login information.

11. In a slip operation support device for executing a slip operation support method, a storage device for storing case information linking registration information on an authenticated corporation with information on a voucher transaction approved by an administrator of the corporation, and authentication information set for the case information or the corporation, which is used for limited authentication when the voucher transaction is executed, and which stores temporary transaction information set for the case information based on input from a person in charge of the voucher transaction; a computing device which creates a code indicating said case information, distributes said code to a staff terminal used by said staff, identifies case information from said storage device using information obtained by reading the code displayed on the screen of said staff terminal from a terminal device used in a branch of the financial institution, distributes the identified case information to said terminal device, causes a display to be displayed encouraging said staff to input said temporary transaction information, and performs authentication by comparing the temporary transaction information input by said staff in response to the display encouraging said staff to input the temporary transaction information with the temporary transaction information stored in said storage device, If the authentication is successful, the invoice processing support device enables the invoice transaction indicated by the case information to be carried out based on the distributed case information.

Images