A method for collecting and distributing accounts of a lease and sale business, a lease and sale system, a distribution system and a medium

Abstract

The application relates to the technical field of real estate rent and sale financial account separation, and discloses a rent and sale business collection account separation method, a rent and sale system, an account separation system and a medium. The method comprises the following steps: sending company information stored by itself to the account separation system; generating a collection confirmation sheet when it is detected that the payment state of a collection order is paid; and generating account separation data according to the collection confirmation sheet, wherein the account separation data is used to trigger the account separation system to execute an account separation operation according to the company information and the account separation data. The application establishes a communication connection between the rent and sale system and the account separation system, automatically generates account separation data and triggers an account separation operation after collection is completed, realizes full-process automation from collection confirmation to fund account separation, replaces a manual cross-system input link, eliminates human error risks, and significantly improves the accuracy and efficiency of account separation.

Description

Technical Field

[0001] This application relates to the field of financial accounting technology for real estate rental and sales, and in particular to a method for accounting for rental and sales revenue, a rental and sales system, an accounting system and medium. Background Technology

[0002] In existing real estate rental and sales transactions, the accounting process after payment is completed is mostly handled manually. Financial staff need to confirm the payment information in the rental and sales system and then manually enter the accounting data (company information, payment amount, transaction information, etc.) into the accounting system. This not only increases the workload of financial staff, but also makes it easy for data errors to occur due to manual entry, leading to accounting mistakes. Summary of the Invention

[0003] This application provides a method for revenue sharing in rental and sales transactions, a rental and sales system, a revenue sharing system, and a medium to solve the problem in existing rental and sales transactions where revenue sharing after collection requires manual cross-system data entry, which is labor-intensive, error-prone, and leads to revenue sharing errors.

[0004] The first aspect of this application provides a method for revenue sharing in rental and sales transactions, applied to a rental and sales system, wherein the rental and sales system and the revenue sharing system are connected in communication, and the method includes: sending company information stored in the system to the revenue sharing system; generating a payment confirmation when the payment status of a payment order is detected as paid; and generating revenue sharing data based on the payment confirmation, wherein the revenue sharing data is used to trigger the revenue sharing system to perform revenue sharing operations based on the company information and the revenue sharing data.

[0005] In some embodiments of this application, the company information includes at least the company name, unified social credit code, bank, bank account number, and region; the payment confirmation slip includes at least the order number, transaction number, actual amount received, company information, and payment confirmation time.

[0006] In some embodiments of this application, the revenue sharing data includes: the company information, the payment order number, the actual amount received, the transaction number, and the payment confirmation time, and the revenue sharing data corresponds one-to-one with the payment confirmation slip.

[0007] In some embodiments of this application, generating split revenue data based on the payment confirmation slip includes: before generating split revenue data, detecting whether the company to which the company belongs in the company information is unique; generating split revenue data when the company to which the company belongs is unique; and sending a prompt message that split revenue is not supported to the client terminal when the company to which the company belongs is not unique, and not generating split revenue data.

[0008] In some embodiments of this application, the method further includes: receiving a push success receipt returned from the revenue sharing system, and updating the status of the receipt corresponding to the receipt confirmation to "data pushed", wherein the push success receipt is a prompt message generated by the revenue sharing system after receiving the revenue sharing data.

[0009] The second aspect of this application provides a method for revenue sharing in rental and sales transactions, applied to a revenue sharing system, wherein the revenue sharing system is connected to the rental and sales system, and the method includes: receiving company information and revenue sharing data sent by the rental and sales system; and performing revenue sharing operations based on the company information and revenue sharing data.

[0010] In some embodiments of this application, after receiving the revenue sharing data, the method further includes: returning a push success receipt to the rental and sales system, wherein the push success receipt is used to trigger the rental and sales system to update the status of the receipt corresponding to the receipt confirmation to "data pushed".

