Approval workflow order apparatus, approval workflow order method and approval workflow order program

Abstract

To provide an approval workflow order apparatus, an approval workflow order method and an approval workflow order program which enable plural payments management relative to plural vendors by one approval request.SOLUTION: An approval workflow order apparatus according to the present embodiment comprises a control unit, and is accessible to budget data on budget allocated by department, expense budget change data on the change of the budget data and payment data on the budget data. The control unit comprises: a vendor payment advance application data creation unit for creating vendor payment advance application data on purchase application for received approval; a vendor payment application data creation unit for creating vendor payment application data by vendor on the purchase application; and a purchase application determination unit for determining whether the purchase application by vendor is final or not.SELECTED DRAWING: Figure 1

Description

Technical Field

[0001] The present invention relates to a requisition workflow ordering device, a requisition workflow ordering method, and a requisition workflow ordering program.

Background Art

[0002] Regarding the payment of policy expenses such as campaigns in financial institutions, a requisition application is made in advance, and after approval, payment is made to the contractor within the range of the requisition amount. However, in a general payment system, it is usually the case that one payment is made for one requisition. Therefore, it is not possible to make multiple payments to multiple contractors with a single requisition application. When multiple payments are made with a single requisition application, separate management of the requisition balance is required, and the management becomes very complicated.

[0003] Patent Document 1 describes a requisition workflow ordering device including a control unit. The control unit includes data acquisition means for acquiring application data for which a purchase application has been made, approval processing means for performing approval processing to obtain approval based on the requisition content of the application data, order processing means for creating order data based on the requisition content of the application data for which final approval has been obtained, output means for outputting an order form from the order data, and inspection processing means for performing inspection when there is a receipt of the goods ordered in the order form. The inspection processing means is characterized by detecting that the billing amount at the time of receipt of the goods exceeds a predetermined ratio from the approved amount obtained by the approval processing means.

Prior Art Documents

Patent Documents

[0004]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0005] Although the apparatus of Patent Document 1 can perform an internal approval application and an order processing, it cannot manage multiple payments to multiple vendors in one internal approval application.

[0006] The present invention has been made in view of the above problems, and an object thereof is to provide an internal approval workflow ordering apparatus, an internal approval workflow ordering method, and an internal approval workflow ordering program that enable management of multiple payments to multiple vendors in one internal approval application.

Means for Solving the Problems

[0007] In order to solve the above-described problems and achieve the object, an internal approval workflow ordering apparatus according to the present invention is an internal approval workflow ordering apparatus including a control unit, and is accessible to budget data regarding a budget tabulated for each department, expense budget change data regarding a change in the budget data, and payment data related to the budget data. The control unit includes a vendor payment pre-application data creation unit that creates vendor payment pre-application data regarding a purchase application for an approved internal approval, a vendor payment application data creation unit that creates vendor payment application data for each vendor regarding the purchase application, and a purchase application determination unit that determines whether a purchase application for each vendor is final.

[0008] Further, the internal approval workflow ordering apparatus according to the present invention includes an application amount determination unit that compares a budget balance with a purchase estimated amount of the purchase application and determines an excess of the purchase estimated amount over the budget balance, and a warning unit that issues a warning when the application amount determination unit determines that the purchase estimated amount exceeds the budget balance.

[0009] Further, in the internal approval workflow ordering apparatus according to the present invention, the vendor payment pre-application data creation unit accepts an application for additional budget and creates vendor payment pre-application data.

[0010] Further, in the internal approval workflow ordering apparatus according to the present invention, the vendor payment pre-application data creation unit accepts an application for account transfer and creates vendor payment pre-application data.

[0011] In addition, in the requisition workflow order device according to the present invention, the pre-application data creation unit for vendor payment creates pre-application data for vendor payment by accepting an application for additional requisition.

[0012] In addition, the requisition workflow order method according to the present invention is a requisition workflow order method for causing a requisition workflow order device including a control unit to execute. The requisition workflow order device can access budget data regarding the budget tabulated for each department, expense budget change data regarding changes to the budget data, and payment data related to the budget data. The method includes a step of creating pre-application data for vendor payment regarding a purchase application for an approved requisition to be executed by the control unit, a step of creating vendor payment application data for each vendor regarding the purchase application, and a determination step of determining whether the purchase application for each vendor is the final one.

