JP7794777B2 - Offsetting processing device, offsetting processing method, and offsetting processing program - Google Patents

Description

The present invention relates to an offset processing device, an offset processing method, and an offset processing program.

For example, in the construction industry, when a client places an order with a subcontractor, they often pay the material costs and expenses for the work on behalf of the subcontractor. A conventional system for processing construction costs is disclosed, for example, in Patent Document 1.

JP 2017-91279 A

However, the above-mentioned Patent Document 1 does not state anything about how, when an ordering party places an order with a subcontractor, the amount of work completed and the amount of expenses and other expenses paid in advance can be offset easily and with little work involved.

The present invention was made in consideration of the above, and aims to provide an offsetting device, offsetting method, and offsetting program that, when an ordering party places an order with a subcontractor, can offset the amount of work completed and expenses paid in advance with ease and low workload.

In order to solve the above-mentioned problems and achieve the objectives, the present invention provides an offsetting processing device equipped with a control unit, which includes an order input means for creating and registering in a storage area, when placing an order for construction work with a subcontractor, order data including the order number, subcontractor, order subject, cost item, order date, order period, order amount, and debt item; an expense import means for creating and registering in the storage area, for unpaid construction vouchers and advance vouchers, scheduled expense payment data including the expense number, date of occurrence, business partner, expense item, amount, and debt item, and linking data linking the expense number and order number; and an expense import means for importing and registering in the storage area, for inputting, based on the order data registered in the storage area, purchase number, purchase date, order number, handling company, order date, cost item, order amount, and debt item specified by an operator. The system is characterized by a purchase input means that creates purchase data including the purchase amount and payable item for the current month to be set, references the linking data registered in the storage area, reads from the storage area the scheduled expense payment data for the expense number linked to the purchase order number of the purchase data as a candidate for offset with the purchase amount for the current month of the purchase data, determines the scheduled payment data for the expense number specified by the operator as the item to be offset, creates advance payment data for the determined item to be offset, including the purchase number, purchase date, advance payment recipient, order number, advance payment item, and advance payment amount, and creates scheduled payment data including the scheduled payment number, scheduled payment date, payee vendor, and scheduled payment amount based on the purchase data and the advance payment data.

Furthermore, according to one aspect of the present invention, the purchase input means may be configured to allow one or more of the offset candidates to be designated as targets for offset against purchase amounts in the following month or later.

Furthermore, according to one aspect of the present invention, the control unit is configured to be able to access an item setting master that associates and registers expense items with cost items that serve as debit items in journal entries, and the expense capture means may refer to the item setting master based on the expense payment schedule data to create journal entry data that includes the journal entry number, posting date, business partner, debit item, debit amount, credit item, and credit amount.

Furthermore, according to one aspect of the present invention, the purchase input means may create journal data including a journal number, accounting date, customer, debit item, debit amount, credit item, and credit amount based on the purchase data and the advance purchase data.

Furthermore, according to one aspect of the present invention, the control unit may further include a payment statement management means for creating and outputting a payment statement based on the purchase data, the advance purchase data, and the payment schedule data.

Furthermore, in order to solve the above-mentioned problems and achieve the objectives, the present invention provides an offsetting processing method executed by an information processing device equipped with a control unit, which includes an order input process executed by the control unit to create and register in a memory area order data including the order number, subcontractor, order subject, cost item, order date, order construction period, order amount, and debt item when placing an order for construction work with a subcontractor; an expense import process to create and register in the memory area expense payment schedule data including the expense number, date of occurrence, trading company, expense item, amount, and debt item for unpaid vouchers and advance vouchers for the construction work, and to create and register in the memory area linking data linking the expense number and order number; and an expense import process to create and register in the memory area purchase number, purchase date, order number, handling company, and other related data based on the order data registered in the memory area. a purchase input process for creating purchase data including the order date, cost item, order amount, purchase amount for the current month specified by the operator, and payable item; referencing the linking data registered in the storage area, reading from the storage area the planned expense payment data for the expense number linked to the purchase number of the purchase data as a candidate for offset with the purchase amount for the current month of the purchase data; determining the planned payment data for the expense number specified by the operator as the item to be offset; creating advance payment data for the determined item to be offset, including the purchase number, purchase date, advance payment recipient, order number, advance payment item, and advance payment amount; and creating planned payment data including the planned payment number, planned payment date, payee vendor, and planned payment amount based on the purchase data and the advance payment data.

In order to solve the above-mentioned problems and achieve the object, the present invention provides an offset processing program to be executed by an information processing device having a control unit, the offset processing program including an order input step in the control unit for creating order data including an order number, a subcontractor, an order subject, a cost item, an order date, an order construction period, an order amount, and a debt item when placing an order for construction work with a subcontractor, and registering the order data in a storage area;
an expense import process for creating and registering in the storage area, with respect to unpaid vouchers and advance vouchers for construction work, scheduled expense payment data including expense number, date of occurrence, business operator, expense item, amount, and debt item, and linking data linking the expense number and purchase order number; and a process for creating and registering in the storage area, based on the purchase order data registered in the storage area, purchase data including purchase number, purchase date, purchase order number, handling business operator, purchase date, cost item, purchase amount, purchase amount for the current month designated by an operator, and debt item, and and a purchase input process of reading out from the storage area the scheduled expense payment data of the expense number linked to the purchase number as a candidate for offsetting with the purchase amount of the purchase data for the current month, determining the scheduled payment data of the expense number specified by the operator as the offset target, creating advance purchase data for the determined offset target, including the purchase number, purchase date, advance payment recipient, order number, advance payment subject, and advance payment amount, and creating payment schedule data, including the payment schedule number, payment schedule date, payment recipient company, and payment schedule amount, based on the purchase data and the advance purchase data.

