Business support device, business support method, and business support program

Abstract

We provide business support devices that allow for easy identification of deposit and withdrawal details. [Solution] The business support device according to the present invention comprises an acquisition unit and a determination unit. The acquisition unit acquires detailed information including source information, recipient information, deposit / withdrawal category, and description. The determination unit determines, based on the source information, recipient information, deposit / withdrawal category, and description of the acquired detailed information, whether the detailed information relates to fund transfers within the group or between branches.

Description

Technical Field

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

Background Art

[0002] In a group consisting of multiple companies, a CMS (Cash Management System) may be used to manage fund transfers within the group. Also, within a company, fund concentration may be carried out between the head office and branch offices. In addition to these fund transfers, corporate bank transactions include deposits that are subject to offsetting of claims and withdrawals for other expense payments. Depending on the type differences of these deposit and withdrawal transactions, the type of data generated from the details and the process for generating journal data may vary.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] The process of determining whether bank deposit and withdrawal details correspond to CMS transactions within a group company or transactions associated with fund concentration between the head office and branch offices can sometimes become complicated.

[0005] The present invention has been made in view of the above, and an object thereof is to provide a business support device, a business support method, and a business support program capable of easily determining deposit and withdrawal details.

Means for Solving the Problems

[0006] To solve the above-mentioned problems and achieve the objective, the business support device according to the present invention comprises an acquisition unit and a determination unit. The acquisition unit acquires detailed information including source information, recipient information, deposit / withdrawal category, and description. The determination unit determines, based on the source information, recipient information, deposit / withdrawal category, and description of the acquired detailed information, whether the detailed information relates to fund transfers within the group or between branches.

[0007] Furthermore, the business support method according to the present invention includes the steps of: acquiring detailed information including source information, recipient information, deposit / withdrawal category, and description; and determining whether the detailed information relates to fund transfers within the group or between branches, based on the source information, recipient information, deposit / withdrawal category, and description of the acquired detailed information.

[0008] Furthermore, the business support program according to the present invention performs the steps of: acquiring detailed information including source information, recipient information, deposit / withdrawal category, and description; and determining whether the detailed information relates to fund transfers within the group or between branches, based on the source information, recipient information, deposit / withdrawal category, and description of the acquired detailed information. [Effects of the Invention]

[0009] The present invention has the effect of making it possible to easily distinguish between deposit and withdrawal details. [Brief explanation of the drawing]

[0010] [Figure 1] Figure 1 shows an example of the movement of funds in an embodiment. [Figure 2] Figure 2 shows an example of deposit and withdrawal statement data according to the embodiment. [Figure 3] Figure 3 shows an example of the configuration of a business support system according to the embodiment. [Figure 4] Figure 4 shows an example of the information stored in the master storage unit of the business support device according to this embodiment. [Figure 5] FIG. 5 is a diagram showing an example of a settlement account master stored in the master storage unit according to the embodiment. [Figure 6] FIG. 6 is a diagram showing an example of a discrimination master stored in the master storage unit according to the embodiment. [Figure 7] FIG. 7 is a diagram showing an example of information stored in the data storage unit of the business support device according to the embodiment. [Figure 8] FIG. 8 is a diagram showing an example of a processing flow according to the embodiment. [Figure 9] FIG. 9 is a diagram showing an example of a data import process according to the embodiment. [Figure 10] FIG. 10 is a diagram showing an example of a detail table stored in the data storage unit according to the embodiment. [Figure 11] FIG. 11 is a diagram showing an example of a determination process according to the embodiment. [Figure 12] FIG. 12 is a diagram showing another example of a determination process according to the embodiment. [Figure 13] FIG. 13 is a diagram showing another example of a determination process according to the embodiment. [Figure 14] FIG. 14 is a diagram showing an example of a deposit table according to the embodiment. [Figure 15] FIG. 15 is a diagram showing an example of a journal creation target table according to the embodiment. [Figure 16] FIG. 16 is a diagram showing an example of a journal detail table according to the embodiment. [Embodiment for Carrying Out the Invention]

[0011] <着 Embodiments of the present invention will be described in detail based on the drawings. Note that the present invention is not limited by these embodiments.

[0012] [1. Overview] In an embodiment, fund transfers are made between accounts within a group consisting of three companies: the head office, Group Company A, and Group Company B shown in FIG. 1. Also, within each company, fund transfers are made between accounts between the head office and branch offices. FIG. 1 is a diagram showing an example of the movement of funds. For example, in the morning, funds move from the head office to a group company or from the head office to a branch office, and in the evening, funds move from the group company to the head office or from the branch office to the head office. Note that in FIG. 1, the illustrations of the head office and branch offices of the head office and Group Company A are omitted. Also, the fund transfer within the group may be performed not only between the head office shown in FIG. 1 and Group Company A or Group Company B, but also between Group Company A and Group Company B. In the following, when expressing without distinguishing between the fund transfer by CMS transactions within the group and the fund transfer for fund concentration between the head office and branch offices, it may be simply referred to as "fund transfer".

