Transfer business support device, transfer business support method, and transfer business support program

Abstract

To improve the flexibility and productivity of integrated transfer business.SOLUTION: The transfer work supporting apparatus according to the present embodiment includes: a payment processing unit that creates payment detail data including a payment detail number, a payment type, a payment date, payee account information, a payment item, and a payment amount when a payment occurs for each department; a payment settlement processing unit that creates payment data including a payment settlement number, a payment date, payee account information, a payment amount, a payment settlement user who performs payment settlement, and a payment type for each department based on the payment detail data at the time of payment settlement; and a transfer file creation processing unit that creates a transfer file including transfer data and transfer detail data for each department.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present invention relates to a transfer operation support device, a transfer operation support method, and a transfer operation support program. [Background technology]

[0002] For example, in the general transfer business in the rent guarantee industry, since each remittance department has different remittance intentions, a general transfer file is created for each remittance department. Conventionally, a system for creating transfer data at a rent guarantee company is known, for example, from Patent Document 1. [Prior art documents] [Patent documents]

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

[0004] However, in the past, when payments made by multiple departments were transferred on the same day, the system would consolidate them into a single comprehensive transfer file after confirming that each department had completed their payment.This meant that comprehensive transfer files had to be created based on the progress of each department's administrative work, and payments from all departments had to be confirmed before the transfer was scheduled, resulting in low flexibility and productivity in creating comprehensive transfer files.

[0005] The present invention has been made in consideration of the above, and aims to provide a transfer business support device, a transfer business support method, and a transfer business support program that can improve the flexibility and productivity of comprehensive transfer business. [Means for solving the problem]

[0006] In order to solve the above-mentioned problems and achieve the object, the present invention provides a transfer business support device equipped with a control unit, which is characterized by comprising: a payment processing means for creating payment detail data including a payment detail number, payment type, payment date, payee account information, payment item, and payment amount when a payment occurs for each department; a payment settlement processing means for creating payment data including a payment settlement number, payment date, payee account information, payment amount, the payment settlement user who made the payment settlement, and payment type based on the payment detail data at the time of payment settlement for each department; and a transfer file creation processing means for aggregating the payment data for each department using the payment date and payment type or payment settlement user as aggregation conditions, and creating a transfer file including transfer data including transfer identification information, designated transfer date, company account information, number of transfers, and transfer amount, and transfer detail data including transfer identification information, payee account information, and transfer amount.

[0007] According to another aspect of the present invention, the departments may include a collection agency department, a subrogation department, and a management company settlement department of the rent guarantee company.

[0008] According to another aspect of the present invention, the payment type may include collection agency, subrogation, or management company settlement.

[0009] According to another aspect of the present invention, the payment settlement user may be able to hold multiple positions in multiple departments.

[0010] In addition, in order to solve the above-mentioned problems and achieve the object, the present invention is a transfer business support method executed by an information processing device equipped with a control unit, characterized in that it includes: a payment processing step executed by the control unit, which creates, for each department, payment detail data including payment detail number, payment type, payment date, payee account information, payment item, and payment amount when a payment occurs; a payment settlement processing step, for each department, which creates payment data including payment settlement number, payment date, payee account information, payment amount, payment settlement user who made the payment settlement, and payment type based on the payment detail data at the time of payment settlement; and a transfer file creation processing step, for each department, which aggregates the payment data using the payment date and payment type or payment settlement user as aggregation conditions, and creates a transfer file including transfer data including transfer identification information, designated transfer date, company account information, number of transfers, and transfer amount, and transfer detail data including transfer identification information, payee account information, and transfer amount.

[0011] In addition, in order to solve the above-mentioned problems and achieve the objectives, the present invention is a transfer business support device rent guarantee management program to be executed by an information processing device equipped with a control unit, which is characterized in that the control unit executes the following steps: a payment processing step for creating payment detail data including a payment detail number, payment type, payment date, payee account information, payment item, and payment amount when a payment occurs for each department; a payment settlement processing step for creating payment data including a payment settlement number, payment date, payee account information, payment amount, the payment settlement user who made the payment settlement, and payment type based on the payment detail data at the time of payment settlement for each department; and a transfer file creation processing step for aggregating the payment data for each department using the payment date and payment type or payment settlement user as aggregation conditions, and creating a transfer file including transfer data including transfer identification information, designated transfer date, company account information, number of transfers, and transfer amount, and transfer detail data including transfer identification information, payee account information, and transfer amount. [Effects of the Invention]

[0012] The present invention has the effect of making it possible to improve the flexibility and productivity of comprehensive transfer operations. [Brief explanation of the drawings]

