CN111402020A - Automatic account checking system for enterprise account receivable/payment - Google Patents

Abstract

An enterprise accounts receivable/accounts payable automatic reconciliation system includes a first reconciliation system established at a supplier, a second reconciliation system established at a customer, and a reconciliation system established at a third party; establishing and maintaining a basic file dictionary which can be acquired by a first reconciliation system and a second reconciliation system in a coordination system, and defining customer information, supplier information and product information; for the sale service of the first reconciliation system or the payment service of the second reconciliation system, the intelligent reconciliation can be realized with the assistance of the coordination system; the method establishes the message queue to assist the supplier and the client to complete the automatic registration of the related financial documents, and establishes the contrast relationship between the payable account verification and the return verification of the payable account of the client and the return verification of the receivable account of the supplier, so that the business activities of the two parties are clear; the data consistency and balance between the supplier and the client are ensured, economic disputes caused by poor accounts are avoided, and the burden of operators is reduced.

Description

Automatic account checking system for enterprise account receivable/payment

Technical Field

The application relates to the field of financial data processing, in particular to an automatic account checking system for receivable/payable accounts of an enterprise, which is used for automatically comparing and registering receivable/payable account business documents of a communication type enterprise.

Background

At present, the verification and sale of account receivable money of a circulation type enterprise mainly have the following modes:

1. verification against customer name number; 2. and (4) checking and selling the bill number.

What corresponds to accounts receivable is accounts payable, and what corresponds to the verification of accounts receivable is the verification of accounts payable, both operations occurring in the two associated units with close correlation. However, in the existing account system, both the supplier and the client (the payee and the payer) cannot realize online interaction; in the absence of effective online interaction, the prior art suffers from the following drawbacks: the checking and canceling of the payable account by the payer and the checking and canceling of the receipt account by the payee are different and are not known mutually, so that the confusion of accounts of both parties is caused and even economic disputes are caused.

Disclosure of Invention

The application aims to provide an automatic account checking system for the account receivable/paid by an enterprise, which is used for solving the problem of account checking and canceling caused by the fact that suppliers and customers cannot realize online interaction in the prior art.

In order to realize the task, the following technical scheme is adopted in the application:

an enterprise accounts receivable/accounts payable automated reconciliation system comprising a first reconciliation system established at a supplier, a second reconciliation system established at a customer, and a reconciliation system established at a third party;

a basic file dictionary which can be acquired by a first reconciliation system and a second reconciliation system is established and maintained in the coordination system, and comprises a basic file definition mapping table and a basic file data mapping table which are used for defining customer information, supplier information and product information; the basic file definition mapping table stores definitions and corresponding relations of basic data of a first account checking system and a second account checking system, wherein the basic data comprises customer information, product information and receipt information; the basic archive data mapping table stores data key values and corresponding relations of client identification numbers, product identification numbers and supplier identification numbers of a first account system and a second account system;

for the sales service of the first reconciliation system, firstly generating a sales order through the first reconciliation system, converting the sales order by using a basic archive definition mapping table, sending the converted sales order to the reconciliation system, regenerating the sales order by using the basic archive data mapping table by using the reconciliation system, inserting the sales order into a message queue, and waiting for reading by using the second reconciliation system; the second account checking system reads the corresponding sales order from the message queue and converts the sales order into a purchase order after being connected with the coordination system, and then the purchase order is converted and stored by utilizing the basic archive definition mapping table and the basic archive data mapping table;

for the payment service of the second account checking system, firstly, the second account checking system appoints an incoming bill to be paid, generates a bill through the incoming bill, then communicates with the coordination system, converts the bill by using a basic archive definition mapping table, sends the converted bill to the coordination system, regenerates the bill by using a basic archive data mapping table, inserts the bill into a message queue, and waits for the reading of the first account checking system; and the first reconciliation system is connected with the coordination system, reads the corresponding payment order from the message queue and converts the payment order into a receipt, and then converts and stores the receipt by utilizing the basic file definition mapping table and the basic file data mapping table.

Further, when the phenomenon that accounts receivable and accounts payable are inconsistent occurs in the first reconciliation system and the second reconciliation system, the electronic reconciliation function is realized through difference analysis, which comprises the following steps:

