Program, information processing apparatus, and method

Abstract

To provide a program, an information processing device, and a method that facilitate confirmation of an advance purchase application.SOLUTION: In this purchase application management system for performing the settlement processing of payment to the application of purchase, a server stores purchase application data related with purchase, and as its function, when a payer who has performed payment related with purchase inputs, the program causes the computer to execute a step of receiving voucher information relating to payment using a credit card, a step S321 of acquiring usage details information using the credit card from a settlement company of the credit card, a step S323 of collating and associating the purchase application information, the voucher information, and the usage details information, a step S324 of presenting two or more of the associated purchase application information, voucher information, and usage details information to a user, and a step of performing settlement processing of the presented purchase application information according to an instruction input from the presented user.SELECTED DRAWING: Figure 9

Description

[Technical Field]

[0001] The present disclosure relates to a program, an information processing device, and a method. [Background technology]

[0002] When companies purchase materials, equipment, etc. necessary for business operations, or when travel expenses are incurred for business trips, they accept various applications, such as expense claims, from employees, and then settle the expenses after the purchase. For such expenses, if the procedure required employees to submit applications and wait for approval before actually purchasing the items, the purchasing process would be inefficient. Therefore, it is becoming increasingly common for companies to have employees purchase the items at their own expense, and then settle the expenses after the expense claim is approved, and then pay the employee for the purchase.

[0003] As a technology for a system for processing small expenses in such companies, Patent Document 1 discloses technology for a system in which, when an application (settlement data) for advance payment for business trips, entertainment, social gatherings, etc. is received from an employee, the user settles the expense using a credit card, the credit card usage detail data is obtained and registered in a usage detail table, and the settlement data applied for by the employee is compared with the credit card usage detail sent by the credit card company to perform the settlement process. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Japanese Patent Application Laid-Open No. 2000-348099 Summary of the Invention [Problem to be solved by the invention]

[0005] Incidentally, when expenses such as those mentioned above are incurred, companies and other organizations accept various applications, such as expense claims, in advance. This is because, even if the expense settlement is made at a later date, there are cases where it is unclear whether the expense will be recognized, such as entertainment, so applications are accepted in advance. This also serves to prevent employees from fraudulently claiming expenses and to manage expenses within a predetermined budget.

[0006] Therefore, when expenses such as those mentioned above are incurred and payment is made using a post-pay method such as a credit card, for example, using a corporate card in the company's name, it is necessary to cross-check the advance purchase application for expenses, the evidence from the credit card payment, and the credit card statement linked from the credit card company, which requires the accounting staff at the company, etc., who accept the expense application, to do search and input work, which is time-consuming.

[0007] Therefore, this disclosure describes a technology that makes it easy to confirm a purchase request in advance in a purchase request management system that performs payment settlement processing for a purchase request. [Means for solving the problem]

[0008] According to one embodiment of the present disclosure, a program is provided for executing on a computer including a processor and a memory to perform a payment settlement process for a purchase request related to a business. The memory stores purchase request data related to the purchase. The program causes the processor to execute the following steps: accepting supporting data related to a payment using a credit card as input from a payer who made the payment for the purchase; acquiring credit card usage detail data from a credit card payment service provider; matching the purchase request data, supporting data, and usage detail data to establish correspondence; presenting two or more of the associated purchase request data, supporting data, and usage detail data to a user; and performing a settlement process for the presented purchase request data based on instructions input by the user. [Effects of the Invention]

[0009] According to the present disclosure, purchase request data related to business purchases, supporting data related to payments made using a credit card for the purchase, and credit card transaction details data are matched and presented to the user, and settlement processing of the purchase request data is performed based on instructions input by the user. This reduces the search and input work required by accounting staff at companies, etc. This makes it easier to understand the status of purchases at companies and facilitates purchase management. [Brief explanation of the drawings]

[0010] [Figure 1] 1 is a block diagram showing the overall configuration of a purchase application management system 1 according to a first embodiment. [Figure 2] 2 is a block diagram showing a functional configuration of the terminal device 10 of FIG. 1. FIG. [Figure 3] 2 is a block diagram showing the functional configuration of the server 20 of FIG. 1. FIG. [Figure 4] FIG. 4 is a diagram illustrating an example of the data structure of a purchase request database 2021 in FIG. 3. [Figure 5] FIG. 4 is a diagram illustrating an example of the data structure of the voucher database 2022 in FIG. 3. [Figure 6] FIG. 4 is a diagram showing an example of the data structure of a usage details database 2023 shown in FIG. 3. [Figure 7] 10 is a flowchart showing an example of the flow of purchase application acceptance processing by the purchase application management system 1. [Figure 8] 10 is a flowchart showing an example of the flow of processing for accepting voucher data by the purchase application management system 1. [Figure 9] 10 is a flowchart showing an example of the flow of a matching process performed by the purchase request management system 1. [Figure 10] 10 is a flowchart showing an example of a flow of settlement processing by the purchase application management system 1. [Figure 11] FIG. 10 is a diagram showing an example of a screen of a purchase request list displayed on the terminal device 10. DETAILED DESCRIPTION OF THE INVENTION

[0011] Hereinafter, embodiments of the present disclosure will be described with reference to the drawings. The following description and drawings are examples for explaining the present invention, and appropriate omissions and simplifications have been made for clarity of explanation. The present invention can be implemented in various other forms. Unless otherwise specified, each component may be singular or plural. In the following description, the same components are denoted by the same reference numerals. Their names and functions are also the same. Therefore, detailed descriptions thereof will not be repeated.

[0012] The functions performed by the components described herein may be implemented in circuitry or processing circuitry, including general-purpose processors, application-specific processors, integrated circuits, ASICs (Application Specific Integrated Circuits), a CPU (a Central Processing Unit), conventional circuits, and / or combinations thereof, programmed to perform the described functions. A processor includes transistors and other circuits and is considered to be circuitry or processing circuitry. A processor may also be a programmed processor that executes programs stored in memory.

