Information processing device, information processing method, information processing program, and information processing system

Abstract

The purpose is to understand the status of transactions with business partners. [Solution] This information processing device has a screen output unit that references a memory unit in which business partner information indicating business partners and information indicating the details of guarantees for claims against the business partners are stored in association with each other, and displays, for each of multiple business partners, transaction status information indicating the status of transactions with the business partners and information indicating the details of the guarantees on a display unit.

Description

[Technical field]

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

[0002] Conventionally, a guarantee service device is known that, when a claim arises against a business operator, acquires a guarantee claim including claim information, and in the event of default on the debt, claims insurance money for the claim related to the debt and executes the process of paying the guarantee money to the business operator, which is the creditor. Summary of the Invention [Problem to be solved by the invention]

[0003] The above-mentioned conventional techniques do not take into consideration the understanding of the state of transactions between a business operator and a customer before and after a default occurs.

[0004] The present invention has been made in view of the above circumstances, and has as its object to enable a company to grasp the status of transactions with its business partners. [Means for solving the problem]

[0005] The disclosed technology is a registration unit for storing in a storage unit guarantee registration information that associates customer information indicating a customer, invoice information for the customer, and information input from a terminal device indicating the guarantee content of the claim for the customer; The information processing device has a screen output unit that refers to a memory unit and displays, for each of the multiple trading partners, transaction status information indicating the status of transactions with the trading partners and information indicating the guarantee content on a display unit. Effect of the Invention

[0006] It allows you to understand the status of transactions with business partners. [Brief description of the drawings]

[0007] [Figure 1] FIG. 1 is a diagram illustrating an example of a system configuration of an information processing system according to an embodiment of the present invention. [Diagram 2]FIG. 2 illustrates an example of a hardware configuration of an information processing device. [Diagram 3] FIG. 2 illustrates an example of a hardware configuration of a terminal device. [Figure 4] FIG. 13 is a diagram illustrating an example of an invoice database. [Diagram 5] FIG. 2 is a diagram illustrating an example of a business partner database. [Figure 6] FIG. 11 is a diagram illustrating an example of a warranty registration database. [Figure 7] FIG. 13 is a diagram illustrating an example of a performance history database. [Figure 8] FIG. 2 is a diagram illustrating the functional configuration of each device in the information processing system. [Figure 9] FIG. 11 is a first sequence diagram illustrating an operation of the information processing system. [Figure 10] FIG. 2 is a second sequence diagram illustrating the operation of the information processing system. [Figure 11A] FIG. 1 is a first diagram showing a home screen. [Figure 11B] FIG. 13 is a diagram showing another display example of the display field. [Figure 12] FIG. 13 is a diagram showing an example of a supplier selection screen. [Figure 13] FIG. 13 is a diagram showing an example of a registration screen. [Figure 14] FIG. 11 is a third sequence diagram illustrating the operation of the information processing system. [Figure 15] FIG. 13 is a diagram showing an example of a list screen of application information. [Figure 16] FIG. 13 is a diagram showing an example of an input screen for warranty details. [Figure 17] FIG. 4 is a fourth sequence diagram illustrating the operation of the information processing system. [Figure 18] 13 is a first flowchart illustrating the processing of a risk assessment unit. [Figure 19] FIG. 11 is a diagram illustrating an example of a determination result table. [Figure 20] FIG. 2 is a second diagram showing the home screen. [Figure 21] FIG. 13 is a diagram showing an example of a list screen of performance history information. [Figure 22] FIG. 5 is a fifth sequence diagram illustrating the operation of the information processing system. [Diagram 23] FIG. 2 is a diagram illustrating an example of a quotation database. [Figure 24] 13 is a second flowchart illustrating the processing of the risk assessment unit. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0008] DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS An embodiment will be described below with reference to the drawings. Fig. 1 is a diagram showing an example of a system configuration of an information processing system according to the present embodiment.

[0009] The information processing system 1 of this embodiment includes a transaction management system 100 and a terminal device 400.

[0010] The transaction management system 100 has a document management device 200 and a transaction management device 300. The document management device 200 and the transaction management device 300 of this embodiment may be realized, for example, by a general information processing device. For example, the transaction management device 300 of this embodiment is a first information processing device, and the document management device 200 is a second information processing device.

[0011] In addition, the transaction management system 100 of this embodiment communicates with a terminal device 400 and a claim guarantee management system 500.

[0012] In the transaction management system 100 of this embodiment, the terminal device 400 is, for example, a terminal device used by a business operator who conducts transactions with various business partners. Note that the business operator in this embodiment may be an individual or an organization such as a company or a corporation. In the following description of the embodiment, the business operator who is the user of the terminal device 400 may be referred to as a tenant. Also, the user who actually operates the terminal device 400 may be referred to as a tenant.

[0013] The claim guarantee management system 500 is managed by a claim guarantee institution or the like that provides a service of guaranteeing claims relating to a debt in the event of a default on a debt by a business partner of the business entity using the terminal device 400.

[0014] In the following description, the service provided to tenants by the claim guarantee management system 500 may be referred to as a claim guarantee service.

[0015] In addition, the claim guarantee service of this embodiment is a service in which, when a tenant is unable to pay the claim amount due to a lack of funds or other reasons on the part of the business partner, the claim guarantee agency that manages the claim guarantee management system 500 pays the claim amount to the tenant within a predetermined upper guarantee limit amount.

[0016] In this embodiment, a claim is a right that allows a tenant to request payment of an invoice from a business partner who has issued an invoice, and is a right that a tenant has against a business partner.

[0017] In addition, the receivable in this embodiment is not limited to an invoice issued by the tenant to a business partner, but may also be a right of the tenant to request payment for goods, services, etc. from a business partner based on documents such as purchase orders and receipts received by the tenant from the business partner, and documents such as quotations and delivery notes issued by the tenant to the business partner.

[0018] The claim guarantee management system 500 of this embodiment includes a claim guarantee management device 600 and a terminal device 700. The claim guarantee management device 600 stores, for example, information input from the terminal device 700 and information acquired through communication with the transaction management system 100. The terminal device 700 is used by the administrator of the claim guarantee management system 500, etc.

[0019] In the transaction management system 100 of this embodiment, the form management device 200 has an invoice database 210, a supplier database 220, and a form management section 230. In the transaction management system 100, the transaction management device 300 has a warranty registration database 310 and a performance history database 320.

[0020] The transaction management system 100 of this embodiment receives a request from a tenant via a terminal device 400 and registers, in the claim guarantee management system 500, a business partner that uses the claim guarantee service.

[0021] Specifically, the transaction management system 100 stores information on forms issued from tenants to business partners in the invoice database 210 by the form management unit 230 of the form management device 200. In the following description of the embodiment, an invoice is used as an example of a form, but the form is not limited to an invoice. The form may be an estimate, a delivery note, or the like.

[0022] Furthermore, the form management device 200 stores information indicating the business partner identified from the invoice information in the business partner database 220 by the form management unit 230. In the following description, the information stored in the business partner database 220 is referred to as business partner information. A business partner is, in other words, a party to whom an invoice amount is to be billed.

[0023] In addition, in the document management device 200, the document management unit 230 receives a request from the terminal device 400 to register business partner information in the credit guarantee management system 500, and transmits the invoice information and business partner information of the tenant using the terminal device 400 to the transaction management device 300.

[0024] The transaction management device 300 transmits the invoice information and the customer information to the claim guarantee management system 500 via the transaction management unit 330, and accepts input of information indicating the guarantee details. The transaction management unit 330 then associates the customer information with the information indicating the guarantee details and stores them in the guarantee registration database 310. In the following explanation, the information stored in the guarantee registration database 310 is referred to as guarantee registration information.

[0025] Furthermore, upon receiving a request from the terminal device 400, the transaction management device 300 causes the terminal device 400 to display a list of warranty registration information for each supplier of the tenant.

[0026] Furthermore, in the event of a default on a debt, the transaction management device 300, upon receiving a request from the terminal device 400, requests the debt guarantee management system 500 to guarantee the debt related to the debt via the transaction management section 330. In other words, the transaction management device 300 requests the debt guarantee management system 500 to perform the debt for the transaction.

[0027] Then, the transaction management unit 330 stores in the performance history database 320 performance history information indicating the history of the performance of the obligation, which indicates that the performance of the obligation has been requested, that the obligation has been performed, and so on.

