A method and system for auditing transactions on an e-commerce platform

Abstract

This invention relates to the field of digital technology in e-commerce and auditing services, and provides a method and system for auditing services transactions on e-commerce platforms, including the following steps: receiving payment instructions sent by the buyer's terminal, verifying the payment result and generating a transaction record, transferring the corresponding order amount to the platform's escrow account after verification, and updating the order status to pending fulfillment; controlling the order status based on the seller's fulfillment information, the buyer's confirmation information, and dispute instructions; and executing seller settlement when receiving a buyer's confirmation completion instruction and there are no dispute instructions for the order, transferring the corresponding funds in the platform's escrow account to the seller's account. By placing product review, professional screening, order snapshots, and escrow settlement in a unified process, the controllability and structure of the auditing service transaction process are achieved.

Description

Technical Field

[0001] This invention relates to the field of digital technology in e-commerce and auditing services, and in particular to a transaction method and system for an e-commerce platform for auditing services. Background Technology

[0002] Currently, there are generally three pathways for SMEs to obtain audit services. First, SMEs directly contact accounting firms or audit service providers offline to complete the engagement, signing of contracts, and payment. Second, they use general-purpose e-commerce platforms to publish or browse audit service information. Third, they receive recommendations for value-added audit services through corresponding entry points within the financial software ecosystem.

[0003] While the aforementioned implementation paths can meet the audit service procurement needs of enterprises to a certain extent, they still generally suffer from the following shortcomings: First, there is a lack of a unified and professional online mechanism for the qualification verification and capability demonstration of audit service providers, making it difficult for buyers to effectively judge service quality; second, the billing logic for different product forms such as audit packages, expert consultations, and audit software subscriptions varies greatly, and existing platforms typically lack the transaction processing capabilities to accommodate buy-out, pay-per-use, and subscription models; third, the lack of fund escrow, dispute freezing, evidence retention, and evaluation retrospective mechanisms tailored to the characteristics of audit services during the transaction process results in insufficient protection of the rights and interests of both buyers and sellers; and fourth, existing platforms typically struggle to organize searches and screenings based on professional dimensions such as audit type, applicable industry, and compliance standards, leading to low efficiency in matching supply and demand. Summary of the Invention

[0004] The purpose of this invention is to provide a transaction method and system for audit services on an e-commerce platform, in order to solve the problems of insufficient professional review in the audit service transaction process, single billing model, weak transaction security mechanism, and insufficient traceability of quality evaluation in the existing technology.

[0005] To achieve the above objectives, the present invention provides the following technical solution: a method for auditing services transactions on an e-commerce platform, comprising the following steps: Receive product listing requests sent from the seller's terminal; The product release request is reviewed, and the product status is set according to the review results; Receive query requests sent by buyer terminals, filter and sort the set of tradable goods, and return a list of goods; In response to the order placement command sent by the buyer's terminal, generate order data and product snapshot data for the target product; Receive payment instructions sent by the buyer's terminal, verify the payment result and generate a transaction record. After verification, transfer the corresponding order amount to the platform's escrow account and update the order status to pending fulfillment. Control the order status based on seller fulfillment information, buyer confirmation information, and dispute instructions; Upon receiving confirmation from the buyer that the order is complete and there are no disputes, the seller settlement is executed, transferring the corresponding funds from the platform escrow account to the seller's account.

[0006] Furthermore, the aforementioned product posting request should include at least the following information: basic product information, service type, billing model, service scope, applicable industry, applicable compliance standards, delivery cycle, price information, and seller qualification information.

[0007] Furthermore, the review of the product posting request includes: verifying the seller's identity information, professional qualification information, service capability information, and historical credit information; Verify that the service scope, billing model, applicable industries, applicable compliance standards, and delivery method in the product release request comply with the preset release specifications; Products that pass the review will be assigned a listing label, while products that fail the review will generate a rejection reason and send it to the seller's terminal.

[0008] Furthermore, the filtering and sorting of the tradable goods set includes: establishing a search index based on the goods name, goods description, and goods tags; Upon receiving keywords, keyword matching is performed on the product name, product description, and product tags; The results are sorted based on at least one of the following: latest listing time, sales volume, rating score, price, and seller credit rating.

[0009] Furthermore, before generating order data and product snapshot data for the target products, the method further includes: receiving shopping cart operation information from buyers for multiple target products; maintaining shopping cart records based on the shopping cart operation information; and extracting the selected products from the shopping cart records and generating corresponding order details when an order instruction is received. The product snapshot data includes the service content, billing mode, price parameters, validity period parameters and / or number of uses parameters, seller identifier, unit price at the time of order placement, service delivery cycle, refund rules, and after-sales rules.

[0010] Furthermore, the process of receiving payment instructions from the buyer's terminal, verifying the payment result, and generating a transaction record includes: Receive balance payment requests or third-party payment requests; When a third-party payment request is made, the system receives a payment callback notification returned by the third-party payment platform and performs signature verification and order amount consistency verification on the payment callback notification. After verification, the payment record is written, the order payment status is updated, and the corresponding funds are credited to the platform's escrow account.

