Business support apparatus, business support method, and business support program

Abstract

To simplify remittance operations in a collection agency service and enable flexible handling for desired remittance destinations.SOLUTION: A determination part refers to a contract allocation remittance cost item storage part in which allocation target cost items, which are cost items to be remitted to other remittance destinations, are set for each contractor, and determines whether or not an allocation target cost item to be remitted to another remittance destination exists among cost items of money received from a contractor in a collection agency service. A remittance data generation part refers to a contract data storage part in which, for each contractor, allocation remittance destination information indicating another remittance destination to which money of the allocation target cost item is remitted, and normal remittance destination information indicating a remittance destination of money of a normal remittance cost item, which is a cost item other than the allocation target cost item, are set. When an allocation target cost item exists, the remittance data generation part generates remittance data including contractor information for identifying the contractor, a remittance amount of the allocation target cost item, and a remittance amount of the normal remittance cost item. When no allocation target cost item exists, the remittance data generation part generates remittance data including contractor information for identifying the contractor and a remittance amount of the normal remittance cost item.SELECTED DRAWING: Figure 1

Description

[Technical Field]

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

[0002] Today, for example, in the rental debt guarantee industry, collection agency services involve the transfer of rental fees on a management company basis and on an account basis.

[0003] As background technology relating to collection agency services, Patent Document 1 (JP Patent Publication No. 2023-171370) discloses an information processing device that makes it possible to improve the convenience of users who send money cashlessly.

[0004] Paragraph 0048 of Patent Document 1 discloses a technology in which an information processing device, based on remittance destination identification information, refers to information such as "remittance destination," "remittance destination display name," "deduction flag," "deduction content / corresponding system," "remittance amount," "per unit setting," and "per unit amount" associated with the remittance destination identification information from a remittance destination database, and obtains the name of the remittance destination, the remittance destination display name, information indicating whether the remittance destination is subject to the deduction system, the remittance amount, etc.

[0005] Furthermore, paragraph 0081 of Patent Document 1 states that the service information database stores information about the services used by service users who are businesses (corporations) such as companies and organizations that use corporate accounts, and that the services include payment services (collection agency services) that become available by entering into an affiliated store contract. [Prior art documents] [Patent documents]

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

[0007] In actual remittance operations in collection agency services, different remittance destinations are often specified for each product and contract. However, because the system can only process remittances on a management company or account basis, it is difficult to remit to different designated remittance destinations using the system. In such cases, manual remittances outside the system, EUC (End User Computing), or data maintenance are often required, making remittance operations extremely complicated.

[0008] Although there are such problems, it is also desirable to be able to flexibly respond to desired remittance destinations.

[0009] The present invention has been made in consideration of the above-mentioned problems, and aims to provide a business support device, a business support method, and a business support program that simplify the remittance operations of collection agency services and enable flexible response to desired remittance destinations. [Means for solving the problem]

[0010] In order to solve the above-mentioned problems and achieve the object, the business support device according to the present invention, when remitting money collected from a contractor through a collection agency to a remittance destination, refers to a contract allocation remittance item storage unit in which allocation target items, which are items to be remitted to other remittance destinations, are set for each contractor, and determines whether or not there are any allocation target items to be remitted to other remittance destinations among the items of money collected from the contractor; and stores allocation remittance destination information indicating other remittance destinations to which money of the allocation target items will be remitted, and a remittance destination for money of normal remittance items, which are items other than the allocation target items. The system has a remittance data generation unit that references a contract data storage unit set for each contractor for the normal remittance destination information indicated, and if the discrimination unit determines that there is an item to be allocated, generates remittance data including contractor information for identifying the contractor, the remittance amount for the item to be allocated, and the remittance amount for the normal remittance item, and if the discrimination unit determines that there is no item to be allocated, generates remittance data including contractor information for identifying the contractor and the remittance amount for the normal remittance item, and an output control unit that outputs the generated remittance data to an output target.

[0011] In order to solve the above-mentioned problems and achieve the object, the business support method according to the present invention includes a determination step in which, when remitting money collected from a contractor by collection agency to a remittance destination, a determination unit refers to a contract allocation remittance item storage unit in which allocation target items, which are items to be remitted to other remittance destinations, are set for each contractor, and determines whether or not there are any allocation target items to be remitted to other remittance destinations among the items of money collected from the contractor; and a remittance data generation unit stores allocation remittance destination information indicating other remittance destinations to which money of the allocation target items will be remitted, and a remittance destination for money of normal remittance items, which are items other than the allocation target items. The method has a remittance data generation step of referring to a contract data storage unit set for each contractor for normal remittance destination information indicating the normal remittance destination, and if it is determined in the determination step that an item to be allocated exists, generating remittance data including contractor information for identifying the contractor, the remittance amount of the item to be allocated, and the remittance amount of the normal remittance item, and if it is determined in the determination step that an item to be allocated does not exist, generating remittance data including contractor information for identifying the contractor and the remittance amount of the normal remittance item; and an output control step in which an output control unit outputs the generated remittance data to an output target.

