CN111402020B - Enterprise account-receiving/paying automatic checking system - Google Patents
Enterprise account-receiving/paying automatic checking system Download PDFInfo
- Publication number
- CN111402020B CN111402020B CN202010158084.7A CN202010158084A CN111402020B CN 111402020 B CN111402020 B CN 111402020B CN 202010158084 A CN202010158084 A CN 202010158084A CN 111402020 B CN111402020 B CN 111402020B
- Authority
- CN
- China
- Prior art keywords
- bill
- reconciliation system
- reconciliation
- mapping table
- sales
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
- G06Q40/12—Accounting
- G06Q40/125—Finance or payroll
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/30—Information retrieval; Database structures therefor; File system structures therefor of unstructured textual data
- G06F16/33—Querying
- G06F16/3331—Query processing
- G06F16/334—Query execution
Landscapes
- Engineering & Computer Science (AREA)
- Business, Economics & Management (AREA)
- Accounting & Taxation (AREA)
- Finance (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Development Economics (AREA)
- Technology Law (AREA)
- Strategic Management (AREA)
- General Business, Economics & Management (AREA)
- Marketing (AREA)
- Economics (AREA)
- Computational Linguistics (AREA)
- Data Mining & Analysis (AREA)
- Databases & Information Systems (AREA)
- General Engineering & Computer Science (AREA)
- Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
Abstract
The application discloses an enterprise receivables/accounts payables automatic reconciliation system, comprising a first reconciliation system established at a provider, 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 the first reconciliation system and the second reconciliation system is established and maintained in the coordination system and is used for defining customer information, provider information and product information; for sales business of the first reconciliation system or payment business of the second reconciliation system, intelligent reconciliation can be realized with the assistance of the coordination system; in the method, a message queue is established, the automatic registration of relevant financial documents is completed by a supplier and a client, and a comparison relation is established between accounts payable verification of the client and accounts receivables verification of the supplier, so that business activities of the two parties are clear; the consistency and balance of data of both the suppliers and the clients are ensured, and the problems of economic disputes, lightening the burden of operators and the like caused by unclear accounts are avoided.
Description
Technical Field
The application relates to the field of financial data processing, in particular to an enterprise accounts receivable/payable automatic account checking system which is used for automatically comparing and registering business documents of accounts receivable and payable of circulation enterprises.
Background
At present, the accounts receivable and receivables of the circulation type enterprises are verified in the following modes:
1. verifying and marketing aiming at the client name; 2. verification against ticket numbers.
Corresponding to accounts receivable is accounts payable and accounts payable is billed, both operations occurring at the associated two units with close correlation. However, in existing accounting methods, neither the suppliers nor the customers (payee, payer) can achieve online interaction; in the absence of efficient online interaction, the prior art suffers from the drawbacks of: the payor has difference between the accounting of accounts payable and the accounting of accounts receipts corresponding to the payor and is not aware of each other, which inevitably causes confusion of accounts of both parties and even economic disputes.
Disclosure of Invention
The utility model aims to provide an automatic account checking system for accounts receivable/payable of enterprises, which is used for solving the account verification problem in the prior art, which is caused by the fact that suppliers and clients cannot realize online interaction.
In order to achieve the above task, the present application adopts the following technical scheme:
an enterprise accounts receivable/payable automatic reconciliation system includes a first reconciliation system established at a provider, a second reconciliation system established at a customer, and a reconciliation system established at a third party;
the coordination system establishes and maintains a basic file dictionary which can be acquired by a first reconciliation system and a second reconciliation system, wherein the basic file dictionary comprises a basic file definition mapping table and a basic file data mapping table which are used for defining client information, provider information and product information; the basic file definition mapping table stores definitions of basic data of a first reconciliation system and a second reconciliation system and corresponding relations of the definitions, and the basic data comprises client information, product information and bill information; the basic file data mapping table stores the data key values of the client identification numbers, the product identification numbers and the supplier identification numbers of the first reconciliation system and the second reconciliation system and the corresponding relations thereof;
for sales business of a first reconciliation system, firstly, a sales bill is generated through the first reconciliation system and converted by utilizing a basic file definition mapping table, the converted sales bill is sent to a coordination system, the coordination system regenerates the sales bill by utilizing the basic file data mapping table and inserts the sales bill into a message queue, and the sales bill is waited for being read by a second reconciliation system; the second reconciliation system is connected with the coordination system, reads the corresponding sales bill from the message queue and converts the sales bill into an incoming bill, and then converts and stores the incoming bill by utilizing the basic file definition mapping table and the basic file data mapping table;
for the payment business of the second reconciliation system, firstly, the second reconciliation system designates an incoming bill to be paid, generates a payment bill through the incoming bill, then communicates with the coordination system, converts the payment bill by utilizing a basic file definition mapping table, sends the converted payment bill to the coordination system, regenerates the payment bill by utilizing the basic file data mapping table, inserts the payment bill into a message queue and waits for the first reconciliation system to read; the first reconciliation system is connected with the coordination system, reads the corresponding payment bill from the message queue and converts the payment bill into a collection bill, and then utilizes the basic file definition mapping table and the basic file data mapping table to convert and store the collection bill.
Further, when the first and second reconciliation systems have inconsistent accounts receivable and accounts payable, the electronic reconciliation function is realized through the difference analysis, including:
a difference analysis function is customized in the coordination system, and the function is to list a business bill list corresponding to the parameter according to the parameter n, wherein the meaning of the parameter n is agreed to be different business or financial operations including sales, goods intake, payment and refund;
when electronic reconciliation is carried out, the first reconciliation system and the second reconciliation system respectively call a difference analysis function, a sales service list/payment list of the first reconciliation system and a goods-incoming service list/return list of the second reconciliation system are obtained through corresponding assignment of the parameter n, difference records are obtained through comparison of the sales service list and the goods-incoming service list or comparison of the payment list and the return list, and the difference records are respectively sent to the first reconciliation system and the second reconciliation system to be corrected after manual verification.
Further, the generating, by the first reconciliation system, a sales order includes:
the sales order comprises header information, corresponding data, in-table information and corresponding data; wherein, the field corresponding to the header information and the field corresponding to the information in the table should be contained in the basic data of the basic file definition mapping table; the fields corresponding to the header information comprise a bill identification number, a bill date and a client identification number, and the fields corresponding to the information in the table comprise a product identification number, a bill quantity, a bill unit price and a bill amount; the data corresponding to the client identification number, the product identification number, the bill number and the bill unit price are manually input, the data corresponding to the bill identification number is automatically generated according to the input sequence of the bill, the data corresponding to the bill date is the storage date of the bill, and the data corresponding to the bill amount is automatically calculated and generated.
Further, the process of the sales order generated by the first reconciliation system and converted using the base profile definition mapping table comprises:
the first reconciliation system queries the basic file definition mapping table through communication with the coordination system, and converts header information of the sales order and information in the table into fields corresponding to the first reconciliation system recorded in the basic file definition mapping table, wherein data corresponding to the header information and data corresponding to the information in the table are unchanged.
Further, the coordination system regenerates the sales order by using the basic archive data mapping table and inserts the sales order into the message queue, waits for the second reconciliation system to read, and comprises:
the coordination system converts the client identification number in the sales list header information into the client identification number corresponding to the second reconciliation system by inquiring the basic file data mapping table;
regenerating a sales order in the coordination system through renaming the receipt identification number, wherein the sales order in the first reconciliation system and the sales order generated in the coordination system establish a corresponding relation;
the regenerated sales order is inserted into the message queue of the coordination system and the state of the sales order is recorded as "no" indicating unprocessed, waiting for the second reconciliation system B to read.
Further, after the second reconciliation system is connected with the coordination system, the second reconciliation system reads the corresponding sales order from the message queue and converts the sales order into an incoming order, and then converts and stores the incoming order by using the basic archive definition mapping table and the basic archive data mapping table, including:
the client is connected with the coordination system through the second reconciliation system, and a sales order corresponding to the client is read from a message queue of the coordination system;
the second reconciliation system converts the sales order into an inventory order for the second reconciliation system;
the method comprises the steps of inquiring a basic file definition mapping table and a basic file data mapping table, converting header information of a purchase order and information in the table into fields corresponding to a second reconciliation system recorded in the basic file definition mapping table, converting data corresponding to a product identification number in the information in the table into data corresponding to a second reconciliation system B recorded in the basic file data mapping table, keeping the rest of data unchanged, and then storing;
after the conversion is completed, the state 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. according to the method and the system, the message queue is established, the automatic registration of relevant financial documents is completed by the auxiliary provider and the client, and the comparison relation between accounts payable verification of the client and accounts receivables verification of the provider is established, so that business activities of the two parties are clear; and the consistency and balance of data of both suppliers and customers are ensured, and manual operation is reduced.
2. The coordination system C which can coordinate the first accounting system A of the provider and the second accounting system B of the customer is arranged, the C system is not only the 'place' for information exchange between the A, B system and the 'judge' for analysis A, B difference, but also the copy of the A, B data of the two systems is reserved, so that the data safety can be effectively ensured, the intelligent accounting can be realized, the problems of economic disputes, reduction of the burden of a salesman and the like caused by online long-distance backup of the data, and the normal development of the business are promoted.
Drawings
FIG. 1 is a schematic diagram of the interactive architecture of the system of the present application;
FIG. 2 is a schematic diagram of the primary business of a provider;
FIG. 3 is a schematic diagram of the primary business of a customer;
fig. 4 is a schematic diagram of the system a and the system B in the present application when they interact with a message queue.
Detailed Description
From the perspective of the provider, the main services are customer profile C (C is code number, hereinafter the same), sales order management Sa, accounts receivable management Ar, collection management R, as shown in fig. 2. The services affecting accounts receivable are sales order Sa and receipt order R.
Similarly, from the perspective of the customer, the corresponding services are the provider profile S (S is code number, hereinafter the same), the order management Pc, the accounts payable management Ap, the payment management P, as shown in fig. 3; the services affecting the 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 in fact the purchase order management Pc of the product consumer (customer), and the payment order P of the product consumer is in fact the receipt R of the product provider. However, in real life, it is often the case that the product provider and the product consumer each have their own financial systems, so that the same business (such as Sa and Pc) is respectively recorded in the financial systems of the product provider and the product consumer, which may cause the difference between the two financial systems.
In order to solve the above-mentioned problems, the present application provides an enterprise accounts receivable/payable automatic reconciliation system, which includes a third party coordination system C, a first reconciliation system a of a provider, and a second reconciliation system B of a customer, each of which is described as follows:
1. coordination system C
In the scheme, a coordination system C is established at a third party except a provider and a customer, 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 the relationship of the three systems A, B, C is shown in figure 1.
The coordination system C establishes and maintains a basic file dictionary which can be acquired by the first reconciliation system A and the second reconciliation system B, and comprises a basic file definition mapping table and a basic file data mapping table which are used for defining client information, provider information, product information and the like.
1.1 basic archive definition mapping tables
The basic file definition mapping table stores the definition of basic data of the first reconciliation system A and the second reconciliation system B and the corresponding relation thereof, wherein the basic data comprises client information, product information and bill information; for the same piece of basic data, different representation modes are adopted in two systems A, B, for example, for the basic data of 'client identification number', the basic data are respectively represented by a test.ID and a client.ID in a system A and a system B, and the corresponding relation, namely the test.ID corresponds to the client.ID.
In one embodiment, the base archive definition map is as 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 includes a product identification number and the like; the bill information includes the bill quantity, bill price, bill amount, bill receipt and payment, bill date, receipt and payment bill number, receipt and payment date, etc. In practical application, the data in the customer information, the product information and the bill information can be increased or decreased according to practical requirements.
Table 1 basic archive definition map
| Sequence number | Meaning of | A system (should be received) | B system (cope with) | Data type |
| 1 | Customer identification number | Cust.ID | Client.ID | Character string |
| 2 | Customer bank account | Cust.Acct | Client.Bank | Character string |
| 3 | Customer name | Cust.Name | Client.Name | Character string |
| 4 | Product identification number | Prod.ID | Goods.ID | Character string |
| 5 | Receipt identification number | Sa.ID | Pc.ID | Character string |
| 6 | Document quantity | Sa.Amount | Pc.Amt | Digital number |
| 7 | Bill unit price | Sa.Price | Pc.Price | Digital number |
| 8 | Bill amount | Sa.Qty | Pc.Total | Amount of money |
| 9 | Receipt and payment | Sa.Recive | Pc.Paym | Amount of money |
| 10 | Document date | Sa.outdate | Pc.indate | Date of day |
| 11 | Receipt and payment bill number | R.ID | P.ID | Character string |
| 12 | Date of receipt and payment | R.recdate | P.paydate | Date of day |
1.2 basic archive data mapping tables
The basic archive data mapping table stores the client identifiers of the first reconciliation system a and the second reconciliation system B, the product identifiers, the data key values (primary keys) of the vendor identifiers, and the correspondence relationships thereof, as shown in table 2.
Table 2 basic archive data map
2. Sales business of first reconciliation system A
For sales business of the first reconciliation system A, the second reconciliation system B and the coordination system C are matched to realize:
2.1 first reconciliation System A generates sales order
The first reconciliation system a is a reconciliation system established at a vendor. For a sales service of a provider, the provider first establishes a sales order in the first reconciliation system a. The sales order comprises header information, corresponding data, in-table information and corresponding data; 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 header information include a document identification number, a document date, and a customer identification number, and the fields corresponding to information in the table include a product identification number, a document unit price, and a document amount. The data corresponding to the client identification number, the product identification number, the bill number and the bill unit price are manually input, the data corresponding to the bill identification number is automatically generated according to the input sequence of the bill, the data corresponding to the bill date is the storage date of the bill, and the data corresponding to the bill amount is automatically calculated and generated.
For example, one sales service is: product G1 is sold to customer C1 in quantity Q1 and unit price P1. The sales order corresponding to the sales service is expressed as table 3:
TABLE 3 sales order
Document identification number:Sa1document date:D1customer identification number:C1
| product identification number | Document quantity | Bill unit price | Bill amount |
| G1 | Q1 | P1 | Q1*P1 |
After the sales order table 3 is stored in the first reconciliation system a, the first reconciliation system a queries the basic file definition mapping table 1 by communicating with the reconciliation system C, and converts header information and information in the table of the sales order table 3 into fields corresponding to the first reconciliation system a recorded in the basic file definition mapping table, where data corresponding to the header information and data corresponding to the information in the table are unchanged. The converted sales order is the internal code order of the a system as shown in table 4.
Table 4 converted sales order (inner code order) sa.id:Sa1 Sa.outdate：D1 Cust.ID：C1
| Prod.ID | Sa.Amount | Sa.Price | Sa.Qty |
| G1 | Q1 | P1 | Q1*P1 |
after the first reconciliation system a generates the converted sales order table 4, the converted sales order Sa1 is pushed to the reconciliation system C.
2.2 coordination System C processes sales orders
After receiving the sales order Sa1, the coordinator system C performs the following processing:
2.2-1 coordinator system C converts the customer identification number C1 in the header information of sales order Sa1 (Table 4) into customer identification number S1 corresponding to second reconciliation system B by querying base archive data mapping table 2. The purpose of the conversion here is that the second reconciliation system B cannot identify C1, only S1, but both represent the same customer.
2.2-2 the sales order is regenerated in the coordinator system C by renaming the document identification number, denoted as Sa1 'in the following table, and at this time, sa1 in the first reconciliation system A has a correspondence with the sales order Sa1' generated in the coordinator system C.
Sa.ID：Sa1’Sa.outdate：D1 Cust.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 coordinator system C, and recording the state of the sales order Sa1' as indicating unprocessed NO, waiting for the second reconciliation system B to read; the queue identification number of the sales order Sa1 'is also Sa1'. Message queues are the sites where the A, B two systems exchange information, allowing asynchronous operation, as shown in fig. 4.
2.3 second reconciliation System B converting sales order into incoming order
The second reconciliation system B is a reconciliation system established at the customer. When the coordination system C is not available, the customer utilizes the second reconciliation system B to manually enter an incoming bill corresponding to the sales bill Sa 1; after the scheme establishes the coordination system C, the client can read the sales order Sa1 from the coordination system C and convert the sales order into an incoming order without manual input, and the method comprises the following steps:
2.3-1 customer connects to coordinator system C via second reconciliation system B and reads sales order Sa1' corresponding to the customer from the message queue of coordinator system C. This step may be achieved by querying the message queue for the "customer identification number" of the sales order, according to table 2, since the customer identification number "S1" in the sales order Sa1 'is the customer identification number belonging to the second reconciliation system B, it is known that the sales order Sa1' corresponds to the customer.
2.3-2 the second reconciliation system B converts the sales order Sa1' into an inventory order Pc1 for the second reconciliation system B as shown in Table 5 below:
TABLE 5 inventory
Order number:Pc1document date:D1the suppliers:S1
| product identification number | Document quantity | Bill unit price | Bill amount |
| G1 | Q1 | P1 | Q1*P1 |
2.3-3, by inquiring the basic file definition mapping table 1 and the basic file data mapping table 2, converting the header information and the in-table information of the purchase bill Pc1 into fields corresponding to the second reconciliation system B recorded in the basic file definition mapping table 1, converting the 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 file data mapping table 2, keeping the rest of the data unchanged, and then storing; the converted inventory is shown in table 6; the sales order is an internal code order of the second reconciliation system B, and functions such as data recording and query can be realized through the internal code order.
Table 6 entry form (inner code form) pc.id:Pc1 Pc.indate：D1 Client.ID：S1
| Good.ID | Pc.Amt | Pc.Price | Pc.Total |
| P1 | Q1 | P1 | Q1*P1 |
2.3-4, after the conversion is completed, the status of the sales order Sa1' in the message queue is changed to indicate "yes" which has been processed.
3. Payment service of second reconciliation system B
When the second reconciliation system B of the customer pays the provider, the first reconciliation system A, the second reconciliation system B and the coordination system C are matched to realize:
3.1 the second reconciliation System B generates an inventory
The second reconciliation system B designates an incoming bill to be paid, e.g., the second reconciliation system B pays for the incoming bill Pc1 for payment M1 at a time D2, the designated incoming bill is Pc1 (table 6). The payment bill Pay1 is generated by the purchase order Pc1 as shown in table 7:
TABLE 7 pay sheet
Pay sheet number:Pay1payment date:D2customer identification number:S1
| product identification number | Document quantity | Bill unit price | Bill amount | Bill payment | Remarks |
| P1 | Q1 | P1 | Q1*P1 | M1 |
The payment bill comprises header information, corresponding data, in-table information and corresponding data; 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 header information include a payment sheet number, a document date, and a customer identification number, and the fields corresponding to information in the table include a product identification number, a document unit price, and a document amount. The data corresponding to the bill number is automatically generated, the input corresponding to the bill payment is manually input, and other data come from the bill of deposit Pc1.
After the sales payment bill 3 is stored in the second reconciliation system B, the second reconciliation system B queries the basic file definition mapping table 1 by communicating with the reconciliation system C, and converts header information of the payment bill and information in the table into fields corresponding to the second reconciliation system B recorded in the basic file definition mapping table, where data corresponding to the header information and data corresponding to the information in the table are unchanged. The converted payment form is the internal code form of the B system as shown in table 8.
Table 8 converted payment sheet (inner code sheet)
P.ID：Pay1P.Paydate：D2 Client.ID：S1
| Goods.ID | Pc.Amt | Pc.Price | Pc.Total | Pc.Paym | Remarks |
| P1 | Q1 | P1 | Q1*P1 | M1 |
After the second reconciliation system B generates the converted payment bill table 8, the converted payment bill Pay1 is pushed to the coordination system C.
3.2 coordination System processing payslips
After receiving the payment bill Pay1, the coordination system C performs the following processing:
3.2-1 coordinator system C converts the customer identification number S1 in the header information of Pay1 (Table 8) into the customer identification number C1 corresponding to the first reconciliation system A by querying the base archive data mapping table 2.
3.2-2 the bill of payment is regenerated in the coordinator system C, which is denoted as Pay1 'in the following table, and Pay1 in the second reconciliation system B then establishes a correspondence with the bill of payment Pay1' generated in the coordinator system C.
P.ID：Pay1’P.Paydate：D2 Client.ID：C1
| Goods.ID | Pc.Amt | Pc.Price | Pc.Total | Pc.Paym | Remarks |
| P1 | Q1 | P1 | Q1*P1 | M1 |
3.2-3 the Pay-out Pay1 'is inserted into the message queue of the coordinator system C and the status of the Pay-out Pay1' is noted as indicating unprocessed "no", waiting for the first reconciliation system a to read.
3.3 the first reconciliation System A converts the payment form into a receipt
When the coordination system C is not available, the customer utilizes the first reconciliation system A to manually input a receipt corresponding to the payment bill Pay 1; after the scheme establishes the coordination system C, the client can read the payment bill Pay1 from the coordination system C and convert the payment bill into a receipt bill without manual input, and the steps are as follows:
3.3-1 customer connects to coordinator system C via first reconciliation system A and reads payment sheet Pay1' corresponding to the customer from the message queue of coordinator system C.
3.3-2 the first reconciliation system A converts the payment sheet Pay1' into the bill R1 for the first reconciliation system A as shown in Table 9 below:
table 9 bill of collection
Bill number of collection:R1date of collection:D2customer identification number:C1
| product identification number | Document quantity | Bill unit price | Bill amount | Receipt of documents |
| P1 | Q1 | P1 | Q1*P1 | M1 |
3.3-3, by inquiring the basic file definition mapping table 1 and the basic file data mapping table 2, converting the header information and the in-table information of the payment bill R1 into a field corresponding to the first reconciliation system A recorded in the basic file definition mapping table 1, and converting the data corresponding to the product identification number in the in-table information into data (P1→G1) corresponding to the first reconciliation system A recorded in the basic file data mapping table 2, wherein the rest data are unchanged; the converted bill of collection is shown in Table 10; the receipt is an internal code list of the first reconciliation system A, and functions such as data recording and inquiry can be realized through the internal code list.
Table 10 bill of collection (inner code) r.id:R1 R.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 conversion is completed, the status of sales order Pay1' in the message queue is changed to indicate processed "yes".
4. Differential analysis of coordinator system C
The first account checking system A and the second account checking system B perform information interaction and conversion under the coordination of the coordination system C, and under certain unexpected factors such as network disconnection, human misoperation, viruses and the like, the phenomenon that accounts receivable and accounts payable are inconsistent can be caused in the two systems, and at the moment, the electronic account checking function is realized through difference analysis.
For example, a difference analysis function F may be defined in the coordination system C, where the function is to list a service bill list corresponding to a parameter according to a parameter n, where the meaning of the parameter n is defined as follows: 1-sales, 2-returns, 3-payments, 4-returns. The sales business (corresponding to parameter 1) of the first reconciliation system a and the shipment business (corresponding to parameter 2) of the second reconciliation system B will be described below as examples.
4.1, the first reconciliation system A calls F (1), returns a 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 the inventory service list of the second reconciliation system B, and sets the inventory as B.list;
4.3 comparing the A.list with the B.list to obtain a difference record;
and 4.4, respectively returning the difference records to the first reconciliation system A and the second reconciliation system B, and correcting after the manual audit is passed.
Message queues and variance analysis functions may be encapsulated into a system that supports online updates for offline operations. In addition, the message queue can be changed into an email for sending, and then the payment difference analysis table of both parties can be made according to the content of the email.
Claims (1)
1. An enterprise accounts receivable/payable automatic reconciliation system comprising a first reconciliation system established at a provider, a second reconciliation system established at a customer, and a reconciliation system established at a third party;
the coordination system establishes and maintains a basic file dictionary which can be acquired by a first reconciliation system and a second reconciliation system, wherein the basic file dictionary comprises a basic file definition mapping table and a basic file data mapping table which are used for defining client information, provider information and product information; the basic file definition mapping table stores definitions of basic data of a first reconciliation system and a second reconciliation system and corresponding relations of the definitions, and the basic data comprises client information, product information and bill information; the basic file data mapping table stores the data key values of the client identification numbers, the product identification numbers and the supplier identification numbers of the first reconciliation system and the second reconciliation system and the corresponding relations thereof;
for sales business of a first reconciliation system, firstly, a sales bill is generated through the first reconciliation system and converted by utilizing a basic file definition mapping table, the converted sales bill is sent to a coordination system, the coordination system regenerates the sales bill by utilizing the basic file data mapping table and inserts the sales bill into a message queue, and the sales bill is waited for being read by a second reconciliation system; the second reconciliation system is connected with the coordination system, reads the corresponding sales bill from the message queue and converts the sales bill into an incoming bill, and then converts and stores the incoming bill by utilizing the basic file definition mapping table and the basic file data mapping table;
for the payment business of the second reconciliation system, firstly, the second reconciliation system designates an incoming bill to be paid, generates a payment bill through the incoming bill, then communicates with the coordination system, converts the payment bill by utilizing a basic file definition mapping table, sends the converted payment bill to the coordination system, regenerates the payment bill by utilizing the basic file data mapping table, inserts the payment bill into a message queue and waits for the first reconciliation system to read; the first reconciliation system is connected with the coordination system, reads a corresponding payment form from the message queue and converts the payment form into a collection form, and then utilizes the basic file definition mapping table and the basic file data mapping table to convert and store the collection form;
when the first account checking system and the second account checking system have the phenomenon that accounts receivable and accounts payable are inconsistent, the electronic account checking function is realized through difference analysis, and the method comprises the following steps:
a difference analysis function is customized in the coordination system, and the function is to list a business bill list corresponding to the parameter according to the parameter n, wherein the meaning of the parameter n is agreed to be different business or financial operations including sales, goods intake, payment and refund;
when electronic reconciliation is carried out, the first reconciliation system and the second reconciliation system respectively call a difference analysis function, a sales service list/payment list of the first reconciliation system and a goods-incoming service list/return list of the second reconciliation system are obtained through corresponding assignment of the parameter n, difference records are obtained through comparison of the sales service list and the goods-incoming service list or comparison of the payment list and the return list, the difference records are respectively sent to the first reconciliation system and the second reconciliation system, and correction is carried out after manual audit;
the generating, by the first reconciliation system, a sales order comprising:
the sales order comprises header information, corresponding data, in-table information and corresponding data; wherein, the field corresponding to the header information and the field corresponding to the information in the table should be contained in the basic data of the basic file definition mapping table; the fields corresponding to the header information comprise a bill identification number, a bill date and a client identification number, and the fields corresponding to the information in the table comprise a product identification number, a bill quantity, a bill unit price and a bill amount; the data corresponding to the client identification number, the product identification number, the bill quantity and the bill unit price are manually input, the data corresponding to the bill identification number is automatically generated according to the input sequence of the bill, the data corresponding to the bill date is the storage date of the bill, and the data corresponding to the bill amount is automatically calculated and generated;
the process of the sales order generated by the first reconciliation system and converted using the base archive definition mapping table comprises:
the first reconciliation system queries a basic file definition mapping table through communication with the coordination system, and converts header information of a sales order and information in the table into fields corresponding to the first reconciliation system recorded in the basic file definition mapping table, wherein data corresponding to the header information and data corresponding to the information in the table are unchanged;
the coordination system regenerates the sales order by using the basic archive data mapping table and inserts the sales order into the message queue to wait for the reading of the second reconciliation system, and the coordination system comprises the following steps:
the coordination system converts the client identification number in the sales list header information into the client identification number corresponding to the second reconciliation system by inquiring the basic file data mapping table;
regenerating a sales order in the coordination system through renaming the receipt identification number, wherein the sales order in the first reconciliation system and the sales order generated in the coordination system establish a corresponding relation;
inserting the regenerated sales order into a message queue of the coordination system, and recording the state of the sales order as 'no' representing unprocessed, and waiting for the second reconciliation system B to read;
the second reconciliation system reads the corresponding sales order from the message queue and converts the sales order into an incoming order after being connected with the coordination system, and then converts and stores the incoming order by utilizing the basic archive definition mapping table and the basic archive data mapping table, and the method comprises the following steps:
the client is connected with the coordination system through the second reconciliation system, and a sales order corresponding to the client is read from a message queue of the coordination system;
the second reconciliation system converts the sales order into an inventory order for the second reconciliation system;
the method comprises the steps of inquiring a basic file definition mapping table and a basic file data mapping table, converting header information of a purchase order and information in the table into fields corresponding to a second reconciliation system recorded in the basic file definition mapping table, converting data corresponding to a product identification number in the information in the table into data corresponding to a second reconciliation system B recorded in the basic file data mapping table, keeping the rest of data unchanged, and then storing;
after the conversion is completed, the state of the sales order in the message queue is changed to indicate "yes" which has been processed.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010158084.7A CN111402020B (en) | 2020-03-09 | 2020-03-09 | Enterprise account-receiving/paying automatic checking system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010158084.7A CN111402020B (en) | 2020-03-09 | 2020-03-09 | Enterprise account-receiving/paying automatic checking system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111402020A CN111402020A (en) | 2020-07-10 |
| CN111402020B true CN111402020B (en) | 2023-05-02 |
Family
ID=71430568
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010158084.7A Active CN111402020B (en) | 2020-03-09 | 2020-03-09 | Enterprise account-receiving/paying automatic checking system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111402020B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111951091B (en) * | 2020-08-13 | 2023-12-29 | 金蝶软件（中国）有限公司 | Transaction flow reconciliation method, system and related equipment |
| CN112801531A (en) * | 2021-02-07 | 2021-05-14 | 上海汉询软件有限公司 | Full-process receivable management system |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7177828B1 (en) * | 2000-05-02 | 2007-02-13 | General Electric Canada Equipment Finance G.P. | Method and apparatus for managing account receivables |
| CN102136089A (en) * | 2010-01-21 | 2011-07-27 | 金蝶软件（中国）有限公司 | Group interdepartmental account checking method and system |
| CN105550842A (en) * | 2015-12-11 | 2016-05-04 | 苏州功路驿站网络科技有限公司 | Logistics multi-supplier settlement management method |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20020120550A1 (en) * | 2001-02-26 | 2002-08-29 | Yang Chen-Shi | Computer online trading method for integrating sale and purchase processes and a system for the same |
| TW200508926A (en) * | 2003-08-27 | 2005-03-01 | Hon Hai Prec Ind Co Ltd | Sales reconciling system and method |
-
2020
- 2020-03-09 CN CN202010158084.7A patent/CN111402020B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7177828B1 (en) * | 2000-05-02 | 2007-02-13 | General Electric Canada Equipment Finance G.P. | Method and apparatus for managing account receivables |
| CN102136089A (en) * | 2010-01-21 | 2011-07-27 | 金蝶软件（中国）有限公司 | Group interdepartmental account checking method and system |
| CN105550842A (en) * | 2015-12-11 | 2016-05-04 | 苏州功路驿站网络科技有限公司 | Logistics multi-supplier settlement management method |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111402020A (en) | 2020-07-10 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11361281B2 (en) | Methods and systems for expense management | |
| US7970671B2 (en) | Automated transaction processing system and approach with currency conversion | |
| US8484131B2 (en) | Methods and systems for processing a financial transaction | |
| CN111402020B (en) | Enterprise account-receiving/paying automatic checking system | |
| CN113888298A (en) | Supply chain financial industry and finance integrated processing system and method | |
| JP2009098986A (en) | Electronic receivables mediating system | |
| US8249396B2 (en) | System and methods for handling financial document returns and processing exceptions | |
| JP2001243403A (en) | System and method for payment | |
| KR20020032240A (en) | The automatic processing system for account using value added network and the method for the processing | |
| JP4282882B2 (en) | Spending management system, spending management method, and storage medium | |
| CN111028026A (en) | Invoice matching method and system | |
| US20060184433A1 (en) | Method or application for generating postings based on transformation rules and posting classes | |
| KR100826667B1 (en) | Tenant management system | |
| CN115205000B (en) | Account checking method, account checking terminal and account checking system | |
| AU2004101029A4 (en) | Invoicing method and system | |
| CN117272957A (en) | Financial certificate generation method and device, electronic equipment and storage medium | |
| JP2001338255A (en) | Billing and payment collation system | |
| JP2003022375A (en) | Payment processing system in convenience store for card user according to law compliance | |
| JP4780631B2 (en) | Billing data reception processing system | |
| Stone | The electronic payment industry: change barriers and success requirements from a market segments perspective | |
| CN104574042B (en) | A kind of more map information processing methods and system | |
| CN115526155A (en) | Industry and finance integrated data processing system and method | |
| CN116266330A (en) | Novel accounting and billing system and method with information enabling function | |
| CN116109367A (en) | Fine financial management system and method based on CRM | |
| JP2000276544A (en) | Bank center, and method for receiving cash supply request |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |