System, method, and program for managing evidence data

Abstract

Assists in managing supporting data. [Solution] A business support server 10 according to one embodiment of the present invention provides business support tools for supporting business operations in a company to personnel in a management department or the like who use a management terminal 20, and to users who use user terminals 30, both of which are communicatively connected via a communication network NW. The business support server 10 acquires supporting data and payment data, and identifies corresponding supporting data and payment data based on this data, making it possible to acquire supporting data of a voucher that indicates the transaction details of a payment made using a payment card and automatically link it to the corresponding payment data.

Description

[Technical Field]

[0001] The present invention relates to a technique for managing evidence data. [Background technology]

[0002] Conventionally, in systems for supporting accounting processing, electronic data of supporting documents that show transaction details is managed. For example, Patent Document 1 below discloses a system that outputs stored supporting document data and journal data, accepts an operation to specify journal data to be associated with the supporting document data from the journal data, and associates the supporting document data with the journal data. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Publication No. 2019-023793 Summary of the Invention [Problem to be solved by the invention]

[0004] However, in the conventional technology described above, a user operation is required to associate supporting data with journal data, which can increase the workload in accounting departments, etc. Therefore, it is desirable to realize a system that can reduce the workload associated with managing such supporting data.

[0005] One of the objects of the embodiment of the present invention is to support the management of evidence data. [Means for solving the problem]

[0006] A system according to one embodiment of the present invention is a system having one or more computer processors, which perform operations including the steps of acquiring voucher data relating to a voucher, acquiring payment data relating to a payment made by a payment card, and identifying corresponding voucher data and payment data based on the voucher data and the payment data.

[0007] A method according to one embodiment of the present invention is a method executed by one or more computers, and includes the steps of acquiring voucher data related to a voucher, acquiring payment data related to a payment made by a payment card, and identifying corresponding voucher data and payment data based on the voucher data and the payment data.

[0008] A program according to one embodiment of the present invention causes one or more computers to perform operations including the steps of acquiring supporting document data relating to a supporting document, acquiring payment data relating to a payment made by a payment card, and identifying corresponding supporting document data and payment data based on the supporting document data and the payment data. [Effects of the Invention]

[0009] Various embodiments of the present invention support the management of evidence data. [Brief explanation of the drawings]

[0010] [Figure 1] 1 is a configuration diagram that schematically shows the configuration of a network including a business support server 10 according to an embodiment of the present invention. [Figure 2] FIG. 15 is a diagram illustrating an example of information managed by a user information table 1511. [Figure 3] FIG. 15 is a diagram illustrating an example of information managed by a card information table 1512. [Figure 4] FIG. 15 is a diagram illustrating an example of information managed by a payment data management table 1513. [Figure 5]FIG. 15 is a diagram illustrating information managed by a voucher data management table 1514. [Figure 6] FIG. 15 is a diagram illustrating an example of information managed by an association management table 1515. [Figure 7] 10 is a flowchart illustrating a process executed by the business support server 10 when registering evidence data. [Figure 8] FIG. 2 is a diagram illustrating an example of an input message 200. [Figure 9] FIG. 2 is a diagram illustrating an example of a response message 210. [Figure 10] 10 is a flowchart illustrating a process executed by the business support server 10 when collectively identifying payment data corresponding to evidence data that is not linked to payment data. DETAILED DESCRIPTION OF THE INVENTION

[0011] Hereinafter, embodiments of the present invention will be described with reference to the drawings. In each drawing, the same reference numerals may be used to refer to the same or similar components. Other objects of the embodiments of the present invention will become apparent by reading the entire specification.

[0012] FIG. 1 is a schematic diagram illustrating the configuration of a network including a business support server 10 according to an embodiment of the present invention. As illustrated, the business support server 10 is communicatively connected to a management terminal 20 and a user terminal 30 via a communications network NW such as the Internet. The management terminal 20 is used by personnel in a company's management department (e.g., accounting department), and the user terminal 30 is used by general users such as company employees. While FIG. 1 illustrates only one management terminal 20 and one user terminal 30, the business support server 10 is communicatively connected to multiple management terminals 20 and multiple user terminals 30. The business support server 10 provides business support tools for supporting business operations at a company to personnel in the management department who use the management terminal 20 and users who use the user terminal 30. The business support server 10 is an example of a device that implements all or part of the system of the present invention.

[0013] First, we will explain the hardware configuration of the business support server 10. The business support server 10 is configured as a general computer, and as shown in Fig. 1, includes a computer processor 11, a main memory 12, an input / output I / F 13, a communication I / F 14, and a storage (storage device) 15, and these components are electrically connected via a bus or the like (not shown).

