Claims management device, claims management method, and claims management program

The receivables management system addresses the complexity of managing receivables from multiple billing parties by integrating contract and sales processes, reducing operational burdens through independent accounting units and efficient receivables transfer.

JP7579223B2Active Publication Date: 2024-11-07OBIC CO LTD
View PDF 7 Cites 0 Cited by

Patent Information

Application Number
JP2021141863
Authority / Receiving Office
JP · JP
Patent Type
Patents
Current Assignee / Owner
Filing Date
2021-08-31
Publication Date
2024-11-07
Estimated Expiration
2041-08-31

AI Technical Summary

Technical Problem

In infrastructure projects like electrical equipment and road construction, managing receivables from multiple billing parties is complex due to independent accounting units for sales and receivables management, leading to operational burdens.

Method used

A receivables management system that integrates contract, sales, and billing processes to manage receivables by recording at a representative billing party and transferring to individual billing parties, using a control unit to handle contract and sales information, creating journal entries, and generating receivables transfer entries.

Benefits of technology

This system reduces operational burdens by independently managing sales and receivables accounting units, facilitating efficient receivables management and reducing operational complexities.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 0007579223000001
    Figure 0007579223000001
  • Figure 0007579223000002
    Figure 0007579223000002
  • Figure 0007579223000003
    Figure 0007579223000003
Patent Text Reader

Abstract

To lessen a workload by independently managing a calculation unit for sale management and a calculation unit for credit management when credit management is performed for a target project.SOLUTION: A credit processing device according to the present invention includes: contract processing means for registering contract information that includes a burden ratio and a burden charge amount of a contract amount for each of a plurality of billing destinations regarding a target project, a representative billing destination of the plurality of billing destinations, and a contract amount of each of sales departments in a company; sales processing means for registering sales information based on the contract information, and creating a sales journalization on the sales departments for the representative billing destination in a sales registration month; and billing processing means for registering bill information including a billing amount for each of the billing destinations on the basis of the sales information, and creating a credit transfer journalization for each of the plurality of billing destinations.SELECTED DRAWING: Figure 1
Need to check novelty before this filing date? Find Prior Art

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 infrastructure projects such as electrical equipment, gas pipes, and road construction, there are many transactions in which the client shares the burden, and when a company undertakes the installation work and design, income and expenditures are managed for one project, but in many cases, receivables arise from multiple billing parties, making management complicated. For example, Patent Document 1 is a conventional system for managing receivables from multiple billing parties. [Prior art documents] [Patent documents]

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

[0004] However, Patent Document 1 does not mention anything about reducing the operational burden by managing the accounting units for sales management and the accounting units for accounts receivable management separately when managing accounts receivable for the target project.