[0013] The information regarding the fund transfer shown in FIG. 1 is, for example, the deposit and withdrawal detail data 1000 as shown in FIG. 2. FIG. 2 is a diagram showing an example of the deposit and withdrawal detail data 1000 according to the embodiment. The deposit and withdrawal detail data 1000 is, for example, EB (Electronic Banking) data in the format of the Zenkyoren format (a format defined by the National Bankers Association Federation for data transmission), and is transmitted from Bank 9 as shown in FIG. 1. As shown in FIG. 2, the deposit and withdrawal detail data 1000 includes columns for the bank code, branch number, and account number, the accounting date, the debit / credit classification, the amount, the name of the remitter, and the summary content.

[0014] The bank code, branch number, and account number are information that uniquely identifies the account targeted by the details. In the details of the deposit, the bank code, branch number, and account number indicate the name of the receiving account, and in the details of the withdrawal, they indicate the name of the account of the payer. That is, the bank code, branch number, and account number are an example of the transfer destination information or the transfer source information. The deposit and withdrawal detail data 1000 transmitted to Group Company B includes, in addition to the detail information of the account of the head office of Group Company B shown in FIG. 1, the detail information of each account of Branch (1) and Branch (2) of Group Company B, which will be described later.

[0015] The account date indicates the date the item occurred. The amount indicates the amount of the item. The description indicates the details of the transaction. The description is entered by the remitter, for example, during a bank transfer.

[0016] The deposit / payment category indicates whether the transaction is a deposit or a withdrawal. A deposit / payment category of "1" indicates a deposit, and a category of "2" indicates a withdrawal. In other words, the deposit / payment category is just one example of a deposit / withdrawal category.

[0017] The remitter's name indicates the source account name in the deposit details and the destination account name in the withdrawal details. In other words, the remitter's name is an example of source or destination information. The remitter's name may be set by default, for example, but the remitter may be able to change it each time a transfer is requested.

[0018] [2. Structure] The business support system 1 shown in Figure 3 is installed, for example, at the head office, group company A, and group company B, as shown in Figure 1, and manages the deposit and withdrawal information of each company. Figure 3 is a diagram showing an example of the configuration of the business support system 1 according to the embodiment. In the following, the processing performed by the business support system 1 installed at group company B after obtaining deposit and withdrawal statement data 1000 from bank 9 will be described.

[0019] In Figure 3, the business support system 1 is configured, for example, as a server-client system, with a business support device 100 that functions as a server and multiple terminal devices 200 that are able to communicate with each other via a network 300.

[0020] The business support device 100 provides various input screens to the terminal device 200 in response to requests from the terminal device 200, accepts information input from the terminal device 200 on these screens, and centrally manages the accepted information using various data in the storage unit. In addition, the business support device 100 provides information on various data and generated accounting processes (end-of-month processing, management accounting, financial accounting, etc.) in response to requests from the terminal device 200, allowing the terminal device 200 to view the information on various data and the processed accounting information.

[0021] The business support device 100 can be configured, for example, as a workstation or a personal computer.

[0022] Terminal devices 200 are, for example, placed in each department within the company. Each terminal device 200 is equipped with a monitor, keyboard, printer, etc., and displays various input screens provided by the business support device 100 on the monitor, allowing the person in charge (operator) to perform various inputs. In addition, each terminal device 200 can display information on various data stored by the business support device 100 and information on generated accounting processes (end-of-month processing, management accounting, financial accounting, etc.) on the monitor, allowing users to view this information.

[0023] The terminal device 200 may be, for example, a commercially available desktop personal computer, and is not limited to stationary information processing devices such as desktop personal computers, but may also be portable information processing devices such as commercially available notebook personal computers, PDAs (Personal Digital Assistants), smartphones, or tablet personal computers.

[0024] As shown in Figure 3, the business support device 100 comprises a control unit 102, a communication interface unit 104, a storage unit 106, and an input / output interface unit 108. Each component of the business support device 100 is connected to communicate via any communication path.

[0025] The communication interface unit 104 connects the business support device 100 to the network 300 via communication devices such as routers and wired or wireless communication lines such as dedicated lines, enabling communication between them. The communication interface unit 104 has the function of communicating data with other devices via communication lines. Here, the network 300 has the function of connecting the business support device 100 and the terminal device 200 so that they can communicate with each other, and is, for example, the Internet or a LAN (Local Area Network).

[0026] The memory unit 106 stores various databases, tables, and files. The memory unit 106 also stores computer programs that work in cooperation with the OS (Operating System) to give instructions to the CPU (Central Processing Unit) to perform various processes. As the memory unit 106, for example, memory devices such as RAM (Random Access Memory) and ROM (Read Only Memory), fixed disk devices such as hard disks, flexible disks, and optical disks can be used.

[0027] As shown in Figure 3, the storage unit 106 includes a master storage unit 106a and a data storage unit 106b.