[0014] The computer processor 11 is configured with a CPU, GPU, FPGA, etc., or a circuit including any of them, and loads various programs stored in the storage 15, etc., into the main memory 12 and executes various instructions included in the programs. The main memory 12 is configured with, for example, a DRAM, etc.

[0015] The input / output I / F 13 includes various input / output devices for exchanging information with an operator, etc. The input / output I / F 13 includes, for example, information input devices such as a keyboard and a pointing device (e.g., a mouse, a touch panel, etc.), a voice input device such as a microphone, and an image input device such as a camera. The input / output I / F 13 also includes an image output device such as a display, and an audio output device such as a speaker.

[0016] The communication I / F 14 is implemented as hardware such as a network adapter, various communication software, or a combination of these, and is configured to enable wired or wireless communication via a communication network NW or the like.

[0017] The storage 15 is configured, for example, by a magnetic disk or flash memory. The storage 15 stores various programs including an operating system, various data, and the like. For example, the storage 15 has various tables 151 that manage various information. The storage 15 also stores, for example, a server-side program 40 according to an embodiment of the present invention. The program 40 is a program that causes the business support server 10 to function as all or part of a system for providing business support tools. At least a portion of the server-side program 40 can be configured to be executed on the management terminal 20 or the user terminal 30 via a management terminal-side program 42 or a user terminal-side program 44, which will be described later.

[0018] In this embodiment, the business support server 10 may be configured using a plurality of computers each having the above-described hardware configuration. For example, the business support server 10 may be configured by one or a plurality of server devices.

[0019] The business support server 10 configured in this manner functions as a web server and an application server, and executes various processes in response to requests from the management terminal side program 42 or the user terminal side program 44 installed in the management terminal 20 or the user terminal 30, and transmits screen data (e.g., HTML data) and control data according to the results of the processes to the management terminal 20 or the user terminal 30. The management terminal 20 or the user terminal 30 outputs a web page or other screen based on the received data.

[0020] Next, we will explain the hardware configuration of the management terminal 20. The management terminal 20 is configured as a general computer, and as shown in Fig. 1, it includes a computer processor 21, a main memory 22, an input / output I / F 23, a communication I / F 24, and a storage (storage device) 25, with each of these components being electrically connected via a bus or the like (not shown).

[0021] The computer processor 21 is configured with a CPU, GPU, FPGA, etc., or a circuit including any of them, and loads various programs stored in the storage 25, etc., into the main memory 22 and executes various instructions included in the programs. The main memory 22 is configured with, for example, a DRAM, etc.

[0022] The input / output I / F 23 includes various input / output devices for exchanging information with an operator, etc. The input / output I / F 23 includes, for example, information input devices such as a keyboard and a pointing device (e.g., a mouse, a touch panel, etc.), audio input devices such as a microphone, and image input devices such as a camera. The input / output I / F 23 also includes an image output device such as a display, and an audio output device such as a speaker.

[0023] The communication I / F 24 is implemented as hardware such as a network adapter, various communication software, or a combination thereof, and is configured to realize wired or wireless communication via a communication network NW or the like.

[0024] The storage 25 is configured, for example, by a magnetic disk or flash memory. The storage 25 stores various programs including an operating system, various data, and the like. The programs stored in the storage 25 can be downloaded and installed from an application market or the like. The storage 25 also stores the management terminal-side program 42 described above. The program 42 can be configured as a web browser or other application (for example, a business support tool application for the management department, etc.), and can be configured to execute at least a part of the server-side program 40, as described above.

[0025] In this embodiment, the management terminal 20 may be configured as a smartphone, a tablet terminal, a wearable device, a personal computer, or the like.

[0026] The person operating the management terminal 20 configured in this manner can use the management functions of the business support tools provided by the business support server 10 by communicating with the business support server 10 via the management terminal side program 42 installed in storage 25, etc.

[0027] Next, we will explain the hardware configuration of the user terminal 30. Like the above-mentioned management terminal 20, the user terminal 30 is configured as a general computer, and as shown in Fig. 1, it includes a computer processor 31, a main memory 32, an input / output I / F 33, a communication I / F 34, and a storage (storage device) 35, and these components are electrically connected via a bus or the like (not shown).

[0028] The storage 35 stores the above-mentioned user terminal-side program 44. The program 44 is configured as a web browser or other application (for example, an application for general users of a business support tool), and can be configured to execute at least a part of the server-side program 40 as described above.

[0029] In this embodiment, the user terminal 30 may be configured as a smartphone, a tablet terminal, a wearable device, a personal computer, or the like.