[0005] The present invention has been made in consideration of the above-mentioned problems, and aims to provide a receivables management device, a receivables management method, and a receivables management program that can reduce the operational burden when managing receivables for a target project by independently managing accounting units for the purposes of sales management and accounting units for the purposes of receivables management. [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 equipped with a control unit, the control unit being characterized in that it comprises: a contract processing means for registering contract information for a target project, including the burden ratio and burden amount of the contract amount for each of multiple billing recipients, a representative billing recipient of the multiple billing recipients, and the contract amount for each sales department of the company; a sales processing means for registering sales information based on the contract information and creating a sales journal entry for the sales department for the representative billing recipient in the month of sales registration; and a billing processing means for registering billing information including the billing amount for each billing recipient based on the sales information, and creating a accounts receivable transfer journal entry for each of the multiple billing recipients.

[0007] According to another aspect of the present invention, the sales journal entry may debit the completed construction receivables from the representative billing recipient and credit the completed construction amount of each sales department.

[0008] In addition, according to one aspect of the present invention, the billing processing means may generate receivables accounting data for each billing recipient based on the billing information, the receivables accounting data including records in which the billing amount is a positive value and records in which the billing amount is a negative value, and may create receivables transfer journal entries for each of the multiple billing recipients based on the generated receivables accounting data.

[0009] In addition, according to one aspect of the present invention, the receivables transfer journal entry may include a journal entry in which the debit is accounts receivable for completed construction and the credit is a provisional item, and a journal entry in which the debit is a provisional item and the credit is accounts receivable for completed construction.

[0010] According to another aspect of the present invention, the project may include an infrastructure project.

[0011] In addition, in order to solve the above-mentioned problems and achieve the object, the present invention is a receivables management method to be executed by an information processing device equipped with a control unit, and is characterized by including a contract processing step executed by the control unit to register contract information for a target project, the contract information including the burden ratio and burden amount of the contract amount for each of multiple billing recipients, a representative billing recipient of the multiple billing recipients, and the contract amount for each sales department of the company; a sales processing step to register sales information based on the contract information and prepare a sales journal entry for the sales department for the representative billing recipient in the month of sales registration; and a billing processing step to register billing information including the billing amount for each billing recipient based on the sales information, and prepare a receivables transfer journal entry for each of the multiple billing recipients.

[0012] 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 equipped with a control unit, which causes the control unit to execute the following steps: a contract processing step of registering contract information for a target project, including the burden ratio and burden amount of the contract amount for each of multiple billing recipients, a representative billing recipient of the multiple billing recipients, and the contract amount for each sales department of the company; a sales processing step of registering sales information based on the contract information and creating a sales entry for the sales department for the representative billing recipient in the month of sales registration; and a billing processing step of registering billing information including the billing amount for each billing recipient based on the sales information, and creating a receivables transfer entry for each of the multiple billing recipients. Effect of the Invention

[0013] According to the present invention, when managing accounts receivable for a target project, the accounting unit for the purpose of sales management and the accounting unit for the purpose of accounts receivable management can be managed separately, thereby making it possible to reduce the operational burden. [Brief description of the drawings]

[0014] [Figure 1] FIG. 1 is a block diagram showing an example of the configuration of a claim management device according to the present embodiment. [Diagram 2]FIG. 2 is a diagram illustrating an example of a data structure of the contract information. [Diagram 3] FIG. 3 is a flowchart for explaining an outline of the overall processing of the control unit of the claim management device in this embodiment. [Figure 4] FIG. 4 is a diagram for explaining a specific example of the process of the control unit of the bond management device in this embodiment. [Diagram 5] FIG. 5 is a diagram for explaining a specific example of the process of the control unit of the bond management device in this embodiment. [Figure 6] FIG. 6 is a diagram for explaining a specific example of the process of the control unit of the bond management device in this embodiment. [Figure 7] FIG. 7 is a diagram for explaining a specific example of the process of the control unit of the claim management device in this embodiment. [Figure 8] FIG. 8 is a diagram for explaining a specific example of the process of the control unit of the bond management device in this embodiment. [Figure 9] FIG. 9 is a diagram for explaining a specific example of the process of the control unit of the bond management device in this embodiment. [Figure 10] FIG. 10 is a diagram for explaining a specific example of the process of the control unit of the claim management device in this embodiment. [Figure 11] FIG. 11 is a diagram for explaining a specific example of the process of the control unit of the claim management device in this embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0015] 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.

[0016] [1. Overview] For example, in infrastructure projects such as electrical equipment, gas pipes, and road construction, there are many transactions in which the client shares the burden, and when a company undertakes the installation work and design in-house, it manages income and expenditure for a single project, but there are often cases in which receivables arise from multiple billing parties, making management of these complex.

[0017] Previously, the accounting of sales by department under the company's management unit and the accounting of receivables by billing recipient were handled separately, which created a burden on the company's operations.

[0018] Therefore, in this embodiment, when managing the income and expenditures for a single project, it is possible to specify the billing burden ratios of multiple billing recipients, and a system has been created in which a receivable is recorded for a representative billing recipient at the time of sales, and the receivables are transferred to each billing recipient when billing is made to the multiple billing recipients.

[0019] In other words, in this embodiment, the accounting unit for the purpose of sales management and the accounting unit for the purpose of receivables management are separated, and a system is constructed in which the receivables are recorded to a representative billing destination in accounting entries, and the receivables are transferred to the billing destination when the receivables are confirmed, thereby reducing the operational burden.

[0020] The loan management device of the present invention is widely applicable to various industries, such as infrastructure projects such as electrical equipment, gas pipes, and road construction.

[0021] [2. Configuration] An example of the configuration of a claim management device 100 according to this embodiment will be described with reference to Fig. 1. Fig. 1 is a block diagram showing an example of the configuration of the claim management device 100.

