Work support device, work support method and work support program

Abstract

To support making work of a transfer request slip.SOLUTION: A payment schedule data generation unit generates payment schedule data which is the payment schedule data to a prescribed payment destination, and includes a payment schedule date which is a date at which the payment to the payment destination is hoped, and a payment amount. A determination unit refers to a storage unit in which information indicating business days or holidays of a bank for each date is stored, and performs determination processing of whether or not the date obtained by adding the number of payable days which is the number of the business days of the bank, required for demanded payment processing, to the date on which payment request to the payment destination has been performed, is the date after the payment schedule date of the payment schedule data. A payment data generation unit, when a determination result that the date obtained by adding the number of the business days of the bank is the date after the payment schedule date of the payment schedule data is obtained, generates payment data on a format capable of being handled in the bank, on the basis of the payment schedule data. A storage control unit stores the generated payment data in a storage unit.SELECTED DRAWING: Figure 1

Description

Technical Field

[0001] The present invention relates to a business support device, a business support method, and a business support program.

Background Art

[0002] These days, when making a transfer such as payment for goods to a business partner, the person in charge of the transfer operation creates a transfer request slip for the business partner and transmits it to the terminal device of the bank. Thereby, at the terminal device of the bank, a transfer process for the business partner is performed based on the transfer request slip.

[0003] Patent Document 1 (Japanese Patent Application Laid-Open No. 2021-196699) discloses a transportation expense payment system that can efficiently support the transportation expense payment operation for an unspecified number of payees.

[0004] This transportation expense payment system includes a user computer, a company in-charge computer of a company that encourages the use of a public transportation network where the destination is specified for the user, a payment in-charge computer of a person in charge of paying transportation expenses to the user-specified account in the company, a processing unit, and a transportation expense payment device including a storage unit.

[0005] The transportation expense payment device is a device that supports the transfer operation of transportation expenses to the user-specified account at a financial institution, and stores the financial institution name, account number, and account name entered by the user in the storage unit. Further, the transportation expense payment device accepts an application for payment of the specified transportation expenses based on the departure place and the arrival place entered by the user, and when receiving an input indicating that there is an error in the application as a result of checking the application from the payment in-charge computer, it transmits an e-mail prompting the user to reapply.

Prior Art Documents

Patent Documents

[0006]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0007] Here, the operation of creating a transfer request slip for making a transfer request to a business partner involves many troublesome operations, which poses a problem of burden on the operator.

[0008] The present invention has been made in view of the above problems, and an object thereof is to provide a business support device, a business support method, and a business support program that enable support for the operation of creating a transfer request slip.

Means for Solving the Problems

[0009] In order to solve the above problems and achieve the object, a business support device according to the present invention includes: a payment schedule data generation unit that generates payment schedule data which is payment schedule data for a predetermined payee and includes a payment schedule date which is a date on which payment to the payee is desired and a payment amount; a determination unit that refers to a storage unit in which information indicating business days or holidays of a bank is stored for each date, and performs a determination process as to whether a date obtained by adding the number of business days of the bank, which is the number of business days required for the applied payment process, to the date on which a payment request to the payee is made is a date after the payment schedule date of the payment schedule data; a transfer request data generation unit that generates transfer request data in a format that can be handled by a bank based on the payment schedule data when a determination result that the date obtained by adding the number of business days of the bank is a date after the payment schedule date of the payment schedule data is obtained; and a storage control unit that stores the generated transfer request data in the storage unit.

[0010] In addition, in order to solve the above-described problems and achieve the object, a business support method according to the present invention includes a payment schedule data generation step in which a payment schedule data generation unit generates payment schedule data including a payment schedule date, which is a date on which payment to a predetermined payee is desired, and a payment amount, which is payment schedule data for a predetermined payee; a determination step in which a determination unit refers to a storage unit in which information indicating a business day or a holiday of a bank is stored for each date, and determines whether a date obtained by adding the number of business days of the bank, which is the number of business days required for the applied payment process, to the date on which a payment request to the payee is made is a date after the payment schedule date of the payment schedule data; a transfer request data generation step in which a transfer request data generation unit generates transfer request data in a format that can be handled by a bank based on the payment schedule data when a determination result that the date obtained by adding the number of business days of the bank is a date after the payment schedule date of the payment schedule data is obtained; and a storage control step in which a storage control unit stores the generated transfer request data in the storage unit.

