JP2018139042A - Accounting processing system and accounting processing method - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide an accounting processing system that enables prompt reconciliation processing.SOLUTION: An accounting processing system for managing transaction data relating to a transaction between an orderer and an order receiver comprises: a payment schedule registering part that stores payment schedule data registered by the orderer and indicating a payment schedule from the orderer to the order receiver in a transaction data storage part; a payment application generating part that generates payment application data for applying for payment from the orderer to the order receiver on the basis of the payment schedule data; a payment application transmitting part that transmits the payment application data to a financial institution; and a payment schedule notification part for notifying the order receiver of the payment schedule to the order receiver on the basis of the payment schedule data.SELECTED DRAWING: Figure 2A

Description

  The present invention relates to an accounting processing system and an accounting processing method.

  When the transaction between the orderer and the contractor is settled through a financial institution such as a bank, the accounting processing system displays the accrual account generated based on the billing data from the contractor to the orderer and the order from the orderer. The application data is checked against the payment data indicating the completion of payment to the person. Thereby, the contractor manages whether the transaction is correctly recorded in the accounting system.

  When manually performing the application process, it is necessary to collate the accrual account and the payment data for each transaction, which is a considerable burden in the accounting process. For this reason, means for automating the application process by associating the accrual account with the receipt data has been studied. For example, Patent Literature 1 includes a billing data registration unit, a transaction specification registration unit, a matching processing unit, and an update registration unit, and automatically performs an application process even if the transaction details do not include a matching key. An application processing system that makes it possible to perform the above is disclosed.

JP 2014-59667 A

  However, in the application processing system described in Patent Document 1, the application process cannot be executed unless a transaction statement is issued from the bank. For this reason, even if there was a deposit instruction from the orderer, there was a concern that the accounting process would be delayed because it was necessary to wait for the transaction details to be issued from the bank.

  The present invention has been made in view of such circumstances, and an object of the present invention is to provide an accounting processing system capable of quick application processing.

  An accounting processing system according to an aspect of the present invention is an accounting processing system that manages transaction data relating to a transaction between an orderer and a contractor, and is a payment schedule from the orderer to the contractor registered by the orderer. A payment schedule registration unit that stores payment schedule data to be shown in the transaction data storage unit, a payment application generation unit that generates payment application data for applying for payment from the orderer to the contractor based on the payment schedule data, A payment application transmitting unit that transmits payment application data to a financial institution; and a payment schedule notifying unit that notifies the contractor of a payment schedule to the contractor based on the payment schedule data.

  An accounting processing system according to another aspect of the present invention is an accounting processing system for managing transaction data relating to a transaction between an orderer and a contractor, wherein billing data indicating a request for payment from the contractor to the orderer is provided. A billing registration unit stored in the transaction data storage unit, a payment plan registration unit stored in the transaction data storage unit, which is registered by the orderer and shows payment plan data indicating the payment plan from the orderer to the contractor, and payment plan data Based on the above, based on the payment application generation unit that generates payment application data for applying for payment from the orderer to the contractor, the payment application transmission unit that transmits the payment application data to the financial institution, An application generating unit that generates application data for applying the invoice data, an application registration unit that stores the application data in the transaction data storage unit, and an application that deletes the invoice data based on the application data And a non-clearing unit.

  In the present invention, the “part” does not simply mean a physical means, but includes a case where the function of the “part” is realized by software. Also, even if the functions of one “unit” or device are realized by two or more physical means or devices, the functions of two or more “units” or devices are realized by one physical means or device. May be.

  According to the present invention, it is possible to provide an accounting processing system capable of quick application processing.