[0013] In addition, the requisition workflow order program according to the present invention is a requisition workflow order program for causing a requisition workflow order device including a control unit to execute. The requisition workflow order device can access budget data regarding the budget tabulated for each department, expense budget change data regarding changes to the budget data, and payment data related to the budget data. The program is for causing the control unit to execute a step of creating pre-application data for vendor payment regarding a purchase application, a step of creating vendor payment application data for each vendor regarding the purchase application, and a determination step of determining whether the purchase application for each vendor is the final one.

Advantages of the Invention

[0014] According to the present invention, there is an effect that it is possible to manage multiple payments to multiple vendors for one requisition application.

Brief Description of the Drawings

[0015]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Figure 13

Figure 14

Figure 15

Figure 16

Figure 17

Figure 18

Figure 19

Figure 20

Figure 21

Figure 22

Figure 23

Figure 24

Embodiments for Carrying Out the Invention

[0016] Embodiments of a requisition workflow ordering device, a requisition workflow ordering method, and a requisition workflow ordering program according to the present invention will be described in detail below with reference to the drawings. Note that the present invention is not limited by the present embodiment.

[0017] [1. Configuration] An example of the configuration of the requisition workflow ordering device according to the present embodiment will be described with reference to FIG. 1 and the like. FIG. 1 is a diagram showing an example of the configuration of a requisition workflow ordering device 100 according to the present embodiment.

[0018] The requisition workflow ordering device 100 is constructed based on a commercially available desktop personal computer. Note that the requisition workflow ordering device 100 is not limited to being constructed based on a stationary information processing device such as a desktop personal computer, and may be constructed based on a portable information processing device such as a commercially available notebook personal computer, a PDA (Personal Digital Assistants), a smartphone, or a tablet personal computer.

[0019] The requisition workflow ordering device 100 includes a control unit 102, a communication interface unit 104, a storage unit 106, and an input / output interface unit 108. Each unit included in the requisition workflow ordering device 100 is communicably connected via an arbitrary communication path.

[0020] The communication interface unit 104 communicably connects the requisition workflow ordering 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 a function of communicating data with other devices via a communication line. Here, the network 300 has a function of communicably connecting the requisition workflow ordering device 100 and the server device 200 to each other, and is, for example, the Internet or a LAN (Local Area Network). Note that the data stored in the storage unit 106 may be stored in the server device 200, for example.

[0021] An input / output interface unit 108 has an input device 400 and an output device 500 connected thereto. As the output device 500, in addition to a monitor (including a home television), a speaker or a printer can be used. As the input device 400, in addition to a keyboard, a mouse, and a microphone, a monitor that cooperates with the mouse to realize a pointing device function can be used. Note that hereinafter, the output device 500 may be described as the monitor 500, and the input device 400 may be described as the keyboard 400 or the mouse 400.

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

[0023] The storage unit 106 stores, for example, budget data 106a, expense budget change data 106b, payment data 106c, prior application data 106d for payment to a vendor, application data 106e for payment to a vendor, and the like.

[0024] The budget data 106a is data regarding the budget of the policy implementation expenses counted for each department. Data regarding the budget for each request approved by the request workflow ordering device 100 or the like is stored. As shown in an example in FIG. 3, information such as the budget registration date, department, expense item, budget amount, etc. is stored in the budget data 106a.

[0025] The expense budget change data 106b is data regarding the change of the budget data 106a counted for each department. As shown in an example in FIG. 4, information such as the budget change date, department, expense item, changed budget amount, etc. is stored in the expense budget change data 106b. In the expense budget change data 106b of FIG. 4, the amount "100,000" diverted to other items on May 1, 2023 is counted as a reduction, and the additional budget "200,000" is added on June 1, 2023.

[0026] The payment data 106c is data regarding the payment of the budget data 106a counted for each department. As shown in an example in FIG. 5, information such as the payment date, department, expense item, payment amount, etc. is stored in the payment data 106c. The payment data 106c stores data where the request is approved for the budget of the same policy implementation expenses and the payment is made by a purchase request. In the payment data 106c of FIG. 5, "300,000" is spent as hospitality expenses on July 1, 2023.

