JP6796504B2 - Payment request electronic approval device, payment request electronic approval method, and payment request electronic approval program - Google Patents

Description

The present invention relates to a payment request electronic approval device, a payment request electronic approval method, and a payment request electronic approval program.

According to Patent Document 1, the applicant and the approver enter the user ID and password from the Internet browser of the client computer when logging in to the system. The server / computer determines whether or not it is registered in the user authentication file, and login is permitted only if it is registered. At the same time as logging in, it is determined whether the applicant has the authority to issue an electronic slip, and only those who are determined to have the application authority can enter the application. Also, when the approver approves, it is judged whether or not the approver has the approval authority at the same time as logging in, and it is judged that the approver has the approval authority. The electronic approval system is disclosed.

Japanese Unexamined Patent Publication No. 2005-128986

However, Patent Document 1 has a problem that an electronic approval function cannot be provided for a payment request and the payment method determination process cannot be switched to some patterns.

The present invention has been made in view of the above problems, and is a payment request electronic approval device that enables paperless operation, labor saving in payment management or confirmation in the accounting department, and serial number management of payment application and settlement. , A payment request electronic approval method, and a payment request electronic approval program.

In order to solve the above-mentioned problems and achieve the object, the payment request electronic approval device according to the present invention is a payment request electronic approval device including a storage unit and a control unit, and the storage unit is a sales department. Setting whether or not electronic approval of debt payment schedule input is required, setting whether or not electronic approval of payment request input from the sales department to the accounting department is required, and electronic approval of the debt payment schedule input are described above. A pattern storage means for storing a plurality of approval patterns including setting whether or not to consider the payment request input as electronic approval is provided, and the control unit sets and approves the approval pattern applied to the debt in the sales department. When there is a setting means to be set as a pattern and a debt payment schedule input of the debt in the sales department, the presence or absence of electronic approval of the debt payment schedule input of the debt is confirmed based on the setting approval pattern, and the debt is concerned. When it is determined by the debt payment schedule input determination means for determining whether or not to accept the payment schedule input and the debt payment schedule input determination means to accept the debt payment schedule input, and the sales department of the debt says When a payment request is input to the accounting department, a payment request input determination means for confirming whether or not the payment request input is electronically approved based on the setting approval pattern and determining whether or not to accept the payment request input. When it is determined by the payment request input determination means that the payment request input is accepted, the payment request input is provided with a drafting means for drafting the payment request data of the payment request slip to the accounting department. ..

Further, the payment request electronic approval device according to the present invention further includes a payment processing execution means in which the control unit extracts a plurality of the payment request data for each predetermined summary unit and executes the payment process collectively. It is characterized by that.

Further, in the payment request electronic approval device according to the present invention, the predetermined summary unit is the business establishment, withdrawal payment destination, payment method, scheduled payment date, payment request number, payment department, currency, department, and / or. It is characterized by being an accounting slip number.

Further, the payment request electronic approval device according to the present invention is further characterized in that the control unit further includes a payment processing execution means for executing payment processing for each payment request data when the debt is an expense debt. To do.

Further, the payment request electronic approval device according to the present invention is characterized in that the debt payment schedule input is a prepaid request for the debt.

Further, the payment request electronic approval method according to the present invention is a payment request electronic approval method for causing a payment request electronic approval device including a storage unit and a control unit to execute the payment request electronic approval method, and the storage unit is a debt in the sales department. Set whether or not electronic approval of payment schedule input is required, set whether or not electronic approval of payment request input from the sales department to the accounting department is required, and electronically approve the debt payment schedule input. A pattern storage means for storing a plurality of approval patterns including setting whether or not to consider the input as electronic approval is provided, and the approval pattern applied to the debt in the sales department to be executed by the control unit is set and approved. When there is a setting step to be set as a pattern and a debt payment schedule input of the debt in the sales department, based on the setting approval pattern, it is confirmed whether or not there is electronic approval of the debt payment schedule input of the debt, and the debt is concerned. When it is determined in the debt payment schedule input determination step for determining whether or not to accept the payment schedule input and the debt payment schedule input determination step for accepting the debt payment schedule input, and from the sales department of the debt. When a payment request is input to the accounting department, the payment request input determination is determined based on the setting approval pattern to confirm the presence or absence of electronic approval of the payment request input and to determine whether to accept the payment request input. It is characterized by including a step and a drafting step of drafting payment request data of a payment request slip to the accounting department when it is determined in the payment request input determination step to accept the payment request input. To do.

