JP7754866B2 - Invoice issuing device, invoice issuing method, and invoice issuing program - Google Patents

Description

The present invention relates to an invoice issuing device, an invoice issuing method, and an invoice issuing program.

For example, in the real estate management industry, management companies not only issue invoices to tenants for monthly rent and other payments, but also to owners. The content of the invoices varies depending on the type of property management, but in the case of outsourced management, the main items of the invoice include management fees, which are the company's sales, and advance payments to contractors. Under the invoice system that will be introduced on October 1, 2023, the requirements for invoice content will be different from previous systems. Previously, systems that comply with the invoice system include, for example, Patent Document 1.

Japanese Patent Application Laid-Open No. 2022-162901

However, the above-mentioned Patent Document 1 does not state anything about reducing the workload and improving the accuracy of billing operations associated with the invoice system.

The present invention has been made in light of the above, and aims to provide an invoice issuing device, an invoice issuing method, and an invoice issuing program that can reduce the burden of billing operations associated with the invoice system and achieve accuracy.

To solve the above-mentioned problems and achieve the objectives, the present invention provides an invoice issuing device equipped with a control unit and used by an issuer to issue invoices. The control unit is configured to be able to access a management item master that associates and registers management items with invoice subject categories including sales or advance payments. When issuing an invoice, the device references the management item master, and if the invoice in question has both advance payments for the invoice subject category and other management items, issues an invoice that includes advance payment details for the advance payment management item and billing details for the other management items.

According to one aspect of the present invention, the control unit is further configured to access a customer master register in which customer information is registered in association with registration numbers, an issuer master register in which issuers information is registered in association with registration numbers, billing statement data including the billing payment category, billing payment SEQ, billing destination code, management item code, property code, invoice issue date, expected payment date, applicable month, base amount, consumption tax, amount including tax, tax category code, and invoice number, and to link the billing statement data with payment statement data, and to access advance payment statement data including the billing payment category, billing payment SEQ, advance payment billing statement data, and advance payment billing statement data including the advance payment billing statement, advance payment billing statement SEQ, payee code, management item code, property code, payment date, applicable month, base amount, consumption tax, amount including tax, tax category code, and payment number, and the invoice issuance means extracts the billing statement data based on the specified output conditions, and outputs the "billing payment category" of the extracted billing statement data to the payment statement data. and "Bill Payment SEQ" as keys, extracts advance payment detail data, extracts payment detail data using the "Advance Payment Bill Payment Category" and "Advance Payment Bill Payment SEQ" of the advance payment detail data as keys, and for each management item of the same invoice number for the extracted advance payment detail data, references the management item master to obtain the invoice subject category. If there is an advance payment invoice subject category and sales, an invoice is issued that includes an advance payment detail created based on the extracted advance payment detail data and that lists the recipient, issuer, issuer registration number obtained from the issuer master, sales expense item, applicable month, invoice amount, total invoice amount, tax rate, total consumption tax, and total amount including tax, and an advance payment settlement statement that is an advance payment detail created based on the extracted payment detail data and that lists the recipient, issuer, payee, payee registration number obtained from the business partner master, advance payment item, applicable month, amount, tax rate, consumption tax, and amount including tax.

Furthermore, according to one aspect of the present invention, the invoice may include an invoice copy created based on the extracted detailed invoice data, which contains the recipient, issuer, total invoice amount, all expense items, the relevant month, invoice amount, total invoice amount, tax rate, total consumption tax, and total amount including tax, and an advance payment detail created based on the extracted detailed invoice data, which contains the recipient, issuer, expense items to be advanced, the relevant month, amount, total amount, tax rate, total consumption tax, and total amount including tax.

Furthermore, according to one aspect of the present invention, the issuer may include a real estate management company.

Furthermore, to solve the above-mentioned problems and achieve the objective, the present invention provides an invoice issuance method executed by an information processing device equipped with a control unit, wherein the control unit is configured to be able to access a management item master that associates and registers management items with invoice subject categories including sales or advance payments, and the method includes an invoice issuance means executed by the control unit that, when issuing an invoice, references the management item master, and, if the invoice in question has an advance payment invoice subject category and both an advance payment and other management items, issues an invoice including an advance payment statement for the advance payment management item and an invoice statement for the other management items.

