Transfer commission setting device, transfer commission setting method, and transfer commission setting program

Abstract

To provide a transfer commission setting device and the like that can bill an account transfer commission by customer unit instead of by contract unit as to billing an account transfer commission to a borrower concluding a plurality of lease contracts.SOLUTION: In the present embodiment, a transfer commission setting device is configured to: (1) set account transfer commission information by customer unit upon registering customer information; (2), with reference to the account transfer commission information on the registered customer information upon preparing withdraw request data with respect to the customer, prepare billing data on the account transfer commission apart from billing data on a transfer amount such as respective rents of a lease contract of a billing object and the like; (3), with reference to the billing data on the transfer amount such as respective rents of the lease contract of the billing object and the billing data on the account transfer commission such as respective rents of the lease contract of the billing object, prepare withdraw request data adding the account transfer commission to a total amount of the transfer amount such as respective rents of the lease contract of the billing object as a withdraw request amount.SELECTED DRAWING: Figure 2

Description

[Technical Field]

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

[0002] Patent Document 1 describes a rent payment system in which a computer of a rental guarantee organization bills rent to a tenant by direct debit via a rent transfer management organization. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Laid-Open No. 2016-129045 Summary of the Invention [Problem to be solved by the invention]

[0004] Here, when a tenant rents a room, they often also rent a parking space. In such cases, separate lease agreements are concluded for the room and the parking space, resulting in two contracts for the same tenant. In such cases, if the tenant selects direct debit as the collection method for receivables, the debit request is made for both the room and the parking space combined, but because the direct debit fee is set to be charged for each individual contract, it is possible to mistakenly set the direct debit fee for each contract. Furthermore, even if the direct debit fee is set correctly, if the room contract is canceled alone, if the direct debit fee is set for the room contract, the correct direct debit fee cannot be charged unless the setting for the direct debit fee is changed to the parking space contract.

[0005] The present invention has been made in consideration of the above-mentioned problems, and aims to provide a transfer fee setting device, a transfer fee setting method, and a transfer fee setting program that can charge transfer fees to tenants who have signed multiple rental contracts on a customer-by-customer basis rather than on a contract-by-contract basis. [Means for solving the problem]

[0006] In order to solve the above-mentioned problems and achieve the object, the transfer fee setting device of the present invention is characterized by comprising: a customer registration unit that sets account transfer fee information on a customer-by-customer basis when registering customer information; a billing data creation processing unit that, when creating debit request data for a customer, references the account transfer fee information in the registered customer information and creates billing data for the account transfer fee separately from the billing data for the transfer amount for the contract to be billed; and a debit request data creation processing unit that references the billing data for the transfer amount for the contract to be billed and the billing data for the account transfer fee and creates debit request data in which the account transfer fee is added to the transfer amount for the contract to be billed as the debit request amount.

[0007] In addition, in the transfer fee setting device of the present invention, the billing data creation processing unit may refer to the account transfer fee information in the registered customer information and create billing data for the account transfer fee separately from the billing data for the transfer amount for each of the multiple contracts to be billed, and the debit request data creation processing unit may refer to the billing data for the transfer amount for each of the multiple contracts to be billed and the billing data for the account transfer fee and create debit request data that adds the account transfer fee to the total amount of the transfer amount for each of the multiple contracts to be billed as the debit request amount.

[0008] In addition, the transfer fee setting device of the present invention may further include a target contract data identification processing unit that, when creating debit request data for a customer, identifies the contract information to be billed from the customer's contract information master and extracts it as target contract data; in the transfer fee setting device of the present invention, the target contract data identification processing unit may identify a customer for whom multiple pieces of identified contract information exist as a multi-contract customer; and when the customer is a multi-contract customer, the billing data creation processing unit may create billing data for the transfer amount for the contract to be billed by referring to the target contract data, and may also create billing data for the bank transfer fee by referring separately to the bank transfer fee information in the registered customer information.

