Non-electric charge income industry financial ticket collaborative management method and system
Through the collaborative management method and system of non-electricity income industry financial invoices, the problem of non-electricity income processing in the existing technology relying on offline manual operations, realizing the coordinated integration of the entire process of online processing of non-electricity income and business financial data, and improving the efficiency and controllability of data management.
Patent Information
- Application Number
- CN202411858351.6
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-12-17
- Publication Date
- 2025-04-11
- Estimated Expiration
- Not applicable · inactive patent
AI Technical Summary
The existing technology relies on offline manual operations in the invoice, certificate making, and reconciliation of non-electricity revenue, resulting in cumbersome and time-consuming data maintenance, and the lack of real-time coordination of business and financial data.
Provide a collaborative management method and system for non-electricity income industry financial invoices, and realize the in-depth integration of non-electricity income industry financial invoices through business management basics and invoice management. The system receives project information and invoice applications submitted by the business department, conducts review and invoice applications, and receives posting and reconciliation applications from the financial department to form relevant records and vouchers.
It has realized the online processing of non-electricity revenues in the entire process, connected business and financial connection points, and centralized and unified invoice issuance, certificate making, reconciliation and other operations, promoted the coordinated integration of business and financial data, and realized the full visual and controllable invoice status, revenue confirmation, and payment progress.
Smart Images

