Liability management system, liability management method, and liability management program

Abstract

To provide a debt management system, a debt management method and a debt management program, allowing easy payment by a different payment method when payment cannot be made by firm banking due to a system failure of a bank.SOLUTION: A debt management system according to the present embodiment includes payment data creation means for creating payment detail data including a payee, a payment date, a payment method, a transaction amount, and a transfer fee, transfer data creation means for creating transfer data including a transfer destination, a transfer date, a transfer amount, and a payment method of FB based on the payment detail data and transmitting the transfer data to the FB, creation cancellation means for deleting the transfer data when transmission of the transfer data fails and creating transfer data deletion data as a history of the deleted transfer data, and withdrawal processing means for creating transfer data in which the payment method is changed to another payment method for the transfer data deletion data and performing a withdrawal procedure.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present invention relates to a debt management system, a debt management method, and a debt management program. [Background technology]

[0002] For example, a bank system provides a firm banking service. Patent Document 1, for example, discloses a system that provides a firm banking service. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Laid-Open No. 2013-65062 Summary of the Invention [Problem to be solved by the invention]

[0004] However, when making a payment (transfer) using firm banking, if the payment cannot be made through firm banking due to a system failure at the bank or the like, the credit of the transfer recipient will be reduced.

[0005] The present invention has been made in consideration of the above, and aims to provide a debt management system, debt management method, and debt management program that enable payments to be made easily using a different payment method when payments cannot be made via firm banking due to a bank system failure or the like. [Means for solving the problem]

[0006] In order to solve the above-mentioned problems and achieve the object, the present invention is a debt management system that has a control unit and makes transfers using FB (firm banking), wherein the control unit is characterized by having: a payment data creation means that creates payment detail data including the payee, payment date, payment method, transaction amount, and transfer fee; a transfer data creation means that creates transfer data including the payee, transfer date, transfer amount, and payment method set to FB based on the payment detail data and sends it to FB; a creation cancellation means that deletes the transfer data if transmission of the transfer data fails, and creates transfer data deletion data as a history of the deleted transfer data; and a withdrawal processing means that creates transfer data for the transfer data deletion data in which the payment method is changed to another payment method and performs withdrawal procedures.

[0007] According to another aspect of the present invention, the other payment method may be a slip or internet banking.

[0008] In addition, according to one aspect of the present invention, if the transfer data creation means is successful in transmitting the transfer data, it may output a transfer procedure list with FB payment, and the withdrawal processing means may output a transfer procedure list with FB payment.

[0009] In addition, in order to solve the above-mentioned problems and achieve the object, the present invention is a debt management method for making transfers using FB (firm banking), executed by an information processing device equipped with a control unit, and is characterized by including: a payment data creation process executed by the control unit for creating payment detail data including a payee, payment date, payment method, transaction amount, and transfer fee; a transfer data creation process for creating transfer data including a payee, payment date, transfer amount, and payment method set to FB based on the payment detail data, and sending the transfer data to FB; a creation cancellation process for deleting the transfer data if transmission of the transfer data fails, and creating transfer data deletion data as a history of the deleted transfer data; and a withdrawal processing process for creating transfer data for the transfer data deletion data in which the payment method is changed to another payment method, and performing withdrawal procedures.

[0010] In addition, in order to solve the above-mentioned problems and achieve the object, the present invention is a debt management program for making transfers using FB (firm banking) to be executed by an information processing device equipped with a control unit, and is characterized in that the control unit executes the following steps: a payment data creation process for creating payment detail data including a payee, payment date, payment method, transaction amount, and transfer fee; a transfer data creation process for creating transfer data including a payee, transfer date, transfer amount, and payment method set to FB based on the payment detail data, and sending the data to FB; a creation cancellation process for deleting the transfer data if transmission of the transfer data fails, and creating transfer data deletion data as a history of the deleted transfer data; and a withdrawal processing process for creating transfer data for the transfer data deletion data in which the payment method is changed to another payment method, and performing withdrawal procedures. [Effects of the Invention]

[0011] According to the present invention, when payment cannot be made through firm banking due to a system failure at a bank or the like, it is possible to easily make a payment using a different payment method. [Brief explanation of the drawings]

