Payment management device, budget payment management method, and budget payment management program

Abstract

To provide a payout managing apparatus, an estimated-cost payout managing method and an estimated-cost payout managing program that allows for preventing a deviation from occurring between estimated-cost management and payout of the present month.SOLUTION: A payout managing apparatus in the present embodiment is allowed to make reference to estimated-cost data and payout request data and display a payout-schedule selecting screen including estimated-cost total information in which estimated costs are summed up on a cost-item basis and payout result information upon which a situation of cost-based, monthly payout results is reflected.SELECTED DRAWING: Figure 1

Description

[Technical field]

[0001] The present invention relates to a payment management device, a budget payment management method, and a budget payment management program. [Background technology]

[0002] Patent Document 1 discloses a technology that, when an order for materials and work for a construction site is received, performs billing and receivable balance management not only on a billing recipient basis, but also on a temporary receivable management unit (hereinafter simply referred to as a "project"). [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2017-168090 A Summary of the Invention [Problem to be solved by the invention]

[0004] In general accounts receivable management, when a payment request is registered, the payment data is compared with pre-registered budget data when the payment amount is entered, and an input alert is issued if the budget amount is insufficient. For this reason, in payment operations using conventional technology, the pre-registered budget and the invoiced amount may be registered in a different state, causing the budget data to become outdated, or an invoice for the content that should have been paid that month may not arrive, causing a delay in payment.

[0005] However, in the above-mentioned Patent Document 1, no consideration is given to this, and there is a problem in that there is a gap between the budget management and the payment for the current month.

[0006] The present invention has been made in consideration of the above, and aims to provide a payment management device, a budget payment management method, and a budget payment management program that can prevent a discrepancy from occurring between the current month's budget management and payments. [Means for solving the problem]

[0007] In order to solve the above-mentioned problems and achieve the objectives, the payment management device of the present invention is a payment management device equipped with a control unit, which is capable of accessing budget data that links and manages expense item names, years and months, and budget amounts for each project name, and payment request data that links and manages payment occurrence dates, scheduled payment dates, payees, project names, expense items, and payment amounts, and the control unit is equipped with a display control means that references the budget data and the payment request data, and displays a payment schedule selection screen including budget total information that totals the budget for each expense item, and actual payment information that reflects the actual payment status for each expense and month.

[0008] In addition, the budget payment management method of the present invention is a budget payment management method executed by a payment management device equipped with a control unit, which is capable of accessing budget data that links and manages expense item names, years and months, and budget amounts for each project name, and payment request data that links and manages payment occurrence dates, scheduled payment dates, payees, project names, expense items, and payment amounts, and is characterized by including a display control step executed by the control unit that references the budget data and payment request data and displays a payment schedule selection screen that includes budget total information that totals the budget for each expense item, and actual payment information that reflects the actual payment status for each expense and month.

[0009] In addition, the budget payment management program of the present invention is a budget payment management program executed by a payment management device equipped with a control unit, and is capable of accessing budget data that links and manages expense item names, years and months, and budget amounts for each project name, and payment request data that links and manages payment occurrence dates, scheduled payment dates, payees, project names, expense items, and payment amounts, and the control unit includes a display control step that refers to the budget data and the payment request data, and displays a payment schedule selection screen that includes budget total information that totals the budget for each expense item, and actual payment information that reflects the actual payment status for each expense and month. Effect of the Invention

[0010] According to the present invention, it is possible to prevent a discrepancy between the current month's budget management and payment. [Brief description of the drawings]

[0011] [Figure 1] FIG. 1 is a schematic diagram showing an overview in a block diagram of an example of the configuration of a payment management device. [Diagram 2] FIG. 2 is a diagram showing an example of a budget data table in the budget data. [Diagram 3] FIG. 3 is a diagram showing an example of a payment request data table in the payment request data. [Figure 4] FIG. 4 is a diagram showing an example of a control master table in the control master. [Diagram 5] FIG. 5 is a flowchart showing an outline of the processing executed by the payment management device. [Figure 6] FIG. 6 is a diagram showing an example of a payment schedule selection screen that the display control unit causes to be displayed on the monitor. [Figure 7] FIG. 7 is a diagram showing an example of a payment schedule selection screen that the display control unit causes to be displayed on the monitor. [Figure 8] FIG. 8 is a diagram showing an example of a payment request input screen that the display control unit causes to be displayed on the monitor. [Figure 9] FIG. 9 is a diagram illustrating an example of the payment request data. [Figure 10] FIG. 10 is a diagram showing an example of a payment request data table in the payment request data. [Figure 11] FIG. 11 is a diagram showing an example of a payment schedule selection screen that the display control unit causes to be displayed on the monitor. [Figure 12] FIG. 12 is a diagram showing another example of the payment request input screen that the display control unit causes to be displayed on the monitor. [Figure 13] FIG. 13 is a diagram showing an example of a payment request data table in the payment request data generated by the generating unit. [Figure 14]FIG. 14 is a diagram showing an example of a payment request data table in the payment request data. [Figure 15] FIG. 15 is a diagram showing another example of the payment request input screen that the display control unit causes to be displayed on the monitor. [Figure 16] FIG. 16 is a diagram showing another example of the payment request input screen that the display control unit causes to be displayed on the monitor. [Figure 17] FIG. 17 is a diagram showing an example of a payment request input screen that the display control unit causes to be displayed on the monitor. [Figure 18] FIG. 18 is a diagram showing an example of a payment request data table in the payment request data generated by the generating unit. [Figure 19] FIG. 19 is a diagram showing an example of a payment request data table in the payment request data. [Figure 20] FIG. 20 is a diagram showing an example of a payment request input screen that the display control unit causes to be displayed on the monitor. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0012] Hereinafter, an embodiment of a payment management device, a budget payment management method, and a budget payment management program according to the present invention will be described in detail with reference to the drawings. Note that the present invention is not limited to the embodiment.

