JP2022060819A - Information processing apparatus, information processing method, information processing program, and information processing system - Google Patents

Abstract

To cause a user to recognize a condition of a transaction with a client.SOLUTION: An information processing apparatus includes: a registration unit which stores client information indicative of clients and information indicative of warranty details of receivables from the clients into a storage unit in association with each other; and a window output unit which causes a display unit to display transaction condition information indicative of conditions of transactions with each of the clients and information indicative of warranty details of receivables from each of the clients.SELECTED DRAWING: Figure 11A

Description

The present invention relates to an information processing apparatus, an information processing method, an information processing program, and an information processing system.

Conventionally, when a claim is incurred by a business operator, a guarantee claim including claim information is obtained, an insurance claim is made for the claim related to the debt when the debt is defaulted, and a guarantee deposit is given to the creditor business operator. Warranty service devices are known to perform processing for payment.

In the above-mentioned conventional technique, it is not considered to grasp the transaction status between the business operator and the business partner before and after the default occurs.

The present invention has been made in view of the above circumstances, and an object of the present invention is to make it possible to grasp the status of transactions with business partners.

The disclosed technology includes a registration unit that stores customer information indicating a business partner and information indicating the guarantee content of a claim against the business partner in a storage unit, and a business partner for each business partner. It is an information processing apparatus having a transaction status information indicating a transaction status and a screen output unit for displaying the information indicating the guarantee content on the display unit.

It is possible to grasp the status of transactions with business partners.

It is a figure which shows an example of the system configuration of the information processing system of this embodiment. It is a figure which shows an example of the hardware composition of an information processing apparatus. It is a figure which shows an example of the hardware composition of a terminal apparatus. It is a figure which shows an example of an invoice database. It is a figure which shows an example of the business partner database. It is a figure which shows an example of the guarantee registration database. It is a figure which shows an example of the performance history database. It is a figure explaining the functional structure of each apparatus which an information processing system has. It is a 1st sequence diagram explaining the operation of an information processing system. It is a second sequence diagram explaining the operation of an information processing system. It is the first figure which shows the home screen. It is a figure which shows another display example of a display column. It is a figure which shows an example of the selection screen of a business partner. It is a figure which shows the example of the registration screen. It is a 3rd sequence diagram explaining the operation of an information processing system. It is a figure which shows an example of the list screen of application information. It is a figure which shows an example of the input screen of the guarantee contents. It is a 4th sequence diagram explaining the operation of an information processing system. It is the first flowchart explaining the process of a risk determination part. It is a figure which shows an example of the determination result table. It is the second figure which shows the home screen. It is a figure which shows an example of the list screen of the performance history information. It is a fifth sequence diagram explaining the operation of an information processing system. It is a figure which shows an example of the quotation database. It is a 2nd flowchart explaining the process of a risk determination part.

The embodiments will be described below with reference to the drawings. FIG. 1 is a diagram showing an example of a system configuration of the information processing system of the present embodiment.

The information processing system 1 of the present embodiment includes a transaction management system 100 and a terminal device 400.

The transaction management system 100 includes a form management device 200 and a transaction management device 300. The form management device 200 and the transaction management device 300 of the present embodiment may be realized by, for example, a general information processing device. For example, the transaction management device 300 of the present embodiment is the first information processing device, and the form management device 200 is the second information processing device.

Further, the transaction management system 100 of the present embodiment communicates with the terminal device 400 and the credit guarantee management system 500.

In the transaction management system 100 of the present embodiment, the terminal device 400 is, for example, a terminal device used by a business operator who conducts transactions with various business partners. The business operator of the present 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 expressed as a tenant. Further, a user who actually operates the terminal device 400 may be expressed as a tenant.

The credit guarantee management system 500 is managed by a credit guarantee organization or the like that provides a service for guaranteeing a claim relating to a debt when a default occurs at a business partner of a business operator who uses the terminal device 400.

In the following description, the service provided to the tenant by the credit guarantee management system 500 may be referred to as a credit guarantee service.

In addition, the claim guarantee service of this embodiment is a claim that the claim amount is within the range of the predetermined guarantee upper limit amount when the tenant or the invoiced amount cannot be paid due to reasons such as lack of funds of the business partner. It is a service that pays to the tenant from the credit guarantee organization that manages the guarantee management system 500.

The claim of the present embodiment is a right that the tenant can request the business partner who issued the invoice to pay the invoice amount, and is a right that the tenant has to the business partner.

The claims in this embodiment are not limited to the invoices issued by the tenant to the business partner, but also the purchase orders received from the business partner, the forms such as receipts, and the tenant issued to the business partner. It may be the right of the tenant to request the business partner to pay for the goods, services, etc. according to the form such as the quotation and the invoice.

The credit guarantee management system 500 of the present embodiment includes a credit guarantee management device 600 and a terminal device 700. The credit guarantee management device 600 stores, for example, information input from the terminal device 700, information acquired by communication with the transaction management system 100, and the like. The terminal device 700 is used by the administrator of the credit guarantee management system 500 or the like.

In the transaction management system 100 of the present embodiment, the form management device 200 has an invoice database 210, a business partner database 220, and a form management unit 230. Further, in the transaction management system 100, the transaction management device 300 has a guarantee registration database 310 and a performance history database 320.

The transaction management system 100 of the present embodiment receives a request from the tenant via the terminal device 400, and registers a business partner who uses the credit guarantee service in the credit guarantee management system 500.

Specifically, the transaction management system 100 stores the information of the form issued from the tenant to the business partner in the invoice database 210 by the form management unit 230 of the form management device 200. In the following description of the embodiment, the invoice will be described as an example of the invoice, but the invoice is not limited to the invoice. The form may be a quotation, a delivery note, or the like.

Further, the form management device 200 stores the information indicating the business partner specified 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 billing destination for the billed amount.

Further, in the form management device 200, the form management unit 230 receives a request from the terminal device 400 to register the customer information in the credit guarantee management system 500, and makes a transaction with the invoice information of the tenant who uses the terminal device 400. The destination information is transmitted to the transaction management device 300.

The transaction management device 300 transmits the invoice information and the business partner information to the credit guarantee management system 500 by the transaction management unit 330, and accepts the input of the information indicating the guarantee content. Then, the transaction management unit 330 associates the customer information with the information indicating the guarantee content and stores it in the guarantee registration database 310. In the following description, the information stored in the warranty registration database 310 is referred to as warranty registration information.

Further, the transaction management device 300 receives a request from the terminal device 400 and causes the terminal device 400 to display a list of guarantee registration information for each business partner of the tenant.

Further, when the default of the debt occurs, the transaction management device 300 receives a request from the terminal device 400 by the transaction management unit 330, and requests the credit guarantee management system 500 to guarantee the claim relating to the debt. .. In other words, the transaction management device 300 requires the credit guarantee management system 500 to fulfill its obligations for this transaction.

Then, the transaction management unit 330 stores the performance history information indicating the history of the performance of the debt indicating that the performance of the debt is requested, the performance of the debt, and the like in the performance history database 320.

As described above, in the transaction management system 100 of the present embodiment, the status of transactions between the tenant and each business partner can be presented to the tenant.