Further, the payment request electronic approval program according to the present invention is a payment request electronic approval program for being executed by a payment request electronic approval device including a storage unit and a control unit, and the storage unit is a debt in a sales department. Set whether or not electronic approval of payment schedule input is required, set whether or not electronic approval of payment request input from the sales department to the accounting department is required, and electronically approve the debt payment schedule input. A pattern storage means for storing a plurality of approval patterns including setting whether or not to consider the input as electronic approval is provided, and the control unit uses the approval pattern applied to the debt in the sales department as the setting approval pattern. When there is a setting step to be set and a debt payment schedule input of the debt in the sales department, it is confirmed whether or not there is electronic approval of the debt payment schedule input of the debt based on the setting approval pattern, and the debt payment schedule is confirmed. When it is determined in the debt payment schedule input determination step for determining whether or not to accept the input and the debt payment schedule input determination step for accepting the debt payment schedule input, and the accounting from the sales department of the debt. When there is a payment request input to the department, based on the setting approval pattern, the payment request input determination step of confirming the presence or absence of electronic approval of the payment request input and determining whether to accept the payment request input When it is determined in the payment request input determination step that the payment request input is accepted, the issuance step of issuing the payment request data of the payment request slip to the accounting department is executed. ..

According to the present invention, there are effects such as paperless operation, labor saving in payment management or confirmation in the accounting department, and serial number management of payment application and settlement.

FIG. 1 is a block diagram showing an example of the configuration of the payment request electronic approval device. FIG. 2 is a flowchart showing an example of processing of the payment request electronic approval device in the present embodiment. FIG. 3 is a diagram showing an example of the overall configuration of the system including the payment request electronic approval device. FIG. 4 is a diagram showing an example of a pattern table in the present embodiment. FIG. 5 is a diagram showing an example of a payment request input screen. FIG. 6 is a diagram showing an example of a payment request detail input screen. FIG. 7 is a diagram showing an example of the transfer information screen. FIG. 8 is a diagram showing an example of a slip breakdown screen. FIG. 9 is a diagram showing an example of a payment request input transfer table. FIG. 10 is a diagram showing an example of a payment method confirmation processing screen and a list of screen items thereof. FIG. 11 is a diagram showing an example of summary unit switching of payment method determination processing and debt balance management by business establishment department. FIG. 12 is a diagram showing an example of summary unit switching of payment method determination processing and debt balance management by business establishment department.

Embodiments of the present invention will be described in detail with reference to the drawings. The present invention is not limited to the present embodiment.

[1. Overview]
First of all, there has been an electronic approval function for checking the contents of debt recording (accounts, etc.), but it is possible to electronically approve payment request operations that correspond to the business characteristics of product purchases and expense payments. There wasn't.

Therefore, in the present embodiment, it is possible to control the electronic approval of payment requests from the sales department to the accounting department in a general manner. Specifically, in the present embodiment, the presence / absence of approval / approval route may be set in advance by the electronic approval function common to other operations. Further, in the present embodiment, for debts such as product purchases and various charges that are expected to be paid in a batch to one payee, electronic approval is made by inputting a payment request (debt consolidation processing) after recording the debts. May be drafted. Here, in the purchase of goods, electronic approval may be made after the debt consolidation process. Further, in the present embodiment, the expense obligation, which is expected to be requested for payment each time the obligation is generated, may be treated as a payment request together with the recording of the obligation, and electronic approval may be issued. Further, in the present embodiment, approval may be performed by the accounting department after passing through an arbitrary approval route. As a result, in the present embodiment, it is possible to make it paperless, save labor in management / confirmation at the time of payment in the accounting department, and manage the serial number of payment application / settlement.

[2. Constitution]
An example of the configuration of the payment request electronic approval device according to the present embodiment will be described with reference to FIG. FIG. 1 is a block diagram showing an example of the configuration of the payment request electronic approval device.