This invention has the advantage that when an ordering party places an order with a subcontractor, it can easily offset the amount of work completed and the amount of expenses and other expenses paid in advance with little effort.

FIG. 1 is a block diagram showing an example of the configuration of a cancellation processing device according to this embodiment. FIG. 2 is a diagram showing an example of the configuration of the subject setting master. FIG. 3 is a flowchart for explaining an outline of the overall processing of the control unit of the offset processing device according to this embodiment. FIG. 4 is a diagram for explaining a specific example of the processing of the control unit of the offset processing device according to this embodiment. FIG. 5 is a diagram for explaining a specific example of the processing of the control unit of the offset processing device according to this embodiment. FIG. 6 is a diagram for explaining a specific example of the processing of the control unit of the offset processing device according to this embodiment. FIG. 7 is a diagram for explaining a specific example of the processing of the control unit of the offset processing device according to this embodiment. FIG. 8 is a diagram for explaining a specific example of the processing of the control unit of the offset processing device according to this embodiment. FIG. 9 is a diagram for explaining a specific example of the processing of the control unit of the offset processing device according to this embodiment. FIG. 10 is a diagram for explaining a specific example of the processing of the control unit of the offset processing device according to this embodiment. FIG. 11 is a diagram for explaining a specific example of the processing of the control unit of the offset processing device according to this embodiment. FIG. 12 is a diagram for explaining a specific example of the processing of the control unit of the offset processing device according to this embodiment. FIG. 13 is a diagram for explaining a specific example of the processing of the control unit of the offset processing device according to this embodiment. FIG. 14 is a diagram for explaining a specific example of the processing of the control unit of the offset processing device according to this embodiment.

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

[1: Overview]
For example, in the construction industry, when a client places an order with a subcontractor under an outsourcing contract, the client incurs a large amount of material costs and expenses that are paid in advance to the subcontractor.

However, in the past, when offsetting subcontractors' advance payments against unpaid invoices from multiple contractors for materials and expenses related to the work completed, it was difficult to link them to the outsourcing contracts that were the subject of the offset. Furthermore, multiple processes had to be carried out, such as unpaid invoices for materials and expenses incurred on behalf of contractors and advance payments to subcontractors. It was not possible to manage which contracts and invoices were being paid on behalf of contractors in the system. Therefore, for example, when payment statements were used, it was difficult to determine how much was being offset against which contract.

In this embodiment, we provide a system that allows you to easily offset the amount of work completed and expenses paid in advance when outsourcing construction work to an outsourced contractor, with little effort.

Specifically, the offset processing device of this embodiment provides the following functions.
(1) It is possible to simultaneously generate unpaid invoices and advance invoices for multiple contractors, and to link them to the contract numbers of outsourced work that are subject to offsetting when expenses are imported.
(2) Unpaid invoices from multiple contractors, such as parking fees and garbage disposal fees, can be treated as advance payments and offset when recording the progress of outsourced work.
(3) In relation to (2), it is also possible to pool the amount of unpaid invoices that have already been generated and that are to be offset, and offset it when the volume of the following month or later is recorded, rather than the volume of the current month.

The offset processing device of the present invention can be widely applied to industries such as the construction industry (e.g., general contractors, large-scale building and condominium construction companies, etc.).

2. Configuration
An example of the configuration of the offset processing device according to this embodiment will be described with reference to Fig. 1. Fig. 1 is a block diagram showing an example of the configuration of the offset processing device.

The offsetting processing device 100 is a commercially available desktop personal computer. Note that the offsetting processing 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 offsetting 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 offsetting processing 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 offsetting 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 a communication line. Here, the network 300 has the function of connecting the offsetting 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).

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.

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 also stores an account setting master 106a, order data, scheduled expense payment data, linking data, journal data, purchase data, advance purchase data, scheduled payment data, and the like. Figure 2 shows an example of the configuration of the account setting master 106a.

As shown in Figure 2, the item setting master 106a can be configured as a table that associates and registers expense items with the cost items that are debited when accounting entries occur.

Order data may include order number, subcontractor, order subject, cost item, order date, order period, order amount, and debt item.

Expense payment schedule data may include expense number, date of occurrence, supplier, expense item, amount, debt item, and external receipt number.

The linking data may include the expense number, order number, and a flag specifying whether or not to offset against the current month's production volume ("1" for offset, "0" for offset).

Journal entry data may include journal entry number, accounting date, customer, debit account, debit amount, credit account, credit amount, and summary.

Purchase data may include purchase number, purchase date, trading company, order number, order date, cost item, order amount, current month's purchase amount, and debt item.

Advance purchase data may include purchase number, purchase date, advance recipient, order number, advance item, and advance amount.