[0028] As shown in Figure 4, the master storage unit 106a stores the settlement account master 106aa and the discrimination master 106ab. Figure 4 is a diagram showing an example of the information stored in the master storage unit 106a of the business support device 100 according to this embodiment. The settlement account master 106aa is used to identify the account in the deposit and withdrawal details data 1000 shown in Figure 2. The discrimination master 106ab is used to determine whether the deposit and withdrawal details data 1000 shown in Figure 2 corresponds to a fund transfer within a group, a fund transfer between branches, or a deposit subject to reconciliation.

[0029] As shown in Figure 5, the settlement account master 106aa stores the bank code, branch code, and account number, as well as the account code, department code, and account holder name associated with each settlement account. Figure 5 is a diagram showing an example of the settlement account master 106aa stored by the master storage unit 106a according to this embodiment. A settlement account is information that uniquely identifies an account, which is specified by the bank code, branch, and account number. The account code is information that is assigned as a debit account or credit account in the journal entry process, which will be explained later. The department code is information that is assigned in the generation process, which will be explained later.

[0030] As shown in Figure 5, the settlement account master 106aa has three records registered for the same bank code. For example, the settlement account "000" record indicates an account with branch code "0001" and account number "123456789", the settlement account "001" record indicates an account with branch code "0002" and account number "234567890", and the settlement account "002" record indicates an account with branch code "0003" and account number "345678901". Also, as shown in the columns for account code, department code, and account name, settlement account "000" indicates an account at the head office, settlement account "001" indicates an account at branch (1), and settlement account "002" indicates an account at branch (2).

[0031] As shown in Figure 6, the discrimination master 106ab stores discrimination values ​​associated with each item SEQ. Figure 6 is a diagram showing an example of the discrimination master 106ab stored in the master storage unit 106a. In Figure 6, item SEQ is information that uniquely identifies the discrimination value and is numbered sequentially starting from 1. The discrimination value stores the discrimination conditions used in the judgment process, which will be explained later.

[0032] As shown in Figure 6, item SEQ "1" of the discrimination master 106ab registers the account used for fund transfers in CMS transactions within the group. In addition, discrimination conditions related to the "remitter name" are registered in items SEQ "2", "3", "7", "10", and "12" of the discrimination master 106ab, discrimination conditions related to the "description content" are registered in items SEQ "4" and "8" of the discrimination master 106ab, and discrimination conditions related to the "settlement account" are registered in items SEQ "5", "6", "9", and "11" of the discrimination master 106ab.

[0033] As shown in Figure 7, the data storage unit 106b stores the details table 106ba, the deposit table 106bb, the journal entry creation target table 106bc, and the journal entry details table 106bd. Figure 7 is an example of the information stored by the data storage unit 106b of the business support device 100 according to this embodiment. The details table 106ba stores information based on the deposit and withdrawal details data 1000 acquired by the acquisition unit 102a, which will be described later. The deposit table 106bb stores data related to deposits subject to receivable settlement, which will be generated by the generation unit 102c, which will be described later. The journal entry creation target table 106bc stores data used to generate journal entry information, which will be generated by the generation unit 102c. The journal entry details table 106bd stores journal entry information generated from the data in the journal entry creation target table 106bc. Details of each table will be described in detail later.

[0034] The control unit 102 is a CPU or the like that comprehensively controls the business support device 100. The control unit 102 has an internal memory for storing control programs such as the OS, programs that define various processing procedures, and required data, and executes various information processing based on these stored programs. Functionally, the control unit 102 comprises an acquisition unit 102a, a determination unit 102b, and a generation unit 102c.

[0035] [3. Processing executed by the control unit 102] Figure 8 shows an example of the processing flow according to the embodiment. In Figure 8, the data acquisition process is performed by the acquisition unit 102a shown in Figure 3, and the determination process is performed by the determination unit 102b. In addition, the deposit data generation process and the journal entry target data generation process are performed by the generation unit 102c, and the journal entry process is performed by the journal entry unit 102d.

[0036] [3-1. Acquisition Process] The acquisition unit 102a acquires the deposit and withdrawal statement data 1000 shown in Figure 2 and updates the statement table 106ba. The acquisition unit 102a acquires the deposit and withdrawal statement data 1000 shown in Figure 2 periodically (for example, about twice a day). That is, the acquisition unit 102a acquires statement information including the source information, recipient information, deposit / withdrawal category, and description. At that time, the acquisition unit 102a may display a screen that accepts input of a business establishment code that identifies the deposit and withdrawal statement data 1000 to be acquired. Note that the deposit and withdrawal statement data 1000 may also be acquired by manual processing.

[0037] Furthermore, when the acquisition unit 102a acquires the deposit and withdrawal statement data 1000, it assigns a sequential number to each record of the deposit and withdrawal statement data 1000, which is information that uniquely identifies the statement line, called "Deposit / Withdrawal SEQ".