[0013] [1. Configuration] An example of the configuration of a payment management device according to this embodiment will be described with reference to Fig. 1 etc. Fig. 1 is a schematic diagram showing an overview in a block diagram of an example of the configuration of a payment management device.

[0014] The payment management device 100 shown in Fig. 1 is a commercially available desktop personal computer. Note that the payment management device 100 is not limited to a stationary information processing device such as a desktop personal computer, and may be a portable information processing device such as a commercially available notebook personal computer, a PDA (Personal Digital Assistant), a smartphone, or a tablet personal computer.

[0015] The payment management apparatus 100 comprises a control unit 102, a communication interface unit 104, a memory unit 106, and an input / output interface unit 108. The units comprised in the payment management apparatus 100 are connected to each other so as to be able to communicate with each other via any communication path.

[0016] The communication interface unit 104 communicatively connects the payment management apparatus 100 to the network 300 via a communication device such as a router and a wired or wireless communication line such as a dedicated line. The communication interface unit 104 has a function of communicating data with other devices via the communication line. Here, the network 300 has a function of connecting the payment management apparatus 100 and the server 200 so that they can communicate with each other, and is, for example, the Internet or a LAN (Local Area Network). The data stored in the memory unit 106 may be stored in the server 200, for example.

[0017] 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 realize a pointing device function. In the following, 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.

[0018] The storage unit 106 stores various databases, tables, files, etc. The storage unit 106 records computer programs for cooperating with an OS (Operating System) to give instructions to a CPU (Central Processing Unit) to perform various processes. For example, memory devices such as RAM (Random Access Memory) and ROM (Read Only Memory), fixed disk devices such as hard disks, flexible disks, and optical disks can be used as the storage unit 106. The storage unit 106 stores budget data 106a, payment request data 106b, a control master 106c, and payment request data 106b.

[0019] The budget data 106a holds a project code (hereinafter simply referred to as a "project CD") previously registered by a user using the input device 112, an expense item name, a year and month, and a budget amount, all of which are linked together.

[0020] 2 is a diagram showing an example of a budget data table in the budget data 106a. In the budget data table T1 shown in FIG. 2, a project CD registered in advance by a user using the input device 112, an expense item name, a year and month, and a budget amount are linked and stored. For example, in the first row of the budget data table T1, the project CD is "PJ0001", the expense item name is "land cost", the year and month are "2021 / 07", and the budget amount is "100,000", all of which are linked and stored.

[0021] The payment request data 106b is stored in association with the payment request number previously registered by the user using the input device 112, the date of occurrence, the scheduled payment date, the payee, the project CD, the expense item name, and the payment amount.

[0022] 3 is a diagram showing an example of a payment request data table in the payment request data 106b. In the payment request data table T2 shown in FIG. 3, the payment request number registered in advance by the user using the input device 112, the occurrence date (payment occurrence date), the scheduled payment date, the payee, the project CD, the expense item name, and the payment amount are linked and stored. For example, in the first row of the payment request data table T2, the payment request number "NY0001", the occurrence date "2021 / 07 / 10", the scheduled payment date "2021 / 08 / 31", the payee "Landowner", the project CD "PJ0001", the expense item name "Land price", and the payment amount "100,000" are linked and stored.

[0023] The control master 106c holds the processing date that is registered in advance by the user using the input device 112.

[0024] 4 is a diagram showing an example of a control master table in the control master 106c. The control master table T3 shown in FIG. 4 holds the processing date “2021 / 09” that the user registered in advance using the input device 112.