[0013] In this specification, a circuitry, unit, or means is hardware that is programmed to realize or performs the described functions, which may be any hardware disclosed herein or any hardware known to be programmed to realize or perform the described functions.

[0014] If the hardware is a processor considered to be a type of circuitry, the circuitry, means, or unit is a combination of the hardware and software used to configure the hardware and / or processor.

[0015] <Summary> The following describes a purchase request management system according to the present disclosure. The purchase request management system according to the present disclosure is a system for accepting and managing applications for various purchases and expenses from employees and other parties for businesses such as companies and sole proprietors, and for settling accounts. Various applications submitted by companies and sole proprietors include, for example, applications for purchasing materials and equipment, travel expenses for business trips, and other expenses, and are procedures carried out to seek approval from superiors at the company. The purchase request management system according to the present disclosure is a computer system that registers application data related to applications from applicants such as employees, and associates and manages supporting data from payments made using credit cards with transaction detail data obtained from credit card payment providers. Furthermore, the purchase request management system according to the present disclosure is a system provided as a web service, for example, via a cloud server or the like, known as SaaS (Software as a Service).

[0016] Incidentally, when expenses, etc. are incurred as described above, companies, etc., have a procedure of accepting various applications, such as expense claims, in advance. Furthermore, when expenses, etc. are paid, companies, etc., settle the accounts by having employees pay using a credit card in the company's name, and then paying the credit card company. In this case, it is necessary to cross-check the purchase request data for the advance purchase request for expenses, etc., the supporting data for the credit card payment, and the credit card statement data linked from the credit card company. This requires the accounting staff at companies, etc., who accept such expense requests, to perform search and input tasks, which is time-consuming.

[0017] Therefore, the purchase request management system disclosed herein registers purchase request data related to applications from applicants such as employees, and manages supporting data when payments are made using a credit card in association with usage detail data obtained from the credit card payment provider, presents this to the user, and performs settlement processing for the purchase request data based on instructions from the user.

[0018] In addition, the purchase request management system according to the present disclosure accepts input of the association from the user when, for example, the association between the purchase request data, supporting document data, and usage detail data presented as a list is incorrect.

[0019] The above configuration makes it easy to understand the correspondence between purchase request data, supporting data, and usage details data, which reduces the amount of searching and input work required by accounting staff at companies, etc. This makes it easier to understand the status of purchases at companies and to manage purchases.

[0020] <First Embodiment> The following describes the purchase request management system 1. In the following description, for example, when the terminal device 10 accesses the server 20, the server 20 responds with information for generating a screen on the terminal device 10. The terminal device 10 generates and displays a screen based on the information received from the server 20.

[0021] <1 Overall configuration of the purchase request management system 1> FIG. 1 is a block diagram showing the overall configuration of a purchase request management system 1 according to a first embodiment. As shown in FIG. 1, the purchase request management system 1 includes a plurality of terminal devices (terminal device 10A and terminal device 10B are shown in FIG. 1; hereinafter, they may be collectively referred to as "terminal devices 10") and a server 20. The terminal devices 10 and the server 20 are connected to each other so as to be able to communicate with each other via a network 80. The network 80 is configured as a wired or wireless network. In this embodiment, the server 20 is a web server (including a cloud server) and exchanges information with the terminal device 10 via web pages. Furthermore, a web page browser for viewing web pages is installed on the terminal device 10, but a dedicated application for providing the services of the server 20 may also be installed so that the web pages can be viewed using the dedicated application.

[0022] The terminal device 10 is a device operated by each user. Here, a user is a person who uses the terminal device 10 to apply for various purchases and expenses, which are functions of the purchase request management system 1, such as an employee of a business enterprise. The terminal device 10 is realized by a desktop personal computer (PC), a laptop PC, or the like. Alternatively, the terminal device 10 may be a mobile terminal such as a tablet compatible with a mobile communication system or a smartphone.

[0023] The terminal device 10 is communicatively connected to the server 20 via a network 80. The terminal device 10 is connected to the network 80 by communicating with communication devices such as a wireless base station 81 conforming to communication standards such as 4G, 5G, and LTE (Long Term Evolution), and a wireless LAN router 82 conforming to a wireless LAN (Local Area Network) standard such as IEEE (Institute of Electrical and Electronics Engineers) 802.11. As shown as a terminal device 10B in FIG. 1 , the terminal device 10 includes a communication IF (Interface) 12, an input device 13, an output device 14, a memory 15, a storage unit 16, and a processor 19.

[0024] The communication IF 12 is an interface for inputting and outputting signals so that the terminal device 10 can communicate with external devices. The input device 13 is an input device (e.g., a keyboard, a touch panel, a touch pad, a pointing device such as a mouse, etc.) for receiving input operations from a user. The output device 14 is an output device (e.g., a display, a speaker, etc.) for presenting information to a user. The memory 15 is for temporarily storing programs and data processed by the programs, etc., and is a volatile memory such as a DRAM (Dynamic Random Access Memory). The storage unit 16 is a storage device for saving data, such as a flash memory or an HDD (Hard Disc Drive). The processor 19 is hardware for executing an instruction set written in a program, and is composed of an arithmetic unit, registers, peripheral circuits, etc.

[0025] Server 20 is a device that provides businesses such as corporations and sole proprietors with a service that accepts and manages applications for various purchases and expenses from employees and others, and performs settlement. Server 20 registers purchase request data related to applications from applicants such as employees, accepts supporting data when users make payments using credit cards, and obtains usage statement data from credit card payment providers. Server 20 associates the purchase request data, supporting data, and usage statement data, presents the associated data to the user, and accepts input of the association from the user. Server 20 also performs settlement processing for the presented purchase request data based on instructions input by the user.

