ERP financial reconciliation method and device integrating OA collaborative management

Abstract

The embodiment of the present invention relates to the field of ERP technology, and discloses an ERP financial reconciliation method and device that integrates OA collaborative management. The method includes: generating a reconciliation statement task in response to a billing request issued by a salesperson from an OA system; generating a reconciliation statement based on the basic information in the billing request; approving the reconciliation statement, and after the approval is completed, calling a third-party plug-in interface to issue the bill according to the ticketing situation, and feeding back the billing result to the OA system. The embodiment of the present invention can integrate the data sharing of the two systems of OA and ERP, overcoming the traditional single-threaded reconciliation management method based on trade and the problem of difficult data matching.

Description

Technical Field

[0001] The present invention relates to the technical field of ERP systems, and in particular to an ERP financial reconciliation method and device integrating OA collaborative management. Background Art

[0002] At present, there is incoordination in software applications. The OA system and the ERP system belong to different departments respectively. For many trading companies, the relatively isolated and single-threaded operations have low collaboration efficiency and poor data sharing. For example, offline financial personnel are generally selected to check and process orders, but this reconciliation process requires a large number of people to communicate offline by phone and record various reports in detail. There is no record of the process after the document and invoice are checked, and the work of keeping a copy of the physical invoice is very complicated. Summary of the invention

[0003] In response to the above-mentioned defects, an embodiment of the present invention discloses an ERP financial reconciliation method and device integrating OA collaborative management, which can integrate the data sharing of OA and ERP systems, overcome the traditional trade-based single-threaded reconciliation management method and the problem of difficult data matching, and use the OA collaborative management system to open up the data connection of multiple actual personnel, so as to guide business personnel to complete the reconciliation work more clearly and efficiently, and make every transaction trace clearly visible.

[0004] A first aspect of an embodiment of the present invention discloses an ERP financial reconciliation method integrating OA collaborative management, the method comprising:

[0005] Generate a statement task in response to the invoicing request sent by the salesperson from the OA system;

[0006] Generate a statement based on the basic information in the invoicing request;

[0007] The statement of account is reviewed and approved. After the review and approval is completed, a third-party plug-in interface is called to issue the invoice according to the ticketing situation, and the invoicing result is fed back to the OA system.

[0008] As an optional implementation, in a first aspect of the embodiment of the present invention, in response to a billing request issued by a salesperson from an OA system, generating a statement task includes:

[0009] The salesperson retrieves transaction cost data from the OA system, generates report data, connects related documents and sends them to the ERP system, so that the salesperson sends an invoicing request from the OA system. The ERP system creates a statement task with one click based on the invoicing request.

[0010] As an optional implementation, in a first aspect of the embodiment of the present invention, generating a statement according to the invoicing request and basic information includes:

[0011] Confirming whether to generate a statement asynchronously based on the report data;

[0012] A statement of account is generated based on one or more of the product details, returned product details, and refund slip in the report data.

[0013] As an optional implementation manner, in the first aspect of the embodiment of the present invention, approving the statement includes:

[0014] Match the statement with the document to confirm whether the document is correct. If the document is incorrect, send it to the salesperson in the form of an email or text message, and start the repair program to execute the synchronization script to repair the document;

[0015] When the statement and the document are matched successfully, the three settlement tables associated with the statement are automatically changed to the reconciled status;

[0016] Determine whether there are two or more records of the same SKU on the same platform. If so, determine whether it is a gift.

[0017] As an optional implementation, in the first aspect of the embodiment of the present invention, calling a third-party plug-in interface to issue a ticket according to the ticketing situation, and feeding back the issue result to the OA system, includes:

[0018] Confirm the payment status according to the statement, and call the third-party plug-in interface to issue an invoice based on the payment status;

[0019] When the invoices of the invoicing type are insufficient, the third-party plug-in sends a reminder message to the ERP system, and the ERP system reminds the salesperson through the OA system, or / and the ERP system sends a reminder to the users of the corresponding e-commerce platform or recommends whether to choose other types of invoices.

[0020] As an optional implementation, in the first aspect of the embodiment of the present invention, after the salesperson receives the invoicing result from the OA system and confirms the invoicing result, the confirmation information is received and fed back to the customer according to the invoice type: when the invoice type is a paper invoice, the ERP system automatically generates an express demand form based on the customer information; when the invoice type is an electronic invoice, the ERP system automatically sends it to the customer based on the customer information.