[0013] [Figure 1] FIG. 1 is a block diagram showing an example of the configuration of a transfer business support device according to this embodiment. [Figure 2] 2 and 3A are flow charts for explaining an outline of the overall processing of the control unit of the transfer business support device of this embodiment. [Figure 3] FIG. 3 is a diagram for explaining a specific example of the processing of the control unit of the transfer business support device of this embodiment. [Figure 4] FIG. 4 is a diagram for explaining a specific example of the processing of the control unit of the transfer business support device of this embodiment. [Figure 5] FIG. 5 is a diagram for explaining a specific example of the processing of the control unit of the transfer business support device of this embodiment. [Figure 6] FIG. 6 is a diagram for explaining a specific example of the processing of the control unit of the transfer business support device of this embodiment. [Figure 7] FIG. 7 is a diagram for explaining a specific example of the processing of the control unit of the transfer business support device of this embodiment. [Figure 8] FIG. 8 is a diagram for explaining a specific example of the processing of the control unit of the transfer business support device of this embodiment. [Figure 9] FIG. 9 is a diagram for explaining a specific example of the processing of the control unit of the transfer business support device of this embodiment. [Figure 10] FIG. 10 is a diagram for explaining a specific example of the processing of the control unit of the transfer business support device of this embodiment. [Figure 11] FIG. 11 is a diagram for explaining a specific example of the processing of the control unit of the transfer business support device of this embodiment. [Figure 12] FIG. 12 is a diagram for explaining a specific example of the processing of the control unit of the transfer business support device of this embodiment. [Figure 13] FIG. 13 is a diagram for explaining a specific example of the processing of the control unit of the transfer business support device of this embodiment. [Figure 14]FIG. 14 is a diagram for explaining a specific example of the processing of the control unit of the transfer business support device of this embodiment. [Figure 15] FIG. 15 is a diagram for explaining a specific example of the processing of the control unit of the transfer business support device of this embodiment. [Figure 16] FIG. 16 is a diagram for explaining a specific example of the processing of the control unit of the transfer business support device of this embodiment. [Figure 17] FIG. 17 is a diagram for explaining a specific example of the processing of the control unit of the transfer business support device of this embodiment. [Figure 18] FIG. 18 is a diagram for explaining a specific example of the processing of the control unit of the transfer business support device of this embodiment. [Figure 19] FIG. 19 is a diagram for explaining a specific example of the processing of the control unit of the transfer business support device of this embodiment. DETAILED DESCRIPTION OF THE INVENTION

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

[0015] [1. Overview] The outline of the present invention will be explained in the order of [1-1. Problems and Solutions] and [1-2. Outline of the Transfer Operation Support Device of the Present Invention].

[0016] [1-1. Issues / solutions] For example, in the rent guarantee industry, comprehensive transfer operations involve creating a comprehensive transfer file for each remittance department, as each remittance department has different remittance intentions.

[0017] However, in the past, when payments made by multiple departments were transferred on the same day, the system would consolidate them into a single comprehensive transfer file after confirming that each department had completed their payment.This meant that comprehensive transfer files had to be created based on the progress of each department's work, and payments from all departments had to be confirmed before the transfer was scheduled, resulting in low flexibility and productivity in creating comprehensive transfer files.

[0018] This invention improves the flexibility and productivity of comprehensive transfer operations by making it possible to create comprehensive transfer files for each settlement officer and payment type when remittances are made multiple times and by multiple departments on each transfer date.

[0019] Specifically, according to the present invention, in a comprehensive transfer operation, when remittance departments are different, a comprehensive transfer file is created for each settlement (payment settlement) unit, thereby improving the flexibility of the remittance operation when multiple departments are conducting the remittance operation. Also, when remittances are made multiple times on the same day by multiple departments, a comprehensive transfer file can be created for each settlement department and settlement unit.

[0020] In the following explanation, we will use as an example the case where the transfer business support device of the present invention is applied to a rent guarantee company, but the present invention is not limited to this and can be widely applied to companies that handle general transfers (payments) for various purposes and businesses.

[0021] [1-2. Overview of the Transfer Operation Support Device of the Present Invention] When remittances are made multiple times per transfer date and by multiple departments, the transfer business support device of the present invention specifies a settlement clerk or payment type for the settled payment data and creates a (comprehensive) transfer file for each settlement clerk or payment type.

[0022] (Payment type) Examples of payment types are described below. Collection agency: The collection agency department transfers the rent collected through collection agency to the owner / management company. Subrogation: The receivables management department remits subrogation payments for unpaid rent based on a request for subrogation from the management company. Management company settlement: The settlement department transfers the commission fee and agent fee to the management company.

[0023] (Feature Overview) The functional overview is as follows: (1) The user ID of the person who made the payment and the payment type are stored in the payment data. (2) When creating a (general) transfer file, create the (general) transfer file by specifying the user ID or payment type of the payment data stored in (1) as the extraction condition.

[0024] [2. Configuration] The configuration of the transfer business support device 100 according to this embodiment will be described with reference to Fig. 1. Fig. 1 is a block diagram showing an example of the configuration of the transfer business support device 100 according to this embodiment. The transfer business support device 100 according to this embodiment can be suitably used in, for example, a rent guarantee company or the like.

[0025] The transfer operation support device 100 is a workstation, a commercially available desktop personal computer, etc. Note that the transfer operation support device 100 is not limited to a stationary information processing device such as a desktop personal computer, but may also be a portable information processing device such as a commercially available notebook personal computer, PDA (Personal Digital Assistant), smartphone, or tablet personal computer.

[0026] As shown in Figure 1, the transfer operation support device 100 comprises a control unit 102, a communication interface unit 104, a memory unit 106, and an input / output interface unit 108. The units comprised in the transfer operation support device 100 are connected to each other so as to be able to communicate with each other via any communication path.