[0012] [Figure 1] FIG. 1 is a block diagram showing an example of the configuration of a debt management system according to this embodiment. [Figure 2] FIG. 2 is a flowchart for explaining an outline of the overall processing of the control unit of the debt management system in this embodiment. [Figure 3] FIG. 3 is a diagram for explaining a specific example of the processing of the control unit of the debt management system according to this embodiment. [Figure 4] FIG. 4 is a diagram for explaining a specific example of the processing of the control unit of the debt management system according to this embodiment. [Figure 5] FIG. 5 is a diagram for explaining a specific example of the processing of the control unit of the debt management system according to this embodiment. [Figure 6]FIG. 6 is a diagram for explaining a specific example of the processing of the control unit of the debt management system according to this embodiment. [Figure 7] FIG. 7 is a diagram for explaining a specific example of the processing of the control unit of the debt management system according to this embodiment. [Figure 8] FIG. 8 is a diagram for explaining a specific example of the processing of the control unit of the debt management system according to this embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0013] DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS An embodiment of the present invention will be described in detail with reference to the accompanying drawings. However, the present invention is not limited to the embodiment.

[0014] [1. Overview] For example, a bank's system provides firm banking (FB) services and internet banking services. When transferring funds to a bank using firm banking, an FB file is created in the debt management system and then uploaded to firm banking. Specifically, the transfer is carried out using the following steps:

[0015] (1) Create an FB file in the debt management system. The debt management system will treat the payment as completed. (2) The person in charge uploads the data outside the debt management system. (3) The firm banking side will carry out the withdrawal procedure and withdraw the funds from the actual account (the funds will be considered withdrawn in actual business).

[0016] Since (1) and (3) are not data-linked, the timing of withdrawals on the debt management system differs from the timing of withdrawals in business operations. During this time lag, due to system failures on the firm banking side, (1) the FB file may have been created, but (3) the firm banking side may not be able to complete the withdrawal procedure.

[0017] Previously, invoices for which withdrawal procedures had been completed were not allowed to be modified in order to ensure consistency between the payables management system and operations. This meant that it was necessary to enter red invoices and black invoices using a different withdrawal method to cancel payables data for which withdrawal procedures had been completed (see Figure 4). This requires new input from the system operator, which increases the risk of operational errors, and if an error occurs in the payment process, it could lead to a decline in corporate value.

[0018] Therefore, in the debt management system of the present invention, after creating an FB file (withdrawal procedure on the system), if the actual withdrawal from firm banking is not completed due to a failure in the bank system, etc., the withdrawal procedure is canceled, and a mechanism has been created that allows the withdrawal procedure to be carried out using a different payment method (for example, bringing in a slip, paying via Internet banking) without changing the payment data (debt data).

[0019] This allows for easy payment by a different payment method when payment cannot be made through firm banking due to a system failure at the bank, etc. Specifically, the following effects are achieved.

[0020] -Since there is no need to change payment data (debt data), the following effects are expected. (1) Reduction of administrative burden (2) Redundancy slips are no longer necessary, reducing journal entries and unnecessary redundancy slips.

[0021] The following effects are expected from the withdrawal process: (1) Reducing the risk of duplicate withdrawals (2) Reducing the risk of double counting

[0022] By streamlining and simplifying the process of changing withdrawal actions, it is possible to prevent payments from becoming impossible and prevent a decline in corporate value.

[0023] The functional outline of the present invention is as follows. (1) A function to cancel the creation of an FB file has been implemented for payment data for which an FB file has already been created. (2) For payment data for which FB file creation has been canceled, it is now possible to carry out withdrawal procedures using a different payment method without changing the payment data. (3) Since payment data is not changed and red and black vouchers are not entered, unnecessary journal entries are not generated, preventing the ledger from becoming dirty. (4) Since the payment method in the transfer procedure list is not changed, the number of payments that are actually made via FB payment can be correctly identified, making it possible to carry out data analysis.

[0024] The debt management system of the present invention is widely applicable to industries such as the real estate and financial industries that manage a large number of accounts and accounts of other parties.

[0025] [2. Configuration] Fig. 1 is a block diagram showing an example of the configuration of a debt management system 100 according to this embodiment. In Fig. 1, the debt management system 100 comprises a control unit 102, a communication interface unit 104, a storage unit 106, and an input / output interface unit 108. The units comprised in the debt management system 100 are connected to each other so as to be able to communicate with each other via any communication path.

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

[0027] The bank system 400 (also called the "comprehensive transfer system") provides firm banking (FB) services and internet banking services. The debt management system 100 is configured to be able to use these firm banking services and internet banking services, and allows deposits and transfers (withdrawals) via firm banking and internet banking.

