Deposit management device, deposit management method, and computer-readable recording medium

Abstract

To provide a deposit management device, a deposit management method, and a deposit management program capable of receiving an excessive deposit as a temporary deposit to each billing destination when bills to a plurality of branches are collectively received from the other head office and the excessive deposit occurs.SOLUTION: A deposit management device according to the present embodiment includes a control unit, and manages a transaction in which a bill to a plurality of branches is collectively deposited from a head office, the deposit management device including a deposit transfer unit that can access deposit data, a bill destination master, and collection schedule data, and that refers to the bill destination master and the collection schedule data after the deposit data is updated by a deposit, extracts a transfer bill destination of the deposit after the deposit data is updated by the deposit, and accepts the transfer bill as a temporary receipt for each bill destination in a case where overpayment occurs.SELECTED DRAWING: Figure 1

Description

[Technical Field]

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

[0002] There are transactions in which invoices to multiple branches are paid in bulk from the counterparty's headquarters. If an overpayment occurs in such a transaction, the overpayment is treated as a provisional receipt by the counterparty's headquarters, but there is a need to transfer the overpayment to each invoice recipient and manage credit.

[0003] Patent document 1 describes a deposit management device that has a control unit, wherein the control unit is equipped with a deposit recognition means that recognizes the date and amount of deposit from a contractor who has payment obligations with multiple payment due dates, a deposit accounting means that compares the deposit amount obtained by the deposit recognition means with the payment obligation amount on the deposit date, and if the deposit amount exceeds the payment obligation amount, records the difference as a deposit, and an appropriation means that, on the first payment due date after the date on which the deposit accounting means recorded the deposit, allocates the deposit recorded at that time as part or all of the payment obligation amount at that time. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Japanese Patent Application Publication No. 2023-23221 Summary of the Invention [Problem to be solved by the invention]

[0005] The technology in Patent Document 1 records excess payments as a deposit and applies the deposit to the amount of payment obligations from the next time onwards, but does not relate to the handling of excess payments that occur when bills to multiple branches are paid in one lump sum from the counterparty's headquarters.

[0006] The present invention has been made in consideration of the above-mentioned problems, and aims to provide a deposit management device, a deposit management method, and a deposit management program that, when bills to multiple branches are paid in bulk from the other party's headquarters and an overpayment occurs, can accept the overpayment as a provisional receipt for each billing destination. [Means for solving the problem]

[0007] In order to solve the above-mentioned problems and achieve the objectives, the deposit management device of the present invention is a deposit management device that has a control unit and manages transactions in which bills to multiple branches are deposited in one lump sum from the head office, and is capable of accessing deposit data that stores information including the deposit destination and deposit amount, a billing destination master that stores the deposit billing destination code of the head office that makes the payment and the billing destination code of each branch that makes the bill, linked to each other, and collection schedule data that stores information including the billing destination, billing destination code, and planned collection amount, and is characterized in that after the deposit data is updated by the deposit, the control unit refers to the billing destination master and the collection schedule data, extracts the transfer billing destination for the deposit, transfers the deposit, and after an overdeposit occurs, accepts the overdeposit as a provisional receipt for each billing destination.

[0008] In addition, the deposit management device of the present invention is capable of accessing debt balance data that stores information including debt balance, deposit amount, debt clearing amount, and provisional receipt amount, and the billing destination master stores the credit limit for each billing destination, and the control unit is characterized by having a credit balance inquiry unit that outputs the credit balance for each billing destination based on the credit limit of the billing destination master and the debt balance and provisional receipt amount of the debt balance data.

[0009] The deposit management method of the present invention is a deposit management method that is executed by a deposit management device that has a control unit and manages transactions in which bills to multiple branches are deposited in bulk from a head office, and the deposit management device has access to deposit data that stores information including the deposit destination and the deposit amount, a billing destination master that stores the deposit billing destination code of the head office that makes the payment and the billing destination code of each branch that makes the bill, linked to each other, and collection schedule data that stores information including the billing destination, billing destination code, and planned collection amount, and is characterized by including a deposit transfer step that is executed by the control unit, after the deposit data is updated by the deposit, refers to the billing destination master and the collection schedule data, extracts a transfer billing destination for the deposit, transfers the deposit, and then, if an overdeposit occurs, accepts the overdeposit as a provisional receipt for each billing destination.

