Debt management device, debt management method, and debt 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 apparatus, a claim management method, and a claim management program.

Background Art

[0002] For example, in a project management type of business, an advance payment may be billed (hereinafter referred to as "advance billing") before the completion of service provision with respect to the contract amount. Conventionally, as a system related to advance billing, for example, there is Patent Document 1.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] However, Patent Document 1 does not describe anything regarding reducing the load of the claim management business related to advance billing.

[0005] The present invention has been made in view of the above, and an object thereof is to provide a claim management apparatus, a claim management method, and a claim management program capable of reducing the load of the claim management business related to advance billing.

Means for Solving the Problems

[0006] To solve the above-mentioned problems and achieve the objective, the present invention provides a debt management device comprising a storage unit and a control unit, wherein the control unit comprises: contract registration means for registering contract information including order number, goods or services, billing address, order date, planned sales date, and contract amount in the storage unit; pre-billing registration means for registering pre-billing information including planned billing and payment number, billing date, billing address, order number, and billing amount, and planned billing and collection information including a slip number including planned billing and payment number, responsible department, billing address, planned collection date, planned collection amount, amount settled, and a settled flag indicating whether or not payment has been settled; and sales input means for automatically extracting and displaying contract information and unpaid pre-billing information associated with a specified order number from the storage 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 planned billing and collection information.

[0007] Furthermore, 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 address, sales date, scheduled collection date, and sales amount, in the storage unit based on the input content of the sales input screen.

[0008] Furthermore, according to one aspect of the present invention, the sales input means may update the planned collection amount for previous invoices that have been reconciled with the planned collection amount to the amount obtained by subtracting the amount reconciled in the current invoice, update the payment reconciled flag to reconciled, add data for the sales information in which the amount obtained by subtracting the invoice amount from the sales amount is the planned collection amount, and add data for the sales information in which the updated planned collection amount is the planned collection amount.

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

[0010] Furthermore, in order to solve the above-mentioned problems and achieve the objectives, the present invention provides a debt management method to be executed by an information processing device equipped with a control unit and a storage unit, comprising: a contract registration step executed by the control unit to register contract information including order number, goods or services, billing address, order date, planned sales date, and contract amount in the storage unit; a pre-billing registration step to register pre-billing information including planned billing and payment number, billing date, billing address, order number, and billing amount, and planned billing and collection information including a slip number including planned billing and payment number, responsible department, billing address, planned collection date, planned collection amount, amount settled, and a settled flag indicating whether or not payment has been settled, in the storage unit; and a sales input step that, on a sales input screen displayed on a display unit, automatically extracts and displays contract information and unpaid pre-billing information associated with a specified order number from the storage unit, and when recording the sales amount for the contract information, settles the sales amount with the billing amount of the pre-billing information and updates the planned billing and collection information.

[0011] Furthermore, in order to solve the above-mentioned problems and achieve the objectives, the present invention is a debt management program to be executed by an information processing device equipped with a control unit and a storage unit, characterized in that the control unit is used to execute a contract registration step of registering contract information including order number, goods or services, billing address, order date, planned sales date, and contract amount in the storage unit; a pre-billing registration step of registering pre-billing information including pre-billing information including pre-billing payment number, billing date, billing address, order number, and billing amount, and pre-billing collection information including a slip number including pre-billing payment number, responsible department, billing address, planned collection date, planned collection amount, amount settled, and a settled flag indicating whether or not payment has been settled in the storage unit; and a sales input step of automatically extracting and displaying contract information and unpaid pre-billing information associated with a specified order number from the storage unit on a sales input screen displayed on the display unit, and when recording the sales amount for the contract information, settling the sales amount with the billing amount of the pre-billing information and updating the pre-billing collection information. [Effects of the Invention]

[0012] The present invention has the effect of reducing the workload of debt management operations related to prior invoices. [Brief explanation of the drawing]