[0028] The storage unit 106 stores various databases, tables, files, etc. The storage unit 106 stores computer programs that work in conjunction with the OS (Operating System) to issue commands to the CPU (Central Processing Unit) to perform various processes. The storage unit 106 can be, for example, a memory device such as RAM (Random Access Memory) or ROM (Read Only Memory), a fixed disk device such as a hard disk, a flexible disk, or an optical disk. The storage unit 106 stores payment statement data, transfer data (FB data), transfer data deletion data, etc.

[0029] The payment details data may include the payee, payment date (transfer date), payment method, transaction amount, transfer fee, transfer sequence, etc.

[0030] The transfer data may include the transfer sequence, transfer destination, transfer date, transfer amount, payment method, file name, output date and time, etc.

[0031] The transfer data deletion data may include the transfer sequence, transfer destination, transfer date, transfer amount, payment method, file name, output date and time, etc.

[0032] An input device 112 and an output device 114 are connected to the input / output interface unit 108. The output device 114 may be a monitor (including a home television), a speaker, or a printer. The input device 112 may be a keyboard, a mouse, a microphone, or a monitor that functions as a pointing device in cooperation with a mouse. Note that hereinafter, the output device 114 may be referred to as the monitor 114.

[0033] The control unit 102 is a CPU or the like that controls the debt management system 100. The control unit 102 has an internal memory for storing control programs such as an OS, programs that define various processing procedures, and required data, and executes various information processing operations based on these stored programs. The control unit 102 is configured to be able to access payment statement data, transfer data (FB data), transfer data deletion data, and the like stored in the memory unit 106. Note that the payment statement data, transfer data (FB data), transfer data deletion data, and the like may be stored in other locations (e.g., the server 200) as long as they are accessible by the control unit 102. Functionally, the control unit 102 includes a payment data creation unit 102a, a transfer data creation unit 102b, a creation cancellation unit 102c, a withdrawal processing unit 102d, and a screen display control unit 102e.

[0034] The payment data creation unit 102a creates payment details data including the payee, payment date, payment method, transaction amount, and transfer fee, and stores the data in the storage unit 106.

[0035] The transfer data creation unit 102b creates transfer data (also called "FB data" or "FB file") including the transfer destination, transfer date, transfer amount, and payment method designated as FB based on the payment details data stored in the memory unit 106, for example, based on the operations of the person in charge on the FB data output screen (see Figure 6) displayed on the monitor, and sends the data to the FB and stores it in the memory unit 106.

[0036] When the transmission of transfer data fails due to an FB failure or the like, the creation cancellation unit 102c deletes the transfer data stored in the memory unit 106, for example, based on the operation of the person in charge on the FB data output screen (see Figure 6) displayed on the monitor, and creates transfer data deletion data as a history of the deleted transfer data, and stores it in the memory unit 106.

[0037] For example, based on the operation of the person in charge on the other payment data output screen (see FIG. 7) displayed on the monitor, the withdrawal processing unit 102d creates transfer data in which the payment method is changed to another payment method for the transfer data deletion data stored in the memory unit 106, and performs the withdrawal procedure. The other payment method may be a slip or internet banking.

[0038] The screen display control unit 102e controls the display of various screens (for example, FB data output screen, other payment data output screen, etc.) displayed on the monitor 114 and the inputs thereto.

[0039] [3. Specific Examples] A specific example of the processing by the control unit 102 of the debt management system 100 according to this embodiment will be described with reference to Figures 1 to 8. Figures 2 to 8 are diagrams for explaining a specific example of the processing by the control unit 102 of the debt management system 100 according to this embodiment.

[0040] [3-1. Overall processing] The overall processing flow of the control unit 102 of the debt management system 100 according to this embodiment will be described with reference to Figure 2. Figure 2 is a diagram showing a flow for explaining the overall processing flow of the control unit 102 of the debt management system 100 according to this embodiment.

[0041] 2, when the payment data creation unit 102a receives a payment instruction, it creates (application and approval) payment details data (step S1). Here, the case where the payment method (FB) is selected will be described.

[0042] The transfer data creation unit 102b, for example, confirms the payment details (payment schedule schedule) (step S2) and confirms the payment registration (check ON) based on the operations of the person in charge on the FB data output screen (see Figure 6) displayed on the monitor, and creates transfer data (FB file) including the transfer destination, transfer date, transfer amount, and payment method set as FB based on the payment detail data stored in the memory unit 106, sends it to FB (step S4), and outputs the FB data list (step S10).