[0027] The communication interface unit 104 communicatively connects the transfer operation support 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 exchanging data with other devices via a communication line. Here, the network 300 has a function of communicatively connecting the transfer operation support device 100 with the server 200, terminals 400, etc., and is, for example, the Internet or a LAN (Local Area Network). Note that the data stored in the memory unit 106, which will be described later, may be stored on a server. The terminals 400, etc. are, for example, terminals of the collection agency department, the subrogation department, and the management company settlement department, and are configured so that personnel in the collection agency department, the subrogation department, and the management company settlement department can access the transfer operation support device 100 from the terminals 400, etc.

[0028] An input device 112 and an output device 114 are connected to the input / output interface unit 108. The output device 114 may be a monitor (including a home television), a speaker, or a printer. The input device 112 may be a keyboard, a mouse, a microphone, or a monitor that cooperates with a mouse to achieve a pointing device function. 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. Furthermore, displaying on the screen of the output device (monitor) 114 by a user and operating the input device 112 may be referred to as a "user operation via a UI."

[0029] The memory unit 106 stores various databases, tables, files, and the like. The memory unit 106 stores computer programs that work in conjunction with the OS (Operating System) to issue commands to the CPU (Central Processing Unit) to perform various processes. The memory unit 106 may be, for example, a memory device such as RAM (Random Access Memory) or ROM (Read Only Memory), a fixed disk device such as a hard disk, a flexible disk, or an optical disk. The memory unit 106 also stores a management company master 106a, a management company account master 106b, a company's own account master 106c, contract data, contract rent data, remittance data, subrogation payment data, settlement data, payment statement data, payment data, transfer data, transfer statement data, and the like. The transfer data and transfer statement data are referred to as "transfer files."

[0030] The management company master 106a can be configured as a table in which management company codes and management company names are registered in association with each other (see FIG. 3).

[0031] The management company account master 106b can be configured as a table or the like in which management company codes, account codes, banks, branches, deposit types, and account numbers are registered in association with each other (see FIG. 4).

[0032] The company's account master 106c can be configured as a table or the like in which payment account codes, banks, branches, deposit types, and account numbers are registered in association with each other (see FIG. 5).

[0033] The contract data may include a contract number, a customer name, a management company, a management company name, a remittance destination management company code, a remittance destination management company account code, a remittance destination management company code, and a remittance destination management company account code (see FIG. 6).

[0034] The contract rent data may include a contract number, an expense item code, and an invoice amount (see FIG. 7).

[0035] The remittance data may include the contract number, remittance number, rent month, and management company (see Figure 8).

[0036] The subrogation data may include the contract number, the subrogation number, the rent month, the management company, the repayment amount, and the payment statement number (see FIG. 9).

[0037] The settlement data may include the settlement number, settlement date, settlement management company, settlement amount, and payment statement number (see FIG. 10).

[0038] The payment details data may include payment details number, payment type (1: collection agency, 2: subrogation payment, 3: management company settlement), remittance number, payment date, payee account information (payee code, payee account code), payment item code, payment amount, and payment settlement number (see Figure 11).

[0039] The payment data may include the payment settlement number, payment date, payment account information (payment code, payment account code), payment amount, payment settlement user ID, payment type, and transfer GUID (identification information) (see FIG. 12).

[0040] The transfer data may include a transfer GUID (identification information), a designated transfer date, company account information (sending bank code, sending branch code, sending deposit type classification, sending account number), number of transfers, and transfer amount (see Figure 15).

[0041] The transfer details data may include a transfer GUID (identification information), payee account information (payee code, remitted bank code, remitted branch code, remitted deposit type classification, remitted account number), and transfer amount (see Figure 16).

[0042] The control unit 102 is a CPU or the like that performs overall control of the transfer operation support device 100. The control unit 102 has an internal memory for storing control programs such as an OS, programs that define various processing procedures, required data, etc., and executes various information processing operations based on these stored programs.

[0043] The control unit 102 is configured to be able to access the management company master 106a, management company account master 106b, the company's own account master 106c, contract data, contract rent data, remittance data, subrogation data, settlement data, payment statement data, payment data, transfer data, transfer statement data, etc. stored in the memory unit 106. Note that the management company master 106a, management company account master 106b, the company's own account master 106c, contract data, contract rent data, remittance data, subrogation data, settlement data, payment statement data, payment data, transfer data, transfer statement data, etc. may be provided elsewhere (for example, in the server 200), as long as the control unit 102 is able to access them.

[0044] The control unit 102 conceptually includes a remittance calculation processing unit 102a, a subrogation registration unit 102b, a settlement processing unit 102c, a payment settlement processing unit 102d, a transfer file creation processing unit 102e, a master maintenance unit 102f, and a screen display control unit 102g. The remittance calculation processing unit 102a, the subrogation registration unit 102b, and the settlement processing unit 102c are collectively referred to as the "payment processing means."

[0045] The remittance calculation processing unit 102a, for example, provides a payment input screen in response to access from the receiving agency department's terminal 400, and inputs remittance data and payment detail data in response to operations on the payment input screen by the person in charge of the receiving agency department's terminal 400, and stores the data in the memory unit 106.