[0025] Returning to FIG. 1, the description of the configuration of the payment management apparatus 100 will continue. The control unit 102 is a CPU or the like that comprehensively controls the payment management apparatus 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 based on these stored programs. The control unit 102 includes a display control unit 102a, a determination unit 102b, and a generation unit 102c.

[0026] The display control unit 102a refers to the budget data 106a and the payment request data 106b, and causes the monitor 114 to display a payment schedule selection screen including budget total information that totals the budget for each expense item, and actual payment information that reflects the status of actual payments for each expense item and each month. Furthermore, the display control unit 102a causes the payment schedule selection screen to display, as actual payment information, actual payments for each expense item and month in the month before the processing year and month, and budget amounts related to the budget for each expense item and month after the processing year and month. Furthermore, the display control unit 102a causes the display mode of each cell by expense item to be changed and displayed according to the budget balance based on the budget amount and the payment amount in the payment schedule selection screen. Furthermore, the display control unit 102a causes the display mode of the cells of the expense items with budget balances to be highlighted in comparison with the cells of the expense items with no budget balances and the cells of the expense items in the month before the processing year and month, based on the budget amount and the payment amount in the payment schedule selection screen. Furthermore, the display control unit 102a displays the display mode of the cell of the expense item having a budget balance and payment request data 106b in an emphasized manner compared to the display mode of the cell of the expense item having a budget balance and no payment request data 106b on the payment schedule selection screen. Furthermore, when the determination unit 102b determines that the cursor is placed by the input device on the display area of ​​the cell having the budget balance and payment request data 106b on the payment schedule selection screen, the display control unit 102a displays payment information indicating the current payment status around the display area of ​​the cell having the payment request data 106b. Furthermore, when a cell of an expense item having a budget balance is selected on the payment schedule selection screen based on the budget amount and the payment amount, the display control unit 102a changes the payment request input screen P2 of the selected expense item to the payment schedule selection screen and displays it.

[0027] The determination unit 102b determines whether or not the user has placed the cursor on the display area of ​​a cell that has a budget balance and payment request data 106b on the payment schedule selection screen using the input device 112. Furthermore, the determination unit 102b determines whether or not the user has used the input device 112 to select a target cell of an expense item that has a budget balance exceeding 0 (budget balance > 0) and that contains control request data.

[0028] The generating unit 102c generates payment request data 106b according to the registration results entered by the user on the payment request input screen P2 using the input device 112, and stores the generated data in the storage unit .

[0029] 2. Processing performed by the payment management device 100 Next, it will be described how the payment management apparatus 100 executes the process. Figure 5 is a flowchart showing an overview of the process the payment management apparatus 100 executes.

[0030] As shown in FIG. 5, first, the display control unit 102a acquires the project CD and the processing date input by the user using the input device 112 (step S101).

[0031] Next, the display control unit 102a acquires the budget data 106a and the payment request data 106b from the storage unit 106 based on the project CD and the processing date input by the user using the input device 112 (step S102).

[0032] Thereafter, the display control unit 102a refers to the project CD, processing date, budget data 106a, payment request data 106b, and control master 106c input by the user using the input device 112, and displays a payment schedule selection screen including total budget information that totals the budget for each expense item, and actual payment information that reflects the actual payment status for each expense item and month (step S103).

[0033] Fig. 6 is a diagram showing an example of a payment schedule selection screen that the display control unit 102a causes to be displayed on the monitor 114. The payment schedule selection screen P1 shown in Fig. 6 includes a project CD display area B1, a start date display area B2, a project name display area B3, and a payment schedule selection table T4.

[0034] Specifically, the payment schedule selection screen P1 displays "PJ0001" in the project CD display area B1, "2021 / 07" in the start month display area B2, and the project name "ABC Project" corresponding to the project CD in the project name display area B3.

[0035] Furthermore, the payment schedule selection table T4 includes total budget information K1, which is the total of the budget for each expense item, and actual payment information K2, which reflects the status of actual payment by expense item and by month. Specifically, the first column of the payment schedule selection table T4 displays multiple expenses, such as "land price", "agency fee", "registration fee", and "construction cost". Furthermore, in the payment schedule selection table T4, when the expense item in the first row is "land price", "500,000" is displayed as total budget information K1. Furthermore, in the payment schedule selection table T4, when the expense item is "land price", "100,000" is displayed for "2021 / 07" and "400,000" is displayed for "2021 / 08" as actual payment information K2, which reflects the status of actual payment by expense item and by month.