[0043] If the transfer data creation unit 102b has successfully transmitted the FB file ("Yes" in step S5), it outputs a list of transfer procedures for which payment has been made as FB (step S11). On the other hand, if transmission of the FB file has failed due to a system failure in the firm banking system or the like ("No" in step S5), the creation cancellation unit 102c deletes the FB data output (step S6), for example, based on the operation of the person in charge on the FB data output screen (see FIG. 6) displayed on the monitor, deletes the transfer data, and creates transfer data deletion data as a history of the deleted transfer data.

[0044] The withdrawal processing unit 102d, for example, outputs other payment data (for comprehensive transfers) based on the operator's operation on the other payment data output screen (see FIG. 7) displayed on the monitor, and creates (outputs) transfer data for the deleted transfer data in which the payment method has been changed to another payment method (for example, bringing in a slip) (step S7). The withdrawal processing unit 102d then performs a withdrawal procedure for the transfer data in which the payment method has been changed (step S8). The withdrawal processing unit 102d outputs a transfer procedure list with FB payment as the payment method (step S9). The other payment method may also be internet banking.

[0045] After creating an FB file for payment procedures on the FB data output screen (see Figure 6), if the withdrawal process cannot be carried out normally due to a defect on the comprehensive transfer system (bank system 400) side, the debt management system 100 will show a status where a withdrawal record has been created (step S10 above), and the data will not be eligible for internet banking or voucher payment. For this reason, the FB data output screen is equipped with a function to delete withdrawal records for each FB file created, and the screen will be configured so that new payment procedures can be carried out from "Internet recipient master output (comprehensive transfer compatible): internet banking transfer" or "voucher etc. payment data output (comprehensive transfer compatible): bring in voucher" on the separately constructed other payment method data output screen (see Figure 7).

[0046] [3-2. Sample Data] 3 to 8 are diagrams showing sample data for explaining a specific example of the processing by the control unit 102 of the debt management system 100 in this embodiment. A specific example of the processing by the control unit 102 of the debt management system 100 in this embodiment will be explained with reference to FIGS. 3 to 8.

[0047] (Processing for creating payment details data and transfer data) The payment data creation unit 102a creates payment details data including the payee, payment date, payment method, transaction amount, and transfer fee, and stores the data in the storage unit 106.

[0048] Figure 3(A) shows an example of payment details data. The payment details data includes fields such as payee, payment date, payment method, transaction amount, transfer fee, and transfer sequence. Major payees include, for example, property management companies, construction and cleaning companies, and taxpayers. In the example shown in the figure, the first line lists the payee "Construction Company A," payment date "6 / 4 / 2024," payment method "FB," transaction amount "1,000,000 yen," and transfer fee "550 yen."

[0049] The transfer data creation unit 102b creates transfer data (FB file) including the transfer destination, transfer date, and transfer amount based on the payment details data, for example, based on the person in charge's operations on the FB data output screen (see Figure 6) displayed on the monitor, and sends it to the FB.

[0050] Figure 3(B) shows an example (part) of transfer data. The transfer data may include the transfer sequence number, transfer destination, transfer date, transfer amount, payment method, file name, output date and time, etc. In the example shown in the figure, the first line contains the transfer destination "Construction Contractor A," the transfer date "June 4, 2024," the transfer amount "3,001,100 yen," the payment method "FB," and the file name "File (1)."

[0051] (What to do if you cannot send the FB file to firm banking) Regarding the process when the FB file cannot be sent to the firm banking due to a malfunction of the firm banking, "conventional process" and "process according to the present invention" will be explained.

[0052] "Traditional Processing" The conventional process will be explained with reference to Figure 4. Conventionally, as shown in Figure 4(A), for the payment detail data, it is necessary to cancel the details on lines 1 to 3 by entering the details of the red slip on lines 4 to 6, and then enter the details of a different payment method (in this example, "bring the slip in") on lines 7 to 9. As for the transfer data, as shown in Figure 4(B), it is necessary to leave it as it is and perform the cancellation process outside the debt management system.

[0053] The transfer data and the new payment method transfer data must be entered twice into the payables management system. Withdrawal processing also involves output FB files and invoices, so even if the payables management system cancels the process, it cannot control the process outside the system.

[0054] "Process of the present invention" The processing of the present invention will be described with reference to Figure 5. Figure 5(A) is a diagram showing an example of payment details data, and Figure 5(B) is a diagram showing an example of transfer data. Figure 5(C) is a diagram showing an example of transfer data deletion data. Figure 5(D) is a diagram showing an example of transfer data with a changed payment method.

