Money reception management device, money reception management method, and money reception management program

Abstract

To reduce the risk of making an input error or the like by suppressing a business burden of money reception management.SOLUTION: A money reception management device 100 acquires a money reception file 10 and credit data 12, performs an appropriation process for appropriating received money to credits en bloc by batch processing, outputs information about unallocated received money when the unallocated received money for which a credit of an appropriation destination has not been identified is present, extracts and outputs information about a credit which becomes a candidate of an appropriation destination for target unallocated received money which is the input unallocated received money on the basis of the credit data 12 when a message of individually determining credits of appropriation destinations for the output unallocated received money is input, performs an individual appropriation process for appropriating the target unallocated received money to an identified credit when a message of identification of the credit of the appropriation destination for the target unallocated received money is input, and performs a disclaim process for determining that processing has been done in a state where no credit is identified for the target unallocated received money when a message of not identifying a credit of the appropriation destination for the target unallocated received money is input.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] Patent document 1 describes a deposit management device that performs deposit management operations, and describes how batch processing is performed to identify and allocate claims for each deposit made by bank transfer or other means from debtors. [Prior art documents] [Patent documents]

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

[0004] In a deposit management device such as that described in Patent Document 1, not all deposits are as expected, such as deposits for which the receivable cannot be identified or deposits with an excess or deficiency in the amount, and in unexpected cases, the operator must make a judgment on each case. In this case, the operator's workload is heavy and there is a risk of input errors.

[0005] 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 can reduce the workload of deposit management and reduce the risk of input errors, etc. [Means for solving the problem]

[0006] In order to solve the above-mentioned problems and achieve the object, the deposit management device of the present invention is a deposit management device equipped with a control unit, wherein the control unit acquires a deposit file showing information on deposits from a plurality of debtors and credit data showing the correspondence between the debtors and the credits of the debtors, searches for the credits to which each of the deposits in the deposit file should be allocated, and when the credit to which the deposit should be allocated is specified, performs allocation processing in a batch process to allocate the deposits to the specified credits, and when there is an unallocated deposit, which is a deposit for which the credit to which the deposit should be allocated is not specified in the allocation processing, Information is output, and if an input is made to individually determine the receivable to which the output unallocated deposit should be allocated, information on the receivables that are candidates for allocation to the target unallocated deposit, which is the unallocated deposit for which the input was made, is extracted and output based on the receivables data, and if an input is made to the effect that the receivable to which the target unallocated deposit should be allocated has been identified, an individual allocation process is performed to allocate the target unallocated deposit to the identified receivable, and if an input is made to the effect that the receivable to which the target unallocated deposit should be allocated is not identified, an unclaimed process is performed to process the target unallocated deposit without identifying the receivable.

[0007] Furthermore, the deposit management method according to the present invention includes the steps of: acquiring a deposit file showing information on deposits from a plurality of debtors and credit data showing the correspondence between the debtors and the credits of the debtors; searching for the credits to which each of the deposits in the deposit file should be allocated; and, when the credits to which the deposits should be allocated are identified, performing an allocation process in a batch process to allocate the deposits to the identified credits; and, when an unallocated deposit exists, which is a deposit for which the credit to which the deposits should be allocated is not identified in the allocation process, outputting information on the unallocated deposit; and, for the output unallocated deposit, searching for the credits to which the deposits should be allocated. When an input is made to judge the receivables individually, the control unit performs the following steps: extracting and outputting information about the receivables that are candidates for allocation to the target unallocated deposit, which is the unallocated deposit for which the input was made, based on the receivable data; when an input is made to indicate that the receivable to which the target unallocated deposit is to be allocated has been identified, performing individual allocation processing to allocate the target unallocated deposit to the identified receivable; and when an input is made to indicate that the receivable to which the target unallocated deposit is to be allocated has not been identified, performing non-claim processing to mark the target unallocated deposit as processed without identifying the receivable.