[0026] The server 20 is a computer connected to a network 80. The server 20 includes a communication IF 22, an input / output IF 23, a memory 25, a storage 26, and a processor 29.

[0027] The communication IF 22 is an interface for inputting and outputting signals so that the server 20 can communicate with external devices. The input / output IF 23 functions as an interface with an input device for receiving input operations from a user and an output device for presenting information to the user. The memory 25 is for temporarily storing programs and data processed by the programs, etc., and is a volatile memory such as a DRAM (Dynamic Random Access Memory). The storage 26 is a storage device for saving data, such as a flash memory or an HDD (Hard Disc Drive). The processor 29 is hardware for executing an instruction set written in a program, and is composed of an arithmetic unit, registers, peripheral circuits, etc.

[0028] <1.1 Configuration of the terminal device 10> FIG. 2 is a block diagram showing the functional configuration of the terminal device 10 of FIG. 1. As shown in FIG. 2, the terminal device 10 includes multiple antennas (antenna 111, antenna 112), wireless communication units (first wireless communication unit 121, second wireless communication unit 122) corresponding to the respective antennas, an operation reception unit 130 (including a keyboard 131 and a mouse 132), an audio processing unit 140, a microphone 141, a speaker 142, a display 150, a storage unit 170, and a control unit 180. The terminal device 10 also has functions and configurations not specifically shown in FIG. 2 (e.g., a battery for storing power, a power supply circuit for controlling the supply of power from the battery to each circuit, etc.). As shown in FIG. 2, the blocks included in the terminal device 10 are electrically connected by a bus or the like. The terminal device 10 shown in FIG. 2 will be described as a mobile terminal such as a tablet or smartphone compatible with a mobile communication system, but may also be a stationary personal computer (PC) or a laptop PC.

[0029] The antenna 111 emits a signal emitted by the terminal device 10 as a radio wave. The antenna 111 also receives a radio wave from space and provides the received signal to the first radio communication unit 121.

[0030] The antenna 112 emits a signal emitted by the terminal device 10 as a radio wave. The antenna 112 also receives a radio wave from space and provides the received signal to the second radio communication unit 122.

[0031] The first wireless communication unit 121 performs modulation / demodulation processing and the like for transmitting and receiving signals via the antenna 111 so that the terminal device 10 can communicate with other wireless devices. The second wireless communication unit 122 performs modulation / demodulation processing and the like for transmitting and receiving signals via the antenna 112 so that the terminal device 10 can communicate with other wireless devices. The first wireless communication unit 121 and the second wireless communication unit 122 are communication modules including a tuner, an RSSI (Received Signal Strength Indicator) calculation circuit, a CRC (Cyclic Redundancy Check) calculation circuit, a high-frequency circuit, etc. The first wireless communication unit 121 and the second wireless communication unit 122 perform modulation / demodulation and frequency conversion of wireless signals transmitted and received by the terminal device 10, and provide the received signals to the control unit 180.

[0032] The operation reception unit 130 has a mechanism for receiving input operations from the user. Specifically, the operation reception unit 130 includes a keyboard 131 and a mouse 132. Note that the operation reception unit 130 may be configured as a touch screen that detects the position of the user's contact on the touch panel, for example, by using a capacitive touch panel.

[0033] The keyboard 131 accepts input operations by the user of the terminal device 10. The keyboard 131 is a device for inputting characters, and outputs input character information to the control unit 180 as an input signal.

[0034] The mouse 132 accepts input operations by the user of the terminal device 10. The mouse 132 is a pointing device for selecting an object displayed on the display 150, and outputs position information of the selected object on the screen and information indicating that a button has been pressed as input signals to the control unit 180.

[0035] The audio processing unit 140 modulates and demodulates audio signals. The audio processing unit 140 modulates a signal provided from the microphone 141 and provides the modulated signal to the control unit 180. The audio processing unit 140 also provides the audio signal to the speaker 142. The audio processing unit 140 is realized, for example, by a processor for audio processing. The microphone 141 accepts audio input and provides an audio signal corresponding to the audio input to the audio processing unit 140. The speaker 142 converts the audio signal provided from the audio processing unit 140 into audio and outputs the audio to the outside of the terminal device 10.

[0036] Display 150 displays data such as images, videos, and text under the control of control unit 180. Display 150 is realized by, for example, an LCD (Liquid Crystal Display) or an organic EL (Electro-Luminescence) display.

[0037] Camera 160 is a device that receives light with a light receiving element and outputs the received light as a captured image in accordance with the control of control unit 180. Camera 160 may be configured, for example, by an imaging device such as a digital camera or a video camera.

[0038] Storage unit 170 is configured with memory 15, such as a flash memory, and storage unit 16, and stores data and programs used by terminal device 10. In one aspect, storage unit 170 stores user information 171.

[0039] The user information 171 is information about a user who uses the terminal device 10 to apply for various purchases and expenses, which are functions of the purchase request management system 1. The user information includes information that identifies the user (user ID), the names of employees, and the like.

[0040] The control unit 180 is configured by, for example, the processor 19, and controls the operation of the terminal device 10 by reading a program stored in the storage unit 170 and executing instructions included in the program. The control unit 180 performs the functions of an input operation reception unit 181, a transmission / reception unit 182, a notification control unit 183, and a data processing unit 184 by operating in accordance with a program (not shown) that is an application that is stored in advance in the storage unit 170 of the terminal device 10 and installed, for example.

[0041] The input operation receiving unit 181 performs processing to receive input operations by the user via input devices such as the keyboard 131 and the mouse 132 .

[0042] The transmitting / receiving unit 182 performs processing for the terminal device 10 to transmit and receive data to and from an external device such as the server 20 in accordance with a communication protocol.

[0043] The notification control unit 183 performs processing to present information to the user. The notification control unit 183 performs processing to display a display image on the display 150, processing to output sound from the speaker 142, and the like.

[0044] The data processing unit 184 performs calculations on the data that the terminal device 10 has received as input in accordance with a program, and outputs the calculation results to a memory or the like.

