JP2015207142A - Payment processor, payment processing method, and payment processing program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To shorten time required for payment processing, and to improve the accuracy of processing.SOLUTION: A payment processor 1 includes: a payment information acquisition part 11 for acquiring payment information including payment source information and a paid money amount; an unpaid money information storage part 14 for storing unpaid money information including billing destination information and unpaid money amount; an index information storage part 15 for storing index information in which billing destination information is associated with the payment source information; a billing destination information acquisition part 16 for acquiring billing destination information associated with the payment source information of the payment information by referring to index information; a collation part 17 for extracting the unpaid money information including the billing destination information acquired by the billing destination information acquisition part 16 from the unpaid money information stored in the unpaid money information storage part 14, and for executing the collation of whether or not the unpaid money amount of the unpaid money information and the paid money amount of the payment information correspond to each other; and an association part 18 for associating the paid money amount and the unpaid money amount determined to correspond to each other from the collation result.

Description

  The present invention relates to a deposit processing apparatus, a deposit processing method, and a deposit processing program for executing deposit processing.

  2. Description of the Related Art Conventionally, a provider of goods, services, etc., usually executes the following application process when accounts receivable are generated by providing goods, services, etc. to a business partner (purchaser). That is, the provider of goods, services, etc. collates the amount of money received from the business partner and the accounts receivable, and if a matching result is obtained that the amount of money is matched with the accounts receivable, executes the receivable application process. . For example, Japanese Patent Application Laid-Open No. 2004-151561 describes that the sum of account receivable data is collated with receipt data, and when the two match, an account receivable application process is executed.

JP 11-328292 A

  By the way, in such an account receivable application process, it is necessary to specify which account receivable is related to the receipt shown in the receipt information (for example, bank transfer information) from the business partner. However, when making a payment by bank transfer or the like, the business partner does not always write information (for example, an invoice number) indicating to which accounts receivable the payment is in the remarks column. Furthermore, the name of the transfer holder may be different from the name of the business partner who is the billing destination for the accounts receivable. Therefore, it is not easy for an operator or the like to specify which account receivable is included in the receipt information, and there is a problem that it takes time for the receipt process such as the receivable application process.

  Therefore, an object of the present invention is to provide a deposit processing apparatus, a deposit processing method, and a deposit processing program that can shorten the deposit processing time and improve the processing accuracy.

  A deposit processing apparatus according to the present invention includes deposit information acquiring means for acquiring deposit source information for identifying a deposit source and deposit information including the deposit amount of the deposit source, billing destination information for identifying a billing destination, and the billing destination. Non-payment information storage means for storing one or more non-payment information including a non-payment amount, and index information storage means for storing index information in which one or more billing destination information is associated with one payment source information And billing information acquisition for acquiring one or more billing destination information associated with the depositing source information of the depositing information acquired by the depositing information acquiring unit by referring to the index information stored in the index information storage unit And the non-payment information stored in the non-payment information storage means to extract the non-payment information including the billing destination information acquired by the billing destination information acquisition means, and the unpaid amount of the extracted non-payment information Payment information acquisition Executes a process for associating the deposit amount and the unpaid amount with which the collation unit obtains a collation result that the collation unit corresponds to each other, and a collation unit that performs collation to check whether or not the deposit amount of the deposit information acquired by And an associating means.

  In the deposit processing apparatus according to the present invention, when the deposit information is acquired, one or more billing destination information associated with the deposit source information of the deposit information is acquired by referring to the index information. Subsequently, the non-payment information including the billing information is extracted, and the non-payment amount of the non-payment information is compared with the deposit amount of the payment information. Then, a process of associating the non-payment amount and the payment amount obtained with the matching result indicating that they correspond to each other is executed. According to the above deposit processing apparatus, it is possible to link the deposit source information and the billing destination information based on the index information, and therefore it is possible to shorten the work time for linking the deposit source information and the billing destination information. . Also, in commercial transactions, for example, the parent company often makes payments for paying accounts receivable from a plurality of subsidiaries at once. According to the deposit processing apparatus, the deposit process can be appropriately executed even in such a case. That is, non-payment information of a plurality of subsidiaries is extracted based on index information in which the parent company's payment source information and billing information of a plurality of subsidiaries are associated, and the non-payment amount of the non-payment information and the payment amount from the parent company Can be matched and associated with each other. As described above, according to the deposit processing apparatus, the deposit information and one or more unpaid information can be automatically and appropriately associated with each other based on the index information. Accuracy can be improved.

  In the payment processing apparatus, the non-payment information stored in the non-payment information storage means includes a non-payment amount for each predetermined category, and the matching means is based on the non-payment amount for each category. The above collation may be executed.

  According to the deposit processing apparatus, the collation is executed based on the non-payment amount for each predetermined classification, so that the deposit amount and the non-payment amount can be associated with each other appropriately. For example, when deposits are made for unpaid amounts in all categories (collective deposits), or when only deposits for some categories are not deposited (partial deposits), Can be properly associated. Thereby, it is possible to appropriately execute the deposit process for both collective deposit and partial deposit.

  In the deposit processing apparatus, the non-payment information stored in the non-payment information storage means includes billing time information indicating the billing time for the billing destination, and the collating means is stored in the non-payment information storage means. It is determined whether or not the non-payment information is to be collated based on the billing time information of the non-payment information, and includes the billing destination information acquired by the billing destination information acquisition means and is also set as the collation target The non-payment information may be extracted, and the above verification may be performed on the non-payment amount of the extracted non-payment information and the deposit amount of the payment information.

  According to the deposit processing apparatus, it is possible to appropriately associate the deposit amount and the non-payment amount based on the billing time. For example, when receivables are billed periodically (for example, every month), it can be determined that only non-payment information related to billing for the latest month is targeted for verification. As a result, when the payment source has made a payment for the bill for the latest month in the state of neglecting the payment for the past (previous month) due to misunderstandings, etc., the deposit amount is the unpaid amount of the latest month. Can be associated appropriately. As a result, it is possible to suppress the occurrence of flaws related to payment with the payment source.

  In the deposit processing apparatus, the verification unit stores a fee related to deposit in advance, and determines whether or not the difference between the unpaid amount and the deposit amount matches the fee in the verification, and the difference matches the fee May output a matching result indicating that the unpaid amount and the deposited amount correspond to each other.

  For example, if the deposit source misunderstands the fees that are incurred at the time of deposit (for example, bank transfer fees), the amount to be paid (the amount not yet paid) is the amount that is greater (or less) than the amount to be paid There is a risk of being. In such a case, there is a difference between the unpaid amount and the deposited amount by the fee. Here, if the non-payment amount and the payment amount match each other based on whether or not the amounts match, they will correspond to each other even though they correspond to each other. The result of the verification that it is not a thing is output, and the deposit process is not properly executed. According to the deposit processing apparatus, when the difference between the unpaid amount and the deposited amount matches the fee, a matching result that the unpaid amount and the deposited amount correspond to each other is output. This makes it possible to appropriately associate the deposit amount with the non-payment amount in consideration of the fee generated at the time of deposit.

  By the way, the present invention can be described as an invention of a deposit processing apparatus as described above, and can also be described as an invention of a deposit processing method and a deposit processing program as follows. Since these inventions are substantially the same inventions only in different categories, they exhibit the same operations and effects.

  That is, the deposit processing method according to the present invention includes a non-payment information storage means for storing one or more non-payment information including billing destination information for identifying a billing destination and an unpaid amount of the billing destination, and one depositing source. Index information storage means for storing index information in which one or more billing destination information is associated with information, and a deposit processing method executed by a deposit processing apparatus comprising: deposit source information for identifying a deposit source; Payment information acquisition step for acquiring payment information including the payment amount of the payment source, and the payment source of the payment information acquired in the payment information acquisition step by referring to the index information stored in the index information storage means Obtained in the billing information acquisition step from the billing information acquisition step for acquiring one or more billing information associated with the information and the non-payment information stored in the non-payment information storage means Verification that extracts non-payment information including billing address information and performs verification to determine whether the non-payment amount of the extracted non-payment information and the deposit amount of the payment information acquired in the payment information acquisition step correspond to each other And an associating step for executing a process of associating the deposit amount and the non-payment amount obtained as a result of matching that correspond to each other in the matching step.

  Further, the deposit processing program according to the present invention includes a computer, a deposit information acquiring unit for acquiring deposit information including a deposit source information for identifying a deposit source and a deposit amount of the deposit source, and a billing destination for identifying a billing destination. Non-payment information storage means for storing one or more non-payment information including information and the non-payment amount of the billing destination, and index information in which one or more billing destination information is associated with one payment source information One or more billing destination information associated with the payment source information of the payment information acquired by the payment information acquisition means is obtained by referring to the index information storage means to be performed and the index information stored in the index information storage means The non-payment information including the billing destination information acquired by the billing destination information acquisition unit is extracted from the non-payment information stored in the non-payment information storage unit and the non-payment information storage unit. A matching unit that performs a collation to check whether or not the unpaid amount and the deposit amount of the deposit information acquired by the deposit information acquisition unit correspond to each other, and a deposit amount for which the collation unit corresponds to each other And an association means for executing a process for associating a non-payment amount.

  According to the present invention, it is possible to provide a deposit processing apparatus, a deposit processing method, and a deposit processing program capable of reducing the deposit processing time and improving the processing accuracy.

