JP2017168090A - Credit management device per project, credit management method per project, and credit management program per project - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a credit management device per project, a credit management method per project, and a credit management program per project in which even settlement day or collection condition can be managed per project by enabling management of claim or credit per project in addition to a billing destination.SOLUTION: In a credit management device per project, sales data per project is obtained, and a credit management setting linked to a billing destination of sales data registered in a billing destination mater or a credit management setting specified by a user is registered into a project master to which a project of the sales data is linked. When the credit management setting to perform a credit management per project is registered, the credit management including a billing process to a billing destination per project is performed for the sales data based on the project master.SELECTED DRAWING: Figure 1

Description

  The present invention relates to a project-specific credit management device, a project-specific credit management method, and a project-specific credit management program.

  According to Patent Document 1, it is difficult to understand the “monthly sales record result information” in one construction in the system so far. It is difficult to understand “contrast information between contract amount and sales record” for one construction. “Monthly payment inspection record information” for each payment inspection partner in one construction work cannot be obtained. “Contrast information between contract amount and payment record” cannot be obtained for each payment inspection destination in one construction. There has been a problem that information on “total of monthly”, “total of specified month to specified month”, and “total of annual” cannot be obtained for each customer and payment inspection destination. For this reason, Patent Document 1 discloses a construction ledger and a cash flow system based on a business management system that can easily obtain the various information in one construction and can easily create a construction ledger with less man-hours. Yes.

JP 2009-245140 A

  As described above, Patent Document 1 can easily obtain the various types of information in a single construction, and can easily create a construction ledger with a small number of man-hours. However, in Patent Document 1, since billing and claim management are not performed for each site or project, there is a problem that the closing date and the collection condition cannot be managed for each site or project.

  The present invention has been made in view of the above-mentioned problems, and by making it possible to carry out billing and claim management for each project in addition to the billing destination, the deadline and collection conditions can also be managed on a project basis. An object is to provide a project-specific credit management device, a project-specific credit management method, and a project-specific credit management program.

  In order to solve the above-described problems and achieve the object, a project-specific credit management device according to the present invention is a project-specific credit management device including a storage unit and a control unit, and the storage unit is a bill. A billing destination storage means for storing a billing destination master associated with a billing destination as a delivery destination and a claim management setting indicating whether or not to perform the claim management for each project, the billing destination, the project, and the project A project storage means for storing a project master associated with a closing date and a debt collection condition, and the control unit includes a sales data acquisition means for acquiring sales data for each project, and the billing master The receivable management setting associated with the billing address of the registered sales data or the receivable management setting specified by the user is changed to the profile of the sales data. When the master management means for registering the project to which the project is linked and the credit management setting for performing the credit management for each project by the master management means are registered, the sales data is based on the project master. And a credit management means for executing credit management including billing processing for each project with respect to the billing destination.

  Further, the credit management device by project according to the present invention, the credit management means, when the credit management setting for performing credit management for each project is registered by the master management means, based on the project master, For sales data, executing the billing process by creating billing data for each project with respect to the billing destination, and executing the bond management based on the billing data and payment data from the billing destination. Features.

  Further, in the claim management apparatus by project according to the present invention, the billing master further stores the billing date and claim collection conditions, and the claim management means is further controlled by the master management means. Including the billing process for each billing destination with respect to the billing destination for the sales data based on the billing destination master and the project master when the claim management setting not performing the claim management for each project is registered. It is characterized by executing debt management.

  Further, the credit management device by project according to the present invention is characterized in that the credit management further includes management of credit balance data for each project and / or management of credit balance data for each billing destination. To do.

  Moreover, the credit management apparatus according to project according to the present invention is characterized in that the project is a construction site in a construction industry including a civil engineering business.

  The project-specific credit management method according to the present invention is a project-specific credit management method for causing a project-based credit management device including a storage unit and a control unit to execute, wherein the storage unit sends a bill. A billing destination storage means for storing a billing destination master associated with a billing destination that is a destination and a claim management setting indicating whether or not the claim management is performed for each project, the billing destination, the project, and the closing date of the project And a project storage means for storing the project master associated with the claim collection condition, and the sales data acquisition step for acquiring the sales data for each project, which is executed by the control unit, and the billing master The receivable management setting associated with the billing address of the registered sales data or the receivable management setting specified by the user When the master management step for registering in the project master associated with the project of sales data and the credit management setting for performing credit management for each project in the master management step are registered, based on the project master The sales data includes a credit management step for executing credit management including billing processing for each project with respect to the billing destination.

  The project-specific credit management program according to the present invention is a project-specific credit management program for causing a project-specific credit management device including a storage unit and a control unit to execute the program. A billing destination storage means for storing a billing destination master associated with a billing destination that is a destination and a claim management setting indicating whether or not the claim management is performed for each project, the billing destination, the project, and the closing date of the project And a project storage means for storing a project master associated with a debt collection condition, and in the control unit, a sales data acquisition step of acquiring sales data for each project, and registered in the billing destination master The receivable management setting associated with the billing destination of the sales data or the receivable management setting specified by the user A master management step for registering in the project master associated with the project of the sales data, and the credit management setting for performing credit management for each project in the master management step. Based on the master, a credit management step for executing credit management including billing processing for each project with respect to the billing destination is executed on the sales data.

  According to the present invention, billing and claim management can be performed for each project in addition to the billing party, and the effect is that the deadline and collection conditions can be managed in units of projects.