[0012] In order to solve the above-mentioned problems and achieve the object, the business support program of the present invention includes a computer that, when remitting money collected from a contractor through a collection agency to a remittance destination, refers to a contract-assigned remittance item storage unit in which allocation-targeted expense items, which are expense items to be remitted to other remittance destinations, are set for each contractor, and determines whether or not there are any allocation-targeted expense items to be remitted to other remittance destinations among the expense items of money collected from the contractor; and a determination unit that stores allocation-targeted remittance destination information indicating other remittance destinations to which money of the allocation-targeted expense items will be remitted, and a determination unit that stores information on the amount of ordinary remittance items, which are expense items other than the allocation-targeted expense items. The normal remittance destination information indicating the remittance destination of money is referenced to a contract data storage unit set for each contractor, and if the discrimination unit determines that an item to be allocated exists, it generates remittance data including contractor information for identifying the contractor, the remittance amount of the item to be allocated, and the remittance amount of the normal remittance item, and if the discrimination unit determines that an item to be allocated does not exist, it functions as a remittance data generation unit that generates contractor information for identifying the contractor and remittance data including the remittance amount of the normal remittance item, and an output control unit that outputs the generated remittance data to an output target. [Effects of the Invention]

[0013] The present invention can simplify the remittance operations of a collection agency service and can flexibly accommodate desired remittance destinations. [Brief explanation of the drawings]

[0014] [Figure 1] FIG. 1 is a block diagram illustrating a hardware configuration of a task assistance device according to an embodiment. [Figure 2] FIG. 2 is a diagram showing an example of a management company master table that stores the code and name of the management company or lessor to which rent collected from the lessee (contractor) is to be remitted. [Figure 3] FIG. 3 is a diagram showing an example of a management company account master table that stores bank account information for each management company and lessor to which remittance is to be made. [Figure 4]FIG. 4 is a diagram showing an example of a contract data storage unit that stores contract data indicating the remittance destinations of the normal remittance expense items and the apportionment target expense items collected from each real estate contract holder. [Figure 5] FIG. 5 is a diagram showing an example of a contract rent data storage unit that stores the billing amount for each expense item for each contract number. [Figure 6] FIG. 6 is a diagram showing an example of a contract allocation remittance item storage unit in which allocation target items for contracts with each contract number are stored. [Figure 7] FIG. 7 is a diagram for explaining the management company registration process and contract input process of the business support device according to the embodiment. [Figure 8] FIG. 8 is a diagram for explaining the remittance calculation process and the payment settlement process of the business support device according to the embodiment. [Figure 9] FIG. 9 is a diagram showing an example of remittance data generated by the remittance data generation unit. [Figure 10] FIG. 10 is a diagram illustrating an example of payment data generated by the payment data generating unit. DETAILED DESCRIPTION OF THE INVENTION

[0015] The following describes in detail, with reference to the drawings, an embodiment of a business support device, which is an example of application of the present invention to a terminal device of a collection agency service company that provides collection agency services for real estate business such as rent. Note that the present invention may also be applied to a terminal device for a collection agency service for money other than real estate business, and is not limited to the following embodiment.

[0016] (Hardware configuration) As shown in Fig. 1, the business support device 1 of the embodiment includes a storage unit 2, a control unit 3, a communication interface unit 4, and an input / output interface unit 5. An input device 6 and an output device 7 are connected to the input / output interface unit 5. The output device 7 corresponds to a display unit such as a monitor device (including a home television), a printing device, or a speaker device. The input device 6 may be a keyboard device, a mouse device, a microphone device, or a monitor device that cooperates with a mouse device to realize a pointing device function.

[0017] The communication interface unit 4 is connected to a network such as a wide area network like the Internet or a private network like a LAN (Local Area Network). A bank terminal device 51 of a real estate lease contract holder (contractor) is connected to the network 50.

[0018] Also connected to network 50 is bank terminal device 52, which is the remittance destination of money collected from policyholders for remittance-targeted expense items, which are expense items for which other remittance destinations are specified. Also connected to network 50 is bank terminal device 53, which is the remittance destination of money collected from policyholders for normal remittance items, which are expense items other than the remittance-targeted expense items described above. Control unit 3 (communication control unit 21) of business support device 1 is capable of communicating with these bank terminal devices 51 to 53 via communication interface unit 4.

[0019] The storage unit 2 may be, for example, a storage device such as a read only memory (ROM), a random access memory (RAM), a hard disk drive (HDD), or a solid state drive (SSD).

[0020] The memory unit 2 stores a business support program that simplifies the remittance operations of the collection agency service and allows for flexible support of desired remittance destinations. The memory unit 2 also has a management company master table 11, a management company account master table 12, a contract data memory unit 13, and a contract rent data memory unit 14, which are memory areas. The memory unit 2 also has a contract allocation remittance item memory unit 15, a remittance data memory unit 16, and a payment data memory unit 17, which are memory areas.

[0021] The management company master table 11 stores the codes and names of the management companies or lessors to which rent collected from lessees (contractors) is remitted, as shown in Figure 2. The example in Figure 2 shows that the management company name for the management company code "1001" is "A Co., Ltd.", and the management company name for the management company code "2001" is "B Co., Ltd." It also shows that the management company code "3001" is set for "Lorcerer A."

[0022] The management company account master table 12 stores bank account information for each management company and each lessor to which remittances are to be made, as shown in Figure 3. Specifically, the management company account master table 12 stores the account code, bank code, branch code, deposit type, and account number in association with each of the management company codes mentioned above.

[0023] The example in Figure 3 shows that "Co., Ltd.", with a management company code of "1001," has two banks set as banks for remittance: a bank with an account code of "01" and a bank with an account code of "02." Note that three or more bank accounts may be set up for one management company, etc.