[0011] Furthermore, the order status includes pending fulfillment, fulfillment in progress, and dispute resolution in progress. Controlling the order status based on seller fulfillment information, buyer confirmation information, and dispute instructions includes: The settlement process is frozen upon receiving a dispute instruction. Receive dispute evidence and generate dispute resolution records; based on the administrator's review results, execute at least one of the following actions: full refund, partial refund, continued performance, or continued settlement.

[0012] Furthermore, after transferring the corresponding funds in the platform escrow account to the seller's account, the process also includes the following steps: verifying the eligibility for evaluation, and receiving the buyer's evaluation information for the completed order when the verification is successful, so as to update the quality evaluation indicators of the target product.

[0013] Furthermore, the transaction method also includes: When at least one of the following events occurs: product review status change, order status change, payment completion, dispute resolution completion, new review addition, and subscription expiration, a notification record corresponding to the event is generated and associated with the target user's account so that the target user can mark it as read and count the number of unread messages.

[0014] On the other hand, an auditing service e-commerce platform transaction system is provided, comprising: a receiving unit for receiving product posting requests sent by seller terminals; an auditing unit for auditing the product posting requests and setting the product status according to the audit results; a first processing unit for receiving query requests sent by buyer terminals, filtering and sorting the set of tradable products, and returning a product list; a second processing unit for responding to order placement instructions sent by buyer terminals, generating order data and product snapshot data for the target product; a first payment unit for receiving payment instructions sent by buyer terminals, verifying the payment results and generating a transaction record, transferring the corresponding order amount to the platform escrow account after verification, and updating the order status to pending fulfillment; an auditing unit for controlling the order status according to seller fulfillment information, buyer confirmation information, and dispute instructions; and a second payment unit for executing seller settlement when receiving a buyer confirmation completion instruction and there are no dispute instructions for the order, transferring the corresponding funds in the platform escrow account to the seller account.

[0015] Analysis reveals that this invention discloses a transaction method and system for audit services on an e-commerce platform. By placing product review, professional screening, order snapshots, and escrow settlement within a unified process, it achieves controllability and structuring of the audit service transaction process. By recording billing models, validity period parameters, and usable usage parameters at the order level, it improves compatibility with scenarios involving buy-out, pay-per-use, and subscription models. By introducing platform escrow, dispute freezing, evidence retention, and evaluation qualification verification mechanisms, it enhances the protection of the rights and interests of both buyers and sellers. By organizing searches based on dimensions such as audit type, applicable industry, and compliance standards, it improves the matching efficiency between audit services and enterprise needs. Through the correlation between pre-audit analysis results and products, orders, or consultation sessions, it enhances the platform's ability to support decision-making throughout the entire audit service transaction process. Attached Figure Description

[0016] The accompanying drawings, which form part of this application, are used to provide a further understanding of the invention. The illustrative embodiments of the invention and their descriptions are used to explain the invention and do not constitute an undue limitation of the invention. Wherein: Figure 1 A flowchart of an embodiment of the present invention.

[0017] Figure 2 A flowchart illustrating the product release and review process according to an embodiment of the present invention.

[0018] Figure 3 A flowchart illustrating the order creation and payment process according to an embodiment of the present invention. Detailed Implementation

[0019] The present invention will now be described in detail with reference to the accompanying drawings and embodiments. Various examples are provided by way of explanation and not by way of limitation. Indeed, those skilled in the art will recognize that modifications and variations can be made to the invention without departing from its scope or spirit. For example, a feature shown or described as part of one embodiment may be used in another embodiment to produce yet another embodiment. Therefore, it is desirable that the invention encompass such modifications and variations falling within the scope of the appended claims and their equivalents.

[0020] In the description of this invention, the terms "longitudinal," "lateral," "upper," "lower," "front," "rear," "left," "right," "vertical," "horizontal," "top," and "bottom," etc., indicate the orientation or positional relationship based on the orientation or positional relationship shown in the accompanying drawings. They are used only for the convenience of describing the invention and do not require the invention to be constructed and operated in a specific orientation; therefore, they should not be construed as limitations on the invention. The terms "connected," "linked," and "set up" used in this invention should be interpreted broadly. For example, they can refer to a fixed connection or a detachable connection; a direct connection or an indirect connection through intermediate components; a wired connection, a radio connection, or a wireless communication signal connection. Those skilled in the art can understand the specific meaning of the above terms according to the specific circumstances.

[0021] The accompanying drawings illustrate one or more examples of the invention. The detailed description uses numerals and letters to refer to features in the drawings. Similar or analogous reference numerals in the drawings and description have been used to refer to similar or analogous parts of the invention. As used herein, the terms “first,” “second,” “third,” and “fourth,” etc., are used interchangeably to distinguish one component from another and are not intended to indicate the location or importance of individual components.

[0022] In this embodiment, the audit service e-commerce platform is preferably built using a B / S architecture. The front end can be accessed through web pages, mini-programs, mobile applications, or other clients with network access capabilities. The back end consists of an application server, a database server, a file storage server, a message service component, a payment interface component, and a model inference service component. The platform can be deployed on a single server or in a multi-node cluster in a cloud computing environment. When using a distributed deployment, the various business modules can communicate through interface calls, message queues, event buses, or shared data buses to ensure data consistency and status synchronization among product review, search matching, order processing, payment escrow, dispute resolution, evaluation retrospective, and audit auxiliary analysis.

