Vehicle selling information management method, device and system, computing equipment and storage medium

Abstract

The embodiment of the invention provides a vehicle selling information management method, device and system, computing equipment and a storage medium, and the method comprises the steps: calling a resource system corresponding to a target payment channel to pay a vehicle purchase order in response to the creation operation of the vehicle selling system on the vehicle purchase order; setting the state of the car purchase order based on the payment result of the car purchase order; the information of the car purchase order is sent to a financial system, and the information of the car purchase order comprises the state of the car purchase order. The method can improve the overall efficiency of the vehicle selling process.

Description

Technical Field

[0001] The embodiments of this specification relate to the field of computer technology, and in particular to a method for managing vehicle sales information; they also relate to a vehicle sales information management device, a vehicle sales information management system, a computing device, a computer-readable storage medium, and a computer program product. Background Art

[0002] With the development of computer technology, the requirements for task execution efficiency are getting higher and higher.

[0003] In the process of selling cars, car companies usually sell cars in bulk to dealers, who pay the money to the car company's account through offline payment. After the car company receives the payment from the dealer, the financial staff will record and check it. The task execution efficiency of each link in the whole car selling process is low, resulting in low overall efficiency of the car selling process. Summary of the invention

[0004] The embodiments of this specification provide a method for managing vehicle sales information, which can improve the overall efficiency of the vehicle sales process. One or more embodiments of this specification also relate to a vehicle sales information management device, a vehicle sales information management system, a computing device, a computer-readable storage medium, and a computer program product.

[0005] According to one aspect of an embodiment of this specification, a method for managing vehicle sales information is provided, including:

[0006] In response to the vehicle sales system creating an operation on the vehicle purchase order, calling a resource system corresponding to the target payment channel to pay for the vehicle purchase order;

[0007] Based on the payment result of the car purchase order, setting the status of the car purchase order;

[0008] The information of the car purchase order is sent to a financial system, wherein the information of the car purchase order includes a status of the car purchase order.

[0009] According to another aspect of the embodiment of this specification, a vehicle sales information management device is provided, including:

[0010] A calling module, for responding to the vehicle selling system's creation operation of the vehicle purchase order, calling the resource system corresponding to the target payment channel to pay for the vehicle purchase order;

[0011] A setting module, used for setting the status of the car purchase order based on the payment result of the car purchase order;

[0012] The sending module is used to send the information of the car purchase order to the financial system, wherein the information of the car purchase order includes the status of the car purchase order.

[0013] According to another aspect of the embodiments of this specification, there is provided a vehicle sales information management system, including a payment system, a vehicle sales system, a resource system and a financial system;

[0014] The vehicle selling system is used to send creation operation information for a vehicle purchase order to the vehicle selling information management system;

[0015] The payment system is used to execute the above-mentioned car sales information management method, call the resource system to pay for the car purchase order, and send the information of the car purchase order to the financial system.

[0016] According to another aspect of the embodiments of this specification, there is provided a computing device, including: a memory and a processor;

[0017] The memory is used to store computer programs / instructions, and the processor is used to execute the computer programs / instructions. When the programs / instructions are executed by the processor, the steps of the above method are implemented.

[0018] According to another aspect of the embodiments of this specification, a computer-readable storage medium is provided, which stores a computer program / instruction, and the steps of the above method are implemented when the computer program / instruction is executed by a processor.

[0019] According to another aspect of the embodiments of this specification, a computer program product is provided, including a computer program / instruction, and when the computer program / instruction in the computer program product is executed by a processor, the steps of the above method are implemented.

[0020] In one embodiment of the present specification, in response to the vehicle sales system creating a vehicle purchase order, the resource system corresponding to the target payment channel can be called to pay for the vehicle purchase order, and then the state of the vehicle purchase order is set, and the information of the vehicle purchase order is sent to the financial system. In this way, the vehicle sales system, the payment system and the financial system can be linked to quickly and efficiently transmit vehicle sales information, improve the task processing efficiency in the vehicle sales process, and improve the overall vehicle sales efficiency. BRIEF DESCRIPTION OF THE DRAWINGS

[0021] Figure 1 It is a structural diagram of a car sales information management system provided in an embodiment of this specification;

[0022] Figure 2 is a flow chart of a method for managing vehicle sales information provided in an embodiment of this specification;

[0023] Figure 3 It is a schematic diagram of a payment page provided in an embodiment of this specification;

[0024] Figure 4 It is a schematic diagram of a car sales information display page in the order details dimension provided in an embodiment of this specification;

[0025] Figure 5 It is a schematic diagram of a car sales information display page in the dimension of full payment status provided in an embodiment of this specification;

[0026] Figure 6 It is a schematic diagram of a car sales information display page in the refund status dimension provided in an embodiment of this specification;

[0027] Figure 7 It is a schematic diagram of a car sales information display page in the dimension of price reduction status provided by an embodiment of this specification;

[0028] Figure 8 It is a schematic diagram of a car sales information display page in a resource system dimension provided in an embodiment of this specification;

[0029] Fig. 9 It is a schematic diagram of a car sales information display page in a car model dimension provided in an embodiment of this specification;

[0030] Fig.10 It is a schematic diagram of a car sales information display page in the merchant dimension provided in an embodiment of this specification;

[0031] Fig.11 It is a schematic diagram of a car sales information display page provided in an embodiment of this specification;

[0032] Fig.12 It is a schematic diagram of a display page of a summary report provided in an embodiment of this specification;

[0033] Fig.13 This is a microservice architecture diagram of a car sales information management device provided in an embodiment of this specification;

[0034] Fig.14 It is a structural diagram of a vehicle sales information management device provided in an embodiment of this specification;

[0035] Fig.15 It is a structural block diagram of a computing device provided in an embodiment of this specification. DETAILED DESCRIPTION

[0036] Many specific details are described in the following description to facilitate a full understanding of this specification. However, this specification can be implemented in many other ways than those described herein, and those skilled in the art can make similar generalizations without violating the connotation of this specification, so this specification is not limited to the specific implementation disclosed below.

[0037] The terms used in one or more embodiments of this specification are for the purpose of describing specific embodiments only and are not intended to limit one or more embodiments of this specification. The singular forms of "one", "said" and "the" used in one or more embodiments of this specification and the appended claims are also intended to include plural forms, unless the context clearly indicates other meanings. It should also be understood that the term "and / or" used in one or more embodiments of this specification refers to and includes any or all possible combinations of one or more associated listed items. The term "at least one" in one or more embodiments of this specification refers to "one or more", and "multiple" refers to "two or more". The term "including" is an open description and should be understood as "including but not limited to", and may include other content on the basis of the content already described.

[0038] It should be understood that although the terms "first", "second", etc. may be used to describe various information in one or more embodiments of this specification, this information should not be limited to these terms. These terms are only used to distinguish the same type of information from each other. For example, without departing from the scope of one or more embodiments of this specification, "first" may also be referred to as "second", and similarly, "second" may also be referred to as "first". Depending on the context, the word "if" as used herein may be interpreted as "at the time of" or "when" or "in response to determining".