[0024] The bank with account code "01" is a bank with bank code "1234" and branch code "001." The deposit type of this bank account is "1: Regular deposit" and the account number is "1000001." In contrast, the bank with account code "02" is a bank with bank code "2345" and branch code "002." The deposit type of this bank account is "1: Regular deposit" and the account number is "1000002."

[0025] Similarly, the example in Figure 3 shows that "Corporation B," with a management company code of "2001," has two banks set as remittance banks: a bank with account code "01" and a bank with account code "02." The bank with account code "01" has a bank code of "3456" and a branch code of "001." The example also shows that the deposit type of this bank account is "1: Regular Deposit" and the account number is "1000003." In contrast, the bank with account code "02" has a bank code of "3456" (the same bank as the bank with account code "01") and a branch code of "002." The example also shows that the deposit type of this bank account is "1: Regular Deposit" and the account number is "9000003."

[0026] The example in Figure 3 also shows that for "Lessor A" with a management company code of "3001," the bank for remittances has been set with an account code of "01" and a bank code of "5678." The branch code for this bank is "003," the deposit type is "1: Regular Deposit," and the account number is "1000004."

[0027] As shown in Figure 4, the contract data storage unit 13 stores, for each management company, bank account information to which the money for the above-mentioned normal remittance items will be transferred, and bank account information to which the money for the above-mentioned apportionment items will be transferred, out of the rent collected from each real estate contract holder.

[0028] Specifically, the contract data storage unit 13 stores the contract number, customer name, management company, regular remittance destination information, and remittance destination information, each associated with the other. The regular remittance destination information includes the remittance destination management company code and remittance destination management company account code to which money for regular remittance items is remitted. The remittance destination information includes the remittance destination management company code and remittance destination management company account code to which money for remittance-targeted items is remitted.

[0029] In the example of Figure 4, the contract data with contract number "0001" is the contract data for "A Co., Ltd." with management company code "1001," and the contract data indicates that the rent collected from "Contractor A" and the regular remittance expense item will be remitted to the bank account with account code "01" of management company "1001" (Figure 3: bank code "1234," branch code "001," deposit type "1: Regular deposit," account number "1000001").

[0030] In addition, the contract data with contract number "0001" indicates that the rent collected from "Contractor A" and the amount of the apportioned expenses will be transferred to the bank account with account code "01" of Lessor A "3001" (Figure 3: bank code "5678", branch code "003", deposit type "1: Regular deposit", account number "1000004").

[0031] The contract data for this contract number "0001" indicates that, of the rent collected from "Contractor A," the money for the regular remittance item will be remitted to the bank with the bank code "1234" of Co. A, and the money for the apportionment item will be remitted to the bank with the bank code "5678" of Lessor A.

[0032] Also, in the example of Figure 4, the contract data with contract number "0002" is contract data for "Co., Ltd." with management company code "1001," and the contract data indicates that the money for regular remittance expenses out of the rent collected from "Contractor B" will be remitted to the bank account with account code "02" of management company "1001" (Figure 3: bank code "2345," branch code "002," deposit type "1: ordinary deposit," account number "1000002").

[0033] In addition, since the rent collected from "Contractor B" does not include any money for items subject to allocation, the allocation remittance destination information is not set for the contract data with contract number "0002." In other words, the rent collected from "Contractor B" will only be remitted to the bank account of Company A at bank "2345."

[0034] Also, in the example of Figure 4, the contract data with contract number "0003" is contract data for "Co., Ltd." with management company code "2001," and the contract data indicates that the money for regular remittance expenses out of the rent collected from "Contractor C" will be remitted to the bank account with account code "01" of the management company "2001" (Figure 3: bank code "3456," branch code "001," deposit type "1: ordinary deposit," account number "1000003").

[0035] Furthermore, the contract data with contract number "0003" indicates that the rent collected from "Contractor C" and the amount of the apportioned expenses will be transferred to the bank account with account code "02" of the management company "2001" (Figure 3: bank code "3456", branch code "002", deposit type "1: Regular deposit", account number "9000003").

[0036] This contract data with contract number "0003" indicates that, of the rent collected from "Contractor C," the money for the regular remittance item will be transferred to the bank account of Co., Ltd. B with bank code "3456" and branch code "001," while the money for the allocation item will be transferred to the bank account of Co., Ltd. B with bank code "3456" and branch code "002." In other words, although the bank is the same Co., Ltd. B with bank code "3456," the money for the regular remittance item will be transferred to the bank account with branch code "001," while the money for the allocation item will be transferred to the bank account with branch code "002."

[0037] The contract rent data storage unit 14 stores the billing amount for each expense item for each contract number, as shown in Figure 5. The example in Figure 5 shows that the breakdown of the money collected from Contractor A, whose contract number is "00001", is as follows: "Rent" with expense item code "10001" is "100,000 yen", "Common area fee" with expense item code "10002" is "5,000 yen", and "Management fee" with expense item code "10003" is "3,000 yen".

[0038] In addition, the example in Figure 5 shows that the breakdown of the money collected from Contractor B, whose contract number is "00002," is "Rent" with expense item code "10001" of "80,000 yen" and "Parking Fee" with expense item code "10004" of "10,000 yen."