[0046] The subrogation registration unit 102b, for example, provides a payment input screen in response to access from the subrogation department's terminal 400, and inputs subrogation data and payment detail data in response to operations on the payment input screen by the person in charge of the subrogation department's terminal 400, and stores them in the memory unit 106.

[0047] The settlement processing unit 102c, for example, provides a payment input screen in response to access from the settlement processing department's terminal 400, and inputs settlement data and payment detail data in response to operations on the payment input screen by the person in charge of the settlement processing department's terminal 400, and stores the data in the memory unit 106.

[0048] The payment settlement processing unit 102d, for example, provides a payment settlement screen in response to access from the terminals 400 of each department, and in response to operations on the payment settlement screen by the person in charge (payment settlement user) of the terminal 400 of each department, creates payment data including the payment settlement number, payment date, payee account information (payee code, payee account code), payment amount, payment settlement user, and payment type based on the payment detail data stored in the memory unit 106 at the time of payment settlement, and stores this in the memory unit 106. A payment settlement user may be able to work for multiple departments.

[0049] The transfer file creation processing unit 102e, for example, provides a transfer file creation screen in response to access from each department's terminal 400, etc., and in response to operations on the transfer file creation screen by the person in charge (payment settlement user) of each department's terminal 400, aggregates (consolidates) the payment data stored in the memory unit 106 using the specified payment date and payment type or payment settlement user as aggregation (consolidation) conditions, creates a transfer file containing transfer data including transfer identification information, specified transfer date, company account information, number of transfers, and transfer amount, and transfer detail data including transfer identification information, payee account information, and transfer amount, and stores the file in the memory unit 106.

[0050] The master maintenance unit 102f performs editing such as inputting, adding, and changing data in the management company master 106a, management company account master 106b, and company account master 106c, for example, in response to operator operations on a master maintenance screen (not shown) displayed on the monitor 114.

[0051] The screen display control unit 102g controls the display of various screens (for example, payment input screen, payment settlement screen, transfer file creation screen, master maintenance screen) that are displayed on the monitor 114 or provided to the terminals 400, etc., and the acceptance of inputs therefor.

[0052] [3. Specific examples of processing] A specific example of the processing by the control unit 102 of the transfer business support device 100 in this embodiment will be described with reference to Figures 1 to 19. Figures 2 to 19 are diagrams for explaining a specific example of the processing by the control unit 102 of the transfer business support device 100 in this embodiment.

[0053] [3-1. Overall processing] 2 is a diagram showing a processing flow for explaining an outline of the overall processing of control unit 102 of transfer business support device 100 in this embodiment. With reference to FIG. 2, an outline of the overall processing of control unit 102 of transfer business support device 100 in this embodiment will be described.

[0054] 2, the remittance calculation processing unit 102a executes the remittance calculation process (receiving agency) (step S1). Specifically, in the remittance calculation process, the remittance calculation processing unit 102a provides a payment input screen in response to access from the receiving agency department terminal 400, for example, and inputs remittance data and payment detail data in response to operations on the payment input screen by the person in charge of the receiving agency department terminal 400, and stores the data in the storage unit 106. In the remittance calculation process, receiving agency remittance information for the management company and the lessor is created.

[0055] The subrogation registration unit 102b executes the subrogation registration process (step S2). Specifically, in the subrogation registration process, the subrogation registration unit 102b provides a payment input screen in response to access from the subrogation department terminal 400, for example, and inputs subrogation data and payment detail data in response to operations on the payment input screen by the person in charge of the subrogation department terminal 400, and stores the data in the storage unit 106. In the subrogation registration process, delinquent remittance information to the management company and the lessor is created.

[0056] The settlement processing unit 102c executes the management company settlement process (step S3). Specifically, in the management company settlement process, the settlement processing unit 102c provides a payment input screen in response to access from the settlement processing department terminal 400, for example, and inputs settlement data and payment detail data in response to operations on the payment input screen by the person in charge of the settlement processing department terminal 400, and stores the data in the memory unit 106. In the management company settlement process, payment information for the outsourcing fee to the management company is created.

[0057] The payment settlement processing unit 102d executes the payment settlement process (step S4). Specifically, in the payment settlement process, the payment settlement processing unit 102d provides a payment settlement screen in response to access from each department's terminal 400, and in response to operations on the payment settlement screen by the person in charge (payment settlement user) of each department's terminal 400, creates payment data including the payment settlement number, payment date, payee account information (payee code, payee account code), payment amount, payment settlement user, and payment type based on the payment detail data stored in the memory unit 106 at the time of payment settlement, and stores the created payment data in the memory unit 106. In the payment settlement process, the payment procedure is carried out based on the payment detail data.

[0058] The transfer file creation processing unit 102e executes the transfer file creation process (step S5). Specifically, in the transfer file creation process, the transfer file creation processing unit 102e provides a transfer file creation screen in response to access from the terminals 400 of each department, and in response to operations on the transfer file creation screen by the person in charge (payment settlement user) of the terminal 400 of each department, aggregates the payment data stored in the memory unit 106 using the specified payment date and payment type or payment settlement user as aggregation conditions, creates a transfer file containing transfer data including transfer identification information, specified transfer date, company account information, number of transfers, and transfer amount, and transfer detail data including transfer identification information, payee account information, and transfer amount, and stores the file in the memory unit 106.

