Invoice processing device, invoice processing method, and invoice processing program

Abstract

To provide an invoice processing device for automatically issuing an invoice corresponding to an invoice system without making an operator issuing the invoice aware of a registration date of an owner in a management company.SOLUTION: An invoice processing device includes: billing confirmation means, when billing detail data is confirmed, referring to a client master, and when details for the current month before a registration date of a client in an equity ratio master associated with an equity ratio code and details for the current month after the registration date are mixed in a same billing identification code, updating the details to a billing identification code different from the same billing identification code and confirming it; and invoice issuing means for issuing an invoice by billing identification code unit based on the confirmed billing detail data, at that time, referring to the client master to acquire a client registration number and registration date of the equity ratio master associated with the equity ratio code, in a case of (registration date)≤(current month), printing the registration number of the client, and in a case of (registration date)>(current month), not printing the registration number of the client.SELECTED DRAWING: Figure 3

Description

[Technical Field]

[0001] The present invention relates to a bill processing device, a bill processing method, and a bill processing program. [Background technology]

[0002] For example, in the real estate industry, there are various contract types, such as company ownership, sublease, and entrusted management, depending on the type of property ownership. Under the method for storing qualified invoices under the invoice system that will be introduced on October 1, 2023, if a qualified invoice issuing business registers after the system's start date (October 1, 2023), it will not be able to issue qualified invoices for transactions that occurred after the system's start date but before the date of registration. Previously, systems that comply with the invoice system include, for example, Patent Document 1. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Laid-Open No. 2023-38949 Summary of the Invention [Problem to be solved by the invention]

[0004] However, the above-mentioned Patent Document 1 does not state anything about enabling the operator at the management company who issues the invoice to issue an invoice that complies with the invoice system without being aware of the owner's registration date.

[0005] The present invention has been made in consideration of the above, and aims to provide an invoice processing device, an invoice processing method, and an invoice processing program that enable an operator at a management company who issues invoices to issue invoices that comply with the invoice system without having to be aware of the owner's registration date. [Means for solving the problem]

[0006] In order to solve the above-mentioned problems and achieve the object, the present invention provides an invoice processing device that includes a control unit and allows a management company to issue invoices on behalf of an owner, the control unit being configured to be able to access a memory area that stores a customer master that associates and registers customer, registration number of qualified invoice issuer, and registration date, and an ownership ratio master that associates and registers property, ownership ratio code, customer including owner, and ownership ratio, invoice registration means that inputs and registers in the memory area detailed invoice data including invoice destination, management item, property, ownership ratio code, relevant month, base amount, consumption tax, amount including tax, and invoice unit, and a invoice identification code that specifies the invoice unit, and a billing registration means that inputs and registers in the memory area detailed invoice data including invoice destination, management item, property, ownership ratio code, relevant month, base amount, consumption tax, amount including tax, and invoice unit, and a billing identification code that specifies the invoice unit, and a billing registration means that inputs and registers in the memory area detailed invoice data at the time of invoice confirmation, the ... and a billing confirmation means for referring to the business partner master and, if there is a mixture of details for the month before the registration date of the business partner in the equity ratio master linked to the equity ratio code with the same billing identification code and details for the month after the registration date, updating and confirming the details to a billing identification code different from the same billing identification code; and an invoice issuing means for issuing an invoice for each billing identification code based on the confirmed billing detail data, and at that time, referencing the business partner master to obtain the registration number and registration date of the business partner in the equity ratio master linked to the equity ratio code, and printing the registration number of the business partner if the registration date is less than or equal to the month, and not printing the registration number of the business partner if the registration date is greater than the month.

[0007] Furthermore, according to one aspect of the present invention, when the billing detail data registered in the storage area is billed, if there are multiple business partners in the ownership ratio master linked to the ownership ratio code for the billing detail data, the billing confirmation means may divide the details for each business partner, create billing detail apportionment data in which the amount is apportioned according to the ownership ratio of the business partner in the ownership ratio master, and register the data in the storage area.

[0008] In addition, according to one aspect of the present invention, the billing confirmation means may further refer to the customer master for the billing detail allocation data, and if there is a detail with the same billing identification code for the month prior to the registration date of the customer in the ownership ratio master linked to the ownership ratio code, update the detail to a billing identification code other than the same billing identification code.

[0009] Furthermore, according to one aspect of the present invention, when issuing an invoice, if invoice detail allocation data is available, the invoice issuance means may issue the invoice based on the invoice detail allocation data, and otherwise issue the invoice based on the invoice detail data.

[0010] In order to solve the above-mentioned problems and achieve the object, the present invention provides an invoice processing method executed by an information processing device having a control unit, wherein the control unit is configured to be able to access a memory area storing a customer master in which customer, registration number of qualified invoice issuer, and registration date are associated and registered, and an ownership ratio master in which property, ownership ratio code, customer including owner, and ownership ratio are associated and registered, and a invoice registration step executed by the control unit to input and register in the memory area invoice detail data including invoice destination, management item, property, ownership ratio code, relevant month, base amount, consumption tax, amount including tax, and invoice identification code specifying invoice unit; The method includes an invoice confirmation step of, at the time of confirmation, referring to the business partner master, and if there is a mixture of details for the month before the registration date of the business partner in the equity ratio master linked to the equity ratio code with the same invoice identification code and details for the month after the registration date, updating the details to a different invoice identification code from the same invoice identification code and confirming them; and an invoice issuing step of issuing an invoice for each invoice identification code based on the confirmed invoice detail data, referring to the business partner master to obtain the registration number and registration date of the business partner in the equity ratio master linked to the equity ratio code, and printing the registration number of the business partner if the registration date is less than or equal to the month, and not printing the registration number of the business partner if the registration date is greater than the month.

