JP5108404B2 - Payment support system, payment support method, and program - Google Patents

Description

  The present invention relates to a payment support system, a payment support method, and a program.

Payments based on commercial transactions may be made by transferring existing receivables. For example, in the system described in Patent Document 1, a combination of receivables that can be used for payment is extracted in consideration of the market value of the receivables already held.
JP-A-2005-32278

In the conventional system, by paying attention to the market value of the receivable, both the payer and the payee can exchange the receivable fairly.
However, when the payer selects a receivable to be transferred to the recipient for payment, if the receivable has the same market value, it is desirable to transfer the beneficial receivable to the recipient. It has not been considered in the past whether or not it will benefit the recipient.

  The present invention has been made in view of such a background, and a payment support system, a payment support method, and the like that can present a merit brought to the payee by the payer transferring the receivable to the payee, And to provide a program.

The main invention of the present invention for solving the above-mentioned problems is a payment support system, a creditor identification information that is information for identifying a creditor, a debtor identification information that is information for identifying a debtor, and a credit amount A receivable information storage unit for storing receivable information associated with the payer, payer identification information that is information identifying the payer, payee identification information that is information identifying the payee, and payment from the payer to the payee A payment information receiving unit for receiving an amount of money, a first bond information extracting unit that extracts, as the first bond information, the creditor identification information that matches the payer identification information among the bond information, and the bond information A second credit information extracting unit that extracts, as second credit information, the creditor identification information that matches the payee identification information; the debtor identification information of the first credit information; An offsetable credit pair generation unit that generates an offsetable claim pair that is a combination of the first and second claim information that matches the creditor identification information of the claim information of two claims, and constitutes the offsettable claim pair Transferable to generate transferable receivable information, which is information associated with the first receivable information, with the smaller amount of the receivable included in the first and second receivable information as an amount that can be offset by the recipient The amount of payment from the payer to the payee by transferring a claim from the payer to the payee, obtained by selecting one or more of the transferable claim information, A payment method information generating unit that generates payment method information that is information indicating a payment method, and each of the payment method information is transferred according to payment method identification information that is information for identifying each, and the payment method information. Is information relating to the occurrence or split of claims resulting from excess or deficiency of the transfer amount and the payment amount when the claim is transferred according to the payment method information. A payment method information storage unit that stores division generation information as associated information is provided.

  According to the present invention, it is possible to present the merit brought to the payee by the payer transferring the receivable to the payee.

  Hereinafter, a claim management system according to an embodiment of the present invention will be described. The claim management system of this embodiment is a system that manages claims as data electronically.

  FIG. 1 is a schematic diagram of a bond management system of the present embodiment. As shown in the figure, the claim management system of this embodiment includes a claim management server 1 and at least two user devices 5. The bond management server 1 and the user device 5 are connected to each other via a network 9 so as to communicate with each other. The network 9 is constructed by a wired or wireless communication path, for example, the Internet, an intranet, or a LAN (Local Area Network).

  The bond management server 1 is an information processing apparatus that electronically manages bonds, and is, for example, a personal computer or a workstation. As will be described later, the claim management server 1 manages information relating to claims including creditors, debtors, debt amounts, etc. (hereinafter referred to as credit information) in a database.

  The user device 5 is a computer operated by a debtor who can be a debtor or a creditor, and is, for example, a personal computer, a PDA (Personal Digital Assistance), a mobile phone, or the like. The user operates the user device 5 to access the claim management server 1 and registers the claim information in the database. In the present embodiment, it is assumed that all receivables generated between users are registered in the receivable management server 1.

  For example, when the company A delivers the product to the company B, the company B registers the claim information related to the payment obligation in the claim management server 1.

  When the company B pays the company A for payment, it can be repaid by transferring the credit to the other company owned by the company B to the company A instead of payment by cash. For example, when the company B has accounts receivable with respect to the company C, the claim information with the company B as the creditor and the company C as the debtor is registered in the claim management server 1. The company B updates the creditor information so that the creditor of the credit information becomes the company A, thereby transferring the credit to the company A.

  Here, if the amount of debt that Company B has against Company A is different from the amount of receivable that Company B has against Company C, if the amount of debt to Company A is larger, If the amount of receivables against Company C is larger, the receivables to Company C can be split and some of them can be transferred to Company A. . In this way, there are many methods for assigning receivables. Therefore, in the present embodiment, as a merit for the payee company A, it is preferable to transfer what can be offset by the payee company A using the transferred receivable. A presents a claim that can be used for offsetting (hereinafter referred to as an offsettable claim).

  As shown in FIG. 1, the claim management server 1 includes a claim procedure processing unit 11, a payment method extracting unit 12, an offsettable amount calculating unit 13, a fee calculating unit 14, an uncancellable degree calculating unit 15, an information receiving unit 18, and A storage unit 20 is provided, and the storage unit 20 stores a bond information table 21 and a fee information table 22.

  The bond information table 21 stores information (hereinafter referred to as bond information) indicating the contents of the bond. FIG. 2 is a diagram showing a configuration of bond information registered in the bond information table 21. As shown in FIG. 2, the bond information includes a bond ID field 211, a creditor field 212, a debtor field 213, an amount field 214, a due date field 215, and a disclosure field 216.