[0059] [3-2. Sample Data] 3 to 19 are diagrams showing sample data for explaining a specific example of the processing by control unit 102 of transfer business support device 100 in this embodiment. A specific example of the processing by control unit 102 of transfer business support device 100 in this embodiment will be explained with reference to FIGS. 3 to 19.

[0060] (Prerequisite master data) The following explanation will be given assuming that the memory unit 106 has pre-registered therein a management company master 106a as shown in Figure 3, a management company account master 106b as shown in Figure 4, a company account master 106c as shown in Figure 5, contract data as shown in Figure 6, and contract rent data as shown in Figure 7.

[0061] The management company master 106a includes items for management company code and management company name, as shown in Fig. 3. In the example shown in the figure, the first line contains the management company code "1001" and the management company name "Management Company A."

[0062] The management company account master 106b has the following fields: management company code, account code, bank, branch, deposit type, and account number, as shown in Figure 4. In the example shown in the figure, the first line contains the management company code "1001," account code "01," bank "1234," branch "001," deposit type "1: Regular," and account number "1000001."

[0063] The company's account master 106c has the following fields: payment account code, bank, branch, deposit type, and account number, as shown in Figure 5. In the example shown in the figure, the first line contains payment account code "101," bank "001," branch "001," deposit type "1: Regular," and account number "0000001."

[0064] As shown in Figure 6, the contract data has the following fields: contract number, customer name, management company code, management company name, remittance destination management company code, remittance destination management company account code, remittance destination management company code, and remittance destination management company account code. The contract number is "00001", customer name is "Contractor A", management company code is "1001", management company name is "A Co., Ltd.", remittance destination management company code is "1001", remittance destination management company account code is "01", remittance destination management company code is "-", and remittance destination management company account code is "-".

[0065] The contract rent data has the fields of contract number, expense item code, and invoice amount, as shown in Figure 7. In the example shown in the figure, the first line has contract number "00001," expense item code "10001: rent," and invoice amount "50,000 yen."

[0066] (S1: remittance calculation processing, S2: subrogation registration processing, S3: management company settlement processing) Specific examples of S1: remittance calculation processing, S2: subrogation payment registration processing, and S3: management company settlement processing will be described with reference to FIGS. 8 to 11.

[0067] FIG. 8 shows an example of remittance data, FIG. 9 shows an example of subrogation data, FIG. 10 shows an example of settlement data, and FIG. 11 shows an example of payment details data.

[0068] S1: In the remittance calculation process, remittance data for collection agency is created, and payment detail data is created and updated based on the remittance data. S2: In the subrogation payment registration process, subrogation payment data for subrogation payment is created, and payment detail data is created and updated based on the subrogation payment data. S3: In the management company settlement process, settlement data for management company settlement is created, and payment detail data is created and updated based on the settlement data.

[0069] The remittance data includes the fields of contract number, remittance number, rent month, and management company, as shown in Figure 8. In the example shown in the figure, the first line contains contract number "00001," remittance number "001," rent month "2024 / 03," and management company "1001."

[0070] As shown in Figure 9, the subrogation data has the following fields: contract number, subrogation number, rent month, management company, payment amount, and payment statement number. In the example shown in the figure, the first line contains the contract number "00001," the subrogation number "00001," the rent month "2024 / 03," the management company "1001," the payment amount "50,000 yen," and the payment statement number "4."

[0071] The settlement data includes the following fields: settlement number, settlement month, settlement management company, settlement amount, and payment statement number, as shown in Figure 10. In the example shown in the figure, the first line contains the settlement number "001," the settlement month "2024 / 03," the settlement management company "10001," the settlement amount "¥100,000," and the payment statement number "7."

[0072] As shown in Figure 11, the payment details data has the following fields: payment details number, payment type (1: collection agency, 2: subrogated payment, 3: management company settlement), remittance number, payment date, payee code, payee account code, payment item code, payment amount, and payment settlement number. Each field is as follows:

[0073] Payment statement number: Automatically numbered from 1 Payment type: Classified by the process of the originator (1: collection agency, 2: subrogation, 3: management company settlement...) Remittance number: Number assigned for each rent month and contract number during collection agency remittance calculation process Payment date: The payment date entered on the remittance calculation screen Payment destination code: If the contract data remittance destination management company code is not NULL, the remittance destination management company code; otherwise, the remittance destination management company code Payment account code: If the contract data's remittance destination management company account code is not NULL, the remittance destination management company account code; otherwise, the remittance destination management company account code Payment Item Code: Payment item code Payment amount: Contract rent data invoice amount Payment settlement number: Payment settlement number of payment data only when payment settlement processing is performed

[0074] (S4: Payment settlement processing) A specific example of the payment settlement process will be described with reference to FIGS.

[0075] (Example 1) A case where payment settlement for the collection agency portion is carried out in the collection agency department will be described with reference to Figure 12. The case where payment date: 2024 / 2 / 29, payment type: 1: collection agency, and payment user: A are specified on the payment settlement screen will be described.

[0076] Figure 12(A) shows an example of the payment details data to be processed (similar to Figure 11). Figure 12(B) shows an example of payment data created during payment settlement (the first to third lines of payment data are created).

