JP2020166614A - Deposit transfer device, deposit transfer method, and deposit transfer program - Google Patents

Abstract

To provide a deposit transfer device, a deposit transfer method, and a deposit transfer program that can appropriately transfer deposits to each branch even when debt collection from a company having a plurality of branches is performed collectively from a representative branch.SOLUTION: A deposit transfer device includes: deposit processing means that inputs a billing destination master registered by associating a billing destination with a deposit billing destination and deposit data including the billing destination, a deposit date, and a deposit amount; and deposit transfer processing means that acquires, with reference to the billing destination master, a billing destination whose deposit billing destination is a billing destination of the deposit data, acquires billing data for a scheduled collection date within a predetermined business day before and after the deposit date among the acquired billing data of the billing destination, and performs, when the billing destination for the deposit data and the billing destination for the acquired billing data are different, a deposit transfer.SELECTED DRAWING: Figure 2

Description

The present invention relates to a deposit transfer device, a deposit transfer method, and a deposit transfer program.

Conventionally, as a system for transferring deposits, for example, there is Patent Document 1. In the system of Patent Document 1, a client in which the date, amount, and billing address of the payment slip are input, a closing control table that stores accounting closing classification information and credit closing classification information for each year and month, and a year and month. A database server that has a deposit business calendar table that stores the deposit business available date for each, receives the date of the deposit slip entered from the client, instructs the database server, and the date of the entered deposit slip is the claim closing classification. It is determined that the closing status is shown as the information of the closing status and the unclosing status is shown as the information of the accounting closing classification, it is judged that the date of the entered payment slip is the deposit business available date, and the amount of the entered deposit slip is Has an application server that executes balance update processing in.

Japanese Unexamined Patent Publication No. 2016-151943

However, Patent Document 1 does not describe anything about the case where debt collection from a company having a plurality of branches is collectively performed from a representative branch.

The present invention has been made in view of the above, and is a deposit transfer device and deposit transfer capable of appropriately transferring deposits to each branch even when debt collection from a company having a plurality of branches is collectively performed from a representative branch. The purpose is to provide a method and a deposit transfer program.

In order to solve the above-mentioned problems and achieve the object, the present invention is a deposit transfer device including a storage unit and a control unit, and the storage unit is a request registered by associating a billing destination and a payment billing destination. The destination master, the billing destination, the scheduled collection date, and the billing data including the billing amount are stored, and the control unit serves as a deposit processing means for inputting the deposit data including the billing destination, the deposit date, and the deposit amount. , With reference to the billing destination master, acquire a billing destination whose payment billing destination is the billing destination of the payment data, and among the billing data of the acquired billing destination, the scheduled collection date within a predetermined business day before and after the payment date. When the billing data is acquired and the billing destination of the received billing data is different from the billing destination of the acquired billing data, it is characterized by providing a deposit transfer processing means for performing the deposit transfer.

Further, according to a preferred embodiment of the present invention, the storage unit stores a fee master in which a bank transfer fee is registered, and the deposit transfer processing means includes the total billing amount of the acquired billing data and the billing amount. If there is a miscalculation in the deposit amount and the miscalculation matches the fee of the fee master, the deposit may be transferred.

Further, according to a preferred embodiment of the present invention, the deposit transfer processing means determines to perform the deposit transfer according to the operation of the operator when there is a discrepancy between the total billing amount of the acquired billing data and the deposit amount. May be good.

Further, in order to solve the above-mentioned problems and achieve the object, the present invention is a deposit transfer method executed by an information processing device including a control unit and a storage unit, and the storage unit is billed. The billing destination master registered in association with the billing destination, and the billing data including the billing destination, the scheduled collection date, and the billing amount are stored, and the billing destination, the payment date, and the billing date executed by the control unit are stored. With reference to the deposit processing step for inputting the deposit data including the deposit amount and the billing destination master, the billing destination with the billing destination of the deposit data as the deposit billing destination is acquired, and among the billing data of the acquired billing destination, If the billing data for the scheduled collection date within the specified business days before and after the deposit date is acquired and the billing destination for the deposit data and the billing destination for the acquired billing data are different, the deposit transfer processing step for performing the deposit transfer and the deposit transfer processing step.
It is characterized by including.