The payment request electronic approval device 100 is a commercially available desktop personal computer. The payment request electronic approval device 100 is not limited to a stationary information processing device such as a desktop personal computer, but may be a commercially available notebook personal computer, PDA (Personal Digital Assistants), smartphone, tablet personal computer, or the like. It may be a portable information processing device.

The payment request electronic approval device 100 includes a control unit 102, a communication interface unit 104, a storage unit 106, and an input / output interface unit 108. Each part of the payment request electronic approval device 100 is communicably connected via an arbitrary communication path.

The communication interface unit 104 connects the payment request electronic approval device 100 to the network 300 so as to be communicable 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 another device via a communication line. Here, the network 300 has a function of connecting the payment request electronic approval device 100 and the server 200 so as to be able to communicate with each other, and is, for example, the Internet or a LAN (Local Area Network).

Various databases, tables, files, and the like are stored in the storage unit 106. In the storage unit 106, a computer program for giving a command to a CPU (Central Processing Unit) in cooperation with an OS (Operating System) to perform various processes is recorded. 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, an optical disk, or the like can be used. The storage unit 106 includes a pattern table 106a, a debt data file 106b, and a payment request file 106c.

The pattern table 106a sets whether or not electronic approval of debt payment schedule input in the sales department is required, whether or not electronic approval of payment request input from the sales department to the accounting department is required, and debt payment schedule input. Stores multiple approval patterns, including setting whether or not to consider electronic approval of payment request input as electronic approval.

The debt data file 106b stores the debt data of the debt. Here, the debt may be a debt in the sales department. In addition, the debt data may include a debt payment schedule. In addition, the debt may be expenses, goods costs, and / or expenses.

The payment request file 106c stores the payment request table data of the payment request table. Here, the payment request table data may be electronically approved. Further, the payment request table may be a payment request table to the accounting department (from the sales department or the like in the company).

An input device 112 and an output device 114 are connected to the input / output interface unit 108. As the output device 114, a speaker or a printer can be used in addition to a monitor (including a home television). As the input device 112, 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. In the following, the output device 114 may be referred to as a monitor 114, and the input device 112 may be referred to as a keyboard 112 or a mouse 112.

The control unit 102 is a CPU or the like that collectively controls the payment request electronic approval device 100. The control unit 102 has an internal memory for storing a control program such as an OS, a program that defines various processing procedures, required data, and the like, and performs various information processing based on these stored programs. Execute. The control unit 102 is functionally conceptually provided with a setting unit 102a, a debt payment schedule input determination unit 102b, a payment request input determination unit 102c, a drafting unit 102d, and a payment processing execution unit 102e.

The setting unit 102a sets the approval pattern applied to the debt in the sales department as the setting approval pattern. Here, the setting unit 102a may set the approval pattern to be applied to the debt in the sales department as the setting approval pattern by using the approval pattern stored in the pattern table 106a.

When the debt payment schedule input determination unit 102b in the sales department receives the debt payment schedule input in the sales department, the debt payment schedule input determination unit 102b confirms whether or not the debt payment schedule input of the debt is electronically approved based on the setting approval pattern, and the debt payment schedule Determine whether to accept input. Here, the debt payment schedule input determination unit 102b may store (register) the debt data of the debt in the sales department in the debt data file 106b. Further, the debt payment schedule input may be a debt prepayment request.

When the payment request input determination unit 102c is determined by the debt payment schedule input determination unit 102b to accept the debt payment schedule input, and when the debt sales department inputs the payment request to the accounting department, the setting approval pattern Based on, it is confirmed whether or not the payment request input is electronically approved, and whether or not the payment request input is accepted is determined.

When the payment request input determination unit 102c determines that the payment request input is accepted, the billing unit 102d drafts the payment request data of the payment request slip to the accounting department. Here, the drafting unit 102d may store (register) the payment request data in the payment request file 106c.

The payment processing execution unit 102e executes payment processing of payment request data. Here, the payment processing execution unit 102e may extract a plurality of the payment request data for each predetermined summary unit and execute the payment process collectively. Here, the predetermined summary unit may be a business establishment, a withdrawal payment destination, a payment method, a scheduled payment date, a payment request number, a payment department, a currency, a department, and / or an accounting slip number. Further, the payment processing execution unit 102e may execute payment processing for each payment request data when the debt is an expense debt.