[0008] Furthermore, the deposit management program according to the present invention is a deposit management program executed by a deposit management device equipped with a control unit, and acquires a deposit file showing information on deposits from a plurality of debtors and credit data showing the correspondence between the debtors and the credits of the debtors, searches for the credits to which each of the deposits in the deposit file should be allocated, and when the credit to which the deposit should be allocated is identified, performs an allocation process in a batch process to allocate the deposit to the identified credit, and when there is an unallocated deposit, which is a deposit for which the credit to which the deposit should be allocated is not identified in the allocation process, outputs information on the unallocated deposit. The control unit executes the following processes: when an input is made to individually determine the receivables to which the output unallocated deposit should be allocated, a process of extracting and outputting information on the receivables that are candidates for allocation to the input target unallocated deposit, which is the unallocated deposit for which the input was made, based on the receivables data; when an input is made to the effect that the receivable to which the output unallocated deposit should be allocated has been identified, a process of allocating the target unallocated deposit to the identified receivable; and when an input is made to the effect that the receivable to which the output unallocated deposit should be allocated has been completed without identifying the receivable for the target unallocated deposit. [Effects of the Invention]

[0009] The present invention has the effect of reducing the workload of managing deposits and reducing the risk of input errors, etc. [Brief explanation of the drawings]

[0010] [Figure 1] FIG. 1 is a block diagram showing an example of a deposit management device according to this embodiment. [Figure 2] FIG. 2 is a flowchart showing an example of the process flow in the deposit management device. [Figure 3] FIG. 3 shows an example of an input screen, a file, and data used in batch processing. [Figure 4] FIG. 4 is a diagram showing an example of processing for a deposit for which the target receivable has been identified. [Figure 5] FIG. 5 is a diagram showing an example of a screen showing a list of unallocated deposits. [Figure 6] FIG. 6 is a diagram showing an example of the deposit reconciliation input screen and data related to processing using this screen. [Figure 7] FIG. 7 is a diagram showing another example of the deposit reconciliation input screen and data related to processing using this screen. [Figure 8] FIG. 8 is a diagram showing an example of an input screen and data used in the deposit refund process. [Figure 9] FIG. 9 is a diagram showing an example of an input screen and data used in a deposit transfer process. [Figure 10] FIG. 10 is a diagram showing an example of a case where a claim cannot be identified in the individual allocation process. [Figure 11] FIG. 11 is a diagram showing an example of a screen for checking the processing result. [Figure 12] FIG. 12 is a diagram showing another example of a screen for checking the processing result. [Figure 13] FIG. 13 is a diagram showing another example of a screen for checking the processing result. DETAILED DESCRIPTION OF THE INVENTION

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

[0012] [1. Configuration] An example of the configuration of a deposit management device according to this embodiment will be described with reference to the drawings. The deposit management device according to this embodiment is used for debt collection operations in the financial industry and for debt collection operations for various businesses. In such debt management and debt collection operations, deposits are made by bank transfer, etc., and batch processing may be performed to identify and appropriate each deposit.

[0013] Fig. 1 is a block diagram showing an example of a deposit management device 100 according to this embodiment. The deposit management device 100 shown in Fig. 1 is constructed based on a commercially available desktop personal computer. Note that 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.

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

[0015] The control unit 102 is a CPU (Central Processing Unit) or the like that controls the deposit management device 100 in an integrated manner. The control unit 102 performs information processing based on various data stored in the storage unit 106. 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 performs various information processing based on these stored programs. The specific processing content of the control unit 102 will be described later.

[0016] The communication interface unit 104 communicatively 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 other devices so that they can communicate with each other, such as the Internet or a LAN (Local Area Network). The network 300 may also have a function of connecting the deposit management device 100 and the server 200 so that they can communicate with each other. In this case, the data stored in the memory unit 106 may be stored in the server 200, for example.

[0017] 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. In the following, the output device 114 may be referred to as the monitor 114, and the input device 112 may be referred to as the keyboard 112 or the mouse 112.

[0018] Various databases, tables, files, etc. are stored in the storage unit 106. Computer programs that work in conjunction with an OS (Operating System) to issue instructions to a CPU to perform various processes are recorded in the storage unit 106. The storage unit 106 can be, for example, a memory device such as a RAM (Random Access Memory) or a ROM (Read Only Memory), a fixed disk device such as a hard disk, a flexible disk, an optical disk, etc.

[0019] The memory unit 106 stores various files and data, such as a deposit file 10, deposit data 11, bond data 12, allocation candidate data 13, bond transaction data 14, deposit allocation data 15, and screen creation data 16. The screen creation data 16 is data that constitutes the lump-sum deposit reconciliation input screen W1, deposit reconciliation list screen W2, deposit reconciliation input screen W3, bond list screen W4, deposit transfer screen W5, and bond portal screen W6, which will be described later. The various files and data in the memory unit 106 will be explained together in the specific examples of processing below.