[0009] In addition, in the transfer fee setting device of the present invention, the billing data creation processing unit may create billing data for the account transfer fee using the smallest contract number in ascending order among the contract numbers of each of the multiple contracts to be billed.

[0010] In the transfer fee setting device according to the present invention, the contract to be billed may be a contract for a property, and the transfer amount for the contract to be billed may be rent.

[0011] Furthermore, in the transfer fee setting device of the present invention, when a customer has contracted for a room and a parking space, the billing data creation processing unit may create billing data for the transfer amount for the room contract, create billing data for the transfer amount for the parking space contract, and separately create billing data for the account transfer fee by referring to the account transfer fee information in the customer information registered, and the debit request data creation processing unit may create debit request data that adds the account transfer fee to the total amount of the transfer amount for the room contract and the transfer amount for the parking space contract as the debit request amount.

[0012] In addition, the transfer fee setting method of the present invention is characterized by including: a customer registration step in which a customer registration unit sets account transfer fee information on a customer-by-customer basis when registering customer information; a billing data creation processing step in which, when creating debit request data for a customer, a billing data creation processing unit references the account transfer fee information in the registered customer information and creates billing data for the account transfer fee separately from the billing data for the transfer amount for the contract to be billed; and a debit request data creation processing step in which the debit request data creation processing unit references the billing data for the transfer amount for the contract to be billed and the billing data for the account transfer fee and creates debit request data in which the account transfer fee is added to the transfer amount for the contract to be billed as the debit request amount.

[0013] In addition, the transfer fee setting program of the present invention causes an information processing device to function as a customer registration means for setting account transfer fee information on a customer-by-customer basis when registering customer information, a billing data creation processing means for creating billing data for the account transfer fee separately from the billing data for the transfer amount for the contract to be billed, by referring to the billing data for the transfer amount for the contract to be billed and the billing data for the account transfer fee, by referring to the billing data for the transfer amount for the contract to be billed and the billing data for the account transfer fee, and creating debit request data in which the account transfer fee is added to the transfer amount for the contract to be billed as the debit request amount. [Effects of the Invention]

[0014] The present invention has the effect of enabling the charge for account transfer fees to be billed to tenants who have concluded multiple rental contracts to be billed on a customer-by-customer basis rather than on a contract-by-contract basis. [Brief explanation of the drawings]

[0015] [Figure 1] FIG. 1 is a block diagram showing an example of the configuration of a transfer fee setting device. [Figure 2]FIG. 2 is a diagram showing an example of the customer registration master, the contract information master, the billing data, and the withdrawal request data. [Figure 3] FIG. 3 is a diagram illustrating an example of a customer registration process. [Figure 4] FIG. 4 is a diagram showing an example of the lease contract input process. [Figure 5] FIG. 5 is a diagram illustrating an example of the target contract data specifying process. [Figure 6] FIG. 6 is a diagram illustrating an example of the billing data creation process. [Figure 7] FIG. 7 is a diagram showing an example of the withdrawal request data creation process. DETAILED DESCRIPTION OF THE INVENTION

[0016] Hereinafter, embodiments of a transfer fee setting device, a transfer fee setting method, and a transfer fee setting 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.

[0017] [1. Configuration] An example of the configuration of the transfer fee setting device 100 according to this embodiment will be described with reference to Fig. 1 etc. Fig. 1 is a block diagram showing an example of the configuration of the transfer fee setting device 100.

[0018] Transfer fee setting device 100 is constructed based on a commercially available desktop personal computer. Note that transfer fee setting device 100 is not limited to being constructed based on a stationary information processing device such as a desktop personal computer, but may also be constructed based on a portable information processing device such as a commercially available notebook personal computer, PDA (Personal Digital Assistant), smartphone, or tablet personal computer.

[0019] The transfer fee setting 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 of the transfer fee setting device 100 are connected to each other so that they can communicate with each other via any communication path.