Further, in the present embodiment, since the tenant's business partner is specified from the form information managed by the form management device 200 and registered as the business partner using the credit guarantee service provided by the credit guarantee management system 500, the business partner is registered. There is no work such as the tenant entering the information of. Therefore, in the present embodiment, the time and effort required to easily use the credit guarantee service can be reduced.

In the example of FIG. 1, the transaction management system 100 includes, but is not limited to, the form management device 200 and the transaction management device 300. The form management device 200 and the transaction management device 300 may be realized by, for example, one information processing device, or the form management device 200 and the transaction management device 300 may be realized by a plurality of information processing devices. good.

Further, in the example of FIG. 1, the form management device 200 has an invoice database 210 and a business partner database 220, and the transaction management device 300 has a guarantee registration database 310 and a performance history database 320. However, it is not limited to this.

Each of the above-mentioned databases may be partially or wholly provided in an external device other than the form management device 200 and the transaction management device 300. Further, for example, the above-mentioned four databases may be provided in either the form management device 200 or the transaction management device 300.

Hereinafter, the hardware configuration of the information processing device that realizes the form management device 200 and the transaction management device 300 and the hardware configuration of the terminal device 400 will be described with reference to FIGS. 2 and 3.

FIG. 2 is a diagram showing an example of the hardware configuration of the information processing apparatus. FIG. 2 shows, as an example, the hardware configuration of the form management device 200, which is the second information processing device.

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

Of these, the CPU 201 controls the operation of the entire form management device 200. The ROM 202 stores a program used to drive the CPU 201 such as an IPL. The RAM 203 is used as a work area of the CPU 201. The HD204 stores various data such as programs. The HDD controller 205 controls reading or writing of various data to the HD 204 according to the control of the CPU 201. The display 206 displays various information such as cursors, menus, windows, characters, or images. The external device connection I / F 208 is an interface for connecting various external devices. The external device in this case is, for example, a USB (Universal Serial Bus) memory, a printer, or the like. The network I / F 209 is an interface for performing 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.

Further, the keyboard 211 is a kind of input means including a plurality of keys for inputting characters, numerical values, various instructions and the like. The pointing device 212 is a kind of input means for selecting and executing various instructions, selecting a processing target, moving a cursor, and the like. The DVD-RW drive 214 controls reading or writing of various data to the DVD-RW 213 as an example of a detachable recording medium. The DVD-RW is not limited to the DVD-RW, and a DVD-R or the like may be used. The media I / F 216 controls reading or writing (storage) of data to a recording medium 215 such as a flash memory.

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

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

The CMOS (Complementary Metal Oxide Semiconductor) sensor 405 is a kind of built-in imaging means for capturing an image of a subject (mainly a self-image) and obtaining image data under the control of a CPU 401. It should be noted that the image pickup means such as a CCD (Charge Coupled Device) sensor may be used instead of the CMOS sensor.

The image sensor I / F 406 is a circuit that controls the drive of the CMOS sensor 405. The acceleration / orientation sensor 407 is a variety of sensors such as an electronic magnetic compass, a gyro compass, and an acceleration sensor that detect the geomagnetism. The media I / F 409 controls reading or writing (storage) of data to a recording medium 408 such as a flash memory. The GPS receiving unit 411 receives a GPS signal from a GPS satellite.

Further, the terminal device 400 includes a long-distance communication circuit 412, an antenna 412a of the long-distance communication circuit 412, a CMOS sensor 413, an image pickup element I / F 414, a microphone 415, a speaker 416, a sound input / output I / F 417, a display 418, and an external device. It includes a connection I / F (Interface) 419, a short-range communication circuit 420, an antenna 420a of the short-range communication circuit 420, and a touch panel 421.

Of these, the telecommunications circuit 412 is a circuit that communicates with other devices via a communication network. The CMOS sensor 413 is a kind of built-in image pickup means for capturing an image of a subject and obtaining image data under the control of the CPU 401. The image sensor I / F 414 is a circuit that controls the drive of the CMOS sensor 413. The microphone 415 is a built-in circuit that converts sound into an electric signal. The speaker 316 is a built-in circuit that converts an electric signal into physical vibration to produce sounds such as music and voice. The sound input / output I / F 417 is a circuit that processes sound signal input / output between the microphone 415 and the speaker 416 under the control of the CPU 401.

The display 418 is a kind of display means such as a liquid crystal display or an organic EL (Electro Luminescence) for displaying an image of a subject, various icons, and the like. The external device connection I / F419 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 kind of input means for operating the terminal device 400 by the user pressing the display 418. The display 418 is an example of a display unit included in the terminal device 400.

Next, each database included in the transaction management system 100 of the present embodiment will be described with reference to FIGS. 4 to 7.

FIG. 4 is a diagram showing an example of an invoice database. The invoice database 210 of this embodiment is provided for each tenant. Further, in the invoice database 210, invoice information is accumulated when the tenant issues an invoice to the business partner.

The invoice database 210 of the present embodiment includes a tenant ID, a billing address, a billing amount, a billing date, a payment deadline date, a payment status, a payment date, and the like as information items.

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

The value of the item "Billing" indicates where the billing amount will be billed. In other words, the value of the item "billing destination" is the business partner of the tenant specified by the tenant ID.

The value of the item "Invoice Amount" indicates the amount to be charged, and the value of the item "Invoice Date" indicates the date when the invoice was issued. The value of the item "Payment deadline" indicates the payment deadline of the billed amount.

The value of the item "payment status" indicates whether or not the invoiced amount has been paid, and is changed according to the operation from the terminal device 400. Further, in the invoice information, the invoice amount for which the value of the item "payment status" is "unpaid" is the amount of the transaction between the tenant and the business partner. The value of the item "payment date" indicates the date when the billing amount was deposited in the bank account of the tenant ID.

The image data of the invoice or the 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 the invoice information.

As described above, the invoice information of the present embodiment can be said to be information regarding the invoice to the business partner.

FIG. 5 is a diagram showing an example of a customer database. The customer database 220 of the present embodiment may be provided for each tenant. Further, the business partner information of this embodiment is registered by the tenant.

The business partner database 220 of the present embodiment includes a tenant ID, a business partner name, an address, a telephone number, an e-mail address, a person in charge, and the like as information items.

In the supplier database 220, each value of the items "customer name", "address", "telephone number", "email address", and "contact person name" is the name, address, telephone number, and email address of the supplier. , Show the name of the person in charge.

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

The value of the item "tenant name" indicates the name of the tenant. The value of the item "account name" is the name of the account indicated by the value of the item "account name" in the account database 220. The value of the item "address" indicates the address of the business partner. The value of the item "transaction start date" indicates the date when the tenant and the business partner started the transaction. Specifically, the registration unit 333 may set the oldest invoice date included in the invoice information stored in the invoice database 210 as the transaction start date.

The value of the item "whether or not payment is delayed" indicates whether or not the payment of the billed amount from the business partner to the tenant is delayed. Specifically, the registration unit 333 has invoice information stored in the invoice database 210 in which the payment deadline has been exceeded and the value of the item "payment status" is "unpaid". If is present, the value of the item "Presence / absence of payment delay" is set to "Yes".