[0020] [2. Specific examples of processing] Next, a detailed description will be given of a specific example of the processing executed by the control unit 102 in the deposit management apparatus 100. FIG.

[0021] <Lump sum allocation through batch processing> FIG. 3 shows an example of an input screen, file, and data used in batch processing. The control unit 102 acquires the deposit file 10 input from the communication interface unit 104 (step S101) and stores the acquired deposit file 10 in the memory unit 106. Here, the deposit file 10 indicates information regarding deposits from multiple debtors. The deposit file 10 includes, for example, the following fields: data category, accounting date, transaction amount, remittance requester code, and remittance requester name. FIG. 3 shows an example in which data for three deposits from three different debtors is included.

[0022] 3, in batch processing, the control unit 102 outputs a lump-sum deposit reconciliation input screen W1 to the monitor 114. Note that data such as the format of the lump-sum deposit reconciliation input screen W1 can refer to data stored in advance in the screen creation data 16.

[0023] The lump sum deposit reconciliation input screen W1 displays the following items as execution conditions for the lump sum deposit reconciliation process: information indicating whether the deposit file is the target for lump sum processing, the import date and time of the deposit file, the import user ID, the import user name, and the imported file information. In the information item indicating whether the file is the target for execution, by entering a check mark in the box, the deposit file becomes the target for lump sum processing. By entering a check mark in the deposit file box and pressing the "Execute" button, the control unit 102 will perform the lump sum deposit reconciliation process for the deposit file 10 with the check mark entered.

[0024] In the lump-sum deposit reconciliation process, the control unit 102 creates deposit data 11 based on the acquired deposit file 10 (step S102) and stores the created deposit data 11 in the memory unit 106. As shown in Figure 3, the deposit data 11 includes items such as deposit ID, deposit date, deposit amount, deposit route code, company account code, and imported deposit information. In the example shown in Figure 3, deposit data 11 has been created for three deposits in the deposit file 10.

[0025] The control unit 102 generates candidate allocation data 13 based on the deposit data 11 and the claim data 12 stored in advance in the storage unit 106 (step S103). The claim data 12 indicates the correspondence between the debtor and the debtor's claim. The claim data 12 is data created in advance based on the correspondence between the debtor and the claim, and includes, for example, the following items: claim ID, customer name in kana, customer name, product code, product name, and invoice amount.

[0026] In step S103, the control unit 103 searches for the corresponding bond for each deposit by comparing each item in the deposit file 10 with each item in the bond data 12. This comparison can be performed, for example, using a name matching master. The name matching master 17 includes a name matching ID and the items to be compared. The name matching master 17 can perform comparison using the name (name matching 1) and the invoice amount (name matching 2). The name matching master 17 can be stored in the memory unit 106.

[0027] The control unit 103 generates candidate allocation data 13 based on the results of the matching (name matching). The candidate allocation data 13 is data including a deposit ID, a claim ID, a customer name in kana, a customer name, an invoice amount, and a name matching result. In the candidate allocation data 13, the name matching result may be, for example, "claim confirmed," which indicates that a claim corresponding to the deposit has been identified, "multiple matches," which indicates that multiple candidates for the deposit have been found, or "invoice amount mismatch," which indicates that the deposited amount differs from the invoice amount.

[0028] The example shown in Figure 3 shows a case where a lump-sum allocation process was performed on three deposits contained in the deposit file 10, and the claim could be identified for one of them (the deposit with deposit ID 150 in the deposit data 11), but the claim could not be identified for the other two (the deposits with deposit IDs 151 and 152 in the deposit data 11). Specifically, the deposit with deposit ID 151 corresponds to multiple claims based on the name and invoice amount, and the deposit with deposit ID 152 corresponds to one claim based on the name, but the invoice amount does not match.

[0029] FIG. 4 is a diagram showing an example of processing for a deposit for which a target receivable has been identified. As shown in FIG. 4, the control unit 102 determines that a target receivable has been identified for a deposit for which the name matching result in the allocation candidate data 13 is "0: confirmed receivable" (Yes in step S104). The control unit 102 performs allocation processing for a deposit for which it has determined that a target receivable has been identified (step S105). In the allocation processing, the control unit 102 creates bond transaction data 14 and deposit allocation data 15. The bond transaction data 14 includes the following items: a bond ID, a bond log ID, transaction details, transaction date, transaction amount, receivable balance, and deposit. The deposit allocation data 15 includes the following items: an ID for identifying the deposit allocation, a deposit ID, a deposit date, a deposit amount, a bond log ID, an unbilled application reason code, and remarks. As shown in FIG. 4, the control unit 102 generates new bond transaction data 14 and new deposit allocation data 15 with a bond log ID of 25711 for the deposit with a deposit ID of 100 in the allocation candidate data 13.