[0036] In addition, in the payment schedule selection table T4, when the expense item is "registration costs", "500" is displayed in "2021 / 09" as the actual payment information K2 reflecting the status of the actual payment by expense item and month. Furthermore, in the payment schedule selection table T4, when the expense item is "construction costs", "100,000" is displayed in "2021 / 09", "300,000" in "2021 / 12", and "300,000" in "2022 / 02" as the actual payment information K2 reflecting the status of the actual payment by expense item and month. In this case, when the processing date is "2021 / 09", the display control unit 102a displays the actual payment for "2021 / 07" and "2021 / 08", which are the month before the processing date, and displays the budget for "2021 / 09" and after, which are the processing date and month.

[0037] Furthermore, when the processing date is "2021 / 09", the display control unit 102a causes the monitor 114 to display in a display mode corresponding to the current payment performance status in the cells of each expense item. Specifically, when the processing date is "2021 / 09", the display control unit 102a causes the monitor 114 to highlight, for example, in white (without hatching), the expense items (cells D1, D2) for which the budget balance exceeds 0 (budget balance > 0) and no control request data exists.

[0038] In addition, the display control unit 102a displays on the monitor 114, for example, highlighted in yellow, items for which the budget balance exceeds 0 (budget balance > 0) and for which control request data exists when the processing date is "2021 / 09". Furthermore, in order to allow the user to intuitively understand that they cannot be selected using the input device 112, the display control unit 102a displays on the monitor 114 items for which the budget balance is 0 or less (budget balance ≦ 0) or items from the month before the processing date when the processing date is "2021 / 09", for example, highlighted in gray. This allows the user to intuitively understand the status of actual payment results for each expense item and month. As a result, it is possible to prevent a discrepancy between the budget management and payment for the current month.

[0039] Returning to FIG. 5, the description of step S104 and subsequent steps will be continued. In step S104, the judgment unit 102b judges whether or not the user has used the input device 112 to select a target cell of an expense item whose budget balance exceeds 0 (budget balance > 0) and for which no control request data exists. Specifically, as shown in FIG. 7, the judgment unit 102b judges whether or not the user has used the input device 112 to click a cursor A1 (symbol, figure, etc.) on cell D1, which is a target cell of an expense item whose budget balance exceeds 0 (budget balance > 0) and for which no payment request data exists, thereby selecting cell D1. If the judgment unit 102b judges that the user has used the input device 112 to select a target cell (e.g., cell D1) of an expense item whose budget balance exceeds 0 (budget balance > 0) and for which no control request data exists (step S104: Yes), the payment management device 100 proceeds to step S105, which will be described later. On the other hand, if the judgment unit 102b determines that the user has used the input device 112 to select a budget balance that exceeds 0 (budget balance > 0) and a payment target cell (e.g., cell D1) for an expense item for which no control request data exists (step S104: No), the payment management device 100 proceeds to step S109, which will be described later.

[0040] In step S105, the display control unit 102a causes the monitor 114 to display a payment request input screen corresponding to the target cell selected by the user using the input device 112. Specifically, the monitor 114 causes the monitor 114 to display a payment request input screen corresponding to the target cell selected by the user using the input device 112 (for example, cell D1 shown in FIG. 7).

[0041] Fig. 8 is a diagram showing an example of a payment request input screen that the display control unit 102a causes to be displayed on the monitor 114. As shown in Fig. 8, the payment request input screen P2 includes a payment request number display area B11, a payment destination display area B12, an occurrence date display area B13, a payment request date display area B14, and a payment request input data table T5.

[0042] Specifically, on the payment request input screen P2, the payment number (automatically assigned at the time of registration) is displayed in the payment request number display area B11, "XX legal processing" is displayed in the payment destination display area B12, "21 / 09 / 15" is displayed in the occurrence date display area B13, and "21 / 10 / 31" is displayed in the payment request date display area B14. Furthermore, the payment request input data table T5 holds the project CD, the expense name, the payment amount, the current month's budget balance, and the total budget balance in a linked manner. The user uses the input device 112 to register each item in the payment request input data table T5, for example, the payee, and corrects and inputs the payment amount as necessary. Specifically, the user uses the input device 112 to input "500" as the payment amount and registers it.

[0043] Returning to FIG. 5, the description of step S106 and subsequent steps will be continued. In step S106, the determination unit 102b determines whether the user has used the input device 112 to register a payee and, if necessary, corrected and registered the payment amount. If the determination unit 102b determines that the user has used the input device 112 to register a payee and, if necessary, corrected and registered the payment amount (step S106: Yes), the payment management apparatus 100 proceeds to step S107, which will be described later. On the other hand, if the determination unit 102b determines that the user has not used the input device 112 to register a payee and, if necessary, corrected and registered the payment amount (step S106: No), the payment management apparatus 100 returns to step S105, described above.