It is a figure which shows the structure of the accounting processing system which concerns on 1st Embodiment of this invention. It is a figure which shows the structure of the transaction data processing part and transaction data storage part with which the accounting processing system which concerns on 1st Embodiment is equipped. It is a figure which shows an example of the transaction data stored in the claim data storage part of 1st Embodiment. It is a figure which shows an example of the transaction data stored in the payment plan data storage part of 1st Embodiment. It is a figure which shows an example of the transaction data stored in the tied data storage part of 1st Embodiment. It is a figure which shows the structure of the transaction data processing part and transaction data storage part with which the accounting processing system which concerns on 1st Embodiment is equipped. It is a figure which shows the structure of the transaction data processing part with which the accounting processing system which concerns on 2nd Embodiment is equipped, and a transaction data storage part. It is a flowchart which shows an example of the process in the accounting processing system which concerns on 2nd Embodiment. It is a figure which shows the structure of the transaction data processing part and transaction data storage part with which the accounting processing system which concerns on 3rd Embodiment is equipped. It is a flowchart which shows an example of the process in the accounting processing system which concerns on 3rd Embodiment. It is a figure which shows the structure of the transaction data processing part with which the accounting processing system which concerns on 4th Embodiment is equipped, and a transaction data storage part. It is a flowchart which shows an example of the process in the accounting processing system which concerns on 4th Embodiment. It is a figure which shows the structure of the transaction data processing part and transaction data storage part with which the accounting processing system which concerns on 5th Embodiment is equipped. It is a flowchart which shows an example of the process in the accounting processing system which concerns on 5th Embodiment. It is a figure which shows the structure of the transaction data processing part and transaction data storage part with which the accounting processing system which concerns on 6th Embodiment is equipped. It is a flowchart which shows an example of the process in the accounting processing system which concerns on 6th Embodiment. It is a figure which shows the structure of the transaction data processing part and transaction data storage part with which the accounting processing system which concerns on 7th Embodiment is equipped. It is a flowchart which shows an example of the process in the accounting processing system which concerns on 7th Embodiment.

  Embodiments of the present invention will be described below. In the following description of the drawings, the same or similar components are denoted by the same or similar reference numerals. The drawings are merely examples, and the functions and information exchange of each part are schematic, and the technical scope of the present invention should not be understood as being limited to the embodiments. In addition, in each embodiment, about the structure which has the same or similar function, the same name is attached | subjected and description is abbreviate | omitted suitably.

<First Embodiment>
First, the configuration of the accounting processing system 100 according to the first embodiment will be described with reference to FIG. FIG. 1 is a diagram showing a configuration of an accounting processing system according to the first embodiment of the present invention. Note that the accounting system according to each of the following embodiments has the same configuration as that shown in FIG.

  The accounting processing system 100 is an information processing system for managing transaction data related to transactions between the orderer 10A and the contractor 10B. As shown in FIG. 1, the accounting processing system 100 is communicably connected to computers of the orderer 10A and the contractor 10B via, for example, the Internet. In addition, the accounting processing system 100 is connected to a system of the financial institutions 20A and 20B so as to be communicable via the Internet, for example.

  The orderer 10A accesses the accounting processing system 100 via the user terminal 11A, and the contractor 10B accesses the accounting processing system 100 via the user terminal 11B. The user terminals 11A and 11B are computers used by the user, such as personal computers, smartphones, tablet terminals, and the like. For example, a client application for accessing the accounting processing system 100 is installed in the user terminals 11A and 11B. The client application may be a general-purpose application such as a web browser or an application dedicated to the accounting processing system 100. The accounting processing system 100 acquires transaction data from the user terminals 11A and 11B. Then, the accounting processing system 100 provides the user terminals 11A and 11B with data necessary for accounting processing or data subjected to accounting processing. Details will be described later.

  The financial institution 20A is an organization that manages deposits and withdrawals by the orderer 10A, and is, for example, a bank in which the orderer 10A has an account. The financial institution 20B is an organization that manages deposits and withdrawals by the contractor 10B, and is, for example, a bank in which the contractor 10B has an account. The financial institution 20A includes a deposit / withdrawal processing system 21A and a deposit / withdrawal recording system 22A, and the financial institution 20B includes a deposit / withdrawal processing system 21B and a deposit / withdrawal recording system 22B. Each system of the financial institutions 20A and 20B is configured using one or a plurality of computers. For example, the deposit / withdrawal processing system 21A provides an API (Application Programming Interface) for executing deposit / withdrawal processing. The deposit / withdrawal recording system 22A includes a database for managing account information. The deposit / withdrawal processing system 21B provides an API for executing deposit / withdrawal processing. The deposit / withdrawal recording system 22B includes a database for managing account information.

  The accounting processing system 100 includes a transaction data processing unit 100A and a transaction data storage unit 100B. The transaction data processing unit 100A acquires transaction data related to the transaction between the orderer 10A and the contractor 10B from the user terminals 11A and 11B and stores it in the transaction data storage unit 100B. For example, the transaction data processing unit 100A is an application server, and the transaction data storage unit 100B is a database. Transaction data processing unit 100A may change the acquired transaction data as necessary. The change of transaction data is, for example, extraction or addition of information, format change, or the like. Further, the transaction data processing unit 100A stores the account information registered by the user terminal 11A for accessing the deposit / withdrawal processing system 21A of the financial institution 20A in the transaction data storage unit 100B. The transaction data processing unit 100A accesses the deposit / withdrawal processing system 21A based on the account information. Similarly, the transaction data processing unit 100A may store account information for accessing the deposit / withdrawal processing system 21B of the financial institution 20B in the transaction data storage unit 100B and access the deposit / withdrawal processing system 21B.

  Next, with reference to FIG. 2A, each unit constituting the transaction data processing unit 100A and the transaction data storage unit 100B of the accounting processing system 100 according to the first embodiment will be described. FIG. 2A is a diagram illustrating a configuration of a transaction data processing unit and a transaction data storage unit included in the accounting processing system according to the first embodiment.

  The functions of the transaction data processing unit 100A and the transaction data storage unit 100B can be realized, for example, by using a storage area or by executing a program stored in the storage area. Similarly, each unit constituting transaction data processing unit 100A and transaction data storage unit 100B described below is realized by using a storage area or by executing a program stored in the storage area. Can do.

  The transaction data processing unit 100A includes a billing registration unit 103, a payment schedule registration unit 106, a linking unit 109, a payment application generation unit 112, a payment application transmission unit 115, a payment schedule notification unit 118, an application registration unit 121, and an application process. Part 124 is provided. The transaction data storage unit 100B includes a billing data storage unit 133, a payment schedule data storage unit 136, a tied data storage unit 139, a payment application data storage unit 142, an application data storage unit 148, and an application result storage unit 151.

  The billing registration unit 103 stores billing data registered by the user terminal 11B from the contractor 10B in the billing data storage unit 133. The billing data is information indicating a billing for payment from the contractor 10B to the orderer 10A.

  Here, an example of the billing data will be described with reference to FIG. 2B. FIG. 2B is a diagram illustrating an example of transaction data stored in the billing data storage unit of the first embodiment.

  As shown in FIG. 2B, in the billing data storage unit 133, for example, as billing data, the input source (ordering party) is company B, the customer (ordering party 10A) is company A, and the transaction content is a product. It is stored that α, the amount charged is 100,000, and the payment due date is 2017/05/51.

  The payment schedule registration unit 106 stores the payment schedule data registered by the user terminal 11 </ b> A from the orderer 10 </ b> A in the payment schedule data storage unit 136. The payment schedule data is information indicating a payment schedule from the orderer 10A to the contractor 10B.

  Here, an example of the payment schedule data will be described with reference to FIG. 2C. FIG. 2C is a diagram illustrating an example of transaction data stored in the payment schedule data storage unit of the first embodiment.