[0021] A second aspect of an embodiment of the present invention discloses an ERP financial reconciliation device integrating OA collaborative management, which includes:

[0022] A response unit, used to generate a statement task in response to a billing request issued by a salesperson from the OA system;

[0023] A generating unit, configured to generate a statement according to the basic information in the invoicing request;

[0024] The approval unit is used to approve the statement of account. After the approval is completed, the third-party plug-in interface is called to issue the invoice according to the ticketing situation, and the invoicing result is fed back to the OA system.

[0025] The third aspect of an embodiment of the present invention discloses an ERP system, comprising: a memory storing executable program code; a processor coupled to the memory; the processor calls the executable program code stored in the memory to execute an ERP financial reconciliation method for integrated OA collaborative management disclosed in the first aspect of the embodiment of the present invention.

[0026] A fourth aspect of an embodiment of the present invention discloses a computer-readable storage medium storing a computer program, wherein the computer program enables a computer to execute an ERP financial reconciliation method for integrated OA collaborative management disclosed in the first aspect of an embodiment of the present invention.

[0027] The fifth aspect of the embodiment of the present invention discloses a computer program product. When the computer program product runs on a computer, the computer executes an ERP financial reconciliation method for integrated OA collaborative management disclosed in the first aspect of the embodiment of the present invention.

[0028] The sixth aspect of an embodiment of the present invention discloses an application publishing platform, which is used to publish a computer program product. When the computer program product runs on a computer, the computer executes an ERP financial reconciliation method for integrated OA collaborative management disclosed in the first aspect of an embodiment of the present invention.

[0029] Compared with the prior art, the embodiments of the present invention have the following beneficial effects:

[0030] The present invention perfectly combines the advanced collaborative office mechanism of ERP by fully introducing the OA collaborative management module and the integrated document module into the ERP system, realizing the information integration of ERP logic and solving the problem that the ERP system is difficult to operate and use. The data integration of ERP and OA system contracts and financial business realizes the data flow between two different systems. It ensures the enterprise's ability to obtain information, improves work efficiency, and has strong practicality.

[0031] There is no need to purchase an additional OA system. While reducing production costs, it can meet the needs of industrial and commercial enterprise management informationization in various industries and truly help enterprises achieve effective integration of business flow, logistics and capital flow. In addition, its built-in workflow management model can help enterprises solidify business processes, ensure standardized operation of enterprise business, and improve enterprise business decision-making and management capabilities. This system can be widely used in various types of trade-related enterprises, supporting the financial management needs of enterprises with business models of customer-oriented order-based production or procurement, as well as the financial management needs of enterprises with business models of inventory-oriented stocking production or procurement, and also supporting the management needs of enterprises with both business models. It is a model of the new generation of ERP systems. BRIEF DESCRIPTION OF THE DRAWINGS

[0032] In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings required for use in the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0033] Figure 1 It is a flowchart of an ERP financial reconciliation method integrating OA collaborative management disclosed in an embodiment of the present invention;

[0034] Figure 2 It is a flowchart of the interaction between the OA system and the ERP system disclosed in the embodiment of the present invention;

[0035] Figure 3 It is a schematic diagram of the approval process of importing a statement of account disclosed in an embodiment of the present invention;

[0036] Figure 4 It is a schematic diagram of the process of allocating payment returns disclosed in an embodiment of the present invention;

[0037] Figure 5 It is a schematic diagram of the entire process of reconciliation and invoicing disclosed in an embodiment of the present invention;

[0038] Figure 6 It is a schematic diagram of the invoicing process disclosed in the embodiment of the present invention;

[0039] Figure 7 It is a structural diagram of an ERP financial reconciliation device integrating OA collaborative management disclosed in an embodiment of the present invention;

[0040] Figure 8 It is a structural diagram of an ERP system disclosed in an embodiment of the present invention. DETAILED DESCRIPTION