[3. Concrete example]
Specific examples of this embodiment will be described with reference to FIGS. 2 to 12.

[Payment request electronic approval processing]
Here, an example of the payment request electronic approval process in the present embodiment will be described with reference to FIG. FIG. 2 is a flowchart showing an example of processing of the payment request electronic approval device 100 in the present embodiment.

As shown in FIG. 2, the setting unit 102a sets the approval pattern to be applied to the debt in the sales department of the company as the setting approval pattern by using the approval pattern stored in the pattern table 106a (step SA-1). ).

Then, when the user receives a debt payment schedule input in the sales department via the input device 112, the debt payment schedule input determination unit 102b electronically approves the debt payment schedule input of the debt based on the setting approval pattern. It is determined whether or not the debt payment schedule input is accepted (step SA-2).

Then, when the debt payment schedule input determination unit 102b determines that the debt payment schedule input is not accepted (step SA-2: No), the process ends.

On the other hand, when the debt payment schedule input determination unit 102b determines that the debt payment schedule input is accepted (step SA-2: Yes), the debt data of the debt in the sales department is registered in the debt data file 106b, and the process is performed in step SA. Move to -3.

Then, when the payment request input determination unit 102c receives a payment request input from the sales department of the debt to the accounting department via the input device 112 by the user, the payment request input determination unit 102c electronically approves the payment request input based on the setting approval pattern. The presence or absence is confirmed, and it is determined whether or not to accept the payment request input (step SA-3).

Then, when the payment request input determination unit 102c determines that the payment request input is not accepted (step SA-3: No), the process ends.

On the other hand, when the payment request input determination unit 102c determines that the payment request input is accepted (step SA-3: Yes), the process shifts to step SA-4.

Then, the drafting unit 102d drafts the payment request data of the payment request slip from the sales department to the accounting department, and registers the payment request data in the payment request file 106c (step SA-4). Here, the payment request data finally approved with the electronic approval of the payment request input may be prohibited from being deleted from the payment request file 106c.

Then, the payment processing execution unit 102e determines whether or not the debt of the payment request slip issued by the drafting unit 102d is an expense debt (step SA-5).

Then, when the payment processing execution unit 102e determines that the debt of the payment request slip is not an expense debt (step SA-5: No), the payment processing execution unit 102e shifts the processing to step SA-6.

Then, the payment processing execution unit 102e extracts a plurality of the payment request data stored in the payment request file 106c for each predetermined summary unit, collectively executes the payment process (step SA-6), and performs the process. finish.

On the other hand, when the payment processing execution unit 102e determines that the debt of the payment request slip is an expense debt (step SA-5: Yes), the payment processing execution unit 102e shifts the processing to step SA-7.

Then, the payment processing execution unit 102e executes the payment processing for each payment request data stored in the payment request file 106c (step SA-7), and ends the processing.

Here, the processing contents of the payment request electronic approval device 100 according to the present embodiment will be described with reference to FIG. FIG. 3 is a diagram showing an example of the overall configuration of the system including the payment request electronic approval device 100.

In this embodiment, as shown in FIG. 3, the scope of responsibility of the sales department includes purchase import processing, purchase input, purchase charge input, export charge input, and expense payment schedule input at the left end of the figure. When debts are incurred from various debt-generating items such as expense payment schedule acquisition processing, travel expenses expenses, and contractor payment applications, payment requests may be made for these.

Here, in the flow of payment request, this time, a summary process of paying only this amount is performed, and the summary process is a payment request slip, which is circulated as a circulation document. If you circulate the payment request slip on paper, the accounting department shown in Fig. 3 has a large number of employees, and if you issue many payment request slips a day, you will need a large amount of paper, and you will need to stamp and stock it. Considering the space, it was very inefficient.

Therefore, in the present embodiment, as shown in FIG. 3, an electronic approval function may be provided for paper approval, which is a standard function of the payment request slip. Further, in the present embodiment, as shown in FIG. 3, a payment method confirmation processing function may be added. That is, in the present embodiment, the unit is summarized in the business process on the accounting department side at the time of settlement, such as whether the final settlement is performed at the end of the month or whether each control number that has been electronically approved later is extracted and used for payment. Therefore, it may be possible to switch between "current status" and "additional" for determining the payment method by this summary unit.