[0023] In a preferred embodiment, users on the platform can be categorized into at least three roles: buyers, sellers, and administrators. Buyers are typically small and medium-sized enterprises (SMEs) with needs for auditing, tax compliance, internal control assessments, special inspections, or consulting. Sellers are typically accounting firms, audit consulting agencies, tax service providers, or professional entities with corresponding service capabilities. Administrators are responsible for implementing platform governance actions, such as reviewing products, handling disputes, managing user status, and conducting platform operation statistics. The user management module can collect account identifiers, contact information, entity information, login credentials, and role application information during the user registration phase. After login, it performs identity verification and permission checks on access requests based on tokens, session identifiers, or other authentication mechanisms to ensure that different roles can only access functional interfaces that match their roles.

[0024] Furthermore, to adapt to the transaction needs of different types of goods in audit service scenarios, the goods objects maintained by the goods management module may include, but are not limited to, the following fields: goods identifier, seller identifier, goods name, goods description, service type, service scope, applicable industry, applicable compliance standards, delivery cycle, delivery form, billing model, price information, feature list, specification parameter list, tag list, supported regions, after-sales rules, refund rules, review status, listing status, delisting reason, evaluation statistics, and sales statistics. The service type may include audit packages, audit software, audit consulting services, financial and tax compliance review services, internal control review services, special verification services, or other digital goods forms related to audit business; the billing model may include buy-out, pay-per-use, monthly subscription, and annual subscription. By organizing goods objects using structured fields, the platform can establish specialized transaction models for service elements unique to the audit field, rather than simply using the single physical goods model of a general e-commerce platform.

[0025] In this implementation, the platform can also maintain several core business data objects. For example, user account data objects can record account balance, account status, real-name authentication status, role type, most recent login time, and reputation score; order data objects can record order number, buyer identifier, seller identifier, total order amount, payment status, fulfillment status, refund status, settlement status, creation time, and update time; product snapshot data objects can record the service content, billing mode, price parameters, delivery cycle, applicable industry, refund rules, and after-sales rules of the corresponding product at the time of ordering, so that even after the original product information is edited or removed from the shelves, historical orders can still be fulfilled and disputes can be resolved based on the fixed transaction conditions at the time of ordering; transaction flow data objects can record payment flow number, fund direction, fund type, payment channel, amount, status, and timestamp; dispute record data objects can record the dispute initiator, dispute reason, evidence materials, processing conclusion, and processing time; evaluation record data objects can record rating, evaluation content, advantages, disadvantages, evaluation time, and seller's reply content; and notification data objects can record notification type, associated business object, recipient, read status, and sending time. By organizing and associating the aforementioned data objects, a traceable, retrospective, and auditable data loop can be formed throughout the entire transaction process.

[0026] The audit service method for e-commerce platform transactions described in this invention may include a product posting and review stage, a search and order placement stage, a payment and escrow stage, a performance and dispute resolution stage, a settlement and evaluation stage, and an optional audit auxiliary analysis stage. The invention will be described in detail below with reference to the business activities at each stage.

[0027] First, during the product listing and review stage, the seller sends a product listing request to the platform, and the platform receives the product information submitted by the seller for the intended transaction. In addition to the usual product name, price, and description, the product listing request preferably includes professional fields required for audit services, such as audit type, applicable industry, applicable company size, applicable compliance standards, service delivery cycle, required documentation list, deliverables description, service boundaries description, supported regions, communication methods, billing model, and seller qualification information. For audit software or SaaS products, the product listing request may also include authorization method, number of accounts that can be activated, functional module description, trial rules, and version validity period description; for consulting services, it may also include the number of service sessions, session duration, appointment rules, and information on available expert levels.

[0028] This method includes the following steps: Step S101: Receive the product publishing request sent by the seller terminal; Step S102: Review the product release request and set the product status according to the review result; Step S103: Receive the query request sent by the buyer's terminal, filter and sort the set of tradable goods, and return the list of goods; Step S104: In response to the order placement instruction sent by the buyer's terminal, generate order data and product snapshot data for the target product; Step S105: Receive the payment instruction sent by the buyer's terminal, verify the payment result and generate a transaction record. After verification, transfer the corresponding order amount to the platform's escrow account and update the order status to pending fulfillment. Step S106: Control the order status based on the seller's fulfillment information, the buyer's confirmation information, and the dispute instruction; Step S107: Upon receiving the buyer's confirmation of completion and the order's lack of dispute, execute the seller settlement, transferring the corresponding funds from the platform's escrow account to the seller's account.

[0029] like Figures 1-3 As shown, in step S101, after receiving the product posting request from the seller's terminal, the platform can first perform a completeness check on the request content. The completeness check can include at least: checking whether required fields are missing, checking whether the price and billing fields are in valid formats, checking whether the service period is within a preset range, checking whether tags belong to the allowed set, and checking whether the file format and size of uploaded attachments meet the platform's requirements. When the check results indicate missing fields, incorrect formats, or obvious conflicts, the platform can directly return a correction prompt and temporarily save the product as a draft or pending supplementation state for the seller to modify and improve later.