The payment schedule data may include the payment schedule number, the payment schedule date, the payment recipient, and the payment schedule amount.

Returning to Figure 1, the control unit 102 is a CPU or the like that provides overall control of the offsetting processing device 100. The control unit 102 has 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.

The control unit 102 is configured to be able to access the subject setting master 106a, order data, scheduled expense payment data, linking data, journal data, purchase data, advance purchase data, scheduled payment data, etc. stored in the memory unit 106. Note that the subject setting master 106a, order data, scheduled expense payment data, linking data, journal data, purchase data, advance purchase data, scheduled payment data, etc. may be stored in another location (e.g., server 200) as long as the control unit 102 is able to access them.

The control unit 102 conceptually includes an order input unit 102a, an expense capture unit 102b, a purchase input unit 102c, a payment statement management unit 102d, a master maintenance unit 102e, and a screen display control unit 102f.

When placing an order for construction work with a subcontractor, the order input unit 102a inputs order data including the order number, subcontractor, order subject, cost item, order date, order construction period, order amount, and debt item in response to operations by an operator or the like on an order input screen (not shown) displayed on the monitor 114, and registers the input data in the memory unit 106.

For example, in response to operations by an operator or the like on an expense capture screen (not shown) displayed on the monitor 114, the expense capture unit 102b creates expense payment schedule data for unpaid construction vouchers and advance vouchers, including the expense number, date of occurrence, business partner, expense item, amount, and debt item, and registers this data in the memory unit 106. It also creates linking data linking the expense number with the purchase order number and registers this data in the memory unit 106.

In addition, the expense capture unit 102b references the account setting master 106a based on the expense payment schedule data registered in the memory unit 106, and creates journal data including the journal number, accounting date, business partner, debit account, debit amount, credit account, and credit amount, and registers this data in the memory unit 106.

The purchase input unit 102c, for example, in response to operations by an operator or the like on the purchase input screen displayed on the monitor 114, creates purchase data based on the order data registered in the memory unit 106, including the purchase number, purchase date, order number, handling business, order date, cost item, order amount, the purchase amount for the current month specified by the operator, and debt item; references the linking data registered in the memory unit 106, reads from the memory unit 106 the scheduled expense payment data for the expense number linked to the order number of the purchase data as a candidate for offset with the purchase amount for the current month of the purchase data; determines the scheduled payment data for the expense number specified by the operator as the item to be offset; creates advance payment data for the determined item to be offset, including the purchase number, purchase date, advance payment recipient, order number, advance payment item, and advance payment amount; creates scheduled payment data based on the purchase data and advance payment data, including the scheduled payment number, scheduled payment date, payee, and scheduled payment amount; and registers the created data in the memory unit 106.

The purchase input unit 102c may be configured to allow one or more of the offset candidates to be designated as the target for offset against the purchase amount for the following month or later.

The purchase input unit 102c may create journal data including the journal number, accounting date, customer, debit item, debit amount, credit item, and credit amount based on the purchase data and advance purchase data, and register this in the memory unit 106.

The payment statement management unit 102d may, for example, create and output (display and/or print) a payment statement based on purchase data, advance purchase data, and payment schedule data in response to operator operations on a payment statement management screen (not shown) displayed on the monitor 114.

The master maintenance unit 102e performs settings such as data input, addition, change, and update on the subject setting master 106a, for example, in response to operator operations on a master maintenance screen (not shown) displayed on the monitor 114.

The screen display control unit 102f controls the display of various screens (e.g., order entry screen, expense capture screen, purchase entry screen, payment statement operation screen, master maintenance screen, etc.) displayed on the monitor 114 and the acceptance of input.

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

(3-1. Overall processing)
FIG. 3 is a diagram showing a flow (flow of piecework calculation) for explaining an outline of the overall processing of the control unit 102 of the offset processing device 100 in this embodiment.

With reference to Figure 3, an overview of the overall processing of the control unit 102 of the offset processing device 100 in this embodiment will be described. In Figure 3, the order input unit 102a executes the order input process (step S1). In the order input process, an order for construction work is placed with a subcontractor. Specifically, in the order input process, when placing an order for construction work with a subcontractor, the order input unit 102a inputs order data including the order number, subcontractor, order subject, cost item, order date, order construction period, order amount, and debt item in response to operations by an operator or the like on the order input screen displayed on the monitor 114, and stores the data in the memory unit 106.

The expense capture unit 102b executes expense capture processing (step S2). In the expense capture processing, scheduled expense payment data linked to orders is generated. Specifically, in the expense capture processing, the expense capture unit 102b creates scheduled expense payment data for unpaid construction vouchers and advance vouchers, including the expense number, date of occurrence, supplier, expense item, amount, and debt item, in response to operations by an operator or the like on the expense input screen displayed on the monitor 114, and registers this data in the memory unit 106. The expense capture unit 102b also creates linking data linking the expense number and order number, and registers this data in the memory unit 106.

The purchase input unit 102c executes the purchase input process (step S3). During the purchase input process, progress reports are received from subcontractors and the amount of the "progress" payment for the current month is recognized. Unpaid vouchers and advance payment vouchers are registered based on invoices for materials and expenses used in the construction work, etc., which are imported during expense collection. Furthermore, the information required for creating progress reports and payment reports is registered on the purchase input screen, and the expense payment schedule data linked at the time of recording is obtained and advance purchase data is generated.