[0011] In addition, in order to solve the above-described problems and achieve the object, a business support program according to the present invention causes a computer to function as a payment schedule data generation unit that generates payment schedule data including a payment schedule date, which is a date on which payment to a predetermined payee is desired, and a payment amount, which is payment schedule data for a predetermined payee; a determination unit that refers to a storage unit in which information indicating a business day or a holiday of a bank is stored for each date, and determines whether a date obtained by adding the number of business days of the bank, which is the number of business days required for the applied payment process, to the date on which a payment request to the payee is made is a date after the payment schedule date of the payment schedule data; a transfer request data generation unit that generates transfer request data in a format that can be handled by a bank based on the payment schedule data when a determination result that the date obtained by adding the number of business days of the bank is a date after the payment schedule date of the payment schedule data is obtained; and a storage control unit that stores the generated transfer request data in the storage unit.

Advantages of the Invention

[0012] The present invention can support the creation work of transfer request slips.

Brief Description of the Drawings

[0013]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Embodiments for Carrying Out the Invention

[0014] Hereinafter, a business support apparatus according to an embodiment to which the present invention is applied will be described in detail with reference to the drawings. Note that the present invention is not limited to the following embodiments.

[0015] (Hardware Configuration) As shown in FIG. 1, the business support device 1 of the embodiment includes a storage unit 2, a control unit 3, a communication interface unit 4, and an input / output interface unit 5. An input device 6 and an output device 7 are connected to the input / output interface unit 5. As the output device 7, a display unit such as a monitor device (including a home television), a printing device, or a speaker device corresponds. As the input device 6, in addition to a keyboard device, a mouse device, and a microphone device, a monitor device that realizes a pointing device function in cooperation with the mouse device can be used.

[0016] The communication interface unit 4 is an example of a communication unit and is connected to a network 50 such as a wide area network such as the Internet or a private network such as a LAN (Local Area Network). A terminal device of a person in charge (person-in-charge terminal device) 51 that approves payment schedule data and a bank terminal device 52 that transmits transfer request data (text data in FB format) to a business partner are connected to the network 50.

[0017] As the storage unit 2, for example, a storage device such as a ROM (Read Only Memory), a RAM (Random Access Memory), an HDD (Hard Disk Drive), or an SSD (Solid State Drive) can be used. A business support program that supports the creation work of transfer request slips is stored in the storage unit 2. In addition, in this storage unit 2, a calendar master 11, a message master 12, a slip type payable days master 13, a payment method control master 14, and a slip type approval route master 15, which are storage areas, are provided.

[0018] In addition, the storage unit 2 is provided with a payment data storage unit 17, a transfer request data storage unit 18, and an FB data storage unit 19, which are storage areas respectively. Note that FB (Firm Banking) data is data used when performing multiple transfers such as comprehensive transfers or salary transfers at one time, and is data of a text file created in the "National Bankers Association" format common to each bank.

[0019] As shown in FIG. 2, the calendar master 11 stores, for each date, a business classification indicating whether it is a business day of the bank or a holiday of the bank.

[0020] As shown in FIG. 3, the message master 12 stores messages output according to the determination result as to whether the payment scheduled date specified in the payment schedule data by the determination unit 23 is a date considering the number of payable days counted as business days of the bank. In this FIG. 3, when the determination result is "OK", a message "Application accepted" is output, and when the determination result is "Error", an example of a message "The number of days until the payment scheduled date is insufficient" is output.