[0055] (1) The creation cancellation unit 102c deletes the already output transfer data (FB file) in response to the operation of the person in charge, using the output deletion function (new) on the FB data output screen (see FIG. 6). In this example, the transfer data shown in FIG. 5(B) is deleted.

[0056] (2) The creation cancellation unit 102c creates transfer data deletion data as a history of the deleted transfer data and stores it in the storage unit 106 (saving it as a history of deleted transfer data). In this example, the transfer data deletion data shown in Figure 5(C) is created. The content of the data is the same as the deleted transfer data.

[0057] (3) The withdrawal processing unit 102d outputs transfer data in which the payment method of the transfer data deletion data has been changed from "FB" to "deliver slip" based on the operation of the person in charge on the other payment data output screen (see Figure 7). In this example, the transfer data shown in Figure 5(D) is output. For the transfer data in Figure 5(B), the payment method has been changed to "deliver slip" and the file name to "File (2)". Then, the withdrawal procedure is carried out for the transfer data in which the payment method has been changed to "deliver slip".

[0058] (Images of the FB data output screen, other payment method data output screen, and transfer procedure list) Figures 6(A) and (B) show examples of the FB data output screen. The FB data output screen allows you to create and delete FB data. On the FB data output screen 500 shown in Figure 6(A), when you specify the transfer date, transfer format, and processing category and press the execute button (not shown on the screen), an FB file is created for the payment statement data for the same transfer date stored in the memory unit 106 and sent to the FB.

[0059] In addition, the FB data output screen 500 shown in Figure 6(A) is provided with an output deletion button (FB file creation cancellation function), and when the output deletion button is pressed, a screen 600 showing a list of transfer data is displayed as shown in Figure 6(B), and when the execute button is pressed for the transfer data selected by the person in charge in the list, the transfer data is deleted and transfer data deletion data is created as a history of the deleted transfer data.

[0060] Figure 7 shows an example of the display of the other payment method data output screen 700. On the other payment method data output screen 700 shown in Figure 7, if you specify the transfer date, etc., check the checkbox for "Output total transfer data (used when total transfer data (FB file) cannot be sent)," and press the execute button, transfer data will be created (output) in which the payment method "FB" in the transfer data deletion data has been changed to "delivery of slip." Note that while the other payment method is "delivery of slip" here, it may also be "Internet banking." Figure 8 shows an example of the output of the transfer procedure list.

[0061] As described above, according to this embodiment, the system is equipped with a payment data creation unit 102a that creates payment details data including the payee, payment date, payment method, transaction amount, and transfer fee; a transfer data creation unit 102b that creates transfer data including the payee, payment date, transfer amount, and payment method set to FB based on the payment details data, and sends the data to FB; a creation cancellation unit 102c that deletes the transfer data if transmission of the transfer data fails, and creates transfer data deletion data as a history of the deleted transfer data; and a withdrawal processing unit 102d that creates transfer data for the transfer data deletion data in which the payment method is changed to another payment method and performs withdrawal procedures, so that when payment cannot be made via firm banking due to a bank system failure or the like, it becomes possible to easily make a payment using a different payment method.

[0062] [4. Contribution to the United Nations-led Sustainable Development Goals (SDGs)] This embodiment can contribute to improving business efficiency and promoting appropriate management decisions by companies, thereby contributing to the achievement of SDGs Goals 8 and 9.

[0063] Furthermore, this embodiment can contribute to reducing waste and promoting paperless and electronic systems, thereby contributing to the achievement of SDGs Goals 12, 13, and 15.

[0064] Furthermore, this embodiment can contribute to strengthening control and governance, which can contribute to the achievement of Goal 16 of the SDGs.

[0065] 5. Other Embodiments The present invention may be implemented in various different embodiments other than those described above within the scope of the technical concept set forth in the claims.

[0066] For example, among the processes described in the embodiments, all or part of the processes described as being performed automatically can be performed manually, or all or part of the processes described as being performed manually can be performed automatically using known methods.

[0067] Furthermore, the processing procedures, control procedures, specific names, information including parameters such as registered data and search conditions for each process, screen examples, and database configurations shown in this specification and drawings can be changed as desired unless otherwise specified.

[0068] Furthermore, with regard to the debt management system 100, the components shown in the figures are functional concepts, and do not necessarily have to be physically configured as shown in the figures.