customizing a difference analysis function in a coordination system by user, wherein the function of the difference analysis function is to list a business document list corresponding to a parameter according to the parameter n, and the meaning of the parameter n is agreed to different operation or financial operation, including sale, delivery, payment and cash withdrawal;

when electronic reconciliation is carried out, the first reconciliation system and the second reconciliation system respectively call a difference analysis function, a sales business list/payment list of the first reconciliation system and a goods-in business list/money-back list of the second reconciliation system are obtained by correspondingly assigning the parameter n, a difference record is obtained by comparing the sales business list and the goods-in business list or comparing the payment list and the money-back list, the difference record is respectively sent to the first reconciliation system and the second reconciliation system, and correction is carried out after manual audit.

Further, the generating of the sales order through the first reconciliation system comprises:

the sales order comprises header information and corresponding data, and in-table information and corresponding data; wherein, the field corresponding to the header information and the field corresponding to the information in the table are contained in the basic data of the basic file definition mapping table; the fields corresponding to the header information of the form comprise a form identification number, a form date and a customer identification number, and the fields corresponding to the information in the form comprise a product identification number, a form quantity, a form unit price and a form amount; the data corresponding to the customer identification number, the product identification number, the number of the documents and the unit price of the documents are manually input, the data corresponding to the document identification number are automatically generated according to the input sequence of the documents, the data corresponding to the document date are the storage date of the documents, and the data corresponding to the document amount are automatically generated through calculation.

Further, the process of generating the sales order by the first reconciliation system and converting the sales order by using the base archive definition mapping table comprises the following steps:

the first reconciliation system inquires the basic archive definition mapping table through communication with the coordination system, and converts the header information and the information in the table of the sales order into a field corresponding to the first reconciliation system recorded in the basic archive definition mapping table, wherein the data corresponding to the header information and the data corresponding to the information in the table are unchanged.

Further, the coordinating system regenerates the sales order using the base archive data mapping table and inserts the sales order into the message queue, and waits for the second reconciliation system to read, including:

the coordination system converts the client identification number in the head information of the sales order into a client identification number corresponding to the second reconciliation system by inquiring the basic archive data mapping table;

the sales order is regenerated through renaming the document identification number in the coordination system, and at the moment, the sales order in the first reconciliation system establishes a corresponding relation with the sales order generated in the coordination system;

inserting the regenerated sales order into a message queue of the coordination system, recording the status of the sales order as the unprocessed 'no', and waiting for the reading of the second reconciliation system B.

Further, after the second reconciliation system is connected with the coordination system, the corresponding sales order is read from the message queue and converted into the freight order, and then the freight order is converted and stored by using the basic archive definition mapping table and the basic archive data mapping table, which includes:

the client is connected with the coordination system through the second reconciliation system, and reads a sales order corresponding to the client from a message queue of the coordination system;

the second account checking system converts the sales order into a purchase order of the second account checking system;

by inquiring a basic archive definition mapping table and a basic archive data mapping table, converting the header information and the information in the table of the purchase order into a field corresponding to a second reconciliation system recorded in the basic archive definition mapping table, converting the data corresponding to the product identification number in the information in the table into data corresponding to a second reconciliation system B recorded in the basic archive data mapping table, keeping the rest data unchanged, and then storing the data;

after the conversion is complete, the status of the sales order in the message queue is changed to indicate "yes" which has been processed.

The application has the following technical characteristics:

1. the method and the system assist the supplier and the client to complete the automatic registration of the related financial documents by establishing the message queue, and establish the contrast relationship between the payable account verification and the return verification of the payable account of the client and the return verification of the receivable account of the supplier, so that the business activities of the two parties are clear; the consistency and the balance of data of both the supplier and the client are ensured, and manual operation is reduced.

2. The method and the system have the advantages that a coordination system C capable of coordinating a first reconciliation system A of a supplier and a second reconciliation system B of a client is arranged, the system C is a 'place' for information exchange of A, B two systems, is a 'judge' for analyzing A, B difference, keeps a copy of data of A, B two systems, and can effectively ensure data safety and realize intelligent reconciliation, so that the problems of online remote backup of data, economic dispute caused by unclear accounts, reduction of burden of operators and the like are solved, and normal development of services is promoted.

Drawings

FIG. 1 is a schematic diagram of an interaction architecture of the system of the present application;

FIG. 2 is a schematic diagram of the main services of a provider;