[0030] A user operating a user terminal 30 configured in this manner can utilize the user functions of the business support tools provided by the business support server 10 by communicating with the business support server 10 via a user terminal side program 44 installed in storage 35 or the like.

[0031] Next, we will explain the functions of the business support server 10 configured as above. The computer processor 11 of the business support server 10 is configured to function as a management function control unit 112 and a business support control unit 114 by executing instructions included in a program (for example, at least a part of the server-side program 40) loaded into the main memory 12, as shown in Figure 1.

[0032] The management function control unit 112 is configured to execute various processes related to the control of the management functions of the business support tool. For example, the management function control unit 112 transmits screen data and control data of various screens related to the management functions to the management terminal 20 or the user terminal 30, executes various processes in response to operation input by an operator via the screens output on the management terminal 20 or the user terminal 30, and transmits screen data and control data according to the results of the processes to the management terminal 20 or the user terminal 30. The management functions controlled by the management function control unit 112 include, for example, login processing (user authentication) and management of various master information.

[0033] The business support control unit 114 is configured to execute various processes for controlling business support. For example, the business support control unit 114 transmits screen data and control data of various screens for controlling business support to the management terminal 20 or the user terminal 30, executes various processes in response to operation input by an operator via the screen output on the management terminal 20 or the user terminal 30, and transmits screen data, control data, etc. according to the results of the processes to the management terminal 20 or the user terminal 30.

[0034] In this embodiment, the business support control unit 114 is configured to acquire voucher data related to the voucher. The voucher is documentary evidence showing a transaction, and includes, but is not limited to, receipts, invoices, and delivery notes. The voucher data is data related to the voucher, and typically includes transaction information related to the transaction shown by the voucher (for example, transaction date, transaction amount, recipient information, issuer information, etc.).

[0035] The business support control unit 114 is also configured to acquire payment data related to payments made by payment card. A payment card is a card that can be used to pay for goods (including services), and includes, but is not limited to, credit cards, debit cards, and prepaid cards. The payment data is acquired, for example, from the system of the business issuing the payment card. The payment data can also be said to be data corresponding to the payment card's usage details. Furthermore, when a business issuing a payment card provides a business support tool, the payment data can be acquired based on authorization data and clearing data transmitted from a payment terminal or the like installed at the payment card's affiliated store.

[0036] In this embodiment, the business support control unit 114 is configured to identify corresponding supporting data and payment data based on the supporting data and payment data (link the supporting data and payment data). For example, the business support control unit 114 identifies corresponding supporting data and payment data based on amount information and date information included in the supporting data and amount information and date information included in the payment data. The correspondence between the identified supporting data and payment data is managed, for example, in a specific table included in the various tables 151.

[0037] In this way, the business support server 10 in this embodiment acquires supporting data and payment data, and identifies corresponding supporting data and payment data based on these data, so that supporting data of a supporting document showing the transaction details of payment using a payment card can be acquired and automatically linked to the corresponding payment data. In other words, the business support server 10 supports the management of supporting data, thereby reducing the burden on, for example, personnel in the management department and users such as employees.

[0038] In this embodiment, the acquisition of evidential data can be realized in various ways. For example, the business support control unit 114 can be configured to acquire evidential data based on image data of the evidential data attached to an email. For example, the business support control unit 114 acquires image data attached to an email addressed to a specific destination, and acquires evidential data based on the image data. For example, the business support control unit 114 converts the image data of the evidential data into text data using technology such as OCR, and acquires evidential data based on the text data (rule-based). The image data is stored in the storage 15, etc. This configuration makes it possible to easily acquire evidential data based on image data attached to an email.

[0039] In this case, the business support control unit 114 may be configured to acquire email information about the email as at least a part of the supporting evidence data and, based on the email information, identify payment data corresponding to the supporting evidence data. The email information includes, but is not limited to, the sender address and destination address of the email. For example, the business support control unit 114 identifies a payment card based on the email information and identifies payment data related to the payment made by the payment card (associated with the payment card) as payment data corresponding to the supporting evidence data. For example, multiple pieces of payment data for the payment card identified based on the email information are extracted as candidates for payment data to be linked to the supporting evidence data, and payment data to be linked to the supporting evidence data is identified from these multiple candidates. For example, if the destination address of the email is a dedicated address for receiving invoices, the payment data of the payment card pre-assigned to that dedicated address is identified as payment data corresponding to the supporting evidence data acquired based on image data attached to the email. This configuration makes it possible to identify corresponding payment data based on information about the email to which image data of the supporting evidence is attached.