[0020] The communication interface unit 104 communicably connects the transfer fee setting device 100 to the network 300 via a communication device such as a router and a wired or wireless communication line such as a dedicated line. The communication interface unit 104 has a function of communicating data with other devices via a communication line. Here, the network 300 has a function of connecting the transfer fee setting 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). The data stored in the memory unit 106 may also be stored in the server 200, for example.

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

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

[0023] The storage unit 106 stores a customer registration master 106a, a contract information master 106b, billing data 106c, and withdrawal request data 106d.

[0024] An example of information stored in the customer registration master 106a is shown in Figure 2. The customer registration master 106a is used to manage registration information (customer information) related to customers. As shown in Figure 2, the customer registration master 106a stores the customer code (e.g., customer identification number, customer name, etc.), debit account, bank, branch, deposit type, account number, account holder name in kana, new category, customer number, fee category, fee amount, etc.

[0025] An example of information stored in the contract information master 106b is shown in Fig. 2. The contract information master 106b is used to manage customer contract information. As shown in Fig. 2, the contract information master 106b stores the property code, property name (e.g., apartment name, parking lot name, etc.), NO (e.g., room number, parking space number, etc.), contract number, customer code, status (e.g., canceled, currently occupied, etc.), contract period (e.g., start date of contract, etc.), termination (e.g., end date of contract, etc.), rent, cancellation date (only in the case of cancellation), etc.

[0026] An example of information stored in the billing data 106c is shown in Figure 2. The billing data 106c is used to manage information related to billing to customers (for example, billing for rent, etc.). As shown in Figure 2, the billing data 106c stores the contract number, customer code, billing year and month (for example, the month in which the billing is made), the relevant month (for example, the month in the contract period that corresponds to the billing year and month), item (for example, rent, account debit fee, etc.), amount, etc.

[0027] An example of information stored in the debit request data 106d is shown in Figure 2. The debit request data 106d is used to manage information related to debit requests from customer accounts (e.g., bank accounts, etc.). As shown in Figure 2, the debit request data 106d stores the main contract number, bank, branch, deposit type, account number, account holder name in kana, new classification, customer number, debit request amount, etc.

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

[0029] The control unit 102 conceptually includes a customer registration unit 102a, a lease contract input unit 102b, a target contract data identification processing unit 102c, a billing data creation processing unit 102d, and a debit request data creation processing unit 102e.

[0030] When the customer registration unit 102a receives input of registration information (customer information) related to a customer, it stores the registration information in the customer registration master 106a of the storage unit 106. For example, the customer registration unit 102a adds a record of the input registration information related to the customer to a database table of the customer registration master 106a. Alternatively, the customer registration unit 102a may obtain the registration information via the network 300 from an external server 200 that manages registration information related to customers, align the data format, and store the information in the customer registration master 106a of the storage unit 106. In this embodiment, the customer registration unit 102a sets account transfer fee information for each customer when registering customer information.

[0031] When the lease contract input unit 102b accepts input of customer contract information, it stores the contract information in the contract information master 106b of the storage unit 106. For example, the customer registration unit 102a adds a record of the input customer contract information to a database table of the contract information master 106b. Alternatively, the customer registration unit 102a may obtain the contract information via the network 300 from an external server 200 that manages customer contract information, align the data format, and store the information in the contract information master 106b of the storage unit 106.

[0032] The target contract data identification processing unit 102c identifies contract information that is the subject of billing among the customer's contract information from the contract information master 106b and extracts it as target contract data 106b'. The target contract data 106b' is temporary data (intermediate data) used for internal processing. However, in reality, the target contract data identification processing unit 102c may store the target contract data 106b' in the storage unit 106. The target contract data identification processing unit 102c may also identify a customer for whom there are multiple identified contracts (two or more contracts) as a multiple-contract customer (a lessee who has concluded multiple rental contracts). The target contract data identification processing unit 102c may enable the function of this embodiment and process a deduction request (a deduction request for multiple contracts) according to this embodiment only if the customer is a multiple-contract customer, and may control the processing to process a conventional deduction request (a deduction request for a single contract) if the customer is not a multiple-contract customer. In this embodiment, when creating the withdrawal request data 106d for a customer, the target contract data identification processing unit 102c identifies contract information to be billed from the customer's contract information master 106b and extracts it as target contract data 106b'. In addition, the target contract data identification processing unit 102c identifies a customer for whom multiple pieces of identified contract information exist as a multiple-contract customer.