Furthermore, to solve the above-mentioned problems and achieve the objectives, the present invention provides an invoice issuance program to be executed by an information processing device equipped with a control unit, and an invoice issuance method to be executed by an information processing device equipped with a control unit, wherein the control unit is configured to be able to access a management item master that associates and registers management items with invoice subject categories including sales or advance payments, and the control unit, when issuing an invoice, references the management item master, and if the target invoice has both advance payments for the invoice subject category and other management items, the invoice issuance program executes an invoice issuance step that issues an invoice including advance payment details for the advance payment management item and billing details for the other management items.

This invention has the effect of reducing the burden of billing operations associated with the invoice system and achieving accuracy.

FIG. 1 is a diagram showing an example of the configuration of a bill issuing device according to this embodiment. FIG. 2 is a diagram illustrating an example of the property master. FIG. 3 is a diagram illustrating an example of the supplier master. FIG. 4 is a diagram illustrating an example of the sender master. FIG. 5 is a diagram illustrating an example of the management item master. FIG. 6 is a flow chart showing an example of the overall processing of the bill issuing device according to this embodiment. FIG. 7 is a diagram for explaining a specific example of the processing of the control unit of the invoice issuing device according to this embodiment. FIG. 8 is a diagram for explaining a specific example of the processing of the control unit of the invoice issuing device according to this embodiment. FIG. 9 is a diagram for explaining a specific example of the processing of the control unit of the invoice issuing device according to this embodiment. FIG. 10 is a diagram for explaining a specific example of the processing of the control unit of the invoice issuing device according to this embodiment.

Embodiments of the invoice issuing device, invoice issuing method, and invoice issuing program according to the present invention are described in detail below with reference to the accompanying drawings. Note that the present invention is not limited to these embodiments.

[1. Overview]
For example, in the real estate management business, management companies not only issue monthly invoices to tenants for rent, but also to owners. The content of the invoices varies depending on the type of property management, but in the case of outsourced management, the main items of the invoice include management fees, which are the company's revenue, and advance payments to the company.

In the past, invoices were mostly issued with both sales and advances listed together on a single page. However, with the introduction of the invoice system on October 1, 2023, advances and other items must be clearly distinguished on invoices, and advance settlement statements must be prepared for advances. Property management companies (for example, PM (Property Management) companies) must check the contents of their invoices every month, and if advances and other items are mixed, they must manually prepare separate detailed statements and advance settlement statements, raising concerns about the workload and potential for errors that will accompany this operational review.

In this embodiment, when an invoice contains a mixture of advance payment items and other items, the invoice is automatically split into advance payment items and other items, allowing an invoice (including details) that meets the requirements of the invoice system to be issued, thereby reducing the workload and improving the accuracy of billing operations associated with the invoice system.

The present invention can be widely applied to industries that handle billing for invoices that include a mixture of advance payment items and other items, such as real estate management companies (including PM companies) in the real estate industry.

2. Configuration
An example of the configuration of the bill issuing device according to this embodiment will be described with reference to FIG.
The invoice issuing device according to this embodiment can be suitably used, for example, in a real estate management company, etc. Fig. 1 is a block diagram showing an example of the configuration of an invoice issuing device 100 according to this embodiment.

The invoice issuing device 100 is a commercially available desktop personal computer. Note that the invoice issuing device 100 is not limited to stationary information processing devices such as desktop personal computers, but may also be portable information processing devices such as commercially available notebook personal computers, PDAs (Personal Digital Assistants), smartphones, and tablet personal computers.

The invoice issuing device 100 comprises a control unit 102, a communication interface unit 104, a memory unit 106, and an input/output interface unit 108. Each unit of the invoice issuing device 100 is connected to each other so that they can communicate with each other via any communication path.

The communication interface unit 104 communicatively connects the invoice issuing 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 the function of communicating data with other devices via a communication line. Here, the network 300 has the function of connecting the invoice issuing 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).