It is a block diagram which shows the function structure of the money_receiving | payment processing apparatus which concerns on one Embodiment of this invention. It is a figure which shows an example of payment information. It is a figure which shows an example of accounts receivable information. It is a figure which shows an example of non-payment information. It is a figure which shows an example of index information. It is a figure which shows an example of payment journal information. It is a figure which shows an example of (a) payment information after an update, (b) index information, and (c) non-payment information. It is a figure which shows an example of the accounts receivable information after an update. It is a flowchart which shows operation | movement of a money_receiving | payment processing apparatus. It is a block diagram which shows the function structure of the money_receiving | payment process program which concerns on one Embodiment of this invention.

  An embodiment of a deposit processing apparatus, a deposit processing method, and a deposit processing program according to the present invention will be described with reference to the drawings. If possible, the same parts are denoted by the same reference numerals, and redundant description is omitted.

  FIG. 1 is a block diagram showing a functional configuration of a deposit processing apparatus according to an embodiment of the present invention. The deposit processing apparatus 1 according to the present embodiment is managed by a provider that provides products, services, and the like (hereinafter referred to as “products etc.”), for example. Examples of the provision of products and the like include rental services for distribution containers (pallets, etc.), distribution container sales (new product sales and used product sales), and the like. The payment processing apparatus 1 acquires information (payment information) related to payment to a provider from a supplier (payment source) that purchased the product from the provider, and receives the deposit amount related to the deposit information as a receivable of a specific product, etc. It is an apparatus for executing processing that is appropriately associated with a balance (unpaid amount). More specifically, the deposit processing device 1 is a device for executing processing for specifying which account receivable is the payment when the deposit is received from a business partner. In the following description, the process of appropriately associating the deposit amount related to the deposit information with the unpaid amount of a specific product or the like is referred to as “payment process”.

  In this embodiment, as an example, the deposit processing apparatus 1 acquires deposit information related to deposit transferred to a deposit account of a provider by bank transfer. The deposit processing apparatus 1 acquires deposit information from an FB (farm banking) system 2 via a communication network such as a telephone line. The FB system 2 is a system that provides services (bank transfer, various information inquiries, etc.) of financial institutions such as banks. As one of the above services, payment information by bank transfer is externally converted into electronic data such as text files. provide. The deposit processing apparatus 1 acquires deposit information from the FB system 2 by using the service provided by the FB system 2. As shown in FIG. 1, the deposit processing apparatus 1 executes a deposit process for the deposit amount of the deposit information acquired from the FB system 2, a deposit information acquisition unit 11, an accounts receivable management information storage unit 12, an unpaid account. An information generation unit 13, a non-payment information storage unit 14, an index information storage unit 15, a billing destination information acquisition unit 16, a collation unit 17, and an association unit 18 are provided.

  The deposit processing apparatus 1 is physically composed of one or a plurality of CPUs, a RAM and a ROM as main storage devices, an input device such as a keyboard and a mouse as input devices, an output device such as a display, and a network card. The computer system includes a communication module that is a data transmission / reception device such as a hard disk drive and an auxiliary storage device such as a semiconductor memory. The deposit processing device 1 may be physically configured as a single device, or may be configured as a plurality of devices that operate in cooperation with each other. Each function of the deposit processing device 1 is, for example, by reading predetermined computer software (a deposit processing program P1 described later) on hardware such as a CPU and a RAM, thereby controlling the input device and the output device under the control of the CPU. The communication module is operated, and data is read and written in the RAM and the auxiliary storage device. Hereinafter, each function of the deposit processing apparatus 1 will be described. Note that a series of processes executed by the deposit information acquisition unit 11, the non-payment information generation unit 13, the billing information acquisition unit 16, the collation unit 17, and the association unit 18 of the deposit processing apparatus 1 described below are performed in advance every day. At the time set by the operator or the like, it is executed for each deposit information acquired by the deposit information acquisition unit 11 as a daily process. In the following description, the processing executed on the specific deposit information A acquired by the deposit information acquiring unit 11 will be described.

  The deposit information acquisition unit 11 is deposit information acquisition means for acquiring deposit information including deposit source information for identifying a deposit source and the deposit amount of the deposit source. As described above, the deposit information acquisition unit 11 receives (acquires) the deposit information from the FB system 2 via the communication network. FIG. 2 is a diagram illustrating an example of payment information. As shown in FIG. 2, the deposit information includes, for example, deposit source account information (information including, for example, a bank name, a branch name, and a name associated with each other) as deposit source information for identifying the deposit source. The deposit information A shown in FIG. 2 is provided from specific account information X whose bank name, branch name, and name are “A bank”, “B branch”, and “C company”, respectively, and the account information X. And “69,300 yen”, which is the deposit amount transferred to the deposit account.

  The accounts receivable management information storage unit 12 shows accounts receivable information related to accounts receivable in each sales form (classification) in a billing unit (for example, a unit in which an invoice is issued), and a deposit amount of each sales form in each billing unit. This is means for storing deposit journal information (see FIG. 6A). Accounts receivable information is stored in advance in the accounts receivable management information storage unit 12 by being input (registered) via a dedicated terminal or the like by an operator or the like who manages sales of products or the like. In addition, the account receivable management information storage unit 12 stores payment journal information generated by processing performed by the association unit 18 described later or input by an operator or the like before processing for the payment information A. Details of the deposit journal information will be described later. As shown in FIG. 6A, the deposit journal information includes at least an invoice number and a sales form (in this embodiment, as an example, rental, fare, organized sales). The information includes the account item code corresponding to and the deposit amount in association with each other. There are two types of deposit journal information: journal data related to deposit amounts corresponding to accounting debits (records with a debit category of “1”, which will be described later), and journal data related to unpaid amounts corresponding to accounting credits (lending) A record whose classification is “2”).

  FIG. 3 is a diagram showing an example of the accounts receivable information stored in the accounts receivable management information storage unit 12. As shown in FIG. 3, the accounts receivable information includes the supplier code, the billing date, the invoice number, the accounts receivable for each sales format, and the payment related information for each sales format (rental receipt information, freight receipt information, (Consolidated sales / payment information) and a total balance which is a total of the balances of the sales forms. Accounts receivable in each sales form include fees (rental fees, fares, off-charge fees) and consumption tax. The payment related information of each sales form includes the payment amount, the payment date, and the balance (the amount obtained by subtracting the payment amount from the sum of the charge and the consumption tax of each sales type). In the present embodiment, the A / R management information storage unit 12 stores A / R information B1 whose supplier code is “32136” and A / R information B2 whose supplier code is “32137”. The supplier code (invoice destination information) is a number for identifying the supplier (invoice destination). Information indicating the correspondence between the supplier code and the supplier is stored in, for example, information (a supplier master) related to the supplier stored in a database or the like (not shown).

  The billing date indicates the date when the bill was issued. In the present embodiment, as an example, the billing date is composed of a 4-digit number. The first two digits of the billing year represent the last two digits of the year of the billing year, and the last two digits of the billing year represent the billing month as a two-digit number. For example, the billing date “1301” in the accounts receivable information shown in FIG. 3 indicates that the billing date is “January 2013”.

  The invoice number is a number for identifying the invoice. In the present embodiment, as an example, the first digit of the bill number indicates the last digit of the year of the billing year. In addition, the 6-digit number excluding the first digit of the invoice number is given based on the rules determined in advance according to the above-mentioned rental service, new product sales (general sales), used product sales, etc. The number to be shown. For example, invoices whose provision form is “rental service” are assigned numbers of 200,000 or less as invoice numbers (for example, sequentially assigned from “100001” in the order in which invoices are issued). Invoices other than “rental service” are provided with numbers of 200,000 or more as invoice numbers (for example, sequentially assigned from “20001” in the order in which the invoices are issued).

  In this embodiment, as an example, “rental service” is assumed as a provision form, and “rental”, “freight”, and “sorted sale” are included as sales forms. “Rental” is a sales form in which a rental fee is charged according to the rental period of a product. The “fare” is a sales form in which a fare is charged for shipping a product from a factory or the like to the purchaser. “Organized sales” charge a sales fee as a consignment collection fee instead of the normal rental fee when the rental product cannot be returned for some reason (for example, lost or damaged). Sales form. In the organized sales, payment may be made in installments based on a contract, for example.

  When there are a plurality of provision forms, the receivable management information storage unit 12 may store the receivable information for each provision form having different data items related to the sales form, for example, by an input process by an operator or the like. . For example, the accounts receivable information (general accounts receivable information) such as second-hand sales and general sales does not include “rental” and “consolidated sales” as data items relating to the sales form, but indicates “second-hand or new sales”. "Product sales" may be included.

  The payment related information of each sales form is updated by monthly processing based on the payment journal information generated daily by the association unit 18 described later. In the “payment date” of the payment related information, for example, empty data, a default value (eg, “0”), and the like are stored until the above-described monthly processing is updated. In the present embodiment, as an example, “0”, which is a default value, is stored in “payment date” of the deposit related information.

  The non-payment information generation unit 13 is means for generating non-payment information based on the receivable information and the payment journal information stored in the accounts receivable management information storage unit 12. The non-payment information generation unit 13 stores the generated non-payment information in the non-payment information storage unit 14. The non-payment information storage unit 14 is non-payment information storage means for storing non-payment information. FIG. 4 is a diagram illustrating an example of non-payment information. As shown in FIG. 4, the non-payment information includes a supplier code, a billing date (billing time information), a data type indicating a provision form, and a non-payment amount for each sales form (rental, fare, organized sales). (Balance), the total of the unpaid amount (total balance), and the invoice number are associated with each other. Here, for example, “0” is assigned to the data type when the provision form is “rental service”, and “1” is assigned when the provision form is “second-hand sales”. In the case of “general sales”, “2” is given.

  For example, the non-payment information generation unit 13 generates the non-payment information by executing the following process for each piece of receivable information stored in the accounts receivable management information storage unit 12, and generates the non-payment information as non-payment. The information is stored in the information storage unit 14. If the non-payment information corresponding to the accounts receivable information is already stored in the non-payment information storage unit 14, the non-payment information generation unit 13 does not newly generate the non-payment information, The non-payment information stored in the storage unit 14 is updated. Hereinafter, the non-payment information generation process executed by the non-payment information generation unit 13 for each piece of sales information will be described. First, the non-payment information generation unit 13 retrieves the payment journal information including the invoice number of the receivable information to be processed from the payment journal information (credit journal data) stored in the accounts receivable management information storage unit 12. To do. That is, the non-payment information generation unit 13 searches for payment journal information related to payment for the receivable of the receivable information to be processed.

  The non-payment information generation unit 13 generates non-payment information in which each item is non-payment information related to the receivable information to be processed when each of the items is not found by the search. . And the supplier code, billing date, bill number, unpaid amount of each sales form (data items of “rental”, “fare”, “consolidated sales” shown in FIG. 4), and balance To the total, the business partner code, billing date, invoice number, balance of each sales form, and total balance are set. In addition, the non-payment information generation unit 13 stores in advance information indicating the data type of the provision form corresponding to, for example, a combination of sales forms included in the accounts receivable information. Then, by referring to the information, the data type corresponding to the combination of sales forms included in the receivable information to be processed is set as the data type of the newly generated non-payment information. For example, when the combination of sales forms included in the receivable information to be processed is “rental”, “freight”, and “consolidated sales”, the non-payment information generation unit 13 selects the combination of sales forms. The data type “0” indicating the corresponding providing form is set as the data type of the newly generated non-payment information. The non-payment information generation unit 13 stores the non-payment information generated and set as described above in the non-payment information storage unit 14. Such a data type makes it easy to refer to non-payment information regarding a specific provision form. That is, by searching the non-payment information stored in the non-payment information storage unit 14 using the data type as a search key, it becomes possible to easily extract non-payment information related to a specific form of provision.

  When the unpaid information generation unit 13 finds the corresponding deposit journal information by the search, it corresponds to the balance of each sales form of the receivable information to be processed and the account code of the deposit journal information found by the search. Compare the deposit amount of each sales form. Here, the non-payment information generation unit 13 compares the balance of the same sales form with the deposit amount. The non-payment information generation unit 13 determines that there is no non-payment amount (paid) for the receivable information to be processed when the balance and the deposit amount match for all sales forms included in the receivable information. Then, the process for the account receivable information is terminated without generating the non-payment information related to the account receivable information.

  On the other hand, the non-payment information generation unit 13 determines that there is a non-payment amount regarding the receivable information to be processed when the balance and the deposit amount do not match for at least one sales form included in the receivable information. Then, non-payment information related to the account receivable information is generated. Specifically, the non-payment information generation unit 13 subtracts the deposit amount of each sales form indicated in the payment journal information found by the search from the balance of each sales form of the sales receivable information to be processed. The balance of each sales form at the time of processing (processing date) is calculated. Then, the non-payment information generation unit 13 sets the calculated balance of each sales form as the non-payment amount of each sales form of the newly generated non-payment information. With respect to data items other than the non-payment amount of each sales form of the non-payment information, the non-payment information generation unit 13 can set by the same method as in the case where the corresponding deposit journal information is not found by the above search. it can.

  The non-payment information C1 and C2 shown in FIG. 4 is non-payment information generated by the non-payment information generation unit 13 based on the accounts receivable information B1 and B2 by the above-described processing. In the present embodiment, when the non-payment information C1 and C2 is generated, the payment journal information whose invoice number is “3100001” or “3100002” is stored in the accounts receivable management information storage unit 12. Absent. For this reason, the non-payment amount of each sales form of the non-payment information C1, C2 matches the balance of each sales form of the accounts receivable information B1, B2.

  As a result of the above-described processing by the non-payment information generation unit 13, as shown in FIG. 4, the non-payment information storage unit 14 stores a business partner code for identifying a business partner (payment source) and an unpaid amount of the business partner. One or more non-payment information is stored.

  The index information storage unit 15 is an index information storage unit that stores index information in which one or more business partner codes are associated with one account information (bank name, branch name, and name). In the index information storage unit 15, for example, a set of account information and a supplier code that has been associated with a deposit amount and a non-payment amount in the past is stored in advance by an input by an operator or the like. In the present embodiment, in the past, the deposit amount from the account information X to the deposit account of the provider is associated as a payment for the unpaid amount of the non-payment information whose supplier codes are “32136” and “32137”. There shall be. That is, in this embodiment, as shown in FIG. 5, the index information storage unit 15 has two supplier codes (“32136” which is a supplier code 1 and a supplier code 2) for the account information X. Index information D associated with “32137”) is stored.

  In addition, a billing date (billing date 1 and billing date 2) is associated with each customer code (customer code 1 and customer code 2) in the index information. The billing date associated with each supplier code is related as a payment for the unpaid amount of the non-payment information including the supplier code by the associating unit 18 to be described later. The latest billing date is shown. The billing date associated with each supplier code is set by processing by the associating unit 18 to be described later or manually by an operator or the like.

  The billing information acquisition unit 16 refers to the index information stored in the index information storage unit 15, so that one or more transactions associated with the account information X of the payment information A acquired by the payment information acquisition unit 11. This is billing destination information acquisition means for acquiring a destination code. Specifically, the billing destination information acquisition unit 16 performs the following processing.

  The billing destination information acquisition unit 16 checks whether or not index information including the account information X of the deposit information A acquired by the deposit information acquisition unit 11 is stored in the index information storage unit 15 by searching or the like. When index information including account information X is stored in the index information storage unit 15, the billing destination information acquisition unit 16 acquires the supplier code and billing date of the index information. In the present embodiment, since the index information D including the account information X is stored in the index information storage unit 15, the billing destination information acquisition unit 16 is provided with the supplier code (the customer code 1 and the customer code 1 and the index information D). Obtain supplier code 2) and billing date (billing date 1 and billing date 2).

  On the other hand, if index information including the account information X is not stored in the index information storage unit 15, the billing information acquisition unit 16 converts the payment information A acquired by the payment information acquisition unit 11 into the unmatch list. Add to The unmatch list is a list in which payment information that cannot be subjected to payment processing by processing of the collation unit 17 and the association unit 18 described later is stored, and is stored in a database (not shown) or the like. The deposit information registered in the unmatch list is confirmed by an operator or the like, for example, and a manual deposit process (individual deposit process) is executed. For example, the operator or the like specifies the non-payment amount of the non-payment information corresponding to the deposit amount of the deposit information by individual confirmation such as telephone contact with the deposit source. In this individual deposit process, when the unpaid amount of the unpaid information corresponding to the deposited amount of the deposit information is specified, the operator or the like manually performs the unpaid on the account information X of the deposited information. Index information (the above-mentioned index information D) that associates the information supplier code and the billing date is newly generated and stored in the index information storage unit 15. As a result, the next time the deposit is made from the account information X to the deposit account of the provider, that is, when the deposit information including the account information X is acquired by the deposit information acquiring unit 11, the billing information acquiring unit 16 Can acquire the supplier code and the billing date associated with the account information X based on the index information D stored in the index information storage unit 15.

  The collation unit 17 extracts the non-payment information including the supplier code acquired by the billing destination information acquisition unit 16 from the non-payment information stored in the non-payment information storage unit 14, and the extracted non-payment information This is a collation means for collating whether or not the unpaid amount and the deposit amount of the deposit information acquired by the deposit information acquiring unit 11 correspond to each other. Specifically, the collation part 17 performs the following processes.

  First, the collation unit 17 includes non-payment information including the supplier code (“32136” and “32137”) acquired by the billing destination information acquisition unit 16 from the non-payment information stored in the non-payment information storage unit 14. (Non-payment information C1, C2, etc.) is extracted.