[0045] <1.2 Functional configuration of server 20> Fig. 3 is a block diagram showing the functional configuration of the server 20 in Fig. 1. As shown in Fig. 3, the server 20 functions as a communication unit 201, a storage unit 202, and a control unit 203.

[0046] The communication unit 201 is configured by, for example, the communication IF 22, and performs processing for the server 20 to communicate with external devices.

[0047] The storage unit 202 is composed of, for example, a memory 25 and a storage 26, and stores data and programs used by the server 20. The storage unit 202 stores a purchase request database 2021, a voucher database 2022, a usage details database 2023, and the like.

[0048] The purchase request database 2021 is a database for storing purchase request data related to business purchases, such as purchases of materials and equipment, expenses for travel expenses for business trips, etc., which are managed by the purchase request management system 1. Details will be described later.

[0049] The voucher database 2022 is a database for storing voucher data when payments are made using a credit card for the purchase of materials, equipment, etc., and expenses such as transportation costs, which are managed by the purchase request management system 1. Details will be described later.

[0050] The usage details database 2023 is a database for storing usage details data linked from the credit card payment service provider after payments are made using a credit card for various purchases, travel expenses, and other expenses that are managed by the purchase request management system 1. Details will be described later.

[0051] The control unit 203 performs the functions shown in various modules, such as a receiving control module 2031, a sending control module 2032, a purchase request data reception module 2033, a supporting document data reception module 2034, a usage detail data acquisition module 2035, a data matching module 2036, a matching result presentation module 2037, a matching data input reception module 2038, and a settlement module 2039, by having the processor 29 of the server 20 perform processing according to the program.

[0052] The reception control module 2031 controls the process by which the server 20 receives signals from external devices in accordance with a communication protocol.

[0053] The transmission control module 2032 controls the process in which the server 20 transmits signals to external devices in accordance with a communication protocol.

[0054] The purchase request data reception module 2033 controls the process of receiving purchase request data related to various purchases through operation input by a user of the purchase request management system 1 on the terminal device 10. The purchase request data received from the user by the purchase request data reception module 2033 is data regarding applications submitted in advance to a business operator for purchases such as the purchase of materials and equipment, and travel expenses for business trips, etc. This purchase request data is regarding applications made to the company to which the user belongs.

[0055] The purchase request data acceptance module 2033, for example, displays a predetermined input format on the terminal device 10 for accepting input of purchase request data, and the user operates the terminal device 10 to enter various necessary items related to the purchase into the input format and transmits the data to the server 20 to accept the data.

[0056] The purchase request data includes, for example, the identification number (employee number, etc.) of the company to which the user who made the request belongs, the user's name, the purchase date, the item being requested for purchase, the amount, etc. The amount may be the actual purchase amount (for example, the amount stated on an estimate received from the store from which the purchase is made), the selling price at a general retail store, or a reference price displayed by searching on the Internet.

[0057] The purchase request data reception module 2033 stores the received purchase request data in, for example, the purchase request database 2021.

[0058] The supporting data receiving module 2034 controls the process of receiving supporting data related to payments made using a credit card for various purchases, based on operational input from the terminal device 10 by a user of the purchase request management system 1. Here, the supporting data received from the user by the supporting data receiving module 2034 may be, for example, image data captured by the camera 160 of the terminal device 10 of a statement of purchases (receipt) or the like received from a store or the like when the user makes payments using a credit card for various purchases. Furthermore, the supporting data received from the user by the supporting data receiving module 2034 may be, for example, electronic data such as a statement of purchases (receipt) received from an e-commerce site when the user makes payments using a credit card for various purchases. The supporting data receiving module 2034 may receive supporting data in any data format, such as PDF (Portable Document Format), Word, XML (eXtensible Markup Language), jpeg, png, bmp, tiff, gif, eps, or svg.

[0059] The supporting data acceptance module 2034, for example, displays a predetermined input format on the terminal device 10 for accepting the input of supporting data, and the user operates the terminal device 10 to input the supporting data (or a link to the supporting data, etc.) into the input format and transmits it to the server 20 to accept the data.

[0060] It should be noted that the user who inputs the evidence data into the evidence data reception module 2034 does not need to be the same person as the user who received the purchase request data by the purchase request data reception module 2033. This is because the user, such as an employee, who inputs the purchase request data is not necessarily the same person as the user, such as an employee, who made a purchase at a store, etc.

[0061] The voucher data reception module 2034 stores the received voucher data in, for example, the voucher database 2022.

[0062] The usage statement data acquisition module 2035 controls the process of acquiring credit card usage statement data from the payment service provider of the credit card used, for the supporting document data accepted by the supporting document data acceptance module 2034. The usage statement data acquired by the usage statement data acquisition module 2035 is, for example, data linked to accounting data from financial institutions, credit card companies, etc., when synchronizing with accounting data. For example, with the consent of a user of the purchase request management system 1, the usage statement data acquisition module 2035 accesses the servers of financial institutions and credit card companies to acquire account information held by the user at the financial institution and usage information of the credit card used by the user via API integration, etc. The process of acquiring usage statement data by the usage statement data acquisition module 2035 may be a pull-type information acquisition process that accesses the servers of financial institutions and credit card companies, as described above, or a push-type information acquisition process that accepts information transmission from the servers of financial institutions and credit card companies.

[0063] The usage detail data acquisition module 2035 stores the acquired usage detail data in, for example, the usage detail database 2023.

[0064] The data matching module 2036 controls the process of matching and associating the purchase request data accepted by the purchase request data receiving module 2033, the supporting voucher data accepted by the supporting voucher data receiving module 2034, and the usage detail data acquired by the usage detail data acquisition module 2035. The data matching module 2036, for example, reads the purchase request data, supporting voucher data, and usage detail data, and determines the corresponding supporting voucher data and usage detail data based on information included in the purchase request data, such as the purchase date, purchased item, and amount of the application target. At this time, the data matching module 2036 may read the request data using OCR processing, for example.