FIG. 3 is a schematic diagram of the main services of a customer;

fig. 4 is a schematic diagram of the system a and the system B interacting with a message queue in the present application.

Detailed Description

From the supplier's perspective, the main services include customer profile C (C is code number, the same below), sales order management Sa, receivable management Ar, and collection management R, as shown in fig. 2. The services affecting accounts receivable are sales order Sa and collection order R.

Similarly, from the perspective of the client, the corresponding services are the supplier profile S (S is code number, the same below), the invoice management Pc, the accounts payable management Ap, and the payment management P, as shown in fig. 3; the services affecting accounts payable are the purchase order Pc and the payment order P.

From the business itself, the sales order management Sa of the product provider (supplier) is actually the purchase order management Pc of the product consumer (client), and the payment order P of the product consumer is actually the collection order R of the product provider. However, in real life, the product provider and the product consumer often have their own financial systems, so that the same service (for example, Sa and Pc) is recorded in the financial systems of the product provider and the product consumer, respectively, which may cause the difference between the two financial systems of the same service.

In order to solve the above problems, the present application provides an automatic account system for accounts receivable/accounts payable of an enterprise, which comprises a coordination system C of a third party, a first account system a of a supplier and a second account system B of a customer, each system being described as follows:

1. coordination system C

In the scheme, a coordination system C is established at a third party except a supplier and a client, the coordination system C can be established on a cloud platform, information exchange and financial reconciliation between a first reconciliation system a and a second reconciliation system B are realized through the coordination system C, and A, B, C the relationship among the three systems is shown in fig. 1.

The coordination system C establishes and maintains a basic archive dictionary which can be acquired by the first reconciliation system a and the second reconciliation system B, and the basic archive dictionary comprises a basic archive definition mapping table and a basic archive data mapping table which are used for defining customer information, supplier information, product information and the like.

1.1 base archive definition mapping Table

The basic file definition mapping table stores the definition and the corresponding relation of basic data of a first account system A and a second account system B, wherein the basic data comprises customer information, product information and receipt information; for the same basic data, different representation modes are adopted in A, B two systems, for example, for the basic data of "customer identification number", the basic data in the system A and the system B are respectively represented by the client.ID and the client.ID, and the corresponding relation, namely the client.ID corresponds to the client.ID.

In one embodiment, the base profile definition mapping table is shown in Table 1; in this embodiment, the customer information includes a customer identification number, a customer bank account number, a customer name, and the like; the product information comprises a product identification number and the like; the document information includes document quantity, document unit price, document amount, document receipt and payment, document date, receipt and payment number, receipt and payment date, and the like. In practical application, data in the customer information, the product information and the document information can be increased and decreased according to actual needs.

TABLE 1 base archive definition mapping table

Serial number	Means of	A system (receivable)	B System (payable)	Data type
					1	Customer identification number	Cust.ID	Client.ID	Character string
2	Customer bank account	Cust.Acct	Client.Bank	Character string
					3	Name of customer	Cust.Name	Client.Name	Character string
4	Product identification number	Prod.ID	Goods.ID	Character string
					5	Document identification number	Sa.ID	Pc.ID	Character string
6	Number of documents	Sa.Amount	Pc.Amt	Number of
					7	Unit price of bill	Sa.Price	Pc.Price	Number of
8	Amount of document	Sa.Qty	Pc.Total	Amount of money
					9	Receipt and payment	Sa.Recive	Pc.Paym	Amount of money
10	Date of receipt	Sa.outdate	Pc.indate	Date
					11	Number of receipt and payment	R.ID	P.ID	Character string
12	Date of receipt and payment	R.recdate	P.paydate	Date

1.2 base archive data mapping Table

The basic archive data mapping table stores the client identification number, the product identification number, and the data key value (primary key) of the supplier identification number of the first reconciliation system a and the second reconciliation system B, and the corresponding relationship thereof, as shown in table 2.

TABLE 2 basic archive data mapping Table

2. Sales service of first reconciliation System A

For the sale service of the first reconciliation system A, the sale service is realized by the cooperation of the first reconciliation system A, the second reconciliation system B and the coordination system C:

2.1 first Account System A generates sales orders