[0040] Furthermore, for example, the business support control unit 114 may be configured to acquire evidence data based on image data of the evidence input by the user. For example, the business support control unit 114 presents a screen to the user that allows the input (e.g., upload) of image data of the evidence (e.g., transmits screen data and control data of the screen to the user terminal 30), and accepts the image data input via the screen. For example, as described above, the business support control unit 114 converts the image data of the evidence into text data using technology such as OCR, and acquires the evidence data based on the text data. This configuration makes it possible to easily acquire evidence data based on image data individually input by the user.

[0041] In this case, the business support control unit 114 may be configured to acquire user information about the user as at least a part of the supporting data and identify payment data corresponding to the supporting data based on the user information. The user information may include, but is not limited to, a user ID identifying the corresponding user and the organization (division, department, section, etc.) to which the user belongs. For example, the business support control unit 114 may identify a payment card based on the user information and identify payment data related to a payment made with the payment card as payment data corresponding to the supporting data. For example, multiple payment data items of payment cards available to the user identified based on the user information may be extracted as candidates for payment data to be linked to the supporting data, and the payment data to be linked to the supporting data may be identified from among these multiple candidates. For example, a payment card for payment may be pre-set for an individual user or for an organization to which multiple users belong. This configuration enables the identification of corresponding payment data based on information about the user who inputs image data of the supporting data.

[0042] In this embodiment, a trained model generated through machine learning may be used when acquiring supporting data from image data of supporting documents. For example, the business support control unit 114 inputs text data based on the image data of the supporting documents, or the image data itself, into a trained model and acquires transaction information output from the trained model as at least a portion of the supporting data. The trained model may be configured, for example, as a large-scale language model (LLM) that outputs transaction information when a prompt is input instructing the system to output transaction information based on input data (e.g., text data based on the image data, or the image data itself). In such a case, the input prompt includes the image data of the supporting documents or the text data of the supporting documents, information indicating an instruction to acquire the transaction information, format information for the transaction information to be output, etc. For example, if the supporting document is an invoice that includes both a pre-discount amount and a discounted amount, a system using a trained model may more easily recognize the discounted amount as the actual transaction amount compared to a rule-based system. This configuration may improve the quality of the process of acquiring supporting data from image data of supporting documents.

[0043] Furthermore, the business support control unit 114 can be configured to, in response to the acquisition of specific supporting data, identify payment data corresponding to the specific supporting data from among a first plurality of payment data (acquired and accumulated in advance), and, if such payment data cannot be identified, subsequently identify payment data corresponding to the specific supporting data from among a second plurality of payment data including newly acquired payment data. Such a configuration makes it possible to identify corresponding payment data in response to the acquisition of supporting data, and to deal with cases where the payment data cannot be identified.

[0044] Conversely, the business support control unit 114 can be configured to, in response to acquisition of specific payment data, identify supporting data corresponding to the specific payment data from among a first plurality of supporting data (acquired and accumulated in advance), and, if such supporting data cannot be identified, subsequently identify supporting data corresponding to the specific payment data from among a second plurality of supporting data including newly acquired supporting data. Such a configuration makes it possible to identify corresponding supporting data in response to acquisition of payment data, and to deal with cases where the supporting data cannot be identified.

[0045] Next, a specific example of one aspect of the business support server 10 of this embodiment having such functions will be described. In this example, the provider of the business support tool is a business that issues credit cards (corporate cards) for businesses, and the business support tool has a function to support business related to the credit cards.

[0046] First, in this example, the information managed by each table included in the various tables 151 will be described. Fig. 2 illustrates information managed by the user information table 1511 in this example. The user information table 1511 in this example manages information related to users (employees of a company) of the business support tool, and as shown in the figure, manages information such as "name," "company ID" identifying the company to which the user belongs, "organization ID" identifying the organization to which the user belongs within the company, and "management department person in charge flag" indicating that the user is in charge of the management department, in association with a "user ID" identifying an individual user.

[0047] 3 illustrates information managed by card information table 1512 in this example. Card information table 1512 in this example manages information related to credit cards used in a company, and as shown, manages information such as a "company ID" that identifies the corresponding company, an "organization ID" that identifies the corresponding organization, and an "email address for receiving invoices" that is set when the credit card is used to settle invoices received via email, in association with a "card number" that identifies an individual credit card. In this way, in this example, credit cards issued to a company are assigned to a specific organization within the company.