[0033] The billing data creation processing unit 102d creates billing data 106c based on the customer registration master 106a and the target contract data 106b'. The billing data creation processing unit 102d then stores the billing data 106c in the storage unit 106. In this embodiment, when creating the debit request data 106d for a customer, if the customer has multiple contracts, the billing data creation processing unit 102d references the account transfer fee information in the registered customer information and creates billing data 106c for the account transfer fee separately from the billing data 106c for the transfer amount for each of the multiple contracts to be billed.

[0034] The debit request data creation processing unit 102e creates debit request data 106d based on the customer registration master 106a and the billing data 106c. Then, the debit request data creation processing unit 102e stores the debit request data 106d in the storage unit 106. The debit request data creation processing unit 102e also outputs the debit request data 106d. In this embodiment, the debit request data creation processing unit 102e references the billing data 106c of the transfer amount for the contract to be billed and the billing data 106c of the account transfer fee, and creates debit request data 106d that adds the account transfer fee to the total amount of the transfer amounts for each of the multiple contracts to be billed as the debit request amount.

[0035] [2. Specific examples of processing] Here, specific examples of processing executed by the transfer fee setting device 100 will be described with reference to Figs. 3 to 7. Fig. 3 is a diagram showing an example of customer registration processing. Fig. 4 is a diagram showing an example of lease contract input processing. Fig. 5 is a diagram showing an example of target contract data identification processing. Fig. 6 is a diagram showing an example of billing data creation processing. Fig. 7 is a diagram showing an example of debit request data creation processing.

[0036] First, as shown in FIG. 3, the customer registration unit 102a displays a UI (User Interface) for customer registration on a monitor serving as the output device 114, and when it receives input of registration information about a customer from an operator or the like via the input device 112, it stores the registration information in the customer registration master 106a.

[0037] For example, as shown in FIG. 3, the customer registration unit 102a accepts input of information such as customer code "0000000001," debit destination account "debit destination bank," debit source account bank "●● Bank," branch "△ Branch," deposit type "regular," account number "0123456," account holder name in kana "Obic Taro," new category "new," customer number "00000000000001000010," fee category "1: required," and fee amount "200" as registration information related to the customer, and stores this information in association with the customer registration master 106a.

[0038] In practice, the customer registration unit 102a may obtain the registration information via the network 300 from an external server 200 that manages registration information relating to customers, and store the information in the customer registration master 106a.

[0039] Next, as shown in FIG. 4, when the lease contract input unit 102b receives input of the contract information of the customer, it stores the contract information in the contract information master 106b.

[0040] 4, the lease contract input unit 102b associates the following customer contract information into the customer registration master 106a: property code "0000000010," property name "Obic Heights," NO "101," contract number "1000000001," customer code "20000000001 Obic Taro," status "cancellation," contract period "2022 / 01 / 01," expiration date "2023 / 12 / 31," rent "200,000," and cancellation date "2023 / 01 / 10." In other words, the customer canceled the contract for Room 101 in Obic Heights on January 10, 2023.

[0041] As shown in FIG. 4, the lease contract input unit 102b associates the property name "Obic Heights," the number "102," the contract number "1000000002," the customer code "20000000001 Obic Taro," the status "occupied," the contract period "2022 / 02 / 01," the expiration date "2024 / 2 / 28," and the rent "200,000" with the same property code "0000000010," and stores these in the customer registration master 106a. Because this is not a cancellation, the cancellation date field is left blank. In other words, the customer (the same customer as above) has also signed a contract for Room 102 in Obic Heights and is currently residing there.