The value of the item "application status" indicates whether or not the credit guarantee service can be used. Specifically, when the value of "application status" is "examined", it indicates that the credit guarantee service can be used for this business partner. In addition, when the value of the item "application status" is "under examination" and when there is no value of the item "application status", it indicates that the credit guarantee service for this business partner is not available.

The value of the item "guaranteed upper limit amount" indicates the upper limit amount guaranteed to the business partner. The value of the item "guarantee period" indicates the period during which the credit guarantee service can be used for the business partner.

That is, the guarantee registration information of the present embodiment includes at least a part of the business partner information, a part of the invoice information, and information indicating the guarantee contents for the business partner.

FIG. 7 is a diagram showing an example of a performance history database. The performance history database 320 of the present embodiment includes, as information items, a tenant name, a business partner name, a billing amount, a billing date, a payment deadline date, a performance status, a performance execution date, a guarantee upper limit amount, a guarantee period, and the like.

In the performance history database 320, the item "tenant name" and other items are associated with each other, and in the performance history database 320, the performance history contains information including the value of the item "tenant name" and the value of other items. Call it information.

The value of the item "Fulfillment status" indicates the performance status of the obligation. The value of the item "Performance Execution Date" indicates the date on which the obligation was fulfilled.

It should be noted that the image data of the invoice to be executed or the storage destination information such as a file path indicating the storage destination of the image data may be stored in the performance history database 320 as the performance history information.

Next, with reference to FIG. 8, the functions of each device of the transaction management system 100 of the present embodiment will be described. FIG. 8 is a diagram illustrating a functional configuration of each device included in the information processing system.

First, the form management device 200 will be described. The form management device 200 of the present embodiment has an invoice database 210, a business partner database 220, and a form management unit 230. The invoice database 210 and the customer database 220 are realized by storage devices such as 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 the form recognition program.

The form management unit 230 has a form recognition unit 231, a request reception unit 232, a clearing unit 233, a communication unit 234, and a form generation unit 235.

The form recognition unit 231 extracts the name (item name) of the item included in the form image indicated by the form image data acquired by the form management device 20, and the value (item value) of this item, and the item and the value of the item. Form recognition is performed by converting and to text data and associating them. 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 the invoice is used as an example of the form, the information indicating the form recognition result is the invoice information.

The request reception unit 232 receives various requests for the form management device 200. Specifically, the request reception unit 232 receives a request for acquisition of invoice information and business partner information from the transaction management device 300.

The clearing unit 233 accepts an operation of changing the value of the item "payment status" included in the invoice information stored in the invoice database 210 by the operation from the terminal device 400. Specifically, the clearing unit 233 changes the value of the item "payment status" from "unpaid" to "paid" according to the operation from the terminal device 400.

The communication unit 234 transmits / receives information between the form management device 200 and each of the other devices. The form generation unit 235 issues an invoice by operating from the terminal device 400, and stores the invoice information of the issued invoice in the invoice database 210.

Next, the transaction management device 300 will be described. The transaction management device 300 has a guarantee registration database 310, a performance history database 320, and a transaction management unit 330.

The guarantee registration database 310 and the performance history database 320 are realized by storage devices such as ROM, RAM, and HD included in the transaction management device 300. The transaction management unit 330 is realized by the CPU of the transaction management device 300 reading and executing the transaction management program.

The transaction management unit 330 of the present embodiment includes an input reception unit 331, an information acquisition unit 332, a registration unit 333, a performance management unit 334, a risk determination unit 335, a screen output unit 336, and a communication unit 337.

The input receiving unit 331 receives various inputs to the transaction management device 300. Specifically, the input reception unit 331 accepts, for example, a request for registration for enabling the use of the credit guarantee service. Further, the input receiving unit 331 receives input of information or the like indicating the guarantee contents to the business partner from the terminal device 700 or the like of the credit guarantee management system 500.

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 form management device 200.

The registration unit 333 registers (stores) the acquired business partner information in the guarantee registration database 310 in association with the information indicating the guarantee content received by the input reception unit 331.

The performance management unit 334 stores the performance history information in the performance history database 320 when an operation related to the performance of the debt or the performance of the debt by the credit guarantee service is performed. In other words, the performance management unit 334 updates the performance history database 320.

The risk determination unit 335 determines the degree of risk of transactions between the tenant and the business partner based on the information indicating the guarantee content for each business partner stored in the guarantee registration database 310 and the invoice information for each business partner. , It is retained as a determination result table 339.

More specifically, the risk determination unit 335 calculates the amount of money in transaction with the tenant for each business partner from the invoice information, the amount of money in transaction, information indicating the guarantee contents for each business partner, and payment. Determine the degree of risk of transactions with business partners based on the presence or absence of delays.

Then, the risk determination unit 335 provides transaction status information in which the amount of money in the transaction, information indicating the guarantee contents for each business partner, the presence or absence of payment delay, and the degree of risk of the transaction with the business partner are associated with each other. It is stored in the determination result table 339.

Details of the processing of the risk determination unit 335 and the determination result table 339 will be described later.

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

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

The terminal device 400 of the present embodiment has a display control unit 440 and a communication unit 454500. The display control unit 440 controls the display on 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 or the like for using the credit guarantee service.

The communication unit 450 transmits / receives information between the terminal device 400 and each of the other devices. The terminal device 700 of the present embodiment may also have a display control unit and a communication unit, similarly to the terminal device 400.

Next, the operation of the transaction management system 100 of the present embodiment will be described. FIG. 9 is a first sequence diagram illustrating the operation of the information processing system. FIG. 9 shows the operation of the transaction management system 100 when the invoice information and the business partner information are stored in the form management device 200.

In the transaction management system 100 of the present embodiment, the form management device 200 causes the terminal device 400 to display the invoice issuance screen by the form generation unit 235 of the form management unit 230 (step S901).

The form management device 200 can display the issuing screen on the terminal device 400 by accessing a specific URL (Uniform Resource Locator) or clicking a link, a button, or the like displayed on the screen in the terminal device 400, for example. It may be displayed in.

Subsequently, the terminal device 400 accepts the setting of invoice information by the tenant (user belonging to the tenant) (step S902). Specifically, the terminal device 400 accepts, for example, settings such as a billing address, a billing amount, a billing date, and a payment deadline date.

Subsequently, the terminal device 400 receives the invoice issuance operation by the tenant (step S903), and the communication unit 450 transmits the invoice information to the form management device 200 (step S904).

Subsequently, 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 generates PDF data of the invoice based on the invoice information received by the communication unit 234, and transmits the PDF data to a preset e-mail address of the billing destination or the like. You may.

Subsequently, the form management device 200 stores the invoice information in the invoice database 210 (step S906).

The form management device 200 of the present embodiment receives, for example, image data generated by scanning an invoice from a terminal device 400, and forms a form with respect to an image (image of the invoice) indicated by the image data. The result of form recognition by the recognition unit 231 may be used as invoice information.

FIG. 10 is a second sequence diagram illustrating the operation of the information processing system. FIG. 10 shows the operation of the transaction management system 100 when registering the guarantee registration information in the guarantee registration database 310 in the transaction management device 300.

In the transaction management system 100 of the present embodiment, the transaction management device 300 causes the terminal device 400 to display the home screen of the credit guarantee service by the screen output unit 336 (step S1001). Details of the home screen will be described later.