[0030] <Individual allocation process for unallocated receipts> After performing the lump-sum allocation batch processing, the control unit 102 displays on a list screen (step S106) any deposits for which no receivables could be identified (unassigned deposits) (No in step S104). FIG. 5 is a diagram showing an example of a screen showing a list of unallocated deposits. As shown in FIG. 5, the control unit 102 outputs the deposit reconciliation list screen W2 to the monitor 114. Note that data such as the format of the deposit reconciliation list screen W2 can refer to data stored in advance in the screen creation data 16. The deposit reconciliation list screen W2 displays the following items for each deposit for which no receivables could be identified: deposit ID, deposit date, deposit amount, deposit route, company account, and imported deposit information. The control unit 102 references the deposit data 11 and deposit allocation data 15 shown in FIG. 5 and displays on the deposit reconciliation list screen W2 any deposits for which no deposit allocation data 15 linked by a deposit ID exists.

[0031] On the deposit reconciliation list screen W2, a deposit can be selected by user operation. When a deposit is selected and the "Display" button is operated, the control unit 102 displays information about the deposit. Figure 6 is a diagram showing an example of the deposit reconciliation input screen and data related to processing using this screen. The deposit reconciliation input screen W3 shown in Figure 6 allows the user to make individual judgments about deposits for which the receivables could not be identified.

[0032] The deposit reconciliation input screen W3 displays information on deposit occurrence (deposit ID, deposit date, deposit amount, depositor, deposit route, company account), allocation history (reconciliation ID, credit ID, customer name, customer name in kana, credit log ID, reconciliation amount, non-billing reason), and allocation destination candidates (credit ID, customer name, customer name in kana, name matching information, billing amount). The example shown in Figure 6 shows an example where multiple allocation destination candidates were found when the customer name in kana is the same.

[0033] The candidate allocation data 13 shown in FIG. 6 shows candidate destinations for the same customer name written in kana but with different kanji characters, such as "Tenkomi Jiro" and "Tenkomi Jiro." It can be seen that the deposit displayed on the deposit reconciliation input screen W3 is a deposit from "Tenkomi Jiro" with a deposit ID of 151. The user confirms with "Tenkomi Jiro" and, for example, if "Tenkomi Jiro" contacts the user to request that the deposit with ID 151 be allocated to bond ID 20-1, the allocation destination for the deposit with ID 151 is confirmed. In this case, the user selects the allocation destination with bond ID 20-1 from the two candidate allocation destinations and clicks the "Apply" button. When the user makes such an input (Yes in step S107), the control unit 102 performs individual allocation processing for the deposit with ID 151, allocating it to the bond with bond ID 20-1 (step S108).

[0034] In the individual allocation process, the control unit 102 generates new bond transaction data 14 and deposit allocation data 15 with a claim log ID of 25714 for a deposit with a deposit ID of 151 in the allocation candidate data 13, as shown in Fig. 6. The control unit 102 determines whether the deposit amount matches the claim amount (step S109). If the deposit amount matches the claim amount (Yes in step S109), no deposit is generated in the bond transaction data 14, the process for the deposit is completed, and the control unit 102 proceeds to step S115.

[0035] FIG. 7 shows another example of a deposit reconciliation input screen and data related to processing using this screen. FIG. 7 illustrates a case where there is an overpayment or underpayment relative to the claim amount, i.e., a case where the amount of the deposit does not match the claim amount. The deposit reconciliation input screen W3 in FIG. 7 shows an example where the depositor and the claim customer are the same person, "Tenkomi Saburo," but a deposit of 30,000 yen was made for a claim of 20,000 yen. In this case, if the customer separately notifies the user that they have mistakenly overpaid, the claim (claim ID 300-1) displayed as a potential allocation destination can be identified as the destination for the deposit. In this case, the user simply selects the claim with claim ID 300-1 as a potential allocation destination and clicks the "Reconcile" button.