[0038] Furthermore, the acquisition unit 102a refers to the settlement account master 106aa stored in the master storage unit 106a and adds items to the deposit and withdrawal details data 1000 as shown in Figure 9. Figure 9 is a diagram showing an example of the data acquisition process according to the embodiment. First, as shown in Figure 9, the acquisition unit 102a compares the bank code, branch number, and account number of each record in the deposit and withdrawal details data 1000 with each record in the settlement account master 106aa. Then, the acquisition unit 102a adds the settlement accounts of records in the settlement account master 106aa whose bank code, branch number, and account number match to each record in the deposit and withdrawal details data 1000.

[0039] Through this process, the acquisition unit 102a stores the data shown in Figure 10 in the detail table 106ba. Figure 10 is a diagram showing an example of the detail table 106ba stored by the data storage unit 106b according to this embodiment. In the record group 1001 in Figure 9, the settlement account "000" is registered, as shown in Figure 10. In addition, the settlement account "001" is registered in the record group 1002 shown in Figure 9, and the settlement account "002" is registered in the record group 1003. Furthermore, each record in the detail table 106ba is numbered sequentially with deposit / withdrawal SEQ "1" to "10", as shown in Figure 10.

[0040] [3-2. Judgment Process] The determination unit 102b extracts records from the details table 106ba one by one and sequentially determines whether each record corresponds to a fund transfer within a group, a fund transfer between branches, or a deposit subject to reconciliation of receivables.

[0041] The determination unit 102b extracts records from the details table 106ba one by one, determines whether the deposit / payment category is "deposit" or "withdrawal," and also determines whether it matches each of the determination values ​​in the determination master 106ab. In other words, the determination unit 102b determines whether the details information relates to a fund transfer within the group or between branches, based on the source information, destination information, deposit / payment category, and description of the acquired details information.

[0042] First, in the determination process shown in Figure 8, the determination unit 102b determines whether the deposit / payment category of the record read from the details table 106ba corresponds to "deposit" or "withdrawal". If it is determined that the deposit / payment category is "2", i.e., "withdrawal", the determination unit 102b determines whether the record meets all of the following conditions, as shown in Figure 11. Figure 11 is a diagram showing an example of the determination process according to the embodiment. Note that in Figure 11 and subsequent figures, some information such as the bank code, branch number, and account number columns of the details table 106ba shown in Figure 10 may be omitted. <First Judgment Criteria> 1. Deposit / Withdrawal Details Table. Remitter Name = Identification Master (Item SEQ=2) 2. Deposit / Withdrawal Details Table.Description = Identification Master (Item SEQ=4) 3. Deposit / Withdrawal Details Table. Settlement Account = Identification Master (Item SEQ=5)

[0043] Condition 1 above determines whether the name of the remitter in the record is "Zandaka Furikae Shuchuu" (Zandaka Transfer Concentration). Condition 2 above determines whether the description of the record is "Shikin Shuchuu" (Deposit Concentration), and Condition 3 determines whether the settlement account in the record is "000".

[0044] The determination unit 102b determines that a record is not subject to processing if any one of the determination conditions is not met. For example, record ba002 in Figure 11 satisfies condition 3 but not conditions 1 and 2. Also, record ba006 in Figure 11 satisfies conditions 2 and 3 but not condition 1, and records ba008 and ba010 do not satisfy any of conditions 1 through 3. Transactions determined to be excluded include, for example, "rent" as shown in the description of record ba002 in Figure 11, and recurring deductions such as utility bills. Journal entry data for excluded transactions is generated separately in a financial accounting system, for example.

[0045] On the other hand, if the determination unit 102b determines that all of the determination conditions 1 to 3 are met, it determines that the record is a "withdrawal associated with a fund transfer within the group." That is, if the determination unit 102b determines that the deposit / withdrawal category in the acquired statement information is a withdrawal, it determines whether the description, the recipient information, and the source information relate to a fund transfer within the group. For example, in the record ba004 of Figure 11, the settlement account is "000", the remitter name is "Zandaka Furikae Shuchu", and the description is "Shikin Shuchu", so all of the determination conditions 1 to 3 are met, and it is determined that it is a "withdrawal associated with a fund transfer within the group".

[0046] Furthermore, if the determination unit 102b determines that the deposit / payment category of a record read from the details table 106ba is "1", that is, that it corresponds to "deposit", it determines whether the record meets all of the following conditions, as shown in Figure 11. Figure 12 shows another example of the determination process according to the embodiment. <Second Judgment Criteria> 1. Deposit / Withdrawal Details Table. Deposit Description not in Discrimination Master (item SEQ=4 or 8) 2. Deposit / Withdrawal Details Table. Remitter Name (not in Identification Master) (Item SEQ=2 or 7)

[0047] Condition 1 above is met if the description of the record does not fall under "Deposit Concentration". Condition 2 above is met if the remitter name of the record does not fall under either "Zandaka Furikae Concentration" or "●● (Honten 000000000)".

[0048] The determination unit 102b determines that a record is a "deposit subject to receivable settlement" if it finds that both of the determination conditions 1 and 2 are met. For example, in the record ba001 in Figure 12, the remitter name is "○○ Real Estate Company" and the description is "Money Payment," so it satisfies both determination conditions 1 and 2 and is determined to be a "deposit subject to receivable settlement." Note that the settlement account for the record ba001 in Figure 12 is "000," but for example, if the settlement account is "001" or "002," it may also be determined to be a "deposit subject to receivable settlement."