Specifically, in the purchase input process, the purchase input unit 102c, for example, in response to operations by an operator or the like on the purchase input screen displayed on the monitor 114, creates purchase data based on the order data registered in the memory unit 106, including the purchase number, purchase date, order number, handling business operator, order date, cost item, order amount, the purchase amount for the current month specified by the operator, and debt item; references the linking data registered in the memory unit 106, reads from the memory unit 106 the scheduled expense payment data for the expense number linked to the order number of the purchase data as a candidate for offset with the purchase amount for the current month of the purchase data; determines the scheduled payment data for the expense number specified by the operator as the item to be offset; creates advance payment data for the determined item to be offset, including the purchase number, purchase date, advance payment recipient, order number, advance payment item, and advance payment amount; creates scheduled payment data based on the purchase data and advance payment data, including the scheduled payment number, scheduled payment date, payee, and scheduled payment amount; and registers the created data in the memory unit 106.

The payment statement operation unit 102d executes payment statement operation processing (step S4). Specifically, in the payment statement operation processing, the payment statement operation unit 102d creates and outputs (displays and/or prints) a payment statement based on purchase data, advance purchase data, and payment schedule data, in response to operator operations on a payment statement operation screen (not shown) displayed on the monitor 114. This payment statement is then sent to the subcontractor.

(3-2. Sample data)
4 to 14 are diagrams showing sample data for explaining a specific example of the processing by the control unit 102 of the offsetting processing device 100 in this embodiment. A specific example of the processing by the control unit 102 of the offsetting processing device 100 in this embodiment will be explained with reference to Figs. 4 to 14. In the following explanation, all monetary amounts are expressed in units of "yen," and the notation thereof will be omitted.

1. Explain the prerequisite information.
(S1: Order input process)
The order input process will be described in detail with reference to Figure 4. Order form information for subcontracted work is registered through the order input process. When placing an order for work with a subcontractor, the order input unit 102a inputs order data including the order number, subcontractor, order subject, cost item, order date, order period, order amount, and debt item in response to operations by an operator or the like on an order input screen (not shown) displayed on the monitor 114, and registers the data in the storage unit 106.

Figure 4 shows an example of order data. Order data includes the following fields: order number, subcontractor, order subject, cost item, order date, order construction period, order amount, and liability item. In the example shown in the figure, the order number is "HAC0001," the subcontractor is "XX Formwork Industry," the order subject is "XX Building Formwork Work," the cost item is "Uncompleted Work Expenditures (Subcontracted)," the order date is "3/19/2022," the order construction period is "4/1/2022 - 3/31/2024," the order amount is "10,000,000," and the liability item is "Construction Accounts Payable."

Figure 5 is a diagram that provides an overview of the offsetting example described below. The amount of work completed for outsourced construction work is recorded for subcontractor "XX Formwork Industry." Purchases of 6,000,000 yen are made in June 2022, against a contract amount of 10,000,000 yen. In addition, invoices for unpaid vouchers for expenses and materials used in this construction work have been received from multiple contractors (XX Recycle, XX Trading, XX Heavy Equipment, XX Crane). The administrative department also received a detailed breakdown of the amounts (totaling 1,000,000) advanced to subcontractors (XX Formwork Industry) from the on-site worksite manager. The unpaid vouchers for XX Recycle, XX Heavy Equipment, and XX Crane are offset against the June amount completed by XX Formwork Industry. It was decided that the portion of XX Trading's unpaid vouchers to be offset against payments to XX Formwork Industry would be offset when the amount completed the following month, July, is recorded.

2. Use the expense import function to simultaneously create unpaid information and information on planned offsets.
(S2: Expense import process)
The expense input process will be described in detail with reference to Figures 6 to 8. In the expense input process, unpaid and offsetting vouchers are registered based on invoices for expenses and materials used in subcontracted construction work. The expense capture unit 102b, for example, creates and registers in the storage unit 106 expense payment schedule data for unpaid construction vouchers and advance vouchers, including the expense number, date of occurrence, supplier, expense item, amount, and debt item, in response to operations by an operator or the like on an expense input screen (not shown) displayed on the monitor 114. The expense capture unit 102b also creates and registers in the storage unit 106 linking data linking the expense number and the purchase order number. Furthermore, the expense capture unit 102b may refer to the item setting master 106a based on the expense payment schedule data registered in the storage unit 106 to create and register in the storage unit 106 journal data including the journal number, posting date, supplier, debit item, debit amount, credit item, and credit amount.

Figure 6 (A) is a diagram showing an example of the configuration of the item setting master 106a. The item setting master 106a includes items for expense items and cost items that are debited when accounting entries occur. In the example shown in the figure, for "expense items" such as garbage transportation and disposal costs, miscellaneous hardware, heavy construction machinery, and mobile cranes, "uncompleted construction expenses" is set as the "cost item." Furthermore, for "expense items" such as advance expense items, "subcontractor advance payments" is set as the "cost item."

Figure 6 (B) shows an example of an offset schedule received from the site foreman, detailing the advance payments.

First, based on the unpaid information (not shown) and the offset schedule of the unpaid information (Figure 6(B)), an expense import format (e.g., an Excel format) is created in response to the operator's operations on the expense import screen (not shown).

