Credit management device, credit management method, and credit management program

Abstract

To reduce a burden on credit management operations related to pre-billing.SOLUTION: A credit management device according to the present embodiment comprises: contract registration means that registers, in a storage unit, contract information including an order reception number, a commodity or a service, a billing destination, an order reception date, a sales scheduled date, and a contract amount; pre-billing registration means that registers, in the storage unit, pre-billing information including a billing payment scheduled number, a billing date, a billing destination, an order reception number, and a billing amount, and for the pre-billing information, billing recovery schedule information including a slip number including the billing payment scheduled number, a division in charge, a billing destination, a recovery scheduled date, a recovery scheduled amount, a payment reconciled amount, and a payment reconciled flag indicating whether the payment has been reconciled; and sales input means that, on a sales input screen displayed on a display, automatically extracts, from the storage unit, the contract information and unpaid pre-billing information linked to a designated order reception number and displays the extracted information, and when summing up the sales amount for the contract information, performs reconciliation of the sales amount and the billing amount of the pre-billing information and updates the billing recovery schedule information.SELECTED DRAWING: Figure 2

Description

[Technical field]

[0001] The present invention relates to a claim management device, a claim management method, and a claim management program. [Background technology]

[0002] For example, in project management type business, a deposit for a contract amount may be requested before the completion of the provision of services (hereinafter referred to as "advance billing"). Conventionally, a system related to advance billing is disclosed in, for example, Patent Document 1. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2017-182765 A Summary of the Invention [Problem to be solved by the invention]

[0004] However, Patent Document 1 does not state anything about reducing the burden of claims management work related to advance claims.

[0005] The present invention has been made in consideration of the above, and aims to provide a claim management device, a claim management method, and a claim management program that are capable of reducing the burden of claim management work related to advance billing. [Means for solving the problem]

[0006] In order to solve the above-mentioned problems and achieve the object, the present invention provides a accounts receivable management device having a memory unit and a control unit, wherein the control unit is characterized by comprising: a contract registration means for registering contract information including an order number, a product or service, a billing destination, an order date, a scheduled sales date, and a contract amount in the memory unit; a pre-billing registration means for registering in the memory unit pre-billing information including a scheduled billing payment number, a billing date, a billing destination, an order number, and a billing amount, and billing collection schedule information including a voucher number including the scheduled billing payment number, a responsible department, a billing destination, a scheduled collection date, a scheduled collection amount, an amount that has been reconciled with the payment, and a payment reconciliation flag indicating whether the payment has been reconciled; and a sales input means for automatically extracting and displaying contract information and unpaid pre-billing information linked to a specified order number from the memory unit on a sales input screen displayed on a display unit, and when recording the sales amount for the contract information, reconciling the sales amount with the billing amount of the pre-billing information, and updating the billing collection schedule information.

[0007] According to one aspect of the present invention, the sales input means may register sales information including sales number, order number, product or service, billing destination, sales date, scheduled collection date, and sales amount in the memory unit based on the input contents on the sales input screen.

[0008] According to one aspect of the present invention, the sales input means may update the planned collection amount for the previous invoice that has been cleared to an amount obtained by subtracting the current cleared amount from the planned collection amount for the invoice collection scheduled information, update the payment cleared flag to cleared, add data about the sales information in which the planned collection amount is the sales amount minus the invoice amount, and add data about the sales information in which the updated planned collection amount is the planned collection amount.

[0009] In addition, according to one aspect of the present invention, when updating the billing collection schedule information, the sales input means may generate previous billing reconciliation information including a previous billing reconciliation number, a sales number, a billing amount, and a reconciliation amount, and register the information in the memory unit.

[0010] In addition, in order to solve the above-mentioned problems and achieve the object, the present invention provides a receivables management method to be executed by an information processing device having a control unit and a memory unit, the method comprising: a contract registration process executed by the control unit, for registering contract information including an order number, a product or service, a billing destination, an order date, a scheduled sales date, and a contract amount in the memory unit; a pre-billing registration process for registering in the memory unit pre-billing information including a scheduled billing payment number, a billing date, a billing destination, an order number, and a billing amount, and billing collection schedule information including a voucher number including the scheduled billing payment number, a responsible department, a billing destination, a scheduled collection date, a scheduled collection amount, an amount that has been reconciled with the payment, and a payment reconciliation flag indicating whether the payment has been reconciled; and a sales input process for automatically extracting and displaying contract information and unpaid pre-billing information linked to a specified order number from the memory unit on a sales input screen displayed on a display unit, and, when recording the sales amount for the contract information, reconciling the sales amount and the billing amount of the pre-billing information to update the billing collection schedule information.