[0022] 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.

[0023] 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.

[0024] 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).

[0025] 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 touch panel), 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 or the printer 114, and the input device 112 may be referred to as the keyboard 112 or the mouse 112. Moreover, "output" refers to outputting by the output device 114, and includes, for example, display output to the monitor 114, print output by the printer 114, and transmission of data to the outside.

[0026] The storage unit 106 stores various databases, tables, files, and the like. 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 also includes a data file 106a.

[0027] The data file 106a is a file for storing various data such as contract information, sales data, sales journal entries, billing information, credit data, credit transfer journal entries, etc. Fig. 2 is a diagram showing an example of the data structure of contract information. The contract information may be composed of a project order header, project order details (contract details), and a billing burden amount.

[0028] The project order header may include data such as project number, order number, fiscal year and month, customer code, voucher sales amount (contract amount), voucher sales consumption tax amount (contract amount consumption tax), voucher cost amount, and voucher gross profit amount.

[0029] Project order details (contract details) may include data such as order number, order line number, product code, product name, credit item classification, consumption tax rate classification, order quantity, sales price (contract price), sales price, sales amount, sales tax amount, cost price, cost amount, and gross profit amount.

[0030] Billing cost data includes project number, order number, billing code, billing cost ratio, It may include data on the billing amount, the billing amount consumption tax, and the total billing amount.

[0031] Sales information may include data such as sales number, project number, order number, main customer, name of contract work, contract period, order date, expected sales date, name of performance obligation, tax rate, quantity, sales price (contract price), sales amount (contract amount), cost estimate, gross profit, sales department, cost department, billing destination, billing burden ratio, billing amount itself, billing amount tax, and total billing amount.

[0032] The billing information may include data such as billing number, billing destination, billing date, sales number, scheduled collection date, billing amount (voucher amount), project number, and order number.

[0033] The receivables accounting data may include data such as accounting date, billing destination, invoice amount (invoice amount), invoice consumption tax (invoice amount consumption tax), project number, and order number.

[0034] 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. In terms of functional concept, the control unit 102 includes a contract processing unit 102a, a sales processing unit 102b, a billing processing unit 102c, and a screen display control unit 102d.

[0035] The contract processing unit 102a inputs contract information including the share and amount of the contract amount for each of a plurality of billing recipients, the representative billing recipient of the plurality of billing recipients, and the contract amount for each of the company's sales departments for the target project in response to, for example, an operator's operation on a contract input screen (see FIG. 4) displayed on the monitor 114, and registers the information in the data file 106a. The project may include an infrastructure project.

[0036] The sales processing unit 102b inputs sales information based on contract information in response to, for example, the operator's operation on the sales input screen (see FIG. 5) displayed on the monitor 114, registers the information in the data file 106a, and also creates a sales journal entry for the sales department to the representative billing recipient in the month of sales registration, and registers the information in the data file 106a. The sales journal entry may be debited with the completed construction receivables for the representative billing recipient, and credited with the completed construction amount for each sales department.

[0037] The billing processing unit 102c inputs billing information including billing amounts for each billing recipient based on sales information in response to, for example, an operator's operation on a billing input screen (see FIG. 7) displayed on the monitor 114, and registers the information in the data file 106a. It also creates a credit transfer journal entry for each of multiple billing recipients, and registers the information in the data file 106a.

[0038] In addition, the billing processing unit 102c may generate, for each billing destination, credit accounts receivable including records with the billing amount set to a positive value and records with the billing amount set to a negative value based on the billing information, and may create a credit accounts receivable transfer journal entry for each of the multiple billing destinations based on the generated credit accounts receivable data. Credit transfer journal entries may include journal entries with the debit set to accounts receivable for completed construction and the credit set to provisional account, and journal entries with the debit set to provisional account and the credit set to accounts receivable for completed construction.

[0039] The screen display control unit 102d controls the display of various screens (eg, a contract input screen, a sales input screen, a billing input screen, etc.) displayed on the monitor 114 and the input therefor.

[0040] [3. Specific Examples] A specific example of the processing of the claim management device 100 in this embodiment will be described with reference to Figures 1 to 11. First, an overview of the overall processing of the claim management device 100 in this embodiment will be described with reference to Figure 3. Figure 3 is a diagram showing a flow for explaining the overview of the overall processing of the claim management device 100 in this embodiment.