An input device 112 and an output device 114 are connected to the input/output interface unit 108. The output device 114 may be a monitor (including a home television), a speaker, or a printer. The input device 112 may be a keyboard, a mouse, a microphone, or a monitor that functions as a pointing device in conjunction with a mouse. Note that, below, the output device 114 may be referred to as the monitor 114, and the input device 112 may be referred to as the keyboard 112 or the mouse 112. Displaying information on the monitor 114 and the user operating the input device 112 may be referred to as "user operation via a UI."

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

The storage unit 106 stores, for example, an object master 106a, a customer master 106b, a sender master 106c, a management item master 106d, billing detail data, advance payment detail data, payment detail data, etc. Figure 2 is a diagram showing an example of the configuration of the object master 106a. Figure 3 is a diagram showing an example of the configuration of the customer master 106b. Figure 4 is a diagram showing an example of the configuration of the sender master 106c. Figure 5 is a diagram showing an example of the configuration of the management item master 106d.

The property master 106a is a master for property information, and can be configured as a table that associates and registers property codes and property names, as shown in Figure 2. In the example shown in the figure, the property code is "BK01" and the property name is "XX Building." The property master 106a is referenced when converting property codes and property names.

The customer master 106b is a master for customer information, and as shown in Figure 3, can be configured as a table that associates and registers customer codes, customer names, and registration numbers (taxable business registration numbers). The customer master 106b is referenced by the invoice issuing unit 102c when entering the customer (payee) registration number on the advance payment settlement statement. In the example shown in the figure, the first line contains customer code "OW001," customer name "Owner A," and registration number "T1000000000001," the second line contains customer code "GY001," customer name "Contractor A," and registration number "T1000000000003," and the third line contains customer code "GY002," customer name "Contractor B," and registration number "T1000000000004."

The sender (issuer) master 106c is a master relating to sender (issuer) information, and as shown in Figure 4, can be configured as a table that associates and registers sender (issuer) codes, sender (issuer) names, and registration numbers. The sender master 106c is referenced by the invoice issuing unit 102c when entering the sender's registration number in the invoice details. In the example shown in the figure, the sender code is "H01", the sender name is "PM Real Estate", and the registration number is "T1000000000002".

The management item master 106d is a master for managing billing management items, and can be configured as a table that associates and registers management item codes, billing management item names, and invoice subject categories (e.g., 0: Sales, 1: Advances), as shown in FIG. 5. In the example shown in the figure, the first line has the management item code "K01," the management item name "Management fee income (PM fee)," and the invoice subject category "0: Sales." The second line has the management item code "K02," the management item name "Brokerage fee income (LM fee)," and the invoice subject category "0: Sales." The third line has the management item code "K03," the management item name "Construction supervision fee income (CM fee)," and the invoice subject category "0: Sales." The fourth line has the management item code "K04," the management item name "Advance payments," and the invoice subject category "1: Advances."

The billing details data may include billing payment category, billing payment SEQ, billing destination code, management item code, property code, billing issue date, expected payment date, applicable month, base amount, consumption tax, amount including tax, tax category code, and billing number (see Figure 9 (A)).

The advance payment details data (advance payment information management table) is used to link billing details data with payment details data, and may include billing payment category, billing payment SEQ, advance payment billing payment category, and advance payment billing payment SEQ (see Figure 9 (B)).

Payment details data (details of advance payment) may include the advance payment claim payment category, advance payment claim payment SEQ, payee code, management item code, property code, payment date, applicable month, base amount, consumption tax, amount including tax, tax category code, and payment number (see Figure 9 (C)).

Returning to Figure 1, the control unit 102 is a CPU or the like that provides overall control of the invoice issuing device 100. The control unit 102 has internal memory for storing control programs such as an OS, programs that define various processing procedures, and required data, and performs various information processing operations based on these stored programs.

The control unit 102 is configured to be able to access the property master 106a, customer master 106b, sender master 106c, management item master 106d, billing detail data, advance payment detail data, payment detail data, etc. stored in the memory unit 106. Note that the property master 106a, customer master 106b, sender master 106c, management item master 106d, billing detail data, advance payment detail data, payment detail data, etc. may be stored in another location (e.g., server 200) as long as the control unit 102 is able to access them.

Functionally, the control unit 102 comprises a master maintenance unit 102a, a billing processing unit 102b, an invoice issuing unit 102c, and a screen display control unit 102d.