[0027] The advance application data 106d for payment to vendors is data regarding the purchase request for the approved request. As shown in an example in FIG. 6, information such as the voucher number, department, expense item, estimated purchase amount, initial budget, request number, remaining amount of the advance request, etc. is stored in the advance application data 106d for payment to vendors. The advance application data 106d of FIG. 6 is data regarding the request number "RONG001" and applies for a payment of "11,000" as "10001 hospitality expenses".

[0028] The vendor payment application data 106e is data related to the payment application for each vendor regarding the purchase application. Information such as the voucher number, voucher type, supplier, department, transaction classification, and planned purchase is stored in the vendor payment application data 106e.

[0029] The control unit 102 is a CPU or the like that comprehensively controls the requisition workflow ordering device 100. The control unit 102 has an internal memory for storing control programs such as the OS, programs defining various processing procedures, and required data, and executes various information processes based on these stored programs.

[0030] Functionally conceptually, the control unit 102 includes a vendor pre-application data creation unit 102a, a vendor payment application data creation unit 102b, a purchase application determination unit 102c, a purchase amount determination unit 102d, a warning unit 102e, and the like.

[0031] The vendor payment pre-application data creation unit 102a creates vendor payment pre-application data 106d regarding the purchase application for the approved requisition.

[0032] The vendor payment application data 102b creates vendor payment application data 106e for each vendor regarding the purchase application.

[0033] The purchase application determination unit 102c determines whether the purchase application for each vendor is the final one.

[0034] [2. Process] Here, a specific example of the process executed by the requisition workflow ordering device 100 will be described with reference to FIGS. 2 to 22.

[0035] FIG. 2 is a diagram showing an example of a pre-application screen MA-1 for contractor payment of the request-for-proposal workflow ordering device 100 according to the present embodiment. When a user logs in to the request-for-proposal workflow ordering device 100, the user's department is automatically set to "Department" based on the login information. Along with the setting of "Department", the local budget (A) related to the policy expenses of "Department", the amount diverted to other items (B), the approved additional budget (C), the expenditure amount (D), and the budget balance (A - B + C - D) are automatically set with reference to the budget data 106a, the expense budget change data 106b, and the payment data 106c.

[0036] On the pre-application screen MA-1 for contractor payment, the user inputs the request-for-proposal number, the estimated purchase amount, the expense item, etc., or refers to the request-for-proposal data stored in the storage unit by inputting the request-for-proposal number, and other information is automatically input.

[0037] On the pre-application screen MA-1 for contractor payment in FIG. 2, with reference to the budget data 106a, the expense budget change data 106b, and the payment data 106c in FIGS. 3 to 5, the initial budget (A) is the budget amount in the budget data 106a, the amount diverted to other items (B) and the approved additional budget (C) are the expense budget change data 106b, and the expenditure amount (D) is the payment amount in the expenditure data. The budget balance (A - B + C - D) is also calculated and set from the above items. The final budget balance is set to the numerical value obtained by adding and / or subtracting the amount of transfer between expenses, the additional budget, and the estimated purchase amount. On the pre-application screen MA-1 for contractor payment, since there is no input of the amount of transfer between expenses and the additional budget, "289,000" obtained by subtracting the estimated purchase amount "11,000" from the budget balance (A - B + C - D) "300,000" is input.

[0038] When the user inputs the request-for-proposal number, etc., the pre-application data creation unit 102a for contractor payment creates pre-application data 106d for contractor payment related to the purchase application for the approved request-for-proposal (see FIG. 6). Since the purchase application to the contractor has not been made, the final payment of the pre-application data 106d created from the input information on the pre-application screen MA-1 for contractor payment is in the state of "0: in progress".

[0039] After that, using the vendor payment application screens MB-1 and MB-2 shown as an example in FIGS. 7 and 10, a payment application for each vendor is made regarding the purchase application. The requisition workflow ordering device 100 according to the present embodiment enables payments to multiple vendors for one requisition. Here, a case where payments are made to two vendors for one requisition will be described.