Further, in order to solve the above-mentioned problems and achieve the object, the present invention is a deposit transfer program for causing an information processing device including a control unit and a storage unit to execute a payment transfer program, and the storage unit is charged. The billing destination master registered by associating the destination with the payment billing destination, and the billing data including the billing destination, the scheduled collection date, and the billing amount are stored, and the billing destination, the payment date, and the deposit amount are stored in the control unit. With reference to the deposit processing step for inputting the deposit data including the above and the billing address master, the billing address with the billing destination of the deposit data as the deposit billing destination is acquired, and among the billing data of the acquired billing destination, the deposit date If the billing data for the scheduled collection date within the specified business days before and after is acquired and the billing destination for the deposit data is different from the billing destination for the acquired billing data, the deposit transfer processing step for performing the deposit transfer and the execution of It is characterized by being a deposit transfer program.

According to the present invention, even when debt collection from a company having a plurality of branches is collectively performed from a representative branch, it is possible to appropriately transfer the deposit to each branch.

FIG. 1 is a diagram for explaining a processing image of the present embodiment. FIG. 2 is a block diagram showing an example of the configuration of the deposit transfer device 100 according to the present embodiment. FIG. 3 is a diagram showing a configuration example of the billing destination master. FIG. 4 is a diagram showing a configuration example of a bank fee master. FIG. 5 is a flowchart for explaining an example of the entire processing of the deposit transfer device according to the present embodiment. FIG. 6 is a flowchart for explaining a detailed process of the deposit transfer process. FIG. 7 is a diagram showing an example of a deposit transfer screen. FIG. 8 is a diagram showing sample data for explaining the specific example 1. FIG. 9 is a diagram showing sample data for explaining the second embodiment. FIG. 10 is a diagram showing sample data for explaining the specific example 3.

Hereinafter, the deposit transfer device, the deposit transfer method, and the embodiment of the deposit transfer program according to the present invention will be described in detail with reference to the drawings. The present invention is not limited to this embodiment.

[1. Overview]
For example, when dealing with a company that has multiple branches, there are many patterns in which the actual deposit is made by the representative customer. In the case of such a pattern, it is possible to carry out the application process by setting the payment billing destination with the function of the conventional sales system, but if the person in charge is divided for each business partner (branch office), the application process is 1 It is possible that it will not be completed by human operations.

More specifically, even with the conventional function, it was possible to apply the claims of each branch (base) from the actual deposit destination on a deposit slip basis, but the person in charge was different for each branch and fees and miscalculations occurred. At that time, the operation was troublesome. In the case of a large company, the person in charge is often different for each branch even if it is the same corporation, and when a miscalculation occurs, the person in charge handles it, so it was difficult for the company to control it.

Therefore, in this embodiment, it is possible to collate with the receivable amount of each business partner at the time of recording the payment data, distribute the payment amount to each business partner at the timing of data creation, and perform the application processing by each person in charge. did.

More specifically, in this embodiment, even when debt collection from a company having multiple branches is collectively performed from the representative branch, the application processing can be performed for each branch, and (1) actual payment. Calculate the transfer amount from the claim of the billing destination linked first to each billing destination, (2) At this time, considering that there are fees and miscalculations, manual transfer processing is also possible, (3) After that, based on the transferred amount, the payment application process can be performed for each person in charge at each branch, and the burden on the person in charge of application can be distributed.

FIG. 1 is a diagram for explaining a processing image of the present embodiment. The person in charge at each site records the sales and inputs the sales (P1). Next, billing is performed on the recorded sales (P2). The accounting department inputs the deposit information and processes the deposit (P3). The accounting department performs payment transfer processing based on the billing information (P4). Based on the transferred information, each business partner person in charge performs payment application input processing for each billing destination (business partner) in the payment transfer processing (P5).

[2. Constitution]
The configuration of the deposit transfer device 100 according to the present embodiment will be described with reference to FIG. FIG. 2 is a block diagram showing an example of the configuration of the deposit transfer device 100 according to the present embodiment.

The deposit transfer device 100 is a commercially available desktop personal computer. The deposit transfer device 100 is not limited to a stationary information processing device such as a desktop personal computer, but is a portable type such as a commercially available notebook personal computer, a PDA (Personal Digital Assistants), a smartphone, or a tablet personal computer. It may be an information processing device.

