Voucher work support method and system
Patent Information
- Application Number
- JP2022079210
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Filing Date
- 2022-05-13
- Publication Date
- 2024-11-14
- Estimated Expiration
- 2042-05-13
AI Technical Summary
【0013】 本発明によれば、代理人による大量の伝票持込に伴う業務を効率化し、各種コストを適宜に抑制可能となる。
Smart Images

Figure 0007583763000001 
Figure 0007583763000002 
Figure 0007583763000003
Abstract
Description
[Technical field]
[0001] The present invention relates to a method and system for supporting slip processing operations. [Background technology]
[0002] In many cases, corporate clients who visit bank branches are agents. The cases they bring in tend to involve time-consuming and complicated business matters, and are assumed to be handled at the counter. In addition, when a transaction was made by an agent, the branch counter was required to have a procedure for verifying that the transaction had 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 allows customers to insert the cash card of a parent account set up at a financial institution into an ATM machine. and by inputting authentication information, the host computer verifies that the customer is a legitimate transactor. Furthermore, necessary temporary account information including information input by the customer specifying the period for which the temporary account is to be opened 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, in various contract procedures at financial institutions, customers can apply without bringing their personal seal or passbook to the counter, and paper-based application documents can be eliminated, reducing the burden on customers to fill out forms and reducing the chance of incomplete filling out. Furthermore, a device has been proposed that allows customers and counter staff to check the application details together, making procedures more efficient (see Patent Document 2).
[0006] This technology relates to a server computer that executes processing related to a transaction contract with a customer at a counter of a financial institution, the server computer being 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 proposed is a store visit system (see Patent Document 3) that provides the counter staff with store visitor information that identifies each individual store visitor in advance.
[0008] This technology includes an information processing device that holds a customer file in which personal data is registered, a store reception device that is connected to the information processing device via a communication network and has an input unit through which a customer inputs an account identifier and a customer recognition unit that recognizes the biometric characteristics of the customer, and a store reception terminal that is installed at a reception counter and connected to the communication network, and the store reception device assigns reception numbers to customers in the order in which they are received, acquires the personal data from the information processing device based on the account identifier, and identifies the customer based on the acquired personal data and the recognized biometric characteristics of the customer. and transmitting visitor information of the identified visitor together with a 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 business involving the bringing in of a large number of transaction slips by agents of corporate clients, and therefore the staff at the branch are overwhelmed with the task of processing such transaction slips, placing a heavy burden on them. The same is true for the authentication procedures carried out by the aforementioned agents when conducting transactions, and the human and time costs associated with this work tended 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] The invoice processing support method of the present invention, which solves the above-mentioned problems, is characterized in that an information processing device stores in a storage device authentication information related to a corporation and information related to multiple invoice transactions approved by an administrator of the corporation, and upon receiving an authentication request from a terminal of a person in charge of the corporation, performs an authentication process based on the authentication information contained in the authentication request and the authentication information related to the corporation, and if the authentication is successful, performs a process of delivering coded information that encodes the information related to the invoice transaction to the terminal of the person in charge, and a process of responding to the customer service terminal with information related to the invoice transaction identified through a reading operation at a customer service terminal of a financial institution in response to the coded information displayed on the terminal screen of the person in charge, and the customer service terminal performs a read of the corporation's cash card presented by the person in charge, compares predetermined identification information obtained by the read with predetermined card management information, and if it is determined that the cash card belongs to the corporation, performs a predetermined process related to the invoice transaction. The invoice processing support system of the present invention is characterized by including: a storage device that stores authentication information related to a corporation and information related to a plurality of invoice transactions approved by an administrator of the corporation; an information processing device that has a calculation device that executes a process of receiving an authentication request from a terminal of a person in charge of the corporation, and performing an authentication process based on the authentication information contained in the authentication request and the authentication information related to the corporation, and if the authentication is successful, a process of delivering coded information that encodes the information related to the invoice transaction to the terminal of the person in charge, and a process of responding to the customer service terminal with information related to the invoice transaction identified through a reading operation at a customer service terminal of a financial institution in response to the coded information displayed on the terminal screen of the person in charge; a card reader that executes reading of the corporation's cash card presented by the person in charge; and a customer service terminal that has a calculation device that compares predetermined identification information obtained by the reading with predetermined card management information, and executes predetermined processing related to the invoice transaction if it is determined that the cash card belongs to the corporation. Effect of the Invention
[0013] According to the present invention, it is possible to improve the efficiency of the operations associated with the delivery of a large number of slips by agents, and to appropriately reduce various costs. [Brief description of the drawings]
[0014] [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 hardware configuration of an ATM in the present embodiment. [Figure 4] FIG. 2 is a diagram illustrating an example of a configuration of a customer management DB according to the present embodiment. [Diagram 5] FIG. 2 is a diagram illustrating an example of the configuration of a case management DB 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 7] FIG. 2 is a diagram showing an example of a flow of a slip processing support method according to the present embodiment. [Figure 8] FIG. 2 is a diagram showing an example of a flow of a slip processing support method according to the present embodiment. [Figure 9] FIG. 2 is a diagram showing an example of a flow of a slip processing support method according to 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. [Figure 12] FIG. 4 is a diagram showing an example of a screen in the present embodiment. [Figure 13] FIG. 4 is a diagram showing an example of a screen in the present embodiment. [Figure 14] FIG. 4 is a diagram showing an example of a screen in the present embodiment. [Figure 15] FIG. 4 is a diagram showing an example of a screen in the present embodiment. [Figure 16] FIG. 4 is a diagram showing an example of a screen in the present embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0015] <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.
[0016] As shown in Fig. 1, in this embodiment, invoice processing support device 100 is communicatively connected to employee terminal 200, manager terminal 250, ATM 300, and accounting system 400 via network 1. Therefore, all of these devices or multiple devices including invoice processing support device 100 may be collectively referred to as invoice processing support system 10. Note that network 1 may be composed of multiple network systems in addition to the example shown in Fig. 1.
[0017] The invoice processing support device 100 of this embodiment can be said to be a service providing device that appropriately handles invoice transactions that corporate customers wish to process and improves the efficiency of those transactions. Of course, the device may be integrated with any of the devices included in the invoice processing support system 10 described above.
[0018] The person in charge terminal 200 is a terminal operated by the person in charge at the corporate customer. Specifically, a personal computer, a smartphone, a tablet terminal, etc. can be assumed, but there is no limitation as long as it is an information processing device that can communicate with the slip process support device 100.
[0019] The person in charge inputs information on invoice transactions that have occurred in relation to the corporation's business into the person in charge terminal 200, and transmits the information as an approval request to the manager terminal 250 via invoice processing support device 100.
[0020] The staff member terminal 200 acquires and stores from the invoice processing support device 100, a code 210 (e.g., a two-dimensional barcode) that the invoice processing support device 100 generates for each invoice transaction. This code 210 is displayed on the screen of the staff member terminal 200 by the operation of the staff member, and can be read by an ATM 300 in the branch (which can be an ATM inside the branch or an ATM outside the branch) or by a specified other device (e.g., a cash handling device such as a ticket machine, which is another example of a customer service terminal). There are also cases where a single code 210 described above is generated for multiple invoice transaction cases collectively.
[0021] In addition, it is also conceivable that the staff terminal 200 may be operated as 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 210 on the screen; and there is no limitation to this type of operation.
[0022] The administrator terminal 250 is a terminal operated by the manager or the accounting department manager of the corporate client. Specifically, a personal computer, a smartphone, a tablet terminal, or the like can be assumed, but is not limited thereto as long as it is an information processing device capable of communicating with the slip operation support device 100.
[0023] The accounting department manager or the like will view, on this administrator terminal 250, 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).
[0024] Meanwhile, the ATM 300 is an automated teller machine that is one of the customer service terminals installed in a branch. The ATM 300 is equipped with a code reader 307 such as a digital photographing device for reading the above-mentioned code 310. In addition to the ATM 300, various information processing devices installed in a branch, such as a teller terminal operated by a teller clerk, may also be considered as customer service terminals.
[0025] The accounting system 400 is one of the core systems of the financial institution described above, and manages each customer's account information in an account management DB 425, and also manages all financial transactions in the accounts. The basic configuration itself is the same as that of existing accounting systems. The account management DB 425 is also the same as that of a general accounting system, and a description thereof will be omitted.
[0026] However, accounting system 400 of this embodiment performs corporate authentication processing based on the account information of the corporate customer and its authentication information in response to a request from a service user of the invoice processing support method provided by invoice processing support device 100, i.e., from person in charge terminal 200 of the person in charge or administrator terminal 250 of the administrator (this authentication processing is executed, for example, via invoice processing support device 100, and login to the service site of invoice processing support device 100 is also automatically executed depending on the authentication result). These points are configurations that are implemented independently by accounting system 400 of this embodiment. <Hardware configuration> The hardware configuration of slip process support device 100 of this embodiment is as shown in FIG.
[0027] 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.
[0028] The memory 103 is composed of a volatile storage element such as a RAM.
[0029] The calculation device unit 104 is a CPU that reads out the program 102 stored in the storage device 101 into the memory 103 and executes the program, controls the device itself, and performs various types of judgment, calculation, and control processing.
[0030] 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 person in charge terminal 200, the manager terminal 250, the ATM 300, and the accounting system 400.
[0031] The slip processing support device 100 is an input device that accepts key input or voice input from the user. The processing device may further include an output device such as a display for displaying processed data.
[0032] Furthermore, in addition to program 102 for implementing the functions required for form work support device 100 of this embodiment, at least a customer management database 125 and a case management database 1266 are stored in storage device 101. Details of these databases will be described later. Customer management database 125 and case management database 126 may be implemented in an external device separate from form work support device 100, and may be configured to be operated so that they can be accessed appropriately by form work support device 100.
[0033] 3 shows an example of a hardware configuration of an ATM 300 in this embodiment. The ATM 300 in this embodiment includes a storage device 301, a memory 303, a calculation device 304, an input / output device 305, a communication device 306, and a code reader 307. The ATM 300 naturally includes mechanisms and functions for handling cash that should be included in a typical ATM (not shown).
[0034] Of these, the storage device 301 is configured with an appropriate non-volatile storage element such as an SSD (Solid State Drive) or a hard disk drive.
[0035] The memory 303 is composed of a volatile storage element such as a RAM.
[0036] The calculation device unit 304 is a CPU that reads out a program 302 stored in the storage device 301 into a memory 303 and executes the program, controls the device itself, and performs various types of judgment, calculation, and control processing.
[0037] The input / output device 305 is a device such as a touch panel that receives key input or voice input from the user and displays processing data.
[0038] The communication device 306 is assumed to be a network interface card or the like that is connected to the network 1 and handles communication processing with the slip process support device 100 and the accounting system 400 .
[0039] The code reader 307 is an imaging device that photographs the code 210 (distributed from the invoice processing support device 100) displayed on the screen of the person in charge of the corporate client mentioned above on the person in charge terminal 200, and inputs the image data into the code analysis engine 310.
[0040] Furthermore, in the storage device 301, in addition to a program for implementing general ATM functions, a code analysis engine 310 is also included as a program 302 for implementing functions required for the ATM 300 of this embodiment. However, this code analysis engine 310 may be implemented in an external device separate from the ATM 300 and configured to be operated so as to be appropriately accessible via an appropriate line or the like. <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.
[0041] 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 authentication pass, account information, administrator information, and person in charge information of the customer, using a customer ID that uniquely identifies the corporate customer as a key.
[0042] The authentication pass is a password issued to the corporate customer. The password is required when using the slip work support service provided by slip work support device 100.
[0043] The account information is information such as the branch number, account number, account number, and PIN number of the account held by the corporate customer. This account information may include information on the cash card held by the corporate customer (e.g., so-called bank account information, as well as identification information of the customer and the card itself). In that case, for example, it may be assumed that the cash card information is acquired in advance from the accounting system 400 of the financial institution as information on the corporate customer and is synchronized with this DB.
[0044] 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.
[0045] 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.
[0046] 5 shows an example of the case management DB 126 in this embodiment. The case management DB 126 in this embodiment is a database that stores various information related to slip transactions that occur at corporate clients.
[0047] 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, and identity verification information, using a case ID that uniquely identifies a case of invoice transaction processing as a key.
[0048] Among these, the customer ID is identification information that uniquely identifies the corporate customer that requested the project.
[0049] The corporate authentication result is the authentication result obtained in the accounting system 400 for the corporate customer.
[0050] Furthermore, the target invoice is the invoice number of one or more invoices included in this case.
[0051] The transaction details are information about the details of the financial transaction in the target slip (e.g., transfer, transfer slip operation support, transfer amount).
[0052] In addition, the approved information is information necessary for financial transactions, such as code 210 generated upon approval by the corporate customer's administrator regarding the slip transaction in question entered by the corporate customer's staff member, and is information necessary for the operation of the slip transaction at ATM 300.
[0053] 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.
[0054] The personal identification information is authentication information obtained from the person in charge terminal 200 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 person in charge's face, iris, veins, etc., or a separately determined password.
[0055] In the example of the case management DB 126 shown in FIG. 5, the case ID “00001” has two It shows that each slip has been approved by the administrator and registered in the case management DB 126. In addition, the person who will actually visit the branch to handle the transactions on these slips has also been determined, and the code 210, which is the identity verification information, has also been registered.
[0056] Meanwhile, the case ID "00002" indicates that each of the 30 slips has been approved by the administrator and registered in the case management DB 126. In addition, the person who will actually visit the branch to handle the transactions of these 30 slips has also been determined, and their identity verification information has also been registered.
[0057] 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. Also, regarding the transaction of this one slip, the person in charge who will actually visit the branch has been decided, but the identity verification information has not been registered.
[0058] Also, 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 of invoices, their approval, and the issuance and registration of code 210 associated with the approval will take place. <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.
[0059] 6 is a diagram showing an example of a flow of the slip processing support method in this embodiment. Here, it is assumed that the administrator of the corporate client applies for use of the slip processing support service (provided by slip processing support device 100).
[0060] In this case, the administrator terminal 250 operated by the administrator mentioned above will accept an application for use including information on the corporation's accounts, their authentication information (such as a PIN number), and contact information for a person who may be responsible for handling invoice transactions (see Figure 10), and will send this to the invoice processing support device 100.
[0061] Invoice processing support device 100 receives the application for use sent by manager terminal 250 (s1).
[0062] 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 400 (s2).
[0063] In response to the authentication request, accounting system 400 determines whether the set of account information and its authentication information matches the information held in account management DB 425 for the account held by the corporate customer, and executes authentication processing. Accounting system 400 returns the result of this authentication processing to slip operation support device 100.
[0064] On the other hand, if the authentication result in accounting system 400 indicates a successful authentication (s3: Y), invoice work support device 100 generates a customer ID and authentication pass for the above-mentioned corporate customer, and 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 authentication result indicates a failed authentication (s3: N), invoice work support device 100 ends this flow. <Flow example: When creating a document> 7 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.
[0065] In this case, the staff terminal 200 operated by the above-mentioned staff member first transmits a login request including the login information (e.g., ID, password) entered by the staff member to the accounting system 400, for example via the invoice processing support device 100 (s5).
[0066] In this case, the accounting system 400 performs authentication processing by comparing the information held about the corporate customer in the account management DB 425 with the login information included in the login request, and responds with the result (s6).
[0067] The invoice processing support device 100 obtains the above-mentioned response from the accounting system 400, and if the response indicates successful login (s7: Y), it delivers (s8) an entry screen for the transaction details in the invoice processing (see FIG. 11) to the staff terminal 200 and displays it.
[0068] Meanwhile, the person in charge terminal 200 accepts the plurality of pieces of slip content information input by the person in charge via the entry screen (s9).
[0069] The person in charge terminal 200 also sends an approval request, including the information on the invoice content obtained in s9, to the invoice processing support device 100 (s10), and the process ends. <Flow example: When approving a document> Fig. 8 is a diagram showing an example of the flow of the invoice processing support method in this embodiment. Here, it is assumed that invoice processing support device 100 and manager terminal 250 cooperate with each other in response to an approval request sent from person in charge terminal 200 as a result of the flow of Fig. 7 described above.
[0070] Here, the corporate customer's administrator terminal 250 transmits a login request including the login information (eg, ID, password) entered by the administrator to the slip processing support device 100 (s11).
[0071] In this case, slip process support device 100 executes authentication processing by comparing the customer ID and authentication pass stored in customer management DB 125 for the corporate customer with the login information included in the login request (s12). In other words, slip process support device 100 uses customer management DB 125 to control access through authentication processing for the corporate customer who is the operator of administrator terminal 250.
[0072] If the above authentication process is successful, i.e., the login is successful (s13:Y), the invoice processing support device 100 sends an approval request for multiple invoice transactions received from the corporate customer's staff terminal 200 to the administrator terminal 250 (s14).
[0073] Meanwhile, the manager terminal 250 receives the above-mentioned approval request and displays it to the manager (s15). The manager checks the information on multiple vouchers (see FIG. 12) that is the content of the approval request sent from the person in charge terminal 200 via the voucher work support device 100, and determines whether or not to register it.
[0074] Manager terminal 250 receives input regarding the manager's decision, ie, approval or disapproval, and responds to slip processing support device 100 (s16).
[0075] The slip operation support device 100 receives, from the manager terminal 250, the following information regarding each slip transaction: The administrator then obtains the result of his / her decision as to whether or not the request is approved (s17).
[0076] If the above-mentioned determination result indicates approval (s18: Y), then invoice processing support device 100 links the information on the invoice transaction to be approved with the registration information, and stores the linked information as case information in case management database 126 (s19).
[0077] The information on the slip transaction corresponds to information such as the slip number and the transaction details, and the registered information corresponds to information such as the case ID generated by slip operation support device 100 for the case.
[0078] In addition, for cases for which approval has been obtained from the above-mentioned administrator, the invoice processing support device 100 generates a code 210 such as a two-dimensional barcode by providing the case information to a specified coding engine, and registers this in association with the corresponding record in the case management DB 126 (s20).
[0079] It is more preferable that invoice processing support device 100 sets a predetermined expiration date, such as a few hours or a day, for code 210 and manages the expiration date. When operating in this manner, code 210 that has exceeded the expiration date is invalidated in case management DB 126. The invalidation process can be performed by deleting code 210 from case management DB 126 or by setting an "invalid" flag.
[0080] The fact that code 210 has been issued as described above is notified from invoice process support device 100 to the email address or the like (based on the invoice manager information in customer management DB 125) of the invoice manager terminal 200. In other words, the invoice manager recognizes that the invoice transaction for which he or she performed the entry procedure has been approved by the administrator and has become a case. <Flow example: Voucher transaction processing> Next, assume that a person in charge of a corporate client visits a branch office to actually process a case registered in case management DB 126. Fig. 9 is a diagram showing an example of a flow of a slip processing support method in this embodiment.
[0081] In this case, for example, it is assumed that upon receiving notification of the issuance of the above-mentioned code 210, or upon the approach of a closing date such as the end of the month, the person in charge operates person in charge terminal 200 to log in to slip process support device 100.
[0082] At this time, the person in charge terminal 200 sends a login request including the login information (eg, ID and password) entered by the person in charge to the slip process support device 100 (s21).
[0083] In this case, invoice processing support device 100 executes authentication processing by comparing the customer ID and authentication pass stored in customer management DB 125 for the corporate customer with the login information included in the login request (s22). In other words, invoice processing support device 100 uses customer management DB 125 to control access through authentication processing for the corporate customer who is the operator of staff member terminal 200.
[0084] If the above authentication process is successful, i.e., the login is successful (s23: Y), the invoice processing support device 100 extracts the code 210 from the record linked to the relevant person in the case management DB 126 and sends it to the person in charge terminal 200 (s24).
[0085] On the other hand, the staff terminal 200 receives the above-mentioned code 210 and displays it on the screen (see FIG. 13) (s25). At this time, the staff member inputs the code displayed on the screen to the code reader 307 of the ATM 300 (which may be an ATM inside the business branch or an ATM outside the business branch, or may include a cash handling machine such as a ticket vending machine, which is another example of a customer service terminal) that the staff member is visiting. The card 210 is held up to the reader to read the information.
[0086] This ATM 300 obtains case information by reading the code 210 displayed on the screen of the staff terminal 200 using the code reader 307, and sends a search request to the invoice processing support device 100 using the case ID and invoice number indicated in the case information as keys (s26).
[0087] On the other hand, slip processing support device 100 receives a search request from ATM 300 and determines whether code 210 exists and is valid, and whether code 210 is associated with the case ID or the like indicated in the search request (s27).
[0088] If the result of the above determination is that code 210 does not exist or is invalid (s27:N), slip operation support device 100 ends the process by responding to ATM 300 that the transaction is not possible. In this case, ATM 300 also outputs the response and ends the process.
[0089] On the other hand, if the result of the above determination is that code 210 exists or is valid (s27: Y), slip processing support device 100 responds to that effect to ATM 300 (s28).
[0090] When the ATM 300 receives a response that the code 210 exists or is valid, it outputs a message (see FIG. 14) to the person in charge to request him to insert his cash card (s29). The person in charge checks the message and inserts the corporate cash card he carries into the card insertion slot. Note that this corporate cash card was given to the person in charge in advance by the manager of the corporate customer, etc., to carry with him for slip transactions.
[0091] The ATM 300 reads the corporate cash card inserted by the person in charge, acquires information on the corporate cash card, and queries, for example, the accounting system 400 for the information (s30).
[0092] The accounting system 400 compares the corporate cash card information obtained from the ATM 300 with the account management DB 425 to confirm that account information etc. matching the information is registered, and responds with the result.
[0093] If slip process support device 100 manages corporate cash card information for each corporate customer in customer management DB 125, ATM 300 may make the above-mentioned inquiry to slip process support device 100. In that case, slip process support device 100 will also perform the matching and respond with the result.
[0094] If the response from the accounting system 400 indicates that no information is registered in the account management DB 425 (s31:N), the ATM 300 outputs a message to the effect that the transaction is not possible (see FIG. 15) and ends the process.
[0095] On the other hand, if the response from the accounting system 400 indicates that the information is registered in the account management DB 425 (s31: Y), the ATM 300 sends a request for case information using the case ID obtained from the above-mentioned code 201 as a key to the voucher processing support device 100, and obtains the case information related to the voucher transaction (s32).
[0096] Based on the case information obtained from the invoice processing support device 100, the ATM 300 executes the specified processing related to the invoice transaction with the accounting system 400 (s33), displays the result (see FIG. 16) (s34), and terminates the processing.
[0097] At this time, the ATM 300 notifies the completion of the processing of the slip transaction in the slip transaction support message. The invoice processing support device 100 receives the notification and executes a clearing process for the case information held for the invoice transaction in the case management database 126. The clearing process may involve setting a value such as "transaction completed" to the corresponding record, or deleting the record itself.
[0098] When the response from the accounting system 400 indicates that the information is registered in the account management DB 425, the ATM 300 may further perform identity verification of the person in charge. For example, the ATM 300 may request the person in charge to present a driver's license or the like, and obtain identity verification information such as facial image data of the driver's license. The ATM 300 may also obtain a facial image of the person in charge as identity verification information using an appropriate photographing device or the like of the ATM 300. The ATM 300 may then perform identity verification by comparing the facial image data obtained from the driver's license or the like with the facial image of the person in charge obtained by the photographing device or the like of the ATM 300, and may perform subsequent processing only if identity verification is successful.
[0099] 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.
[0100] 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.
[0101] The description of this specification makes at least the following clear: That is, in the invoice work support device of this embodiment, when an information processing device receives information about the invoice transaction from a terminal of a person in charge of the corporation, the information processing device may further execute a process of delivering the information about the invoice transaction to a terminal of a manager of the corporation and obtaining a response from the manager regarding whether or not the invoice transaction is approved, and if the response indicates approval, a process of linking the information about the invoice transaction to authentication information of the corporation and storing it in a storage device as case information.
[0102] In this way, the manager of the corporation can accurately determine whether or not a voucher transaction based on information input by a corporation employee can be accepted, and this determination can be efficiently reflected in subsequent processing.
[0103] In addition, in the invoice processing support method of this embodiment, the information processing device may set a predetermined expiration date for the coded information, and if the expiration date is exceeded, further execute a process of invalidating the coded information.
[0104] This maintains the freshness of the code and prevents the code from being leaked to and used by malicious individuals between the time of code generation and the time of code use, thereby improving security.
[0105] In the invoice processing support method of this embodiment, when the information processing device executes the predetermined process related to the invoice transaction, the information processing device may further execute a clearing process of information held regarding the invoice transaction.
[0106] This makes it easier to effectively prevent the occurrence of situations in which slip transaction information is leaked and illegally reused, and makes it easier to improve the security of slip transactions.
[0107] In addition, in the slip operation support system of this embodiment, when the information processing device receives information about the slip transaction from a terminal of a person in charge of the corporation, the information processing device further executes a process of delivering the information about the slip transaction to a terminal of an administrator of the corporation and obtaining a response from the administrator as to whether or not the slip transaction is approved, and if the response indicates approval, a process of linking the information about the slip transaction to authentication information of the corporation and storing it in a storage device as case information. It may also be stated that the above is a measure to
[0108] In addition, in the invoice processing support system of this embodiment, the information processing device may be configured to set a predetermined expiration date for the coded information, and if the expiration date is exceeded, further execute processing to invalidate the coded information.
[0109] In addition, in the invoice processing support system of this embodiment, the information processing device may further execute a clearing process for information held regarding the invoice transaction when the specified process regarding the invoice transaction is executed. [Explanation of symbols]
[0110] 1 Network 10. Billing support system 100 Bill handling support device 101 Storage device 102 Programs 103 Memory 104 Arithmetic equipment 105 Communication equipment 125 Customer management DB 126 Item management DB 200 Personnel terminal 210 Code (Coded Information) 250 Administrator terminal 300 ATMs (customer service terminals) 301 Storage device 302 Program 303 Memory 304 Arithmetic equipment 305 I / O Device 306 Communication Equipment 307 Code Reader 310 Code Analysis Engine 400 Accounting System 425 Account Management DB
Claims
1. An information processing device, storing authentication information for a corporation and information regarding a plurality of voucher transactions approved by an administrator of the corporation in a storage device; receiving an authentication request from a terminal of a person in charge of the corporation, performing an authentication process based on authentication information included in the authentication request and authentication information related to the corporation, and if the authentication is successful, performing a process of transmitting coded information obtained by coding information related to the slip transaction to the terminal of the person in charge, and performing a process of responding to the customer service terminal with information related to the slip transaction identified through a reading operation of a customer service terminal of the financial institution in response to the coded information displayed on the terminal screen of the person in charge; The customer service terminal, reading the cash card of the corporation presented by the person in charge, comparing predetermined identification information obtained by the reading with predetermined card management information, and if it is determined that the cash card belongs to the corporation, executing a predetermined process related to the slip transaction; A method for supporting slip operations.
2. An information processing device, a process for receiving information about the invoice transaction from a terminal of a person in charge of the corporation, distributing the information about the invoice transaction to a terminal of an administrator of the corporation and obtaining a response from the administrator as to whether the invoice transaction is approved or not, and if the response indicates approval, linking the information about the invoice transaction to authentication information of the corporation and storing it as case information in a storage device; 2. The method for supporting slip operations according to claim 1, further comprising the steps of:
3. The information processing device, a predetermined expiration date is set for the coded information, and when the expiration date is exceeded, a process of invalidating the coded information is further executed.
2. The method for supporting slip operations according to claim 1.
4. The information processing device, When the predetermined process for the slip transaction has been executed, a clearing process for the information held for the slip transaction is further executed.
2. The method for supporting slip operations according to claim 1.
5. an information processing device including a storage device for storing authentication information related to a corporation and information related to a plurality of slip transactions approved by an administrator of said corporation; and an arithmetic unit for executing, upon receiving an authentication request from a terminal of a person in charge of said corporation, an authentication process based on the authentication information included in said authentication request and the authentication information related to said corporation, and, if said authentication is successful, a process for delivering coded information obtained by coding information related to said slip transactions to said terminal of said person in charge, and a process for responding to said customer service terminal with information related to said slip transactions identified through a reading operation of a customer service terminal of the financial institution in response to the coded information displayed on the screen of said terminal of said person in charge; a customer service terminal including a card reader that reads the corporation's cash card presented by the person in charge, and a calculation device that compares predetermined identification information obtained by the reading with predetermined card management information, and executes a predetermined process related to the slip transaction if the cash card is found to belong to the corporation; A slip operation support system comprising:
6. The information processing device includes: When the information regarding the slip transaction is received from the terminal of the person in charge of the corporation, and if the response indicates approval, linking the information about the voucher transaction to authentication information of the corporation and storing the information about the voucher transaction as case information in a storage device.
6. The slip processing support system according to claim 5.
7. The information processing device includes: a predetermined expiration date is set for the coded information, and when the expiration date is exceeded, a process of invalidating the coded information is further executed.
6. The slip processing support system according to claim 5.
8. The information processing device includes: When the predetermined process for the slip transaction is executed, a clearing process for information held for the slip transaction is further executed.
6. The slip processing support system according to claim 5.
Citation Information
Patent Citations
Store visitor reception system, its device, and its program
JP2004151862A
Opening method and opening system for temporary account
JP2005352526A
Automatic transaction system, information management server, and method of automatic transaction
JP2007087006A
Automatic transaction system
JP2007241359A
Subject authentication system in window transaction of financial institution and transaction method thereof
JP2016024620A