[0011] In addition, in order to solve the above-mentioned problems and achieve the object, the present invention is a receivables management program to be executed by an information processing device having a control unit and a memory unit, the control unit executing the following: a contract registration process for registering contract information including an order number, a product or service, a billing destination, an order date, a scheduled sales date, and a contract amount in the memory unit; a pre-billing registration process for registering in the memory unit pre-billing information including a scheduled billing payment number, a billing date, a billing destination, an order number, and a billing amount, and billing collection schedule information including a voucher number including the scheduled billing payment number, a responsible department, a billing destination, a scheduled collection date, a scheduled collection amount, an amount that has been reconciled with the payment, and a payment reconciliation flag indicating whether the payment has been reconciled; and a sales input process for automatically extracting and displaying contract information and unpaid pre-billing information linked to a specified order number from the memory unit on a sales input screen displayed on a display unit, and when recording the sales amount for the contract information, reconciling the sales amount and the billing amount of the pre-billing information, and updating the billing collection schedule information. Effect of the Invention

[0012] According to the present invention, it is possible to reduce the burden of claims management work related to advance billing. [Brief description of the drawings]

[0013] [Figure 1] FIG. 1 is a diagram for explaining an example of journal entry for the settlement process for an advance payment. [Diagram 2] FIG. 2 is a block diagram showing an example of the configuration of the claim management device according to this embodiment. [Diagram 3] FIG. 3 is a diagram showing an ER diagram of the claim management device according to the present embodiment. [Figure 4] FIG. 4 is a flowchart for explaining the overall process flow of the control unit of the claim management device according to the present embodiment. [Diagram 5] FIG. 5 is a diagram showing sample data for explaining a specific example of the processing of the control unit of the claim management device according to the present embodiment. [Figure 6] FIG. 6 is a diagram showing sample data for explaining a specific example of the processing of the control unit of the claim management device according to the present embodiment. [Figure 7] FIG. 7 is a diagram showing sample data for explaining a specific example of the processing of the control unit of the claim management device according to the present embodiment. [Figure 8] FIG. 8 is a diagram showing sample data for explaining a specific example of the processing of the control unit of the claim management device according to the present embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0014] DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS An embodiment of the present invention will be described in detail with reference to the drawings. However, the present invention is not limited to the embodiment.

[0015] [1. Overview] For example, in project management type business, a deposit may be requested before the completion of the provision of services in relation to the contract amount (hereinafter referred to as "advance billing"). In this case, if sales information is registered before the collection of the advance billing due to reasons such as delayed payment from the client, unless the receivable information and advance billing information are properly matched and settled, excessive information on the planned collection date may remain or excessive receivable amounts may be recorded, which may result in double billing to the client or an inappropriate income and expenditure situation for the project.

[0016] Figure 1 is a diagram for explaining an example of journal entry for the settlement process for an advance payment. If the project contract amount = 10,000,000 yen and the advance payment = 1,000,000 yen, the transaction is generally processed using the journal entry shown in Figure 1.

[0017] In Figure 1, when a deposit is made, the debit is cash deposit: ¥1,000,000, and the credit is advance received: ¥1,000,000. When a sale is made, the debit is advance received: ¥1,000,000, accounts receivable: ¥9,000,000, and the credit is sales: ¥10,000,000.

[0018] Since accounting processing for pre-billing work does not occur, it is not possible to register credit information in a manner consistent with accounting information, as with the above-mentioned advance receipts. Therefore, if there is a plan to collect from pre-billing work, it is necessary to record credit taking into account the unpaid pre-billing amount, or to cancel the pre-billing amount and credit separately when the payment is made.

[0019] In this embodiment, the pre-billing information, which does not appear as accounting information when the sales are recorded, and the credit information generated by the sales recording are automatically adjusted to match the amount expected to be received in the future, thereby reducing the load of the additional clearing work described above and reducing the load of the credit management work related to the advance payment. In addition, by performing the clearing appropriately, double billing is prevented.

[0020] The claim management device of this embodiment can be suitably used in, for example, the IT media and construction work industries, and can also be widely applied in other industries.

[0021] In the following explanation, "goods" will be read as "goods or services", and services will also be referred to as "goods".

[0022] [2. Configuration] An example of the configuration of the debt management device according to this embodiment will be described with reference to Fig. 2. Fig. 2 is a block diagram showing an example of the configuration of an information processing device.

[0023] The claim management device 100 is a commercially available desktop personal computer. Note that the claim management device 100 is not limited to a stationary information processing device such as a desktop personal computer, but may be a portable information processing device such as a commercially available notebook personal computer, a PDA (Personal Digital Assistant), a smartphone, or a tablet personal computer.