[0011] In order to solve the above-mentioned problems and achieve the object, the present invention provides an invoice processing program to be executed by an information processing device having a control unit, the control unit being configured to be able to access a memory area storing a customer master in which customer, registration number of qualified invoice issuer, and registration date are associated and registered, and an ownership ratio master in which property, ownership ratio code, customer including owner, and ownership ratio are associated and registered, the control unit including a billing registration step of inputting billing detail data including billing destination, management item, property, ownership ratio code, relevant month, base amount, consumption tax, amount including tax, and billing identification code specifying invoice unit, and registering the input data in the memory area; and an invoice confirmation step of referring to the customer master and, if there is a mixture of details for the month before the registration date of the customer in the equity ratio master linked to the equity ratio code, and details for the month after the registration date, updating and confirming the details to a different invoice identification code from the same invoice identification code; and issuing an invoice for each invoice identification code based on the confirmed invoice detail data, and in doing so, referring to the customer master to obtain the customer registration number and registration date in the equity ratio master linked to the equity ratio code, and printing the customer registration number if the registration date is less than or equal to the month, and not printing the customer registration number if the registration date is greater than the month. [Effects of the Invention]

[0012] According to the present invention, an operator at a management company who issues invoices can issue invoices that comply with the invoice system without having to be aware of the owner's registration date. [Brief explanation of the drawings]

[0013] [Figure 1] FIG. 1 is a diagram for explaining qualified invoices. [Figure 2] Figure 2 shows a transaction diagram for the special intermediary delivery exemption. [Figure 3]FIG. 3 is a diagram showing an example of the configuration of the invoice processing device according to this embodiment. [Figure 4] FIG. 4 is a diagram showing the relationship between the billing statement data, the ownership ratio master, and the customer master. [Figure 5] FIG. 5 is a diagram showing the relationship between the billing statement data, billing statement allocation data, and ownership ratio master. [Figure 6] FIG. 6 is a diagram illustrating an example of the configuration of the supplier master. [Figure 7] FIG. 7 is a diagram illustrating an example of the configuration of the management item master. [Figure 8] FIG. 8 is a diagram illustrating an example of the configuration of the property master. [Figure 9] FIG. 9 is a diagram illustrating an example of the configuration of the ownership ratio master. [Figure 10] FIG. 10 is a flow diagram showing an example of the overall processing of the invoice processing device according to this embodiment. [Figure 11] FIG. 11 is a diagram for explaining a specific example of processing by the control unit of the invoice processing device according to this embodiment. [Figure 12] FIG. 12 is a diagram for explaining a specific example of processing by the control unit of the invoice processing device according to this embodiment. [Figure 13] FIG. 13 is a diagram for explaining a specific example of processing by the control unit of the invoice processing device according to this embodiment. [Figure 14] FIG. 14 is a diagram for explaining a specific example of processing by the control unit of the invoice processing device according to this embodiment. [Figure 15] FIG. 15 is a diagram for explaining a specific example of processing by the control unit of the invoice processing device according to this embodiment. [Figure 16] FIG. 16 is a diagram for explaining a specific example of processing by the control unit of the invoice processing device according to this embodiment. [Figure 17] FIG. 17 is a diagram for explaining a specific example of processing by the control unit of the invoice processing device according to this embodiment. [Figure 18] FIG. 18 is a diagram for explaining a specific example of processing by the control unit of the invoice processing device according to this embodiment. [Figure 19] FIG. 19 is a diagram for explaining a specific example of processing by the control unit of the invoice processing device according to this embodiment. [Figure 20] FIG. 20 is a diagram for explaining a specific example of processing by the control unit of the invoice processing device according to this embodiment. [Figure 21] FIG. 21 is a diagram for explaining a specific example of processing by the control unit of the invoice processing device according to this embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0014] Hereinafter, embodiments of a bill processing device, a bill processing method, and a bill processing program according to the present invention will be described in detail with reference to the accompanying drawings. However, the present invention is not limited to these embodiments.

[0015] [1. Overview] An overview of the present invention will be explained with reference to Figures 1 and 2. For example, in the real estate industry, there are various contract types, such as company ownership, sublease, and entrusted management, depending on the type of property ownership. Under the qualified invoice storage method of the invoice system that will be introduced on October 1, 2023, if a qualified invoice issuing business registers after the system's start date (October 1, 2023), it will not be able to issue qualified invoices for transactions that occur after the system's start date but before the registration date. Therefore, for invoices that span the registration date, it is necessary to separate transactions before and after the registration date and include them on the invoice, etc.

[0016] Figure 1 is a diagram explaining qualified invoices. If a qualified invoice issuer is registered after the system start date (October 1, 2023), they cannot issue qualified invoices for transactions prior to the registration date. For example, in a management contract, if the electricity charges are for October and the owner's registration date is November 1, 2023, they cannot issue a qualified invoice that includes the October electricity charges; they must separate the qualified invoice for November from the invoice for the October electricity charges.

[0017] In the case of entrusted management, the management company issues the invoice on behalf of the owner (proxy) (Issuance). Figure 2 is a transaction diagram for the special exception for issuance by an intermediary. Both the trustor (owner) and the trustee (management company) must be qualified invoice issuers. The trustee (management company) can issue a qualified invoice to the purchaser (tenant) that lists its name and registration number. The trustee (management company) must also provide a copy of the issued qualified invoice to the trustor (owner) (the trustee (management company) is also obligated to keep it). The trustor (owner) is obligated to keep a copy of the qualified invoice issued to them by the trustee (management company).

[0018] Management companies face the challenge of determining whether or not to issue qualified invoices for transactions that occurred before and after the owner's registration as a qualified invoice issuing business, which creates a heavy workload.

[0019] Therefore, in this embodiment, it is possible to automatically issue invoices that comply with the invoice system in accordance with the date of registration of the owner as a qualified invoice issuing business in the case of entrusted management.

[0020] Specifically, in this embodiment, in order to prevent transactions before and after the date of registration of the owner's qualified invoice issuer registration from being issued together on the same invoice, the invoice information before and after the registration date is automatically separated and the invoices are output separately.