[0011] A third aspect of this application provides a rental and sales system that is communicatively connected to a revenue-sharing system. The rental and sales system includes: a company information synchronization module for sending its stored company information to the revenue-sharing system; a payment confirmation module for generating a payment confirmation slip when the payment status of a payment order is detected as paid; and a revenue-sharing data push module for generating revenue-sharing data based on the payment confirmation slip. The revenue-sharing data is used to trigger the revenue-sharing system to perform revenue-sharing operations based on the company information and the revenue-sharing data.

[0012] The fourth aspect of this application provides a revenue-sharing system that is communicatively connected to a rental and sales system. The revenue-sharing system is used to execute the steps of any of the above-described rental and sales business revenue-sharing methods applied to the revenue-sharing system.

[0013] The fifth aspect of this application provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the rental and sales business revenue collection and distribution method described in any of the first or second aspects of the above embodiments.

[0014] This application has the following beneficial effects: This application proposes a method for revenue sharing in rental and sales business, applied to a rental and sales system, wherein the rental and sales system and the revenue sharing system are connected in communication, and the method includes: sending the company information stored in the system to the revenue sharing system; generating a payment confirmation when the payment status of a payment order is detected as paid; generating revenue sharing data based on the payment confirmation, wherein the revenue sharing data is used to trigger the revenue sharing system to perform revenue sharing operations based on the company information and the revenue sharing data.

[0015] This application establishes a communication connection between the rental and sales system and the revenue sharing system, automatically generating revenue sharing data and triggering revenue sharing operations after payment is received. This achieves full automation of the process from payment confirmation to fund sharing, replacing the manual cross-system data entry step, thereby eliminating the risk of human error and significantly improving the accuracy and efficiency of revenue sharing. Attached Figure Description

[0016] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with this application and, together with the specification, serve to explain the technical solutions of this application.

[0017] Figure 1 This is a flowchart illustrating an embodiment of the rental and sales revenue collection and distribution method provided in this application; Figure 2 This is a flowchart illustrating another embodiment of the rental and sales revenue collection and distribution method provided in this application; Figure 3 This is a schematic diagram of the framework of an embodiment of the message interaction between the rental and sales system and the revenue sharing system provided in this application; Figure 4 This is a schematic diagram of a framework of an embodiment of the computer-readable storage medium provided in this application. Detailed Implementation

[0018] In the following description, specific details such as particular system architectures, interfaces, and technologies are presented for illustrative purposes rather than for limiting purposes, in order to provide a thorough understanding of this application.

[0019] In this document, the term "and / or" is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, and B existing alone. Additionally, the character " / " generally indicates that the preceding and following related objects have an "or" relationship. Furthermore, "many" in this document means two or more. Moreover, the term "at least one" in this document means any combination of at least two of any one or more of a plurality of objects. For example, including at least one of A, B, and C can mean including any one or more elements selected from the set consisting of A, B, and C.

[0020] As described in the background section, in existing real estate rental and sales transactions, the accounting and distributing of payments after collection is mostly handled manually. Finance personnel must confirm the collection information in the rental and sales system and then manually enter the accounting and distributing data (company information, collection amount, transaction information, etc.) into the accounting and distributing system. This not only increases the workload of finance personnel but also easily leads to data errors due to manual entry, resulting in accounting and distributing mistakes. Furthermore, the company information in the rental and sales system and the accounting and distributing system is not synchronized. If company information is added or modified in the rental and sales system, it must be manually updated in the accounting and distributing system, easily leading to inconsistencies between the two systems and affecting accounting and distributing efficiency. In addition, some accounting and distributing processes are complex, supporting single collections to multiple companies, increasing the difficulty of accounting and distributing. However, the accounting and distributing requirements of property rental and sales transactions are mostly for single collections to a single company; complex accounting and distributing processes actually reduce accounting and distributing efficiency. While some revenue-sharing systems in the industry currently support automatic revenue sharing, they are not customized for the revenue sharing scenarios of property rental and sales businesses. They cannot seamlessly integrate with the payment module of rental and sales systems, nor do they simplify revenue sharing rules according to the revenue sharing needs of rental and sales businesses, making it difficult to adapt to the efficient revenue sharing needs of property rental and sales businesses.

