JP7250652B2 - Withdrawal Result Update Device, Withdrawal Result Update Method, and Withdrawal Result Update Program - Google Patents

Description

The present invention relates to a withdrawal result update device, a withdrawal result update method, and a withdrawal result update program.

Paragraph 0006 of Patent Document 1 discloses a settlement management system, a settlement management method, and a settlement management program for supporting efficient settlement at a store. Paragraph 0053 of Patent Document 1 discloses a store terminal. 30 transmits an account transfer request message to the management server 20 .

Japanese Patent Application Laid-Open No. 2017-130013

In the field of such account transfer requests, there are cases where the account transfer is entrusted to an agency. In order to identify the receivables that the consignor wants to collect, the consignor assigns a number called a “credit key” for management of the consignor. must be numbered. The customer number is created based on the rules set by the contractor. For example, outsourcer A creates the customer number based on the rule of "consignor code (8 digits) + 00 + bond key (10 digits)", and outsourcer B creates the customer number "0 + consignor code (5 digits)". digits) + 0000 + bond key (10 digits)".

For this reason, conventionally, even if the consignee returns a withdrawal result for the customer number, the consignor refers to the rule set by the consignee to determine which bond key each customer number corresponds to. Therefore, it takes a lot of time and effort to update the withdrawal result for each claim. In the example of the preceding paragraph, if entrustee B returns a message indicating that a withdrawal has been made to the customer number "01234500001000000001", the entrustor will determine that the bond key corresponding to the customer number is Based on the rule of B above, specifying "1000000001" updates the fact that the bond with the bond key "1000000001" has been withdrawn.

Also, even if the specific work is automated, since the rules differ for each contractor, it is necessary to create a separate program for each contractor, and there is room for improvement from the viewpoint of cost and operational efficiency. There was a lot

In other words, there has been a demand for a technology that can automate the task of identifying a bond key from a customer number and that can be used by any consignee, but has not been realized in the past.

The present invention has been made in view of the above-mentioned problems, and the customer number (credit identification data for consignor management) created based on the rules set by the consignee To provide a withdrawal result update device, a withdrawal result update method, and a withdrawal result update program that automatically update the withdrawal result by specifying data) and can be used for any consignee.

In order to solve the above-described problems and achieve the object, a withdrawal result update device according to the present invention is a withdrawal result update device comprising a control unit, wherein the control unit entrusts account transfer agency. Account transfer request data including entrustor management credit identification data for the entrustor to manage his/her own receivables and the amount to be debited from the customer's account corresponding to the receivable, and a destination to which the account transfer agency is entrusted. a consignee master containing consignee identification data for identifying the consignee and a rule for generating consignee management claim identification data for the consignee to manage the claim; a bond identification data generation means for generating the bond identification data for management of the consignee including the credit identification data for management of the consignor based on the rule in the master of the consignee linked to the identification data of the consignor; Tying master generation means for generating a tying master containing the management bond identification data and the bond identification data for management of the consignee generated by the bond identification data generation means, and the withdrawal amount and the bond identification data generation means. a request file generating means for generating an account transfer request file to be delivered to the entrustee when the entrustor requests the entrustee to perform the account transfer on behalf of the entrustee, the account transfer request file including the credit identification data for management of the entrustee generated in step; Withdrawal, which is data indicating that the withdrawal amount in the account transfer request file linked to the consignee management credit identification data and the consignee management credit identification data in the account transfer request file is successful. the account transfer result file, which includes completed data or non-withdrawal data that means that it was not possible, to be delivered to the consignor when the consignee returns the result of the account transfer agency to the consignor; a result file importing means to be imported into an apparatus; With respect to the claim specified by the entrustor management credit identification data, the withdrawal result in the account transfer request data is updated to mean that the withdrawal has been made, and the account captured by the result file capturing means. With respect to the claim specified by the consignor management claim identification data in the linking master linked to the trustee management claim identification data corresponding to the non-withdrawal data in the transfer result file, a withdrawal result updating means for updating the withdrawal result to mean that the withdrawal was not possible.