The master maintenance unit 102a performs settings such as inputting, adding, changing, and updating data in the property master 106a, business partner master 106b, sender master 106c, and management item master 106d, in response to, for example, operator operations on a master maintenance screen (not shown) displayed on the monitor 114.

The billing processing unit 102b inputs billing detail data, advance payment detail data, payment detail data, etc., in response to, for example, operator operations on a registration screen (not shown) displayed on the monitor 114, and registers the data in the memory unit 106.

When issuing an invoice, the invoice issuing unit 102c references the management item master 106d, and if the invoice in question has both advance payment and other management items in the invoice subject classification, it issues (displays and/or prints) an invoice that includes advance payment details for the advance payment management item and billing details for the other management items.

Specifically, the invoice issuance unit 102c extracts billing detail data from the memory unit 106 based on the specified output conditions, for example, in response to the operator's operation on the invoice issuance screen displayed on the monitor 114, extracts advance payment detail data from the memory unit 106 using the "invoice payment category" and "invoice payment SEQ" of the extracted billing detail data as keys, extracts payment detail data from the memory unit 106 using the "advance payment billing payment category" and "advance payment SEQ" of the advance payment detail data as keys, and, for the extracted billing detail data, refers to the management item master 106d for each management item of the same invoice number, and The item category is obtained, and if sales exist, an invoice is issued that includes an invoice detail created based on the extracted invoice detail data, which includes the destination, issuer, issuer registration number obtained from sender master 106c, sales expense item, applicable month, invoice amount, total invoice amount, tax rate, total consumption tax, and total amount including tax; and an advance payment settlement statement, which is an advance payment detail created based on the extracted payment detail data, which includes the destination, issuer, payee, payee registration number obtained from customer master 106b, advance expense item, applicable month, amount, tax rate, consumption tax, and amount including tax.

The invoice may also include an invoice copy created based on the extracted detailed invoice data, which contains the recipient, issuer, total invoice amount, all expense items, the relevant month, invoice amount, total invoice amount, tax rate, total consumption tax, and total amount including tax, and an advance payment detail created based on the extracted detailed invoice data, which contains the recipient, issuer, expense items to be advanced, the relevant month, amount, total amount, tax rate, total consumption tax, and total amount including tax. The issuer may include a real estate management company.

The screen display control unit 102d controls the display and input of various screens (e.g., invoice issuance screen, various data registration screen, master maintenance screen, etc.) displayed on the monitor 114.

3. Specific Examples
A specific example of the processing performed by the control unit 102 of the bill issuing device 100 in this embodiment will be described with reference to FIGS.

(3-1. Overall processing)
FIG. 6 is a flowchart for explaining an outline of the overall processing of the control unit 102 of the invoice issuing device 100 in this embodiment.

With reference to Figure 6, an overview of the overall processing of the control unit 102 of the invoice issuing device 100 in this embodiment will be described. In Figure 6, the master maintenance unit 102a executes management item master maintenance processing (step S1). Specifically, in the management item master maintenance processing, the master maintenance unit 102a performs initial data settings for the management item master 106d in response to, for example, an operator's operation on a management item master maintenance screen (not shown) displayed on the monitor 114.

The invoice issuance unit 102c executes the invoice issuance process (step S2). Specifically, in the invoice issuance process, the invoice issuance unit 102c, monthly, for example, refers to the management item master 106d for the target invoice in accordance with the specified output conditions in response to an operator's operation on the invoice issuance screen displayed on the monitor 114, and, if the invoice subject classification includes both advance payment and other management items, issues (displays and/or prints) an invoice including advance payment details for the advance payment management item and billing details for the other management items.

The invoice issuance unit 102c extracts billing detail data based on the specified output conditions, for example, in response to the operator's operation on the invoice issuance screen displayed on the monitor 114, extracts advance payment detail data using the "invoice payment category" and "invoice payment SEQ" of the extracted billing detail data as keys, extracts payment detail data using the "advance payment billing payment category" and "advance payment billing payment SEQ" of the advance payment detail data as keys, and for the extracted billing detail data, for each management item of the same invoice number, references the management item master 106d to obtain the invoice subject category, and sets the invoice subject category as "advance payment" If sales exist, an invoice is automatically issued, which includes an invoice detail created based on the extracted invoice detail data and includes the destination, issuer, issuer registration number obtained from sender master 106c, sales expense item, applicable month, invoice amount, total invoice amount, tax rate, total consumption tax, and total amount including tax; an advance payment settlement statement, which is an advance payment detail created based on the extracted payment detail data and includes the destination, issuer, payee, payee registration number obtained from business partner master 106b, expense item to be advanced, applicable month, amount, tax rate, consumption tax, and amount including tax; a copy of the invoice; and an advance payment detail.