[0048] 4 illustrates information managed by payment data management table 1513 in this example. In this example, payment data management table 1513 manages information (payment data) related to payments made by credit card, and as shown in the figure, manages information such as a "card number" identifying the credit card used for the payment, a "date and time of use" which is the date and time the credit card was used (the date and time the payment was made), a "payment amount", "merchant information" which is information about the merchant where the payment card was used, "user memo information" which is a memo (text) entered by the user, and "linked or not" which indicates whether or not there is linking to supporting data, in association with a "payment ID" which identifies an individual payment.

[0049] In this example, when a credit card is used at each affiliated store and payment processing (authorization processing and clearing processing) is performed, payment data is sent from a payment processing system (not shown, which in this example is managed by the provider of the business support tool) to the business support server 10. The business support server 10 then registers the received (acquired) payment data in the payment data management table 1513, specifically inserting a new record and registering the payment ID, card number, usage date and time, payment amount, and affiliated store information.

[0050] 5 illustrates information managed by the supporting document data management table 1514 in this example. In this example, the supporting document data management table 1514 manages information about supporting documents (support document data) and, as shown in the figure, manages information such as a "support document ID" that identifies each individual document, a "support document type" indicating the type of supporting document, an "acquisition date and time," a "user ID" that identifies the user who input the image data of the supporting document, an "email address" indicating the email address of the recipient (the recipient) of the email to which the image data of the supporting document was attached, "image data information" that is information about the image data of the supporting document, a "transaction date" that is the date of the transaction indicated by the supporting document, a "transaction amount" that is the amount of the transaction, "business partner information" that is information (including the name, etc.) about the business partner (the issuer of the supporting document), a "registered business number" that is the registration number of the issuer of the supporting document as a qualified invoice issuer, and a "linked / unlinked" that indicates whether the document is linked to payment data. The supporting document type is set to a value corresponding to one of "receipt," "invoice," "invoice," and "other." The image data information also includes the file name of the image data.

[0051] 6 illustrates information managed by the linking management table 1515 in this example. The linking management table 1515 in this example manages the linking (combination) of corresponding payment data and supporting document data, and as shown in the figure, manages information such as the "registration date and time" which is the date and time when this combination was registered (linked) in association with the combination of a "payment ID" which identifies an individual payment and a "supporting document ID" which identifies an individual support document.

[0052] The information managed by each table in this example has been described above. Next, the processing executed by the business support server 10 and the information output at the user terminal 30 in this example will be described.

[0053] 7 is a flowchart illustrating the processing executed by the business support server 10 when registering evidence data. As shown in the figure, the business support server 10 first waits for the input of image data of the evidence (NO in step S100). Specifically, the business support server 10 waits for the image data of the evidence to be input individually by the user and for an email with the image data of the evidence attached to be received at the email address for receiving invoices.

[0054] The business support tool in this example has a chat function, and users input image data of supporting documents using chat messages in the chat function. Specifically, chat messages input in a specific space (channel) are automatically analyzed for their content (text), etc. If the input chat message is determined to correspond to the input of image data of supporting documents, the attached file is acquired as image data of the supporting documents. For example, the input message 200 illustrated in FIG. 8 contains the text "Please link the supporting documents." and has image data attached (a preview of the attached file is displayed in the preview display area 201), and is therefore determined to correspond to the input of image data of supporting documents. This determination is made using, for example, a trained model such as a large-scale language model.

[0055] Returning to the flowchart in Figure 7, when image data of the supporting document is input (YES in step S100), the business support server 10 extracts transaction information from the image data (step S110). Specifically, the image data attached to the chat message or email is acquired, and the image data is converted into text data using OCR technology, and the transaction information is acquired based on the text data. The transaction information includes the transaction date, transaction amount, customer information, and registered business number.

[0056] In this example, the transaction information is acquired based on the character data using a large-scale language model. Specifically, the business support server 10 generates a prompt to instruct extraction of the transaction information from the character data, inputs the prompt to the large-scale language model, and acquires the transaction information based on the information output from the large-scale language model.

[0057] Next, the business support server 10 registers the supporting document data (step S120). Specifically, a new record is inserted in the supporting document data management table 1514, and each data item including transaction information (transaction date, transaction amount, customer information, and registered business number) is set. Note that the supporting document type is set to a value corresponding to the type of supporting document determined using the large-scale language model. Furthermore, if the image data of the supporting document is input individually by a user (via a chat message), a value corresponding to the user ID in the supporting document data management table 1514 is set, and if the image data is input via email addressed to an email address for receiving invoices, a value corresponding to the email address in the supporting document data management table 1514 is set.