[0069] For example, all or any part of the processing functions of the debt management system 100, particularly the processing functions performed by the control unit, may be implemented by a CPU and a program interpreted and executed by the CPU, or may be implemented as hardware using wired logic. The program is recorded on a non-transitory, computer-readable recording medium containing programmed instructions for causing an information processing device to execute the processes described in this embodiment, and is mechanically read by the debt management system 100 as needed. That is, a computer program is recorded in a storage unit such as a ROM or HDD (Hard Disk Drive) for working with the OS to issue instructions to the CPU and perform various processes. This computer program is executed by being loaded into RAM, and works in cooperation with the CPU to form the control unit.

[0070] This computer program may also be stored in an application program server connected to the debt management system 100 via any network, and all or part of it may be downloaded as needed.

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

[0072] Furthermore, a "program" is a data processing method written in any language or description method, regardless of the format, such as source code or binary code. Note that a "program" is not necessarily limited to a single structure, but also includes a structure that is distributed as multiple modules or libraries, or a structure that achieves its function by cooperating with a separate program, such as an OS. Note that the specific configuration and reading procedure for reading a recording medium in each device shown in the embodiments, as well as the installation procedure after reading, can use well-known configurations and procedures.

[0073] The various databases stored in the memory unit are storage means such as memory devices such as RAM and ROM, fixed disk devices such as hard disks, flexible disks, and optical disks, and store various programs, tables, databases, and web page files used for various processes and providing websites.

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

[0075] Furthermore, the specific form of distribution and integration of the devices is not limited to that shown in the drawings, and all or part of them can be configured by functionally or physically distributing and integrating them in any unit depending on various additions or functional loads. In other words, the above-described embodiments can be implemented in any combination, or embodiments can be implemented selectively. [Explanation of symbols]

[0076] 100 Debt Management System 102 Control section 102a Payment Data Creation Department 102b Transfer Data Creation Department 102c Creation Cancellation Section 102d Withdrawal processing section 102e Screen display control unit 104 Communication interface unit 106 Storage section 108 Input / Output Interface Section 112 Input Device 114 Output Device 200 servers 300 Network 400 Banking System

Claims

1. A debt management system that includes a control unit and transfers funds using FB (firm banking), The control unit a payment data creation means for creating payment details data including a payee, a payment date, a payment method, a transaction amount, and a transfer fee; A transfer data creation means for creating transfer data including a transfer destination, a transfer date, a transfer amount, and a payment method designated as FB based on the payment details data, and transmitting the data to FB; a creation cancellation means for deleting the transfer data when the transfer data transmission has failed and creating transfer data deletion data as a history of the deleted transfer data; a withdrawal processing means for creating transfer data in which the payment method is changed to another payment method for the transfer data deletion data and carrying out a withdrawal procedure; A debt management system comprising:

2. 2. The debt management system according to claim 1, wherein the other payment method is a slip or internet banking.

3. If the transfer data is successfully transmitted, the transfer data creation means outputs a transfer procedure list with Facebook payment, 3. The debt management system according to claim 1, wherein the withdrawal processing means outputs a list of transfer procedures for Facebook payments.

4. A debt management method for transferring funds using firm banking (FB), executed by an information processing device having a control unit, Executed in the control unit: a payment data creation step of creating payment details data including a payee, a payment date, a payment method, a transaction amount, and a transfer fee; A transfer data creation process for creating transfer data including a transfer destination, a transfer date, a transfer amount, and a payment method designated as FB based on the payment statement data, and transmitting the data to FB; a creation cancellation step of deleting the transfer data when the transmission of the transfer data fails and creating transfer data deletion data as a history of the deleted transfer data; a withdrawal processing step of creating transfer data in which the payment method is changed to another payment method for the transfer data deletion data and carrying out a withdrawal procedure; A debt management method comprising:

5. A debt management program for making a transfer using FB (firm banking) to be executed by an information processing device having a control unit, The control unit a payment data creation step of creating payment details data including a payee, a payment date, a payment method, a transaction amount, and a transfer fee; A transfer data creation process for creating transfer data including a transfer destination, a transfer date, a transfer amount, and a payment method designated as FB based on the payment statement data, and transmitting the data to FB; a creation cancellation step of deleting the transfer data when the transmission of the transfer data fails and creating transfer data deletion data as a history of the deleted transfer data; a withdrawal processing step of creating transfer data in which the payment method is changed to another payment method for the transfer data deletion data and carrying out a withdrawal procedure; Debt management program to implement.

Images