[0039] At present, car companies sell cars by selling them in bulk to dealers, who then sell them offline. Buyers learn about the cars on sale at dealers and pay them. Dealers pay the company's public account offline, with payment methods such as cash, acceptance bills, or financial loans. After the car company's finance department receives funds from dealers offline, it manually records and generates accounting vouchers. There is no linkage between vehicle sales, payment, and accounting, and all are done offline. The vehicle sales process is not smooth, resulting in low overall efficiency in the vehicle sales process.

[0040] The embodiments of this specification provide a method for managing vehicle sales information, which can improve the smoothness of the vehicle sales process and improve the overall efficiency of the vehicle sales process. The embodiments of this specification also relate to a vehicle sales information management device, a vehicle sales information management system, a computing device, a computer-readable storage medium, and a computer program product, which will be introduced one by one in the following embodiments.

[0041] Figure 1 This is a schematic diagram of the structure of a car sales information management system provided in an embodiment of this specification. Figure 1As shown, the vehicle sales information management system 10 may include a payment system 101, a vehicle sales system 102, a resource system 103 corresponding to the payment channel, and a financial system 104. In some embodiments, the vehicle sales information management system 10 may also include an after-sales system 105. The vehicle sales system 102, the resource system 103 corresponding to the payment channel, the financial system 104, and the after-sales system 105 may all be connected to the payment system 101. In some of the following contents, the financial system is represented by WIT and the after-sales system is represented by CCO.

[0042] The car sales information management method provided in the embodiment of this specification can be applied to the car sales information management system 10, such as specifically to the payment system 101. The payment system 101 can perform corresponding operations based on a payment application. Based on the car sales information it manages, the payment system 101 can link the various connected systems and quickly send corresponding information or instructions to the system that needs to perform tasks in the car sales process to improve the overall efficiency of the car sales process. The payment system 101 can correspond to a background device within the car company, and the background device can be a terminal or a server. The background device is used to support the operation of the payment application. The background device can display the car sales information managed by the payment system 101 for information management personnel to view, and perform corresponding operations on the car sales information. Optionally, the information management personnel may include financial personnel. The background device is referred to as a car sales information management device below.

[0043] In the embodiment of this specification, the car company can use the vehicle sales system 102 to realize online direct sales and retail of vehicles. The vehicle sales system 102 can correspond to a vehicle sales platform, such as a vehicle sales application, and the vehicle sales application can be installed on the user terminal. The terminal in the embodiment of this specification can be a smart phone, a computer, a smart wearable device and other devices, and the terminal needs to have communication function and display function. The payment application corresponding to the payment system 101 can be installed together with the vehicle sales application. In the process of installing the vehicle sales application on the terminal, the payment application corresponding to the payment system 101 can be installed simultaneously. Buyers can view the vehicles on sale online through the vehicle sales system 102, obtain vehicle information, and make reservations, pay deposits, and pay the balance, etc., to purchase vehicles. When buyers use the vehicle sales system 102 to purchase a vehicle, they can use the payment application to pay.

[0044] The resource system 103 corresponding to the payment channel can be a payment institution, such as a bank, UnionPay or a non-bank payment institution that can make online payments. The resources described in the embodiments of this specification may include funds, and in some ways may also include other resources that can replace funds. Different payment institutions may correspond to different payment channels, such as different non-bank payment institutions corresponding to different payment channels. Alternatively, multiple payment institutions may also correspond to the same payment channel, such as different banks may all correspond to bank transfer payment channels, or to payment channels that use POS machines for payment. POS (Point of sales) refers to a point of sale information management system, which is a terminal reader equipped with barcode or OCR code technology, with cash or barter quota cashier function, and can realize automatic electronic fund transfer. The payment system 101 can be connected to the resource system 103 corresponding to multiple payment channels. When using the payment application corresponding to the payment system 101 to pay, the user can select the payment channel, and the payment system 101 can call the resource system 103 corresponding to the payment channel selected by the user to transfer resources, so as to realize the payment of the vehicle required by the user.

[0045] The financial system 104 may be a system used by the financial personnel of the automobile enterprise, who use the financial system to check accounts and make payments. For example, the financial system 104 also corresponds to an application, and the financial personnel use the various functions of the financial system 104 through the application. The payment system 101 can send relevant account information to the financial system 104 based on the managed car sales information, and can also perform some financial work (such as account settlement, fee calculation, and reconciliation) on behalf of the financial personnel to improve the work efficiency of the financial personnel.

[0046] After-sales system 105 can be used to provide buyers with refunds and some other after-sales services. After-sales system 105 can be used by after-sales staff, and buyers can also exchange information with after-sales system 105 through vehicle sales system 102.

[0047] Figure 2 This is a flow chart of a method for managing vehicle sales information provided in an embodiment of this specification. The method can be applied to Figure 1 The payment system 101 in the car sales information management system 10 shown in the figure can be specifically applied to the backend device corresponding to the payment system 101, that is, the car sales information management device. Figure 2 As shown, the method may include the following steps:

[0048] Step 202: In response to the vehicle sales system creating an operation for a vehicle purchase order, calling a resource system corresponding to a target payment channel to pay for the vehicle purchase order.

[0049] Buyers can use the vehicle sales system to view the vehicles on sale and purchase them. If they decide to purchase a vehicle, they can place an order on the vehicle purchase page, and the vehicle sales system can create a purchase order for the vehicle. The purchase order can include vehicle information (such as model, configuration, and color), buyer identity information, and order time.

[0050] The vehicle sales information management device can use the payment system to monitor the vehicle sales system's operations on the vehicle purchase order, such as creation operations, information change operations, order cancellation operations, etc. The vehicle sales information management device can perform different subsequent operations for different operations. When the vehicle sales information management device detects the vehicle sales system's creation operation on the vehicle purchase order, it can confirm that the buyer needs to pay for the vehicle purchase order. The payment for the vehicle purchase order can be the full payment for the vehicle, or only the vehicle deposit (or down payment). The specific fees to be paid can be determined based on the buyer's choice. The vehicle sales information management device can call the resource system specified by the buyer to pay for the vehicle purchase order.

[0051] When the vehicle sales information management device detects the creation operation of the vehicle purchase order by the vehicle sales system, it can trigger the buyer's terminal to display a payment page. The payment page may include the amount to be paid and multiple payment channel options. The payment channel displayed on the payment page can be determined based on the payment channels supported by the buyer's terminal. The buyer can select the payment channel he wants to use from the multiple payment channels, and then the vehicle sales information management device can call the resource system corresponding to the payment channel to pay for the vehicle purchase order based on the user's operation on the payment page.

[0052] Figure 3 is a schematic diagram of a payment page provided in an embodiment of this specification. Figure 3 As shown, the terminal can support payment channels of multiple non-bank payment institutions, and can also support payment channels of bank transfers and payment channels of POS payment. Buyers can choose any payment channel to pay. For example, the buyer chooses a payment channel of a non-bank payment institution, and then the terminal can display the password input interface corresponding to the non-bank payment institution. The user can enter the corresponding password, and then the non-bank payment structure can transfer the corresponding amount of funds in the buyer's account to the car company's account. For another example, the buyer chooses the payment channel of bank transfer, and then the terminal can display the bank card number input box and the password input box. The buyer can enter his bank card number and payment password, and then the bank to which the bank card belongs can transfer the corresponding amount of funds in the bank card to the car company's account. In the case where the buyer chooses to pay by POS, the terminal can display the delivery location, and then instruct the buyer to go to the delivery location to pay by POS.