[0036] In this case, similarly to the above, when the user inputs the relevant information (Yes in step S107), the control unit 102 performs individual allocation processing for the deposit with deposit ID 152, assigning the bond with bond ID 301-1 as the allocation destination (step S108). In the individual allocation processing, as shown in FIG. 7, the control unit 102 generates new bond transaction data 14 and deposit allocation data 15 with a bond log ID of 25715 for the deposit with deposit ID 152 in the allocation destination candidate data 13. The control unit 102 determines whether the deposit amount matches the claim amount of the bond (step S109). In the example shown in FIG. 7, the deposit is in excess of the claim amount of the bond, so a deposit is generated. Specifically, the excess deposit of 10,000 yen becomes the deposit. In such a case, the control unit 102 determines that the deposit amount does not match the claim amount of the bond (No in step S109). Although the example shown in FIG. 7 shows an example of excessive deposit, the same processing can be performed when there is a shortfall in the amount of deposit.

[0037] If the amount of the deposit does not match the amount claimed for the claim (No in step S109), the control unit 102 determines whether or not there is a balance for the claim amount after applying the deposit to the claim (step S110). If there is a balance for the claim amount (Yes in step S110), the control unit 102 performs processing to apply the excess or shortfall of the deposit amount, in this case the deposit, to the next application process (step S111).

[0038] On the other hand, if there is no outstanding claim (No in step S110), the control unit 102 performs a refund process for the excess deposit (step S112).

[0039] FIG. 8 is a diagram showing an example of an input screen and data used in the deposit refund process. As shown in FIG. 8, when performing the refund process, the control unit 102 displays the bond list screen W4 on the monitor 114. The bond list screen W4 has an input section for inputting search conditions (customer name in kana, customer name in kanji, bond balance, deposit amount). When the "Display" button is pressed with specified conditions entered in the input section, the control unit 102 searches for bonds that meet the entered conditions and displays the search results as a list. As shown in FIG. 8, the control unit 102 references the bond transaction data 14 to obtain the current amount of the deposit. The control unit 102 also references the bond data 12 to obtain bond information for screen display. In the example shown in FIG. 8, information about the bond with bond ID 301-1 is displayed. The bond with bond ID 301-1 has no bond balance and a deposit of 10,000 yen.

[0040] In this state, when the user selects the bond with bond ID 301-1 and presses the "Transfer" button, the control unit 102 performs the transfer process of the deposit.

[0041] FIG. 9 is a diagram showing an example of an input screen and data used in a deposit transfer process. As shown in FIG. 9, when performing a transfer process, the control unit 102 displays a deposit transfer screen W5 on the monitor 114. The deposit transfer screen W5 displays basic information such as a bond ID, a customer name, and a customer name in kana. The deposit transfer screen W5 also displays bond information (bond ID, bond status, bond balance, deposit, transfer deposit). The transfer deposit is the amount to be refunded and is input by a user operation. The deposit transfer screen W5 also displays transfer information (transfer date, transfer source account, transfer destination customer account, total transfer amount, transfer fee, net transfer amount, and summary). The transfer source account, transfer destination customer account, transfer fee, summary, etc. are input by a user operation. When the "Execute" button is pressed with the above items entered on the deposit transfer screen W5, the control unit 102 performs the deposit transfer process. After the transfer process is completed, the control unit 102 adds new "Transfer" transaction data with bond log ID 25720 to the bond transaction data 14.

[0042] Figure 10 illustrates an example of a case where a claim cannot be identified during individual allocation processing. The candidate allocation data 13 shown in Figure 10, like the example shown in Figure 6, retrieves candidate customer names with the same kana customer name but different kanji characters, such as "Tenkomi Jiro" and "Tenkomi Jiro." The deposit displayed on the deposit reconciliation input screen W3 is from "Tenkomi Jiro" with deposit ID 151. In this case, if the user checks "Tenkomi Jiro" but is unable to determine the appropriate recipient for the deposit with deposit ID 151, the appropriate recipient will not be determined. In this case, the user can simply press the "Non-claim" button without selecting the claim shown as an allocation candidate. The control unit 102 then activates the input field for entering the details of the non-claim, based on the user's input. The user then enters the allocation date, allocation amount, non-claim reason, remarks, and other information into the input field and presses the "Execute" button. When the user makes such an input (step S113), the control unit 102 performs non-invoice processing for the deposit with deposit ID 151, without selecting a claim and marking the deposit as processed without specifying the claim (step S114). In the non-invoice processing, the control unit 102 adds the deposit with deposit ID 151 in the deposit data 11 to the deposit allocation data 15, as shown in FIG. 10. In this case, the control unit 102 erases the claim log ID and reflects the contents of the above-mentioned "non-invoice reason" and "remarks" as the items "non-invoice allocation free code" and "remarks".