As shown in FIG. 2, the deposit transfer device 100 includes a control unit 102, a communication interface unit 104, a storage unit 106, and an input / output interface unit 108. Each part of the deposit transfer device 100 is communicably connected via an arbitrary communication path.

The communication interface unit 104 connects the deposit transfer device 100 to the network 300 in a communicable manner 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 another device via a communication line. Here, the network 300 has a function of connecting the deposit transfer device 100, the server 200, and the terminal device 400 of each branch or accounting department so as to be able to communicate with each other. For example, the Internet or LAN (Local Area) Network) and the like. The data stored in the storage unit 106, which will be described later, may be stored in the server.

An input device 112 and an output device 114 are connected to the input / output interface unit 108. As the output device 114, a speaker or a printer can be used in addition to a monitor (including a home television). In addition to the keyboard, mouse, and microphone, the input device 112 can use a monitor that cooperates with the mouse to realize the pointing device function. In the following, the output device 114 may be referred to as a monitor 114, and the input device 112 may be referred to as a keyboard 112 or a mouse 112. Further, the user displaying on the screen of the output device (monitor) 114 and operating the input device 112 may be described as "user operation via UI".

Various databases, tables, files, and the like are stored in the storage unit 106. In the storage unit 106, a computer program for giving a command to a CPU (Central Processing Unit) in cooperation with an OS (Operating System) to perform various processes is recorded. As the storage unit 106, 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, or the like can be used.

The storage unit 106 stores the billing destination master 106a, the bank fee master 106b, the billing data file 106c, the deposit data file 106d, the deposit application data file 106e, and the like. FIG. 3 is a diagram showing a configuration example of the billing destination master 106a. FIG. 4 is a diagram showing a configuration example of the bank fee master 106b.

The billing destination master 106a is a master for associating a billing destination with a deposit billing destination for making a deposit. For example, when the head office collectively deposits the claims of each branch, the billing destination is the head office and each branch is the billing destination.

As shown in FIG. 3, the billing destination master 106a can be composed of a billing destination code, a billing destination name, a payment billing destination code, a table registered in association with the fee burden classification, and the like.

The bank fee master 106b is a master for storing the fee of the bank to be used. As shown in FIG. 4, the bank fee master 106b can be composed of a table or the like in which transfer fees are registered. When using multiple banks, fees may be registered for each bank.

The billing data file 106c is a file for storing billing data. The billing data may include data on the billing code, billing name, scheduled collection date, previous billing amount, deposit amount, sales amount, current billing amount, and applied amount.

The deposit data file 106d is a file for storing the deposit data. The deposit data may include data on the deposit number, billing code, billing name, deposit date, deposit category, deposit amount, application source amount, and application amount.

The deposit application data file 106e is a file for storing the deposit application data. The deposit application data may include data on the deposit application number, the deposit number, the billing code, the deposit application date, and the deposit application amount.

Returning to FIG. 2, the control unit 102 is a CPU or the like that collectively controls the deposit transfer device 100. The control unit 102 has an internal memory for storing a control program such as an OS, a program that defines various processing procedures, required data, and the like, and performs various information processing based on these stored programs. Execute. The control unit 102 conceptually includes a billing processing unit 102a, a deposit processing unit 102b, a deposit transfer processing unit 102c, an application processing unit 102d, a master maintenance unit 102e, and a screen display control unit 102f.

The billing processing unit 102a creates billing data based on the sales recording and stores it in the billing data file 106c. In addition, the billing processing unit 102a may output (issue) an invoice based on the billing data.

The deposit processing unit 102b creates deposit data and stores it in the deposit data file 106d when there is a deposit from the billing destination (customer).

The deposit transfer processing unit 102c refers to the billing destination master 106a to acquire a billing destination whose payment billing destination is the billing destination of the deposit data, and among the billing data of the acquired billing destination, a predetermined business day before and after the payment date. If the billing data for the scheduled collection date within the period is acquired and the billing destination for the payment data and the billing destination for the acquired billing data are different, the payment is transferred.