Further, a withdrawal result update method according to the present invention is a withdrawal result update method executed by an information processing apparatus having a control unit, and is executed by the control unit. Account transfer request data including consignor management credit identification data for managing its own credit and the amount to be debited from the customer's account corresponding to the credit, and the consignee to whom the account transfer agency is entrusted and a consignee master containing consignee identification data for identifying the consignee and a rule for generating consignee management claim identification data for the consignee to manage the claim, and referring to the designated consignee a bond identification data generating step of generating the bond identification data for management of the consignor including the bond identification data for management of the consignor based on the rule in the master of the consignee linked to the identification data; A linking master generation step for generating a linking master containing the bond identification data and the bond identification data for management of the entrusted party generated in the bond identification data generation step in a linked manner, and the withdrawal amount and the bond identification data generation step and the account Withdrawal completed data, which is data indicating that the withdrawal amount in the account transfer request file linked to the trustee management credit identification data in the transfer request file and the trustee management credit identification data is completed. Alternatively, an account transfer result file, including non-withdrawal data, which is data indicating that it was not possible, is sent to the consignor when the entrustee returns the result of the account transfer agency to the consignor. a result file importing step, and the consignor in the pegging master linked with the credit identification data for consignee management corresponding to the debited data in the account transfer result file imported in the result file importing step; For the claim specified by the credit identification data for administration, the withdrawal result in the account transfer request data is updated to mean that the withdrawal has been made, and the account transfer result captured in the result file capturing step. Withdrawal result in the account transfer request data for the claim specified by the consignor management claim identification data in the linking master linked to the consignee management claim identification data corresponding to the non-withdrawal data in the file and a debit result updating step of updating the to mean that the debit was not possible.

Further, a withdrawal result update program according to the present invention is a withdrawal result update program to be executed by an information processing apparatus having a control unit, and is a person who entrusts account transfer agency services to be executed by the control unit. Account transfer request data including entrustor management credit identification data for the entrustor to manage his/her own receivables and the amount to be debited from the customer's account corresponding to the receivable, and a destination to which the account transfer agency is entrusted. a consignee master containing consignee identification data for identifying the consignee and a rule for generating consignee management claim identification data for the consignee to manage the claim; a bond identification data generation step of generating the bond identification data for management of the consignor including the credit identification data for management of the consignor based on the rule in the consignee master linked to the consignor identification data; A linking master generation step for generating a linking master containing the bond identification data for management and the bond identification data for management of the consignee generated in the bond identification data generation step, and a withdrawal amount and the bond identification data generation step. a request file generating step of generating an account transfer request file to be delivered to the consignee when the consignor requests the consignee to perform the account transfer on behalf of the consignee, Withdrawal, which is data indicating that the withdrawal amount in the account transfer request file linked to the consignee management credit identification data and the consignee management credit identification data in the account transfer request file is successful. the account transfer result file, which includes completed data or non-withdrawal data that means that it was not possible, to be delivered to the consignor when the consignee returns the result of the account transfer agency to the consignor; a step of loading a result file to be loaded into a device; and a step of loading a result file into a device; For the claim specified by the entrustor management credit identification data, the withdrawal result in the account transfer request data is updated to mean that the withdrawal has been made, and the account captured in the result file capturing step. With respect to the claim specified by the consignor management claim identification data in the linking master linked to the trustee management claim identification data corresponding to the non-withdrawal data in the transfer result file, and a withdrawal result update step of updating the withdrawal result to mean that the withdrawal was not possible.

According to the present invention, the withdrawal result is automatically determined by specifying the bond key (creditor-managed credit identification data) from the customer number (creditor-managed credit-identification data) created based on the rules set by the consignee. The effect is that it can be updated and used for any subcontractor.

FIG. 1 is a block diagram showing an example of the configuration of a withdrawal result update device. FIG. 2 is an image diagram showing an example of the relationship between a consignor, a consignee, a financial institution, and a customer. FIG. 3 is a diagram showing an example of the Japanese Bankers Association format. FIG. 4 is a diagram showing an example of a customer number setting rule for each consignee. FIG. 5 is a diagram showing an example of generating an account transfer request file. FIG. 6 is a diagram showing an example of importing an account transfer result file and updating the withdrawal result in the account transfer request data.