[0065] The data matching module 2036 may, for example, analyze and associate the purchase request data, supporting voucher data, and usage detail data. Specifically, the data matching module 2036 may perform text analysis on character strings contained in the purchase request data, supporting voucher data, and usage detail data using a method such as text mining to infer relationships between the purchase request data, supporting voucher data, and usage detail data and perform the association. Furthermore, the data matching module 2036 may, for example, perform the association based on a machine learning model that infers relationships between the purchase request data, supporting voucher data, and usage detail data and outputs correspondences. This machine learning model may, for example, include an OCR model, an object detection model, R CNN, Fast R CNN, Faster R CNN, etc.

[0066] If it is determined that no corresponding data exists among the purchase request data, the evidence data, and the usage details data, the data matching module 2036 may match the existing data.

[0067] The matching result presentation module 2037 controls the process of presenting to the user two or more pieces of data among the purchase request data, supporting voucher data, and usage detail data that have been matched by the data matching module 2036. The matching result presentation module 2037 transmits the purchase request data, supporting voucher data, usage detail data, and data indicating the correspondence between these pieces of data to the terminal device 10 and displays them on the display 150, thereby presenting them to the user.

[0068] At this time, the matching result presentation module 2037 presents the purchase application data, supporting document data, and usage detail data to the user in a selectable manner, using the functions of the matching data input acceptance module 2038 and the settlement module 2039, which will be described later.

[0069] When the data matching module 2036 determines that no corresponding data exists among the purchase requisition data, supporting voucher data, and usage detail data, and there is data that has not been matched, the matching result presentation module 2037 may present to the user some of the matched purchase requisition data, supporting voucher data, and usage detail data, excluding any of the purchase requisition data, supporting voucher data, and usage detail data that has not been matched. Furthermore, when the data matching module 2036 has purchase requisition data, supporting voucher data, and usage detail data that has not been matched, the matching result presentation module 2037 may present to the user a list of the purchase requisition data, supporting voucher data, and usage detail data that has not been matched.

[0070] When there is purchase requisition data, supporting voucher data, or usage detail data that has not been matched by the data matching module 2036, the matching data input acceptance module 2038 controls processing for accepting input of the matching through operation input on the terminal device 10 by the user of the purchase requisition management system 1. At this time, the matching data input acceptance module 2038 may accept input of the matching of any two or more of the purchase requisition data, supporting voucher data, and usage detail data presented as a list by the matching result presentation module 2037. Furthermore, the matching data input acceptance module 2038 may accept input of the matching of either or both of the purchase requisition data and supporting voucher data through operation input on the terminal device 10 by the user.

[0071] Furthermore, the matching data input acceptance module 2038 controls the process of accepting input to correct any of the associated purchase requisition data, supporting voucher data, or usage detail data presented by the matching result presentation module 2037. The matching data input acceptance module 2038 accepts input to correct the association from the user, as the association by the data matching module 2036 may be incorrect. Therefore, the matching data input acceptance module 2038 accepts input of the correct association for any of the purchase requisition data, supporting voucher data, or usage detail data, by operation input from the terminal device 10 by the user of the purchase requisition management system 1.

[0072] The settlement module 2039 controls the process of settling the purchase request data for the associated purchase request data, supporting document data, and usage detail data presented by the matching result presentation module 2037, in response to operation input on the terminal device 10 by the user of the purchase request management system 1. Specifically, the settlement module 2039 accepts the selection of the purchase request data for which settlement processing is to be performed in response to operation input on the terminal device 10 by the user, registers a status indicating that payment has been completed, and performs so-called clearing processing to perform the settlement processing.

[0073] Furthermore, when budgets for various purchases are managed, the settlement module 2039 may perform processing to deduct the payment amount related to the purchase request data for which settlement processing has been performed from the budget amount. For example, when the matching result presentation module 2037 presents the purchase request data, supporting document data, and usage detail data, the budget amount for various purchases may be presented by transmitting it to the terminal device 10 and displaying it on the display 150, and if a reduction has been made, the budget amount after the reduction may be presented.

[0074] <2 Data Structure> Fig. 4 is a diagram showing an example of the data structure of the purchase request database 2021 in Fig. 3. Fig. 5 is a diagram showing an example of the data structure of the evidence database 2022 in Fig. 3. Fig. 6 is a diagram showing an example of the data structure of the usage details database 2023 in Fig. 3.

[0075] As shown in Figure 4, each record in the purchase request database 2021 includes an item "application ID," an item "applicant ID," an item "applicant name," an item "application date," an item "purchase request details," etc.

[0076] The item "application ID" is information that identifies each purchase application data item related to various purchases that are subject to management by the purchase application management system 1.

[0077] The item "applicant ID" is information that identifies each user who is an employee who inputs purchase application data and is subject to management by the purchase application management system 1.

[0078] The item "applicant name" is the name of the user who is an employee who is subject to management by the purchase application management system 1 and who inputs the purchase application data.

[0079] The item "application date" is information on the date on which purchase application data, which is subject to management by the purchase application management system 1, was entered.

[0080] The item "purchase request content details" is data on the contents of the purchase request data to be managed by the purchase request management system 1, and specifically includes the items "purchase item" and "amount", etc.

[0081] The item "Purchase item" is information about items desired to be purchased in connection with the request, entered by the user when entering purchase request data, which is managed by the purchase request management system 1. For example, as shown in Figure 4, the item "Purchase item" stores information such as "travel expenses" and "equipment purchase expenses."

[0082] The item "amount" is information on the amount of the item or the like desired to be purchased in the request, which is managed by the purchase request management system 1 and entered by the user when inputting the purchase request data.