[0041] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0042] It should be noted that the terms "first", "second", "third", "fourth", etc. in the specification and claims of the present invention are used to distinguish different objects rather than to describe a specific order. The terms "including" and "having" in the embodiments of the present invention and any variations thereof are intended to cover non-exclusive inclusions. For example, a process, method, system, product or device including a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0043] The embodiment of the present invention discloses an ERP financial reconciliation method and device integrating OA collaborative management, which comprehensively introduces the OA collaborative management module and the integrated document module into the ERP system, perfectly combining the advanced collaborative office mechanism of ERP, realizing the information integration of ERP logic, and solving the problem that the ERP system is difficult to operate and difficult to use. It is described in detail below with reference to the accompanying drawings.

[0044] Embodiment 1

[0045] See also Figure 1 , Figure 1 This is a flowchart of an ERP financial reconciliation method integrated with OA collaborative management disclosed in an embodiment of the present invention. The method described in the embodiment of the present invention is applicable to the connection between the ERP system and the OA system. Of course, in some scenarios, the ERP system can also be connected with third-party systems such as e-commerce platforms, invoicing systems, and express delivery systems. Figure 1 As shown, the ERP financial reconciliation method for the OA collaborative management includes the following steps:

[0046] S110, generating a statement task in response to the invoicing request sent by the salesperson from the OA system.

[0047] After the OA system and ERP system are connected, the salesperson can directly perform reconciliation and invoicing operations in the OA system. The ERP system receives the relevant operations in the OA system and executes them. The interactive relationship between the OA system and the ERP system is as follows: Figure 2 shown.

[0048] The salesperson sends an invoicing request to the ERP system through the OA system. The invoicing request contains the identity information of the target salesperson in the OA system. When the identity information does not belong to the business scope, the request will not be responded to, or results such as identity non-compliance will be returned.

[0049] After verifying the identity information, the ERP system creates a statement task with one click. There are two scenarios here. If the invoicing request already carries report data and document information, and the report data is filled in according to the statement requirements, then the statement task can be created directly. In the other scenario, the ERP system creates a statement task with one click, and then feeds the corresponding format document to the corresponding salesperson through the OA system, who then fills in the report data in the relevant documents such as EXCEL tables, or directly in the preset template in the OA system.

[0050] For the second situation, you can import the statement with one click through the relevant documents, or you can import the statement with one click after filling in the preset template. In the early stage, you can conduct a preliminary review of the imported statement. Its content is similar to the data screening in step 130. Figure 3 shown.

[0051] S120: Generate a statement according to the basic information in the invoicing request.

[0052] The process of generating a statement can be performed using an asynchronous task to avoid massive data redundancy causing server performance degradation. Specifically, the report data is monitored and its data volume is confirmed. When the data volume is greater than a certain threshold, the statement is generated using an asynchronous task. Of course, you can also set whether to start the asynchronous task mode based on the total data request volume at that time.

[0053] The report data mainly includes the following information: store name, basic data, platform order number, product code, product name, product specification code, product specification name, cost information and quantity, etc. Among them, the basic data can include the details of shipped products, the details of returned products and refund orders, etc. The generated statement is saved in the MySQL database for subsequent reconciliation and invoicing operations.

[0054] The reconciliation statement is associated with the document, and an associated information table is established between the two. The reconciliation process involves the capture of document information.

[0055] S130, the statement is approved. When the approval is completed, a third-party plug-in interface is called to issue an invoice according to the ticketing situation, and the invoicing result is fed back to the OA system.

[0056] The first part of the approval of the generated statement is data screening to see if there are any omissions or errors, such as missing documents, incorrect amounts, unit prices, etc. Of course, in some scenarios, it may be that the information included in the statement does not include documents. When omissions or errors occur, the ERP system can notify the corresponding salesperson to make changes through email or SMS, and send the corresponding changes to the OA system for the salesperson to adjust.

[0057] In a preferred embodiment of the present invention, the ERP system can also start a repair program. If there are any missing documents, the data synchronization script can be executed to fill the gaps.

[0058] In some other embodiments, the ERP system can also establish a connection with the e-commerce platform system and automatically generate a statement. For example, the store managed by the salesperson on the e-commerce platform is confirmed according to the salesperson identity attribute of the OA system, and the statement is automatically generated according to the shipped goods details, returned goods details and refund orders (including refund only and refund after delivery, etc.) recorded by the e-commerce platform. Then, when the salesperson submits an invoicing or reconciliation request through the OA system, the statement is directly sent to the OA system for review.