Figure 7 (A) shows an example of data in an expense import format. The expense import format has fields for temporary voucher number, date of occurrence, vendor, expense item, amount, debt item, and order number. The debt item is set to "unpaid construction costs." In the example shown in the figure, lines 1 to 4 are data on unpaid information. Lines 5 to 8 are data on the offset schedule, which is information on the offset schedule in Figure 6 (B). The "order number" is left unset for unpaid information and set for offsetting plans.

In the example shown in the figure, the first line has the temporary voucher number "KAR0001," the date of occurrence "6/10/2022," the supplier "XX Recycling," the expense item "Garbage transportation and disposal costs," the amount "80,000," and the debt item "Construction accounts payable." The fifth line has the temporary voucher number "KAR0005," the date of occurrence "6/30/2022," the supplier "XX Recycling," the expense item "Advance expenses," the amount "20,000," and the debt item "Construction accounts payable."

Create planned expense payment data (unpaid vouchers, advance vouchers) based on the expense import format you created.

Figure 7 (B) shows an example of expense payment schedule data. Expense payment schedule data includes the following fields: expense number, date of occurrence, supplier, expense item, amount, debt item, and external receipt number. The "provisional voucher number" in the expense import format is stored as the "external receipt number."

In the example shown in the figure, the first line has the invoice number "KEI0001," the date of occurrence "6/10/2022," the supplier "○○ Recycling," the expense item "Garbage transportation and disposal expenses," the amount "80,000," the debt item "Unpaid construction expenses," and the external receipt number "KAR0001." The fifth line has the expense number "KEI0005," the date of occurrence "6/30/2022," the supplier "○○ Recycling," the expense item "Advance expenses," the amount "20,000," the debt item "Unpaid construction expenses," and the external receipt number "KAR0001."

Figure 7 (C) is a diagram showing an example of linked data. The linked data includes fields for expense number, order number, and a flag specifying whether or not to offset with the current month's output ('1' for offset, '0' for offset). By specifying the 'Order Number' to be offset with the current month's output in the expense import format, the 'Expense Number' linked to the 'External Receipt Number', which is the 'Provisional Voucher Number' linked to the 'Order Number', is obtained in the expense payment schedule data, and linking data is created for the obtained 'Expense Number' and the specified 'Order Number'. The 'Flag' is initially set to '0'.

Journal data is created based on the expense payment schedule data in Figure 7 (B) and the item setting master 106a in Figure 6 (A). Figure 8 is a diagram showing an example of the journal data created. The journal data has the following fields: journal entry number, posting date, business partner, debit item, debit amount, credit item, credit amount, and summary. For "Debit item," the cost item obtained from the item setting master 106a is set using the expense item in the expense payment schedule data as a key. In this example, for the expense item "Advance expense item," the debit item "Subcontractor advance payment" is set. For "Credit item," the debt item in the expense payment schedule data is set. For "Summary," the expense number in the expense payment schedule data is set.

In the example shown in the figure, the first line has journal entry number "SIW0001," date of occurrence "6/10/2022," supplier "○○ Recycling," liability item "Uncompleted construction expenditures (expenses)," debit amount "80,000," credit item "Unpaid construction costs," credit amount "80,000," and summary number "KEI0001." The fifth line has journal entry number "SIW0005," date of occurrence "6/30/2022," supplier "○○ Formwork Industry," liability item "Subcontractor advance payments," debit amount "20,000," credit item "Unpaid construction costs," credit amount "20,000," and summary number "KEI0005."

3. The offsetting amount is recognized when the volume of work is recorded.
(S3: Purchase input processing)
The purchase input process will be described in detail with reference to Figures 9 to 13. The purchase input unit 102c, for example, in response to operations by an operator or the like on the purchase input screen displayed on the monitor 114, creates purchase data based on the order data registered in the storage unit 106, including the purchase number, purchase date, order number, handling company, order date, cost item, order amount, purchase amount for the current month designated by the operator, and debt item; references the linking data registered in the storage unit 106, reads from the storage unit 106 the scheduled expense payment data for the expense number linked to the order number of the purchase data as a candidate for offset with the purchase amount for the current month of the purchase data; determines the scheduled payment data for the expense number designated by the operator as the offset target; creates advance payment data for the determined offset target, including the purchase number, purchase date, advance payment recipient, order number, advance payment item, and advance payment amount; creates payment schedule data based on the purchase data and advance payment data, including the scheduled payment number, scheduled payment date, payee, and scheduled payment amount; and registers the created data in the storage unit 106. In this case, one or more of the offset candidates may be designated as the target for offset with the purchase amount for the following month or later (see Figure 13). The purchase input unit 102c may create journal data including a journal number, a posting date, a customer, a debit item, a debit amount, a credit item, and a credit amount based on the purchase data and the advance purchase data, and register the journal data in the storage unit 106.

Here, based on the current month's production report, select the relevant purchase order number from the purchase entry screen and enter the purchase details. Here, we will explain how to enter purchases for a volume of 6,000,000 in June 2022.

Figure 9 shows an example of the purchase entry screen 400. The purchase entry screen 400 includes a header area 401 for specifying the purchase date, purchase order number, order subject, subcontractor, and debt item, and a details area 402 for displaying purchase details or advance payment details according to the switch button.