In the bond ID field 211, identification information of bond information (hereinafter referred to as bond ID) is set.
In the creditor field 212, a creditor name specifying the creditor is set. The creditor name may be the name of the creditor, the name of the corporation, or the user ID assigned to the creditor.
In the debtor field 213, a debtor name that identifies the debtor is set. The name of the debtor may be the name of the debtor or the name of the corporation, or a user ID assigned to the debtor.
In the amount field 214, the amount of receivable is set, and in the due date field 215, the due date of the receivable is set.
In the disclosure field 216, a flag value (hereinafter referred to as a disclosure flag) indicating whether or not the credit information may be disclosed to users other than the creditor and the debtor is set. In the present embodiment, it is assumed that the disclosure flag set in the disclosure field 216 is either “OK” or “NO”.

  In the present embodiment, it is assumed that when a bond is newly created (generated), transferred, or divided, the bond information is registered in the bond information table 21 and a fee is charged to the user. In the present embodiment, it is assumed that the bond is divided into only two.

  The fee information table 22 stores information about fees (hereinafter referred to as fee information). FIG. 3 is a diagram illustrating a configuration example of fee information stored in the fee information table 22. As shown in FIG. 3, the fee information includes a processing field 221 and a fee field 222. In the processing field 221, “occurrence”, “transfer”, “split”, or “disappear” indicating new creation (occurrence), transfer, split, or disappearance (hereinafter referred to as a claim procedure) of a bond is set. A fee is set in the fee field 222. Note that for the credit procedure for which no fee is generated, the fee information may not be registered, or the fee information may be registered with the fee set to “0”.

  The information receiving unit 18 (corresponding to the payment information receiving unit of the present invention) is a command (hereinafter referred to as a bond presentation request) transmitted from the user device 5 and instructing to present a bond usable for payment. ), Commands for instructing new creation, assignment, splitting and extinguishment of receivables (hereinafter referred to as receivable procedure), and instructing the payer to make a payment to the payee A command (hereinafter referred to as a payment procedure request) is received.

  In the bond presentation request, at least a payer name indicating the payer and a payee name indicating the payee are set. When only the payer name and the payee name are set in the claim presentation request, the payer information related to the offsettable claim that can be offset by the payee (hereinafter referred to as the offsettable claim information). ) Is generated and returned to the user device 5. The details of the process of extracting offsettable bond information will be described later.

  In addition, in the claim presentation request, a payment amount, a payment date, and a display format of bond information may be set. In this case, a payment method including one or more bond information necessary to complete the payment is presented. The display format is information for determining the display order of payment methods. In the present embodiment, an amount that can be offset by the recipient (hereinafter referred to as “cancellable amount”), a fee for the procedure for receivables, or a degree of risk that the receivables cannot be recovered (hereinafter referred to as “uncancellable level”). It is assumed to be one of “cancellable amount”, “fee”, and “non-cancellable level”. Details of the processing in response to the claim presentation request will be described later.

  In the claim procedure request, at least information representing the claim procedure (hereinafter referred to as procedure information. In this embodiment, it is assumed that “occurrence”, “transfer”, “split”, or “disappear”) is set.

  In addition, when the procedure information indicates the creation (occurrence) of a bond, the creditor name, the name of the debtor, the amount of claims, the due date, and the disclosure flag are further set in the claim procedure request. When the procedure information indicates assignment of a claim, the claim procedure request is further set with a claim ID and a recipient name indicating the recipient of the assignment destination. When the procedure information indicates the split of the claim, the claim procedure request is further set with the claim ID and the newly created claim amount (hereinafter referred to as the split amount). When the procedure information indicates the disappearance of the claim, the claim ID is further set in the claim procedure request.

  The payment procedure request includes a payment method ID for specifying payment method information to be described later, a payer name indicating the payer, and a payee name indicating the payee.

  The payment method extraction unit 12 (corresponding to the first bond information extraction unit, the second bond information extraction unit, the countervailable bond pair generation unit, and the bond information output unit of the present invention) pays in response to a claim presentation request. Information on receivables that can be transferred from person to recipient (hereinafter referred to as transferable receivables information), and information on receivables that can be used for payment (hereinafter referred to as payment amount and payment date) , Payment method information) is created, and the offsettable bond information or payment method information is transmitted to the user device 5.

  The payment method information includes one or more bond IDs. In addition, in the payment method information, if the total amount of receivables in the receivable information indicated by the receivable ID is less than the payment amount, the procedure information indicating the occurrence of the receivable and the newly generated receivable amount are set. If the amount is larger than the payment amount, procedure information indicating the split of the bond, a bond ID indicating the bond information to be split (hereinafter referred to as split bond ID), and a split amount are set. The payment method information creation process by the payment method extraction unit 12 and details of the payment method information will be described later.

  The bond procedure processing unit 11 performs processing such as registration, update, and deletion of bond information in response to a claim procedure request and a payment procedure request.

  The claim procedure processing unit 11 receives the claim procedure request, and when “occurrence” is set in the received claim procedure request, the claim procedure processing unit 11 receives the creditor name and the debt set in the claim procedure request. Claim information in which the name, claim amount and disclosure flag are set is generated, and the generated claim information is registered in the claim information table 21.

  When “assignment” is set in the claim procedure request, the claim procedure processing unit 11 sets the creditor name of the claim information corresponding to the claim ID set in the claim procedure request in the claim procedure request. Update to payee name.

  When “divided” is set in the claim procedure request, the claim procedure processing unit 11 reads the claim information corresponding to the claim ID set in the claim procedure request from the claim information table 21, Generates receivable information in which the creditor name, the obligor name and the disclosure flag, and the split amount set in the receivable procedure request are set, and the generated receivable information is registered in the receivable information table 21 and the receivable procedure request The split amount is subtracted from the amount of receivable in the receivable information corresponding to the set receivable ID.

  When “Destruction” is set in the claim procedure request, the claim procedure processing unit 11 deletes the claim information corresponding to the claim ID set in the claim procedure request from the claim information table 21.

  When the payment procedure processing unit 11 receives the payment procedure request, the credit procedure name is given to the creditor information indicated by each payment ID included in the payment method information indicated by the payment method ID included in the payment procedure request, The receivables are transferred by updating the payer name included in the payment procedure request to the payee name.

  If the above payment method information includes procedure information indicating the occurrence of a claim, the claim procedure processing unit 11 generates claim information to which a new claim ID is assigned, The payer name included in the payment procedure request is set in the payer field 212, the payer name included in the payment procedure request is set in the debtor field 213, and the payment method information is included in the amount field 214. The credit amount is set, “OK” is set in the disclosure field 216, and registered in the credit information table 21. As a result, a payment obligation for the balance of the payment from the payer to the payee is registered.

  Further, when the payment method information includes procedure information indicating the split of the claim, the claim procedure processing unit 11 receives the claim information corresponding to the split claim ID included in the payment method information (hereinafter, The amount of split included in the payment method information is subtracted from the amount of credit in the split credit information, and new credit information assigned with a new credit ID is generated, and the creditor field 212 of the generated credit information is generated. In the debtor field 213 and the disclosure field 216, the values of the creditor field 212, the debtor field 213 and the disclosure field 216 of the split credit information are set, and in the newly generated credit information amount field 214, a payment method is set. A split amount included in the information is set and registered in the bond information table 21. As described above, the split of the bond is registered.

  The offsettable amount calculation unit 13 obtains the debtor of the transferred receivable when the receivable held by the payer is transferred from the payer (company B) to the payee (company A). An amount that can be offset by the recipient (hereinafter referred to as an offsettable amount) is calculated for (Company C). The amount that can be offset is, for example, when company A has a debt to company C and company B transfers the credit it holds to company C to company A. And the amount of the receivable transferred from the company B to the company A is the smaller amount. Details of the process for calculating the offsettable amount will be described later.

  The fee calculation unit 14 calculates a fee when a bond procedure is performed in accordance with the payment method information created by the payment method extraction unit 12.

  The non-cancellable degree calculating unit 15 calculates a degree (hereinafter referred to as non-cancellable degree) representing a risk when performing the bond procedure according to the payment method information. In the present embodiment, the non-cancellation degree is obtained by subtracting a value obtained by multiplying the number of days from the current date to the repayment date by the offset amount from a value obtained by multiplying the number of days from the current date to the due date by the amount of the receivable. To do.

  For example, when the payer (company B) transfers the first receivable possessed to the third party (company C) to the payee (company A), the company A receives the first receivable transferred from the company B. The risk of not being able to collect the amount of the loan from Company C. This risk is expressed by a value obtained by multiplying the number of days from the current date and time to the due date by the amount of the receivable. Here, when company C has a second receivable for company A, company A uses the first receivable as an automatic receivable and offsets the amount equivalent to the second receivable (cancellable amount). This offset reduces the risk. The degree of reduction is expressed by a value obtained by multiplying the number of days from the current date and time to the due date of the first bond by an offset amount.

  FIG. 4 is a diagram illustrating a hardware configuration of the bond management server 1. As shown in FIG. 4, the bond management server 1 includes a CPU 901, a memory 902, an external storage device 903, an input device 904, an output device 905, and a communication control device 906.

  The input device 904 is, for example, a keyboard or a mouse that accepts data input. The output device 905 is, for example, a display or a printer that outputs data. The communication control device 906 is, for example, an Ethernet (registered trademark) adapter, a modem, a wireless communication device, or the like for connecting to the network 9.

  The external storage device 903 is, for example, a hard disk drive that stores various data and programs. The memory 902 is a main storage device such as a RAM (Random Access Memory). The storage unit 20 of the bond management server 1 described above is realized as a storage area provided by the memory 902 and the external storage device 903.

  The CPU 901 is an arithmetic device that controls the operation of the bond management server 1, and reads the program stored in the external storage device 903 into the memory 902 and executes it, thereby executing the above-described bond procedure processing unit 11 and payment method extraction unit 12. Various functions such as a cancelable amount calculating unit 13, a fee calculating unit 14, an uncancellable degree calculating unit 15, and an information receiving unit 18 are realized. Each functional unit described above may be realized as hardware.

  Next, processing in the bond management system of this embodiment will be described. In the following explanation, regarding payment obligations such as merchandise charges, the paying company (hereinafter referred to as the paying company) is changed from the paying company (hereinafter referred to as the paying company) to the paying company. It is assumed that payment will be made by transferring the receivable. FIG. 5 is a diagram showing the flow of processing in the bond management system.

  When a payment obligation is generated by a commercial transaction, the paying company inputs a payer name indicating the paying company and a payee name indicating the receiving company to the user device 5. The user apparatus 5 transmits a claim presentation request in which the input payer name and payee name are set to the claim management server 1 (S3).

  The claim management server 1 performs processing for extracting offsettable claim information in response to the claim presentation request received from the user device 5 (S4). The details of the process of extracting offsettable bond information will be described later. The receivable management server 1 attaches an offsettable amount to all receivable information set by the paying company as the creditor and transmits it to the user device 5 of the paying company (S5).

  The user device 5 displays a list of the receivable information received from the receivable management server 1 in association with the offsettable amount (S6). The paying company browses the receivable information displayed on the user device 5 and, at this time, if the paying company can select the receivable to be transferred, the payment ID and the receivable ID of the receivable to be transferred are omitted. Then, a claim procedure request in which the name of the recipient representing the recipient company and the procedure information of “assignment” are set is transmitted to the claim management server 1, and the procedure for assigning the claim is performed.

  When the paying company inputs the payment amount, the payment due date, and the display format, the user device 5 sends a claim presentation request in which the payer name, the payee name, the payment amount, the payment due date, and the display format are set to the claim management server 1. (S7).

  The claim management server 1 creates payment method information including a claim that allows the receiving company to receive the payment amount within the due date (S8). The details of the payment method information creation process will be described later.

  Next, the claim management server 1 confirms whether the display format included in the claim presentation request is “cancellable amount”, “fee”, or “non-cancellable level” (S9).

  When the display format is “cancellable amount”, the claim management server 1 calculates the total amount of offsettable amount for the payment method information (S10). The total amount that can be offset is the total amount that can be offset by the receiving company when the claim relating to the claim information included in the payment method information is transferred to the receiving company. The receivable management server 1 transmits the payment method information ordered based on the total offset amount to the user device 5 used by the payment company (S11).

  When the display format is “fee”, the receivable management server 1 calculates the total amount that can be offset for the payment method information, and calculates the fee for the receivable procedure according to the payment method information (S12). Details of the fee calculation process will be described later. The receivable management server 1 orders the payment method information based on the fee, and further orders the payment method of the same fee according to the total amount that can be offset, and transmits it to the user device 5 used by the paying company (S13). ).

  When the display format is “uncancellable”, the bond management server 1 calculates the uncancellable degree for the payment method information (S14). The non-cancellable degree represents the risk that the receiving company will be unable to collect when the receivable included in the payment method information is transferred to the receiving company. In the present embodiment, it is a numerical value obtained by multiplying the amount that cannot be offset (that is, the amount obtained by subtracting the offsettable amount from the amount of receivable) by the number of days from the present to the payment date. The receivable management server 1 transmits the payment method information ordered based on the degree of non-cancellation to the user device 5 used by the payment company (S15).

  Here, the non-cancellation degree will be described with reference to FIGS. FIG. 6 is a diagram for explaining the receivable X1 that the paying company has for the K company and the debt X2 that the receiving company has for the K company. In the example of FIG. 6, X1 is a claim whose amount is 1 million yen and whose due date comes 30 days later, and Y1 is a debt whose amount is 500,000 yen and whose due date comes 45 days later.

  When the paying company transfers the receivable X1 to the receiving company, even if K company defaults and 1 million yen is uncollectible for the period from now to 30 days, the receiving company makes a payment to K company. Since it can be offset with the debt Y1 of 500,000 yen that it has, the substantial loss for the recipient company is suppressed to 500,000 yen. That is, among the receivables X1, 500,000 yen up to 30 days after hitting the area 1 is secured by offsetting.

  On the other hand, when a 1 million yen receivable is transferred from the paying company to the receiving company, the receivable company cannot guarantee that the receivable for the amount of 500,000 yen up to 30 days after hitting area 2 is secured. There is a risk that the receiving company will be unable to collect. This risk is the non-cancellable degree, and the non-cancellable degree is the area of area 2, that is, (100-50) million yen × 30 days = 1500.

  FIG. 7 is a diagram for explaining the receivables that the paying company has for the L company and the debts that the receiving company has for the K company. In this case, the area of area 3 means the degree of non-cancellation, and the degree of non-cancellation is 700,000 yen × (60-20) days = 2800.

  FIG. 8 is a diagram for explaining the receivables that the paying company has for M companies. In the example of FIG. 8, it is assumed that the receiving company does not have debts owed to M company. In this case, the area of area 1 means the degree of non-cancellation, which is 300,000 yen × 40 days = 1,200.

  The user device 5 receives the payment method information transmitted from the bond management server 1, and displays the received payment method information (S16). The payment company confirms the payment method information displayed on the user device 5 and selects the payment method information used for payment to the receiving company. The user apparatus 5 transmits a payment procedure request including the payment method ID indicating the selected payment method information to the bond management server 1 (S17).

  As described above, the claim procedure processing unit 11 of the claim management server 1 performs the claim procedure based on the payment method information such as update and registration of the claim information in response to the payment procedure request (S18).