[0042] 4, the lease contract input unit 102b associates the property name "OBIC Parking Lot," NO "201," contract number "1000000003," customer code "20000000001 OBIC Taro," status "occupied," contract period "2022 / 03 / 01," expiration date "2024 / 3 / 31," and rent "100,000" with the same property code "0000000010," and stores these in the customer registration master 106a. Because this is not a cancellation, the cancellation date field is left blank. In other words, the customer (the same customer as above) has also contracted for space number 201 in the OBIC Parking Lot and is currently occupying (using) it.

[0043] In practice, the lease contract input unit 102b may acquire the contract information from an external server 200 that manages customer contract information via the network 300 and store the contract information in the contract information master 106b.

[0044] Next, as shown in Figure 5, when the debit request data creation process is started, the target contract data identification processing unit 102c displays a UI for specifying (or inputting) the target remittance month on the monitor serving as the output device 114, and when it receives the specification of the target remittance month from an operator or the like via the input device 112, it identifies the contract information corresponding to the target remittance month from the contract information master 106b and extracts it as target contract data 106b'.

[0045] For example, as shown in Figure 5, when the target remittance month and year "February 2024" is specified, the target contract data identification processing unit 102c identifies two currently occupied contracts that are subject to the target remittance month and year from the contract information stored in the contract information master 106b and extracts them as target contract data 106b'. In the example of Figure 5, the target contract data identification processing unit 102c extracts the first data of NO "102", contract number "1000000002", customer code "20000000001 Obic Taro", status "occupied", contract period "2022 / 02 / 01", end date "2024 / 2 / 28", and rent "200,000", and the second data of NO "201", contract number "1000000003", customer code "20000000001 Obic Taro", status "occupied", contract period "2022 / 03 / 01", end date "2024 / 3 / 31", and rent "100,000" as the target contract data 106b'.

[0046] Here, the target contract data identification processing unit 102c may identify a customer for whom there are multiple identified contract information (two or more contracts) as a multiple-contract customer (a lessee who has concluded multiple rental contracts).The target contract data identification processing unit 102c may then enable the function according to this embodiment and perform the subsequent processing only if the customer is a multiple-contract customer, and may control the processing to carry out the usual debit request (debit request for one contract) that has been conventionally performed if the customer is not a multiple-contract customer.

[0047] Next, as shown in FIG. 6, the billing data creation processing unit 102d creates billing data 106c based on the customer registration master 106a and the target contract data 106b'.

[0048] At this time, the billing data creation processing unit 102d creates billing data for the direct debit fee as newly created data by referring to the fee amount set in the customer registration for the smallest contract number (youngest contract number) in ascending order of the contracts (targeting the current occupancy) linked to the customer. In this embodiment, since it is assumed that the room contract is entered first when registering into the system, the billing data for the direct debit fee is created using the smallest contract number in ascending order of the contract numbers of the billing data for the current occupancy.

[0049] For example, if a customer has contracted for both a room and a parking space, the room contract information is registered first, so the smallest contract number in ascending order becomes the room contract number. Generally, room contract numbers tend to be less likely to change due to cancellation than parking space contract numbers and are more stable. Furthermore, if all occupied room contracts are canceled and only the parking space contract remains, there is no problem as the parking space contract number will become the smallest contract number in ascending order.

[0050] For example, as shown in FIG. 6, billing data 106c stores, in association with each other, contract number "1000000002," customer code "20000000001 Obic Taro," billing year and month "2024 / 2," applicable month "2024 / 2," item "rent," and amount "200,000."

[0051] As shown in FIG. 6, the billing data 106c stores the contract number "1000000003," the customer code "20000000001 Obic Taro," the billing year and month "2024 / 2," the relevant month "2024 / 2," the item "rent," and the amount "100,000," in association with each other.