[0010] The deposit management program of the present invention is a deposit management program that has a control unit and is executed by a deposit management device that manages transactions in which bills to multiple branches are deposited in one lump sum from a head office, and the deposit management device is able to access deposit data that stores information including the deposit destination and deposit amount, a billing destination master that stores the deposit billing destination code of the head office that makes the payment and the billing destination code of each branch that makes the bill, linked to each other, and collection schedule data that stores information including the billing destination, billing destination code, and planned collection amount, and causes the control unit to execute a deposit transfer step that, after the deposit data is updated by a deposit, refers to the billing destination master and the collection schedule data, extracts the transfer billing destination for the deposit, transfers the deposit, and then, if an overdeposit occurs, accepts the overdeposit as a provisional receipt for each billing destination. [Effects of the Invention]

[0011] According to the present invention, even if bills to multiple branches are paid in bulk from the counterparty's headquarters and an overpayment occurs, the overpayment can be accepted as a provisional receipt for each billing destination. [Brief explanation of the drawings]

[0012] [Figure 1]FIG. 1 is a diagram showing an example of the configuration of a deposit management device according to the present embodiment. [Figure 2] FIG. 2 is a diagram showing an example of deposit data. [Figure 3] FIG. 3 is a diagram showing an example of a deposit transfer processing screen. [Figure 4] FIG. 4 is a diagram illustrating an example of the billing destination master. [Figure 5] FIG. 5 is a diagram illustrating an example of collection schedule data. [Figure 6] FIG. 6 is a diagram showing an example of a deposit transfer processing screen. [Figure 7] FIG. 7 is a diagram showing an example of the deposit transfer subscreen. [Figure 8] FIG. 8 is a diagram showing an example of a deposit transfer processing screen. [Figure 9] FIG. 9 is a diagram illustrating an example of collection schedule data. [Figure 10] FIG. 10 is a diagram showing an example of deposit data. [Figure 11] FIG. 11 is a diagram showing an example of the payment reconciliation data. [Figure 12] FIG. 12 is a diagram showing an example of the bond balance data. DETAILED DESCRIPTION OF THE INVENTION

[0013] Hereinafter, embodiments of a deposit management device, a deposit management method, and a deposit management program according to the present invention will be described in detail with reference to the accompanying drawings. Note that the present invention is not limited to these embodiments.

[0014] [1. Configuration] An example of the configuration of the deposit management device according to this embodiment will be described with reference to Fig. 1 etc. Fig. 1 is a diagram showing an example of the configuration of the deposit management device 100 according to this embodiment.

[0015] The deposit management device 100 is constructed based on a commercially available desktop personal computer. The deposit management device 100 is not limited to those constructed based on a stationary information processing device such as a desktop personal computer, but may also be constructed based on a portable information processing device such as a commercially available notebook personal computer, PDA (Personal Digital Assistant), smartphone, or tablet personal computer.

[0016] The deposit 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 deposit management device 100 is connected to each other so as to be able to communicate with each other via any communication path.

[0017] The communication interface unit 104 communicably connects the deposit 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 deposit management device 100 and the server device 200 so that they can communicate with each other, and is, for example, the Internet or a LAN (Local Area Network). Note that the data stored in the memory unit 106 may be stored in the server device 200, for example.

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

[0019] Various databases, tables, files, etc. are stored in the storage unit 106. Computer programs that work in conjunction with the OS (Operating System) to issue commands to the CPU (Central Processing Unit) to perform various processes are recorded in the storage unit 106. 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, an optical disk, etc.

[0020] The storage unit 106 stores, for example, deposit data 106a, billing destination master 106b, collection schedule data 106c, deposit reconciliation data 106d, and debt balance data 106e.

[0021] The deposit data 106a is data related to deposits from business partners. As shown in an example in Figure 2, the deposit data 106a stores information such as the deposit number, deposit request destination, deposit date, credit item, deposit amount, adjustment amount, fee, and reconciliation source.

[0022] The billing destination master 106b stores the billing destination code of the head office that makes the payment and the billing destination code of each branch that makes the bill, in association with each other. As shown in an example in Figure 3, the billing destination master 106b stores information such as the billing destination code, billing destination name, billing destination code for the payment, the credit item at the time of payment, and the credit limit.

[0023] The collection schedule data 106c is data related to the collection of receivables. As shown in an example in Fig. 4, the collection schedule data 106c stores information such as the billing destination code, billing destination name, scheduled collection date, scheduled collection amount, and payment reconciliation amount.

[0024] The payment reconciliation data 106d is data related to the reconciliation of receivables. As shown in an example in Figure 11, the payment reconciliation data 106d stores the payment reconciliation number, payment number, payment invoice destination, payment reconciliation date, reconciliation source, reconciliation amount, unreconciled amount, etc.