[0028] In this manner, the transaction management system 100 of this embodiment can present the status of transactions between the tenant and each of its business partners to the tenant.

[0029] In addition, in this embodiment, the tenant's business partner is identified from the information on the form managed by the form management device 200 and registered as a business partner that uses the claim guarantee service provided by the claim guarantee management system 500, so there is no need for the tenant to input information on the business partner. Therefore, in this embodiment, the effort required to use the claim guarantee service can be easily reduced.

[0030] 1, the transaction management system 100 includes the document management device 200 and the transaction management device 300, but is not limited to this. The document management device 200 and the transaction management device 300 may be realized, for example, by a single information processing device, or each of the document management device 200 and the transaction management device 300 may be realized by multiple information processing devices.

[0031] In addition, in the example of Figure 1, the document management device 200 has an invoice database 210 and a customer database 220, and the transaction management device 300 has a warranty registration database 310 and a performance history database 320, but this is not limited to this.

[0032] The above-mentioned databases may be provided in part or in whole in an external device other than the document management device 200 and the transaction management device 300. Also, for example, the above-mentioned four databases may be provided in either the document management device 200 or the transaction management device 300.

[0033] The hardware configuration of the information processing device that realizes the document management device 200 and the transaction management device 300, and the hardware configuration of the terminal device 400 will be described below with reference to FIGS.

[0034] Fig. 2 is a diagram showing an example of the hardware configuration of an information processing device, and Fig. 2 shows an example of the hardware configuration of a form management device 200 which is a second information processing device.

[0035] The document management device 200 is constructed by a computer, and as shown in FIG. 2, includes a CPU 201, a ROM 202, a RAM 203, a HD 204, a HDD (Hard Disk Drive) controller 205, a display 206, an external device connection I / F (Interface) 208, a network I / F 209, a bus line B1, a keyboard 211, a pointing device 212, a DVD-RW (Digital Versatile Disk Rewritable) drive 214, and a media I / F 216.

[0036] Among these, the CPU 201 controls the operation of the entire document management device 200. The ROM 202 stores programs such as IPL used to drive the CPU 201. The RAM 203 is used as a work area for the CPU 201. The HD 204 stores various data such as programs. The HDD controller 205 controls reading or writing of various data from the HD 204 under the control of the CPU 201. The display 206 displays various information such as a cursor, a menu, a window, a character, or an image. The external device connection I / F 208 is an interface for connecting various external devices. In this case, the external device is, for example, a USB (Universal Serial Bus) memory or a printer. The network I / F 209 is an interface for data communication using a communication network. The bus line B1 is an address bus, a data bus, or the like for electrically connecting each component such as the CPU 201 shown in FIG. 2.

[0037] The keyboard 211 is a type of input means having a plurality of keys for inputting characters, numbers, various instructions, etc. The pointing device 212 is a type of input means for selecting and executing various instructions, selecting a processing target, moving a cursor, etc. The DVD-RW drive 214 controls reading and writing of various data from a DVD-RW 213 as an example of a removable recording medium. Note that the medium is not limited to DVD-RW, and may be a DVD-R, etc. The media I / F 216 controls reading and writing (storing) of data from a recording medium 215 such as a flash memory.

[0038] 3 is a diagram showing an example of the hardware configuration of a terminal device 400 according to this embodiment. The terminal device 400 includes a CPU 401, a ROM 402, a RAM 403, an EEPROM 404, a CMOS sensor 405, an image sensor I / F 406, an acceleration / direction sensor 407, a media I / F 409, and a GPS receiver 411.

[0039] Of these, the CPU 401 is an arithmetic processing device that controls the overall operation of the terminal device 400. The ROM 402 stores the CPU 401 and programs used to drive the CPU 401, such as the IPL. The RAM 403 is used as a work area for the CPU 401. The EEPROM 404 reads or writes various data, such as smartphone programs, under the control of the CPU 401. The ROM 402, the RAM 403, and the EEPROM 404 are examples of storage devices of the terminal device 400.

[0040] The CMOS (Complementary Metal Oxide Semiconductor) sensor 405 is a type of built-in imaging means that captures an image of a subject (mainly a self-portrait) to obtain image data under the control of the CPU 401. Note that instead of a CMOS sensor, an imaging means such as a CCD (Charge Coupled Device) sensor may also be used.

[0041] The imaging element I / F 406 is a circuit that controls the driving of the CMOS sensor 405. The acceleration / direction sensor 407 is various sensors such as an electronic magnetic compass that detects geomagnetism, a gyrocompass, and an acceleration sensor. The media I / F 409 controls the reading and writing (storage) of data from and to a recording medium 408 such as a flash memory. The GPS receiver 411 receives GPS signals from GPS satellites.

[0042] The terminal device 400 also includes a long-distance communication circuit 412, an antenna 412a of the long-distance communication circuit 412, a CMOS sensor 413, an image sensor I / F 414, a microphone 415, a speaker 416, an audio input / output I / F 417, a display 418, an external device connection I / F (Interface) 419, a short-distance communication circuit 420, an antenna 420a of the short-distance communication circuit 420, and a touch panel 421.

[0043] Of these, the long-distance communication circuit 412 is a circuit that communicates with other devices via a communication network. The CMOS sensor 413 is a type of built-in imaging means that captures an image of a subject and obtains image data under the control of the CPU 401. The image sensor I / F 414 is a circuit that controls the driving of the CMOS sensor 413. The microphone 415 is a built-in circuit that converts sound into an electrical signal. The speaker 416 is a built-in circuit that converts an electrical signal into physical vibrations to generate sounds such as music and voice. The audio input / output I / F 417 is a circuit that processes the input and output of audio signals between the microphone 415 and the speaker 416 under the control of the CPU 401.

[0044] The display 418 is a type of display means such as a liquid crystal or organic EL (Electro Luminescence) that displays an image of a subject, various icons, etc. The external device connection I / F 419 is an interface for connecting various external devices. The short-range communication circuit 430 is a communication circuit such as NFC (Near Field Communication) or Bluetooth (registered trademark). The touch panel 421 is a type of input means that allows a user to operate the terminal device 400 by pressing the display 418. The display 418 is an example of a display unit that the terminal device 400 has.

[0045] Next, each database included in the transaction management system 100 of this embodiment will be described with reference to FIGS.

[0046] 4 is a diagram showing an example of the invoice database. The invoice database 210 of this embodiment is provided for each tenant. In addition, the invoice database 210 accumulates invoice information as the tenant issues invoices to business partners.

[0047] The invoice database 210 of this embodiment includes information items such as tenant ID, invoice destination, invoice amount, invoice date, payment due date, payment status, and payment date.

[0048] The value of the item "tenant ID" indicates identification information for identifying a tenant. The identification information for identifying a tenant may be, for example, the name of the tenant.

[0049] The value of the item "Billing destination" indicates the party to which the invoice amount is to be billed. In other words, the value of the item "Billing destination" is the business partner of the tenant identified by the tenant ID.

[0050] The value of the item "billing amount" indicates the amount to be billed, the value of the item "billing date" indicates the date on which the bill was issued, and the value of the item "payment due date" indicates the due date for payment of the billed amount.

[0051] The value of the item "Payment Status" indicates whether the invoiced amount has been paid, and is changed in response to operations from the terminal device 400. In addition, in the invoice information, an invoice amount for which the value of the item "Payment Status" is "Unpaid" is the amount currently being transacted between the tenant and the business partner. The value of the item "Deposit Date" indicates the date on which the invoiced amount was deposited into the bank account, etc., of the tenant ID.

[0052] In addition, image data of the invoice or storage destination information such as a file path indicating the storage destination of the image data may be stored in the invoice database 210 as invoice information.

[0053] In this way, the invoice information in this embodiment can be said to be information regarding invoices to business partners.

[0054] 5 is a diagram showing an example of a supplier database. The supplier database 220 of this embodiment may be provided for each tenant. Furthermore, supplier information of this embodiment is registered by each tenant.

[0055] The supplier database 220 of this embodiment includes information items such as tenant ID, supplier name, address, telephone number, email address, and person in charge.

[0056] In supplier database 220, the values ​​of the items "supplier name," "address," "telephone number," "email address," and "person in charge" indicate the supplier's name, address, telephone number, email address, and person in charge's name, respectively.

