Bills receivable management device, bills receivable management method, and bills receivable management program

Abstract

To provide a bills receivable management device, a bills receivable management method and a bills receivable management program, which enable management by switching from data of an original bill to data of a new bill when performing a bill jump.SOLUTION: When a request for a bill jump for a target bill is approved, a bills receivable management device registers, based on bill receivable data, new bill receivable data in bill receivable history with the outcome of the target bill set as "bill jump" and a status set as "unwinding" in conjunction with each other; and registers new bill receivable data in the bill receivable history with the outcome of the jumped bill set as "bill jump," the status set as "request for collection", and the target bill set as a jump source of the jumped bill in conjunction with each other.SELECTED DRAWING: Figure 3

Description

[Technical Field]

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

[0002] Patent document 1 discloses a configuration for centralized system management of bill detail data by creating detail data for bills entrusted by a trustor, and setting a return flag on the detail data if the bill is returned. [Prior art documents] [Patent documents]

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

[0004] However, the invention described in Patent Document 1 above only allows management of the due date and details of a single bill, and has the problem of not being able to accurately manage the connection of bills when transferring them to another bill.

[0005] The present invention has been made in consideration of the above-mentioned problems, and aims to provide a bill receivable management device, a bill receivable management method, and a bill receivable management program that enable management by switching from the data of the original bill to the data of the new bill when performing a bill jump. [Means for solving the problem]

[0006] In order to solve the above-mentioned problems and achieve the objective, the bill receivable management device of the present invention is a bill receivable management device equipped with a memory unit and a control unit, wherein the memory unit is equipped with a bill receivable memory means for storing a bill receivable history consisting of bill receivable data set by linking the outcome of the target bill and the status, and the control unit is characterized in that when a request for a bill jump for the target bill is approved, the control unit is equipped with a bill receivable registration means for registering in the bill receivable history, based on the bill receivable data, new bill receivable data set by linking the bill jump as the outcome of the target bill and return as the status, and registering in the bill receivable history new bill receivable data set by linking the bill jump as the outcome of the jumped bill, collection request as the status, and the target bill as the jump source of the jumped bill.

[0007] In addition, in the bills receivable management device of the present invention, the control unit is characterized by further comprising a bills receivable inquiry means that displays the bills receivable history when a reference instruction for the bills receivable history is set.

[0008] In addition, in the bills receivable management device of the present invention, the control unit is characterized by further comprising a journal entry creation means for creating bills receivable journal entry data corresponding to each bills receivable data based on the bills receivable history.

[0009] In addition, in the bill receivable management device of the present invention, the bill receivable registration means is further characterized in that when a collection execution instruction is set for the jumped bill, it registers new bill receivable data in the bill receivable history, with collection as the outcome of the jumped bill, collection date, collection execution as the status, and the target bill as the jump source of the jumped bill.

[0010] In addition, in the bill receivable management device of the present invention, the bill receivable registration means is characterized in that when the target bill to be jumped is specified on the reassembly input screen and the request for the bill jump for the target bill is approved, it registers new bill receivable data in the bill receivable history based on the bill receivable data, with the bill jump set as the outcome of the target bill and the reassembly set as the status, and when the target bill to be jumped from is specified on the bill receivable input screen, it registers new bill receivable data in the bill receivable history, with the bill jump set as the outcome of the jumped bill, the collection request set as the status, and the target bill set as the jump source of the jumped bill.

[0011] In addition, in the bill receivable management device of the present invention, the control unit is characterized by further comprising a bill receivable inquiry means that displays the bill receivable data when a remaining debt inquiry instruction is set.

[0012] In addition, the bills receivable management method of the present invention is a bills receivable management method to be executed by a bills receivable management device equipped with a memory unit and a control unit, wherein the memory unit is equipped with a bills receivable memory means for storing a bills receivable history consisting of bills receivable data set by linking the outcome of the target bill and the status, and is characterized in that when a request for a bill jump for the target bill, executed by the control unit, is approved, the bills receivable registration step is performed to register new bills receivable data in the bills receivable history based on the bills receivable data, with the bill jump set as the outcome of the target bill and the return set as the status, and to register new bills receivable data in the bills receivable history, with the bill jump set as the outcome of the jumped bill, collection request set as the status, and the target bill set as the jump source of the jumped bill.