[0059] After the data screening is completed, the invoicing operation can be carried out. Before invoicing, the second part of the statement should be reviewed, mainly including the modification of the reconciliation status and the collection status.

[0060] First, check whether there are two records of the same SKU on the same e-commerce platform in the statement. If so, it may cause the reconciliation status to be marked incorrectly. Determine whether there is a gift. If so, you can delete one record in the statement or automatically modify one of them as a gift.

[0061] There are many criteria for judgment. For example, when there are two records of the same SKU multiple times within a period of time, there is generally a possibility of gifts. It is also possible to confirm whether there is a promotion activity during the time period when the two records of the same SKU exist, for example, by documenting, by retrieving the activity record document of the time period, or by retrieving the information recorded by the e-commerce platform where the two records of the same SKU exist.

[0062] Secondly, check whether the report data is consistent with the data synchronized with the e-commerce platform, that is, compare whether the store name, basic data, platform order number, product code, product name, product specification code, product specification name, cost information and quantity are consistent with the data synchronized with the e-commerce platform. For example, the store name corresponding to the platform order number is incorrect, and the product code does not include the product specification code.

[0063] When the approval is completed, the three settlement forms associated with the reconciliation statement (delivery note, return note and refund note) will be automatically adjusted to the reconciled status. In order to prevent repeated reconciliation or omission of reconciliation content, in a preferred embodiment of the present invention, on the one hand, it can be done by setting a time period to include all reconciliation information within the time period, and then the reconciliation statement of this time period will no longer be approved. On the other hand, it can also be verified according to the unique identity information such as the platform order number. For example, the approved unique identity information is saved in a folder and automatically associated with the approval process. During a certain approval process, the unique identity information of the reconciliation statement to be approved will be compared with the unique identity information in the above folder to see if there is any duplication. If there is a duplication, the reconciliation information will be sent to the OA system to be reconciled, and its content will no longer be reconciled. After this approval is completed, the content in the folder is updated, and the records saved before the preset time are deleted, for example, the unique identity information approved in the previous month is deleted, etc.

[0064] Then, modify the payment status: please refer to Figure 4 As shown, the statement follows the principle of "refunds for returns and refunds are paid first, and the one with the earliest delivery time is paid first". If the payment is not enough, it will be in partial payment status; if the bill has been fully paid or partially paid before the invoice is issued, the payment status will be directly changed to full payment after the invoice is approved; if the statement is a partial payment, the payment amount of the statement - the sum of the payment amounts of the other invoices under the statement = the amount of the invoice that can be paid back. If the amount of the invoice that can be paid back is greater than or equal to the amount of the invoice, the status of the invoice is full payment. If it is less than, it is partial payment. If it is zero, it is waiting for payment.

[0065] After the approval is completed, it will be returned to the salesperson for verification. After the verification is correct, the corresponding invoice can be issued. The invoicing information and customer information are already included in the invoicing request.

[0066] In other embodiments of the present invention, the salesperson may submit a reconciliation request through the OA system, and for the reconciliation completed part, the invoicing request may be submitted in the OA system. The principle is the same as that of directly submitting an invoicing request in the embodiment of the present invention. Figure 5 The implementation process is shown and will not be described in detail here.

[0067] Invoicing is done by calling a third-party plug-in interface, and the third-party invoicing system issues invoices. When invoicing, the invoicing information in the invoicing request (including invoicing type, customer information, and amount) is sent to the invoicing system through the third-party plug-in interface, and the invoicing system issues the invoice. Please refer to Figure 6 As shown, after the invoicing is completed, the invoicing status of the statement is changed. Generally, if the invoiced amount = 0, it is pending invoicing; if the invoiced amount < the amount to be settled, it is partial invoicing; if the invoiced amount = the amount to be settled, it is full invoicing.

[0068] In the process of invoicing, especially at the end of the month or during a period with large sales volume, there may be a situation where there are insufficient invoices. At this time, if the customer is in urgent need or is not notified that the invoice will be issued later, it may affect their experience. In a preferred embodiment of the present invention, the invoicing system can send a message to ERP that the current invoice type is insufficient and it is necessary to wait for 2 working days before issuing, etc., and ERP sends information to the OA system to remind the salesperson, or the ERP system directly sends a reminder message to the user of the corresponding e-commerce platform.