As shown in FIG. 2C, in the payment schedule data storage unit 136, for example, as payment schedule data, the input source (orderer 10A) is company A, the customer (ordering party) is company B, and the transaction details Is the product α, the scheduled payment amount is 100,000, and the scheduled payment date is 2017/05/30.

  The associating unit 109 associates information on the orderer 10A side and information on the contractor 10B side in the transaction data. That is, the associating unit 109 associates the billing data stored in the billing data storage unit 133 with the payment schedule data stored in the payment schedule data storage unit 136. Then, the association unit 109 stores the associated association data in the association data storage unit 139. The association data is, for example, information including one data table generated by combining billing data and payment schedule data. Further, the association data may be an information group including billing data and payment schedule data stored as separate data tables, and a cooperation ID assigned to each data table in order to link them. .

  Here, an example of the association data will be described with reference to FIG. 2D. FIG. 2D is a diagram illustrating an example of transaction data stored in the tied data storage unit of the first embodiment.

  As illustrated in FIG. 2D, the associating data storage unit 139 stores associating data obtained by combining the billing data illustrated in FIG. 2B and the payment schedule data illustrated in FIG. 2C as one data table. That is, in the associating data storage unit 139, the orderer 10A is the company A, the contractor is the company B, the transaction content is the product α, the invoice amount is 100,000, and the payment due date is 2017/05. / 51, the scheduled payment amount is 100,000, and the scheduled payment date is 2017/05/30.

  The associating unit 109 automatically associates the billing data and the payment schedule data based on the contents of the billing data and the payment schedule data, for example. Specifically, the associating unit 109 collates information that can specify the transaction such as the transaction establishment date, the customer, the transaction content, and the like included in each of the billing data and the payment schedule data at the time of the association. Good. In addition, a transaction ID for specifying a transaction may be registered in advance when registering billing data and payment schedule data, and the billing data and payment schedule data may be linked based on the transaction ID. Note that the associating unit 109 may be manually associated, for example, in such a manner that the orderer 10A and the contractor 10B sequentially input the billing data and the payment schedule data in one prepared data table.

  The payment application generation unit 112 generates payment application data for applying for payment from the orderer 10A to the contractor 10B based on the payment schedule data. Then, the payment application generation unit 112 stores the payment application data in the payment application data storage unit 142. The payment application data is, for example, data for transfer for calling an API. Since the payment schedule data is linked to the billing data, the payment application data generated based on the payment schedule data may also be linked to the billing data.

  The payment application transmission unit 115 instructs the remittance from the financial institution 20A to the financial institution 20B by transmitting the payment application data stored in the payment application data storage unit 142 to the financial institution 20A.

  The payment schedule notification unit 118 notifies the ordering party 10B of a payment schedule notification to the contractor 10B based on the payment schedule data. The payment schedule notification is data including a deposit amount from the financial institution 20A to the financial institution 20B, a scheduled payment date, and the like. The payment schedule notification unit 118 notifies the payment schedule notification before the actual payment to the financial institution 20B. However, the payment schedule notification unit 118 may notify the payment schedule notification after actual payment to the financial institution 20B. Note that the payment schedule notification unit 118 may notify the contractor 10B of a payment schedule notification based on data generated based on the payment schedule data, for example, based on payment application data. In addition, the payment schedule notification unit 118 can notify the payment schedule notification to the order receiving party 10B by any method as long as the order receiving party 10B can confirm with the user terminal 11B. For example, the payment schedule notification may be information that the contractor 10B accesses and confirms the accounting processing system 100, or information that is notified to the contractor 10B by e-mail or the like.

  The application registration unit 121 stores application data for deleting the billing data in the application data storage unit 148. The application data is data indicating that the trade receivable indicated by the billing data has been collected. The application data may be manually input by the contractor 10B that has received the payment schedule notification, or may be generated by the transaction data processing unit 100A in response to an instruction from the contractor 10B that has received the payment schedule notification. The application data may be generated based on the payment schedule data, or may be generated based on other data (for example, payment application data) generated based on the payment schedule data.

  The application processing unit 124 deletes the billing data based on the application data stored in the application data storage unit 148. The application processing unit 124 stores an application result indicating the association data reflecting the application process in the application result storage unit 151.

  Next, the accounting information processing method in the accounting processing system 100 according to the first embodiment will be described with reference to FIG. 2E. FIG. 2E is a flowchart illustrating an example of processing in the accounting processing system according to the first embodiment.

  First, the associating unit 109 associates the billing data acquired from the contractor 10B with the payment schedule data acquired from the orderer 10A (S103). Next, the payment application generation unit 112 generates payment application data based on the payment schedule data (S106). The payment application data is transmitted to the financial institution 20A by the payment application transmission unit 115. At this time, a payment schedule notification is notified to the contractor 10B based on the payment application data. Next, the application registration unit 121 registers application data generated based on the payment schedule notification by the contractor 10B in the application data storage unit 148. Next, the application processing unit 124 executes an application data consumption process based on the application data (S109). The accounting processing system 100 executes transaction completion processing based on the application result stored in the application result storage unit 151 and the notification indicating completion of the withdrawal process received from the financial institution 20B (S112). ). At this time, the accounting processing system 100 notifies the orderer 10A of a withdrawal notification indicating that the withdrawal process has been completed. In addition, the accounting processing system 100 notifies the contractor 10B of a deposit notification indicating that the deposit process has been completed and an application result.