[0024] The bond management device 100 comprises a control unit 102, a communication interface unit 104, a memory unit 106, and an input / output interface unit 108. Each unit of the bond management device 100 is connected to each other so as to be able to communicate with each other via any communication path.

[0025] The communication interface unit 104 communicatively connects the claim management device 100 to the network 300 via a communication device such as a router and a wired or wireless communication line such as a dedicated line. The communication interface unit 104 has a function of communicating data with other devices via the communication line. Here, the network 300 has a function of connecting the claim management device 100 and the server 200 so that they can communicate with each other, and is, for example, the Internet or a LAN (Local Area Network).

[0026] An input device 112 and an output device 114 are connected to the input / output interface unit 108. The output device 114 may be a monitor (including a home television), a speaker, or a printer. The input device 112 may be a keyboard, a mouse, a microphone, or a monitor that cooperates with a mouse to realize a pointing device function. In the following, the output device 114 may be referred to as the monitor 114, and the input device 112 may be referred to as the keyboard 112 or the mouse 112.

[0027] The storage unit 106 stores various databases, tables, files, etc. The storage unit 106 records computer programs for cooperating with an OS (Operating System) to give instructions to a CPU (Central Processing Unit) to perform various processes. For example, memory devices such as RAM (Random Access Memory) and ROM (Read Only Memory), fixed disk devices such as hard disks, flexible disks, and optical disks can be used as the storage unit 106. The storage unit 106 includes a data table 106a.

[0028] The data table 106a is a file for storing various data such as contract information (contract header information, contract detail information), previous billing information, billing collection schedule information, sales information (sales header information, sales detail information), previous billing reconciliation information, etc. Figure 3 shows an ER diagram of contract information (contract header information, contract detail information), previous billing information, billing collection schedule information, sales information (sales header information, sales detail information), and previous billing reconciliation information.

[0029] Contract information may be composed of contract header information and contract detail information. Contract header information may include the order number, contract name, department in charge, billing destination, order date, expected sales date, and contract amount, as shown in Figure 3. Contract detail information may include the order number, order line number, product name, quantity, unit price, and contract detail amount, as shown in Figure 3.

[0030] As shown in FIG. 3, the pre-billing information may include the billing payment schedule number, department in charge, billing date, billing destination, order number, billing subject, and billing amount.

[0031] As shown in FIG. 3, the billing collection schedule information may include the invoice number, responsible department, billing destination, order number, order line number, scheduled collection date, scheduled collection amount, reconciled amount, and reconciled flag.

[0032] The sales information may include sales header information and sales detail information. The sales header information may include sales number, order number, responsible department, billing destination, sales date, expected collection date, and sales amount, as shown in Fig. 3. The sales detail information may include sales number, sales line number, order number, order line number, product name, quantity, unit price, and detailed sales amount, as shown in Fig. 3.

[0033] The previous invoice reconciliation information may include the invoice payment reconciliation number, the sales amount, the invoice amount, and the reconciliation amount, as shown in FIG.

[0034] Returning to Fig. 2, the control unit 102 is a CPU or the like that performs overall control of the claim management device 100. The control unit 102 has an internal memory for storing control programs such as an OS, programs that define various processing procedures, and required data, and executes various information processing based on these stored programs. The control unit 102 conceptually includes a contract registration unit 102a, a pre-billing registration unit 102b, a sales input unit 102c, and a screen display control unit 102d.

[0035] The contract registration unit 102a registers contract information (contract header information, contract details information) in the data table 106a in response to, for example, an operator's operation of the input device 112 on an input screen (not shown) displayed on the monitor 114.

[0036] When an advance billing is made for contract information in response to, for example, an operator operating the input device 112 on an input screen (not shown) displayed on the monitor 114, the advance billing registration unit 102b generates advance billing information and registers it in the data table 106a, and also generates billing collection schedule information based on the advance billing information and stores it in the data table 106a.

[0037] The sales input unit 102c, for example, in response to an operator's operation of the input device 112 on a sales input screen (see Figure 7) displayed on the monitor 114, registers sales information (sales header information, sales detail information) in the data table 106a, updates the billing collection schedule information registered in the data table 106a, and registers previous billing settlement information in the data table 106a.

[0038] Specifically, the sales input unit 102c may, for example, automatically extract and display contract information and unpaid pre-billing information linked to a specified order number from the data table 106a in response to an operator's operation of the input device 112 on a sales input screen (see Figure 7) displayed on the monitor 114, and when recording the sales amount for the contract information, may cancel the sales amount and the billing amount of the pre-billing information, thereby updating the billing collection schedule information.

[0039] In addition, the sales input unit 102c may register sales information including the sales number, order number, product or service, billing destination, sales date, scheduled collection date, and sales amount in the data table 106a based on the input contents on the sales input screen.