[0025] The receivables balance data 106e is data related to the receivables balance. As shown in an example in Fig. 12, the data includes the accounting year and month, billing destination, previous month's receivables balance, current month's sales amount, current month's deposit amount, current month's adjustment amount, current month's commission, current month's receivables write-off amount, current month's provisional receipt amount, current month's receivables balance, etc.

[0026] The control unit 102 is a CPU or the like that comprehensively controls the deposit 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.

[0027] The control unit 102 conceptually includes a deposit transfer unit 102a, a credit inquiry unit 102b, and the like.

[0028] The deposit transfer unit 102a refers to the billing destination master 106b and the collection schedule data 106c, extracts the transfer billing destination of the deposit, and accepts the deposit transfer. In addition, if the deposit transfer amount is an overpayment that is greater than the billing amount (collection amount), the deposit transfer unit 102a accepts the overpayment as a provisional receipt for each billing destination.

[0029] The credit balance inquiry unit 102b outputs the credit balance for each billing party based on the credit limit in the billing party master 106b and the credit balance and provisional receipt amount in the credit balance data 106e.

[0030] [2. Processing] Here, a specific example of the process executed by the deposit management apparatus 100 will be described with reference to FIGS.

[0031] FIG. 2 is a diagram showing an example of deposit data 106a-1. After deposit data 106a-1 is updated with deposit from the billing destination, the user performs the deposit transfer process using deposit transfer processing screen MA. FIG. 3 is a diagram showing an example of deposit transfer processing screen MA-1. When the user enters the deposit number of the transaction for which the deposit transfer process is to be performed in the "Deposit Number" field on deposit transfer processing screen MA-1, the entered deposit number is used as a call key, and the "Deposit Billing Destination," "Deposit Date," "Amount of Funds to be Applied," and "Credit Account Classification" are automatically entered from deposit data 106a-1 into deposit transfer processing screen MA-1.

[0032] When the user presses "Display transfer billing destination" on the deposit transfer processing screen MA-1, the deposit transfer unit 102a references the billing destination master 106b and the collection schedule data 106c-1 to extract the transfer billing destination of the deposit. Figure 4 is a diagram showing an example of the billing destination master 106b, and Figure 5 is a diagram showing an example of the collection schedule data 106c-1.

[0033] The billing destination master 106b is an extract of billing destinations with a received billing destination code of "A100." In the billing destination master 106b in Figure 4, the received billing destination code "A100" links the billing destination (head office) with its branch offices, namely, billing destination (Yokohama), billing destination (Osaka), billing destination (Nagoya), and billing destination (Fukuoka).

[0034] The deposit transfer unit 102a extracts the invoices linked to the deposit code from the invoice master 102b, and then extracts invoices with outstanding debts (invoices for which deposits have not been settled) from the collection schedule data 106c-1. In the collection schedule data 106c-1 of Figure 5, "17,530" yen (record 3) for the invoices (Yokohama) and "8,470" yen (record 4) for the invoices (Osaka) that have not been settled as of May 31, 2024 are extracted.

[0035] 6 is a diagram showing an example of the deposit transfer processing screen MA-2 that displays the extracted transfer billing destination. The "Billing destination" and "Amount to be collected" are automatically entered through extraction.

[0036] When the user specifies the billing details on the deposit transfer processing screen MA-2, the deposit transfer subscreen MB is launched. Figure 7 is a diagram showing an example of the deposit transfer subscreen MB. The deposit transfer subscreen MB-1 is the screen when the billing destination (Yokohama) is specified, and the deposit transfer subscreen MB-2 is the screen when the billing destination (Osaka) is specified. When the deposit transfer subscreen MB is launched, the line number, billing destination, and total billing amount have already been entered.

[0037] When the user specifies the deposit transfer amount, adjustment amount, and fee on the deposit transfer subscreen MB, the total deposit transfer amount, which is the sum of the deposit transfer amount, adjustment amount, and fee, and the total unsettled amount, which is the difference between the total deposit transfer amount and the total invoice amount, are automatically entered. After specifying the deposit transfer amount, adjustment amount, and fee, the user presses the "Confirm" button to move to the deposit transfer processing screen MA.

[0038] 8 is a diagram showing an example of the deposit transfer processing screen MA-3 that displays the deposit transfer amount, etc. specified on the deposit transfer sub-screen MB. If there are no problems with the displayed deposit transfer amount, adjustment amount, fee, deposit transfer total amount, unapplied amount, etc., when the user presses the "Register" button, the deposit transfer unit 102a will apply the deposit transfer amount to the amount to be collected, and will accept the unapplied amount, which is an overpayment, as a provisional receipt for each billing destination.