[0053] Step 204: Based on the payment result of the car purchase order, set the status of the car purchase order.

[0054] After the vehicle sales system creates a vehicle purchase order, if no payment is made for the vehicle purchase order within the set time, the vehicle sales system can cancel the vehicle purchase order. After the buyer pays for the vehicle purchase order, the vehicle sales information management device can record the vehicle purchase order and send a prompt message of successful payment to the buyer's terminal. The vehicle sales information management device can also set a corresponding status for the vehicle purchase order based on the payment result. The vehicle sales information management device can set different statuses for the vehicle purchase order according to the different payments made by the buyer for the vehicle purchase order. The status of the vehicle purchase order can determine the time when the buyer receives the vehicle. For example, the status of the vehicle purchase order can include: deposit payment status (deposit), down payment status (down), full payment status (full), full payment confirmation status (confirm) and vehicle delivery status (settle).

[0055] In some embodiments, the order status can be set for the car purchase order by using the capital position design. The car sales information management device can set a corresponding capital account for the car purchase order based on the payment result of the car purchase order. The car sales information management device can set a corresponding capital account for the car purchase order when the payment for the car purchase order is successful, and then record all the funds paid for the car purchase order under the capital account. The capital account can be a virtual account, and the funds corresponding to the capital account can be used in the processing related to the car purchase order. The car sales information management device can determine the position of the capital account based on the paid resources of the car purchase order, such as based on the paid amount. Based on the position, the reference state corresponding to the position can be set as the state of the car purchase order in multiple reference states, and the multiple reference states respectively correspond to different positions of the capital account.

[0056] For example, each car purchase order may correspond to a total amount, and the total amount of funds may be the total sales price of the vehicle. The car sales information management device may determine the current position of the capital account corresponding to the car purchase order based on the ratio of the paid amount of the car purchase order to the total amount. The multiple reference states may include the aforementioned multiple states of the car purchase order, namely, deposit, down, full, confirm, and settle. Optionally, the positions corresponding to the multiple states may increase in sequence. The car sales information management device may compare the current position of the capital account with the positions corresponding to each reference state, and determine the reference position that matches the current position as the state of the capital account. In the event that the paid funds under the capital account change or the total amount corresponding to the capital account changes, the state of the capital account may be adjusted accordingly.

[0057] In the embodiment of this specification, the car sales information management device can also record the payment information of the car purchase order. For example, the payment information may include the amount paid for the car purchase order, the payment time, the payment channel used, the buyer's payment account and the receiving account, etc.

[0058] Step 206: Send the car purchase order information to the financial system, wherein the car purchase order information includes the status of the car purchase order.

[0059] When recording a new car purchase order or updating the status of an existing car purchase order, the car sales information management device can send the car purchase order information to the finance department for the finance system to check and count the accounts, and trigger the vehicle delivery process for the car purchase orders that meet the conditions. For example, the car sales information management device can send the car purchase order information to the finance system regularly, such as sending the car purchase order information updated on the same day to the finance system at a set time every day, or sending the car purchase order information to the finance system every time there is a car purchase order information update.

[0060] In summary, in the vehicle sales information management method provided in the embodiments of this specification, the vehicle sales information management device, in response to the vehicle sales system creating a vehicle purchase order, can call the resource system corresponding to the target payment channel to pay for the vehicle purchase order, and then set the state of the vehicle purchase order, and send the information of the vehicle purchase order to the financial system. In this way, the vehicle sales system, payment system and financial system can be linked to quickly and efficiently realize the transmission of vehicle sales information, improve the task processing efficiency in the vehicle sales process, and improve the overall vehicle sales efficiency.

[0061] In some implementations, after sending the information of the car purchase order to the financial system in step 206, the car sales information management method provided in the embodiments of this specification may further include the following steps:

[0062] When a refund request is received from the target system for a vehicle purchase order, based on the payment method of the vehicle purchase order, the resource system corresponding to the target payment resource channel is called to refund the vehicle purchase order, or the financial system is requested to refund the vehicle purchase order; wherein the target system is a vehicle sales system or an after-sales system.

[0063] After paying for a vehicle purchase order, the buyer may also use the vehicle sales system to initiate a refund request for the vehicle purchase order. For example, after the buyer pays a deposit for a vehicle purchase order, a refund control may be displayed on the buyer's terminal for the vehicle purchase order, and the buyer may trigger a refund request through the refund control. The vehicle sales system may send the refund request to the vehicle sales information management device, so that the refund request is processed by the vehicle sales information management device and the buyer is refunded. In another implementation mode, if the vehicle corresponding to the vehicle purchase order for which funds have been paid is reduced in price, the after-sales system may proactively refund the buyer, and accordingly the after-sales system may send a refund request to the vehicle sales information management device for the vehicle purchase order.

[0064] The car sales information management device can return the refundable funds to the account used to pay for the car purchase order based on the specific payment information of the car purchase order recorded. For example, if the car purchase order is paid by calling the resource system corresponding to the target payment resource channel, the car sales information management device can then call the resource system corresponding to the target payment resource channel to refund the car purchase order and return the funds in the original way.

[0065] For car purchase orders paid by different payment methods, there may be some differences in the refund method; the refund time is different, and the corresponding refund method may also be different. In some cases, the refund request for the car purchase order needs to be reviewed by the financial system, and the financial system will release the money to realize the refund of the car purchase order. For example, if the funds are transferred to the car company's account through bank transfer for the car purchase order, and the finance has registered the payment for the car purchase order, then when the car purchase order is refunded, the car sales information management device can request the financial system to refund the car purchase order. In some cases, when a refund request is initiated within a set time after the deposit payment time of the car purchase order, the resource system corresponding to the target payment resource channel used during payment can be directly called for refund; when a refund request is initiated after the set time, it is necessary to request the financial system to refund the car purchase order.

[0066] In some implementations, the vehicle sales information management method provided in the embodiments of this specification may also include the following steps:

[0067] The information of each car purchase order is counted from multiple dimensions, wherein the multiple dimensions include multiple dimensions of order details dimension, full payment status dimension, refund status dimension, and price reduction status dimension;

[0068] In response to an order information viewing instruction for any dimension among multiple dimensions, information of each car purchase order under any dimension is displayed.

[0069] The car sales information management device records information for each car purchase order it processes, and the information of the car purchase order may include payment information and status, etc. The car sales information management device can also separately count the information of each recorded car purchase order according to the required viewing dimension, and generate order information summarized under each dimension. The car sales information management device can display a car sales information display page, which may include selection controls corresponding to each dimension. The user can click on the selection control corresponding to any dimension to trigger the order information viewing instruction of that dimension, so that the car sales information management device displays the information of the car purchase order of that dimension, so that the information management personnel can easily view the order information under each dimension. The embodiment of this specification takes the required viewing dimensions including the order details dimension, the full payment status dimension, the refund status dimension, and the price reduction status dimension as an example. The full payment status is also the aforementioned full payment status.