Second Embodiment
Next, the configuration of the accounting processing system 200 according to the second embodiment and the information processing method in the accounting processing system 200 will be described with reference to FIGS. 3A and 3B. FIG. 3A is a diagram illustrating a configuration of a transaction data processing unit and a transaction data storage unit included in the accounting processing system according to the second embodiment. FIG. 3B is a flowchart illustrating an example of processing in the accounting processing system according to the second embodiment.

  As shown in FIG. 3A, the accounting processing system 200 according to the second embodiment is different from the accounting processing system 100 according to the first embodiment in that the transaction data processing unit 200A includes a transmission history storage unit 245. The transmission history storage unit 245 stores the transmission history of payment application data transmitted by the payment application transmission unit 215.

  As shown in FIG. 3B, as a difference from the information processing method in the accounting system 100, in the accounting system 200, after the payment application transmission unit 215 transmits the payment application data to the financial institution, the transmission history The storage unit 245 stores the transmission history of payment application data (S207). Then, the payment schedule notification unit 218 notifies the contractor 10B of the payment schedule notification based on the transmission history.

<Third Embodiment>
Next, the configuration of the accounting processing system 300 according to the third embodiment and the information processing method in the accounting processing system 300 will be described with reference to FIGS. 4A and 4B. FIG. 4A is a diagram illustrating a configuration of a transaction data processing unit and a transaction data storage unit included in the accounting processing system according to the third embodiment. FIG. 4B is a flowchart illustrating an example of processing in the accounting processing system according to the third embodiment.

  As shown in FIG. 4A, the accounting processing system 300 according to the third embodiment is different from the accounting processing system 100 according to the first embodiment in that a transaction data processing unit 300A includes a consumption generation unit 319. The application generation unit 319 generates application data based on the payment application data, and registers the application data in the application registration unit 321. Note that the application generation unit 319 may generate application data based on the payment schedule data.