In addition, the deposit transfer processing unit 102c decides to transfer the deposit if there is a difference between the total billed amount of the acquired billing data and the deposit amount and the miscalculation matches the fee of the bank charge master 106b. You may.

Further, the deposit transfer processing unit 102c may perform the deposit transfer according to the operation of the operator when there is a discrepancy between the total billing amount of the acquired billing data and the deposit amount.

The application processing unit 102d performs a deposit application process to apply the current billing amount and the deposit amount of the billing data.

The master maintenance unit 102e edits, for example, input / change / add data of the billing destination master 106a and the bank fee master 106b in response to an operator's operation on a master maintenance screen (not shown) displayed on the monitor 114. I do.

The screen display control unit 102f controls the display and input of various screens (for example, a deposit transfer screen and the like) displayed on the monitor 114.

[3. Specific example of processing]
A specific example of the processing of the control unit 102 of the deposit transfer device 100 in the present embodiment will be described with reference to FIGS. 2 to 10. First, with reference to FIGS. 5 and 6, the outline of the entire processing of the deposit transfer device 100 in the present embodiment will be described. FIG. 5 is a flowchart for explaining an example of the entire processing of the deposit transfer device 100 according to the present embodiment. FIG. 6 is a flowchart for explaining a detailed process of the deposit transfer process. FIG. 7 is a diagram showing an example of a deposit transfer screen. FIG. 8 is a diagram showing sample data for explaining the specific example 1. FIG. 9 is a diagram showing sample data for explaining the second embodiment. FIG. 10 is a diagram showing sample data for explaining the specific example 3.

In FIG. 5, the billing processing unit 102a executes the billing processing (step S1). In the billing process, billing data may be created, stored in the billing data file 106c, and an invoice based on the billing data may be output (issued).

The deposit processing unit 102b executes the deposit input process (step S2). In the deposit input process, when there is a deposit from a business partner, deposit data is created and stored in the deposit data file 106d.

The deposit transfer processing unit 102c executes the deposit transfer processing (step S3). In the deposit transfer process, the billing destination master 106a is referred to to acquire a billing destination whose payment billing destination is the billing destination of the deposit data, and among the billing data of the acquired billing destination, within a predetermined business day before and after the payment date. The billing data of the scheduled collection date is acquired, and if the billing destination of the deposit data and the billing destination of the acquired billing data are different, the deposit transfer is performed.

The application processing unit 102d executes the payment application input process (step S4). In the deposit application process, the deposit application data is created and stored in the deposit application data file 106e, and the billing data and the deposit data are updated.

Next, the detailed processing of the deposit transfer processing will be described with reference to FIG. In FIG. 6, using the billing address of the deposit data as a key, the deposit billing address code is acquired from the billing address master 106a (step S10), and the billing address code associated with the deposit billing address code acquired from the billing address master 106a is further obtained. Acquire (step S11). Of the billing data (unapplied) of the acquired billing address code, the billing data of the scheduled collection date is acquired within a predetermined business day (for example, 3 business days before and after) before and after the payment date (step S12).

It is determined whether the total of the deposit amount of the deposit data and the billing amount of the billing data match (step S13), and if they match (“Yes” in step S13), the billing destination of the deposit data and the collection schedule (billing data) If the billing address is different, the deposit is transferred to a different billing address (step S14). If they do not match (“No” in step S13), it is determined whether or not the fee burden classification of the billing destination master 106a is “self-pay” (step S15). If it is not "own expense" ("No" in step S15), the process proceeds to step S17. If it is "own expense" ("Yes" in step S15), it is determined whether or not the difference and the fee of the bank fee master 106b match (step S16), and if they match (step S16 "Yes"). Yes ”), transfer the deposit (step S14). If they do not match (“No” in step S16), the process proceeds to step S17. In step S17, the deposit is transferred according to the operation of the operator. As will be described later, for example, the operator sets the transfer amount for each billing destination on the deposit transfer screen, and performs the deposit transfer according to the set contents.

FIG. 7 is a diagram showing an example of a deposit transfer screen for confirmation of an operator when performing a deposit transfer process. FIG. 7A shows the main screen, and when the deposit number is input, the corresponding deposit data and the transfer amount of the billing destination are displayed. If there is a difference (except when it matches the fee), the transfer amount will not be displayed. When a billing address is selected on the main screen, a detail input screen as shown in FIGS. 7 (B) to 7 (D) is displayed. On this detail input screen, the operator can input and change the transfer amount. For example, when there is a difference (Specific Example 3), the operator sets the transfer amount of the billing destination on the deposit transfer screen. In this case, the deposit transfer processing unit 102c may perform the transfer according to the contents set on the deposit transfer screen.

[Specific example 1]
Specific Example 1 will be described with reference to FIG. FIG. 8 is a diagram for explaining the specific example 1. In Specific Example 1, a pattern in which transfer is possible without causing a difference will be described.

FIG. 8A shows an example of data of the billing destination master 106a. In the example of the billing destination master 106a shown in FIG. 8A, the first line is the billing destination code "070320201", the billing destination name "△△ Headquarters Co., Ltd.", and the deposit billing destination code "070320201", the second line. However, the billing address code "070320301", the billing address name "△△ Osaka Branch", and the deposit billing address code "070320201", the third line is the billing address code "070320401", the billing address name "△△ Co., Ltd. △△" "Fukuoka branch" and the payment billing code "070320201". In this example, the "head office" is the payment request destination.

(S1: Billing process)
FIG. 8B shows an example of billing data. In the example of billing data shown in FIG. 8 (B), the first line is the billing address code "070320201", the billing address name "△△ Headquarters Co., Ltd.", the scheduled collection date "2018/03/15", and the previous billing amount. "0", deposit amount "0", sales amount "350,000", this time billing amount "350,000", and applied amount "0", the second line is billing code "070320301", billing destination Name "△△ Osaka Branch", scheduled collection date "2018/03/15", previous billing amount "0", deposit amount "0", sales amount "250,000", current billing amount "250,000" , And the applied amount "0", the third line is the billing address code "070320401", the billing address name "△△ Fukuoka Branch Co., Ltd.", the scheduled collection date "2018/03/15", the previous billing amount "0" , The deposit amount is "0", the sales amount is "400,000", the billing amount is "400,000", and the applied amount is "0".

(S2: Deposit processing)
FIG. 8C shows an example of deposit data. In the example of the deposit data shown in FIG. 8C, the deposit number "NY00000001", the billing address code "070320201", the billing address name "△△ Headquarters Co., Ltd.", the deposit date "2018/03/13", and the deposit category " 3: "Transfer", deposit amount "1,000,000", application source amount "1,000,000", and application amount "0". In this example, the case where the head office makes a collective deposit is shown.

(S3: Deposit transfer processing)
FIG. 8D is a diagram for explaining a deposit transfer process for deposit data. Using the deposit data billing address "070320201 (△△ Headquarters Co., Ltd.)" as a key, the deposit billing address code "070320201" is acquired from the billing address master 106a, and the billing address code linked to the deposit billing address code "070320201". Acquire "070320201", "070320301", and "070320401". Of the billing data (unapplied) of the acquired billing code "070320201", "070320301", and "070320401", the data of the scheduled collection date within the predetermined business days (for example, 3 business days before and after) before and after the payment date (for example, 3 business days before and after) 1 to 3 lines) are acquired. The predetermined business day can be set arbitrarily.

Since the deposit amount of the deposit data "1,000,000" and the total billing amount of the billing data "1,000,000" match, the transfer process is performed. At this time, since there is data in which the billing destination of the payment data and the billing destination of the collection schedule (billing data) are different, the payment data of the transfer is generated.

As shown in FIG. 8 (D), for the deposit number "NY00000001" on the first line, the deposit category "9: transfer" is added, and the deposit amounts "-350,000", "-250,000", "-" Add "400,000". Furthermore, on the second line, the deposit number "NY00000002", the billing address code "070320201", the billing address name "△△ Headquarters Co., Ltd.", the deposit date "2018/03/13", the deposit category "9: transfer", the deposit Amount "350,000", application resource amount "350,000", deposit number "NY0000003", billing code "070320301", billing name "△△ Osaka Branch", deposit date "2018/03/13", deposit category "9: transfer", deposit amount "250,000", application source amount "250,000", deposit number "NY0000004", billing address code on the 4th line "070320401", billing address "△△ Fukuoka Branch", deposit date "2018/03/13", deposit category "9: transfer", deposit amount "400,000", application source amount "400,000" "Is added.