[0021] In this embodiment, an invoice group code is assigned to the billing information for unregistered business owners, enabling them to be issued separately from qualified invoices. When outputting invoices for multiple owners, the invoices are divided for each owner.

[0022] This embodiment is equipped with the following functions. When a bill is finalized, if transactions before and after the owner's registration date are mixed in the same bill in the billing detail data created from the contract information of the management outsourcing, the billing group code and billing identification code are updated. At this time, if there are multiple owners, the update is made for each owner. Invoices with different billing group codes and billing identification codes are output separately from the billing detail data.

[0023] According to this embodiment, when issuing qualified invoices on behalf of an entrusted management company, the operator who issues the invoices can automatically split and issue invoices with details for periods when multiple owners were unregistered businesses, without the operator having to be aware of the registration of each owner as a qualified invoice issuer. Also, because the operator who issues the invoices does not need to determine the registration dates of multiple owners as qualified invoice issuers, it is possible to reduce the workload and input errors.

[0024] [2. Configuration] An example of the configuration of the invoice processing device according to this embodiment will be described with reference to FIG. 3 and other figures. The invoice processing device according to this embodiment can be suitably used, for example, in real estate management companies (including PM companies), etc. Fig. 3 is a block diagram showing an example of the configuration of an invoice processing device 100 according to this embodiment.

[0025] The invoice processing device 100 is a commercially available desktop personal computer. Note that the invoice processing device 100 is not limited to a stationary information processing device such as a desktop personal computer, but may also be a portable information processing device such as a commercially available notebook personal computer, PDA (Personal Digital Assistant), smartphone, or tablet personal computer.

[0026] The invoice processing 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 processing device 100 is connected to each other so that they can communicate with each other via any communication path.

[0027] The communication interface unit 104 communicatively connects the invoice processing 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 the communication line. Here, the network 300 has the function of connecting the invoice processing 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).

[0028] 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 cooperates with a mouse to achieve a pointing device function. Note that, hereinafter, 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 a "user operation via a UI."

[0029] Various databases, tables, files, etc. are stored in the storage unit 106. Computer programs that work in conjunction with an OS (Operating System) to issue commands to a CPU (Central Processing Unit) to perform various processes are recorded in the storage unit 106. The storage unit 106 can be, 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.

[0030] The storage unit 106 stores, for example, a business partner master 106a, a management item master 106b, a property master 106c, an ownership ratio master 106d, billing statement data, billing statement apportionment data, etc. FIG. 4 is a diagram showing the relationship between the billing statement data, the ownership ratio master 106d, and the business partner master 106a. FIG. 5 is a diagram showing the relationship between the billing statement data, the billing statement apportionment data, and the ownership ratio master 106d. FIG. 6 is a diagram showing an example of the configuration of the business partner master 106a. FIG. 7 is a diagram showing an example of the configuration of the management item master 106b. FIG. 8 is a diagram showing an example of the configuration of the property master 106c. FIG. 9 is a diagram showing an example of the configuration of the ownership ratio master 106d.

[0031] The supplier master 106a is a master for supplier information, and can be configured as a table in which supplier codes, supplier names, and registration numbers (qualified bill issuer registration numbers) are associated and registered, as shown in FIG. 6.

[0032] In the example shown in the same figure, the first line has the customer code "T00001," customer name "Tenant A," registration number "T1000000000001," and registration date "2023 / 10 / 1," the second line has the customer code "T00002," customer name "Owner B," registration number "T1000000000002," and registration date "2023 / 11 / 1," the third line has the customer code "T00003," customer name "Owner C," registration number "T1000000000003," and registration date "2023 / 12 / 1," and the fourth line has the customer code "T00009," customer name "Our company (PM Real Estate)," registration number "T1000000000009," and registration date "2023 / 10 / 1."

[0033] The management item master 106b is a master for managing billing management items, and can be configured as a table in which management item codes and management item names are registered in association with each other, as shown in Figure 7. The management item master 106b is referenced when converting management item codes and management item names. In the example shown in the figure, the first line has the management item code "K01" and the management item name "office rent," the second line has the management item code "K02" and the management item name "common area charges," and the third line has the management item code "K03" and the management item name "electricity charges."

[0034] The property master 106c is a master for managing property information, and can be configured as a table in which property codes and property names are associated and registered, as shown in Fig. 8. The property master 106c is referenced when converting property codes and property names. In the example shown in the figure, the property code is "1001" and the property name is "OB Building."

[0035] The ownership ratio master 106d is a master for managing the ownership ratios of properties, and can be configured with a table in which property codes, ownership ratio codes, constituent customer codes, and ownership ratios are associated and registered, as shown in Fig. 9. In the example shown in Fig. 9, the first line contains the property code "1001," ownership ratio code "01," constituent customer code "T00002," and ownership ratio "100," the second line contains the property code "1001," ownership ratio code "02," constituent customer code "T00009," and ownership ratio "100," the third line contains the property code "1001," ownership ratio code "03," constituent customer code "T00002," and ratio "60," and the fourth line contains the property code "1001," ownership ratio code "03," constituent customer code "T00003," and ownership ratio "40."

[0036] The billing detail data may include a billing sequence number, billing destination code, management item code, property code, ownership ratio code, applicable month, base amount, consumption tax, tax-inclusive amount, billing group code, and a billing identification code that defines the billing unit (the unit for consolidating bills into one sheet) (see Figure 13).

[0037] The billing detail allocation data may include a billing sequence number, an owner code (customer code), a base amount, consumption tax, a tax-inclusive amount, a billing group code, and a billing identification code (see FIG. 14).

[0038] As shown in FIG. 4, the billing statement data and the ownership ratio master 106d are linked by the property code and ownership ratio code, and the ownership ratio master 106d and the customer master 106a are linked by the customer code.

[0039] As shown in FIG. 5, the billing detail data and the billing detail apportionment data are linked by the billing sequence number, and the billing detail apportionment data and the ownership ratio master 106d are linked by the customer code.