[0040] In addition, the sales input unit 102c may update the planned collection amount for the previous billing that has been cleared to the amount obtained by subtracting the current cleared amount, update the payment cleared flag to cleared, add data about sales information in which the planned collection amount is the amount obtained by subtracting the billing amount from the sales amount, and add data about sales information in which the updated planned collection amount is the planned collection amount.

[0041] Furthermore, when updating the billing collection schedule information, the sales input unit 102c may generate previous billing settlement information including the previous billing settlement number, the sales number, the billing amount, and the settlement amount, and register the information in the data table 106a.

[0042] The screen display control unit 102d controls, for example, the display of various screens (for example, a sales input screen, etc.) displayed on the monitor 114 and the reception of inputs therefor.

[0043] [3. Specific Examples] A specific example of the processing of the claim management device 100 according to this embodiment will be described with reference to FIGS.

[0044] (3-1. Overall processing) Fig. 4 is a diagram showing a flow for explaining the overall processing flow of the control unit 102 of the claim management apparatus 100 according to this embodiment. The overall processing flow of the claim management apparatus 100 according to this embodiment will be described with reference to Fig. 4.

[0045] 4, the contract registration unit 102a executes a contract information registration process (step S1). Specifically, in the contract information registration process, the contract registration unit 102a registers contract information (contract header information, contract detail information) in the data table 106a in response to, for example, an operator's operation of the input device 112 on an input screen (not shown) displayed on the monitor 114.

[0046] The pre-billing registration unit 102b executes a pre-billing information registration process (step S2). Specifically, when a pre-billing is performed for the contract information in response to an operator's operation of the input device 112 on an input screen (not shown) displayed on the monitor 114, the pre-billing registration unit 102b generates pre-billing information and registers it in the data table 106a, and also generates billing collection schedule information based on the pre-billing information and stores it in the data table 106a.

[0047] The sales input unit 102c executes a sales information registration process (step S3). Specifically, in the sales information registration process, the sales input unit 102c automatically extracts and displays contract information and unpaid pre-billing information linked to a designated order number from the data table 106a in response to an operator's operation of the input device 112 on a sales input screen (see FIG. 7) displayed on the monitor 114, and when recording the sales amount for the contract information, it cancels the sales amount and the billing amount of the pre-billing information, and updates the billing collection schedule information.

[0048] In this case, the sales input unit 102c may register sales information including the sales number, order number, product or service, billing destination, sales date, scheduled collection date, and sales amount in the data table 106a based on the input contents on the sales input screen.

[0049] In addition, the sales input unit 102c may update the planned collection amount for the previous billing that has been cleared to the amount obtained by subtracting the current cleared amount, update the payment cleared flag to cleared, add data about sales information in which the planned collection amount is the amount obtained by subtracting the billing amount from the sales amount, and add data about sales information in which the updated planned collection amount is the planned collection amount.

[0050] Furthermore, when updating the billing collection schedule information, the sales input unit 102c may generate previous billing settlement information including the previous billing settlement number, the sales number, the billing amount, and the settlement amount, and register the information in the data table 106a.

[0051] (3-2. Specific examples) 5 to 8 are diagrams showing sample data for explaining a specific example of the processing by the control unit 102 of the claim management apparatus 100 according to this embodiment. A specific example of the processing by the control unit 102 of the claim management apparatus 100 according to this embodiment will be explained with reference to FIG.

[0052] (S1: Contract information registration process) 5 is a diagram for explaining the contract information registration process. The contract registration unit 102a inputs contract information (contract header information, contract details information) in response to, for example, an operator's operation of the input device 112 on a sales input screen (not shown) displayed on the monitor 114, and stores the information in the data table 106a.

[0053] Figure 5 (A) shows an example of contract header information registration. In the example of contract header information shown in Figure 5 (A), the first line is the order number "JUC001", the contract name "XX system construction contract", the responsible department "Tokyo department", the billing destination "△△ Co., Ltd.", the order date "2020 / 8 / 1", ​​the expected sales date "2020 / 12 / 10", and the contract amount "¥1,500,000", and the second line is the order number "JUC002", the contract name "XX system construction contract", the responsible department "Tokyo department", the billing destination "□□ Co., Ltd.", the order date "2020 / 9 / 1", the expected sales date "2020 / 12 / 20", and the contract amount "¥1,000,000".

[0054] FIG. 5(B) shows an example of registration of contract details information. In the example, the first line has the order number "JUC001", order line number "001", product name "Software development", quantity "1 set", unit price "¥800,000", and contract detail amount "¥800,000". The second line has the order number "JUC001", order line number "002", product name "Software construction", quantity "1 set", unit price "¥700,000", and contract detail amount "¥700,000". The third line has the order number "JUC002", order line number "001", product name "Software development", quantity "1 set", unit price "¥1,000,000", and contract detail amount "¥1,000,000".