[0021] As shown in FIG. 4, the voucher type payable days master 13 sets the number of payable days counted as business days of the bank for each payee and each voucher type. In the example of this FIG. 4, the number of payable days of "2 days" is set for the "regular voucher" of the payee "Company A", and the number of payable days of "1 day" is set for the "temporary voucher" of "Company A".

[0022] Similarly, in the example of FIG. 4, the number of payable days of "3 days" is set for the "regular voucher" of the payee "Company B", and the number of payable days of "2 days" is set for the "temporary voucher" of "Company B".

[0023] In the payment method control master 14, as shown in FIG. 5, the payment method specified in the payment schedule data and whether or not to automatically create vouchers for the payment method are associated and stored. In the example of FIG. 4, the payment methods for which voucher automatic creation is performed are "transfer" and "bill", and among these, only for "transfer", it is set to perform automatic voucher creation (1: control). Note that when the payment method is "bill", automatic voucher creation is not performed (0: no control).

[0024] In the voucher type approval route master 15, an approval route for payment schedule data corresponding to the voucher type is set. FIG. 6 shows an example where for "normal voucher", a "normal approval route" by the responsible person is set, and for "temporary voucher", a "temporary approval route" by the responsible person is set.

[0025] (Functional Configuration of Business Support Device) Next, the control unit 3 functions as a display control unit 21, a payment schedule data generation unit 22, a determination unit 23, a transfer request data generation unit 24, an FB data generation unit 25, a storage control unit 26, a communication control unit 27, and a payment data generation unit 28 as shown in FIG. 1 by executing the business support program stored in the storage unit 2.

[0026] The display control unit 21 displays a merchant payment application screen, a payment settlement input screen, etc. via the output device 7.

[0027] The payment schedule data generation unit 22 generates payment schedule data that is payment schedule data for a predetermined payee and includes a payment schedule date, which is the date on which payment to the payee is desired, and a payment amount (see FIGS. 9(a) and 9(b)).

[0028] The determination unit 23 refers to a storage unit (calendar master 11 in FIG. 2) in which information indicating a business day or a holiday of the bank is stored for each date, and determines whether or not the date obtained by adding the number of payable days, which is the number of business days of the bank required for the applied payment process, to the date (voucher issue date) on which a payment request to the payee was made is a date after the payment schedule date of the payment schedule data.

[0029] When the determination result is obtained that the date obtained by adding the number of business days of the bank is a date after the payment scheduled date of the payment schedule data, the transfer request data generation unit 24 (and the FB data generation unit 25) generates transfer request data in a format that can be handled by the bank based on the payment schedule data (see FIG. 10).

[0030] The storage control unit 26 causes the storage unit (FB data storage unit 19) to store the generated transfer request data in a format that can be handled by the bank.

[0031] The communication control unit 27 controls the communication unit (communication interface unit 4) to transmit the generated transfer request data in a format that can be handled by the bank to the bank terminal device 52 via the network 50.

[0032] In addition, in the storage unit (voucher type payment available days master 13 in FIG. 4), the number of business days of the bank required for the applied payment process is set for each payee. The determination unit 23 reads out the payment available days corresponding to the payee from the storage unit (voucher type payment available days master 13 in FIG. 4) based on the payee included in the payment schedule data and performs the above-described determination process.

[0033] In addition, as the payment available days stored in the storage unit (voucher type payment available days master 13 in FIG. 4), at least the payment available days in the case of a normal voucher in which the voucher type of the payment schedule data has the payment available days as normal days and the payment available days in the case of a temporary voucher in which the voucher type of the payment schedule data has the payment available days shorter than normal days are stored. Therefore, the determination unit 23 performs the above-described determination process using the payment available days corresponding to the voucher type of the payment schedule data.

[0034] In the voucher type approval route master 15 in FIG. 6, a normal approval route in which the responsible person approves the payment schedule data over a normal period of time and a temporary approval route in which the responsible person approves the payment schedule data in a shorter time than normal are set for each voucher type.