[0057] 6 is a diagram showing an example of a warranty registration database. The warranty registration database 310 includes information items such as tenant name, business partner name, address, transaction start date, whether or not there is a payment delay, application status, warranty upper limit amount, warranty period, etc. In the warranty registration database 310, the item "tenant name" is associated with other items. In the following description, information in the warranty registration database 310 that includes the value of the item "tenant name" and the values ​​of the other items is referred to as warranty registration information.

[0058] The value of the item "Tenant Name" indicates the name of the tenant. The value of the item "Customer Name" is the name of the customer indicated by the value of the item "Customer Name" in the customer database 220. The value of the item "Address" indicates the address of the customer. The value of the item "Transaction Start Date" indicates the date on which the tenant and customer started trading. Specifically, the registration unit 333 may set the oldest billing date included in the invoice information stored in the invoice database 210 as the transaction start date.

[0059] The value of the item "Delayed payment" indicates whether or not there is a delay in the payment of the invoice amount from the business partner to the tenant. Specifically, when there is invoice information stored in the invoice database 210 for which the payment due date has passed and the value of the item "Payment status" is "unpaid," the registration unit 333 sets the value of the item "Delayed payment" to "Yes."

[0060] The value of the item "Application Status" indicates whether or not the claim guarantee service is available. Specifically, when the value of the item "Application Status" is "Reviewed", it indicates that the claim guarantee service is available for this business partner. Also, when the value of the item "Application Status" is "Under Review" or when there is no value for the item "Application Status", it indicates that the claim guarantee service is not available for this business partner.

[0061] The value of the item "Guarantee Maximum Amount" indicates the maximum amount guaranteed to a business partner. The value of the item "Guarantee Period" indicates the period during which the credit guarantee service is available to a business partner.

[0062] In other words, the warranty registration information in this embodiment includes at least a portion of the supplier information, a portion of the invoice information, and information indicating the warranty details for the supplier.

[0063] 7 is a diagram showing an example of a performance history database. The performance history database 320 of this embodiment includes, as information items, a tenant name, a business partner name, an invoice amount, an invoice date, a payment due date, a performance status, a performance execution date, a guarantee upper limit amount, a guarantee period, and the like.

[0064] In the performance history database 320, the item "tenant name" is associated with other items, and information including the value of the item "tenant name" and the values ​​of the other items in the performance history database 320 is referred to as performance history information.

[0065] The value of the item "Performance Status" indicates the status of the performance of the obligation. The value of the item "Performance Execution Date" indicates the date on which the performance of the obligation was executed.

[0066] In addition, image data of the invoice to be fulfilled or destination information such as a file path indicating the destination where the image data is saved may be stored in the fulfillment history database 320 as fulfillment history information.

[0067] Next, the functions of each device of the transaction management system 100 of this embodiment will be described with reference to Fig. 8. Fig. 8 is a diagram illustrating the functional configuration of each device of the information processing system.

[0068] First, the form management device 200 will be described. The form management device 200 of this embodiment has an invoice database 210, a supplier database 220, and a form management unit 230. The invoice database 210 and the supplier database 220 are realized by storage devices such as the ROM 202, RAM 203, and HD 204 of the form management unit 230. The form management unit 230 is realized by the CPU 201 reading and executing a form recognition program.

[0069] The form management unit 230 includes a form recognition unit 231 , a request reception unit 232 , an erasure unit 233 , a communication unit 234 , and a form generation unit 235 .

[0070] The form recognition unit 231 extracts the names of items (item names) and the values ​​of these items (item values) included in the form image shown by the form image data acquired by the form management device 20, and performs form recognition by converting the items and the item values ​​into text data and associating them with each other. Then, the form recognition unit 231 stores the form recognition result, which is the result of performing the form recognition, in the invoice database 210. In this embodiment, since an invoice is used as an example of a form, information indicating the form recognition result becomes invoice information.

[0071] The request receiving unit 232 receives various requests to the document management device 200. Specifically, the request receiving unit 232 receives requests from the transaction management device 300 to acquire invoice information, supplier information, and the like.

[0072] The erasing unit 233 accepts an operation to change the value of the item "payment status" included in the invoice information stored in the invoice database 210, by an operation from the terminal device 400. Specifically, the erasing unit 233 changes the value of the item "payment status" from "unpaid" to "paid" in response to the operation from the terminal device 400.

[0073] The communication unit 234 transmits and receives information between the form management device 200 and each of the other devices. The form generation unit 235 issues an invoice in response to an operation from the terminal device 400, and stores invoice information of the issued invoice in the invoice database 210.

[0074] Next, a description will be given of transaction management device 300. Transaction management device 300 has a warranty registration database 310, a performance history database 320, and a transaction management section 330.

[0075] Warranty registration database 310 and performance history database 320 are realized by storage devices such as ROM, RAM, and HD of transaction management device 300. Transaction management unit 330 is realized by the CPU of transaction management device 300 reading and executing a transaction management program.

[0076] The transaction management unit 330 of this embodiment has an input reception unit 331, an information acquisition unit 332, a registration unit 333, a performance management unit 334, a risk assessment unit 335, a screen output unit 336, and a communication unit 337.

[0077] The input reception unit 331 receives various inputs to the transaction management device 300. Specifically, the input reception unit 331 receives, for example, a registration request to enable the use of the claim guarantee service. The input reception unit 331 also receives inputs such as information indicating the details of the guarantee for the business partner from the terminal device 700 of the claim guarantee management system 500.

[0078] The information acquisition unit 332 acquires various types of information. Specifically, for example, the information acquisition unit 332 acquires invoice information and business partner information from the document management device 200.

[0079] The registration unit 333 associates the acquired supplier information with the information indicating the warranty content received by the input reception unit 331, and registers (stores) the information in the warranty registration database 310.

[0080] The performance management unit 334 stores performance history information in the performance history database 320 when an operation related to the performance of a debt is performed, when a debt is performed through a credit guarantee service, etc. In other words, the performance management unit 334 updates the performance history database 320.

[0081] The risk assessment unit 335 assesses the degree of risk of transactions between the tenant and the business partner based on information indicating the guarantee content for each business partner stored in the guarantee registration database 310 and invoice information for each business partner, and stores the result as a assessment result table 339.

[0082] More specifically, the risk assessment unit 335 calculates the amount of the transaction with each tenant from the invoice information, and determines the degree of risk of the transaction with the tenant based on the amount of the transaction, information indicating the guarantee details for each tenant, and whether or not there is a payment delay.

[0083] The risk assessment unit 335 then stores transaction status information in the assessment result table 339, which corresponds the amount of the transaction, information indicating the guarantee details for each trading partner, whether or not there is a payment delay, and the degree of risk of the transaction with the trading partner.

[0084] The processing of the risk determination unit 335 and the determination result table 339 will be described in detail later.

[0085] The screen output unit 336 generates screen data for displaying various screens, and outputs the data to the terminal device 400, the terminal device 700, and the like via the communication unit 337.

[0086] The communication unit 337 transmits and receives information between the transaction management device 300 and each of the other devices.

[0087] The terminal device 400 of this embodiment includes a display control unit 440 and a communication unit 454500. The display control unit 440 controls the display in the terminal device 400. The display control unit 440 may be realized by, for example, a browser or the like, or may be realized by an application for using a credit guarantee service or the like.

[0088] The communication unit 450 transmits and receives information between the terminal device 400 and each of the other devices. Similarly to the terminal device 400, the terminal device 700 of this embodiment may also have a display control unit and a communication unit.

[0089] Next, the operation of the transaction management system 100 of this embodiment will be described. Fig. 9 is a first sequence diagram explaining the operation of the information processing system. Fig. 9 shows the operation of the transaction management system 100 when storing invoice information and business partner information in the form management device 200.

[0090] In the transaction management system 100 of this embodiment, the form management device 200 causes the form generation unit 235 of the form management section 230 to display an invoice issuance screen on the terminal device 400 (step S901).

[0091] Furthermore, the document management device 200 may display the issuance screen on the terminal device 400, for example, by accessing a specific URL (Uniform Resource Locator) on the terminal device 400 or by clicking a link or button displayed on the screen.

[0092] Next, the terminal device 400 accepts settings of invoice information by the tenant (user belonging to the tenant) (step S902). Specifically, the terminal device 400 accepts settings of, for example, the invoice destination, the invoice amount, the invoice date, the payment due date, and the like.