[0043] <Confirming the processing results> When the above-mentioned lump-sum allocation process (step S105), individual allocation process (step S108), or non-invoice process (step S114) has been performed, or when none of the processes has been performed (No in step S113), the user can check the processing results by displaying a screen on the monitor 114. When the user inputs an instruction to display the processing results on the monitor 114 (Yes in step S115), the control unit 102 displays the processing results on the monitor 114 in accordance with the input (step S116). The determination in step S115 and the processing in step S116 may be performed as separate processes from the above-mentioned steps S101 to S114.

[0044] FIG. 11 is a diagram showing an example of a screen for confirming the processing results. In the example shown in FIG. 11, the processing results can be confirmed by displaying the deposit reconciliation list screen W2 and the receivables list screen W4. By performing a search on the deposit reconciliation list screen W2 with "Include no balance" unchecked, it can be confirmed that there are no unprocessed deposit balances remaining. The example shown in FIG. 11 shows a case where no matching deposits exist when a search is performed with "Include no balance" unchecked.

[0045] Also, by searching on the bond list screen W4 with "balance 0 yen" and "deposit exists (1 yen or more)", it is possible to confirm that there is no remaining balance to be refunded for the deposit. The example shown in Figure 11 shows a case where a search is performed with "balance 0 yen" and "deposit exists (1 yen or more)" and no corresponding bond exists.

[0046] Figure 12 is a diagram showing another example of a screen for checking processing results. As shown in Figure 12, on the deposit reconciliation list screen W2, by searching using conditions such as date, it is possible to check past processing at any time. The example shown in Figure 12 shows a case where a search is performed using August 20, 2023 as the deposit date, and the corresponding deposits are displayed.

[0047] Additionally, by selecting a deposit ID 152 on the deposit reconciliation list screen W2 in Figure 12, the deposit reconciliation input screen W3 can be opened for the deposit with that deposit ID 152. The deposit reconciliation input screen W3 is in inquiry mode, and is set up so that new input and updates to each piece of information cannot be made. By checking the allocation history on the deposit reconciliation input screen W3, the processing details can be confirmed.

[0048] <Checking past processing details> FIG. 13 is a diagram showing another example of a screen for confirming processing results. As shown in FIG. 13, by selecting a search result on the bond list screen W4, the bond portal screen W6 can be opened. The bond portal screen W6 displays information such as customer information (customer name), bond information (bond ID, bond balance, deposit), and transaction history (bond log ID, transaction details, transaction date, transaction amount, bond balance, deposit). The control unit 102 references the bond transaction data 14 and displays the information on the bond portal screen W6. By checking the transaction history, it is possible to confirm that the deposit has been transferred.

[0049] After the processing results are displayed on the monitor 114, if no input is made to display the processing results on the monitor 114 (No in step S115), the processing can be completed by inputting completion of the processing.

[0050] As described above, the deposit management device 100 according to this embodiment is a deposit management device 100 equipped with a control unit 102, and the control unit 102 acquires the deposit file 10 showing information on deposits from a plurality of debtors and the credit data 12 showing the correspondence between the debtors and the debtors' credits, searches for credits to which the deposits should be allocated for each deposit in the deposit file 10, and when a credit to which the deposits should be allocated is identified, performs allocation processing in a batch process to allocate the deposits to the identified credits, and when there is an unallocated deposit, which is a deposit for which a credit to which the deposits should be allocated is not identified in the allocation processing, the unallocated deposit is Deposit information is output, and if an input is made to determine the appropriated receivable individually for the outputted unallocated deposit, information on receivables that are candidates for appropriation for the inputted unallocated deposit, which is the target unallocated deposit, is extracted and output based on receivables data 12, and if an input is made to the effect that the appropriated receivable has been specified for the target unallocated deposit, an individual appropriation process is performed to allocate the target unallocated deposit to the specified receivable, and if an input is made to the effect that the appropriated receivable has not been specified for the target unallocated deposit, an unclaimed process is performed to treat the target unallocated deposit as having been processed without specifying the receivable.