Subsequently, the collation unit 17 performs primary matching. The primary matching is a process of collating the deposit amount of the deposit information A acquired by the deposit information acquisition unit 11 with the unpaid amount of the non-deposit information related to the latest month (current month). For example, the collation unit 17 acquires the newest billing date (“1301” in the present embodiment) among the billing dates included in the extracted non-payment information.
However, the method for acquiring information indicating the latest month is not particularly limited. For example, the collation unit 17 may store information indicating the latest month in advance by an advance input by an operator or the like.

  Subsequently, the collation unit 17 further extracts non-payment information C1 and C2 including “1301” acquired as information indicating the latest month as the billing date as the non-payment information to be collated. Note that the procedure for the collation unit 17 to extract the non-payment information C1 and C2 to be collated is not limited to a specific procedure. For example, the collation unit 17 does not execute the two-stage extraction process as described above, but includes non-payment information that includes the supplier code acquired by the invoice destination information acquisition unit 16 and whose invoice date is the latest month. May be extracted by a single extraction process. As described above, the collation unit 17 determines whether or not to make the non-payment information to be collated based on the billing date (billing time information) of the non-payment information stored in the non-payment information storage unit 14. The non-payment information C1 and C2 determined to be included in the verification while including the supplier code acquired by the billing information acquisition unit 16 are extracted.

  Subsequently, the collation unit 17 performs collation between the non-payment amount indicated in the non-payment information and the deposit amount of the deposit information A acquired by the deposit information acquisition unit 11. Here, “non-payment amount indicated in non-payment information” to be collated includes non-payment amount of a specific sales form (for example, rental balance of non-payment information C1, etc.), non-payment amount of a plurality of sales forms (For example, rental of non-payment information C1 and total fare balance) and the total of non-payment amounts of multiple non-payment information (for example, rental balance of non-payment information C1 and rental of non-payment information C2) This means unpaid amount in any combination such as total balance. The collation unit 17 performs the above-described collation in the order and combination preset by, for example, an operator.

  As an example in this embodiment, the collation unit 17 first collates the deposit amount of the deposit information A in the order of “rental”, “freight”, “sorted sales”, and “total balance” with respect to the non-payment information C1. That is, the matching unit 17 performs the matching based on the non-payment amount for each sales form (classification). If it is not determined that the unpaid amount and the deposited amount match in such verification, the verification unit 17 performs “rental”, “freight”, “consolidated sales”, “ The deposit amount of deposit information A is collated in the order of “total balance”. Here again, if it is not determined that the non-payment amount matches the deposit amount, the collation unit 17 sums the non-payment amounts of the plurality of non-payment information C1, C2 (the total balance of a specific sales form or all of them) The total amount of sales in the sales form) and the deposit amount of the deposit information A are collated.

  When it is determined that the non-payment amount and the deposit amount match by the above-mentioned collation, or the collation unit 17 performs the collation with all combinations set in advance by an operator or the like, the non-payment amount and the deposit amount Is not determined to match, the primary matching is terminated.

  When it is determined that the unpaid amount and the deposited amount match, the matching unit 17 outputs a matching result that the unpaid amount and the deposited amount correspond to each other to the associating unit 18. The verification result includes information indicating the deposit information A to be verified, and breakdown information indicating a breakdown of the unpaid amount determined to match the deposit amount of the deposit information A. The breakdown information is information indicating a set of non-payment information and sales form in which it is determined that the deposit amount and the non-payment amount of the deposit information A match. That is, the breakdown information is information indicating which sales form balance of which non-payment information is included in the non-payment amount determined to match the deposit amount of the deposit information A. In addition, the collation unit 17 can grasp that the collation result corresponding to each other by the primary matching is obtained by the operator or the like. Information indicating primary matching may be given to the matching result.

  On the other hand, if it is not determined that the non-payment amount matches the deposit amount even after collation with all combinations set in advance by an operator or the like, the collation unit 17 executes secondary matching. Also good. The secondary matching is a process of collating the deposit amount of the deposit information A acquired by the deposit information acquisition unit 11 with the unpaid amount of the unpaid information related to the oldest billing date among the extracted unpaid information. is there. The procedure for collating the non-paid amount and the deposited amount in the secondary matching is the same as in the above-described primary matching. In the present embodiment, the collation unit 17 ends the collation process and determines the deposit information acquisition unit 11 when it is determined that the non-payment amount and the deposit amount do not match in either the primary matching or the secondary matching. Is added to the unmatch list. However, the procedure of collation processing by the collation unit 17 is not limited to the above. For example, the collation unit 17 may execute only the primary matching or the secondary matching, or may execute the secondary matching before the primary matching. In addition, the matching unit 17 may execute matching that is not related to the billing date of the non-payment information (that is, a process of matching the deposit amount and the non-payment amount with all the extracted non-payment information as a collation target). .

  In the present embodiment, the collation unit 17 performs the above-described primary matching to obtain the balance total of non-payment information C1 (63,000 yen) and the balance total of non-payment information C2 (6,300 yen). It is determined that the added amount matches the deposit amount of deposit information A. And the collation part 17 outputs the collation result including the breakdown information which shows that the breakdown of the non-payment amount is the balance total of the non-payment information C1 and the balance total of the non-payment information C2. Moreover, the collation part 17 provides the information which shows primary matching as a kind of matching to a collation result.

  The associating unit 18 is an associating unit that executes a process of associating the deposit amount and the non-payment amount obtained by the collation unit 17 so as to correspond to each other. Specifically, the associating unit 18 includes the deposit information A acquired by the deposit information acquiring unit 11, the non-payment information C1 and C2 stored in the non-payment information storage unit 14, and the verification result by the verification unit 17. Based on the information, the payment journal information is generated by associating the deposit amount of the deposit information A with the unpaid amounts of the deposit information C1 and C2. More specifically, the associating unit 18 generates the above-described two types of journal data, that is, the debit and the credit for each set (each set of non-payment information and sales form) indicated in the breakdown information of the matching result. The pair of the debit and credit journal data for each group indicates that the (a part of) the deposit amount of the deposit information A is associated with the unpaid amount of the sales form of the non-payment information shown in the group. Each of the debit and credit journal data is information in which an invoice number, a data type, a payment date, a payment date, a loan classification, an account item code, and an amount are associated with each other.

  The account item code of each journal data is a code set in advance by an operator or the like for each account item such as ordinary deposit, accounts receivable (rental fee), uncollected fare, and accounts receivable (off-charge fee). In the present embodiment, as an example, codes of “0002” are set in advance for the ordinary deposit, “0031” for the accounts receivable (rental fee), “0040” for the uncollected fare, and “0042” for the accounts receivable (off charge fee). . Here, the ordinary deposit is an account item corresponding to the deposit amount deposited in the deposit account of the provider. Accounts receivable (rental charges), uncollected fares, and accounts receivable (off-charge charges) are account items corresponding to each sales form.

  The associating unit 18 sets each group (rental of non-payment information C1, fare of non-payment information C1, organized sales of non-payment information, rental of non-payment information C2, fare of non-payment information C2) shown in the breakdown information of the verification result In addition, each item of the journal data of the debit and the credit is set for the non-payment information).

  In the following, a process when each item of the debit journal data E11 and the credit journal data E12 for “rental of non-payment information C1” is set will be described. The associating unit 18 sets the invoice number, data type, and billing date of the non-payment information C1 to the invoice number, data type, and payment date of each journal data E11, E12. Further, the date of receipt of the receipt information A by the receipt information acquisition unit 11 (processing date) is set to the receipt date of each journal data E11, E12. Further, “31,500 yen”, which is the non-payment amount (= payment amount for the non-payment amount) of the sales form (rental) of the non-payment information C1, is set as the amount of each journal data E11, E12. Further, the association unit 18 sets “2” indicating the debit category to the debit category and “0002” indicating the ordinary deposit to the account code for the debit journal data E11. On the other hand, with respect to the credit journal data E12, the associating unit 18 sets “1” indicating the credit classification to the credit classification, and the account code “indicating the account corresponding to the sales form (rental)” is set in the account code. "0031" is set. The pair of journal data E11 and E12 indicates that “31,500 yen”, which is a part of the deposit amount of the deposit information A, is associated as a payment for the unpaid amount of “rental” of the non-payment information C1.

  Similarly, the pair of journal data E21 and E22 indicates that “21,000 yen”, which is a part of the deposit amount of the deposit information A, is associated as a payment for the unpaid amount of “fare” of the non-payment information C1. ing. The pair of journal data E31 and E32 indicates that “10,500 yen”, which is a part of the deposit information of the deposit information A, is associated as a payment for the unpaid amount of “consolidated sales” of the non-payment information C1. ing. The pair of journal data E41 and E42 indicates that “3,150 yen”, which is a part of the deposit information of the deposit information A, is associated as payment for the unpaid amount of “rental” of the non-payment information C2. Yes. The pair of journal data E51 and E52 indicates that “2,100 yen”, which is a part of the deposit information of the deposit information A, is associated as payment for the unpaid amount of “fare” of the non-payment information C2. Yes. The pair of journal data E61 and E62 indicates that “1,050 yen”, which is part of the deposit information of the deposit information A, is associated as a payment for the unpaid amount of “consolidated sales” of the non-payment information C2. ing.

  FIG. 6B is tabular data formatted so that the correspondence between the deposit amount (debit) and the unpaid amount (credit) can be easily understood based on the deposit journal information shown in FIG. . The associating unit 18 can generate data shown in FIG. 6B by using a function such as commercially available application software for managing accounts receivable. However, the associating unit 18 does not necessarily have to generate the data shown in FIG.

  In the data shown in FIG. 6B, the record E1 on the first line indicates data corresponding to a pair of journal data E11 and E12. The data related to the debit of the record E1 is data in which the account item code of the journal data E11, the name of the account item corresponding to the account item code, and the amount are associated. The data related to the credit of the record E1 is data in which the account item code of the journal data E12, the name of the account item corresponding to the account item code, and the amount are associated. Records E2 to E6 are the same data as record E1. The record E2 is data corresponding to the pair of journal data E21, E21, the record E3 is data corresponding to the pair of journal data E31, E31, and the record E4 corresponds to the pair of journal data E41, E41. The record E5 is data corresponding to a pair of journal data E51 and E51, and the record E6 is data corresponding to a pair of journal data E61 and E61.

  Moreover, the associating unit 18 may execute the following processing in addition to generating the above-described deposit journal information. That is, as shown in FIG. 7A, the associating unit 18 adds the payment information A acquired by the payment information acquiring unit 11 based on the information indicating the type of matching given to the verification result by the verification unit 17. A processing flag may be added. This processing flag is information indicating the type of collation processing (primary matching, secondary matching, individual deposit processing, etc.) performed for obtaining the collation result. The associating unit 18 stores in advance the contents of the processing flag corresponding to each matching process, and assigns the processing flag corresponding to the type of matching to the deposit information A. For example, when the type of matching is primary matching, the associating unit 18 assigns “5” as the processing flag. On the other hand, the associating unit 18 assigns “4” as the processing flag when the type of matching is secondary matching. Further, the association unit 18 assigns “3” as a processing flag in cases other than the above (when collation processing by individual deposit processing is performed). In this embodiment, since the information indicating the type of matching given to the collation result is information indicating primary matching, the associating unit 18 gives “5” as the processing flag to the deposit information A.

  As shown in FIG. 7A, the associating unit 18 may give a deposit flag to the deposit information A acquired by the deposit information acquiring unit 11. The deposit flag is information indicating whether or not deposit journal information, which will be described later, is generated for the deposit information A. For example, the associating unit 18 generates information for depositing journal information for the depositing information A, and then indicates that the processing for generating the depositing journal information for the depositing information A is completed as the depositing flag for the depositing information A (this implementation). In the form, “*”) is given. Thereby, the operator or the like can easily grasp whether or not the processing for each piece of payment information acquired by the payment information acquisition unit 11 is completed by referring to the payment flag of the payment history information. The deposit information A to which the processing flag and the deposit flag are added as described above is stored in a database (not shown) or the like as deposit history information for the operator or the like to grasp the processing status for the deposit information.

  As illustrated in FIG. 7B, the associating unit 18 may update the billing date of the index information D stored in the index information storage unit 15 based on the breakdown information of the collation result by the collation unit 17. . Specifically, the associating unit 18 refers to the supplier code and the billing date of each set of non-payment information (non-payment information C1 and C2 in this embodiment) indicated in the breakdown information of the collation result. When the billing date of each supplier code in the index information D indicates a date older than the billing date of each non-payment information, the billing date of each supplier code in the index information D is “1301”, which is the billing date of the non-payment information C1 and C2, is set. Accordingly, the index information D indicates that the latest billing date in which the non-payment amount and the deposit amount of the non-payment information including the supplier code is associated is “January 2013”. Such information indicating the latest billing date is used as reference information when, for example, an operator or the like manually matches a deposit amount and an unpaid amount.

  As illustrated in FIG. 7C, the associating unit 18 may add a processing flag to the non-payment information stored in the non-payment information storage unit 14 based on the breakdown information of the collation result by the collation unit 17. . Specifically, the associating unit 18 processes the non-payment information C1 and C2 in which the breakdown information includes a set relating to all sales forms (the deposit amount is associated with the non-payment amount of all sales forms). Give a flag. This processing flag is information indicating that the non-payment information has been deposited (the balance has been lost). For example, the associating unit 18 assigns “1” to the non-payment information C1 and C2 as a processing flag indicating that the non-payment information has been deposited. On the other hand, the associating unit 18 does not assign a processing flag to non-payment information in which a balance remains for at least one sales form. The non-payment information to which the processing flag is given is removed from the extraction target by the collation unit 17 described above by being deleted from the non-payment information storage unit 14 at a predetermined timing. On the other hand, the non-payment information to which the processing flag has not been assigned (the non-payment information in which the balance remains) is continuously stored in the non-payment information storage unit 14 as an extraction target by the matching unit 17.

  The deposit journal information (see FIG. 6A) generated by the associating unit 18 is stored in the accounts receivable management information storage unit 12. The deposit journal information is referred to by the non-payment information generation unit 13 described above. That is, as described above, the non-payment information generation unit 13 refers to the payment journal information in order to generate non-payment information. Further, the payment journal information is referred to by a monthly processing unit (not shown) for executing a receivable application process (update of receivable information) which is a monthly process. The monthly processing unit is a means for executing an account receivable process as a monthly process at a date and time preset by an operator or the like every month. The account receivable process is a process for updating the receipt related information of the account receivable information stored in the account receivable management information storage unit 12 based on the receipt journal information generated by the daily process described above. An operator or the like can grasp whether or not the payment for the accounts receivable in each sales form has been completed by referring to the payment related information in the updated accounts receivable information.

  Specifically, the monthly processing unit, for example, among the journal data E11, E21, E31, E41, E51, E61 whose balance class is “2” shown in FIG. The following processing is executed for journal data to which no is assigned. Hereinafter, the process for the journal data E11 to which the updated flag is not assigned will be described as a representative of the process for each journal data.

  The monthly processing unit extracts the receivable information B1 associated with the same invoice number (3100001) as the invoice number of the journal data E11 from the receivable information stored in the receivable management information storage unit 12. . Then, the monthly processing unit sets the deposit date (20130131) of the journal data E11 as the deposit date of the rental receipt information of the accounts receivable information B1. Further, the “rental” amount (31,500 yen) corresponding to the account item code “0031” of the journal data E11 is set as the deposit amount of the rental receipt information of the accounts receivable information B1. After that, the monthly processing department rents the amount (0 yen) obtained by subtracting the deposit amount (31,500 yen) of the rental receipt information from the total rental fee and consumption tax (31,500 yen) of the A / R information B1. Set to the deposit information balance. As a result, as shown in FIG. 8, the deposit amount of the rental deposit information of the A / R information B1 is updated to “31,500”, the deposit date is updated to “20130131”, and the balance is updated to “0”. Is done. In the same way as the rental receipt information in the A / B information B1, the fare receipt information and the arranged sale receipt information in the A / B information B1, and the rental receipt information, the fare receipt information, and the arranged sale receipt information in the A / B information B2 are respectively journalized. It is updated based on the data E21, E31, E41, E51, E61. The monthly processing unit adds an updated flag indicating that the account receivable information is updated using the journal data to the journal data used for updating the account receivable information as described above. Thereby, the receivable information update based on each journal data is executed only once, and the receivable information is appropriately updated by the monthly processing unit.

  FIG. 9 is a flowchart showing the operation of the deposit processing apparatus 1. The operation of the deposit processing apparatus 1 including the deposit processing method according to one embodiment of the present invention will be described with reference to FIG. However, step S9 in FIG. 9 is an individual deposit process executed by an operator or the like, and is not a process executed by the deposit processing apparatus 1.

  First, payment information A is acquired by the payment information acquisition unit 11 (step S1, payment information acquisition step). Subsequently, the billing information acquisition unit 16 refers to the index information stored in the index information storage unit 15 and acquires one or more supplier codes associated with the account information X of the deposit information A (step) S2, S3, billing information acquisition step). Specifically, first, the billing information acquisition unit 16 checks whether index information including the account information X is stored in the index information storage unit 15 by searching or the like (step S2).

  When the index information including the account information X is stored in the index information storage unit 15 (step S2: YES), the billing information acquisition unit 16 acquires the supplier code and the billing date of the index information. (Step S3). In the present embodiment, since the index information D including the account information X is stored in the index information storage unit 15, the billing destination information acquisition unit 16 uses the supplier code (“32136” and “ 32136 ") and the billing date (" 1301 ") corresponding to each supplier code are acquired (step S2: YES, step S3).

  Subsequently, the non-payment information including the supplier code acquired by the billing destination information acquisition unit 16 is extracted from the non-payment information stored in the non-payment information storage unit 14 by the collation unit 17, and the extracted non-payment information is extracted. A check is performed to determine whether or not the unpaid amount of the deposit information and the deposited amount of the deposit information acquired by the deposit information acquiring unit 11 correspond to each other (step S4 → S5 → S6 or step S4 → S5 → S7 → S6, collation step). Specifically, first, the non-payment information including the supplier code acquired by the billing information acquisition unit 16 is extracted from the non-payment information stored in the non-payment information storage unit 14 by the matching unit 17. (Step S4).

  Subsequently, when the matching unit 17 performs primary matching and determines that the unpaid amount and the deposited amount match (step S5: YES), the unpaid amount and the deposited amount correspond to each other. Then, the collation result is output (step S6). On the other hand, when it is not determined that the non-payment amount matches the deposit amount in the primary matching (step S5: NO), the secondary matching is executed. If it is determined in the second matching that the non-payment amount matches the deposit amount (step S7: YES), a matching result indicating that the non-payment amount and the deposit amount correspond to each other is output (step S6). ). In the present embodiment, as described above, the sum of the balance of the non-payment information C1 (63,000 yen) and the balance of the non-payment information C2 (6,300 yen) is added by the primary matching (69, (300 yen) and the deposit amount (69,300 yen) of the deposit information A are determined to match, and a matching result indicating this is output (step S5: YES, step S6).

  Subsequently, the associating unit 18 performs a process of associating the deposit amount and the non-payment amount obtained by the collation unit 17 so as to correspond to each other (step S8, association step). Specifically, in step S8, the associating unit 18 updates various data (payment information A, index information D, non-payment information C1, C2) based on the collation result, and deposit journal information (FIG. 6 ( a) see) is generated. The payment journal information generated in step S8 is stored in the accounts receivable management information storage unit 12, and is referred to by the above-mentioned non-payment information generation unit 13 to generate non-payment information. The payment journal information is also referred to by a monthly processing unit (not shown) in order to execute a receivable application process (update of receivable information) which is a monthly process.

  On the other hand, when the index information including the account information X is not stored in the index information storage unit 15 in step S2 (step S2: NO), it is not determined that the unpaid amount and the deposited amount match in the secondary matching. If this is the case (step S7: NO), an individual deposit process by an operator or the like is executed (step S9).

  FIG. 10 is a block diagram showing a functional configuration (module configuration) of the deposit processing program P1. The deposit processing program P <b> 1 is a program for causing a computer to function as the deposit processing apparatus 1. As shown in FIG. 10, the deposit processing program P1 includes a deposit information acquisition module P11, an unpaid information storage module P12, an index information storage module P13, a billing destination information acquisition module P14, a collation module P15, and an association module P16. The functions realized by executing the receipt information acquisition module P11, the non-payment information storage module P12, the index information storage module P13, the billing destination information acquisition module P14, the collation module P15, and the association module P16, respectively, The functions of the deposit information acquisition unit 11, the non-payment information storage unit 14, the index information storage unit 15, the billing destination information acquisition unit 16, the collation unit 17, and the association unit 18 of the processing device 1 are the same.

  The deposit processing program P1 is stored in a recording medium such as a CD-ROM, DVD, and HD, and is executed by a computer used as the deposit processing apparatus 1. Specifically, the computer includes a recording medium reading unit such as a CD-ROM drive, a DVD drive, and an HDD. When the recording medium is set in the recording medium reading unit, the computer can access the deposit processing program P1 stored in the recording medium from the recording medium reading unit. Then, the computer can be operated as the deposit processing apparatus 1 by causing the computer to execute the deposit processing program P1. The deposit processing program P1 may be provided via a network as a data signal superimposed on a carrier wave.

  Then, the effect of the money_receiving | payment processing apparatus 1 which concerns on this embodiment is demonstrated. First, the reason why it is not easy to properly associate the deposit amount included in the deposit information with the accounts receivable balance (unpaid amount) managed by the provider will be described below.

  The deposit information A acquired from the FB system 2 does not include a supplier code that is uniquely assigned and managed by the provider. Moreover, the account information X of the depositing source used when the depositing source deposits is not normally registered in the supplier master managed independently by the providing source. Also, it is not normal for the provider to specify the bank account of the deposit source that is used for payment for each bill. Furthermore, since the payment source may pay in a lump sum to pay the charge amounts related to a plurality of different charges by bank transfer, the deposit amount related to one deposit is not necessarily one charge (for example, one invoice). ) Does not necessarily correspond to the amount charged. Further, when the payment source is a parent company having a plurality of subsidiaries, the payment source may collectively deposit the total amount charged for each of the plurality of subsidiaries. For this reason, it is not easy for an operator or the like to manually associate a deposit amount from a certain account information X with a non-payment amount of a specific customer, and it takes a lot of work time.

  In the deposit processing apparatus 1 according to the present embodiment, when the deposit information A is acquired by the deposit information acquisition unit 11, the billing information acquisition unit 16 refers to the index information stored in the index information storage unit 15. Thus, one or more business partner codes (“32136” and “32137”) associated with the account information X of the deposit information A are acquired. Subsequently, the collation unit 17 extracts the non-payment information C1 and C2 including the supplier code, and collates the non-payment amount of the non-payment information C1 and C2 with the deposit amount of the payment information A. Then, the associating unit 18 executes a process of associating the non-paid amount and the deposited amount, which are obtained as matching results corresponding to each other.

  According to the deposit processing apparatus 1, since the account information X and the customer code can be linked based on the index information D, the work time for linking the account information X and the customer code can be shortened. it can. Further, as described above, in commercial transactions, for example, the parent company often makes payments for paying the accounts receivable of a plurality of subsidiaries at once. According to the deposit processing apparatus 1, the deposit process can be appropriately executed even in such a case. That is, based on the index information D in which the account information X of the parent company and the business partner codes of a plurality of subsidiaries (here, “32136” of the subsidiary a and “32137” of the subsidiary b) are associated, a plurality of subsidiaries a, b's non-payment information C1 and C2 can be extracted, and the non-payment amounts of the non-payment information C1 and C2 can be collated with each other and related to each other. Thus, according to the deposit processing apparatus 1, the deposit information A and the one or more non-payment information C1 and C2 can be automatically and appropriately associated with each other based on the index information D. As a result, the accuracy of processing can be improved.

  Further, in the deposit processing apparatus 1, the non-payment information C1 and C2 stored in the non-payment information storage unit 14 includes a non-payment amount for each predetermined sales form (classification). 17 can execute the above collation based on the non-payment amount for each sales form. According to such a deposit processing apparatus 1, since the collation is executed based on a predetermined amount of non-payment for each sales form, the deposit amount and the non-payment amount can be associated appropriately. For example, when payment is made for unpaid amounts in all sales forms (lump sum payment), or when only payment is made for unpaid amounts for some sales forms (for example, “rental”) (partial payment) It is possible to appropriately associate the deposit amount and the non-deposit amount. Thereby, it is possible to appropriately execute the deposit process for both collective deposit and partial deposit.

  In the deposit processing apparatus 1, the non-payment information C1 and C2 stored in the non-payment information storage unit 14 includes the billing date (billing time information) for the billing party. Based on the billing date of the non-payment information C1 and C2 stored in the non-payment information storage unit 14, it is determined whether or not the non-payment information C1 and C2 is to be collated. And the collation part 17 extracts the non-payment information C1 and C2 determined to be the object of collation including the supplier code acquired by the billing information acquisition part 16, and the extracted non-payment information C1 and C2 The above collation can be executed for the unpaid amount and the deposited amount of deposit information A. According to such a deposit processing apparatus 1, the deposit amount and the non-deposit amount can be appropriately associated based on the billing date. For example, when receivables are billed periodically (for example, monthly), it may be determined that only non-payment information C1 and C2 related to billing for the latest month is to be collated as in the above-mentioned primary matching. it can. As a result, if the business partner (payment source) failed to pay for the previous (previous month) billing due to misunderstandings, etc., and made the payment for the latest month billing, the deposit amount (payment information A deposit amount) can be appropriately associated with the unpaid amount of the latest month (the unpaid amount of the non-payment information C1 and C2). As a result, it is possible to suppress the occurrence of flaws related to deposits with business partners.

  The present invention has been described in detail based on the embodiments. However, the present invention is not limited to the above embodiment. The present invention can be variously modified without departing from the gist thereof. For example, the collation unit 17 may perform collation in consideration of a fee related to payment as described below.

  For example, if the deposit source misunderstands the fees that are incurred at the time of deposit (for example, bank transfer fees), the amount to be paid (the amount not yet paid) is the amount that is greater (or less) than the amount to be paid There is a risk of being. As such a case, for example, a case where the deposit source forgets to pay the fee (a case where the deposit amount is smaller than the non-payment amount by the fee) can be considered. In addition, in the case where the billing source bears the transfer fee (the case where the deposit source only has to deposit the transfer fee minus the transfer fee), the case where the payment source mistakenly pays the transfer fee (the deposit amount is not equal to the fee) A case in which the amount of money is larger than the deposit amount) may also be considered. In such a case, there is a difference between the unpaid amount and the deposited amount by the fee. Here, if the non-payment amount and the payment amount match each other based on whether or not the amounts match, they will correspond to each other even though they correspond to each other. The result of the verification that it is not a thing is output, and the deposit process is not properly executed.

  Therefore, the collation unit 17 may perform the above-described collation between the unpaid amount and the deposited amount in consideration of the fee related to the deposit. Specifically, the collation unit 17 stores a fee related to payment (for example, “315 yen”, “525 yen”, etc.) in advance. Then, the collation unit 17 determines whether or not the difference between the unpaid amount and the deposited amount matches the fee in the above collation. If the difference matches the fee, the unpaid amount and the deposited amount are determined. May output collation results that correspond to each other. This makes it possible to appropriately associate the deposit amount with the non-payment amount in consideration of the fee generated at the time of deposit.

  Further, the collation unit 17 determines a fee that is considered to be highly likely that the customer has mistakenly charged the fee (for example, “300 yen” that the customer has forgotten to pay for the consumption tax of the fee). May be stored as information (flagged fee) that holds a checklist output flag. Here, the fee check list is a list in which payment information that is considered to be highly likely that a business partner has received a fee in error is registered, and is stored in a database (not shown) or the like. The collation unit 17 determines whether or not the difference between the unpaid amount and the deposited amount matches the flagged fee in the above collation. If the difference matches the flagged fee, the deposit information is checked for the fee. You may output to the list. As a result, operators and others can efficiently conduct individual confirmations over the telephone, etc., for business partners that are the source of the deposit information registered in the checklist for commissions (partners who have a high possibility of depositing fees by mistake). It becomes possible to carry out well.

  DESCRIPTION OF SYMBOLS 1 ... Deposit processing apparatus, 11 ... Deposit information acquisition part, 12 ... Account receivable management information storage part, 13 ... Non-payment information generation part, 14 ... Non-payment information storage part, 15 ... Index information storage part, 16 ... Billing destination information Acquisition unit, 17 ... collation unit, 18 ... association unit, P1 ... deposit processing program, P11 ... deposit information acquisition module, P12 ... non-payment information storage module, P13 ... index information storage module, P14 ... billing information acquisition module, P15 ... collation module, P16 ... association module.