[0055] (S2: Pre-billing information registration process) 6 is a diagram for explaining the contract information registration process. For example, in response to an operator's operation of the input device 112 on a pre-billing input screen (not shown) displayed on the monitor 114, when pre-billing is performed for the contract information, the pre-billing registration unit 102b generates pre-billing information and billing collection schedule information for the pre-billing information, and stores them in the data table 106a.

[0056] Fig. 6(A) is a diagram showing an example of pre-billing information registration. In the example of pre-billing information shown in Fig. 6(A), the billing payment number is "SNY001", the department in charge is "Tokyo Department", the billing date is "2020 / 9 / 10", the billing destination is "△△ Co., Ltd.", the order number is "JUC001", the billing subject is "Deposit", and the billing amount is "￥300,000".

[0057] Fig. 6(B) is a diagram showing an example of scheduled billing collection information. In the example of scheduled billing collection information shown in Fig. 6(B), the slip number is "SNY001", the department in charge is "Tokyo Department", the billing destination is "△△ Co., Ltd.", the scheduled collection date is "2020 / 10 / 15", the scheduled collection amount is "¥300,000", the reconciled amount is "¥0", and the reconciled flag is "Not yet".

[0058] (S3: Sales information registration process) 7 and 8 are diagrams for explaining the sales information registration process. For example, in response to the operation of the input device 112 by the operator on the sales input screen (see FIG. 7) displayed on the monitor 114, the sales input unit 102c registers sales information (sales header information, sales detail information) in the data table 106a, updates the billing collection schedule information registered in the data table 106a, and registers previous billing clearing information in the data table 106a.

[0059] 7 is a diagram showing an example of the display of the sales input screen. The sales input screen has a header area for inputting the order number, sales date, billing destination, transaction category, billing destination, department, scheduled collection date, etc., a sales detail area for displaying sales details, a previous invoice clearing area for performing previous invoice clearing, an area for displaying the total sales amount, the total clearing amount, and the total scheduled collection amount, and a register button (not shown). When the register button (not shown) is pressed, sales information (sales header information, sales detail information) is registered in data table 106a, the billing collection schedule information registered in data table 106a is updated, and previous invoice clearing information is registered in data table 106a according to the input (display) contents on the screen.

[0060] In the header area, when an order number is entered, the contract name, billing destination, and department of the contract information linked to the order number are read and automatically displayed, and the operator enters the sales date and expected collection date.

[0061] The sales details area displays the following items: product, sales quantity, unit price, sales amount, and sales recording completion flag. The product name and unit price from the contract information linked to the entered order number are read and automatically displayed. For products for which sales are to be recorded, the operator enters the sales quantity and sets the completion flag to ON. The sales amount is automatically calculated and displayed as the sales quantity x unit price.

[0062] The previous invoice settlement area displays the following items: invoice scheduled payment number, scheduled collection date, invoice amount, collected amount, current settlement amount, and remaining amount after settlement. The data for the invoice scheduled payment number (slip number), scheduled collection date, invoice amount (amount to be collected), and collected amount (paid and settled amount) of the invoice scheduled collection information with the paid settlement flag set to "Not yet", which is the previous invoice information for which settlement has not been completed and payment has not yet been made, linked to the input order number, are read and automatically displayed. The settlement amount is calculated automatically based on the invoice amount of the previous invoice for which settlement has not been completed and the sales amount recorded in the sales statement. Specifically, the "current settlement amount" is automatically calculated and displayed as the smaller of (invoice amount - collected amount) or the sales amount. The "remaining amount after settlement" is automatically calculated and displayed as (invoice amount - collected amount) - current settlement amount.

[0063] In the example shown in Figure 7, the operator enters the order number "JUC001" in the header area, and the contract name "XX System Construction Contract", billing destination "SEI002 △△ Co., Ltd.", and department "BMN001 Tokyo Department" of the contract information linked to the order number "JUC001" are read and displayed. In addition, the operator enters the sales date "2020 / 10 / 11" and the planned collection date "2020 / 11 / 15".

[0064] The sales details area reads out the product name and unit price from the contract information linked to the entered order number "JUC001", and displays the product "SH001 Software Development" and unit price "800,000" for order line number "001" on the first line, and the product "SH008 Hardware Construction" and unit price "¥700,000" for order line number "002" on the second line. The operator enters the sales quantity "1" for the product "SH001 Software Development" on the first line for which sales are recorded, and sets the completion flag to "Done". The sales amount "¥800,000" = sales quantity "1" x unit price "¥800,000" is automatically calculated and displayed.