[0093] Next, the terminal device 400 accepts an invoice issuance operation from the tenant (step S903), and transmits the invoice information to the document management device 200 via the communication unit 450 (step S904).

[0094] Next, when the form management device 200 receives the invoice information, the form generation unit 235 performs a process of issuing an invoice (step S905). Specifically, the form management device 200 may generate PDF data of an invoice based on the invoice information received by the communication unit 234, for example, and transmit the PDF data to a preset email address or the like of the billing destination.

[0095] Next, the form management device 200 stores the invoice information in the invoice database 210 (step S906).

[0096] In addition, the document management device 200 of this embodiment may, for example, receive image data generated by scanning an invoice from the terminal device 400, and perform document recognition on the image represented by this image data (image of the invoice) by the document recognition unit 231, and use the result as invoice information.

[0097] 10 is a second sequence diagram for explaining the operation of the information processing system 100. FIG. 10 shows the operation of the transaction management system 100 when registering warranty registration information in the warranty registration database 310 in the transaction management device 300.

[0098] In the transaction management system 100 of this embodiment, the transaction management device 300 causes the screen output unit 336 to display the home screen of the claim guarantee service on the terminal device 400 (step S1001). The details of the home screen will be described later.

[0099] When terminal device 400 accepts an operation to register supplier information through communication unit 450 (step S1002), it transmits a supplier registration request to transaction management device 300 (step S1003).

[0100] In response to the request to register the supplier information, the transaction management device 300 causes the information acquisition unit 332 to transmit a request to acquire a list of billing destinations (suppliers) included in the invoice information of the tenant to the document management device 200 (step S1004).

[0101] The document management device 200 receives the request through the request receiving unit 232 and acquires a list of business partners (step S1005). Specifically, the document management device 200 acquires the value of the item "billing destination" from the invoice database 210 of the tenant corresponding to the terminal device 400 as the list of business partners.

[0102] Next, the document management device 200 transmits the list of suppliers to the transaction management device 300 via the communication unit 234 (step S1006).

[0103] When the transaction management device 300 acquires the list of business partners, the screen output unit 336 generates screen data for displaying a business partner selection screen (step S1007). Then, in response to the business partner information registration operation, the transaction management device 300 transmits the generated screen data to the terminal device 400 via the communication unit 337, causing the terminal device 400 to display the selection screen (step S1008). Details of the selection screen will be described later.

[0104] When terminal device 400 receives the selection of a supplier on the selection screen (step S1009), it transmits the selected supplier name to transaction management device 300 (step S1010).

[0105] When the transaction management device 300 receives the supplier name, the information acquisition unit 332 transmits a request to acquire supplier information corresponding to the supplier name to the document management device 200 (step S1011).

[0106] When the request receiving unit 232 receives the request, the document management device 200 retrieves supplier information in the supplier database 220 whose value in the item "name" matches the selected supplier name, and transmits the retrieved supplier information to the transaction management device 300 (step S1012).

[0107] When the transaction management device 300 acquires the supplier information through the information acquisition unit 332, the registration unit 333 sets the acquired supplier information as part of the warranty registration information stored in the warranty registration database 310 (step S1013).

[0108] Next, the transaction management device 300 transmits a request to the form management device 200 to obtain invoice information of the selected supplier (step S1014).

[0109] When the request receiving unit 232 of the document management device 200 receives a request to obtain invoice information, it retrieves invoice information from the invoice database 210 corresponding to the tenant, whose value in the "billing destination" field matches the selected business partner, and transmits the invoice information to the transaction management device 300 (step S1015).

[0110] Next, the transaction management device 300 causes the registration unit 333 to identify information to be registered as warranty registration information from the acquired invoice information, and sets this as part of the warranty registration information (step S1016).

[0111] Specifically, the registration unit 333 sets the oldest billing date among the billing dates included in the acquired billing information as the value of "transaction start date." Furthermore, if there is billing information that is unpaid even though the payment due date has passed, the registration unit 333 sets the value of the item "Delay in payment" in the warranty registration information to "Yes."

[0112] That is, the registration unit 333 of this embodiment includes information on a predetermined specific item from the invoice information as part of the warranty registration information.

[0113] Next, the transaction management device 300, via the registration unit 333, associates the business partner information set in step S1013 with part of the invoice information set in step S1015 to form warranty registration information, and stores (registers) it in the warranty registration database 310 (step S1017).

[0114] At this time, the warranty registration information stored in the warranty registration database 310 does not include information indicating the details of the warranty, such as the items "application status," "maximum warranty amount," and "warranty period."

[0115] Next, the transaction management device 300 generates screen data for displaying a registration screen including the warranty registration information via the screen output unit 336, and transmits the screen data via the communication unit 337 to the terminal device 400 for display (step S1018).

[0116] When the registration screen including the warranty registration information is displayed on the terminal device 400, the tenant modifies the warranty registration information (step S1019). The modified content is reflected in the warranty registration database 310.

[0117] 10 may be executed each time a transaction is made between a tenant and a business partner. In other words, the warranty registration database 310 may be updated each time a transaction is made between a tenant and a business partner. A transaction includes, for example, the issuance of an invoice from the tenant to the business partner, and the payment of the invoiced amount from the business partner to the tenant.

[0118] Below, examples of displays on the terminal device 400 will be described with reference to Figures 11 to 13. Figure 11A is a first diagram showing a home screen.

[0119] A screen 111 shown in FIG. 11A is, for example, an example of a home screen when using a credit guarantee service, and is displayed on the terminal device 400 in step S1002 of FIG.

[0120] Screen 111 displays the tenant name, and has display field 112 and display field 113. Display field 112 displays a list of business partner names registered as business partners that use the claim guarantee service. In other words, display field 112 displays a list of business partner names whose guarantee registration information is stored in guarantee registration database 310.

[0121] In addition, in the display field 112, together with each business partner name, information indicating the guarantee content for each business partner and transaction status information indicating the status of the transaction between the tenant and the business partner are displayed.

[0122] 11A, display column 112 includes display columns 112-1, 112-2, 112-3, etc., and in each display column, together with the business partner name, information indicating the guarantee content for each business partner, the amount of the transaction between the tenant and the business partner, and whether or not there is a payment delay are displayed. In other words, display columns 112-1, 112-2, 112-3 display transaction status information for each business partner. Also, display column 112-4 displays display component 115 instead of the business partner name.

[0123] A list of transaction status information for each business partner is displayed in display field 113. In addition, for business partners with overdue payments among those listed in display field 113, display component 114 for requesting the execution of debt performance is displayed.

[0124] 11A, the display field 113 displays a list of warranty registration information of business partners, but is not limited to this. For example, the display field 113 may display a list of invoice information of each business partner.

[0125] Specifically, for example, the display field 113 may display a list of invoice information for each business partner as the invoice destination.

[0126] Fig. 11B shows another example of the display field 113. Fig. 11B is a diagram showing another display example of the display field.

[0127] Display field 113A shown in FIG. 11B displays a list of invoice information for invoices issued to each supplier for which transaction status information is displayed in display field 112.

[0128] Specifically, display field 113A displays billing information for each supplier, such as the billing destination, billing amount, and payment due date (see FIG. 4).

[0129] Furthermore, when the current date passes the payment due date and the payment status of the invoice information is "unpaid", the display column 113A determines that the invoice information is overdue and displays "overdue" as the value of the item "overdue". Furthermore, the display column 113A displays display component 114A in association with invoice information whose value for the item "overdue" is "overdue". Display component 114A is a display component for instructing the execution of the performance of a debt.

[0130] Also, for example, if no business partner using the credit guarantee service is registered, the display column 113 may be blank. In that case, only the display component 112-5 may be displayed in the display column 112.

[0131] When display component 115 is selected on screen 111, transaction management device 300 of this embodiment accepts this as a registration operation for a new supplier, and transitions the display on terminal device 400 from the home screen to a supplier selection screen.

[0132] 12 is a diagram showing an example of a supplier selection screen 121. A screen 121 shown in FIG. 12 is an example of a supplier selection screen displayed on the terminal device 400 in step S1008 of FIG.

[0133] The screen 121 may be displayed in a pop-up format on the screen 111 shown in FIG.

[0134] Screen 121 displays a list of names of business partners that are not registered as business partners using the credit guarantee service, from the list of business partners acquired in step S1006 of FIG.