FIG. 1 is a block diagram showing an example of the configuration of a project-specific credit management device. FIG. 2 is a flowchart showing an example of processing of the project-specific credit management device in the present embodiment. FIG. 3 is a diagram illustrating an example of the billing destination master. FIG. 4 is a diagram illustrating an example of a project master. FIG. 5 is a diagram illustrating an example of a sales input screen. FIG. 6 is a diagram illustrating an example of sales data. FIG. 7 is a diagram illustrating an example of billing data. FIG. 8 is a diagram illustrating an example of a billing list. FIG. 9 is a diagram showing an example of a billing statement in billing balance management by project. FIG. 10 is a diagram showing another example of a billing statement in billing balance management by project. FIG. 11 is a diagram showing an example of a billing statement in billing balance management by billing destination. FIG. 12 is a diagram showing an example of a receivable balance list in receivable balance management. FIG. 13 is a diagram illustrating an example of a deposit input screen. FIG. 14 is a diagram showing an example of a billing statement in the deposit process.

  Embodiments of the present invention will be described in detail with reference to the drawings. In addition, this invention is not limited by this embodiment.

[1. Overview]
In the present embodiment, for example, assuming a business condition to be wholesaled for a construction project such as construction / civil engineering, project information can be specified for each order, and performance management and billing / credit management can be performed for each project.

  The present embodiment is characterized in that a temporary credit management unit (hereinafter referred to as “project” or “PJ”) is managed separately from the invoice delivery destination (hereinafter referred to as “invoice destination”). Yes, it is possible to provide a mechanism for managing the balance of receivables by a combination of these “bill-to party” and “project”.

  In this embodiment, for example, a work that can be expected to have an effect is not only a billing unit when receiving an order for a material / construction for a construction site (temporary credit management unit) from a general contractor. There are cases where billing balance management and receivable balance management are performed by a combination of “Billing Address” + “Construction Site Unit”. This is because if the partner is managing the budget for each project (construction site), the contractor is also required to manage the bill balance and receivable balance by project (construction site). Because there is.