When the terminal device 400 receives the registration operation of the business partner information by the communication unit 450 (step S1002), the terminal device 400 transmits the business partner registration request to the transaction management device 300 (step S1003).

In response to the request for registration of customer information, the transaction management device 300 requests the form management device 200 to acquire a list of billing destinations (customers) included in the invoice information of the tenant by the information acquisition unit 332. Transmit (step S1004).

The form management device 200 receives a request by the request receiving unit 232 and acquires a list of business partners (step S1005). Specifically, the form 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 a list of business partners.

Next, the form management device 200 transmits a list of business partners to the transaction management device 300 by the communication unit 234 (step S1006).

When the transaction management device 300 acquires the list of business partners, the screen output unit 336 generates screen data for displaying the business partner selection screen (step S1007). Then, the transaction management device 300 transmits the generated screen data to the terminal device 400 by the communication unit 337 as a response to the registration operation of the customer information, and displays the selection screen (step S1008). Details of the selection screen will be described later.

When the terminal device 400 accepts the selection of the business partner on the selection screen (step S1009), the terminal device 400 transmits the selected business partner name to the transaction management device 300 (step S1010).

When the transaction management device 300 receives the business partner name, the information acquisition unit 332 transmits a request for acquisition of the business partner information corresponding to the business partner name to the form management device 200 (step S1011).

When the form management device 200 receives the request by the request reception unit 232, the form management device 200 acquires the business partner information whose value of the item "name" matches the selected business partner name in the business partner database 220, and sends the transaction management device 300 to the transaction management device 300. Transmit (step S1012).

When the transaction management device 300 acquires the customer information by the information acquisition unit 332, the registration unit 333 sets the acquired customer information as a part of the guarantee registration information stored in the guarantee registration database 310 (step). S1013).

Next, the transaction management device 300 transmits a request for acquisition of invoice information of the selected business partner to the form management device 200 (step S1014).

When the form management device 200 receives the invoice information acquisition request by the request receiving unit 232, the invoice database 210 corresponding to the tenant has a billing that matches the value of the item "billing destination" with the selected business partner. The document information is acquired and transmitted to the transaction management device 300 (step S1015).

Subsequently, the transaction management device 300 identifies the information to be registered as the guarantee registration information from the acquired invoice information by the registration unit 333, and sets it as a part of the guarantee registration information (step S1016).

Specifically, the registration unit 333 sets the oldest billing date included in the acquired invoice information as the value of the "transaction start date". In addition, when the invoice information that has not been paid exists even though the payment deadline has been exceeded, the registration unit 333 sets the value of the item "presence or absence of payment delay" of the guarantee registration information to "yes". do.

That is, the registration unit 333 of the present embodiment includes the information of a predetermined specific item from the invoice information as a part of the guarantee registration information.

Subsequently, the transaction management device 300 associates the customer information set in step S1013 with a part of the invoice information set in step S1015 by the registration unit 333 to obtain the guarantee registration information, and obtains the guarantee registration database 310. Store (register) in (step S1017).

At this time, the guarantee registration information stored in the guarantee registration database 310 does not include information indicating the guarantee contents such as the items "application status", "guarantee upper limit amount", "guarantee period" and the like.

Subsequently, the transaction management device 300 generates screen data for displaying the registration screen including the guarantee registration information by the screen output unit 336, and transmits the screen data to the terminal device 400 by the communication unit 337 to display the screen data. (Step S1018).

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

The processes of steps S1014 to S1017 in FIG. 10 may be executed each time a transaction is made between the tenant and the business partner. In other words, the guarantee registration database 310 may be updated every time a transaction is made between the tenant and the business partner. The transaction includes, for example, issuance of an invoice from the tenant to the business partner, payment of the invoice amount from the business partner to the tenant, and the like.

Hereinafter, a display example in the terminal device 400 will be described with reference to FIGS. 11 to 13. FIG. 11A is a first diagram showing a home screen.

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

The tenant name is displayed on the screen 111, and has a display field 112 and a display field 113. In the display field 112, a list of business partner names registered as business partners who use the credit guarantee service is displayed. In other words, in the display field 112, a list of business partner names in which the guarantee registration information is stored in the guarantee registration database 310 is displayed.

Further, in the display column 112, along with each business partner name, information indicating the guarantee contents for each business partner and transaction status information indicating the transaction status between the tenant and the business partner are displayed.

In FIG. 11A, the display column 112 includes display columns 112-1, 112-2, 112-3, etc., and in each display column, along with the business partner name, information indicating the guarantee contents for each business partner, and a tenant. The amount of money in the transaction with the business partner and the presence or absence of payment delay are displayed. In other words, the transaction status information for each business partner is displayed in the display fields 112-1, 112-2, 112-3. Further, in the display field 112-4, the display component 115 is displayed instead of the business partner name.

In the display column 113, a list of transaction status information for each business partner is displayed. Further, in the list displayed in the display column 113, the display component 114 for requesting the execution of the performance of the obligation is displayed for the business partner who has a payment delay.

In the example of FIG. 11A, the display column 113 is supposed to display a list of guarantee registration information of the business partner, but the present invention is not limited to this. For example, the display field 113 may display a list of invoice information of each business partner.

Specifically, for example, in the display column 113, a list of invoice information with each business partner as a billing destination may be displayed.

FIG. 11B shows another example of the display field 113. FIG. 11B is a diagram showing another display example of the display column.

The display field 113A shown in FIG. 11B displays a list of invoice information of the invoice issued to each business partner whose transaction status information is displayed in the display field 112.

Specifically, in the display column 113A, the invoice destination, the invoice amount, the payment deadline date (see FIG. 4) and the like are displayed as the invoice information of each business partner.

Further, the display column 113A determines that the invoice information is overdue when the current date exceeds the payment deadline and the payment status of the invoice information is "unpaid", and the item "overdue". "Excess" is displayed as the value of. Further, in the display column 113A, the display component 114A is displayed in association with the invoice information in which the value of the item "overdue" is "exceeded". The display component 114A is a display component for instructing the execution of the performance of the obligation.

Further, the display field 113 may be blank, for example, when a business partner who uses the credit guarantee service is not registered. Further, in that case, only the display component 112-5 may be displayed in the display field 112.

When the display component 115 is selected on the screen 111, the transaction management device 300 of the present embodiment accepts it as a new business partner registration operation, and displays the terminal device 400 from the home screen to the business partner selection screen. Make a transition.

FIG. 12 is a diagram showing an example of a business partner selection screen. The screen 121 shown in FIG. 12 is an example of a business partner selection screen displayed on the terminal device 400 in step S1008 of FIG.

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

The screen 121 displays a list of business partner names that are not registered as business partners who use the credit guarantee service from the list of business partners acquired in step S1006 of FIG.

When the customer name is selected on the screen 121, the transaction management device 300 performs the processes after step S1010 in FIG. 10 to shift the display of the terminal device 400 from the screen 121 to the registration screen described later.

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

The screen 131 has a display field 132 and display components 133 and 134. In the display field 132, the guarantee registration information in which the customer information set in step S1013 of FIG. 10 and the information specified from the invoice information in step S1016 are associated with each other is displayed.