[0070] Figure 4 is a schematic diagram of a car sales information display page in the order details dimension provided in an embodiment of this specification, Figure 5 is a schematic diagram of a car sales information display page in the dimension of full payment status provided in an embodiment of this specification, Figure 6 is a schematic diagram of a car sales information display page in the refund status dimension provided in an embodiment of this specification. Figure 7 Schematic diagram of a car sales information display page in the dimension of price reduction status provided by an embodiment of this specification. Figures 4 to 7 As shown, the text "New Car Order Management" on the left side of the car sales information display page is a selection control corresponding to the order details dimension, the text "Full Payment Confirmation" is a selection control corresponding to the full payment status dimension, the text "Refund Application Report" is a selection control corresponding to the refund status dimension, and the text "Order Price Reduction Record Report" is a selection control corresponding to the price reduction status dimension. The information of the car purchase order in these multiple dimensions can be collectively included in the information under the "Retail Business Management" dimension. The car sales information display page can also query the corresponding order through different aspects of information.

[0071] like Figure 4 As shown, in the order details dimension, for each car purchase order, information such as order number, payment method, deposit payable, total order amount, paid amount, amount to be paid, currency, fund status, fund account number, payer list, frozen status, and closed status can be displayed. The paid amount can correspond to the paid resources of the aforementioned car purchase order, the total order amount is the total amount corresponding to the aforementioned car purchase order, the fund status corresponds to the status of the aforementioned car purchase order, the fund account number is the identifier of the fund account set for the car purchase order, the frozen status refers to whether the fund account is frozen, and the closed status refers to whether the car purchase order is closed. In the order details dimension, users can view car purchase orders and payment information.

[0072] like Figure 5 As shown, in the full payment status dimension, for each car purchase order, the order number, fund account number, total order amount, paid amount, overpaid amount, full payment arrival status, and full payment confirmation time can be displayed. For each car purchase order, a "Confirm Full Payment" control can also be displayed, and the information manager can confirm that the car purchase order has been paid in full by clicking the control. In the full payment status dimension, users can check whether the vehicle has been paid in full, trigger the full payment confirmation action, and send the car purchase order information to the financial system.

[0073] like Figure 6 As shown in the figure, in the refund status dimension, the information of the car purchase order for which a refund application has been made can be displayed. For example, the refund application number, refund sequence number, order number, refund source, refund type, refund channel, original transaction serial number, withdrawal transaction serial number, original return mark, and total refund amount of the customer can be displayed.

[0074] like Figure 7 As shown, in the price reduction status dimension, information about car purchase orders with price reductions can be displayed, such as order number, sequence code, original account status, original order price, new order price, refund processed mark, refund application number, car model, creator, and creation time.

[0075] In some implementations, the vehicle sales information management method provided in the embodiments of this specification may also include the following steps:

[0076] Record the handling fee information paid for each car purchase order;

[0077] The handling fee information of each vehicle purchase order is respectively counted from multiple dimensions, wherein the multiple dimensions include multiple dimensions of an order dimension, a resource system dimension, a vehicle model dimension, and a merchant dimension of the vehicle;

[0078] In response to an instruction to view handling fee information for any dimension among the multiple dimensions, handling fee information for any dimension is displayed.

[0079] In the process of using the resource system to pay for each car purchase order, a certain handling fee needs to be paid to the resource system, and the handling fee can be paid by the car company. The car sales information management device can record the handling fee information paid for each car purchase order, and then count the handling fee information of each car purchase order from multiple required dimensions, so that the user can view the handling fee information from the required dimensions.

[0080] Figure 8 This is a schematic diagram of a car sales information display page in a resource system dimension provided in an embodiment of this specification. Regarding the resource system dimension, the following only takes the UnionPay dimension as an example. Figure 8 As shown in the figure, the text "Order Price Reduction Record Report" is the selection control corresponding to the UnionPay dimension. The car sales information display page can display information such as model number, merchant number, settlement date, transaction date, transaction amount, transaction type, UnionPay handling fee, total handling fee, comparison mark, and search number.

[0081] Fig. 9 Schematic diagram of a car sales information display page in the dimension of a car model provided in an embodiment of this specification. Fig. 9 As shown in the figure, the text "Model Fee Report" is the selection control corresponding to the vehicle model dimension. For the vehicle model dimension, the fee can be counted on a monthly basis. For example, the current fee statistical period (year / month), vehicle model number, UnionPay fee, total fee, year (i.e. total year), voucher number, creation time, release time, completion time, and status can be displayed.

[0082] Fig.10 1 is a schematic diagram of a car sales information display page in the merchant dimension provided in an embodiment of this specification. The merchants selling cars may correspond to different branches of the car company, or may also correspond to the dealers of the car company. Fig.10 As shown in the figure, the place where the text "Service Fee Summary Report" is located is the selection control corresponding to the merchant dimension. You can select according to the statistical period of the service fee, merchant number, merchant name, statement type, UnionPay service fee, total service fee, and creation time.

[0083] In some embodiments, each merchant that sells vehicles may have an auxiliary payment system. The auxiliary payment system may be connected to the vehicle sales information management device, such as being integrated with the payment system corresponding to the vehicle sales information management device, or being differentiated from the payment system corresponding to the vehicle sales information management device. The auxiliary payment system may be substantially the same as the payment system corresponding to the vehicle sales information management device, such as being able to achieve the same functions, and no additional details are given here. The auxiliary payment system may record the information of the vehicle purchase order placed from its corresponding merchant, and may also send the information of the vehicle purchase order to the vehicle sales information management device. Accordingly, the vehicle sales information management device receives the information of the vehicle purchase order sent by the connected auxiliary payment system, wherein each auxiliary payment system corresponds to a merchant that sells vehicles. The vehicle sales information management device may, based on the information of the vehicle purchase order recorded by it, combine the information of the vehicle purchase order received from the auxiliary payment system, and count the information related to the merchant dimension.

[0084] In some embodiments, the car sales information management device can obtain the handling fee information from the resource system, such as UnionPay periodically sending the handling fee information in the previous period to the car company, so that the car company can pay the handling fee based on the handling fee information. In the embodiment of this specification, the car sales information management device counts the handling fee information of the resource system dimension by itself, and then can compare the handling fee information obtained from the resource system with the handling fee information of the resource system dimension that is counted. After completing the comparison and confirming that the comparison is consistent, the handling fee information of the resource system dimension can be sent to the financial system based on the comparison result, so that the financial system pays the handling fee to the resource system. If the comparison result indicates that the handling fee information obtained from the resource system is inconsistent with the handling fee information of the resource system dimension that is counted, it can be analyzed whether there is a problem with the handling fee sent by the resource system or the handling fee counted by the car sales information management device, and then the problem can be repaired by itself or a warning can be issued to the staff so that the staff can repair the problem.