(3-2. Sample data)
7 to 10 are diagrams showing sample data for explaining a specific example of the processing by the control unit 102 of the invoice issuing device 100 in this embodiment. A specific example of the processing by the control unit 102 of the invoice issuing device 100 in this embodiment will be described with reference to FIGS.
In the following, an example will be described in which the master configuration examples shown in FIGS. 2 to 5 are used.

(S1: Management item master maintenance processing)
A specific example of the management item master maintenance process will be described with reference to Fig. 7. The master maintenance unit 102a performs initial data settings for the management item master 106d in response to, for example, an operator's operation on a management item master maintenance screen (not shown) displayed on the monitor 114.

Figure 7 shows an example of the management item master maintenance screen. The management item master maintenance screen has fields for specifying the management item code, management item name, and invoice subject category, as well as a register button and a close button. When the management item code, management item name, and invoice subject category are specified for each management item and the register button is pressed, the input information is registered in the management item master 106d. For example, data such as that shown in Figure 5 is registered in the management item master 106d.

(S2: Invoice issuance process)
A specific example of the invoice issuance process will be described with reference to Figures 8 to 10. The invoice issuance unit 102c extracts detailed invoice data from the storage unit 106 based on specified output conditions in response to, for example, an operator's operation on the invoice issuance screen displayed on the monitor 114, extracts detailed advance payment data from the storage unit 106 using the "invoice payment category" and "invoice payment SEQ" of the extracted detailed advance payment data as keys, and extracts detailed payment data from the storage unit 106 using the "invoice payment category" and "invoice payment SEQ" of the detailed advance payment data as keys. The invoice issuing unit 102c obtains the invoice subject classification for each management item of the same invoice number for the extracted invoice detail data by referring to the management item master 106d, and if there is an advance payment for the invoice subject classification and a sale, automatically issues an invoice including an invoice detail created based on the extracted invoice detail data and including the address, issuer, issuer registration number obtained from the sender master 106c, sales expense item, applicable month, invoice amount, total invoice amount, tax rate, total consumption tax, and total amount including tax, an advance payment settlement statement which is an advance payment detail created based on the extracted payment detail data and including the address, issuer, payee, payee registration number obtained from the business partner master 106b, expense item to be advanced, applicable month, amount, tax rate, consumption tax, and amount including tax, a copy of the invoice, and an advance payment detail.

Figure 8 shows an example of the invoice issuance screen. The invoice issuance screen has an output condition specification area for specifying output conditions such as the invoice issuance date, invoice code, property code, expected payment date, and invoice number, as well as a print button and a close button. When the output conditions are specified and the print button is pressed, the following process is executed according to the output conditions, and the invoice is printed out. Here, we will explain an example where the output conditions specified are an invoice issuance date of "2023/11/01-2023/11/30" and invoice code of "OW001: Owner A."

Billing detail data is extracted from the memory unit 106 based on the specified output conditions, and advance payment detail data is extracted using the "bill payment category" and "bill payment SEQ" of the extracted billing detail data as keys, and payment detail data is extracted using the "advance payment billing category" and "advance payment SEQ" of the advance payment detail data as keys.

Figure 9 (A) shows an example of billing detail data, Figure 9 (B) shows an example of advance payment detail data, and Figure 9 (C) shows an example of payment detail data.

In this example, billing statement data such as that shown in Figure 9 (A) is extracted using the invoice issue date "2023/11/01-2023/11/30" and billing destination code "OW001: Owner A" as keys. The billing statement data includes the following fields: billing payment category, billing payment SEQ, billing destination code, management item code, property code, invoice issue date, expected payment date, applicable month, base amount, consumption tax, amount including tax, tax category code, and invoice number.