In the example of FIG. 13, in the display field 132, the guarantee registration information includes the customer information including the company name, the address, etc., which is the customer name, the transaction start date specified from the claim information, the presence or absence of payment delay, and the like. Is displayed as.

That is, the guarantee registration information of the present embodiment includes information extracted from the supplier information acquired from the form management device 200 and the invoice information acquired from the form management device 200 based on predetermined conditions and the like. And are included.

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 guarantee registration information in the guarantee registration database 310 and requesting (applying) the credit guarantee management system 500 to examine the guarantee contents.

In the present embodiment, when the display component 114 is selected on the transaction management device 300 and the screen 131, a process of requesting the credit guarantee management system 500 to examine the guarantee contents is performed.

FIG. 14 is a third sequence diagram illustrating 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 contents.

In the transaction management system 100, when the terminal device 400 receives the operation of selecting the request (application) for the examination of the guarantee contents (the operation of selecting the display component 134) by the tenant (step S1401), the transaction management device 300 is contacted. Then, the application request is transmitted (step S1402).

In response to this request, the transaction management device 300 stores the application status in the guarantee registration information stored in the guarantee registration database 310 by the registration unit 333 (step S1403).

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 customer name in the guarantee registration database 310. At this time, the transaction management device 300 may send a notification indicating a request for examination to the terminal device 700 of the credit guarantee management system 500.

When the terminal device 700 receives an operation instructing the display of application information in the credit guarantee management system 500 (step S or 1404), the terminal device 700 transmits this request to the transaction management device 300 (step S1405). The operation of the terminal device 700 is performed by, for example, the administrator of the credit guarantee management system 500.

Subsequently, the transaction management device 300 generates screen data for displaying the list of application information by the screen output unit 336, and causes the terminal device 700 to display the list screen of the application information (step S1406). Details of the application information list screen will be described later.

Subsequently, the terminal device 700 accepts the input of the guarantee contents to the applied business partner (step S1407). Subsequently, the terminal device 700 accepts an operation of registering the input information indicating the guarantee content (step S1408).

Upon receiving this operation, the terminal device 700 transmits the information indicating the guarantee content and the registration request of the emotional driver's cab 10 to the transaction management device 300 (step S1409).

The transaction management device 300 receives this request by the input receiving unit 331, and the registration unit 333 stores the information indicating the guarantee content in the guarantee registration database 310 (step S1410). At this time, the registration unit 333 stores in the guarantee registration database 310 the business partner for whom the examination of the guarantee content has been requested and the information indicating the guarantee content in association with each other in the guarantee registration database 310.

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

The display field 152 and the display components 153, 154, and 155 are displayed on the screen 151. In the display field 152, the guarantee registration information stored in the guarantee registration database 310 is displayed. Further, in the display column 152, among the warranty registration information, the display component 156 associated with the warranty registration information whose value of the item "application status" is "under examination" is displayed. The display component 156 is a display component for transitioning the screen 151 to the input screen of the warranty content.

The guarantee registration information in which the value of the item "application status" is "under examination" is the guarantee registration information for which the input of the information indicating the guarantee content has not been completed. Specifically, for example, it is guarantee registration information that does not include at least one value of the item "guarantee upper limit amount" and the item "guarantee period".

The display component 153 is a display component for displaying all the warranty registration information stored in the warranty registration database 310 in the display column 152. When the display component 153 is operated, the display column shows the warranty registration information in which the value of the item "application status" is "under examination" and the warranty registration information in which the value of the item "application status" is "examined". Is displayed.

The display component 154 is a display component for displaying only the warranty registration information in which the value of the item "application status" is "under examination" among the warranty registration information stored in the warranty registration database 310.

The display component 155 is a display component for switching between a screen for listing application information and a screen for fulfilling an obligation, which will be described later.

When the display component 156 is operated on the screen 151, the display of the terminal device 700 transitions from the screen 151 to the input screen of the guarantee content described later.

FIG. 16 is a diagram showing an example of a guarantee content input screen. The screen 161 shown in FIG. 16 is an example of the screen displayed on the terminal device 700 in step S1407 of FIG.

Display columns 162, 163 and display parts 164, 165 are displayed on the screen 161. Business partner information is displayed in the display field 162, and an input field for guarantee contents is displayed in the display field 16.

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

In the terminal device 700 of the present embodiment, when the information indicating the guarantee content is input to the display field 163 in the terminal device 700 and the display component 165 is operated, the information indicating the guarantee content is sent to the transaction management device 300. Send a registration request.

In the example of FIG. 16, the registration request of the guarantee registration information of the business partner name “Company A” is transmitted to the transaction management device 300. The guarantee registration information of company A includes the business partner information of company A, the transaction start date specified from the invoice information, the presence or absence of payment delay, the maximum guarantee amount, and the guarantee period.

In response to this registration request, the transaction management device 300 associates the received guarantee content information with the supplier information displayed in the display field 162 of the screen 161 by the registration unit 333 in the guarantee registration database 310. Register (store).

The guarantee registration information stored in the guarantee registration database 310 becomes information including the business partner information and the information indicating the guarantee contents at this stage.

In the present embodiment, information (examination result) indicating the guarantee contents of the business partner is received from the credit guarantee management system 500 via the network, but the present invention is not limited to this. The information indicating the guarantee content may be directly input to the transaction management device 300 by, for example, the manager of the credit guarantee management system 500. In this case, the screen 151 shown in FIG. 15 and the screen 161 shown in the figure setting storage unit 16 may be displayed on a display device such as a display connected to the transaction management device 300.

Next, with reference to FIG. 17, the operation of the transaction management system 100 when requesting a guarantee by the credit guarantee service for the default of the debt will be described. FIG. 17 is a fourth sequence diagram illustrating the operation of the information processing system.

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

Subsequently, the transaction management device 300 identifies one of the business partners whose tenant is registered as a business partner who uses the credit guarantee service to the form management device 200 by the information acquisition unit 332. A request for acquisition of the invoice information of this business partner is transmitted (step S1703).

In response to this acquisition 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 the specified business partner to the transaction management device 300.

When the transaction management device 300 receives the invoice information of the specified business partner, the risk determination unit 335 obtains an index indicating the risk in the transaction between the business partner and the tenant (step S1705). In other words, the transaction management device 300 derives information indicating the status of transactions between the tenant and the business partner by the risk determination unit 335. Details of the process of step S1705 will be described later.

The transaction management device 300 performs the processes from step S1703 to step S1705 for all the business partners registered as business partners who use the credit guarantee service, and the screen output unit 336 displays the home screen including the result. To generate screen data for (step S1706).

Subsequently, 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).

Next, the terminal device 400 accepts the selection of the business partner on the home screen (step S1708). When the terminal device 400 accepts the selection of the business partner, the terminal device 400 displays a list of invoice information of the selected business partner information on the home screen (step S1709).

Subsequently, when the terminal device 400 receives an operation instructing the performance of the debt from the tenant (step S1710), the terminal device 400 transmits a demand for performance of the debt to the transaction management device 300 (step S1711).

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

Specifically, the performance management unit 334 obtains the tenant name, the selected business partner name, the billing amount for the business partner, the billing date, the payment deadline, the guarantee maximum amount, and the guarantee period from the guarantee registration database 310, and fulfills the guarantee. The performance history information in which the state is being fulfilled may be stored in the performance history database 320 (see FIG. 7).