[0085] In some embodiments, the car sales information management device periodically obtains the reconciliation statement sent by the resource system, such as UnionPay periodically sending the reconciliation statement within the previous cycle period to the car company. For example, the reconciliation statement may include the fund details received by the resource system. The car sales information management device can automatically reconcile based on the received reconciliation statement, such as comparing the reconciliation statement with the target payment information of each car purchase order within the cycle period to obtain the reconciliation result. When the reconciliation result indicates that the reconciliation statement matches the target payment information, a reconciliation voucher is generated and sent to the financial system. Optionally, after obtaining the reconciliation statement, the car sales information management device can first parse the reconciliation statement to obtain specific fund details, and then reconcile based on the parsed data. This method is equivalent to the car sales information management device replacing the financial personnel to perform automatic reconciliation, which can reduce the burden of financial personnel, improve the work efficiency of financial personnel, and improve the efficiency and accuracy of reconciliation.

[0086] In the case where the reconciliation result indicates that the reconciliation statement does not match the target payment information, the car sales information management device can analyze the reconciliation statement and the target payment information separately. In the case where the target payment information is analyzed to have data errors, the car sales information management device automatically corrects the target payment information, such as using intelligent error processing technology to correct the target payment information. In the case where the reconciliation statement is analyzed to have data errors, the car sales information management device sends an alarm message and the reconciliation result to the financial system, so that the financial personnel can communicate with the staff of the resource system based on the alarm message and the reconciliation result to correct the problem.

[0087] Optionally, the resource system sends the statement to the financial system of the car company, and the staff manually uploads the statement to the car sales information management device, so that the car sales information management device can automatically reconcile based on the uploaded statement. The car sales information management device can set different upload interfaces to upload statements from different resource systems respectively, such as uploading UnionPay statements and bank statements through different pages.

[0088] In the embodiments of this specification, for the payment of the car purchase order by bank transfer, the bank can send the relevant information of each transfer to the car sales information management device after receiving it. The car sales information management device can verify the bank transfer information based on the received information, and perform a confirmation registration operation after the verification passes, thereby confirming that a fund has been successfully received. If the verification fails, the registration fails, and a refund operation needs to be performed on the transfer.

[0089] In some embodiments, the car sales information management device can settle and manage transaction information by time period. The car sales information management device can periodically update the transaction time period. After the transaction time period is updated, the payment information of each car purchase order in the previous transaction time period is settled, and the settlement information corresponding to the previous transaction time period is generated. For example, the car sales information management device can settle once a day, which can be called daily settlement, and switching the transaction time period every day can be called daily switching. The staff can set the switching time of the transaction time period, and the car sales information management device can switch the recorded transaction day when the transaction time is reached every day, and then settle the payment information in the previous transaction day. For example, calculate the total new car purchase order data, the total income, the total refunded funds, the number of refund orders incurred, and other information on the previous day. Optionally, the staff can also manually switch the transaction day.

[0090] Fig.11 Schematic diagram of a car sales information display page provided in an embodiment of this specification. Fig.11 As shown, the car sales information management device can perform reconciliation, upload bank statements and UnionPay statements, bank transfer registration and refund, daily cut management and daily settlement management under the settlement management dimension. Fig.11 Only the page views corresponding to bank transfer registration and refund are illustrated. For example, for bank transfer registration and refund, information such as statement source, bank transaction serial number, report number, report generation time, transaction date, transaction time, transaction amount, debit / credit indicator, transaction currency, and virtual account number can be displayed.

[0091] In some embodiments, the vehicle sales information management device can generate a summary report of multiple dimensions based on the payment information of each vehicle purchase order, wherein the multiple dimensions include multiple dimensions of order dimension, payment channel dimension, refund dimension, abnormal transaction dimension, and reconciliation dimension. Afterwards, in response to a report viewing instruction for any dimension of the multiple dimensions, a summary report under any dimension can be displayed. The summary reports of multiple dimensions can be triggered by different controls under the same management dimension. For example, they can belong to multiple display sub-dimensions under the report management dimension.

[0092] Fig.12 Schematic diagram of a display page of a summary report provided in an embodiment of this specification. Fig.12 The "Order Report" in corresponds to the order dimension and is used to manage order payment information reports. The "Transaction Record Report" corresponds to the payment channel dimension and is used to manage payment records of all payment channels. The "Abnormal Transaction Report" corresponds to the abnormal transaction dimension and is used to manage payment records with abnormalities. The "UnionPay Statement Report" and "Bank Statement Report" correspond to the reconciliation dimension and are used to manage automatic reconciliation results. The "Refund Panel Report" corresponds to the refund dimension and is used to view the statistical information of various dimensions related to refunds in real time. The "Payment Panel Report" can comprehensively display payment information of multiple dimensions and is used to view the statistical information of various dimensions related to payment in real time, such as the number of transactions and transaction amounts of each payment channel. Under the "Refund Panel Report" and "Payment Panel Report", information can be displayed in the form of charts (such as pie charts, bar charts, and tables).

[0093] Fig.12 Take the display page after selecting "Bank Statement Report" as an example. For example, the display page can display information such as the statement source, bank transaction serial number, report number, report generation time, transaction date, transaction time, transaction amount, debit / credit mark, transaction currency, and virtual account number.

[0094] In the embodiments of this specification, the car sales information management device can also provide a system management interface for staff to perform certain user management, role management and authority management. For example, different information access rights are set for different users, so that they can only access the car sales information within their own authority. The car sales information management device can also set the bank ratio of the virtual account. The capital account allocated by the car sales information management device for each car purchase order can belong to certain actual banks, and the staff can set the proportion of the capital account allocated under different banks.

[0095] In some embodiments, the payment system corresponding to the car sales information management device can be a system with a microservice architecture. The car sales information management device can perform corresponding functions through multiple microservices, and different microservices can be used to perform different tasks. For example, the multiple microservices may include an information receiving microservice for receiving information sent by other systems connected to the payment system. The multiple microservices may also include a display microservice for controlling the buyer's terminal to display a payment page. The multiple microservices may also include a payment microservice and microservices corresponding to the resource systems of each payment channel. The payment microservice is used to perform the main functions of the car sales information management device, such as information recording, information statistics of different dimensions, reconciliation, and status setting.

[0096] Under this microservice architecture, in step 202, in response to the vehicle sales system creating the vehicle purchase order, calling the resource system corresponding to the target payment channel to pay for the vehicle purchase order may include:

[0097] Use the information receiving microservice to receive the creation operation information for the vehicle purchase order from the vehicle sales system;

[0098] In response to the payment operation in the payment page, the payment microservice calls the microservice corresponding to the target payment channel, triggering the resource system corresponding to the target payment channel to pay for the car purchase order.

[0099] Optionally, the aforementioned periodically obtaining the statement of account sent by the resource system may include: periodically obtaining the statement of account sent by the resource system through a microservice corresponding to the resource system.