[0030] In step S102, the aforementioned product posting request includes at least basic product information, service type, billing model, service scope, applicable industry, applicable compliance standards, delivery cycle, price information, and seller qualification information. The platform verifies the qualifications and reviews the content of the product posting request based on preset review rules. Preferably, the preset review rules can be divided into two categories: entity qualification review rules and product content review rules. Entity qualification review rules may include verification of factors such as seller identity, unified social credit code, business license, number of practitioners, historical transaction records, historical disputes, account status, and historical credit rating. Product content review rules may include verification of whether the product description is clear and complete, whether it exceeds the seller's qualification scope, whether it contains false advertising information, whether it lacks necessary service boundary descriptions, whether there is a conflict between the billing model and delivery model, and whether the applicable industry and applicable compliance standards are clearly stated. For review items requiring manual judgment, the platform can push the corresponding product to the administrator terminal for manual review; for review items that can be automatically judged, the platform can directly provide a review conclusion through the rule engine.

[0031] In one optional implementation, the product review results can include at least three categories: approved, rejected, and pending supplementation. For approved products, the platform assigns a listing tag and adds them to the tradable product set; for rejected products, the platform records the reason for rejection, the triggering rule identifier, and the processing time, and returns the corresponding reason to the seller's terminal; for products pending supplementation, the platform may require the seller to resubmit qualification attachments, supplement the service scope description, or revise the price parameters. To improve transaction security, the platform may also restrict the display of unapproved products to buyers, or clearly indicate their unorderable status when displayed, to prevent service providers who have not completed the review from directly entering the transaction process.

[0032] In some implementations, sellers can edit, delist, or relist products that have already been listed. When a seller only modifies fields that do not affect the substance of the transaction, such as display images, some descriptive text, or tag information, the platform can directly update the product information. When a seller modifies core transaction fields such as price, billing model, delivery cycle, service scope, applicable standards, or refund rules, the platform can place the modified product back into a pending review state. This approach ensures that the product content entering the transaction process is always verifiable, controllable, and consistent with the seller's qualifications.

[0033] During the search and order placement phase, the buyer sends a query request to the platform to browse, filter, and compare audit service products from different sellers. The query request can include at least one of the following: audit type, service category, applicable industry, applicable compliance standards, price range, billing model, keywords, seller credit rating, delivery cycle, supported regions, and sorting method. To accommodate the specialized search needs of audit services, the search and filtering module can create indexes for fields such as product name, product summary, product tags, service description, applicable industry, and applicable standards. Keywords entered by the buyer can be matched against these indexes, thereby improving search recall and positioning accuracy.

[0034] Specifically, in step S103, the review of the product posting request includes: verifying the seller's identity information, professional qualification information, service capability information, and historical credit information; The platform verifies whether the service scope, billing model, applicable industry, applicable compliance standards, and delivery method in the product listing request conform to the preset listing specifications. For approved products, a listing badge is assigned; for rejected products, a rejection reason is generated and fed back to the seller's terminal. After receiving a query request from the buyer's terminal, the platform can first parse the query parameters and construct combined query conditions. For structured filtering conditions, such as audit type, price range, billing model, applicable industry, and applicable compliance standards, the platform can preferentially use exact matching or range matching. For unstructured keywords, the platform can perform keyword matching, word segmentation matching, regular expression matching, fuzzy matching, or semantic relevance matching on the product name, description, and tags.

[0035] In some implementations, to improve the usability of search results, the platform may also sort candidate results based on at least one of the following: listing time, sales volume, rating score, price, platform recommendation weight, and seller credit rating, and return the product list and pagination information in a paginated manner.

[0036] During the product details display phase, in addition to showing basic information such as product name, price, service scope, applicable industries, and delivery cycle, the platform can also aggregate and display product ratings, number of reviews, historical sales volume, seller response speed, seller information, and summaries of historical service cases. For subscription-based or pay-per-use products, the platform can also display validity period information, remaining usage information, renewal rules, and applicable version information. Through these display methods, buyers can more fully understand the product boundaries and service conditions before making a transaction, thereby reducing information asymmetry.

[0037] In one optional implementation, buyers can directly place an order for a single target product, or add multiple target products to their shopping cart first. After receiving the buyer's shopping cart operation information, the shopping cart management module can perform operations such as adding products, removing products, modifying quantities, clearing the shopping cart, and checking for expired products. For scenarios supporting the purchase of multiple services at once, the shopping cart can contain products from multiple sellers simultaneously; before checkout, the platform can preferentially re-verify the availability, price validity, and inventory or service capacity status of each product. If a product is found to be unavailable, its price has been updated, or the seller has suspended services, the platform can mark the product as an anomaly and prompt the buyer to reconfirm, ensuring that subsequent orders are generated based on the latest tradable status.