(S4: Payment application input processing)
FIG. 8E shows an example of payment application data. In the example of the deposit application data shown in FIG. 8 (E), the first line is the deposit application number "NK0000001", the deposit number "NY00000001", the billing code "070320201", and the deposit application date "2018/03/03 /". 15 ”, deposit application amount“ 350,000 ”, second line is deposit application number“ NK00002 ”, deposit number“ NY0000002 ”, billing code“ 070320301 ”, deposit application date“ 2018/03/18 ” , Deposit application amount "250,000", 3rd line is deposit application number "NK0000003", deposit number "NY0000003", billing code "070320401", deposit application date "2018/03/20", deposit The application amount is "400,000".

As shown in FIG. 8 (F), the "applied amount" of the billing data is updated, and the first to third lines are changed to the applied amounts of "350,000", "250,000", and "400,000". Update each. Further, as shown in FIG. 8 (G), the "applied amount" of the deposit data is updated, and the applied amounts "350,000", "250,000" and "400,000" are displayed on the 2nd to 4th lines. Update to each.

(Specific example 2)
Specific Example 2 will be described with reference to FIG. FIG. 9 is a diagram for explaining a specific example 2. In Specific Example 2, since the difference matches the fee, a pattern that can be transferred will be described.

In FIG. 9, the description of the parts common to FIG. 8 will be omitted, and the differences will be described. As shown in FIG. 9A, the billing master 106a has the fee burden category set to “own burden”.

(S1: Billing process)
The billing data shown in FIG. 9B is the same as that in FIG. 8B.

(S2: Deposit input processing)
As shown in FIG. 9C, the deposit data includes the deposit number "NY00000001", the billing address code "070320201", the billing address name "△△ Headquarters Co., Ltd.", the deposit date "2018/03/13", and the deposit category "2018/03/13". 3: "Transfer", deposit amount "999,676", application source amount "999,676", and application amount "0".

(S3: Deposit transfer processing)
The acquisition of the target billing data is the same as in Specific Example 1 (FIG. 8). Although the deposit amount "999,676" of the deposit data and the total billing amount "1,000,000" of the billing data do not match, it is a transfer slip and the transfer fee of the billing master 106a is borne by the company. Therefore, the bank fee master 106b is referred to, the fee is acquired, and it is checked whether the difference matches the fee.

FIG. 9D shows an example of data of the bank charge master 106b, and in the example shown in the figure, “108”, “216”, and “324” are set as the transfer fee.

Compare the total amount of the deposit amount "¥ 999,676" and the acquired transfer fee with the total amount of the current billing amount "1,000,000" of the billing data. In the case of the transfer fee "108", it is ¥ 999,676 + ¥ 108 = ¥ 999,784, which is a mismatch.

In the case of the transfer fee "216", it is ¥ 999,676 + ¥ 216 = ¥ 999,892, which is a mismatch. In the case of the transfer fee "324", it is ¥ 999,676 + ¥ 324 = ¥ 1,000,000, which is the same. Since there is data in which the billing destination of the deposit data and the billing destination of the collection schedule (billing data) are different, the deposit data of the transfer is generated.

In the deposit data shown in FIG. 9 (E), the deposit number "NY00000001" in the first line is set to the deposit amount "-349,676" in "9: Transfer" in the second line of the deposit category. Other than that, it is the same as in FIG. 8 (D).

(S4: Payment application input processing)
The creation of the deposit application data shown in FIG. 9 (F), the update of the billing data shown in FIG. 9 (G) and the update of the deposit data shown in FIG. 9 (H) are the same as those in FIGS. 8 (E) to 8 (G). ..

(Specific example 3)
Specific Example 3 will be described with reference to FIG. FIG. 10 is a diagram for explaining a specific example 3. In Specific Example 3, a pattern in which a difference occurs will be described.

In FIG. 10, the description of the parts common to FIG. 8 will be omitted, and the differences will be described. The data example of the billing destination master 106a shown in FIG. 10A is the same as that in FIG. 8A.