[0040] Returning to Figure 3, the control unit 102 is a CPU or the like that provides overall control of the invoice processing device 100. 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 executes various information processing operations based on these stored programs.

[0041] The control unit 102 is configured to be able to access the business partner master 106a, management item master 106b, property master 106c, ownership ratio master 106d, billing statement data, billing statement apportionment data, etc., stored in the storage unit 106. Note that the business partner master 106a, management item master 106b, property master 106c, ownership ratio master 106d, billing statement data, billing statement apportionment data, etc. may be stored in another location (for example, server 200) as long as the control unit 102 is able to access them.

[0042] The control unit 102 conceptually includes a billing registration unit 102a, a billing data determination unit 102b, a bill issuing unit 102c, a master maintenance unit 102d, and a screen display control unit 102e.

[0043] The billing registration unit 102a inputs billing detail data including the billing sequence, billing destination, management item, property, ownership ratio code, applicable month, base amount, consumption tax, tax-inclusive amount, billing group code, and billing identification code that defines the billing unit, in response to, for example, an operator's operation on the variable billing registration screen displayed on the monitor 114, and registers the data in the memory unit 106.

[0044] For example, in response to an operator's operation on the billing data confirmation screen displayed on the monitor 114, the billing data confirmation unit 102b refers to the customer master 106a for the billing detail data registered in the memory unit 106 at the time of billing confirmation (for example, the billing closing date), and if there is a mixture of details for the month before the registration date of the customer in the ownership ratio master 106d linked to the same billing identification code and details for the month after the registration date, the billing data confirmation unit 102b updates the details to a billing identification code different from the same billing identification code and confirms them.

[0045] In addition, when finalizing the billing of billing detail data registered in the memory unit 106, if there are multiple business partners in the ownership ratio master 106d linked to the ownership ratio code for the billing detail data, the billing data finalization unit 102b may divide the details for each business partner, create billing detail allocation data in which the amount is prorated according to the ownership ratio of the business partner in the ownership ratio master 106d, and register this in the memory unit 106.

[0046] Furthermore, the billing data determination unit 102b may further refer to the customer master 106a for the billing detail allocation data, and if there is a detail for the month before the customer registration date in the ownership ratio master 106d linked to the ownership ratio code with the same billing identification code, update that detail to a billing identification code other than the same billing identification code.

[0047] The invoice issuing unit 102c issues an invoice for each invoice identification code based on the confirmed invoice detail data, for example, in response to an operator's operation on the invoice issuance screen displayed on the monitor 114, and at that time, refers to the customer master 106a to obtain the customer registration number and registration date in the ownership ratio master 106d linked to the ownership ratio code, and if the registration date is less than or equal to the relevant month, prints the customer registration number, and if the registration date is greater than or equal to the relevant month, does not print the customer registration number.

[0048] In addition, when issuing an invoice, the invoice issuing unit 103c may issue the invoice based on the invoice detail allocation data if the invoice detail allocation data is available, and otherwise issue the invoice based on the invoice detail data.

[0049] The master maintenance unit 102d performs editing such as registering, updating, adding, and deleting data in the customer master 106a, the management item master 106b, the property master 106c, and the ownership ratio master 106d, for example, in response to an operator's operation on a master maintenance screen (not shown) displayed on the monitor 114.

[0050] The screen display control unit 102e controls the display of various screens (for example, a master maintenance screen, a variable billing registration screen, a billing data confirmation screen, a billing issuance screen, etc.) displayed on the monitor 114 and the inputs thereto.

[0051] [3. Specific Examples] Specific examples of the processing performed by the control unit 102 of the invoice processing device 100 in this embodiment will be described with reference to Figures 3 to 21. Figures 10 to 21 are diagrams for explaining specific examples of the processing performed by the control unit 102 of the invoice processing device 100 in this embodiment.

[0052] [3-1. Overall processing] Fig. 10 is a diagram showing a flow for explaining an outline of the overall processing of the control unit 102 of the invoice processing device 100 in this embodiment. Fig. 11 is a diagram showing a display example of a variable invoice registration screen. Fig. 12 is a diagram showing a display example of a invoice data registration screen.

[0053] In FIG. 10, the billing registration unit 102a executes a variable billing registration process (step S1). In the variable billing registration process, billing detail data is created. Specifically, in the variable billing registration process, the billing registration unit 102a inputs billing detail data including the billing sequence, billing destination, management item, property, ownership ratio code, applicable month, base amount, consumption tax, tax-inclusive amount, billing group code, and billing identification code that defines the billing unit, in response to, for example, an operator's operation on the variable billing registration screen displayed on the monitor 114, and registers the data in the storage unit 106. Note that the billing detail data may also be imported from an external source.

[0054] The billing data confirmation unit 102b executes the billing data confirmation process (step S2). The billing data confirmation process is a process for confirming the unit for issuing an invoice, and if there are multiple business partners in the ownership ratio, it creates billing detail allocation data, and if an invoice is to be issued that spans the owner registration date, it updates the billing detail data for the period when the owner was not registered.

[0055] Specifically, in the billing data confirmation process, the billing data confirmation unit 102b, for example, in response to an operator's operation on the billing data confirmation screen displayed on the monitor 114, refers to the customer master 106a for the billing detail data registered in the memory unit 106 at the time of billing confirmation (for example, the billing closing date), and if there is a mixture of details for the month before the registration date of the customer in the ownership ratio master 106d linked to the same billing identification code and details for the month after the registration date, updates the details to a billing identification code different from the same billing identification code and confirms them.

[0056] In addition, when finalizing the billing of billing detail data registered in the memory unit 106, if there are multiple business partners in the ownership ratio master 106d linked to the ownership ratio code for the billing detail data, the billing data finalization unit 102b may divide the details for each business partner, create billing detail allocation data in which the amount is prorated according to the ownership ratio of the business partner in the ownership ratio master 106d, and register this in the memory unit 106.