Details of each process will be described below.
FIG. 9 is a diagram showing the flow of the process of extracting the offsettable bond in step S4 of FIG.

  The payment method extraction unit 12 acquires the payer name and the payee name set in the claim presentation request (S4a).

  The payment method extraction unit 12 reads transferable receivable information (corresponding to the first receivable information of the present invention) in which the creditor field 212 matches the payer name from the receivable information table 21 and sets it as the receivable group 1 ( S4b; first bond information extraction unit). The payment method extraction unit 12 reads from the bond information table 21 bond information (hereinafter referred to as disclosed bond information) in which the obligor field 213 matches the payee name and the disclosure field 216 is set to “OK”. The data is read and set as a credit group 2 (S4c).

  The payment method extraction unit 12 performs transferable receivable information and disclosed receivable information in which the obligor field 213 of the transferable receivable information included in the receivable group 1 and the creditor field 212 of the disclosed receivable information included in the receivable group 2 match. A combination with information (hereinafter referred to as a countervailable credit information pair) is generated (S4d).

  The payment method extraction unit 12 selects an unselected offsettable claim information pair (S4e), and the offsettable amount calculation unit 13 is set in the amount field 214 of the claim information included in the selected offsettable claim information pair. The smaller amount of the receivable is set as an offsettable amount (S4f). The payment method extraction unit 12 executes Steps S4e and S4f for all counterbalanceable bond information pairs (S4g).

  The payment method extraction unit 12 sorts the transferable receivable information included in the receivable group 1 in the order of the corresponding offsettable amounts (S4h), and creates screen data for displaying the sorted first receivable information ( S4i).