[0049] On the other hand, for example, record ba005 in Figure 12 satisfies condition 2 of the second determination criterion, but does not satisfy condition 1. In this case, the determination unit 102b determines whether the record meets all of the following conditions, as shown in Figure 13. Figure 13 is a diagram showing another example of the determination process according to the embodiment. <Third Judgment Condition> 1. Deposit / Withdrawal Details Table. Remitter Name in Identification Master (Item SEQ=10 or 12) 2. Deposit / Withdrawal Details Table.Description = Identification Master (Item SEQ=8) 3. Deposit / Withdrawal Details Table. Settlement Account = Identification Master (Item SEQ=6)

[0050] Condition 1 above determines whether the remitter's name in the record falls under either "●●(Shiten 000000001)" or "●●(Shiten 000000002)". Condition 2 above determines whether the description of the record is "Shikinshuchu" (Deposit Concern), and Condition 3 determines whether the settlement account in the record is "000".

[0051] If the determination unit 102b determines that all of the determination conditions 1 to 3 are met, it determines that the record is a "fund transfer between branches (fund transfer from a branch to the head office)". That is, if the deposit / withdrawal category in the acquired details information is a deposit, the determination unit 102b determines whether the recipient information belongs to the head office or a branch, and if it determines that the recipient information belongs to the head office, it determines whether the source information relates to a fund transfer within the group, a fund transfer between branches, or something else. For example, the record ba005 shown in Figure 13 has a settlement account of "000", a remitter name of "●● (Branch 000000002)", and a description of "fund transfer", so all of the determination conditions 1 to 3 are met, and it is determined that it is a "fund transfer between branches (fund transfer from a branch to the head office)".

[0052] On the other hand, records ba007 and ba009 shown in Figure 13, for example, satisfy condition 2 of the third determination criterion, but do not satisfy conditions 1 and 3. In this case, the determination unit 102b determines whether the record meets all of the following conditions, as shown in Figure 13. <Fourth Judgment Condition> 1. Deposit / Withdrawal Details Table. Remitter Name in Identification Master (Item SEQ=7) 2. Deposit / Withdrawal Details Table. Settlement Account in Identification Master (Item SEQ=9 or 11) 3. Deposit / Withdrawal Details Table. Settlement Account ≠ Identification Master (Item SEQ=6)

[0053] Condition 1 above determines whether the remitter's name in the record corresponds to "●● (Honten 000000000)", and Condition 2 above determines whether the description of the record corresponds to "Shikinshuchu" (Deposit in Progress). Condition 3 is met if the settlement account in the record does not correspond to "000".

[0054] If the determination unit 102b determines that all of the determination conditions 1 to 3 are met, it determines that the record is a "fund transfer between the head office and branches (fund transfer from the head office to a branch)". That is, if the deposit / withdrawal category in the acquired details information is a deposit, the determination unit 102b determines whether the transfer destination information belongs to the head office or a branch, and if it determines that the transfer destination information belongs to a branch, it determines whether the transfer source information relates to a fund transfer between the head office and branches. For example, in Figure 13, record ba007 has a settlement account of "001" and not "000", and the remitter name is "●● (Head Office 000000000)", so all of the determination conditions 1 to 3 are met, and it is determined to be a "fund transfer between the head office and branches (fund transfer from the head office to a branch)". Similarly, record ba009 in Figure 13 also meets all of the conditions 1 to 3.

[0055] On the other hand, for example, record ba003 shown in Figure 13 satisfies condition 2 of the fourth determination criterion, but does not satisfy conditions 1 and 3. In this case, the determination unit 102b determines whether the record meets all of the following conditions, as shown in Figure 13. <Fifth Judgment Condition> 1. Deposit / Withdrawal Details Table. Remitter Name in Identification Master (Item SEQ=3) 2. Deposit / Withdrawal Details Table.Description = Identification Master (Item SEQ=4) 3. Deposit / Withdrawal Details Table. Settlement Account = Identification Master (Item SEQ=5)

[0056] Condition 1 above determines whether the name of the remitter in the record corresponds to "Zandaka Furikae Haibun". Condition 2 above determines whether the description of the record is "Shikinshuchu" (Deposit Concern), and Condition 3 determines whether the settlement account in the record is "000".

[0057] If the determination unit 102b determines that all of the determination conditions 1 to 3 are met, it determines that the record is a "deposit associated with a transfer of funds within the group." For example, in the record ba003 of Figure 13, the settlement account is "000", the remitter name is "Zandaka Furikae Haibun", and the description is "Shikin Shuchu", so all of the determination conditions 1 to 3 are met, and it is determined that it is a "deposit associated with a transfer of funds within the group".

[0058] As described above, the determination unit 102b determines whether the details pertain to a fund transfer within the group or between branches, based on the source information, recipient information, deposit / payment category, and description of the acquired details.