[0041] 3, the contract processing unit 102a executes a contract input process (step S1). Specifically, in the contract input process, the contract processing unit 102a inputs contract information including the share and amount of the contract amount for each of a plurality of billing recipients, the representative billing recipient of the plurality of billing recipients, and the contract amount for each sales department of the company for the target project in response to, for example, an operator's operation on a contract input screen (see FIG. 4) displayed on the monitor 114, and registers the information in the data file 106a.

[0042] The sales processing section 102b executes sales input processing (step S2). Specifically, in the sales input processing, the sales processing section 102b inputs sales information based on contract information in response to, for example, an operator's operation on the sales input screen (see FIG. 5) displayed on the monitor 114, registers the information in the data file 106a, and creates a sales journal entry for the sales department for the representative billing recipient in the month of sales registration, and registers the information in the data file 106a. The sales journal entry may be debited to the completed construction receivables for the representative billing recipient, and credited to the completed construction amount for each sales department.

[0043] The billing processor 102c executes billing input processing (step S3). Specifically, in the billing input processing, the billing processor 102c inputs billing information including the billing amount for each billing destination based on the sales information in response to, for example, an operator's operation on the billing input screen (see FIG. 7) displayed on the monitor 114, and registers the information in the data file 106a. Also, the billing processor 102c creates a credit transfer journal entry for each of the multiple billing destinations, and registers the information in the data file 106a.

[0044] In this case, the billing processing unit 102c may generate, for each billing destination, credit accounts receivable including records with the billing amount set to a positive value and records with the billing amount set to a negative value based on the billing information, and may create a credit accounts receivable transfer journal entry for each of the multiple billing destinations based on the generated credit accounts receivable data. Credit transfer journal entries may include journal entries with the debit set to accounts receivable for completed construction and the credit set to provisional account, and journal entries with the debit set to provisional account and the credit set to accounts receivable for completed construction.

[0045] Next, a specific example of the processing by the control unit 102 of the claim management device 100 in this embodiment will be described with reference to Fig. 4 to Fig. 11. Fig. 4 to Fig. 11 are diagrams for explaining a specific example of the processing by the control unit 102 of the claim management device 100 in this embodiment. In the following description, the unit of monetary amount is always "yen", and the notation may be omitted.

[0046] (S1: Contract input processing) The contract input process will be described with reference to FIG. 4. FIG. 4 is a diagram showing a display example of a contract input screen. For example, in response to an operator's operation on the contract input screen displayed on the monitor 114, the contract processing unit 102a inputs contract information including the share of the contract amount and the share of the contract amount for each of multiple billing recipients, a representative billing recipient of the multiple billing recipients, and the contract amount for each sales department of the company for the target project, and registers the information in the data file 106a. When registering a contract, multiple billing recipients are specified, and the share of the contract amount and the share of the contract amount are specified. In the following example, a case will be described in which the billing recipients are "Company A" and "Company B", and the sales departments are "First Construction Department" and "Second Construction Department".

[0047] The contract information input screen shown in Fig. 4 has a header area for specifying the project number, order number, main customer, contract work name, contract period, order date, and expected sales date, a contract details (performance obligation) area for specifying the contract amount by sales department, a multiple billing destination designation area for specifying the burden ratios and billing amounts of multiple billing destinations, a register button, and an end button. When the register button is pressed, the contract information corresponding to the data entered on the screen is stored in the data file 106a.

[0048] The Contract Details (Performance Obligation) area displays the name of the performance obligation, tax rate, quantity, contract price, contract amount, cost estimate amount, gross profit amount, sales department, and cost department, and allows you to specify data for each item.

[0049] In the multiple billing destination designation area, the items of billing destination, billing burden ratio, billing amount, billing amount tax, and total billing amount are displayed, and data for each item is designated.

[0050] In the example shown in Figure 4, the header area contains the project number "PJ0001," order number "JY0001," main customer "Company A," main billing address "Company A," contract work name "XX Air Conditioning Work," contract period "2021 / 07 / 01~2021 / 09 / 30," and order date "2021 / 6 / 25."