[0040] First, a payment application for the first vendor is made using the vendor payment application screen. As shown in FIG. 7, after inputting the vendor pre-payment application screen MA-1 and opening the vendor payment application screen MB-1, the requisition number is automatically input and the pre-application slip number is automatically assigned. The user inputs other items, such as the supplier, the estimated purchase amount, etc. In FIG. 7, there are two payments, "4,400" and "3,300", for the supplier "XX Shoko", and each payment is input respectively. Also, since the input on the vendor payment application screen MB-1 is the first payment, the final payment column is in the state of "□ (unchecked)".

[0041] When the content of the vendor payment application is input on the vendor payment application screen MB-1, the vendor payment application data creation unit 102b creates vendor payment application data 106e-1 shown as an example in FIG. 8 for each vendor regarding the purchase application. The vendor payment application data 106e-1 has information including the slip type, transaction category, amount, consumption tax, etc. created for each payment.

[0042] Also, the vendor pre-payment application data creation unit 102a creates vendor pre-payment application data 106d-1 that reflects the content of the vendor payment application input on the vendor payment application screen MB-1. As shown in FIG. 9, in the vendor pre-payment application data 106d-1, the pre-requisition balance is updated to the amount "3,300" obtained by subtracting the estimated purchase amount "7,700" on the vendor payment application screen MB-1 from the pre-requisition balance "11,000" of the vendor pre-payment application data 106d in FIG. 6. Also, since the final payment column on the vendor payment application screen MB-1 is in the state of "□ (unchecked)", the final payment in the vendor pre-payment application data 106d-1 remains in the state of "0: in progress".

[0043] Subsequently, a payment application for the second vendor is made on the vendor payment application screen. As shown in FIG. 10, after inputting the vendor payment application screen MB-1 and opening the vendor payment application screen MB-2, the approval number is automatically input, and the user inputs other items, such as the pre-application slip number, the supplier, the estimated purchase amount, etc. In FIG. 9, there is one payment of "3,300" for the supplier "△△ Shoko", and the input is made for this payment. Since the input on the vendor payment application screen MB-2 is the final payment for the approval number "RONG001", the "□ (checked)" is input in the final payment column.

[0044] When the content of the vendor payment application is input on the vendor payment application screen MB-2, the vendor payment application data creation unit 102b creates vendor payment application data 106e-2 shown in FIG. 11 for each vendor regarding the purchase application.

[0045] In addition, the vendor payment pre-application data creation unit 102a creates vendor payment pre-application data 106d-2 that reflects the content of the vendor payment application input on the vendor payment application screen MB-2. As shown in FIG. 12, in the vendor payment pre-application data 106d-2, the remaining amount of the pre-approval is updated to "0", which is the amount obtained by subtracting the estimated purchase amount of "3,300" on the vendor payment application screen MB-2 from the remaining amount of the pre-approval of "3,300" in the vendor payment pre-application data 106d-1 in FIG. 9. Also, since the "□ (checked)" is in the final payment column on the vendor payment application screen MB-2, the purchase application determination unit 102c determines that the purchase application for each vendor is the final one, and in the vendor payment pre-application data 106d-2, the final payment is updated to the state of "1: final". Note that when the final payment is "□ (checked)" and the remaining amount of the final approval in the vendor payment pre-application data 106d-2 is not "0", the warning unit 102e issues an error.

[0046] In the above purchase application, since the total purchase deposit amount of the two vendor payment applications in FIGS. 7 and 10 (the sum of "7,700" and "3,300") matches the purchase deposit amount "11,000" approved by the internal document (see FIG. 2), the purchase application is approved. However, the total purchase deposit amount of the vendor payment applications may exceed the purchase deposit amount approved by the internal document. If the application is passed in this state, payment may not be possible, leading to troubles.

[0047] In the internal document workflow ordering device 100 according to this embodiment, when the purchase deposit amount of the vendor payment application exceeds the purchase deposit amount approved by the internal document, the warning unit 102e issues an error.