Upon receiving the performance request, the performance management unit 334 acquires necessary information such as image data of the invoice to be executed from the form management device 200, generates performance history information, and stores the performance history database 320. May be stored.

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

In the transaction management device 300, the screen output unit 336 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). Details of the performance history list screen will be described later.

When the terminal device 700 receives an operation indicating that the obligation has been fulfilled (step S1716), the terminal device 700 transmits a notification indicating that the obligation has been fulfilled to the transaction management device 300 (step S1717). ..

Upon receiving this notification, the transaction management device 300 updates the value of the item "performance status" of the performance history information stored in the performance history database 320 in step S1712 to "performance completed" by the performance management unit 334 (step S1712). 1718).

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

The risk determination unit 335 of the present embodiment calculates the total value of the invoice amount of the 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 description, the total value calculated in step S1801 is referred to as the total value A. The total value A is the amount of money being traded between the tenant and the business partner.

Subsequently, the risk determination unit 335 identifies the invoice information whose payment status is overdue from the invoice information whose payment status is unpaid, and calculates the total value of the total invoice amounts whose payment is overdue. (Step S1802). In the following description, the total value calculated in step S1802 is referred to as the total value B.

Subsequently, the risk determination unit 335 determines whether or not the value of the total value B is larger 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.

In step S1803, when the total value B is 0, that is, when there is no unpaid amount whose payment deadline has passed, the risk determination unit 335 proceeds to step S1806 described later.

In step S1803, when the total value B is larger than 0, that is, when there is an unpaid amount whose payment deadline has been exceeded, the risk determination unit 335 determines whether or not the total value B exceeds the guaranteed upper limit amount ( Step S1804).

That is, the risk determination unit 335 determines whether or not the unpaid amount whose unpaid deadline has passed is the amount that can be fully recovered by the credit guarantee service.

In step S1804, when the total value B exceeds the guaranteed upper limit amount, the risk determination unit 335 determines that the risk in the transaction with this business partner is “high” (step S1805), and ends the process.

If the total value B does not exceed the guaranteed upper limit amount in step S1804, the risk determination unit 335 proceeds to step S1809 described later.

When the total value B is 0 in step S1803, the risk determination unit 335 determines whether or not the total value A is equal to or less than the guaranteed upper limit amount (step S1806).

In step S1806, when the total value A is not equal to or less than the guaranteed upper limit amount, that is, when the total value A exceeds the guaranteed upper limit amount, the risk determination unit 335 determines that the risk in the transaction with this business partner is "medium" ( Step S1807), the process is terminated.

In step S1806, when the total value A is equal to or less than the guaranteed upper limit amount, the risk determination unit 335 determines that the risk in the transaction with the business partner is “low” (step S1808), and ends the process.

Further, in step S1804, when the total value B does not exceed the guaranteed upper limit amount, the risk determination unit 335 determines whether the total value A is equal to or less than the guaranteed upper limit amount (step S1809).

If the total value A is not equal to or less than the guaranteed upper limit amount in step S1809, the process proceeds to step S1805. That is, if there is an unpaid amount whose payment deadline has been exceeded and the amount billed to the business partner exceeds the guarantee upper limit amount, the risk determination unit 335 determines that the risk of the transaction with this business partner is "high". ..

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. That is, if there is an unpaid amount whose payment deadline has been exceeded and the amount billed to the business partner is less than the guaranteed upper limit amount, the risk determination unit 335 determines that the risk of the transaction with this business partner is "medium".

The risk determination unit 335 of the present embodiment performs the process of FIG. 18 for each customer registered as a customer who uses the credit guarantee service, and stores the risk determination result in the determination result table 339.

The risk determination unit 335 of the present embodiment calculates, for example, the ratio of the total value A (total of unpaid billing amounts) to the guaranteed upper limit amount after determining the risk, and stores it in the determination result table 339. You may.

Further, the process shown in FIG. 18 may be executed every time the guarantee registration database 310 is updated, for example, in other words, the process shown in FIG. 18 may be executed every time a transaction is performed between the tenant and the business partner. It may be executed.

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

The value of the item "total value A" indicates the total amount of invoiced amounts whose payment status is unpaid in the transaction between the corresponding business partner and the tenant. The value of the item "ratio" indicates the ratio of the total value A to the guaranteed upper limit amount.

The value of the item "total value B" indicates the total amount of billing amounts for which the payment status has not been paid and the payment deadline has been exceeded in the transaction between the corresponding business partner and the tenant. The value of the item "risk judgment result" indicates an index of risk when the tenant ID and the business partner make a transaction.

In the example of FIG. 19, there are companies B, C, D, E, and F as business partners of the tenant name “X company”. Among them, in Company B, the total value A is less than the guaranteed upper limit amount, and the total value B is 0. Moreover, the ratio is as low as 5%. Therefore, the risk when company X deals with company B is considered to be "low".

Further, in Company C, the total value A is less than the guaranteed upper limit amount, but the total value B exists. Therefore, the risk when company X deals with company C is considered to be "medium". Further, in Company D, both the total value A and the total value B are equal to or more than the guaranteed upper limit amount. Therefore, the risk when company X deals with company D is considered to be "high".

The transaction management device 300 of the present embodiment refers to the determination result table 339 when displaying the home screen on the terminal device 400, and generates screen data for displaying the home screen.

FIG. 20 is a second diagram showing a home screen. In the screen 111A shown in FIG. 20, among the business partners of the tenant "X company", "A company" is newly registered as a business partner who uses the credit guarantee service, and the debt of the D company is fulfilled by the credit guarantee service. It shows the state of being done.

The screen 111A includes display fields 112A and 113A. In the display field 112A, display fields 112-1, 112-2, 112-3, 112-4 and the like are displayed.

In the display column 112-1, the name (customer name) of company B in the determination result table 339, the marker 171 indicating the risk of the transaction with company B, and the transaction status information 172 are displayed.

Specifically, according to the transaction status information of Company B, the maximum amount of guarantee is 10 million yen, the total amount of unpaid bills is 500,000 yen, and there is no unpaid amount that has exceeded the payment deadline (see Fig. 19). ..

Therefore, the marker 171 is a marker indicating that the risk determination result is "low", and the transaction status information 172 includes a guarantee upper limit amount of 10 million yen, a total of unpaid billing amount of 500,000 yen, and an unpaid amount of 0 that has exceeded the payment deadline. Is displayed.

Further, since the upper limit of the guarantee amount is displayed in the display column 112-1, information indicating the guarantee contents of the company B is displayed.

In the display column 112-2, the name of company B (customer name) in the determination result table 339, the marker 173 indicating the risk of the transaction with company C, and the transaction status information 174 are displayed.

Specifically, according to the transaction status information of Company C, the guarantee upper limit amount is 5 million yen, the total unpaid billing amount is 3 million yen, and the unpaid amount overdue is 500,000 yen (). See FIG. 19).

Therefore, the marker 173 is a marker indicating the risk determination result "medium", and as the transaction status information 174, the guarantee upper limit amount is 5 million yen, the total amount of unpaid bills is 3 million yen, and the unpaid amount overdue is 500,000. It is displayed as a circle.