[0051] In the contract details (performance obligation) area, the first line is filled in with the name "Design", tax rate "10%", quantity "1", contract unit price "500,000", contract amount "500,000", cost estimate amount "300,000", gross profit amount "200,000", sales department "First Construction Department", cost department "First Construction Department", and the second line is filled in with the name "Installation work", tax rate "10%", quantity "1 ", contract unit price "500,000", contract amount "500,000", cost estimate amount "300,000", gross profit amount "200,000", sales department "Second Construction Department", and cost department "Second Construction Department" have been entered, with the total contract amount being "1,000,000", the total cost estimate amount being "600,000", and the total gross profit amount being "400,000".

[0052] In the multiple billing destination area, the following is entered on the first line: billing destination "Company A", billing share "70%, billing amount "700,000", billing tax "70,000", and total billing amount "770,000". On the second line: billing destination "Company B", billing share "30%, billing amount "300,000", billing tax "30,000", and total billing amount "330,000".

[0053] When the registration button is pressed, contract information corresponding to the data entered on the screen is stored in the data file 106a.

[0054] (S2: Sales input processing) The sales input process will be described with reference to Figures 5 and 6. Figure 5 is a diagram showing an example of a sales input screen. Figure 6 is a diagram showing an example of sales journalization. The sales processing unit 102b inputs sales information based on contract information in response to, for example, an operator's operation on the sales input screen displayed on the monitor 114, and registers the sales information in the data file 106a. When registering the sales information (in the month of sales registration), the sales journalization is created for the sales department for the representative billing destination, and is registered in the data file 106a.

[0055] The sales input screen shown in Figure 5 reads and displays contract information from data file 106b using the project number and order number as keys. Sales numbers may be assigned automatically. If the sales and contract differ, the data should be corrected as necessary. By pressing the register button, sales information corresponding to the data entered on the screen is registered in data file 106a. In the example shown in Figure 5, the same data as in Figure 4 is specified, except for the addition of the sales number "UR0001."

[0056] Figure 6 shows an example of a sales journal entry created based on the sales information in Figure 5. At the time of sales, receivables are recorded to the representative billing recipient. In the example shown in Figure 6, the debit side is "Account receivable for completed construction, 1.1 million, Company A." The credit side is "Amount of completed construction, 500,000, First construction division," "Suspended consumption tax, 500,000, First construction division," "Amount of completed construction, 500,000, Second construction division," and "Suspended consumption tax, 500,000, Second construction division."

[0057] (S3: Billing entry processing) The billing input process will be described with reference to Fig. 7 to Fig. 10. Fig. 7 is a diagram showing an example of the billing input screen (Company A), Fig. 8 is a diagram showing an example of the receivables recording data and receivables transfer journal entry (Company A), Fig. 9 is a diagram showing an example of the billing input screen (Company B), and Fig. 10 is a diagram showing an example of the receivables recording data and receivables transfer journal entry (Company B).

[0058] The billing processing unit 102c, for example, in response to operator operations on the billing input screen displayed on the monitor 114, inputs billing information including the billing amount for each billing recipient based on sales information, and registers this in the data file 106a; also, based on the billing information, generates receivables accounting data including records for each billing recipient in which the billing amount is a positive value and records in which the billing amount is a negative value, and registers this in the data file 106a; and further, based on the receivables accounting data, creates receivables transfer entries for each of multiple billing recipients, and registers this in the data file 106a.

[0059] FIG. 7 shows an example of a billing input screen when registering billing information for Company A. The billing input screen has a header area for specifying the billing destination and billing date, a billing information input area for inputting billing information, a register button, and an end button. The billing information input area displays the following items: sales number, billing destination, scheduled collection date, voucher amount (billing amount), project number, and order number, and data for each item is specified. The billing input screen reads sales information from data file 106a using the billing destination as a key, and displays the corresponding data in the billing information input area. Data such as the amount can be changed. By pressing the register button, billing information corresponding to the data entered on the screen is registered in data file 106a.

[0060] In the example shown in Figure 7, the header area shows the billing destination as "Company A" and the billing date as "2021 / 10 / 15."

[0061] The billing information input area contains the sales number "UR0001," billing destination "Company A," scheduled collection date "10 / 31 / 2021," invoice amount (billing amount) "770,000," project number "PJ0001," and order number "JY0001."

