JP2001319180A - Method and system for managing expense payment - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide managing method/system for automating expense payment. SOLUTION: It is confirmed that a request order common to a delivery slip, a delivered goods and a bill exists in a work request data table. Reception is registered in the work request data table and payment data is generated based on the bill where reception is registered by presuming that the delivery slip, the delivered goods and the bill, where the common request order exist, are received in accordance with this order. When the delivery slip, the delivered goods and the bill are not received in this order, or they are overlapped and received, that it information to a request destination that the received data is mistaken.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a method and system for managing payments of expenses for facilitating payment processing.

[0002]

2. Description of the Related Art In an ordering operation, an ordering process and a delivery process are performed. Particularly, in the delivery process, it is customary to accompany a delivery note and an invoice in addition to the delivered product.

[0003] It is therefore necessary to process these deliveries, invoices and invoices. In addition, if your deliverables, invoices and invoices are submitted at different times,
It is necessary to determine the relevance of these documents.

[0004] Such processing is conventionally performed exclusively by hand. Therefore, when the processing is congested, there is a high possibility that an error occurs.

[0005]

SUMMARY OF THE INVENTION Accordingly, it is an object of the present invention to provide a cost payment management method for automating cost payment and a cost payment management system using the same in view of the above problems. is there.

[0006] The cost payment management method and system according to the present invention that achieves the above object of the present invention includes a delivery note,
Confirm that there is a common request order in the work request data table for each of the delivered item and the invoice, and receive the invoice, delivered item, and invoice with the common requested order in accordance with these orders. Assuming that
A receipt is registered in the work request data table, and payment data is created based on the registered bill.

In a preferred embodiment, the delivery note,
Not received in the order of delivery and invoice, or
When each of them is received in duplicate, the request destination is notified that the received data is incorrect.

[0008] The features of the present invention will become more apparent from the embodiments described with reference to the following drawings.

[0009]

Embodiments of the present invention will be described below with reference to the drawings. In the drawings, the same or similar components are denoted by the same reference numerals or reference symbols.

FIG. 1 is a diagram for explaining an example of a system configuration to which a method for managing cost payment according to the present invention is applied.

The example shown in FIG. 1 is an example of a case where a business is requested to an external delegation office, for example, a case where an application agency is delegated to a patent office. An office 1 entrusted with delegation and an expense payment processing system 2 to which the invention of the requester is applied are connected through a network 3.

At this time, in consideration of security, it is preferable that the network 3 is not an open network such as the Internet but is connected to the processing system 2 in the WAN as a host and the office 1 as a client.

The office 1 prepares a delivery 10, a delivery note 11 and a bill 12 in response to the request of the requester, and transmits it to the processing system 2 through the network 3.

That is, assuming that the office 1 is a patent office, the deliverable 10 is an application document including a specification, a delivery note 1
1 is an invoice document for identifying the delivery 10 and a bill 12
Is a document for making a claim for the agency business in the office 1.

The delivery 10, delivery note 11, and bill 12 are all documents that can be digitized. Therefore, these documents can be transmitted from the office 1 to the processing system 2 as digitized data.

The processing system 2 receives the digitized data transmitted from the office 1 by the data transmission / reception means 20. The processing system 2 includes a computer system as a control unit and a database 21 in addition to the data transmission / reception unit 20.

The database 21 includes, as an embodiment, a delivery note storage area, a work request data storage area, a charge table storage area, a delivery type / page number storage area, a bill storage area, a payment data storage area, and an office. It has a bank account storage area and a bank master data storage area.

In FIG. 1, each step of the document data processing method of the present invention is realized by executing a predetermined program by the computer system. In FIG. 1, the processing in each step of the document data processing method of the present invention is shown in a block diagram as corresponding means.

Delivery note checking means 200, delivery note checking means 3
00 and each processing of the invoice confirmation means 400
This is shown in FIGS.

FIG. 2 is a flowchart showing the processing steps of the delivery note confirming means 200. The delivery note confirming means 200 determines whether the requested order described in the received delivery note 11 exists in the work request data (201).

FIG. 5 shows an example of the work request data stored in the work request data storage area, which is configured in a table. Request order numbers, office codes, requested office names, request dates, request type codes, and the like are recorded.

Therefore, in the process 201, it is determined whether or not the requested order number corresponding to the delivery note 11 exists by referring to the work request data storage area of the database 21. As a result, if the corresponding requested order number does not exist, it is an error, and the fact is automatically transmitted to the requested office 1 via the network 3 (20
7).