[2. Constitution]
An example of the configuration of the project-based credit management device 100 according to the present embodiment will be described with reference to FIG. FIG. 1 is a block diagram showing an example of the configuration of the project-specific credit management device 100.

  The project-specific credit management device 100 is a commercially available desktop personal computer. The project-specific credit management device 100 is not limited to a stationary information processing device such as a desktop personal computer, but may be a commercially available notebook personal computer, PDA (Personal Digital Assistant), smartphone, tablet personal computer, or the like. It may be a portable information processing apparatus.

  The project-specific bond management device 100 includes a control unit 102, a communication interface unit 104, a storage unit 106, and an input / output interface unit 108. Each part with which the claim management apparatus 100 according to a project is equipped is connected so that communication is possible via arbitrary communication paths.

  The communication interface unit 104 communicatively connects the project-specific bond 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 a communication line. Here, the network 300 has a function of connecting the project-specific credit 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).

  The storage unit 106 stores various databases, tables, files, and the like. The storage unit 106 stores a computer program for giving various instructions to a CPU (Central Processing Unit) in cooperation with an OS (Operating System). As the storage unit 106, for example, a memory device such as a RAM (Random Access Memory) and a ROM (Read Only Memory), a fixed disk device such as a hard disk, a flexible disk, and an optical disk can be used. The storage unit 106 includes a billing master 106a, a project master 106b, a sales data file 106c, and a billing data file 106d.

  The billing destination master 106a is a billing destination master in which a billing destination, which is a bill destination, and a credit management setting indicating whether or not to perform credit management for each project are linked. Here, the billing destination master may further register the billing party's closing date and claim collection conditions. Further, a billing destination code (CD) may be registered in the billing destination master 106a.

  The project master 106b is a project master in which a billing destination, a project, a closing date of the project, and a debt collection condition are associated with each other. Here, the project may be a construction site in a construction industry including a civil engineering business. Further, the project master 106b further includes a billing destination code (CD), a project (CD), a credit management setting indicating whether or not to perform credit management for each project, a closing date and a credit collection condition for each project, and / or The project completion date may be registered.

  The sales data file 106c stores sales data. Here, the sales data file 106c may store sales data for each billing destination and / or for each project. The sales data may include a sales slip number, a recording date, a billing destination CD, a billing destination name, a project CD, a project name, a sales amount, and / or a consumption tax amount.

  The billing data file 106d stores billing (billing) data. Here, the billing data file 106d may store billing data for each billing destination and / or for each project. Here, the billing data may include billing specification (billing specification) data. The billing data may include a billing destination CD, a billing destination name, a project CD, a project name, a sales amount, a consumption tax amount, and / or a total billing amount. The billing data file 106d may store bond balance data. Here, the receivable balance data may be receivable balance management data based on the billing data and the deposit data from the billing destination. The billing data file 106d may store credit balance data for each billing destination or each project.

  An input device 112 and an output device 114 are connected to the input / output interface unit 108. As the output device 114, a speaker (including a home television), a speaker, and a printer can be used. As the input device 112, in addition to a keyboard, a mouse, and a microphone, a monitor that realizes a pointing device function in cooperation with the mouse can be used. In the following description, the output device 114 may be described as the monitor 114, and the input device 112 may be described as the keyboard 112 or the mouse 112.

  The control unit 102 is a CPU or the like that controls the project-specific credit management device 100 in an integrated manner. The control unit 102 has an internal memory for storing a control program such as an OS, a program that defines various processing procedures, and necessary data, and performs various information processing based on these stored programs. Run. The control unit 102 includes a sales data acquisition unit 102a, a master management unit 102b, and a bond management unit 102c in terms of functional concept.

  The sales data acquisition unit 102a acquires sales data. Here, the sales data acquisition unit 102a may acquire sales data for each billing destination and / or for each project. Here, the sales data acquisition unit 102a may acquire sales data input by the user. The sales data acquisition unit 102a may store the sales data in the sales data file 106c.

  The master management unit 102b sets the credit management setting associated with the billing destination of the sales data registered in the billing destination master 106a or the credit management setting designated by the user to the project master 106b linked with the sales data project. Register with.

  The bond management unit 102c executes bond management including a billing process for the billing party for the sales data. Here, when the credit management setting for performing credit management for each project is registered by the master management unit 102b, the credit management unit 102c performs billing processing for each project with respect to the billing destination based on the project master 106b. Including debt management. In addition, when the master management unit 102b registers the credit management setting for performing the credit management for each project, the credit management unit 102c creates billing data for each project with respect to the billing destination based on the project master 106b. Thus, the billing process may be executed, and the bond management may be executed based on the billing data and the deposit data from the billing destination. In addition, when the master management unit 102b registers a credit management setting that does not perform credit management for each project, the credit management unit 102c charges the billing destination for the sales data based on the billing master 106a and the project master 106b. Receivable management including billing processing for each destination may be executed. Here, the receivable management may include management of receivable balance data for each project and / or management of receivable balance data for each billing destination. Further, the bond management unit 102c may create and / or update bond balance data based on the billing data and the deposit data from the billing party. Further, the claim management unit 102c may store billing data and / or claim balance data in the billing data file 106d.

[3. Concrete example]
A specific example of this embodiment will be described with reference to FIGS.