[0065] In the previous billing clearing area, the following data is read and automatically displayed from the billing collection schedule information with the paid cleared flag set to "Not yet" linked to the input order number "JUC001": billing payment schedule number (slip number) "SNY001", scheduled collection date "2020 / 10 / 15", billing amount (scheduled collection amount) "¥300,000", and collected amount (paid cleared amount) "¥0". Specifically, the previous billing information is obtained using the order number "JUC001" as a key, and the billing collection schedule information is obtained using the billing payment schedule number "SNY001" of the obtained previous billing information as a key.

[0066] "Current application amount" is automatically calculated as the smaller of (billed amount - collected amount) or sales amount, and in this example, "¥300,000" is set because "¥300,000" (billed amount "¥300,000" - collected amount "¥0" = "¥300,000") is less than the sales amount "¥800,000" recorded for the sales on the first line of the sales statement. "Remaining amount after application" is automatically calculated and displayed as (billed amount "¥300,000" - collected amount "¥0") - current application amount "¥300,000" = "¥0".

[0067] The total sales amount is ¥800,000, the total application amount is ¥300,000, and the total amount to be collected is ¥500,000.

[0068] In this example, if the sales amount is 200,000 yen, the amount to be applied this time will be 200,000 yen, and the remaining amount after application will be 100,000 yen.

[0069] In this way, the sales input screen automatically extracts and displays unpaid pre-billing information linked to order information, eliminating the task of searching for information managed in pre-billing operations, which was cited as an issue, and makes it easy to specify the amount to be written off against sales. When sales information is registered, the receivables based on the contract information are recorded, and at the same time, the amount is written off against the pre-billing information, so that the amount to be collected in the future is adjusted to match the amount expected to be collected.

[0070] Figure 8 (A) is a diagram showing an example of sales header information registration. The example of sales header information shown in Figure 8 (A) is sales number "URI001", order number "JUC001", responsible department "Tokyo Department", billing destination "△△ Co., Ltd.", sales date "2020 / 10 / 11", expected collection date "2020 / 11 / 15", and sales amount "800,000 yen". Sales numbers are automatically assigned at the time of registration.

[0071] Fig. 8(B) is a diagram showing an example of sales statement information registration. In the example of sales statement information shown in Fig. 8(B), the first line contains sales number "URI001", sales line number "001", order number "JUC001", order line number "001", product name "software development", quantity "1 set", unit price "¥800,000", and detailed sales amount "¥800,000", and the sale is complete.

[0072] The second line contains the sales number "URI001", sales line number "002", order number "JUC001", order line number "002", product name "Software Construction", quantity "0", unit price "¥700,000", and detailed sales amount "¥0", and the sale is incomplete.

[0073] 8(C) is a diagram showing an example of updated billing collection schedule information. The billing collection schedule information created at the time of the previous billing is treated as cleared, and collection schedule information linked to the sales information that inherited the same amount is created separately, and the amount of receivables and the scheduled collection amount are reconciled.

[0074] In the example of the billing collection schedule information shown in Figure 8 (C), for the first line, the billing collection schedule information specified in the sales input where the payment reconciliation has not been completed will have its scheduled collection amount "¥300,000" and the payment reconciliation completion flag "Not yet" updated to "¥0" and "Completed", respectively. The scheduled collection amount will be ¥300,000-¥300,000=0.

[0075] The second line contains the document number "URI001", department "Tokyo Department", billing destination "△△ Co., Ltd.", order number "JUC001", order line number "001", scheduled collection date "2020 / 11 / 15", scheduled collection amount "￥500,000", reconciled payment amount "￥0", and reconciled payment flag "Not yet". Create new scheduled billing collection information that has newly arisen due to the registration of sales information. The scheduled collection amount is ￥800,000 - ￥300,000 = ￥500,000.

[0076] For the third line, the document number is "URI001", department in charge is "Tokyo Department", billing destination is "△△ Co., Ltd.", order number is "JUC001", order line number is "001", scheduled collection date is "2020 / 11 / 15", scheduled collection amount is "￥300,000", reconciled amount is "￥0", and reconciled flag is "Not yet". For the updated collection amount on the first line, create a new scheduled collection amount linked to the sales input, and set it to "￥300,000".

[0077] Figure 8(D) is a diagram showing an example of previous invoice reconciliation information registration. In the example of previous invoice reconciliation information in Figure 8(D), the previous invoice reconciliation number is "MSEIK001," the sales number is "URI001," the invoice number is "SNY001," and the reconciliation amount is "300,000 yen." At the same time as registering the invoice collection schedule information, information on previous invoice slips that have been reconciled with that sales slip is stored. This makes it possible to realize previous invoice remaining management for pre-invoiced data, excluding slips that have actually been paid and, as in this case, slips that have been reconciled with sales.