[0135] When a supplier name is selected on screen 121, transaction management device 300 performs the processes in and after step S1010 in FIG. 10, and transitions the display on terminal device 400 from screen 121 to a registration screen, which will be described later.

[0136] 13 is a diagram showing an example of a registration screen. A screen 131 shown in FIG 13 is an example of the registration screen displayed on the terminal device 400 in step S1019 of FIG.

[0137] Screen 131 has a display field 132 and display components 133 and 134. Display field 132 displays warranty registration information in which the supplier information set in step S1013 of Fig. 10 is associated with information identified from the invoice information in step S1016.

[0138] In the example of Figure 13, display field 132 displays supplier information including the supplier's company name, address, etc., as well as the transaction start date and whether or not there is a payment delay identified from the claim information, as warranty registration information.

[0139] In other words, the warranty registration information in this embodiment includes business partner information obtained from the document management device 200 and information extracted from the invoice information obtained from the document management device 200 based on predetermined conditions, etc.

[0140] The display component 113 is a display component for canceling the storage of the warranty registration information in the warranty registration database 310. The display component 114 is a display component for storing the warranty registration information in the warranty registration database 310 and requesting (applying for) the credit guarantee management system 500 to review the warranty details.

[0141] In this embodiment, when the display component 114 is selected on the screen 131 of the transaction management device 300, a process is performed to request the credit guarantee management system 500 to examine the guarantee details.

[0142] 14 is a third sequence diagram for explaining the operation of the information processing system. Fig. 14 shows the operation of the transaction management system 100 when the transaction management device 300 requests the credit guarantee management system 500 to examine the guarantee details.

[0143] In the transaction management system 100, when the terminal device 400 receives an operation by a tenant to select a request (application) for review of the warranty content (an operation to select display component 134) (step S1401), the terminal device 400 sends an application request to the transaction management device 300 (step S1402).

[0144] In response to this request, the transaction management device 300 causes the registration unit 333 to store the application status in the warranty registration information stored in the warranty registration database 310 (step S1403).

[0145] Specifically, the registration unit 333 sets the value of the item "application status" to "under review" for the guarantee registration information in which the value of the item "tenant name" matches the business partner name in the guarantee registration database 310. At this time, the transaction management device 300 may send a notification to the terminal device 700 of the claim guarantee management system 500 indicating a request for review.

[0146] In the claim guarantee management system 500, when the terminal device 700 receives an operation to instruct the display of application information (step S1404), it transmits this request to the transaction management device 300 (step S1405). The terminal device 700 is operated, for example, by an administrator of the claim guarantee management system 500.

[0147] Next, transaction management device 300 generates screen data for displaying a list of the application information through screen output unit 336, and causes terminal device 700 to display the application information list screen (step S1406). The application information list screen will be described in detail later.

[0148] Next, the terminal device 700 accepts input of the warranty details for the applied supplier (step S1407), and then accepts an operation to register information indicating the input warranty details (step S1408).

[0149] When the terminal device 700 accepts this operation, it transmits information indicating the guarantee contents and a registration request for this message driver's room 10 to the transaction management device 300 (step S1409).

[0150] The transaction management device 300 receives this request through the input receiving unit 331, and causes the registration unit 333 to store information indicating the warranty contents in the warranty registration database 310 (step S1410). At this time, the registration unit 333 associates the business partner for which the warranty contents review request has been made with the information indicating the warranty contents, and stores them in the warranty registration database 310.

[0151] 15 is a diagram showing an example of a list screen of application information. A screen 151 shown in FIG. 15 is an example of a screen displayed on the terminal device 700 in step S1406 in FIG.

[0152] Displayed on screen 151 are a display field 152 and display components 153, 154, and 155. Display field 152 displays warranty registration information stored in warranty registration database 310. Display field 152 also displays display component 156 associated with warranty registration information whose item "application status" has a value of "under review". Display component 156 is a display component for transitioning screen 151 to an input screen for warranty details.

[0153] Warranty registration information in which the value of the item "application status" is "under review" is warranty registration information in which the input of information indicating the warranty content has not been completed. Specifically, for example, warranty registration information that does not include at least one of the values ​​of the items "maximum warranty amount" and "warranty period".

[0154] Display component 153 is a display component for displaying all warranty registration information stored in warranty registration database 310 in display field 152. When display component 153 is operated, warranty registration information whose value for the item "application status" is "under review" and warranty registration information whose value for the item "application status" is "reviewed" are displayed in the display field.

[0155] The display component 154 is a display component for displaying only warranty registration information stored in the warranty registration database 310, the warranty registration information having an item "application status" value of "under review".

[0156] The display component 155 is a display component for switching between a list screen of application information and a screen related to the performance of a debt, which will be described later.

[0157] When the display component 156 is operated on the screen 151, the display on the terminal device 700 transitions from the screen 151 to an input screen for the warranty details, which will be described later.

[0158] 16 is a diagram showing an example of an input screen for the warranty details. A screen 161 shown in FIG. 16 is an example of a screen displayed on the terminal device 700 in step S1407 in FIG.

[0159] Displayed on a screen 161 are display columns 162, 163, and display parts 164, 165. Display column 162 displays supplier information, and display column 16 displays an input column for warranty details.

[0160] The display component 164 is a display component for canceling the storage of information indicating the warranty details stored in the warranty registration database 310. The display component 165 is a display component for storing the input information indicating the warranty details in the warranty registration database 310.

[0161] In this embodiment, when information indicating the warranty content is entered into the display field 163 on the terminal device 700 and the display component 165 is operated, the terminal device 700 sends a registration request for the information indicating the warranty content to the transaction management device 300.

[0162] In the example of Fig. 16, a request to register warranty registration information for a supplier name "Company A" is sent to the transaction management device 300. Company A's warranty registration information includes supplier information for Company A, the transaction start date identified from invoice information, whether there is a payment delay, the maximum warranty amount, and the warranty period.

[0163] Upon receiving this registration request, the transaction management device 300 causes the registration unit 333 to register (store) the received information indicating the warranty content in the warranty registration database 310 in association with the business partner information displayed in the display field 162 of the screen 161.

[0164] At this stage, the warranty registration information stored in the warranty registration database 310 contains business partner information and information indicating the warranty details.

[0165] In this embodiment, information (examination results) indicating the guarantee contents of the trading partner is received from the claim guarantee management system 500 via a network, but this is not limited to this. Information indicating the guarantee contents may be directly input to the transaction management device 300 by, for example, an administrator of the claim guarantee management system 500. In this case, the screen 151 shown in FIG. 15 and the screen 161 shown in the screen setting storage unit 16 may be displayed on a display device such as a display connected to the transaction management device 300.

[0166] Next, the operation of the transaction management system 100 when a guarantee is requested from a credit guarantee service for a default of a debt will be described with reference to Fig. 17. Fig. 17 is a fourth sequence diagram illustrating the operation of the information processing system.

[0167] In the transaction management system 100, when the terminal device 400 accepts a display operation of the home screen from a tenant (step S1701), the terminal device 400 transmits a display request of the home screen to the transaction management device 300 (step S1702).

[0168] Next, the transaction management device 300, via the information acquisition unit 332, identifies one of the tenant's business partners that is registered as a business partner that will use the debt guarantee service, and sends a request to the document management device 200 to acquire invoice information for this business partner (step S1703).

[0169] Upon receiving this request, the form management device 200 acquires the corresponding invoice information from the invoice database 210 and transmits it to the transaction management device 300 (step S1704). At this time, the form management device 200 transmits all of the invoice information, including that of the identified supplier, to the transaction management device 300.

[0170] When the transaction management device 300 receives the invoice information of the specified supplier, the risk determination unit 335 determines an index indicating the risk in the transaction between the supplier and the tenant (step S1705). In other words, the transaction management device 300 derives information indicating the status of the transaction between the tenant and the supplier by the risk determination unit 335. The process of step S1705 will be described in detail later.

[0171] The transaction management device 300 performs the processes from step S1703 to step S1705 for all business partners registered as business partners using the claim guarantee service, and generates screen data for displaying a home screen including the results via the screen output unit 336 (step S1706).

[0172] Next, the transaction management device 300 causes the terminal device 400 to display the home screen based on this screen data (step S1707). The information for each business partner obtained in the processes from step S1703 to step S1705 is displayed in the display field 112 of the home screen 111 (see FIG. 11).