[Debt management processing]
Here, with reference to FIG. 2, an example of the project-specific credit management process in the present embodiment will be described. FIG. 2 is a flowchart showing an example of processing of the project-specific credit management device 100 in the present embodiment.

  As shown in FIG. 2, the sales data acquisition unit 102a acquires sales data for each project input by the user via the input device 112, and stores the sales data in the sales data file 106c (step SA-1). ).

  Then, the master management unit 102b displays the credit management setting associated with the billing destination of the sales data registered in the billing destination master 106a or the credit management setting designated by the user via the input device 112. The sales data project acquired by 102a is registered in the project master 106b associated with the project (step SA-2).

  Then, the credit management unit 102c determines whether or not the credit management setting for performing credit management for each project is registered by the master management unit 102b (step SA-3).

  Then, the credit management unit 102c shifts the processing to step SA-4 when it is determined that the credit management setting for performing credit management for each project is registered by the master management unit 102b (step SA-3: Yes).

  Based on the project master 106b, the bond management unit 102c executes billing processing by creating billing data for each project with respect to the billing destination for the sales data for each project stored in the sales data file 106c. The billing data for each project is stored in the billing data file 106d (step SA-4).

  Then, the credit management unit 102c executes credit management including creation and updating of credit balance data for each project based on the billing data for each project stored in the billing data file 106d and the payment data from the billing destination. (Step SA-5), the process ends.

  On the other hand, when it is determined by the master management unit 102b that the credit management setting for performing credit management for each project is not registered (No at Step SA-3), the credit management unit 102c shifts the processing to Step SA-6. .

  Then, the claim management unit 102c creates billing data for each billing destination for the billing destination for the sales data for each project stored in the sales data file 106c based on the billing destination master 106a and the project master 106b. The process is executed, and the billing data for each billing destination is stored in the billing data file 106d (step SA-6).

  Then, the receivable management unit 102c performs receivable management including creation and updating of receivable balance data for each billing destination based on the billing data for each billing destination stored in the billing data file 106d and the payment data from the billing destination. Execute (step SA-7) and end the process.

  Here, an example of master management in the present embodiment will be described with reference to FIGS. 3 and 4. FIG. 3 is a diagram illustrating an example of the billing destination master. FIG. 4 is a diagram illustrating an example of a project master.

  The master configuration in this embodiment includes a billing master 106a shown in FIG. 3 and a project master 106b shown in FIG. Here, as shown in FIG. 3, the billing destination master 106 a registers a billing destination as a bill destination (a business partner). Also, as shown in FIG. 4, the project master 106b registers a project for each billing destination (each), holds a completion date, and manages it as temporary information. 3 and 4 sets whether or not to manage the balance of receivables for each project (each). In the case of managing the balance of receivables for each project, the transaction performed for the PJ is managed as “billing destination” + “by PJ”. If you do not manage the balance of receivables for each project, the transactions performed for the PJ should be managed for each billing destination (each) (in this case, PJ information is added to the transaction as delivery destination information) But not a credit management unit). Further, items such as a closing date / collection condition can be set in both the billing destination master and the project master (in the case of managing claims by PJ). When managing loans by PJ, billing is made according to the deadline / collection conditions of the project master. Whether or not to manage receivables by PJ is determined by the billing party, and it is also possible to set whether or not the transactions of the same billing destination code can be changed to "transactions by transaction (by slip)". However, since there is a possibility that whether or not billing for each project is required for each billing destination project, it is necessary to separately operate billing destination codes. That is, as a breakdown of the billing destination, a billing destination code and a project code are set, and the billing management level as the billing destination unit can be selected from “billing destination unit” and “project unit”. As described above, when the credit management unit is set on a project basis, the effectiveness increases if the billing and credit management unit can be determined by the project linked to each transaction.

  In addition, an example of the flow of credit management processing in the present embodiment will be described with reference to FIGS. FIG. 5 is a diagram illustrating an example of a sales input screen. FIG. 6 is a diagram illustrating an example of sales data. FIG. 7 is a diagram illustrating an example of billing data. FIG. 8 is a diagram illustrating an example of a billing list. FIG. 9 is a diagram showing an example of a billing statement in billing balance management by project. FIG. 10 is a diagram showing another example of a billing statement in billing balance management by project. FIG. 11 is a diagram showing an example of a billing statement in billing balance management by billing destination. FIG. 12 is a diagram showing an example of a receivable balance list in receivable balance management. FIG. 13 is a diagram illustrating an example of a deposit input screen. FIG. 14 is a diagram showing an example of a billing statement in the deposit process.

  First, as (1) sales input processing, as shown in FIG. 5, the user inputs sales data using a sales input screen. In particular, in the sales input screen of FIG. 5, it is necessary to input at least billing destination data and project information (receivable management setting) for controlling whether or not to perform receivable management by project. And in this embodiment, as shown in FIG. 6, sales data are produced | generated by inputting into the sales input screen of FIG. Here, as shown in FIG. 6, for each sales slip number, a case for managing a claim by PJ or a case for managing a claim by claim destination is linked.

  As (2) billing processing, in this embodiment, billing data is generated based on the sales data in FIG. 6 as shown in FIG. 7, and based on the billing data, as shown in FIG. A billing table is created. Here, as shown in the billing list of FIG. 8, the project deadline management and the collection conditions are displayed for the projects for which the project balance management is performed, and the projects for which the bill balance management is performed for each billing party. The previous closing date and the collection conditions are displayed.

  Here, as shown in FIG. 9 and FIG. 10, in the billing statement in the case of performing the billing balance management by project in this embodiment, the project name is described separately from the destination (billing destination), It is a billing statement. Further, as shown in FIG. 11, in the billing specification when performing billing balance management by billing destination in the present embodiment, only the sending destination (billing destination) is described, and the billing specification is in units of billing destinations. Yes.

  (3) In the present embodiment, as shown in the list of receivable balances in FIG. 12, as for receivable balance management, each project-specific statement and bill-to-destination account are separately divided for the projects for which charge balance management by project is performed. It is displayed and each receivable balance can be managed. On the other hand, in the present embodiment, as shown in the list of claims balance in FIG. 12, the billing total is displayed for the billing balance management by billing destination, and the claim balance can be managed based on that.

  (4) As shown in FIG. 13, as the deposit process, in this embodiment, when the user inputs a deposit request destination (billing destination: invoice sending destination) on the deposit input screen, Information on each project that is handled is displayed, and a check box is displayed as to whether or not to perform the payment application for each project. Here, as shown in FIG. 13, in this embodiment, when a check is entered by the user in the check box of the case where the PJ subject is “XX City Hall Annex Building”, the receivable balance list of FIG. As described above, the payment application processing for each project may be executed for the payment from the billing party using the collective payment function.