[0077] As shown in Figure 12(B), the payment data includes the following fields: payment settlement number, payment date, payee code, payee account code, payment amount, payment settlement user ID, payment type, and transfer GUID. Each field is as follows:

[0078] Payment settlement number: Automatically numbered from 1 when processing payment settlement Payment date: Scheduled payment date of payment details data Payee code: Payee code of payment details data Payment account code: Payment account code for payment details data Payment amount: Payment amount from payment details data * Aggregated by payment date, payee, and payee account Payment settlement user ID: User ID of the person who processed the payment settlement Payment type: Payment type of payment details data Transfer GUID: A unique key for each transfer that is assigned when creating the overall transfer data

[0079] In the example shown in the figure, the first line contains the payment settlement number "100", payment date "2024 / 2 / 29", payee code "1001", payee account code "01", payment amount "50,000 yen", payment settlement user ID "A", payment type "1: Collection agency", and transfer GUID " ".

[0080] FIG. 12(C) shows an example of payment details data in which the "payment settlement number" has been updated to the "payment settlement number" of the payment data after payment settlement.

[0081] (Example 2) With reference to Figure 13, we will explain the case where the receivables management department has carried out payment settlement for the subrogated payment. We will explain the case where payment date: 2024 / 2 / 29, payment type: 2: subrogated payment, and settlement user: B are specified on the payment settlement screen.

[0082] Figure 13(A) shows an example of the payment details data to be processed (similar to the payment details data in Figure 12(C)). Figure 13(B) shows an example of payment data created during payment settlement (the payment data in lines 4 to 6 is created).

[0083] In the example shown in the same figure, the fourth line contains the payment settlement number "103", payment date "2024 / 2 / 29", payee code "1001", payee account code "01", payment amount "50,000 yen", payment settlement user ID "B", payment type "2: Subrogation payment", and transfer GUID " ".

[0084] FIG. 13(C) shows an example of payment details data in which the "payment settlement number" has been updated to the "payment settlement number" of the payment data after payment settlement.

[0085] (Example 3) With reference to Figure 14, we will explain the case where Person B, who works in both the receivables management department and the settlement department, makes a payment settlement for the management company settlement. We will explain the case where, on the payment settlement screen, payment date: 2024 / 2 / 29, payment type: 3: management company settlement, and settlement user: B are specified.

[0086] Figure 14(A) shows an example of the payment details data to be processed (similar to the payment details data in Figure 13(C)). Figure 14(B) shows an example of payment data created during payment settlement (the payment data in lines 7 to 9 is created).

[0087] In the example shown in the same figure, the 7th line contains the payment settlement number "106", payment date "2024 / 2 / 29", payee code "1001", payee account code "01", payment amount "￥100,000", payment settlement user ID "B", payment type "3: Management company settlement", and transfer GUID " ".

[0088] FIG. 14(C) shows an example of payment details data in which the "payment settlement number" has been updated to the "payment settlement number" of the payment data after payment settlement.

[0089] (S5: Transfer file creation process) A specific example of the transfer file creation process will be described with reference to Figures 15 to 19. In the creation process, a transfer file (transfer data (header data) and transfer detail data (detail data)) is created based on the payment data settled in the payment settlement process. Figure 15 shows an example of the target payment data (payment data before processing) (similar to Figure 14(B)).

[0090] (Example 1) 16 and 17, we will explain how to create a comprehensive transfer file for collection agency in the collection agency department. We will explain the case where, on the transfer file creation screen, payment date is 2024 / 2 / 29, payment type is 1: collection agency, and payment user is not specified.

[0091] Figure 16(A) shows an example of the target payment data (payment data before processing) (similar to Figure 15). Figure 16(B) shows an example of transfer data created by the transfer file creation process (the transfer data in the first line is created), and Figure 17(A) shows an example of transfer detail data created by the transfer file creation process (the transfer detail data in lines 1 to 3 is created).

[0092] As shown in Figure 16(B), the transfer data has the following fields: transfer GUID, transfer date, sending bank code, sending branch code, sending deposit type classification, sending account number, number of transfers, and transfer amount.

[0093] Transfer GUID: A unique key for each transfer that is assigned when creating the overall transfer data Transfer date: Payment date of Payment D Sending bank code: Bank code in your company's account master Sending branch bank code: Branch code of your company's account master Outgoing deposit type classification: Deposit type in company account master Sender account number: Your company's account master account number Number of transfers: Total number of transfers per transfer GUID in the comprehensive transfer details data Transfer amount: Total transfer amount for each transfer GUID in the comprehensive transfer detail data

[0094] In the example shown in the figure, the first line contains the transfer GUID "10000000-0000-0000-0000-0000000001", transfer date "2024 / 2 / 29", sending bank code "0001", sending branch code "001", outgoing deposit type classification "1: Regular", sending account number "0000001", number of transfers "3", and transfer amount "￥230,000".

[0095] As shown in Figure 17(A), the transfer details data has the following fields: transfer GUID, payee code, recipient bank code, recipient branch code, recipient deposit type classification, recipient account number, and transfer amount. Each field is as follows:

[0096] Transfer GUID: A unique key for each transfer that is assigned when creating the overall transfer data Vendor Code: Vendor code of payment data Receiving bank code: Payment data payee code, bank code of management company account M linked to the payee account code Recipient branch bank code: Payment data payee code, bank branch code of management company account M linked to the payment recipient account code Deposit type classification: Deposit type classification of management company account M linked to the payment data payee code and payee account code Receiving account number: Payment data payee code, account number of management company account M linked to the payment recipient account code Transfer amount: Total of payment amounts for the payment date, payment destination code, and payment destination account code of the payment data

[0097] In the example shown in the figure, the first line contains the transfer GUID "10000000-0000-0000-0000-0000000001", payee code "1001", recipient bank code "1234", recipient branch code "001", recipient deposit type classification "1: Regular", recipient account number "1000001", and transfer amount "50,000 yen".

[0098] FIG. 17(B) shows an example of payment data in which the "Transfer GUID" has been updated to the "Transfer GUID" of the transfer details data after the transfer file creation process.

[0099] (Example 2) 18 and 19, we will explain the case where B, a person in charge of the receivables management department, creates a comprehensive transfer file for the subrogated payment portion and the management company settlement portion. We will explain the case where, on the transfer file creation screen, payment date: 2024 / 2 / 29, payment type: not specified, and payment user: B are specified.

[0100] Figure 18(A) shows an example of the target payment data (payment data before processing) (similar to Figure 17(B)). Figure 18(B) is an example of transfer data created by the transfer file creation process (transfer data on line 2 is created), and Figure 18(C) is an example of transfer detail data created by the transfer file creation process (transfer detail data on lines 4 to 6 is created).

[0101] In the example of transfer data shown in Figure 18 (B), the second line contains the transfer GUID "10000000-0000-0000-0000-0000000002", transfer date "2024 / 2 / 29", sending bank code "0001", sending branch code "001", sending deposit type classification "1: Regular", sending account number "0000001", number of transfers "3", and transfer amount "830,000 yen".

[0102] In the example of transfer details data shown in Figure 18 (C), the fourth line contains the transfer GUID "10000000-0000-0000-0000-0000000002", payee code "1001", receiving bank code "1234", receiving branch code "001", receiving deposit type classification "1: Regular", receiving account number "1000001", and transfer amount "￥150,000".

[0103] When generating transfer detail data from payment data, it is aggregated by payee. It is aggregated by payee code and payee account code. The payee information such as bank, branch, deposit type, account number, etc. is set from the payee account code. In this example, it is aggregated by payee codes "1001", "2001", and "3001", and the transfer amount is "¥150,000 (=¥50,000 + ¥100,000)", "¥280,000 (=¥80,000 + ¥200,000)", and "¥400,000 (=¥100,000 + ¥300,000)".

[0104] FIG. 19 shows an example of payment data in which the "Transfer GUID" has been updated to the "Transfer GUID" of the transfer details data after the transfer file creation process.

[0105] As described above, according to this embodiment, when a payment occurs, there is provided a payment processing means for creating payment detail data including the payment detail number, payment type, payment date, payee account information, payment item, and payment amount for each department; a payment settlement processing unit 102d for creating payment data including the payment settlement number, payment date, payee account information, payment amount, the payment settlement user who made the payment settlement, and payment type based on the payment detail data for each department at the time of payment settlement; and a transfer file creation processing unit 102e for creating a transfer file for each department that includes transfer data including transfer identification information, specified transfer date, company account information, number of transfers, and transfer amount, and transfer detail data including transfer identification information, payee account information, and transfer amount, thereby making it possible to improve the flexibility and productivity of comprehensive transfer operations.

[0106] [4. Contribution to the United Nations-led Sustainable Development Goals (SDGs)] This embodiment can contribute to improving business efficiency and promoting appropriate management decisions by companies, thereby contributing to the achievement of SDGs Goals 8 and 9.

[0107] Furthermore, this embodiment can contribute to reducing waste and promoting paperless and electronic systems, thereby contributing to the achievement of SDGs Goals 12, 13, and 15.

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

[0109] 5. Other Embodiments The present invention may be implemented in various different embodiments other than those described above within the scope of the technical concept set forth in the claims.

[0110] For example, among the processes described in the embodiments, all or part of the processes described as being performed automatically can be performed manually, or all or part of the processes described as being performed manually can be performed automatically using known methods.

[0111] Furthermore, the processing procedures, control procedures, specific names, information including parameters such as registered data and search conditions for each process, screen examples, and database configurations shown in this specification and drawings can be changed as desired unless otherwise specified.

[0112] Furthermore, with regard to the transfer business support device 100, the components shown in the figures are functional concepts, and do not necessarily have to be physically configured as shown in the figures.

[0113] For example, all or any part of the processing functions of the transfer operation support device 100, particularly the processing functions performed by the control unit 102, may be implemented by a CPU and a program interpreted and executed by the CPU, or may be implemented as hardware using wired logic. The program is recorded on a non-transitory, computer-readable recording medium containing programmed instructions for causing the information processing device to execute the processes described in this embodiment, and is mechanically read by the transfer operation support device 100 as needed. That is, a computer program for providing instructions to the CPU in cooperation with the OS and performing various processes is recorded in a storage unit such as a ROM or HDD (Hard Disk Drive). This computer program is executed by being loaded into RAM, and cooperates with the CPU to form the control unit.