[0069] In addition, paper VAT general invoices and electronic VAT general invoices are equivalent. In the initial stage, customers choose paper VAT general invoices. When paper VAT general invoices are insufficient during invoicing, the invoicing system can also remind the ERP system to issue more sufficient electronic VAT general invoices. Of course, the ERP system can also send information on its recommendations of other types of invoices to the OA system.

[0070] Of course, if the customer chooses a special VAT invoice and the special VAT invoice is insufficient, we can also recommend him to choose a general VAT invoice.

[0071] When a customer reports on the e-commerce platform that he does not need to select other types of invoices or has not made a selection for a period of time (for example, he has not made a selection when the invoice types he has selected are sufficient), it is deemed that he can accept the waiting time. If the customer accepts other types of invoices on the e-commerce platform, then after ERP receives the customer's confirmation information, it will issue the corresponding invoice in accordance with the other invoice types accepted by the customer (if additional information is required, it will be reminded when the ERP system sends it to the e-commerce platform).

[0072] In order to reduce the workload of sales personnel and avoid omissions when sending invoices to customers, in a preferred embodiment of the present invention, after the invoicing results are fed back to the salesperson through the OA system, when the salesperson confirms that the invoicing results are correct, the ERP system receives the confirmation information and sends the invoice to the customer according to the customer information (mailing address, customer name, phone number and / or email address, etc.) in the invoicing request. For example, for paper invoices, the third-party express interface is automatically called according to the mailing address to send a mailing request to the third-party express system. For electronic invoices, the electronic invoice can be sent directly to the mailbox, or the electronic invoice can be sent to the purchase interface through the e-commerce platform.

[0073] Similarly, in order to avoid the possibility of duplicate invoicing, in a preferred embodiment of the present invention, invoicing can also be performed according to time periods, or the invoiced data can be saved in a fixed folder.

[0074] Embodiment 2

[0075] See also Figure 7 , Figure 7 This is a schematic diagram of the structure of an ERP financial reconciliation device integrating OA collaborative management disclosed in an embodiment of the present invention. Figure 7 As shown, the ERP financial reconciliation device for the integrated OA collaborative management may include:

[0076] The response unit 210 is used to generate a statement task in response to the invoicing request sent by the salesperson from the OA system;

[0077] A generating unit 220, configured to generate a statement according to the basic information in the invoicing request;

[0078] The approval unit 230 is used to approve the statement. After the approval is completed, the third-party plug-in interface is called to issue the invoice according to the ticketing situation, and the invoicing result is fed back to the OA system.

[0079] Preferably, the response unit 210 may include:

[0080] The salesperson retrieves transaction cost data from the OA system, generates report data, connects related documents and sends them to the ERP system, so that the salesperson sends an invoicing request from the OA system. The ERP system creates a statement task with one click based on the invoicing request.

[0081] Preferably, the generating unit 220 may include:

[0082] Confirming whether to generate a statement asynchronously based on the report data;

[0083] A statement of account is generated based on one or more of the product details, returned product details, and refund slip in the report data.

[0084] Preferably, the approval unit 230 may include:

[0085] Match the statement with the document to confirm whether the document is correct. If the document is incorrect, send it to the salesperson in the form of an email or text message, and start the repair program to execute the synchronization script to repair the document;

[0086] When the statement and the document are matched successfully, the three settlement tables associated with the statement are automatically changed to the reconciled status;

[0087] Determine whether there are two or more records of the same SKU on the same platform. If so, determine whether it is a gift.

[0088] Preferably, the approval unit 230 may further include:

[0089] Confirm the payment status according to the statement, and call the third-party plug-in interface to issue an invoice based on the payment status;

[0090] When the invoices of the invoicing type are insufficient, the third-party plug-in sends a reminder message to the ERP system, and the ERP system reminds the salesperson through the OA system, or / and the ERP system sends a reminder to the users of the corresponding e-commerce platform or recommends whether to choose other types of invoices.