Claims (6)

A deposit information acquisition means for acquiring deposit information including a deposit source information for identifying a deposit source and a deposit amount of the deposit source;
Non-payment information storage means for storing one or more non-payment information including billing destination information for identifying a billing destination and the non-payment amount of the billing destination;
Index information storage means for storing index information in which one or more billing destination information is associated with one payment source information;
By referring to the index information stored in the index information storage unit, one or more billing destination information associated with the deposit source information of the deposit information acquired by the deposit information acquiring unit is acquired. Billing information acquisition means;
From the non-payment information stored in the non-payment information storage unit, the non-payment information including the billing destination information acquired by the billing destination information acquisition unit is extracted, and the extracted non-payment information Collating means for performing a collation of whether or not an unpaid amount and the deposit amount of the deposit information acquired by the deposit information acquiring unit correspond to each other;
An associating means for performing a process of associating the deposit amount and the non-paid amount with which the collation result corresponding to each other is obtained by the collating unit;
A deposit processing apparatus. The non-payment information stored in the non-payment information storage means includes a non-payment amount for each predetermined classification,
The matching means performs the matching based on the non-payment amount for each classification.
The deposit processing apparatus according to claim 1. The non-payment information stored in the non-payment information storage means includes billing time information indicating a billing time for the billing destination,
The collation means determines whether or not the non-payment information is to be collated based on the billing timing information of the non-payment information stored in the non-payment information storage means, and the billing information acquisition means The non-payment information that is determined to be the verification target is included, including the billing information acquired by the above, and the non-payment amount of the extracted non-payment information and the deposit amount of the payment information Perform matching,
The deposit processing apparatus according to claim 1 or 2. The verification means stores a fee related to deposit in advance, and determines whether or not a difference between the non-paid amount and the deposit amount matches the fee in the verification, and the difference matches the fee Output a matching result that the non-payment amount and the deposit amount correspond to each other,
The deposit processing device according to any one of claims 1 to 3. Non-payment information storage means for storing one or more non-payment information including billing destination information for identifying a billing destination and the non-payment amount of the billing destination, and one or more billing destination information for one payment source information A deposit processing method executed by a deposit processing apparatus comprising: index information storage means for storing associated index information,
A deposit information acquisition step for acquiring deposit information including the deposit source information for identifying the deposit source and the deposit amount of the deposit source;
By referring to the index information stored in the index information storage means, one or more billing information associated with the payment source information of the payment information acquired in the payment information acquisition step is acquired. A billing information acquisition step;
From the non-payment information stored in the non-payment information storage means, extract the non-payment information including the billing destination information acquired in the billing destination information acquisition step, and the extracted non-payment information A collation step of performing a collation of whether or not an unpaid amount and the deposit amount of the deposit information acquired in the deposit information acquisition step correspond to each other;
An association step of executing a process of associating the deposit amount and the non-payment amount obtained with a matching result corresponding to each other in the matching step;
Including deposit processing method. Computer
A deposit information acquisition means for acquiring deposit information including a deposit source information for identifying a deposit source and a deposit amount of the deposit source;
Non-payment information storage means for storing one or more non-payment information including billing destination information for identifying a billing destination and the non-payment amount of the billing destination;
Index information storage means for storing index information in which one or more billing destination information is associated with one payment source information;
By referring to the index information stored in the index information storage unit, one or more billing destination information associated with the deposit source information of the deposit information acquired by the deposit information acquiring unit is acquired. Billing information acquisition means;
From the non-payment information stored in the non-payment information storage unit, the non-payment information including the billing destination information acquired by the billing destination information acquisition unit is extracted, and the extracted non-payment information Collating means for performing a collation of whether or not an unpaid amount and the deposit amount of the deposit information acquired by the deposit information acquiring unit correspond to each other;
An associating means for executing a process of associating the deposit amount and the non-paid amount with which the collation result corresponding to each other is obtained by the collating unit;
Payment processing program to function as.

Images