In the details area 402, when purchase details are selected with the switch button, purchase information (row number, cost item, order amount, current month purchase amount, remaining order amount items) and the total purchase amount are displayed (see Figure 9). When advance details are selected with the switch button, the order amount, current month's output amount, advance information (row number, expense number, supplier, expense item, advance amount, field to specify whether or not to offset), the total offset amount, and the expected payment amount (= total purchase amount - total offset amount) are displayed (see Figure 10 (C)). On the purchase input screen 400, hatched cells cannot be entered by the operator (automatic input/display), and unhatched cells can be entered by the operator.

In the header area 401, the operator specifies the purchase date and order number. Using the specified order number as a key, the order subject, subcontractor, and debt item are read from the order data and automatically displayed. In the example shown in the figure, the purchase date "2023/6/30" and order number "HAC0001" are specified, and the order subject "Formwork work for XX building," subcontractor "XX Formwork Industry," and debt item "Construction accounts payable" are automatically displayed.

Also, when a purchase detail is selected in the details area 402, the specified purchase order number is used as a key to read the cost item and order amount from the purchase data and automatically display them in the purchase information. The operator enters the "purchase amount for this month" in the purchase information. The remaining order amount is automatically calculated by subtracting the purchase amount for this month, and is automatically displayed.

In the example shown in the figure, the cost item "Uncompleted Work Expenditures (Subcontracted)" and order amount "10,000,000" are automatically displayed. When the operator specifies the current month's purchase amount of "6,000,000," the remaining order amount of "4,000,000 (= 10,000,000 - 6,000,000)" is automatically displayed. The total purchase amount of "6,000,000" is also automatically displayed.

Also, as shown in Figure 10(C), when an advance payment detail is selected in the detail area 402, the order amount and current month's purchase amount for the purchase detail are automatically displayed as the order amount and current month's output amount. For advance payment information, the expense number from the linked data in Figure 10(A) is retrieved using the specified order number as a key, and offset candidates are read from the expense payment data shown in Figure 10(B) using the retrieved expense number as a key, and the expense number, supplier, expense item, and advance payment amount for the advance payment information are automatically displayed. The operator sets the offset target by specifying (checking) whether each expense number is eligible for offset. In the example shown in the figure, the details for expense numbers "PJ0005," "PJ0007," and "PJ0008" are designated as offset targets, while the detail for "XX Trading Co., Ltd. Miscellaneous Hardware" for expense number "PJ0006" is not designated as an offset target, so that it will not be offset against the current month's output. The total offset amount of "1,000,000" and the expected payment amount of "5,000,000 (= 6,000,000 - 1,000,000)" will be automatically displayed.

For expense numbers designated as offset targets, the linking data flag is updated to "1" as shown in Figure 11. Expenses with a flag of "0" can be offset targets when recording production from the following month onwards.

When the registration button (not shown) is pressed, purchase data and advance payment purchase data are created according to the input content on the purchase input screen 400 and registered in the storage unit 106. In addition, payment schedule data and journal data are created based on the purchase data and advance payment purchase data and registered in the storage unit 106. In the case of the input content shown in the examples of Figures 10 and 11, the data shown in Figure 12 is registered.

Figure 12 (A) is a diagram showing an example of purchasing data. The purchasing data includes the following fields: purchase number, purchase date, supplier, order number, order date, cost item, order amount, purchase amount for the current month, and liability item. In the example shown in the figure, the purchase number is "SIR0001," the purchase date is "6/30/2022," the supplier is "XX Formwork Industry," the order number is "HAC0001," the order date is "3/19/2022," the cost item is "Uncompleted construction expenditure (subcontracted)," the order amount is "10,000,000," the purchase amount for the current month is "6,000,000," and the liability item is "Construction accounts payable."

Figure 12 (B) is a diagram showing an example of advance purchase data. Advance purchase data has the following fields: purchase number, purchase date, advance recipient, order number, advance item, and advance amount. In the example shown in the figure, the first line contains purchase number "TSI001," purchase date "6/30/2022," advance recipient "XX Formwork Industry," order number "HAC0001," advance item "Subcontractor advance payment," and advance amount "20,000."

Figure 12 (C) is a diagram showing an example of payment schedule data. The payment schedule data includes fields for the scheduled payment number, scheduled payment date, payee company, and scheduled payment amount. In the example shown in the figure, the first line shows the payment schedule generated from purchase data, while lines 2 to 4 show the payment schedule generated from advance purchase data. The first line shows the scheduled payment number "SIH0001," the scheduled payment date "8/31/2022," the payee company "XX Formwork Industry," and the scheduled payment amount "6,000,000." The second line shows the scheduled payment number "SIH0002," the scheduled payment date "8/31/2022," the payee company "XX Formwork Industry," and the scheduled payment amount "-20,000."