[0013] In addition, the bills receivable management program of the present invention is a bills receivable management program to be executed by a bills receivable management device having a memory unit and a control unit, wherein the memory unit has a bills receivable memory means for storing a bills receivable history consisting of bills receivable data set by linking the outcome of the target bill and the status, and wherein the control unit, when a request for a bill jump for the target bill is approved, executes a bills receivable registration step in which, based on the bills receivable data, new bills receivable data set by linking the bill jump as the outcome of the target bill and return as the status is registered in the bills receivable history, and new bills receivable data set by linking the bill jump as the outcome of the jumped bill, collection request as the status, and the target bill as the jump source of the jumped bill is registered in the bills receivable history. [Effects of the Invention]

[0014] The present invention provides the advantage that a series of registered details of bill jumps (return input and bill receivable input) can be referenced using the "bill receivable history inquiry." Furthermore, the present invention provides the advantage that accounting journal entries can be registered from a series of input details, including return input details, thereby ensuring consistency in accounting management. Furthermore, the present invention provides the advantage that management accuracy can be improved by managing the continuity of multiple bills in conjunction with bill jumps. Furthermore, the present invention provides the advantage that strict management of outstanding receivables can be achieved. Furthermore, the present invention provides the advantage that accuracy can be improved in managing outstanding receivables, including due date extensions, in bill receivable due date management and progress management. Furthermore, the present invention provides the advantage that processing based on bill receivable return input and bill receivable input, as well as related processing such as history inquiries, can be performed. [Brief explanation of the drawings]

[0015] [Figure 1] FIG. 1 is a diagram showing an example of a bills receivable management process in this embodiment. [Figure 2]FIG. 2 is a diagram showing an example of a bills receivable management process in this embodiment. [Figure 3] FIG. 3 is a block diagram showing an example of the configuration of the bills receivable management device in this embodiment. [Figure 4] FIG. 4 is a flowchart showing an example of the processing of the bills receivable management device in this embodiment. [Figure 5] FIG. 5 is a diagram showing an example of the bills receivable management process in this embodiment. [Figure 6] FIG. 6 is a diagram showing an example of a display screen in this embodiment. [Figure 7] FIG. 7 is a diagram showing an example of a display screen in this embodiment. [Figure 8] FIG. 8 is a diagram showing an example of a display screen in this embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0016] 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 this embodiment.

[0017] [1. Overview] First, an overview of the present invention will be described with reference to Figures 1 and 2. Figures 1 and 2 are diagrams showing an example of bills receivable management processing in this embodiment.

[0018] Traditionally, when a customer requests an extension of the due date of a bill, depending on their cash flow situation, the existing bill may be exchanged for a bill with a new due date; this type of operation is known as "bill jumping."

[0019] Here, in this embodiment, when a bill jump is performed, a system is provided that enables management by switching from the data of the original bill (bill number, payment date) to the data of the new bill. That is, in this embodiment, the original bill is returned by inputting the return of the original bill, and when the new bill is registered by inputting the bill receivable for the new bill, it is registered by linking it to the data of the original bill.

[0020] For example, in this embodiment, as shown in Figure 1, when a bill is issued, bill receivable data that holds the outcome of the bill (request for collection / collection / return / discount, etc.) is stored in a database, and as shown in Figure 2, when a bill jump occurs, the bill that is the target of the jump is returned, the bill number of the bill that was jumped is linked to it and the data for the new bill is registered, and by adding it to the reference for the return, it becomes possible to check the bill image and create an accounting entry for the return.

[0021] [2. Configuration] An example of the configuration of the bill receivable management apparatus 100 according to this embodiment will be described with reference to Fig. 3. Fig. 3 is a block diagram showing an example of the configuration of the bill receivable management apparatus 100 according to this embodiment.