[0078] As described above, according to this embodiment, the system includes the contract registration unit 102a that registers contract information including order number, product or service, billing destination, order date, scheduled sales date, and contract amount in the storage unit 106, the pre-billing registration unit 102b that registers pre-billing information including scheduled billing payment number, billing date, billing destination, order number, and billing amount, and billing collection schedule information including, for the pre-billing information, a slip number including the scheduled billing payment number, a responsible department, the billing destination, scheduled collection date, scheduled collection amount, the amount already cleared of the payment, and a payment cleared flag indicating whether the payment has been cleared or not, in the storage unit, and the sales input unit 102c that automatically extracts and displays contract information and unpaid pre-billing information linked to a specified order number from the storage unit on a sales input screen displayed on the monitor 114, and when recording the sales amount for the contract information, clears the sales amount and the billing amount of the pre-billing information, and updates the billing collection schedule information, thereby making it possible to reduce the load of the receivables management work related to pre-billing.

[0079] [4. Contribution to the United Nations-led Sustainable Development Goals (SDGs)] This embodiment can contribute to improving business efficiency and promoting appropriate management decisions by companies, thereby contributing to goals 8 and 9 of the SDGs.

[0080] Furthermore, this embodiment can contribute to reducing waste and promoting paperless and electronic systems, thereby contributing to the achievement of SDGs Goals 12, 13, and 15.

[0081] Furthermore, this embodiment can contribute to strengthening control and governance, making it possible to contribute to Goal 16 of the SDGs.

[0082] 5. Other embodiments The present invention may be embodied in various different embodiments other than those described above within the scope of the technical concept set forth in the claims.

[0083] For example, among the processes described in the embodiments, all or part of the processes described as being performed automatically can be performed manually, or all or part of the processes described as being performed manually can be performed automatically using known methods.

[0084] In addition, the processing procedures, control procedures, specific names, information including parameters such as registered data and search conditions for each process, screen examples, and database configurations shown in this specification and drawings may be changed as desired unless otherwise specified.

[0085] Furthermore, with regard to the claim management device 100, each of the components shown in the figures is a functional concept, and does not necessarily have to be physically configured as shown in the figures.

[0086] For example, the processing functions of the claim management device 100, particularly the processing functions performed by the control unit, may be realized in whole or in part by a CPU and a program interpreted and executed by the CPU, or may be realized as hardware using wired logic. The program is recorded on a non-transient computer-readable recording medium that includes programmed instructions for causing the information processing device to execute the processes described in this embodiment, and is mechanically read by the claim management device 100 as necessary. That is, a computer program for giving instructions to the CPU in cooperation with the OS and performing various processes is recorded in a storage unit such as a ROM or HDD (Hard Disk Drive). This computer program is executed by being loaded into a RAM, and cooperates with the CPU to form the control unit.

[0087] In addition, this computer program may be stored in an application program server connected to the claim management device 100 via any network, and it is also possible to download all or part of it as necessary.

[0088] In addition, the program for executing the process described in this embodiment may be stored in a non-transient computer-readable recording medium, or may be configured as a program product. Here, the "recording medium" includes any "portable physical medium" such as a memory card, a Universal Serial Bus (USB) memory, a Secure Digital (SD) card, a flexible disk, a magneto-optical disk, a ROM, an Erasable Programmable Read Only Memory (EPROM), an Electrically Erasable and Programmable Read Only Memory (EEPROM (registered trademark)), a Compact Disk Read Only Memory (CD-ROM), a Magneto-Optical disk (MO), a Digital Versatile Disk (DVD), and a Blu-ray (registered trademark) Disc.

[0089] Moreover, a "program" is a data processing method written in any language or description method, and may be in any form, such as source code or binary code. Note that a "program" is not necessarily limited to a single configuration, but also includes a distributed configuration as multiple modules or libraries, and a program that works with a separate program, such as an OS, to achieve its function. Note that the specific configuration and reading procedure for reading a recording medium in each device shown in the embodiments, as well as the installation procedure after reading, may use well-known configurations and procedures.

[0090] The various databases etc. stored in the memory unit are storage means such as memory devices such as RAM and ROM, fixed disk devices such as hard disks, flexible disks, and optical disks, and store various programs, tables, databases, and web page files etc. used for various processes and providing websites.

[0091] The claim management device 100 may be configured as an information processing device such as a known personal computer or workstation, or may be configured as the information processing device to which any peripheral device is connected. The claim management device 100 may be realized by installing software (including programs or data, etc.) that causes the device to realize the processing described in this embodiment.