Figure 12 (D) is a diagram showing an example of journal entry data. Journal entry data has the following fields: journal entry number, accounting date, business partner, debit item, debit amount, credit item, and credit amount. In the example shown in the figure, the first line is a journal entry arising from purchase data, and lines 2 to 4 are journal entries arising from advance purchase data. In the example shown in the figure, the first line has journal entry number "SIW0009," date of occurrence "6/30/2022," business partner "○○ Formwork Industry," debt item "Uncompleted construction expenditures (expenses)," debit amount "6,000,000," credit item "Construction accounts payable," and credit amount "6,000,000." The second line has the journal entry number "SIW0010", the date of occurrence "6/30/2022", the trading company "○○ Formwork Industry", the liability item "Construction outstanding", the debit amount "20,000", the credit item "Subcontractor advance payment", the credit amount "20,000".

(Supplementary Note 1)
Figure 13 shows an example of an advance payment detail when the amount of work completed in July 2022 is recorded based on the purchase entry. Here, we will explain the case where the amount of work completed for July is 3,000,000. In Figure 13, the details area 402 of the purchase entry screen 400 displays the order amount "10,000" and the amount of work completed for the current month "3,000,000." The advance payment information displays the following offset candidates: expense number "PJ0006," business partner "XX Trading," expense item "Miscellaneous Hardware," and advance payment amount "100,000." The operator specifies (checks) the offset target for expense number "PJ0006" to set it as the offset target. The total offset amount of "100,000" and the expected payment amount of "2,900,000 (= 3,000,000 - 1,000,000)" are automatically displayed.

(Supplementary Note 2)
If a payment statement is used, it is also possible to utilize the purchase data, advance purchase data, and scheduled payment data processed in 2. The payment statement operation unit 102d creates and outputs (displays and/or prints) a payment statement based on the purchase data, advance purchase data, and scheduled payment data, for example, in response to an operator's operation on a payment statement operation screen (not shown) displayed on the monitor 114. Figure 14 is a diagram showing an example of a payment statement. The payment statement is sent to the subcontractor "XX Formwork Industry."

As explained above, according to this embodiment, when placing an order for construction work with a subcontractor, the order input unit 102a creates order data including the order number, subcontractor, order subject, cost item, order date, order period, order amount, and debt item, and registers it in the memory unit 106; the expense capture unit 102b creates expense payment schedule data for unpaid construction vouchers and advance vouchers including the expense number, date of occurrence, business partner, expense item, amount, and debt item, and registers this in the memory unit 106, as well as creates linking data linking the expense number and order number, and registers this in the memory area; and the expense capture unit 102b creates and stores purchase data including the purchase number, purchase date, order number, handling company, order date, cost item, order amount, purchase amount for the current month specified by the operator, based on the order data registered in the memory unit 106. and a purchase input unit 102c that references the linking data registered in unit 106, reads from the storage area the scheduled expense payment data for the expense number linked to the purchase order number of the purchase data as a candidate for offset with the current month's purchase amount for the purchase data, determines the scheduled payment data for the expense number specified by the operator as the item to be offset, creates advance purchase data for the determined item to be offset, including the purchase number, purchase date, advance payment recipient, purchase order number, advance payment item, and advance payment amount, and creates payment schedule data including the scheduled payment number, scheduled payment date, payee contractor, and scheduled payment amount based on the purchase data and the advance purchase data.This makes it possible for an ordering party to easily offset the progress of the work and the advance payment amount for expenses and other items with little workload when ordering work from a subcontractor.