As described above, the offsettable claims provided to the user device 5 are extracted.
For example, when “A company” is set as the payer name and “B company” is set as the payee name in the claim presentation request transmitted from the user device 5, the payment method extraction unit 12 displays The first bond information in which “Company A” is set in the creditor field 212 is read from the bond information table 21 shown (S4b), and a bond group 1 (21a) as shown in FIG. 10 is generated. In addition, the payment method extraction unit 12 sets the second item in which “B” is set in the debtor field 213 and “OK” is set in the disclosure field 216 from the bond information table 21 of FIG. The bond information is read (S4c), and a bond group 2 (21b) as shown in FIG. 11 is generated.

  Next, the payment method extraction unit 12 obtains the creditor field 213 of the first claim information included in the claim group 1 shown in FIG. 10 and the creditor of the second claim information included in the claim group 2 shown in FIG. Two offsettable receivables, which are the same as field 212, a pair of receivable information with receivable ID "X1" and receivable information with "Y1", and a receivable information pair with receivable ID "X2" and "Y2" Extract pairs.

  The offsettable amount calculation unit 13 calculates “500,000 yen”, which is the lower amount of claims, as the offsettable amount for the offsettable claims pair with claims ID “X1” and “Y1” (S4f) For the counterbalanceable receivable pair with IDs “X2” and “Y2”, “700,000 yen”, which is the lower amount of the receivable amount, is calculated as an offsettable amount (S4f).

  The payment method extraction unit 12 sorts the transferable receivable information included in the receivables group 1 in the order of the offsettable amount by adding the offsettable amount for the calculated offsettable amount as shown in FIG. Such a list table 21c is generated (S4h).

  FIG. 13 is a diagram showing a flow of the payment method information generation process in step S8 of FIG. An example of a payment method information table 23a that stores payment method information created by the following processing is shown in FIG.

As shown in FIG. 14, the payment method information includes a plurality of bond IDs and information relating to a split or generated loan procedure (hereinafter referred to as split generation information) in association with a payment method ID that is identification information of the payment method information. .) Is included. The number of receivable ID included in the payment method information is the number of transferable debt information after the date from creditor group 1 described above (21a in FIG. 10) was excluded ones after the due date.

  The payment method extraction unit 12 acquires the payer name, the payee name, the payment amount, the payment deadline, and the display format from the claim presentation request (S8a), and the date after the due date from the claim group 1 (21a) in FIG. Excludes the bond information set in the due date field 215 (S8b). The payment method extraction unit 12 includes the creditor field 212 of any of the disclosed receivable information included in the receivable group 2 (21b) shown in FIG. 11 among the transferable receivable information included in the receivable group 1 (21a), and the debt If the recipient field 213 matches, that is, if the claim relating to the transferable claim information is transferred from the payer to the payee, it is determined whether there is any payable information that can be offset by the payee, and the offsettable claim information If there is not (S8c: No), the process is terminated.

  The payment method extraction unit 12 sets the numbers of transferable bond information included in the bond group 1 (21a) to n and k (S8d).

  The payment method extraction unit 12 generates a combination of k pieces of transferable receivable information from the n pieces of transferable receivable information (S8e), and selects one unprocessed combination (S8f).

  The payment method extraction unit 12 obtains an offsettable amount corresponding to each transferable bond information included in the selected combination from the list table 21c in FIG. 12, and any one of the offsettable amounts is greater than 0. Confirm (S8g). If there is no offsettable amount greater than 0, the process proceeds to step S8m.

  If the sum of the amount of receivable information included in the combination is greater than the amount of payment (S8h: Yes), the payment method extraction unit 12 subtracts the amount of payment from the sum of the amounts of receivable. (S8i), a process for creating payment method information related to the bond split is performed (S8j).