As shown in FIG. 4B, as a difference from the information processing method in the accounting processing system 100, the accounting processing system 300 stores in the payment application data storage unit 342 using the application instruction received from the contractor 10B as a trigger. Based on the received payment application data, the application generation unit 319 generates application data (S308). The application instruction is information for instructing the execution of the application process input by the contractor 10B to the accounting system 300 based on the payment schedule notification notified to the contractor 10B by the payment schedule notification unit 318. The application processing unit 324 executes application processing based on the application data generated by the application generation unit 319 (S309).
<Fourth embodiment>
Next, the configuration of the accounting processing system 400 according to the fourth embodiment and the information processing method in the accounting processing system 400 will be described with reference to FIGS. 5A and 5B. FIG. 5A is a diagram illustrating a configuration of a transaction data processing unit and a transaction data storage unit included in the accounting processing system according to the fourth embodiment. FIG. 5B is a flowchart illustrating an example of processing in the accounting processing system according to the fourth embodiment.

  As shown in FIG. 5A, the accounting system 400 according to the fourth embodiment includes a transaction data processing unit 400A provided with an estimate registration unit 401 and a bill generation unit 402, and a transaction data storage unit 400B with an estimated data storage unit 431. Is different from the accounting processing system 100 according to the first embodiment. The estimate registration unit 401 stores, in the estimate data storage unit 431, estimate data related to the estimate of the transaction issued by the contractor 10B to the orderer 10A. The bill generation unit 402 generates bill data based on the estimate data stored in the estimate data storage unit 431. Transaction data (payment schedule data, payment request data, etc.) stored in the transaction data storage unit 400B other than the billing data may also be generated based on the estimated data. According to this, all the transaction data generated based on the same estimate data can be automatically linked. The billing data does not necessarily have to be generated based on the estimated data, but may be registered in the billing registration unit 403 by the contractor 10B and associated with the estimated data by the associating unit 409. That is, the bill generation unit 402 may be omitted.

As shown in FIG. 5B, as a difference from the information processing method in the accounting system 100, in the accounting system 400, the estimate registration unit 401 obtains estimate data from the contractor 10B, and the bill generation unit 402 estimates. Billing data is generated based on the estimated data stored in the data storage unit 431 (S401). Further, the associating unit 409 associates the billing data generated by the billing generating unit 402 with the payment schedule data acquired from the orderer 10A (S403).
<Fifth Embodiment>
Next, a configuration of the accounting processing system 500 according to the fifth embodiment and an information processing method in the accounting processing system 500 will be described with reference to FIGS. 6A and 6B. FIG. 6A is a diagram illustrating a configuration of a transaction data processing unit and a transaction data storage unit included in the accounting processing system according to the fifth embodiment. FIG. 6B is a flowchart illustrating an example of processing in the accounting processing system according to the fifth embodiment.

  As shown in FIG. 6A, the accounting processing system 500 according to the fifth embodiment relates to the first embodiment in that the transaction data processing unit 500 </ b> A does not include a payment schedule notification unit but includes a consumption generation unit 519. This is different from the accounting processing system 100. The application generation unit 519 generates application data based on the payment schedule data or payment application data. The application data generated by the application generation unit 519 is stored in the application data storage unit 548 by the application registration unit 521.

  As shown in FIG. 6B, as a difference from the information processing method in the accounting processing system 100, in the accounting processing system 500, the consumption generating unit 519 generates consumption data based on the payment application data (S608). . The accounting processing system 500 does not notify the contractor 10B of a payment schedule notification, and does not acquire application data or an application instruction from the contractor 10B.