Embodiments of a withdrawal result update device, a withdrawal result update method, and a withdrawal result update program according to the present invention will be described in detail below with reference to the drawings. It should be noted that the present invention is not limited by this embodiment.

[1. overview]
In the Japanese Bankers Association format, which defines the format for the account transfer request file and the account transfer result file that are linked with the account transfer service providers, the customer number setting rules differ depending on the entrustee. Specifically, the format of the Japanese Bankers Association is unified as shown in FIG. 3, but the customer number setting rule is defined for each consignee as shown in FIG.

For this reason, conventionally, it was necessary to create a program for creating an account transfer request file and a program for retrieving an account transfer result file for each consignee.

Therefore, in this embodiment, by using the account transfer customer number linking master, the bond key on the system and the account transfer result file are uniquely linked regardless of the customer number setting rule specified by any consignee. made it possible. Specific configurations and operations will be described below.

[2. composition]
An example of the configuration of the withdrawal result update device 100 according to this embodiment will be described with reference to FIG. FIG. 1 is a block diagram showing an example of the configuration of the withdrawal result update device 100. As shown in FIG.

The withdrawal result update device 100 is a commercially available desktop personal computer. The withdrawal result updating device 100 is not limited to a stationary information processing device such as a desktop personal computer. type information processing device.

The withdrawal result update device 100 includes a control unit 102 , a communication interface unit 104 , a storage unit 106 and an input/output interface unit 108 . Each unit included in the withdrawal result updating device 100 is communicably connected via an arbitrary communication path.

The communication interface unit 104 communicably connects the payment result update 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 another device via a communication line. Here, the network 300 has a function of connecting the payment result update device 100 and the server 200 so that they can communicate with each other, and is, for example, the Internet or a LAN (Local Area Network). Data such as various masters described later may be stored in the server 200, for example.

An input device 112 and an output device 114 are connected to the input/output interface section 108 . The output device 114 can be a monitor (including a home television), a speaker, or a printer. The input device 112 can be a keyboard, a mouse, a microphone, or a monitor that realizes a pointing device function in cooperation with a mouse. Note that, hereinafter, 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 .

The storage unit 106 stores various databases, tables, files, and the like. The storage unit 106 stores a computer program for performing various processes by giving commands to a CPU (Central Processing Unit) in cooperation with an OS (Operating System). As the storage unit 106, for example, memory devices such as RAM (Random Access Memory) and ROM (Read Only Memory), fixed disk devices such as hard disks, flexible disks, and optical disks can be used.

The storage unit 106 stores, for example, account transfer request data 106a, a trustee master 106b, an account transfer customer number linking master 106c as a linking master (hereinafter simply referred to as "linking master 106c"), and an account transfer request file 106d. and an account transfer result file 106e.

As shown in FIG. 5, the account transfer request data 106a includes, for example, consignor management credit identification data (credit key) for the consignor, who entrusts the account transfer agency, to manage his/her own credit, The amount to be debited from the customer's account corresponding to the receivable, the debiting bank identification data (debiting bank number and debiting bank name) for identifying the debiting bank that will debit the debiting amount, and the debiting amount at the debiting bank including withdrawal branch identification data (withdrawal branch number and withdrawal branch name), depositor identification data (depositor name), withdrawal results, and the like. The entrustor management bond identification data (bond key) is a key item that can uniquely identify a bond on the system.

Since the account transfer request data 106a shown in FIG. 5 is data before requesting account transfer agency, the withdrawal result is "Z: Requesting". On the other hand, the account transfer request data 106a shown in FIG. 6 is the data after the account transfer agency request (that is, the data reflecting the request result), so the withdrawal result is "0: transferred" or It has been updated to "1: Insufficient funds". The consignor can automatically perform the update by using the withdrawal result update device 100 according to the present embodiment.

The consignee master 106b is a master for managing customer number setting rules for each consignee. As shown in FIG. 5, the consignee master 106b contains, for example, consignee identification data (consignee classification and consignee name) for identifying the consignee who entrusts the account transfer agency, and consignor code and a rule (layout pattern) relating to generation of trustee management credit identification data (customer number) for the trustee to manage the credit.