[0173] Next, the terminal device 400 accepts the selection of a supplier on the home screen (step S1708). Upon accepting the selection of the supplier, the terminal device 400 displays a list of invoice information for the selected supplier information on the home screen (step S1709).

[0174] Next, when the terminal device 400 receives an operation from the tenant instructing the performance of the debt (step S1710), the terminal device 400 transmits a debt performance request to the transaction management device 300 (step S1711).

[0175] When the transaction management device 300 accepts the performance request, the performance management unit 334 generates performance history information, and the registration unit 333 stores the performance history information in the performance history database 320 (step S1712).

[0176] Specifically, the performance management unit 334 obtains the tenant name, the selected business partner name, the billing amount to the business partner, the billing date, the payment deadline, the maximum guarantee amount, and the guarantee period from the guarantee registration database 310, and stores the performance history information with the performance status set to "in progress" in the performance history database 320 (see Figure 7).

[0177] Furthermore, upon receiving a performance request, the performance management unit 334 may obtain necessary information, such as image data of the invoice to be fulfilled, from the form management device 200, generate performance history information, and store it in the performance history database 320.

[0178] Next, the terminal device 700 receives an operation from the manager of the claim guarantee management system 500, etc., instructing to display a list screen of performance history information (step S1713). The terminal device 700 receives this operation and transmits a display request for the list of performance history information to the transaction management device 300 (step S1714).

[0179] The screen output unit 336 of the transaction management device 300 generates screen data for displaying a list of performance history information, and causes the terminal device 700 to display the performance history list screen (step S1715). The performance history list screen will be described in detail later.

[0180] When terminal device 700 accepts an operation indicating that the debt has been fulfilled (step S1716), it transmits a notification indicating that the debt has been fulfilled to transaction management device 300 (step S1717).

[0181] Upon receiving this notification, the transaction management device 300 causes the performance management unit 334 to update the value of the "performance status" item of the performance history information stored in the performance history database 320 in step S1712 to "performed" (step S1718).

[0182] Next, the process of the risk determination unit 335 in step S1705 in Fig. 7 will be described with reference to Fig. 18. Fig. 18 is a first flowchart illustrating the process of the risk determination unit.

[0183] The risk determination unit 335 of this embodiment calculates the total invoice amount of invoice information whose payment status is unpaid, among the invoice information of a certain business partner acquired from the form management device 200 (step S1801). In the following explanation, the total calculated in step S1801 is referred to as total A. Total A is the amount currently being transacted between the tenant and the business partner.

[0184] Next, the risk determination unit 335 identifies invoice information whose payment status is unpaid and whose payment due date has passed, and calculates the total value of the invoice amounts whose payment due date has passed (step S1802). In the following explanation, the total value calculated in step S1802 is referred to as total value B.

[0185] Next, the risk determination unit 335 determines whether or not the value of the total value B is greater than 0 (step S1803). That is, the risk determination unit 335 determines whether or not there is an unpaid amount whose payment deadline has passed.

[0186] In step S1803, if the total value B is 0, that is, if there is no outstanding amount whose payment deadline has passed, the risk assessment unit 335 proceeds to step S1806, which will be described later.

[0187] In step S1803, if the total value B is greater than 0, that is, if there is an unpaid amount whose payment deadline has passed, the risk determination unit 335 determines whether the total value B exceeds the upper limit of the guarantee (step S1804).

[0188] In other words, the risk determination unit 335 determines whether or not the unpaid amount that is past the due date can be fully recovered by the credit guarantee service.

[0189] In step S1804, if the total value B exceeds the guaranteed upper limit amount, the risk determination unit 335 determines the risk in the transaction with this business partner to be "high" (step S1805), and ends the process.

[0190] In step S1804, if the total value B does not exceed the upper guarantee amount limit, the risk determination unit 335 proceeds to step S1809, which will be described later.

[0191] In step S1803, if the total value B is 0, the risk determination unit 335 determines whether the total value A is equal to or less than the upper limit of the guarantee amount (step S1806).

[0192] In step S1806, if the sum A is not less than the guaranteed upper limit amount, that is, if the sum A exceeds the guaranteed upper limit amount, the risk determination unit 335 determines the risk in the transaction with this trading partner to be "medium" (step S1807) and terminates the processing.

[0193] In step S1806, if the total value A is equal to or less than the guaranteed upper limit amount, the risk determination unit 335 determines the risk in the transaction with this business partner to be "low" (step S1808), and ends the process.

[0194] Furthermore, in step S1804, if the total value B does not exceed the upper limit of the guarantee amount, the risk determination unit 335 determines whether the total value A is equal to or less than the upper limit of the guarantee amount (step S1809).

[0195] In step S1809, if the total value A is not equal to or less than the guaranteed upper limit amount, the process proceeds to step S1805. In other words, if there is an unpaid amount that is past due and the amount billed to the business partner exceeds the guaranteed upper limit amount, the risk determination unit 335 determines the risk of the transaction with this business partner to be "high."

[0196] In step S1809, if the total value A is equal to or less than the guaranteed upper limit amount, the risk determination unit 335 proceeds to step S1809. In other words, if there is an unpaid amount that is past due and the amount claimed against the business partner is less than the guaranteed upper limit amount, the risk determination unit 335 determines the risk of the transaction with this business partner to be "medium."

[0197] The risk assessment unit 335 of this embodiment performs the process of FIG. 18 for each trading partner registered as a trading partner that uses the credit guarantee service, and stores the risk assessment results in a assessment result table 339.

[0198] Incidentally, the risk determination unit 335 of this embodiment may, for example, after performing risk determination, calculate the ratio of the total value A (the total of unpaid billing amounts) to the guaranteed upper limit amount, and store it in the determination result table 339.

[0199] In addition, the process shown in FIG. 18 may be executed, for example, each time the warranty registration database 310 is updated; in other words, the process of FIG. 18 may be executed each time a transaction is conducted between a tenant and a business partner.

[0200] FIG. 19 is a diagram showing an example of a judgment result table. The judgment result table 339 of this embodiment is generated for each tenant. The judgment result table 339 has the following information items: tenant ID, business partner name, guarantee upper limit amount, total value A, ratio, total value B, and risk judgment result. In the judgment result table 339, the item "business partner name" is associated with other items, and information including the value of the item "business partner name" and the values ​​of the other items may be expressed as transaction status information. The transaction status information is information indicating the status of transactions between a tenant and a business partner. That is, the risk judgment unit 335 of this embodiment calculates the transaction status information. The business partner information may be updated every time the warranty registration database 310 is updated.

[0201] The value of the item "Total Value A" indicates the total amount of invoices whose payment status is unpaid in transactions between the corresponding business partner and tenant. The value of the item "Ratio" indicates the ratio of Total Value A to the guaranteed upper limit amount.

[0202] The value of the item "Total Value B" indicates the total amount of invoices that are unpaid and overdue in transactions between the corresponding business partner and tenant. The value of the item "Risk Assessment Result" indicates an index of risk when conducting transactions between the tenant ID and business partner.

[0203] In the example of FIG. 19, the tenant name "Company X" has three business partners: Company B, Company C, Company D, Company E, and Company F. Of these, for Company B, the total value A is less than the upper guarantee amount, and the total value B is 0. The ratio is also low at 5%. For this reason, the risk for Company X when doing business with Company B is deemed "low."

[0204] In addition, for Company C, total value A is less than the guaranteed upper limit amount, but total value B exists. Therefore, the risk for Company X when doing business with Company C is deemed "medium." In addition, for Company D, both total values ​​A and B are greater than the guaranteed upper limit amount. Therefore, the risk for Company X when doing business with Company D is deemed "high."

[0205] When the transaction management device 300 of this embodiment displays the home screen on the terminal device 400, the transaction management device 300 refers to this determination result table 339 to generate screen data for displaying the home screen.

[0206] Fig. 20 is a second diagram showing the home screen. Screen 111A shown in Fig. 20 shows a state in which "Company A", one of the business partners of tenant "Company X", has been newly registered as a business partner using the credit guarantee service, and the debt of Company D has been fulfilled by the credit guarantee service.

[0207] Screen 111A includes display columns 112A and 113A. Display columns 112-1, 112-2, 112-3, 112-4, etc. are displayed in display column 112A.

[0208] In the display field 112-1, the name of company B (business partner name) in the judgment result table 339, a marker 171 indicating the risk of transactions with company B, and transaction status information 172 are displayed.