Here, the electronic approval function itself confirms whether or not the slip contents for each recording of general debts are correct (the superior confirms whether the slip contents can be recorded in the accounting books) and electronically. There is already something to approve (for example, approval of expense payment / vendor payment itself in the sales department in Fig. 3 and approval of payment request). However, the electronic approval function in the present embodiment is different from this, and is an electronic approval function for inputting a payment request, which is an unprecedented function. That is, in the present embodiment, it is possible to support individual settlement processing by combining electronic approval with the place where the debt is recorded for settlement.

In addition, electronic approval of this payment request means that the payment request itself has various recording data of debts. For example, for "purchase" or "various charges", if they occur daily, they are first recorded and then the day after that. In many cases, a two-step process of making a payment request again is performed, but "expenses" etc. are recorded on the same day and sent to electronic approval without looking back, etc., and steps are performed according to the type of recorded data (business). There is a peculiarity that it is necessary to switch between. For example, in the case of checking ON for creating payment request data for "expense", when the approval of the payment request is completed, the approval of the payment request is also completed, so that it is treated as a one-step process.

Here, an example of the pattern table 106a in the present embodiment will be described with reference to FIG. FIG. 4 is a diagram showing an example of the pattern table 106a in the present embodiment.

As shown in FIG. 4, the pattern table 106a in the present embodiment may store an approval pattern in which one-step processing or two-step processing is divided into patterns according to the setting of check ON and check OFF. In the present embodiment, when the expense is recorded in the expense payment schedule input and the expense is requested, the pattern in FIG. 4 may be used for processing. Further, in the pattern table 106a of FIG. 4, the operation is divided into eight patterns according to the combination of three conditions (check ON / OFF, expense payment schedule input approval setting, and payment request input approval setting), and the operation meets the conditions. Is set to be done.

Returning to FIG. 3, in the present embodiment, in the payment notification / payment schedule by denomination after the payment method confirmation process, for example, in the case of actual business, not only “expense” or “simple debt” but also “Advance payment” may also be subject to electronic approval of payment requests. For this reason, in the present embodiment, the management number is attached after the approval for how much prepayment is requested is given, and then the prepayment is settled, and then the money is transferred to the bank, instead of the actual price. Or the settlement (exchange) rate may be finalized. As a result, in the present embodiment, it corresponds to the case where the prepaid item is paid with the request number after this, but it is called later and the price of the item is applied (that is, the prepaid item). It is possible. As described above, in the present embodiment, the management by the management number is the same as the management by the payment request number in the summary unit. That is, in the present embodiment, it may be said that what has been paid in advance has been approved at this timing.

Further, an example of payment request input in the present embodiment will be described with reference to FIGS. 5 to 9. FIG. 5 is a diagram showing an example of a payment request input screen. FIG. 6 is a diagram showing an example of a payment request detail input screen. FIG. 7 is a diagram showing an example of the transfer information screen. FIG. 8 is a diagram showing an example of a slip breakdown screen. FIG. 9 is a diagram showing an example of a payment request input transfer table.

As shown in FIG. 5, on the payment request input screen in the present embodiment, payment request data to be paid is created for the approved purchase data of the payee each time, and the payment request number is assigned. can do. Further, on the payment request input screen in the present embodiment, payment requests can be combined for a plurality of purchase slips. Further, on the payment request input screen in the present embodiment, it is possible to calculate the scheduled payment date with the set value of the closing payment while using the payment request by setting the payee master (scheduled payment date calculation category). .. Further, on the payment request input screen in the present embodiment, the planned payment amount by denomination may be calculated for each payment request. Further, on the payment request input screen in the present embodiment, the withholding tax deposit may be recalculated in units of payment requests. Further, in the payment request input screen of the present embodiment, if there is a "total amount input category", the amount stated in the invoice from the payee may be input and automatically allocated. Further, in the payment request input screen of the present embodiment, if there is no "total amount input category", the payment schedule of the company may be arbitrarily specified and the payment request amount may be determined by accumulating.