FIG. 15 shows a flow of processing for creating payment method information related to bond splitting.
The payment method extraction unit 12 selects one transferable receivable information included in the combination (S9a), and the receivable amount of the selected transferable receivable information is larger than the transfer amount (S9b: Yes). If the total amount of receivables included in the transferable receivable information included in the combination is less than the payment amount (S9c: Yes), the amount obtained by subtracting the transfer amount from the receivable amount is set as the split amount (S9d), and the selected transfer Split generation information is generated by attaching the split amount to the bond ID of the possible bond information (S9e). In the present embodiment, it is assumed that the split occurrence information is generated in the form of “bond ID (split amount)”. The payment method extraction unit 12 generates payment method information in which the receivable IDs of all transferable receivable information included in the combination and the split occurrence information are set, and registers them in the payment method information table 23a (S9f).

  The payment method extraction unit 12 determines whether or not all transferable bond information has been selected (S9g), and if all transferable bond information has not been selected (S9g: No), the process returns to step S9a. As described above, payment method information by division is generated.

  On the other hand, if the total amount of receivables in the combination of k pieces of transferred receivable information is less than or equal to the payment amount (S8h: No), the payment method extraction unit 12 sets the amount obtained by subtracting the total amount from the payment amount as the generated amount (S8k) , Generate the split generation information by attaching the generated amount to the information indicating that the bond will be generated, and generate payment method information that sets the bond ID and split generation information of all transferable loan information included in the combination To the payment method information table 23a (S81). In the present embodiment, the division occurrence information is generated in the form of “occurrence (occurrence amount)”.

  The payment method extraction unit 12 determines whether all the combinations have been processed (S8m), and if not all the combinations have been processed (S8m: No), returns to step S8f. If all combinations have been processed (S8m: Yes), the payment method extraction unit 12 decrements k (S8o) if k is not 1 (S8n: No), and returns to step S8e.

  For example, when the payment amount is “1.25 million yen”, the payment date is “8/2”, and the current date on which the above processing is performed is “5/24”, first, the payment method extraction unit 12 The credit information of the credit ID “X4” whose payment due date comes after the payment due date “8/2” is excluded from the credit group 1 (21a) in FIG. 10 (S8b). That is, the three pieces of receivable information of the receivable IDs “X1”, “X2”, and “X3” remain in the receivable group 1 (21a).

  Next, the payment method extraction unit 12 confirms whether the receivable information remaining in the receivable group 1 (21a) includes reversible receivable information (S8c). In this example, when a claim related to claim information of claim IDs “X1” and “X2” included in claim group 1 (21a) is transferred from paying company “A” to receiving company “B”, B The company can offset the claim related to the claim information of the claim IDs “Y1” and “Y2” included in the claim group 2 (21b).

  The payment method extraction unit 12 substitutes “3”, which is the number of transferable receivable information registered in the receivable group 1 (21a), for the variables n and k (S8d), and from 3 receivables to 3 receivables The combination which takes out is extracted. One type of combination for extracting all of the bond IDs “X1”, “X2” and “X3” is extracted (S8e). The payment method extraction unit 12 selects one combination that has not yet been processed from the extracted combinations, that is, the combination of the bond IDs “X1”, “X2”, and “X3” (S8f).

  Here, when the total amount of receivables in each transferable receivable information constituting the selected combination is compared with the amount of payment, “2 million yen”> “1.25 million yen” is obtained (S8g: Yes). The part 12 sets 2 million yen-12,500,000 yen = 750,000 yen as the transfer amount (S8h).

  The payment method extraction unit 12 sets the payment method information including the division occurrence information of “X1 (25)” only for “X1” whose receivable amount is larger than the transfer amount of 750,000 yen, and the payment method information table 23b shown in FIG. (S9f).

  Since there was only one type of method for extracting three bonds from three bonds, all the combinations were processed as described above (S8m), so the payment method extraction unit 12 subtracts 1 from k, 2 ”(S8o), and a combination of k = 2 pieces of transferable receivable information from n = 3 pieces of transferable receivable information, that is, the receivable IDs are“ X1 ”“ X2 ”,“ X2 ”“ X3 ”,“ Three types of combinations “X3” and “X1” are generated (S8e).

  For example, the payment method extraction unit 12 selects a combination of “X2” and “X3” that has not been processed yet (S8f), and the total amount of receivables “1 million yen” <payment amount “1.25 million yen”. (S8h: No), 1.25 million yen-1 million yen = 250,000 yen is assumed as the generated amount (S8k).

  The payment method extraction unit 12 generates payment method information including the bond IDs “X2” and “X3” and “Occurrence (25)”, and registers the payment method information in the payment method information table 23b shown in FIG. 14 (S81).

FIG. 16 is a diagram showing the flow of the offsettable amount calculation process in step S10 of FIG.
The offsettable amount calculation unit 13 extracts one piece of payment method information from the payment method information table 23a of FIG. 14 (S10a), and sets 0 to the variable Z (S10b). The offsettable amount calculation unit 13 extracts one receivable ID from the payment method information, and acquires transferable receivable information corresponding to the extracted receivable ID from the receivable group 1 (21a) (S10c).

  The offsettable amount calculation unit 13 determines whether or not the transferable receivable information includes the disclosed receivable information having the obligor field 213 that matches the obligor field 212 of the acquired transferable receivable information in the receivable group 2 (21b). It is determined whether or not cancellation is possible (S10d).

  If the transferable receivable information can be canceled (S10d: Yes), the offsettable amount calculating unit 13 acquires the above disclosed receivable information from the receivable group 2 (21b), and enters the amount field 214 of the acquired disclosed receivable information. Let C be the smaller amount between the set amount of receivables and the amount of receivables set in the transferable receivable information amount field 214 (S10e). When the split amount for the credit ID is specified in the split occurrence information included in the payment method information, C is the smaller amount of the split amount and the credit amount of the disclosed credit information. The cancelable amount calculation unit 13 adds C to Z (S10f).

  The cancelable amount calculation unit 13 repeats the processing from step S10c if there is a loan ID that has not been acquired (S10g).

  The offsettable amount calculation unit 13 appends Z calculated by repeating the above processing to the payment method information as an offsetable amount of payment method information, and registers it in the list table 23b as shown in FIG. 17 (S10h). . The list table 23b is generated in the memory 902 or the external storage device 903, for example.

  The offsettable amount calculation unit 13 repeats the processing from step S10a for all payment method information registered in the payment method information table 23a (S10i).

  The payment method extraction unit 12 sorts the payment method information in the order of the offsettable amount (S10j), and generates screen data for displaying the sorted payment method information (S10k). This screen data is transmitted to the user apparatus 5 in step S11 of FIG.

  For example, in step S10a, when the offsettable amount calculation unit 13 reads the payment method information whose payment method ID is “3” from the payment method information table 23a of FIG. Is set (S10b), and the bond information corresponding to the bond ID “X1” is acquired from the bond group 1 (21a) (S10c). The offsettable amount calculation unit 13 determines that the debt with the credit ID “Y1” can be offset in the credit group 2 (21b) (S10d: Yes), and the smaller of the credit amounts of “X1” and “Y1” The amount “500,000 yen” is added to Z, and Z becomes 500,000 yen (S10f).

  Next, the offsettable amount calculation unit 13 obtains receivable information for the receivable ID “X2” (S10b), and the receivable related to the receivable information of “X2” and the receivable information of the receivable ID “Y2” can be offset. (S10d: Yes). Since the split amount of “250,000 yen” for “X2” is specified in the split generation information of the payment method information, the offsettable amount calculating unit 13 determines the split amount of “250,000 yen” and the credit amount of “Y2”. Compared with “1 million yen”, the smaller amount “250,000 yen” is added to Z as C, and Z becomes 750,000 yen (S10f).

  Here, the processing for all bond IDs included in the payment method information is completed (S10g: Yes), Z = 750,000 yen is attached as an offsettable amount of the payment method information, and is recorded in the list table 23a of FIG. S10h) When the above processing is performed for all payment method information (S10i), after sorting in the order of offsettable amount (S10j), screen data for displaying the list table 23a of FIG. 14 is generated (S10h). S10k).

  An example of the screen 31 displayed on the user device 5 based on the screen data is shown in FIG. As shown in FIG. 18, in the payment method display column, a list of obligor names and amounts of receivable information corresponding to the respective receivable IDs included in the payment method information, and any receivable ID is divided and generated information. Is included as “(split)”, and if the split occurrence information indicates that a new claim will be generated and the amount of the claim is set, the amount of the claim and “(new occurrence)” Is displayed.