[0058] Then, the business support server 10 identifies the payment data corresponding to the registered evidence data (step S130). Specifically, from among the multiple payment data managed in the payment data management table 1513, payment data that meets the following three conditions is identified. (1) No linking to supporting data (2) The settlement amount matches the transaction amount in the supporting document data. (3) The date of use matches the transaction date of the target supporting document data.

[0059] Next, the business support server 10 registers a combination of the registered evidence data and the payment data identified as the corresponding payment data (step S140). Specifically, a new record is inserted into the link management table 1515, and the payment ID, evidence ID, and registration date and time are set. Note that if no corresponding payment data is identified in step S130, the registration of the combination is skipped.

[0060] FIG. 9 illustrates a response message 210 displayed on the user terminal 30 in response to the registration of a combination of evidence data and payment data when image data of the evidence is individually entered by the user. The message 210 is displayed as a response to the input message 200 described above. As shown, the message 210 displays text indicating that the registration of the evidence data has been completed ("Attachment of this receipt has been completed"), registered transaction information (transaction date, transaction amount, and registered business number), the file name of the corresponding image data, and a preview of the image data. It also includes a memo addition button 212 labeled "Add memo." When the button 212 is selected, an area for entering memos is displayed, allowing the user to enter memos for the payment data (e.g., to be used as a memo for the approver) via the area. The entered memo is registered in the user memo information for the corresponding payment in the payment data management table 1513. Note that an object (such as a button) for canceling the registration (linking) of the combination of the evidence data and the payment data may be placed in the response message 210, thereby enabling the user to cancel the registration. Alternatively, the user may be required to confirm the combination of the evidence data and the payment data before registering it.

[0061] In addition, if the image data of the supporting document is entered via email addressed to an email address for receiving invoices, information similar to the response message 210 described above will be displayed on a screen for managing such invoices (for example, output on the management terminal 20).

[0062] In this example, if two or more payment data are identified as payment data corresponding to the registered supporting data in step S130, the registration of the combination of supporting data and payment data is skipped. However, in another example of this embodiment, if two or more payment data are identified, two or more combinations are registered in a provisional state. The status of combinations, including provisional status, can be managed in the linkage management table 1515. The status of combinations registered in a provisional state can be changed individually by the user or a person in charge in the management department.

[0063] In another example of this embodiment, when the type of supporting document is an invoice, if there is payment data that satisfies conditions (1) and (2) of the above-mentioned conditions (1) to (3), but does not satisfy condition (3), the corresponding combination may be registered in a provisional state (because it is expected that the transaction date (billing date) on the invoice and the usage date (settlement date) in the payment data will not match).

[0064] Furthermore, if there are multiple payment data that satisfy conditions (1) and (2) but do not satisfy condition (3), condition (3) may be changed to the following condition. (3') The date of use is within a specified range (for example, within one month) from the transaction date of the target supporting document data. Furthermore, these conditions may be changed based on the type of evidence. For example, if the type of evidence is a receipt or invoice, condition (3) may be applied, while if the type of evidence is an invoice, condition (3') may be applied (a perfect match of the dates may not be required). Furthermore, the determination of the conditions to be applied may be performed using a large-scale language model. In this case, the input prompt may include image data or text data of the evidence, information indicating instructions for determining the conditions to be applied, and format information for the information to be output.

[0065] In another example of this embodiment, the above-mentioned condition (1) may be excluded from the required conditions. For example, condition (1) is excluded when a case where multiple evidence data of different types are linked to one payment data or when a user submits the same evidence multiple times is permitted. Furthermore, for example, when the evidence data is evidence data based on image data individually input by the user, condition (1) may be excluded, whereas when the evidence data is evidence data based on image data attached to an email addressed to an email address for receiving invoices, condition (1) may be maintained.

[0066] In another example of this embodiment, the following condition may be added to the above conditions (1) to (3). (4) The card number matches the card number corresponding to the supporting document. Here, if the supporting evidence data is based on image data individually input by a user, the card number corresponding to the supporting evidence data is the card number of the credit card (identified by referencing the organization ID in card information table 1512) corresponding to the organization to which the user belongs (identified by referencing the organization ID in user information table 1511). Also, if the supporting evidence data is based on image data attached to an email addressed to an email address for receiving invoices, the card number corresponding to the supporting evidence data is the card number of the credit card (identified by referencing the email address for receiving invoices in card information table 1512) corresponding to that email address. In this case, first, multiple payment data that satisfy condition (4) may be extracted as multiple candidates for payment data corresponding to the supporting evidence data, and payment data that satisfies conditions (1) to (3) may be identified from these multiple candidates.