[0035] When the slip type is the slip type of the normal approval route, the communication control unit 27 transmits the payment schedule data to the terminal device (responsible person terminal device 51) of the person in charge of approving the payment schedule data via the network 50 and receives the approval result. Also, when the slip type is the slip type of the temporary approval route, the communication control unit 27 transmits the payment schedule data to the terminal device (responsible person terminal device 51) of the person in charge of approving the payment schedule data via the network 50 and receives the approval result.

[0036] Based on the approved payment schedule data, the transfer request data generation unit 24 generates transfer request data in a format that can be handled by the bank.

[0037] Also, the determination unit 23 performs the above-described determination process on the payment schedule data for which the payment method is set to "transfer". In other words, when the payment method of the payment schedule data is other than "transfer", the determination unit 23 does not perform the above-described determination process.

[0038] Based on the approved payment schedule data, the payment data generation unit 28 generates payment data and stores it in the payment data storage unit 17.

[0039] (Automatic generation operation of payment request slip) Next, the business support device 1 of the embodiment automatically generates a payment request slip in the flow shown in FIG. 7 by the control unit 3 functioning as the display control unit 21 to the communication control unit 27 based on the business support program.

[0040] In this example, the display control unit 21 to the communication control unit 27 will be described as being realized by software based on the business support program. However, all or part of the display control unit 21 to the communication control unit 27 may be realized by hardware. In any case, the same effects as those described later can be obtained.

[0041] That is, in step S1 of FIG. 7, the business support apparatus 1 according to the embodiment allows an operator to perform a merchant payment application input (input of payment schedule data) via a merchant payment application screen displayed via the output device 7 by the display control unit 21. With respect to this merchant payment application screen, the operator performs an input operation of the business partner, payment schedule date, document type, payment amount, etc., and operates a button with the character "application" written thereon.

[0042] When the button with the character "application" written thereon is operated, the payment schedule data generation unit 22 generates payment schedule data as shown in FIG. 8 based on the input content for the merchant payment application screen, and stores it in the payment schedule data storage unit 16.

[0043] FIG. 9(a) shows an example of the generated payment schedule data. As shown in this FIG. 9(a), the payment schedule data is composed of a document issue date, payment schedule date, document type, payee code, payee name, payment amount, payment method, and approval status. The document issue date is the date when the operator performed the above-described input operation on the merchant payment application screen. The payment schedule data generation unit 22 acquires date information (system date information) counted by a timer provided in the business support apparatus 1 and sets it as the document issue date. That is, the document issue date is the date when the operator created this payment request document.

[0044] The payment schedule date is the date on which payment is scheduled to be made to the business partner. This payment schedule date is input by the operator via the merchant payment application screen as described above.

[0045] The document type is a type of normal document or temporary document, and is input or selected by the operator via the merchant payment application screen.

[0046] The payee code is a code uniquely assigned to the payee to whom payment is to be made. In the example of FIG. 9(a), the payee code is "T0001" and the payee name is "XX Shoko".

[0047] The payment amount is the amount to be paid to the business partner. In the example of Fig. 9(a), the payment amount is "1,000,000 yen".

[0048] The payment method is a payment type of "transfer" or "bill", and is input or selected by the operator via the business partner payment application screen. The example of Fig. 9(a) is an example where the payment method of "transfer" is input or selected.

[0049] The approval status is information indicating whether or not approval has been given by the responsible person for this payment request slip, and there are status types of "unapproved" and "approved". In the example of Fig. 9(a), at the time of creation of this scheduled payment data, since the approval process by the responsible person has not been performed, the approval status is "unapproved".

[0050] When the scheduled payment data is generated in this way, the determination unit 23 determines whether or not the payment method of the generated scheduled payment data is "transfer". And when the determination unit 23 determines that the payment method is "transfer", as described below, it determines whether or not the scheduled payment date specified by the operator is a legitimate scheduled payment date. Note that when the determination unit 23 determines that the payment method is "bill", the determination of the scheduled payment date described below is not performed.