Further, as shown in FIG. 6, in the payment request detail input screen in the present embodiment, the detail items include data classification, code, name, slip number, supplier, slip date, scheduled payment date, and delivery note number. The slip amount, the paid amount, the planned payment amount, the requested amount this time, and the like may be included. Further, as shown in FIG. 7, on the transfer information screen in the present embodiment, in the case of a normal payee, only the display may be executed, and in the case of a Morokuchi payee, the user may be able to input via the input device 112. Further, as shown in FIG. 8, on the slip breakdown screen in the present embodiment, the total amount requested for each item is displayed in the "current payment request amount" instead of the total amount displayed in the item information. You may. As a result, on the slip breakdown screen in the present embodiment, the total amount of the details does not match when a part of the details is requested, but it always matches when the details are requested.

Further, as shown in the payment request input transfer table of FIG. 9, the screen transition may be controlled. Here, in the present embodiment, in the case of a slip unit, only the detail selection display screen may be displayed. Further, on the payment request screen of the present embodiment, when each payment request detail is double-clicked and the details are input, the payment request details input screen may be displayed. Further, in the payment request screen of the present embodiment, when the detail button is selected, the detail selection display screen may be displayed. Further, in the present embodiment, the amount of money input on the payment request screen (details) may be automatically set on the detail selection display screen. Further, in the present embodiment, in the case of prepaid payment, only the details associated with the details selection display screen may be displayed.

In addition, an example of the payment method determination process in the present embodiment will be described with reference to FIGS. 10 to 12. FIG. 10 is a diagram showing an example of processing details of the payment method confirmation processing screen. 11 and 12 are diagrams showing an example of summary unit switching of payment method determination processing and debt balance management by business establishment department.

As shown in FIG. 10, on the payment method confirmation processing screen (condition specification screen) in the present embodiment, the payment schedule data can be aggregated by the payment schedule date or the withdrawal payment destination to create a payment notification file. Further, on the payment method confirmation processing screen in the present embodiment, the target payment schedule can be reaggregated to create a denomination payment schedule. Further, on the payment method confirmation processing screen in the present embodiment, it is possible to calculate the consumption tax difference by tax rate for the consumption tax calculation category = the payee at the time of closing. Further, the payment method determination process in the present embodiment may be canceled and / or re-executed until the payment schedule by denomination is paid.

Further, FIG. 11 shows a payment method determination process in which the scheduled payment date set in the payee master is used as a summary unit, and a debt balance management process for each business establishment department. On the other hand, FIG. 12 shows a payment method determination process in which the payment request number set in the payee master is a collective unit, and a debt balance management process for each business establishment department. Then, in the present embodiment, the payment notification and the payment unit of the payee and the payment category can be changed by switching the unit of the payment method determination process.

In this embodiment, when the payment summary unit is switched between "withdrawal payment destination unit" and "payment request number unit", F payment when the payment category of M payment destination is 1 (payment each time). The unit for creating notifications and D payments changes. Further, in the present embodiment, when the payment method change input is input, the F payment notification may be recreated. Further, in the present embodiment, the payment request number may not be held in the F payment notification, the F denomination payment schedule, the D payment header, the D payment details, and the D payment application header. Further, in the present embodiment, the payment request number and the payment notification number may be held in the D payment schedule. D The payment request number may be held in the payment application statement. Further, in the present embodiment, the payment request number held in the F payment notification may be acquired, or the payment request number may be acquired via the D payment schedule if necessary.

In this way, in the present embodiment, by making it possible to control the electronic approval of payment requests from the sales department to the accounting department, the payment request form becomes paperless and the accounting department saves labor in management and confirmation at the time of payment. It is possible to manage payment applications and payment serial numbers.

In general, in trade transactions, the payee is often billed for both goods and / or charges by individual invoice, and in the case of foreign currency settlement, the settlement rate differs for each invoice. In particular, in the case of prepayment, since it is necessary to manage payment data in units of billing by the other party (= payment request unit), it is difficult for the accounting department to collectively confirm the contents of a large number of slips, and individual confirmation is performed by electronic approval. There is a need. In general, in import transactions, when import usance (Japanese loan) occurs, a bill of exchange is inserted into the domestic bank and payment is deferred, and the accounts payable to the import destination is the unpaid debt to the bank. Transferred to.