In the consignee master 106b shown in FIG. 5, a layout pattern "2:B" is set as a customer number setting rule for company B, which is the consignee. Specifically, the customer number setting rule defined by "2:B" is "0+consignor code (5 digits)+customer management code (14 digits)" as shown in FIG. The customer management code is a management code that can uniquely identify the bond by including the bond key. This is the code written as

The linking master 106c is a feature of the present invention. By linking the bond key and the customer number in this master, the linking is performed with the customer number based on the customer number in the account transfer result file 106e, which will be described later. It becomes possible to specify the bond key in the account transfer request data 106a, and as a result, it becomes possible to automatically update the withdrawal result in the account transfer request data 106a. As shown in FIG. 5, the linking master 106c includes, for example, the bond identification data for management of the consignor (bond key) and the bond identification data for management of the consignee (customer number) in a linked manner.

The account transfer request file 106d is a file that is passed to the entrustee when the entrustor requests the entrustee to perform the account transfer on behalf of the entrustee. The account transfer request file 106d includes, for example, the withdrawal amount, the credit identification data (customer number) for management of the consignee, and the like, as partially shown in FIG.

The account transfer result file 106e is a file that is given to the entrustor when the entrustee returns the result of the account transfer to the entrustor, and is created by the entrustee, for example. The account transfer result file 106e has the same format as the account transfer request file 106d, but only the withdrawal result area has been updated by the trustee. The account transfer result file 106e, as shown in FIG. Withdrawn data ("0" in the withdrawal result area), which means that the withdrawal amount in the linked account transfer request file 106d was successfully withdrawn, or non-withdrawn data, which means that it was not possible (“1” in withdrawal result area), and so on.

The control unit 102 is a CPU or the like that comprehensively controls the withdrawal result update device 100 . The control unit 102 has an internal memory for storing a control program such as an OS, a program defining various processing procedures, required data, and the like, and performs various information processing based on these stored programs. Execute.

The control unit 102 functionally and conceptually includes, for example, (1) creditor management credit identification data for the trustor who entrusts the account transfer agency to manage his/her credit, and customer information corresponding to the credit; account transfer request data including the amount to be deducted from the account; trustee identification data for identifying the trustee who entrusts the account transfer agency; trustee management for the trustee to manage the claim; and a consignee master containing rules relating to the generation of credit identification data for credit management, and based on the rules in the consignee master associated with the designated consignee identification data, the credit identification for management of the consignor a bond identification data generation unit 102a as bond identification data generation means for generating the bond identification data for management of the outsourcee including data; (3) the withdrawal amount and the consignment generated by the bond identification data generating means; a request file generating unit 102c as request file generating means for generating an account transfer request file to be delivered to the entrustee when the entrustor requests the entrustee to perform the account transfer on behalf of the entrustee, and (4) means that the debit amount in the account transfer request file linked with the consignee management credit identification data in the account transfer request file and the consignee management credit identification data has been successfully withdrawn. The account to be handed over to the consignor when the consignee returns the result of the account transfer agency to the consignor (5) the result file fetching unit 102d as result file fetching means for fetching the transfer result file into the device; The withdrawal result in the account transfer request data means that the withdrawal was successful for the claim specified by the credit identification data for consignor management in the pegging master linked with the credit identification data for consignee management. and the credit for management of the consignor in the pegging master linked with the credit identification data for consignor management corresponding to the non-withdrawal data in the account transfer result file imported by the result file importing means a withdrawal result updating unit 102e as withdrawal result updating means for updating the withdrawal result in the account transfer request data to mean that the withdrawal could not be made for the claim specified by the identification data; there is

The bond identification data generation unit 102a refers to the account transfer request data 106a including the bond key and the debit amount, and the consignee master 106b including the consignee and the layout pattern, and associates with the specified consignee. Based on the layout pattern in the consignee master 106b, a customer number including the bond key is generated.

The tying master generating unit 102b generates a tying master 106c including the bond key and the customer number generated by the bond identification data generating unit 102a in a linked manner.