[0013] [Figure 1] Figure 1 is a diagram illustrating an example of journal entries for the reconciliation process for advance payments. [Figure 2] Figure 2 is a block diagram showing an example of the configuration of the debt management device according to this embodiment. [Figure 3] Figure 3 is a diagram showing the ER diagram of the debt management system according to this embodiment. [Figure 4] Figure 4 is a flowchart illustrating the overall processing flow of the control unit of the debt management device according to this embodiment. [Figure 5] Figure 5 shows sample data to illustrate a specific example of the processing performed by the control unit of the debt management device according to this embodiment. [Figure 6] Figure 6 shows sample data to illustrate a specific example of the processing performed by the control unit of the debt management device according to this embodiment. [Figure 7] Figure 7 shows sample data to illustrate a specific example of the processing performed by the control unit of the debt management device according to this embodiment. [Figure 8] Figure 8 shows sample data to illustrate a specific example of the processing performed by the control unit of the debt management device according to this embodiment. [Modes for carrying out the invention]

[0014] Embodiments of the present invention will be described in detail with reference to the drawings. However, the present invention is not limited to these embodiments.

[0015] [1. Overview] For example, in project management-type operations, an advance payment may be billed (hereinafter referred to as "pre-billing") before the completion of service provision with respect to the contract amount. In this case, if sales information is registered before the recovery of the pre-billing due to reasons such as a delay in payment from the customer, unless the receivables information and the pre-billing information are properly reconciled and offset, excessive recovery schedule information may remain, or an excessive receivables amount may be recorded, leading to double billing to the customer or an inappropriate project balance situation.

[0016] FIG. 1 is a diagram for explaining an example of journal entries for offsetting the advance payment. When the project contract amount = ¥10,000,000 and the advance payment = ¥1,000,000, generally, the processing is performed by the journal entries as shown in FIG. 1.

[0017] In FIG. 1, at the time of receipt of payment, the debit is Cash in Deposit: ¥1,000,000 / the credit is Advance Payment: ¥1,000,000. At the time of sales, the debit is Advance Payment: ¥1,000,000, Accounts Receivable: ¥9,000,000 / the credit is Sales: ¥10,000,000.

[0018] Since the accounting treatment for pre-billing operations does not originally occur, it is not possible to register receivables information in a form that is consistent with the accounting information like the above advance payment. Therefore, when there is a recovery schedule due to pre-billing operations, it is necessary to record the receivables considering the amount of the unbilled pre-billing, or to perform an operation to separately offset the pre-billing amount and the receivables at the time of receipt of payment.

[0019] In the present embodiment, by automatically adjusting the pre-billing information that does not appear as accounting information at the time of sales recording and the receivables information generated by sales recording so as to be consistent with the amount expected to be received in the future, the load of the above additional offsetting operation is reduced, and the load of the receivables management operation related to the advance payment is alleviated. Also, by performing appropriate offsetting, double billing is prevented.

[0020] The receivables management device of the present embodiment can be suitably used, for example, in industries such as IT media and construction work, and is also widely applicable in other industries.

[0021] In the following explanation, "goods" should be read as "goods or services," and services are also described as "goods."

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

[0023] The debt management device 100 is a commercially available desktop personal computer. However, the debt management device 100 is not limited to stationary information processing devices such as desktop personal computers, but may also be portable information processing devices such as commercially available notebook personal computers, PDAs (Personal Digital Assistants), smartphones, or tablet personal computers.

[0024] The debt management device 100 comprises a control unit 102, a communication interface unit 104, a storage unit 106, and an input / output interface unit 108. Each part of the debt management device 100 is connected to communicate via any communication path.

[0025] The communication interface unit 104 connects the debt management device 100 to the network 300 via communication devices such as routers and wired or wireless communication lines such as dedicated lines, enabling communication between the two devices. The communication interface unit 104 also has the function of communicating data with other devices via communication lines. Here, the network 300 has the function of connecting the debt 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] The input / output interface unit 108 is connected to an input device 112 and an output device 114. The output device 114 can be a monitor (including a home television), a speaker, or a printer. The input device 112 can be a keyboard, a mouse, a microphone, or a monitor that works in conjunction with a mouse to provide pointing device functionality. 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 mouse 112.