Therefore, in the present embodiment, it is possible to electronically approve the payment request. That is, in the present embodiment, the case Guid and the approval status classification are provided in the payment request file, the Fx standard can be electronically approved by the new application type, and the approval voucher is a payment request slip, which is used at the time of closing payment. Payment requests registered by the payment closing date update process are not subject to electronic approval. Further, in the present embodiment, when the expense is recorded in the expense payment schedule input and the expense is requested, the payment request may be processed based on the preset approval pattern.

[4. Other embodiments]
In addition to the above-described embodiments, the present invention may be implemented in various different embodiments within the scope of the technical ideas described in the claims.

For example, of each of the processes described in the embodiments, all or part of the processes described as being automatically performed may be performed manually, or all of the processes described as being performed manually. Alternatively, a part thereof can be automatically performed by a known method.

In addition, the processing procedure, control procedure, specific name, information including parameters such as registration data and search conditions of each processing, screen examples, and database configuration shown in this specification and drawings are not specified unless otherwise specified. Can be changed arbitrarily.

Further, with respect to the payment request electronic approval 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.

For example, with respect to the processing functions included in the payment request electronic approval device 100, particularly each processing function performed by the control unit 102, all or any part thereof is realized by the CPU and a program interpreted and executed by the CPU. It may be realized as hardware by wired logic. The program is recorded on a non-temporary computer-readable recording medium including a programmed instruction for causing the information processing apparatus to execute the process described in the present embodiment, and the payment request electronic is required. It is read mechanically by the approval device 100. That is, in a storage unit such as a ROM or an HDD (Hard Disk Drive), a computer program for giving instructions to the CPU in cooperation with the OS and performing various processes is recorded. This computer program is executed by being loaded into RAM, and constitutes a control unit in cooperation with a CPU.

Further, this computer program may be stored in an application program server connected to the payment request electronic approval device 100 via an arbitrary network, and all or a part thereof may be downloaded as needed. It is possible.

Further, the program for executing the process described in the present embodiment may be stored in a non-temporary computer-readable recording medium, or may be configured as a program product. Here, the "recording medium" includes 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), and an EPROM (registered). Trademarks) (Electrically Erasable and Programmable Read Only Memory), CD-ROM (Compact Disk Read Only Memory), MO (Magnet-Optical Disk), MO (Magnet-Optical Disk), Digital Disk, DVD (Digital), DVD (Digital) It shall include any "portable physical medium".

Further, the "program" is a data processing method described in an arbitrary language or description method, regardless of the format such as source code or binary code. The "program" is not necessarily limited to a single program, but is distributed as a plurality of modules or libraries, or cooperates with a separate program represented by the OS to achieve its function. Including things. A well-known configuration and procedure can be used for a specific configuration and reading procedure for reading the recording medium in each device shown in the embodiment, an installation procedure after reading, and the like.

Various databases and the like stored in the storage unit are memory devices such as RAM and ROM, fixed disk devices such as hard disks, flexible disks, and storage means such as optical disks, and are used for various processes and website provision. Stores programs, tables, databases, files for web pages, etc.

Further, the payment request electronic approval 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 payment request electronic approval device 100 may be realized by mounting software (including a program or data) that realizes the processing described in the present embodiment on the device.

Further, the specific form of the distribution / integration of the device is not limited to the one shown in the drawing, and all or a part thereof may be functionally or physically in an arbitrary unit according to various additions or functional loads. It can be distributed and integrated. That is, the above-described embodiments may be arbitrarily combined and implemented, or the embodiments may be selectively implemented.

The present invention is particularly useful in a company having a large proportion of import business from overseas.

100 Payment request electronic approval device 102 Control unit 102a Setting unit 102b Debt payment schedule input determination unit 102c Payment request input determination unit 102d Drafting unit 102e Payment processing execution unit 104 Communication interface unit 106 Storage unit 106a Pattern table 106b Debt data file 106c Payment Request file 108 Input / output interface unit 112 Input device 114 Output device 200 Server 300 Network

Claims (7)