[0039] When the deposit transfer unit 102a clears the scheduled collection amount, the collection schedule data 106c, deposit data 106a, deposit clearing data 106d, and claim balance data 106e are updated. Fig. 9 is a diagram showing an example of the updated collection schedule data 106c-2, and Fig. 10 is a diagram showing an example of the updated deposit data 106a-2. Fig. 11 is a diagram showing an example of the deposit clearing data 106d before and after the update, and Fig. 12 is a diagram showing an example of the claim balance data 106e before and after the update.

[0040] The collection schedule data 106c-2 is updated by inputting the payment application amounts for the billing destination (Yokohama) (record 3 in the table) and the billing destination (Osaka) (record 4) on May 31, 2024, when the payment transfer was made, as shown in Figure 9. In the collection schedule data 106c-1 before the update (see Figure 5), the payment application amounts for the billing destination (Yokohama) (record 3 in the table) and the billing destination (Osaka) (record 4) are "0", but in the collection schedule data 106c-2 after the update, the payment application amount for the billing destination (Yokohama) (record 3 in the table) is input as "17,530" yen, and the payment application amount for the billing destination (Osaka) (record 4 in the table) is input as "8,470" yen.

[0041] In the deposit data 106a-2, as shown in Figure 10, the deposit from the billing destination (head office) is transferred to the billing destination (Yokohama) and billing destination (Osaka), so the deposit amount, adjustment amount, fee, and clearing source are each updated to "0" (see Figure 2 for the data before the update). In addition, a new deposit number is assigned to the billing destination (Yokohama) and billing destination (Osaka) to which the deposit transfer was made, and new data is stored along with the deposit billing destination, deposit date, credit item, deposit amount, adjustment amount, fee, and clearing source.

[0042] As shown in Figure 11, the deposit reconciliation number "NK1000000001" in the deposit reconciliation data 106d-1 before the update had not been reconciled, so the reconciled amount was "0" yen and the reconciliation source was "31,000" yen, but because the full amount has been reconciled through the deposit transfer, the updated deposit reconciliation data 106d-2 has an reconciled amount of "31,000" yen and a reconciliation source of "0" yen. Also, in the updated deposit reconciliation data 106d-2, new deposit reconciliation numbers are assigned for the billing destination (Yokohama) and billing destination (Osaka) for which the deposit transfer was made, and new data is stored along with the deposit number, deposit billing destination, deposit reconciliation date, reconciliation source, reconciliation amount, and unreconciled amount.

[0043] As shown in Figure 12, the billing destination (head office) (record 3 in the table) of the receivables balance data 106e-1 before the update has the current month's deposit amount of "30,000" yen, current month's adjustment amount of "340" yen, current month's fee of "660 yen", current month's provisional receipt amount of "31,000" yen, and current month's receivables balance of "-31,000" yen entered. However, in the updated receivables balance data 106e-2, the full amount will be transferred, so the data will be updated to the current month's deposit amount of "0" yen, current month's adjustment amount of "0" yen, current month's fee of "0" yen, current month's provisional receipt amount of "0" yen, and current month's receivables balance of "0" yen. Furthermore, the billing destination (Yokohama) (record 4 in the table) in the receivables balance data 106e-1 before the update had the following entered: current month's deposit amount "0" yen, current month's adjustment amount "0" yen, current month's fee "0" yen, current month's receivables write-off amount "0" yen, current month's provisional receipt amount "0" yen, and current month's receivables balance "0" yen. However, in the updated receivables balance data 106e-2, the transfer input process has updated these to: current month's deposit amount "19,930" yen, current month's adjustment amount "200" yen, current month's fee "400" yen, current month's receivables write-off amount "17,530" yen, current month's provisional receipt amount "3,000" yen, and current month's receivables balance "12,650" yen. Similarly, the billing destination (Osaka) (record 5 in the table) in the receivables balance data 106e-1 before the update has the following entered: current month's deposit amount "0" yen, current month's adjustment amount "0" yen, current month's fee "0" yen, current month's receivables write-off amount "0" yen, current month's provisional receipt amount "0" yen, and current month's receivables balance "0" yen. However, in the updated receivables balance data 106e-2, the transfer input process has updated the following to current month's deposit amount "10,070" yen, current month's adjustment amount "140" yen, current month's fee "260" yen, current month's receivables write-off amount "8,470" yen, current month's provisional receipt amount "2,000" yen, and current month's receivables balance "7,920" yen.

[0044] When the credit balance data 106e is updated, the credit balance section 102b can output the credit balance for each billing party from the credit balance in the billing party master 106b and the current month's credit balance and current month's provisional receipt amount in the billing party balance data 106e.