[0100] Fig.13 This is a microservice architecture diagram of a car sales information management device provided in an embodiment of this specification. Fig.13 Each dotted box in the figure represents a microservice, and boxes enclosed by different dotted lines represent microservices that are connected to the public network or to the intranet. Fig.13 As shown, the car sales information management device may include multiple information receiving microservices, such as Fig.13 The first information receiving microservice, the second information receiving microservice and the third information receiving microservice in the system. The first information receiving microservice can be used to receive information related to other orders other than vehicle sales, such as order information of charging piles. The second information receiving microservice and the third information receiving microservice can be used to receive information in different ways, such as the second information receiving microservice is used to receive information sent via HTTP, and the third information receiving microservice is used to receive information sent via broadcast (MQ). Both the second information receiving microservice and the third information receiving microservice can receive information from the vehicle sales system and the after-sales system.

[0101] The information receiving microservice can transmit the received information to the front-end display microservice to trigger the terminal to display the corresponding page. Based on the operation in the page, the payment microservice can be triggered to work, such as recording information, calling other microservices, etc. Fig.13 The figure shows the microservices corresponding to three payment channels, namely, UnionPay microservice, microservice corresponding to POS payment (POS microservice in the figure), and microservice corresponding to non-bank payment (SF microservice in the figure). When the buyer chooses any payment channel to pay for the car purchase order, the corresponding microservice can be called to make the payment.

[0102] For different types of orders, different microservices can be generated based on a unified code package (jar package). For example, for car purchase orders and other orders, different fund account management microservices can be generated based on related code packages (such as the standard fund account management model in the figure), such as Fig.13 The car sales fund account management microservice and the non-car sales fund account management microservice are both extended based on the standard fund account management model. When the payment microservice needs to perform a refund operation for an order, different fund account management microservices can be called to perform specific operations.

[0103] For different functions, the payment microservice can call different functional microservices to implement the corresponding functions. Fig.13 As shown, it can also include reconciliation microservice, settlement microservice and accounting microservice, so as to perform reconciliation, daily settlement and accounting respectively through these different microservices. These microservices can be connected with the resource system (bank or UnionPay) to receive the statement or other payment information sent by the resource system.

[0104] In the embodiments of this specification, the payment system corresponding to the car sales information management device can be developed using the SpringBoot framework to quickly build independent, production-level applications using the framework to ensure the rapid construction of the payment system. The payment system can use Istio as a service mesh platform to manage traffic and telemetry data between services, and provide seamless connections between microservices, and methods for managing and protecting different microservice networks. The payment system can also be combined with the Enabling Service Platform to achieve continuous integration, continuous delivery, and testing to ensure the quality and stability of the application.

[0105] In the embodiments of this specification, the payment system can be deployed on a cloud platform, such as Azure Kubernetes Service (AKS), and the high availability, scalability and automation characteristics of the cloud platform can be used to manage and expand applications, such as the aforementioned auxiliary payment system. The payment system can also use the services of the cloud platform to implement some additional functions and improve the performance of the application. For example, services such as Azure Key Vault of the cloud platform can be used to perform identity authentication and authorization management to ensure the security of the application. Monitoring tools such as Azure Monitor can be used to monitor and alarm the application in real time, so as to promptly discover and solve program operation problems and business data problems, and improve the reliability and stability of the system.

[0106] In the embodiments of this specification, the payment system uses a capital account position design to characterize the status of the car purchase order, which can support a flexible and dynamic payment model. The payment system provides multiple payment channels online (non-bank payment institution payment) and offline (such as POS machines, bank account transfers), providing users with efficient, convenient and secure payment and refund services. The payment system is also deeply integrated with UnionPay and multiple banks, providing automated reconciliation and settlement services with banks and UnionPay, and automated calculation and comparison services for handling fees. The payment system is also deeply integrated with the financial system, providing automated accounting service support for payment refund records to ensure efficient financial work. The payment system can also provide support for the payment systems of multiple entities of various branches of automobile companies to ensure rapid acquisition and integrated management of information. The payment system also provides a user-oriented workbench for staff (such as financial staff), which can facilitate staff to query relevant data in real time and facilitate efficient work.

[0107] In the embodiments of this specification, it is possible to provide multi-mode, multi-channel, safe and fast online payment in the sales process, complete the payment actions of each node of the order, and connect the entire sales process in series; it is also possible to realize the split docking of multiple entities, so that each entity business process can run independently, completely and safely, and ensure the flexibility and efficiency of business operation. In addition, it is possible to automatically reconcile transactions with UnionPay and banks to ensure the rigor and correctness of transactions. The car sales information management device can also record transaction information in real time and push the corresponding accounting vouchers to the financial system, automatically calculate the UnionPay transaction fee information, and push it to the financial system according to the accounting voucher requirements, reduce the work pressure of financial personnel, and improve financial work efficiency. The car sales information management method provided in the embodiments of this specification realizes the automated linkage of the overall sales system, payment system, after-sales system, and financial system, which can improve the overall efficiency of car sales.

[0108] In summary, in the vehicle sales information management method provided in the embodiments of this specification, in response to the vehicle sales system creating a vehicle purchase order, the resource system corresponding to the target payment channel can be called to pay for the vehicle purchase order, and then the state of the vehicle purchase order is set, and the information of the vehicle purchase order is sent to the financial system. In this way, the vehicle sales system, the payment system and the financial system can be linked to quickly and efficiently realize the transmission of vehicle sales information, improve the task processing efficiency in the vehicle sales process, and improve the overall vehicle sales efficiency.

[0109] Corresponding to the above method embodiment, this specification also provides a vehicle sales information management device embodiment. Fig.14 This is a schematic diagram of a vehicle sales information management device provided in an embodiment of the present specification. The vehicle sales information management device is applied to Figure 1 Payment systems 101. Fig.14 As shown, the vehicle sales information management device includes:

[0110] The calling module 1402 is used to call the resource system corresponding to the target payment channel to pay for the vehicle purchase order in response to the vehicle sales system creating the vehicle purchase order;

[0111] A setting module 1404, used to set the status of the car purchase order based on the payment result of the car purchase order;

[0112] The sending module 1406 is used to send the information of the car purchase order to the financial system, wherein the information of the car purchase order includes the status of the car purchase order.

[0113] Optionally, the setting module 1404 is used to:

[0114] Based on the payment result of the car purchase order, set up a corresponding fund account for the car purchase order;

[0115] Based on the paid resources of the car purchase order, the position of the capital account is determined, and the reference state corresponding to the position is set as the state of the car purchase order in multiple reference states; wherein the multiple reference states correspond to different positions of the capital account respectively.

[0116] Optionally, the vehicle sales information management device provided in the embodiment of this specification further includes:

[0117] A first statistics module is used to count the information of each car purchase order from multiple dimensions, wherein the multiple dimensions include multiple dimensions of order details dimension, full payment status dimension, refund status dimension and price reduction status dimension;

[0118] The first display module is used to respond to an order information viewing instruction for any dimension of multiple dimensions and display information of each car purchase order under any dimension.

[0119] Optionally, the vehicle sales information management device provided in the embodiment of this specification further includes:

[0120] A recording module is used to record the handling fee information paid for each car purchase order;

[0121] The second statistical module is used to count the handling fee information of each car purchase order from multiple dimensions, wherein the multiple dimensions include multiple dimensions of order dimension, resource system dimension, vehicle model dimension and merchant dimension of selling vehicles;