[0044] In step S107, the generating unit 102c generates payment request data according to the registration result registered by the user on the payment request input screen P2 using the input device 112, and stores the data in the storage unit 106. Fig. 9 is a diagram showing an example of a payment request data table in the payment request data 106b generated by the generating unit 102c. The payment request data table T6 shown in Fig. 9 holds a payment request number, an occurrence date, a scheduled payment date, a payee, an expense item name, and a payment amount in association with each other.

[0045] Specifically, the payment request data table T6 holds the payment request number "NY0004", the date of occurrence "2021 / 09 / 15", the scheduled payment date "2021 / 10 / 31", the payee "XX Judicial Scrivener", the project CD "PJ0001", the expense name "Registration Fee", and the payment amount "500" in association with each other. As a result, as shown in FIG. 10, the payment request data table T7 holds the payment request data table T6 in accordance with the registration result registered by the user on the payment request input screen P2 using the input device 112. In this case, as shown in FIG. 11, the display control unit 102a switches the display mode of the cell D1 on the payment schedule selection screen P1 from white highlighting to gray display on the monitor 114 so that the user cannot select the cell D1 with the cursor A1 using the input device 112. As a result, the user can confirm that the payment amount has been registered against the budget for the specified expense item in the current processing month, thereby preventing any discrepancy between the current month's budget management and payment.

[0046] Next, the determination unit 102b determines whether or not the user will end the payment request input using the input device 112 (step S108). If the determination unit 102b determines that the user will end the payment request input using the input device 112 (step S108: Yes), the payment management apparatus 100 ends this processing. On the other hand, if the determination unit 102b determines that the user will not end the payment request input using the input device 112 (step S108: No), the payment management apparatus 100 returns to step S103 and repeats the above-mentioned processing.

[0047] Here, a case where a partial payment request for the expense item of the current month is made in the above-mentioned steps S103 to S107 will be described. Fig. 11 is a diagram showing an example of a payment schedule selection screen that the display control unit 102a causes to be displayed on the monitor 114. Note that in Fig. 11, an example of the payment schedule selection screen that the display control unit 102a displays based on the budget data table T1 in Fig. 2 and the payment request data table T7 in Fig. 10 will be described.

[0048] As shown in FIG. 11, when the user selects cell D2 by using the input device 112 to click cursor A1 on cell D2, which is the target cell of an expense item whose budget balance exceeds 0 (budget balance > 0) and for which no control request data exists, the display control unit 102a causes the monitor 114 to display a payment request input screen corresponding to cell D2 selected by the user using the input device 112.

[0049] Fig. 12 is a diagram showing another example of a payment request input screen that the display control unit 102a causes to be displayed on the monitor 114. As shown in Fig. 12, the payment request input screen P3 includes a payment request number display area B11, a payment destination display area B12, an occurrence date display area B13, a payment request date display area B14, and a payment request input data table T5.

[0050] The user uses input device 112 to input "△△△Construction" in payment destination display area B12, "21 / 09 / 15" in occurrence date display area B13, and "21 / 10 / 31" in payment request date display area B14 on payment request input screen P3. In addition, the user uses input device 112 to input "80,000", which is part of the current month's budget balance, into the payment amount on payment request input screen P3.

[0051] Thereafter, the generating unit 102c generates payment request data 106b according to the registration result registered by the user on the payment request input screen P3 using the input device 112, and stores the generated payment request data 106b in the storage unit 106. Fig. 13 is a diagram showing an example of a payment request data table in the payment request data 106b generated by the generating unit 102c. The payment request data table T8 shown in Fig. 13 holds a payment request number, an occurrence date, a scheduled payment date, a payee, an expense item name, and a payment amount in association with each other.

[0052] Specifically, in the payment request data table T8, the payment request number is "NY0005", the date of occurrence is "2021 / 09 / 15", the scheduled payment date is "2021 / 10 / 31", the payee is "XX Construction", the project CD is "PJ0001", the expense name is "Construction Cost", and the payment amount is "80,000" are linked and stored. As a result, as shown in FIG. 14, the payment request data table T9 (line 6) reflects and stores the registration results registered by the user on the payment request input screen P3 using the input device 112. For this reason, as shown in FIG. 15, the display control unit 102a switches the display mode of the cell D2 on the payment schedule selection screen P1 from white highlighting to yellow highlighting and displays it on the monitor 114. Note that in FIG. 15, the highlighting is expressed by hatching.