[0039] In addition, the example in Figure 5 shows that the breakdown of the money collected from Contractor C, whose contract number is "00003," is "Rent" with expense item code "10001" of "70,000 yen" and "Parking Fee" with expense item code "10004" of "8,000 yen."

[0040] The contract allocation remittance item storage unit 15 stores allocation target items for contracts with each contract number, as shown in Figure 6. The example in Figure 6 shows that, of the rent, common area charges, and management fee items for contract number "00001" (see Figure 5), "rent" with item code "10002" is set as an allocation target item. The example in Figure 6 also shows that, of the rent and parking fee items for contract number "00003" (see Figure 5), "parking fee" with item code "10004" is set as an allocation target item.

[0041] As will be described later, the control unit 3 refers to this contract allocation remittance item storage unit 15 and processes the remittance of the money of the allocation target item to the remittance destination indicated in the allocation destination remittance information shown in FIG.

[0042] (Functional configuration of business support device) Next, the control unit 3 executes the business support program stored in the memory unit 2, thereby functioning as a communication control unit 21, a discrimination unit 22, a data generation unit 23, and an output control unit 24, as shown in Fig. 1. The data generation unit 23 includes a remittance data generation unit 25 and a payment data generation unit 26.

[0043] In this example, the communication control unit 21 to the payment data generation unit 26 are described as being realized by software based on a business support program, but some or all of the communication control unit 21 to the payment data generation unit 26 may also be realized by hardware. In either case, the same effects as those described below can be obtained.

[0044] The communication control unit 21 collects the rent from the contract holder's bank terminal device 51 via the communication interface unit 4 and the network 50, and performs the remittance process to the bank terminal device 52 to which the remittance is to be allocated and / or the bank terminal device 53 to which the normal remittance is to be paid.

[0045] When remitting money collected from a contractor through collection agency to a remittance destination, the determination unit 22 refers to the contract allocation remittance item storage unit 15 in which allocation target items, which are items to be remitted to other remittance destinations (remittance destinations indicated by the allocation remittance destination information in Fig. 4), are set for each contractor. The determination unit 22 then determines whether or not there are any allocation target items to be remitted to other remittance destinations among the items of money collected from the contractor.

[0046] The remittance data generation unit 25 refers to the contract data storage unit 13 in which remittance destination information indicating other remittance destinations to which money for the remittance target expense items will be remitted, and normal remittance destination information indicating the remittance destination of money for normal remittance expense items, which are expense items other than the remittance target expense items, are set for each contractor. If the determination unit 22 determines that there is a remittance target expense item, the remittance data generation unit 25 generates remittance data including contractor information for identifying the contractor, the remittance amount for the remittance target expense items, and the remittance amount for the normal remittance item (the remittance header data in Figure 9(a) and the remittance detail data in Figure 9(b) are examples of "remittance data").

[0047] In addition, if the discrimination unit 22 determines that there are no items eligible for allocation, the remittance data generation unit 25 generates remittance data including subscriber information for identifying the subscriber and the remittance amount for the normal remittance item (see Figures 9(a) and 9(b)).

[0048] The output control unit 24 outputs the generated remittance data to an output target. As an example of the output target, the output device 7 can be used. This output device 7 may be a monitor device for obtaining a display output, a printer device for obtaining a print output, or a speaker device for obtaining an audio output. The output target may also be the memory unit 2, an external storage device externally connected to the business support device 1, or a server device on the network 50.

[0049] When the discrimination unit 22 determines that there is an item eligible for allocation, the payment data generation unit 26 generates remittance data based on the remittance data, including contractor information for identifying the contractor, the remittance amount for the item eligible for allocation, the payment settlement number for the item eligible for allocation, the remittance amount for the regular remittance item, and the payment settlement number for the regular remittance item (the payment header data in Figure 10(a) and the payment detail data in Figure 10(b) are examples of payment data).

[0050] In addition, if the discrimination unit 22 determines that there are no items eligible for allocation, the payment data generation unit 26 generates payment data including subscriber information for identifying the subscriber, the remittance amount for the regular remittance item, and the payment settlement number for the regular remittance item (see Figures 10(a) and 10(b)).

[0051] The output control unit 24 outputs the generated payment data to the output target.

[0052] In addition, as shown in Figure 4, the contract data storage unit 13 stores, as remittance destination information, company information of the company that will be the other remittance destination to which money for the remittance target expense item will be transferred and account information of the bank that will be the remittance destination (see remittance destination information in Figure 4), and, as regular remittance destination information, company information of the company that will be the remittance destination to which money for the regular remittance expense item will be transferred and account information of the bank that will be the remittance destination (see regular remittance destination information in Figure 4).

[0053] (Supporting operations for remittance business) Next, we will explain the support operation of the remittance business in the business support device 1 of this embodiment. This support operation is performed in the flow of management company registration processing in step S1 shown in Figure 7, contract input processing in step S2, remittance calculation processing in step S3 shown in Figure 8, and payment settlement processing in step S4.

[0054] (Step S1) First, in step S1 shown in Fig. 7, the person in charge registers the management company, lessor, bank account, etc. via the input device 6 of the business support device 1. As a result, the management company name is associated with each management company code and stored in the management company master table 11, as shown in Fig. 2.

[0055] As shown in FIG. 3, for each management company code, the bank account code, bank code, branch code, deposit type, and account number are stored in association with each other in the management company account master table 12.