[0052] 6, the billing data 106c stores, as newly created data, the contract number "1000000002," the customer code "20000000001 Obic Taro," the billing year and month "2024 / 2," the relevant month "2024 / 2," the item "direct debit fee," and the amount "200," all associated with each other. The amount "200" is data obtained from the fee amount "200" in the customer registration master 106a. In other words, the amount "200" in the billing data 106c is the same as the fee amount "200" in the customer registration master 106a.

[0053] 7, the debit request data creation processing unit 102e creates debit request data 106d based on the customer registration master 106a and the billing data 106c. In this embodiment, the debit request data creation processing unit 102e aggregates the billing data 106c by customer number to create the debit request data 106d.

[0054] For example, as shown in Figure 7, the withdrawal request data 106d stores, in association with each other, the main contract number "1000000002," the bank "●● Bank," the branch "△ Branch," the deposit type "Regular," the account number "0123456," the account holder name in kana "Obic Taro," the new classification "New," the customer number "00000000000001000010," and the withdrawal request amount "300,200."

[0055] The representative contract number "1000000002" is the smallest contract number, "1000000002," in ascending order among the contract numbers of the billing data currently in use in the billing data 106c. The bank "●● Bank," branch "△ Branch," deposit type "Regular," account number "0123456," account holder name in kana "Obic Taro," new account classification "New," and customer number "00000000000001000010" are data obtained from the customer registration master 106a and are therefore identical to the data stored in the customer registration master 106a. The requested withdrawal amount "300,200" is the sum of the amounts "200,000," "100,000," and "200" in the billing data 106c.

[0056] The debit request data creation processing unit 102e may also output the debit request data 106d. For example, the debit request data creation processing unit 102e may output (transmit) the debit request data 106d to a terminal device or server of the bank (or its branch) of the debit source account via the network 300. The debit request data creation processing unit 102e may also output the debit request data 106d to the output device 114. The debit request data creation processing unit 102e may also output the debit request data 106d to the server 200 via the network 300.

[0057] As described above, according to this embodiment, it is possible to set account transfer fee information on a customer-by-customer basis. Because there is only one tenant even if there are multiple contracts, setting the account transfer fee on a tenant (customer) basis rather than on a contract-by-contract basis makes it possible to avoid duplicate billing of account transfer fees to the same tenant (customer). This makes it possible to set the collection method for monthly rent and other receivables from tenants (customers) as "direct debit," and to correctly bill the company's account transfer fees.

[0058] Furthermore, according to this embodiment, the account transfer fee information in the registered customer information is referenced, and the debit request data creation process creates billing data for the account transfer fee separately from the billing data for the transfer amount for the contract to be debited, and the account transfer fee can be added to the transfer amount for the contract to be debited as the debit request amount.

[0059] In the above explanation of this embodiment, a lease contract in the rental housing industry is used as an example, but in reality, the present invention can be applied to any business or industry that conducts direct debit operations, regardless of the industry or type of contract.

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

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

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

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

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

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

[0066] Furthermore, with regard to the transfer fee setting device 100, the components shown in the figures are functional concepts, and the device does not necessarily have to be physically configured as shown in the figures.

[0067] For example, all or any part of the processing functions of the transfer fee setting device 100, particularly the processing functions performed by the control unit, 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 fee setting device 100 as needed. That is, a computer program is recorded in a storage unit such as a ROM or HDD (Hard Disk Drive) for working with the OS to issue instructions to the CPU and perform various processes. This computer program is executed by being loaded into RAM, and works with the CPU to form the control unit.

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

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

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

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

[0072] Transfer fee setting device 100 may be configured as an information processing device such as a known personal computer or workstation, or may be configured as such an information processing device connected to any peripheral device. Transfer fee setting 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.

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

[0074] The present invention is useful in the rental housing industry and in industries and sectors that conduct direct debit services. [Explanation of symbols]