[0062] FIG. 8(A) shows an example of claim accounting data created based on the billing information in FIG. The first record has the accounting date "2021 / 10 / 15", billing destination "Company A", invoice amount (billing amount) "700,000 (positive value)", invoice consumption tax (billing amount consumption tax) "70,000 (positive value)", project number "PJ0001", order number "JY0001", the second record has the accounting date "2021 / 10 / 15", billing destination "Company A", invoice amount (billing amount) "-700,000 (negative value)", invoice consumption tax (billing amount consumption tax) "-70,000 (negative value)", project number "PJ0001", order number "JY0001". In this way, black and red invoices are created.

[0063] Figure 8(B) shows an example of a receivables transfer journal entry created based on Figure 8(A). The first line has a debit of "Accounts receivable from completed construction, 770,000, Company A" and a credit of "Provisional account, 770,000, Company A", and the second line has a debit of "Provisional account, 770,000, Company A" and a credit of "Accounts receivable from completed construction, 770,000, Company A".

[0064] Figure 9 shows an example of a billing input screen when registering billing information for Company B. In the example shown in Figure 9, the header area shows the billing destination as "Company B" and the billing date as "2021 / 10 / 15".

[0065] The billing information input area contains the sales number "UR0001," billing destination "Company B," scheduled collection date "10 / 31 / 2021," invoice amount (billing amount) "330,000," project number "PJ0001," and order number "JY0001."

[0066] Figure 10 (A) shows an example of receivables accounting data created based on the billing information in Figure 9. The first record has an accounting date of "2021 / 10 / 15", billing destination "Company B", invoice amount (billing amount) "300,000 (positive value)", invoice consumption tax (billing amount consumption tax) "30,000 (positive value)", project number "PJ0001", and order number "JY0001". The second record has an accounting date of "2021 / 10 / 15", billing destination "Company B", invoice amount (billing amount) "-300,000 (negative value)", invoice consumption tax (billing amount consumption tax) "-30,000 (negative value)", project number "PJ0001", and order number "JY0001".

[0067] Figure 10(B) shows an example of a receivables transfer journal entry created based on Figure 10(A). The first line has a debit of "Accounts receivable from completed construction, 330,000, Company B" and a credit of "Provisional account, 330,000, Company B," and the second line has a debit of "Provisional account, 330,000, Company B" and a credit of "Accounts receivable from completed construction, 330,000, Company B."

[0068] In this manner, in this embodiment, after the sales journal entry is generated, the receivables are transferred by inputting the invoice. A project (item) is inspected and sales are recorded, but there are cases where the invoice ratio is then determined by settling for each invoice recipient. In this case, since the receivable amount for each invoice recipient has not been determined for the receivables recorded in the sales month, it is possible to record sales and receivables for a representative invoice recipient and transfer the receivable amount after determining it in the invoice month. Conventionally, sales receivables were recorded after the invoice ratio was determined, which was a practical problem as it was a different procedure from the timing of sales recording as the original revenue standard, but this problem has been solved in this embodiment.

[0069] In this embodiment, the accounting unit for the purpose of sales management and the accounting unit for the purpose of receivables management are separated, and a system is constructed in which the accounting is recorded to a representative billing destination in accounting entries, and the receivables are transferred to the billing destination when the receivables are confirmed, thereby reducing the operational burden that would occur if the two were processed separately.

[0070] Figure 11 shows an example of the case where sales are recorded by department at the unit managed by the company and receivables are recorded by billing recipient, and sales recording and receivable recording are managed independently, Figure 11(A) shows the output image of actual sales, and Figure 11(B) shows the output image of the receivable balance list. Previously, when recording sales and receivables at the same time, the sales amount by department had to be calculated by apportioning it to each billing recipient, which made the process complicated.

[0071] As described above, according to this embodiment, the system is provided with a contract processing unit 102a which registers contract information for a target project, including the share and amount of the contract amount for each of a plurality of billing recipients, a representative billing recipient of the plurality of billing recipients, and contract amounts for each of the company's sales departments; a sales processing unit 102b which registers sales information based on the contract information and creates a sales journal entry for the sales department for the representative billing recipient in the month of sales registration; and a billing processing unit 102c which registers billing information including the billing amount for each billing recipient based on the sales information and creates a credit transfer journal entry for each of the plurality of billing recipients. Therefore, when managing credit for a target project, the accounting unit for the purpose of sales management and the accounting unit for the purpose of credit management can be managed independently, thereby reducing the operational burden.