[0027] The storage unit 106 stores various databases, tables, and files. The storage unit 106 also stores computer programs that work in cooperation with the OS (Operating System) to give instructions to the CPU (Central Processing Unit) to perform various processes. As the storage unit 106, 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. The storage unit 106 includes a data table 106a.

[0028] 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), and previous billing reconciliation information. Figure 3 shows the ER diagram for 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 consist of contract header information and contract detail information. The contract header information may include the order number, contract name, responsible department, billing address, order date, expected sales date, and contract amount, as shown in Figure 3. The 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] The previous billing information may include, as shown in Figure 3, the billing payment schedule number, responsible department, billing date, billing recipient, order number, billing subject, and billing amount.

[0031] As shown in Figure 3, the billing and collection schedule information may include the voucher number, responsible department, billing address, order number, order line number, scheduled collection date, scheduled collection amount, amount reconciled, and payment reconciled flag.

[0032] Sales information may include sales header information and sales detail information. Sales header information may include sales number, order number, department in charge, billing address, sales date, expected collection date, and sales amount, as shown in Figure 3. 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 Figure 3.

[0033] The pre-billing reconciliation information may include the billing and payment reconciliation number, sales amount, billing amount, and reconciliation amount, as shown in Figure 3.

[0034] Returning to Figure 2, the control unit 102 is a CPU or the like that comprehensively controls the debt management device 100. The control unit 102 has internal memory for storing control programs such as the OS, programs that define various processing procedures, and required data, and executes various information processing based on these stored programs. Functionally, the control unit 102 comprises a contract registration unit 102a, a previous 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 detail information) in the data table 106a in response to the operator's operation of the input device 112 on an input screen (not shown) displayed on the monitor 114.

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

[0037] The sales input unit 102c performs operations such as registering sales information (sales header information, sales detail information) in the data table 106a, updating the billing collection schedule information registered in the data table 106a, and registering previous billing reconciliation information in the data table 106a, in response to the operator's operation of the input device 112 on the sales input screen (see Figure 7) displayed on the monitor 114.

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

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

[0040] Furthermore, the sales input unit 102c may update the planned collection amount for previous invoices that have been reconciled with the amount obtained by subtracting the amount reconciled in the current invoice, update the payment reconciled flag to reconciled, add sales information data where the amount obtained by subtracting the invoice amount from the sales amount is the planned collection amount, and add sales information data where the updated planned collection amount is the planned collection amount.

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

[0042] The screen display control unit 102d controls the display of various screens (e.g., sales input screen, etc.) to be displayed on the monitor 114 and the acceptance of their input.

[0043] [3. Specific Examples] A specific example of the processing performed by the debt management device 100 according to this embodiment will be explained with reference to Figures 2 to 8.

[0044] (3-1. Overall Processing) Figure 4 is a flowchart illustrating the overall processing flow of the control unit 102 of the debt management device 100 according to this embodiment. The overall processing flow of the debt management device 100 according to this embodiment will be explained with reference to Figure 4.

[0045] In Figure 4, the contract registration unit 102a executes the 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 the operation of the input device 112 by an operator on an input screen (not shown) displayed on the monitor 114.

[0046] The pre-billing registration unit 102b executes the pre-billing information registration process (step S2). Specifically, for example, when an operator performs an input device 112 on an input screen (not shown) displayed on the monitor 114 to perform a pre-billing on contract information, 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 the 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 previous invoice information associated with a specified order number from the data table 106a in response to the operator's operation of the input device 112 on the sales input screen (see Figure 7) displayed on the monitor 114. When recording the sales amount for the contract information, it reconciles the sales amount with the invoice amount of the previous invoice information and updates the invoice collection schedule information.

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

[0049] Furthermore, the sales input unit 102c may update the planned collection amount for previous invoices that have been reconciled with the amount obtained by subtracting the amount reconciled in the current invoice, update the payment reconciled flag to reconciled, add sales information data where the amount obtained by subtracting the invoice amount from the sales amount is the planned collection amount, and add sales information data where the updated planned collection amount is the planned collection amount.

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

