Document receiving and sending method and system based on ERP system
By building a customer label matrix and dynamic priority division, the resource mismatch problem in the receipt and reception process of documents in the ERP system is solved, efficient document circulation and risk control are achieved, and the enterprise's supply chain collaboration efficiency and customer service capabilities are improved.
Patent Information
- Application Number
- CN202510566073.5
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-04-30
- Publication Date
- 2025-08-15
- Estimated Expiration
- Not applicable · inactive patent
AI Technical Summary
The traditional ERP system lacks in-depth exploration of customer historical document behavior during document receipt and reception, resulting in a mixture of high-risk orders and high-quality customer orders, serious resource mismatch, and lack of dynamic process adjustment mechanisms, resulting in a surge in operating costs.
By building a customer tag matrix, excellent tag information is generated based on customer historical document data analysis, combining priority coefficients and business weight calculations, document priority is dynamically divided, and differentiated processing and real-time synchronization are achieved through ERP workflow engine and message middleware to optimize tag rules and processing thresholds.
It has achieved efficient circulation of high-value businesses and early warning and control of risk orders, improved the efficiency of enterprise supply chain coordination and customer service response capabilities, and reduced operating costs.
Smart Images
Figure CN120494729A_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the technical field of document sending and receiving processing, and in particular to a document sending and receiving method and system based on an ERP system. Background Art
[0002] In traditional enterprise resource planning (ERP) system scenarios, document delivery and receipt, as a key hub connecting multiple departments such as procurement, production, sales, and finance, faces the following challenges:
[0003] Traditional ERP relies solely on basic customer profiles (such as name and address) for document distribution, lacking in-depth insights into historical customer document behavior (e.g., delivery and receipt delay rates, and high-frequency, unusual order types). When a customer's ability to fulfill their orders suddenly changes due to operational fluctuations (e.g., tight capital chains, supply chain restructuring), the system is unable to automatically identify risky customers and trigger differentiated processing mechanisms. This results in high-risk orders being mixed with those from high-quality customers within the standard process, creating a reverse resource utilization situation where "high-quality customers wait for approval while risky customers occupy the pipeline."
[0004] Traditional customer grading methods rely on subjective labeling by salespeople (e.g., "Class A customers" and "temporary customers"), lacking a unified data labeling system and quantitative assessment rules. When customers involve both urgent orders (e.g., expedited production orders) and regular orders, the lack of automated calculation of multi-dimensional indicators such as business urgency (e.g., the delivery deadline coefficient) and dollar weighting (e.g., the risk of advance payment for large orders) leads to frequent mismatches in manual scheduling, with urgent orders stuck at process nodes and regular orders wasting approval resources.
[0005] Traditional ERP document approval processes follow a fixed path (e.g., all orders must be countersigned at each level), without dynamically adjusting processes based on customer priorities and business characteristics. When urgent orders from high-value customers and regular orders from low-risk customers enter the system simultaneously, both are forced to share the same approval nodes and response timelines. This results in high-quality customers being lost due to lengthy processes, while low-value orders are subject to excessive management costs due to excessive intervention.
[0006] Therefore, it is necessary to provide a document sending and receiving method and system based on an ERP system to solve the above technical problems. Summary of the Invention
[0007] In order to solve the above technical problems, the present invention provides a document sending and receiving method and system based on the ERP system to solve the problems of the lack of static tags in the traditional document sending and receiving method, the mismatch caused by reliance on manual experience decision-making, and the surge in operating costs caused by resource mismatch.
[0008] The present invention provides a document sending and receiving method based on an ERP system, the sending and receiving method comprising the following steps:
[0009] Obtain and analyze each customer's historical document sending and receiving information, generate corresponding high-quality label information for each customer, embed decision-making keywords and phrases, and build a customer label matrix;
[0010] Based on the customer label matrix, assign a priority coefficient to each customer to obtain the priority coefficient of each customer;
[0011] Obtain the current business of each customer and assign a weight coefficient to each customer's business based on the preset threshold conditions;
[0012] Combine the priority coefficient of each customer and the weight coefficient assigned to each customer's business, and calculate the comprehensive weight of each customer through weighted summation;
[0013] Based on the comprehensive weight of each customer, the customer's documents are divided into high priority, medium priority and low priority, and differentiated processing is performed based on the current business of each customer to obtain the customer document processing results;
[0014] Approve the customer document processing results, synchronize the approval results to the ERP system immediately and provide feedback to complete the document data update.
[0015] Preferably, the specific steps of acquiring and analyzing each customer's historical document sending and receiving information, generating corresponding excellent label information for each customer, and embedding decision-making keywords and phrases to construct a customer label matrix include:
[0016] From the ERP system database, based on unique identification information such as customer ID or name, accurately extract historical document receipt and delivery data for each customer within a specified time period, including document delivery time, quantity, or delivery status;
[0017] Use data analysis tools to conduct multi-dimensional analysis of each customer's historical document delivery and receipt data. This multi-dimensional analysis includes analyzing the frequency of customer document delivery and receipt, calculating the average delivery and receipt cycle, and counting the delivery and receipt ratios of different document types.
[0018] Based on the results of multi-dimensional analysis, corresponding excellent label information is formulated for each customer. On the basis of the generated excellent label information, decision-making keywords are further embedded to construct a customer label matrix, where the excellent label information includes high-quality, general and risk.
[0019] Preferably, the specific steps of assigning a priority coefficient to each customer based on the customer label matrix and obtaining the priority coefficient of each customer include:
[0020] Priority coefficient rules are set based on the customer tag matrix, including: high-quality = 0.6, average = 0.3, and risky = 0.1. If a customer's recent document delays surge, the trigger coefficient is lowered by 0.1. Recent periods include the past week or the past month.
[0021] Based on the priority coefficient rules, priority coefficients are dynamically assigned to each customer, and a customer priority coefficient table is generated and written into the ERP database.
[0022] Preferably, the specific steps of obtaining the current business of each customer and allocating a weight coefficient to each customer business based on a preset threshold condition include:
[0023] Obtain the current business of each customer, including amount, urgency, and product type;
[0024] Two threshold conditions, amount threshold and urgency, are preset, and a weight coefficient is assigned to the current business of customers who meet the conditions.
[0025] Preferably, the formula for calculating the comprehensive weight of each customer by combining the priority coefficient of each customer and the weight coefficient allocated to each customer's business through weighted summation is: comprehensive weight = priority coefficient × 60% + business weight × 40%.
[0026] Preferably, the process of classifying each customer's documents into high priority, medium priority, and low priority according to the comprehensive weight of each customer, and performing differentiated processing based on each customer's current business, wherein the differentiated processing in the customer document processing result includes:
[0027] High priority: Trigger the automated fast track and reference the decision-making keywords in the customer tag matrix for enhanced execution; Medium priority: Enter the standard processing flow and perform manual or semi-automatic processing based on the prompt information in the tag matrix; Low priority: Temporarily queue or process according to default rules, and record the cause of the delay for optimization analysis.
[0028] Preferably, the steps of approving the customer document processing results and synchronizing the approval results to the ERP system and providing feedback to complete the document data update include:
[0029] Through the ERP workflow engine, high-priority documents are sent directly to supervisors for approval, and medium- and low-priority documents are countersigned as needed;
[0030] After approval is completed, ERP automatically updates the document status and notifies the finance and logistics modules through the message middleware;
[0031] Feedback processing time and abnormal events to the customer tag matrix.
[0032] A document sending and receiving system based on an ERP system, the sending and receiving system comprising:
[0033] The label construction module is used to obtain and analyze each customer's historical document sending and receiving information, generate corresponding high-quality label information for each customer, and embed decision-making keywords and phrases to build a customer label matrix;
[0034] A priority allocation module is used to allocate a priority coefficient to each customer based on the customer label matrix to obtain the priority coefficient of each customer;
[0035] The weight division module is used to obtain the current business of each customer and assign a weight coefficient to each customer's business based on the preset threshold conditions;
[0036] The weight calculation module is used to combine the priority coefficient of each customer and the weight coefficient assigned to each customer's business, and calculate the comprehensive weight of each customer through weighted summation;
[0037] The information processing module is used to classify each customer's documents into high priority, medium priority, and low priority according to the comprehensive weight of each customer, and perform differentiated processing based on the current business of each customer to obtain the customer document processing results;
[0038] The approval update module is used to approve the customer document processing results, and at the same time, synchronize the approval results to the ERP system in real time and provide feedback to complete the document data update.
[0039] Compared with related technologies, the document sending and receiving method and system based on the ERP system provided by the present invention has the following beneficial effects:
[0040] The present invention realizes in-depth classification and dynamic profiling of customers by accurately extracting and analyzing historical document data to construct a label matrix, and forms a comprehensive evaluation system by combining dynamic priority coefficient allocation with weighted calculation of business characteristics, and then implements differentiated response strategies of automated fast channel, semi-manual collaborative processing and elastic buffer queue for documents of different priorities. At the same time, it relies on ERP workflow engine and message middleware to open up the approval closed loop and synchronize data in real time, and finally continuously optimizes label rules and processing thresholds through abnormal event backtracking mechanism, which not only ensures the efficient flow of high-value business and early warning control of risky orders, but also drives the agile iteration of document sending and receiving process through full-link data precipitation and intelligent feedback, significantly improving the collaborative efficiency of enterprise supply chain and customer service response capability. BRIEF DESCRIPTION OF THE DRAWINGS
[0041] Figure 1 Schematic diagram of the flow of the document sending and receiving method based on the ERP system of the present invention;
[0042] Figure 2 This is a system block diagram of the document sending and receiving system based on the ERP system of the present invention. DETAILED DESCRIPTION
[0043] The present invention will be further described below with reference to the accompanying drawings and embodiments.
[0044] Example 1
[0045] like Figure 1 As shown, a document sending and receiving method based on an ERP system includes the following steps:
[0046] S1. Obtain and analyze each customer's historical document sending and receiving information, generate corresponding high-quality label information for each customer, embed decision-making keywords and phrases, and build a customer label matrix;
[0047] S2. Based on the customer label matrix, assign a priority coefficient to each customer to obtain the priority coefficient of each customer;
[0048] S3. Obtain the current business of each customer and assign a weight coefficient to each customer business based on a preset threshold condition;
[0049] S4. Calculate the comprehensive weight of each customer by combining the priority coefficient of each customer and the weight coefficient assigned to each customer's business through weighted summation;
[0050] S5. Classify each customer's documents into high priority, medium priority, and low priority based on their comprehensive weights. Perform differentiated processing based on each customer's current business, and obtain the customer document processing results.
[0051] S6. Approve the customer document processing results, and synchronize the approval results to the ERP system in real time and provide feedback to complete the document data update.
[0052] In the specific implementation process, the specific steps of step S1 include:
[0053] S101. From the database of the ERP system, based on unique identification information such as customer ID or name, accurately extract historical document receipt and delivery data for each customer within a specified time period, including the document's receipt and delivery time, quantity, or receipt and delivery status.
[0054] Specifically, in an ERP system, each customer has unique identification information, such as a customer ID or name. This unique identification information can be used to precisely locate and extract the customer's historical document delivery and receipt data for a specified time period from the database, including the delivery time, quantity, or delivery status of the documents. For example, when extracting a customer's historical document delivery and receipt data for the past three months, the system uses the customer ID as the search condition and searches the relevant database tables for all documents for that customer during that period. This information includes each document's delivery time, delivery time, quantity delivered, quantity received, and delivery status information, such as whether the document was successfully delivered or returned.
[0055] S102. Use data analysis tools to perform multi-dimensional analysis on the acquired historical document sending and receiving data of each customer. The multi-dimensional analysis includes analyzing the sending and receiving frequency of customer documents, calculating the average sending and receiving cycle, and counting the sending and receiving ratios of different types of documents.
[0056] Specifically, use data analysis tools to count the total number of times customers send and receive documents within a specified time period (one month or half a month), and divide the total number by the number of days in the time period to obtain the average daily number of document sending and receiving, so as to measure the customer's document sending and receiving activity; for each document, calculate the time interval from issuance to receipt, then add up the time intervals of all documents and divide it by the total number of documents to obtain the average sending and receiving cycle; finally, classify documents by type, such as purchase orders, sales invoices, shipping notices, etc., count the number of documents sent and received for each type respectively, and then calculate the proportion of the number of documents sent and received for each type to the total number of documents sent and received.
[0057] S103. Based on the results of multi-dimensional analysis, corresponding excellent label information is formulated for each customer. Based on the generated excellent label information, decision-making keywords are further embedded to construct a customer label matrix, where the excellent label information includes high-quality, general and risk.
[0058] Specifically, if a customer is active in terms of sending and receiving frequency, has a short average sending and receiving cycle, and has a reasonable ratio of sending and receiving different types of documents, indicating frequent business transactions and high processing efficiency, they are identified as high-quality customers and are labeled with a high-quality tag. If a customer's sending and receiving frequency, average sending and receiving cycle, and document sending and receiving ratio are average, with no obvious advantages or disadvantages, they are identified as average customers and are labeled with a general tag. If a customer has a low sending and receiving frequency (possibly indicating low business activity or partnership issues), a long average sending and receiving cycle (possibly indicating low processing efficiency), or an abnormal ratio of sending and receiving certain document types (e.g., a large number of documents being returned), they are identified as risky customers and are labeled with a risk tag. Based on the generated high-quality tag information, decision-making keywords are further embedded. Decision-making keywords can be set based on the characteristics of different tag types. For example, for high-quality customers, keywords such as "priority processing" and "more preferential treatment" can be set; for average customers, keywords such as "process according to normal procedures" and "pay attention to business changes" can be set; and for risky customers, keywords such as "enhanced monitoring" and "cautious cooperation" can be set. Build a customer tag matrix through these excellent tag information and decision-making keywords.
[0059] In the specific implementation process, the specific steps of step S2 include:
[0060] S201. Set priority coefficient rules based on the customer tag matrix, including: high quality = 0.6, general = 0.3, risk = 0.1; if the customer's recent document delays surge, the trigger coefficient is lowered by 0.1, where the recent period includes the past week or the past month.
[0061] Specifically, "recent period" is defined as the most recent week or month, as these two time periods can best reflect recent changes in a customer's business status. We continuously monitor the receipt and delivery of documents by customers during these two time periods, and count the number of document delays. If we detect a surge in document delays for a customer within the recent period, we trigger a coefficient reduction mechanism. The specific rule is: once the conditions for a surge in document delays are met, the customer's priority coefficient is adjusted up or down by 0.1 from the original level. This allows for timely response to changes in the customer's business status and prevents temporary customer business issues from impacting the smoothness of the overall document processing process.
[0062] In this embodiment, customer A is marked as "high-quality" in the customer label matrix. According to the basic priority coefficient setting rules, customer A's basic priority coefficient is 0.6, customer B is marked as "general", and its basic priority coefficient is 0.3, and customer C is marked as "risk", and its basic priority coefficient is 0.1. There is a customer D who was originally a "general" customer in the customer label matrix, with a basic priority coefficient of 0.3. System monitoring found that in the past week, out of the 20 documents that customer D should have received on time, 10 were delayed, and the delay rate reached 50%, which is a significant increase compared to the previous normal delay rate (such as 10%), meeting the conditions for a surge in document delays. At this time, the coefficient reduction mechanism is triggered, and customer D's priority coefficient is reduced from 0.3 to 0.2 (0.3-0.1=0.2).
[0063] S202. Based on the priority coefficient rule, dynamically assign a priority coefficient to each customer, and generate a customer priority coefficient table, and write it into the ERP database.
[0064] Specifically, each customer is judged and calculated one by one according to the priority coefficient rules set in step S201; for each customer, first determine its basic priority coefficient (based on the excellent label information in the customer label matrix), and then check whether the customer has a surge in document delays in the recent period. If so, the priority coefficient is lowered according to the rules; if not, the basic priority coefficient remains unchanged. In this way, each customer is dynamically assigned its currently applicable priority coefficient; after completing the dynamic allocation of priority coefficients for all customers, the system organizes this information into a customer priority coefficient table. The table contains fields such as customer ID or name, customer label information, basic priority coefficient, whether to trigger coefficient reduction, and the actually assigned priority coefficient.
[0065] In the specific implementation process, the specific steps of step S3 include:
[0066] S301. Obtain the current business of each customer, including amount, urgency, and product type.
[0067] Specifically, obtain the amount of each customer's current business: from the sales order, purchase order and other business document tables, based on the associated fields such as customer ID or business number, extract the transaction amount data involved in the customer's current business. For example, for sales business, obtain the total order amount from the sales order table; for purchase business, obtain the purchase amount from the purchase order table; obtain the urgency of each customer's current business: usually when a business document is created or entered, a field is set to identify the urgency of the business, such as "urgent", "expedited", "normal" and other options. The system reads this information directly from the corresponding field of the business document; obtain the product type in each customer's current business: obtain it from the associated records of the product information table and the business document. The product information table records the basic information of each product in detail, including product number, product name, product category, etc.
[0068] S302 , presetting two threshold conditions, namely, the amount threshold and the urgency level, and assigning a weight coefficient to the current business of the customer who meets the conditions.
[0069] Specifically, in this embodiment, the amount threshold is set to be divided into three intervals: the amount is less than 10,000 yuan as the low amount interval; the amount is between 10,000 yuan (inclusive) and 50,000 yuan as the medium amount interval; the amount is greater than 50,000 yuan (inclusive) as the high amount interval; the urgency is divided into three levels, and the threshold conditions are set accordingly. For example, "urgent" business is defined as high urgency, "expedited" business is defined as medium urgency, and "ordinary" business is defined as low urgency. For the amount weight coefficient, the low amount interval business weight coefficient can be set to 0.2, the medium amount interval business weight coefficient can be set to 0.5, and the high amount interval business weight coefficient can be set to 0.8; for the urgency weight coefficient, the low urgency business weight coefficient can be set to 0.1, the medium urgency business weight coefficient can be set to 0.3, and the high urgency business weight coefficient can be set to 0.6.
[0070] In the specific implementation process, in step S4, the calculation formula for the comprehensive weight of each customer is calculated by weighted summation: comprehensive weight = priority coefficient × 60% + business weight × 40%.
[0071] In the specific implementation process, the differentiation processing in step S5 includes:
[0072] High priority: Trigger the automated fast track and reference the decision-making keywords in the customer tag matrix for enhanced execution; Medium priority: Enter the standard processing flow and perform manual or semi-automatic processing based on the prompt information in the tag matrix; Low priority: Temporarily queue or process according to default rules, and record the cause of the delay for optimization analysis.
[0073] Specifically, when the ERP system determines a customer document is high-priority, it automatically separates the document from the regular business processing queue and transfers it to an automated fast-track channel specifically designed for high-priority documents. This channel bypasses some conventional approval nodes and waiting stages, such as reducing unnecessary intermediate review levels, and directly enters critical business processing. Furthermore, at each stage of the automated fast-track channel, the system reads the customer's decision-making key phrases corresponding to the customer in the customer tag matrix in real time. During the document processing process, these decision-making key phrases are automatically adjusted based on the decision-making key phrases. For example, in the inventory allocation stage, if the decision-making key phrase is "guarantee supply first," the system will automatically allocate the required goods from existing inventory to the high-priority document, even if this may affect the inventory allocation of other, less high-priority orders. In the logistics arrangement stage, if the key phrase is "special channel for urgent orders," the system will automatically select the fastest logistics method and transportation route and coordinate logistics resources in advance to ensure the fastest shipment of goods. Medium-priority documents are processed according to the company's pre-defined standard business processing process. This process includes a series of prescribed steps and stages, such as business acceptance, preliminary review, detailed review, business processing, and result feedback. Each link has clear responsibilities, processing deadlines, and operational specifications. Documents are passed to each processing node in sequence according to the process flow. Processors complete their tasks within the specified timeframe and report the results to the system, which then automatically passes the document to the next node. Low-priority documents are temporarily stored in a dedicated pending queue and are not immediately processed. Instead, they are batch-processed according to pre-set default rules, which include order processing from smallest to largest amount and from earliest to latest submission time.
[0074] In the specific implementation process, the specific steps of step S6 include:
[0075] S601. Through the ERP workflow engine, high-priority documents are sent directly to supervisors for approval, and medium-priority and low-priority documents are co-signed as needed.
[0076] Specifically, the engine automatically packages all relevant information of high-priority documents, including customer information, business details, key data in the processing process (such as the basis for calculating priority coefficients, business weights, etc.), the application of decision-making keywords, etc., into an approval package and pushes it directly to the supervisor's ERP system approval interface. During the push process, the system will remind supervisors through pop-up prompts, email notifications, and other methods that there are new high-priority documents that need to be approved, ensuring that supervisors can pay attention to and handle them in a timely manner. For medium-priority documents, the ERP workflow engine will analyze key factors such as the business type, amount involved, and urgency of the document, and determine the relevant departments and personnel who need to participate in the counter-signing based on the preset counter-signing rules in the system. For low-priority documents, the preset rules will determine whether counter-signing is required. If the low-priority document involves some special business (such as new product promotion, contract terms change, etc.), the business development department or legal department will need to participate in the counter-signing; if it is a regular, small-amount replenishment order, etc., the relevant business processing personnel only need to simply confirm it, and there is no need for a formal counter-signing process.
[0077] S602. After approval is complete, the ERP automatically updates the document status and notifies the finance and logistics modules via the messaging middleware. When the supervisor or co-signer completes the approval process, the ERP system receives the approval result in real time and automatically updates the document status from "pending approval" to the corresponding subsequent status based on the approval result. For example, if the approval is passed, the document status is updated to "approved, pending execution"; if the approval is rejected, the document status is updated to "failed, requiring revision." At the same time, key information such as the approver, approval time, and approval opinion is recorded on the document details page for subsequent query and traceability. Finally, the finance and logistics modules are notified via the messaging middleware.
[0078] S603: Feedback the processing time and abnormal events to the customer tag matrix.
[0079] Specifically, the recorded processing time and abnormal event information are sorted and analyzed to form corresponding feedback data. Then, the feedback data is updated in real time to the customer tag matrix through a preset interface or data transmission mechanism.
[0080] Example 2
[0081] like Figure 2 As shown, a document receiving and sending system based on an ERP system includes:
[0082] The label construction module is used to obtain and analyze each customer's historical document sending and receiving information, generate corresponding high-quality label information for each customer, and embed decision-making keywords and phrases to build a customer label matrix;
[0083] A priority allocation module is used to allocate a priority coefficient to each customer based on the customer label matrix to obtain the priority coefficient of each customer;
[0084] The weight division module is used to obtain the current business of each customer and assign a weight coefficient to each customer's business based on the preset threshold conditions;
[0085] The weight calculation module is used to combine the priority coefficient of each customer and the weight coefficient assigned to each customer's business, and calculate the comprehensive weight of each customer through weighted summation;
[0086] The information processing module is used to classify each customer's documents into high priority, medium priority, and low priority according to the comprehensive weight of each customer, and perform differentiated processing based on the current business of each customer to obtain the customer document processing results;
[0087] The approval update module is used to approve the customer document processing results, and at the same time, synchronize the approval results to the ERP system in real time and provide feedback to complete the document data update.
[0088] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the steps in the process. Figure 1 a process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.
[0089] Those skilled in the art will appreciate that all or part of the steps in the various methods of the above embodiments can be completed by instructing related hardware through a program, and the program can be stored in a computer-readable storage medium, including a read-only memory (ROM), a random access memory (RAM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), a one-time programmable read-only memory (OTPROM), an electronically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disc storage, magnetic disk storage, magnetic tape storage, or any other computer-readable medium capable of carrying or storing data.
[0090] It should also be noted that the terms "comprises," "includes," or any other variations thereof are intended to encompass non-exclusive inclusion, such that a process, method, commodity, or apparatus that includes a series of elements includes not only those elements but also other elements not explicitly listed, or includes elements inherent to such process, method, commodity, or apparatus. In the absence of further limitations, an element defined by the phrase "comprises a ..." does not exclude the presence of other identical elements in the process, method, commodity, or apparatus that includes the element.
Claims
1. A document sending and receiving method based on an ERP system, characterized in that: The sending and receiving method comprises the following steps: Obtain and analyze each customer's historical document sending and receiving information, generate corresponding high-quality label information for each customer, embed decision-making keywords and phrases, and build a customer label matrix; Based on the customer label matrix, assign a priority coefficient to each customer to obtain the priority coefficient of each customer; Obtain the current business of each customer and assign a weight coefficient to each customer's business based on the preset threshold conditions; Combine the priority coefficient of each customer and the weight coefficient assigned to each customer's business, and calculate the comprehensive weight of each customer through weighted summation; Based on the comprehensive weight of each customer, the customer's documents are divided into high priority, medium priority and low priority, and differentiated processing is performed based on the current business of each customer to obtain the customer document processing results; Approve the customer document processing results, synchronize the approval results to the ERP system immediately and provide feedback to complete the document data update.
2. The document sending and receiving method based on the ERP system according to claim 1, characterized in that: The specific steps of acquiring and analyzing each customer's historical document sending and receiving information, generating corresponding excellent label information for each customer, and embedding decision-making keywords and phrases to construct a customer label matrix include: From the ERP system database, based on unique identification information such as customer ID or name, accurately extract historical document receipt and delivery data for each customer within a specified time period, including document delivery time, quantity, or delivery status; Use data analysis tools to conduct multi-dimensional analysis of each customer's historical document delivery and receipt data. This multi-dimensional analysis includes analyzing the frequency of customer document delivery and receipt, calculating the average delivery and receipt cycle, and counting the delivery and receipt ratios of different document types. Based on the results of multi-dimensional analysis, corresponding excellent label information is formulated for each customer. On the basis of the generated excellent label information, decision-making keywords are further embedded to construct a customer label matrix, where the excellent label information includes high-quality, general and risk.
3. The document sending and receiving method based on the ERP system according to claim 2, characterized in that: The specific steps of assigning a priority coefficient to each customer based on the customer label matrix and obtaining the priority coefficient of each customer include: Priority coefficient rules are set based on the customer tag matrix, including: high-quality = 0.6, average = 0.3, and risky = 0.
1. If a customer's recent document delays surge, the trigger coefficient is lowered by 0.
1. Recent periods include the past week or the past month. Based on the priority coefficient rules, priority coefficients are dynamically assigned to each customer, and a customer priority coefficient table is generated and written into the ERP database.
4. The document sending and receiving method based on the ERP system according to claim 3 is characterized in that: The specific steps of obtaining the current business of each customer and assigning a weight coefficient to each customer business based on a preset threshold condition include: Obtain the current business of each customer, including amount, urgency, and product type; Two threshold conditions, amount threshold and urgency, are preset, and a weight coefficient is assigned to the current business of customers who meet the conditions.
5. The document sending and receiving method based on the ERP system according to claim 4 is characterized in that: The priority coefficient of each customer and the weight coefficient allocated to each customer's business are combined to calculate the comprehensive weight of each customer through weighted summation. The calculation formula is: comprehensive weight = priority coefficient × 60% + business weight × 40%.
6. The document sending and receiving method based on the ERP system according to claim 5, characterized in that: According to the comprehensive weight of each customer, each customer's documents are divided into high priority, medium priority and low priority, and differentiated processing is performed based on the current business of each customer. The differentiated processing in the customer document processing result includes: High priority: Trigger the automated fast track and reference the decision-making keywords in the customer tag matrix for enhanced execution; Medium priority: Enter the standard processing flow and perform manual or semi-automatic processing based on the prompt information in the tag matrix; Low priority: Temporarily queue or process according to default rules, and record the cause of the delay for optimization analysis.
7. The document sending and receiving method based on the ERP system according to claim 6, characterized in that: The specific steps of approving the customer document processing results, synchronizing the approval results to the ERP system and providing feedback, and completing the document data update include: Through the ERP workflow engine, high-priority documents are sent directly to supervisors for approval, and medium- and low-priority documents are countersigned as needed; After approval is completed, ERP automatically updates the document status and notifies the finance and logistics modules through the message middleware; Feedback processing time and abnormal events to the customer tag matrix.
8. A document receiving and sending system based on an ERP system, applied to a document receiving and sending method based on an ERP system according to any one of claims 1 to 7, characterized in that: The transceiver system includes: The label construction module is used to obtain and analyze each customer's historical document sending and receiving information, generate corresponding high-quality label information for each customer, and embed decision-making keywords and phrases to build a customer label matrix; A priority allocation module is used to allocate a priority coefficient to each customer based on the customer label matrix to obtain the priority coefficient of each customer; The weight division module is used to obtain the current business of each customer and assign a weight coefficient to each customer's business based on the preset threshold conditions; The weight calculation module is used to combine the priority coefficient of each customer and the weight coefficient assigned to each customer's business, and calculate the comprehensive weight of each customer through weighted summation; The information processing module is used to classify each customer's documents into high priority, medium priority, and low priority according to the comprehensive weight of each customer, and perform differentiated processing based on the current business of each customer to obtain the customer document processing results; The approval update module is used to approve the customer document processing results, and at the same time, synchronize the approval results to the ERP system in real time and provide feedback to complete the document data update.