[0059] [3-3. Various Data Generation Processes] The generation unit 102c generates various data based on the results of the determination process by the determination unit 102b. The generation unit 102c adds records to the payment table 106bb shown in Figure 14 from records that the determination unit 102b has determined to be "payments subject to receivable reconciliation," based on the following data generation rules. Figure 14 is a diagram showing an example of the payment table 106bb according to the embodiment. <First Data Generation Rule> 1. The columns for Amount, Description, and Remitter's Name shall be filled with the corresponding items from the relevant record in Details Table 106ba. 2. In the column for the deposit date, post the account date of the relevant record in details table 106ba. 3. The business establishment code column is where the business establishment code received by the acquisition unit 102a is copied. 4. In the Department Code column, transfer the department code from the settlement account master 106aa that corresponds to the settlement account of the record in the details table 106ba. The deposit number is assigned sequentially each time a record is generated, and the detail line number is assigned sequentially within the deposit number. Additionally, "0" is entered for the journal entry linkage flag, and "NULL" is entered for the journal entry linkage update date and time.

[0060] Based on this first data generation rule, the record with deposit number "N0001" in the deposit table 106bb shown in Figure 14 is generated from record ba001 in the detail table 106ba shown in Figure 12.

[0061] Furthermore, the generation unit 102c generates records in the journal entry target table 106bc shown in Figure 15 by applying the following data generation rules to records that the determination unit 102b has determined to be "deposits due to fund transfers within the group". Figure 15 shows an example of the journal entry target table 106bc. <Second Data Generation Rule> 1. The columns for settlement account, deposit / payment type, amount, description, and remitter name are to be filled with the corresponding items from the details table 106ba. 2. In the "Date of Occurrence" column, post the account date of the relevant record in detail table 106ba. 3. The business establishment code column is where the business establishment code received by the acquisition unit 102a is copied. 4. In the Department Code column, the department code from the settlement account master 106aa corresponding to the settlement account of the record in the details table 106ba is transferred. Note that the deposit / withdrawal number is assigned sequentially each time a record is generated, and the row number is assigned sequentially within the deposit / withdrawal number.

[0062] Based on these data generation rules, a record with the deposit / withdrawal number "N1001" shown in Figure 15 is added to record ba003 in the details table 106ba shown in Figure 13.

[0063] Furthermore, the generation unit 102c applies the above data generation rules to records that the determination unit 102b has determined to be "disbursements due to fund transfers within the group" and records that have been determined to be "fund transfers between branches," thereby adding records to the journal entry creation target table 106bc shown in Figure 15.

[0064] Based on these data generation rules, a record with the deposit / withdrawal number "N1002" shown in Figure 15 is added from record ba004 in the details table 106ba shown in Figure 13. Additionally, a record with the deposit / withdrawal number "N1003" shown in Figure 15 is added from record ba005 in the details table 106ba shown in Figure 13, and records with deposit / withdrawal numbers "N1004" and "N1005" are added from records ba007 and ba009 in the details table 106ba, respectively.

[0065] [3-4. Journal entry processing] Furthermore, the journal entry unit 102d generates each record in the journal entry details table 106bd shown in Figure 16 from each record in the journal entry target table 106bc shown in Figure 15. Figure 16 is a diagram showing an example of the journal entry details table 106bd according to the embodiment. If the receipt / payment category of a record in the journal entry target table 106bc is "2", the journal entry unit 102d adds the record to the journal entry details table 106bd based on the group withdrawal journal entry rules shown below. <Rules for journalizing withdrawals within the group> 1. For the debit account, retrieve the account code "999: CMS Adjustment Account" (item SEQ=1) from the identification master 106ab. 2. For credit accounts, retrieve the account code from settlement account master 106aa that corresponds to the settlement account in the record of journal entry details table 106bd. 3. The columns for Occurrence Date, Business Establishment Code, Department Code, and Amount shall be filled with the corresponding items from the relevant record in the journal entry creation table 106bc. Note that the slip number is assigned sequentially each time a record is generated, and the line number is assigned sequentially within the slip number.

[0066] By applying this withdrawal journal entry rule, a record with transaction number "S1002" in the journal entry details table 106bd is generated from the record with deposit / withdrawal number "N1002" in the journal entry target table 106bc. As shown in Figure 16, the credit account for the record with transaction number "S1002" is entered with the account code "100: Deposit (Head Office)" which corresponds to the settlement account "000".

[0067] Furthermore, the journal entry unit 102d determines whether the description of a record in the journal entry target table 106bc includes "Zandakafurikae Haibun" if the receipt / payment category of that record is "1".

[0068] If the journal entry unit 102d determines that the description contains "Zandakafurikae Haibun", it adds a record to the journal entry details table 106bd for that record based on the group deposit journal entry rules shown below. <Rules for journal entries for intercompany receipts> 1. For each debit account, retrieve the account code from settlement account master 106aa that corresponds to the settlement account in the record of journal entry details table 106bd. 2. For the credit account, retrieve the account code "999: CMS Adjustment Account" (item SEQ=1) from the identification master 106ab. 3. The columns for Occurrence Date, Business Establishment Code, Department Code, and Amount shall be filled with the corresponding items from the relevant record in the journal entry creation table 106bc. Note that the slip number is assigned sequentially each time a record is generated, and the line number is assigned sequentially within the slip number.