[0057] Furthermore, the billing data determination unit 102b may further refer to the customer master 106a for the billing detail allocation data, and if there is a detail for the month before the customer registration date in the ownership ratio master 106d linked to the ownership ratio code with the same billing identification code, update that detail to a billing identification code other than the same billing identification code.

[0058] The invoice issuing unit 102c executes the invoice issuance process (step S3). Specifically, in the invoice issuance process, the invoice issuing unit 102c issues an invoice for each invoice identification code based on the confirmed invoice detail data, for example, in response to an operator's operation on the invoice issuance screen displayed on the monitor 114. In doing so, the invoice issuing unit 102c references the supplier master 106a to obtain the supplier registration number and registration date in the ownership ratio master 106d linked to the ownership ratio code, and if the registration date is less than or equal to the relevant month, prints the supplier registration number (qualified invoice), but if the registration date is greater than or equal to the relevant month, does not print the supplier registration number (invoice).

[0059] In addition, when issuing an invoice, the invoice issuing unit 103c may issue the invoice based on the invoice detail allocation data if the invoice detail allocation data is available, and otherwise issue the invoice based on the invoice detail data.

[0060] [3-2. Sample Data] 13 to 21 are diagrams showing sample data for explaining a specific example of the processing by the control unit 102 of the invoice processing device 100 in this embodiment. A specific example of the processing by the control unit 102 of the invoice processing device 100 in this embodiment will be described with reference to FIGS. 13 to 21. Below, an example will be described in which the master configuration examples shown in FIGS. 6 to 9 are used.

[0061] (S1: Variable billing registration process) The variable billing registration process will be described with reference to Figures 13 and 14. The billing registration unit 102a inputs billing detail data including the billing sequence, billing destination, management item, property, ownership ratio code, applicable month, base amount, consumption tax, tax-inclusive amount, billing group code, and billing identification code that defines the billing unit, in response to, for example, an operator's operation on the variable billing registration screen displayed on the monitor 114, and registers the data in the storage unit 106.

[0062] 13A shows an example of billing detail data. The billing detail data includes the following fields: billing sequence number, billing destination code, management item code, property code, ownership ratio code, applicable month, base amount, consumption tax, amount including tax, billing group code, and billing identification code.

[0063] Invoice detail data with the same invoice identification code is compiled into one invoice. The invoice identification code is automatically updated when the items that compile the invoice, such as the invoice destination code, property code, or invoice group code, are updated.

[0064] In the example shown in the same figure, for example, lines 4 to 6 have the billing identification code "B001", and line 4 has the billing SEQ "103", billing destination code "T00001: Tenant A", management item code "K01: Office rent", property code "1001", ownership ratio code "01", applicable month "2023 / 11", base amount "100,000", consumption tax "10,000", amount including tax "110,000", and billing identification code "B001". The fifth line has the billing sequence number "104," billing code "T00001: Tenant A," management item code "K02: Common area fee," property code "1001," ownership percentage code "01," applicable month "2023 / 11," base amount "100,000," consumption tax "10,000," amount including tax "110,000," and billing identification code "B001." The sixth line has the billing sequence number "105," billing code "T00001: Tenant A," management item code "K03: Electricity," property code "1001," ownership percentage code "01," applicable month "2023 / 10," base amount "50,000," consumption tax "5,000," amount including tax "55,000," and billing identification code "B001." If the billing identification code is "B001", the electricity bill is the only transaction that occurred during a period when Owner B was not registered.

[0065] For example, lines 13 to 15 have a billing identification code of "E001", and line 13 has a billing sequence of "112", billing destination code "T00001: Tenant A", management item code "K01: Office rent", property code "1001", ownership ratio code "03", applicable month "2023 / 12", base amount "100,000", consumption tax "10,000", amount including tax "110,000", and billing identification code "E001". The 14th line contains the billing sequence number "113," billing destination code "T00001: Tenant A," management item code "K02: Common area fee," property code "1001," ownership percentage code "03," applicable month "2023 / 12," base amount "100,000," consumption tax "10,000," amount including tax "110,000," and billing identification code "E001." The 15th line contains the billing sequence number "114," billing destination code "T00001: Tenant A," management item code "K03: Electricity," property code "1001," ownership percentage code "03," applicable month "2023 / 11," base amount "50,000," consumption tax "5,000," amount including tax "55,000," and billing identification code "E001." If the billing identification code is "E001", all of Owner B's transactions are for the registered business period, while Owner C's only electricity bill is for the unregistered period.

[0066] Figure 13(B) is a diagram for explaining the format of the invoice for each invoice identification code in the invoice detail data of Figure 13(A). Invoice identification code "A001" is issued on behalf of Owner B, with all details for the registered provider period. Invoice identification code "B001" is issued on behalf of Owner B, with only the electricity bill being a detail for the unregistered provider period. Invoice identification code "C001" is issued on behalf of Owner B, with all details for the unregistered provider period. Invoice identification code "D001" is an invoice for the company's own account, with all details for the registered provider period. Invoice identification code "E001" is issued on behalf of Owners B and C, with only Owner C's electricity bill being a detail for the unregistered provider period.

[0067] (S2: Billing data confirmation process) A specific example of the billing data confirmation process will be described with reference to Figures 14 and 15. In the billing data confirmation process, the billing detail data is updated and the billing detail apportionment data is created and updated.

[0068] (Creating billing details allocation data) When the billing detail data registered in the memory unit 106 is confirmed (when the billing data confirmation is executed, for example, on the billing closing date), if there are multiple business partners in the ownership ratio master 106d linked to the ownership ratio code for the billing detail data, the billing data confirmation unit 102b divides the details for each business partner, creates billing detail allocation data in which the amount is prorated according to the ownership ratio of the business partner in the ownership ratio master 106d, and registers the data in the memory unit 106.