[0051] (3-2. Specific Examples) Figures 5 to 8 are diagrams showing sample data to illustrate a specific example of the processing performed by the control unit 102 of the debt management device 100 according to this embodiment. Referring to Figure 4, a specific example of the processing performed by the control unit 102 of the debt management device 100 according to this embodiment will be explained.

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

[0053] Figure 5(A) shows an example of registered contract header information. In the example of contract header information shown in Figure 5(A), the first line contains the order number "JUC001", contract name "○○ System Construction Contract", responsible department "Tokyo Department", billing address "△△ Corporation", order date "2020 / 8 / 1", ​​expected sales date "2020 / 12 / 10", and contract amount "¥1,500,000". The second line contains the order number "JUC002", contract name "×× System Construction Contract", responsible department "Tokyo Department", billing address "□□ Corporation", order date "2020 / 9 / 1", expected sales date "2020 / 12 / 20", and contract amount "¥1,000,000".

[0054] Figure 5(B) shows an example of registered contract details information. In the example, the first line contains the order number "JUC001", order line number "001", product name "Software Development", quantity "1 set", unit price "¥800,000", and contract item amount "¥800,000". The second line contains the order number "JUC001", order line number "002", product name "Software Construction", quantity "1 set", unit price "¥700,000", and contract item amount "¥700,000". The third line contains the order number "JUC002", order line number "001", product name "Software Development", quantity "1 set", unit price "¥1,000,000", and contract item amount "¥1,000,000".

[0055] (S2: Previous billing information registration process) Figure 6 is a diagram illustrating the contract information registration process. The pre-billing registration unit 102b generates pre-billing information and scheduled billing and collection information for the pre-billing information when an operator performs a pre-billing on an unshown pre-billing input screen displayed on the monitor 114, for example, in response to an operation of the input device 112 by the operator on the pre-billing input screen displayed on the monitor 114, and stores them in the data table 106a.

[0056] Figure 6(A) shows an example of registered prior invoice information. In the example prior invoice information shown in Figure 6(A), the invoice payment schedule number is "SNY001", the department in charge is "Tokyo Department", the invoice date is "2020 / 9 / 10", the billing recipient is "△△ Corporation", the order number is "JUC001", the invoice subject is "Down payment", and the invoice amount is "¥300,000".

[0057] Figure 6(B) shows an example of registered billing collection information. In the example of billing collection information shown in Figure 6(B), the invoice number is "SNY001", the department in charge is "Tokyo Department", the billing recipient is "△△ Corporation", the collection date is "2020 / 10 / 15", the collection amount is "¥300,000", the amount paid is "¥0", and the payment payment flag is "Not yet".

[0058] (S3: Sales information registration process) Figures 7 and 8 are diagrams illustrating the sales information registration process. The sales input unit 102c performs operations such as registering sales information (sales header information, sales detail information) into the data table 106a, updating the billing and collection schedule information registered in the data table 106a, and registering previous billing reconciliation information into the data table 106a, in response to the operator's operation of the input device 112 on the sales input screen (see Figure 7) displayed on the monitor 114.

[0059] Figure 7 shows an example of the sales entry screen. The sales entry screen includes a header area for entering order number, sales date, customer, transaction type, department, expected collection date, etc., a sales details area for displaying sales details, a pre-billing reconciliation area for performing pre-billing reconciliation, an area for displaying total sales amount, total reconciliation amount, and total expected collection amount, and a registration button (not shown). When the registration button (not shown) is pressed, the sales information (sales header information, sales details information) is registered in data table 106a, the expected collection information registered in data table 106a is updated, and the pre-billing reconciliation information is registered in data table 106a, depending on the content entered (displayed) on the screen.

[0060] In the header area, when an order number is entered, the contract name, billing address, and department associated with the order number are automatically retrieved and displayed, and the operator enters the sales date and expected collection date.

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