[0083] The purchase request data acceptance module 2033 of the server 20 increases or decreases the number of records in the purchase request database 2021 as purchase request data is accepted from users of the purchase request management system 1.

[0084] As shown in Figure 5, each record in the evidence database 2022 includes an item "Evidence ID," an item "Applicant ID," an item "Applicant Name," an item "Application ID," an item "Evidence Transmission Date," an item "Evidence Image Data," etc.

[0085] The item "voucher ID" is information that identifies each piece of voucher data related to payment for various purchases that are managed by the purchase request management system 1.

[0086] The item “Applicant ID” is information that identifies each user who is an employee who entered supporting document data and is subject to management by the purchase request management system 1, and corresponds to the item “Applicant ID” in the purchase request database 2021.

[0087] The item “Applicant Name” is the name of the employee user who entered the supporting document data and is subject to management by the purchase request management system 1, and corresponds to the item “Applicant ID” in the purchase request database 2021.

[0088] The item "application ID" is information that identifies each purchase request data item related to various purchases that are managed by the purchase request management system 1, and corresponds to the item "application ID" in the purchase request database 2021. This item is stored to indicate the correspondence between the purchase request data and supporting data when they are associated by the data matching module 2036 of the server 20.

[0089] The item "voucher transmission date" is information on the date on which voucher data, which is managed by the purchase request management system 1, was transmitted.

[0090] The item "voucher image data" is voucher data that is managed by the purchase request management system 1. The item "voucher image data" may store voucher data in a data format such as PDF as is, or may store a link to another storage location.

[0091] The voucher data reception module 2034 of the server 20 adds a record to the voucher database 2022 upon receiving voucher data from a user of the purchase request management system 1.

[0092] As shown in Figure 6, each record in the usage details database 2023 includes the items "Details ID", "Applicant ID", "Applicant Name", "Application ID", "Transaction Date", and "Usage Details", etc.

[0093] The item "detail ID" is information that identifies each piece of credit card transaction detail data that is managed by the purchase request management system 1.

[0094] The item “applicant ID” is information that identifies each user who is an employee involved in the use of a credit card and is subject to management by the purchase request management system 1, and corresponds to the item “applicant ID” in the purchase request database 2021.

[0095] The item “applicant name” is the name of a user who is an employee and is involved in the use of a credit card, and is subject to management by the purchase request management system 1, and corresponds to the item “applicant ID” in the purchase request database 2021.

[0096] The item "application ID" is information that identifies each purchase request data item related to various purchases that are managed by the purchase request management system 1, and corresponds to the item "application ID" in the purchase request database 2021. This item is stored to indicate the correspondence between the purchase request data and the usage detail data when they are associated by the data matching module 2036 of the server 20.

[0097] The item "transaction date" is information on the date of a purchase using a credit card, which is managed by the purchase request management system 1.

[0098] The item "usage details" is data on the contents of the usage statement data that is managed by the purchase request management system 1, and specifically includes the items "store used" and "amount", etc.

[0099] The item "Store Used" is information on the store (credit card affiliated store) where the purchase related to the credit card was made, which is managed by the purchase request management system 1.

[0100] The item "amount" is information on the amount of a purchase made using a credit card, which is managed by the purchase request management system 1.

[0101] The usage statement data acquisition module 2035 of the server 20 increases or decreases the number of records in the usage statement database 2023 as it acquires usage statement data for credit card use from the credit card payment company.

[0102] <3 operations> Hereinafter, the purchase application acceptance process, the evidence data acceptance process, the matching process, and the expense settlement process performed by the purchase application management system 1 in the first embodiment will be described with reference to FIGS.

[0103] FIG. 7 is a flowchart showing an example of the flow of purchase request reception processing by the purchase request management system 1.

[0104] In step S121, the purchase request data acceptance module 2033 of the server 20 accepts, via the communication unit 201, purchase request data regarding various purchases entered by a user applying for the purchase of materials, equipment, etc., or travel expenses for business trips, etc., transmitted from the terminal device 10.

[0105] In step S122, the purchase request data acceptance module 2033 of the server 20 stores the purchase request data accepted from the user in the purchase request database 2021.

[0106] As described above, the purchase request management system 1 receives and stores purchase request data.

[0107] FIG. 8 is a flowchart showing an example of the flow of the voucher data reception process performed by the purchase application management system 1.

[0108] In step S221, the voucher data receiving module 2034 of the server 20 receives, via the communication unit 201, the voucher data sent from the terminal device 10 and received when the user pays for various purchases using a credit card.

[0109] In step S222, the evidence data receiving module 2034 of the server 20 stores the evidence data received from the user in the evidence database 2022.

[0110] As described above, the purchase application management system 1 receives and stores voucher data.

[0111] FIG. 9 is a flowchart showing an example of the flow of the matching process performed by the purchase request management system 1.

[0112] In step S321, the usage statement data acquisition module 2035 of the server 20 accepts, via the communication unit 201, usage statement data acquired in cooperation with the credit card payment provider, showing that the user paid for various purchases using a credit card.

[0113] In step S322, the usage statement data acquisition module 2035 of the server 20 stores the usage statement data acquired from the credit card payment company in the usage statement database 2023.

[0114] In step S323, the data matching module 2036 of the server 20 matches the purchase request data received in step S121, the supporting voucher data received in step S221, and the usage detail data acquired in step S321, and establishes correspondence between them. In step S323, the purchase request data, supporting voucher data, and usage detail data are read, and the corresponding supporting voucher data and usage detail data are determined based on information included in the purchase request data, such as the purchase date, purchased item, and amount of the application target.

[0115] In step S324, the matching result presentation module 2037 of the server 20 presents to the user two or more of the purchase request data, supporting voucher data, and usage detail data that were associated in step S323. In step S324, for example, the purchase request data, supporting voucher data, usage detail data, and data indicating the correspondence between these data are transmitted to the terminal device 10 and displayed on the display 150, thereby presenting them to the user.