FIG. 19 is a diagram showing a flow of fee calculation processing in step S12 of FIG.
The fee calculation unit 14 extracts one payment method information from the payment method information table 23a of FIG. 14 (S12a).
The offsettable amount calculation unit 13 calculates the offsettable amount for the payment method information by the processing from step S10b to step 10h of FIG. 16 described above (S12b).

  The fee calculation unit 14 counts the number of receivable IDs included in the payment method information to obtain the number of transfers (S12c), reads the fee corresponding to the transfer division procedure from the fee information table 22, and transfers the fee to the read fee. A value obtained by multiplying the number of times is set as a payment fee (S12d).

  When the split occurrence information included in the payment method information indicates the occurrence of a bond, that is, when “occurrence (occurrence amount)” is set (S12e: Yes), the fee calculation unit 14 generates the occurrence from the split occurrence information. The amount is acquired, and the acquired amount is added to the payment fee (S12f).

  When the split occurrence information included in the payment method information indicates the split of the receivable, that is, when “Receivable ID (split amount)” is set (12g: Yes), the fee calculating unit 14 Is read from the fee information table 22, and the read fee is added to the payment fee (S12h).

  The fee calculation unit 14 attaches the payment fee calculated as described above and the offsettable amount to the payment method information and registers it in the list table 25a as shown in FIG. 20 (S12i). The list table 25a is generated in the memory 902 or the external storage device 903, for example.

  The fee calculation unit 14 and the offsettable amount calculation unit 13 repeat the processing from step S12a for all payment methods (S12j).

  The fee calculation unit 14 sorts the payment method information so that the payment fee is in ascending order and the offsettable amount is in descending order (S12k), and generates screen data for displaying the sorted payment method information (S12l). . This screen data is transmitted to the user apparatus 5 in step S13 of FIG.

  FIG. 21 is a diagram illustrating an example of a screen 32 displayed on the user device 5 based on the above screen data. The information displayed in the payment method column of the screen 32 is the same as that of the screen 31 shown in FIG. 18 described above. However, on the screen 32, the payment methods are summarized for each payment fee. The payment methods are displayed in descending order of the offsettable amount.

  A specific example of the above process will be described. For example, it is assumed that the payment method information whose payment method ID is “5” is extracted from the payment method information table 23a of FIG. This payment method information indicates a method of transferring a claim indicated by the claim information having a claim ID of “X2” or “X3” and generating a new claim with a claim amount of 250,000 yen. Since the receivable IDs included in the payment method information are “X2” and “X3”, the number of transfers is “2”. From the fee information table 22 of FIG. 3, since the fee for transfer is “20 yen”, 2 × 20 (yen) = 40 (yen) is set as the payment fee (S12d).

  Next, since the generated amount of “250,000 yen” is specified in the payment method information (S12e: Yes), the generated fee “30 yen” is obtained from the fee information table 22 of FIG. The payment fee is 40 (yen) +30 (yen) = 70 (yen), and the payment method information accompanied by the payment fee is registered in the list table 25a shown in FIG. (S12k).

FIG. 22 is a diagram showing the flow of the non-cancellation degree calculation process in step S14 of FIG.
The non-cancellable degree calculation unit 15 extracts one piece of payment method information from the payment method information table 23a of FIG. 14 (S14a), and sets the non-cancellable degree Z for the payment method information to 0 (S14b).
The offsettable amount calculation unit 13 calculates the offsettable amount for the payment method information by the processing from step S10b to step 10h of FIG. 16 described above (S14c).
The non-cancellable degree calculation unit 15 acquires one receivable ID included in the payment method information, and extracts receivable information corresponding to the acquired receivable ID from the receivable group 1 (21a) (S14d).

The non-cancellable degree calculation unit 15 calculates the number of days from the current date to the due date, and sets A as a value obtained by multiplying the calculated number of days by the amount of claims in the claim information (S14e). In addition, when the split amount for the bond ID is specified in the split occurrence information included in the payment method information, a value obtained by multiplying the number of days by the split amount is A.
The non-cancellable degree calculation unit 15 calculates the number of days from the current date until the due date of the acquired bond information, and sets B to a value obtained by multiplying the calculated number of days by the amount that can be canceled (S14f).
The non-cancellable degree calculation unit 15 calculates a value obtained by subtracting B from A as the non-cancellable degree C for the bond information (S14g), and adds C to Z (S14h).

  The non-cancellable degree calculation unit 15 performs the above processing for all the receivable IDs included in the payment method information (S14i: Yes), attaches Z to the payment method information, and displays a list as shown in FIG. It is registered in the table 26a (S14j). The list table 26a is generated in the memory 902 or the external storage device 903, for example.

  The non-cancellable degree calculating unit 15 and the cancelable amount calculating unit 13 repeat the processing from step S14a to step S14j for all payment method information (S14k).

  The non-cancellable degree calculation unit 15 sorts the payment method information in ascending order of the non-cancellable degree (S141), and generates screen data for displaying the sorted payment method information (S14m). This screen data is transmitted to the user apparatus 5 in step S13 of FIG.

  An example of the screen 33 displayed on the user device 5 based on the screen data generated as described above is shown in FIG. The information displayed in the payment method column on the screen 33, which is the same as the surface 31 shown in FIG. 18 described above, but on the screen 33, the degree of non-cancellation is displayed. The non-cancellable level represents the risk that the receiving company bears by performing the receivable procedure as shown in the payment method column. Therefore, the paying company can grasp the risk associated with transferring the receivable to the receiving company with reference to the non-offset degree, which is convenient for determining the transferred receivable.

  A specific example of the above process will be described. For example, it is assumed that the current date on which the above processing is performed is “5/24”, and payment method information whose payment method ID is “8” is acquired from the payment method information table 23a of FIG. This payment method information indicates that the receivables with the receivable IDs “X2” and “X3” are transferred, and the receivable with the receivable ID “X1” is divided and transferred to a receivable amount of 250,000 yen. .

The non-cancellable degree calculation unit 15 acquires the bond ID “X1” from the payment method information, and extracts the bond information corresponding to the acquired “X1” from the bond group 1 (21a).
Since the split amount for “X1” is specified in the split occurrence information of the payment method information, the offsettable amount calculation unit 13 determines that the split amount “25 (10,000 yen)” and “X1” “25 (10,000 yen) ) “25 (10,000 yen)”, which is the smaller of the “Y1” claim amount “100 (10,000 yen)” that can be offset against the claim amount, is calculated as an offsettable amount (S14b).

The non-cancellable calculation unit 15 calculates “30 days”, which is the number of days from “5/24” of the current date to the due date “6/23” of the loan information of “X1”, and divides the payment method information Since the split amount for “X1” is specified in the occurrence information, “750” obtained by multiplying the split amount “25 (10,000 yen)” and “30 days” is set as A (S14e).
Further, the non-cancellable degree calculation unit 15 sets “750” obtained by multiplying the offsettable amount “25 (10,000 yen)” by “30 days” as B (S14f), calculates C = A−B, and C = 750-750 = 0 (S14g). The non-cancellable degree calculation unit 15 calculates Z + = C = 0 (S14h).