[0056] (Step S2) Next, in step S2 shown in Fig. 7, the person in charge sets the remittance destination, bank account, regular remittance expense item, and allocation target expense item via the input device 6 of the business support device 1. As a result, the contract number, customer name, management company, remittance destination management company code, remittance destination management company account code, remittance destination management company code, and remittance destination management company account code are stored in the contract data storage unit 13, as shown in Fig. 4.

[0057] As shown in FIG. 5, the contract number, the expense item code, and the amount billed for each expense item are stored in the contract rent data storage unit 14.

[0058] As shown in FIG. 6, the allocation target expense items and the contract number of the contract in which the allocation target expense items are set are stored in the contract allocation remittance item storage unit 15.

[0059] (Step S3) Next, in step S3 shown in Figure 8, the communication control unit 21 accesses the contractor's bank terminal device 51 at the time of rent collection, such as at the end of the month, and performs the rent collection process (debit process from the bank account) for the rent corresponding to the billing amount set for each expense item for each contract number.

[0060] The discrimination unit 22 refers to the contract allocation remittance item storage unit 15 shown in Fig. 6, and recognizes the contract number to which the allocation target item is set, and the allocation target item. In the example of Fig. 6, "rent" with the item code "10001" set for the contract number "00001" is recognized as an allocation target item. In addition, "parking fee" with the item code "10004" set for the contract number "00003" is recognized as an allocation target item.

[0061] Based on the contract number recognized by referencing the contract allocation remittance item memory unit 15, the discrimination unit 22 refers to the contract rent data memory unit 14 shown in Fig. 5 and recognizes the billing amount of the allocation target item. In the example of Fig. 5, the discrimination unit 22 recognizes the billing amount of "100,000 yen" as the billing amount of the "rent" item with the item code "10001" set as the allocation target item for the contract number "00001". Also, in the example of Fig. 5, the discrimination unit 22 recognizes the billing amount of "8,000 yen" as the billing amount of the "parking fee" item with the item code "10004" set as the allocation target item for the contract number "00003".

[0062] Next, based on each contract number, the discrimination unit 22 refers to the contract data storage unit 13 shown in Figure 4 and determines whether or not remittance destination information has been set for the contract number from which the rent was collected. In the example of Figure 4, the discrimination unit 22 determines that remittance destination information has been set along with regular remittance destination information for the contract number "00001". Also, in the example of Figure 4, the discrimination unit 22 determines that only regular remittance destination information has been set for the contract number "00002", and determines that remittance destination information has been set along with regular remittance destination information for the contract number "00003".

[0063] Next, based on the judgment result of the judgment unit 22, the remittance data generation unit 25 generates remittance data indicating the remittance amount for each expense item to the remittance destination indicated by the normal remittance destination information and the allocated remittance destination information in the contract data storage unit 13.

[0064] Specifically, the expense items for the money collected under the contract number "00001" are "rent," "common area fees," and "management fees." Of these, "rent" is set as the expense item subject to allocation (see Figure 6). Furthermore, "common area fees" and "management fees" are regular remittance expense items.