[0067] In this example, for multiple pieces of supporting evidence data for which corresponding payment data has not been identified, the corresponding payment data is then identified again in a batch. Figure 10 is a flowchart illustrating the processing executed by the business support server 10 when collectively identifying payment data corresponding to supporting evidence data that is not linked to payment data. These processing steps are executed periodically (for example, at a specified time every day).

[0068] First, as shown in the figure, the business support server 10 extracts evidence data that is not linked to payment data at that time (step S200). Such evidence data is identified by referring to the presence or absence of linkage in the evidence data management table 1514.

[0069] Next, the business support server 10 identifies the corresponding payment data for each extracted evidence data in the same manner as in the processes of steps S130 and S140 described above, and registers the combination (step S210).

[0070] In the above example, in response to acquisition of image data of a voucher, evidence data is acquired based on the image data, and payment data corresponding to the evidence data is identified. However, instead of or in addition to this, in response to acquisition of payment data, evidence data corresponding to the payment data may be identified. In this case, for example, when new payment data is registered in the payment data management table 1513, evidence data corresponding to the registered payment data is identified, and specifically, from among the multiple evidence data managed in the evidence data management table 1514, evidence data that satisfies the following three conditions is identified as the corresponding evidence data: (1) No link to payment data (2) The transaction amount matches the payment amount in the target payment data. (3) The transaction date matches the date of use of the payment data in question. In addition to these conditions (1) to (3), the following condition may be added. (4) The corresponding card number matches the card number in the payment data. Here, as described above, if the supporting evidence data is based on image data individually input by a user, the card number corresponding to the supporting evidence data is the card number of the credit card corresponding to the organization to which the user belongs. Also, if the supporting evidence data is based on image data attached to an email addressed to an email address for receiving invoices, the card number of the credit card corresponding to that email address is the card number corresponding to the supporting evidence data. In this case, first, multiple supporting evidence data that satisfy condition (4) may be extracted as multiple candidates for supporting evidence data corresponding to the payment data, and supporting evidence data that satisfies conditions (1) to (3) may be identified from these multiple candidates. Furthermore, in this case, for multiple payment data for which corresponding supporting evidence data has not been identified, corresponding supporting evidence data may then be re-identified in a lump.

[0071] In the above example, the business support tool has a chat function, but the business support server 10 may be configured to cooperate with an external chat system. In this case, various information including image data may be input and output via an API provided by the chat system.

[0072] The business support server 10 according to the present embodiment described above acquires supporting data and payment data, and identifies corresponding supporting data and payment data based on these data, thereby making it possible to acquire supporting data of a supporting document showing the transaction details of a payment made using a payment card and automatically link it to the corresponding payment data. In other words, the business support server 10 supports the management of supporting data, thereby reducing the burden on personnel in the management department and users such as employees.

[0073] In another embodiment of the present invention, some or all of the functions of the business support server 10 in the above-described embodiment may be realized by cooperation between the business support server 10 and the management terminal 20 or the user terminal 30, or may be realized by the management terminal 20 or the user terminal 30. In other words, the system of the present invention may be configured not only by the business support server 10, but also by the business support server 10 and the management terminal 20 or the user terminal 30, or may be configured by the management terminal 20 or the user terminal 30.

[0074] The processes and procedures described herein, other than those explicitly described, may be implemented by software, hardware, or any combination thereof. For example, the processes and procedures described herein may be implemented by implementing logic corresponding to the processes and procedures in media such as integrated circuits, volatile memory, non-volatile memory, and magnetic disks. The processes and procedures described herein may also be implemented as computer programs corresponding to the processes and procedures and executed by various computers.

[0075] Although processes and procedures described herein are described as being performed by a single device, software, component, or module, such processes or procedures may be performed by multiple devices, software, components, and / or modules. Also, the software and hardware elements described herein may be implemented by combining them into fewer components or breaking them down into more components. [Explanation of symbols]

[0076] 10 Business support server 11. Computer Processor 112 Management function control section 114 Business Support Control Section 15. Storage 151 various tables 1511 User Information Table 1512 Card Information Table 1513 Payment Data Management Table 1514 Voucher Data Management Table 1515 Linking Management Table 20 Management terminal 30 User terminals 40 Server-side programs 42 Management terminal side program 44 User terminal side program 200 Input Message 210 Response Message

Claims