[0051] Furthermore, the deposit management method according to this embodiment is a deposit management method executed by a deposit management device 100 equipped with a control unit 102, and includes the steps of: acquiring a deposit file 10 showing information on deposits from a plurality of debtors and claim data 12 showing the correspondence between debtors and the debtors' claims; searching for a claim to which the deposit should be allocated for each deposit in the deposit file 10; and, if a claim to which the deposit should be allocated is identified, performing an allocation process in a batch process to allocate the deposit to the identified claim; and, if there is an unallocated deposit, which is a deposit for which a claim to which the deposit should be allocated is not identified in the allocation process, outputting information about the unallocated deposit. If an input is made to determine the appropriate receivable individually for the output unallocated deposit, the control unit 102 performs the following steps: extracting and outputting information on receivables that are candidates for allocation for the input unallocated deposit, which is the target unallocated deposit, based on the receivables data 12; if an input is made to indicate that an appropriate receivable has been identified for the target unallocated deposit, performing individual allocation processing to allocate the target unallocated deposit to the identified receivable; and if an input is made to indicate that an appropriate receivable has not been identified for the target unallocated deposit, performing non-claim processing to mark the target unallocated deposit as processed without identifying the receivable.

[0052] Furthermore, the deposit management program according to this embodiment is a deposit management program executed by a deposit management device 100 equipped with a control unit 102, and acquires a deposit file 10 showing information on deposits from multiple debtors and credit data 12 showing the correspondence between debtors and the debtors' credits, searches for credits to which the deposits should be allocated for each deposit in the deposit file 10, and when a credit to which the deposits should be allocated is identified, performs an allocation process in a batch process to allocate the deposits to the identified credits, and when there is an unallocated deposit, which is a deposit for which a credit to which the deposits should be allocated is not identified in the allocation process ... unallocated deposits. The control unit 102 executes the following processes: a process to output information on the above; a process to extract and output, based on the claims data 12, information on claims that are candidates for allocation to the target unallocated deposit, which is the unallocated deposit for which the input was made, if an input is made to determine the claim to which the output unallocated deposit should be allocated individually; a process to allocate the target unallocated deposit to the identified claim, if an input is made to indicate that the claim to which the target unallocated deposit should be allocated has been specified; and a process to mark the target unallocated deposit as processed without specifying a claim, if an input is made to indicate that the claim to which the target unallocated deposit should be allocated has not been specified.

[0053] According to this embodiment, even if there is an unallocated deposit, which is a deposit for which no receivable to be allocated has been identified during the allocation process, the control unit 102 can search for potential allocation destinations and output the search results, and the output results can be used to perform individual allocation processing and non-invoice processing, thereby reducing the workload of managing deposits and the risk of input errors, etc.

[0054] In the deposit management device 100 according to this embodiment, when the amount of a target unallocated deposit that has undergone individual allocation processing does not match the amount of the claim, and there is a balance in the claim amount as a result of allocating the target unallocated deposit to the claim, the control unit 102 applies the excess or shortfall in the amount of the deposit to the next allocation processing. With this configuration, when the amount of the deposit does not match the amount of the claim, an addition or deduction can be made at the time of the next or subsequent claim invoice, enabling efficient processing.

[0055] In the deposit management device 100 according to this embodiment, when the deposit amount and the claim amount of the unallocated deposit that has undergone individual allocation processing do not match, and when there is no remaining claim amount as a result of allocating the unallocated deposit to the claim, and a deposit is generated, the control unit 102 performs processing to refund the deposit. With this configuration, the excess amount deposited can be appropriately refunded as a deposit.

[0056] In the deposit management apparatus 100 according to this embodiment, the control unit 102 outputs information relating to the refundable balance of the deposit. With this configuration, it is possible to easily check information relating to the marginal balance of the deposit.

[0057] In the deposit management apparatus 100 according to this embodiment, the control unit 102 outputs the past processing details regarding deposits. With this configuration, the past processing details regarding deposits can be easily confirmed.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0072] The present invention is particularly useful in managing payments for loans, credit, leases, and the like. [Explanation of symbols]

[0073] W1 Mass Deposit Reconciliation Input Screen W2 Payment Reconciliation List Screen W3 Payment Reconciliation Input Screen W4 Debt List Screen W5 Deposit Transfer Screen W6 Bond Portal Screen 10 Deposit File 11 Deposit data 12 Bond Data 13. Data on potential allocations 14 Bond trading data 15. Deposit Allocation Data 16 Screen creation data 17 Name Matching Master 100 Deposit management device 102,103 Control unit 104 Communication interface unit 106 Storage section 108 Input / Output Interface Section 112 Input devices, keyboards, mice 114 Output Device, Monitor 200 servers 300 Network