[0091] Preferably, after the salesperson receives the invoicing result from the OA system and confirms the invoicing result, he receives the confirmation information and feeds back to the customer according to the invoice type: when the invoice type is a paper invoice, the ERP system automatically generates an express demand form according to the customer information; when the invoice type is an electronic invoice, the ERP system automatically sends it to the customer according to the customer information.

[0092] Embodiment 3

[0093] See also Figure 8 , Figure 8 1 is a schematic diagram of the structure of an ERP system disclosed in an embodiment of the present invention. The ERP system includes ERP software and an electronic device on which the ERP software is installed. The electronic device may be a desktop computer, a notebook computer, a common server, a cloud server, etc. In some scenarios, it may also be a mobile phone or a tablet computer, etc.

[0094] like Figure 8 As shown, the electronic device may include:

[0095] A memory 310 storing executable program codes;

[0096] a processor 320 coupled to the memory 310;

[0097] The processor 320 calls the executable program code stored in the memory 310 to execute part or all of the steps in the ERP financial reconciliation method for integrated OA collaborative management disclosed in the first embodiment.

[0098] An embodiment of the present invention discloses a computer-readable storage medium storing a computer program, wherein the computer program enables a computer to execute part or all of the steps in an ERP financial reconciliation method for integrated OA collaborative management disclosed in Embodiment 1.

[0099] An embodiment of the present invention further discloses a computer program product, wherein when the computer program product runs on a computer, the computer executes part or all of the steps in an ERP financial reconciliation method for integrated OA collaborative management disclosed in Embodiment 1.

[0100] An embodiment of the present invention also discloses an application publishing platform, wherein the application publishing platform is used to publish a computer program product, wherein when the computer program product runs on a computer, the computer executes part or all of the steps in an ERP financial reconciliation method for integrated OA collaborative management disclosed in Embodiment 1.

[0101] In various embodiments of the present invention, it should be understood that the size of the serial numbers of the processes does not necessarily mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present invention.

[0102] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, i.e., they may be located in one place or distributed over multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0103] In addition, each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0104] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-accessible memory. Based on this understanding, the technical solution of the present invention, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product, which is stored in a memory and includes several requests for a computer device (which can be a personal computer, a server or a network device, etc., specifically a processor in a computer device) to perform some or all of the steps of the method described in each embodiment of the present invention.

[0105] In the embodiments provided by the present invention, it should be understood that "B corresponding to A" means that B is associated with A, and B can be determined according to A. However, it should also be understood that determining B according to A does not mean determining B only according to A, and B can also be determined according to A and / or other information.

[0106] A person of ordinary skill in the art can understand that some or all of the steps in the various methods of the embodiments can be completed by instructing related hardware through a program, and the program can be stored in a computer-readable storage medium, and the storage medium includes 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 rewritable read-only memory (EEPROM), a compact disc (CD-ROM) or other optical disc storage, magnetic disk storage, magnetic tape storage, or any other computer-readable medium that can be used to carry or store data.

[0107] The above is a detailed introduction to an ERP financial reconciliation method and device for integrated OA collaborative management disclosed in an embodiment of the present invention. Specific examples are used in this article to illustrate the principles and implementation methods of the present invention. The description of the above embodiments is only used to help understand the method of the present invention and its core idea; at the same time, for general technical personnel in this field, according to the idea of ​​the present invention, there will be changes in the specific implementation method and application scope. In summary, the content of this specification should not be understood as a limitation on the present invention.

Claims

1. An ERP financial reconciliation method integrating OA collaborative management, characterized in that: include: Generate a statement task in response to the invoicing request sent by the salesperson from the OA system; Generate a statement based on the basic information in the invoicing request; Approve the statement, and after the approval is completed, call the third-party plug-in interface to issue the invoice according to the ticketing situation, and feed back the invoicing result to the OA system; Generate a statement based on the basic information in the invoicing request, including: Confirm the store managed by the salesperson on the e-commerce platform based on the salesperson's identity attributes in the OA system, automatically generate a statement based on the shipped goods details, returned goods details and refund slips recorded on the e-commerce platform, and then send the statement directly to the OA system for review when the salesperson submits an invoicing or reconciliation request through the OA system; Approving the statement of account, including: Match the statement with the document to confirm whether the document is correct. If the document is incorrect, send it to the salesperson via email or SMS, and start the repair program to execute the synchronization script to repair the document; Determine whether there are two or more records of the same SKU on the same platform. If so, determine whether it is a gift; When the statement and the document are matched successfully, the three settlement tables associated with the statement are automatically changed to the reconciled status, and the three settlement tables include the delivery note, return note and refund note; as well as The approved unique identity information is saved in a folder and automatically associated with the approval process. During a certain approval process, the unique identity information of the statement to be approved will be compared with the unique identity information in the above folder to see if there is any duplication. If there is duplication, the reconciliation information will be sent to the OA system and the content will no longer be reconciled. After the approval is completed, the content in the folder will be updated and the records saved before the preset time will be deleted. The unique identity information is the platform order number.