[0038] In step S104, the filtering and sorting of the tradable goods set includes: establishing a search index for product name, product description, and product tags; performing keyword matching on product name, product description, and product tags upon receiving keywords; sorting the filtering results based on at least one of the following: latest listing time, sales volume, rating score, price, and seller credit rating; and generating order data and product snapshot data in response to the order instruction sent by the buyer's terminal. The order data preferably includes fields such as order identifier, buyer identifier, seller identifier, order time, total order amount, order details, payment status, fulfillment status, refund status, settlement status, and notification status. The product snapshot data is used to freeze key transaction conditions at the time of order placement, and may include at least the product name, service content, billing model, price parameters, discount parameters, validity period parameters, number of uses parameters, delivery cycle, applicable industry, applicable compliance standards, refund rules, after-sales rules, seller identifier at the time of order placement, and product version information. By writing product snapshot data when an order is generated, it prevents sellers from subsequently editing product information and causing uncertainties to existing orders, thus providing the platform with objective evidence for judgment in the event of a refund or dispute.

[0039] For different billing models, the platform can use different snapshot and order field organization methods. For example, when a product is purchased outright, the order data can record the one-time payment amount, delivery content, and delivery node; when a product is paid per use, the order data can record the total number of purchases, the number of uses, the remaining number of uses, the scope of each use, and the validity period of the uses; when a product is subscribed to monthly or annually, the order data can record the subscription start time, subscription end time, automatic renewal status, renewal price, service start / stop rules, and grace period information. This structured record allows the platform to create differentiated yet uniformly manageable transaction processing flows for different audit service products.

[0040] During the payment and escrow phase, buyers can complete payment via balance payment or third-party payment. Preferably, when the payment settlement module receives a payment instruction, it first verifies whether the order is in a payment-allowed state based on the order status, and generates the amount to be paid based on the order amount, discount information, and coupon information. If the buyer chooses balance payment, the platform can directly verify whether the buyer's account balance is sufficient, and write the corresponding funds into the platform's escrow account's internal accounting records after deducting the balance; if the buyer chooses third-party payment, the platform preferably generates payment request parameters and calls the third-party payment interface to guide the buyer to complete the payment through an external payment system.

[0041] In step S105, before generating order data and product snapshot data for the target products, the method further includes: receiving shopping cart operation information from buyers for multiple target products; maintaining shopping cart records based on the shopping cart operation information; and extracting the selected products from the shopping cart records and generating corresponding order details upon receiving an order instruction. The product snapshot data includes the service content, billing mode, price parameters, validity period parameters and / or usability parameters, seller identifier, unit price at the time of order placement, service delivery cycle, refund rules, and after-sales rules. For third-party payment methods, after receiving the payment callback notification from the third-party payment platform, the platform preferably verifies the callback signature, order identifier, payment amount, currency, payment status, and callback time to prevent accounting errors caused by forged callbacks, duplicate callbacks, or inconsistent amounts. In one implementation, the platform can establish an idempotent verification mechanism for the same order; when the same payment transaction has been processed, duplicate callback notifications will not be recorded again. After verification, the platform generates a payment transaction record, which records the payment channel, payment transaction number, amount received, payment time and payment status, and transfers the corresponding funds from the payment process to the platform's escrow account. At the same time, the order status is updated from pending payment to pending fulfillment.

[0042] In this invention, the aforementioned platform escrow account refers to an escrow accounting mechanism maintained by the platform at the business accounting level for temporarily storing the amount of paid orders. The escrow account is not limited to a single bank account; it can also manifest as an escrow fund pool within the platform's internal accounting system, a mapping relationship with a third-party payment guarantee account, or other fund control structures that embody the "pay first, settle later" logic. By recording the order payment amount in the escrow account first, instead of immediately settling it with the seller after payment, the platform can freeze and control the funds corresponding to the order in cases of incomplete performance, unconfirmed buyer transactions, disputes, or unprocessed refund requests, thereby enhancing transaction security.

[0043] During the fulfillment and dispute resolution phases, the order management module continuously receives seller fulfillment information, buyer feedback, and administrator processing information, driving the order status progression accordingly. Order statuses can include at least the following: pending payment, pending fulfillment, fulfilling, pending confirmation, dispute resolution, completed, and refunded. For audit packages or special audit products, sellers can upload fulfillment documents such as document receipt confirmation records, interim communication minutes, interim analysis results, preliminary drafts, final delivery instructions, or meeting minutes during the fulfillment process. For audit software subscription products, sellers can upload activation certificates, account activation records, authorization certificates, system usage instructions, or version upgrade records. For consulting services, sellers can upload appointment records, service start and end times, consultation minutes, and result summaries. All of the above fulfillment information can be associated with the corresponding order for subsequent review.

[0044] In step S106, receiving the payment instruction sent by the buyer's terminal, verifying the payment result, and generating a transaction record includes: receiving a balance payment request or a third-party payment request; when it is a third-party payment request, receiving a payment callback notification returned by the third-party payment platform, verifying the signature of the payment callback notification and checking the consistency of the order amount; after successful verification, writing the payment record, updating the order payment status, and crediting the corresponding funds to the platform's escrow account; if the seller submits a service completion application, the platform can push a confirmation notification to the buyer and trigger a confirmation countdown or confirmation window; when the buyer confirms that the service meets the agreed conditions, they can send a confirmation completion instruction, causing the order to enter the completed pending settlement or directly enter the completed state. If the buyer believes that the seller's delivery content is inconsistent with the agreement, has omissions, or does not meet the agreed standards, the buyer can initiate a dispute or refund application within a preset time. Upon receiving a dispute instruction, the platform preferably immediately freezes the settlement process of the corresponding order and updates the order status to "dispute in progress" to prevent the escrow funds from being released prematurely before the dispute is resolved.