Similarly to the accounting processing system 200 according to the second embodiment, the accounting processing system 500 may include a transmission history storage unit that stores a transmission history of payment application data in the transaction data storage unit 500B. In the case of such a configuration, the consumption generation unit 519 may generate consumption data based on the transmission history.
<Sixth Embodiment>
Next, the configuration of the accounting processing system 600 according to the sixth embodiment and the information processing method in the accounting processing system 600 will be described with reference to FIGS. 7A and 7B. FIG. 7A is a diagram illustrating a configuration of a transaction data processing unit and a transaction data storage unit included in the accounting processing system according to the sixth embodiment. FIG. 7B is a flowchart illustrating an example of processing in the accounting processing system according to the sixth embodiment.

  As shown in FIG. 7A, the accounting processing system 600 according to the sixth embodiment is different from the accounting processing system 500 according to the fifth embodiment in that the transaction data processing unit 600A includes an application result notification unit 625. The application result notifying unit 625 notifies the contractor 10B of an application result indicating that the billing data has been applied based on the application result stored in the application result storage unit 651. The application result notification unit 625 may notify the contractor 10B of the application result based on the application data stored in the application data storage unit 648. In the configuration in which the application result notification unit 625 notifies the application result based on the application data, the application result notification unit 625 can notify the contractor 10B of the application result before executing the application process. .