[0075] 100 Transfer fee setting device 102 Control section 102a Customer Registration Department 102b Rental contract input section 102c Target contract data specific processing section 102d Billing data creation processing unit 102e Withdrawal request data creation processing unit 104 Communication interface unit 106 Storage section 106a Customer registration master 106b Contract information master 106c Billing Data 106d Withdrawal request data 108 Input / Output Interface Section 112 Input Device 114 Output Device 200 servers 300 Network

Claims

1. a customer registration unit that sets account transfer fee information for each customer when registering customer information; a billing data creation processing unit that, when creating debit request data for a customer, references the account transfer fee information in the registered customer information and creates billing data for the account transfer fee separately from the billing data for the transfer amount for the contract to be billed; a debit request data creation processing unit that references the billing data for the transfer amount for the contract to be billed and the billing data for the account transfer fee, and creates debit request data that adds the account transfer fee to the transfer amount for the contract to be billed as a debit request amount; A transfer fee setting device comprising:

2. the billing data creation processing unit references the account transfer fee information in the registered customer information and creates billing data for the account transfer fee separately from the billing data for the transfer amount for each of the multiple billing target contracts; The debit request data creation processing unit references the billing data of the transfer amount for each of the plurality of contracts to be billed and the billing data of the account transfer fee, and creates debit request data that adds the account transfer fee to the total amount of the transfer amount for each of the plurality of contracts to be billed as the debit request amount.

2. The transfer fee setting device according to claim 1.

3. The system further includes a target contract data identification processing unit that, when creating debit request data for a customer, identifies contract information to be billed from among the contract information of the customer from the contract information master and extracts it as target contract data, The target contract data identification processing unit identifies a customer for whom there are multiple pieces of identified contract information as a multiple contract customer, When the customer has multiple contracts, the billing data creation processing unit creates billing data for the transfer amount for the contract to be billed by referring to the target contract data, and also creates billing data for the account transfer fee by referring to the account transfer fee information in the customer information registered separately.

2. The transfer fee setting device according to claim 1.

4. The billing data creation processing unit creates billing data for the account transfer fee using the smallest contract number in ascending order among the contract numbers of the contracts to be billed.

2. The transfer fee setting device according to claim 1.

5. The contract that is the subject of the claim is a property contract, The transfer amount for the contract to be billed is the rent.

2. The transfer fee setting device according to claim 1.

6. The billing data creation processing unit creates billing data for the transfer amount for the room contract when the customer has contracted for a room and a parking lot, creates billing data for the transfer amount for the parking lot contract, and also creates billing data for the account transfer fee by referring to the account transfer fee information in the customer information registered separately, The debit request data creation processing unit creates debit request data that adds the account transfer fee to the total amount of the transfer amount for the room contract and the transfer amount for the parking contract as the debit request amount.

6. The transfer fee setting device according to claim 5.

7. a customer registration step in which a customer registration unit sets account transfer fee information for each customer when registering customer information; a billing data creation processing step in which, when creating debit request data for a customer, a billing data creation processing unit references the account transfer fee information in the registered customer information and creates billing data for the account transfer fee separately from the billing data for the transfer amount for the contract to be billed; a debit request data creation processing step in which a debit request data creation processing unit references the billing data for the transfer amount for the contract to be billed and the billing data for the account transfer fee, and creates debit request data that adds the account transfer fee to the transfer amount for the contract to be billed as the debit request amount; A transfer fee setting method comprising:

8. An information processing device a customer registration means for setting account transfer fee information for each customer when registering customer information; a billing data creation processing means for creating billing data for the account transfer fee separately from the billing data for the transfer amount for the contract to be billed, by referring to the account transfer fee information in the registered customer information when creating debit request data for the customer; a debit request data creation processing means for creating debit request data by referring to the billing data for the transfer amount for the contract to be billed and the billing data for the account transfer fee, and adding the account transfer fee to the transfer amount for the contract to be billed as the debit request amount; Transfer fee setting program to function as.

Images