[0062] The previous invoice reconciliation area displays the following items: invoice payment scheduled number, scheduled collection date, invoice amount, collected amount, current reconciliation amount, and remaining balance after reconciliation. The data for the invoice payment scheduled number (voucher number), scheduled collection date, invoice amount (scheduled collection amount), and collected amount (reconciled amount) of the unpaid previous invoice information (invoices with the "Unreconciled" flag set to "Unreconciled"), which is linked to the entered order number, is read and automatically displayed. The reconciliation amount is automatically calculated based on the invoice amount of the unreconciled previous invoice and the sales amount recorded in the sales details. Specifically, the "current reconciliation amount" is automatically calculated and displayed as the smaller of (invoice amount - collected amount) and the sales amount. The "remaining balance after reconciliation" is automatically calculated and displayed as (invoice amount - collected amount) - current reconciliation amount.

[0063] In the example shown in Figure 7, the operator enters the order number "JUC001" in the header area, and the contract name "○○ System Construction Contract", billing address "SEI002 △△ Corporation", and department "BMN001 Tokyo Department" associated with the order number "JUC001" are read and displayed. The operator also enters the sales date "2020 / 10 / 11" and the collection date "2020 / 11 / 15".

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

[0065] In the pre-billing reconciliation area, the following data is automatically retrieved and displayed: the billing payment schedule number (voucher number) "SNY001", the collection date "2020 / 10 / 15", the billing amount (collection amount) "¥300,000", and the collected amount (reconciled amount) "¥0", all of which are linked to the entered order number "JUC001" and have a payment reconciliation flag of "Not yet paid". Specifically, the pre-billing information is retrieved using the order number "JUC001" as the key, and the billing payment schedule number "SNY001" from the retrieved pre-billing information is retrieved using that as the key.

[0066] The "Amount to be settled this time" is automatically calculated as the smaller of (Invoice amount - Amount collected) and the sales amount. In this example, the invoice amount "¥300,000" - Amount collected "¥0" = "¥300,000" is smaller than the sales amount "¥800,000" recorded as the first line of sales details, so "¥300,000" is set. The "Balance after settlement" is automatically calculated and displayed as (Invoice amount "¥300,000" - Amount collected "¥0") - Amount to be settled this time "¥300,000" = "¥0".

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

[0068] In this example, if the sales amount was 200,000 yen, the amount to be reconciled this time would be 200,000 yen, and the remaining balance after reconciliation would be 100,000 yen.

[0069] In this way, the sales entry screen automatically extracts and displays unpaid pre-billing information linked to order information, eliminating the need to search for information managed in the pre-billing process, which was cited as a challenge, and making it easy to specify the reconciliation amount for sales. When registering sales information, the system records the receivable based on the contract information and simultaneously reconciles it with the pre-billing information to ensure consistency with the expected future collection amount.

[0070] Figure 8(A) shows an example of registered sales header information. In the example sales header information shown in Figure 8(A), the sales number is "URI001", the order number is "JUC001", the department in charge is "Tokyo Department", the billing address is "△△ Corporation", the sales date is "2020 / 10 / 11", the collection date is "2020 / 11 / 15", and the sales amount is "¥800,000". The sales number is automatically assigned at the time of registration.

[0071] Figure 8(B) shows an example of registered sales details information. In the example of sales details information shown in Figure 8(B), the first line contains the 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 sales amount "¥800,000", indicating that the sale is complete.

[0072] The second line shows sales number "URI001", sales line number "002", order number "JUC001", order line number "002", product name "Software Development", quantity "0", unit price "¥700,000", and itemized sales amount "¥0", indicating that the sale is incomplete.

[0073] Figure 8(C) shows an example of updated billing and collection schedule information. The billing and collection schedule information created at the time of the previous billing is treated as settled, and separate collection schedule information is created linked to the sales information that carries over the same amount, thereby reconciling the amount of receivable and the amount to be collected.