[0065] The remittance data generation unit 25 references the contract data storage unit 13 based on the contract number "00001" and acquires the management company code of "1001" and the remittance destination management company account code of "01" to which the normal remittance items, "common area fees" and "management fees", are remitted. The remittance data generation unit 25 also references the contract data storage unit 13 based on the contract number "00001" and acquires the management company code of "3001" (in this case, the lessor's code) and the remittance destination management company account code of "01" to which the allocation target item, "rent", is remitted.

[0066] Similarly, the remittance data generation unit 25 references the contract data storage unit 13 based on the contract number "00002" and obtains the management company code "1001" and the remittance destination management company account code "02" to which the regular remittance items "rent" and "parking fee" are remitted. Note that the contract number "00002" does not include any items eligible for allocation, so the remittance destination management company code and the remittance destination management company account code are not obtained.

[0067] Similarly, the remittance data generation unit 25 references the contract data storage unit 13 based on the contract number "00003" and obtains the management company code "2001" and the remittance management company account code "01" to which the normal remittance item "rent" is to be remitted. Furthermore, the remittance data generation unit 25 references the contract data storage unit 13 based on the contract number "00003" and obtains the management company code "2001" and the remittance management company account code "02" to which the normal remittance item "parking fee" is to be remitted.

[0068] Then, based on the various information thus acquired, the remittance data generation unit 25 generates remittance data consisting of the remittance header data shown in Figure 9(a) and the remittance detail data shown in Figure 9(b), and stores it in the remittance data storage unit 16.

[0069] More specifically, the remittance data generation unit 25 generates the remittance header data shown in Figure 9(a) including the contract number, remittance number, rent month, and remittance date. At this time, the remittance data generation unit 25 generates remittance header data for normal remittance items and remittance header data for allocation target items, respectively.

[0070] That is, for the contract number "00001", there were a normal remittance destination and a remittance destination, as shown in Figure 4. Therefore, the remittance data generation unit 25 generates remittance data for the remittance number "001" corresponding to the normal remittance destination, and also generates remittance data for the remittance number "002" for the remittance destination, as shown in Figure 9(a).

[0071] Similarly, for the contract number "00003", there were normal remittance destinations and remittance destinations, as shown in Figure 4. Therefore, the remittance data generation unit 25 generates remittance data for the remittance number "004" corresponding to the normal remittance destination, and also generates remittance data for the remittance number "005" for the remittance destination, as shown in Figure 9(a).

[0072] In contrast, for the contract number "00002", only a regular remittance destination exists, as shown in Figure 4. Therefore, the remittance data generation unit 25 generates only remittance data for the remittance number "003", which corresponds to the regular remittance destination, as shown in Figure 9(a).

[0073] The "remittance number" in this type of remittance data is automatically assigned for each rent month and contract number. The "rent month" is the rent month entered on the remittance calculation processing screen, and in the example of Figure 9(a) it is "March 2024." The "remittance date" is the date entered on the remittance calculation processing screen, and in the example of Figure 9(a) it is "February 29, 2023."

[0074] In addition to the remittance header data, the remittance data generation unit 25 generates remittance detail data indicating the remittance amount for each expense item corresponding to each remittance number shown in Figure 9(b) and stores it in the remittance data storage unit 16.

[0075] As described above, the remittance number "001" is the remittance number for the regular remittance items "common area fee" and "management fee," and the remittance amounts are "5,000 yen" and "3,000 yen," respectively. Therefore, the remittance data generation unit 25 generates remittance statement data for the remittance number "001," in which the remittance amount for "common area fee" is "5,000 yen," the remittance date is "February 29, 2023," the remittance destination code is "1001," and the remittance destination account code is "01." The remittance data generation unit 25 also generates remittance statement data for the remittance number "001," in which the remittance amount for "management fee" is "3,000 yen," the remittance date is "February 29, 2023," the remittance destination code is "1001," and the remittance destination account code is "01."

[0076] In contrast, the remittance number "002" is the remittance number for "rent," which is the expense item to be allocated, and the remittance amount is "100,000 yen." Therefore, the remittance data generation unit 25 generates remittance detail data with the remittance number "002," the remittance amount for "rent" set to "100,000 yen," the remittance date set to "February 29, 2023," the remittance destination code set to "3001," and the remittance destination account code set to "01."

[0077] Similarly, the remittance number "003" is the remittance number for "rent" and "parking fee," which are regular remittance items, and the remittance amounts are "80,000 yen" and "10,000 yen," respectively. Therefore, the remittance data generation unit 25 generates remittance statement data for the remittance number "003," in which the remittance amount for "rent" is "80,000 yen," the remittance date is "February 29, 2023," the remittance destination code is "1001," and the remittance destination account code is "02." The remittance data generation unit 25 also generates remittance statement data for the remittance number "003," in which the remittance amount for "parking fee" is "10,000 yen," the remittance date is "February 29, 2023," the remittance destination code is "1001," and the remittance destination account code is "02."

[0078] Similarly, the remittance number "004" is the remittance number for "rent," which is a regular remittance item, and the remittance amount is "70,000 yen." Therefore, the remittance data generation unit 25 generates remittance detail data with the remittance number "004," the remittance amount for "rent" set to "70,000 yen," the remittance date set to "February 29, 2023," the remittance destination code set to "2001," and the remittance destination account code set to "01."

[0079] In contrast, the remittance number "005" is the remittance number for "parking fee," which is an expense item to be allocated, and the remittance amount is "8,000 yen." Therefore, the remittance data generation unit 25 generates remittance detail data with the remittance number "005," the remittance amount for "parking fee" set to "8,000 yen," the remittance date set to "February 29, 2023," the remittance destination code set to "2001," and the remittance destination account code set to "02."

[0080] Such remittance detail data includes a remittance detail number, remittance number, remittance date, remittance destination code, remittance destination account code, remittance expense code, remittance amount, and remittance number. The "remittance detail number" is automatically assigned in descending order by the remittance data generation unit 25 and assigned to each remittance detail data.

[0081] The "remittance number" is automatically assigned by the remittance data generation unit 25 for each rent month and contract number, and the remittance number attached to the remittance header data as shown in Figure 9(a) is attached to each corresponding remittance detail data.

[0082] For "remittance date," the remittance date attached to the remittance header data is attached to each corresponding remittance detail data, as shown in Figure 9(a). For "remittance destination code," if the remittance destination management company code is set in the contract data shown in Figure 4 (remittance destination management company code ≠ NULL), the remittance data generation unit 25 attaches the remittance destination management company code to the remittance detail data. Also, if the remittance destination management company code is not set in the contract data (remittance destination management company code = NULL), the remittance data generation unit 25 attaches the remittance destination management company code to the remittance detail data.

[0083] Regarding the "remittance destination account code," if the remittance destination management company account code is set in the contract data shown in Fig. 4 (remittance destination management company account code ≠ NULL), the remittance data generation unit 25 will add the remittance destination management company account code to the remittance detail data. Also, if the remittance destination management company account code is not set in the contract data (remittance destination management company account code = NULL), the remittance data generation unit 25 will add the remittance destination management company account code to the remittance detail data.

[0084] For the "remittance item code," the remittance data generation unit 25 assigns the item code of each item set for each contract number in the contract rent data shown in Figure 5. For the "remittance amount," the remittance data generation unit 25 assigns the invoice amount of each item set for each contract number in the contract rent data shown in Figure 5 as the amount to be sent.

[0085] The output control unit 24 performs remittance processing at the desired timing based on the remittance data stored in the remittance data storage unit 16 to the bank terminal device 52 of the allocation remittance destination indicated by the remittance destination code and remittance destination account code of each expense item, and / or the bank terminal device 53 of the normal remittance destination. This allows for easy remittance processing to bank accounts specified for each contract number and each expense item.

[0086] (Step S4) Next, when the remittance data is input, in step S4, the payment data generation unit 26 generates payment data corresponding to the remittance data and stores it in the payment data storage unit 17, thereby carrying out a payment settlement process.

[0087] Specifically, the payment data generation unit 26 generates payment data consisting of payment header data shown in FIG. 10(a) and payment detail data shown in FIG. 10(b).

[0088] That is, the payment data generation unit 26 generates payment header data including the payment settlement number, payment date, payee code, payee account code, and payment amount, as shown in Figure 10(a). The "payment settlement number" is automatically assigned to the payment header data based on the remittance number in the remittance header data.

[0089] "Payment date" assigns the same date as the remittance date in the remittance header data to the payment header data. "Payee code" assigns the remittance code from the remittance detail data to the payment header data. "Payee account code" assigns the remittance account code from the remittance detail data to the payment header data. "Payment amount" assigns the remittance amount from the remittance detail data as the payment amount to the payment header data.

[0090] In addition, the payment data generation unit 26 generates payment detail data including the payment detail number, remittance number, payment date, payee code, payee account code, payment item code, payment amount, and payment settlement number, as shown in Figure 10(b).

[0091] The payment data generation unit 26 automatically assigns a "payment detail number" in descending order to each payment detail data. The "remittance number" is assigned to each payment detail data the same as the remittance number in the remittance detail data. This allows the remittance detail data and payment detail data to be associated via the remittance number.

[0092] "Payment date" is the date of remittance from the remittance header data and remittance detail data, and is attached to the payment detail data as the payment date. "Payee code" is the code of the remittance from the remittance detail data, and is attached to the payment detail data as the payee code. "Payee account code" is the code of the remittance from the remittance detail data, and is attached to the payment detail data as the payee account code.

[0093] "Payment Item Code" is the remittance item code in the remittance detail data that is assigned to the payment detail data as the payment item code. "Payment Amount" is the remittance amount in the remittance detail data that is assigned to the payment detail data as the payment amount for the corresponding item. "Payment Settlement Number" is assigned to each expense item based on the payment settlement number in the payment header data shown in Figure 10(a).

[0094] Such payment data is read out from the payment data storage unit 17 by the output control unit 24 at a desired timing such as the accounting month, and is used for accounting processing.

[0095] (Effects of the embodiment) As is clear from the above explanation, the business support device 1 of the embodiment can specify allocation for each remittance destination (management company, landlord, agency, etc.) and remittance destination account for each contract, regardless of the management company's account settings, and enable the allocation and remittance of rent or other remittance items. This simplifies the remittance work of collection agency services and significantly reduces the burden on staff.

[0096] In addition, since it is possible to flexibly allocate remittance items and amounts for each contract, it is possible to improve the sophistication and competitiveness of collection agency services.

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

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

[0099] Furthermore, the present invention can contribute to strengthening control and governance, thereby contributing to the achievement of Goal 16 of the SDGs.

[0100] [Other embodiments] The present invention can be implemented in various different forms other than the above-described embodiments within the scope of the technical concept described in the claims.

[0101] For example, among the processes described in the embodiments, all or part of the processes described as being performed automatically may be performed manually, or all or part of the processes described as being performed manually may be performed automatically using a known method or the like.

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

[0103] Furthermore, the components of the business support device 1 shown in the figure are conceptual functional components and do not necessarily have to have the physical configuration shown in the figure. For example, all or any part of the processing functions of the business support device 1, particularly the processing functions performed by the control unit 3, may be realized by a program interpreted and executed by the control unit 3 (CPU: Central Processing Unit), or may be realized by hardware using wired logic.

[0104] 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 the embodiments, and is mechanically read by the business support device 1 as needed. That is, a computer program is recorded in the storage unit 2, such as a ROM or HDD, for working with an OS (Operating System) to give instructions to a control unit 3 (CPU) and perform various processes. The computer program is loaded into RAM, expanded, and executed by the control unit 3 as appropriate.

[0105] In addition, the business support program of this business support device 1 may be stored in another server device connected to the business support device 1 via any network, and all or part of it may be downloaded and executed as needed.

[0106] Furthermore, the business support program for executing the processes described in the embodiments may be stored in a non-transitory computer-readable recording medium, or may be configured as a program product.

[0107] Here, the "recording medium" can be any "portable physical medium" such as a memory card, a USB (Universal Serial Bus) memory, an SD (Secure Digital) card, a flexible disk, a magneto-optical disk, a ROM, an EPROM (Erasable Programmable Read Only Memory), an EEPROM (registered trademark) (Electrically Erasable and Programmable Read Only Memory), a CD-ROM (Compact Disk Read Only Memory), an MO (Magneto-Optical Disk), a DVD (Digital Versatile Disk), and a Blu-ray (registered trademark) Disc.

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

[0109] It should be noted that a "program" is not necessarily limited to a single structure, but includes a structure that is distributed as multiple modules or libraries, and a structure that achieves its function by working together with other programs, such as an OS.

[0110] Furthermore, the specific configuration for reading the recording medium in the task support device 1 of the embodiment, the reading procedure, and the installation procedure after reading can be any known configuration or procedure.

[0111] The memory unit 2 is a storage means such as a memory device such as RAM or ROM, a fixed disk device such as a hard disk, a flexible disk, or an optical disk, and stores various programs, tables, databases, web page files, etc. used for various processes or providing websites.

[0112] The business support device 1 may be configured as an information processing device such as a known personal computer or a workstation, or may be configured as an information processing device connected to any peripheral device. The information processing device may be implemented with software (including programs or data) that realizes the processes described in the embodiments.

[0113] Furthermore, the specific forms of distribution and integration of the devices are not limited to those shown in the drawings, and all or part of them can be functionally or physically distributed or integrated in any unit depending on various additions or functional loads. In other words, the above-mentioned embodiments can be selectively implemented by combining them in any way. [Industrial Applicability]

[0114] As an example, the present invention is suitable for application to the remittance business of guarantee companies and credit companies that handle collection agency products. [Explanation of symbols]

[0115] 1 Business support equipment 2 Storage section 3. Control Unit 4. Communication interface section 5 Input / output interface section 6 Input Devices 7 Output Devices 11 Management Company Master Table 12 Management company account master table 13 Contract data storage unit 14 Contract rent data storage unit 15 Contract allocation remittance expense item storage section 16 Remittance data storage unit 17 Payment data storage unit 21 Communication control unit 22 Discrimination part 23 Data Generation Unit 24 Output control section 25 Remittance data generation unit 26 Payment data generation unit 50 Network 51 Customer's bank terminal device 52 Bank terminal device of the remittance destination 53 Bank terminal equipment of the usual remittance destination

Claims

1. a determination unit that, when remitting money collected from a contractor through collection agency services to a remittance destination, refers to a contract allocation remittance item storage unit in which allocation target items, which are items to be remitted to other remittance destinations, are set for each contractor, and determines whether or not there are any allocation target items to be remitted to other remittance destinations among the items of money collected from the contractor; a remittance data generation unit that references the contract data storage unit set for each contractor for remittance destination information indicating the other remittance destination to which money for the remittance target expense item will be remitted, and normal remittance destination information indicating the remittance destination of money for normal remittance expense items, which are expense items other than the remittance target expense item, and generates remittance data including contractor information for identifying the contractor, the remittance amount for the remittance target expense item, and the remittance amount for the normal remittance item, if the determination unit determines that the remittance target expense item does not exist; an output control unit that outputs the generated remittance data to an output target; A business support device having the above.

2. a payment data generation unit that, when the determination unit determines that the allocation target expense item exists, generates remittance data based on the remittance data, including contractor information for identifying the contractor, the remittance amount of the allocation target expense item, the payment settlement number of the allocation target expense item, the remittance amount of the normal remittance expense item, and the payment settlement number of the normal remittance expense item; and, when the determination unit determines that the allocation target expense item does not exist, generates payment data, including contractor information for identifying the contractor, the remittance amount of the normal remittance expense item, and the payment settlement number of the normal remittance expense item, the output control unit outputs the generated payment data to an output target; 2. The business support device according to claim 1, wherein:

3. The contract data storage unit stores, as the remittance destination information, company information of the company that will be the other remittance destination to which the money for the remittance target expense item will be remitted and account information of the bank that will be the remittance destination, and, as the normal remittance destination information, company information of the company that will be the remittance destination to which the money for the normal remittance expense item will be remitted and account information of the bank that will be the remittance destination; 3. The business support device according to claim 1 or 2, wherein:

4. a determination step in which, when remitting money collected from a contractor through collection agency to a remittance destination, the determination unit refers to a contract allocation remittance item storage unit in which allocation target items, which are items to be remitted to other remittance destinations, are set for each contractor, and determines whether or not there are any allocation target items to be remitted to other remittance destinations among the items of money collected from the contractor; a remittance data generation step in which a remittance data generation unit refers to a contract data storage unit set for each contractor for remittance destination information indicating the other remittance destination to which money for the remittance target expense item will be remitted, and normal remittance destination information indicating the remittance destination of money for normal remittance expense items other than the remittance target expense item, and if it is determined in the determination step that the remittance target expense item exists, generates remittance data including contractor information for identifying the contractor, the remittance amount for the remittance target expense item, and the remittance amount for the normal remittance expense item, and if it is determined in the determination step that the remittance target expense item does not exist, generates remittance data including contractor information for identifying the contractor and the remittance amount for the normal remittance expense item; an output control step in which an output control unit outputs the generated remittance data to an output target; A business support method having the above.

5. Computer, a determination unit that, when remitting money collected from a contractor through collection agency services to a remittance destination, refers to a contract allocation remittance item storage unit in which allocation target items, which are items to be remitted to other remittance destinations, are set for each contractor, and determines whether or not there are any allocation target items to be remitted to other remittance destinations among the items of money collected from the contractor; a remittance data generation unit that references the contract data storage unit set for each contractor for remittance destination information indicating the other remittance destination to which money for the remittance target expense item will be remitted, and normal remittance destination information indicating the remittance destination of money for normal remittance expense items, which are expense items other than the remittance target expense item, and generates remittance data including contractor information for identifying the contractor, the remittance amount for the remittance target expense item, and the remittance amount for the normal remittance item, if the determination unit determines that the remittance target expense item does not exist; an output control unit that outputs the generated remittance data to an output target; A business support program that functions as a

Images