The request file generation unit 102c generates an account transfer request file 106d containing the amount to be withdrawn and the customer number generated by the bond identification data generation unit 102a.

The result file importing unit 102d retrieves the account containing the customer number in the account transfer request file 106d and data that has been withdrawn ("0" in the withdrawal result area) or data that has not been withdrawn ("1" in the withdrawal result area). The transfer result file 106e is taken into the withdrawal result update device 100.

The debit result update unit 102e updates the receivables in the linking master 106c linked to the customer number corresponding to the debited data (“0” in the debit result area) in the account transfer result file 106e captured by the result file capture unit 102d. For the claim specified by the key, the withdrawal result in the account transfer request data 106a is updated to "0: transferred". In response to this, the withdrawal result update unit 102e links the customer number corresponding to the non-withdrawal data ("1" in the withdrawal result area) in the account transfer result file 106e imported by the result file import unit 102d. For the bond specified by the bond key in the master 106c, the withdrawal result in the account transfer request data 106a is updated to "1: insufficient funds".

[3. Specific example of processing]
In this section, a specific example of processing according to this embodiment will be described. In this item, when the consignor entrusts the account transfer agency to the consignee B company, the withdrawal result in the consignor's account transfer request data 106a goes through the process from the state shown in FIG. Whether the state is automatically updated to the state shown in 6 will be specifically described. In this item, the description will proceed on the assumption that the consignee master 106b is set with the contents shown in FIG.

Note that the correspondence between FIG. 2 and FIGS. 5 and 6 is as follows. 2 corresponds to "company A and company B" in FIG. 5, and "financial institution" in FIG. 2 "Customer" corresponds to "Taro Yamada, Jiro Yamada and Saburo Yamada" in FIGS.

[3-1. Generate account transfer request file]
In this section, generation of the account transfer request file 106d will be described.

First, the account transfer agency consignor prepares account transfer request data 106a shown in FIG.

Subsequently, the consignor designates a consignee for account transfer agency. In this example, it is assumed that "consignee classification=2 (consignee name=B company)" is specified as the consignee.

When the consignee is designated, the bond identification data generation unit 102a generates a customer number as follows. Referring to the consignee master 106b in FIG. 5, the layout pattern associated with the specified consignee "consignee classification=2 (consignee name=company B)" is "2:B".

The customer number generation rule specified by the layout pattern "2:B" is "0+consignor code (5 digits)+customer management code (14 digits)". The entrustor code is the entrustor code "12345" associated with the entrustee "entrustee classification=2 (entrustee name=Company B)" specified in the entrustee master 106b of FIG. The customer management code is a 14-digit code created by zeroing the bond key in the account transfer request data 106a of FIG.

That is, the bond identification data generation unit 102a generates a customer number 01234500001000000001 consisting of "0+consignor code 12345+0000+bond key 1000000001" and a customer number 01234500001000000002 consisting of "0+consignor code 12345+0000+bond key 1000000002". and customer number 01234500001000000003 consisting of "0 + consignor code 12345 + 0000 + receivable key 1000000003".

Subsequently, the tying master generating unit 102b generates a tying master 106c including the bond key and the customer number generated by the bond identification data generating unit 102a in a linked manner. Specifically, as shown in FIG. 5, the tying master generation unit 102b ties the bond key 1000000001 with the customer number 01234500001000000001, includes the bond key 1000000002 with the customer number 01234500001000000002, and includes the bond key 1000000003. and customer number 01234500001000000003 in a linked manner. The linking master 106c holds a combination of a credit key that uniquely identifies a credit in the system and a customer number that uniquely identifies a line in the account transfer request file 106d.

At the same time when the linking master 106c is generated, the request file generation unit 102c links the withdrawal amount of 10,000 yen in the account transfer request data 106a with the customer number 01234500001000000001 generated by the bond identification data generation unit 102a, and generates account transfer request data. 106a and the customer number 01234500001000000002 generated by the bond identification data generation unit 102a are linked, and the withdrawal amount of 30,000 yen in the account transfer request data 106a and the customer number generated by the bond identification data generation unit 102a are included. 01234500001000000003 are linked and the account transfer request file 106d (fixed length file) is generated. Note that the account transfer request file 106d of FIG. 5 does not show the withdrawal amount, but shows only the customer number. The created account transfer request file 106d is passed from the consignor to the consignee.