The first reconciliation system a is a reconciliation system established at the supplier. For a sale service of a supplier, the supplier firstly establishes a sale order in a first reconciliation system A for the sale service. The sales order comprises header information and corresponding data, and in-table information and corresponding data; wherein the fields corresponding to the header information and the fields corresponding to the information in the table are included in the basic data of the basic file definition mapping table. For example, in this example, the fields corresponding to the header information include the document identification number, the document date, and the customer identification number, and the fields corresponding to the information in the table include the product identification number, the number of documents, the document unit price, and the document amount. The data corresponding to the customer identification number, the product identification number, the number of the documents and the unit price of the documents are manually input, the data corresponding to the document identification number are automatically generated according to the input sequence of the documents, the data corresponding to the document date are the storage date of the documents, and the data corresponding to the document amount are automatically generated through calculation.

For example, one sales service is: product G1, quantity Q1, unit price P1 was sold to customer C1. Then the sales order corresponding to the sales service is represented as table 3:

TABLE 3 sales order

Document identification number:Sa1document date:D1the client identification number:C1

product identification number	Number of documents	Unit price of bill	Amount of document
				G1	Q1	P1	Q1*P1

After the sales slip table 3 is saved in the first reconciliation system a, the first reconciliation system a queries the basic archive definition mapping table 1 through communication with the coordination system C, and converts the header information and the information in the sales slip table 3 into a field corresponding to the first reconciliation system a recorded in the basic archive definition mapping table, wherein the data corresponding to the header information and the data corresponding to the information in the table are unchanged. The converted sales order is the internal code order of system a, as shown in table 4.

Table 4 converted sales slip (inner code slip) sa.id:Sa1Sa.outdate：D1Cust.ID：C1

Prod.ID	Sa.Amount	Sa.Price	Sa.Qty
				G1	Q1	P1	Q1*P1

the first reconciliation system a generates the converted sales order table 4 and then pushes the converted sales order Sa1 to the reconciliation system C.

2.2 coordination System C handles sales order

After receiving the sales order Sa1, the coordination system C performs the following processing:

2.2-1 coordinating system C converts the customer ID C1 in the header information of sales order Sa1 (Table 4) into the corresponding customer ID S1 of the second reconciliation system B by querying the basic archive data mapping table 2. The purpose of this conversion is because the second reconciliation system B cannot recognize C1, but only S1, but both represent the same client.

2.2-2, the sales order is regenerated in the coordination system C by renaming the document identification number, which is denoted as Sa1 'in the following table, and at this time, Sa1 in the first reconciliation system a establishes a corresponding relationship with the sales order Sa 1' generated in the coordination system C.

Sa.ID：Sa1’Sa.outdate：D1Cust.ID：S1

Prod.ID	Sa.Amount	Sa.Price	Sa.Qty
				G1	Q1	P1	Q1*P1

2.2-3 inserting the regenerated sales order Sa1 'into the message queue of the coordination system C, recording the status of the sales order Sa 1' as 'no' indicating unprocessed, and waiting for the reading of the second reconciliation system B; the queue identification number of the sales order Sa1 'is also Sa 1'. The message queue is A, B where two systems exchange information, allowing asynchronous operation, as shown in FIG. 4.

2.3 second Account checking System B converts sales order into an invoice

The second reconciliation system B is a reconciliation system established at the customer site. When the coordination system C is not available, the customer must manually enter the purchase order corresponding to the sales order Sa1 by using the second reconciliation system B; after the coordination system C is established, the customer does not need to enter manually, and can read the sales order Sa1 from the coordination system C and convert the sales order Sa1 into the purchase order, and the steps are as follows:

2.3-1 customer connects to the coordination system C through the second reconciliation system B and reads the sales order Sa 1' corresponding to the customer from the message queue of the coordination system C. This step can be implemented by referring to the "client identification number" of the sales order in the message queue, and according to table 2, since the client identification number "S1" in the sales order Sa1 'is the client identification number belonging to the second reconciliation system B, it can be known that the sales order Sa 1' corresponds to the client.

2.3-2 the second reconciliation system B converts the sales order Sa 1' into the purchase order Pc1 of the second reconciliation system B, as shown in Table 5 below:

TABLE 5 invoice

The order number of the incoming note:Pc1document date:D1the supplier:S1

product identification number	Number of documents	Unit price of bill	Amount of document
				G1	Q1	P1	Q1*P1