[0053] Returning to FIG. 5, the description of step S109 and subsequent steps will be continued. In step S109, the determination unit 102b determines whether or not the user has moved the cursor A1 over cell D2 by operating the input device 112. If the determination unit 102b determines that the user has moved the cursor A1 over cell D2 by operating the input device 112 (step S109: Yes), the payment management apparatus 100 proceeds to step S110, which will be described later. On the other hand, if the determination unit 102b determines that the user has not moved the cursor A1 over cell D2 by operating the input device 112 (step S109: No), the payment management apparatus 100 proceeds to step S108.

[0054] In step S110, the determination unit 102b determines whether or not there is a budget balance in cell D2 of the expense item selected by the user. If the determination unit 102b determines that there is a budget balance in cell D2 of the expense item selected by the user (step S110: Yes), the payment management apparatus 100 proceeds to step S111, which will be described later. On the other hand, if the determination unit 102b determines that there is no budget balance in cell D2 of the expense item selected by the user (step S110: No), the payment management apparatus 100 proceeds to step S108.

[0055] In step S111, the display control unit 102a refers to the payment request data 106b and displays the payment details indicating the payment status for the current month near cell D2. Specifically, as shown in Fig. 16, the display control unit 102a pops up and displays payment information W1 indicating the payment status for the current month for the expense item in cell D2 where the user has placed cursor A1 on the monitor 114. This allows the user to intuitively grasp the payment status for the current month for the current expense item.

[0056] Next, the judgment unit 102b judges whether or not the user has selected, using the input device 112, a target cell of an expense item whose budget balance exceeds 0 (budget balance>0) and in which control request data exists (step S112). Specifically, as shown in FIG. 16, the judgment unit 102b judges whether or not the user has selected cell D2 by clicking cursor A1 on cell D2, which is a target cell of an expense item whose budget balance exceeds 0 (budget balance>0) and in which control request data exists, using the input device 112. If the judgment unit 102b judges that the user has selected, using the input device 112, a target cell (e.g., cell D2) of an expense item whose budget balance exceeds 0 (budget balance>0) and in which control request data exists (step S112: Yes), the payment management device 100 proceeds to step S113, which will be described later. On the other hand, if the judgment unit 102b judges that the user has used the input device 112 to determine that the budget balance exceeds 0 (budget balance > 0) and that the user has not selected a payment target cell (e.g., cell D2) for an expense item for which control request data exists (step S112: No), the payment management device 100 proceeds to step S108.

[0057] In step S113, the display control unit 102a causes the monitor 114 to display a payment request input screen corresponding to the target cell selected by the user using the input device 112.

[0058] Fig. 17 is a diagram showing an example of a payment request input screen that the display control unit 102a causes to be displayed on the monitor 114. As shown in Fig. 17, the payment request input screen P5 includes a payment request number display area B11, a payment destination display area B12, an occurrence date display area B13, a payment request date display area B14, and a payment request input data table T5.

[0059] Specifically, on the payment request input screen P5, the payment number (automatically assigned at the time of registration) is displayed in the payment request number display area B11, "△△ Construction" is displayed in the payment destination display area B12, "21 / 09 / 15" is displayed in the occurrence date display area B13, and "21 / 10 / 31" is displayed in the payment request date display area B14. Furthermore, the payment request input data table T5 holds the project CD, the expense name, the payment amount, the current month's budget balance, and the total budget balance in association with each other. The user uses the input device 112 to register the payee, and corrects and inputs the payment amount as necessary. Specifically, the user uses the input device 112 to input the payment amount "20,000" so that there is no discrepancy with the current month's budget balance "20,000".

[0060] Returning to FIG. 5, the description of step S114 and subsequent steps will be continued. In step S114, the determination unit 102b determines whether the user has used the input device 112 to register a payee, and if necessary, corrected and registered the payment amount. If the determination unit 102b determines that the user has used the input device 112 to register a payee, and if necessary, corrected and registered the payment amount (step S114: Yes), the payment management apparatus 100 proceeds to step S115, which will be described later. On the other hand, if the determination unit 102b determines that the user has not used the input device 112 to register a payee, and if necessary, corrected and registered the payment amount (step S114: No), the payment management apparatus 100 returns to step S113, described above.

[0061] In step S115, the generating unit 102c generates payment request data 106b according to the registration result registered by the user on the payment request input screen P2 using the input device 112, and stores the data in the storage unit 106. Fig. 18 is a diagram showing an example of a payment request data table in the payment request data 106b generated by the generating unit 102c. The payment request data table T10 shown in Fig. 18 holds a payment request number, an occurrence date, a scheduled payment date, a payee, an expense item name, and a payment amount in association with each other.