[3-2. Import account transfer result file and update withdrawal result]
The trustee executes the account transfer based on the account transfer request file 106d generated in [3-1], and sets the withdrawal result area to "0", which means that the withdrawal was successful, or that the withdrawal was not possible. The account transfer result file 106e shown in FIG. 6 is created by updating to "1" which means The created account transfer result file 106e is passed from the consignee to the consignor. The result file importing unit 102d imports the account transfer result file 106e handed over from the trustee into the debit result updating device 100. FIG.

Subsequently, the withdrawal result update unit 102e updates the withdrawal result in the account transfer request data 106a as follows based on the captured account transfer result file 106e.

The bond key associated with the customer number 01234500001000000001 corresponding to "0" in the withdrawal result area in the account transfer result file 106e of FIG. In this case, the withdrawal result updating unit 102e updates the withdrawal result in the account transfer request data 106a of FIG. In a similar manner, the withdrawal result updating unit 102e also updates the withdrawal result in the account transfer request data 106a of FIG.

On the other hand, the bond key associated with the customer number 01234500001000000003 corresponding to "1" in the withdrawal result area in the account transfer result file 106e of FIG. In this case, the withdrawal result updating unit 102e updates the withdrawal result in the account transfer request data 106a of FIG.

As described above, the withdrawal result "Z: requesting" in the account transfer request data 106a could be updated to "0: transferred" or "1: lack of funds".

Here, conventionally, when identifying the bond key in the corresponding account transfer data 106a from the customer number in the account transfer result file 106e, the customer number setting rule differs depending on each outsourcee. It was necessary to change the conditions specified in On the other hand, in this embodiment, it is possible to update the withdrawal result in the account transfer request data 106a under the same conditions by going through the linking master 106c.

[3-3. Concerning the setting of the subcontractor]
In [3-1] and [3-2], the processing when "outsourcer classification = 2 (outsourcer name = Company B)" is specified as the outsourcee, but for example, the outsourcee If "outsourcer classification=1 (outsourcer name=Company A)" is specified as a customer number, a customer number can be generated based on the layout pattern "1:A". Although not shown in the consignee master 106b of FIG. 5, if another consignee and a corresponding layout pattern are added to the consignee master 106b, a customer number can be generated based on the added layout pattern. can be done. As described above, in the present embodiment, if a combination of consignees and layout patterns is set in advance in the consignee master 106b, it is possible to automatically update the debit results for all consignees using only one program. , there is no need to create a separate program for each subcontractor as in the past.

[4. Summary of this embodiment]
As described above, the withdrawal result updating device 100 according to the present embodiment converts the customer number (creditor's credit identification data for management of consignor) created based on the rule set by the consignee to the credit key (creditor's credit identification data for management). ) can be specified to automatically update the withdrawal results and can be used for any consignee.

[5. Other embodiments]
The present invention may be implemented in various different embodiments other than the embodiments described above within the scope of the technical idea described in the claims.

For example, among the processes described in the embodiments, all or part of the processes described as being automatically performed can be manually performed, or all of the processes described as being manually performed Alternatively, some can be done automatically by known methods.

In addition, unless otherwise specified, the processing procedures, control procedures, specific names, information including parameters such as registration data and search conditions for each process, screen examples, and database configurations shown in this specification and drawings can be changed arbitrarily.

Also, with regard to the withdrawal result update device 100, each component shown in the figure is functionally conceptual, and does not necessarily need to be physically configured as shown in the figure.

For example, the processing functions of the withdrawal result updating device 100, particularly the processing functions performed by the control unit, may be implemented in whole or in part by a CPU and a program interpreted and executed by the CPU. Alternatively, it may be implemented as hardware using wired logic. The program is recorded on a non-temporary computer-readable recording medium containing programmed instructions for causing the information processing apparatus to execute the processing described in this embodiment, and updates the withdrawal result as necessary. It is read mechanically by the device 100 . That is, a storage unit such as a ROM or HDD (Hard Disk Drive) stores a computer program for giving commands to the CPU in cooperation with the OS to perform various processes. This computer program is executed by being loaded into the RAM and constitutes a control section in cooperation with the CPU.