As shown in FIG. 7B, as a difference from the information processing method in the accounting processing system 500, in the accounting processing system 600, an application processing is executed in the application processing unit 624, and before the payment notification is notified (S612). Then, the application result is notified to the contractor 10B by the application result notification unit 625 (S609).
<Seventh embodiment>
Next, the configuration of the accounting processing system 700 according to the seventh embodiment and the information processing method in the accounting processing system 700 will be described with reference to FIGS. 8A and 8B. FIG. 8A is a diagram illustrating a configuration of a transaction data processing unit and a transaction data storage unit included in the accounting processing system according to the seventh embodiment. FIG. 8B is a flowchart illustrating an example of processing in the accounting processing system according to the seventh embodiment.

  As shown in FIG. 8A, an accounting system 700 according to the seventh embodiment includes a transaction data processing unit 700A provided with a verification unit 710 and a verification result notification unit 711, and a transaction data storage unit 700B with a verification result storage unit 740. Is different from the accounting processing system 500 according to the fifth embodiment.

  The collation unit 710 collates the billing data and the payment schedule data, and stores the collation result indicating the match / mismatch of the transaction data (billing data and payment schedule data) in the collation result storage unit 740. The verification result notifying unit 711 notifies the verification result stored in the verification result storage unit 740 to at least one of the orderer 10A and the contractor 10B. When the collation result generated in the collation unit 710 indicates a mismatch, the accounting processing system 700 can issue a warning to at least one of the orderer 10A and the contractor 10B. In the same case, the accounting processing system 700 can stop the generation of payment application data in the payment application generation unit 712. Alternatively, generation of consumption data in the consumption generation unit 719 can be stopped. In addition, the collation part 710 may collate bill data with payment application data, and may collate bill data and application data.

  As shown in FIG. 8B, as a difference from the information processing method in the accounting processing system 500, in the accounting processing system 700, the collation unit 710 performs billing data based on the association data stored in the association data storage unit 739. Then, the payment schedule data is collated (S705). At this time, the verification result notifying unit 711 notifies the verification result to the orderer 10A and the contractor 10B.

  An example of information processing in the collation unit 710 and the collation result notification unit 711 will be described with reference to an example of the association data illustrated in FIG. 2D. The collation unit 710 collates, for example, the billed amount and the scheduled payment amount. Then, when the invoiced amount and the scheduled payment amount do not match, the matching unit 710 stores a matching result indicating a mismatch of transaction data in the matching result storage unit 740. Based on the collation result, the collation result notifying unit 711 can notify at least one of the orderer 10A and the contractor 10B of the amount mismatch. Moreover, the collation part 710 collates a payment scheduled date and a payment time limit, for example. If the scheduled payment date exceeds the due date, the verification result notification unit 711 can issue a warning regarding the due date to the orderer 10A.

  As described above, according to one aspect of the present invention, the transaction processing system 100 manages transaction data related to transactions between the orderer 10A and the contractor 10B, and receives orders from the orderer 10A registered by the orderer 10A. A payment schedule registration unit 106 that stores payment schedule data indicating a payment schedule to the buyer 10B in the transaction data storage unit 100B, and payment for applying for payment from the orderer 10A to the contractor 10B based on the payment schedule data Based on the payment schedule data, the payment application generation unit 112 that generates application data, the payment application transmission unit 115 that transmits the payment application data to the financial institution 20A, and the payment plan data are notified to the contractor 10B. An accounting processing system including a payment schedule notification unit 118 is provided.

  According to the above aspect, the contractor downloads data necessary for transmitting payment application data from a financial institution and accesses the accounting system without uploading the payment application data to the financial institution. Application data can be sent to financial institutions. According to this, the accounting processing system can manage transaction data in a unified manner. Further, since the accounting processing system includes a payment schedule notification unit, the payment schedule notification can be notified to the contractor before the payment notification is notified from the financial institution.

  The deposit schedule notification unit 118 may notify the contractor 10B of a deposit schedule notification to the contractor 10B based on the payment application data. According to this, the accounting processing system can notify the contractor of the payment schedule notification before transmitting the payment application data to the financial institution.

  A transmission history storage unit 245 that stores a transmission history of payment application data may be further provided, and the payment schedule notification unit 218 may notify the orderer of a payment schedule notification to the contractor based on the transmission history. According to this, the accounting processing system can notify the contractor of the payment schedule notice before the payment notice is notified to the contractor.

  A billing registration unit 103 that stores billing data indicating a request for payment from the contractor 10B to the orderer 10A in the transaction data storage unit 100B, and application data for erasing the billing data are stored in the transaction data storage unit 100B. You may further provide the consumption registration part 121 and the consumption processing part 124 which erases billing data based on consumption data. According to this, according to the action of the contractor based on the payment schedule notification, the accounting processing system can execute the application process without waiting for receipt of the payment notification.

  The application data may be registered by the contractor 10B based on the payment schedule notification. According to this, the contractor can create the application data after confirming the payment schedule notification. The accounting processing system can execute the application process based on the application data registered by the contractor.

  In response to an instruction from the contractor 10 </ b> B, an application generation unit 319 may be provided that generates application data based on the payment schedule notification. According to this, the contractor can confirm the payment schedule notification. Further, the contractor only needs to input a consumption instruction without creating consumption data. Further, since the consumption data is generated from the registered data by the consumption generation unit, the accounting processing system can automatically associate the consumption data with other transaction data. From the above, the accounting processing system can reduce the complexity of input and improve convenience.

  According to another aspect of the present invention, there is an accounting processing system 500 that manages transaction data related to transactions between an orderer 10A and an orderer 10B, and shows a request for payment from the orderer 10B to the orderer 10A. A billing registration unit 503 that stores data in the transaction data storage unit 500B, and a payment that is stored by the transaction data storage unit 500B, which is registered by the orderer 10A and indicates payment schedule data indicating a payment plan from the orderer 10A to the contractor 10B. The schedule registration unit 506, the payment application generation unit 512 that generates payment application data for applying for payment from the orderer 10A to the contractor 10B based on the payment schedule data, and the payment application data are transmitted to the financial institution 20A. Payment application transmission unit 515 and application generation unit 5 that generates application data for applying the billing data based on the payment schedule data 9, an application registration unit 521 that stores application data in the transaction data storage unit 500 </ b> B, and an application processing unit 524 that deletes billing data based on the application data. .

  According to the above aspect, the contractor downloads data necessary for transmitting payment application data from a financial institution and accesses the accounting system without uploading the payment application data to the financial institution. Application data can be sent to financial institutions. According to this, the accounting processing system can manage transaction data in a unified manner. Further, since the application data can be generated based on the payment schedule data, the accounting processing system can execute the application process without waiting for receipt of the payment notice from the financial institution. In addition, after receiving the payment schedule data, the accounting processing system can automatically execute the application process without receiving instructions from the contractor and the orderer. That is, the accounting processing system can reduce the complexity of input and speed up the consumption process.

  The application generation unit 519 may generate application data based on the payment application data. According to this, the accounting processing system can execute the application process before sending the payment application data to the financial institution.

  A transmission history storage unit 245 that stores the transmission history of payment application data may be further provided, and the consumption generation unit 519 may generate consumption data based on the transmission history. According to this, the accounting processing system can execute the application process before the payment notice is notified to the contractor.

  You may further provide the consumption result notification part 625 which notifies a contractor of the consumption result which shows that the claim data was deleted. According to this, the accounting processing system can notify the application result before the payment notice is notified to the contractor. That is, the contractor can quickly acquire accounting data such as the application status.

  You may further provide the collation part 710 which collates bill data with payment plan data. According to this, the accounting processing system can notify the orderer and the contractor of the difference between the billing data and the payment schedule data, and can accept the correction of the billing data and the payment schedule data. Further, the accounting processing system can stop generating the payment request data or the generation of the application data based on the collation result between the charge data and the payment schedule data.

  The system further includes an estimate registration unit 401 that stores estimate data related to a transaction estimate issued by the contractor 10B to the orderer 10A in an estimate data storage unit, and a bill generation unit 402 that generates billing data based on the estimate data. May be. According to this, the accounting system can automatically generate other transaction data such as billing data based on the estimated data. Further, by generating other transaction data based on the estimate data, it becomes easy to link the transaction data.

  A linking unit for linking the billing data and the payment schedule data based on the contents of the transaction data may be further provided. According to this, the accounting processing system can automatically associate transaction data. That is, the accounting processing system can reduce the complexity of input and improve convenience.

  As described above, according to one aspect of the present invention, it is possible to provide an accounting processing system that can perform quick application processing.

  The embodiments described above are for facilitating the understanding of the present invention, and are not intended to limit the present invention. The present invention can be changed / improved without departing from the spirit thereof, and the present invention includes equivalents thereof. In other words, those obtained by appropriately modifying the design of each embodiment by those skilled in the art are also included in the scope of the present invention as long as they include the features of the present invention. For example, each element included in each embodiment and its arrangement, material, condition, shape, size, and the like are not limited to those illustrated, and can be changed as appropriate. In addition, each element included in each embodiment can be combined as much as technically possible, and combinations thereof are included in the scope of the present invention as long as they include the features of the present invention.