[0048] FIG. 13 is a diagram showing an example of the vendor payment pre-application screen MA-3. Similar to the vendor payment pre-application screen MA-1, when the user logs in to the internal document workflow ordering device 100, the user's affiliated department is automatically set to "Department" based on the login information, and the local budget (A) related to the policy expenses of the "Department", the amount diverted to other items (B), the approved additional budget (C), the expenditure amount (D), and the budget balance (A - B + C - D) are automatically set with reference to the budget data 106a, the expense budget change data 106b, and the payment data 106c.

[0049] On the vendor payment pre-application screen MA-3, the user inputs the internal document number, the purchase deposit amount, the expense item, etc., or refers to the internal document data stored in the storage unit by inputting the internal document number, and other information is automatically input.

[0050] When the user inputs the internal document number, etc., the vendor payment pre-application data creation unit 102a creates the vendor payment pre-application data 106d-3 related to the purchase application for the approved internal document (see FIG. 14). The vendor payment pre-application data 106d-3 created from the input information on the vendor payment pre-application screen MA-3 is in the state where the final payment is "0: in progress".

[0051] On the pre-application screen MA-3 for vendor payment in FIG. 13, the purchase reservation amount of "550,000" for the advertising expense of "20001" approved with the memo number "RING002" is entered. The budget balance (A - B + C - D) is "300,000", and the final budget balance is "-250,000" obtained by subtracting the purchase reservation amount of "550,000" from the budget balance (A - B + C - D) of "300,000" because there is no transfer amount between expenses and no additional budget.

[0052] The application amount determination unit 102d compares the budget balance (A - B + C - D) of "300,000" with the purchase reservation amount of "550,000" in the purchase application and determines whether there is an excess of the purchase reservation amount over the budget balance. In the case of FIG. 13, it is determined that the purchase reservation amount exceeds the budget balance.

[0053] When the application amount determination unit 102d determines that the purchase reservation amount exceeds the budget balance, the warning unit 102e issues an error. Due to the error, the application on the pre-application screen MA-3 for vendor payment is rejected.

[0054] In the memo workflow ordering device 100 according to the present embodiment, when the purchase reservation amount exceeds the budget balance, the warning unit 102e issues an error and the application cannot be made. However, an application for increasing the amount to the budget management section or a transfer application from another account can be accepted to continue the purchase application.

[0055] FIG. 15 is a diagram showing an example of the pre-application screen MA-4 for vendor payment with an application for increasing the amount to the budget management section. The pre-application screen MA-4 for vendor payment is obtained by the user entering "300,000" in the additional budget column from the pre-application screen MA-3 for vendor payment. By entering the additional budget, the final budget balance becomes "50,000" obtained by adding the additional budget of "300,000" to the budget balance (A - B + C - D) of "300,000" and subtracting the purchase reservation amount of "550,000".

[0056] When the user inputs a request number or the like, the pre-application data creation section 102a for payment to the contractor creates pre-application data 106d-4 for payment to the contractor (see Fig. 16). In the pre-application data 106d-4 for payment to the contractor, "300,000" is input in the item of additional budget input on the pre-application screen MA-4 for payment to the contractor, and the final budget balance becomes "50,000".

[0057] When additional budget and purchase applications are made and approved according to the content of the pre-application screen MA-4 for payment to the contractor, it is updated to expense budget change data 106b-4 including the content of the newly applied and approved additional application (see Fig. 17). Also, it is updated to payment data 106c-4 including the content of the approved purchase application (see Fig. 18).

[0058] Fig. 19 is a diagram showing an example of the pre-application screen MA-5 for payment to the contractor involving account transfer. The pre-application screen MA-5 for payment to the contractor is obtained by the user inputting the transfer item and the amount of transfer between expenses from the pre-application screen MA-3 for payment to the contractor. By inputting the amount of transfer between expenses "350,000", the final budget balance is "100,000" obtained by adding the amount of transfer between expenses "350,000" to the budget balance (A - B + C - D) of "300,000" and subtracting the purchase advance amount of "550,000".

[0059] When the user inputs a request number or the like, the pre-application data creation section 102a for payment to the contractor creates pre-application data 106d-5 for payment to the contractor (see Fig. 20). In the pre-application data 106d-4 for payment to the contractor, the transfer item and the amount of transfer between expenses input on the pre-application screen MA-5 for payment to the contractor are input.