2. The ERP financial reconciliation method for collective OA collaborative management according to claim 1 is characterized in that: In response to the invoicing request sent by the salesperson from the OA system, a statement task is generated, including: The salesperson retrieves transaction cost data from the OA system, generates report data, connects related documents and sends them to the ERP system, so that the salesperson sends an invoicing request from the OA system. The ERP system creates a statement task with one click based on the invoicing request.

3. The ERP financial reconciliation method for collective OA collaborative management according to claim 2 is characterized in that: Generate a statement based on the invoicing request and basic information, and also include: Determine whether to generate a statement asynchronously based on the report data.

4. The ERP financial reconciliation method for collective OA collaborative management according to claim 1 is characterized in that: Call the third-party plug-in interface to issue tickets based on the ticketing situation, and feed back the ticketing results to the OA system, including: Confirm the payment status according to the statement, and call the third-party plug-in interface to issue an invoice based on the payment status; When the invoices of the invoicing type are insufficient, the third-party plug-in sends a reminder message to the ERP system, and the ERP system reminds the salesperson through the OA system, or / and the ERP system sends a reminder to the users of the corresponding e-commerce platform or recommends whether to choose other types of invoices.

5. The ERP financial reconciliation method for collective OA collaborative management according to any one of claims 1 to 4, characterized in that: After the salesperson receives the invoicing result from the OA system and confirms the invoicing result, he receives the confirmation information and feeds back to the customer according to the invoice type: when the invoice type is a paper invoice, the ERP system automatically generates an express demand form based on the customer information; when the invoice type is an electronic invoice, the ERP system automatically sends it to the customer based on the customer information.

6. An ERP financial reconciliation device integrating OA collaborative management, characterized in that: It includes: A response unit, used to generate a statement task in response to a billing request issued by a salesperson from the OA system; A generating unit, configured to generate a statement according to the basic information in the invoicing request; An approval unit is used to approve the statement. After the approval is completed, a third-party plug-in interface is called to issue the invoice according to the ticketing situation, and the invoicing result is fed back to the OA system; The generation unit includes: Confirm the store managed by the salesperson on the e-commerce platform based on the salesperson's identity attributes in the OA system, automatically generate a statement based on the shipped goods details, returned goods details and refund slips recorded on the e-commerce platform, and then send the statement directly to the OA system for review when the salesperson submits an invoicing or reconciliation request through the OA system; Approval units include: Match the statement with the document to confirm whether the document is correct. If the document is incorrect, send it to the salesperson via email or SMS, and start the repair program to execute the synchronization script to repair the document; Determine whether there are two or more records of the same SKU on the same platform. If so, determine whether it is a gift; When the statement and the document are matched successfully, the three settlement tables associated with the statement are automatically changed to the reconciled status, and the three settlement tables include the delivery note, return note and refund note; as well as The approved unique identity information is saved in a folder and automatically associated with the approval process. During a certain approval process, the unique identity information of the statement to be approved will be compared with the unique identity information in the above folder to see if there is any duplication. If there is duplication, the reconciliation information will be sent to the OA system and the content will no longer be reconciled. After the approval is completed, the content in the folder will be updated and the records saved before the preset time will be deleted. The unique identity information is the platform order number.

7. An ERP system, characterized in that: include: A memory storing executable program code; a processor coupled to the memory; The processor calls the executable program code stored in the memory to execute the ERP financial reconciliation method for integrated OA collaborative management as described in any one of claims 1 to 5.

8. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, wherein the computer program enables a computer to execute an ERP financial reconciliation method for collective OA collaborative management as described in any one of claims 1 to 5.

Images