[0072] [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.

[0073] 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.

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

[0075] 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.

[0076] 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.

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

[0078] 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.

[0079] For example, the processing functions of the claim management device 100, particularly the processing functions performed by the control unit 102, 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 the storage unit 106 such as a ROM or HDD (Hard Disk Drive). This computer program is executed by being loaded into the RAM, and constitutes the control unit 102 in cooperation with the CPU.

[0080] 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.

[0081] 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.

[0082] 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.

[0083] The various databases etc. stored in the memory unit 106 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.

[0084] 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 information processing device to realize the processing described in this embodiment.

[0085] Furthermore, the specific form of distribution and integration of the devices is not limited to those 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 function additions. In other words, the above-mentioned embodiments can be implemented in any combination, or the embodiments can be implemented selectively. [Explanation of symbols]

[0086] 100 Credit management device 102 Control section 102a Contract Processing Department 102b Sales Processing Department 102c Claims Processing Department 102d Screen display control unit 104 Communication interface section 106 Storage section 106a Data File 108 Input / Output Interface Section 112 Input Devices 114 Output Device 200 Servers 300 Network

Claims

1. A claim management device having a control unit, The control unit is A contract processing means for registering contract information including the burden ratio and burden amount of the contract amount for each of a plurality of billing recipients for a target project, a representative billing recipient of the plurality of billing recipients, and the contract amount for each sales division of the company; a sales processing means for registering sales information based on the contract information and preparing a sales journal entry for a sales department for a representative billing recipient in the month of sales registration; a billing processing means for registering billing information including a billing amount for each billing destination based on the sales information and creating a credit transfer journal entry for each of the multiple billing destinations; A claim management device comprising:

2. 2. The receivables management device according to claim 1, wherein the sales journal entry has a debit of unreceived completed construction revenue for a representative billing recipient and a credit of the amount of completed construction revenue for each sales department.

3. The claim management device described in claim 1 or claim 2, characterized in that the claim processing means generates claims accounting data for each billing recipient based on the billing information, the records including records in which the billing amount is a positive value and records in which the billing amount is a negative value, and creates claims transfer journal entries for each of the multiple billing recipients based on the generated claims accounting data.

4. 4. The receivables management device according to claim 3, characterized in that the receivables transfer journal entry includes a journal entry in which the debit is accounts receivable for completed construction and the credit is a provisional item, and a journal entry in which the debit is a provisional item and the credit is accounts receivable for completed construction.

5. 5. The loan management device according to claim 1, wherein the project includes an infrastructure project.

6. A claim management method to be executed by an information processing device having a control unit, Executed by the control unit, a contract processing step of registering contract information including the share and amount of the contract amount for each of a plurality of billing recipients, a representative billing recipient of the plurality of billing recipients, and the contract amount for each of the company's sales divisions for the target project; a sales processing step of registering sales information based on the contract information and creating a sales journal entry for the sales department for the representative billing recipient in the month of sales registration; a billing processing step of registering billing information including a billing amount for each billing destination based on the sales information and creating a credit transfer journal entry for each of the multiple billing destinations; A method for managing claims, comprising:

7. A claim management program to be executed by an information processing device having a control unit, In the control unit, a contract processing step of registering contract information including the share and amount of the contract amount for each of a plurality of billing recipients, a representative billing recipient of the plurality of billing recipients, and the contract amount for each of the company's sales divisions for the target project; a sales processing step of registering sales information based on the contract information and creating a sales journal entry for the sales department for the representative billing recipient in the month of sales registration; a billing processing step of registering billing information including a billing amount for each billing destination based on the sales information and creating a credit transfer journal entry for each of the multiple billing destinations; A receivables management program to implement the above.

Citation Information

Patent Citations

  • Work ledger creation device, and program for executing work ledger creation on computer

    JP2004054662A

  • Credit management device per project, credit management method per project, and credit management program per project

    JP2017168090A

  • Bulk payment processor, bulk payment processing method, and bulk payment processing program

    JP2017182806A

  • In-house management system and construction management system

    JP2019168947A

  • Sales transfer classification apparatus, sales transfer classification method and sales transfer classification program

    JP2020004213A