[0045] To enhance the standardization of dispute resolution, the platform can further establish dispute record objects and allow buyers and sellers to upload evidence materials separately. Evidence materials may include order snapshots, service communication records, uploaded business documents, delivery deliverables, meeting minutes, timestamp logs, payment vouchers, and platform message records. The administrator terminal can read order snapshot data, payment records, performance logs, and evidence materials from both parties, and provide a resolution based on preset dispute resolution rules. The resolution can include at least one or more of the following: continued performance, partial refund, full refund, rejection of the dispute, and continued settlement. If the resolution is continued performance, the platform can put the order back into the performance status; if the resolution is a partial or full refund, the payment and settlement module can execute the refund according to the determined amount and simultaneously update the refund and settlement status.

[0046] In a preferred embodiment, to facilitate quantitative management of seller fulfillment quality, the platform can also record information such as fulfillment timeliness, initial response time, number of deliveries, number of times buyers supplement materials, number of disputes, and final resolution results at the order level, and update the seller's credit rating or service quality score accordingly. In this way, the platform can not only provide a dispute control mechanism for individual orders, but also improve the accuracy of subsequent product sorting and service provider selection by accumulating fulfillment quality data.

[0047] During the settlement and evaluation phase, when an order meets the preset settlement conditions, the payment settlement module executes the seller's settlement. Preferably, the settlement conditions include at least: the buyer confirms completion or the confirmation period has expired without initiating a dispute, there are no outstanding refund requests for the order, and the relevant risk control checks have been passed.

[0048] In step S107, the order status includes pending fulfillment, fulfillment in progress, and dispute resolution in progress. Controlling the order status based on seller fulfillment information, buyer confirmation information, and dispute instructions includes: freezing the settlement process upon receiving a dispute instruction; receiving dispute evidence and generating a dispute resolution record; and executing at least one of the following actions based on administrator review results: full refund, partial refund, continued fulfillment, or continued settlement. The platform can generate a settlement statement based on the total order amount, platform service fee rate, discount amount, refund amount, tax parameters, and other deduction parameters. The settlement statement may include order identifier, buyer identifier, seller identifier, amount due, amount refunded, platform service fee, settlement method, settlement time, and settlement status. For orders that meet the settlement conditions, the platform releases the corresponding funds in the escrow account and transfers them to the seller's account, while simultaneously generating a settlement transaction record.

[0049] Different billing models can be handled differently in terms of settlement. For example, for buy-out products, a single settlement can be executed after delivery and confirmation; for pay-per-use products, settlement can be completed after all uses are delivered, or it can be settled in stages after each confirmed use; for subscription products, periodic settlement can be executed according to the subscription period, or the escrow funds can be released in installments according to a preset ratio after deducting refunds and discounts. By configuring settlement rules differently according to billing models, the platform can ensure a unified escrow logic while taking into account the business characteristics of different product types.

[0050] Regarding message notifications, the notification module can automatically create notification records and push them to the target user's account when several key business events occur. These business events may include, but are not limited to: product approval, product rejection, product removal from the platform, successful order placement, payment completion, seller commencement of fulfillment, seller submission of completion application, buyer confirmation of completion, buyer initiation of dispute, dispute resolution completion, refund receipt, new review, and subscription expiration. Notifications can be delivered via in-app messages, SMS, email, or third-party push notifications. Users can mark notifications as read after viewing them, and the platform simultaneously maintains the number of unread notifications to improve the visibility and timeliness of the transaction process.

[0051] In some embodiments, the present invention may also include an audit-assisted analysis process, that is, introducing intelligent pre-audit analysis of financial documents outside or within the transaction process to assist buyers in product selection, seller communication, and contract fulfillment preparation. Specifically, buyers or sellers can upload financial statements, general ledger details, voucher images, contract texts, tax declarations, bank statements, inventory lists, or other documents related to auditing through the client. After receiving the uploaded files, the platform preferably first performs format and security checks, including checking file type, file size, whether it contains malicious code, and whether there is any unidentifiable damage; then, based on the file type, it calls the corresponding parsing strategy to perform text extraction, table reading, image recognition, or structured field extraction.

[0052] In one optional implementation, the audit analysis module can preset two types of analytical capabilities: text models and visual models. For reports, contracts, or explanatory materials from which text content can be directly extracted, the platform can invoke the text model to perform audit Q&A, risk summarization, and anomaly analysis. For scanned documents, invoice images, voucher images, or table screenshots, the platform can invoke the visual model or a combined visual-text model to perform content recognition and semantic understanding. The platform can also automatically select the appropriate model between text and visual models based on document type, content length, image quality, and business question type, and construct inference requests containing audit standard knowledge, analysis templates, and prompt rules to generate structured pre-audit analysis results.

