JP2004302574A - Payment processing system and method - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To improve the efficiency of erasure processing. <P>SOLUTION: In this payment processing system for receiving and processing payment data including a business code supplied through a predetermined network for uniquely identifying at least a payment origin and payment information showing the amount of paid money, a computer is provided with a business department correspondence data base means, a claim information management data base means, a correspondence department extracting means, an accounting processing means and a processing invalidation display means. Thus, the accounting processing means extracts the combination of the sets of one or more such claim information that the same department identification information as one or more department identification information recorded by the correspondence department extracting means is included, and that the total sum of the claim sum agrees with or approximates to the sum of the the payment information by retrieving the claim information management data base means, and executes the erasure processing of the sets of the claim information. <P>COPYRIGHT: (C)2005,JPO&NCIPI

Description

[0001]
TECHNICAL FIELD OF THE INVENTION
The present invention relates to a payment processing system and method, in which, for example, a customer transfers money paid to a predetermined account such as a bank to a plurality of departments in the company that have been charging money to the customer. It is suitable to be applied to the case where the transfer is made.
[0002]
[Prior art]
2. Description of the Related Art Conventionally, for example, when money is charged or paid between companies, a billing company has performed operations such as creation and shipping of bills and creation of accounts receivable slips.
[0003]
On the other hand, the paying company that receives the bill has performed operations such as inspection of the contents of the bill and transfer of money to a bank in accordance with the contents of the bill. Then, the billing company collated the amount paid by transfer or the like with the amount charged.
[0004]
Since this series of operations is complicated and time-consuming, the techniques of Patent Literatures 1 to 3 below have been devised with the aim of improving the efficiency of the collation operation.
[0005]
Patent Literature 1 uses a plurality of virtual transfer-only accounts (transfer-only accounts) associated with payers. There is one original account (specific account) under which the plurality of transfer-only accounts are subordinated, and the money transferred to each transfer-only account is finally concentrated on this specific account. The point that the account number of the transfer-only account can be used to identify the payer can reduce the work load at the time of transfer among the series of works. Therefore, on the billing side, it is possible to specify the payer by utilizing the account number of the transfer-only account, etc., and it is possible to improve the efficiency of the transfer confirmation work.
[0006]
Further, Patent Document 2 discloses that when there are multiple types of claims from a certain invoicing company to a certain paying company, it is automatically checked whether or not the total amount of the multiple types of claims has been correctly paid. , To improve the efficiency of a series of operations.
[0007]
Further, Patent Literature 3 improves the efficiency of the matching process when the transfer amount paid by the payer does not match the amount charged by the requester.
[0008]
[Patent Document 1]
Japanese Patent No. 3029421
[0009]
[Patent Document 2]
Japanese Patent No. 3333126
[0010]
[Patent Document 3]
JP 2000-268119 A
[0011]
[Problems to be solved by the invention]
By the way, when a billing company actually requests money to be paid to an individual or a company on the paying side, a person in charge of the accounting department or the like often manages the money collectively. In many cases, the main body (that is, the entity responsible for the transaction that caused the bill) is each department (section, section, etc.) in the billing company. Therefore, each department of the billing company has the most detailed information on the billing situation such as the amount paid by the payer. For this reason, when collating the billed amount with the paid amount and performing operations such as clearing the billing data, if the collation could not be performed, each department must collaborate with the accounting department and other personnel. It is efficient to work. Further, for the company making the bill, the sum of the amounts billed from the respective departments is the amount billed to the paying individual and the like (including the paying company) as the entire billing company. If the money corresponding to the total value is paid as it is, the reconciliation process can be performed without any problem. However, actually, the reconciliation may not be performed.
[0012]
In Patent Documents 1 to 3, there is no description about the collation processing by cooperation between the departments in charge of transactions and the like and the collective management department such as the accounting department.
[0013]
Further, in Patent Document 3, if the transfer amount does not match the total invoice amount of a plurality of invoices, matching is performed on a bill-by-invoice basis. Is disclosed in which the invoices are combined and matched with the total invoice amount. Also disclosed is a process in which, when the number of invoices is larger than a predetermined number, the receivables data is collected in units of months, and the unit is similarly matched to the invoice unit or the total amount obtained by combining a plurality of invoices for each unit. ing. However, it does not show how to execute a combination of a plurality of invoices concretely, and after all, it is necessary to sum up a plurality of invoices for all combinations and perform a matching process on each of them. Instead, the number of steps in the matching process becomes enormous.
[0014]
In view of such circumstances, the present invention provides a means for efficiently comparing a billing amount and a paid amount with respect to a billing case generated in each department.
[0015]
[Means for Solving the Problems]
In order to solve such a problem, in the payment processing system according to the present invention, a handling code (for example, F1 in FIG. 4) supplied through a predetermined network and uniquely identifying at least the payment source that made the payment. ) And payment data (for example, RD3 in FIG. 4) including payment information indicating the amount of money paid in, the processing being performed by a computer. Operating department correspondence database means that registers in association with department identification information that uniquely identifies each department, billing amount information indicating the amount of money charged to the paying source based on a request from each department, The department identification information is associated with one set (a set is one line specified by a charge code L1 shown in FIG. 6) and registered as one or a plurality of sets of charge information. Claim information management database means, and when the payment data is received via a network, search the business department correspondence database means using the business code included in the payment data as a search key, and A corresponding section extracting unit that extracts a plurality of the section identification information and records the plurality of section identification information in association with the operation code and the payment amount information, and one or a plurality of the section identification information recorded by the corresponding section extraction unit. The billing information management database means retrieves and extracts a combination of one or a plurality of sets of the billing information having the same department identification information and having the total amount of the billing amounts matching or approximating the amount of the payment amount information. And an accounting processing means for executing the reconciliation processing of the set of billing information, and a reconciliation processing by the accounting processing means among the combinations of the set of billing information. Recorded for unhandled set that did not put off by, characterized in that a processing impossible display means for displaying.
[0016]
By adopting such a system, it is possible to perform the reconciliation work on the amount paid from the payment source for each section corresponding to the operation code, thereby improving the efficiency of the reconciliation work.
[0017]
Here, the operation code is information for uniquely identifying a payment source of the charged amount. The payer is, for example, a premium collector who collects insurance premiums for an insurance contract and pays the insurance company, or a person who pays when an individual or company purchases a product or service. The payment source is provided with an operation code for uniquely identifying each of the payment sources in advance.
[0018]
The section identification information is information for uniquely identifying a section having a correspondence relationship with the payer, and the section includes, for example, a sales office of an insurance company having jurisdiction over a premium collector, or a product or service provided. It means a sales department or the like in a company that is in charge of a customer to whom the product or service is sold. These departments are the most familiar with the information about the circumstances that cause the payment from the payment source, and in many cases, even if the payment cannot be cleared by computer, the cause can be easily clarified.
[0019]
Further, in the payment processing system according to the present invention, the processing-impossible display means includes means for receiving a display request for the unprocessable group from a predetermined section, and the section identification information of the predetermined section which has issued the display request. The payment processing system further includes means for identifying and displaying the unprocessable set included, and the payment processing system further includes correction means for allowing correction of the content displayed by the unprocessable display means. A correction for at least one of the department identification information and the billing amount information from the predetermined department is received, and the billing information management database unit, based on the correction received by the correction unit, the department identification information and The at least one of the billing amount information is updated, and the accounting processing unit is configured to update the billing amount after performing the updating process. Searches the broadcast management database means may be arranged such that the process scrubbing of the set of billing information.
[0020]
By performing such processing, for example, a billing amount (or a scheduled payment amount may be used) out of billing information (meaning information on a transaction or the like to be deposited regardless of whether a bill is issued). And so on) can be corrected from each department in charge, and the reconciliation process can be performed based on the corrected contents.
[0021]
Further, in the payment processing system according to the present invention, the processing inability display means includes the payment data including the operation code whose combination of one or a plurality of sets of the billing information could not be extracted by the accounting processing means. The payment processing system further includes a business code correction unit that allows correction of the business code included in the displayed payment data, and the corresponding department extraction unit includes the business code Using the operating code corrected by the correction unit as a search key, one or more corresponding department identification information is extracted again, and the accounting processing unit uses the newly extracted one or more department identification information. The reconciliation process of the set of billing information may be executed.
[0022]
By doing so, it is possible to smoothly cope with a case where the application cannot be applied due to an input error of the business code included in the transfer data.
[0023]
Further, in the payment processing system according to the present invention, for a group that cannot be processed, a first notification of non-application is transmitted to a section corresponding to the section identification information to thereby prompt a clearing for each section. Means, wherein the processing disable notification means checks whether or not the set notified by the first apply disable notification has been applied, and addresses the sets that could not be applied to a plurality of departments. It is also possible to transmit a second revocation disable notification.
[0024]
By adopting such a system, for example, if there is a payment case for which the cause of the inability to apply cannot be ascertained even if the department corresponding to the business code is notified of the inability to process, It can be sent to the department to find out why it could not be applied.
[0025]
Further, in the payment processing system according to the present invention, the accounting processing means selects all or some of the extracted sets of the billing information, and calculates the total value of the billing amounts indicated by the billing amount information for the selected set. May be provided, and a comparison determination unit that checks the magnitude relationship between the total value and the value indicated by the payment amount information in the payment data corresponding to the corresponding operation code.
[0026]
By doing so, it is possible to combine and sum the billing amount between the specific multiple pairs and compare it with the transferred amount, and check which combination matches the payment data Can be. Also, if the transfer fee to a financial institution is deducted, the total billed amount of multiple billing cases may be larger than the transfer amount, but if the transfer amount is larger than the billed amount, It is considered that collation cannot be performed, and such a determination can be made.
[0027]
Further, in the payment processing system according to the present invention, the billing information management database means includes a priority setting section for registering information indicating a priority in advance in the set of the billing information, and the total value calculating means May select a set in accordance with the priority so that the total value is equal to or greater than the value indicated by the paid-in amount information.
[0028]
This makes it possible, for example, to give priority to the billing information that is certain to be transferred, and to apply the transfer data sequentially from the higher priority billing information, so that the clearing process can be performed. Can be performed efficiently.
[0029]
Further, in the deposit processing system according to the present invention, the total value calculating means determines that, as a result of the inspection, the total value is equal to or more than the value indicated by the payment amount information, and the number of sets to be subjected to the application processing is maximized. May be provided, and a selection group number priority adaptive control unit that performs the selection process according to the selection.
[0030]
Further, in the deposit processing system according to the present invention, as a result of the inspection, the total value calculating means is such that the total value is equal to or more than the value indicated by the paid amount information, and a difference between the total value and the value indicated by the paid amount information is minimum. It is also possible to select a set so as to satisfy the condition, and execute the erasing process according to the selection.
[0031]
Further, in the deposit processing system according to the present invention, the financial institution system facing the deposit processing system via the network associates a plurality of related accounts with a single payment receiving account, and sets a predetermined related account identification information. In the case of providing an associated account service that uniquely identifies an associated account by using the relevant account, the payment source is caused to pay the money to an associated account associated with itself, and the associated account identification of the associated account is performed. The information may include information on the handling code or the content of the transaction.
[0032]
Furthermore, in the payment processing method according to the present invention, a payment code that is supplied through a predetermined network and uniquely identifies at least the payment source that has made the payment, and a payment amount that indicates the amount of the paid money. A payment processing method for receiving and processing payment data including information, wherein the computer associates the operating code with department identification information for uniquely identifying each department, and manages the corresponding department. And the billing amount information indicating the amount of money to be paid to the payer and the department identification information are associated as one set, and one or a plurality of sets of the billing information are stored in the billing information management database means. When the registration is received and the payment data is received via the network, the business section corresponding database means is searched using the business code included in the payment data as a search key. Then, one or a plurality of the corresponding department identification information is extracted, recorded in the corresponding department extraction means in association with the operation code and the payment amount information, and recorded in the accounting processing means by the corresponding department extraction means. One or more of the department identification information that has the same department identification information, and a combination of one or more sets of the billing information that the total amount of the billing amount matches or approximates the amount of the payment amount information The billing information management database means is searched and extracted, and the reconciliation processing of the set of billing information is executed. Of the combinations of the set of billing information, the reconciliation processing by the accounting processing unit failed. The processing-impossible set is recorded and displayed on the processing-impossible display means.
[0033]
According to such a method as well, it is possible to perform the reconciliation work on the amount paid from the payment source for each section corresponding to the operation code, thereby improving the efficiency of the reconciliation work.
[0034]
BEST MODE FOR CARRYING OUT THE INVENTION
(A) Embodiment
Hereinafter, embodiments of a payment processing system and method according to the present invention will be described.
[0035]
(A-1) Configuration of the embodiment
FIG. 1 shows an overall configuration example of a communication system 10 according to the present embodiment.
[0036]
In FIG. 1, the communication system 10 includes an external network 11, a payment system 12, a bank system 13, and a billing system 14.
[0037]
Of these, the external network 11 may be the Internet, or may be a closed network such as a dedicated line transmission network. In the configuration of the present embodiment, communication via the external network 11 is performed via the bank system 13.
[0038]
That is, the payment system 12 and the bank system 13 communicate, and the bank system 13 and the billing system 14 communicate according to the communication. Therefore, in the present embodiment, basically, the paying system 12 and the billing system 14 do not directly communicate with each other.
[0039]
The paying system 12 is used by the paying user (individual user U1 or corporate user E1), the billing system 14 is used by the company E2, and the bank system 13 is operated by the bank K1. The company E2 is a side that requests money, and the paying user U1 and the like (the paying user also includes the corporate user E1, but the case where the paying user is an individual user will be described below as an example). It is the side that pays money on demand.
[0040]
In the case of payment for the purchase price of goods or services, documents and data such as invoices are sent from the company E2 to the paying user U1, but the premium collector of the insurance contract and the like collectively contact the individual user U1. In such a case, the insurance company and the insurance company handle the information on the insurance contract and the insurance company, and the insurance company creates claim data (that is, payment schedule data) based on the information. Insurance collectors voluntarily pay the amount collected by themselves to an insurance company account.
[0041]
Normally, a request from the company E2 to the individual user U1 or the like can be made collectively under the name of the company E2. Individual departments, such as, are usually the substantive bodies of the claim. For example, when the company E2 is an insurance company, and a section (such as a section) in charge of a premium collector or the like is provided for each area in each region, one paying user U1 is operated by one specific section. Be in charge. In this case, the individual payer user U1 and the company E2 have a one-to-one correspondence. Further, for example, when an insurance company handles various insurances such as car insurance, ship insurance, and cargo insurance, and a separate section is provided for each insurance, a plurality of insurances are provided for one individual user U1. The department is in charge, and the insurance premium for the individual user U1 is also charged from the automobile insurance section B1, the insurance premium for the ship insurance from the ship section B2, and the insurance premium for the cargo insurance from the cargo section B3. As such, multiple departments may be in charge.
[0042]
Various methods can be used as a method of transmitting the contents of the billing information (such as the billing amount) from the billing company E2 or each section therein to the paying user U1. For example, mail or the like may be used, or electronic mail (using a network other than the external network 11) may be used. Also, as described above, there is a case where the individual user U1 voluntarily pays without sending a bill or the like. In addition, it is not always necessary to individually transfer claims for insurance premiums and rental apartment rentals that are paid periodically.
[0043]
In addition, the billing system 14 has a function of increasing the efficiency of processing such as billing and erasing individual bills in a computer network including a personal computer (see FIG. 2). The billing system 14 is indispensable in the configuration of the present embodiment.
[0044]
On the other hand, the payment system 12 can be omitted because it only has a function of paying money to a predetermined account provided in the bank system 13. If the payment-side system 12 is omitted, the payment-side individual user U1 or the like can make a payment using an ATM (Automatic Teller Machine) terminal installed at a store or the like of the bank K1.
[0045]
When the payment system 12 is used, the transfer data RD1 supplied from the payment system 12 is supplied to the bank system 13, and a process corresponding to the transfer data RD1 is performed in the bank system 13, and as a result of the processing, The transfer data RD2 corresponding to the transfer data RD1 is supplied from the bank system 14 to the billing system 14. The transfer data RD2 is supplied by a reporting service described below provided by the bank K1 to the company E2.
[0046]
Note that the transfer data RD1 and RD2 may be encrypted as necessary to enhance security.
[0047]
The transfer data RD1 and RD2 may be data having basically the same contents. The transfer data RD2 (or RD1) includes, for example, as shown in FIG. 4, information such as an operation code F1, a transfer requester name F2, an amount F3, and a transfer date F4.
[0048]
The operation code F1 is an identifier for identifying a payment source (payment side user). There may be various functions for the business code, but at least a function (payer user identification function) for identifying each payer user (for example, individual user U1) in the billing company E2. Have. If necessary, a billing side identification function (department identification function) for identifying a billing side, which will be described later, can be provided in the handling code.
[0049]
As the handling code, for example, a sequence of numbers of about 10 digits (in addition to numerical values, symbols, other character strings, and combinations thereof) may be used. When focusing only on the paying user identification function of the business code, information such as the address, name, and telephone number of the paying user can be used as the business code. In addition, by adding a series of numerical values or symbols before (or after) the character string of the transfer requester name (name of the paying user), it is possible to acquire the transfer requester as a part of the transfer requester name.
[0050]
For example, the value of the operation code F1 can be notified in advance to the user on the payment side when the contents of the bill are transmitted by the mail or electronic mail.
[0051]
The business code F1 may be input by the user on the payment side at the time of payment. However, in the case of using the technique of Patent Document 1, for example, instead of inputting the business code, identification of the payee account is performed. The handling code can be included in the information, and the operation burden on the paying user can be reduced.
[0052]
In other words, the transfer-only account that is different for each paying-side user is associated, and if the correspondence between the paying-side user and each transfer-only account is managed by the billing system 14, the transferred transfer-only account is specified. It is also possible to specify the paying user only by the above.
[0053]
In this case, when a payment (hereinafter also referred to as “transfer”) is made to the transfer-only account in Patent Document 1, the account number of the transfer-only account (in this case, this account number also has a function as the operation code F1). ) Is notified from the bank system 13 to the billing system 14. At this time, the money transferred is concentrated on a specific account opened by the company E2 at the bank K1, which is associated with the transfer-only account.
[0054]
As described above, the handling code F1 is an identifier having a payer user identification function. However, in actuality, as long as the payer user can be specified, it is determined which transfer corresponds to the transfer (the cause of the transfer). In many cases, it is also possible to specify the contents (hereinafter, referred to as the cause of payment or the cause of transfer) for specifying the changed transaction or the like. However, if necessary, information for identifying the cause of the transfer may be input in addition to the operation code in order to clearly indicate the cause of the transfer of the paying user.
[0055]
The transfer requester name F2 is the name and the like of the transfer requester (that is, the paying user), and is input when the paying user makes a transfer (payment). Since the payer user can be uniquely identified by the handling code F1, it is possible to adopt a system configuration in which the input of the transfer requester name F2 can be omitted. In order to be able to detect an input error or the like of the code F1, it is preferable to also input the transfer requester name F2.
[0056]
The amount F3 is information indicating the amount of money transferred by the paying user to a predetermined account (for example, the transfer-only account). This value is generated, for example, by subtracting the transfer fee according to the function in the bank system 13.
[0057]
The transfer date F4 is information indicating the date on which the transfer was made.
[0058]
In addition, various information may be included in the transfer data RD2 (or RD1) if necessary. For example, a representative department store code, a bank code, a bank branch code, an account number, an account, and the like may be included.
[0059]
When the ATM terminal or the like is used in place of the payment system 12, the contents of the transfer data RD1 are transferred from the ATM terminal or the like to the bank system in accordance with the operation performed by the payment user on the ATM terminal. 13 will be supplied.
[0060]
The information included in the transfer data RD2 is determined by a predetermined format defined by the bank.
[0061]
The report service provided by the bank K1 to the billing company E2 basically includes only supplying the transfer data RD2 to the billing system 14 of the company E2.
[0062]
An example of the internal configuration of the billing side system 14 will be described with reference to FIG.
[0063]
(A-1-1) Example of internal configuration of billing system
In FIG. 2, the billing side system 14 includes an electronic bulletin board system 9, an internal network 20, a communication processing device 21, a relay processing server (intermediate processing server) 22, a database server 23, and a business department correspondence database 24. , A billing information management database 25, a display device 29, and client terminals 27 and 28 provided for each department, which are connected via an internal network 20.
[0064]
The communication processing device 21 is a network device such as a router for connecting the internal network 20 and the external network 11. The internal network 20 may be, for example, a TCP / IP network.
[0065]
The relay processing server 22 performs an appropriate process of clearing billing information (scheduled payment data) recorded in the billing information management database 25 based on information on the transfer notified from the bank system 13 or the like. Processing such as giving an instruction regarding the content of the bulletin board to be provided is executed. If necessary, this relay processing server 22 can also perform the rearrangement processing of each information (F1, F2, etc.) in the transfer data RD2 shown in FIG. The order of the information in the transfer data RD2 is often different for each bank (one of which is K1), but when the valid order is one in the billing system 14, this sorting process causes The order of the information in the incoming transfer data RD2 can be rearranged so as to be unified into a valid order in the billing system 14.
[0066]
The electronic bulletin board system 9 is a one-to-many message exchange system. The user (M2, M1, etc.) who has viewed the message can also proceed with message exchange and perform collaborative work by writing his / her own message for the message on the bulletin board. There are various methods for realizing such electronic bulletin board functions on a computer network. For example, an electronic bulletin board can be configured using net news using the NNTP protocol, but when the internal network 20 is a TCP / IP network, it is convenient to use a Web server mechanism.
[0067]
In an electronic bulletin board system using a Web server mechanism, a form is basically used when a user describes a message. The form is a collection of components (fields) for collecting information written by the user on the Web server side. Therefore, based on the information collected from the fields, a new Web page (bulletin board) is used by using a CGI program or the like. ), Many users can know the content of the message of the user by browsing the Web page.
[0068]
If the CGI program is provided with an access control function (for example, a user authentication function), only a user who has obtained a positive authentication result can read the message. It can be used as one communication means or one-to-many (in this case, one-to-specified many) communication means.
[0069]
In the present embodiment, the relay processing server 22 first writes a message on a bulletin board provided by the electronic bulletin board system 9, requests a confirmation of billing information and transfer data, and requests a manual clearing.
[0070]
In the case of an electronic bulletin board provided with an access control function for permitting access only to the section to which the user belongs, the person in charge of reconciliation (eg, M1) who is an employee of each section accesses the bulletin board to access his / her department. Can be confirmed.
[0071]
The database server 23 retrieves and reads various data recorded in the operating department correspondence database 24 and the billing information management database 25, and provides data for processing in the relay processing server 22. Execute the management process.
[0072]
Generally, a database has a type such as a net type or a hierarchical type according to its logical data model (DBMS type), and the present invention is applicable to a net type or a hierarchical type database. It is assumed that the form is a relational database. Therefore, the operating department correspondence database 24 is a relational database composed of one or a plurality of relational tables.
[0073]
The operating department correspondence database 24 has, for example, a correspondence table TB1 as shown in FIG. 5 (A) or (B). In FIG. 5A, the correspondence table TB1 on the handling department correspondence database 24 includes at least a handling code, a payer name (payer user name), and department identification information corresponding to each handling code. ing. The operation code is associated with the section identification information, and when the operation code is determined, the corresponding section identification information is specified. The value of the department identification information corresponding to the value of one operation code may be one or plural. In the example of FIG. 5A, one section identification information value (eg, DD1) corresponds to one operation code value (eg, CD1), and there is a one-to-one correspondence. In the example (B), a plurality of department identification information values (for example, DD1 and DD2) correspond to one operation code value (for example, CD1), and there is a one-to-many correspondence. Of course, one-to-one correspondence and one-to-many correspondence may be mixed in the same table.
[0074]
Whether the correspondence is one-to-one or one-to-many is determined according to the function of the business code and the details of the claim. In the case where the transaction code has only the paying-side user identification function described above, a one-to-many correspondence is established if a request is made to the same paying-side user from a plurality of departments. If the business code has a department identification function together with a payer user identification function, one department will make a one-to-one correspondence if one billing user is not simultaneously charged with one billing user. If there is one to many.
[0075]
When a department identification function is provided, the corresponding department identification information can be included in the handling code itself, so that the handling department correspondence database 24 shown in FIG. 5A or 5B is omitted. Is also possible. For example, in FIG. 5B, by using a handling code such as “DD1DD2CD1” for the paying user name “Taro Nichido”, the handling code is associated with the department identification information “DD1” and “DD2”. Can be confirmed from the operating code itself. In the following, it is assumed that the transaction code has only the payer user identification function and does not have the department identification function.
[0076]
The display device 29 performs display in order for the person in charge of the supervising department to confirm the contents when performing the processing in the supervising department performing the collective management of the transfer at the head office or the like centering on the relay processing server 22. Communication device, and plays an important role in the present embodiment. However, the function of the apparatus itself is one of the client terminals similar to the client terminal 27 and the like for the electronic bulletin board system 9 as the server.
[0077]
If the content of the bulletin board provided by the electronic bulletin board system 9 to each client terminal (including the display device 29) is changed or added by the person in charge of the general division operating the display device 29, the other client terminals are changed. (For example, 28) accesses the electronic bulletin board system 9 to browse the bulletin board after the change and after the addition, and the employee (for example, M2) operating the person in charge M0 and the client terminal (for example, 28). Can exchange messages.
[0078]
Since the employees M1 and M2 belong to the departments in charge of the paying user, the departments in charge of the paying user can execute the collation processing of the transfer money in cooperation with the supervising department by such message exchange. It becomes possible.
[0079]
It should be noted that the communication processing device 21, the relay processing server 22, the database server 23, the operating department correspondence database 24, the billing information management database 25, and the display device 29 are not provided separately, but are provided in one server or host computer. May be integrated within.
[0080]
The above-described relay processing server 22 receives the transfer money data RD2 (see FIG. 4, various data related to the transfer such as the transfer person, the transfer amount, and the transfer date including the operation code) from the bank processing system 13 via the communication processing device 21. At this point, each billing information in the billing (scheduled payment) content table TB2 recorded in the billing information management database 25 shown in FIG. 6 is acquired via the database server 23, and it is confirmed whether or not there has been a transfer. For the billing information that has been transferred, a clearing process is performed.
[0081]
FIG. 6 shows the contents of each billing data (billing information) registered from each department in the company E2. A billing code (L1) for uniquely specifying each billing item, department identification information on the department that caused the bill, a billing (scheduled payment) amount, a scheduled payment date, a paying user name, and a priority Is recorded for each billing information. Here, the handling code is not an essential item, but if the handling code is recorded as a part of the billing information, for example, in the billing (payment expected) content table TB2 in the billing information management database 25, the business handling code may be used. The handling department correspondence database 24 becomes unnecessary. In the following, a description will be given on the assumption that no business code is recorded in the billing (scheduled payment) content table TB2, and relevant department identification information is extracted using the business department corresponding database 24.
[0082]
The section identification information is for uniquely designating a substantive claim base, such as a section in the company E2 (a section will be mainly described below by way of example). In FIGS. 5A, 5B, and 6, the names of the sections such as the automobile section and the ship section and the corresponding symbols are described in combination in parentheses. Alternatively, the description may be made using numerical values, symbols, other character strings, and combinations thereof, or may be made using only numerical values or only symbols.
[0083]
As long as the business code is not included, there is no primary key for uniquely specifying the billing information (that is, the row) in the billing content table TB2 with only the data items (excluding the business code) shown in FIG. Therefore, it is desirable to provide a new data item that can constitute a primary key (L1 to L7, etc.) like the billing code in FIG.
[0084]
Note that a row is generally a horizontal row in a table. For example, in the table TB2 in FIG. 6, "L1, automobile section (DD1), 4000, 2003.2.25, Taro Nichido, The horizontal arrangement of "CD1,1" is one line. In the configuration of the present embodiment, a row is equal to billing information.
[0085]
The billing (payment-scheduled) amount is a data item indicating the amount (here, insurance premium) charged from each section to the corresponding paying-side user. Even if the claims are from the same section, the amount of the insurance premium differs for each paying user according to the contents of the contracted insurance. Also, the billing amount may be notified to the paying user by a bill or the like, but if the billing side knows it in advance, it is displayed as the expected deposit amount.
[0086]
For example, if the paying user name is “Taro Nichido” (the business code is CD1) and the paying user name is “4000 yen (L1), 5000 yen (L2), and 10,000 yen (L3)”, the amount charged from the automobile section is Is recorded. Then, the billing amount from the ship section is 3000 yen (L5), and there is no other billing data.
[0087]
In addition, the priority is a data indicating the degree of the degree to be preferentially selected as a remittance object when collating (transferring) with the transfer data in a bill to the same paying user. It is. The smaller the value, the higher the priority. In the case of FIG. 6, for example, it is shown that the priority is higher in the order of the billing codes L1 and L2 for the paying user of the business code CD1, and that the L3 and L4 are out of priority.
[0088]
The priority means an item that is preferentially applied to the application amount to the transfer amount from the paying user. The priority is set to be high based on the degree of credibility related to the application processing, such as a high probability of payment on the scheduled payment date. Alternatively, higher priority may be set for claim information that is more important for the claimant such as an insurance company. The method of setting the priority is arbitrary. The priority value stored in the billing content table TB2 shown in FIG. 6 needs to be set before the transfer data RD2 is actually supplied.
[0089]
It should be noted that the reconciliation is a process in which the billing information and the transfer data are collated, and the fact that the payment (transfer) payment for each billing information has already been performed is reflected in the registered contents of the billing (payment expected) content table TB2. Say. As the transfer data, the transfer data table TB3 shown in FIG. 7 is used, and collation is performed between the transfer data table and the billing information (that is, the billing (payment expected) content table TB2). The generation of the transfer data table TB3 shown in FIG. 7 will be described later in detail.
[0090]
There are various methods for processing the rejection. For example, each line of the billing information (each line designated by a billing code L1 to L7) may be deleted (erased) from the billing (scheduled payment) content table TB2 to be applied to the billing. The value may be changed to 0 yen for the erasing.
[0091]
In the configuration of the present embodiment, the total amount, which is the sum of the amounts charged from all the sections to one paying user, is important. For example, in the case of a paying user whose sales code is CD1 and the paying user name is "Taro Nichido", there are two lines in the priority target, and one line (the line of the billing code L1) is charged from the automobile section. Since the amount is 4000 yen and the other line (the line of the billing code L2) is 5000 yen, the total amount is 9000 yen.
[0092]
Partial reconciliation is to partially erase billing information among a plurality of billing information for one payer user. In the case where the application is partially applied, even if the application is performed by deleting a line or applying the amount of billing to 0 yen, unapplied billing information remains. (Scheduled) When displaying the total amount of money, it is necessary to change the value.
[0093]
The value of the total amount may be calculated in advance and registered in a table (for example, TB2 or the like), but here, it is assumed that the value is calculated dynamically when it becomes necessary.
[0094]
The application performed inside the billing system 14 includes an application process (automatic application process) performed first when the relay processing server 22 receives the transfer data, and an employee in charge of each section (for example, M1) can be divided into a clearing process (corrected clearing process) performed after the billing information and the transfer data have been corrected (corrected) by operating the client terminals 27 and 28 and the like. Furthermore, an erasing process (manual erasing process) performed by an employee in charge of each section (for example, M1) by operating the client terminals 27 and 28 (hereinafter, mainly the case where the client terminal 27 is used is described as an example). There is.
[0095]
In the reconciliation performed in the present embodiment, first, automatic reconciliation is performed by the relay processing server 22. For the billing information that could not be reconciled by the automatic reconciliation, the billing information and transfer data (transfer data The table TB3) is corrected. Further, based on the corrected billing information and the transfer data, the relay processing server 22 performs the clearing process again. Regarding the billing information that could not be applied, the contents of the billing information (billing (scheduled payment) content table TB2) and the transfer data (transfer data table TB3) were corrected and corrected via the client terminal 27 or the like in each department. Later, the erasing process is performed again. For those items that cannot be applied yet, they are manually applied by the person in charge in each section.
[0096]
In general, manual clearing involving human judgment is more reliable, so the more frequently manual clearing is performed, the more reliable clearing can be performed as a whole. On the contrary, from the viewpoint, it is desirable to increase the frequency of automatic clearing.
[0097]
For example, predetermined billing information that cannot be cleared by the automatic clearing (billing information specified by L1 in FIG. 6) or transfer data (see RD2 in FIG. 4) in which the corresponding billing information cannot be searched occurs. When the clearing impossible condition occurs, the relay processing server 22 displays the billing information and the transfer data on the display device 29. Alternatively, if the department on the billing side can be specified by the department identification information, a notification to the effect that the application cannot be applied is sent to the department via the communication processing device 21. The person in charge of the department, who has obtained the information indicating that the application cannot be erased by the display on the display device or the notification from the relay processing server 22, sends the billing information to the relay processing server 22 from the client terminals 27 and 28 or the like. Or, request the provision of a transfer data correction acceptance screen.
[0098]
The correction process based on the correction request and the subsequent clearing process will be described later.
[0099]
When performing automatic clearing, the relay processing server 22 functions. In the automatic clearing, the relay processing server 22 that has received the transfer data RD2 instructs the database server 23 to automatically execute the clearing.
[0100]
Most billing information can be reconciled by this automatic reconciliation, but in fact, as described above, there can be billing information that cannot be reconciled with automatic reconciliation.
[0101]
The client terminals 27 and 28 shown in FIG. 2 are installed for each section (here, each section) in the company E2. For example, the client terminal 27 is installed in the automobile section B1, and the client terminal 28 is installed in the ship section B2. The number of client terminals is not limited to two, and one or more client terminals can be installed in each department, and the number is arbitrary.
[0102]
The client terminal 27 may be, for example, a personal computer having a network function, and the internal configuration is as shown in FIG. The client terminal 28 and the display device 29 also have the same internal configuration.
[0103]
When the mobile communication terminal has a client software such as a Web browser, the mobile communication terminal can be used as the client terminal 27 as it is.
[0104]
(A-1-2) Example of internal configuration of client terminal
3, the client terminal 27 includes a communication unit 30, a control unit 31, a display unit 32, an operation unit 33, and a storage unit 34.
[0105]
The communication section 30 is a section that functions to communicate with each component in the billing system 14 via the internal network 20. Although any constituent elements in the billing system 14 can be selected as a communication partner of the communication unit 30, communication with the electronic bulletin board system 9 is usually performed.
[0106]
If the content of the bulletin board provided by the electronic bulletin board system 9 to each client terminal (including the display device 29) is changed or added by the person in charge of the general division operating the display device 29, the other client terminals are changed. (For example, 28) accesses the electronic bulletin board system 9 to browse the bulletin board after the change and after the addition, and the employee (for example, M2) operating the person in charge M0 and the client terminal (for example, 28). Can exchange messages.
[0107]
The operation unit 33 is a part that is operated by the employee M1 to transmit an instruction to the client terminal 27, and includes, for example, a pointing device such as a mouse, a keyboard, and the like.
[0108]
The control unit 31 is a part corresponding to a CPU (central processing unit) of the client terminal 27 in terms of hardware, and a part corresponding to various programs such as an OS (operating system) and client software CL1 in terms of software.
[0109]
The client software CL1 is a program for the employee M1 to access the database server 23 or the like using the client terminal 27. Although a general-purpose client software such as a Web browser can be used as the client software CL1, a dedicated program may be used. Access from the client terminal 27 to the database server 23 may be performed via the electronic bulletin board system 9.
[0110]
The electronic bulletin board provided by the electronic bulletin board system 9 as a server can basically display the content (message) of the bulletin board on the display unit 32 only when the person in charge M1 accesses the client terminal 27. Although it is a pull-type communication means, it has a function of automatically and periodically accessing the client software CL1 so as to forcibly display the contents of the bulletin board even if the person in charge M1 does not try to access it. It can also be used as a type of communication means. At this time, it is easy to provide a function (message selection function) for selecting and displaying only messages addressed to M1 (including those addressed to the unspecified majority or the specified majority and including M1 in the destination). is there.
[0111]
The client software CL1 can also function as a client of each component described above in the billing system 14 with which the communication unit 30 communicates.
[0112]
The display unit 32 is a part corresponding to a display device that performs screen display according to functions such as the client software CL1. Since the DBMS of the database server 23 corresponds to the relation type (relation model), for example, when an inquiry is made using an SQL statement, the result of the inquiry is displayed on the display unit 32 on the screen. Since the employee M1 who operates the client terminal 27 belongs to the automobile section B1, for example, the value on the billing side is the automobile section (DD1), and there is a high possibility that an inquiry is made to search for an unapplied row or the like. In that case, if the line of the billing code L1 shown in FIG. 5 has not been erased yet, a list including the line can be displayed on the display unit 32 as the inquiry result.
[0113]
Such an inquiry may be performed in the process of the manual clearing, or may be performed independently of the manual clearing.
[0114]
The storage unit 34 is a storage resource including a RAM (random access memory), a hard disk, and the like. A program file such as the client software CL1 is also stored in the storage unit 34. When various screens including the list are displayed on the display unit 32, a view table corresponding to the list may be stored in the storage unit 34.
[0115]
The components of the billing system 14 other than the client terminals 27, 28, and 29 may basically have the same internal configuration as that shown in FIG. However, in this case, the parts corresponding to the display unit 32 and the operation unit 33 are mainly used for maintenance management and the like. When remote maintenance is performed, the display unit 32 and the operation unit 33 can be omitted.
[0116]
In addition, since these are servers, the storage unit 44 stores not the client software (for example, CL1) but the program files and the like for each server software (for example, a server program mainly composed of DBMS). become.
[0117]
Hereinafter, the operation of the present embodiment having the above configuration will be described.
[0118]
(A-2) Operation of the embodiment
The operation of registering the contents of the billing (payment schedule) contents table TB2 from the client terminal 27 to the database server 23 is as follows.
[0119]
(A-2-1) Billing information registration operation
A person M1 belonging to the automobile section B1 among persons in charge of each section requests the electronic bulletin board system 9 from the client terminal 27 for an input screen for registering information of the billing (scheduled payment) contents table TB2. FIG. 8 shows an example of an input screen for inputting the contents of the billing (scheduled payment) contents table TB2. FIG. 8 includes columns for inputting an input date, inputting a name of a department to be input, department identification information, a scheduled payment date, a paying user name, and a scheduled payment amount. By pressing a registration button after inputting in each of the input fields, billing information reaches the electronic bulletin board system 9 via the communication unit 20 in the client terminal 27. For example, the CGI program Accesses the database server 23. Thereafter, the billing information is registered in the billing information management database 25 by the processing of the database server 23. Regarding the billing information that is generated periodically every month, for example, when the database server 23 receiving the request from the relay processing server 22 reaches a predetermined date based on the information registered in the billing information management database 25, The billing information is generated and registered in the billing information management database 25. In any case, such registration of the billing information needs to be performed before the payment user performs the transfer and the transfer data RD2 corresponding to the transfer arrives at the billing system 14.
[0120]
Of the billing information registered in this way, for example, the billing date of February 25, 2003, which is the scheduled payment date, is searched by the database server 23 and is listed (corresponding to the view table). 6 may be a billing (payment schedule) content table TB2.
[0121]
The billing information recorded in the billing information management database 25 is not only updated or read out by access from the client terminal 27 or the relay processing server 22, but also the electronic bulletin board system 9 from the client terminal 28 or the display device 29. It may be read or updated depending on the access via the interface.
[0122]
For example, the billing information specified by the billing code L1 of the billing information in the billing (payment schedule) content table TB2 is registered from the client terminal 27 by the person in charge M1 belonging to the automobile section B1. Further, the employees of each department (for example, M1) can also check the progress of the reconciliation with reference to the contents of the billing (scheduled payment) contents table TB2 as appropriate.
[0123]
Next, the flow from when the relay processing server 22 acquires the transfer data RD2 to when the remittance processing is performed will be described with reference to the flowchart of FIG. 9 and FIGS. 4 to 7 and FIGS. 10 to 13. I do. Here, description will be made assuming that the operating department correspondence table TB1 shown in FIG. 5A or 5B exists.
[0124]
(A-2-2) Operation during reconciliation processing
In order to execute the clearing process, the transfer data table TB3 needs to be generated as a prerequisite. The transfer data RD2 registered in the transfer data table TB3 includes, as shown in FIG. 4, an operation code, a transfer requester name, an amount, and a transfer date. As described above, it is possible to use information including a transfer requester name and a temporary account number as the business handling code.
[0125]
When the relay processing server 22 acquires such transfer data RD2 (Step S901 in FIG. 9), the transfer data RD2 is taken over by the database server 23, and the database server 23 stores the transfer data RD2 in a predetermined storage unit. This storage unit may be logically a transfer data table TB3 as shown in FIG. Each time one transfer data RD2 is stored, a row of the transfer data table TB3 is added one by one.
[0126]
When generating the transfer data table TB3, the database server 23 refers to the operating department correspondence table TB1 (FIG. 5) stored in the operating department correspondence database 24 and operates the transaction code included in the transfer data RD2. Is used as a search key, the section identification information corresponding to the business code is extracted (step S903 in FIG. 9), and recorded in the transfer data table TB3 in association with the information such as the business code and the transfer amount. In the example of FIG. 7, in the row (H1) of CD1, Taro Nichido, and 8700, "automobile section (DD1)" and "ship section (DD2)" are recorded in association with each other as section identification information. Similarly, in the row (H2) of CD2, Takao Urano, and 7000, "automobile section (DD1)" and "automobile liability section (DD3)" are recorded in association with each other as section identification information. According to the table TB3 generated in this way, even if the operation code does not have the department identification function as described above, the department of the billing source can be identified only by the contents of the table TB3. It becomes.
[0127]
Next, the relay processing server 22 compares the content of the transfer data table TB3 with the content of the billing (scheduled payment) content table TB2, and performs an application process (automatic application process). Even during the execution of the clearing process, a new row may be added to the transfer data table TB3 whenever new transfer data RD2 arrives.
[0128]
In the automatic clearing process, first, the relay processing server 22 has the same department identification as the department identification information (including the name of the department corresponding to the department identification information) for the transfer data in the row H1 in FIG. A set of billing information having information and meeting predetermined conditions (for example, those set as extraction conditions, such as those for which the scheduled payment date falls within a certain range) is extracted, and the billing information shown in FIG. A (tentative) content table TB2 is generated and stored at a predetermined location in the billing information management database 25. Then, a combination of the sets of the billing information that matches or approximates the transfer amount of the transfer data is extracted from among them. As claim information having “Automobile Section (DD1)” and “Ship Section (DD2)” corresponding to the section identification information in row H1 in FIG. 7, six claims L1 to L6 from the claim (scheduled payment) content table TB2 are provided. Information is extracted (step S905 in FIG. 9). The relay processing server 22 checks whether there is billing information in which a priority value is set (step S907 in FIG. 9), and a flag of priority "1" is set in the line L1. Is confirmed (YES in step S907 in FIG. 9). Thereafter, the relay processing server 22 checks whether the amount of money in the line L1 matches the amount of money in H1 (step S913 in FIG. 9). In this case, since the amounts do not match, the relay processing server 22 checks which of the amounts of the line L1 is larger than the amount of the line H1, and checks whether the charged amount of the line L1 is larger (FIG. 9). Step S915). If the billing amount is smaller, the relay processing server 22 proceeds to step S927 via the “NO” determination in step S919 in FIG. 9 and selects another billing information to be specified.
[0129]
Similarly, the relay processing server 22 checks whether there is any other billing information for which a priority value is set as a flag (step S907 in FIG. 9), and sets a priority flag of “2” in the line L2. Make sure that In this embodiment, since the priority flags are set from a plurality of departments in charge of the paying user corresponding to the business code, the same priority may be set in some cases, In that case, as appropriate (for example, by following the order in which the names, numerical values, symbols, etc. of the department identification information are arranged in ascending order), the order of confirmation of the claim information of the same priority is set before and after, This is compared with the amount in the transfer data table TB3.
[0130]
The relay processing server 22 specifies the line L2 to which the next priority “2” is assigned, and changes the billing (scheduled payment) amount of the line to the billing (scheduled payment) amount of the line L1 (hereinafter, billing amount). ). As a result, while the transfer amount of the transfer data H1 is 8700 yen, it is confirmed that the sum of the charged amounts of the lines L1 and L2 is 9000 yen. The relay processing server 22 combines the line of L1 with other plural pieces of billing information, and checks whether the total amount is equal to 8700 yen or a more approximate total amount is obtained at 8700 yen or more. At this time, if there is billing information with a priority flag set in the lines L2 to L6, the amount of the billing information is prioritized and added to the amount of the line L1. Thus, as a result of performing a check by combining a plurality of billing information, it is confirmed that the total amount of 9000 yen of each line of L1 and L2 is most approximated by the value of the transfer amount of H1 of 8700 yen or more. Further, the relay processing server 22 uses the billing information of L2 on which the flag of the next priority “2” is set, and in combination with billing information other than the billing information of L1, the total amount is 9000 yen. Check if there is something more similar with the same amount or less than 9000 yen. Further, the billing information without the priority flag is specified one by one or in combination (step S913 in FIG. 9) and compared with the amount of the transfer data (step S913 in FIG. 9).
[0131]
In this way, the relay processing server 22 determines the total amount and the transfer amount of the transfer data for all the combinations of the request information from L1 to L6 because no combination of the request information corresponding to 8700 yen recorded in the transfer data is found. A comparison is made (step S921 in FIG. 9), and as a result, it is confirmed that the sum of the charged amounts of L1 and L2 is 9,000 yen or more, which is more than 8,700 yen of the transfer data H1, (step S925 in FIG. 9).
[0132]
It should be noted that it is convenient to set a processing procedure in advance so that the difference between the transfer amount of the transfer data and the charge amount by the combination of the charge information and the charge amount is minimized so that the combination can be held as efficiently as possible. . For example, each billing information is individually (one by one) collated with the transfer data to execute the clearing process. At this time, collation is performed sequentially from the billing information with the priority Bragg. Those that can be applied alone are excluded from the target of subsequent application processing. By setting such a processing procedure in advance and the relay processing server 22 performing the clearing processing, the number of combinations can be significantly reduced.
[0133]
Further, the relay processing server 22 checks whether or not the difference between the total charge amount of 9000 yen and the transfer data H1 of 8700 yen is within a certain range (not shown). For example, here, it is checked whether it is within the range of 300 yen. Here, confirmation of whether or not the amount is within a certain range means, for example, that an amount that needs to be paid to a financial institution as a transfer fee is determined in advance as an amount for setting a range, and whether or not the amount is within the range of the amount is determined. It means to confirm. The amount for setting the range is stored in a predetermined storage area in the relay processing server 22 in advance, for example. When the relay processing server 22 confirms that the difference between 8700 yen and 9000 yen does not exceed 300 yen, it is possible to determine that the amount of the billing information and the amount of the transfer data may be regarded as collated. That is, by setting such a range, it is possible to obtain Merckmar as to whether or not it can be considered that the amount of the billing information and the amount of the transfer data can be regarded as collated. If there is only a combination that causes a difference in the amount of money exceeding the set range, the transfer data is processed (cannot be processed) as being unrecognizable because it could not be collated.
[0134]
In this way, the relay processing server 22 collates the billing information of L1 and L2 with the transfer data H1, and performs a clearing process on both (step S929 in FIG. 9).
[0135]
In the above reconciliation process, confirm that the difference between the transfer amount of the transfer data and the charge amount of the billing information, which is caused by the transfer fee paid to the bank, etc., is minimum and within a certain range. The reimbursement process was performed as a result, but instead, a predetermined expected transfer amount was added to the transfer amount included in the transfer data, and the amount and the charge amount of the billing information (according to a combination of the set of the billing information). (Including the total amount) to determine whether they match. In this case, as shown in FIG. 10, for each operation code included in each transfer data, a transfer fee assumed in advance is recorded as a table and stored in a predetermined storage unit in the billing information management database 25. Keep it. Then, at the time when the transfer data is transmitted from the bank system 14, the relay processing server 22 instructs the database server 23 to add each amount (the transfer fee) in the table shown in FIG. ) Is added to correct the transfer data. A reconciliation process with the billing information is performed based on the corrected transfer data. In this case, the relay processing server 22 may omit the processing from step S915 to step S925 in FIG. 9 and directly proceed to step S927 if the amounts do not match in step S913.
[0136]
In this case, the transfer data table TB3 in FIG. 7 shows whether the financial institution (bank) of the transfer source transferred by the paying user corresponding to each business code is the same as the transaction bank in the table TB4 shown in FIG. The relay processing server 22 checks whether the transaction bank is the same and records the transaction bank if it is the same, and also records the name of the transfer-receiving financial institution (bank) of the company E2 that has received the transfer. Instruct 23. In this case, the database server 23 generates the transfer data table TB3 based on the instruction. Based on the generated transfer data table TB3, the relay processing server 22 specifies the transfer fee using the transfer amount included in the transfer data, adds the transfer fee to the transfer amount of the transfer data, corrects the transfer data, and corrects the transfer fee. The clearing process is performed using the transferred data. Also in the following embodiment, it is possible to execute the reconciliation process with the billing information using such corrected transfer data.
[0137]
Next, the relay processing server 22 performs a clearing process for the transfer data H2. At this time, as the billing information having the “Automobile Section (DD1)” and the “Compensation Division (DD3)” corresponding to the section identification information of the transfer data H2, the billing (scheduled payment) content table TB2 was previously cleared. Three pieces of billing information of L3 to L4 and L7 excluding L1 and L2 are extracted. The relay processing server 22 confirms that L4 has the same amount as H2 by the same processing as in the case of H1, and performs a clearing process on both.
[0138]
Next, the relay processing server 22 performs a clearing process on the transfer data H3. The line L6 is extracted from the billing (scheduled payment) content table TB2 as billing information having “ship section (DD2)” and “fire section (DD4)” corresponding to the section identification information of the transfer data H3. The relay processing server 22 compares the transfer amount of the transfer data H3 with the charge amount of the charge information of L6, and confirms that the charge amount is larger than the transfer amount, but the difference between the two exceeds 300 yen. Since there is no billing information corresponding to the above, all of them are processed as being inapplicable. As will be described later in the correction process, the billing information of L6 here is the one in which the person in charge of the section concerned incorrectly entered the amount when inputting the billing information and could not be collated. It is.
[0139]
As described above, the relay processing server 22 sequentially performs the reconciliation process for each transfer data, and performs the reconciliation process for the transfer data H5. The business code of H6 is CD6, and the department identification information corresponding to this business code is only "Compensation Division (DD3)". Then, the relay processing server 22 confirms that there is no billing information that matches the department identification information and whose amount is appropriate by the same processing as described above. Therefore, the relay processing server 22 processes the transfer data of H5 as being unable to erase. Further, the transfer data H6 can be compared with the billing information H7, and the relay processing server 22 performs a clearing process for any of them. In this way, the data that can be erased and the data that cannot be erased are generated as data as shown in FIGS. 11A and 11B, for example. Is stored in the storage unit.
[0140]
In the above-described reconciliation processing, it is assumed that the business code and the paying user name are not recorded in the billing (scheduled payment) content table TB2. The billing (scheduled payment) content table TB2 is recorded together with the department identification information, and all of the information is used for grouping the billing information. For each billing information having the same department identification information, the same business code, and the paying user name, , Can be applied to the transfer data. By doing so, the number of sets of billing information to be settled for each transfer data is reduced, so that the number of combinations of billing information is also reduced, and the efficiency of the settling process can be further improved.
[0141]
In addition, in the billing (scheduled payment) content table TB2 and the transfer data table TB3, those having the same scheduled payment date and the same transfer date are listed and the application process is performed. Etc.), a billing (scheduled payment) content table TB2 is generated, and similarly, a transfer data table TB3 is generated based on the transfer data transferred during a predetermined period, and erased between the two. May be performed. As a result, even when the scheduled transfer date and the actual transfer date are different, the application process can be performed. It is possible to prevent the inability to apply due to the wrong transfer date. In this case, the relay processing server 22 causes the database server 23 to extract the billing information or the transfer data that cannot be settled even after a predetermined period (for example, one week) has passed from the scheduled payment date or the transfer date. May transmit the billing information and the transfer data to each department via the electronic bulletin board system 9 to urge the user to confirm the cause.
[0142]
Also, in the reconciliation process, based on the priority flag, the billing information to be subjected to the reconciliation process was selected, but the priority flag is not always required, and if the priority flag is not set, The relay processing server 22 may select arbitrary billing information and sequentially execute the clearing process.
[0143]
Also, instead of the above-described method of combining the billing information, when the clearing process with the corresponding transfer data cannot be performed by the single (one) billing information, the clearing process is performed by combining as many billing information as possible. The relay processing server 22 may perform a clearing process so as to find possible transfer data. Depending on the company, even if the individual transfer data does not correspond strictly to each billing information, for example, it is sufficient if the transfer amount of the transfer data and the billing amount match as a total over a certain period of time There are places to process. In that case, it is also possible to perform the application processing in combination so that as much billing information as possible can be applied to the transfer data and the application processing.
[0144]
The result of the erasing process can be summarized, for example, as the erasing-processed portion shown in FIG. 11A and the erasing-impossible portion shown in FIG. 11B. Of the inapplicable payment processing, the lines L5 and L6 displayed on the left side are obtained in the billing (payment expected) content table TB2, but the transfer data is obtained (that is, the transfer was made). Means that it could not be done. Further, H3 and H5 displayed on the right side can specify the billing information from those listed in the billing (payment expected) content table TB2 even though the transfer data RD2 has been transmitted from the bank system. Means what did not.
[0145]
The cause of the inability to perform the reconciliation process is that the paying user collectively transfers the billing amount of each billing information and the relay processing server 22 cannot find a combination of billing information corresponding to the amount. It is conceivable that there was an error in the billing information or the transfer data, and the reason why the lines L5 and L6 on the left side could not be applied was that the transfer was not carried out by the paying user. The reason why the reconciliation processing of H3 and H5 could not be performed may be that the billing information has not been registered in the department in charge.
[0146]
In this embodiment, in order to apply the billing information in a certain group unit based on the department identification information corresponding to the business code included in the transfer data, for example, in the case of collation with only the transfer person name, etc. The possibility that the relay processing server 22 cannot find the combination of the billing information corresponding to the transfer data is lower than that of the case. However, if there is an error in the description of the transfer person name or the handling code, or the transfer data is incorrect due to an incorrect amount, the relay processing server 22 cannot execute the clearing process. Also, if the billing information is not registered in the billing information management database 25 before the transfer data RD2 is transmitted from the bank system 13 or at the latest at the time of performing the clearing process, the relay processing server 22 is similarly erased. Cannot be performed.
[0147]
It is difficult to confirm the cause of such data that cannot be erased by a headquarters department that performs collective management processing, such as the accounting department at the head office. Ultimately, it is necessary to check with each department in charge (such as the above-mentioned automobile insurance section B1) dealing with a transaction such as a transfer which caused a payment.
[0148]
In the following, the data which cannot be applied to the clearing process is accessed by each department and browsed through the electronic bulletin board system 9 so that if there is an error in the billing information or the transfer data, the clearing process by the relay processing server 22 is further performed. Correction processing when there is an error will be described.
[0149]
First, a person in charge (M1) of each section starts up, for example, the client terminal 27, inputs predetermined section identification information through an operation on the operation section 33, and sends an electronic command from the communication section 30 according to an instruction from the control section 31. It requests the bulletin board system 9 to provide a screen for requesting the application processing result data. In response to this, the electronic bulletin board system 9 transmits the screen for requesting the erasure processing result shown in FIG. 12 to the client terminal 27. The section manager M1 inputs the information for requesting the application processing result to the screen shown in FIG. 12, sends the information to the electronic bulletin board system 9 via the communication unit 30, and requests the display of the application processing result. This display request requests that the contents of the bulletin board be displayed on the display unit 32 of the display device 29. Although the display device 29 is a client terminal, the above-described client software CL1 mounted on the display device 29 has a function of automatically and periodically accessing the electronic bulletin board system 9. A message addressed to the device 29 (the contents of this message can be various, but in the case of giving details of the non-removal, as an example, a screen for the rejection process shown in FIG. Can be part of such a message) on a bulletin board, and the content of the message is automatically displayed on the display unit 32 of the display device 29.
[0150]
In generating this message, the electronic bulletin board system 9 instructs the database server 23 to extract the erase processing result from the billing information management database 25 in accordance with the content included in the erase processing result request data, and the extracted electronic bulletin board system 9 is extracted. The message is generated based on the result of the application processing. This message may also be transmitted from the electronic bulletin board system 9 to the client terminal 27 that is the transmission source of the display request and displayed on the display unit 32 of the client terminal 27.
[0151]
Of course, if the access is a normal access other than the display request, the electronic bulletin board system 9 transmits the message to only the client terminal 27 that has made the access.
[0152]
In the reconciliation processing result data acquisition request screen shown in FIG. 12, the input section name of the requesting section, the input section of the section identification information, the input period of the requested billing information (the period including the expected payment date), the target A column for selecting only the information of the own department, information of all departments, or information of the specified department as information, and a department for specifying a department when specifying a department and specifying billing information to be obtained. There is a column for inputting identification information, and the person in charge M1 of the requesting section inputs necessary items on the screen of FIG. 12 based on the content of the request.
[0153]
FIG. 12 shows an example in which the person in charge belongs to the ship section DD2 instead of the above-described car (insurance) section DD1 (in the case of the person in charge M2), and payment is scheduled to be made in February 2003 as billing information. Is specified. The screen displayed by the person in charge M2 belonging to the vessel section DD2 operating the client terminal 28 is the screen of FIG. Here, it is assumed that the billing information scheduled to be paid in February 2003 is all shown in FIG. In FIG. 12, since only the information of the ship section is requested, only the clearing processing result (impossible) data related to the ship section is displayed on the display section 32 as shown in FIG. Note that the data that has been subjected to the reconciliation processing may also be displayed, but the data for which the reconciliation processing has already been performed does not exist in the ship section.
[0154]
In addition, it is natural that each person in charge may access the electronic bulletin board system 9 in order to display billing information relating to billing from a section other than the section to which he or she belongs and the result of the reconciliation process. Will be described later. Unless rejected by the above-described access control function, each person in charge M1 to M3 can view the contents of all bulletin boards provided by the electronic bulletin board system 9 on their own client terminals (including the display device 29). A screen is displayed on the display unit 32 in accordance with the access. In other words, access to a bulletin board that is desired to be viewed only by some persons in charge is restricted by the access control function.
[0155]
The ship section clerk M2 who looks at the screen of FIG. 13 on the display unit 32 of the client terminal 28 checks the clearing processing result data, and the billing information of L5 and L6 and the transfer data H3 and H5 cannot be cleared. Recognize that Then, the user confirms past transaction data and the like, and finds that the billing (scheduled payment) amount entered in the billing information of L6 is not "6500 yen" but that the transfer data H3 is taken with Takeko Maki (management code CD3). It is a transaction, and although it should have been correctly input as 5500 yen, it is confirmed that the input was incorrect. Also, it is assumed that the handling code of the transfer person “Taro Nichido” in the transfer data H5 is correctly CD1, and that the payment code is erroneously written when the paying user performs the transfer processing. Then, after confirming the transaction material or confirming with Taro Nichido, it is confirmed that the handling code of the transfer data should have been correctly described as "CD1".
[0156]
In this way, the cause of the inability to perform the erase process is confirmed. The ship section clerk M2 presses the billing information correction input button 111 and the transfer data correction input button 112 of FIG. 13 from the operation unit 33 of the client terminal 28 so that the electronic bulletin board system 9 can accept the correction input. Ask to do so. By pressing each of the correction buttons 111 and 112, each data in FIG. 13 can be corrected, and the ship section manager M2 sets the expected payment amount of the billing information of L6 to 5500 yen and the operation code of the transfer data H5. A correction is input to “CD1” and a confirmation button (not shown) is pressed, and the correction information is transmitted from the client terminal 28 to the electronic bulletin board system 9. The electronic bulletin board system 9 takes over the received correction information to the database server 23, and the database server 23 updates the original data stored in the billing information management database 25 based on the correction content. Upon receiving the correction update by the billing information management database 25, the relay processing server 22 performs the reconciliation process (reconciliation after correction) again. This post-correction clearing process may be started in response to a request transmitted from the electronic bulletin board system 9 to the relay processing server 22. As a result of the correction, the billing information of L6 and the transfer data H3, and the billing information of L5 and the transfer data H5 are collated based on the procedure shown in FIG. In this way, the cause of the case where the erasing process cannot be performed is specified, and the erasing process is correctly performed.
[0157]
Next, a case where the car section DD1 requests the application processing result data will be described. In the same manner as described above, the person in charge M1 of the car section DD1 requests the electronic bulletin board system 9 to provide a screen for requesting the application processing result data, and this is shown in FIG. 12 sent from the electronic bulletin board system 9. On the same screen as above, "Information on the following designated section" was selected as the target billing information, and "Automobile section DD1,""Ship section DD2," and "Compensation section DD3" were entered in the designated section identification information field. I do. As a result, as shown in FIGS. 11A and 11B, the application processing result data of three sections (sections) including the automobile section DD1 is generated and acquired by the relay processing server 22. At this time, it is assumed that the correction processing by the Ship Division has not been implemented yet. For this reason, data related to the ship section is displayed as an unprocessable portion. Here, the person in charge M1 of the automobile section DD1 must not apply the set of billing information of L1 and L2 and the transfer data H1 that have been settled by the relay processing server 22. Suppose you confirm. For example, it is assumed that the transfer data H1 has been transferred based on another transaction of 8700 yen, for example, which was not registered due to forgetting to register. In this case, M1 inputs a check mark or the like in the “cancel application cancellation” column of the row of H1 in FIG. 11 displayed on the display unit 32, and presses the “cancel application result” button 123 from the operation unit 33 of the client terminal 27. Press. When the “correction result correction” button 123 is pressed on the row H 1 in FIG. 11, the information is transmitted to the relay processing server 22 via the electronic bulletin board system 9. The relay processing server 22 instructs the database server 23 to update the billing information of L1 and L2, which have been registered as the reconciliation process completed, and the transfer data H1 so that the reconciliation process is disabled. The contents of the billing information management database 25 are updated. FIG. 14 shows the updated result transmitted from the relay processing server 22 to the client terminal 27 and displayed on the display unit 32. In FIG. 14, the billing information of L1 and L2 is further added to L6 and L5, which were classified as being incapable of performing the application processing, and displayed as an inapplicable application processing. In addition, H1 is added to H3 and H5 as transfer data that cannot be cleared. In this case, the person in charge M1 of the automobile section also registers the billing information corresponding to the transfer data H1 from the client terminal 27. The database server 23 updates the registered billing information in the billing information management database 25, and upon receiving the registration result, the relay processing server 22 performs the reconciliation process again.
[0158]
The reconciliation processing by the relay processing server 22 may be performed by the relay processing server 22 when correction or registration is performed and information such as the modification is received, or the reconciliation processing may be periodically performed at a predetermined interval. May be implemented.
[0159]
Note that, at the time of accepting the above-described correction processing result data, the access control function of the electronic bulletin board system 9 or the relay processing server 22 may manage the presence or absence of the correction authority based on the department identification information. As a result, only the transfer data related to the operation code associated with the relevant department identification information to be corrected and the billing information having the relevant department identification information will be accepted from the relevant department, and the corrections from other departments will be accepted. There can be no processing.
[0160]
In this way, the electronic bulletin board system 9 provides a screen for a correction process regarding the data of the reconciliation process, accepts the content of the correction from each section, and performs the reconciliation process again with the corrected content. The information and the transfer data can be compared more accurately. Each department knows the actual situation of the transaction in detail, so if the reconciliation process could not be performed, check the cause and use this system efficiently so that the reconciliation process can be performed correctly You can do it. In addition, regarding the case where the relay processing server 22 has mistakenly processed as the reconciliation processing has been completed, each section manager can confirm the error and correct it so that the processing is correct.
[0161]
Further, if necessary, log information indicating the contents of the transfer data RD2 received by the relay processing server 22 may be accumulated. This log information is inspected by each employee (for example, M1) using a client terminal as appropriate, so that it is possible to confirm that there is no error in the application processing.
[0162]
In the case where the application cannot be performed by the automatic application processing and the correction application processing after correction, the relay processing server 22 requests the relevant section via the electronic bulletin board system 9 for manual application processing.
[0163]
In the case where the above-mentioned application-disabled condition occurs inside the billing system 14 and it is desired to perform manual application, it is necessary to notify the applicable department of the fact and request the manual application start. There is.
[0164]
There are various notification methods, for example, an electronic mail can be used. In this embodiment, as described above, an electronic bulletin board is mainly used.
[0165]
First, a case will be described in which the person in charge M1 acquires, from the electronic bulletin board system 9, billing information from the client terminal 27, for which the clearing process was not possible.
[0166]
In the present embodiment, the relay processing server 22 first describes the message MS1 on the bulletin board provided by the electronic bulletin board system 9, requests confirmation of billing information and transfer data, and requests manual clearing.
[0167]
The person in charge of each section such as the person in charge M1 can access the section to which he / she belongs only by the access control function described above, or by the above-described message selection function of selecting only a message addressed to him / her and displaying it on the display unit 32. , Only the message (for example, MS1) related to the own department can be confirmed.
[0168]
The request message MS1 for manual reconciliation and the like is a message for requesting the employees of the corresponding section to start manual reconciliation. The minimum information necessary for manual reconciliation is not only a request but also a request. Since it is more efficient to communicate at the same time, the content may differ depending on the non-removable condition that has occurred.
[0169]
For example, if the non-reconciliation condition is that the partial reconciliation described above has been executed in automatic reconciliation, the transfer data for the partial reconciliation as well as the content of the rows remaining after partial reconciliation It is desirable that the content of the RD2, the content of the line erased by partially applying, and the like are also included in the manual application start request message MS1.
[0170]
When the contents of the billing information subjected to the reconciliation processing are included, the destination of the manual reconciliation start request message MS1 (for example, a section or an employee permitted to access the manual reconciliation start request message MS1 by the access control function) ) Is determined according to the value of the department identification information of the row.
[0171]
The specific destination may be only the billing side (the person in charge of the department) of the row remaining after the partial application, or may include the billing side of the row partially applied by the partial application. If only the billing side of the partially erased line is addressed to the billing side, and the employee of the section of the address recognizes the need, the billing side of the partially erased line and the electronic bulletin board system can be used at any time. 9 can be used to keep in touch.
[0172]
For example, when only the line L1 of the lines L1 to L3 is partially erased in accordance with the supply of the transfer data RD2 corresponding to the transfer from the paying user of the handling code CD1, the remaining Only the ship section and the cargo section, which are the billing sides of the rows L2 and L3, may be the destinations of the manual clearing start request message MS1, but the automobile section which is the billing side of the cleared row L1 is also included in the destination. You may do so.
[0173]
If the value of the amount F3 (transfer amount) has received normal transfer data RD2 with no excess or deficiency, there is no need to partially apply, so it is anticipated that partial application has been performed by automatic application. It means that the possibility of hidden errors is not small. And in order to detect such unexpected errors efficiently, it may be necessary to work together with these divisions. The main role of the person in charge of the section receiving the manual application start request message MS1 caused by the partial application is to check for such unexpected errors.
[0174]
If necessary for the inspection, the staff in each section can exchange messages using the electronic bulletin board system 9.
[0175]
As a result of this inspection, for example, the handling code described in the transfer data RD2 was incorrect (the handling code having the same value as the handling code incorrectly described accidentally existed on the table TB1). That is, it may become clear that partial clearing has been performed by automatic clearing. In this case, the person in charge needs to cancel the partial application. This cancellation is executed as a part of the manual cancellation, and the contents of the billing content table TB1 may be further changed by the manual cancellation.
[0176]
If the name of the transfer client is described in the transfer data RD2, the person in charge can detect an input error of the handling code or the like based on the description.
[0177]
Conversely, there may be an error in the description of the transfer requester name, but due to the configuration of the present embodiment, the transfer requester name is not used for automatic application, so the description of the transfer requester name was incorrect. However, it does not trigger manual scrubbing. However, it is also possible to adopt a configuration in which the name of the transfer requester is used for automatic application, and in such a case, the above-mentioned application impossible condition is generated due to an error in the description of the transfer requester name. It can happen that manual scrubbing is started.
[0178]
Generally, it is considered that a transfer requester's name written in a natural language that is easy to understand has a lower frequency of occurrence of errors than a business code that is difficult to understand and that is less readable for humans.
[0179]
It is desirable that the history of a series of processing by automatic clearing or manual clearing be stored as the log information so that it can be tracked later.
[0180]
In addition, when the rejection impossible condition is that the transfer data RD2 which cannot search the corresponding line is supplied, the contents of the transfer data RD2 are included in the manual reconciliation start request message MS1, and If the application cannot be executed, only the contents of the remaining lines are included in the manual application start request message MS1.
[0181]
In the case where the transfer data RD2 for which the corresponding row cannot be searched is supplied, in the present embodiment in which the operation code does not have the department identification function, the billing side corresponding to the transfer data RD2 cannot be narrowed down. The destination of the start request message MS1 is all sections within the company E2 (sections that are unlikely to be billing parties can be excluded).
[0182]
Further, when the partial clearing is not executed, a manual clearing start request message MS1 is transmitted to the electronic bulletin board system 9 to the billing side of the remaining line as a destination, and the fact is described on the bulletin board. Will be.
[0183]
For example, if all of the lines L1 to L3 and L5 relating to the paying user of the business code CD1 remain without being partially erased, they are sent to the automobile section and the ship section, which are the billing sides, and the manual clearing is started. Although the request message MS1 is transmitted, the manual reconciliation start request message MS1 is not transmitted to the Automobile Liability Division or the International Division, which is not the requesting side of the lines L1 to L3 and L5.
[0184]
As a result, each person in charge only needs to read the manual application start request message MS1 that is strongly related to the section to which he / she belongs, and can proceed with the manual application efficiently.
[0185]
If the person in charge of the manual reconciliation recognizes the necessity, the information other than the information included in the manual reconciliation start request message MS1 is transmitted to each component (for example, Naturally, it can be collected from the billing content table TB1).
[0186]
When the person in charge who has received the manual application start request message MS1 from the relay processing server 22 can perform the application, the manual application procedure ends at that time, but the person in charge performs the application. If not, it is desirable to continue the manual clearing procedure.
[0187]
This continuation can be performed, for example, by a person (for example, M1) who has not been able to apply the manual application by writing a secondary manual application start request message MS2 on the electronic bulletin board.
[0188]
When the person in charge M1 can infer one or a plurality of persons (or one or more departments) who can perform manual reconciliation, the secondary manual reconciliation start request message MS2 sends However, if it cannot be guessed, it is addressed to all sections within the company E2 (that is, addressed to an unspecified majority).
[0189]
It should be noted that there is basically a pull-type communication means, and in order to compensate for the drawbacks of an electronic bulletin board lacking in real time, only a new manual clearing start request message MS1 (or MS2) is described on the electronic bulletin board. It is also desirable that the e-mail to be transmitted be automatically sent to the relevant person in the relevant department. The function of automatically creating and sending such an e-mail can be installed in the relay processing server 22, for example.
[0190]
It is desirable that the electronic mail be transmitted to a mobile communication terminal (for example, a mail terminal, a mobile phone, or a PHS terminal) carried by the person in charge (for example, M2). Thus, no matter where the person in charge M2 is located, it is possible to inform in real time that the manual clearing start request message MS2 or MS1 addressed to the person in charge M2 has been described on the electronic bulletin board provided by the electronic bulletin board system 9.
[0191]
Note that, for example, a pager or the like may be used instead of the e-mail.
[0192]
(A-3) Effects of the embodiment
According to the present embodiment, it is possible to improve the efficiency of the process of applying the rows (the rows L1 to F7) of the billing (scheduled payment) content table (TB2).
[0193]
In addition, in the present embodiment, the processing efficiency of partial erasure when various errors occur can be increased, and the flexibility is high.
[0194]
Further, in the present embodiment, since the manual wiping that complements the automatic wiping can be executed efficiently, it is not only efficient but also highly reliable of the wiping result.
[0195]
(B) Other embodiments
In the above embodiment, the contents of various tables are specifically shown in FIGS. 5 to 7 and the like, but the configuration (schema) as well as the values (instances) of each table are different from those shown. be able to.
[0196]
For example, it is generally considered that the number of banks to which the company E2 receives the reporting service is not only the bank K1 but also a plurality of banks. Therefore, each table includes, as a data item for identifying each bank, A bank code may be provided.
[0197]
When a bank code is provided, a view table including only rows corresponding to a specific bank (for example, K1) is generated according to the content of an inquiry from the client terminal, and a view table corresponding to the view table is generated. It is natural that the list can be displayed on the display unit 32 of the client terminal.
[0198]
Further, it is desirable to perform normalization (first to third normalization) on each table as appropriate to increase the efficiency of table management.
[0199]
Further, the number of rows in each table may be smaller or larger than that shown in the figure. However, for example, in the case of the table TB2, the number of rows is considered to be several times at most the number of paying users for the company E2. May exist.
[0200]
In the case of using the transfer-only account described in Patent Document 1, a plurality of transfer-only accounts may be assigned to one paying-side user, and may be transferred to different transfer-only accounts depending on the section on the billing side. In this case, it can be confirmed from which billing side the payment was made based on the account number of the transfer-only account to which the transfer was actually made.
[0201]
However, even in this case, it is not always necessary to make a one-to-one correspondence between the transfer-only account and the billing side (section). Therefore, where a plurality of billing parties are associated with one transfer-only account, it is possible to select a line to be applied by the partial application described above.
[0202]
In the above embodiment, B1 and B2 are different sections, but it is obvious that these sections may be divided into units other than sections. For example, offices (head office, branch, etc.) scattered in geographically distant places may be used as a unit.
[0203]
Further, in the above embodiment, B1 and B2 are basically equal. However, a supervising department such as an accounting department to which the person in charge M0 belongs, for example, performs the reconciliation process and the contents stored in each table. , The accounting department may be given a higher priority and broader access authority to have more comprehensive responsibilities than other departments and sections. For example, a person in charge of the accounting department may be allowed to access a data item that cannot be accessed by a person in charge of another department. For example, when a data item indicating the history of the past payment status related to a certain paying user is provided, only the accounting unit may access the data item.
[0204]
When there is a jurisdiction area for each business office inside the company E2, such as an insurance company, it is checked whether or not the data is input from a bank store in the jurisdiction area (automatic or manual check). ) Can be an effective means for the manual clearing.
[0205]
Furthermore, there is a possibility that some or all of the work performed by the person in charge by manual reconciliation in the above embodiment can be automatically executed.
[0206]
In the above embodiment, it is mainly assumed that the business code has only the payer user identification function. However, even if the business code has the billing user identification function in addition to the payment user identification function, Specifically, each process of the above embodiment can be applied as it is.
[0207]
Entering a business code that has a department identification function together with a payer user identification function can be regarded as an indication of the intention of the payer user to identify the billing side of the money transferred by himself. It is also desirable to make changes.
[0208]
However, even in this case, in order to perform automatic and manual clearing in consideration of the input error of the business code itself, it is necessary to execute a process that doubts the normality of the department identification function of the business code. Therefore, it is necessary to execute the same processing as in the case where the transaction code has only the payer user identification function.
[0209]
Furthermore, in the above-described embodiment, each department voluntarily confirms a case in which reconciliation processing is not possible, performs correction processing, and further performs reconciliation processing based on the correction. The transfer data and the billing information may be transmitted to the department to which the relay processing server 22 relates. For the set of billing information and transfer data that cannot be processed, the first clearing notification is sent to the department that corresponds to the department identification information, so that each department can correct billing information and transfer data. For example, if a clearing operation is performed or a manual clearing operation is performed, and the clearing process still cannot be performed, the clearing process may be retransmitted to all departments to prompt confirmation.
[0210]
By doing so, even if the department that was completely different due to incorrect input of the handling code etc. was associated, other departments should confirm that it was the transfer data of their own department Can be. At this time, the retransmission destination is not set to all the departments, but may be, for example, the same area (for example, each department in the same prefecture) or an organization having a similar function (for example, each headquarters in the head office). Retransmission may be performed to a plurality of departments having a specific relationship, such as departments, or departments at the same level in an organizational hierarchical relationship (organization levels such as branches and headquarters). In this case, attribute information (for example, affiliation area, function attribute, level of vertical relationship in the organization, etc.) of each department is recorded in the handling department correspondence tables in FIGS. 5A and 5B. Then, the information will be passed on to subsequent billing information and the like. Alternatively, the billing system 14 may separately hold a department attribute database, and may hold the department attributes in association with the department identification information.
[0211]
In the above description, the present invention is mainly realized by hardware, but the present invention can be realized by software.
[0212]
【The invention's effect】
As described above, according to the present invention, the set erasing process can be executed efficiently.
[Brief description of the drawings]
FIG. 1 is a schematic diagram illustrating an example of an overall configuration of a communication system according to an embodiment.
FIG. 2 is a schematic diagram showing an example of the internal configuration of a billing system used in the embodiment.
FIG. 3 is a schematic diagram illustrating an example of an internal configuration of a client terminal used in the embodiment.
FIG. 4 is a schematic diagram showing a configuration example of a format of transfer data used in the embodiment.
FIG. 5 is a schematic diagram showing a configuration example of a business department correspondence table used in the embodiment.
FIG. 6 is a schematic diagram showing a configuration example of a billing (scheduled payment) content table used in the embodiment.
FIG. 7 is a schematic diagram illustrating a configuration example of a transfer data table used in the embodiment.
FIG. 8 is a schematic diagram illustrating a configuration example of a billing content registration screen used in the embodiment.
FIG. 9 is a flowchart illustrating an operation example of the embodiment.
FIG. 10 is a schematic diagram illustrating a configuration example of a table used in the embodiment.
FIG. 11 is an operation explanatory diagram showing an operation example of the embodiment.
FIG. 12 is a schematic diagram illustrating a configuration example of a screen for requesting an erasing process result used in the embodiment.
FIG. 13 is an operation explanatory diagram showing an operation example of the embodiment.
FIG. 14 is an operation explanatory diagram showing an operation example of the embodiment.
[Explanation of symbols]
9 electronic bulletin board system, 10 communication system, 11 external network, 12 payment system, 13 bank system, 14 billing system, 20 internal network, 21 communication processing device, 22 relay processing server, Reference numeral 23: database server, 24: business department correspondence database, 25: billing information management database, 27, 28: client terminal, 29: display device, 30: communication unit, 31: control unit, 32: display unit, 33: operation Unit, 34: storage unit, RD1, RD2: transfer data, TB1 to TB4: table, MS1, MS2: manual clearing start request message.