[0022] 3, the bills receivable management device 100 is a commercially available desktop personal computer. Note that the bills receivable management device 100 is not limited to a stationary information processing device such as a desktop personal computer, but may also be a portable information processing device such as a commercially available notebook personal computer, PDA (Personal Digital Assistant), smartphone, or tablet personal computer.

[0023] The bill receivable management device 100 comprises a control unit 102, a communication interface unit 104, a memory unit 106, and an input / output interface unit 108. Each unit of the bill receivable management device 100 is connected to each other so that they can communicate with each other via any communication path.

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

[0025] 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 touch panel), a speaker, or a printer. The input device 112 may be a keyboard, a mouse, a microphone, or a monitor that cooperates with a mouse to achieve a pointing device function. In the following, the output device 114 may be referred to as the monitor 114 or the printer 114, and the input device 112 may be referred to as the keyboard 112 or the mouse 112.

[0026] 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 may 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 includes a bills receivable database 106a.

[0027] The bills receivable database 106a stores bills receivable data. Here, the bills receivable database 106a may store a bills receivable history consisting of bills receivable data linked to the outcome and status of the target bill. The bills receivable database 106a may also store journal data.

[0028] The control unit 102 is a CPU or the like that comprehensively controls the bills receivable management device 100. The control unit 102 has an internal memory for storing control programs such as an OS, programs that define various processing procedures, required data, etc., and executes various information processing based on these stored programs. Functionally, the control unit 102 is equipped with a bills receivable registration unit 102a, a bills receivable inquiry unit 102b, and a journal entry creation unit 102c.

[0029] The bills receivable registration unit 102a registers bills receivable data in the bills receivable history. Here, when a request for bill jump for the target bill is approved, the bills receivable registration unit 102a may register new bills receivable data in the bills receivable history based on the bills receivable data, linking the result of the target bill with "bill jump" and the status with "return," and may register new bills receivable data in the bills receivable history, linking the result of the jumped bill with "bill jump," the status with "collection request," and the target bill as the jump source of the jumped bill. Also, when a collection execution instruction for the jumped bill is set, the bills receivable registration unit 102a may register new bills receivable data in the bills receivable history, linking the result of the jumped bill with "collection," the collection date, the status with "collection execution," and the target bill as the jump source of the jumped bill. In addition, when a target bill to be jumped is specified on the reassembly input screen and a request for bill jump for the target bill is approved, the bill receivable registration unit 102a may register new bill receivable data in the bill receivable history based on the bill receivable data, with bill jump set as the outcome of the target bill and reassembly set as the status, and when a target bill to be jumped from is specified on the bill receivable input screen, it may register new bill receivable data in the bill receivable history, with bill jump set as the outcome of the jumped bill, collection request set as the status, and linked to the target bill as the jump source of the jumped bill.

[0030] The bills receivable inquiry unit 102b can inquire about bills receivable. Here, when an instruction to refer to the bills receivable history is set, the bills receivable inquiry unit 102b may display the bills receivable history. Also, when an instruction to inquire about the remaining balance is set, the bills receivable inquiry unit 102b may display the bills receivable data.

[0031] The journal entry creating unit 102c creates journal entry data. Here, the journal entry creating unit 102c may create bills receivable journal data corresponding to each bills receivable data based on the bills receivable history.

[0032] [3. Specific Examples] A specific example of this embodiment will be described with reference to FIGS.

[0033] [Bills Receivable Management Processing] An example of bills receivable management processing in this embodiment will now be described with reference to Fig. 4. Fig. 4 is a flowchart showing an example of processing by the bills receivable management apparatus 100 in this embodiment.

[0034] As shown in Figure 4, when the user specifies the target bill to be jumped on the return input screen via the input device 112 and the request for bill jump for the target bill is approved, the bill receivable registration unit 102a registers new bill receivable data in the bill receivable history stored in the bill receivable database 106a, based on the bill receivable data stored in the bill receivable database 106a, with the outcome of the target bill set to bill jump and the status set to return (step SA-1).