On the other hand, the delivery note 1 is stored in the work request data storage area.
If the requested order corresponding to 1 exists, it is next determined whether or not the delivery note 11 has already been received (20).
2). This is performed by referring to the work request table in the database 21. In the work request table, a flag is set in the delivery note reception column when the delivery note 11 is received, corresponding to the requested order. If the receipt has already been received by referring to the presence or absence of this flag, the delivery note is duplicated and an error occurs. In this case, the fact is automatically transmitted to the request destination office 1 via the network 3 (207). .

If the delivery note 11 has not yet been received, each data of the delivery note 11 is confirmed (203). FIG. 6 is an example of the delivery note 11. The mutual relationship between the type, type code, quantity, unit price and price is checked based on the digitized data (204).

Therefore, in the contents of the delivery note 11,
If there is an inconsistency in the mutual relationship, it is an error, and the fact is automatically notified to the requested office 1 via the network 3 (207). If there is no error, the contents of the delivery note data are registered in the delivery note storage area (205). Further, a receiving flag is set in the delivery note receiving column of the work request table in FIG. 5, and the processing in FIG. 2 ends (206).

Next, according to the flow of FIG.
The process performed when the message is received will be described. Delivery confirmation means 300
In, it is determined whether the corresponding requested order exists in the work request table shown in FIG. 5 (301).

As a result, if the corresponding requested order number does not exist, it is an error, and the fact is automatically transmitted to the requested office 1 via the network 3 (30).
8).

In the work request table, a flag is set in the delivery receipt column when the delivery 10 is received, corresponding to the requested order. If it has already been received by referring to the presence or absence of this flag, it is an error, so that
Is automatically transmitted to the request destination office 1 via (308).

Further, it is determined whether the delivery note 11 has already been received (302). If the delivery note 11 has already been received, it is determined whether or not the requested order number exists (303).

If the delivery note 11 has not yet been received, the delivery 10 has been sent prior to the delivery note 11,
This is also an error. Therefore, network 3
The error is automatically notified to the request destination office 1 via (3)
08). When it is determined that the delivery note 11 has already been received, each data of the delivery 11 is confirmed (304).

Here, it is determined whether or not there is an error item in the delivered item 10 (305). If there is no error, the delivered item data is registered. For example, information such as a name and the number of claims in the specification is registered (306). ). Further, a receiving flag is set in the delivered goods receiving column of the work request table in FIG. 5, and the processing in FIG. 3 ends (307).

In the process 305, if there is an error item in the delivered item 11, the error item is automatically transmitted to the requested office 1 via the network 3 (30).
8).

Next, the processing when the bill 12 is received will be described according to the bill processing flow shown in FIG. In the invoice confirmation means 400, the corresponding order is shown in FIG.
It is determined whether it exists in the work request table shown in (1) (401).

Therefore, in the above-mentioned process 401, it is determined whether or not the requested order number corresponding to the delivery 10 exists with reference to the work request table of FIG. As a result, if the corresponding requested order number does not exist, it is an error, and the fact is automatically transmitted to the requested office 1 via the network 3 (40).
7).

In the work request table, flags are set in the corresponding delivery note and delivery receipt columns when the delivery note 10 and delivery 11 are received, respectively, in accordance with the requested order.
Therefore, the presence or absence of these flags is referred to (402,
403). If it has already been received, it is an error due to duplication, and the fact is automatically transmitted to the requested office 1 via the network 3 (407).

Further, it is determined whether the bill 12 has already been received (404). If the bill 12 has already been received, it is an error, and the fact is automatically transmitted to the requested office 1 via the network 3 (408).

If the bill 12 has not been received yet, each data of the received bill is confirmed (405). Here, FIG. 7 is an example of a fee table stored in the database 21. Therefore, each data of the received bill 12 is confirmed with reference to the charge table.

It is determined whether there is an error item in the bill 12 (406). If there is no error, the bill data is registered (408). Further, a receipt flag is set in the bill receipt column of the work request table in FIG. 5, and the processing in FIG.
09).

On the other hand, if there is an error item in the process 406, the error item is automatically notified to the requested office 1 via the network 3 (407).

When the data of the received bill 12 is registered as described above, payment data of the cost is created.

FIG. 8 is a flowchart illustrating the procedure for creating such payment data. Payment data is created by the payment data creation means 500 for the invoice 12 whose receipt has been registered in the work request table (FIG. 5) (501).

The transfer destination bank code has already been registered in the office bank account data corresponding to the request destination office. Therefore, the transfer destination account described in the bill 12 and the registered account are confirmed (502).

In this confirmation, if the bank code / branch code is incorrect, an error item is automatically transmitted to the requested office 1 via the network 3 (505).

If the bank code / branch code is correct, the payment data is registered in a payment data table as shown in FIG. 9 (503). This completes the payment data creation, and the billed amount is used as the payment amount in the database 2.
It is registered in the first bill storage area (504).