[0116] In step S325, the matching data input acceptance module 2038 of the server 20 accepts input to correct any of the associated purchase requisition data, supporting voucher data, and usage detail data presented in step S324. Also, in step S325, for purchase requisition data, supporting voucher data, and usage detail data that have not been associated, input to associate any two or more of the purchase requisition data, supporting voucher data, and usage detail data may be accepted.

[0117] As described above, usage detail data is accepted and stored in the purchase request management system 1. Furthermore, the purchase request data, evidence data, and usage detail data are associated with each other and presented to the user.

[0118] FIG. 10 is a flowchart showing an example of the flow of settlement processing by the purchase application management system 1.

[0119] In step S421, the settlement module 2039 of the server 20 performs settlement processing for the associated purchase request data, supporting document data, and usage detail data in response to operation input from the terminal device 10 by the user of the purchase request management system 1. In step S421, based on the selection of purchase request data for which settlement processing is to be performed, transmitted from the terminal device 10, a status indicating that payment has been completed is registered, and settlement processing is performed by performing so-called clearing processing.

[0120] As described above, the purchase application management system 1 performs settlement processing for the purchase application data.

[0121] <4 Screen example> Hereinafter, with reference to FIG. 11, an example of a screen in which the purchase request data, supporting document data, and usage detail data are associated by the purchase request management system 1 and presented to the user will be described.

[0122] Fig. 11 is a diagram showing an example of a screen of a purchase request list displayed on the terminal device 10. The screen example of Fig. 11 shows an example of a screen displayed on the display 150 of the terminal device 10, in which the purchase request data, supporting document data, and usage detail data are associated with each other. This corresponds to step S324 in Fig. 9.

[0123] 11, a window 1031 is displayed on the display 150 of the terminal device 10. This window 1031 displays a purchase request list screen 1031a, which is a list of purchase request data relating to various purchases.

[0124] The purchase request list screen 1031a displays a purchase request data display field 1031b showing the contents of the purchase request, a usage detail data display field 1031c obtained in cooperation with the payment service provider of the credit card used, and a voucher data display field 1031d relating to payments made using a credit card for various purchases.

[0125] 11, a purchase request data display field 1031b, a usage statement data display field 1031c, and a supporting document data display field 1031d are displayed side by side, making it possible to grasp at a glance the correspondence between the purchase request data, supporting document data, and usage statement data. Furthermore, if there is data that has not been matched or if the correspondence is incorrect, the user can easily correct it by operating the screen.

[0126] 11 is merely an example, and other screen examples may be configured to display a list of details. For example, the list of details may be configured to display the above-mentioned usage detail data, purchase request data, and supporting document data in a correlated state.

[0127] <Summary> As described above, according to this embodiment, purchase request data indicating the contents of a purchase request is received from a user, supporting data relating to payments made using a credit card for various purchases is received from the user, and usage statement data is obtained in cooperation with the payment service provider of the credit card used. The purchase request data, supporting data, and usage statement data are associated and presented to the user. The settlement process for the purchase request data is performed based on instructions input by the user. This makes it easy to understand the association between the purchase request data, supporting data, and usage statement data, thereby reducing the search and input work required by accounting personnel at companies, etc. This makes it easier to understand the status of purchases at a company and facilitates purchase management.

[0128] Furthermore, according to this embodiment, if there is data that has not been associated or if the association is incorrect, the user is allowed to input an association, which allows the association of each data item to be easily corrected.

[0129] Although the embodiments of the disclosure have been described above, they can be implemented in various other forms and can be implemented with various omissions, substitutions, and modifications. These embodiments, modifications, and omissions, substitutions, and modifications are included in the technical scope of the claims and their equivalents.

[0130] <Additional Notes> The matters explained in the above embodiments will be supplemented below.

[0131] (Supplementary Note 1) A program for executing on a computer having a processor 29 and a memory 25, for processing the settlement of payments for business purchase applications, wherein the memory 25 stores purchase application data relating to the purchase (S122), and the program causes the processor 29 to execute the following steps: accepting supporting data relating to payment using a credit card as input from a payer who has made the payment for the purchase (S221); acquiring credit card usage detail data from the credit card payment service provider (S321); matching the purchase application data, supporting data, and usage detail data to establish correspondence (S323); presenting two or more of the matched purchase application data, supporting data, and usage detail data to the user (S324); and performing the settlement process for the presented purchase application data based on instructions input from the user (S421).

[0132] (Appendix 2) A program as described in (Appendix 1), in which, if, in the step of matching, there is any data among the purchase request data, supporting voucher data, and usage detail data that has not been matched, in the step of presenting two or more data to the user, the matched purchase request data, supporting voucher data, and usage detail data are presented to the user, excluding any of the purchase request data, supporting voucher data, and usage detail data that has not been matched.

[0133] (Appendix 3) A program described in (Appendix 1) or (Appendix 2), in which, if there is any data among the purchase request data, supporting data, and usage detail data that has not been matched in the step of matching, the program further executes a step of presenting to the user a list of the purchase request data, supporting data, and usage detail data that has not been matched.

[0134] (Appendix 4) The program described in (Appendix 3) further executes a step (S325) of accepting input from the user of correspondence between any two or more of the purchase request data, supporting document data, and usage detail data presented as a list.

[0135] (Appendix 5) A program described in (Appendix 2), in which, if there is purchase request data or supporting data that has not been matched in the matching step, the program further executes a step of accepting purchase request data or supporting data through input from the user.

[0136] (Appendix 6) A program described in (Appendix 1) or (Appendix 2), which further executes a step (S325) of accepting input from the presented user to modify any of the associated purchase request data, supporting document data, or usage detail data.

[0137] (Appendix 7) A program as described in (Appendix 1), in which the memory stores budget data for managing a budget for purchases, and the program further executes a step of deducting the payment amount related to purchase request data for which settlement processing has been performed from the amount of the budget for purchases and managing the amount.