2.3-3, by inquiring the basic archive definition mapping table 1 and the basic archive data mapping table 2, converting header information and information in the table of the purchase order Pc1 into a field corresponding to the second reconciliation system B recorded in the basic archive definition mapping table 1, and converting data corresponding to the product identification number in the in-table information into data (G1 → P1) corresponding to the second reconciliation system B recorded in the basic archive data mapping table 2, wherein the rest data are unchanged and then stored; the converted invoice is shown in table 6; the sales order is an internal code order of the second account checking system B, and functions such as data recording, query and the like can be realized through the internal code order.

Table 6 manifest (inner code sheet) pc.id:Pc1Pc.indate：D1Client.ID：S1

Good.ID	Pc.Amt	Pc.Price	Pc.Total
				P1	Q1	P1	Q1*P1

2.3-4, the status of sales order Sa 1' in the message queue is changed to indicate "YES" has been processed.

3. Payment service of second account-checking system B

When the second account system B of the customer pays the supplier, the payment is realized by the cooperation of the first account system A, the second account system B and the coordination system C:

3.1 second Account checking System B generates an order

The second tie-out system B specifies the invoice to be paid, e.g. if the second tie-out system B pays M1 for the invoice Pc1 at a certain time D2, the specified invoice is Pc1 (table 6). The bill of payment Pay1 is generated by the invoice Pc1, as shown in table 7:

TABLE 7 Payment order

Payment order number:Pay1payment date:D2the client identification number:S1

product identification number	Number of documents	Unit price of bill	Amount of document	Document payment	Remarks for note
						P1	Q1	P1	Q1*P1	M1

The payment bill comprises header information and corresponding data, and in-table information and corresponding data; wherein the fields corresponding to the header information and the fields corresponding to the information in the table are included in the basic data of the basic file definition mapping table. For example, in this example, the fields corresponding to the header information include the payment order number, the document date, and the customer identification number, and the fields corresponding to the information in the table include the product identification number, the number of documents, the document unit price, and the document amount. Wherein, the data corresponding to the payment order number is automatically generated, the input corresponding to the bill payment is manually input, and other data come from the bill of lading Pc 1.

After the payment receipt 3 is saved in the second account checking system B, the second account checking system B queries the basic archive definition mapping table 1 through communication with the coordination system C, and converts the header information and the information in the table of the payment receipt into a field corresponding to the second account checking system B recorded in the basic archive definition mapping table, wherein data corresponding to the header information and data corresponding to the information in the table are unchanged. The converted bill of payment is the internal code bill of the system B, as shown in Table 8.

TABLE 8 Payment bill after conversion (inner code bill)

P.ID：Pay1P.Paydate：D2Client.ID：S1

Goods.ID	Pc.Amt	Pc.Price	Pc.Total	Pc.Paym	Remarks for note
						P1	Q1	P1	Q1*P1	M1

The second reconciliation system B generates the converted bill of payment table 8 and pushes the converted bill of payment Pay1 to the reconciliation system C.

3.2 coordinating systems with Payment order

After the reconciliation system C receives the payment order Pay1, the following process is performed:

3.2-1 coordinator system C converts the client ID S1 in the header information of the Pay1 (Table 8) into the client ID C1 corresponding to the first reconciliation system A by querying the basic archive data mapping table 2.

3.2-2, the payment order is regenerated in the coordination system C, and as shown in the following table, the Pay1 in the second reconciliation system B establishes a corresponding relationship with the payment order Pay1 'generated in the coordination system C at the time of marking as Pay 1'.

P.ID：Pay1’P.Paydate：D2Client.ID：C1

Goods.ID	Pc.Amt	Pc.Price	Pc.Total	Pc.Paym	Remarks for note
						P1	Q1	P1	Q1*P1	M1

3.2-3 insert the Pay1 'into the message queue of the coordinator system C and record the status of the Pay 1' as indicating unprocessed "NO" waiting for the first reconciliation system A to read.

3.3 first Account System A converts Payment order into a receipt

When the coordination system C is not provided, the customer must manually enter a bill corresponding to the payment bill Pay1 by using the first reconciliation system A; after the coordination system C is established, the client does not need to enter manually, but can read the payment bill Pay1 from the coordination system C and convert the payment bill into a receipt, and the steps are as follows:

3.3-1 customer connects to the reconciliation System C through the first reconciliation System A and reads the Pay 1' corresponding to the customer from the message queue of the reconciliation System C.

3.3-2 the first reconciliation System A converts the Pay 1' into a receipt R1 for the first reconciliation System A, as shown in Table 9 below:

TABLE 9 receipt

The number of the collection bill is as follows:R1the collection date:D2the client identification number:C1

product identification number	Number of documents	Unit price of bill	Amount of document	Receipt collection
					P1	Q1	P1	Q1*P1	M1

3.3-3, by inquiring the basic archive definition mapping table 1 and the basic archive data mapping table 2, converting the header information and the information in the form of the bill of payment R1 into a field corresponding to the first reconciliation system A recorded in the basic archive definition mapping table 1, and converting the data corresponding to the product identification number in the information in the form of the bill into the data (P1 → G1) corresponding to the first reconciliation system A recorded in the basic archive data mapping table 2, wherein the rest data are unchanged; the converted bill is shown in table 10; the receipt is an internal code sheet of the first reconciliation system A, and the functions of data recording, query and the like can be realized through the internal code sheet.

Table 10 receipt (inner code slip) r.id:R1R.recdate：D2Cust.ID：C1

Prod.ID	Sa.Amount	Sa.Price	Sa.Qty	Sa.Receive
					G1	Q1	P1	Q1*P1	M1

3.3-4 after the transition is complete, the status of the sales order Pay 1' in the message queue is changed to indicate a processed "YES".

4. Difference analysis for coordination System C

The first reconciliation system A and the second reconciliation system B carry out information interaction and conversion under the coordination of the coordination system C, under certain unexpected factors such as network disconnection, manual misoperation, viruses and the like, the phenomenon that accounts receivable and accounts payable are inconsistent can be caused to exist in the two systems, and at the moment, the electronic reconciliation function is realized through difference analysis.

For example, a difference analysis function F can be customized in the coordination system C, and its function is to list a service bill list corresponding to a parameter according to the parameter n, and the meaning of the parameter n is defined as: 1-sale, 2-stock, 3-payment, 4-refund. The following description will be made by taking a sales transaction (corresponding parameter 1) of the first reconciliation system a and a stock transaction (corresponding parameter 2) of the second reconciliation system B as examples.

4.1 the first reconciliation system A calls F (1), returns the sales service list of the first reconciliation system A, and sets the sales service list as A.list;

4.2 the second reconciliation system B calls F (2), returns a goods-feeding business list of the second reconciliation system B, and sets the list as B.list;

4.3 comparing A.list with B.list to obtain the difference record;

and 4.4, respectively returning the difference records to the first account checking system A and the second account checking system B, and correcting after the manual review is passed.

The message queue and the difference analysis function can be packaged into a system to support offline operation online updating. In addition, the message queue can be changed into e-mail sending, and then a difference analysis table of payment receipt and payment of both parties can be made according to the content of the e-mail.

Claims (6)

1. An enterprise accounts receivable/accounts payable automated reconciliation system comprising a first reconciliation system established at a supplier, a second reconciliation system established at a customer, and a reconciliation system established at a third party;

a basic file dictionary which can be acquired by a first reconciliation system and a second reconciliation system is established and maintained in the coordination system, and comprises a basic file definition mapping table and a basic file data mapping table which are used for defining customer information, supplier information and product information; the basic file definition mapping table stores definitions and corresponding relations of basic data of a first account checking system and a second account checking system, wherein the basic data comprises customer information, product information and receipt information; the basic archive data mapping table stores data key values and corresponding relations of client identification numbers, product identification numbers and supplier identification numbers of a first account system and a second account system;

for the sales service of the first reconciliation system, firstly generating a sales order through the first reconciliation system, converting the sales order by using a basic archive definition mapping table, sending the converted sales order to the reconciliation system, regenerating the sales order by using the basic archive data mapping table by using the reconciliation system, inserting the sales order into a message queue, and waiting for reading by using the second reconciliation system; the second account checking system reads the corresponding sales order from the message queue and converts the sales order into a purchase order after being connected with the coordination system, and then the purchase order is converted and stored by utilizing the basic archive definition mapping table and the basic archive data mapping table;