Further, since the upper limit of the guarantee amount is displayed in the display column 112-2, information indicating the guarantee contents of the company C is displayed.

In the display column 112-3, the name of company D (customer name) in the determination result table 339, the marker 175 indicating the risk of the transaction with company D, and the transaction status information 176 are displayed.

Specifically, according to the transaction status information of Company D, the guarantee upper limit amount is 2 million yen, the total unpaid billing amount is 1.5 million yen, and the unpaid amount overdue is 1.5 million yen (). See FIG. 19).

Therefore, the marker 175 is a marker indicating a risk determination result of "high", and as transaction status information 176, a guarantee upper limit amount of 3 million yen, a total of unpaid billing amount of 2 million yen, and an unpaid amount exceeding the payment deadline of 1.5 million yen. It is displayed as a circle.

Further, since the upper limit of the guarantee amount is displayed in the display column 112-3, information indicating the guarantee contents of the company D is displayed.

The markers 171 and 173, 175 may be different from each other in the display mode, and are not limited to the display mode shown in FIG. 20. The markers 171 and 173, 175 may be other than the markers, for example, and may display the risk determination result of the determination result table 339 as it is.

Further, in the present embodiment, the display of the display columns 112 and 113 is updated every time the business partner information is updated.

As described above, in the present embodiment, the tenant is presented with a list of transaction status information indicating the transaction status between the tenant and each business partner. In other words, in this embodiment, the tenant is presented with a list of the tenant's business partner, the amount in transaction (account payable), and the guarantee upper limit amount for each tenant.

Therefore, according to the present embodiment, the tenant can easily grasp the transaction status with each business partner.

Further, in the present embodiment, on the home screen, a list of information indicating the guarantee contents is also displayed for each tenant's business partner. Therefore, according to the present embodiment, it is possible to present the tenant with a list of contents guaranteed by the credit guarantee service for each business partner.

Further, in the present embodiment, when registering a business partner who uses the credit guarantee service in the transaction management device 300, a specific display component in the display field 112 is selected to display a list of business partners, and transactions are performed from this list. You can register a business partner for the credit guarantee service simply by selecting the destination. Therefore, in the present embodiment, in order to use the credit guarantee service, it is possible to reduce the trouble of the tenant manually inputting the information of the business partner, and it is possible to easily register the use of the credit guarantee service for each business partner. can.

Next, the display field 113 will be described. In the display column 113, a list of transaction status information for each business partner is displayed.

Here, when an operation of selecting a display field corresponding to any business partner is performed in the display field 112A, the display field 113 may display a list of invoice information of the selected business partner. ..

In that case, for example, the invoice information whose payment status is unpaid or the invoice information whose payment delay is "Yes" may be highlighted and displayed. Further, the display component 114 may be displayed in the display field 113 in association with the highlighted invoice information.

In this way, by displaying the unpaid invoice information in association with the display component 114 for instructing the fulfillment of the obligation, it is possible to instruct the fulfillment of the obligation for each invoice information.

In the display column 113 shown in FIG. 20, the display component 114 is displayed in association with the company D whose risk determination result is “high”.

When the terminal device 400 receives the operation of selecting the display component 114 on the screen 111A, the terminal device 400 transmits a request for fulfillment of the obligation of the company D to the transaction management device 300.

The transaction management device 300 may send a notification indicating that the performance request of the obligation of the company D has been received to the credit guarantee management system 500.

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

The screen 151A shown in FIG. 21 is displayed on the terminal device 700 in step S1715 of FIG. The screen 151A has a display field 152A, display components 153, 154A, 155A, and 156A.

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

The display component 154A is a display component for displaying only the performance history information whose performance status is “performance in progress” in the display column 152A among the performance history information.

The display component 156A is a display component that is displayed in association with the performance history information whose performance status is “performance in progress”. In the display column 152A, the performance history information of company D and the display component 156A are displayed in association with each other. Upon receiving the operation of selecting the display component 156A, the terminal device 700 may shift the screen 151A to a screen for confirming whether or not the obligation has been fulfilled.

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

When the transaction management device 300 of the present embodiment receives a notification from the credit guarantee management system 500 indicating that the execution of the obligation has been completed, the transaction management device 300 changes the performance state in the performance history database 320 from being performed to being fulfilled. Then, the transaction management device 300 reflects the result of fulfillment or execution of the obligation in the total value A, the total value B, etc. in the guarantee registration database 310.

Next, with reference to FIG. 22, the operation of clearing in the transaction management system 100 of the present embodiment will be described. The application is to receive payment for the invoice amount and change the payment status in the invoice information stored in the invoice database 210 to "paid".

FIG. 22 is a fifth sequence diagram illustrating the operation of the information processing system. In the transaction management system 100 of the present embodiment, the form management device 200 causes the terminal device 400 to display the clearing screen (step S2201). The clearing screen may be periodically displayed from the form management device 200 to the terminal device 400, for example.

Subsequently, the terminal device 400 accepts an operation for setting the invoice information to be applied (step S2202). Subsequently, the terminal device 400 accepts the input of the application information (step S2203). Subsequently, the terminal device 400 accepts a clearing operation instructing the clearing (step S2204).

When the terminal device 400 receives the clearing operation, the terminal device 400 transmits a clearing request for the corresponding invoice information to the form management device 200 (step S2205).

The transaction management device 300 receives the application request and executes the application of the corresponding invoice information (step S2206). Specifically, the form management device 200 identifies the corresponding invoice information in the invoice database 210 by the clearing unit 233, and changes the specified invoice information item "payment status" from unpaid to paid. change. By the above processing, the unpaid application is completed.

In the present embodiment, the invoice has been described as an example of the form, but for example, the quotation may be used as an example of the form. In other words, in the present embodiment, the transaction status information, the information specified from the invoice information, and the information indicating the guarantee contents are included in the guarantee registration information, but the present invention is not limited to this. The information included in the guarantee registration information may include transaction status information, information specified from the invoice information, information specified from the quotation information, and information indicating the guarantee content.

FIG. 23 is a diagram showing an example of a quotation database. The quotation database 210A shown in FIG. 23 stores the quotation information. The quotation information includes the quotation destination, the estimated amount, the estimated date, the scheduled billing date, the scheduled control deadline date, the status, the order date, the billing date, the payment date, the invoice ID, and the like as information items.

The value of the item "Quotation" is the business partner for which the quotation is issued. The value of the item "estimated amount" is the estimated amount stated in the quotation. The value of the item "Quotation date" indicates the date when the quotation was issued. The value of the item "Scheduled invoice date" indicates the scheduled date for issuing the invoice. The value of the item "Scheduled payment deadline" indicates the scheduled payment deadline for the billed amount.

The value of the item "status" indicates the status of the transaction. The value of the item "Order date" indicates the date when the order was received for the quotation. The value of the item "Invoice date" indicates the date when the invoice corresponding to the quotation was issued. The value of the item "Deposit Date" indicates the date when the invoiced amount was deposited. The value of the item "invoice ID" indicates identification information for identifying the invoice corresponding to the quotation.

In the present embodiment, for example, the quotation database 210A may be referred to when the risk determination unit 335 determines the risk.