[0045] The billing destination master 106b stores the credit limit for each billing destination, as shown in Figure 4. For example, the credit limit for the billing destination (Yokohama) is "50,000", and the credit limit for the billing destination (Osaka) is "50,000". The credit balance is the credit limit plus the amount received for the current month minus the current month's outstanding receivables. The credit balance inquiry unit 102b outputs the credit balance for the billing destination (Yokohama) as "40,350" (50,000 + 3,000 - 12,650) and the credit balance for the billing destination (Osaka) as "34,080" (50,000 + 2,000 - 7,920).

[0046] As described above, the deposit management device 100 according to this embodiment can accept the overpayment as a provisional receipt for each invoice recipient even if the invoices for multiple branches are received in a lump sum from the counterparty's headquarters and an overpayment occurs. This also makes it possible to output the credit balance for each branch, making it possible to manage the credit limit for each branch.

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

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

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

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

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

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

[0053] Furthermore, with regard to the deposit 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.

[0054] For example, all or any part of the processing functions of the deposit management device 100, particularly the processing functions performed by the control unit, 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 processes described in this embodiment, and is mechanically read by the deposit 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 give 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.

[0055] In addition, this computer program may be stored in an application program server connected to the deposit management device 100 via any network, and it is also possible to download all or part of it as needed.

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

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

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

[0059] The deposit 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 deposit management device 100 may also be realized by installing software (including programs or data, etc.) that causes the device to realize the processing described in this embodiment.

[0060] 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]

[0061] The present invention is particularly useful in cases where bills to multiple branches are paid in bulk from the counterparty's headquarters. [Explanation of symbols]

[0062] 100 Deposit management device 102 Control section 102a Deposit Transfer Section 102b Credit balance inquiry department 104 Communication interface unit 106 Storage section 106a Deposit Data 106b Billing Master 106c Scheduled collection data 106d Receipt reconciliation data 106e Debt Balance Data 108 Input / Output Interface Section 200 servers 300 Network 400 Input Device 500 output devices

Claims

1. A deposit management device that includes a control unit and manages transactions in which bills to multiple branches are deposited in bulk from a head office, deposit data that stores information including the deposit destination and the deposit amount; A billing master in which the payment billing code of the head office that makes the payment and the billing code of each branch that makes the bill are linked and stored; collection schedule data storing information including a billing address, a billing address code, and a scheduled collection amount; is accessible to The control unit a deposit transfer unit that, after the deposit data is updated by the deposit, refers to the billing destination master and the collection schedule data, extracts a transfer billing destination for the deposit, and after the deposit transfer, if an overpayment occurs, receives the overpayment as a provisional receipt for each billing destination; A deposit management device comprising:

2. Accounts receivable balance data, which stores information including account balance, amount received, amount cleared, and amount received temporarily; is accessible to The billing destination master stores a credit limit for each billing destination, The control unit a credit balance inquiry unit that outputs the credit balance for each billing party based on the credit limit of the billing party master and the receivable balance and provisional receipt amount of the receivable balance data; 2. The deposit management device according to claim 1, further comprising:

3. A deposit management method executed by a deposit management device that includes a control unit and manages transactions in which bills to multiple branches are deposited in bulk from a head office, comprising: The deposit management device is deposit data that stores information including the deposit destination and the deposit amount; A billing master in which the payment billing code of the head office that makes the payment and the billing code of each branch that makes the bill are linked and stored; collection schedule data storing information including a billing address, a billing address code, and a scheduled collection amount; is accessible to causing the control unit to execute a deposit transfer step of, after the deposit data has been updated by the deposit, referring to the billing destination master and the collection schedule data, extracting a transfer billing destination for the deposit, and transferring the deposit, and if an overpayment occurs, accepting the overpayment as a provisional receipt for each billing destination; A deposit management method comprising:

4. A deposit management program to be executed by a deposit management device that has a control unit and manages transactions in which bills to multiple branches are deposited in bulk from a head office, The deposit management device is deposit data that stores information including the deposit destination and the deposit amount; A billing master in which the payment billing code of the head office that makes the payment and the billing code of each branch that makes the bill are linked and stored; collection schedule data storing information including a billing address, a billing address code, and a scheduled collection amount; is accessible to The control unit a deposit transfer step of, after the deposit data has been updated by the deposit, referring to the billing destination master and the collection schedule data, extracting a transfer billing destination for the deposit, and transferring the deposit, and if an overpayment occurs, accepting the overpayment as a provisional receipt for each billing destination; A deposit management program to execute the above.

Images