A payment request electronic approval device equipped with a storage unit and a control unit.
The storage unit
Setting whether or not electronic approval of debt payment schedule input in the sales department is required, setting whether or not electronic approval of payment request input from the sales department to the accounting department is required, and electronic approval of the debt payment schedule input A pattern storage means for storing a plurality of approval patterns including a setting of whether or not to consider the payment request input as electronic approval.
With
The control unit
A setting means for setting the approval pattern applied to the debt in the sales department as a setting approval pattern, and
When there is a debt payment schedule input for the debt in the sales department, it is confirmed whether or not the debt payment schedule input for the debt is electronically approved based on the setting approval pattern, and whether or not the debt payment schedule input is accepted. Debt payment schedule input judgment means to judge
When it is determined by the debt payment schedule input determination means that the debt payment schedule input is accepted, and when the payment request input from the sales department to the accounting department of the debt is made, based on the setting approval pattern. , A payment request input determination means that confirms the presence or absence of electronic approval of the payment request input and determines whether or not to accept the payment request input.
When it is determined by the payment request input determination means that the payment request input is accepted, the drafting means for drafting the payment request data of the payment request slip to the accounting department and the drafting means.
A payment request electronic approval device characterized by being equipped with. The control unit
A payment processing execution means that extracts a plurality of the payment request data for each predetermined summary unit and executes the payment process collectively.
The payment request electronic approval device according to claim 1, further comprising. The predetermined summary unit is
The payment request electronic approval according to claim 2, characterized in that it is a place of business, a withdrawal payment destination, a payment method, an estimated payment date, a payment request number, a payment department, a currency, a department, and / or an accounting slip number. apparatus. The control unit
When the debt is an expense debt, a payment processing execution means that executes payment processing for each payment request data,
The payment request electronic approval device according to claim 1, further comprising. The debt payment schedule input is
The payment request electronic approval device according to any one of claims 1 to 4, wherein the payment request is a prepaid request for the debt. It is a payment request electronic approval method for executing a payment request electronic approval device having a storage unit and a control unit.
The storage unit
Setting whether or not electronic approval of debt payment schedule input in the sales department is required, setting whether or not electronic approval of payment request input from the sales department to the accounting department is required, and electronic approval of the debt payment schedule input A pattern storage means for storing a plurality of approval patterns including a setting of whether or not to consider the payment request input as electronic approval.
With
It is executed by the control unit.
A setting step for setting the approval pattern applied to the debt in the sales department as a setting approval pattern, and
When there is a debt payment schedule input for the debt in the sales department, it is confirmed whether or not the debt payment schedule input for the debt is electronically approved based on the setting approval pattern, and whether or not the debt payment schedule input is accepted. Debt payment schedule input judgment step to determine
When it is determined in the debt payment schedule input determination step that the debt payment schedule input is accepted, and when the payment request input from the sales department to the accounting department of the debt is made, based on the setting approval pattern. Then, the payment request input determination step of confirming whether or not the payment request input is electronically approved and determining whether or not to accept the payment request input, and
When it is determined in the payment request input determination step that the payment request input is accepted, the drafting step of drafting the payment request data of the payment request slip to the accounting department and the drafting step.
A payment request electronic approval method characterized by including. It is a payment request electronic approval program for executing a payment request electronic approval device having a storage unit and a control unit.
The storage unit
Setting whether or not electronic approval of debt payment schedule input in the sales department is required, setting whether or not electronic approval of payment request input from the sales department to the accounting department is required, and electronic approval of the debt payment schedule input A pattern storage means for storing a plurality of approval patterns including a setting of whether or not to consider the payment request input as electronic approval.
With
In the control unit
A setting step for setting the approval pattern applied to the debt in the sales department as a setting approval pattern, and
When there is a debt payment schedule input for the debt in the sales department, it is confirmed whether or not the debt payment schedule input for the debt is electronically approved based on the setting approval pattern, and whether or not the debt payment schedule input is accepted. Debt payment schedule input judgment step to determine
When it is determined in the debt payment schedule input determination step that the debt payment schedule input is accepted, and when the payment request input from the sales department to the accounting department of the debt is made, based on the setting approval pattern. Then, the payment request input determination step of confirming whether or not the payment request input is electronically approved and determining whether or not to accept the payment request input, and
When it is determined in the payment request input determination step that the payment request input is accepted, the drafting step of drafting the payment request data of the payment request slip to the accounting department and the drafting step.
Payment request electronic approval program to execute.