[0053] The preliminary audit analysis results may include, but are not limited to, the following: risk warnings, clues to abnormal transactions, a list of suspected missing materials, suggested supplementary documents, audit focus points, explanations of key indicator fluctuations, risk warnings for contract terms, and suggested consultation directions. The platform can associate and store the preliminary audit analysis results with target products, target orders, or target consultation sessions. For example, when browsing a certain internal control audit service product, a buyer can upload some financial materials and receive preliminary risk warnings to help them determine whether they need to purchase the corresponding service. Similarly, after accepting an order, a seller can use the preliminary audit analysis results to determine the subsequent list of documents and key areas for verification, thereby improving fulfillment efficiency.

[0054] In another alternative implementation, the platform can also maintain session context and analysis history based on the pre-audit analysis results. For example, for financial documents uploaded multiple times by the same buyer in the same order, the platform can correlate the multiple analysis results and record them in chronological order to track the evolution of risk items later. For situations where the same seller provides similar industry services to multiple buyers, the platform can provide a standardized analysis Q&A process based on industry templates without disclosing the privacy information of other buyers, thereby further enhancing the platform's professional assistance capabilities.

[0055] To ensure the stability and security of the platform, in a preferred implementation, the platform can also establish access control, logging, and exception handling mechanisms. Regarding access control, different roles correspond to different interface access permissions. Sellers can only manage their own products and orders, buyers can only view orders and notifications related to themselves, and administrators can access review, dispute, and statistics functions. Regarding logging, the platform preferably records product listing review logs, order status change logs, payment callback processing logs, refund processing logs, dispute handling logs, review submission logs, and model call logs for auditing and troubleshooting. Regarding exception handling, when situations such as payment callback failure, file parsing failure, model call timeout, seller qualification expiration, abnormal product fields, or message push failure occur, the platform can place the corresponding business object in a state of pending retry, pending compensation, or pending manual handling, and generate an exception alarm.

[0056] In a preferred embodiment, after transferring the corresponding funds from the platform escrow account to the seller's account, the method further includes the following steps: verifying the eligibility for evaluation, and receiving the evaluation information submitted by the buyer for the completed order when the verification is successful, so as to update the quality evaluation index of the target product.

[0057] In a specific application example, a buyer from a small-to-medium-sized manufacturing enterprise intends to purchase tax compliance audit services. The buyer first logs into their account on the platform and enters search criteria such as "tax compliance audit," "manufacturing," and "annual inspection" on the search page. The search and filtering module matches products based on name, tags, applicable industry, and compliance standards, returning multiple candidate products that meet the criteria. The buyer further reviews the service scope, delivery time, rating, sales volume, and seller qualifications of each candidate product, then selects a pay-per-use tax compliance consulting service and adds it to their shopping cart, along with an annual subscription audit software product. Before checkout, the platform verifies that both products are tradable, and then generates order data and product snapshot data, which respectively record the pay-per-use frequency parameters and the annual subscription start and end parameters.

[0058] After the buyer completes payment, the platform credits the payment amount to the escrow account and updates the order status to "pending fulfillment." The seller then uploads a document checklist template and preliminary communication minutes to the platform, and the buyer uploads some financial documents as prompted. The audit analysis module performs a preliminary audit analysis on the uploaded financial statements and voucher images, outputting several tax risk warnings and a list of suggested supplementary documents. Based on the preliminary audit results, the seller further provides services and submits a completion application upon completion. After the buyer confirms that the service meets the agreed requirements, they send a completion confirmation instruction. The platform generates a settlement statement based on the order amount and platform service fee rate, releasing the escrow funds to the seller's account. Finally, the buyer submits a rating and review of the service product, and the platform updates the product's review statistics simultaneously. This example illustrates how the present invention integrates search, order placement, escrow, fulfillment, analysis, and evaluation into a single audit service e-commerce platform.

[0059] This invention also discloses an audit service e-commerce platform transaction system, comprising: a receiving unit for receiving product posting requests sent by seller terminals; an auditing unit for auditing product posting requests and setting product status based on the audit results; a first processing unit for receiving query requests sent by buyer terminals, filtering and sorting the set of tradable products, and returning a product list; a second processing unit for responding to order placement instructions sent by buyer terminals, generating order data and product snapshot data for the target product; a first payment unit for receiving payment instructions sent by buyer terminals, verifying the payment result and generating a transaction record, transferring the corresponding order amount to the platform escrow account after verification, and updating the order status to pending fulfillment; an auditing unit for controlling the order status based on seller fulfillment information, buyer confirmation information, and dispute instructions; and a second payment unit for executing seller settlement upon receiving a buyer confirmation completion instruction and finding no dispute instructions for the order, transferring the corresponding funds from the platform escrow account to the seller account.

[0060] Compared with existing technologies, this invention has at least the following beneficial effects: By placing product review, professional screening, order snapshots, and escrow settlement into a unified process, it achieves controllability and structuring of the audit service transaction process; by recording billing models, validity period parameters, and usable usage parameters at the order level, it improves compatibility with scenarios where buyout, pay-per-use, and subscription models coexist; by introducing platform escrow, dispute freezing, evidence retention, and evaluation qualification verification mechanisms, it enhances the protection of the rights and interests of both buyers and sellers; by organizing searches based on dimensions such as audit type, applicable industry, and compliance standards, it improves the matching efficiency between audit services and enterprise needs; and by associating pre-audit analysis results with products, orders, or consultation sessions, it enhances the platform's ability to support decision-making throughout the entire audit service transaction process.