[4. Other Embodiments]
In addition to the above-described embodiments, the present invention may be implemented in various different embodiments within the scope of the technical idea described in the claims.

  For example, among the processes described in the embodiments, all or part of the processes described as being automatically performed can be performed manually, or all of the processes described as being performed manually are all performed. Alternatively, a part can be automatically performed by a known method.

  In addition, the processing procedures, control procedures, specific names, information including parameters such as registration data and search conditions for each processing, screen examples, and database configurations shown in the present specification and drawings, unless otherwise specified. Can be changed arbitrarily.

  Moreover, regarding the credit management apparatus by project 100, each illustrated component is functionally conceptual and does not necessarily need to be physically configured as illustrated.

  For example, all or some of the processing functions provided by the project-based credit management device 100, particularly the processing functions performed by the control unit 102, are realized by a CPU and a program interpreted and executed by the CPU. Alternatively, it may be realized as hardware by wired logic. The program is recorded on a non-temporary computer-readable recording medium including a programmed instruction for causing the information processing apparatus to execute the processing described in the present embodiment. It is mechanically read by the management device 100. In other words, in a storage unit such as a ROM or a HDD (Hard Disk Drive), a computer program for giving instructions to the CPU in cooperation with the OS and performing various processes is recorded. This computer program is executed by being loaded into the RAM, and constitutes a control unit in cooperation with the CPU.

  The computer program may be stored in an application program server connected to the project-specific credit management device 100 via an arbitrary network, and may be downloaded in whole or in part as necessary. Is possible.

  In addition, a program for executing the processing described in this embodiment may be stored in a non-temporary computer-readable recording medium, or may be configured as a program product. Here, the “recording medium” refers to a memory card, USB (Universal Serial Bus) memory, SD (Secure Digital) card, flexible disk, magneto-optical disk, ROM, EPROM (Erasable Programmable Read Only Memory), EEPROM (registration). Trademark) (Electrically Erasable and Programmable Read Only Memory), CD-ROM (Compact Disk Read Only Memory), MO (Magneto-Optical disk), DVD (Digital Digital, Trademark) Any “portable physical media It is intended to include.

  The “program” is a data processing method described in an arbitrary language or description method, and may be in any form such as source code or binary code. Note that the “program” is not necessarily limited to a single configuration, and functions are achieved in cooperation with a separate configuration such as a plurality of modules and libraries or a separate program represented by the OS. Including things. In addition, a well-known structure and procedure can be used about the specific structure and reading procedure for reading a recording medium in each apparatus shown to embodiment, the installation procedure after reading, etc.

  Various databases and the like stored in the storage unit are storage means such as a memory device such as a RAM and a ROM, a fixed disk device such as a hard disk, a flexible disk, and an optical disk. Stores programs, tables, databases, web page files, and the like.

  Further, the project-specific credit 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 an arbitrary peripheral device is connected. Further, the project-specific credit management device 100 may be realized by mounting software (including a program or data) that realizes the processing described in the present embodiment on the device.

  Furthermore, the specific form of distribution / integration of the devices is not limited to that shown in the figure, and all or a part of them may be functionally or physically in arbitrary units according to various additions or according to functional loads. It can be configured to be distributed and integrated. That is, the above-described embodiments may be arbitrarily combined and may be selectively implemented.

  The present invention is particularly useful in a construction and civil engineering business where it is necessary to perform billing and claim management by project in addition to the billing destination when billing and claim management are performed.