Claims

1. A deposit management device having a control unit, The control unit Acquires a deposit file showing information on deposits from a plurality of debtors and credit data showing the correspondence between the debtors and the credits of the debtors, searches for the credits to which each of the deposits in the deposit file should be allocated, and when the credits to which each of the deposits should be allocated are identified, performs allocation processing in a batch process to allocate the deposits to the identified credits, If there is an unallocated deposit, which is the deposit for which the credit to be allocated has not been identified in the allocation process, output information about the unallocated deposit; When an input is made to determine the credits to which the unallocated deposit is to be allocated individually for the output unallocated deposit, information on the credits that are candidates for allocation for the input unallocated deposit, which is the target unallocated deposit, is extracted based on the credit data and output; When an input is made indicating that the receivable to which the unallocated deposit is to be allocated has been specified, an individual allocation process is carried out to allocate the unallocated deposit to the specified receivable, If an input is made to the effect that the credit to which the unallocated payment is to be allocated is not specified, non-invoice processing is performed to treat the unallocated payment as processed without specifying the credit. Deposit management device.

2. The control unit performs processing to apply the excess or shortfall of the deposit amount to the next allocation processing when the deposit amount and the claim amount of the claim do not match for the unallocated deposit for which the individual allocation processing has been performed, and if there is a balance in the claim amount of the claim as a result of allocating the unallocated deposit to the claim. The deposit management device according to claim 1.

3. The control unit, in the case where the amount of the unallocated deposit for which the individual allocation process has been performed does not match the amount of the claim for the claim, and as a result of allocating the unallocated deposit to the claim, there is no remaining balance for the claim amount and a deposit is generated, performs a process to refund the deposit. The deposit management device according to claim 1.

4. The control unit outputs information regarding the refund balance of the deposit. The deposit management device according to claim 3.

5. The control unit outputs past processing details regarding the deposit. The deposit management device according to claim 1.

6. A deposit management method executed by a deposit management device having a control unit, a step of acquiring a deposit file showing information on deposits from a plurality of debtors and credit data showing the correspondence between the debtors and the credits of the debtors, searching for the credit to which each of the deposits in the deposit file should be allocated, and when the credit to which each of the deposits should be allocated is identified, performing an allocation process in which the deposits are allocated to the identified credits in a batch process in a lump sum; If there is an unallocated deposit, which is the deposit for which the credit to be allocated has not been identified in the allocation process, outputting information about the unallocated deposit; When an input is made to determine the credits to which the unallocated deposit is to be allocated individually for the output unallocated deposit, extracting and outputting information on the credits that are candidates for allocation for the input unallocated deposit, which is the target unallocated deposit, based on the credit data; When an input is made indicating that the receivable to which the target unallocated deposit is to be allocated has been specified, a step of performing an individual allocation process to allocate the target unallocated deposit to the specified receivable; When an input is made indicating that the receivable to which the target unallocated deposit is to be allocated is not specified, a step of performing non-invoice processing to mark the target unallocated deposit as processed without specifying the receivable; A deposit management method in which the control unit performs the above.

7. A deposit management program to be executed by a deposit management device having a control unit, a process of acquiring a deposit file showing information on deposits from a plurality of debtors and credit data showing the correspondence between said debtors and their credits, searching for the credit to which each of said deposits in said deposit file should be allocated, and when the credit to which each of said deposits should be allocated is identified, performing an allocation process in a batch process to allocate said deposits to the identified credits; If there is an unallocated deposit, which is the deposit for which the credit to be allocated has not been identified in the allocation process, a process of outputting information about the unallocated deposit; When an input is made to determine the credits to which the unallocated deposit is to be allocated individually for the output unallocated deposit, a process is performed to extract and output information on the credits that are candidates for allocation for the input unallocated deposit, which is the target unallocated deposit, based on the credit data; When an input is made indicating that the receivable to which the unallocated deposit is to be allocated has been specified, a process of allocating the unallocated deposit to the specified receivable; If an input is made indicating that the receivable to be allocated to the unallocated deposit is not specified, the unallocated deposit is processed without specifying the receivable. A deposit management program that causes the control unit to execute the above.

Images