[0069] If there are multiple owners (multiple constituent business partners in the ownership ratio) when the invoice data is finalized, the invoice detail allocation data is created based on the invoice detail data. Specifically, if there are multiple constituent business partner codes (owner codes) in the ownership ratio master 106d linked to the ownership ratio code in the invoice detail data, the invoice detail data is divided for each constituent business partner code, and the amount is allocated proportionally according to the ownership ratio of the corresponding constituent business partner code in the ownership ratio master 106d.

[0070] Figure 14 is a diagram showing an example of billing statement allocation data created for the billing statement data of Figure 13(A). The billing statement allocation data includes the following fields: billing sequence number, owner code, base amount, consumption tax, tax-inclusive amount, billing group code, and billing identification code. In the case of the billing statement data of Figure 13(A), when the ownership ratio code is "03," there are multiple constituent customer codes (T00002, T00003) in the ownership ratio master 106d of Figure 9, so billing statement allocation data is created. In the ownership ratio master 106d of Figure 9, for the property code "1001" and ownership ratio code "03," the constituent customer code is "T00002," the ownership ratio is "60," the constituent customer code is "T00003," and the ratio is "40."

[0071] In the example shown in the same figure, for example, for billing SEQ "112," the first line contains billing SEQ "112," owner code "T00002: Owner B," amount "60,000 (= 100,000 x 60 / (60 + 40))," consumption tax "6,000," amount including tax "66,000," and billing identification code "E001." The second line contains billing SEQ "112," owner code "T00003: Owner C," amount "40,000 (= 100,000 x 40 / (40 + 60))," consumption tax "4,000," amount including tax "44,000," and billing identification code "E001."

[0072] Also, for billing sequence number "114," the fifth line contains billing sequence number "114," owner code "T00002: Owner B," amount "30,000 (=500,000 x 60 / (60+40))," consumption tax "3,000," amount including tax "33,000," and billing identification code "E001." The sixth line contains billing sequence number "114," owner code "T00003: Owner C," amount "20,000 (=100,000 x 40 / (40+60))," consumption tax "2,000," amount including tax "22,000," and billing identification code "E001."

[0073] (Update the invoice group code and invoice identification code for the invoice detail data and invoice detail allocation data) When the billing data is finalized (for example, on the billing closing date), the billing data finalization unit 102b refers to the customer master 106a for the billing detail data registered in the memory unit 106, and if there is a mixture of details for the month before the registration date of the customer in the ownership ratio master 106d linked to the same billing identification code and details for the month after the registration date, the billing data finalization unit 102b updates the details to a billing identification code different from the same billing identification code and finalizes them.

[0074] Referring to Figure 15, this is a diagram for explaining the case where billing detail data is updated when billing data is finalized. Figure 15 shows the billing detail data of Figure 13(A) after updating. When billing data is finalized, the following billing detail data is updated.

[0075] The conditions for updating billing details data are as follows: (1) Billing statement allocation data does not exist (billing statement allocation data will be processed separately) (2) For the same billing identification code (same bill), there are multiple corresponding months that overlap the registration date of the constituent business partners (owners) linked to the ownership ratio code (MIN corresponding month < registration date ≦ MAX corresponding month). (3) Details of the period when the constituent trading partner (owner) linked to the ownership ratio code was an unregistered business operator with the same billing identification code (same bill) (relevant month < registration date)