for the payment service of the second account checking system, firstly, the second account checking system appoints an incoming bill to be paid, generates a bill through the incoming bill, then communicates with the coordination system, converts the bill by using a basic archive definition mapping table, sends the converted bill to the coordination system, regenerates the bill by using a basic archive data mapping table, inserts the bill into a message queue, and waits for the reading of the first account checking system; and the first reconciliation system is connected with the coordination system, reads the corresponding payment order from the message queue and converts the payment order into a receipt, and then converts and stores the receipt by utilizing the basic file definition mapping table and the basic file data mapping table.

2. The system of claim 1, wherein when the accounts receivable/accounts payable of the enterprise are inconsistent with each other in the first and second reconciliation systems, the electronic reconciliation function is implemented by difference analysis, comprising:

customizing a difference analysis function in a coordination system by user, wherein the function of the difference analysis function is to list a business document list corresponding to a parameter according to the parameter n, and the meaning of the parameter n is agreed to different operation or financial operation, including sale, delivery, payment and cash withdrawal;

when electronic reconciliation is carried out, the first reconciliation system and the second reconciliation system respectively call a difference analysis function, a sales business list/payment list of the first reconciliation system and a goods-in business list/money-back list of the second reconciliation system are obtained by correspondingly assigning the parameter n, a difference record is obtained by comparing the sales business list and the goods-in business list or comparing the payment list and the money-back list, the difference record is respectively sent to the first reconciliation system and the second reconciliation system, and correction is carried out after manual audit.

3. The enterprise accounts receivable/accounts payable automated reconciliation system of claim 1 wherein the generating of the sales order by the first reconciliation system comprises:

the sales order comprises header information and corresponding data, and in-table information and corresponding data; wherein, the field corresponding to the header information and the field corresponding to the information in the table are contained in the basic data of the basic file definition mapping table; the fields corresponding to the header information of the form comprise a form identification number, a form date and a customer identification number, and the fields corresponding to the information in the form comprise a product identification number, a form quantity, a form unit price and a form amount; the data corresponding to the customer identification number, the product identification number, the number of the documents and the unit price of the documents are manually input, the data corresponding to the document identification number are automatically generated according to the input sequence of the documents, the data corresponding to the document date are the storage date of the documents, and the data corresponding to the document amount are automatically generated through calculation.

4. The enterprise accounts receivable/accounts payable automated reconciliation system of claim 1 wherein the transformation of the sales order generated by the first reconciliation system using the base profile definition mapping table comprises:

the first reconciliation system inquires the basic archive definition mapping table through communication with the coordination system, and converts the header information and the information in the table of the sales order into a field corresponding to the first reconciliation system recorded in the basic archive definition mapping table, wherein the data corresponding to the header information and the data corresponding to the information in the table are unchanged.

5. The enterprise accounts receivable/accounts payable automated reconciliation system of claim 1 wherein the reconciliation system utilizes the base profile data mapping table to regenerate sales orders and insert them into the message queue awaiting reading by the second reconciliation system comprising:

the coordination system converts the client identification number in the head information of the sales order into a client identification number corresponding to the second reconciliation system by inquiring the basic archive data mapping table;

the sales order is regenerated through renaming the document identification number in the coordination system, and at the moment, the sales order in the first reconciliation system establishes a corresponding relation with the sales order generated in the coordination system;

inserting the regenerated sales order into a message queue of the coordination system, recording the status of the sales order as the unprocessed 'no', and waiting for the reading of the second reconciliation system B.

6. The system of claim 1, wherein the second reconciliation system is connected to the reconciliation system, reads the corresponding sales order from the message queue and converts the sales order into the incoming order, and then converts and stores the incoming order by using the base profile definition mapping table and the base profile data mapping table, and comprises:

the client is connected with the coordination system through the second reconciliation system, and reads a sales order corresponding to the client from a message queue of the coordination system;

the second account checking system converts the sales order into a purchase order of the second account checking system;

by inquiring a basic archive definition mapping table and a basic archive data mapping table, converting the header information and the information in the table of the purchase order into a field corresponding to a second reconciliation system recorded in the basic archive definition mapping table, converting the data corresponding to the product identification number in the information in the table into data corresponding to a second reconciliation system B recorded in the basic archive data mapping table, keeping the rest data unchanged, and then storing the data;

after the conversion is complete, the status of the sales order in the message queue is changed to indicate "yes" which has been processed.

Images