[0062] Specifically, the payment request data table T10 holds the payment request number "NY0006", the date of occurrence "2021 / 09 / 15", the scheduled payment date "2021 / 10 / 31", the payee "△△ Construction", the project CD "PJ0001", the expense name "Construction Cost", and the payment amount "20,000" in association with each other. As a result, as shown in FIG. 19, the payment request data table T11 holds the payment request data table T10 in accordance with the registration result registered by the user on the payment request input screen P3 using the input device 112. For this reason, as shown in FIG. 20, the display control unit 102a switches the display mode of the cell D2 on the payment schedule selection screen P1 from yellow highlighting to gray display on the monitor 114 so that the user cannot select the cell D1 with the cursor A1 using the input device 112. As a result, the user can confirm that the payment amount for the budget of the specified expense item in the processing month has been registered, thereby preventing a discrepancy between the budget management and payment for the month. After step S114, the payment management device 100 proceeds to step S108.

[0063] According to the embodiment described above, the display control unit 102a refers to the budget data 106a and the payment request data 106b, and displays the payment schedule selection screen P1 including budget total information that totals the budget for each expense item and actual payment information that reflects the status of actual payments for each expense and month on the monitor 114. This allows the user to grasp the status of actual payments for each expense and month, thereby preventing discrepancies from occurring between the budget management and payment for the current month.

[0064] Also, according to the embodiment, the display control unit 102a displays, on the payment schedule selection screen P1, actual payment information K2 for each expense item and month in the month before the processing month, and total budget information K1 relating to the budget for each expense item and month after the processing month, as actual payment information. This allows the user to grasp the status of actual payments for each expense item and month while checking the total budget information K1 for each expense item and month and the actual payment information K2 in the month before the processing month, thereby preventing a discrepancy between the budget management and payment for the current month.

[0065] According to the embodiment, the display control unit 102a changes the display mode of each cell by expense item in the payment schedule selection screen P1 according to the budget balance based on the budget amount and the payment amount. Therefore, the user can intuitively grasp the actual payment status by expense and month.

[0066] Furthermore, according to the embodiment, the display control unit 102a displays the cells of the expense items with budget balances on the payment schedule selection screen P1 in an emphasized manner based on the budget amount and the payment amount, compared with the cells of the expense items with no budget balances and the cells of the expense items of the month before the processing month. This allows the user to grasp the status of the actual payment for each expense item in the processing month.

[0067] Furthermore, according to the embodiment, the display control unit 102a displays, on the payment schedule selection screen P1, the display mode of the cells of expense items that have a budget balance and payment request data 106b in an emphasized manner compared to the display mode of the cells of expense items that have a budget balance and no payment request data 106b. This allows the user to distinguish and understand the cells of expense items that have payment request data 106b and the cells of expense items that do not have payment request data 106b.

[0068] Furthermore, according to the embodiment, when the judgment unit 102b judges that there is a budget balance on the payment schedule selection screen P1 and that the cursor A1 is placed by the input device on the display area of ​​the cell containing the payment request data 106b, the display control unit 102a causes the payment information W1 indicating the current payment status to be displayed around the display area of ​​the cell containing the payment request data 106b. This allows the user to grasp the current payment status.

[0069] Furthermore, according to the embodiment, when a cell of an expense item with a budget balance is selected on the payment schedule selection screen P1 based on the budget amount and payment amount, the display control unit 102a changes the payment request input screen P2 of the selected expense item to the payment schedule selection screen P1 and displays it on the monitor 114. This allows the user to input a payment request for the desired expense item.