[0076] In the example shown in Figure 15, the details for billing identification code "B001" and management item code "K03: Electricity" for billing SEQ "105" on line 6 meet the update conditions (of the three details for billing identification code "B001," billing SEQ "105" has owner B's registration date "2023 / 11 / 01" > the corresponding month for management item code "K03: Electricity" is "2023 / 10"), so the bill group code is updated to "I" and the billing identification code is updated to "B002" at the same time. As a result, the details on lines 4 and 5 and the details for billing identification code "B001" and management item code "K03: Electricity" for billing SEQ "105" on line 6 become separate invoices.

[0077] Furthermore, the billing data determination unit 102b further refers to the customer master 106a for the billing detail allocation data, and if there is a detail for the relevant month before the customer registration date in the customer ownership ratio master 106d linked to the ownership ratio code with the same billing identification code, it updates the detail to a billing identification code different from the same billing identification code.

[0078] Referring to Figure 16, this is a diagram for explaining the case where billing detail allocation data is updated when billing data is finalized. Figure 16 shows the billing detail allocation data of Figure 14 after it has been updated. When billing data is finalized, the following billing detail allocation data is updated.

[0079] The conditions for updating billing details are as follows: (1) The same invoice identification code (same invoice) contains a mixture of months that overlap the registration date of the constituent business partners (owners) linked to the ownership ratio code (MIN applicable month < registration date ≦ MAX applicable month). (2) Details of the period when the constituent trading partner (owner) linked to the ownership ratio code was an unregistered business entity with the same billing identification code (same bill) (relevant month < registration date)

[0080] In the example shown in Figure 16, the details of the billing identification code "E001" of the billing sequence "114" on the sixth line and the management item code "K03: Electricity charge" of the owner code "T00003: Owner C" meet the update conditions (Owner C of billing sequence "114" has Owner C's registration date "2023 / 12 / 01" > the corresponding month of the management item code "K03: Electricity charge" "2023 / 11"), so the bill group code is updated to "I" and the billing identification code is updated to "E002" at the same time.

[0081] (S3: Invoice issuance process) A specific example of the invoice issuance process will be described with reference to Figures 17 to 21. Figures 17 to 21 are diagrams showing an example of invoice issuance based on the invoice detail data in Figure 15 and the invoice detail apportionment data in Figure 16.

[0082] The invoice issuing unit 102c issues invoices for each invoice identification code based on the confirmed invoice detail data, for example, in response to operator operations on the invoice issuance screen displayed on the monitor 114. In doing so, it references the supplier master 106a to obtain the supplier's registration number and registration date in the ownership ratio master 106d linked to the ownership ratio code, and if the registration date is less than or equal to the relevant month, it prints the supplier's registration number (qualified invoice), but if the registration date is greater than the relevant month, it does not print the supplier's registration number (invoice). Furthermore, when issuing an invoice, the invoice issuing unit 103c issues the invoice based on the invoice detail apportionment data if such data is available; otherwise, it issues the invoice based on the invoice detail data.

[0083] (1) Invoice issuer If there is billing detail apportionment data, the bill is output based on the billing detail apportionment data, and if there is no billing detail apportionment data, the bill is issued based on the billing detail data. (2) Printing of registration number In the case of a single owner, the constituent customer code is obtained from the equity ratio master 106d using the equity ratio code of the billing detail data as a key, and the registration number and registration date are obtained from the customer master 106a using the obtained constituent customer code as a key, and if the registration date is less than or equal to the relevant month, the obtained registration number is printed, and if the registration date is greater than or equal to the relevant month, the obtained registration number is not printed.

[0084] In the case of multiple owners, the registration number and registration date are obtained from the customer master 106a using the owner code (customer code) of the billing statement allocation data as a key, and if the registration date is less than or equal to the relevant month, the registration number is printed, and if the registration date is greater than or equal to the relevant month, the obtained registration number is not printed.

[0085] Figure 17 shows an example of an invoice (1) with billing identification code "A001" and issued by proxy to Owner B (registration date: November 1, 2023): all details are for registered businesses. The invoice has a header section and a detail section. The header section includes the title (invoice), destination (tenant), biller (owner or company: if the registration date is less than or equal to the relevant month, the acquired registration number is printed), and total invoice amount. The detail section includes each expense item, the relevant month, amount excluding tax, total amount excluding tax, and totals by tax rate (tax rate, consumption tax amount, total amount including tax). In the example shown in Figure 17, the expense items are "office rent," "common area fee," and "electricity fee," and Owner B's registration number is printed.

[0086] Figure 18 shows an example of an invoice for (2) billing identification code "B001" and "B002" issued on behalf of Owner B (registration date 2023 / 11 / 1): electricity charges only are not included in the billing details for an unregistered business. Figure 18(A) shows an invoice for billing identification code "B001", with the expense items "office rent" and "common area charges", and Owner B's registration number is printed. Figure 18(B) shows an invoice for billing identification code "B002", with the expense item "electricity charges", and Owner B's registration number is not printed.

[0087] Figure 19 shows an example of an invoice (3) with billing identification code "C001" and issued on behalf of Owner B (registration date 11 / 1 / 2023): all details for unregistered businesses. In the example shown in Figure 19, the expense items are "office rent," "common area fees," and "electricity," and Owner B's registration number is not printed.

[0088] Figure 20 shows an example of an invoice for (4) billing identification code "D001", invoice for the company (registration date 1 October 2023): all details for registered businesses. In the example shown in Figure 20, the expense items are "office rent", "common area charges", and "electricity", and the registration number of PM Real Estate (the company) is printed.

[0089] Figure 21 shows an example of (4) an invoice with billing identification codes "E001" and "E002", issued on behalf of Owner B (registered on November 1, 2023) and Owner C (registered on December 1, 2023): Owner C's electricity bill is only for an unregistered business. In this example, there is billing detail apportionment data, so the invoice is output based on the billing detail apportionment data.

[0090] Figure 21(A) shows an invoice for Owner B with billing identification code "E001," with the expense items "Office Rent," "Common Expenses," and "Electricity," and Owner B's registration number is printed on it. Figure 21(B) shows an invoice for Owner C with billing identification code "E001," with the expense items "Office Rent" and "Common Expenses," and Owner C's registration number is printed on it. Figure 21(C) shows an invoice for Owner C with billing identification code "E002," with the expense item "Electricity," and Owner C's registration number is not printed on it.

[0091] As described above, according to this embodiment, there are provided a supplier master 106a in which supplier, registration number of qualified invoice issuer, and registration date are registered in association with each other; an ownership ratio master 106d in which property, ownership ratio code, supplier including owner, and ownership ratio are registered in association with each other; a billing registration unit 102a which inputs billing details data including billing destination, management item, property, ownership ratio code, applicable month, base price, consumption tax, tax-inclusive amount, and billing identification code specifying the invoice unit, and registers it in storage unit 106; and a billing registration unit 102b which, when finalizing billing for the billing details data registered in storage unit 106, refers to supplier master 106a and registers the billing details for the applicable month prior to the registration date of the supplier in ownership ratio master 106d linked to the ownership ratio code with the same billing identification code. If details exist, the system is equipped with a billing data confirmation unit 102b which updates and confirms the details to a billing identification code different from the same billing identification code, and an invoice issuing unit 102c which issues invoices for each billing identification code based on the confirmed billing detail data, and in doing so refers to the business partner master 106a to obtain the business partner registration number and registration date in the ownership ratio master 106d linked to the ownership ratio code, and if the registration date is less than or equal to the relevant month, prints the business partner registration number, but if the registration date is greater than the relevant month, does not print the business partner registration number.This means that the operator at the management company can issue invoices that comply with the invoice system without having to be aware of the owner's registration date.

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

[0093] Furthermore, this embodiment can contribute to reducing waste and promoting paperless and electronic systems, thereby contributing to the achievement of SDGs Goals 12, 13, and 15.

[0094] Furthermore, this embodiment can contribute to strengthening control and governance, which can contribute to Goal 16 of the SDGs.

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

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

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

[0098] Furthermore, with regard to the bill processing device 100, the components shown in the figures are functional concepts, and do not necessarily have to be physically configured as shown in the figures.

[0099] For example, all or any part of the processing functions of the invoice processing 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 processing device 100 as needed. 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 issue 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.

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

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

[0102] Furthermore, a "program" is a data processing method written in any language or description method, regardless of the format, such as source code or binary code. Note that a "program" is not necessarily limited to a single structure, but also includes a structure that is distributed as multiple modules or libraries, or a structure that achieves its function by cooperating with a separate program, such as an OS. Note that the specific configuration and reading procedure for reading a recording medium in each device shown in the embodiments, as well as the installation procedure after reading, can use well-known configurations and procedures.

[0103] The various databases stored in the memory 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 store various programs, tables, databases, and web page files used for various processes and providing websites.

[0104] The invoice processing device 100 may be configured as an information processing device such as a known personal computer or workstation, or may be configured as an information processing device connected to any peripheral device. The invoice processing 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.

[0105] Furthermore, the specific form of distribution and integration of the devices is not limited to that shown in the drawings, and all or part of them can be configured by functionally or physically distributing and integrating them in any unit depending on various additions or functional loads. In other words, the above-described embodiments can be implemented in any combination, or embodiments can be implemented selectively. [Explanation of symbols]

[0106] 100 Invoice processing device 102 Control section 102a Claims Registration Department 102b Billing data confirmation section 102c Billing Department 102d Master Maintenance Department 102e Screen display control unit 104 Communication interface unit 106 Storage section 106a Customer Master 106b Management item master 106c Property Master 106d Ownership Ratio Master 108 Input / Output Interface Section 112 Input Device 114 Output Device 200 servers 300 Network

Claims

1. An invoice processing device that includes a control unit and allows a management company to issue an invoice on behalf of an owner, The control unit A customer master record that associates the customer, the registration number of the qualified invoice issuer, and the registration date, The ownership ratio master records the properties, ownership ratio codes, business partners including owners, and ownership ratios in association with each other. The storage area storing the a billing registration means for inputting billing details data including a billing destination, management item, property, ownership ratio code, applicable month, base amount, consumption tax, tax-inclusive amount, and a billing identification code defining the billing unit, and registering the data in the storage area; a billing determination means for, when determining the billing of the billing detail data registered in the storage area, referring to the business partner master, if there is a mixture of details for the month before the registration date of the business partner in the ownership ratio master linked to the property and ownership ratio code with the same billing identification code and details for the month after the registration date, updating the details to a billing identification code different from the same billing identification code and determining the details; an invoice issuing means for issuing an invoice for each invoice identification code based on the confirmed invoice detail data, and at that time, referencing the customer master to obtain the customer registration number and registration date of the customer in the ownership ratio master linked to the property and ownership ratio code, and printing the customer registration number if the registration date is less than or equal to the relevant month, and not printing the customer registration number if the registration date is greater than or equal to the relevant month; A bill processing device comprising:

2. The invoice processing device described in claim 1, characterized in that when the invoice detail data registered in the memory area is invoiced, if there are multiple business partners in the ownership ratio master linked to the property and ownership ratio code for the invoice detail data, the invoice confirmation means divides the details for each business partner, creates invoice detail allocation data in which the amount is apportioned according to the ownership ratio of the business partner in the ownership ratio master, and registers the data in the memory area.

3. The invoice processing device described in claim 2, characterized in that the invoice confirmation means further refers to the customer master for the invoice detail allocation data, and if there is a detail for the corresponding month prior to the registration date of the customer in the ownership ratio master linked to the property and ownership ratio code with the same invoice identification code, updates the detail to a different invoice identification code from the same invoice identification code.

4. The invoice processing device according to claim 2 or 3, characterized in that, when issuing an invoice, the invoice issuing means issues an invoice based on the invoice detail allocation data if the invoice detail allocation data is available, and otherwise issues an invoice based on the invoice detail data.

5. An invoice processing method executed by an information processing device having a control unit, The control unit A customer master record that associates the customer, the registration number of the qualified invoice issuer, and the registration date, The ownership ratio master records the properties, ownership ratio codes, business partners including owners, and ownership ratios in association with each other. The storage area storing the Executed in the control unit: a billing registration step of inputting billing details data including billing destination, management item, property, ownership ratio code, applicable month, base amount, consumption tax, tax-inclusive amount, and billing identification code defining the billing unit, and registering the data in the storage area; a billing confirmation step of referring to the customer master when finalizing the billing of the billing detail data registered in the storage area, and if there is a mixture of details for the month before the registration date of the customer in the ownership ratio master linked to the property and ownership ratio code with the same billing identification code and details for the month after the registration date, updating the details to a billing identification code different from the same billing identification code and finalizing them; an invoice issuing process for issuing an invoice for each invoice identification code based on the confirmed invoice detail data, and at that time, referencing the customer master to obtain the customer registration number and registration date in the ownership ratio master linked to the property and ownership ratio code, and printing the customer registration number if the registration date is less than or equal to the relevant month, and not printing the customer registration number if the registration date is greater than or equal to the relevant month; 1. A method for processing an invoice, comprising:

6. An invoice processing program to be executed by an information processing device having a control unit, The control unit A customer master record that associates the customer, the registration number of the qualified invoice issuer, and the registration date, The ownership ratio master records the properties, ownership ratio codes, business partners including owners, and ownership ratios in association with each other. The storage area storing the In the control unit, a billing registration step of inputting billing details data including billing destination, management item, property, ownership ratio code, applicable month, base amount, consumption tax, tax-inclusive amount, and billing identification code defining the billing unit, and registering the data in the storage area; a billing confirmation step of referring to the customer master when finalizing the billing of the billing detail data registered in the storage area, and if there is a mixture of details for the month before the registration date of the customer in the ownership ratio master linked to the property and ownership ratio code with the same billing identification code and details for the month after the registration date, updating the details to a billing identification code different from the same billing identification code and finalizing them; an invoice issuing process for issuing an invoice for each invoice identification code based on the confirmed invoice detail data, and at that time, referencing the customer master to obtain the customer registration number and registration date in the ownership ratio master linked to the property and ownership ratio code, and printing the customer registration number if the registration date is less than or equal to the relevant month, and not printing the customer registration number if the registration date is greater than or equal to the relevant month; Invoice processing program to run.

Images