[0021] To address the aforementioned issues, this application proposes a method for revenue sharing in rental and sales transactions, which enables the automatic push of data to the revenue sharing system and achieves efficient revenue sharing after the rental and sales transactions are completed.

[0022] This application will now be described in detail with reference to the accompanying drawings and specific embodiments.

[0023] According to one embodiment of this application, this application proposes a method for revenue sharing in rental and sales transactions, applied to a rental and sales system, wherein the rental and sales system and the revenue sharing system are communicatively connected, and as follows: Figure 1 As shown, the revenue sharing method for rental and sales transactions in this application is implemented through the following steps S1-S3: S1. Send the company information stored in its own database to the revenue sharing system; S2. When the payment status of a payment order is detected as "paid", generate a payment confirmation. S3. Generate split data based on the payment confirmation slip. The split data is used to trigger the split system to perform split operations based on company information and the split data.

[0024] Therefore, the above embodiments, by establishing a communication connection between the rental and sales system and the revenue sharing system, automatically generate revenue sharing data and trigger revenue sharing operations after the payment is received, realizing full automation of the process from payment confirmation to fund sharing, replacing the manual cross-system data entry step, thereby eliminating the risk of human error and significantly improving the accuracy and efficiency of revenue sharing.

[0025] In this embodiment, the company information includes at least the company name, unified social credit code, bank, bank account number, and region; the payment confirmation slip includes at least the order number, transaction number, actual payment amount, company information, and payment confirmation time.

[0026] In this embodiment, the revenue sharing data includes: the company information, the payment order number, the actual amount received, the transaction number, and the payment confirmation time, and the revenue sharing data corresponds one-to-one with the payment confirmation slip.

[0027] In some embodiments of this application, such as Figure 2 As shown, generating reconciliation data based on the payment confirmation slip also includes the following steps: S31. Before generating the revenue sharing data, check whether the company attribution in the company attribution information is unique; S32. When a unique ownership company is detected, revenue sharing data is generated; S33. When it is detected that the company to which the revenue belongs is not unique, a prompt message indicating that revenue sharing is not supported is sent to the client terminal, and revenue sharing data is not generated.

[0028] In this embodiment, the method further includes: receiving a push success receipt returned from the revenue sharing system, and updating the status of the receipt corresponding to the receipt confirmation to "data pushed". The push success receipt is a prompt message generated by the revenue sharing system after receiving the revenue sharing data.

[0029] In this embodiment, the rental and sales system includes: a company information synchronization module, used to send its stored company information to the revenue sharing system; a payment confirmation module, used to generate a payment confirmation slip when the payment status of a payment order is detected as paid; and a revenue sharing data push module, used to generate revenue sharing data based on the payment confirmation slip, wherein the revenue sharing data is used to trigger the revenue sharing system to perform revenue sharing operations based on the company information and the revenue sharing data.

[0030] Based on the inventive concept of the above embodiments, this application also provides a method for revenue sharing in rental and sales business, applied to a revenue sharing system, wherein the revenue sharing system is communicatively connected to the rental and sales system, and the method includes: the revenue sharing system receiving company information and revenue sharing data sent by the rental and sales system; and performing revenue sharing operations based on the company information and revenue sharing data.

[0031] In this embodiment, after receiving the revenue sharing data, the method further includes: returning a successful push receipt to the rental and sales system. The successful push receipt is used to trigger the rental and sales system to update the status of the receipt corresponding to the receipt confirmation to "data pushed".

[0032] As mentioned above, the message exchange between the rental / sales system and the revenue-sharing system is as follows: Figure 3 As shown.

