JP5862144B2 - Server apparatus and program - Google Patents

Description

  The present invention relates to a server device, a consumption method, and a program.

  Generally, an accounting system such as an ERP (Enterprise Resource Planning) package has an application processing function for receivable receivables to be matched with deposits. There is also a form in which a plurality of group companies use a common accounting system. In the case where a plurality of group companies conduct transactions with the same customer, usually, a deposit process is performed from the customer to each group company.

  However, in a form in which a plurality of group companies use a common accounting system, it may be assumed that the sum of payment amounts for each of the plurality of group companies is paid from the customer to one of the group companies. Since the receivables to be cleared are recorded in each company, it is necessary to distribute the deposit to each company for the settlement process.

  This invention is made in view of the above, Comprising: Even if it is a case where the total amount of the money_receiving | payment with respect to a some company is paid in one company, the server apparatus which can perform a payment application process efficiently An object is to provide an application method and program.

In order to solve the above-described problems and achieve the object, the present invention provides a storage unit for storing a credit for each of a plurality of different companies, and a first company and a second company included in the plurality of companies, respectively. A total amount of money to be deposited, and a first reception unit that accepts input of the deposit amount deposited to the first company, and a transfer that represents the amount to be transferred to the second company out of the deposited amount A second accepting unit that accepts an input of an amount; and performing an application process of the first company's receivable stored in the storage unit using an amount obtained by subtracting the transfer amount from the deposit amount, and using the transfer amount And a clearing unit that performs a clearing process on the claims of the second company stored in the storage unit .

In addition, the present invention provides a deposit amount obtained by summing amounts of money to be deposited in a first company and a second company included in the plurality of companies, each of which includes a storage unit that stores a receivable for each of a plurality of different companies. A first reception unit that receives an input of the deposit amount received by the first company, and a second reception unit that receives an input of a transfer amount representing an amount to be transferred to the second company out of the deposit amount And a second company stored in the storage unit using the transfer amount by performing a process of clearing the first company's receivable stored in the storage unit using an amount obtained by subtracting the transfer amount from the deposit amount. This is a program for functioning as a clearing unit that performs clearing processing of corporate bonds.

  According to the present invention, even when the total amount of money received for a plurality of companies is deposited into one company, there is an effect that it is possible to efficiently execute the deposit application process.

FIG. 1 is a block diagram illustrating a configuration example of an accounting system including a server device according to the present embodiment. FIG. 2 is a diagram illustrating an example of a data structure of data stored in the company master. FIG. 3 is a diagram illustrating an example of a data structure of data stored in the activity master. FIG. 4 is a diagram illustrating an example of a data structure of transaction information. FIG. 5 shows an example of the data structure of the deposit information. FIG. 6 is a diagram illustrating an example of the data structure of the consumption information. FIG. 7 is a diagram illustrating an example of a data structure of transfer data. FIG. 8 is a diagram showing an example of the overall flow of deposit transfer processing between companies. FIG. 9 is a diagram illustrating an example of a payment confirmation screen. FIG. 10 is a diagram illustrating an example of an application screen. FIG. 11 is a diagram illustrating an example of the consumption information. FIG. 12 is a flowchart illustrating an example of the overall flow of transfer data extraction processing. FIG. 13 is a flowchart showing an example of the overall flow of the registration file creation process. FIG. 14 is a diagram illustrating an example of data in the transfer data accumulation table. FIG. 15 is a flowchart showing an example of the overall flow of the deposit registration process. FIG. 16 is a diagram showing an example of deposit information registered in the deposit information table. FIG. 17 is a diagram showing an example of application information corresponding to the deposit information shown in FIG. FIG. 18 is a diagram illustrating an example of the overall flow of the transfer list creation process. FIG. 19 is a diagram illustrating an example of data in the transfer data accumulation table. FIG. 20 is a diagram illustrating an example of an inter-company deposit transfer list. FIG. 21 is a diagram illustrating an example of deposit information stored after the deposit transfer process is executed. FIG. 22 is a diagram illustrating an example of application information stored after the deposit transfer process is executed. FIG. 23 is an explanatory diagram illustrating a hardware configuration of the server device according to the present embodiment.

  Exemplary embodiments of a server device, a consumption method, and a program according to the present invention will be explained below in detail with reference to the accompanying drawings.