[0138] (Appendix 8) The program according to (Appendix 7), further comprising the step of presenting the user with a budget amount for the purchase.

[0139] (Supplementary Note 9) An information processing device that includes a control unit 203 and a memory 25 (storage unit 202) and performs settlement processing for payments for business purchase applications, wherein the memory 25 stores purchase application data relating to the purchase (S122), and the control unit 203 executes the following steps: a step (S221) of accepting supporting data relating to payment using a credit card based on input from a payer who has made the payment for the purchase; a step (S321) of acquiring credit card usage detail data from a credit card payment provider; a step (S323) of matching the purchase application data, supporting data, and usage detail data to establish correspondence; a step (S324) of presenting two or more of the matched purchase application data, supporting data, and usage detail data to a user; and a step (S421) of performing settlement processing for the presented purchase application data based on instruction input from the presented user.

[0140] (Appendix 10) A method for processing the settlement of payments for business purchase applications, executed by a computer having a processor 29 and a memory 25, the method comprising the steps of: processor 29 receiving supporting data for a payment made using a credit card as input from a payer who has made the payment for the purchase (S221); acquiring credit card usage detail data from a credit card payment service provider (S321); matching and associating the purchase request data, supporting data, and usage detail data (S323); presenting two or more of the associated purchase request data, supporting data, and usage detail data to a user (S324); and performing the settlement process for the presented purchase request data based on instructions input by the user (S421). [Explanation of symbols]

[0141] 1: Purchasing requisition management system 10: Terminal device 10A: Terminal equipment 10B: Terminal device 13: Input device 14: Output device 15: Memory 16: Storage section 19: Processor 20: Server 25: Memory 26: Storage 29: Processor 80: Network 81: Wireless base station 82: Wireless LAN router 111: Antenna 112: Antenna 121: First wireless communication unit 122: Second wireless communication unit 130: Operation reception unit 131: Keyboard 132: Mouse 140: Audio processing unit 141:Mike 142: Speaker 150: Display 160: Camera 170: Storage section 171: User information 180: Control unit 181: Input operation reception unit 182: Transmitter / receiver 183: Notification control section 184: Data processing section 201: Communications Department 202: Storage section 203: Control unit 2021: Purchase Requisition Database 2022: Evidence database 2023: Usage details database 2031: Receiving control module 2032: Transmission control module 2033: Purchase request data reception module 2034: Voucher data reception module 2035: Usage details data acquisition module 2036: Data matching module 2037: Matching result presentation module 2038: Matching data entry acceptance module 2039: Settlement module

Claims

1. A program for causing a computer having a processor and a memory to execute a payment settlement process for a purchase application related to a business, the memory stores purchase requisition data relating to the purchase; The program causes the processor to: receiving, by input from a payer who has made a payment for the purchase, evidence data relating to the payment using a credit card; obtaining transaction details data for the credit card from a payment service provider of the credit card; a step of associating the purchase request data, the evidence data, and the usage detail data by matching them with each other; presenting to a user two or more of the associated purchase request data, the supporting document data, and the usage detail data; and performing a settlement process for the presented purchase request data in response to an instruction input from the presented user.

2. In the step of associating, if there is any data that has not been associated among the purchase request data, the evidence data, and the usage detail data, The program of claim 1, wherein in the step of presenting the two or more data to the user, the purchase request data, the supporting document data, and the usage detail data that have been matched are presented to the user, excluding any of the purchase request data, the supporting document data, and the usage detail data that have not been matched.

3. In the step of associating, if there is any data that has not been associated among the purchase request data, the evidence data, and the usage detail data, The program further comprises:

3. The program according to claim 1, further comprising: a step of presenting to a user a list of the purchase request data, the evidence data, and the usage detail data that have not been associated with each other.

4. The program further comprises:

4. The program according to claim 3, further comprising a step of receiving an input from a user associating any two or more of the purchase request data, the evidence data, and the usage detail data presented as a list.

5. In the step of performing the association, if there is any of the purchase request data or the evidence data that has not been associated, The program further comprises:

3. The program according to claim 2, further comprising: a step of accepting the purchase request data or the evidence data based on an input from a user.

6. The program further comprises: The program according to claim 1 or claim 2, further comprising a step of receiving input from the presented user to modify any of the associated purchase request data, the supporting document data, or the usage details data.

7. the memory stores budget data for managing a budget for the purchase; The program further comprises:

2. The program according to claim 1, further comprising: a step of managing the payment amount related to the purchase request data for which the settlement process has been performed by deducting the payment amount from the budget amount for the purchase.

8. The program further comprises:

8. The program according to claim 7, further comprising the step of presenting a budget amount for the purchase to a user.

9. An information processing device that includes a control unit and a memory, and performs a payment settlement process for a purchase application related to a business, the memory stores purchase requisition data relating to the purchase; The control unit receiving, by input from a payer who has made a payment for the purchase, evidence data relating to the payment using a credit card; obtaining transaction details data for the credit card from a payment service provider of the credit card; a step of associating the purchase request data, the evidence data, and the usage detail data by matching them with each other; presenting to a user two or more of the associated purchase request data, the supporting document data, and the usage detail data; and performing a settlement process for the presented purchase request data in response to an instruction input from the presented user. and a step of generating a plurality of information.

10. 1. A method for processing payment settlement for a business purchase request, the method being executed by a computer having a processor and a memory, the method comprising: the memory stores purchase requisition data relating to the purchase; The method further comprises the processor: receiving, by input from a payer who has made a payment for the purchase, evidence data relating to the payment using a credit card; obtaining transaction details data for the credit card from a payment service provider of the credit card; a step of associating the purchase request data, the evidence data, and the usage detail data by matching them with each other; presenting to a user two or more of the associated purchase request data, the supporting document data, and the usage detail data; and performing a payment process for the presented purchase request data in response to an instruction input from the presented user.

Images