[0209] Specifically, in the transaction status information for Company B, the guaranteed upper limit is 10 million yen, the total unpaid invoice amount is 500,000 yen, and there is no unpaid amount that is past the payment deadline (see FIG. 19).

[0210] Therefore, marker 171 is a marker indicating a "low" risk judgment result, and transaction status information 172 shows a guaranteed upper limit of 10 million yen, a total of unpaid invoice amounts of 500,000 yen, and an amount past due that is 0.

[0211] Furthermore, in display field 112-1, the guaranteed upper limit amount is displayed, and therefore information showing the details of the guarantee by company B is displayed.

[0212] In the display field 112-2, the name of company B (business partner name) in the judgment result table 339, a marker 173 indicating the risk of transactions with company C, and transaction status information 174 are displayed.

[0213] Specifically, Company C's transaction status information indicates that the guaranteed upper limit is 5 million yen, the total unpaid invoice amount is 3 million yen, and the amount of unpaid money that is past the due date is 500,000 yen (see FIG. 19).

[0214] Therefore, marker 173 is a marker indicating a "medium" risk assessment result, and transaction status information 174 shows a guaranteed upper limit of 5 million yen, a total of unpaid claims of 3 million yen, and an amount of 500,000 yen that is past due.

[0215] Moreover, in display field 112-2, the guaranteed upper limit amount is displayed, and therefore information showing the details of the guarantee by company C is displayed.

[0216] In the display field 112-3, the name of the company D (business partner name) in the judgment result table 339, a marker 175 indicating the risk of transactions with the company D, and transaction status information 176 are displayed.

[0217] Specifically, in Company D's transaction status information, the guaranteed upper limit is 2 million yen, the total unpaid invoice amount is 1.5 million yen, and the amount of unpaid money that is past the payment deadline is 1.5 million yen (see Figure 19).

[0218] Therefore, marker 175 is a marker indicating a "high" risk judgment result, and transaction status information 176 shows a guaranteed upper limit of 3 million yen, a total of unpaid invoice amounts of 2 million yen, and an amount of 1.5 million yen that is past the due date.

[0219] Furthermore, in display field 112-3, the guaranteed upper limit amount is displayed, and therefore information showing the details of the guarantee by company D is displayed.

[0220] The markers 171, 173, and 175 may have different display modes, and are not limited to the display mode shown in Fig. 20. The markers 171, 173, and 175 may be, for example, other than markers, and may be the risk judgment results of the judgment result table 339 displayed as they are.

[0221] In this embodiment, the display in the display fields 112 and 113 is updated every time the business partner information is updated.

[0222] In this manner, in this embodiment, a list of transaction status information showing the status of transactions between the tenant and each of its business partners is presented to the tenant. In other words, in this embodiment, a list of the business partners of the tenant, the amount of the transaction (unpaid amount), and the maximum guaranteed amount is presented to the tenant for each tenant.

[0223] Therefore, according to this embodiment, it is possible for a tenant to easily grasp the status of transactions with each business partner.

[0224] In this embodiment, the home screen also displays a list of information indicating the guarantee contents for each of the tenant's business partners. Therefore, according to this embodiment, it is possible to present to the tenant a list of the contents guaranteed by the credit guarantee service for each business partner.

[0225] Furthermore, in this embodiment, when registering a business partner who will use the claim guarantee service in the transaction management device 300, the business partner can be registered for the claim guarantee service simply by selecting a specific display component in the display field 112 to display a list of business partners and selecting the business partner from this list. Therefore, in this embodiment, the time and effort required for a tenant to manually input business partner information in order to use the claim guarantee service can be reduced, and registration for use of the claim guarantee service can be easily performed for each business partner.

[0226] Next, a description will be given of the display field 113. In the display field 113, a list of transaction status information for each business partner is displayed.

[0227] Here, when an operation is performed to select a display field corresponding to any one of the business partners in display field 112A, a list of invoice information of the selected business partner may be displayed in display field 113.

[0228] In this case, for example, invoice information whose payment status is unpaid or invoice information whose payment is delayed may be highlighted. Also, display component 114 may be displayed in display field 113 in association with the highlighted invoice information.

[0229] In this way, by displaying the display component 114 for instructing the performance of a debt in association with unpaid invoice information, it is possible to instruct the performance of a debt for each invoice information.

[0230] In addition, in the display field 113 shown in FIG. 20, a display component 114 is displayed in association with Company D, whose risk assessment result is "high."

[0231] When terminal device 400 accepts an operation to select display component 114 on screen 111A, it transmits a request for performance of the debt of company D to transaction management device 300.

[0232] The transaction management device 300 may send a notification to the claim guarantee management system 500 indicating that the request for performance of Company D's debt has been accepted.

[0233] The terminal device 700 transmits a display request for a performance history information list screen including the performance history information of company D to the transaction management device 300. Fig. 21 is a diagram showing an example of the performance history information list screen.

[0234] Screen 151A shown in Fig. 21 is displayed on terminal device 700 in step S1715 of Fig. 17. Screen 151A has display column 152A, and display components 153, 154A, 155, and 156A.

[0235] In the display field 152A, a list of performance history information stored in the performance history database 320 is displayed.

[0236] The display component 154A is a display component for displaying, among the performance history information, only performance history information whose performance status is "in performance" in the display field 152A.

[0237] The display component 156A is a display component that is displayed in association with performance history information whose performance status is "in performance." In the display field 152A, the performance history information of Company D and the display component 156A are displayed in association with each other. When the terminal device 700 receives an operation to select the display component 156A, the terminal device 700 may transition the screen 151A to a screen for confirming whether or not the debt has been performed.

[0238] In addition, in the list of performance history information displayed in the display field 152A, a button for viewing image data of the invoice corresponding to the performance history information may be displayed for each performance history information.

[0239] When the transaction management device 300 of this embodiment receives a notification from the claim guarantee management system 500 indicating that the performance of the debt has been completed, it changes the performance status in the performance history database 320 from "in performance" to "performed." Then, the transaction management device 300 reflects the result of the debt performance or execution in the total value A, total value B, etc. in the guarantee registration database 310.

[0240] Next, the cancellation operation in the transaction management system 100 of this embodiment will be described with reference to Figure 22. Cancellation refers to receiving payment for the invoice amount and changing the payment status in the invoice information stored in the invoice database 210 to "paid."

[0241] 22 is a fifth sequence diagram explaining the operation of the information processing system. In the transaction management system 100 of this embodiment, the document management device 200 displays a settlement screen on the terminal device 400 (step S2201). The settlement screen may be displayed from the document management device 200 to the terminal device 400 periodically, for example.

[0242] Next, the terminal device 400 accepts an operation to set invoice information to be cleared (step S2202). Next, the terminal device 400 accepts input of clearing information (step S2203). Next, the terminal device 400 accepts a clearing operation to instruct clearing (step S2204).

[0243] When the terminal device 400 accepts the cancel operation, it transmits a cancel request for the corresponding invoice information to the document management device 200 (step S2205).

[0244] The transaction management device 300 receives the clearing request and clears the corresponding invoice information (step S2206). Specifically, the document management device 200 uses the clearing unit 233 to identify the corresponding invoice information in the invoice database 210, and changes the item "payment status" of the identified invoice information from "unpaid" to "paid." With the above process, the clearing of the unpaid amount is completed.

[0245] In this embodiment, an invoice is described as an example of a form, but, for example, a quote may be used as an example of a form. In other words, in this embodiment, the transaction status information, information identified from the invoice information, and information indicating the warranty content are included in the warranty registration information, but this is not limited to this. The information included in the warranty registration information may include the transaction status information, information identified from the invoice information, information identified from the quote information, and information indicating the warranty content.

[0246] Fig. 23 is a diagram showing an example of a quotation database. Quotation information is stored in quotation database 210A shown in Fig. 23. The quotation information includes information items such as quote recipient, estimated amount, estimated date, planned billing date, planned deadline, status, order date, billing date, payment date, invoice ID, etc.

[0247] The value of the field "Quoter" is the business partner to which the quote is issued. The value of the field "Estimated Amount" is the estimated amount listed on the quote. The value of the field "Estimated Date" indicates the date on which the quote was issued. The value of the field "Scheduled Invoice Date" indicates the scheduled date on which the invoice is to be issued. The value of the field "Scheduled Payment Due Date" indicates the scheduled date on which payment of the invoice amount is due.