[0051] Specifically, the determination unit 23 refers to the voucher type payment available days master 13 based on the payee (business partner) and voucher type indicated in the scheduled payment data, and acquires the payment available days corresponding to the business partner and voucher type. Also, the determination unit 23 refers to the calendar master 11 shown in Fig. 2, and compares the "date obtained by adding the business days corresponding to the payment available days to the voucher issue date" with the "scheduled payment date". And when "(the date obtained by adding the business days corresponding to the payment available days to the voucher issue date) < (the scheduled payment date)", the determination unit 23 determines that a legitimate scheduled payment date has been specified (determination result = OK). On the other hand, when "(the date obtained by adding the business days corresponding to the payment available days to the voucher issue date) > (the scheduled payment date)", the determination unit 23 determines that an improper scheduled payment date has been specified (determination result = error).

[0052] For example, in the payment schedule data, when "Company A" is specified as the business partner (payee) and "normal type" is specified as the voucher type, the available payment days are "2 days (2 business days)" as shown in Figure 4. Also, in the payment schedule data, assume that "January 31, 2023 (Tuesday)" is specified as the payment due date and the voucher issue date is "January 26, 2023 (Thursday)". In this case, referring to the calendar master 11 in Figure 2, the date obtained by adding the "2 business days" of the available payment days to the voucher issue date of "January 26, 2023 (Thursday)" is "January 30, 2023 (Monday)" (calculating 2 business days from the day after the voucher issue date).

[0053] And the specified payment due date of "January 31, 2023 (Tuesday)" is a date after "January 30, 2023 (Monday)", which is the date obtained by adding the "2 business days" of the available payment days to the voucher issue date. In this case, the determination unit 23 determines that a valid payment due date has been specified (determination result = OK).

[0054] When the determination result is "OK", the display control unit 21 refers to the message master 12 shown in Figure 3 and obtains the message "Application accepted" corresponding to the "OK" determination result. Then, the display control unit 21 displays the obtained message "Application accepted" on the merchant payment application screen. Thereby, the operator can be made aware that the application for the payment request voucher has been officially accepted.

[0055] On the contrary, for example, in the payment schedule data, when "Company A" is specified as the business partner (payee) and "normal type" is specified as the voucher type, the available payment days are "2 days (2 business days)" as shown in Figure 4. Also, in the payment schedule data, assume that "January 30, 2023 (Monday)" is specified as the payment due date and the voucher issue date is "January 27, 2023 (Friday)". In this case, referring to the calendar master 11 in Figure 2, the date obtained by adding the "2 business days" of the available payment days to the voucher issue date of "January 27, 2023 (Friday)" is "January 31, 2023 (Tuesday)" (calculating 2 business days from the day after the voucher issue date).

[0056] And the specified payment scheduled date, "January 30, 2023 (Monday)", is a date before "January 31, 2023 (Tuesday)" which is obtained by adding the "2 business days" of available payment days to the voucher issue date. In this case, the determination unit 23 determines that no valid payment scheduled date has been specified (determination result = error).

[0057] When the determination result is "error", the display control unit 21 refers to the message master 12 shown in FIG. 3 and obtains a message "The number of days until the payment scheduled date is insufficient" corresponding to the "error" determination result. Then, the display control unit 21 displays the obtained message "The number of days until the payment scheduled date is insufficient" on the merchant payment application screen. Thereby, the operator can be made to recognize that there is a defect in the input of the payment scheduled date. The operator re-enters a new payment scheduled date on the merchant payment application screen to correct this defect.

[0058] Next, in step S2 of FIGS. 7 and 8, based on the voucher type of the payment scheduled data for which the determination result of "OK" has been obtained, the communication control unit 27 refers to the voucher type approval route master 15 shown in FIG. 6 and detects an approval route corresponding to the voucher type. For example, when the voucher type is "ordinary voucher", an "ordinary approval route" in which the approval process is performed by the responsible person over a normal period of time is detected. Also, when the voucher type is "ordinary voucher", a "temporary approval route" in which the approval process is performed in a shorter time than the normal time is detected.