Next, the non-cancellable degree calculation unit 15 similarly applies A = 700,000 yen × 60 days = 4200, B = 700,000 yen × 20 days = 1400, C = 4200 for the claim information whose claim ID is “X2”. −1400 = 2800 is calculated (S14e to S14g). The non-cancellable degree calculation unit 15 calculates Z + = C = 2800 (S14h).
Next, the non-cancellation degree calculation unit 15 similarly calculates A = 300,000 yen × 40 days = 1200, B = 0, C = 1200−0 = 1200 for the claim information whose claim ID is “X3”. (S14e-S14g). For B, since there is no disclosure receivable information that can be offset, the non-cancellation degree calculation unit 15 sets B to 0.
Here, Z = Z + C = 2800 + 1200 = 4000 (S14g), and the non-cancellation degree calculation unit 15 registers the payment method information accompanied with the non-cancellation degree Z = 4000 in the list table 26a of FIG. 23 (S14j). .

  As described above, according to the claim management system of the present embodiment, it is indicated whether the payee can offset other creditors with respect to the receivable that can be transferred from the payer to the payee. be able to. In other words, the merit of the payee can be presented for the receivable that can be transferred from the payer to the payee. Therefore, it is expected that the relationship between the payer and the payee will be improved by paying in consideration of the merit of the payee. In addition, when the payer is the payee's parent company or subsidiary, or a company of the same company, the receivable is secured by offsetting by transferring the receivable that can be offset by the payer. Therefore, the risk of the entire group can be reduced.

  In addition, according to the claim management system of this embodiment, when transferring a plurality of claims, it is possible to present a combined fee, so that the payer considers the payee's merit and the payer's cost. You can review the payment.

  Further, according to the claim management system of the present embodiment, when transferring a plurality of claims, it is possible to present the risk that the recipient will not be able to collect the transferred claims. Accordingly, the payer can consider the payment method by examining the merits of the payee in more detail.

  The payment method information may be sorted by freely combining the offsettable amount, the fee, and the non-cancellable level into two or three sets. At that time, weighting may be performed.

  Further, in the present embodiment, an inter-company transaction is assumed, but the present invention can also be applied to an exchange between individuals or between an individual and an enterprise.

  In the present embodiment, the non-cancellation level is a value obtained by subtracting the number of days until the due date of the claim multiplied by the amount that can be offset from the number of days until the due date of payment, Although the total area of area 2 and area 3 shown in FIG. 6 is calculated as the degree of non-cancellation, the present invention is not limited to this. . For example, only area 2 in FIG. 6 or only area 3 may be calculated as the degree of non-cancellation.

  Further, in the present embodiment, the bond is divided into only two divisions, but may be divided into three or more divisions. In this case, the fee may be changed according to the number of divisions.

  In the present embodiment, the fee is a fixed amount according to the bond procedure, but may be realized as a function for determining the fee in consideration of other factors.

  Further, although the claim management server 1 of the present embodiment updates and registers the claim information in response to the payment procedure request, various methods are conceivable for the actual procedure. For example, the receivable management server 1 transmits the data created in step S18 to the user device 5 used by the payment company, and the payment company uses the user device 5 to input necessary data. Receive data sent by giving an electronic signature or the like, send data requesting the receiving company to approve the transfer of receivables to the user device 5 used by the receiving company, and receive an approval / non-acceptance response; Thereafter, based on the application, processing such as renewal or registration of bond information may be performed.

  Although the present embodiment has been described above, the above embodiment is intended to facilitate understanding of the present invention and is not intended to limit the present invention. The present invention can be changed and improved without departing from the gist thereof, and the present invention includes equivalents thereof.

It is a schematic diagram of a claim management system of this embodiment. It is a figure which shows the structure of the claim information registered into the claim information table 21. It is a figure which shows the structural example of the fee information memorize | stored in the fee information table. 2 is a diagram showing a hardware configuration of a bond management server 1. FIG. It is a figure which shows the flow of the process in a credit management system. It is a figure explaining the credit X1 which a paying company has with respect to K company, and the debt X2 which a receiving company bears to K company. It is a figure explaining the credit which a paying company has to L company, and the debt which a receiving company bears to K company. It is a figure explaining the claim which a payment company has to M company. It is a figure which shows the flow of the extraction process of the claim | claim which can be canceled in step S4. It is a figure which shows the structural example of the bond group 1. FIG. It is a figure which shows the structural example of the bond group 2. FIG. It is a figure which shows the structure of the list table 21c of bond information. It is a figure which shows the flow of the production | generation process of the payment method information in step S8. It is a figure which shows an example of the payment method information table 23a. It is a figure which shows the flow of the creation process of the payment method information which concerns on bond splitting. It is a figure which shows the flow of a calculation process of the amount which can be canceled in step S10. It is a figure which shows the structural example of the list table 23b of payment method information. It is a figure which shows an example of the screen 31 displayed in the user apparatus. It is a figure which shows the flow of the calculation process of the fee in step S12. It is a figure which shows the structural example of the list table 25a of payment method information. It is a figure which shows an example of the screen 32 displayed on the user apparatus. It is a figure which shows the flow of the cancellation impossible degree calculation process in step S14. It is a figure which shows the structural example of the list table 26a of payment method information. It is a figure which shows an example of the screen 33 displayed on the user apparatus.

Explanation of symbols

DESCRIPTION OF SYMBOLS 1 Claim management server 5 User apparatus 9 Network 11 Claim procedure processing part 12 Payment method extraction part 13 Counterbalance amount calculation part 14 Fee calculation part 15 Uncancellation degree calculation part 18 Information receiving part 20 Storage part 21 Claim information table 22 Fee information Table 211 Claim ID field 212 Creditor field 213 Obligor field 214 Amount field 215 Due date field 216 Disclosure field 221 Processing field 222 Fee field 901 CPU 902 Memory 903 External storage device 904 Input device 905 Output device 906 Communication control device

Claims (13)