Here, the problems in the conventional accounting system will be further described. As described above, in a form in which a plurality of companies use a common accounting system, it is assumed that the total amount of payment for a plurality of companies is paid to one of the plurality of companies. In such a case, it is necessary to distribute the payment to each company for the application process. For this purpose, for example, the following deposit process can be considered.
(A1) A company that has received money from a customer manually inputs transfer data from a provisional receipt to another account for the amount to be transferred to another company.
(A2) A company that holds a claim and manually inputs a dummy deposit for erasing the claim.

However, such deposit processing may cause the following problems.
(B1) Since it is necessary to carry out the operation (A2) at each company that holds the bond, the workload of the person in charge of work is large.
(B2) Although it is necessary to match the transfer amount of (A1) and the deposit amount of (A2), there is a risk that a difference occurs due to manual input.

Therefore, in the server device of the present embodiment, the deposit process for the application process is performed according to the following procedure.
(C1) The transfer data from the temporary receipt to the other account at the company (hereinafter referred to as the transfer source company) received from the customer is input manually. This is because the transfer amount to another company cannot be calculated automatically. However, in order to simplify and unify the input work, another company that holds the receivable (hereinafter referred to as the transfer destination company) can be easily selected on the screen by a pull-down list or the like.
(C2) Payment registration to the transfer destination company is automatically performed by the system during night processing based on the information manually input in (C1) above. As a result, it is possible to reduce the workload of business staff, prevent work omissions and incorrect input of amounts, and reduce the time lag.
(C3) After the processing of (C2), the processing results of (C1) and (C2) for the previous day are output to a report (form). At this time, in order for the business person in charge to check the processing status for the necessary daily amount and the necessity of the subsequent work, the report is output with a page break for each combination of the transfer source company and the transfer destination company.

  FIG. 1 is a block diagram illustrating a configuration example of an accounting system including a server device according to the present embodiment. The accounting system of this embodiment has a configuration in which a server device 100 and a plurality of client devices 300a and 300b are connected by a network 200.

  The server apparatus 100 is an apparatus that executes an accounting process including at least an application process for matching a bond with a deposit. The server device 100 can be realized by a device in which an ERP package is introduced, for example. The plurality of client devices 300 a and 300 b are devices for using various functions provided by the server device 100. Since the client devices 300a and 300b have the same function, they are simply referred to as the client device 300 when it is not necessary to distinguish them. The client device 300 is installed in each company to which the accounting system is applied, for example. The network 200 can employ any network form conventionally used, such as a LAN (Local Area Network) and the Internet.

  The server apparatus 100 includes a company master 121, an activity master 122, a transaction information table 123, a deposit information table 124, a deposit transfer table 125, a transfer data storage table 126, an input / output control unit 101, and a display control unit. 102, an extraction unit 103, and a consumption unit 104.

  The company master 121 is a storage unit that stores data regarding each company that uses the accounting system. FIG. 2 is a diagram illustrating an example of a data structure of data stored in the company master 121. As shown in FIG. 2, the company master 121 stores an organization ID, a company code, and a company name. Both the organization ID and the company code are information that can be used as identification information for identifying the company.

  Returning to FIG. 1, the activity master 122 is a storage unit that stores data relating to activities representing transfer (transfer) processing (hereinafter also referred to as “payment transfer processing”). FIG. 3 is a diagram illustrating an example of a data structure of data stored in the activity master 122. As shown in FIG. 3, the activity master 122 stores an activity ID, an organization ID, an activity name, and a transfer destination company code. The activity ID is identification information for identifying an activity. The organization ID in the activity master 122 represents the organization ID of the transfer source company. The transfer destination company code is a company code corresponding to the transfer destination company. Therefore, the data stored in the activity master 122 can identify the correspondence between the deposit transfer source company and the transfer destination company that performs the deposit transfer process.

  Returning to FIG. 1, the transaction information table 123 is a storage unit that stores transaction information regarding transactions that have occurred with customers. FIG. 4 is a diagram illustrating an example of a data structure of transaction information. As shown in FIG. 4, the transaction information includes an organization ID, a transaction ID, a transaction number, a currency, a transaction date, a recording date, a customer code, a customer name, a site code, a statement amount, Includes tax and initial balance.

  Both the transaction ID and the transaction number are information that can be used as identification information for identifying a transaction with a customer. The customer code is identification information for identifying a customer. The amount (initial balance) included in the transaction information corresponds to the receivable subject to application processing. FIG. 4 shows an example in which a transaction occurs with the same customer B Co., Ltd., both at A Sales Co., Ltd. (organization ID = 200) and Tochigi A Co., Ltd. (organization ID = 92).

  Returning to FIG. 1, the deposit information table 124 is a storage unit that stores deposit information including information such as the amount deposited by a customer. FIG. 5 shows an example of the data structure of the deposit information. As shown in FIG. 5, the deposit information includes a deposit ID, an organization ID, a deposit number, a deposit amount, a currency, a deposit date, a recording date, a collection method, a customer code, a customer name, Including site code. The deposit ID and the deposit number are both information that can be used as identification information for identifying deposit information.

  FIG. 5 shows an example of payment information in the case where the payment for the three transactions shown in FIG. That is, the example of FIG. 5 is an example of payment information when B Co., Ltd. deposits money from A Sales Co., Ltd. and Tochigi A Co., Ltd., which are a plurality of trading partners. In this case, it is necessary to transfer the deposit amount corresponding to the transaction information on the third line in FIG. 4 from A Sales Co., Ltd. to Tochigi A Co., Ltd.

  Returning to FIG. 1, the deposit transfer table 125 is a storage unit that stores information on deposits to be transferred (hereinafter also referred to as application information). FIG. 6 is a diagram illustrating an example of the data structure of the consumption information. As illustrated in FIG. 6, the deposit transfer table 125 stores a deposit ID, an application ID, a status, an application date, a recording date, an amount, an application transaction ID, and an activity ID.

  The application ID is identification information for identifying application information. The application transaction ID represents the transaction ID that is the target of the application process among the transaction IDs. The activity ID is stored in the case of application information for which a deposit transfer process is executed. That is, the activity ID of the deposit transfer table 125 can identify which activity in the activity master 122 in FIG. 3 corresponds to the application information.

  Note that the deposit transfer table 125 stores not only the transfer information for transferring from the transfer source company to the transfer destination company, but also the transfer information that is the target of normal application processing (processing for receivables to be matched with payment). You may comprise as follows. In other words, the application information used for the deposit transfer process may be stored in the application information table that has been used conventionally. As a result, development costs can be reduced without the need to construct a new table.

  Whether the information is the application information that is the subject of the deposit transfer process or the application information that is the subject of the normal application process can be determined from the status, for example. That is, status = “APP” is application information that is subject to normal application processing, and status = “ACTIVITY” is application information that is subject to deposit transfer processing.

  FIG. 6 shows an example of the deposit transfer table 125 that stores application information that is a target of a normal application process. That is, FIG. 6 illustrates two pieces of application information corresponding to the transaction information on the first and second lines in which the deposit transfer process is not performed among the transaction information of FIG. When the application process is executed for these two cases, the unapplied balance becomes 5,409 yen.

  Returning to FIG. 1, the transfer data accumulation table 126 is a memory for accumulating the application information extracted as the object of the payment transfer process (hereinafter referred to as transfer data) among the application information stored in the payment transfer table 125. Part. FIG. 7 is a diagram illustrating an example of a data structure of transfer data. As illustrated in FIG. 7, the transfer data includes transfer source information, transfer destination information, and a processing category.

  The transfer source information includes an organization ID of the transfer source company, a payment ID, an application ID, a customer code, a site code, a payment date, a payment recording date, and a transfer amount. The transfer amount represents the amount to be transferred from the transfer source company to the transfer destination company. The transfer destination information includes a company code of the transfer destination company, an organization ID of the transfer destination company, a payment ID, and a site code.

  The processing category is information representing the processing status of transfer data. For example, the processing classification = “0” indicates that the transfer data is newly registered. Further, the processing classification = “1” indicates that it has already been output to the deposit registration file. The deposit registration file is a file used for deposit processing (described later). Process classification = “2” indicates that the deposit has been registered in the transfer destination company.

  Note that the masters and tables shown in FIG. 1 are examples, and other masters and tables necessary for the accounting process may be provided. Each master and table can be constituted by any commonly used storage medium such as an HDD (Hard Disk Drive), an optical disk, a memory card, and a RAM (Random Access Memory). Also, each master and table need not be distributed as shown in FIG. It can be configured to be stored in any combination on one or more physical storage media.

  The input / output control unit 101 controls input / output of information with respect to the server apparatus 100. For example, the input / output control unit 101 controls processing for accepting input of various data necessary for accounting processing from the client device 300 or the like. Further, the input / output control unit 101 controls processing for outputting various data necessary for the accounting processing and various data representing processing results to the client device 300 and the like. Further, the input / output control unit 101 controls a printing process for outputting a report representing the result of the deposit transfer process to a printer or the like connected to the client device 300 or the like.

  The display control unit 102 controls display processing on a display unit (not shown) of an external device such as the client device 300. For example, the display control unit 102 displays a payment confirmation screen or a cancellation screen on the client device 300. The payment confirmation screen is a screen for confirming information related to payment from a customer. The application screen is a screen for inputting application information. Details of the payment confirmation screen and the application screen will be described later.

  The extraction unit 103 extracts data to be processed from each table. For example, the extraction unit 103 extracts, from the deposit transfer table 125, the application information that is the subject of the deposit transfer process, and stores it in the transfer data accumulation table 126. Further, the extraction unit 103 extracts, from the transfer data accumulation table 126, transfer data in which the designated company is the transfer destination company.

  The application unit 104 executes an application process using the application information. For example, when the application unit 104 receives money from a customer to an individual company, the application unit 104 performs an application process on the credit of the company as in the past. In addition, the application unit 104 uses the transfer amount entered as the amount to be transferred out of the deposit amount when the total deposit amount to a plurality of companies is deposited into one company (transfer source company). To clear the receivables of the transferee company. Further, in this case, the clearing unit 104 performs the process of clearing the receivable of the transfer source company using the amount obtained by subtracting the transfer amount to each transfer destination company from the deposit amount.

  Next, an outline of the deposit transfer process will be described. FIG. 8 is a diagram showing an example of the overall flow of deposit transfer processing between companies. The deposit transfer process mainly includes five processes (1) to (5). In FIG. 8, the process executed according to the instruction of the user of the transfer source company and the process executed according to the instruction of the user of the transfer source company are described separately. The common area in FIG. 8 represents one of the storage units in the server device 100.

  In the process (1), first, the user of the transfer source company inputs transfer data using, for example, the client device 300 provided in the transfer source company (step S101). The input transfer data is stored in the deposit transfer table 125.

  The process (2) is executed at night, for example. In the process (2), the extraction unit 103 executes a transfer data extraction process (step S102). In the transfer data extraction process, application information to be transferred to another company is extracted from the deposit transfer table 125 for each transfer source company. The extraction unit 103 stores the extracted consumption information in the transfer data accumulation table 126 as transfer data.

  In the process (3), the extraction unit 103 executes a registration file creation process (step S103). In the registration file creation process, transfer data with the company as the transfer destination is extracted for each transfer destination company and registered in the deposit registration file. The payment registration file registers not only transfer data for transferring between companies, but also data for transferring money from a customer to an individual company as usual. Thus, thereafter, the same deposit registration process and application process as normal deposit (payment from customer to individual company) may be executed. That is, it is not necessary to develop a new function only for transfer data.

  In the process (4), the application unit 104 executes a payment registration process (step S104). In the deposit registration process, a process of deleting the deposited amount (transfer amount) is executed based on the transfer data stored in the deposit registration file. In the payment registration process, the payment information table 124 is used for registering data to be applied for the application process and storing the processing results.

  In the process (5), the input / output control unit 101 executes a transfer list creation process (step S105). In the transfer list creation process, a report (inter-company payment transfer list) representing the result of the payment transfer process is printed.

  Next, details of the process (1) will be described. FIG. 9 is a diagram showing an example of a payment confirmation screen displayed in the process (1). When the display control unit 102 receives a request for displaying the deposit confirmation screen from the client device 300, the display control unit 102 displays the deposit confirmation screen on the display unit of the client device 300. The user of the transfer source company searches for payment information to be subjected to the payment transfer process by using, for example, a search screen (not shown).

  The payment confirmation screen in FIG. 9 shows an example of the payment confirmation screen on which the payment information searched in this way is displayed. The deposit information in FIG. 9 corresponds to the deposit information exemplified in the deposit information table 124 in FIG. Below, the case where a payment transfer process is mainly performed based on this payment information is demonstrated to an example.

  When the application button is pressed on the payment confirmation screen, the application screen is displayed. FIG. 10 is a diagram illustrating an example of an application screen. The user of the transfer source company enters the transaction information to be applied for the application process and the amount to be applied (applied amount) on the application screen. On the application screen, application information for transferring at least a part of the deposit amount included in the receipt information to the transfer destination company can be input. In the case of a payment transfer process, the user changes the “application object” field corresponding to the amount to be transferred to “payment application”. Further, the user selects an activity name that can identify the deposit transfer process and the transfer destination company in the “activity” field 1001. FIG. 10 shows an example in which “sales company integrated payment transfer (Tochigi)” representing an activity that is a deposit transfer process for Tochigi A Co., Ltd. is selected.

  In order to easily select the transfer destination company, for example, when the “activity” field 1001 is pressed, a pull-down list that allows selection of the transfer destination company of the deposit transfer process may be displayed. . That is, the display control unit 102 searches for an activity name corresponding to the organization ID of the user's company from the activity master 122 shown in FIG. 3, for example, and displays it on the client device 300 used by the user. Note that the designation method in FIG. 10 is an example, and any method can be applied as long as it can designate at least the amount to be transferred (transfer amount, the amount already applied in FIG. 10) and the transfer destination company. .

  After step S <b> 101, for example, the application information shown in FIGS. 6 and 11 is stored in the deposit transfer table 125. FIG. 11 shows an example of consumption information corresponding to the third line of the consumption screen of FIG. At the time when the application process is executed for this one item, the unapplied balance is 0 yen.

  Next, details of the process (2) will be described. FIG. 12 is a flowchart illustrating an example of the overall flow of transfer data extraction processing. The extraction unit 103 performs initial processing such as acquisition of a fixed value (step S201). The extraction unit 103 extracts unprocessed application information from the deposit transfer table 125 (step S202). For example, the extraction unit 103 extracts, from the deposit transfer table 125, the consumption information with status = “ACTIVITY” among the consumption information.

  The extraction unit 103 acquires unprocessed consumption information (extraction data) among the extracted consumption information (step S203). The extraction unit 103 determines whether or not the acquired application information is payment in customer units (step S204). When it is not payment of a customer unit (step S204: No), the extraction part 103 acquires customer site information (step S205). When the payment is made in units of customers (step S204: Yes), the extraction unit 103 determines whether or not the collection method of the application information is a collection method that is a processing target of the deposit transfer process (step S206). When the collection method is a collection method to be processed in the deposit transfer process (step S206: Yes), the extraction unit 103 sets a code “0” representing the newly registered transfer data in the process category (step S207). . If it is not the collection method to be processed in the deposit transfer process (step S206: No), the extraction unit 103 sets a code indicating that an error has occurred in the process category (step S208).

  The extraction unit 103 stores, in the transfer data accumulation table 126, transfer data obtained by adding information such as a processing category to the extracted consumption information (Step S209). 7 described above is a transfer created based on the application information extracted from FIG. 11, which is the object of the payment transfer process, among the application information shown in FIGS. 6 and 11 stored in the payment transfer table 125. An example of storing data is shown.

  Note that the extraction unit 103 acquires each piece of information included in the transfer data in FIG. 7 as follows, for example. As the organization ID, the organization ID of the company currently processing may be set. The payment ID, application ID, and transfer amount correspond to the payment ID, application ID, and amount of the extracted application information, respectively. The customer code, site code, payment date, and payment date can be acquired from the customer code, site code, payment date, and date of payment information corresponding to the payment ID. The company code can be acquired from the activity master 122 as a transfer destination company code corresponding to the activity ID.

  The extraction unit 103 determines whether or not all the consumption information has been extracted (step S210). If not extracted (step S210: No), the extraction unit 103 returns to step S203 and repeats the process. When all the consumption information has been extracted (step S210: Yes), the extraction unit 103 performs post-processing such as log output (step S211), and ends the transfer data extraction processing.

  Next, details of the process (3) will be described. FIG. 13 is a flowchart showing an example of the overall flow of the registration file creation process. The extraction unit 103 executes initial processing such as acquisition of a fixed value (step S301). The extraction unit 103 determines whether there is a deposit registration file (unimported file) that has not been imported into the deposit information table 124 (step S302). If it exists (step S302: Yes), a new payment registration file cannot be created, so error processing such as log output is executed (step S303), and the registration file creation processing is terminated.

  When there is no uncaptured file (step S302: No), the extraction unit 103 extracts all unprocessed transfer data for the company from the transfer data accumulation table 126 (step S304). The extraction unit 103 acquires unprocessed extracted data from the extracted transfer data (extracted data) (step S305).

  The extraction unit 103 acquires the site code of the transfer destination company based on the company code of the extracted data (step S306). The extraction unit 103 determines whether or not the site code has been successfully acquired (step S307). If it can be acquired (step S307: Yes), the extraction unit 103 acquires the employee number of the employee of the transfer destination company (step S308). The extraction unit 103 determines whether the employee number has been acquired normally (step S309).

  If it can be acquired (step S309: Yes), the extraction unit 103 checks the recording date of the transfer destination (step S310). The extraction unit 103 determines whether or not the transfer source recording date matches the transfer destination recording date (step S311). If they match (step S311: Yes), the extraction unit 103 outputs the extracted data to the deposit registration file (step S312). The extraction unit 103 sets “1” indicating that the data has already been output to the deposit registration file as a processing category (step S314).

  The deposit registration file stores, for example, data obtained by adding the organization ID of the transfer destination company and the site code acquired in step S306 to the extracted data. The organization ID can be acquired from the company master 121 using, for example, the company code of the transfer destination company as a key.

  If the site code cannot be acquired (step S307: No), the employee number cannot be acquired (step S309: No), and the transfer source recording date does not match the transfer destination recording date (step S311: No). ) The extraction unit 103 sets a code indicating that an error has occurred in the processing category (step S313).

  The extraction unit 103 updates the transfer data accumulation table 126 (step S315). For example, the extraction unit 103 updates the organization ID and site code of the transfer destination company to the same values as the organization ID and site code output to the deposit registration file. Further, the extraction unit 103 updates the processing classification to the value set in step S313 or step S314. FIG. 14 shows an example of data in the transfer data accumulation table 126 updated from FIG. 7 in this way.

  Returning to FIG. 13, the extraction unit 103 determines whether or not all the extracted data has been processed (step S316). If the extraction unit 103 has not processed the extracted data (step S316: No), the extraction unit 103 returns to step S305 and repeats the process. When all the extracted data has been extracted (step S316: Yes), the extraction unit 103 performs post-processing such as log output (step S317), and ends the registered file creation processing.

  Next, details of the process (4) will be described. FIG. 15 is a flowchart showing an example of the overall flow of the deposit registration process. As described above, the deposit registration file stores not only data to be transferred between companies but also data for depositing money from the customer to the company.

  The consumption unit 104 performs initial processing such as acquisition of a fixed value (step S401). The application unit 104 reads data from the deposit registration file and stores the read data in a work table (not shown) for work (step S402).

  The application unit 104 acquires unprocessed data from the work table (step S403). The consumption unit 104 determines whether or not the acquired data is return data (step S404). When it is return data (step S404: Yes), the application part 104 judges whether the existing payment information corresponding to the payment information table 124 exists (step S405). When it exists (step S405: Yes), the application part 104 performs the payment return process with respect to the existing payment information (step S406).

  If it is determined in step S404 that the data is not return data (step S404: No), the application unit 104 determines whether there is existing deposit information corresponding to the deposit information table 124 (step S407). When it exists (step S407: Yes), the application part 104 updates the existing payment information with the newly acquired data (step S408). If there is no existing payment (step S407: No), the application unit 104 registers it as new payment information in the payment information table 124, and executes an application process using the payment information (step S409).

  FIG. 16 is a diagram showing an example of deposit information created from the transfer data in the transfer data storage table 126 as shown in FIG. 14 and registered in the deposit information table 124. As the deposit ID and deposit number, newly acquired values are set for the deposit information. As the organization ID and site code, the organization ID and site code included in the transfer destination information of the transfer data are set. Each information from the deposit amount to the customer name is set to the same value as the deposit information of the transfer source. FIG. 17 is a diagram showing an example of application information corresponding to the deposit information shown in FIG. The consumption unit 104 executes the consumption process using the consumption information as shown in FIG.

  Returning to FIG. 15, when there is no existing deposit (step S405: No), and after execution of step S406, step S408, and step S409, the application unit 104 updates the data to have been processed (step S410). .

  The application unit 104 determines whether or not all data in the work table has been processed (step S411), and if not processed (step S411: No), returns to step S403 and repeats the processing. When all the data has been processed (step S411: Yes), the application unit 104 performs post-processing such as log output (step S412), and ends the deposit registration processing.

  Next, details of the process (5) will be described. FIG. 18 is a diagram illustrating an example of the overall flow of the transfer list creation process. First, the consumption unit 104 executes initial processing such as acquisition of a fixed value (step S501). The application unit 104 checks the processing result of the deposit registration process (step S502), and determines whether or not the processing result includes the result of the deposit transfer process with the company as the transfer destination (step S503). If it does not exist (step S503: No), the consumption unit 104 sets a code indicating that an error has occurred in the processing category (step S504). If it exists (step S503: Yes), the application unit 104 sets a code “2” indicating that the payment has been registered in the processing category (step S505).

  The application unit 104 updates the transfer data accumulation table 126 (step S506). For example, the application unit 104 updates the payment ID of the transfer destination company to the payment ID of the payment information created from the transfer data. Further, the consumption unit 104 updates the processing classification to the value set in step S504 or step S505. FIG. 19 shows an example of data in the transfer data accumulation table 126 updated from FIG. 14 in this way.

  The input / output control unit 101 extracts the transfer data stored after the previous time from the transfer data accumulation table 126 (step S507). The input / output control unit 101 acquires unprocessed transfer data among the extracted transfer data (step S508). The input / output control unit 101 determines whether the processing category of the acquired transfer data is “2” (step S509). When the processing category is “2” (step S509: Yes), the input / output control unit 101 acquires payment information corresponding to the transfer data (step S510). For example, the input / output control unit 101 acquires the corresponding deposit information from the deposit information table 124 using the deposit ID included in the transfer destination information of the transfer data as a key.

  When the processing category is not “2” (step S509: No), and after acquiring the deposit information, the input / output control unit 101 stores the extracted transfer data in the transfer list output work table (step S511). . The input / output control unit 101 determines whether or not all transfer data has been processed (step S512). If not processed (step S512: No), the process returns to step S503 and repeats the process.

  When all the transfer data has been processed (step S512: Yes), the input / output control unit 101 outputs an inter-company payment transfer list based on the data stored in the work table (step S513). FIG. 20 is a diagram illustrating an example of an inter-company deposit transfer list. After executing post-processing such as log output (step S514), the input / output control unit 101 ends the transfer list creation processing.

  As a result of such processing, the transaction information of FIG. 4, the deposit information of FIG. 21, the application information of FIG. 22, and the transfer data of FIG. 19 finally exist. FIG. 21 is a diagram illustrating an example of deposit information stored after the deposit transfer process is executed. FIG. 22 is a diagram illustrating an example of application information stored after the deposit transfer process is executed. The deposit information in FIG. 21 includes the deposit information in both FIG. 5 and FIG. The consumption information in FIG. 22 includes the consumption information in FIGS. 6, 11, and 17, respectively.

  As described above, the server device according to the present embodiment realizes data linkage between companies (organizations) and can efficiently execute a payment application process even when the credit and the payment recording company are different. . That is, if the transfer destination information is designated at the depositing company, the deposit transfer process is automatically performed, and the deposit registration to the depositing company can be executed.

  Since information about the transfer destination company can be easily selected by a user interface such as a pull-down list, the data input procedure at the transfer source company can be simplified and unified. In addition, as described in (A2) above, manual input of data at the receivable accounting company is not required, and the work load of the business staff can be reduced. As a result, since there are no work omissions or input mistakes, it is possible to avoid the risk of inconsistency between companies.

  In addition, the payment registration result in the night processing of the previous day can be confirmed with a report such as an inter-company payment transfer list. For this reason, it is possible to grasp the data and confirm the processing status, and it is possible to smoothly proceed to the subsequent work. Further, even if there is unprocessed data due to data deficiency (processing conditions are not satisfied), the business staff can quickly respond.

  Next, the hardware configuration of the server apparatus according to the present embodiment will be described with reference to FIG. FIG. 23 is an explanatory diagram illustrating a hardware configuration of the server device according to the present embodiment.

  The server device according to the present embodiment communicates with a control device such as a CPU (Central Processing Unit) 51 and a storage device such as a ROM (Read Only Memory) 52 and a RAM (Random Access Memory) 53 connected to a network. A communication I / F 54, an external storage device such as an HDD (Hard Disk Drive) and a CD (Compact Disc) drive device, a display device such as a display device, an input device such as a keyboard and a mouse, and a bus connecting each part 61, and has a hardware configuration using a normal computer.

  A program executed in the server device according to the present embodiment is a file in an installable format or an executable format, and is a CD-ROM (Compact Disk Read Only Memory), a flexible disk (FD), a CD-R (Compact Disk Recordable). ), A DVD (Digital Versatile Disk) or the like, recorded on a computer-readable recording medium and provided as a computer program product.

  The program executed by the server device according to the present embodiment may be stored on a computer connected to a network such as the Internet and provided by being downloaded via the network. Further, the program executed by the server device according to the present embodiment may be provided or distributed via a network such as the Internet.

  Further, the program of this embodiment may be configured to be provided by being incorporated in advance in a ROM or the like.

  The program executed by the server device according to the present embodiment has a module configuration including the above-described units (input / output control unit, display control unit, extraction unit, and consumption unit), and the CPU 51 is the actual hardware. (Processor) reads the program from the storage medium and executes the program, so that each unit is loaded onto the main storage device, and each unit described above is generated on the main storage device.