[0059] The communication control unit 27 controls the communication interface unit 4 to add the approval route information indicating the detected approval route to the payment scheduled data for which the determination result of "OK" has been obtained and transmit it to the responsible person terminal device 51. The responsible person operating the responsible person terminal device 51 performs the approval process of the payment scheduled data over a time corresponding to the "ordinary approval route" or "temporary approval route" according to the approval route information added to the payment scheduled data. Then, the responsible person inputs the approval status of the payment scheduled data shown in FIG. 9(b) via the responsible person terminal device 51.

[0060] This approval status will be "Approved" if the payment schedule data is approved, and "Not Approved" if the payment schedule data is not approved. The person in charge transmits the payment schedule data (see Fig. 9(b)) with the approval status thus entered to the business support device 1 via the person-in-charge terminal device 51.

[0061] The storage control unit 26 of the business support device 1 stores the payment schedule data (Approved) with the approval status received from the person-in-charge terminal device 51 in the payment schedule data storage unit 16.

[0062] Next, when the payment schedule data is approved by the person in charge, the operator performs a payment settlement input operation on the payment settlement input screen displayed by the display control unit 21 based on the approved payment schedule data. The payment data generation unit 28 generates the payment data shown in Fig. 11(a) and the payment detail data shown in Fig. 11(b) from the input content entered on the payment settlement input screen based on the approved payment schedule data in steps S3 of Figs. 7 and 10, and stores this in the payment data storage unit 17.

[0063] As shown in Fig. 11(a), the payment data is composed of the payment date, transfer requester code, transfer requester name (in kana), receiving bank code, receiving bank name, receiving bank branch name, receiving deposit type, and receiving account number.

[0064] Also, as shown in Fig. 11(b), the payment detail data is composed of the payee code, payee name, receiving bank number, receiving bank name, receiving bank branch number, receiving bank branch name, transfer amount, and payment method. Among these, the "payment method" is the payment type of "transfer" or "bill" described above.

[0065] Next, in step S4 of FIGS. 7 and 10, the transfer request data generation unit 24 generates transfer request data based on the payment data and the payment detail data, and stores this in the transfer request data storage unit 18. Also, in step S4, the FB data generation unit 25 converts the transfer request data stored in the transfer request data storage unit 18 into FB (Firm Banking) data, which is data used when performing a plurality of transfers, such as a comprehensive transfer or a salary transfer, at once, and is data of a text file created in the "National Bankers Association" format common to each bank. Then, the FB data generation unit 25 stores the FB data generated by performing such format conversion processing in the FB data storage unit 19.

[0066] Next, in step S5 of FIGS. 7 and 10, the communication control unit 27 reads out the FB data stored in the FB data storage unit 19 at a timing designated by, for example, an operator, and transmits it to the bank terminal device 52 via the communication interface unit 4. As a result, in the bank terminal device 52, transfer processing for a predetermined amount to the payee is performed based on the FB data.

[0067] (Effects of the Embodiment) Uploading a file of FB (Firm Banking) data to the bank's software via human hands is often prohibited as a control requirement. In the business support device 1 of the embodiment, after the payment request slip (merchant payment application) is approved by the responsible person, the file is automatically transmitted to the bank. As a result, a payment request slip that meets the control requirements can be uploaded to the bank's software.

[0068] Also, the business support device 1 of the embodiment can determine whether a proper payment scheduled date is specified for each type of slip, such as two days later for a regular slip and one day later for a temporary slip, by selecting the slip type of a regular slip or a temporary slip when issuing a payment request slip for a merchant payment application. As a result, a proper payment request slip can be created, the work of creating the payment request slip can be significantly reduced, and the work of the operator in creating the payment request slip can be supported.

[0069] In addition, since it can also handle provisional vouchers, it can also handle urgent payments such as payments to insurance companies.

[0070] In addition, when issuing a payment request voucher for a vendor payment application, by selecting the voucher type of a normal voucher or a provisional voucher, an approval route corresponding to the voucher type can be set. For this reason, when issuing a provisional voucher, the approval process by the responsible person can be performed using a dedicated approval route for special approval.

