JP7460486B2 - Individual billing management device, individual billing management method, and individual billing management program - Google Patents

Description

The present invention relates to an individual billing management device, an individual billing management method, and an individual billing management program that handle sales data and billing data.

Particularly in the dispatch industry or maintenance industry, there are cases where work requests are received for projects with different billing timings, such as short-term projects and long-term projects. Because they have to be registered separately, even the same billing party may be registered as different billing parties. There were also various billing processing units, such as billing by period and billing by case. As a result, the tasks of data management and billing for accounting personnel have become complex and time-consuming.

Furthermore, depending on the case, for example, it may be necessary to suddenly change the billing destination after billing has been processed on a work-by-work, request-by-request, etc. basis, placing a heavy burden on the accounting staff.

However, to date, no system that solves these problems has been known (Patent Document 1).

Japanese Patent Application Publication No. 6-325057

The object of the present invention is to provide an individual invoice management device equipped with a system that can contribute to early understanding of the invoice recipient's implementation amount against the project budget and early payment procedures by specifying various conditions such as invoice recipient, sales period, request unit, contract classification, etc., and by enabling the issuance of invoices, as well as an individual invoice management method using said system, and an individual invoice management program based on said system.

Another object of the present invention is to provide an individual billing management device equipped with a system capable of responding to sudden changes in billing destination, an individual billing management method using said system, and an individual billing management program based on said system.