Figure CN119809544A_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the technical field of data analysis, and in particular to a method and system for collaborative management of non-electricity revenue business invoices. Background Art
[0002] At present, power companies mainly rely on offline manual operations in the processing of invoicing, certificate preparation, and reconciliation of non-electricity revenue. In order to meet the needs of daily management of non-electricity revenue receivables and filling in final accounts, financial personnel perform offline manual maintenance of data based on invoicing and collection. The statistical processing is cumbersome and time-consuming, which does not meet the requirements of lean accounting management. At the same time, during the entire business process, business data is not transmitted to finance in real time, and financial data cannot be reflected in the business in a timely and accurate manner, and business and financial data are not effectively connected. Summary of the invention
[0003] In view of the problems existing in the above-mentioned prior art, the present invention provides a method and system for collaborative management of non-electricity revenue business and financial invoices, which takes business management as the basis and invoice management as the main line to achieve deep integration of non-electricity revenue business and financial invoices. The technical solution is as follows:
[0004] In a first aspect, a method for collaborative management of non-electricity revenue business and financial invoices is provided, the method comprising the following steps:
[0005] Receive business project information, contract information and project contract document attachments submitted by the business department. Project contract information includes project name, project type, project start and end information, business time node, payment time node and payer;
[0006] Compare and review the submitted project contract information and the project contract document attachments, and store the submitted project contract information to form a business project database after confirming that it is correct;
[0007] Receive the invoicing application submitted by the business department, which is filled out online by the business handling personnel of the business department;
[0008] Compare and review the invoicing application information with the project contract information in the business project database. After confirming that the submitted invoicing application information is correct, call the invoicing system to issue invoices, obtain invoices, and form an invoice pool.
[0009] Receive posting applications from the finance department, post the invoices selected by the user based on the invoice information, invoice documents, project contract information, and project contract document attachments, form posting records, and generate accounts receivable vouchers;
[0010] Receive reconciliation applications from the finance department, and reconcile and write off bank statements of non-electricity revenue by matching them with posting record information, forming reconciliation and write-off records and generating receipts;
[0011] Receive invoice inquiry applications submitted by business departments, including invoice issuance status, receivables voucher production status, and payment recovery status.
[0012] In some implementations, the comparative review based on the submitted project contract information and the project contract document attachments includes:
[0013] Represent each information of the project contract information in the form of a key-value pair, wherein the project contract information includes a plurality of key-value pair data representing multi-dimensional information of the project contract, and record the key data and value data of each information of the project contract information as first key data and corresponding first value data;
[0014] For each information of the project contract information, that is, the first key data and the corresponding first value data in each key-value pair data, the second key data matching the first key data is searched in the content of the project contract document attachment, and the second value data corresponding to the second key data is searched in the content of the project contract document attachment;
[0015] A comparative review is performed based on the first value data and the second value data to determine the consistency of the information.
[0016] In some implementations, the method for obtaining the second key data and the second value data includes:
[0017] Determine the template file type of the project contract document based on the project name and project type;
[0018] For the first key data and the first value data of the project contract information, determine the positions of the first key data and the first value data in the template file, record them as the first candidate area, and determine the position of the second key data in the project contract file based on the same area position of the first candidate area in the project contract file and the word-by-word or word-by-word matching of the text or words of the first key data in the text of the first candidate area;
[0019] Based on the location of the second key data in the project contract document, second value data is determined in a next region adjacent to the location of the second key data.
[0020] In some embodiments, the method for obtaining the second key data and the second value data further includes: matching the text or words in the first candidate area word by word or phrase by phrase based on the first key data, and when no second key data matching the first key data is found,
[0021] Based on the template document as a reference, review whether the outline content of the project contract document is consistent with the template document;
[0022] If they are consistent, the first candidate area is expanded as an updated first candidate area, the second key data position is determined in the updated first candidate area, and the text in the next adjacent area of the second key data position is used as the second value data corresponding to the second key data; the first value data corresponding to the first key data of the key-value pair of the project contract information and the second value data extracted from the project contract file are compared and analyzed for consistency to determine the comparison and review result;
[0023] If there is any inconsistency, it is determined that the project type information is filled in incorrectly or the project contract document format is incorrect.
[0024] In some implementations, the method for obtaining the second key data and the second value data includes:
[0025] Acquire semantic codes for the first key data and the corresponding first value data in a key-value pair in the project contract information, respectively, and determine the joint semantics of the first key data and the first value data in the key-value pair;
[0026] Perform text recognition on candidate areas or all areas of the project contract document to obtain regional text recognition results;
[0027] Based on the regional text of the project contract document, window semantic recognition, i.e., local semantic recognition, is performed in the form of a sliding window to obtain at least one matching window, wherein the text in the matching window has the maximum similarity with the joint semantics and is greater than a preset matching threshold;
[0028] Acquiring second value data corresponding to the second key data based on the text in the window in the matching window, including: selecting at least one keyword based on the text in the matching window and converting it into a second value data after it complies with the value data format rule;
[0029] The step of performing window semantic recognition, i.e., local semantic recognition, in the form of a sliding window to obtain at least one matching window includes:
[0030] Training phase:
[0031] Based on the key-value pair data of each information in the project contract information, namely the first key data and the first value data as sample data, based on the actual location area of the corresponding second key data and the second value data in the project contract file as annotation data;
[0032] The regional text of the project contract document is used to obtain multiple window regional texts in the form of a sliding window, and all the window regional texts, the first key data, and the first value data are input into a first preset model, and after semantic encoding and semantic decoding, the predicted position area of the second key data and the second value data is output;
[0033] Based on the error between the actual location area and the predicted location area, the parameters of the first preset model are updated in reverse order, and the training process of the first preset model is performed until the error meets the preset training stop condition, thereby obtaining the trained first preset model;
[0034] Matching window determination stage:
[0035] The regional text of the project contract document is used to obtain multiple window regional texts in the form of a sliding window, and all the window regional texts, the first key data, and the first value data are input into a first preset model to obtain an output result, wherein the output result represents the semantic similarity between each window regional text and the first key data and the first value data, and based on the output result, a window regional position having the maximum semantic similarity with the first key data and the first value data and greater than a preset matching threshold is obtained;
[0036] In some implementations, the invoice to be posted selected by the user is posted based on the invoice information, the invoice file, the project contract information, and the project contract file attachments to form a posting record and generate an A / R voucher, including:
[0037] Post the issued invoices corresponding to the uncertified records selected by the user from the issued invoice ledger page;
[0038] For invoices that need to be posted, extract preset multiple dimensional information based on invoice information and project contract information;
[0039] A posting record is formed based on the extracted dimensional information and an accounts receivable voucher number is automatically generated and added to the posting record. An accounts receivable voucher is generated based on part or all of the dimensional information in the posting record. The posting record carries an invoice document and a project contract document attachment.
[0040] In some embodiments, the bank statement of non-electricity income is reconciled and written off by matching with the posting record information to form a reconciliation and write-off record and generate a receipt voucher, including:
[0041] Based on the user's selection range, obtain the bank account record of the non-electricity income selected by the user;
[0042] Generate a bank receipt notice for non-electricity income based on the bank account receipt record selected by the user;
[0043] Based on the posted but unreconciled posting records, a reconciliation statement of accounts receivable is generated.
[0044] Based on the dimension information in the accounts receivable reconciliation table and the bank receipt notification, the reconciliation and write-off are completed, and a reconciliation and write-off record is generated. The dimension information contained in the accounts receivable reconciliation table and the bank receipt notification includes the customer name and the amount;
[0045] For bank receipt notices that have completed reconciliation and write-off, a receipt voucher is generated by combining the posting record information, accounts receivable reconciliation information, and reconciliation and write-off records.
[0046] The checking and matching process includes:
[0047] For the customer name information in a bank receipt notification on the bank receipt notification form, match the receivables reconciliation information with the same customer name information in the receivables reconciliation table;
[0048] In the case that there is only one matching receivables reconciliation information, determine the size of the amount in the bank account arrival notification information and the amount in the matching receivables reconciliation information. (1) If they are equal, mark the full write-off and the write-off amount after the matching receivables reconciliation information; and mark the written-off after the bank account arrival information. (2) If they are less than, mark the partial write-off and the write-off amount after the matching receivables reconciliation information; and mark the written-off after the bank account arrival information. (3) If they are greater than, mark the bank account arrival notification information and the matching receivables reconciliation information as abnormal and transfer them to manual review.
[0049] In the case where there are multiple matching accounts receivable reconciliation information, determine the size of the amount in the bank account arrival notification information and the total amount in the multiple matching accounts receivable reconciliation information. (1) If they are equal, then mark the full amount written off and the written off amount after each matching accounts receivable reconciliation information; at the same time, mark the bank account arrival information as written off. (2) If they are not equal, further match the additional information in the bank account arrival notification information with the additional information in the multiple matching accounts receivable reconciliation information. In the result of the further matching, determine the size of the amount in the bank account arrival notification information and the amount in the further matching accounts receivable reconciliation information. (21) If the amount in the bank account arrival notification information is equal to the cumulative amount of the amount in at least one account receivable reconciliation information, (22) If the amount in the bank account arrival notification information is inconsistent with the cumulative amount of any combination of at least one account receivable reconciliation information, determine the size of the amount in the bank account arrival notification information and the total amount in the further matched multiple account receivable reconciliation information; (221) If it is less than, mark the apportioned write-off and the apportioned write-off amount after each matched account receivable reconciliation information; and mark the apportioned write-off after the bank account arrival information; (222) If it is greater than, mark the bank account arrival notification information and the matched multiple account receivable reconciliation information as abnormal and transfer them to manual review;
[0050] In the case where the number of matching accounts receivable reconciliation information is zero, mark "not requiring write-off" after the one bank receipt notice information, generate a non-reconciliation identifier, and then enter the process of generating a receipt voucher.
[0051] In some embodiments, the further matching of the additional information in the bank receipt notice information with the additional information in the multiple matching accounts receivable reconciliation information includes:
[0052] Further match according to the project information, the project name, project content, and contract time in the contract information, determine the project and contract information corresponding to the bank receipt notice information and the invoice information corresponding to the project contract, and delete the accounts receivable reconciliation information that does not belong to the project and contract information corresponding to the bank receipt notice information.
[0053] In some embodiments, (21) includes:
[0054] Record the number of accounts receivable reconciliation information with the same customer name information matched in the accounts receivable reconciliation table according to the customer name information in one bank receipt notice information on the bank receipt notice as m1, that is, one bank receipt notice information matches m1 pieces of accounts receivable reconciliation information;
[0055] Record that when m1>1, among the results of further matching the additional information in the bank receipt notice information with the additional information in the m1 pieces of matching accounts receivable reconciliation information, there are m2 pieces of accounts receivable reconciliation information, m2<m1, that is, one bank receipt notice information matches m2 pieces of accounts receivable reconciliation information;
[0056] The method for determining the allocated write-off amount in (221) includes:
[0057] For the m2 pieces of matching accounts receivable reconciliation information, sort them based on the amount size in the reconciliation information;
[0058] Start writing off from the reconciliation information with a smaller amount until it satisfies that the cumulative amount in the 1st to kth reconciliation information is less than the amount in the bank receipt notice information and the cumulative amount in the 1st to k+1th reconciliation information is greater than the amount in the bank receipt notice information. Determine that the allocated write-off amount for the 1st to kth reconciliation information is the receivable amount of the 1st to kth reconciliation information, and the allocated write-off amount in the k+1th reconciliation information is the difference between the amount in the bank receipt notice information and the cumulative allocated write-off amount of the 1st to kth reconciliation information.
[0059] In a second aspect, a non-electricity revenue business-finance-invoice collaborative management system is provided, and the system includes:
[0060] The project contract information submission unit is used to receive the business project information, contract information and project contract document attachments submitted by the business department. The project contract information includes project name, project type, project start and end information, business time node, payment time node and payer;
[0061] The submitted information review unit is used to compare and review the submitted project contract information and the project contract document attachments, and store the submitted project contract information to form a business project database after confirming that it is correct;
[0062] The invoicing application unit is used to receive the invoicing application submitted by the business department, and the invoicing application is filled out online by the business handling personnel of the business department;
[0063] The application information review unit is used to compare and review the invoicing application information with the project contract information in the business project database. After confirming that the submitted invoicing application information is correct, the invoicing system is called to issue invoices, obtain invoices, and form an invoice pool;
[0064] The invoice posting unit is used to receive posting applications from the finance department, post the invoices selected by the user based on the invoice information, invoice documents, project contract information, and project contract document attachments, form posting records, and generate accounts receivable vouchers;
[0065] The collection reconciliation unit is used to receive reconciliation applications from the finance department. For bank statements of non-electricity revenue, it matches the bank statements with the posting record information, forms a reconciliation record and generates a collection voucher.
[0066] The invoicing inquiry unit is used to receive invoicing inquiry applications submitted by the business department, wherein the inquiry applications include inquiring about invoice issuance, receivable voucher production, and fund collection.
[0067] A method and system for collaborative management of business and financial invoices for non-electricity revenue of the present invention has the following beneficial effects: the present invention enables the business department to submit business project information, submit invoice application and query the progress of invoice posting, and at the same time enables the financial department to perform invoice management, invoice posting, collection reconciliation and other operations. Based on business management and with invoice management as the main line, the deep integration of business and financial invoices for non-electricity revenue is realized. First, the full process of non-electricity revenue is processed online. The business and financial connection points are connected in series to centrally unify the operations of invoicing, certificate making, reconciliation, query, and analysis of other business revenues. Second, it promotes the collaborative integration of business and financial data. Online real-time management of non-electricity revenue data makes the invoicing situation, revenue confirmation, and collection progress visible and controllable throughout the process, facilitating the interaction and sharing of business and financial data. BRIEF DESCRIPTION OF THE DRAWINGS
[0068] Figure 1 It is a flowchart of a method for collaborative management of non-electricity revenue business invoices in an embodiment of the present application;
[0069] Figure 2 It is a flowchart of a method for comparing and reviewing project contract information and project contract document attachments in an embodiment of the present application;
[0070] Figure 3 This is a method for obtaining the second key data and the second value data in an embodiment of the present application;
[0071] Figure 4 It is a structural diagram of a non-electricity revenue business and financial invoice collaborative management system in an embodiment of the present application. DETAILED DESCRIPTION
[0072] It should be understood that the specific embodiments described herein are only used to explain the present invention, and are not used to limit the present invention.
[0073] See also Figure 1 The embodiment of the present application provides a method for collaborative management of non-electricity revenue business invoices, including the following steps:
[0074] Step 1: Receive the business project information, contract information and project contract document attachments submitted by the business department. The project contract information includes project name, project type, project start and end information, business time node, payment time node and payer;
[0075] Step 2: Compare and review the submitted project contract information and the project contract document attachments, and store the submitted project contract information to form a business project database after confirming that it is correct;
[0076] Step 3: receiving the invoicing application submitted by the business department, wherein the invoicing application is filled out online by the business handling personnel of the business department;
[0077] Step 4: Compare and review the invoicing application information with the project contract information in the business project database. After confirming that the submitted invoicing application information is correct, call the invoicing system to issue the invoice, obtain the invoice, and form an invoice pool.
[0078] Step 5: Receive the posting application from the finance department, post the invoice selected by the user based on the invoice information, invoice file, project contract information, and project contract file attachments, form a posting record, and generate an A / R voucher;
[0079] Step 6: Receive the reconciliation application from the finance department, and reconcile and write off the bank statements of non-electricity revenue by matching them with the posting record information, form a reconciliation and write-off record, and generate a receipt;
[0080] Step 7, receiving the invoice inquiry application submitted by the business department, the inquiry application includes inquiry of invoice issuance status, receivable voucher production status, and fund collection status.
[0081] It can be understood that in the embodiment of the present application, a collaborative management system for business and financial invoices of non-electricity revenue is designed. On this system platform, business personnel with different permissions in the business department are supported to import, add, modify, deactivate and delete project contract information. After the business personnel log in to the system with their own account and password information, the data operations performed on the system will record the identity information of the business personnel; business personnel with different permissions in the business department are supported to apply for invoicing and query the invoice issuance status, the receivable voucher issuance status, and the funds recovery status; the invoice issuance status includes: the invoice issuance status includes the invoice application being initiated, the invoice has been issued, and the invoice has been written off; the receivable voucher issuance status, that is, the income recognition status includes: the receivable voucher has been issued, is being issued, is waiting to be issued, and has been written off; the funds recovery status includes: the receivables have not been recovered, have been written off, are partially written off, and do not need to be written off.
[0082] On the system side, managers can view project contract information, invoice application information, etc. submitted by different business personnel, making business data operations traceable.
[0083] The system platform supports financial personnel with different permissions in the financial department to perform posting and reconciliation operations, and query the posting and reconciliation status. After the financial personnel log in to the system with their own account and password information, they can post and reconcile on the system. The operating system will record the operator's identity information based on the login account and password.
[0084] On the system side, managers can view the posting data and reconciliation data of different financial personnel, making financial data operations traceable.
[0085] In the embodiment of the present application, based on business management and invoice management as the main line, the deep integration of non-electricity revenue business and finance invoices is realized. First, the full process of non-electricity revenue is processed online. The business and financial connection points are connected in series, and the operations of non-electricity revenue invoicing, certificate making, reconciliation, inquiry, analysis, etc. are centralized and unified. Second, the coordinated integration of business and financial data is promoted. Online real-time management of non-electricity revenue data makes the invoicing situation, revenue confirmation, and collection progress visible and controllable throughout the process, facilitating the interaction and sharing of business and financial data.
[0086] See also Figure 2 In step 2 above, the comparative review based on the submitted project contract information and the project contract document attachments includes the following steps:
[0087] Step 21, representing each information of the project contract information as a key-value pair, wherein the project contract information includes a plurality of key-value pair data representing multi-dimensional information of the project contract, and recording the key data and value data of each information of the project contract information as first key data and corresponding first value data;
[0088] Step 22, for each information of the project contract information, that is, the first key data and the corresponding first value data in each key-value pair data, searching the content of the project contract document attachment for the second key data matching the first key data, and searching the content of the project contract document attachment for the second value data corresponding to the second key data;
[0089] Step 23: Compare and review the first value data and the second value data to determine the consistency of the information.
[0090] In one implementation, the method for obtaining the second key data and the second value data in step 22 above includes the following steps:
[0091] Step 2201, determining the template file type of the project contract document based on the project name and project type;
[0092] Step 2202, for the first key data and the first value data of the project contract information, determine the positions of the first key data and the first value data in the template file, record them as the first candidate region, and determine the position of the second key data in the project contract file based on the same region position of the first candidate region in the project contract file and the word-by-word or word-by-word matching of the text or words of the first key data in the text of the first candidate region;
[0093] Step 2203, based on the location of the second key data in the project contract file, determine the second value data in the next area adjacent to the location of the second key data.
[0094] Furthermore, the method for obtaining the second key data and the second value data further includes: matching the text or words in the first candidate area based on the first key data word by word or phrase by phrase, and when no second key data matching the first key data is found,
[0095] Step 2204, based on the template file as a reference, review whether the outline content of the project contract document is consistent with the template file;
[0096] Step 2205: if they are consistent, then the first candidate area is expanded as an updated first candidate area, the second key data position is determined in the updated first candidate area, and the text in the next adjacent area of the second key data position is used as the second value data corresponding to the second key data; the first value data corresponding to the first key data of the key-value pair of the project contract information and the second value data extracted from the project contract file are compared and analyzed for consistency, and a comparison and review result is determined;
[0097] If there is any inconsistency, it is determined that the project type information is filled in incorrectly or the project contract document format is incorrect.
[0098] In the embodiment of the present application, considering that in possible application scenarios, the project contract documents of the unit all use template files, and different types of projects and corresponding contracts will have different template texts. Based on the template text, the approximate location of different project contract information on the project contract document can be basically determined, and then text recognition and project contract information extraction can be performed based on the location. By means of template files, the location range for searching for a certain information on the project contract document can be effectively reduced, and the efficiency of information extraction can be improved. The above-mentioned word-by-word or word-by-word matching of the text or words based on the first key data in the text in the first candidate area can determine the location of the second key data in the project contract file based on the area in the first candidate area where the matching positions of the words or words with the first key data are densely distributed.
[0099] In the implementation method of information extraction based on template file matching, the embodiment of the present application also considers the situation where there are differences in the positions of different information areas between the template file and the actual project contract file, and considers whether the outline content of the project contract file is consistent with the template file. If not, it prompts the user that the format of the project contract file uploaded is inconsistent with the template.
[0100] See also Figure 3 In another embodiment, the second key data and the second value data are obtained in a manner not based on template file matching. The method for obtaining the second key data and the second value data includes the following steps:
[0101] Step 2211, obtaining semantic codes for the first key data and the corresponding first value data in a key-value pair in the project contract information, and determining the joint semantics of the first key data and the first value data in the key-value pair;
[0102] Step 2212, performing text recognition on the candidate area or all areas of the project contract document to obtain the regional text recognition result;
[0103] Step 2213, based on the regional text of the project contract document, window semantic recognition, i.e., local semantic recognition, is performed in a sliding window form to obtain at least one matching window, wherein the text in the matching window has the maximum similarity with the joint semantics and is greater than a preset matching threshold;
[0104] Step 2214: Obtain second value data corresponding to the second key data based on the text in the window within the matching window.
[0105] In an embodiment of the present application, based on the joint semantics of the known first key data and the first value data, the project contract document text is searched for areas where the second value data may exist. Compared with a method of searching the project contract document text for areas where the corresponding matching second key data is located based solely on the semantics of the first key data, the accuracy of the search results is improved. The search and matching is performed based on the joint semantics of the first key data and the first value data, which improves the semantic refinement of the reference text, thereby improving the efficiency and accuracy of searching for matching text (i.e., the second value data) in the project contract document text.
[0106] In one implementation, in the above step 2213, window semantic recognition, i.e., local semantic recognition, is performed in a sliding window form to obtain at least one matching window, including:
[0107] Training phase:
[0108] Step 22131, based on the key-value pair data of each information in the project contract information, namely the first key data and the first value data as sample data, based on the actual location area of the corresponding second key data and the second value data in the project contract file as annotation data;
[0109] Step 22132, obtaining multiple window area texts from the regional text of the project contract document in the form of a sliding window, inputting all the window area texts, the first key data, and the first value data into the first preset model, and outputting the predicted position area of the second key data and the second value data after semantic encoding and semantic decoding;
[0110] Step 22133: based on the error between the actual location area and the predicted location area, reversely update the parameters of the first preset model, perform a training process for the first preset model, until the error meets a preset training stop condition, and obtain a trained first preset model;
[0111] Matching window determination stage:
[0112] Step 22134, obtaining multiple window area texts from the area text of the project contract document in a sliding window form, inputting all the window area texts, the first key data, and the first value data into a first preset model, obtaining an output result, wherein the output result represents the semantic similarity between each window area text and the first key data and the first value data, and obtaining a window area position having the maximum semantic similarity with the first key data and the first value data and greater than a preset matching threshold based on the output result;
[0113] In one implementation, the first preset model is implemented based on a transform model, and the method for processing input data by the first preset model includes the following steps:
[0114] The first key data and the first value data are segmented and embedded into a first encoder based on a transform model; at the same time, the text in each window area is segmented and embedded into a second encoder based on a transform model, wherein the encoder includes a multi-head self-attention layer and a feedforward neural network layer;
[0115] Based on the output of the first encoder, i.e., the encoded output X of the first key data and the first value data, and the output of the second encoder, i.e., the encoded output Y of the text in the window area, the attention mechanism module based on the transform model is input, and the Q matrix is obtained based on the output of the first encoder, Q=X*Wq, and the K and V matrices are obtained based on the output of the second encoder, K=Y*Wk, V=Y*Wv, where Wq, Wk, and Wv are linear mapping matrices. Calculate the semantic similarity between the text in each window area and the first key data and the first value data, where d is the dimension of the K matrix.
[0116] In an embodiment of the present application, two encoder modules based on the transform model are used to encode the first key data, the first value data, and the text in the window area, respectively. The encoder module based on the transform model contains a multi-head self-attention layer to fully exploit the front-to-back dependency relationship containing position information of the input sequence. Moreover, the input first key data and the first value data are spliced into an input sequence, and the encoder based on the transform model is used to realize the semantic fusion of the first key data and the first value data, and the first key data and the first value data are merged into an input sequence. The first key data and the first value data are encoded and processed by the encoder based on the transform model in a sequence, so that the encoder can realize the overall encoding and semantic understanding of the first key data and the first value data, and improve the model's understanding of the intention of the search target in the project contract document. Further, the output content of the two encoders is input through an attention mechanism module based on the transform model. The attention mechanism module simultaneously inputs the encoding sequence of the first key data and the first value data and the encoding sequence of the text in the window area, and through QK T The calculation obtains the correlation relationship between the two input sequences, and by applying the correlation relationship to the V matrix, the text in each window area is dynamically focused on, and the semantic similarity representation of each window area text and the first key data and the first value data is output.
[0117] In one embodiment, in the above step 2214, obtaining the second value data corresponding to the second key data in the matching window based on the text in the window includes: selecting at least one keyword based on the text in the matching window and converting it into a value data format rule as the second value data;
[0118] It can be understood that the project contract information submitted by the business department, such as project time, contract signing time, business time node, etc., its corresponding value data are not sentence texts, but simple short words. In this application, after determining the location where the second value data may exist, that is, the matching window location, the answer to the project contract information is found in the text text in the matching window, which can be a date, a company name, etc. For the project files and contract files in the embodiment of the present application, unlike articles, news and other texts that contain answers and other irrelevant sentence descriptions in a paragraph of text, based on the attribute characteristics of project files and contract files, after finding the matching window, the text in the matching window is basically used to represent the answer content, that is, the second value data. For example, based on the payment method, payment date, payment amount, etc. as the first key data, the window text matched in the project contract text can be, for example, "
[0119] 2. Payment Method
[0120] Party B shall pay Party A a down payment of RMB __ (in capital letters: __) on the date of signing this contract.
[0121] The remaining amount of RMB__ (in capital letters:__) shall be paid by Party B to Party A in installments in the following manner:
[0122] Installment period: __ months;
[0123] Monthly payment amount: __ yuan;
[0124] Payment date: before __ day of each month;
[0125] Party B shall remit each installment of payment to the account designated by Party A (Bank:, Account Number:).”
[0126] There is basically no other statement description irrelevant to the first key data in the window text. For this application, after determining the matching window area, the second value data can be obtained based on keyword extraction and appropriate adjustment of the text in the window area.
[0127] Specifically, in the above step 2214, obtaining the second value data corresponding to the second key data based on the text in the window in the matching window includes the following steps:
[0128] Segment the words based on the window text, extract keywords, and obtain the categories of the keywords; the keywords represent important information of the project contract, including words representing time, amount, customer name, location, and time limit;
[0129] Based on the correlation analysis between the first key data and the keywords, the keywords associated with the first key data are screened and the second value data is obtained through combination and expression conversion.
[0130] Among them, keywords associated with the first key data are screened, combined, and their expressions are transformed to obtain the second value data. It can be understood that the screened keywords may be one or more. For example, "before xxx date xxx month xxx year", here there are two keywords, one is the date and the other is "before...". After transformation, it can be "<xxx date xxx month xxx year". For the relevance analysis, for example, if the key data represents time, then the corresponding keywords associated with the first key data should also represent time descriptions. For example, if the key data represents the payment time, then the corresponding keywords associated with the first key data should also represent the combined semantics of "payment" and "time".
[0131] In one implementation, the project contract information in step 1 above includes the start and end time of the project contract, the contract signing time, and the time nodes of the contract payment deadline; in step 2, the comparative review based on the submitted project contract information and the project contract file attachments includes: comparing and reviewing the time node information of the contract payment deadline submitted by the user of the business department with the time node information extracted from the project contract file attachments.
[0132] Among them: when extracting the time node information of the contract payment deadline from the project contract file attachments, that is, when the time node of the contract payment deadline is used as the first key data, after obtaining the matching window, obtaining the second value data corresponding to the second key data based on the text within the matching window includes:
[0133] Performing word segmentation on the window text, extracting keywords, and obtaining the categories of the keywords; the keywords represent important information of the project contract, including words representing time, amount, and time limit.
[0134] Based on whether there is "installment" or "installment payment" or multiple keywords representing "amount" in the keywords, if so, it is determined as installment payment; continue to obtain the payment time node and payment amount for each installment; if not, it is determined as full payment, and continue to obtain the payment time node and payment amount for full payment.
[0135] In the embodiment of the present application, in the project contract information, the agreed way of extracting the contract payment time is included to facilitate clarifying each payment time node of the contract. When reconciling the received payments later, it can also be reviewed whether the received payment arrival time is consistent with the contract agreement time. If not, it may be necessary to further consider the situation of liquidated damages payment. Moreover, extracting the installment payment method of the project contract in the early stage also provides a basis for the separate verification during the subsequent reconciliation of received payments.
[0136] In one embodiment, in the above step 5, posting is performed based on the invoice information, invoice file, project contract information, and project contract file attachments for the invoice to be posted selected by the user to form a posting record and generate an accounts receivable voucher, including the following steps:
[0137] Step 51, posting the issued invoice corresponding to the uncertified record selected by the user from the issued invoice ledger page;
[0138] Step 52: for the invoice that needs to be posted, extract the preset multiple dimensional information based on the invoice information and the project contract information;
[0139] Step 53, forming a posting record based on the extracted dimensional information and automatically generating an A / R voucher number and adding it to the posting record, generating an A / R voucher based on part or all of the dimensional information in the posting record, and the posting record carries an invoice document and a project contract document attachment.
[0140] In one embodiment, in the above step 6, for the bank statement of non-electricity fee income, reconciliation and cancellation are performed by matching with the posting record information to form a reconciliation and cancellation record and generate a receipt voucher, including:
[0141] Step 61, based on the user's selection range, obtaining the bank account record of the non-electricity bill income selected by the user;
[0142] Step 62, generating a bank receipt notification of non-electricity fee income based on the bank account receipt record selected by the user;
[0143] Step 63: Generate a reconciliation statement of accounts receivable based on the posted but unreconciled posting records.
[0144] Step 64, performing a check and match based on the dimension information in the accounts receivable reconciliation table and the bank receipt notification, completing the reconciliation and write-off, and generating a reconciliation and write-off record, wherein the dimension information contained in the accounts receivable reconciliation table and the bank receipt notification includes the customer name and the amount;
[0145] Step 65, for the bank receipt notice that has been reconciled and written off, generate a receipt voucher by combining the posting record information, accounts receivable reconciliation information, and reconciliation and writing off records.
[0146] Specifically, the checking and matching process in step 64 includes:
[0147] Step 641, for a customer name in a bank account arrival notification on the bank account arrival notification form, match the receivables reconciliation information with the same customer name in the receivables reconciliation table;
[0148] Step 642, when there is only one matching receivables reconciliation information, determine the size of the amount in the bank account arrival notification information and the amount in the matching receivables reconciliation information. (1) If they are equal, then mark the full write-off and the write-off amount after the matching receivables reconciliation information; and mark the written-off after the bank account arrival information. (2) If they are less than, then mark the partial write-off and the write-off amount after the matching receivables reconciliation information; and mark the written-off after the bank account arrival information. (3) If they are greater than, then mark the bank account arrival notification information and the matching receivables reconciliation information as abnormal and transfer them to manual review.
[0149] Step 643, when there are multiple matching accounts receivable reconciliation information, determine the size of the amount in the bank account arrival notification information and the total amount in the multiple matching accounts receivable reconciliation information, (1) if they are equal, then mark the full amount written off and the written off amount after each matching accounts receivable reconciliation information; at the same time, mark the bank account arrival information as written off; (2) if they are not equal, then further match the additional information in the bank account arrival notification information with the additional information in the multiple matching accounts receivable reconciliation information, and in the result of the further matching, determine the size of the amount in the bank account arrival notification information and the amount in the further matching accounts receivable reconciliation information, (21) if the amount in the bank account arrival notification information is equal to the amount in at least one account receivable reconciliation information, If the cumulative amounts are consistent, then mark the full write-off and the write-off amount after at least one receivables reconciliation information that forms the consistent cumulative amount; and at the same time mark the write-off after the bank arrival information; (22) If the amount in the bank arrival notification information is inconsistent with the cumulative amount of any at least one receivables reconciliation information combination, determine the size of the amount in the bank arrival notification information and the total amount in the further matched multiple receivables reconciliation information; (221) If it is less than, then mark the apportioned write-off and the apportioned write-off amount after each matched receivables reconciliation information; and at the same time mark the write-off after the bank arrival information; (222) If it is greater than, then mark the bank arrival notification information and the matched multiple receivables reconciliation information as abnormal and transfer them to manual review;
[0150] Step 644, when there are zero matching accounts receivable reconciliation information, mark the bank account arrival notification information as not requiring cancellation, generate a no-reconciliation indicator, and then enter the receipt voucher generation process.
[0151] It should be noted that in (21), it includes: if the amount in the bank account arrival notification information is consistent with the amounts in multiple reconciliation information of the matching multiple accounts receivable reconciliation information, then select one reconciliation information with the same amount for cancellation, mark the system automatically cancel after one account receivable reconciliation information, and mark the full cancellation and cancellation amount. If the amount in the bank account arrival notification information is consistent with the amount in only one reconciliation information of the matching multiple accounts receivable reconciliation information, then cancel only the one reconciliation information with the same amount, mark the system automatically cancel after one account receivable reconciliation information, and mark the full cancellation and cancellation amount.
[0152] In (21), it also includes: if the amount in the bank account arrival notification information is consistent with the cumulative amount of the amounts in all the matched accounts receivable reconciliation information, then after each account receivable reconciliation information of all the matched accounts receivable reconciliation information, mark the system automatically write-off, and mark the full write-off and the write-off amount; at the same time, mark the said bank account arrival information as written off;
[0153] In the embodiment of the present application, a check and match is automatically performed based on the dimensional information in the accounts receivable reconciliation table and the bank arrival notification form, the reconciliation and cancellation is completed, and a reconciliation and cancellation record is generated. In case of anomalies that cannot be automatically checked and matched, manual reconciliation and review are performed, which improves the reconciliation efficiency and reduces the workload of manual reconciliation.
[0154] When automatically checking and matching the dimensional information in the accounts receivable reconciliation table and the bank arrival notice, a preliminary match is first performed based on the customer name, which is divided into two situations: there is only one account receivable information matching the bank arrival notice and there are multiple accounts receivable information matching the bank arrival notice. For the situation where the number of matches is one, full write-off and partial write-off are included. For the situation where the number of matches is multiple, the cumulative amount is first matched with the amount of the bank arrival notice. If they are consistent, it is determined that the multiple matched accounts receivable information can be written off. If they are inconsistent, further detailed matching is required. Based on the detailed matching results, the amount of the matching accounts receivable information is compared and analyzed with the amount of the bank arrival notice to verify whether it can be fully written off or partially written off and confirm the partial write-off amount.
[0155] In one embodiment, in the above (2), the additional information in the bank arrival notification information is further matched with the additional information in the matching multiple accounts receivable reconciliation information, including: further matching according to the project name, project content, and contract time in the project information and contract information, determining the project and contract information corresponding to the bank arrival notification information and the invoice information corresponding to the project contract, and deleting the accounts receivable reconciliation information that does not belong to the project and contract information corresponding to the bank arrival notification information.
[0156] In an embodiment of the present application, it is recorded that according to the customer name information in a bank receipt notice information on the bank receipt notice, the number of accounts receivable reconciliation information with the same customer name information matched in the accounts receivable reconciliation statement is m1, that is, one bank receipt notice information matches m1 pieces of accounts receivable reconciliation information;
[0157] It is recorded that when m1 > 1, the result of further matching the additional information in the bank receipt notice information with the additional information in the m1 pieces of accounts receivable reconciliation information that are matched includes m2 pieces of accounts receivable reconciliation information, m2 < m1, that is, one bank receipt notice information matches m2 pieces of accounts receivable reconciliation information;
[0158] In (21) above, it includes:
[0159] For the analysis of the amount in each piece of accounts receivable reconciliation information among the m2 pieces of accounts receivable reconciliation information that are matched, only the amount of one piece of reconciliation information is consistent with the amount in the bank receipt notice information or the amounts of multiple pieces of reconciliation information are all consistent with the amount in the bank receipt notice information; for the case where there are multiple pieces, one of the reconciliation information is selected for write-off marking;
[0160] For the analysis of the combination of any two or more pieces of accounts receivable reconciliation information among the m2 pieces of accounts receivable reconciliation information that are matched, only the cumulative amount of one combination is consistent with the amount in the bank receipt notice information or the cumulative amounts of multiple combinations are all consistent with the amount in the bank receipt notice information; for the case where there are multiple combinations, each piece of accounts receivable reconciliation information in one of the combinations is selected for write-off marking.
[0161] In one implementation manner, in (21) above, it includes:
[0162] It is recorded that according to the customer name information in a bank receipt notice information on the bank receipt notice, the number of accounts receivable reconciliation information with the same customer name information matched in the accounts receivable reconciliation statement is m1, that is, one bank receipt notice information matches m1 pieces of accounts receivable reconciliation information;
[0163] It is recorded that when m1 > 1, the result of further matching the additional information in the bank receipt notice information with the additional information in the m1 pieces of accounts receivable reconciliation information that are matched includes m2 pieces of accounts receivable reconciliation information, m2 < m1, that is, one bank receipt notice information matches m2 pieces of accounts receivable reconciliation information;
[0164] The method for determining the allocated write-off amount in (221) includes:
[0165] For the m2 pieces of accounts receivable reconciliation information that are matched, sort them based on the amount size in the reconciliation information;
[0166] Start writing off from the reconciliation information with the smaller amount until the cumulative amount in the reconciliation information from 1 to k is less than the amount in the bank arrival notification information and the cumulative amount in the reconciliation information from 1 to k+1 is greater than the amount in the bank arrival notification information. In this case, the allocated write-off amount of the reconciliation information from 1 to k is determined to be the receivable amount of the reconciliation information from 1 to k, and the allocated write-off amount in the k+1 reconciliation information is the difference between the amount in the bank arrival notification information and the cumulative allocated write-off amount of the reconciliation information from 1 to k.
[0167] In the embodiment of the present application, when amortizing and writing off, writing off is first performed based on small-amount receivables to reduce the workload for subsequent reconciliation and writing off.
[0168] See also Figure 4 The embodiment of the present application provides a non-electricity revenue business and financial invoice collaborative management system, which includes:
[0169] The project contract information submission unit is used to receive the business project information, contract information and project contract document attachments submitted by the business department. The project contract information includes project name, project type, project start and end information, business time node, payment time node and payer;
[0170] The submitted information review unit is used to compare and review the submitted project contract information and the project contract document attachments, and store the submitted project contract information to form a business project database after confirming that it is correct;
[0171] The invoicing application unit is used to receive the invoicing application submitted by the business department, and the invoicing application is filled out online by the business handling personnel of the business department;
[0172] The application information review unit is used to compare and review the invoicing application information with the project contract information in the business project database. After confirming that the submitted invoicing application information is correct, the invoicing system is called to issue invoices, obtain invoices, and form an invoice pool;
[0173] The invoice posting unit is used to receive posting applications from the finance department, post the invoices selected by the user based on the invoice information, invoice documents, project contract information, and project contract document attachments, form posting records, and generate accounts receivable vouchers;
[0174] The collection reconciliation unit is used to receive reconciliation applications from the finance department. For bank statements of non-electricity revenue, it matches the bank statements with the posting record information, forms a reconciliation record and generates a collection voucher.
[0175] The invoicing inquiry unit is used to receive invoicing inquiry applications submitted by the business department, wherein the inquiry applications include inquiring about invoice issuance, receivable voucher production, and fund collection.
[0176] For the specific limitations of the above-mentioned non-electricity revenue business and financial invoice collaborative management system, please refer to the limitations of the non-electricity revenue business and financial invoice collaborative management method above, which will not be repeated here. Each unit in the above-mentioned non-electricity revenue business and financial invoice collaborative management system can be implemented in whole or in part through software, hardware and a combination thereof. The above-mentioned units can be embedded in or independent of the processor in the computer device in the form of hardware, or can be stored in the memory of the computer device in the form of software, so that the processor can call and execute the operations corresponding to the above-mentioned units.
[0177] The present invention is not limited to the above-mentioned specific implementation modes. Various changes made by ordinary technicians in this field based on the above-mentioned concepts without creative work are all within the protection scope of the present invention.
Claims
1. A method for collaborative management of non-electricity revenue business invoices, characterized in that: The steps include: Receive business project information, contract information and project contract document attachments submitted by the business department. Project contract information includes project name, project type, project start and end information, business time node, payment time node and payer; Compare and review the submitted project contract information and the project contract document attachments, and store the submitted project contract information to form a business project database after confirming that it is correct; Receive the invoicing application submitted by the business department, which is filled out online by the business handling personnel of the business department; Compare and review the invoicing application information with the project contract information in the business project database. After confirming that the submitted invoicing application information is correct, call the invoicing system to issue invoices, obtain invoices, and form an invoice pool. Receive posting applications from the finance department, post the invoices selected by the user based on the invoice information, invoice documents, project contract information, and project contract document attachments, form posting records, and generate accounts receivable vouchers; Receive reconciliation applications from the finance department, and reconcile and write off bank statements of non-electricity revenue by matching them with posting record information, forming reconciliation and write-off records and generating receipts; Receive invoice inquiry applications submitted by business departments, including invoice issuance status, receivables voucher production status, and payment recovery status.
2. A method for collaborative management of non-electricity revenue business invoices according to claim 1, characterized in that: The comparative review based on the submitted project contract information and project contract document attachments includes: Represent each information of the project contract information in the form of a key-value pair, wherein the project contract information includes a plurality of key-value pair data representing multi-dimensional information of the project contract, and record the key data and value data of each information of the project contract information as first key data and corresponding first value data; For each information of the project contract information, that is, the first key data and the corresponding first value data in each key-value pair data, the second key data matching the first key data is searched in the content of the project contract document attachment, and the second value data corresponding to the second key data is searched in the content of the project contract document attachment; A comparative review is performed based on the first value data and the second value data to determine the consistency of the information.
3. A method for collaborative management of non-electricity revenue business invoices according to claim 2, characterized in that: The method for obtaining the second key data and the second value data includes: Determine the template file type of the project contract document based on the project name and project type; For the first key data and the first value data of the project contract information, the positions of the first key data and the first value data in the template file are determined, recorded as the first candidate area, and based on the same area position of the first candidate area in the project contract file, based on the word-by-word or word-by-word matching of the text or words of the first key data in the text of the first candidate area, the position of the second key data in the project contract file is determined; Based on the location of the second key data in the project contract document, second value data is determined in a next region adjacent to the location of the second key data.
4. A method for collaborative management of non-electricity revenue business invoices according to claim 3, characterized in that: The method for obtaining the second key data and the second value data further includes: matching the text or words in the first candidate area character by character or word by word based on the first key data, and when no second key data matching the first key data is found, Based on the template document as a reference, review whether the outline content of the project contract document is consistent with the template document; If they are consistent, the first candidate area is expanded as an updated first candidate area, the second key data position is determined in the updated first candidate area, and the text in the next adjacent area of the second key data position is used as the second value data corresponding to the second key data; the first value data corresponding to the first key data of the key-value pair of the project contract information and the second value data extracted from the project contract file are compared and analyzed for consistency to determine the comparison and review result; If there is any inconsistency, it is determined that the project type information is filled in incorrectly or the project contract document format is incorrect.
5. The method for collaborative management of non-electricity revenue business invoices according to claim 2 is characterized in that: The method for obtaining the second key data and the second value data includes: Acquire semantic codes for the first key data and the corresponding first value data in a key-value pair in the project contract information, respectively, and determine the joint semantics of the first key data and the first value data in the key-value pair; Perform text recognition on candidate areas or all areas of the project contract document to obtain regional text recognition results; Based on the regional text of the project contract document, window semantic recognition, i.e., local semantic recognition, is performed in the form of a sliding window to obtain at least one matching window, wherein the text in the matching window has the maximum similarity with the joint semantics and is greater than a preset matching threshold; Acquiring second value data corresponding to the second key data based on the text in the window in the matching window, including: selecting at least one keyword based on the text in the matching window and converting it into a second value data after it complies with the value data format rule; The step of performing window semantic recognition, i.e., local semantic recognition, in the form of a sliding window to obtain at least one matching window includes: Training phase: Based on the key-value pair data of each information in the project contract information, namely the first key data and the first value data as sample data, based on the actual location area of the corresponding second key data and the second value data in the project contract file as annotation data; The regional text of the project contract document is used to obtain multiple window regional texts in the form of a sliding window, and all the window regional texts, the first key data, and the first value data are input into a first preset model, and after semantic encoding and semantic decoding, the predicted position area of the second key data and the second value data is output; Based on the error between the actual location area and the predicted location area, the parameters of the first preset model are updated in reverse order, and the training process of the first preset model is performed until the error meets the preset training stop condition, thereby obtaining the trained first preset model; Matching window determination stage: The regional text of the project contract document is used to obtain multiple window area texts in the form of a sliding window, and all the window area texts, first key data, and first value data are input into a first preset model to obtain an output result, wherein the output result represents the semantic similarity between each window area text and the first key data and the first value data, and based on the output result, the window area position having the maximum semantic similarity with the first key data and the first value data and being greater than a preset matching threshold is obtained.
6. The method for collaborative management of non-electricity revenue business invoices according to claim 1, characterized in that: The invoice to be posted selected by the user is posted based on the invoice information, invoice file, project contract information, and project contract file attachments to form a posting record and generate an A / R voucher, including: Post the issued invoices corresponding to the uncertified records selected by the user from the issued invoice ledger page; For invoices that need to be posted, extract preset multiple dimensional information based on invoice information and project contract information; A posting record is formed based on the extracted dimensional information and an accounts receivable voucher number is automatically generated and added to the posting record. An accounts receivable voucher is generated based on part or all of the dimensional information in the posting record. The posting record carries an invoice document and a project contract document attachment.
7. The method for collaborative management of non-electricity revenue business invoices according to claim 1, characterized in that: The bank statements of non-electricity income are reconciled and written off by matching with the posting record information, forming a reconciliation and writing off record and generating a receipt voucher, including: Based on the user's selection range, obtain the bank account record of the non-electricity income selected by the user; Generate a bank receipt notice for non-electricity income based on the bank account receipt record selected by the user; Based on the posted but unreconciled posting records, a reconciliation statement of accounts receivable is generated. Based on the dimension information in the accounts receivable reconciliation table and the bank receipt notification, the reconciliation and write-off are completed, and a reconciliation and write-off record is generated. The dimension information contained in the accounts receivable reconciliation table and the bank receipt notification includes the customer name and the amount; For the bank receipt notice that has been completed for reconciliation and write-off, generate a receipt voucher by combining the posting record information, accounts receivable reconciliation information, and reconciliation and write-off records; The checking and matching process includes: For the customer name information in a bank receipt notification on the bank receipt notification form, match the receivables reconciliation information with the same customer name information in the receivables reconciliation table; In the case that there is only one matching receivables reconciliation information, determine the size of the amount in the bank account arrival notification information and the amount in the matching receivables reconciliation information. (1) If they are equal, mark the full write-off and the write-off amount after the matching receivables reconciliation information; and mark the written-off after the bank account arrival information. (2) If they are less than, mark the partial write-off and the write-off amount after the matching receivables reconciliation information; and mark the written-off after the bank account arrival information. (3) If they are greater than, mark the bank account arrival notification information and the matching receivables reconciliation information as abnormal and transfer them to manual review. In the case where there are multiple matching accounts receivable reconciliation information, compare the amount in the bank receipt notice information with the total amount in the multiple matching accounts receivable reconciliation information. (1) If they are equal, mark full write-off and write-off amount for each of the matching accounts receivable reconciliation information; at the same time, mark "written off" after the one bank receipt information. (2) If they are not equal, further match the additional information in the bank receipt notice information with the additional information in the multiple matching accounts receivable reconciliation information. In the result of the further match, compare the amount in the bank receipt notice information with the amount in the multiple further-matched accounts receivable reconciliation information. (21) If the amount in the bank receipt notice information is consistent with the cumulative amount of the amount in at least one accounts receivable reconciliation information, mark full write-off and write-off amount for at least one accounts receivable reconciliation information with consistent cumulative amount; at the same time, mark "written off" after the one bank receipt information. (22) If the amount in the bank receipt notice information is not consistent with the cumulative amount of any combination of at least one accounts receivable reconciliation information, compare the amount in the bank receipt notice information with the total amount in the multiple further-matched accounts receivable reconciliation information. (221) If it is less, mark pro rata write-off and pro rata write-off amount for each of the matching accounts receivable reconciliation information; at the same time, mark "written off" after the one bank receipt information. (222) If it is greater, mark the one bank receipt notice information and the multiple matching accounts receivable reconciliation information as abnormal and transfer them to manual review; In the case where there are zero matching accounts receivable reconciliation information, mark "no write-off required" after the one bank receipt notice information, generate a no-reconciliation required flag and then enter the process of generating a receipt voucher.
8. The method for collaborative management of non-electricity revenue business invoices according to claim 7 is characterized in that: The further matching of the additional information in the bank receipt notice information with the additional information in the multiple matching accounts receivable reconciliation information includes: Further match based on the project name, project content, and contract time in the project information and contract information to determine the project, contract information corresponding to the bank receipt notice information and the invoice information corresponding to the project contract, and delete the accounts receivable reconciliation information that does not belong to the project and contract information corresponding to the bank receipt notice information.
9. The method for collaborative management of non-electricity revenue business invoices according to claim 7, characterized in that: In (21), it includes: Record that the number of accounts receivable reconciliation information with the same customer name information matched in the accounts receivable reconciliation table according to the customer name information in one bank receipt notice information on the bank receipt notice is m1, that is, one bank receipt notice information matches m1 accounts receivable reconciliation information; Record that when m1 > 1, the result of further matching the additional information in the bank receipt notice information with the additional information in the m1 matching accounts receivable reconciliation information includes m2 accounts receivable reconciliation information, m2 < m1, that is, one bank receipt notice information matches m2 accounts receivable reconciliation information; The method for determining the pro rata write-off amount in (221) includes: For the m2 matching accounts receivable reconciliation information, sort them based on the amount size in the reconciliation information; Start writing off from the reconciliation information with the smaller amount until the cumulative amount in the reconciliation information from 1 to k is less than the amount in the bank arrival notification information and the cumulative amount in the reconciliation information from 1 to k+1 is greater than the amount in the bank arrival notification information. In this case, the allocated write-off amount of the reconciliation information from 1 to k is determined to be the receivable amount of the reconciliation information from 1 to k, and the allocated write-off amount in the k+1 reconciliation information is the difference between the amount in the bank arrival notification information and the cumulative allocated write-off amount of the reconciliation information from 1 to k.
10. A non-electricity revenue business invoice collaborative management system, characterized in that: include: The project contract information submission unit is used to receive the business project information, contract information and project contract document attachments submitted by the business department. The project contract information includes project name, project type, project start and end information, business time node, payment time node and payer; The submitted information review unit is used to compare and review the submitted project contract information and the project contract document attachments, and store the submitted project contract information to form a business project database after confirming that it is correct; The invoicing application unit is used to receive the invoicing application submitted by the business department, and the invoicing application is filled out online by the business handling personnel of the business department; The application information review unit is used to compare and review the invoicing application information with the project contract information in the business project database. After confirming that the submitted invoicing application information is correct, the invoicing system is called to issue invoices, obtain invoices, and form an invoice pool; The invoice posting unit is used to receive posting applications from the finance department, post the invoices selected by the user based on the invoice information, invoice documents, project contract information, and project contract document attachments, form posting records, and generate accounts receivable vouchers; The collection reconciliation unit is used to receive reconciliation applications from the finance department. For bank statements of non-electricity revenue, it matches the bank statements with the posting record information, forms a reconciliation record and generates a collection voucher. The invoicing inquiry unit is used to receive invoicing inquiry applications submitted by the business department, wherein the inquiry applications include inquiring about invoice issuance, receivable voucher production, and payment collection.
Citation Information
Patent Citations
Reconciliation data processing method and device
CN114416809A
Voucher generation method and device, computer equipment and storage medium
CN114648398A
Invoicing management method and device for improving processing efficiency, equipment and storage medium
CN115311029A
Intelligent auditing method and system for construction contract of construction project
CN117710160A
Funds transfer method and system including payment enabled invoices
US20080015982A1