[0033] In summary, in a specific embodiment, after the rental and sales transaction payment is received, the following steps are performed in both the rental and sales system and the revenue sharing system: Company Information Pre-Synchronization: Before commencing revenue sharing, staff maintain all company information (including company name, unified social credit code, bank name, bank account number, and region) in the rental and sales system. The company information synchronization module uses a dedicated interface to synchronize company information from the rental and sales system to the revenue sharing system in real time. If company information is added, modified, or deleted in the rental and sales system, the company information synchronization module immediately pushes the changes to the revenue sharing system to ensure dynamic consistency of company information between the rental and sales system and the revenue sharing system, thereby ensuring the accuracy of subsequent revenue sharing entity information.

[0034] To further enhance the security of changes to critical information, this embodiment also provides an optional review mechanism. Specifically, in the company information management backend of the rental and sales system, the administrator can pre-configure a list of "important companies" (such as the head office, branches in key regions, etc.). When information about these important companies (especially core fields such as bank accounts and unified social credit codes) is modified, the company information synchronization module will not immediately trigger synchronization. Instead, the rental and sales system will generate a "Company Information Change Pending Review" record and notify the designated administrator via internal message or email. Only after the administrator approves the change will the rental and sales system perform the synchronization operation with the revenue sharing system; if the review fails, the modification will be rejected, and the company information in the revenue sharing system will remain unchanged. This mechanism ensures efficient information synchronization while adding a layer of security for critical data.