In order to solve the above-mentioned problems and achieve the objective, the individual billing management device of the present invention is an individual billing management device equipped with a control unit, and the control unit includes or links (1) billing destination identification information, (2) sales identification information, and (3) sales amount related information for each fee generation type classification, and further includes (4) request or assignment identification information, (5) work performance identification information, (6) contract classification identification information, (7) billing timing pattern identification information, (8) customer or person in charge identification information, (9) fee generation type identification information, and (15) A specific identification range selected from the identification information (1) to (11) and the above-mentioned (1) are used as conditions for extracting specific sales information that does not include billing identification information from sales data that includes or is linked to one or more of the following: (1) identification information of the business establishment where the sales are recorded; (11) identification information of the department or division where the sales are recorded; (12) sales date information; (13) request or acceptance date information; and (14) sales collection date information. The system is characterized by comprising a sales information extraction condition receiving means for receiving one or more conditions from a specific date range selected from date information (2) to (14); a sales information extraction means for extracting sales information that meets the conditions received by the sales information extraction condition receiving means from the sales data; a sales information update means for adding new (15) billing identification information for each of the (1) billing recipient identification information to the sales information extracted by the sales information extraction means; and a billing information registration means for creating new billing information including (15') billing identification information that is the same as or corresponds to the (15) billing identification information added by the sales information update means, (3') billing amount information based on the total sales amount calculated from the (3) sales amount related information included in or linked to the sales information extracted by the sales information extraction means, and (1) billing recipient identification information included in or linked to the sales information extracted by the sales information extraction means, and registering the billing information in the billing data for each of the (15') billing identification information.

Further, in the individual billing management device according to the present invention, the control unit may specify the (15) billing identification information in the specific billing information registered in the billing data and the (1) in the specific billing information. billing information change receiving means that accepts the designation of (1') billing party identification information that is different from the billing party identification information; The present invention is characterized by further comprising: billing information updating means for changing the identification information of the billing party (1) to the specified identification information of the billing party (1') received by the change accepting means.

Further, in the individual billing management device according to the present invention, the control unit may select the identification information of the (1) or (1') billing party included in the billing information registered in the billing data, and the (3') billing destination identification information. The present invention is characterized by further comprising a bill issuing means for issuing a bill displaying amount information and (15') billing identification information.

In addition, the individual billing management method according to the present invention is an individual billing management method executed in an individual billing management device having a control unit, and includes or links (1) billing destination identification information, (2) sales identification information, and (3) sales amount related information for each fee generation type classification executed by the control unit, and further includes (4) request or assignment identification information, (5) work performance identification information, (6) contract classification identification information, (7) billing timing pattern identification information, (8) customer or person in charge identification information, and (9) fee generation type classification. (15) A specific identification range selected from the identification information (1) to (11) and the above (12) to (14) as a condition for extracting specific sales information that does not include billing identification information from sales data that includes or is linked to one or more of the following: (10) identification information of the business establishment where the sales are recorded; (11) identification information of the department or division where the sales are recorded; (12) date information of the sales recording; (13) date information of the request or acceptance; and (14) date information of the planned date of sales collection. The method includes a sales information extraction condition receiving step for receiving one or more conditions from a specific date range selected from the date information of the sales information extraction condition receiving step, a sales information extraction step for extracting sales information corresponding to the conditions received in the sales information extraction condition receiving step from the sales data, a sales information update step for adding new (15) billing identification information for each of the (1) billing destination identification information to the sales information extracted by the sales information extraction step, and a billing information registration step for creating new billing information including (15') billing identification information that is the same as or corresponds to the (15) billing identification information added by the sales information update step, (3') billing amount information based on the total sales amount calculated from the (3) sales amount related information included in or linked to the sales information extracted by the sales information extraction step, and (1) billing destination identification information included in or linked to the sales information extracted by the sales information extraction step, and registering the billing information in the billing data for each of the (15') billing identification information.

Further, the individual billing management program according to the present invention is an individual billing management program to be executed by an individual billing management device including a control unit, and includes (1) identification information of a billing party to be executed by the control unit; , (2) sales identification information, and (3) sales amount related information for each charge generation type classification, including or linking, (4) request or acceptance identification information, and (5) work performance identification. (6) Identification information of contract classification, (7) Identification information of billing timing pattern, (8) Identification information of customer or person in charge, (9) Identification information of charge generation type classification, (10) Sales recording. (11) Identification information of the division or department where sales are recorded, (12) Date information of sales recording, (13) Date information of request or acceptance, and (14) Date information of scheduled sales collection. (15) As a condition for extracting specific sales information that does not include billing identification information, from sales data that includes or links one or more of the following, sales information is registered by sales and by classification of charge generation form. Sales information extraction conditions that accept one or more conditions from the specific identification range selected from the identification information in (1) to (11) and the specific date range selected from the date information in (12) to (14) above. a receiving step, a sales information extracting step for extracting sales information corresponding to the conditions accepted by the sales information extraction condition receiving step from the sales data, and adding the above (1) to the sales information extracted by the sales information extracting step. ) a sales information update step of adding new (15) billing identification information for each billing party's identification information; 15') Billing identification information, based on the total sales amount calculated from the (3) sales amount related information included in or linked to the sales information extracted in the sales information extraction step (3') Create new billing information including the billing amount information and the identification information of the billing party (1) included in or linked to the sales information extracted in the sales information extraction step, and (15') The method is characterized by including a billing information registration step of registering each billing identification information in billing data.

The individual billing management device, individual billing management method, and individual billing management program of the present invention allow you to specify various conditions such as billing recipient, sales period, request unit, and contract classification, perform closing processing, and issue invoices, which contributes to early understanding of the billing recipient's actual amount against the project budget and early payment procedures. It is also possible to respond to sudden changes to the billing recipient.

FIG. 1 is a block diagram showing an example of the configuration of a PC 100. FIG. 2 is a diagram showing an example of the configuration of the sales data, billing data, work performance data, work request data, and billing destination master data by information item. FIG. 3 is a diagram showing an example of sales data. FIG. 4 is a diagram showing an example of the flow of information processing by the sales information extraction condition reception unit 102a, the sales information extraction unit 102b, the sales information update unit 102c, and the billing information registration unit 102d. FIG. 5A is a diagram showing an example of a sales information extraction condition input screen (billing information creation screen). FIG. 5B is a diagram showing an example of sales data. FIG. 5C is a diagram showing an example of the billing data. FIG. 6A is a diagram showing an example of a sales information extraction condition input screen (billing information creation screen). FIG. 6B is a diagram showing an example of sales data. FIG. 6C is a diagram illustrating an example of billing data. FIG. 7A is a diagram showing an example of a sales information extraction condition input screen (billing information creation screen). FIG. 7B is a diagram showing an example of sales data. FIG. 7C is a diagram showing an example of the billing data. FIG. 8A is a diagram illustrating an example of a sales information extraction condition input screen (billing information creation screen). FIG. 8B is a diagram showing an example of sales data. FIG. 8C is a diagram showing an example of billing data. FIG. 8D is a diagram showing an example of a billing destination change screen in this example. FIG. 8E is a diagram illustrating an example of billing data.

An embodiment of the present invention will be described in detail with reference to the drawings. Note that the present invention is not limited to this embodiment.

[1. Configuration]
Here, an example of the configuration of a PC (personal computer) 100 according to this embodiment including the individual billing management device of the present invention will be described with reference to Fig. 1. Note that the configuration of this embodiment is merely an example, and the present invention is not limited to being realized with the configuration of this embodiment. Also, in the following description of the configuration, duplicated explanations may be omitted.

Fig. 1 is a block diagram showing an example of the configuration of a PC 100. The PC 100 includes a control unit 102, a communication interface unit 104, a storage unit 106, and an input/output interface unit 108, and is communicatively connected to a server 200 (e.g., a web server, etc.) that stores various data (e.g., data stored in the storage unit 106, which may be described later) via a network 300 (e.g., the Internet, an intranet, a LAN (Local Area Network), etc.).

Each part of the PC 100 is connected so that it can communicate with each other via any communication path.

Note that the PC 100 may be a stationary computer such as a desktop personal computer, or a portable computer such as a notebook personal computer, a PDA (Personal Digital Assistant), a smartphone, or a tablet personal computer. It may be.

The control unit 102 is a CPU or the like that controls the PC 100 in an integrated manner. The control unit 102 has an internal memory for storing control programs such as an OS, programs that define various processing procedures, required data, etc., and performs various information processing based on these stored programs. Execute.

In terms of functional concept, the control unit 102 includes a sales information extraction condition receiving unit 102a, a sales information extraction unit 102b, a sales information update unit 102c, a billing information registration unit 102d, a billing information change receiving unit 102e, a billing information update unit 102f, and an invoice issuing unit 102g.

The sales information extraction condition accepting unit 102a accepts (15) conditions for extracting specific sales information that does not include billing identification information from sales data in which sales information is registered by sales and by charge generation type category.

The sales information includes or is linked to (1) billing destination identification information, (2) sales identification information, and (3) sales amount related information for each fee generation type category, and also includes or is linked to one or more of (4) request or assignment identification information, (5) work performance identification information, (6) contract type identification information, (7) billing timing pattern identification information, (8) customer or person in charge identification information, (9) fee generation type category identification information, (10) sales establishment identification information, (11) sales division or department identification information, (12) sales recognition date information, (13) request or assignment date information, and (14) planned sales collection date information. In addition, (15) billing identification information is added to the sales information by the sales information update unit 102c described below.

(1) Billing destination identification information (including (1') billing destination identification information described below) is information for specifying the billing destination. (2) Sales identification information is information for individually identifying the occurrence of sales. (3) The sales amount related information for each charge generation type category is information for calculating the sales amount or sales amount for each charge generation type category. Information for calculating the sales amount may be, for example, a combination of sales unit price and sales quantity. (4) Request or acceptance identification information is information for distinguishing requests or acceptances for products or services. (5) Identification information of work performance is information for individually identifying the implementation of work. (6) The identification information of the contract category may be, for example, the contract category of work such as dispatch work, contract work, or commissioned work.

(7) The identification information of the billing timing pattern may be, for example, information on closing dates such as anytime closing, closing for each case, special closing, weekly closing (e.g., closing on a specific day of the week), monthly closing (e.g., closing at the end of the month), or, optionally, information on the deadline for the invoice to arrive after the closing date, which may be combined with such information to determine the timing of issuing and sending the billing. (8) The identification information of the customer or the person in charge is information for identifying the customer or the person in charge of the customer. (9) The identification information of the category of the fee generation form is, for example, a category of the generation form of the unit price, and specifically, information for identifying the category of the quantity unit price of the product, the basic unit price of the service, the premium unit price, the night unit price, etc. (10) The identification information of the business establishment where the sales are recorded, and (11) the identification information of the department or division where the sales are recorded are information for identifying the business establishment where the sales are recorded, and the department or division where the sales are recorded, respectively. (15) The identification information of the billing (including the identification information of the billing (15') described below) is information for identifying the billing individually.

The identification information (1) to (11) and (15) may be in the form of, for example, an identifier (ID), a number (NO), etc.

(12) Sales recording date information, (13) Request or acceptance date information, and (14) Sales collection schedule date information are the sales recording date of the product or service, the request date or acceptance date of the product or service, respectively. , and information on the scheduled sales collection date.

The identification information (1) to (11) and the date information (12) to (14) may be directly included in the sales information of the sales data, or may be directly included in the sales information via another identification information. The information linked to or indirectly from the sales data may be data independent of the sales data or information included in the master information.

The conditions accepted by the sales information extraction condition accepting unit 102a are (15) conditions for extracting specific sales information that does not include invoice identification information, and are one or more of a specific identification range selected from the identification information (1) to (11) and a specific date range selected from the date information (12) to (14). The specific identification range and specific date range can be a combination of one specific identification information and date range, or two or more specific identification information and date ranges, and the combination of two or more specific identification information and date ranges is not limited to consecutive identifiers (ID), numbers (NO), or dates.

In one embodiment, the sales information extraction condition receiving unit 102a also receives (16) the specification of billing date information along with the conditions. (16) Billing date information is information on the closing date for finalizing the billing.

The sales information extraction unit 102b extracts sales information that corresponds to the conditions accepted by the sales information extraction condition reception unit 102a from the sales data.

The sales information update unit 102c adds new (15) billing identification information for each (1) billing destination identification information to the sales information extracted by the sales information extraction unit 102b. In one embodiment, the sales information update unit 102c further adds a different, distinguishable branch number for each piece of sales information to which the same (15) billing identification information has been added.

The billing information registration unit 102d stores billing identification information (15') that is the same as or corresponds to (15) billing identification information added by the sales information updating unit 102c, and is included in the sales information extracted by the sales information extraction unit 102b. (3) Based on the total sales amount calculated from the sales amount related information (3') Included in the billing amount information and the sales information extracted by the sales information extraction unit 102b; New billing information including the linked (1) billing destination identification information is created and registered in the billing data for each billing identification information (15').

The billing information includes, for example, (1) (or (1')) billing party identification information, (3') billing amount information, and (15') billing identification information, as well as (3) sales amount. Contains or links related information, (10) identification information of the office where sales are recorded, (11) identification information of the department or department where sales are recorded, (16) billing date information, and (17) information on the amount paid. can be done. The billing information is linked to the sales information via billing identification information (15') that is the same as or corresponding to (15') billing identification information in the sales information.

The billing information change reception unit 102e specifies (15) billing identification information in specific billing information registered in billing data and (1') billing that is different from (1) billing party identification information in specific billing information. Accepts the specification of the previous identification information.

The billing information update unit 102f updates the identification information of the (1) billing party in the billing information including the identification information of the specified (15) request received by the change receiving means into the specified (1') request received by the change receiving means. Change to the previous identification information.

The invoice issuing unit 102g issues an invoice displaying (1) (or (1')) billing recipient identification information, (3') billing amount information, and (15') billing identification information, which are included in the billing information registered in the billing data. In one embodiment, in addition to (1) (or (1')) billing recipient identification information, (3') billing amount information, and (15') billing identification information, which are included in the billing information, the invoice may also display (3) sales amount related information, (10) identification information of the business establishment where the sales are recorded, (11) identification information of the department or division where the sales are recorded, (16) billing date information, (17) information on the amount received, and the like, which are also included in the billing information.

The invoice issuing unit 102g issues invoices by printing the invoice on a paper medium, or as an electronic invoice (an example is a PDF (Portable Document Format) invoice). etc. are included.

The communication interface unit 104 communicatively connects the PC 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.

The storage unit 106 stores various databases, tables, files, and the like. The storage unit 106 stores a computer program for giving instructions to a CPU (Central Processing Unit) to perform various processes in cooperation with an OS (Operating System). As the storage unit 106, for example, a memory device such as a RAM (Random Access Memory) or a ROM (Read Only Memory), a fixed disk device such as a hard disk, a flexible disk, an optical disk, etc. can be used.

The memory unit 106 conceptually includes a sales billing information memory unit 106a, etc.

The sales billing information storage unit 106a stores sales data, billing data, and data or master data that is directly or indirectly linked to the sales data or billing data and is independent from the sales data and billing data.

An input device 400 and an output device 500 are connected to the input/output interface section 108. The output device 400 includes a display device such as a display or a projector, an audio device such as a speaker, a printing device such as a printer, and a device that allows downloading in a data file format. The data file format may be a file format known in the art, such as PDF, CSV, document file, spreadsheet software file, or text file. As the input device 500, in addition to a keyboard, a mouse, and a microphone, a monitor that cooperates with the mouse to realize a pointing device function can be used.

[2. Concrete example]
Here, using a specific example, the sales information extraction condition reception unit 102a, the sales information extraction unit 102b, the sales information update unit 102c, the billing information registration unit 102d, and the billing information change reception unit in the individual billing management device according to the present invention will be explained. Information processing by the unit 102e and the billing information update unit 102f will be described with reference to FIGS. 2 to 8E.

FIG. 2 shows the configuration of each information item of sales data D1, billing data D2, work record data D3, work request data D4, and billing destination master M1 stored in the sales billing information storage unit 106a in this specific example. FIG.

Figure 3 shows sales data D1 before a new billing ID and billing branch number are added to the sales information A01 to A16 that is the subject of this specific example.

In this specific example, the sales data D1 includes sales information, and the sales information included in the sales data D1 includes, for each sales ID (sales identification information) and each product ID (identification information for the fee generation type category), the sales date (sales recording date information), performance number (work performance identification information), billing ID (billing identification information), customer ID (customer identification information), quantity (sales volume), unit (unit of sales volume), unit price (sales unit price), amount (sales amount) (information related to the sales amount for each fee generation type category), work request ID (request identification information), contract category (contract category identification information), recording establishment (identification information for the establishment recording sales), recording department (identification information for the department recording sales), and may further include a billing ID (billing identification information), and billing branch number information, as shown in FIG. 3.

The billing data D2 in this specific example includes billing information, and the billing information included in the billing data D2 includes, for each billing ID, billing party ID, billing date (billing date information), accounting office, accounting department, sales. Contains information on amount (sales amount for each bill), consumption tax amount (consumption tax amount on sales amount for each bill), bill amount (sales amount plus consumption tax amount), and deposit amount (deposited amount), As shown in FIG. 2, the sales information included in the sales data D1 is linked via the billing destination ID.

In this specific example, the work performance data D3 includes work performance information, and the work performance information (not shown) included in the work performance data D3 includes information on the contract category and work request ID for each performance number, and is linked to the sales information included in the sales data D1 via the performance number, work request ID, or contract category, as shown in FIG. 2.

The work request data D4 in this specific example includes work request information, and the work request information (illustration omitted) included in the work request data D4 includes a contract classification and a customer ID for each work request ID. As shown in , it is linked to the work performance information included in the work performance data D3 via the work request ID or contract classification.

In this specific example, the billing master M1 contains billing information, and the billing information (not shown) contained in the billing master M1 contains information on the billing date, billing group (identification information of the billing timing pattern), and scheduled collection date for each billing ID and customer ID, and is linked to sales information contained in the sales data D1 via the billing ID or customer ID, as shown in Figure 2.

FIG. 4 is a diagram showing the flow of information processing by the sales information extraction condition reception unit 102a, the sales information extraction unit 102b, the sales information update unit 102c, and the billing information registration unit 102d in this specific example. Hereinafter, the first to fourth examples will be explained regarding the processing of the sales information extraction condition reception unit 102a, the sales information extraction unit 102b, the sales information update unit 102c, and the billing information registration unit 102d in the individual billing management device of the present invention. This will be explained with reference to the flow shown in FIG.

(2-1. First Example)
In the first example, we will explain the case where a user inputs sales information extraction conditions specifying a specific accounting business establishment, accounting department, sales date, and billing group into the individual billing management device in order to extract sales information for which billing information is to be created.

FIG. 5A is a sales information extraction condition input screen (billing information creation screen) in this example. The screen shown in Figure 5A allows you to input the billing date, accounting office, accounting department, billing party (billing party ID), scheduled collection date, recording date (sales date), actual number, billing group, and contract category. There are item columns, among which the billing date, accounting office, accounting department, accounting date (sales date), and billing group have already been entered.

FIG. 5B shows the sales data D1 after new billing IDs and billing branch numbers are added to each of the sales information A01 to A16 included in the sales data D1 shown in FIG. 3 in this example.

Figure 5C shows billing data D2 in which the newly created billing information B01 in this example has been registered.

In this example, first, the sales information extraction condition receiving unit 102a receives the sales information extraction conditions, via the screen shown in FIG. 5A, specifying "May 31, 2020" as the billing date, as well as "001" and "A" as the recording establishment and recording department, "May 1-31, 2020" as the date range for the recording date (sales date), and "131" as the billing group (S01 in FIG. 4).

Note that billing information (figure omitted) whose billing group is "131" registered in the billing master M1 is limited to billing information with billing ID "X0001" and customer ID "A0001". . As shown in FIG. 2, the billing information is the sales information included in the sales data D1 via the billing ID and customer ID (the billing ID is "X0001" and the customer ID is "A0001"). sales information).

Sales information A01 to A16 that does not include a billing ID and is included in the sales data D1 shown in FIG. Since they are "X0001" and "A0001" (billing group is "131"), and the sales date is within the range of "May 1st to May 31st (2020)," sales information A01 to A16 is All of the conditions correspond to the sales information extraction conditions accepted by the sales information extraction condition reception unit 102a.

The sales information extraction unit 102b therefore extracts sales information A01 to A16 that meets the sales information extraction conditions accepted by the sales information extraction condition acceptance unit 102a from the sales data D1 shown in FIG. 3 (S02 in FIG. 4).

Next, the sales information update unit 102c adds the newly issued billing ID (billing identification information) "SE00000" together with the billing branch number, as shown in FIG. 5B, to each of the sales information A01 to A16 extracted by the sales information extraction unit 102b contained in the sales data D1 shown in FIG. 3 (S03 in FIG. 4).

Next, as shown in FIG. 5C, the billing information registration unit 102d registers the newly issued billing ID "SE00000" by the sales information update unit 102c, the specified billing date "May 31, 2020" accepted by the sales information extraction condition acceptance unit 102a, the billing destination ID "X0001", the recording business establishment "001", and the recording department "A" which are common items of the sales information A01 to A16, and the total of the amounts (sales amounts) included in the sales information A01 to A16 extracted by the sales information extraction unit 102b (10,000 (A01) + 2,500 (A02) + 2,500 (A03) + 3,000 (A04) + 10,000 (A05) + 2,500 (A06) + 2,500 (A07) + 10,000 (A08) + 2,500 (A09) + 2,500 (A10) + 3,000 (A11) + 10,000 (A12) + 3,000 (A13) + 10,000 (A14) + 3,000 (A15) + 10,000 (A16) = 87,000), the sales amount is 87,000, the consumption tax on the sales amount is 8,700 (tax rate 10%), and the total of the sales amount and the consumption tax amount (87,000 + 8,700 = 95,700) is the invoice amount 95,700, and the amount received is 0 (0 for unpaid amount), and this is registered in the invoice data D2 (S04 in FIG. 4).

(2-2. Second Example)
In the second example, we will explain the case where a user inputs sales information extraction conditions specifying a specific billing recipient ID, sales date, and work request ID into the individual billing management device in order to extract sales information for which billing information is to be created.

Figure 6A is the sales information extraction condition input screen (billing information creation screen) in this example. The screen shown in Figure 6A has fields for inputting the billing date, accounting establishment, accounting department, billing destination (billing destination ID), work request ID, customer (customer ID), sales date, and planned collection date, of which the fields for billing date, billing destination (billing destination ID), work request ID, and sales date have already been filled in.

FIG. 6B shows the sales data D1 after new billing IDs and billing branch numbers are added to each of the sales information A01 to A03, A06, and A07 included in the sales data D1 shown in FIG. 3 in this example.

FIG. 6C shows billing data D2 in which newly created billing information B02 is registered in this example.

In this example, first, the sales information extraction condition reception unit 102a specifies "May 31st (2020)" as the billing date, "X0001" as the billing party ID, and The sales information extraction conditions of "X000000001" as the request ID and "May 1st to May 31st (2020)" as the date range of the sales date are accepted (S01 in FIG. 4).

Of the sales information A01 to A16 without a billing ID included in the sales data D1 shown in Figure 3, only sales information A01 to A03, A06, and A07 meet the conditions of a billing destination ID of "X0001", a work request ID of "X000000001", and a sales date within the range of "May 1 to May 31 (2020)".

The sales information extraction unit 102b therefore extracts sales information A01 to A03, A06, and A07 that meet the sales information extraction conditions accepted by the sales information extraction condition acceptance unit 102a from the sales data D1 shown in FIG. 3 (S02 in FIG. 4).

Next, the sales information updating unit 102c updates each of the sales information A01 to A03, A06, and A07 extracted by the sales information extraction unit 102b included in the sales data D1 shown in FIG. 3, as shown in FIG. 6B. , the newly issued billing ID (billing identification information) "SE00001" is added together with the billing branch number (S03 in FIG. 4).

Next, as shown in FIG. 6C, the billing information registration unit 102d receives the billing ID “SE00001” newly issued by the sales information updating unit 102c and the specified billing date “SE00001” that was received by the sales information extraction condition receiving unit 102a. (May 31, 2020)”, billing ID “X0001”, the common item of sales information A01 to A03, A06, and A07, accounting office “001”, and accounting department “A”, in the sales information extraction unit 102b. Total amount of money (sales amount) included in extracted sales information A01 to A03, A06, and A07 (10,000 (A01) + 2,500 (A02) + 2,500 (A03) + 2,500 (A06) + 2,500 (A07) = 20,000), the sales amount is "20,000", the consumption tax amount on the sales amount is "2,000" (tax rate 10%), and the total of the sales amount and consumption tax amount (20,000 + 2,000 = 22, 000), a billing amount of "22,000" and a deposited amount of "0" (0 for unpaid amount) is newly created and registered in the billing data D2 (S04 in FIG. 4).

(2-3. Third case)
In the third case, in order to extract sales information for which billing information is to be created, the user creates sales information extraction conditions that specify a specific billing party ID, accounting office, accounting department, sales date, and contract category. A case will be explained in which the following information is input into the individual billing management device.

Figure 7A is the sales information extraction condition input screen (billing information creation screen) in this example. The screen shown in Figure 7A has the same item fields as the screen shown in Figure 5A, and the item fields for billing date, accounting establishment, accounting department, billing destination, accounting date (sales date), and contract category have already been filled in.

Figure 7B shows the sales data D1 after new billing IDs and billing sub-numbers have been added to each of the sales information A01-A03, A06, A07, and A13-A16 contained in the sales data D1 shown in Figure 3 in this example.

FIG. 7C shows billing data D2 in which billing information B03 newly created in this example is registered.

In this example, first, the sales information extraction condition reception unit 102a specifies "May 31st (2020)" as the billing date and "001" as the accounting office and accounting department via the screen shown in FIG. 7A. ” and “A”, “X0001” as the billing ID, “May 1st to 31st (2020)” as the date range of the recording date (sales date), and “1” as the contract category. (S01 in FIG. 4).

Of the sales information A01 to A16 without a billing ID included in the sales data D1 shown in Figure 3, only sales information A01 to A03, A06, A07, and A13 to A16 meet the conditions that the accounting establishment and accounting department are "001" and "A", respectively, the billing destination ID is "X0001", the sales date is within the range of "May 1st to 31st (2020)", and the contract category is "1".

The sales information extraction unit 102b therefore extracts sales information A01 to A03, A06, A07, and A13 to A16 that meet the sales information extraction conditions accepted by the sales information extraction condition acceptance unit 102a from the sales data D1 shown in FIG. 3 (S02 in FIG. 4).

Next, the sales information update unit 102c updates the sales information A01 to A03, A06, A07, and A13 to A16 extracted by the sales information extraction unit 102b included in the sales data D1 shown in FIG. As shown in FIG. 4, the newly issued billing ID (bill identification information) "SE00002" is added together with the billing branch number (S03 in FIG. 4).

Next, as shown in FIG. 7C, the billing information registration unit 102d receives the billing ID “SE00002” newly issued by the sales information updating unit 102c and the specified billing date “SE00002” that was received by the sales information extraction condition receiving unit 102a. (May 31, 2020)", billing ID "X0001" for common items of sales information A01-A03, A06, A07, and A13-A16, accounting office "001", and accounting department "A", sales The total amount (sales amount) included in sales information A01 to A03, A06, A07, and A13 to A16 extracted by the information extraction unit 102b (10,000 (A01) + 2,500 (A02) + 2,500 (A03) ) + 2,500 (A06) + 2,500 (A07) + 3,000 (A13) + 10,000 (A14) + 3,000 (A15) + 10,000 (A16) = 46,000) Sales amount "46,000" , the consumption tax amount for the sales amount is "4,600" (tax rate 10%), the billed amount is "50,600" as the total of the sales amount and consumption tax amount (46,000 + 4,600 = 50,600), and the deposit amount is "0". A new billing information B03 consisting of (0 for unpaid money) is created and registered in the billing data D2 (S04 in FIG. 4).

(2-4. Fourth case)
In the fourth case, in order to extract sales information for which billing information is to be created, a user enters sales information extraction conditions that specify the accounting office, accounting department, sales date, and performance number into the individual billing management device. The following describes the case where the input is made.

Figure 8A is the sales information extraction condition input screen (billing information creation screen) in this example. The screen shown in Figure 8A has the same item fields as the screen shown in Figure 5A, and the item fields for billing date, accounting establishment, accounting department, accounting date (sales date), and actual number have already been filled in.

FIG. 8B shows the sales data D1 after a new billing ID and billing branch number are added to each of the sales information A08 to A10 included in the sales data D1 shown in FIG. 3 in this example.

Figure 8C shows billing data D2 in which the newly created billing information B04 has been registered in this example.

In this example, first, the sales information extraction condition receiving unit 102a receives the sales information extraction conditions, via the screen shown in FIG. 8A, specifying "May 31, 2020" as the invoice date, "001" and "A" as the recording establishment and recording department, "May 1-31, 2020" as the date range for the recording date (sales date), and "4" as the performance number (S01 in FIG. 4).

Note that among the sales information A01 to A16 without a billing ID included in the sales data D1 shown in Figure 3, the accounting office and accounting department are "001" and "A", respectively, and the sales date is "(2020)". Sales information A08 to A10 is the only information that falls within the range of "May 1st to May 31st" and that satisfies the conditions of performance number "4".

Therefore, the sales information extraction unit 102b extracts sales information A08 to A10 that correspond to the sales information extraction conditions accepted by the sales information extraction condition acceptance unit 102a from the sales data D1 shown in FIG. 3 (S02 in FIG. 4). .

Next, the sales information update unit 102c adds the newly issued billing ID (billing identification information) "SE00003" together with the billing branch number, as shown in FIG. 8B, to each of the sales information A08 to A10 extracted by the sales information extraction unit 102b contained in the sales data D1 shown in FIG. 3 (S03 in FIG. 4).

Next, as shown in FIG. 8C, the billing information registration unit 102d registers the billing ID "SE00003" newly issued by the sales information update unit 102c, the specified billing date "May 31, 2020" accepted by the sales information extraction condition acceptance unit 102a, the billing destination ID "X0001", the recording business establishment "001", and the recording department "A" which are common items of the sales information A08 to A10, and the amounts (sales The system creates new billing information B04 consisting of the total of the sales amount (10,000 (A08) + 2,500 (A09) + 2,500 (A10) = 15,000) giving a sales amount of 15,000, the consumption tax on the sales amount of 1,500 (tax rate 10%), the total of the sales amount and the consumption tax amount (15,000 + 1,500 = 16,500) giving a billing amount of 16,500, and the amount received of 0 (0 as payment has not been made) and registers this in the billing data D2 (S04 in FIG. 4).

As described above, according to the individual billing management device of the present invention, it is possible to carry out closing processing by specifying various conditions, so that the burden of complex bill issuing operations can be reduced.

The processing of the billing information change receiving section 102e and billing information updating section 102f in the individual billing management device of the present invention will be explained below using a fourth example (continued).

(2-5. Fourth case (continued))
In the fourth case (continued), after the billing information B04 is registered in the billing data D2 in the fourth case, the user further sends an instruction to the individual billing management device to change the billing destination ID of the billing information B04. The following describes the case where the input is made.

FIG. 8D is a billing destination change screen in this example. In the screen shown in FIG. 8D, there are field fields for entering the billing ID, the billing date after the change, and the billing address after the change, all of which have already been entered. Items such as billing destination and scheduled payment date (scheduled collection date) are also displayed. Note that the scheduled payment date (scheduled collection date) is the date based on the information on the scheduled collection date included in the billing destination information (illustration omitted) of the billing destination IDs "X0001" and "Y0001" registered in the billing destination master M1. It is.

FIG. 8E shows billing data D2 in which billing information B04' is registered after updating billing information B04 and changing billing destination ID.

In this example, first, the billing information change reception unit 102e accepts, via the screen shown in FIG. 8D, the specification of "SE00003" as the billing ID of the billing information B04 to be changed, "May 31 (2020)" as the changed billing date (unchanged from billing information B04), and "Y0001" as the changed billing destination ID (an ID different from the billing destination ID "X0001" before the change in billing information B04).

Next, as shown in FIG. 8E, the billing information update unit 102f extracts the billing information B04 including the billing ID "SE00003" specified by the billing information change receiving unit 102e from the billing data D2, and extracts the billing information B04 from the billing data D2. Billing information B04' is created with billing destination ID "X0001" changed to "Y0001", and billing information B04 in billing data D2 is updated to billing information B04'. As a result, the billing destination ID in billing information B04 is updated from "X0001" to "Y0001."

As described above, the individual billing management device of the present invention makes it easy to change the billing destination even in cases where a sudden need arises to change the billing destination.

Although the embodiments of the present invention have been described so far, the present invention may be implemented in various different embodiments in addition to the embodiments described above within the scope of the technical idea described in the claims. It is.

For example, among the processes described in the embodiments described above, all or part of the processes described as being performed automatically can be performed manually, or the processes described as being performed manually All or part of this can also be performed automatically using known methods.

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

Furthermore, with regard to the PC 100, each component shown in the figure is a functional concept, and does not necessarily have to be physically configured as shown in the figure.

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

This computer program may also be stored in an application program server connected to the PC 100 via any network, and all or part of it may be downloaded as needed.

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

Further, a "program" is a data processing method written in any language or writing method, and does not matter in the form of source code or binary code. Note that a "program" is not necessarily limited to a unitary structure, but may be distributed as multiple modules or libraries, or may work together with separate programs such as an OS to achieve its functions. Including things. Note that well-known configurations and procedures can be used for the specific configuration and reading procedure for reading the recording medium in each device shown in the embodiments, and the installation procedure after reading.

The various databases stored in the storage unit are storage means such as memory devices such as RAM and ROM, fixed disk devices such as hard disks, flexible disks, and optical disks, and are used for various processing and website provision. Stores programs, tables, databases, web page files, etc.

The PC 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 PC 100 may be realized by implementing software (including programs or data, etc.) that causes the PC 100 to realize the processing described in this embodiment.

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

The present invention is useful for accounting work that requires issuing invoices in complex units, such as in the temporary staffing or maintenance industries.

100 PCs
102 Control unit 102a Sales information extraction condition reception unit 102b Sales information extraction unit 102c Sales information update unit 102d Billing information registration unit 102e Billing information change reception unit 102f Billing information update unit 102g Billing unit 104 Communication interface unit 106 Storage unit 106a Sales Billing information storage unit 108 Input/output interface unit 200 Server 300 Network 400 Input device 500 Output device

Claims (5)

An individual billing management device including a control unit,
The control unit:
(1) Identification information of the billing destination, (2) identification information of sales, and (3) sales amount related information for each fee generation type category, including or linked to (4) identification information of the request or assignment, (5) identification information of the work performance, (6) identification information of the contract category, (7) identification information of the billing timing pattern, (8) identification information of the customer or person in charge, (9) identification information of the fee generation type category, (10) identification information of the business establishment where the sales are recorded, (11) identification information of the department or division where the sales are recorded, and (12) date information of the sales recording. a sales information extraction condition receiving means for receiving one or more of a specific identification range selected from the identification information of (1) to (11) and a specific date range selected from the date information of (12) to (14) as conditions for extracting specific sales information not including billing identification information (15) from sales data registered by sales and fee generation type category, the sales information including or linked to one or more of (13) date information of request or assignment, and (14) date information of planned sales collection;
a sales information extraction means for extracting sales information that meets the conditions accepted by the sales information extraction condition acceptance means from the sales data;
a sales information updating means for adding new (15) billing identification information for each of the (1) billing destination identification information to the sales information extracted by the sales information extracting means;
a billing information registration means for creating new billing information including the (15') billing identification information that is the same as or corresponds to the (15) billing identification information added by the sales information update means, the (3') billing amount information based on the total sales amount calculated from the (3) sales amount related information included in or linked to the sales information extracted by the sales information extraction means, and the (1) billing destination identification information included in or linked to the sales information extracted by the sales information extraction means, and registering the information in the billing data for each of the (15') billing identification information;
An individual billing management device comprising: The control unit:
a billing information change receiving means for receiving designation of the (15) billing identification information in specific billing information registered in the billing data and designation of the (1') billing destination identification information in the specific billing information that is different from the (1) billing destination identification information;
a billing information update means for changing the identification information of the (1) billing destination in the billing information including the identification information of the (15) billing specified by the change acceptance means to the identification information of the (1') billing destination specified by the change acceptance means;
The individual billing management device according to claim 1 , further comprising: The control section,
Displaying the (1) or (1') billing destination identification information, the (3') billing amount information, and the (15') billing identification information included in the billing information registered in the billing data. The individual bill management device according to claim 1 or 2, further comprising: bill issuing means for issuing a bill. An individual claim management method executed in an individual claim management device comprising a control unit, the method comprising:
executed by the control unit,
(1) Billing party identification information, (2) Sales identification information, (3) Sales amount related information for each charge generation type category, and (4) Request or acceptance identification information. , (5) Identification information of work performance, (6) Identification information of contract classification, (7) Identification information of billing timing pattern, (8) Identification information of customer or person in charge, (9) Classification of charge generation form. Identification information, (10) Identification information of the office where sales are recorded, (11) Identification information of the department or division where sales are recorded, (12) Date information of sales recording, (13) Date information of request or acceptance, and (14) ) From the sales data that includes or links one or more of the sales collection schedule date information, registered by sales and charge generation type category, (15) Specific sales information that does not include billing identification information. One or more of the specific identification range selected from the identification information in (1) to (11) above and the specific date range selected from the date information in (12) to (14) above as conditions for extracting. a sales information extraction condition reception step of accepting the conditions of;
a sales information extraction step of extracting sales information corresponding to the conditions accepted by the sales information extraction condition acceptance step from the sales data;
a sales information updating step of adding new (15) billing identification information for each of the (1) billing destination identification information to the sales information extracted in the sales information extraction step;
(15') Claim identification information that is the same as or corresponds to the (15) claim identification information added in the sales information updating step, and that is included in or linked to the sales information extracted in the sales information extraction step. (3) information on the billing amount based on the total sales amount calculated from the sales amount related information, and the information included in or linked to the sales information extracted in the sales information extraction step. (1) a billing information registration step of creating new billing information including billing party identification information, and registering it in the billing data for each billing identification information (15');
An individual claim management method characterized by comprising: An individual claim management program to be executed by an individual claim management device including a control unit,
for the control unit to execute,
(1) Billing party identification information, (2) Sales identification information, (3) Sales amount related information for each charge generation type category, and (4) Request or acceptance identification information. , (5) Identification information of work performance, (6) Identification information of contract classification, (7) Identification information of billing timing pattern, (8) Identification information of customer or person in charge, (9) Classification of charge generation form. Identification information, (10) Identification information of the office where sales are recorded, (11) Identification information of the department or division where sales are recorded, (12) Date information of sales recording, (13) Date information of request or acceptance, and (14) ) From the sales data that includes or links one or more of the sales collection schedule date information, registered by sales and charge generation type category, (15) Specific sales information that does not include billing identification information. One or more of the specific identification range selected from the identification information in (1) to (11) above and the specific date range selected from the date information in (12) to (14) above as conditions for extracting. a sales information extraction condition reception step of accepting the conditions of;
a sales information extraction step of extracting sales information corresponding to the conditions accepted by the sales information extraction condition acceptance step from the sales data;
a sales information updating step of adding new (15) billing identification information for each of the (1) billing destination identification information to the sales information extracted in the sales information extraction step;
(15') Claim identification information that is the same as or corresponds to the (15) claim identification information added in the sales information updating step, and that is included in or linked to the sales information extracted in the sales information extraction step. (3) information on the billing amount based on the total sales amount calculated from the sales amount related information, and the information included in or linked to the sales information extracted in the sales information extraction step. (1) a billing information registration step of creating new billing information including billing party identification information, and registering it in the billing data for each billing identification information (15');
An individual claim management program characterized by comprising:

Images