A creditor identification information that identifies creditors, a debtor identification information that identifies debtors, and a credit information storage unit that stores credit information associated with credit amounts;
Payer identification information that is information for identifying a payer, payee identification information that is information for identifying a payee, and a payment information reception unit that receives a payment amount from the payer to the payee,
A first receivable information extracting unit that extracts, as the first receivable information, the creditor identifying information that matches the payer identifying information among the receivable information;
A second receivable information extracting unit that extracts, as the second receivable information, the obligor identifying information in which the obligor identifying information matches the recipient identifying information;
Offsetting that generates a counterbalanceable claim pair that is a combination of the first and second claim information in which the obligor identification information of the first claim information matches the creditor identification information of the second claim information Possible bond pair generation department,
Assignment that is information in which the smaller of the amount of receivable included in the first and second receivable information constituting the countervailable receivable pair is associated with the first receivable information as an amount that can be canceled by the recipient Assignable credit information generation unit for generating possible credit information,
Information indicating a payment method of the payment amount from the payer to the payee by transferring a claim from the payer to the payee obtained by selecting one or more of the transferable claim information A payment method information generation unit for generating certain payment method information;
Each of the payment method information is payment method identification information that is information for identifying each of the payment method information, receivable identification information that is information for identifying a receivable to be transferred according to the payment method information, and the receivable is transferred according to the payment method information. A payment method information storage unit that stores information relating to the occurrence of splits and information relating to the occurrence or split of claims arising due to excess or deficiency of the payment amount, as information associated therewith, Payment support system. The payment support system according to claim 1,
A payment support system, comprising: a bond information output unit that outputs the stored payment method information in the order of offsettable amounts that are offset when the payment amount is paid according to the stored payment method information. The payment support system according to claim 1 or 2,
A fee storage unit for storing a first fee for generating the claim, a second fee for transferring the claim, and a third fee for dividing the claim;
For each of the payment method information, when the amount of payment and the amount of payment in the first claim information are the same amount, the second fee is set as a payment fee for the payment, and the amount of payment in the first claim information If the amount of receivable is smaller than the amount of payment, the sum of the first and second fees is the payment fee, and if the amount of receivable of the first receivable information is larger than the amount of payment, the second and third A payment support system, comprising: a payment fee calculation unit that calculates a total of all the fees as the payment fee; and a bond information output unit that outputs the payment method information in the order of the payment fee. The payment support system according to any one of claims 1 to 3,
The claim information includes the due date,
The payment information reception unit receives a payment date of the payment amount,
The first receivable information extracting unit extracts the first receivable information from the receivable information that has the creditor identifying information that matches the payer identifying information and whose due date is before the due date. Extract as
For each of the transferable receivable information included in the payment method information, a value obtained by multiplying the number of days from the current date to the due date by the offsettable amount corresponding to the first receivable information, The non-cancellation degree is a value obtained by subtracting the number of days from the date of payment to the due date of the claim amount of the first claim information, and the payment method corresponding to the calculated non-offset degree A non-cancellable degree generating unit that stores the identification information in association with each other, and a bond information output unit that outputs information in which the non-cancellable degree and the payment method information are associated in order of the total value of the non-cancellable degree A payment support system characterized by that. The payment support system according to any one of claims 1 to 4,
Information indicating that a receivable corresponding to the shortage amount is newly generated when the transferred amount is smaller than the paid amount when the receivable is transferred from the payer to the recipient in accordance with the payment method information. A payment support system comprising a bond information output unit for outputting certain procedure information in association with the payment method information. The payment support system according to any one of claims 1 to 5,
Procedure information which is information indicating that the receivable is divided by the amount when the transferred amount is larger than the paid amount when the receivable is transferred from the payer to the recipient according to the payment method information. A payment support system comprising a bond information output unit that outputs the payment method information in association with the payment method information. Information processing device
Storing creditor identification information, which is information for identifying a creditor, debtor identification information, which is information for identifying a debtor, and claim information associated with a credit amount;
Payer identification information that is information for identifying a payer, payee identification information that is information for identifying a payee, and receiving a payment amount from the payer to the payee;
Extracting the creditor information whose creditor identification information matches the payer identification information as the first creditor information,
Extracting the debtor information whose debtor identification information matches the recipient identification information as second bond information,
Generating a counterbalanceable claim pair that is a combination of the first and second claim information in which the creditor identification information of the first claim information and the creditor identification information of the second claim information match. ,
Assignment that is information in which the smaller of the amount of receivable included in the first and second receivable information constituting the countervailable receivable pair is associated with the first receivable information as an amount that can be canceled by the recipient Generating possible bond information;
Information indicating a payment method of the payment amount from the payer to the payee by transferring a claim from the payer to the payee obtained by selecting one or more of the transferable claim information Generating certain payment method information;
Each of the payment method information is payment method identification information that is information for identifying each of the payment method information, receivable identification information that is information for identifying a receivable to be transferred according to the payment method information, and the receivable is transferred according to the payment method information. A step of storing as a corresponding information the division occurrence information, which is information relating to the occurrence or division of the receivable arising from the excess or deficiency of the payment amount. . The payment support method according to claim 7,
The information processing apparatus is
The payment support method, further comprising the step of: arranging and outputting the stored payment method information in order of offsettable amounts that are offset when the payment amount is paid according to each. The payment support method according to claim 7 or 8,
The information processing apparatus is
Storing a first fee for generating the claim, a second fee for transferring the claim, and a third fee for splitting the claim;
For each of the payment method information, when the amount of payment and the amount of payment in the first claim information are the same amount, the second fee is set as a payment fee for the payment, and the amount of payment in the first claim information If the amount of receivable is smaller than the amount of payment, the sum of the first and second fees is the payment fee, and if the amount of receivable of the first receivable information is larger than the amount of payment, the second and third And a step of outputting the payment method information in the order of the payment fees. It is the payment assistance method as described in any one of Claims 7 thru | or 9, Comprising:
The claim information includes the due date,
The information processing apparatus is
Receiving a payment due date of the payment amount;
Of the claims information, the creditor identification information coincides with the payer identification information, and the payment date is before the payment date is extracted as the first claim information,
For each of the transferable receivable information included in the payment method information, a value obtained by multiplying the number of days from the current date to the due date by the offsettable amount corresponding to the first receivable information, The non-cancellation degree is a value obtained by subtracting the number of days from the date of payment to the due date of the claim amount of the first claim information, and the payment method corresponding to the calculated non-offset degree A payment support method, further comprising the step of: storing information associated with the identification information, and outputting information in which the non-cancellable degree and the payment method information are associated in the order of the total value of the non-cancellable degree . It is the payment assistance method as described in any one of Claims 7 thru | or 10, Comprising:
The information processing apparatus is
Information indicating that a receivable corresponding to the shortage amount is newly generated when the transferred amount is smaller than the paid amount when the receivable is transferred from the payer to the recipient in accordance with the payment method information. A payment support method, further comprising the step of outputting certain procedure information in association with the payment method information. It is the payment assistance method as described in any one of Claims 7 thru | or 11, Comprising:
The information processing apparatus is
Procedure information which is information indicating that the receivable is divided by the amount when the transferred amount is larger than the paid amount when the receivable is transferred from the payer to the recipient according to the payment method information. A payment support method, further comprising the step of outputting the payment method information in association with the payment method information. In the information processing device,
A function for storing creditor identification information, which is information for identifying creditors, debtor identification information, which is information for identifying debtors, and credit information for associating credit amounts,
Payer identification information which is information for identifying a payer, payee identification information which is information for identifying a payee, and a function of accepting a payment amount from the payer to the payee,
A function of extracting the creditor identification information that matches the payer identification information as the first creditor information among the creditor information;
A function of extracting, as the second bond information, the debtor information whose debtor identification information matches the recipient identification information,
A function of generating a counterbalanceable claim pair that is a combination of the first and second claim information in which the debtor identification information of the first claim information matches the creditor identification information of the second claim information. ,
Assignment that is information in which the smaller of the amount of receivable included in the first and second receivable information constituting the countervailable receivable pair is associated with the first receivable information as an amount that can be canceled by the recipient A function to generate possible bond information,
Information indicating a payment method of the payment amount from the payer to the payee by transferring a claim from the payer to the payee obtained by selecting one or more of the transferable claim information The ability to generate certain payment method information,
Each of the payment method information is payment method identification information that is information for identifying each of the payment method information, receivable identification information that is information for identifying a receivable to be transferred according to the payment method information, and the receivable is transferred according to the payment method information. A program for realizing a function of storing as information that associates split occurrence information, which is information related to the occurrence or split of credits arising from excess or deficiency of the payment amount, in the event of a transfer.

Images