[0071] [Contribution to the Sustainable Development Goals (SDGs) Led by the United Nations] According to the present invention, since it can contribute to improving business efficiency and making appropriate business judgments of enterprises, it can contribute to the goals of "8" and "9" of the SDGs.

[0072] In addition, according to the present invention, since it can contribute to reducing waste loss and promoting paperless and digitization, it can contribute to the goals of "12", "13" and "15" of the SDGs.

[0073] In addition, according to the present invention, since it can contribute to strengthening control and governance, it can contribute to the goal of "16" of the SDGs.

[0074] [Other Embodiments] The present invention can be implemented in various different forms within the scope of the technical idea described in the claims even in forms other than the above-described embodiments.

[0075] For example, among the respective processes described in the embodiments, all or part of the processes described as being automatically performed may be manually performed. Or, all or part of the processes described as being manually performed may be automatically performed by a known method or the like.

[0076] In addition, regarding the processing procedures, control procedures, specific names, registration data of each process, information including parameters such as search conditions, screen examples, and database configurations shown in the specification or drawings, they can be arbitrarily changed unless otherwise specified.

[0077] Also, regarding the business support device 1, each of the illustrated components is a functional concept and does not necessarily have the physical configuration shown in the figure. For example, regarding the processing functions provided by the business support device 1, especially each processing function performed by the control unit 3, all or any part of them may be realized by a program interpreted and executed by the control unit 3 (CPU: Central Processing Unit), or may be realized by hardware using wired logic.

[0078] 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 embodiment, and is mechanically read by the business support device 1 as necessary. That is, in the storage unit 2 such as a ROM or HDD, a computer program for giving instructions to the control unit 3 (CPU) in cooperation with the OS (Operating System) to perform various processes is recorded. This computer program is loaded into the RAM and expanded, and is appropriately executed by the control unit 3.

[0079] Also, the business support program of this business support device 1 may be stored in another server device connected to the business support device 1 via an arbitrary network, and all or part of it may be downloaded and executed as necessary.

[0080] Also, the business support program for executing the processing described in the embodiment may be stored in a non-transitory computer-readable recording medium, or may be configured as a program product.

[0081] Here, as the "recording medium", 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 can be used.

[0082] Also, the "program" is a data processing method described in any language or description method, and is not limited to forms such as source code or binary code.

[0083] Note that the "program" is not necessarily limited to being configured singularly, and includes those that are distributed as a plurality of modules or libraries and those that achieve their functions in cooperation with separate programs typified by an OS.

[0084] Also, for the specific configuration, reading procedure, and installation procedure after reading for the recording medium reading in the business support apparatus 1 of the embodiment, well-known configurations or procedures can be used.

[0085] The storage unit 2 is a storage means such as a memory device such as a RAM and a ROM, a fixed disk device such as a hard disk, a flexible disk, and an optical disk, and stores various programs, tables, databases, and web page files used for various processes or website provision.

[0086] Further, the business support device 1 may be configured by an information processing device such as a known personal computer device or a workstation, or may be configured by an information processing device to which an arbitrary peripheral device is connected. Further, the information processing device may be realized by implementing software (including programs or data, etc.) that realizes the processing described in the embodiment.

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

Industrial Applicability

[0088] The present invention is suitably applicable, as an example, to the operation of creating transfer request slips for companies such as chemical, trading, food, and steel companies that have internal control requirements.

Explanation of Signs

[0089] 1 Business support device 2 Storage unit 3 Control unit 4 Communication interface unit 5 Input / output interface unit 6 Input device 7 Output device 11 Calendar master 12 Message master 13 Slip type payable days master 14 Payment method control master 15 Slip type approval route master 16 Payment schedule data storage unit 17 Payment data storage unit 18 Transfer request data storage unit 19 FB data storage unit 21 Display control unit 22 Payment schedule data generation unit 23 Judgment unit 24 Transfer request data generation unit 25 FB data generation unit 26 Memory control unit 27 Communication control unit 28 Payment data generation unit