[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 offset processing device 100, the components shown in the figure 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 offsetting 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 processing described in this embodiment, and is mechanically read by the offsetting processing device 100 as needed. In other words, a computer program that works in conjunction with the OS to issue instructions 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.

This computer program may also be stored on an application program server connected to the offset processing 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 offsetting processing device 100 may also be configured as an information processing device such as a known personal computer or workstation, or as an information processing device connected to any peripheral device. The offsetting processing device 100 may also be implemented 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.

100 Offsetting processing device 102 Control unit 102a Order input unit 102b Expense acquisition unit 102c Purchase input unit 102d Payment statement operation unit 102e Master maintenance unit 102f Screen display control unit 104 Communication interface unit 106 Storage unit 106a Account setting master 108 Input/output interface unit 112 Input device 114 Output device 200 Server 300 Network

Claims (6)

An offsetting device equipped with a control unit,
The control unit
an order input means for creating order data including an order number, subcontractor, order subject, cost item, order date, order construction period, order amount, and debt item in response to an operator's operation on an order input screen when placing an order for construction work with a subcontractor, and registering the data in a storage area;
an expense capturing means for creating and registering in the storage area, in response to an operator's operation on an expense capturing screen, expense payment schedule data including expense number, occurrence date, business partner, expense item, amount, and debt item for unpaid slips and advance payment slips for construction work, and for creating and registering in the storage area linking data linking expense number and purchase order number;
In response to the operator's operation on the purchase input screen, purchase data including the purchase number, purchase date, purchase order number, supplier, order date, cost item, order amount, purchase amount for the current month designated by the operator, and debt item is created based on the purchase order data registered in the storage area, and by referring to the linking data registered in the storage area, the expense payment schedule data of the expense number linked to the purchase order number of the purchase data is read from the storage area as a candidate for offset with the purchase amount for the current month of the purchase data, and the expense payment schedule data of the expense number designated by the operator is set as the target for offset. a purchase input means for determining the offset target by using the above method, creating advance purchase data including a purchase number, purchase date, advance payment recipient, purchase order number, advance payment subject, and advance payment amount for the determined offset target, and creating payment schedule data including a payment schedule number, payment schedule date, payment recipient company, and advance payment amount based on the purchase data and the advance purchase data, respectively, whereby, when based on the purchase data, the "payment recipient company" is set to the trading company, and the "expected payment amount" is set to the purchase amount for the current month, and when based on the advance purchase data, the "payment recipient company" is set to the advance payment recipient, and the "expected payment amount" is set to the negative of the advance payment amount;
An offsetting device comprising: The offset processing device described in claim 1, characterized in that the purchase input means is configured to allow one or more of the offset candidates to be designated as the target for offset against purchase amounts from the following month onwards. The control unit
It is configured to be accessible to the item setting master that associates and registers the expense item with the cost item that will be the debit item of the journal entry,
The offsetting processing device described in claim 1 or 2, characterized in that the expense import means, based on the expense payment schedule data, refers to the item setting master and creates journal data including the journal number, accounting date, business partner, debit item, debit amount, credit item, and credit amount, which are set by setting the cost item of the item setting master linked to the expense item of the expense payment schedule data. The offsetting processing device described in claim 1 or 2, characterized in that the purchase input means creates journal entry data including the journal entry number, accounting date, business partner, debit account, debit amount, credit account, and credit amount based on the purchase data and the advance purchase data, respectively; when based on the purchase data, the "accounting date" is set as the purchase date, the "business partner" as the trading company, the "debit account" as the cost account, the "debit amount" as the purchase amount for the current month, the "credit account" as the debt account, and the "credit amount" as the purchase amount for the current month; and when based on the advance purchase data, the "accounting date" is set as the purchase date, the "business partner" as the advance recipient, the "debit account" as the construction account payable, the "debit amount" as the advance amount, the "credit account" as the advance account, and the "credit amount" as the advance amount. An offsetting method executed by an information processing device having a control unit,
Executed in the control unit:
an order input process for creating and registering order data including an order number, subcontractor, order subject, cost item, order date, order construction period, order amount, and debt item in a storage area in response to an operator's operation on an order input screen when placing an order for construction work with a subcontractor;
an expense import process for creating and registering in the storage area, in accordance with the operator's operations on the expense import screen, expense payment schedule data including expense number, occurrence date, business partner, expense item, amount, and debt item for construction unpaid vouchers and advance payment vouchers, and also creating and registering in the storage area linking data linking expense number and purchase order number;
In response to the operator's operation on the purchase input screen, purchase data including the purchase number, purchase date, purchase order number, supplier, order date, cost item, order amount, purchase amount for the current month designated by the operator, and debt item is created based on the purchase order data registered in the storage area, and by referring to the linking data registered in the storage area, the expense payment schedule data of the expense number linked to the purchase order number of the purchase data is read from the storage area as a candidate for offset with the purchase amount for the current month of the purchase data, and the expense payment schedule data of the expense number designated by the operator is set as the target for offset. a purchase input process in which, for the determined offset target, advance purchase data including a purchase number, purchase date, advance payment recipient, purchase order number, advance payment subject, and advance payment amount are created, and payment schedule data including a payment schedule number, payment schedule date, payment recipient company, and advance payment amount are created based on the purchase data and the advance purchase data, respectively, and in this case, when based on the purchase data, the "payment recipient company" is set to the trading company, and the "expected payment amount" is set to the purchase amount for the current month, and when based on the advance purchase data, the "payment recipient company" is set to the advance payment recipient, and the "expected payment amount" is set to the negative of the advance payment amount;
An offsetting method comprising: An offset processing program to be executed by an information processing device having a control unit,
The control unit
an order input process for creating and registering order data including an order number, subcontractor, order subject, cost item, order date, order construction period, order amount, and debt item in a storage area in response to an operator's operation on an order input screen when placing an order for construction work with a subcontractor;
an expense import process for creating and registering in the storage area, in accordance with the operator's operations on the expense import screen, expense payment schedule data including expense number, occurrence date, business partner, expense item, amount, and debt item for construction unpaid vouchers and advance payment vouchers, and also creating and registering in the storage area linking data linking expense number and purchase order number;
In response to the operator's operation on the purchase input screen, purchase data including the purchase number, purchase date, purchase order number, supplier, order date, cost item, order amount, purchase amount for the current month designated by the operator, and debt item is created based on the purchase order data registered in the storage area, and by referring to the linking data registered in the storage area, the expense payment schedule data of the expense number linked to the purchase order number of the purchase data is read from the storage area as a candidate for offset with the purchase amount for the current month of the purchase data, and the expense payment schedule data of the expense number designated by the operator is set as the target for offset. a purchase input process in which, for the determined offset target, advance purchase data including a purchase number, purchase date, advance payment recipient, purchase order number, advance payment subject, and advance payment amount are created, and payment schedule data including a payment schedule number, payment schedule date, payment recipient company, and advance payment amount are created based on the purchase data and the advance purchase data, respectively, and in this case, when based on the purchase data, the "payment recipient company" is set to the trading company, and the "expected payment amount" is set to the purchase amount for the current month, and when based on the advance purchase data, the "payment recipient company" is set to the advance payment recipient, and the "expected payment amount" is set to the negative of the advance payment amount;
An offsetting program to execute the above.