1. 1. A system comprising one or more computer processors, the one or more computer processors comprising: acquiring evidence data relating to the evidence, the evidence data including amount information and date information, based on image data of the evidence attached to an email addressed to a specific address; acquiring payment data relating to a payment made by a payment card, the payment data including the amount information and the date information; and executing an operation including a step of identifying the corresponding evidence data and the corresponding payment data based on the amount information and the date information included in the evidence data and the amount information and the date information included in the payment data, The step of specifying includes identifying a specific payment card corresponding to the specific address from among the multiple payment cards based on payment card information related to multiple payment cards stored in a storage device, the payment card information including email addresses corresponding to each of the multiple payment cards, and identifying the payment data corresponding to the supporting document data from among multiple payment data related to payments made with the specific payment card. system.

2. A system comprising one or more computer processors, wherein the one or more computer processors: acquiring evidence data relating to the evidence based on image data of the evidence input by a specific user, the evidence data including amount information and date information; acquiring payment data relating to a payment made by a payment card, the payment data including the amount information and the date information; and executing an operation including a step of identifying the corresponding evidence data and the corresponding payment data based on the amount information and the date information included in the evidence data and the amount information and the date information included in the payment data, The step of identifying includes identifying a specific payment card corresponding to the specific user or a specific organization to which the specific user belongs from among the multiple payment cards based on payment card information related to multiple payment cards stored in a storage device, the payment card information including information identifying a user or organization corresponding to each of the multiple payment cards, and identifying the payment data corresponding to the supporting document data from multiple payment data related to payments made with the specific payment card. system.

3. The step of identifying includes: In response to the acquisition of the evidence data, identifying the payment data corresponding to the evidence data from among a first plurality of payment data; and and when the payment data corresponding to the supporting data is not identified from the first plurality of payment data, subsequently identifying the payment data corresponding to the supporting data from a second plurality of payment data including the newly acquired payment data.

3. The system of claim 1 or 2.

4. 1. A method implemented by one or more computers, comprising: acquiring evidence data relating to the evidence, the evidence data including amount information and date information, based on image data of the evidence attached to an email addressed to a specific address; acquiring payment data relating to a payment made by a payment card, the payment data including the amount information and the date information; and identifying the corresponding evidence data and the corresponding payment data based on the amount information and the date information included in the evidence data and the amount information and the date information included in the payment data, The step of specifying includes identifying a specific payment card corresponding to the specific address from among the multiple payment cards based on payment card information related to multiple payment cards stored in a storage device, the payment card information including email addresses corresponding to each of the multiple payment cards, and identifying the payment data corresponding to the supporting document data from among multiple payment data related to payments made with the specific payment card. method.

5. A method executed by one or more computers, comprising: acquiring evidence data relating to the evidence based on image data of the evidence input by a specific user, the evidence data including amount information and date information; acquiring payment data relating to a payment made by a payment card, the payment data including the amount information and the date information; and identifying the corresponding evidence data and the corresponding payment data based on the amount information and the date information included in the evidence data and the amount information and the date information included in the payment data, The step of identifying includes identifying a specific payment card corresponding to the specific user or a specific organization to which the specific user belongs from among the multiple payment cards based on payment card information related to multiple payment cards stored in a storage device, the payment card information including information identifying a user or organization corresponding to each of the multiple payment cards, and identifying the payment data corresponding to the supporting document data from multiple payment data related to payments made with the specific payment card. method.

6. On one or more computers, acquiring evidence data relating to the evidence, the evidence data including amount information and date information, based on image data of the evidence attached to an email addressed to a specific address; acquiring payment data relating to a payment made by a payment card, the payment data including the amount information and the date information; and executing an operation including a step of identifying the corresponding evidence data and the corresponding payment data based on the amount information and the date information included in the evidence data and the amount information and the date information included in the payment data, The step of specifying includes identifying a specific payment card corresponding to the specific address from among the multiple payment cards based on payment card information related to multiple payment cards stored in a storage device, the payment card information including email addresses corresponding to each of the multiple payment cards, and identifying the payment data corresponding to the supporting document data from among multiple payment data related to payments made with the specific payment card. program.

7. One or more computers, acquiring evidence data relating to the evidence based on image data of the evidence input by a specific user, the evidence data including amount information and date information; acquiring payment data relating to a payment made by a payment card, the payment data including the amount information and the date information; and executing an operation including a step of identifying the corresponding evidence data and the corresponding payment data based on the amount information and the date information included in the evidence data and the amount information and the date information included in the payment data, The step of identifying includes identifying a specific payment card corresponding to the specific user or a specific organization to which the specific user belongs from among the multiple payment cards based on payment card information related to multiple payment cards stored in a storage device, the payment card information including information identifying a user or organization corresponding to each of the multiple payment cards, and identifying the payment data corresponding to the supporting document data from multiple payment data related to payments made with the specific payment card. program.

Images