[0035] Payment Success Confirmation: The payment confirmation module of the rental and sales system receives payment success results from banks or payment platforms in real time. If the payment status of a certain order is detected as "paid", the system immediately confirms the payment for the order and generates a payment confirmation form. The payment confirmation form includes information such as order number, transaction number, actual amount received, company information (matched from the rental and sales system's company information database), and payment confirmation time.

[0036] Automatic generation of revenue sharing data: After the payment is confirmed, the revenue sharing data push module automatically generates standardized revenue sharing data based on the payment confirmation information. The revenue sharing data includes the company information (name, unified social credit code), payment order number, actual payment amount, transaction number, and payment confirmation time, and the revenue sharing data corresponds one-to-one with the payment confirmation.

[0037] Real-time push of accounting data: The accounting data push module pushes standardized accounting data to the accounting system in real time through the interface module; the data is encrypted during the push process to ensure data security; if the push fails, the system immediately triggers a retry mechanism (retry 3 times, with an interval of 1 minute each time). If the retry still fails, an alarm message is pushed to the system terminal and mobile terminal of the finance personnel to remind them to handle it manually.

[0038] To enhance the adaptability of the rental and sales system to different business scenarios and network environments, the retry mechanism in this embodiment supports flexible configuration. System administrators can customize retry parameters in the "Push Policy Configuration" interface in the backend, based on the actual business requirements for timeliness and reliability. For example, for large transactions, it can be set to "retry 5 times, with an interval of 30 seconds each time"; for non-core businesses, it can be set to "retry 2 times, with an interval of 2 minutes each time". The configuration parameters are associated with specific revenue sharing rules or company information, making the retry strategy more business-oriented and improving the flexibility and robustness of the entire revenue sharing process.

[0039] Rental and sales system revenue sharing status update: After the revenue sharing data is successfully pushed, the revenue sharing system returns a successful push receipt to the rental and sales system through the integration module; after receiving the receipt, the rental and sales system automatically updates the revenue sharing status of the payment order to "data pushed" and saves the push time and receipt information to the payment order ledger; after receiving the revenue sharing data, the revenue sharing system completes the revenue sharing operation according to its own revenue sharing process, and the rental and sales system can also query the revenue sharing progress through the integration module.

[0040] To achieve closed-loop management and status traceability of the entire revenue sharing process, this embodiment further provides a revenue sharing result feedback function. After completing fund transfer or internal accounting based on the received revenue sharing data, the revenue sharing system generates a "Revenue Sharing Result Notification" containing information such as the successful revenue sharing status, revenue sharing transaction number, and actual revenue sharing time. This notification is then proactively fed back to the rental and sales system in real time through the integration module. Upon receiving this notification, the status update module of the rental and sales system automatically updates the revenue sharing status of the corresponding payment order from "Data Pushed" to "Revenue Sharing Completed" and records the details of the revenue sharing result in the order ledger. This setup allows business personnel to track the entire process from payment receipt to revenue sharing completion within the rental and sales system without switching systems, greatly improving business transparency and operational efficiency.

[0041] Revenue sharing rules: The rental and sales system has a pre-set revenue sharing rule that "each expense belongs to a single company". When generating revenue sharing data, the system automatically verifies whether the company to which the payment order belongs is unique. If it detects that the same payment order belongs to multiple companies, it immediately refuses to generate revenue sharing data and sends a prompt message to the staff.

[0042] Furthermore, the rental and sales system also includes a refund processing module. This application can automate the refund process in real time without manual intervention, while also simplifying subsequent revenue sharing and accounting logic. Specifically, when the rental and sales system generates a refund order and completes the refund payment, the refund processing module generates a corresponding "refund confirmation slip." This module then generates "refund revenue sharing data" based on the original payment order corresponding to the refund order. Its data structure and logic correspond to the payment revenue sharing data, but the fund flow is identified as "expenditure." This refund revenue sharing data is then automatically pushed to the revenue sharing system through the same interface module. After receiving the data, the revenue sharing system triggers a refund revenue sharing operation (such as fund deduction) to complete the accounting processing of the refund funds. After processing, the revenue sharing system sends the refund revenue sharing result back to the rental and sales system, which updates the revenue sharing status of the refund order and the associated payment order based on the refund revenue sharing result. This setup seamlessly integrates the refund process into the automated accounting system. Instead of increasing the complexity of accounting, it further strengthens the system's ability to manage cash flow through the unified processing of the two opposite processes of receiving payments and refunds, ensuring the consistency of accounting data under various business changes.

[0043] In some embodiments, to achieve stable, efficient, and secure data interaction between the rental / sales system and the revenue-sharing system, a "connection module" is used to establish a communication connection between the two systems. This connection module is not a separate physical server, but rather a logical collective term for a set of software interfaces (APIs) defined according to specific specifications and data exchange protocols between the rental / sales system and the revenue-sharing system. The connection module has bidirectional communication capabilities.

[0044] In one specific embodiment, the docking module includes the following technical implementation details.

[0045] First, the communication architecture and protocol are as follows: The interface module builds a communication channel based on the HTTPS protocol, utilizing its transport layer security encryption mechanism to ensure that all data transmitted over the network (especially company bank account information, transaction amounts, etc.) is encrypted, preventing data from being stolen or tampered with during transmission. The communication mode adopts a request-response model and also includes an asynchronous notification mechanism. For example, the rental and sales system actively pushing revenue sharing data is a request, and the revenue sharing system returning a "successful push receipt" is a response; while the revenue sharing system actively sending back the result after completing the revenue sharing is an asynchronous notification.

[0046] Secondly, the data format and standards are as follows: All data exchanged through the interface module can be encapsulated using the industry-standard JSON format. JSON format has advantages such as clear structure and ease of parsing. Each data packet contains a predefined data pattern. For example, the JSON structure of the revenue sharing data packet includes required fields such as belongCompany, orderNo, and actualAmount. This standardized format ensures that the rental and sales system and the revenue sharing system can correctly parse and process information.

[0047] In addition, it is necessary to define the interfaces for implementing each function. That is, the interface module is specifically implemented by a set of well-defined API interfaces, mainly including: Company Information Synchronization Interface: Called by the rental and sales system, this interface is used to fully synchronize or incrementally update company entity information with the revenue sharing system. It supports operations such as creation, updating, and querying.

[0048] The revenue sharing data push interface is called by the rental and sales system to send the generated standardized revenue sharing data to the revenue sharing system, triggering the revenue sharing process. Furthermore, this interface can be designed so that when revenue sharing data for the same payment order is pushed repeatedly, the revenue sharing system will only process it once. This prevents the revenue sharing data for the same payment order from being received repeatedly due to network timeouts or other reasons, thereby preventing duplicate revenue sharing for the same payment order.

[0049] Push status receipt interface: Called by the revenue sharing system. After successfully receiving the revenue sharing data, the revenue sharing system returns a success receipt to the rental and sales system through this interface so that the rental and sales system can update the order status.

[0050] Revenue sharing result callback interface: Called by the revenue sharing system, after the fund sharing operation is completed, the final result (success / failure, serial number, timestamp) is notified to the rental and sales system through this interface, completing the status closure loop.

[0051] In addition, the interface module can also use methods such as API keys or digital signatures to ensure the legitimacy of the identities of both communicating parties. For example, with each request, the caller (e.g., the rental / sales system) needs to include its unique API key in the request message header and use a key shared by the rental / sales system and the revenue-sharing system to encrypt the parameters, timestamps, etc. in the request message to generate a signature. The receiver (e.g., the revenue-sharing system) verifies the validity of the API key, and only processes the request message if the verification is successful, thus effectively preventing unauthorized access.

[0052] In summary, the "interface module" in this embodiment constructs a secure data communication bridge between the rental and sales system and the revenue sharing system by employing standardized protocols, structured data, clear interface definitions, and robust security measures. It is not only a channel for technical connection but also a guarantee for seamless integration of business rules and processes between the systems, serving as the core infrastructure for achieving full automation of the revenue collection and distribution process.

[0053] In summary, this application has at least the following innovative solutions: The real-time synchronization mechanism of company information between the rental and sales system and the revenue sharing system ensures dynamic consistency of company information and guarantees the accuracy of revenue sharing entity information. After the rental and sales system confirms receipt of payment, it automatically generates standardized revenue sharing data and pushes it to the revenue sharing system in real time through an encrypted interface, eliminating the need for manual data entry. Design an automatic retry mechanism and a manual alarm mechanism for failed revenue sharing data push to ensure the reliability of revenue sharing data push. The system pre-defines the revenue sharing rule that "each expense belongs to a single company," adapting to the revenue sharing needs of property rental and sales businesses and simplifying the revenue sharing process.

[0054] This application has at least the following beneficial effects: (1) Significantly improve the efficiency of accounting and reduce the data error rate: The automatic generation and real-time push of accounting data completely eliminates the step of manually entering accounting data, which greatly improves the efficiency of accounting work; at the same time, the standardized accounting data generation mechanism avoids data errors caused by manual entry and reduces the risk of accounting errors.

[0055] (2) Ensure consistency of accounting entity information: The real-time synchronization mechanism of company information realizes dynamic consistency of company information between the rental and sales system and the accounting system, solves the problem of information inconsistency caused by manual information updates, provides accurate entity information for accounting work, and further ensures the accuracy of accounting work.

[0056] (3) Simplify the accounting process to meet the needs of property rental and sales business: The accounting rule of "single expense belongs to a single company" has been customized and simplified for the accounting needs of property rental and sales business. It has eliminated the complicated accounting process of multiple companies, reduced the difficulty of accounting, and improved the pertinence and efficiency of accounting work.

[0057] (4) Improve the reliability of split data push: Through the automatic retry mechanism and manual alarm mechanism, the problem of split data push failure is effectively solved, ensuring that split data can be pushed to the split system in a timely and accurate manner, and avoiding split delays caused by push failure.

[0058] Based on the inventive concept of the above embodiments, this application also provides a computer-readable storage medium storing a computer program, wherein the computer program, when executed by a processor, performs the steps of the method described in any of the above embodiments. The following is in conjunction with... Figure 4 This describes the execution process of the above embodiments on a computer-readable storage medium.

[0059] like Figure 4 As shown, it illustrates the computer-readable storage medium of this application. The integrated units described above, if implemented as software functional units and sold or used as independent products, can be stored in the computer-readable storage medium 200. Based on this understanding, the technical solution of this application, 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. This computer software product is stored in a storage medium and includes several instructions / computer programs to cause an Internet of Things device (which may be a personal computer, server, or network terminal, etc.) or processor to execute all or part of the steps of the methods of various embodiments of this application. The aforementioned storage medium includes various media such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks, as well as electronic terminals such as computers, mobile phones, laptops, tablets, and cameras that have the aforementioned storage media.

[0060] The execution process of program data in a computer-readable storage medium can be described with reference to the above-described method embodiments of this application, and will not be repeated here.

[0061] The above description is merely an embodiment of this application and does not limit the patent scope of this application. Any equivalent structural or procedural transformations made using the content of this application's specification and drawings, or direct or indirect applications in other related technical fields, are similarly included within the patent protection scope of this application.

[0062] Those skilled in the art will understand that, in the above-described method of the specific implementation, the order in which each step is written does not imply a strict execution order and does not constitute any limitation on the implementation process. The specific execution order of each step should be determined by its function and possible internal logic.

Claims

1. A method for revenue sharing in rental and sales transactions, characterized in that, The method is applied to a rental and sales system, which is communicatively connected to a revenue-sharing system, and includes: Send its stored company information to the revenue sharing system; When the payment status of a payment order is detected as "paid", a payment confirmation is generated. Based on the payment confirmation, splitting data is generated, wherein the splitting data is used to trigger the splitting system to perform splitting operations based on the company information and the splitting data.

2. The method for revenue sharing in rental and sales transactions according to claim 1, characterized in that, The company information shall include at least the company name, unified social credit code, bank name, bank account number and region; the payment confirmation shall include at least the order number, transaction number, actual amount received, company information and payment confirmation time.

3. The method for revenue sharing in rental and sales transactions according to claim 1, characterized in that, The revenue sharing data includes: company information, payment order number, actual payment amount, transaction number, and payment confirmation time, and the revenue sharing data corresponds one-to-one with the payment confirmation slip.

4. The method for revenue sharing in rental and sales transactions according to claim 2, characterized in that, The step of generating split revenue data based on the payment confirmation includes: Before generating the revenue sharing data, it is checked whether the company attribution in the attribution company information is unique; When the uniqueness of the attributing company is detected, revenue sharing data is generated; And when it is detected that the company to which the account belongs is not unique, a prompt message indicating that revenue sharing is not supported is sent to the client terminal, and revenue sharing data is not generated.

5. The method for revenue sharing in rental and sales transactions according to claim 1, characterized in that, The method further includes: The system receives a push success receipt from the revenue sharing system and updates the status of the payment receipt corresponding to the payment confirmation to "data pushed". The push success receipt is a prompt message generated by the revenue sharing system after it receives the revenue sharing data.

6. A method for revenue sharing in rental and sales transactions, characterized in that, The method is applied to a revenue-sharing system, which is communicatively connected to a rental / sales system, and includes: Receive company information and revenue sharing data sent by the rental and sales system; Based on the company information and the revenue sharing data, perform the revenue sharing operation.

7. The method for revenue sharing in rental and sales transactions according to claim 6, characterized in that, After receiving the revenue sharing data, the method further includes: returning a push success receipt to the rental and sales system, wherein the push success receipt is used to trigger the rental and sales system to update the status of the receipt corresponding to the receipt confirmation to "data pushed".

8. A rental and sales system, characterized in that, The rental and sales system is communicatively connected to the revenue sharing system, and the system includes: The company information synchronization module is used to send its stored company information to the revenue sharing system. The payment confirmation module is used to generate a payment confirmation form when the payment status of a payment order is detected as paid. The revenue sharing data push module is used to generate revenue sharing data based on the payment confirmation form. The revenue sharing data is used to trigger the revenue sharing system to perform revenue sharing operations based on the company information and the revenue sharing data.

9. A revenue-sharing system, characterized in that, The revenue sharing system is communicatively connected to the rental and sales system, and the system is used to execute the steps of the revenue sharing method for rental and sales business as described in any one of claims 6-7.

10. A computer-readable storage medium storing a computer program, characterized in that, When the computer program is executed by a processor, it implements the steps of the method described in any one of claims 1-5 or any one of claims 6-7.

Images