[0074] In the example of the invoice collection schedule information shown in Figure 8(C), for the first row, the collection schedule amount "¥300,000" and the payment reconciliation status flag "Not yet completed" for the invoice collection schedule information that has not yet been reconciled, as specified in the sales entry, are updated to "¥0" and "Completed," respectively. The collection schedule amount is set to ¥300,000 - ¥300,000 = 0.

[0075] The second line contains the following information: Invoice number "URI001", Department in charge "Tokyo Department", Billing recipient "△△ Corporation", Order number "JUC001", Order line number "001", Scheduled collection date "2020 / 11 / 15", Scheduled collection amount "¥500,000", Amount paid reconciled "¥0", and Payment reconciled flag "Not yet". A new invoice collection schedule information will be created as a result of registering the sales information. The scheduled collection amount will be ¥800,000 - ¥300,000 = ¥500,000.

[0076] The third line contains the following information: Invoice number "URI001", Department in charge "Tokyo Department", Billing address "△△ Corporation", Order number "JUC001", Order line number "001", Scheduled collection date "2020 / 11 / 15", Scheduled collection amount "¥300,000", Amount paid reconciled "¥0", and Payment reconciled flag "Not yet". For the updated collection amount in the first line, a new scheduled collection amount linked to the sales entry is created and set to "¥300,000".

[0077] Figure 8(D) shows an example of registering pre-billing reconciliation information. In the example of pre-billing reconciliation information in Figure 8(D), the pre-billing reconciliation number is "MSEIK001", the sales number is "URI001", the invoice number is "SNY001", and the reconciliation amount is "¥300,000". Simultaneously with the registration of the planned invoice collection information, the information of the pre-billing slip that has been reconciled by that sales slip is retained. This makes it possible to manage the remaining balance of pre-billed data, excluding slips that have actually been received and slips that have been reconciled by sales, as in this case.

[0078] As described above, according to this embodiment, a contract registration unit 102a registers contract information including order number, goods or services, billing address, order date, planned sales date, and contract amount in a storage unit 106; a pre-billing registration unit 102b registers pre-billing information including planned billing payment number, billing date, billing address, order number, and billing amount, and for the said pre-billing information, planned billing collection information including a slip number including the planned billing payment number, responsible department, billing address, planned collection date, planned collection amount, amount settled, and a settled flag indicating whether or not payment has been settled, in the storage unit; and a sales input unit 102c that, on the sales input screen displayed on the monitor 114, automatically extracts and displays contract information and unpaid pre-billing information linked to a specified order number from the storage unit, settles the sales amount with the billing amount of the pre-billing information when recording the sales amount for the said contract information, and updates the planned billing collection information. As a result, it is possible to reduce the workload of accounts receivable management work related to pre-billing.

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

[0080] Furthermore, this embodiment can contribute to reducing waste and promoting paperless and digital processes, thereby contributing to SDGs Goals 12, 13, and 15.

[0081] Furthermore, this embodiment can contribute to strengthening control and governance, thereby enabling contributions to SDG Goal 16.

[0082] [5. Other Embodiments] In addition to the embodiments described above, the present invention may be implemented in various different embodiments within the scope of the technical idea described 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 by known methods.

[0084] Furthermore, the processing procedures, control procedures, specific names, information including parameters such as registration data and search conditions for each process, screen examples, and database configuration shown in this specification and in the drawings may be changed at will unless otherwise specified.

[0085] Furthermore, with respect to the debt management device 100, each component shown in the diagram is a functional concept and does not necessarily need to be physically configured as shown.

[0086] For example, the processing functions of the debt management device 100, particularly those performed in the control unit, may be implemented in whole or in part by a CPU and a program interpreted and executed by the CPU, or they may be implemented as wired logic hardware. The program is recorded on a non-temporary computer-readable recording medium containing programmed instructions for the information processing device to execute the processing described in this embodiment, and is mechanically read by the debt management device 100 as needed. That is, a storage unit such as ROM or HDD (Hard Disk Drive) contains a computer program that works in cooperation with the OS to give instructions to the CPU and perform various processing tasks. This computer program is executed by being loaded into RAM and works in cooperation with the CPU to constitute the control unit.