[0069] By applying this group-internal deposit journal entry rule, a record with transaction number "S1001" in the journal entry details table 106bd is generated from the record with deposit / withdrawal number "N1001" in the journal entry target table 106bc. As shown in Figure 16, the debit account of the record with transaction number "S1001" is entered with the account code "100: Deposit (Head Office)" which corresponds to the settlement account "000".

[0070] Furthermore, if the journal entry unit 102d determines that the deposit / payment category of a record in the journal entry target table 106bc is "1" and the description of the record does not include "Zandakafurikae Haibun", it adds a record to the journal entry details table 106bd for that record based on the inter-branch deposit / payment journal entry rules shown below. <Rules for journal entries for deposits between head office and branches> 1. For the debit account, retrieve the account code from the settlement account master 106aa that corresponds to the settlement account in the record of the journal entry target table 106bc. 2. For credit accounts, retrieve the account code from settlement account master 106aa that corresponds to the remitter name in the record of journal entry target table 106bc. 3. The columns for Occurrence Date, Business Establishment Code, Department Code, and Amount shall be filled with the corresponding items from the relevant record in the journal entry creation table 106bc. Note that the slip number is assigned sequentially each time a record is generated, and the line number is assigned sequentially within the slip number.

[0071] By applying this inter-branch deposit journal entry rule, a record with transaction number "S1003" in the journal entry details table 106bd is generated from the record with deposit / withdrawal number "N1003" in the journal entry target table 106bc. As shown in Figure 16, for example, in the record for voucher number "S1003", the debit account is entered with the account code "100: Deposit (Head Office)" corresponding to the settlement account "000", and the credit account is entered with the account code "110: Deposit (Branch (1))" corresponding to the remitter name "●● (Shiten 000000001)". Similarly, the record for voucher number "S1004" is generated from the deposit / withdrawal number "N1004" record in the journal entry creation target table 106bc, and the record for voucher number "S1005" is generated from the deposit / withdrawal number "N1005" record. In each record for voucher numbers "S1004" and "S1005", the credit account is entered with the account code "100: Deposit (Head Office)" corresponding to the remitter name "●● (Honten 000000000)".

[0072] As described above, the business support device 100 according to the embodiment has an acquisition unit 102a and a determination unit 102b. The acquisition unit 102a acquires detailed information 1000 including source information, recipient information, deposit / withdrawal category, and description. The determination unit 102b determines whether the detailed information relates to fund transfers within the group or between branches, based on the source information, recipient information, deposit / withdrawal category, and description of the acquired detailed information.

[0073] With this configuration, deposit and withdrawal data can be identified using only the "settlement account," "remitter name," and "description details" included in the details table 106ba shown in Figure 10, without using other identification information such as a list of remitter names. This makes it easy to determine, with a simple configuration, whether a transaction is a fund transfer between branches, a fund transfer within the group, or a deposit or withdrawal subject to receivable reconciliation.

[0074] Furthermore, in this embodiment, whether or not a transfer constitutes an intra-group fund transfer is determined by the "name of the remitter," the "settlement account," and the "description." In this configuration, for example, even if a new group company is added, by setting the "name of the remitter" and the "description" to those specified in the discrimination master 106ab, it is possible to easily determine whether or not a transfer constitutes an intra-group fund transfer without having to prepare a separate table or the like.

[0075] [4. Contribution to the United Nations-led Sustainable Development Goals (SDGs)] This embodiment can contribute to improving operational efficiency and promoting appropriate management decisions within companies, thereby enabling contributions to SDGs Goals 8 and 9.

[0076] Furthermore, this embodiment can contribute to reducing waste and promoting paperless and digital processes, thereby contributing to SDGs Goals 12, 13, and 15.

[0077] Furthermore, this embodiment can contribute to strengthening control and governance, thereby enabling contributions to SDG Goal 16.

[0078] [5. Other Embodiments] In addition to the embodiments described above, the present invention may be implemented in various different embodiments within the scope of the technical idea described in the claims.

[0079] 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 by known methods.

[0080] Furthermore, the processing procedures, control procedures, specific names, information including parameters such as registration data and search conditions for each process, screen examples, and database configuration shown in this specification and in the drawings may be changed at will unless otherwise specified.

[0081] Furthermore, with respect to the business support device 100, each component shown in the diagram is a functional concept and does not necessarily need to be physically configured as shown.

[0082] For example, the processing functions of the business support device 100, particularly those performed by the control unit, may be implemented in whole or in part by a CPU and a program interpreted and executed by the CPU, or they may be implemented as wired logic hardware. The program is recorded on a non-temporary computer-readable recording medium containing programmed instructions for the information processing device to execute the processing described in this embodiment, and is mechanically read by the business support device 100 as needed. That is, a storage unit such as ROM or HDD (Hard Disk Drive) stores a computer program that works in cooperation with the OS to give instructions to the CPU and perform various processing tasks. This computer program is executed by being loaded into RAM and works in cooperation with the CPU to form the control unit.