[0035] Then, when the user sets an instruction to refer to the bills receivable history via the input device 112, the bills receivable inquiry unit 102b displays a bills receivable history inquiry screen with the bills receivable history set on the output device 114 (step SA-2).

[0036] Then, the journalization creating unit 102c creates bills receivable journal data corresponding to each bills receivable data based on the bills receivable history (step SA-3).

[0037] Then, when the user specifies the target bill to be jumped from on the bill receivable input screen via the input device 112, the bill receivable registration unit 102a, based on the bill receivable data stored in the bill receivable database 106a, registers new bill receivable data in the bill receivable history stored in the bill receivable database 106a, with bill jump as the outcome of the jumped bill, collection request as the status, and linked to the target bill as the jump source of the jumped bill (step SA-4).

[0038] Then, when the user sets an instruction to refer to the bills receivable history via the input device 112, the bills receivable inquiry unit 102b displays a bills receivable history inquiry screen with the bills receivable history set on the output device 114 (step SA-5).

[0039] Then, the journalization creating unit 102c creates bills receivable journal data corresponding to each bills receivable data based on the bills receivable history (step SA-6), and ends the process.

[0040] Here, an example of bills receivable management processing in this embodiment will be described with reference to Fig. 5 to Fig. 8. Fig. 5 is a diagram showing an example of bills receivable management processing in this embodiment. Fig. 6 to Fig. 8 are diagrams showing examples of display screens in this embodiment.

[0041] In this embodiment, as shown in Figure 5(1), when the original bill receivable is collected, new bill receivable data is registered in the bill receivable history with the original bill receivable collection as the outcome and a collection request as the status, and journal data is created.

[0042] In this embodiment, as shown in Figure 6, when a bill jump occurs, if the user specifies the original bill receivable to be jumped on the reassembly input screen and sets the date, summary, and notes (for example, reason for jump), new bill receivable data linked to bill jump as the outcome and reassembly as the status is registered in the bill receivable history, and journal data is created, as shown in Figure 5 (2).

[0043] In this embodiment, as shown in Figure 7, when a bill jump is made, if the user specifies the bill number to be jumped from on the bill receivable input screen, as shown in Figure 5 (2), the outcome of the jumped bill is set as bill jump, the status is collection request, and new bill receivable data is set by linking it to the original target bill as the jump source of the jumped bill, and is registered in the bill receivable history, and journal data is created.

[0044] Here, as shown in Figure 8, in this embodiment, when the user sets an instruction to refer to the bills receivable history, a bills receivable history inquiry screen with the bills receivable history set is displayed, making it possible to refer to the regrouping input when a bill jump occurs and the bills receivable history after the jump.

[0045] As shown in Figure 5 (3), in this embodiment, when a user requests a bank to collect a post-jump bill and collection is carried out, the outcome of the post-jump bill is collection of the post-jump bill, the status is collection carried out, and new bills receivable data linked to the original target bill as the jump source of the post-jump bill is registered in the bills receivable history, and journal data is created.

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

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

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

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

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

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

[0052] Furthermore, with regard to the bill receivable management device 100, the components shown in the figures are functional concepts, and do not necessarily have to be physically configured as shown in the figures.

[0053] For example, all or any part of the processing functions of the bill receivable management device 100, particularly the processing functions performed by the control unit 102, may be realized by a CPU and a program interpreted and executed by the CPU, or may be realized as hardware using wired logic. The program is recorded on a non-transitory computer-readable recording medium containing programmed instructions for causing the information processing device to execute the processing described in this embodiment, and is mechanically read by the bill receivable management device 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 with the CPU to form the control unit.

[0054] In addition, this computer program may be stored in an application program server connected to the bills receivable management apparatus 100 via any network, and all or part of it may be downloaded as needed.

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

[0056] Furthermore, a "program" is a data processing method written in any language or description method, and does not matter whether it is in the form of 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 this embodiment, as well as the installation procedure after reading, can use well-known configurations and procedures.