[0122] The second display module is used to display the handling fee information in any dimension in response to a handling fee information viewing instruction for any dimension of the multiple dimensions.

[0123] Optionally, the vehicle sales information management device provided in the embodiment of this specification further includes:

[0124] A first comparison module is used to compare the handling fee information obtained from the resource system with the handling fee information of the resource system dimension that is statistically analyzed;

[0125] The handling fee information sending module is used to send the handling fee information of the resource system dimension to the financial system based on the comparison result.

[0126] Optionally, the vehicle sales information management device provided in the embodiment of this specification further includes:

[0127] The receiving module is used to receive the information of the car purchase order sent by the connected auxiliary payment system before counting the handling fee information of each car purchase order from multiple dimensions, wherein each auxiliary payment system corresponds to a merchant selling vehicles.

[0128] Optionally, the vehicle sales information management device provided in the embodiment of this specification further includes:

[0129] The acquisition module is used to periodically obtain the statement sent by the resource system;

[0130] The second comparison module is used to compare the target payment information of each car purchase order in the statement and the cycle period to obtain the reconciliation result;

[0131] The voucher generation module is used to generate a reconciliation voucher and send the reconciliation voucher to the financial system when the reconciliation result indicates that the reconciliation statement matches the target payment information.

[0132] Optionally, the vehicle sales information management device provided in the embodiment of this specification further includes:

[0133] An analysis module, for analyzing the reconciliation statement and the target payment information respectively when the reconciliation result indicates that the reconciliation statement and the target payment information do not match;

[0134] A correction module, used to correct the target payment information when the target payment information is analyzed to have data errors;

[0135] The reconciliation result sending module is used to send alarm information and reconciliation results to the financial system when it is analyzed that there are data errors in the reconciliation statement.

[0136] Optionally, the vehicle sales information management device provided in the embodiment of this specification further includes:

[0137] An update module, used to periodically update the trading session;

[0138] The settlement information generation module is used to settle the payment information of each car purchase order in the previous transaction period after the transaction period is updated, and generate the settlement information corresponding to the previous transaction period.

[0139] Optionally, the vehicle sales information management device provided in the embodiment of this specification further includes:

[0140] A report generation module, used to generate summary reports of multiple dimensions based on the payment information of each car purchase order, wherein the multiple dimensions include multiple dimensions of order dimension, payment channel dimension, refund dimension, abnormal transaction dimension and reconciliation dimension;

[0141] The third display module is used to display a summary report under any dimension in response to a report viewing instruction for any dimension of the multiple dimensions.

[0142] Optionally, the vehicle sales information management device provided in the embodiment of this specification further includes:

[0143] The refund module is used to, after sending the information of the car purchase order to the financial system, call the resource system corresponding to the target payment resource channel to refund the car purchase order based on the payment method of the car purchase order when receiving the refund request sent by the target system for the car purchase order, or request the financial system to refund the car purchase order; wherein, the target system is the vehicle sales system or after-sales system.

[0144] Optionally, the calling module 1402 is used to:

[0145] Use the information receiving microservice to receive the creation operation information for the vehicle purchase order from the vehicle sales system;

[0146] In response to the payment operation in the payment page, the payment microservice calls the microservice corresponding to the target payment channel, triggering the resource system corresponding to the target payment channel to pay for the car purchase order.

[0147] In summary, in the embodiments of this specification, the vehicle sales information management device responds to the vehicle sales system's creation operation of the vehicle purchase order, can call the resource system corresponding to the target payment channel to pay for the vehicle purchase order, and then set the state of the vehicle purchase order, and send the information of the vehicle purchase order to the financial system. In this way, the vehicle sales system, payment system and financial system can be linked to quickly and efficiently realize the transmission of vehicle sales information, improve the task processing efficiency in the vehicle sales process, and improve the overall vehicle sales efficiency.

[0148] Each embodiment in this specification is described in a progressive manner, and the same or similar parts between the embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the vehicle sales information management device, since it is basically similar to the vehicle sales information management method embodiment, the description is relatively simple, and the relevant parts can be referred to the partial description of the vehicle sales information management method embodiment.

[0149] Fig.15 7 is a block diagram of a computing device provided in an embodiment of the present specification. The components of the computing device 700 include but are not limited to a memory 710 and a processor 720. The processor 720 is connected to the memory 710 via a bus 730, and the database 750 is used to store data.

[0150] The computing device 700 also includes an access device 740, which enables the computing device 700 to communicate via one or more networks 760. Examples of these networks include a public switched telephone network (PSTN), a local area network (LAN), a wide area network (WAN), a personal area network (PAN), or a combination of communication networks such as the Internet. The access device 740 may include one or more of any type of network interface (e.g., a network interface card (NIC)) of wired or wireless, such as an IEEE 802.11 wireless local area network (WLAN) wireless interface, a world-wide interoperability for microwave access (Wi-MAX) interface, an Ethernet interface, a universal serial bus (USB) interface, a cellular network interface, a Bluetooth interface, and a near field communication (NFC).

[0151] In one embodiment of the present specification, the above components of the computing device 700 and Fig.15 Other components not shown in the figure may also be connected to each other, for example, via a bus. It should be understood that Fig.15 The computing device structure block diagram shown is only for the purpose of illustration, and is not intended to limit the scope of this specification. Those skilled in the art can add or replace other components as needed.

[0152] The computing device 700 may be any type of stationary or mobile computing device, including a mobile computer or mobile computing device (e.g., a tablet computer, a personal digital assistant, a laptop computer, a notebook computer, a netbook, etc.), a mobile phone (e.g., a smart phone), a wearable computing device (e.g., a smart watch, smart glasses, etc.), or other types of mobile devices, or a stationary computing device such as a desktop computer or a personal computer (PC). The computing device 700 may also be a mobile or stationary server.

[0153] The processor 720 is used to execute computer programs / instructions. When the computer programs / instructions are executed by the processor, the steps in the above method are implemented, such as Figure 2 The method shown.

[0154] As for the computing device embodiment, since it is basically similar to the vehicle sales information management method embodiment, the description is relatively simple, and the relevant parts can be referred to the partial description of the vehicle sales information management method embodiment.

[0155] One embodiment of the present specification also provides a computer-readable storage medium, which stores computer instructions, and when the computer instructions are executed by the processor, the steps of the above-mentioned car sales information management method are implemented. The computer instructions include computer program code, and the computer program code can be in source code form, object code form, executable file or some intermediate form, etc. The computer-readable storage medium may include: any entity or device that can carry the computer program code, recording medium, USB flash drive, mobile hard disk, disk, optical disk, computer memory, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), electric carrier signal, telecommunication signal and software distribution medium, etc. It should be noted that the content contained in the computer-readable storage medium can be appropriately increased or decreased according to the requirements of legislation and patent practice in the jurisdiction. For example, in some jurisdictions, according to legislation and patent practice, computer-readable storage media do not include electric carrier signals and telecommunication signals.

[0156] An embodiment of the present specification also provides a computer program product, including a computer program / instruction, which implements the steps of the above-mentioned vehicle sales information management method when the computer program / instruction is executed in a processor.