Next, payment data transfer processing shown in FIG. 10 is performed by the bank transfer data creation means 600.
That is, the payment data created and registered according to the flow of FIG. 8 is converted into a bank transfer data format (601). The bank transfer data format may be different for each bank.

Next, the converted bank transfer data format is received by the transfer data receiving means 40 in the bank 4, and payment processing is performed. The bank 4 determines whether or not there is an error item for the contents requested to be transferred.

As a result, according to the error notification process from the bank shown in FIG.
1), and this is received by the bank transfer error handling means 700. If the error is caused by the data of the invoice 12, the bank transfer error handling means 700 cancels the payment data creation completion data registered in the invoice storage area (70).
2). Next, the error item is automatically transmitted to the requested office 1 via the network 3 (703).

Thus, the requested office 1 discards the incorrect bill, performs a new bill issuing process, and performs the above process again.

As described above, according to the present embodiment, the electronic data of the delivery item (10), the delivery note (11), and the bill (12) are mutually mechanically checked, and if there is an error, In this case, since the contents are automatically notified to the request destination office 1, the accuracy of payment data check is remarkably improved and the processing time can be greatly reduced.

Further, based on the information stored in the payment data creating means 500, business analysis data such as analysis statistics for each type of expense (payment item) and payment performance statistics for each payee can be easily created.

Although the present embodiment has been described as a system for managing payment of costs to a patent office, the present invention is not limited to this embodiment, but can be applied to a general system for managing payment of costs. It is something.

[0052]

As described above, according to the present invention, a series of processes from receipt of an invoice to account transfer to a target bank or the like is centrally and rapidly managed and processed for document data related to cost payment. An expense payment management system can be provided.

[Brief description of the drawings]

FIG. 1 is a diagram illustrating a system configuration to which an expense payment management method according to the present invention is applied.

FIG. 2 is a flowchart showing the processing steps of a delivery note confirmation means 200.

FIG. 3 is a flowchart illustrating a process when a delivery 10 is received.

FIG. 4 is a flowchart illustrating processing when a bill 12 is received.

FIG. 5 is a diagram illustrating an example of work request data.

FIG. 6 is a diagram illustrating an example of a delivery note.

FIG. 7 is an example of a fee table previously agreed with the office 1;

FIG. 8 is a flowchart illustrating a procedure for creating payment data.

FIG. 9 is a diagram showing an example of a payment data table field.

FIG. 10 is a diagram illustrating payment data transfer processing.

FIG. 11 is a diagram illustrating an error notification process from a bank.

[Explanation of symbols]

 REFERENCE SIGNS LIST 1 office 2 processing system 3 network 4 bank 40 transfer data receiving means 20 data transmitting and receiving means 21 database 200 delivery confirmation means 300 delivery confirmation means 400 bill confirmation means 500 payment data creation means 600 bank transfer data creation means 700 bank transfer Error handling means

──────────────────────────────────────────────────続 き Continued on the front page (51) Int.Cl. ⁷ Identification symbol FI Theme coat ゛ (Reference) G06F 17/60 332 G06F 17/60 332 428 428 (72) Inventor Shunichi Sato 1-Machiya, Arakawa-ku, Tokyo 38-16 F-term in Ryoin Co., Ltd. (Reference) 5B049 BB46 CC21 CC36 DD05 EE01 FF09 GG04 GG07 5B055 CB09 EE02 EE21 EE27 FA07 FB04

Claims (4)

[Claims] 1. Check that a common order for a delivery note, a delivered item, and an invoice exists in a work request data table, and check the delivery note, the delivered item, and the invoice for which the common requested order exists. Expense payment management, characterized in that a receipt is registered in the work request data table, and payment data is created based on the registered invoice, on the assumption that the receipt is received in accordance with these orders. Method. 2. The method according to claim 1, wherein when the receipt is not received in the order of the delivery note, the delivery and the bill, or when each of the receipts is received in duplicate, a notification is made to the request destination that the received data is incorrect. A method for managing payment of expenses. 3. A database having a work request data table, a receiving means for receiving a delivery note, a delivery, and a bill, and a delivery note, a delivery, and a claim received by the receiving means according to a predetermined program. Control means for judging the validity of the document by referring to the registered data in the work request data table, the control means comprising: Confirm that it exists in the table, and assuming that the delivery note, delivery item, and invoice where the common request order exists are received in accordance with these orders, the receipt is received in the work request data table. A cost payment management system comprising: registering; and controlling the receipt so as to generate payment data based on the registered invoice. 4. The apparatus according to claim 3, wherein the control unit determines whether the received data is erroneous when the receipt is not received in the order of the delivery note, the delivery, and the bill, or when each of them is received in duplicate. A cost payment management system, wherein