DESCRIPTION OF SYMBOLS 100 Claim management apparatus 102 Control part 102a Sales data acquisition part 102b Master management part 102c Claim management part 104 Communication interface part 106 Memory | storage part 106a Billing master 106b Project master 106c Sales data file 106d Billing data file 108 Input / output interface part 112 Input device 114 Output device 200 Server 300 Network

Claims (7)

A project-specific credit management device comprising a storage unit and a control unit,
The storage unit
A billing destination storage means for storing a billing destination master associated with a billing destination as a billing destination and a claim management setting indicating whether or not to perform claim management for each project;
Project storage means for storing a project master in which the billing destination, the project, the closing date of the project, and the debt collection conditions are linked;
With
The controller is
Sales data acquisition means for acquiring sales data for each project;
The receivable management setting associated with the billing destination of the sales data registered in the billing destination master or the receivable management setting specified by the user is stored in the project master associated with the project of the sales data. A master management means to register;
When the credit management setting for performing credit management for each project is registered by the master management means, based on the project master, the sales data includes credit management including billing processing for each project with respect to the billing destination. Receivable management means to implement;
A project-specific credit management device characterized by comprising: The claim management means includes:
When the credit management setting for performing credit management for each project is registered by the master management means, the billing data for each project with respect to the billing destination is created for the sales data based on the project master. 2. The claim management apparatus according to claim 1, wherein the claim processing is executed, and the claim management is executed based on the billing data and payment data from the billing destination. The billing master is
Furthermore, the closing date of the billing party and the conditions for collection of claims are registered,
The claim management means includes:
Further, when the credit management setting that does not perform credit management for each project is registered by the master management means, the billing destination with respect to the billing destination for the sales data based on the billing master and the project master The credit management apparatus according to project according to claim 1, wherein the credit management including each billing process is executed. The receivable management is
4. Claim management according to any one of claims 1 to 3, further comprising management of credit balance data for each project and / or management of credit balance data for each billing destination. apparatus. The project is
The project-specific credit management device according to any one of claims 1 to 4, which is a construction site in a construction industry including a civil engineering business. A project-based credit management method for causing a project-based credit management device comprising a storage unit and a control unit to execute the method,
The storage unit
A billing destination storage means for storing a billing destination master associated with a billing destination as a billing destination and a claim management setting indicating whether or not to perform claim management for each project;
Project storage means for storing a project master in which the billing destination, the project, the closing date of the project, and the debt collection conditions are linked;
With
To be executed by the control unit;
Sales data acquisition step for acquiring sales data for each project;
The receivable management setting associated with the billing destination of the sales data registered in the billing destination master or the receivable management setting specified by the user is stored in the project master associated with the project of the sales data. A master management step to register,
When the credit management setting for performing credit management for each project is registered in the master management step, the credit management including the billing processing for each project with respect to the billing destination for the sales data based on the project master Receivables management steps to carry out,
A method for managing claims by project, characterized by including: A project-specific credit management program for causing a project-based credit management device comprising a storage unit and a control unit to execute the program,
The storage unit
A billing destination storage means for storing a billing destination master associated with a billing destination as a billing destination and a claim management setting indicating whether or not to perform claim management for each project;
Project storage means for storing a project master in which the billing destination, the project, the closing date of the project, and the debt collection conditions are linked;
With
In the control unit,
Sales data acquisition step for acquiring sales data for each project;
The receivable management setting associated with the billing destination of the sales data registered in the billing destination master or the receivable management setting specified by the user is stored in the project master associated with the project of the sales data. A master management step to register,
When the credit management setting for performing credit management for each project is registered in the master management step, the credit management including the billing processing for each project with respect to the billing destination for the sales data based on the project master Receivables management steps to carry out,
Receivable management program by project to execute

Images