In addition, this computer program may be stored in an application program server connected to the withdrawal result update device 100 via any network, and it is possible to download all or part of it as necessary. is.

Also, the program for executing the processing described in this embodiment may be stored in a non-temporary computer-readable recording medium, or may be configured as a program product. Here, the term "recording medium" refers to memory cards, USB (Universal Serial Bus) memories, SD (Secure Digital) cards, flexible disks, magneto-optical disks, ROMs, EPROMs (Erasable Programmable Read Only Memory), EEPROMs (registered (trademark) (Electrically Erasable and Programmable Read Only Memory), CD-ROM (Compact Disk Read Only Memory), MO (Magneto-Optical disk), DVD (Digital Versatile Disk), and Disc (registered trademark) such as Blu- shall include any "portable physical medium".

A "program" is a data processing method written in any language or writing method, regardless of the format such as source code or binary code. In addition, the "program" is not necessarily limited to a single configuration, but is distributed as multiple 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 embodiments, the installation procedure after reading, and the like.

The various databases stored in the storage 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. It stores programs, tables, databases, files for web pages, and so on.

The withdrawal result update 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 withdrawal result update device 100 may be implemented by installing software (including programs, data, etc.) that implements the processing described in the present embodiment.

Furthermore, the specific forms of distribution and integration of devices are not limited to those shown in the figures, and all or part of them can be functionally or physically arranged in arbitrary units according to various additions or functional loads. It can be distributed and integrated. In other words, the embodiments described above may be arbitrarily combined and implemented, or the embodiments may be implemented selectively.

INDUSTRIAL APPLICABILITY The present invention is useful, for example, in all industries that utilize account transfer entrustment, and is particularly useful in the non-bank industry and the like.

100 Withdrawal result update device 102 Control unit
102a Bond identification data generation unit
102b Linking master generation unit
102c request file generation unit
102d Result file import unit
102e withdrawal result update unit 104 communication interface unit 106 storage unit
106a account transfer request data
106b Outsourced Master
106c Account transfer customer number linking master
106d Account transfer request file
106e account transfer result file 108 input/output interface unit 112 input device 114 output device 200 server 300 network

Claims (3)

A withdrawal result updating device comprising a control unit,
The control unit
Account transfer request data including consignor management credit identification data for the consignor who entrusts the account transfer agency to manage his/her own credit and the amount to be debited from the customer's account corresponding to the credit; a consignee master including entrustee identification data for identifying a consignee to which the account transfer agency is entrusted and a rule for generating consignee management claim identification data for the consignee to manage the claim; , and based on the rule in the outsourcee master linked to the designated outsourcee identification data, a claim for generating the outsourcee management credit identification data including the outsourcer management bond identification data identification data generating means;
a linking master generation means for generating a linking master containing the bond identification data for management of the consignor and the bond identification data for management of the consignee generated by the bond identification data generation means;
An account transfer request to be given to the entrustee when the entrustor requests the entrustee to perform the account transfer on behalf of the entrustee, the entrustor including the debit amount and the credit identification data for managing the entrustee generated by the credit identification data generating means. a request file generating means for generating a file;
Withdrawal, which is data indicating that the withdrawal amount in the account transfer request file linked to the consignee management credit identification data and the consignee management credit identification data in the account transfer request file is successful. the account transfer result file, which includes completed data or non-withdrawal data that means that it was not possible, to be delivered to the consignor when the consignee returns the result of the account transfer agency to the consignor; result file import means for importing into the device;
Specified by the consignor management credit identification data in the linking master associated with the entrustee management credit identification data corresponding to the debited data in the account transfer result file captured by the result file capturing means with respect to the receivables, the withdrawal result in the account transfer request data is updated to mean that the withdrawal has been made, and the non-withdrawal data in the account transfer result file captured by the result file capturing means is updated. The withdrawal result in the account transfer request data for the claim specified by the creditor management credit identification data in the pegging master linked to the corresponding entrustee management credit identification data was not able to be withdrawn. a withdrawal result updating means for updating to mean
to provide
Withdrawal result updating device characterized by A withdrawal result update method executed by an information processing device comprising a control unit,
executed by the control unit;
Account transfer request data including consignor management credit identification data for the consignor who entrusts the account transfer agency to manage his/her own credit and the amount to be debited from the customer's account corresponding to the credit; a consignee master including entrustee identification data for identifying a consignee to which the account transfer agency is entrusted and a rule for generating consignee management claim identification data for the consignee to manage the claim; , and based on the rule in the outsourcee master linked to the designated outsourcee identification data, a claim for generating the outsourcee management credit identification data including the outsourcer management bond identification data an identification data generation step;
a linking master generation step for generating a linking master including the bond identification data for management of the consignor and the bond identification data for management of the consignee generated in the step of generating bond identification data;
An account transfer request to be given to the entrustee when the entrustor requests the entrustee to perform the account transfer on behalf of the entrustee, the entrustor including the debit amount and the claim identification data for managing the entrustee generated in the claim identification data generating step. a request file generation step for generating a file;
Withdrawal, which is data indicating that the withdrawal amount in the account transfer request file linked to the consignee management credit identification data and the consignee management credit identification data in the account transfer request file is successful. the account transfer result file, which includes completed data or non-withdrawal data that means that it was not possible, to be delivered to the consignor when the consignee returns the result of the account transfer agency to the consignor; a step of importing a result file to be imported into the device;
identified by the consignor-managed claim identification data in the pegging master linked with the consignee-managed claim identification data corresponding to the debited data in the account transfer result file imported in the result file importing step with respect to the receivables, the withdrawal result in the account transfer request data is updated to mean that the withdrawal has been made, and the non-withdrawal data in the account transfer result file captured in the result file capturing step is updated. The withdrawal result in the account transfer request data for the claim specified by the creditor management credit identification data in the pegging master linked to the corresponding entrustee management credit identification data was not able to be withdrawn. a debit result update step that updates to mean
including
A withdrawal result update method characterized by: A withdrawal result update program to be executed by an information processing device having a control unit,
for causing the control unit to execute
Account transfer request data including consignor management credit identification data for the consignor who entrusts the account transfer agency to manage his/her own credit and the amount to be debited from the customer's account corresponding to the credit; a consignee master including entrustee identification data for identifying a consignee to which the account transfer agency is entrusted and a rule for generating consignee management claim identification data for the consignee to manage the claim; , and based on the rule in the outsourcee master linked to the designated outsourcee identification data, a claim for generating the outsourcee management credit identification data including the outsourcer management bond identification data an identification data generation step;
a linking master generation step for generating a linking master including the bond identification data for management of the consignor and the bond identification data for management of the consignee generated in the step of generating bond identification data;
An account transfer request to be given to the entrustee when the entrustor requests the entrustee to perform the account transfer on behalf of the entrustee, the entrustor including the debit amount and the claim identification data for managing the entrustee generated in the claim identification data generating step. a request file generation step for generating a file;
Withdrawal, which is data indicating that the withdrawal amount in the account transfer request file linked to the consignee management credit identification data and the consignee management credit identification data in the account transfer request file is successful. the account transfer result file, which includes completed data or non-withdrawal data that means that it was not possible, to be delivered to the consignor when the consignee returns the result of the account transfer agency to the consignor; a step of importing a result file to be imported into the device;
identified by the consignor-managed claim identification data in the pegging master linked with the consignee-managed claim identification data corresponding to the debited data in the account transfer result file imported in the result file importing step with respect to the receivables, the withdrawal result in the account transfer request data is updated to mean that the withdrawal has been made, and the non-withdrawal data in the account transfer result file captured in the result file capturing step is updated. The withdrawal result in the account transfer request data for the claim specified by the creditor management credit identification data in the pegging master linked to the corresponding entrustee management credit identification data was not able to be withdrawn. a debit result update step that updates to mean
including
Withdrawal result update program characterized by.

Images