[0057] The various databases stored in the memory unit 106 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.

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

[0059] 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. [Industrial Applicability]

[0060] The present invention is useful in all industries, including manufacturing industries where customers pay by bill. [Explanation of symbols]

[0061] 100 Bills receivable management device 102 Control section 102a Bills Receivable Registration Department 102b Bills Receivable Inquiry Section 102c Journal Entry Preparation Department 104 Communication interface unit 106 Storage section 106a Bills Receivable Database 108 Input / Output Interface Section 112 Input Device 114 Output Device 200 servers 300 Network

Claims

1. A bill receivable management device comprising a storage unit and a control unit, The storage unit a bill receivable storage means for storing a bill receivable history consisting of bill receivable data set by linking the outcome of the target bill and the status; Equipped with The control unit a bill receivable registration means for, when a request for bill jumping for the target bill is approved, registering new bill receivable data in the bill receivable history based on the bill receivable data, linking the bill jump as the outcome of the target bill and set as return as the status, and registering new bill receivable data in the bill receivable history, linking the bill jump as the outcome of the jumped bill, set as collection request as the status, and linking the target bill as the jump source of the jumped bill; A bill receivable management device comprising:

2. The control unit a bills receivable inquiry means for displaying the bills receivable history when a reference instruction for the bills receivable history is set; 2. The bills receivable management device according to claim 1, further comprising:

3. The control unit a journal entry creation means for creating bills receivable journal entry data corresponding to each bills receivable data based on the bills receivable history; 3. The bills receivable management device according to claim 1, further comprising:

4. The bill receivable registration means Furthermore, when a collection execution instruction is set for the jumped bill, the bill receivable management device described in claim 1 or 2 registers new bill receivable data in the bill receivable history, with collection as the outcome of the jumped bill, collection date, collection execution as the status, and the target bill as the jump source of the jumped bill.

5. The bill receivable registration means A bill receivable management device as described in claim 1 or 2, characterized in that when the target bill to be jumped is specified on the reassembly input screen and the request for the bill jump for the target bill is approved, new bill receivable data is registered in the bill receivable history based on the bill receivable data, with the bill jump set as the outcome of the target bill and the reassembly set as the status, and when the target bill to be jumped from is specified on the bill receivable input screen, new bill receivable data is registered in the bill receivable history, with the bill jump set as the outcome of the jumped bill, the collection request set as the status, and the target bill set as the jump source of the jumped bill.

6. The control unit a bills receivable inquiry means for displaying the bills receivable data when a remaining debt inquiry instruction is set; 2. The bills receivable management device according to claim 1, further comprising:

7. A bills receivable management method to be executed by a bills receivable management device having a storage unit and a control unit, The storage unit a bill receivable storage means for storing a bill receivable history consisting of bill receivable data set by linking the outcome of the target bill and the status; Equipped with Executed in the control unit: a bill receivable registration step for, when a request for bill jump for the target bill is approved, registering new bill receivable data in the bill receivable history based on the bill receivable data, which is set by linking the bill jump as the outcome of the target bill and return as the status, and registering new bill receivable data in the bill receivable history, which is set by linking the bill jump as the outcome of the jumped bill, collection request as the status, and the target bill as the jump source of the jumped bill; A bills receivable management method comprising:

8. A bills receivable management program to be executed by a bills receivable management device having a storage unit and a control unit, The storage unit a bill receivable storage means for storing a bill receivable history consisting of bill receivable data set by linking the outcome of the target bill and the status; Equipped with In the control unit, a bill receivable registration step for, when a request for bill jump for the target bill is approved, registering new bill receivable data in the bill receivable history based on the bill receivable data, which is set by linking the bill jump as the outcome of the target bill and return as the status, and registering new bill receivable data in the bill receivable history, which is set by linking the bill jump as the outcome of the jumped bill, collection request as the status, and the target bill as the jump source of the jumped bill; A bills receivable management program to execute the following.

Images