In the example shown in the figure, the first line contains the following: billing payment category "1", billing payment SEQ "10", billing destination code "OW001: Owner A", management item code "K01: Management fee income", property code "BK01", invoice issue date "2023/11/10", expected payment date "2023/11/25", applicable month "2023/10", base amount "500,000", consumption tax "50,000", amount including tax "550,000", tax category code "21: 10%", and invoice number "100". The fourth line contains the following: billing payment category "1", billing payment SEQ "13", billing destination code "OW001: Owner A", management item code "K04: Advance payment", property code "BK01", invoice issue date "2023/11/10", expected payment date "2023/11/25", applicable month "2023/10", base amount "1,000,000", consumption tax "10,000", amount including tax "1,100,000", tax category code "21: 10%", invoice number "100".

The billing statement data's billing payment category "1" and billing payment sequence "13" are used as keys to extract the advance payment statement data shown in Figure 9 (B). The advance payment statement data is used to link the billing statement data with the payment statement data, and includes the following fields: billing payment category, billing payment sequence, advance payment statement billing payment category, and advance payment statement sequence.

In the example shown in the figure, the first line has a billing payment category of "1", a billing payment SEQ of "13", an advance payment billing payment category of "2", and an advance payment billing payment SEQ of "21", while the second line has a billing payment category of "1", a billing payment SEQ of "13", an advance payment billing payment category of "2", and an advance payment billing payment SEQ of "22".

Payment detail data such as that shown in Figure 9 (C) is extracted using the advance payment claim payment category "2" and advance payment claim payment SEQ "21" and "22" in the advance payment detail data as keys. The payment detail data (advance payment details) includes the advance payment claim payment category, advance payment claim payment SEQ, payee code, management item code, property code, payment date, applicable month, base amount, consumption tax, amount including tax, tax category code, and payment number.

In the example shown in the figure, the first line contains the following: advance payment claim payment category "2", advance payment claim payment SEQ "21", payee code "GY001: Contractor A", management item code "K04: Advance payment", property code "BK01", payment date "2023/10/31", applicable month "2023/10", base amount "500,000", consumption tax "50,000", amount including tax "550,000", tax category code "21: 10%", payment number "210 ", the second line has the following: advance payment claim category "2", advance payment claim payment SEQ "22", payee code "GY002: Contractor B", management item code "K04: Advance payment", property code "BK01", payment date "2023/10/31", applicable month "2023/10", base amount "500,000", consumption tax "50,000", amount including tax "550,000", tax category code "21: 10%", payment number "220".

For billing detail data, the system references the management item master 106d for each management item of the same invoice number to obtain the invoice subject classification, and generates judgment work data (intermediate data) including the billing payment classification, billing payment SEQ, billing destination code, management item code, and invoice subject classification, as shown in Figure 10 (D). It then determines whether invoice subject classifications are mixed.

1: If advance payments and other items (for example, 0: sales) are mixed, separate statements will be issued for each item separately from the invoice.

Figure 10 shows an example of an invoice to be issued. Figure 10(A) shows an example of an invoice (mirror) (not an invoice). The invoice (mirror) is created based on the invoice detail data. The invoice (mirror) has a header section and a details section. The header section contains the title (invoice in the example shown in the figure), invoice number, page number, destination (Owner A in the example shown in the figure), issuer (PM Real Estate in the example shown in the figure), and total invoice amount (¥2,200,000 in the example shown in the figure). The registration number is not listed. The details section contains all expense items, the relevant month, invoice amount for each expense item, total invoice amount, tax rate, total consumption tax, and total amount including tax.

Figure 10 (B) is a diagram showing an example of billing details (sales billing details, company registration number printed, invoice). Billing details are created for management items for which the invoice subject classification in the billing detail data is "0: Sales." Billing details have a header section and a detail section. The header section contains the title (in the example shown in the figure, billing details), invoice number, page number, destination (owner A), issuer, and the issuer's registration number obtained from the sender master 106c using the issuer as a key (T1000000000002 in the example shown in the figure). The detail section contains the sales expense item, the relevant month, the billing amount for each sales expense item, the total billing amount, the tax rate, the total consumption tax, and the total amount including tax.