(S1: Billing process)
The data example of the billing data shown in FIG. 10B is the same as that in FIG. 8B.

(S2: Deposit input processing)
In the example of the deposit data shown in FIG. 10C, the deposit number "NY00000001", the billing address code "070320201", the billing address name "△△ Headquarters", the deposit date "2018/03/13", and the deposit category " 3: "Transfer", deposit amount "900,000", application source amount "900,000", and application amount "0".

(S3: Deposit transfer processing)
The acquisition of the target billing data is the same as in Specific Example 1 (FIG. 8). Since the deposit amount "900,000" of the deposit data and the total billing amount "1,000,000" of the billing data do not match, the transfer amount is not calculated automatically and the user side uses the above-mentioned deposit transfer. The transfer amount is set on the screen (Fig. 7), and the deposit transfer set by the user is performed. For example, with respect to the billing party in which a miscalculation has occurred, after confirming with the business partner, partial clearing or miscalculation adjustment processing is performed.

Here, a case where partial application is performed will be described. In the example shown in FIG. 10D, the deposit amount "900,000" is assigned to the billing address codes "070320201" and "070320301" and the billing address code "070320401", respectively, to "350,000 (total billing amount)". , "250,000 (total billed amount)", "300,000 (part of billed amount)" are sorted.

As described above, according to the present embodiment, the billing destination master 106a registered by associating the billing destination and the deposit billing destination, and the deposit processing unit for inputting the deposit data including the billing destination, the deposit date, and the deposit amount. With reference to 102b and the billing destination master 106a, a billing destination whose payment destination is the billing destination of the payment data is acquired, and among the billing data of the acquired billing destination, collection is scheduled within a predetermined business day before and after the payment date. When the billing data of the day is acquired and the billing destination of the received billing data is different from the billing destination of the acquired billing data, since the deposit transfer processing unit 102c for performing the deposit transfer is provided, the debt collection from the company having multiple branches It is possible to appropriately transfer the deposit to each branch even if the payment is performed from the representative branch in a lump sum.

[4. Other embodiments]
In addition to the above-described embodiments, the present invention may be implemented in various different embodiments within the scope of the technical ideas described in the claims.

For example, among the processes described in the embodiments, all or part of the processes described as being automatically performed may be manually performed, or the processes described as being manually performed may be performed. All or part of it can be done automatically by a known method.

In addition, the processing procedure, control procedure, specific name, information including parameters such as registration data and search conditions of each processing, screen examples, and database configuration shown in the present specification and drawings are not specified unless otherwise specified. Can be changed arbitrarily.

Further, with respect to the deposit transfer device 100, each component shown in the figure is a functional concept and does not necessarily have to be physically configured as shown in the figure.

For example, with respect to the processing functions included in the deposit transfer device 100, particularly each processing function performed by the control unit 102, all or any part thereof is realized by the CPU and a program interpreted and executed by the CPU. It may be realized as hardware by wired logic. The program is recorded on a non-temporary computer-readable recording medium including a programmed instruction for causing the information processing apparatus to execute the process described in the present embodiment, and the deposit transfer apparatus is required. Read mechanically to 100. That is, in a storage unit such as a ROM or an HDD (Hard Disk Drive), a computer program for giving instructions to the CPU in cooperation with the OS and performing various processes is recorded. This computer program is executed by being loaded into RAM, and cooperates with a CPU to form a control unit.

Further, this computer program may be stored in the application program server connected to the deposit transfer device 100 via an arbitrary network, and all or a part thereof can be downloaded as needed. is there.

Further, the program for executing the process described in the present embodiment may be stored in a non-temporary computer-readable recording medium, or may be configured as a program product. Here, the "recording medium" includes a memory card, a USB (Universal Serial Bus) memory, an SD (Secure Digital) card, a flexible disk, a magneto-optical disk, a ROM, an EPROM (Erasable Programmable Read Only Memory), and an EEPROM (registered). Trademarks) (Electrically Erasable and Programmable Read Only Memory), CD-ROM (Compact Disk Read Only Memory), MO (Magnet-Optical Disk), MO (Magnet-Optical Disk), DVD (Digital), DVD (Digital) It shall include any "portable physical medium".