DESCRIPTION OF SYMBOLS 10A ... Ordering party 10B ... Contractor 20A, 20B ... Financial institution 100 ... Accounting processing system 100A ... Transaction data processing part 100B ... Transaction data storage part 103 ... Billing registration part 106 ... Payment schedule registration part 109 ... Linking part 112 ... Payment application Generation unit 115 ... payment application transmission unit 118 ... payment schedule notification unit 121 ... application registration unit 125 ... application processing unit 133 ... billing data storage unit 136 ... payment plan data storage unit 139 ... associated data storage unit 142 ... payment application data Storage unit 148 ... Consumption data storage unit 151 ... Consumption result storage unit

Claims (13)

An accounting system for managing transaction data related to transactions between a purchaser and a contractor,
A payment schedule registration unit that stores payment schedule data indicating a schedule of payment from the orderer to the contractor, which is registered by the orderer, in a transaction data storage unit;
A payment application generation unit that generates payment application data for applying for payment from the orderer to the contractor based on the payment schedule data;
A payment application transmission unit for transmitting the payment application data to a financial institution;
Based on the payment schedule data, a payment schedule notification unit for notifying the orderer of a payment schedule notification to the contractor;
Accounting system. The payment schedule notification unit notifies the contractor of a payment schedule notification to the contractor based on the payment application data.
The accounting system according to claim 1. A transmission history storage unit for storing a transmission history of the payment application data;
The deposit schedule notification unit notifies the contractor of a deposit schedule notification to the contractor based on the transmission history.
The accounting system according to claim 1. A billing registration unit for storing billing data indicating billing for payment from the contractor to the orderer in the transaction data storage unit;
An application registering unit for storing application data for applying the billing data in the transaction data storage unit;
A consumption processing unit that erases the billing data based on the consumption data,
The accounting processing system according to any one of claims 1 to 3. The application data is registered by the contractor based on the payment schedule notification.
The accounting processing system according to claim 4. In response to the instruction of the contractor, the apparatus further comprises an application generation unit that generates the application data based on the payment schedule notification.
The accounting processing system according to claim 4. An accounting system for managing transaction data related to transactions between a purchaser and a contractor,
A billing registration unit for storing billing data indicating billing for payment from the contractor to the orderer in a transaction data storage unit;
A payment schedule registration unit that stores payment schedule data indicating a payment schedule from the orderer to the contractor, which is registered by the orderer, in a transaction data storage unit;
A payment application generating unit that generates payment application data for applying for payment from the orderer to the contractor based on the payment schedule data;
A payment application transmission unit for transmitting the payment application data to a financial institution;
An application generation unit that generates application data for applying the billing data based on the payment schedule data;
An application registration unit for storing the application data in the transaction data storage unit;
An application processing unit for erasing the billing data based on the application data;
Accounting system. The application generation unit generates the application data based on the payment application data.
The accounting system according to claim 7. A transmission history storage unit for storing a transmission history of the payment application data;
The consumption generation unit generates the consumption data based on the transmission history.
The accounting system according to claim 7. A consumption result notifying unit for notifying the contractor of a consumption result indicating that the billing data has been consumed;
The accounting processing system according to any one of claims 7 to 9. A collation unit that collates the billing data with the payment schedule data;
The accounting processing system according to any one of claims 7 to 10. An estimate registration unit that stores, in an estimate data storage unit, estimate data relating to an estimate of the transaction issued by the contractor to the orderer;
A bill generation unit that generates the bill data based on the estimate data;
The accounting processing system according to any one of claims 4 to 11. A linking unit for linking the billing data and the payment schedule data based on the content of the transaction data;
The accounting processing system according to any one of claims 4 to 12.