Figure 10 (C) shows an example of an advance payment statement (a billing statement for an advance payment, not an invoice). An advance payment statement is created for a management item for which the invoice subject classification in the billing statement data is "1: Advance payment." An advance payment statement has a header section and a detail section. The header section contains the title (in the example shown in the figure, the advance payment statement), invoice number, page number, destination, and issuer. The detail section contains the advance payment item, applicable month, billing amount, total billing amount, tax rate, total consumption tax, and total amount including tax.

Figure 10 (D) shows an example of an advance payment settlement slip (details of advance payment, supplier registration number printed, invoice). An advance payment settlement slip is created for management items in the billing detail data with an invoice subject classification of "1: Advance," and for management items in the payment detail data linked by the advance payment detail data. An advance payment settlement slip has a header section and a detail section. The header section lists the title (in the example shown in the figure, an advance payment settlement slip), invoice number, page number, destination, and issuer. The detail section lists the payee (in the example shown in the figure, vendors A and B), the payee registration number (T1000000000003, 4 in the example shown in the figure) obtained from the customer master 106b using the payee as a key, the expense item (advance payment), the relevant month, amount, tax rate, consumption tax, and the amount including tax.

As explained above, this embodiment includes a management item master 106d that associates and registers management items with invoice subject categories including sales or advance payments, and an invoice issuance unit 102c that, when issuing an invoice, references the management item master and, if the invoice in question contains both advance payments for the invoice subject category and other management items, issues an invoice that includes advance payment details for the advance payment management item and billing details for the other management items. Therefore, if an invoice contains a mixture of advance payment subjects and other subjects, the invoice can be automatically split into advance payment and other subjects, and an invoice that meets the requirements of the invoice system can be issued, making it possible to reduce the workload and improve accuracy of billing operations associated with the invoice system.

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

Furthermore, this embodiment can contribute to reducing waste and promoting paperless and electronic systems, thereby contributing to SDGs goals 12, 13, and 15.

Furthermore, this embodiment can contribute to strengthening control and governance, thereby contributing to Goal 16 of the SDGs.

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

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

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

Furthermore, with regard to the bill issuing device 100, the components shown are functional concepts and do not necessarily have to be physically configured as shown.

For example, all or any part of the processing functions of the invoice issuing device 100, particularly the processing functions performed by the control unit, may be implemented by a CPU and a program interpreted and executed by the CPU, or may be implemented as hardware using wired logic. The program is recorded on a non-transitory, computer-readable recording medium containing programmed instructions for causing the information processing device to execute the processes described in this embodiment, and is mechanically read by the invoice issuing device 100 as needed. In other words, a computer program that works in conjunction with the OS to issue commands to the CPU and perform various processes is recorded in a storage unit such as a ROM or HDD (Hard Disk Drive). This computer program is executed by being loaded into RAM, and works in conjunction with the CPU to form the control unit.

In addition, this computer program may be stored on an application program server connected to the invoice issuing device 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-temporary computer-readable recording medium, or may be configured as a program product. Here, this "recording medium" includes memory cards, USB (Universal Serial Bus) memories, SD (Secure Digital) cards, flexible disks, magneto-optical disks, ROMs, EPROMs (Erasable Programmable Read Only Memory), EEPROMs (registered trademark) (Electrically Erasable and Programmable Read Only Memory), CD-ROMs (Compact Disk Read Only Memory), MOs (Magneto-Optical disks), DVDs (Digital Versatile Disks), and more. This includes any "portable physical media" such as a Blu-ray Disc (registered trademark) and a Blu-ray (registered trademark) Disc.

A "program" is a data processing method written in any language or description method, and may be in any format, such as source code or binary code. It should be noted that a "program" is not necessarily limited to a single structure, but also includes a distributed structure consisting of multiple modules or libraries, or a structure that achieves its function by working in conjunction with a separate program, such as an OS. The specific structure and reading procedure for reading a recording medium in each device shown in the embodiments, as well as the installation procedure after reading, can use well-known structures and procedures.

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

The invoice issuing device 100 may be configured as an information processing device such as a known personal computer or workstation, or may be configured as such an information processing device to which any peripheral device is connected. The invoice issuing device 100 may also be realized by installing software (including programs, data, etc.) that causes the device to perform 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 may be implemented in any combination, or embodiments may be implemented selectively.