[0070] [3. 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 goals 8 and 9 of the SDGs.

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

[0072] Furthermore, this embodiment can contribute to strengthening control and governance, making it possible to contribute to Goal 16 of the SDGs.

[0073] [4. Other embodiments] The present invention may be embodied in various different embodiments other than those described above within the scope of the technical concept set forth in the claims.

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

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

[0076] Furthermore, with regard to the payment management device 100, each component shown in the figure is a functional concept, and does not necessarily have to be physically configured as shown in the figure.

[0077] For example, the processing functions of the payment management apparatus 100, particularly the processing functions performed by the control unit, may be realized in whole or in part by a CPU and a program interpreted and executed by the CPU, or may be realized as hardware using wired logic. The program is recorded on a non-transient computer-readable recording medium that contains programmed instructions for causing the information processing device to execute the processes described in this embodiment, and is mechanically read by the payment management apparatus 100 as necessary. That is, a computer program for giving instructions to the CPU in cooperation with the OS and performing 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 cooperates with the CPU to form the control unit.

[0078] In addition, this computer program may be stored in an application program server connected to the payment management apparatus 100 via any network, and it is also possible to download all or part of it as needed.

[0079] In addition, the program for executing the process described in this embodiment may be stored in a non-transient computer-readable recording medium, or may be configured as a program product. Here, the "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.

[0080] Moreover, a "program" is a data processing method written in any language or description method, and may be in any form, such as source code or binary code. Note that a "program" is not necessarily limited to a single configuration, but also includes a distributed configuration as multiple modules or libraries, and a program that works with a separate program, such as an OS, to achieve its function. 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, may use well-known configurations and procedures.

[0081] The various databases etc. 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 etc. used for various processes and providing websites.

[0082] The payment management device 100 may be configured as an information processing device such as a known personal computer or workstation, or may be configured as the information processing device to which any peripheral device is connected. The payment management device 100 may be realized by implementing software (including programs, data, etc.) that causes the device to realize the processes described in this embodiment.

[0083] 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 functionally or physically distributed and integrated in any unit according to various additions or functional loads. In other words, the above-mentioned embodiments can be implemented in any combination, or the embodiments can be implemented selectively. [Industrial Applicability]

[0084] The present invention is useful in industries such as real estate development, where budget management and payment are closely linked in the investment recovery business. [Explanation of symbols]

[0085] 100 Payment Management Device 102 Control section 102a Display control unit 102b Judgment section 102c generator 104 Communication interface section 106 Storage section 106a Budget Data 106b Payment request data 106c Control Master 108 Input / Output Interface Section 112 Input Devices 114 Output Device 200 Servers 300 Network

Claims

1. A payment management device including a control unit, Budget data that links and manages the expense name, year and month, and budget amount for each project name, Payment request data that links and manages the payment date, the scheduled payment date, the payee, the project name, the expense item, and the payment amount; is accessible to The control unit is a display control means for displaying a payment schedule selection screen including budget total information obtained by summing up the budget for each expense item with reference to the budget data and the payment request data, and actual payment information reflecting the actual payment status for each expense item and each month with respect to the budget balance for each expense item in the processing year and month according to the presence or absence of the payment request data; A payment management device comprising:

2. The display control means On the payment schedule selection screen, actual payment results for each expense item and month in the month before the processing month and whether or not there is payment request data for the budget amount for each expense item and month after the processing month are displayed as the actual payment information.

2. The payment management device according to claim 1.

3. The display control means According to a budget balance based on the budget amount and the payment amount, a display mode of a cell of an expense item having a budget balance and a display mode of a cell of an expense item having a budget balance that has exceeded the budget balance are changed and displayed on the payment schedule selection screen.

3. A payment management device as claimed in claim 1 or 2.

4. The display control means According to a budget balance based on the budget amount and the payment amount, a display mode of a cell of an expense item having a budget balance on the payment schedule selection screen is highlighted as compared with a cell of an expense item having no budget balance.

4. A payment management device according to claim 1, wherein:

5. The display control means a display mode of a cell of an expense item having said budget balance and said payment request data is highlighted as compared with a display mode of a cell of an expense item having said budget balance and said payment request data not being displayed; 5. The payment management device according to claim 4.

6. a determination means for determining whether or not the budget balance exists and whether or not a symbol indicating an input position has been placed on a display area of ​​a cell containing the payment request data; The display control means when the budget balance exists and the determination means determines that the symbol has been placed, payment information showing a current payment status is displayed around a display area of ​​a cell containing the payment request data; 6. The payment management device according to claim 5.

7. The display control means When a cell of an expense item having a budget balance is selected based on the budget amount and the payment amount, a payment request input screen for the selected expense item is displayed instead of the payment schedule selection screen. A payment management device according to any one of claims 1 to 6.

8. further comprising a generating means for generating and storing the payment request data based on the input contents entered on the payment request input screen; 8. The payment management device according to claim 7.

9. A budget payment management method executed by a payment management device having a control unit, The payment management device Budget data that links and manages the expense name, year and month, and budget amount for each project name, Payment request data that links and manages the payment date, the scheduled payment date, the payee, the project name, the expense item, and the payment amount; is accessible to Executed by the control unit, a display control step of displaying a payment schedule selection screen including budget total information obtained by summing up the budget for each expense item by referring to the budget data and the payment request data, and actual payment information reflecting the actual payment status for each expense item and each month with respect to the budget balance for each expense item in the processing year and month depending on the presence or absence of the payment request data, A budget payment management method comprising:

10. A budget payment management program executed by a payment management device having a control unit, The payment management device Budget data that links and manages the expense name, year and month, and budget amount for each project name, Payment request data that links and manages the payment date, the scheduled payment date, the payee, the project name, the expense item, and the payment amount; is accessible to To cause the control unit to execute a display control step of displaying a payment schedule selection screen including budget total information obtained by summing up the budget for each expense item by referring to the budget data and the payment request data, and actual payment information reflecting the actual payment status for each expense item and each month with respect to the budget balance for each expense item in the processing year and month depending on the presence or absence of the payment request data, A budget payment management program comprising:

Images