DESCRIPTION OF SYMBOLS 100 Server apparatus 101 Input / output control part 102 Display control part 103 Extraction part 104 Application part 121 Company master 122 Activity master 123 Transaction information table 124 Deposit information table 125 Deposit transfer table 126 Transfer data accumulation table 200 Network 300a, 300b Client apparatus

JP 2007-011712 A

Claims (5)

A storage unit for storing a credit for each of a plurality of different companies;
A first reception unit that accepts an input of the amount of money received by the first company, which is a total amount of money to be paid to each of the first company and the second company included in the plurality of companies ;
A second receiving unit for receiving an input of a transfer amount representing an amount to be transferred to the second company out of the deposit amount;
Using the amount obtained by subtracting the transfer amount from the deposit amount, the receivable of the first company stored in the storage unit is processed, and the second company stored in the storage unit is stored using the transfer amount. A clearing department that performs the clearing process for receivables;
A server device comprising: A display control unit configured to selectably display a plurality of the second companies that can be transferred to the transfer amount;
The second reception unit further receives the second company selected from the plurality of displayed second companies, and inputs the transfer amount to be transferred to the selected second company out of the deposit amount. Accepting,
The server device according to claim 1. A printing control unit that prints a form including at least the transfer amount transferred from the first company for each combination of the first company and the second company;
The server device according to claim 1.   The storage unit stores each of the plurality of credits for each company in association with information indicating customers of the credits,
  The second reception unit receives a selection of the second company among companies associated with one customer's receivable, and receives an input of a transfer amount representing an amount to be transferred to the received second company;
  The server device according to claim 1. A computer having a storage unit for storing a bond for each of a plurality of different companies ,
A first reception unit that accepts an input of the amount of money received by the first company, which is a total amount of money to be paid to each of the first company and the second company included in the plurality of companies ;
A second receiving unit for receiving an input of a transfer amount representing an amount to be transferred to the second company out of the deposit amount;
Using the amount obtained by subtracting the transfer amount from the deposit amount, the receivable of the first company stored in the storage unit is processed, and the second company stored in the storage unit is stored using the transfer amount. Clearing department that performs the clearing process for receivables,
Program to function as.

Images