Claims

1. A payment schedule data generation unit that generates payment schedule data for a predetermined payee, including a payment schedule date, which is the date on which payment to the payee is desired, and a payment amount; A determination unit that refers to a storage unit in which information indicating business days or holidays of a bank is stored for each date, and determines whether a date obtained by adding the number of business days of the bank, which is the number of business days required for the applied payment process, to the date on which the payment request to the payee was made is a date after the payment schedule date in the payment schedule data; A transfer request data generation unit that generates transfer request data in a format that can be handled by the bank based on the payment schedule data when a determination result is obtained that the date obtained by adding the number of business days of the bank is a date after the payment schedule date in the payment schedule data; A storage control unit that stores the generated transfer request data in the storage unit; A business support device having the above.

2. Further comprising a communication control unit that controls a communication unit to transmit the generated transfer request data to a terminal device of the bank via a predetermined network. The business support device according to claim 1, characterized in that.

3. In the storage unit, the number of business days of the bank required for the applied payment process is set for each payee. The determination unit reads out the number of payable days corresponding to the payee from the storage unit based on the payee included in the payment schedule data and performs the determination process. The business support device according to claim 2, characterized in that.

4. The number of payable days includes at least When the document type of the payment schedule data is a normal document for which the number of payable days is the normal number of days, the number of payable days; The payable date of the payment schedule data is set to the payable date in the case of a provisional slip that makes the number of payable days shorter than the normal number of days, The determination unit performs the determination process using the payable date corresponding to the slip type of the payment schedule data, The business support device according to claim 3, characterized in that.

5. A normal approval route in which the responsible person approves the payment schedule data over a normal period of time, and a provisional approval route in which the responsible person approves the payment schedule data in a shorter time than the normal time are set for each slip type, When the slip type is the slip type of the normal approval route, the communication control unit transmits the payment schedule data to the terminal device of the person in charge of approving the payment schedule data via the network and receives the approval result. When the slip type is the slip type of the provisional approval route, the communication control unit transmits the payment schedule data to the terminal device of the person in charge of approving the payment schedule data via the network and receives the approval result, The transfer request data generation unit generates the transfer request data based on the approved payment schedule data, The business support device according to claim 4, characterized in that.

6. The determination unit performs the determination process on the payment schedule data in which the payment method is set to "transfer", The business support device according to any one of claims 1 to 5, characterized in that.

7. A payment schedule data generation step in which a payment schedule data generation unit generates payment schedule data that is payment schedule data for a predetermined payee and includes a payment schedule date and an amount to be paid, which is the date on which payment to the payee is desired, The determination unit refers to a storage unit in which information indicating business days or holidays of the bank is stored for each date, and determines whether the date obtained by adding the number of business days of the bank, which is the number of business days required for the applied payment process, to the date on which the payment request to the payee was made is a date after the payment scheduled date in the payment schedule data. When the determination result that the date obtained by adding the number of business days of the bank is a date after the payment scheduled date in the payment schedule data is obtained, the transfer request data generation unit generates transfer request data in a format that can be handled by the bank based on the payment schedule data. The storage control unit stores the generated transfer request data in the storage unit. A business support method having the above.

8. A computer, A payment schedule data generation unit that generates payment schedule data for a predetermined payee, including a payment scheduled date, which is the date on which payment to the payee is desired, and a payment amount. A determination unit that refers to a storage unit in which information indicating business days or holidays of the bank is stored for each date, and determines whether the date obtained by adding the number of business days of the bank, which is the number of business days required for the applied payment process, to the date on which the payment request to the payee was made is a date after the payment scheduled date in the payment schedule data. A transfer request data generation unit that generates transfer request data in a format that can be handled by the bank based on the payment schedule data when the determination result that the date obtained by adding the number of business days of the bank is a date after the payment scheduled date in the payment schedule data is obtained. Functioning as a storage control unit that stores the generated transfer request data in the storage unit. A business support program characterized by the above.

Images