REFERENCE SIGNS LIST 100 Invoice issuing device 102 Control unit 102a Master maintenance unit 102b Invoice processing unit 102c Invoice issuing unit 102d Screen display control unit 104 Communication interface unit 106 Storage unit 106a Item master 106b Customer master 106c Shipper master 106d Management item master 108 Input/output interface unit 112 Input device 114 Output device 200 Server 300 Network

Claims (6)

A bill issuing device that includes a control unit and allows an issuer to issue a bill,
The control unit
The system is configured to be able to access a management item master that associates management items with invoice subject classifications including sales or advance payments,
An invoice issuing device characterized by having an invoice issuing means that, when issuing an invoice, refers to the management item master, and if there are advance payment and sales management items in the invoice subject classification for the target invoice, issues an invoice including advance payment details for the advance payment management item and invoice details for the sales management item. The control unit further
A customer master that associates a customer with a registration number and registers it,
an issuer master in which issuers and registration numbers are associated and registered;
Invoice detail data including invoice payment category, invoice payment SEQ, invoice destination code, management item code, property code, invoice issue date, expected payment date, applicable month, base amount, consumption tax, amount including tax, tax category code, invoice number;
The billing statement data and the payment statement data are linked together, and the billing statement data includes a billing payment category, a billing payment sequence number, an advance payment billing payment category, and an advance payment billing payment sequence number.
Payment details data including the advance payment claim payment category, advance payment claim payment SEQ, payee code, management item code, property code, payment date, applicable month, base amount, consumption tax, amount including tax, tax category code, and payment number;
It is configured to be accessible to
The bill issuing means
Extracting billing detail data based on the specified output conditions, extracting advance payment detail data using the "bill payment category" and "bill payment SEQ" of the extracted billing detail data as keys, and extracting payment detail data using the "advance payment billing payment category" and "advance payment SEQ" of the advance payment detail data as keys,
The invoice issuing device of claim 1, characterized in that for the extracted invoice detail data, the management item master is referenced to obtain the invoice subject classification for each management item of the same invoice number, and if the invoice subject classifications ``advance payment'' and ``sales'' exist, an invoice is issued that includes an invoice detail created based on the extracted invoice detail data and including the destination, issuer, issuer registration number obtained from the issuer master, sales expense item, applicable month, invoice amount, total invoice amount, tax rate, total consumption tax, and total amount including tax, and an advance payment settlement statement which is an advance payment detail created based on the extracted payment detail data and including the destination, issuer, payee, payee registration number obtained from the business partner master, advance payment expense item, applicable month, amount, tax rate, consumption tax, and amount including tax. The invoice issuing device of claim 2, characterized in that the invoice includes an invoice mirror created based on the extracted invoice detail data and listing the recipient, issuer, total invoice amount, all expense items, the relevant month, invoice amount, total invoice amount, tax rate, total consumption tax, and total amount including tax, and an advance detail created based on the extracted invoice detail data and listing the recipient, issuer, expense items to be advanced, the relevant month, amount, total amount, tax rate, total consumption tax, and total amount including tax. The invoice issuing device described in any one of claims 1 to 3, characterized in that the issuer includes a real estate management company. An invoice issuing method executed by an information processing device having a control unit,
The control unit
The system is configured to be able to access a management item master that associates management items with invoice subject classifications including sales or advance payments,
Executed in the control unit:
An invoice issuance method characterized by including an invoice issuance means that, when issuing an invoice, refers to the management item master, and if there are advance payment and sales management items in the invoice subject classification for the target invoice, issues an invoice including advance payment details for the advance payment management item and invoice details for the sales management item. An invoice issuing program to be executed by an information processing device having a control unit,
An invoice issuing method executed by an information processing device having a control unit,
The control unit
The system is configured to be able to access a management item master that associates management items with invoice subject classifications including sales or advance payments,
In the control unit,
An invoice issuance program for executing an invoice issuance process that, when issuing an invoice, refers to the management item master and, if there are advance payment and sales management items in the invoice subject classification for the target invoice, issues an invoice including advance payment details for the advance payment management item and invoice details for the sales management item.