[0060] When a purchase application involving account transfer is made and approved according to the content of the pre-application screen MA-5 for payment to the contractor, it is updated to expense budget change data 106b-5 including the content of the newly applied and approved account transfer (see Fig. 21).

[0061] The requisition workflow ordering device 100 according to this embodiment can make payments to a plurality of vendors for one requisition using the pre-application screen for vendor payment and the application screen for vendor payment. Therefore, it becomes easy to manage the total amount of payment amounts within the requisition. Also, when the planned purchase amount exceeds the budget balance, the application is rejected, so it is possible to prevent troubles due to non-payment. Furthermore, when the planned purchase amount exceeds the budget balance, an application for additional budget or a transfer application from another account can be accepted simultaneously with the purchase application to continue the purchase application, so the procedures required for the application procedures can be simplified.

[0062] In addition, when there is a change in the requisition (parent) for the payment of approved policy expenses that results in a budget increase and further a requisition (child) application is made, the related requisitions (parent, child) can be linked to easily perform budget management.

[0063] FIG. 22 is a diagram showing an example of the requisition vendor payment application screen MA-6. The requisition number "RING004" is a budget related to the requisition number "RING002", and it is linked by inputting "RING002" as the original requisition number. On the pre-application screen for vendor payment MA-6, the additional budget "300,000" approved by "RING004" is automatically input from the expense budget change data 106b-6 (see FIG. 23).

[0064] When a user inputs a requisition number or the like, the pre-application data creation unit 102a for vendor payment creates pre-application data 106d-6 for vendor payment (see FIG. 24). In the pre-application data 106d-4 for vendor payment, "300,000" is input in the item of the additional budget input on the pre-application screen for vendor payment MA-6.

[0065] [3. Contribution to the Sustainable Development Goals (SDGs) Led by the United Nations] According to this embodiment, it is possible to contribute to promoting business efficiency and appropriate management decisions of the company, so it is possible to contribute to Goals 8 and 9 of the SDGs.

[0066] In addition, according to the present embodiment, it is possible to contribute to reducing waste loss and promoting paperless and digitalization, so it is possible to contribute to SDGs Goals 12, 13, and 15.

[0067] In addition, according to the present embodiment, it is possible to contribute to strengthening control and governance, so it is possible to contribute to SDGs Goal 16.

[0068] [4. Other Embodiments] The present invention may be implemented in various different embodiments within the scope of the technical idea described in the claims, in addition to the embodiments described above.

[0069] For example, among the processes described in the embodiment, all or part of the processes described as being automatically performed can be manually performed, or all or part of the processes described as being manually performed can be automatically performed by a known method.

[0070] In addition, regarding the request for approval workflow ordering device 100, each component shown in the drawings is a functional concept, and it is not necessarily physically configured as shown in the drawings.

[0071] In addition, regarding the request for approval workflow ordering device 100, each component shown in the drawings is a functional concept, and it is not necessarily physically configured as shown in the drawings.

[0072] For example, regarding the processing functions provided by the requisition workflow ordering device 100, particularly each processing function performed by the control unit, all or any part of them may be realized by a CPU and a program interpreted and executed by the CPU, or may be realized as hardware by wired logic. Note that the program is recorded on a non-transitory computer-readable recording medium including programmed instructions for causing the information processing device to execute the processing described in the present embodiment, and is mechanically read by the requisition workflow ordering device 100 as necessary. That is, a computer program for giving instructions to the CPU in cooperation with the OS to perform various processes is recorded in a storage unit such as a ROM or an HDD (Hard Disk Drive). This computer program is executed by being loaded into the RAM and constitutes the control unit in cooperation with the CPU.

[0073] Further, this computer program may be stored in an application program server connected to the requisition workflow ordering device 100 via an arbitrary network, and all or part of it can be downloaded as necessary.

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

[0075] Also, the "program" is a data processing method described in any language or description method, and is not limited to a form such as source code or binary code. Note that the "program" is not necessarily limited to being configured singly, and also includes those that are distributed as a plurality of modules or libraries, or those that achieve their functions in cooperation with other separate programs represented by an OS. Regarding the specific configuration, reading procedure, and installation procedure after reading for reading the recording medium in each device shown in the embodiment, well-known configurations and procedures can be used.