Further, the "program" is a data processing method described in any language or description method, regardless of the format such as source code or binary code. The "program" is not necessarily limited to a single program, but is distributed as a plurality of modules or libraries, or cooperates with a separate program represented by the OS to achieve its function. Including things. It should be noted that well-known configurations and procedures can be used for the specific configuration and reading procedure for reading the recording medium in each device shown in the embodiment, the installation procedure after reading, and the like.

Various databases and the like stored in the storage unit 106 are memory devices such as RAM and ROM, fixed disk devices such as hard disks, flexible disks, and storage means such as optical disks, and are used for various processes and website provision. Stores programs, tables, databases, files for web pages, etc.

Further, the deposit transfer 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 an arbitrary peripheral device is connected. Further, the deposit transfer device 100 may be realized by mounting software (including a program or data) that realizes the processing described in the present embodiment on the device.

Further, the specific form of dispersion / integration of the device is not limited to that shown in the figure, and all or a part thereof may be functionally or physically in an arbitrary unit according to various additions or functional loads. It can be distributed and integrated. That is, the above-described embodiments may be arbitrarily combined and implemented, or the embodiments may be selectively implemented.

100 Deposit transfer device 102 Control unit 102a Billing processing unit 102b Deposit processing unit 102c Deposit transfer processing unit 102d Application processing unit 102e Master maintenance unit 102f Screen display control unit 104 Communication interface unit 106 Storage unit 106a Billing destination master 106b Bank fee master 106c Billing data file 106d Deposit data file 106e Deposit application data file 108 Input / output interface 112 Input device 114 Output device 300 Network 400 Terminal device

Claims (5)

A deposit transfer device equipped with a storage unit and a control unit.
The storage unit
The billing master registered by associating the billing address with the deposit billing address,
Billing data including billing address, estimated collection date, billing amount,
Stores and
The control unit
A deposit processing method for entering deposit data including billing address, deposit date, and deposit amount,
With reference to the billing destination master, a billing destination whose payment billing destination is the billing destination of the deposit data is acquired, and among the billing data of the acquired billing destination, billing on the scheduled collection date within a predetermined business day before and after the payment date. A deposit transfer device provided with a deposit transfer processing means for acquiring data and performing a deposit transfer when the billing destination of the acquired billing data is different from the billing destination of the acquired billing data. The storage unit
Stores a fee master that registers bank transfer fees
The deposit transfer processing means is characterized in that, when there is a difference between the total billing amount of the acquired billing data and the deposit amount, if the miscalculation matches the fee of the fee master, the deposit is transferred. The deposit transfer device according to claim 1. The deposit according to claim 1 or 2, wherein the deposit transfer processing means performs a deposit transfer according to an operation of an operator when there is a discrepancy between the total billing amount of the acquired billing data and the deposit amount. Transfer device. It is a deposit transfer method executed by an information processing device equipped with a control unit and a storage unit.
In the storage unit
The billing master registered by associating the billing address with the deposit billing address,
Billing data including billing address, estimated collection date, billing amount,
Is stored,
Executed in the control unit,
A deposit processing step to enter deposit data including billing address, deposit date, and deposit amount,
With reference to the billing destination master, a billing destination whose payment billing destination is the billing destination of the deposit data is acquired, and among the billing data of the acquired billing destination, billing on the scheduled collection date within a predetermined business day before and after the payment date. If the billing address of the acquired billing data is different from the billing address of the acquired billing data, the deposit transfer processing step to perform the deposit transfer and
A deposit transfer method characterized by including. It is a deposit transfer program to be executed by an information processing device equipped with a control unit and a storage unit.
In the storage unit
The billing master registered by associating the billing address with the deposit billing address,
Billing data including billing address, estimated collection date, billing amount,
Is stored,
In the control unit
A deposit processing step to enter deposit data including billing address, deposit date, and deposit amount,
With reference to the billing destination master, a billing destination whose payment billing destination is the billing destination of the deposit data is acquired, and among the billing data of the acquired billing destination, billing on the scheduled collection date within a predetermined business day before and after the payment date. If the billing address of the acquired billing data is different from the billing address of the acquired billing data, the deposit transfer processing step to perform the deposit transfer and
Deposit transfer program to run.

Images