Hereinafter, a case where the risk determination unit 335 determines the risk using the invoice information and the quotation information will be described with reference to FIG. 24. FIG. 24 is a second flowchart illustrating the processing of the risk determination unit.

In the example of FIG. 24, the risk determination unit 335 calculates the total value of the unpaid billing amount and the estimated amount multiplied by the order rate for each tenant's business partner, and sets the total value as A'(step). S2401).

The order rate indicates the ratio of the number of records of the quotation information in which the value of the item "order date" is input to the number of records of the quotation information of the business partner in the quotation database 210A.

For example, when the business partner is company A, the number of records of the quotation information stored in the quotation database 210A is four (see FIG. 23). In these four quotation information, the number of records of the quotation information in which the value of the item "order date" indicating that the order of the quotation content is actually received is input is 0.

Therefore, in the case of Company A, the amount obtained by multiplying the estimated amount by the order rate is 0 yen, and the total value A'is the same as the total value A of the unpaid invoice amounts.

The processing from step S2402 to step S2409 in FIG. 24 is the same as the processing from step S1802 to step S1809 in FIG. 18 except that the total value A is the total value A', and thus the description thereof will be omitted.

As described above, according to the present embodiment, it is possible to present a list of information indicating the guarantee contents of the business partner to the tenant who is the user of the transaction management system 100 including the transaction management device 300.

In the present embodiment, a part of the invoice information acquired by the form recognition is included in a part of the guarantee registration information, but the guarantee registration information includes the information acquired by the form recognition. It does not have to be.

Specifically, for example, a part of the invoice information included in the warranty registration information may be separately acquired from an apparatus other than the form management apparatus 200.

Each function of the embodiment described above can be realized by one or more processing circuits. Here, the "processing circuit" as used herein is a processor programmed to perform each function by software, such as a processor implemented by an electronic circuit, or a processor designed to execute each function described above. It shall include devices such as ASIC (Application Specific Integrated Circuit), DSP (digital signal processor), FPGA (field programmable gate array) and conventional circuit modules.

Further, the device group described in the embodiment is only one of a plurality of computing environments for implementing the embodiment disclosed in the present specification.

In one embodiment, the form management device 200 includes a plurality of computing devices such as a server cluster. The plurality of computing devices are configured to communicate with each other over any type of communication link, including networks, shared memory, and the like, and perform the processes disclosed herein. Similarly, the form management device 200 can include a plurality of computing devices configured to communicate with each other.

Further, the form management device 200 can be configured to share the disclosed processing steps in various combinations. For example, the process executed by the form management device 200 may be executed by another server device. Similarly, the function of the form management device 200 can be executed by another server device. Further, each element of the server device and the other server device may be integrated into one server device, or may be divided into a plurality of devices.

Further, the correspondence table in the specification may be generated by the learning effect of machine learning. Further, by classifying the keywords and account items that can be included in the description of the transaction contents by machine learning, it is not necessary to use the correspondence table.

Here, machine learning is a technique for making a computer acquire learning ability like a human being, and the computer autonomously generates an algorithm necessary for judgment such as data identification from learning data taken in advance. However, it refers to a technology that applies this to new data to make predictions. The learning method for machine learning may be any of supervised learning, unsupervised learning, semi-supervised learning, enhanced learning, and deep learning, and may be a learning method that combines these learning methods, and machine learning. It doesn't matter how you learn for.

Although the present invention has been described above based on each embodiment, the present invention is not limited to the requirements shown in the above embodiments. With respect to these points, the gist of the present invention can be changed to the extent that the gist of the present invention is not impaired, and can be appropriately determined according to the application form thereof.

100 Information processing system 200 Form management device 210 Invoice database 220 Business partner database 230 Form management unit 300 Transaction management device 310 Guarantee registration database 320 Performance history database 330 Transaction management department 331 Input reception department 332 Information acquisition department 333 Registration department 334 Performance management Section 335 Risk Judgment Section 336 Screen Output Section 337 Communication Section 339 Judgment Result Table 400, 700 Terminal Device 500 Credit Guarantee Management System 600 Credit Guarantee Management Device

Japanese Unexamined Patent Publication No. 2020-003960

Claims (12)

A registration unit that stores the customer information indicating the business partner and the information indicating the guarantee contents of the claim against the business partner in the storage unit in association with each other.
An information processing device having a transaction status information indicating a transaction status with the business partner and a screen output unit for displaying information indicating the guarantee content on a display unit for each business partner. The information processing apparatus according to claim 1, wherein the transaction status information includes at least information indicating an amount of money in transaction with the business partner. An information acquisition unit that acquires the business partner information and invoice information regarding the billing to the business partner, and the information acquisition unit.
It has an input reception unit that accepts input of information indicating the guarantee contents, and has.
The registration unit
The information processing apparatus according to claim 2, wherein the guarantee registration information in which the customer information, a part of the information included in the invoice information, and the information indicating the guarantee contents are associated with each other is stored in the storage unit. .. A risk determination unit that identifies the amount of money in the transaction from the invoice information and determines the risk of the transaction with the business partner for each business partner based on the amount of money in the transaction and the information indicating the guarantee content. Have,
The information processing device according to claim 3, wherein the screen output unit displays a list of determination results for each business partner on the display unit. The risk determination unit
The risk is determined based on the guarantee upper limit amount included in the information indicating the guarantee content and the amount being traded with the business partner.
The information processing apparatus according to claim 4, wherein the transaction status information including the guarantee upper limit amount, the amount of money in transaction with the business partner, and the risk determination result is generated and held. The amount of money in transactions with the above-mentioned business partner is
It is the total amount of accounts payable in the amount billed to the business partner.
The risk determination unit
The information processing apparatus according to claim 5, wherein the risk is determined by using the total amount of the unpaid amount and the total amount of the amount of the unpaid amount whose payment deadline has been exceeded. The screen output unit is
The information processing apparatus according to claim 6, which displays a list of the transaction status information for each business partner. The transaction status information is
The information processing apparatus according to claim 6 or 7, which is updated every time the warranty registration information is updated. The information processing device according to any one of claims 3 to 8, wherein the invoice information is acquired by performing form recognition on an invoice issued to the business partner. An information processing method using an information processing device, wherein the information processing device is
The customer information indicating the business partner and the information indicating the guarantee contents of the claim against the business partner are stored in the storage unit in association with each other.
An information processing method for displaying on a display unit transaction status information indicating the status of a transaction with the business partner and information indicating the guarantee content for each business partner. The customer information indicating the business partner and the information indicating the guarantee contents of the claim against the business partner are stored in the storage unit in association with each other.
An information processing program for causing a computer to display transaction status information indicating the status of transactions with the business partner and information indicating the guarantee content on a display unit for each business partner. An information processing system that includes a terminal device and an information processing device.
The information processing device is
A registration unit that stores the customer information indicating the business partner and the information indicating the guarantee contents of the claim against the business partner in the storage unit in association with each other.
Each business partner has transaction status information indicating the status of transactions with the business partner, information indicating the guarantee content, and a screen output unit for outputting to the terminal device.
The terminal device is
An information processing system having a display unit for displaying transaction status information indicating the status of transactions with the business partner and information indicating the guarantee content for each business partner.

Images