[0076] The various databases and the like stored in the storage unit are storage means such as a memory device such as a RAM or a ROM, a fixed disk device such as a hard disk, a flexible disk, and an optical disk, and store various programs, tables, databases, and web page files used for various processes and website provision.

[0077] Further, the requisition workflow ordering 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 an arbitrary peripheral device is connected. Further, the requisition workflow ordering device 100 may be realized by installing software (including programs or data, etc.) for realizing the processes described in this embodiment in the device.

[0078] Furthermore, the specific forms of distribution and integration of the devices are not limited to those shown in the drawings, and all or part of them can be functionally or physically distributed and integrated in arbitrary units according to various additions or according to the functional load. That is, the above-described embodiments may be arbitrarily combined and implemented, or the embodiments may be selectively implemented.

Industrial Applicability

[0079] The present invention is particularly useful when performing a series of business management flowing from requisition to ordering.

Explanation of Signs

[0080] 100 Requisition Workflow Ordering Device 102 Control Unit 102a Contractor Payment Advance Application Data Creation Unit 102b Contractor Payment Application Data Creation Unit 102c Purchase Application Judgment Unit 102d Application Amount Judgment Unit 102e Warning Unit 104 Communication Interface Unit 106 Storage Unit 106a Budget Data 106b Expense Budget Change Data 106c Payment Data 106d Contractor Payment Advance Application Data 106e Contractor Payment Application Data 108 Input / Output Interface Unit 200 Server 300 Network 400 Input Device 500 output device

Claims

1. A requisition workflow ordering device comprising a control unit, budget data regarding the budget accounted for by each department, expense budget change data regarding changes to the budget data, payment data related to the budget data, is accessible to, The control unit, A vendor payment pre-application data creation unit that creates vendor payment pre-application data regarding a purchase application for an approved requisition, A vendor payment application data creation unit that creates vendor payment application data for each vendor regarding the purchase application, A purchase application determination unit that determines whether the purchase application for each vendor is final, A requisition workflow ordering device characterized by comprising the above.

2. An application amount determination unit that compares the budget balance with the purchase estimated amount of the purchase application and determines an excess of the purchase estimated amount over the budget balance, A warning unit that issues a warning when the application amount determination unit determines that the purchase estimated amount exceeds the budget balance, The requisition workflow ordering device according to claim 1, characterized by comprising the above.

3. The requisition workflow ordering device according to claim 1, wherein the vendor payment pre-application data creation unit receives an application for additional budget and creates vendor payment pre-application data.

4. The requisition workflow ordering device according to claim 1, wherein the vendor payment pre-application data creation unit receives an application for account transfer and creates vendor payment pre-application data.

5. The requisition workflow ordering device according to claim 1, wherein the vendor payment pre-application data creation unit receives an application for additional requisition and creates vendor payment pre-application data.

6. A requisition workflow ordering method for causing a requisition workflow ordering device comprising a control unit to execute, The requisition workflow ordering device, Budget data regarding the budget accounted for by each department, Expense budget change data regarding changes to the budget data, Payment data related to the budget data, Is accessible to, Causing the control unit to execute, A vendor payment pre-application data creation step of creating vendor payment pre-application data regarding a purchase application for an approved requisition, A vendor payment application data creation step of creating vendor payment application data for each vendor regarding the purchase application, A determination step of determining whether the purchase application for each vendor is final, A requisition workflow ordering method characterized by including the above.

7. A requisition workflow ordering program for causing a requisition workflow ordering device comprising a control unit to execute, The requisition workflow ordering device, Budget data regarding the budget calculated for each department, expense budget change data regarding the change of the budget data, payment data related to the budget data, are accessible, to the control unit, a vendor payment pre-application data creation step for creating vendor payment pre-application data regarding a purchase application for an approved internal document, a vendor payment application data creation step for creating vendor payment application data for each vendor regarding the purchase application, a determination step for determining whether the purchase application for each vendor is final, an internal document workflow order program for executing the above.

Images