Claims (10)

Receive and process payment data supplied through a predetermined network and including at least a service code for uniquely identifying a payment source that has made payment and payment amount information indicating the amount of money paid. A payment processing system,
Computer
A handling section corresponding database means for registering the handling code and section identification information for uniquely identifying each section,
A billing information management database means for associating billing amount information indicating a billing amount to the payer with the department identification information as one set and registering it as one or a plurality of billing information sets;
When the payment data is received via the network, the business department corresponding database means is searched using the business code included in the payment data as a search key, and one or more corresponding department identification information is extracted. And a corresponding section extracting means for recording in correspondence with the business code and the payment amount information;
One or more of the one or a plurality of units having the same section identification information as one or a plurality of the section identification information recorded by the corresponding section extraction unit, and wherein the total amount of the billed amount matches or approximates the amount of the paid-in amount information Accounting processing means for searching for and extracting the combination of sets of billing information from the billing information management database means, and executing a reconciliation process of the set of billing information;
A payment processing system for recording and displaying, among the combinations of the sets of billing information, unprocessable groups that could not be erased by the accounting processing by the accounting processing means, and displaying the same. . In the payment processing system of claim 1,
The unprocessable display means receives a display request for the unprocessable set from a predetermined department, and specifies the unprocessable set including at least the department identification information of the predetermined department that made the display request. Means for displaying
The payment processing system,
Further comprising a correction unit that allows correction of the content displayed by the unprocessable display unit,
The correction unit receives a correction for at least one of the department identification information and the billing amount information from the predetermined department,
The billing information management database means performs an updating process on at least one of the department identification information and the billing amount information based on the correction received by the correcting means,
The accounting processing means searches the billing information management database means after performing the update processing, and executes the reconciliation processing of the set of billing information,
A payment processing system characterized by the above-mentioned. In the payment processing system of claim 1,
The processing-impossible display means specifies the payment data including the operation code from which a combination of one or more sets of the billing information could not be extracted in the accounting processing means,
The payment processing system,
Further comprising a service code correction unit that allows correction of the service code included in the displayed payment data,
The corresponding section extraction means, the business code corrected by the business code correction means as a search key to extract a corresponding one or more of the department identification information anew,
The accounting processing means executes a reconciliation process of the set of billing information using the one or more department identification information extracted anew,
A payment processing system characterized by the above-mentioned. In the payment processing system of claim 1,
For the unprocessable group, a process incompatibility notifying unit that prompts an application for each section by transmitting a first application impossible notification to a section corresponding to the section identification information,
The processing inability notifying means checks whether or not the set notified by the first application inability notification has been applied, and sends the second set to the plurality of departments for the set which could not be applied. A payment processing system for transmitting a notice indicating that payment is impossible. The payment processing system according to any one of claims 1 to 4,
The accounting means,
A total value calculation unit that selects all or some of the combinations of the extracted sets of the billing information, and calculates a total value of the billing amounts indicated by the billing amount information for the selected set.
Comparison determination means for checking the magnitude relationship between the total value and the value indicated by the payment amount information in the payment data corresponding to the corresponding operation code;
A payment processing system comprising: In the payment processing system of claim 5,
The billing status management database means,
A priority setting unit that registers information indicating a priority in a set of the billing information set in advance,
The total value calculating means,
A payment processing system, wherein a set is selected in accordance with the priority such that the total value is equal to or greater than the value indicated by the payment amount information as a result of the inspection. The payment processing system according to claim 5 or 6,
The total value calculating means,
As a result of the inspection, a set is selected such that the total value is equal to or greater than the value indicated by the payment amount information, and the number of sets to be subjected to the clearing process is maximized, and the clearing process is executed according to the selection. A paid-in processing system comprising a selection number priority adaptive control unit for causing a selection. The payment processing system according to any one of claims 5 to 7,
The total value calculating means,
As a result of the inspection, a set is selected such that the total value is equal to or greater than the value indicated by the payment amount information, and the difference between the total value and the value indicated by the payment amount information is minimized. A payment processing system comprising a balance priority adaptive control unit for executing processing. The payment processing system according to claim 1, wherein
A financial institution system facing the payment processing system via the network associates a plurality of related accounts with a single payment receiving account, and uniquely identifies the related account using predetermined related account identification information. If you provide related account services,
The payment source is characterized in that the related account associated with the payment source is made to pay the money, and the related account identification information of the related account is provided with information on the handling code or the content of the transaction. Payment processing system. Receive and process payment data supplied via a predetermined network and including at least a service code for uniquely identifying a payment source that has made payment and payment amount information indicating the amount of money paid. A payment processing method,
Computer
The business code and the department identification information for uniquely identifying each department are registered in the business department corresponding database means in association with each other,
After associating the billing amount information indicating the amount of money to be paid to the payer with the department identification information as one set, registering one or more sets of billing information in a billing information management database means,
When the payment data is received via the network, the business section corresponding database means is searched using the business code included in the payment data as a search key, and one or more corresponding department identification information is extracted. And, in the corresponding section extracting means in association with the business code and the payment amount information,
The accounting processing means has the same department identification information as one or more of the department identification information recorded by the corresponding department extraction means, and the total amount of the billing amount matches or approximates the amount of the payment amount information. Searching the claim information management database means for a combination of one or a plurality of the claim information sets, extracting the set, and executing the set information clearing process;
A payout processing method characterized in that, among the combinations of the sets of the billing information, the unprocessable sets that could not be erased by the clearing process by the accounting processing means are recorded on a non-processable display means and displayed.

Images