[0114] This computer program may also be stored in an application program server connected to the transfer business support device 100 via any network, and all or part of it may be downloaded as needed.

[0115] Furthermore, the program for executing the processes described in this embodiment may be stored in a non-transitory computer-readable recording medium or configured as a program product. Here, the term "recording medium" includes any "portable physical medium" such as a memory card, a Universal Serial Bus (USB) memory, a Secure Digital (SD) card, a flexible disk, a magneto-optical disk, a ROM, an Erasable Programmable Read Only Memory (EPROM), an Electrically Erasable and Programmable Read Only Memory (EEPROM (registered trademark)), a Compact Disk Read Only Memory (CD-ROM), a Magneto-Optical disk (MO), a Digital Versatile Disk (DVD), and a Blu-ray (registered trademark) disc.

[0116] Furthermore, a "program" is a data processing method written in any language or description method, regardless of the format, such as source code or binary code. Note that a "program" is not necessarily limited to a single structure, but also includes a structure that is distributed as multiple modules or libraries, or a structure that achieves its function by cooperating with a separate program, such as an OS. Note that the specific configuration and reading procedure for reading a recording medium in each device shown in the embodiments, as well as the installation procedure after reading, can use well-known configurations and procedures.

[0117] The various databases stored in the memory unit 106 are storage means such as memory devices such as RAM and ROM, fixed disk devices such as hard disks, flexible disks, and optical disks, and store various programs, tables, databases, and web page files used for various processes and providing websites.

[0118] The transfer business support 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 transfer business support device 100 may also be realized by installing software (including programs or data) that causes the device to perform the processing described in this embodiment.

[0119] Furthermore, the specific form of distribution and integration of the devices is not limited to that shown in the drawings, and all or part of them can be configured by functionally or physically distributing and integrating them in any unit depending on various additions or functional loads. In other words, the above-described embodiments can be implemented in any combination, or embodiments can be implemented selectively. [Explanation of symbols]

[0120] 100 Transfer business support device 102 Control section 102a Remittance calculation processing unit 102b Subrogation Registration Division 102c Payment Processing Unit 102d Payment settlement processing unit 102e Transfer file creation processing unit 102f Master Maintenance Department 102g Screen display control unit 104 Communication interface unit 106 Storage section 106a Management company master 106b Management company account master 106c Company Account Master 108 Input / Output Interface Section 112 Input Device 114 Output Device 300 Network 400 terminals

Claims

1. A transfer business support device equipped with a control unit, The control unit a payment processing means for creating payment statement data including a payment statement number, payment type, payment date, payee account information, payment item, and payment amount when a payment is made for each department; a payment settlement processing means for creating payment data for each department, based on the payment details data, including a payment settlement number, a payment date, payment destination account information, a payment amount, a payment settlement user who made the payment settlement, and a payment type, at the time of payment settlement; a transfer file creation processing means for aggregating the payment data for each department using payment date and payment type or payment settlement user as aggregation conditions, and creating a transfer file containing transfer data including transfer identification information, transfer date, company account information, number of transfers, and transfer amount, and transfer detail data including transfer identification information, payee account information, and transfer amount; A transfer business support device comprising:

2. 2. The transfer business support device according to claim 1, wherein the departments include a collection agency department of a rent guarantee company, a subrogation department, and a management company settlement department.

3. 3. The transfer business support device according to claim 2, wherein the payment types include collection agency, subrogation, or management company settlement.

4. 4. The transfer business support device according to claim 1, wherein the payment settlement user can hold multiple positions in multiple departments.

5. A method for supporting a transfer operation executed by an information processing device having a control unit, Executed in the control unit: a payment processing step for creating payment statement data including a payment statement number, payment type, payment date, payee account information, payment item, and payment amount when a payment is made for each department; a payment settlement processing step for creating payment data including a payment settlement number, payment date, payee account information, payment amount, payment settlement user who made the payment settlement, and payment type based on the payment detail data for each department at the time of payment settlement; a transfer file creation process for aggregating the payment data for each department using the payment date and the payment type or payment settlement user as aggregation conditions, and creating a transfer file containing transfer data including transfer identification information, transfer date, company account information, number of transfers, and transfer amount, and transfer detail data including transfer identification information, payee account information, and transfer amount; A method for supporting a transfer operation, comprising:

6. A rent guarantee management program for a bank transfer business support device to be executed by an information processing device having a control unit, The control unit a payment processing step for creating payment statement data including a payment statement number, payment type, payment date, payee account information, payment item, and payment amount when a payment is made for each department; a payment settlement processing step for creating payment data including a payment settlement number, payment date, payee account information, payment amount, payment settlement user who made the payment settlement, and payment type based on the payment detail data for each department at the time of payment settlement; a transfer file creation process for aggregating the payment data for each department using the payment date and the payment type or payment settlement user as aggregation conditions, and creating a transfer file containing transfer data including transfer identification information, transfer date, company account information, number of transfers, and transfer amount, and transfer detail data including transfer identification information, payee account information, and transfer amount; A transfer operation support program to carry out the above.

Images