[0087] Furthermore, this computer program may be stored on an application program server connected to the debt management device 100 via any network, and it is possible to download all or part of it as needed.

[0088] Furthermore, the program for executing the processing described in this embodiment may be stored on a non-temporary computer-readable recording medium, or it may be configured as a program product. Here, "recording medium" includes any "portable physical medium" such as memory cards, USB (Universal Serial Bus) memory, SD (Secure Digital) cards, flexible disks, magneto-optical disks, ROMs, EPROMs (Erasable Programmable Read Only Memory), EEPROMs (Registered Trademark) (Electrically Erasable and Programmable Read Only Memory), CD-ROMs (Compact Disk Read Only Memory), MOs (Magneto-Optical disks), DVDs (Digital Versatile Disks), and Blu-ray (Registered Trademark) Discs.

[0089] Furthermore, "program" refers to a data processing method described in any language or writing method, regardless of its format, such as source code or binary code. Note that "program" is not necessarily limited to a single, monolithic structure; it also includes distributed structures consisting of multiple modules or libraries, and those that work in cooperation with other programs, such as an operating system, to achieve their functions. Regarding the specific configuration and reading procedures for reading the recording medium in each device shown in the embodiments, as well as the installation procedures after reading, well-known configurations and procedures can be used.

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

[0091] Furthermore, the debt management device 100 may be configured as a known personal computer or workstation or other information processing device, or as an information processing device to which any peripheral devices are connected. Alternatively, the debt management device 100 may be implemented by installing software (including programs or data, etc.) on the device that enables the processing described in this embodiment.

[0092] Furthermore, the specific forms of distribution and integration of the devices are not limited to those shown in the figures, and all or part of them can be configured by functionally or physically distributing and integrating them in any unit according to various additions or functional loads. In other words, the embodiments described above may be implemented in any combination, or the embodiments may be implemented selectively. [Industrial applicability]

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

[0094] 100 Debt Management System 102 Control Unit 102a Contract Registration Department 102b Pre-billing 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 device 114 Output device 200 servers 300 Networks

Claims

1. A debt management device comprising a memory unit and a control unit, The aforementioned storage unit includes: (1) Contract information including order number, goods or services, billing address, order date, expected sales date, unit price, and contract amount; (2) Pre-billing information including expected billing and payment number, billing date, billing address, order number, and billing amount; and (3) Scheduled billing and collection information including voucher number including expected billing and payment number, responsible department, billing address, expected collection date, expected collection amount, amount settled, and a payment settlement flag indicating whether payment has been settled or not. The control unit, In a sales input screen that includes a sales information input area and a pre-billing reconciliation area, when an operator enters an order number, the system reads from the storage unit the contract information corresponding to the order number and the scheduled billing information with a payment reconciliation flag of "Not Yet" corresponding to the order number. The system then displays the contract information in the sales information input area and the scheduled billing information in the pre-billing reconciliation area. In the sales information input area, when the operator enters the number of goods or services to be recorded as sales and sets the completion flag to ON, the system calculates the number of sales × unit price and displays the result as the sales amount in the sales information input area. It also performs information processing to determine the amount to be reconciled against the previous invoice amount based on the sales amount, and displays the result of this determination in the previous invoice reconciliation area. When an operator instructs registration on the sales entry screen, the following processes are executed: (1) register the sales information corresponding to the order number in the storage unit; (2) register the previous billing reconciliation information corresponding to the sales number of the sales information and the slip number of the billing and collection schedule information in the storage unit; (3) update the billing and collection schedule information to the amount obtained by subtracting the current reconciliation amount and update the payment reconciliation completed flag to "completed"; and (4) register in the storage unit the billing and collection schedule information corresponding to the sales number, where the billing and collection schedule amount is the amount obtained by subtracting the billing amount from the sales amount, and the billing and collection schedule information corresponding to the sales number, where the current reconciliation amount is the billing and collection schedule amount. A debt management system characterized by the following:

2. The debt management device according to claim 1, characterized in that the sales input means registers sales information, including sales number, order number, product or service, billing address, sales date, scheduled collection date, and sales amount, in the storage unit based on the input content of the sales input screen.

3. A debt management method to be executed by an information processing device equipped with a control unit and a memory unit, The aforementioned storage unit includes: (1) Contract information including order number, goods or services, billing address, order date, expected sales date, unit price, and contract amount; (2) Pre-billing information including expected billing and payment number, billing date, billing address, order number, and billing amount; and (3) Scheduled billing and collection information including voucher number including expected billing and payment number, responsible department, billing address, expected collection date, expected collection amount, amount settled, and a payment settlement flag indicating whether payment has been settled or not. The control unit, In a sales input screen that includes a sales information input area and a pre-billing reconciliation area, when an operator enters an order number, the system reads from the storage unit the contract information corresponding to the order number and the scheduled billing information with a payment reconciliation flag of "Not Yet" corresponding to the order number. The system then displays the contract information in the sales information input area and the scheduled billing information in the pre-billing reconciliation area. In the sales information input area, when the operator enters the number of goods or services to be recorded as sales and sets the completion flag to ON, the system calculates the number of sales × unit price and displays the result as the sales amount in the sales information input area. It also performs information processing to determine the amount to be reconciled against the previous invoice amount based on the sales amount, and displays the result of this determination in the previous invoice reconciliation area. When an operator instructs registration on the sales entry screen, the following processes are executed: (1) register the sales information corresponding to the order number in the storage unit; (2) register the previous billing reconciliation information corresponding to the sales number of the sales information and the slip number of the billing and collection schedule information in the storage unit; (3) update the billing and collection schedule information to the amount obtained by subtracting the current reconciliation amount and update the payment reconciliation completed flag to "completed"; and (4) register in the storage unit the billing and collection schedule information corresponding to the sales number, where the billing and collection schedule amount is the amount obtained by subtracting the billing amount from the sales amount, and the billing and collection schedule information corresponding to the sales number, where the current reconciliation amount is the billing and collection schedule amount. A debt management method characterized by the following.

4. A debt management program to be executed by an information processing device equipped with a control unit and a memory unit, The aforementioned storage unit includes: (1) Contract information including order number, goods or services, billing address, order date, expected sales date, unit price, and contract amount; (2) Pre-billing information including expected billing and payment number, billing date, billing address, order number, and billing amount; and (3) Scheduled billing and collection information including voucher number including expected billing and payment number, responsible department, billing address, expected collection date, expected collection amount, amount settled, and a payment settlement flag indicating whether payment has been settled or not. The control unit, In a sales input screen provided with a sales information input area and a pre-billing reconciliation area, when an operator enters an order number, the system reads from the storage unit the contract information corresponding to the order number and the scheduled billing information with a payment reconciliation flag of "Not Yet" corresponding to the order number, and displays the contract information in the sales information input area and the scheduled billing information in the pre-billing reconciliation area, respectively. In the sales information input area, when an operator enters the number of goods or services to be recorded as sales and sets the completion flag to ON, the system calculates the number of sales × unit price, displays the result as the sales amount in the sales information input area, and performs information processing to determine the amount to be reconciled against the previous invoice amount based on the sales amount, and displays the result of this determination in the previous invoice reconciliation area. When an operator instructs registration on the sales entry screen, the means executes: (1) a process to register sales information corresponding to the order number in the storage unit; (2) a process to register previous billing reconciliation information corresponding to the sales number of the sales information and the slip number of the billing and collection schedule information in the storage unit; (3) a process to update the billing and collection schedule amount to the amount obtained by subtracting the current reconciliation amount and update the payment reconciliation completed flag to "completed"; and (4) a process to register in the storage unit the billing and collection schedule information corresponding to the sales number, in which the amount obtained by subtracting the billing amount from the sales amount is the billing amount, and the billing and collection schedule information corresponding to the sales number, in which the current reconciliation amount is the billing amount. A debt management program characterized by its function as such.

Images