[0157] As for the computer-readable storage medium embodiment and the computer program product embodiment, since they are basically similar to the vehicle sales information management method embodiment, the description is relatively simple, and the relevant parts can be referred to the partial description of the vehicle sales information management method embodiment.

[0158] The above is a description of a specific embodiment of the specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recorded in the claims can be performed in an order different from that in the embodiments and still achieve the desired results. In addition, the processes depicted in the drawings do not necessarily require the specific order or continuous order shown to achieve the desired results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0159] It should be noted that the above is a description of a specific embodiment of the present specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recorded in the claims can be performed in an order different from that in the embodiments and still achieve the desired results. In addition, the processes depicted in the accompanying drawings do not necessarily require the specific order or continuous order shown to achieve the desired results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous. Secondly, those skilled in the art should also be aware that the embodiments described in the specification are all preferred embodiments, and the actions and modules involved are not necessarily required by the embodiments of the present specification.

[0160] In the above embodiments, the description of each embodiment has its own emphasis. For parts that are not described in detail in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.

[0161] The preferred embodiments of this specification disclosed above are only used to help explain this specification. The optional embodiments do not describe all the details in detail, nor do they limit the invention to the specific implementation methods described. Obviously, many modifications and changes can be made according to the content of the embodiments of this specification. This specification selects and specifically describes these embodiments in order to better explain the principles and practical applications of the embodiments of this specification, so that technicians in the relevant technical field can understand and use this specification well.

Claims

1. A method for managing vehicle sales information, characterized in that: The method comprises: In response to the vehicle sales system creating an operation on the vehicle purchase order, calling a resource system corresponding to the target payment channel to pay for the vehicle purchase order; Based on the payment result of the car purchase order, setting the status of the car purchase order; The information of the car purchase order is sent to a financial system, wherein the information of the car purchase order includes a status of the car purchase order.

2. The method according to claim 1, characterized in that The step of setting the status of the car purchase order based on the payment result of the car purchase order includes: Based on the payment result of the car purchase order, setting a corresponding fund account for the car purchase order; Based on the paid resources of the car purchase order, the position of the capital account is determined, and the reference state corresponding to the position is set as the state of the car purchase order in multiple reference states; wherein the multiple reference states correspond to different positions of the capital account respectively.

3. The method according to claim 1 or 2, characterized in that: The method further comprises: The information of each car purchase order is collected from multiple dimensions, wherein the multiple dimensions include multiple dimensions of order details, full payment status, refund status, and price reduction status; In response to an order information viewing instruction for any dimension of the multiple dimensions, information of each car purchase order under the any dimension is displayed.

4. The method according to claim 1 or 2, characterized in that: The method further comprises: Record the handling fee information paid for each car purchase order; The handling fee information of each vehicle purchase order is respectively counted from multiple dimensions, wherein the multiple dimensions include multiple dimensions of an order dimension, a resource system dimension, a vehicle model dimension, and a merchant dimension of the vehicle; In response to an instruction to view the handling fee information of any dimension among the multiple dimensions, the handling fee information of the any dimension is displayed.

5. The method according to claim 4, characterized in that The method further comprises: Compare the handling fee information obtained from the resource system with the handling fee information of the resource system dimension; The handling fee information of the resource system dimension is sent to the financial system based on the comparison result.

6. The method according to claim 4, characterized in that Before respectively counting the handling fee information of each car purchase order from multiple dimensions, the method further includes: Receive information about a vehicle purchase order sent by a connected auxiliary payment system, wherein each of the auxiliary payment systems corresponds to a merchant that sells vehicles.

7. The method according to claim 1 or 2, characterized in that: The method further comprises: Periodically obtain the statement sent by the resource system; Compare the reconciliation statement with the target payment information of each car purchase order within the periodic period to obtain a reconciliation result; In the case where the reconciliation result indicates that the reconciliation statement matches the target payment information, a reconciliation voucher is generated and sent to the financial system.

8. The method according to claim 7, characterized in that The method further comprises: If the reconciliation result indicates that the reconciliation statement does not match the target payment information, analyzing the reconciliation statement and the target payment information respectively; If the target payment information is found to have data errors, correct the target payment information; When it is found through analysis that data errors exist in the reconciliation statement, an alarm message and the reconciliation result are sent to the financial system.

9. The method according to claim 1 or 2, characterized in that: The method further comprises: Periodically update trading sessions; After the transaction period is updated, the payment information of each car purchase order in the previous transaction period is settled to generate the settlement information corresponding to the previous transaction period.

10. The method according to claim 1 or 2, characterized in that: The method further comprises: Based on the payment information of each car purchase order, a summary report of multiple dimensions is generated, wherein the multiple dimensions include multiple dimensions of order dimension, payment channel dimension, refund dimension, abnormal transaction dimension and reconciliation dimension; In response to a report viewing instruction for any dimension among the multiple dimensions, a summary report under the any dimension is displayed.

11. The method according to claim 1 or 2, characterized in that: After sending the information of the car purchase order to the financial system, the method further includes: When a refund request is received from the target system for the vehicle purchase order, based on the payment method of the vehicle purchase order, the resource system corresponding to the target payment resource channel is called to refund the vehicle purchase order, or the financial system is requested to refund the vehicle purchase order; wherein the target system is a vehicle sales system or an after-sales system.

12. The method according to claim 1 or 2, characterized in that: In response to the vehicle sales system creating an operation on the vehicle purchase order, calling a resource system corresponding to the target payment channel to pay for the vehicle purchase order includes: Use the information receiving microservice to receive the creation operation information for the vehicle purchase order from the vehicle sales system; In response to the payment operation in the payment page, the microservice corresponding to the target payment channel is called through the payment microservice, triggering the resource system corresponding to the target payment channel to pay for the car purchase order.

13. A vehicle sales information management device, characterized in that: The vehicle sales information management device comprises: A calling module, for responding to the vehicle selling system's creation operation of the vehicle purchase order, calling the resource system corresponding to the target payment channel to pay for the vehicle purchase order; A setting module, used for setting the status of the car purchase order based on the payment result of the car purchase order; The sending module is used to send the information of the car purchase order to the financial system, wherein the information of the car purchase order includes the status of the car purchase order.

14. A car sales information management system, characterized in that: Including payment system, vehicle sales system, resource system and financial system; The payment system is used to execute the car sales information management method described in any one of claims 1 to 12, call the resource system to pay for the car purchase order, and send the car purchase order information to the financial system.

15. A computing device, characterized in that: include: Memory and processor; The memory is used to store computer programs / instructions, and the processor is used to execute the computer programs / instructions. When the programs / instructions are executed by the processor, the method according to any one of claims 1 to 12 is implemented.

16. A computer-readable storage medium, characterized in that: A computer program / instruction is stored, and when the computer program / instruction is executed by a processor, the method according to any one of claims 1 to 12 is implemented.

17. A computer program product, characterized in that The computer program product comprises a computer program / instruction, and when the computer program / instruction in the computer program product is executed by a processor, the method according to any one of claims 1 to 12 is implemented.

Images