[0092] Furthermore, the specific form of distribution and integration of the devices is not limited to that shown in the drawings, and all or part of them can be functionally or physically distributed and integrated in any unit according to various additions or functional loads. In other words, the above-mentioned embodiments can be implemented in any combination, or the embodiments can be implemented selectively. [Industrial Applicability]

[0093] The present invention is useful in industries such as IT media and construction work. [Explanation of symbols]

[0094] 100 Credit management device 102 Control section 102a Contract Registration Department 102b Pre-claim registration section 102c Sales input section 102d Screen display control unit 104 Communication interface section 106 Storage section 106a Data Table 108 Input / Output Interface Section 112 Input Devices 114 Output Device 200 Servers 300 Network

Claims

1. A claim management device including a memory unit and a control unit, The control unit is a contract registration means for registering contract information including an order number, a product or service, a billing destination, an order date, a scheduled sales date, and a contract amount in the storage unit; a pre-billing registration means for registering in the storage unit pre-billing information including a billing payment schedule number, a billing date, a billing destination, an order number, and a billing amount, and billing collection schedule information including a slip number including the billing payment schedule number, a responsible department, a billing destination, a scheduled collection date, a scheduled collection amount, a payment reconciliation completion flag indicating whether the payment has been reconciled or not for the pre-billing information; a sales input means for automatically extracting and displaying from the storage unit, on a sales input screen for inputting sales information and clearing unpaid prior invoice information, the contract information and the unpaid prior invoice information linked to a designated order number and linked to a scheduled invoice payment number of the scheduled invoice collection information with a cleared payment flag of "unpaid", and for clearing the sales amount and the billing amount of the unpaid prior invoice information when recording the sales amount for the contract information, and updating the scheduled invoice collection information; A claim management device comprising:

2. The receivable management device of claim 1, characterized in that the sales input means registers sales information including sales number, order number, product or service, billing destination, sales date, scheduled collection date, and sales amount in the memory unit based on the input contents on the sales input screen.

3. The receivables management device as described in claim 2, characterized in that the sales input means updates the planned collection amount for the previous invoice that has been cleared to the amount obtained by subtracting the current cleared amount from the planned collection amount, updates the payment cleared flag to cleared, adds data about the sales information in which the planned collection amount is the amount obtained by subtracting the invoice amount from the sales amount, and adds data about the sales information in which the updated planned collection amount is the planned collection amount.

4. The receivable management device of claim 3, characterized in that when updating the billing collection schedule information, the sales input means generates previous billing reconciliation information including a previous billing reconciliation number, sales number, billing amount, and reconciliation amount, and registers it in the memory unit.

5. A claim management method to be executed by an information processing device having a control unit and a storage unit, Executed in the control unit, a contract registration step of registering contract information including an order number, a product or service, a billing destination, an order date, a scheduled sales date, and a contract amount in the storage unit; a pre-billing registration process for registering in the storage unit pre-billing information including a billing payment schedule number, a billing date, a billing destination, an order number, and a billing amount, and billing collection schedule information including a slip number including the billing payment schedule number, a responsible department, a billing destination, a scheduled collection date, a scheduled collection amount, a payment cleared amount, and a payment cleared flag indicating whether the payment has been cleared or not for the pre-billing information; a sales input process for automatically extracting and displaying from the storage unit, on a sales input screen for inputting sales information and clearing unpaid prior invoice information, the contract information and the billing payment schedule number of the billing collection schedule information whose paid clearing flag is "unclear" and which are linked to a specified order number, and clearing the sales amount and the billing amount of the unpaid prior invoice information when recording the sales amount for the contract information, and updating the billing collection schedule information; A method for managing claims, comprising:

6. A claim management program to be executed by an information processing device having a control unit and a storage unit, In the control unit, a contract registration step of registering contract information including an order number, a product or service, a billing destination, an order date, a scheduled sales date, and a contract amount in the storage unit; a pre-billing registration process for registering in the storage unit pre-billing information including a billing payment schedule number, a billing date, a billing destination, an order number, and a billing amount, and billing collection schedule information including a slip number including the billing payment schedule number, a responsible department, a billing destination, a scheduled collection date, a scheduled collection amount, a payment cleared amount, and a payment cleared flag indicating whether the payment has been cleared or not for the pre-billing information; a sales input process for automatically extracting and displaying from the storage unit, on a sales input screen for inputting sales information and clearing unpaid prior invoice information, the contract information and the billing payment schedule number of the billing collection schedule information whose paid clearing flag is "unclear" and which are linked to a specified order number, and clearing the sales amount and the billing amount of the unpaid prior invoice information when recording the sales amount for the contract information, and updating the billing collection schedule information; A receivables management program to implement the above.

Images