[0248] The value of the item "Status" indicates the status of the transaction. The value of the item "Order Date" indicates the date the order for the quotation was received. The value of the item "Invoice Date" indicates the date the invoice corresponding to the quotation was issued. The value of the item "Payment Date" indicates the date the invoice amount was received. The value of the item "Invoice ID" indicates identification information for identifying the invoice corresponding to the quotation.

[0249] In this embodiment, for example, when the risk determination unit 335 performs risk determination, the estimate database 210A may be referenced.

[0250] A case where the risk assessment unit 335 assesses a risk using the invoice information and the estimate information will be described below with reference to Fig. 24. Fig. 24 is a second flowchart illustrating the processing of the risk assessment unit.

[0251] In the example of FIG. 24, the risk assessment unit 335 calculates the sum of the unpaid billing amount and the amount obtained by multiplying the estimated amount by the order acceptance rate for each client of the tenant, and sets the sum as a sum A' (step S2401).

[0252] The order acceptance rate indicates the ratio of the number of quotation information records in which a value is input in the item "order date" to the number of quotation information records of a supplier in quotation database 210A.

[0253] For example, when the business partner is Company A, the number of records of quotation information stored in quotation database 210A is four (see FIG. 23). Of these four pieces of quotation information, the number of records of quotation information in which a value has been entered in the item "Order date" indicating that an order for the quoted content has actually been received is zero.

[0254] Therefore, in the case of Company A, the estimated amount multiplied by the order rate is 0 yen, and the total value A' is the same as the total value A of the unpaid invoice amount.

[0255] The processing from step S2402 to step S2409 in FIG. 24 is similar to the processing from step S18002 to step S1809 in FIG. 18 except that the sum A is set to the sum A', and therefore description thereof will be omitted.

[0256] In this manner, according to this embodiment, a list of information indicating the guarantee contents of a trading partner can be presented to a tenant who is a user of the transaction management system 100 including the transaction management device 300.

[0257] In this embodiment, part of the warranty registration information includes a portion of the invoice information obtained by document recognition, but the warranty registration information does not have to include information obtained by document recognition.

[0258] Specifically, for example, a part of the invoice information included in the warranty registration information may be obtained separately from a device other than the document management device 200.

[0259] Each function of the above-described embodiments can be realized by one or more processing circuits. Here, the term "processing circuit" in this specification includes a processor programmed to execute each function by software, such as a processor implemented by an electronic circuit, and a device such as an ASIC (Application Specific Integrated Circuit), a DSP (digital signal processor), an FPGA (field programmable gate array), or a conventional circuit module designed to execute each function described above.

[0260] Additionally, the devices described in the embodiments are merely representative of one of multiple computing environments for implementing the embodiments disclosed herein.

[0261] In one embodiment, the document management device 200 includes multiple computing devices, such as a server cluster, configured to communicate with each other over any type of communication link, including a network, shared memory, etc., to perform the processes disclosed herein. Similarly, the document management device 200 may include multiple computing devices configured to communicate with each other.

[0262] Furthermore, the form management device 200 can be configured to share the disclosed processing steps in various combinations. For example, the processes executed by the form management device 200 can be executed by other server devices. Similarly, the functions of the form management device 200 can be executed by other server devices. Also, the server device and each element of the other server devices may be integrated into one server device or may be separated into multiple devices.

[0263] The correspondence table in the statement may be generated by the learning effect of machine learning. Also, by classifying keywords that may be included in the description of transaction details and account items by machine learning, it is not necessary to use the correspondence table.

[0264] Here, machine learning is a technology that allows a computer to acquire human-like learning capabilities, in which the computer autonomously generates algorithms necessary for judgments such as data identification from learning data that is previously loaded, and applies these to new data to make predictions. The learning method for machine learning may be any of supervised learning, unsupervised learning, semi-supervised learning, reinforcement learning, and deep learning, or may be a combination of these learning methods; any learning method for machine learning is acceptable.

[0265] Although the present invention has been described above based on the embodiments, the present invention is not limited to the requirements shown in the above embodiments. These points can be changed without departing from the spirit of the present invention, and can be appropriately determined according to the application form. [Explanation of symbols]

[0266] 100 Information Processing Systems 200 Document management device 210 Invoice Database 220 Business Partner Database 230 Document Management Department 300 Transaction Management Device 310 Warranty Registration Database 320 Performance History Database 330 Transaction Management Department 331 Input Reception Unit 332 Information Acquisition Department 333 Registration Department 334 Performance Management Department 335 Risk Assessment Department 336 Screen Output Section 337 Communications Department 339 Judgment Result Table 400, 700 terminal equipment 500 Credit guarantee management system 600 Credit guarantee management device [Prior art documents] [Patent documents]

[0267] [Patent Document 1] JP 2020-003960 A

Claims

1. A registration unit that stores in a memory unit guarantee registration information that corresponds to business partner information indicating a business partner, invoice information for the business partner, and information input from a terminal device indicating the content of a guarantee for a claim against the business partner; an information processing device having a screen output unit that refers to the memory unit and displays, for each of the multiple trading partners, transaction status information indicating the status of transactions with the trading partners and information indicating the guarantee content on a display unit.

2. The information processing device according to claim 1 , wherein the transaction status information includes at least information indicating an amount of a transaction being made with the business partner.

3. An information processing device as described in claim 2, wherein the amount of the transaction with the business partner is the amount of the transaction calculated based on the invoice information.

4. an information acquisition unit that acquires the business partner information and the invoice information; The information processing apparatus according to claim 2 , further comprising an input receiving unit for receiving an input of information indicating the guarantee content.

5. a risk determination unit that identifies an amount of the transaction from the invoice information, and determines a risk of a transaction with the trading partner for each trading partner based on the amount of the transaction and information indicating the guarantee content; The information processing apparatus according to claim 4 , wherein the screen output unit causes the display unit to display a list of the judgment results for each of the business partners.

6. The risk assessment unit is determining the risk based on a maximum guarantee amount included in the information indicating the guarantee content and an amount of the transaction with the trading partner; 6. The information processing apparatus according to claim 5, further comprising: generating and storing the transaction status information including the guaranteed upper limit amount, the amount of the transaction with the trading partner, and the result of the risk assessment.

7. The amount of the transaction with the said business partner is, The total amount of unpaid invoice amounts invoiced to the business partner, The risk assessment unit is The information processing apparatus according to claim 6 , wherein the risk is determined using a total amount of the unpaid amount and a total amount of the unpaid amount that is past due for payment.

8. The screen output unit is The information processing apparatus according to claim 7 , further comprising: a display unit configured to display a list of the transaction status information for each of the business partners.

9. The transaction status information is 9. The information processing device according to claim 7, wherein the warranty registration information is updated every time the warranty registration information is updated.

10. The information processing apparatus according to claim 3 , wherein the invoice information is acquired by performing form recognition on an invoice issued to the business partner.

11. An information processing method by an information processing device, comprising: storing in a storage unit guarantee registration information that associates customer information indicating a customer, invoice information for the customer, and information input from a terminal device indicating the details of a guarantee for a claim against the customer; An information processing method comprising: referring to the storage unit; and displaying, for each of a plurality of said business partners, transaction status information indicating the status of transactions with said business partners and information indicating the guarantee content on a display unit.

12. A method for storing guarantee registration information in a storage unit, the guarantee registration information correlating customer information indicating a customer, invoice information for the customer, and information input from a terminal device indicating the details of a guarantee for a claim against the customer, An information processing program that causes a computer to execute a process of referring to the memory unit and displaying, for each of the multiple trading partners, transaction status information indicating the status of transactions with the trading partner and information indicating the guarantee content on a display unit.

13. An information processing system including a terminal device and an information processing device, The information processing device includes: a registration unit that stores in a storage unit guarantee registration information that associates customer information indicating a customer, invoice information for the customer, and information input from a terminal device indicating the details of a guarantee for a claim against the customer; a screen output unit that refers to the storage unit and outputs, for each of the plurality of trading partners, transaction status information indicating a transaction status with the trading partner and information indicating the guarantee content to the terminal device, The terminal device an information processing system having a display unit that displays, for each of the business partners, transaction status information indicating the status of a transaction with the business partner and information indicating the guarantee content;

Images