[0083] Furthermore, this computer program may be stored on an application program server connected to the business support device 100 via any network, and it is possible to download all or part of it as needed.

[0084] Furthermore, the program for executing the processing described in this embodiment may be stored on a non-temporary computer-readable recording medium, or it may be configured as a program product. Here, "recording medium" includes any "portable physical medium" such as memory cards, USB (Universal Serial Bus) memory, SD (Secure Digital) cards, flexible disks, magneto-optical disks, ROMs, EPROMs (Erasable Programmable Read Only Memory), EEPROMs (Registered Trademark) (Electrically Erasable and Programmable Read Only Memory), CD-ROMs (Compact Disk Read Only Memory), MOs (Magneto-Optical disks), DVDs (Digital Versatile Disks), and Blu-ray (Registered Trademark) Discs.

[0085] Furthermore, "program" refers to a data processing method described in any language or writing method, regardless of its format, such as source code or binary code. Note that "program" is not necessarily limited to a single, monolithic structure; it also includes distributed structures consisting of multiple modules or libraries, and those that work in cooperation with other programs, such as an operating system, to achieve their functions. Regarding the specific configuration and reading procedures for reading the recording medium in each device shown in the embodiments, as well as the installation procedures after reading, well-known configurations and procedures can be used.

[0086] The various databases stored in the memory unit are 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 website provision.

[0087] Furthermore, the business support device 100 may be configured as a known personal computer or workstation or other information processing device, or as an information processing device to which any peripheral devices are connected. Alternatively, the business support device 100 may be implemented by installing software (including programs or data, etc.) that enables the processing described in this embodiment on the device.

[0088] Furthermore, the specific forms of distribution and integration of the devices are not limited to those shown in the figures, and all or part of them can be configured by functionally or physically distributing and integrating them in any unit according to various additions or functional loads. In other words, the embodiments described above may be implemented in any combination, or the embodiments may be implemented selectively. [Industrial applicability]

[0089] This invention is useful for companies and other entities that transfer funds within a group or between head offices and branches. [Explanation of Symbols]

[0090] 1. Business support system 100 Business support equipment 102 Control Unit 102a Acquisition Department 102b Judgment section 102c generator 102d Journal Entry Department 104 Communication Interface Section 106 Storage section 106a Master Storage Unit 106aa Payment Account Master 106ab Discrimination Master 106b Data storage unit 106ba Details Table 106bb deposit table 106bc Journal entry creation target table 106bd Journal Entry Details Table 108 Input / Output Interface Section 200 terminal devices 300 Networks

Claims

1. An acquisition unit that acquires detailed information including source information, recipient information, deposit / withdrawal category, and description, A determination unit determines whether the transaction information relates to a fund transfer within the group or between branches, based on the source information, recipient information, deposit / withdrawal category, and description of the acquired transaction information. A business support device having the following features.

2. The determination unit, If the deposit / withdrawal category in the acquired statement information is determined to be a withdrawal, it is determined whether the description, the recipient information, and the source information relate to a fund transfer within the group. The business support device according to claim 1.

3. The determination unit, If the deposit / withdrawal category in the acquired statement information is a deposit, determine whether the transfer destination information belongs to the head office or a branch office. If the aforementioned recipient information is determined to be that of a branch, then it is determined whether the aforementioned source information pertains to a transfer of funds between the head office and the branch. The business support device according to claim 1.

4. The determination unit, If the deposit / withdrawal category in the acquired statement information is a deposit, determine whether the transfer destination information belongs to the head office or a branch office. If it is determined that the aforementioned transfer recipient information belongs to the head office, it is determined whether the aforementioned transfer source information relates to a fund transfer within the group, a fund transfer between the head office and branches, or something else. The business support device according to claim 3.

5. Based on the determination results from the determination unit, a generation unit generates information regarding fund transfers within the group, information regarding fund transfers between branches, and information regarding deposits subject to reconciliation. A journal entry unit generates journal entry information using the generated information on fund transfers within the group and information on fund transfers between the head office and branches, The business support device according to claim 1, further comprising the above.

6. A business support method performed by a business support device equipped with a control unit, The control unit, Steps include obtaining detailed information including source information, recipient information, deposit / withdrawal type, and description, The steps include determining whether the transaction information pertains to a fund transfer within the group or between branches, based on the source information, recipient information, deposit / withdrawal category, and description of the acquired transaction information, A business support method characterized by performing the following actions.

7. A business support program to be executed by a business support device equipped with a control unit, The control unit, Steps include obtaining detailed information including source information, recipient information, deposit / withdrawal type, and description, The steps include determining whether the transaction information pertains to a fund transfer within the group or between branches, based on the source information, recipient information, deposit / withdrawal category, and description of the acquired transaction information, A business support program characterized by its ability to execute certain actions.

Images