[0061] The above description is merely a preferred embodiment of the present invention and is not intended to limit the invention. Various modifications and variations can be made to the present invention by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the present invention should be included within the scope of protection of the present invention.

Claims

1. A transaction method for auditing services on an e-commerce platform, comprising the following steps: Receive product listing requests sent from the seller's terminal; The product release request is reviewed, and the product status is set according to the review results; Receive query requests sent by buyer terminals, filter and sort the set of tradable goods, and return a list of goods; In response to the order placement command sent by the buyer's terminal, generate order data and product snapshot data for the target product; Receive payment instructions sent by the buyer's terminal, verify the payment result and generate a transaction record. After verification, transfer the corresponding order amount to the platform's escrow account and update the order status to pending fulfillment. Control the order status based on seller fulfillment information, buyer confirmation information, and dispute instructions; Upon receiving confirmation from the buyer that the order is complete and there are no disputes, the seller settlement is executed, transferring the corresponding funds from the platform escrow account to the seller's account.

2. The transaction method for an audit service e-commerce platform according to claim 1, characterized in that, The above-mentioned product posting request should include at least the following information: basic product information, service type, billing model, service scope, applicable industry, applicable compliance standards, delivery cycle, price information, and seller qualification information.

3. The transaction method for an e-commerce platform providing audit services according to claim 1, characterized in that, The review of the product posting request includes: verifying the seller's identity information, professional qualification information, service capability information, and historical credit information; Verify that the service scope, billing model, applicable industries, applicable compliance standards, and delivery method in the product release request comply with the preset release specifications; Products that pass the review will be assigned a listing label, while products that fail the review will generate a rejection reason and send it to the seller's terminal.

4. The transaction method for an e-commerce platform providing audit services according to claim 3, characterized in that, The filtering and sorting of the tradable goods set includes: establishing a search index based on the goods name, goods description, and goods tags; Upon receiving keywords, keyword matching is performed on the product name, product description, and product tags; The results are sorted based on at least one of the following: latest listing time, sales volume, rating score, price, and seller credit rating.

5. The transaction method for an e-commerce platform providing audit services according to claim 1, characterized in that, Before generating order data and product snapshot data for the target products, the process also includes: receiving shopping cart operation information from buyers for multiple target products; maintaining shopping cart records based on the shopping cart operation information; and extracting the selected products from the shopping cart records and generating corresponding order details when an order instruction is received. The product snapshot data includes the service content, billing mode, price parameters, validity period parameters and / or number of uses parameters, seller identifier, unit price at the time of order placement, service delivery cycle, refund rules, and after-sales rules.

6. The transaction method for an e-commerce platform providing audit services according to claim 1, characterized in that, The process of receiving payment instructions from the buyer's terminal, verifying the payment result, and generating a transaction record includes: Receive balance payment requests or third-party payment requests; When a third-party payment request is made, the system receives a payment callback notification returned by the third-party payment platform and performs signature verification and order amount consistency verification on the payment callback notification. After verification, the payment record is written, the order payment status is updated, and the corresponding funds are credited to the platform's escrow account.

7. The transaction method for an e-commerce platform providing audit services according to claim 1, characterized in that, The order status includes pending fulfillment, fulfillment in progress, and dispute resolution in progress. Controlling the order status based on seller fulfillment information, buyer confirmation information, and dispute instructions includes: The settlement process is frozen upon receiving a dispute instruction. Receive dispute evidence and generate dispute resolution records; based on the administrator's review results, execute at least one of the following actions: full refund, partial refund, continued performance, or continued settlement.

8. The transaction method for an e-commerce platform providing audit services according to claim 7, characterized in that, After transferring the corresponding funds from the platform escrow account to the seller's account, the process further includes the following steps: verifying the eligibility for evaluation, and receiving evaluation information submitted by the buyer for the completed order when the verification is successful, so as to update the quality evaluation indicators of the target product.

9. A transaction method for an e-commerce platform providing audit services according to claim 8, characterized in that, The transaction method also includes: When at least one of the following events occurs: product review status change, order status change, payment completion, dispute resolution completion, new review addition, and subscription expiration, a notification record corresponding to the event is generated and associated with the target user's account so that the target user can mark it as read and count the number of unread messages.

10. An audit service e-commerce platform transaction system, characterized in that, include: The receiving unit receives product posting requests sent by the seller's terminal; The review unit reviews the product release request and sets the product status based on the review results; The first processing unit receives query requests sent by the buyer's terminal, filters and sorts the set of tradable goods, and returns a list of goods. The second processing unit, in response to the order placement instruction sent by the buyer's terminal, generates order data and product snapshot data for the target product; The first payment unit receives payment instructions sent by the buyer's terminal, verifies the payment result and generates a transaction record. After verification, it transfers the corresponding order amount to the platform's escrow account and updates the order status to pending fulfillment. The review unit controls the order status based on seller fulfillment information, buyer confirmation information, and dispute instructions; The second payment unit, upon receiving confirmation from the buyer that the order is complete and there are no disputes, executes the seller settlement, transferring the corresponding funds from the platform escrow account to the seller's account.

Images