Reconciliation method and device, server and readable storage medium

Abstract

The invention is suitable for the technical field of computers, and provides an account checking method and device, a server and a readable storage medium, and the method comprises the steps: detecting a first operation inputted by a user; obtaining first bill data and second bill data according to the first operation; and based on the first configuration rule, performing account checking processing on the first bill data and the second bill data to obtain an account checking result of the target account period task. Therefore, the corresponding first configuration rule can be set according to the actual account checking requirements of different e-commerce platforms, the method can be suitable for account checking in various scenes, the obtained account checking result is the result of the target account period task in multiple dimensions, and account checking can be more accurate.

Description

Technical Field

[0001] The present application belongs to the field of computer technology, and in particular, relates to a reconciliation method, device, server and readable storage medium. Background Art

[0002] With the increasing popularity of online shopping, the integration between e-commerce platforms and logistics platforms is becoming closer and closer. E-commerce platforms pay certain transportation fees to logistics platforms, which enables them to deliver goods to users. Therefore, when reconciling accounts, e-commerce platforms need to check the billing data of all waybills paid to logistics platforms to ensure the accuracy and authenticity of billing records.

[0003] At present, e-commerce platforms usually use manual monthly reconciliation to obtain the difference in billing data between e-commerce platforms and logistics platforms. However, due to the large number of waybills on e-commerce platforms and the large amount of billing data for waybills, manual reconciliation requires a large workload and a complex reconciliation process, resulting in low reconciliation efficiency and a high error rate. Summary of the invention

[0004] The embodiments of the present application provide a reconciliation method, device, server and readable storage medium, which can meet the diverse reconciliation needs of users and improve the reconciliation efficiency.

[0005] In a first aspect, an embodiment of the present application provides a reconciliation method, the method comprising:

[0006] Receive a first operation input by a user, where the first operation is used to trigger a reconciliation process for a target account period task;

[0007] According to the first operation, first billing data and second billing data are obtained, the first billing data being billing data of an e-commerce platform corresponding to the target billing period task, and the second billing data being billing data of a logistics platform corresponding to the target billing period task;

[0008] Based on the first configuration rule, the first bill data and the second bill data are reconciled to obtain a reconciliation result of the target account period task, the first configuration rule refers to a configuration rule for comparing specified data in the first bill data with specified data in the second bill data when performing reconciliation processing, the specified data in the first bill data is determined by a first calculation rule, the first calculation rule is a rule corresponding to the e-commerce platform, the specified data in the second bill data is determined by a second calculation rule, the second calculation rule is a rule corresponding to the logistics platform, the reconciliation result includes the first reconciliation result and / or the second reconciliation result, the first reconciliation result is the billing data corresponding to the waybill number, and the second reconciliation result is the billing data related to the fee.

[0009] In one possible implementation, the specified data in the first bill data is obtained by summing multiple data in the first bill data using a first calculation rule; and / or, the specified data in the second bill data is obtained by summing multiple data in the second bill data using a second calculation rule.

[0010] In a possible implementation, the first configuration rule also includes a first attribute setting rule, which is a rule corresponding to the e-commerce platform, and the first attribute setting rule is used to configure the starting position and / or ending position of the specified data in the first bill data when performing data comparison.

[0011] In the above implementation, the user can customize the starting position and / or ending position of the specified data in the first billing data when performing data comparison according to different reconciliation requirements of the e-commerce platform, making the reconciliation more flexible.

[0012] In a possible implementation, based on the first configuration rule, reconciliation processing is performed on the first billing data and the second billing data to obtain a reconciliation result of the target bill period task, including:

[0013] Compare the first type of data in the first billing data with the first type of data in the second billing data to obtain a first reconciliation result, where the first type of data is waybill number data;

[0014] The second category data in the first bill data is compared with the second category data in the second bill data to obtain a second reconciliation result, where the second category data is expense item data.

[0015] In the above implementation, the first bill data and the second bill data can be compared from multiple dimensions, so that the reconciliation result is more accurate and comprehensive.

[0016] In a possible implementation, before reconciling the first bill data and the second bill data, the method further includes:

[0017] Receive a first billing file uploaded by a user, and receive a second billing file uploaded by a user, the first billing file is a billing file of an e-commerce platform corresponding to the target billing period task, and the second billing file is a billing file of a logistics platform corresponding to the target billing period task;

[0018] Based on the first bill file, original bill data of the e-commerce platform is obtained, and based on the second bill file, original bill data of the logistics platform is obtained;

[0019] The original billing data of the e-commerce platform is cleaned to obtain the first billing data, and the original billing data of the logistics platform is cleaned to obtain the second billing data.

[0020] In the above implementation, the original bill data is cleaned, which can eliminate duplicate data in the bill data and correct erroneous data in the bill data, thereby making the reconciliation result more accurate.

[0021] In a possible implementation, before performing data cleaning on the original bill data, the method further includes:

[0022] Receive a second operation input by the user, where the second operation is used to trigger a space creation process;

[0023] According to the second operation, a target space is created, and the target space is used to store the bill data of the e-commerce platform and the bill data of the logistics platform;

[0024] In the target space, a target billing period task is created based on the first billing file and the second billing file. The reconciliation method of the target billing period task includes reconciliation according to a preset time period.

[0025] In the above implementation, the reconciliation process can be executed in parallel in each target space, so that multiple e-commerce platforms can be reconciled at the same time, which makes the reconciliation more efficient.

[0026] In a possible implementation, creating a target bill period task based on the first bill file and the second bill file includes:

[0027] In the target space, a target bill period task is created based on the first bill file, the second bill file, and the third bill file. The third bill file includes historical difference data, which is the difference data obtained by comparing the historical bill data of the e-commerce platform with the historical bill data of the logistics platform.

[0028] The first billing data and the second billing data are reconciled based on the first configuration rule to obtain the reconciliation result of the target bill period task, including:

[0029] Based on the first configuration rule, the first bill data, the second bill data and the historical difference data are reconciled to obtain a reconciliation result of the target bill period task.

[0030] In a possible implementation, before receiving the first operation input by the user, the method further includes:

[0031] In response to a third operation input by the user, the first configuration rule is configured.

[0032] In the above implementation, the user can customize the corresponding first configuration rule according to different reconciliation requirements of the e-commerce platform, which is more flexible.

[0033] Compared with the prior art, the embodiment of the present application can start the reconciliation process of the target account period task by receiving the first operation input by the user. Then, according to the first operation, the first bill data and the second bill data can be obtained, which can provide a data basis for the subsequent reconciliation. On this basis, the first bill data and the second bill data can be reconciled based on the first configuration rule to obtain the reconciliation result of the target account period task, and the bill data can be compared from the two dimensions of the waybill number and the expense item to obtain the bill data of the target account period task in the waybill number dimension and the bill data of the target account period task in the expense item dimension. Thereby, it is possible to customize the corresponding first configuration rule according to the actual reconciliation needs of different e-commerce platforms, which can be applied to reconciliation in various scenarios, improve the user experience, and perform the reconciliation of multiple target account period tasks in parallel to obtain the reconciliation results of each account period task in various dimensions, thereby improving the reconciliation efficiency.

[0034] In a second aspect, an embodiment of the present application provides a reconciliation device, the device comprising:

[0035] A receiving module, used for receiving a first operation input by a user, where the first operation is used for triggering a reconciliation process for a target account period task;

[0036] An acquisition module, according to the first operation, acquires first billing data and second billing data, the first billing data being billing data of an e-commerce platform corresponding to the target billing period task, and the second billing data being billing data of a logistics platform corresponding to the target billing period task;

[0037] A processing module is used to reconcile the first bill data and the second bill data based on a first configuration rule to obtain a reconciliation result of the target account period task, wherein the first configuration rule refers to a configuration rule for comparing specified data in the first bill data with specified data in the second bill data when performing reconciliation processing, the specified data in the first bill data is determined by a first calculation rule, the first calculation rule is a rule corresponding to the e-commerce platform, the specified data in the second bill data is determined by a second calculation rule, the second calculation rule is a rule corresponding to the logistics platform, the reconciliation result includes the first reconciliation result and / or the second reconciliation result, the first reconciliation result is the bill data corresponding to the waybill number, and the second reconciliation result is the bill data related to the fee.

[0038] In a third aspect, an embodiment of the present application provides a server, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the computer program, the reconciliation method in the first aspect or any possible implementation of the first aspect is implemented.

[0039] In a fourth aspect, an embodiment of the present application provides a readable storage medium, which stores instructions. When the instructions are executed on a computer, the computer executes the first aspect or any possible implementation of the first aspect, or executes the reconciliation method in the first aspect or any possible implementation of the first aspect.

[0040] In a fifth aspect, an embodiment of the present application provides a computer program product comprising instructions, which, when executed on a server, enables the server to execute the reconciliation method in the first aspect or any possible implementation of the first aspect.

[0041] It can be understood that the beneficial effects of the second to fifth aspects mentioned above can be found in the relevant description of the first aspect mentioned above, and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0043] Figure 1 It is a flowchart of a reconciliation method provided in an embodiment of the present application;

[0044] Figure 2 This is a schematic diagram of the first display interface provided in the embodiment of the present application;

[0045] Figure 3 This is a schematic diagram of a second display interface provided in an embodiment of the present application;

[0046] Figure 4 This is a schematic diagram of a third display interface provided in an embodiment of the present application;

[0047] Figure 5 This is a schematic diagram of the fourth display interface provided in the embodiment of the present application;

[0048] Figure 6 This is a fifth display interface schematic diagram provided in an embodiment of the present application;

[0049] Figure 7 This is a sixth display interface schematic diagram provided in an embodiment of the present application;

[0050] Figure 8 This is a seventh display interface schematic diagram provided in an embodiment of the present application;

[0051] Fig. 9 This is a schematic diagram of the eighth display interface provided in the embodiment of the present application;

[0052] Fig.10 This is a schematic diagram of an application scenario of a reconciliation method provided in an embodiment of the present application;

[0053] Fig.11 It is a schematic block diagram of the structure of a reconciliation device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0054] In the following description, specific details such as specific system structures and technologies are provided for illustration rather than limitation, so as to provide a thorough understanding of the embodiments of the present application. However, it should be clear to those skilled in the art that the present application can also be implemented in other embodiments without these specific details.

[0055] It should be understood that when used in the present specification and the appended claims, the term "comprising" indicates the presence of described features, wholes, steps, operations, elements and / or components, but does not exclude the presence or addition of one or more other features, wholes, steps, operations, elements, components and / or combinations thereof.

[0056] It should also be understood that the term “and / or” used in the specification and appended claims refers to any and all possible combinations of one or more of the associated listed items, and includes these combinations.

[0057] As used in this specification and the appended claims, the term "if" may be interpreted as "when" or "uponce" or "in response to determining" or "in response to detecting" depending on the context.

[0058] In addition, in the description of the present application specification and the appended claims, the terms "first", "second", "third", etc. are only used to distinguish the descriptions and cannot be understood as indicating or implying relative importance.

[0059] References to "one embodiment" or "some embodiments" etc. described in the specification of this application mean that one or more embodiments of the present application include specific features, structures or characteristics described in conjunction with the embodiment. Therefore, the statements "in one embodiment", "in some embodiments", "in other embodiments", etc. that appear in different places in this specification do not necessarily refer to the same embodiment, but mean "one or more but not all embodiments", unless otherwise specifically emphasized in other ways. The terms "including", "comprising", "having" and their variations all mean "including but not limited to", unless otherwise specifically emphasized in other ways.

[0060] See also Figure 1 , Figure 1 A flow chart of a reconciliation method provided in an embodiment of the present application is shown.

[0061] like Figure 1 As shown, the reconciliation method of the embodiment of the present application includes the following steps:

[0062] S101, receiving a first operation input by a user, where the first operation is used to trigger a reconciliation process for a target account period task.

[0063] When receiving the first operation input by the user in the first interface, the server may start the reconciliation process of the target account period task.

[0064] The first interface is a display interface in the server, and may include related controls for triggering the reconciliation process.

[0065] Exemplarily, the first interface may include a start control. At this time, the user may trigger the first operation by clicking the start control in the first interface. In response to the user's triggering operation on the start control, the server may start the reconciliation process.

[0066] It should be noted that the user can complete the click operation with the help of a hardware device. For example, the hardware device is a mouse or a stylus. The user can also complete the click operation directly with a finger, and the actual click method can be adjusted in real time according to the screen characteristics of the server, which is not limited in the embodiments of the present application.

[0067] S102: According to the first operation, obtain first billing data and second billing data.

[0068] The first billing data is the billing data of the e-commerce platform corresponding to the target billing period task. Exemplarily, the first billing data may include first-category data and second-category data. The first-category data is the result data of the waybill number in the e-commerce platform. The second-category data is the result data of the expense items in the e-commerce platform. The expense items may include freight and additional service fees, etc.

[0069] The target account period task is the account period task that needs to be reconciled. There can be one or more target account period tasks. When there are multiple target account period tasks, the server can start the reconciliation process of multiple target account period tasks at the same time point, so that the server can perform the reconciliation of multiple target account period tasks in parallel, thereby improving the reconciliation efficiency.

[0070] The second billing data is the billing data of the logistics platform corresponding to the target billing period task. Exemplarily, the second billing data may include the first type of data and the second type of data. At this time, the first type of data is the result data of the waybill number in the logistics platform. The second type of data is the result data of the expense item in the logistics platform.

[0071] It should be noted that when there is one target billing period task, there is one first billing data and one second billing data. When there are multiple target billing period tasks, there are multiple first billing data and multiple second billing data. It should be understood that the multiple first billing data can be the same or different. The multiple second billing data can be the same or different.

[0072] It should also be noted that a first billing data represents all billing data of the e-commerce platform corresponding to the target bill period task, rather than the number of billing data being only one. Similarly, the multiple first billing data in the embodiment of the present application should not be simply understood as the number of data being multiple. The description of the second billing data can refer to the relevant explanation of the first billing data, which will not be repeated here.

[0073] After receiving the first operation, the server may start the reconciliation process of the target account period task according to the first operation. After starting the reconciliation process of the target account period task, the server may first obtain the first bill data and the second bill data, thereby providing a data basis for reconciliation.

[0074] Optionally, the server may obtain the pre-stored first billing data and the second billing data from a database. For example, the database may be a hive database or a MySQL database. The hive database is used to extract, transform and load data. The hive database can map a structured data file to a database table. The MySQL database is a relational database management system that can store data in different tables instead of placing all data in a large warehouse, thereby speeding up data query and improving the flexibility of data query.

[0075] Alternatively, the server may also obtain the pre-stored first billing data and the second billing data from the hard disk of the server, which is not limited in this application.

[0076] S103, based on the first configuration rule, reconcile the first billing data and the second billing data to obtain a reconciliation result of the target bill period task.

[0077] The first configuration rule is a reconciliation rule pre-configured by the user. The first configuration rule may include at least one of a first calculation rule, a second calculation rule, a first attribute setting rule, and a second attribute setting rule. The first configuration rule may be stored in a database or a hard disk of a server.

[0078] The first configuration rule refers to a configuration rule for comparing the specified data in the first bill data with the specified data in the second bill data when performing reconciliation processing. For example, when the bill data is presented in an Excel table, the specified data may be row data in the table or column data in the table.

[0079] Optionally, the specified data in the first billing data is determined by a first calculation rule. The first calculation rule is a rule corresponding to the e-commerce platform. The specified data in the second billing data is determined by a second calculation rule. The second calculation rule is a rule corresponding to the logistics platform. Exemplarily, the specified data in the first billing data is obtained by summing multiple data in the first billing data using the first calculation rule (for example, the sum of multiple columns of data specified in a table, or the sum of multiple rows of data corresponding to a column of data specified in the table); and / or, the specified data in the second billing data is obtained by summing multiple data in the second billing data using the second calculation rule.

[0080] Optionally, the first configuration rule may further include a first attribute setting rule. The first attribute setting rule is a rule corresponding to the e-commerce platform, and the first attribute setting rule is used to configure the starting position and / or ending position of the specified data in the first bill data in the first bill data when performing data comparison.

[0081] Exemplarily, when the billing data is presented in the form of an Excel table, the first billing data includes row data and column data, and the second billing data includes row data and column data. At this time, the user can set the starting position (for example, starting column or starting row) of the specified data in the first billing data when performing data comparison by means of header configuration. In response to the user's setting operation, the server can obtain the starting position of the specified data in the first billing data in the first billing data when performing data comparison. It should be understood that the header refers to the starting row or starting column of the Excel table. Figure 2 As shown, the user can set the attribute of the table header to the number of rows, and the value of the table header to 12. In response to the user's setting operation, the server can compare the first bill data starting from the 12th row of the table.

[0082] In addition, the user can set the end position (for example, the end column or the end row) of the specified data in the first billing data when performing data comparison through the table footer configuration. In response to the user's setting operation, the server can obtain the end position of the specified data in the first billing data when performing data comparison.

[0083] It should be understood that the end of the table refers to the end row or column of the Excel table. Figure 2As shown, the user can set the attribute of the footer to a character and the value of the footer to a total. In response to the user's setting operation, the server can end the comparison process of the first bill data and display the total value of at least one column (for example, the total amount, etc.) at the footer of the table. It should be noted that the footer can be the last row of the table or any row after the 12th row. Usually, the footer is the last row of the table. Thus, the server can obtain the first attribute setting rule corresponding to the e-commerce platform.

[0084] Optionally, the first configuration rule may further include a second attribute setting rule. The second attribute setting rule is a rule corresponding to the logistics platform, and the second attribute setting rule is used to configure the starting position and / or ending position of the specified data in the second bill data in the second bill data when performing data comparison. The relevant description of the second attribute setting rule can refer to the above description of the first attribute setting rule, which will not be repeated here.

[0085] It should be understood that the above-mentioned first calculation rule, second calculation rule, first attribute setting rule and second attribute setting rule can be customized by the user according to actual reconciliation needs, and this application does not limit this.

[0086] In some embodiments, when receiving a third operation input by the user in the second interface A, the server may configure the first configuration rule in response to the third operation input by the user.

[0087] Optionally, the user may input relevant setting information of the first configuration rule on the second interface A of the server. In response to the relevant setting information input by the user, the server may configure the first configuration rule.

[0088] Based on the above description, if Figure 2 As shown, the user can set the calculation rule of the waybill number corresponding to the e-commerce platform to column L, where column L represents the column where the waybill number in the first billing data is located, and set the calculation rule of the expense item corresponding to the e-commerce platform to column A + column B + column F, where columns A, B, and F represent the columns where the expense items corresponding to the waybill number in the first billing data are located. In response to the user's setting operation, the server can configure the first calculation rule. On this basis, the user can also set the calculation rule of the waybill number corresponding to the logistics platform to column C, where column C represents the column where the waybill number in the second billing data is located, and set the calculation rule of the expense item corresponding to the logistics platform to column E, where column E represents the column where the expense items corresponding to the waybill number in the second billing data are located. In response to the user's setting operation, the server can configure the second calculation rule.

[0089] In summary, after the user has entered the relevant setting information, he can click the confirmation control 10 in the second interface A. In response to the user's click operation on the confirmation control 10, the server can configure the first attribute setting rule, the first calculation rule and the second calculation rule, so that the server can obtain the first configuration rule.

[0090] It should be noted that both the first calculation rule and the second calculation rule can be pre-defined by the user. In other words, the first calculation rules corresponding to different e-commerce platforms can be the same or different. The second calculation rules corresponding to different logistics platforms can be the same or different. Usually, the first calculation rules corresponding to different e-commerce platforms are different, and the second calculation rules corresponding to different logistics platforms are also different.

[0091] It should be understood that Figure 2 The interface shown is only one configuration method of the first configuration rule in the embodiment of the present application. Those skilled in the art can also configure the first configuration rule according to the actual situation. Figure 2 11 or manually input to select other configuration methods of the first configuration rule. For example, configure the second attribute setting rule corresponding to the logistics platform, or set the cost item calculation rule corresponding to the logistics platform to the sum of multiple columns, or Figure 2 The rows and columns in the program are interchanged, etc., which is not limited in this application.

[0092] The reconciliation result may include a first reconciliation result and / or a second reconciliation result, the first reconciliation result is the billing data corresponding to the waybill number, and the second reconciliation result is the billing data related to the fee. For example, the reconciliation result may be presented in an Excel spreadsheet.

[0093] Exemplarily, the reconciliation results can be stored in a hive database or a MySQL database. Since the hive database has a large amount of data and contains all the detailed data in the reconciliation process, the server can synchronously transfer the reconciliation results in the hive database to the MySQL database for storage through a data transmission carrier (e.g., etl). This allows the server to quickly obtain the reconciliation results when the user needs to view or download the reconciliation results, thereby improving efficiency.

[0094] After obtaining the first billing data, the second billing data and the first configuration rule, the server may reconcile the first billing data and the second billing data based on the first configuration rule. For example, when the billing data is in the form of an Excel table, the comparison of column data is used as an example. The server may compare any column of data in the first billing data with any column of data in the second billing data. Alternatively, the server may compare the sum of any multiple columns of data in the first billing data with any multiple columns of data in the second billing data. Alternatively, the server may compare the sum of any multiple columns of data in the first billing data with the sum of any multiple columns of data in the second billing data.

[0095] In some embodiments, the server can use an offline calculation module to reconcile the first bill data and the second bill data. In addition, the offline calculation module is also used to aggregate the same type of data with a longer time span in the bill data offline, which can make the reconciliation result more accurate.

[0096] Thus, the server can obtain the reconciliation result of the target account period task after the reconciliation processing, so that the user can view the current data and trace the historical data through the reconciliation result of the target account period task, which is more efficient.

[0097] It should be noted that the time for the reconciliation process can be set by the user according to the actual reconciliation needs, and this application does not limit this. For example, the actual setting for the reconciliation process is 30 minutes.

[0098] In some embodiments, the user can view and download the first reconciliation result and the second reconciliation result in the third interface B of the server. The third interface B is a display interface for the reconciliation result. Figure 3 As shown, the third interface B includes four verification items: logistics platform bill, e-commerce platform bill, waybill number and expense item. The total number of pieces in the logistics platform bill is piece quantity (or, number of express parcels) A, and the total amount is amount A. The total number of pieces in the e-commerce platform bill is piece quantity B, and the total amount is amount B. The number of pieces of the waybill number is piece quantity C, and the amount is amount C. The number of pieces of the expense item is piece quantity D, and the amount is amount D. When the user clicks the download control 12 of the row where the waybill number is located in the third interface B, the server can download the first reconciliation report, and when the user clicks the download control 12 of the row where the expense item is located in the third interface B, the server can download the second reconciliation report.

[0099] In other embodiments, the waybill number may include a first waybill number and a second waybill number. The first waybill number is used to indicate a waybill number that is available on the e-commerce platform but not on the logistics platform. The second waybill number is used to indicate a waybill number that is available on the logistics platform but not on the e-commerce platform. The expense items may include a first expense item and a second expense item. The first expense item is used to indicate expenses with the same amount on the logistics platform and the e-commerce platform. The second expense item is used to indicate expenses with different amounts on the logistics platform and the e-commerce platform. In addition, the reconciliation results corresponding to the four verification items, namely the first waybill number, the second waybill number, the first expense item and the second expense item, can all be expressed by the quantity and amount.

[0100] It should be understood that the above description is described using an e-commerce platform as an example so that the technical solution of the present application can be more clearly illustrated. The reconciliation method of the embodiment of the present application is also applicable to the reconciliation of multiple e-commerce platforms.

[0101] Considering that the actual reconciliation requirements of each of the multiple e-commerce platforms are different, if an e-commerce platform only needs to compare the expense items, then the reconciliation result obtained by the server is only the second reconciliation result, that is, the result of the expense item dimension. If an e-commerce platform needs to compare not only the expense items but also the waybill number, then the reconciliation result obtained by the server includes not only the second reconciliation result but also the first reconciliation result. In this way, the first bill data and the second bill data can be compared from multiple dimensions, making the reconciliation result more accurate.

[0102] The embodiment of the present application can start the reconciliation process of the target account period task by receiving the first operation input by the user. Then, according to the first operation, the first bill data and the second bill data can be obtained, which can provide a data basis for reconciliation. On this basis, the first bill data and the second bill data can be reconciled based on the first configuration rule to obtain the reconciliation result of the target account period task, and the bill data can be compared from the two dimensions of waybill number and expense item to obtain the bill data of the target account period task in the waybill number dimension and the bill data of the target account period task in the expense item dimension. Thereby, it is possible to customize the corresponding first configuration rule according to the actual reconciliation needs of different e-commerce platforms, which can be applied to reconciliation in various scenarios, improve the user experience, and perform the reconciliation of multiple target account period tasks in parallel to obtain the reconciliation results of each account period task in various dimensions, thereby improving the reconciliation efficiency.

[0103] In the embodiment of the present application, the server can obtain the reconciliation result of the account period task in a variety of ways, and the specific implementation process of the server obtaining the reconciliation result of each account period task is the same.

[0104] Based on the description of S103, a possible implementation method for the server to obtain a reconciliation result of a target account period task is described in detail below.

[0105] In some embodiments, after obtaining the first billing data and the second billing data, the server may compare the first category of data in the first billing data with the first category of data in the second billing data to obtain a first reconciliation result. In other words, the server may compare the result data of the waybill number in the first billing data with the result data of the waybill number in the second billing data to obtain a reconciliation result in the dimension of the waybill number, i.e., the first reconciliation result.

[0106] In another embodiment, after obtaining the first billing data and the second billing data, the server may also compare the result data of the expense items in the first billing data with the result data of the expense items in the second billing data to obtain a reconciliation result on the expense item dimension, i.e., a second reconciliation result.

[0107] Thus, the server can compare the first bill data and the second bill data from multiple dimensions to obtain the reconciliation result of the target bill period task in each dimension, making the reconciliation more comprehensive and more accurate.

[0108] Considering that billing data may be stored in a variety of billing formats (for example, text format and table format, etc.), the billing data may also include user-defined personalized fields (for example, waybill number, time, additional service fees, freight and other expense items, etc.). If the billing data of the e-commerce platform and the billing data of the logistics platform are directly reconciled, it is necessary to extract the billing data from different billing formats separately and compare them according to different dimensions, which will result in a long reconciliation cycle and low reconciliation efficiency. Therefore, before performing the reconciliation process, the server can clean the billing data of the e-commerce platform and the billing data of the logistics platform, eliminate duplicate data and erroneous data in the billing data, improve the quality of the billing data, thereby reducing the reconciliation time and improving the reconciliation efficiency and reconciliation accuracy.

[0109] Optionally, in some embodiments, before reconciling the first billing data and the second billing data, the server may receive a first billing file uploaded by the user, and the server may receive a second billing file uploaded by the user.

[0110] The first billing file is a billing file of an e-commerce platform corresponding to the target billing period task, and the first billing file includes the original billing data of the e-commerce platform. The second billing file is a billing file of a logistics platform corresponding to the target billing period task, and the second billing file includes the original billing data of the logistics platform. The original billing data refers to data that has not been sorted and summarized. Exemplarily, the original billing data may include original billing data with a header and original billing data without a header.

[0111] For example, Figure 4As shown, it is the fourth interface C of the server. The fourth interface C is a display interface for importing current data in the uploaded bill file. The user can upload the bill file by clicking the control 13 for selecting a compressed package and the confirmation control 10 in the fourth interface C. In response to the user's click operation on the control 13 for selecting a compressed package and the confirmation control 10, the server can receive the bill file. Specifically, the user can select the first bill file by clicking the control 13 for selecting a compressed package corresponding to the e-commerce bill, and in response to the user's click operation on the control 13 for selecting a compressed package and the confirmation control 10, the server can receive the first bill file. The user can select the second bill file by clicking the control 13 for selecting a compressed package corresponding to the logistics bill, and in response to the user's click operation on the control 13 for selecting a compressed package and the confirmation control 10, the server can receive the second bill file.

[0112] For example, Figure 5 As shown, the fifth interface D of the server. The fifth interface D is a display interface for importing historical data in the uploaded bill file. The user can select and upload the file of historical difference data by clicking the control 13 for selecting a compressed package and the confirmation control 10 in the fifth interface D. In response to the user's click operation on the control 13 for selecting a compressed package and the confirmation control 10, the server can receive the file of historical difference data. The historical difference data is the difference data obtained by comparing the historical billing data of the e-commerce platform with the historical billing data of the logistics platform.

[0113] Optionally, Figure 4 The fourth interface C and Figure 5 The fifth interface D shown only supports compressed package upload, and multiple compressed packages can be selected. The size of each compressed package in the multiple compressed packages does not exceed 500M, and the format of the compressed package is zip format. It should be understood that the size and format of the compressed package are exemplary, and those skilled in the art can also set other sizes and formats according to actual conditions, which is not limited in this application.

[0114] Thus, the server can obtain the original billing data of the e-commerce platform based on the first billing file. And the server can obtain the original billing data of the logistics platform based on the second billing file.

[0115] Based on the above description, the server can perform data cleaning on the original bill data of the e-commerce platform to obtain the first bill data, and the server can perform data cleaning on the original bill data of the logistics platform to obtain the second bill data. Exemplarily, the server can perform data cleaning on the original bill data through the Flink module. The Flink module is used to sort and summarize the data. The Flink module is also used to transfer the data after data cleaning to the hive database for storage.

[0116] In some embodiments, the original bill data can be written to the server in parallel by means of distributed timed tasks. Distributed timed task sharding can be sharded according to multiple dimensions such as time, waybill number, and expense items. Exemplarily, when the original bill data is written in the form of distributed timed tasks, the writing speed of 100,000 data items per second can be achieved, which saves a lot of time and improves the writing efficiency of the original bill data compared to writing the original bill data one by one. Exemplarily, the server can write the original bill data to the hive database or the Kafka module of the server by means of distributed timed tasks. If a large amount of original bill data (for example, original bill data of the order of 100 million) is written directly to the hive database, the writing speed is slow and may cause the hive database to crash. The Kafka module is a high-throughput distributed publish-subscribe message system for processing all action stream data entered by the user. The Kafka module supports parallel writing and can increase the rate at which the original bill data is written.

[0117] In the case where multiple e-commerce platforms need to be reconciled, the server can create multiple target spaces and complete the reconciliation process of the corresponding e-commerce platforms in each target space. A target space is used to store the billing data of an e-commerce platform and the billing data of a logistics platform. Multiple spaces exist independently, and there will be no data overlap in the billing data in multiple spaces, and the reconciliation processes do not interfere with each other. For example, when the e-commerce platforms that need to be reconciled include e-commerce platform 1 and e-commerce platform 2, the server can create a target space 1 corresponding to e-commerce platform 1, and create a target space 2 corresponding to e-commerce platform 2. The server can complete the reconciliation process of e-commerce platform 1 in target space 1. The server can complete the reconciliation process of e-commerce platform 2 in target space 2. It should be understood that the reconciliation process of e-commerce platform 1 and the reconciliation process of e-commerce platform 2 can be executed simultaneously, or in the order of creating the target spaces, and this application does not limit this.

[0118] Optionally, before performing data cleaning on the original bill data, the user may trigger a second operation in the sixth interface E of the server. Upon receiving the second operation input by the user, the server may start the space creation process. After receiving the second operation, the server may create a target space according to the second operation. Thus, the server can complete the reconciliation process of the corresponding e-commerce platform in the target space.

[0119] For example, Figure 6 As shown, the sixth interface E of the server is shown. The sixth interface E is a display interface for creating a space. The user can trigger the second operation by clicking the control 14 of the new space in the sixth interface E. In response to the user's click operation on the control 14 of the new space, the server can start the space creation process. In addition, the user can also click Figure 6 In response to the user's click operation on the edit control 15, the server can display the edit control 15 as shown in FIG. Figure 6 The sixth interface E shown jumps to display as follows Figure 7 The seventh interface F is shown.

[0120] The user can edit the space 1 in the seventh interface F. Specifically, the user enters the space name and the account group members, and uploads the space name and account group members to the server by clicking the confirmation control 10. In response to the user's click operation on the confirmation control 10, the server can obtain the space name and account group members. Figure 7 As shown, the seventh interface F uses the user number as the representation form of the account reconciliation group member for exemplary description. Number A, number B and number C among the added members all have the authority to log in to the server and start the account reconciliation process.

[0121] The space name may be a combination of one or more of Chinese characters, letters, numbers, and symbols. The reconciliation group member may be a user number or user name, etc. The reconciliation group member may be a financial staff or other user with reconciliation authority, and each reconciliation group member may modify the first configuration rule, which is not limited in this application.

[0122] For any target space, in the target space, the server may create a target billing period task based on the first billing file and the second billing file.

[0123] For example, Figure 8 As shown, the eighth interface G of the server. The eighth interface G is a display interface for monthly reconciliation of bill period tasks in space 1. In the eighth interface G, the user can trigger the creation of a target bill period task by clicking the control 16 for adding a bill period task. In response to the user's click operation on the control 16 for adding a bill period task, the server can jump from displaying the eighth interface G to displaying the interface for adding a bill period task. The interface for adding a bill period task may include the following: Figure 4 The fourth interface C shown and Figure 5 The fifth interface D shown. The user can upload the first bill file and the second bill file in the fourth interface C. Thus, the server creates a target bill period task based on the first bill file and the second bill file.

[0124] Optionally, the reconciliation method of the target account period task includes reconciliation according to a preset duration. The preset duration may be a duration defined in years, months, weeks or days as time units. Thus, the user can select a corresponding reconciliation method according to actual reconciliation needs to ensure the accuracy of the reconciliation result.

[0125] Optionally, the execution status of the target account period task includes any of the following states: not executed, executing, or completed. Not executed means that the server has not started to reconcile the target account period task. Executing means that the server is reconciling the target account period task. Completed means that the server has completed the reconciliation process of the target account period task. After creating the target account period task, the execution status of the target account period task can be displayed in the display interface of the server, so that the user can more intuitively understand the reconciliation status of the target task through the execution status of the target account period task displayed in the display interface of the server.

[0126] For example, Figure 8 As shown in the figure, Accounting Task A, Accounting Task B and Accounting Task C are all created accounting tasks for monthly reconciliation. Fig. 9 As shown, the ninth interface H of the server. The ninth interface H is a display interface for the daily reconciliation of the account period tasks in space 1 (or in other words, the in-transit reconciliation). Account period tasks D, E and F in the ninth interface H are all account period tasks that have been created for daily reconciliation. Taking account period task A as an example, the execution status of account period task A is not executed and the adding time is time A. The user can view the execution status of account period task A through the viewing control in the eighth interface G. In the eighth interface G and the ninth interface H, the user can also view other added account period tasks by sliding the scroll bar 17. In response to the user's operation of the sliding scroll bar 17, the server can control the interface to scroll up and down.

[0127] Since the target account period task is created based on the bill file, and the bill file uploaded by the user may also include a file of historical difference data, the server also needs to combine the file of historical difference data when creating the target account period task, and the reconciliation processing also needs to be compared with the historical difference data to make the reconciliation result more accurate.

[0128] Optionally, in the target space, the server may create a target billing period task based on the first billing file, the second billing file and the third billing file (or the file of historical difference data). The third billing file includes the historical difference data.

[0129] On this basis, the server can reconcile the first bill data, the second bill data and the historical difference data based on the first configuration rule to obtain the reconciliation result of the target bill period task, thereby avoiding the situation where the same waybill number or expense item has a billing date of A in the first bill data and a billing date of B in the second bill data, making it impossible to perform daily reconciliation, resulting in reconciliation errors, thereby improving the accuracy of the reconciliation results.

[0130] It should be understood that the first interface, the second interface A, the third interface B and the fourth interface C are exemplary interfaces of the embodiment of the present application, and their purpose is only to clearly illustrate the technical solution of the embodiment of the present application. Other display interfaces may also be provided in the server. For example, other display interfaces may be jump interfaces of the above-mentioned interfaces, and the present application does not limit this.

[0131] In some embodiments, the reconciliation method of the embodiment of the present application can be implemented by a software module in the server in addition to being implemented by the server. For example, the software module is a reconciliation system created in code form. The user can log in to the reconciliation system and input, modify, and query the relevant information of each display interface in multiple display interfaces of the reconciliation system.

[0132] based on Figures 1 to 9 The following description is combined with Fig.10 , an example is given to illustrate the specific implementation process of the reconciliation method of this application.

[0133] Assume that a reconciliation system, a hive database, and a MySQL database are set up on the server. The reconciliation system includes a Kafka module, a Flink module, and an offline computing module.

[0134] Assume that the e-commerce platforms that need to be reconciled are e-commerce platform 1 and logistics platform 1, and the reconciliation method adopted is monthly reconciliation. The bill files uploaded by the user include the current bill file of e-commerce platform 1, the current bill file of logistics platform 1, and the files of historical difference data of e-commerce platform 1 and logistics platform 1.

[0135] like Fig.10 As shown, the user can upload the current bill file of e-commerce platform 1, the current bill file of logistics platform 1, and the file of historical difference data between e-commerce platform 1 and logistics platform 1 in the display interface of the server. After receiving the user's upload operation, the server can obtain the current bill data of e-commerce platform 1, the current bill data of logistics platform 1, and the historical difference data between e-commerce platform 1 and logistics platform 1, and start the automatic reconciliation process to obtain the reconciliation result. With the user's online assistance (for example, uploading bill files and setting the first configuration rule, etc.), the server can perform automatic reconciliation and display the reconciliation results to the user. The user can view the difference data through the reconciliation results. For example, the difference data shows that the amount of e-commerce platform 1 is greater than the amount of logistics platform 1, but the quantity of e-commerce platform 1 is less than the quantity of logistics platform 1.

[0136] exist Fig.10 In the application scenario, combined with the above Figures 2 to 9 The display interface shown in details describes the specific implementation process of the reconciliation method of the present application. The reconciliation method of the present application specifically includes the following steps:

[0137] Step 11: The user can log in to the account reconciliation system on the login interface. For example, the user can log in to the account reconciliation system by entering an account number and password.

[0138] Step 12: The user can enter the fifth interface E (such as Figure 6 Click the control for adding a new space.

[0139] Step 13, after receiving the user's click operation, the reconciliation system can create Space 1 of the e-commerce platform 1.

[0140] Step 14: The user can enter the seventh interface G (such as Figure 8 Click the control to add a billing period task.

[0141] Step 15, after receiving the user's click operation, the reconciliation system can start the process of creating the account period task A. At this time, the reconciliation system jumps from displaying the seventh interface G to displaying the fourth interface C (such as Figure 4 shown).

[0142] Step 16: The user can select the current bill file of the e-commerce platform 1 and upload the current bill file of the logistics platform 1 in the fourth interface C of the reconciliation system. The user can select the current bill file of the e-commerce platform 1 and upload the current bill file of the logistics platform 1 in the fifth interface D of the reconciliation system (such as Figure 5 As shown in the figure, select the file of historical difference data of e-commerce platform 1 and logistics platform 1, and click the confirmation control. At this time, the reconciliation system can obtain the created account period task A.

[0143] Step 17, write the current bill file of e-commerce platform 1, the current bill file uploaded to logistics platform 1, and the file of historical difference data between e-commerce platform 1 and logistics platform 1 into the Kafka module of the reconciliation system in parallel in the form of distributed scheduled tasks.

[0144] Step 18, the Kafka module transmits the current billing data of e-commerce platform 1 to the Flink module, uploads the current billing data of logistics platform 1, and the historical difference data between e-commerce platform 1 and logistics platform 1.

[0145] In step 19, the Flink module cleans the current billing data of e-commerce platform 1, the current billing data uploaded to logistics platform 1, and the historical difference data between e-commerce platform 1 and logistics platform 1 to obtain the first billing data, the second billing data, and the third billing data.

[0146] Step 20: The Flink module transmits the first bill data, the second bill data, and the third bill data to the hive library.

[0147] Step 21: The user can access the second interface A (eg Figure 2 The first configuration rule is set in (as shown).

[0148] It should be understood that there is no temporal order between step 20 and step 21, and step 20 and step 21 can be executed simultaneously or sequentially. In addition, the configuration rule of step 21 can also be before step 16, that is, the execution order of the configuration rule and the steps of uploading the bill file and cleaning the data can be interchanged, and the specific execution order shall be based on the order of the actual interactive interface in the reconciliation system.

[0149] In step 22, the user can start the account period task A in the start interface of the account reconciliation system.

[0150] Step 23, after receiving the user's start operation, the offline calculation module in the reconciliation system can obtain the first bill data, the second bill data and the third bill data from the hive library.

[0151] In step 24, the offline calculation module may reconcile the first billing data, the second billing data, and the third billing data based on the first configuration rule to obtain the reconciliation details of the bill period task A.

[0152] Step 25, the offline computing module transmits the reconciliation details of the account period task A and the reconciliation result of the account period task A to the hive database.

[0153] Step 26: Synchronously transfer the reconciliation result of account period task A in the hive database to the MySQL database for storage through the carrier of etl.

[0154] Step 27: The user enters the third interface B (eg Figure 3 Click the download control to download the reconciliation results.

[0155] Step 28, after receiving the user's click operation, the reconciliation system can obtain the reconciliation result of the account period task A from the MySQL database. Compared with directly obtaining from the hive database, the acquisition process is simpler and faster.

[0156] In summary, the reconciliation method of the embodiment of the present application is implemented by front-end interface and back-end processing. The front-end interface is used to provide an interface for human-computer interaction. Human-computer interaction can adopt web website technology, which can include hypertext markup language (Hyper Text Markup Language, HTML), Cascading Style Sheets (Cascading Style Sheets, CSS) and scripting language (Java Script, JS) and the like. In addition, the web site can be accessed through the browser in the server, or the uniform resource locator (Url) address, and the access method is more flexible, more convenient for sharing, and can improve the user experience. The back-end processing can include the processing process of the three modules of Kafka module, Flink module and offline computing module, see the description in the above steps, and will not be repeated here. Users can independently create space, independently create account period tasks, independently configure the first configuration rule, and independently select bill files in the reconciliation system, so that it can be realized according to the user's reconciliation needs, according to the user's self-configured first configuration rule, from multiple dimensions to check the first bill data of the e-commerce platform and the second bill data of the logistics platform, obtain multiple dimensions of reconciliation results, and improve the accuracy of reconciliation.

[0157] See also Fig.11 , Fig.11 FIG. 1 is a schematic block diagram showing a structure of a reconciliation device provided in an embodiment of the present application. Fig.11 As shown, the reconciliation device 300 of the present application may include:

[0158] A receiving module 301 is used to receive a first operation input by a user, where the first operation is used to trigger a reconciliation process for a target account period task;

[0159] The acquisition module 302 acquires first billing data and second billing data according to the first operation, wherein the first billing data is billing data of the e-commerce platform corresponding to the target billing period task, and the second billing data is billing data of the logistics platform corresponding to the target billing period task;

[0160] Processing module 303 is used to reconcile the first bill data and the second bill data based on the first configuration rule to obtain the reconciliation result of the target account period task. The first configuration rule refers to a configuration rule for comparing the specified data in the first bill data with the specified data in the second bill data when performing the reconciliation process. The specified data in the first bill data is determined by a first calculation rule, which is a rule corresponding to the e-commerce platform. The specified data in the second bill data is determined by a second calculation rule, which is a rule corresponding to the logistics platform. The reconciliation result includes the first reconciliation result and / or the second reconciliation result. The first reconciliation result is the bill data corresponding to the waybill number, and the second reconciliation result is the bill data related to the fee.

[0161] In some embodiments, the specified data in the first billing data is obtained by summing multiple data in the first billing data using a first calculation rule; and / or, the specified data in the second billing data is obtained by summing multiple data in the second billing data using a second calculation rule.

[0162] In some embodiments, the first configuration rule also includes a first attribute setting rule, which is a rule corresponding to the e-commerce platform, and the first attribute setting rule is used to configure the starting position and / or ending position of the specified data in the first bill data when performing data comparison.

[0163] In some embodiments, the processing module 303 is also used to compare the first category of data in the first billing data with the first category of data in the second billing data to obtain a first reconciliation result, where the first category of data is the waybill number data; and to compare the second category of data in the first billing data with the second category of data in the second billing data to obtain a second reconciliation result, where the second category of data is the expense item data.

[0164] In some embodiments, before reconciling the first bill data and the second bill data, the processing module 303 is further used to receive a first bill file uploaded by a user, and to receive a second bill file uploaded by a user, wherein the first bill file is a bill file of an e-commerce platform corresponding to the target bill period task, and the second bill file is a bill file of a logistics platform corresponding to the target bill period task;

[0165] Based on the first billing file, the original billing data of the e-commerce platform is obtained, and based on the second billing file, the original billing data of the logistics platform is obtained; the original billing data of the e-commerce platform is cleaned to obtain the first billing data, and the original billing data of the logistics platform is cleaned to obtain the second billing data.

[0166] In some embodiments, before performing data cleaning processing on the original bill data, the processing module 303 is also used to receive a second operation input by the user, and the second operation is used to trigger the space creation process; according to the second operation, a target space is created, and the target space is used to store the billing data of the e-commerce platform and the billing data of the logistics platform; in the target space, based on the first bill file and the second bill file, a target bill period task is created, and the reconciliation method of the target bill period task includes reconciliation according to a preset time period.

[0167] In some embodiments, the processing module 303 is also used to create a target bill period task in the target space based on the first bill file, the second bill file and the third bill file, wherein the third bill file includes historical difference data; and the processing module 303 is also used to reconcile the first bill data, the second bill data and the historical difference data based on the first configuration rule to obtain a reconciliation result of the target bill period task, wherein the historical difference data is difference data obtained by comparing the historical bill data of the e-commerce platform with the historical bill data of the logistics platform.

[0168] In some embodiments, before receiving the first operation input by the user, the processing module 303 is further configured to configure the first configuration rule in response to a third operation input by the user.

[0169] In some embodiments, the server of the present application may include: a processor, a memory, a communication interface, and a bus. The processor, the memory, and the communication interface communicate via the bus, or may communicate via other means such as wireless transmission. The memory is used to store instructions, and the processor is used to execute instructions stored in the memory. The memory stores program code, and the processor may call the program code stored in the memory to execute. Figure 1 The reconciliation method shown.

[0170] It should be understood that in the embodiments of the present application, the processor may be a CPU, or may be other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field programmable gate arrays (FPGAs) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor may be a microprocessor or any conventional processor, etc.

[0171] The memory may include a read-only memory and a random access memory, and provide instructions and data to the processor. The memory may also include a non-volatile random access memory. The memory may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memories. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as static RAM (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link DRAM (SLDRAM), and direct memory bus random access memory (DR RAM).

[0172] In addition to the data bus, the bus may also include a power bus, a control bus, a status signal bus, etc.

[0173] An embodiment of the present application further provides a readable storage medium, which stores a computer program. When the computer program is executed by a processor, the steps in the above-mentioned method embodiments can be implemented.

[0174] The embodiment of the present application also provides a computer program product including instructions, which, when executed on a proxy server, enables the proxy server to execute the steps in the above-mentioned method embodiments.

[0175] The technicians in the relevant field can clearly understand that for the convenience and simplicity of description, only the division of the above-mentioned functional units and modules is used as an example for illustration. In practical applications, the above-mentioned function allocation can be completed by different functional units and modules as needed, that is, the internal structure of the above-mentioned device can be divided into different functional units or modules to complete all or part of the functions described above. The functional units and modules in the embodiment can be integrated in a processing unit, or each unit can exist physically separately, or two or more units can be integrated in one unit. The above-mentioned integrated unit can be implemented in the form of hardware or in the form of software functional units. In addition, the specific names of the functional units and modules are only for the convenience of distinguishing each other, and are not used to limit the scope of protection of this application. The specific working process of the units and modules in the above-mentioned system can refer to the corresponding process in the aforementioned method embodiment, which will not be repeated here.

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

[0177] Those skilled in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented by electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution.

[0178] In the embodiments provided in the present application, it should be understood that the disclosed devices / network equipment and methods can be implemented in other ways. For example, the device / network equipment embodiments described above are merely schematic. For example, the division of the above modules or units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0179] The above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit them. Although the present application has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some of the technical features therein. These modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the embodiments of the present application, and should all be included in the protection scope of the present application.

Claims

1. A reconciliation method, characterized in that: The method comprises: Receive a first operation input by a user, where the first operation is used to trigger a reconciliation process for a target account period task; According to the first operation, first billing data and second billing data are obtained, wherein the first billing data is billing data of an e-commerce platform corresponding to the target billing period task, and the second billing data is billing data of a logistics platform corresponding to the target billing period task; Based on a first configuration rule, reconciliation processing is performed on the first billing data and the second billing data to obtain a reconciliation result of the target account period task, wherein the first configuration rule refers to a configuration rule for comparing specified data in the first billing data with specified data in the second billing data when performing reconciliation processing, the specified data in the first billing data is determined by a first calculation rule, which is a rule corresponding to the e-commerce platform, and the specified data in the second billing data is determined by a second calculation rule, which is a rule corresponding to the logistics platform, and the reconciliation result includes a first reconciliation result and / or a second reconciliation result, the first reconciliation result is the billing data corresponding to the waybill number, and the second reconciliation result is the billing data related to the fee.

2. The method according to claim 1, characterized in that The specified data in the first billing data is obtained by summing multiple data in the first billing data using a first calculation rule; and / or, the specified data in the second billing data is obtained by summing multiple data in the second billing data using the second calculation rule.

3. The method according to claim 2, characterized in that The first configuration rule also includes a first attribute setting rule, which is a rule corresponding to the e-commerce platform. The first attribute setting rule is used to configure the starting position and / or ending position of the specified data in the first bill data when performing data comparison.

4. The method according to claim 1, characterized in that The reconciliation processing of the first billing data and the second billing data based on the first configuration rule to obtain the reconciliation result of the target bill period task includes: Compare the first type of data in the first billing data with the first type of data in the second billing data to obtain a first reconciliation result, wherein the first type of data is waybill number data; The second category of data in the first billing data is compared with the second category of data in the second billing data to obtain a second reconciliation result, where the second category of data is expense item data.

5. The method according to claim 1, characterized in that Before reconciling the first bill data and the second bill data, the method further includes: Receive a first billing file uploaded by a user, and receive a second billing file uploaded by a user, wherein the first billing file is a billing file of an e-commerce platform corresponding to the target billing period task, and the second billing file is a billing file of a logistics platform corresponding to the target billing period task; Based on the first billing file, obtaining original billing data of the e-commerce platform, and based on the second billing file, obtaining original billing data of the logistics platform; The original billing data of the e-commerce platform is cleansed to obtain the first billing data, and the original billing data of the logistics platform is cleansed to obtain the second billing data.

6. The method according to claim 5, characterized in that Before performing data cleaning processing on the original bill data, the method further includes: Receive a second operation input by a user, where the second operation is used to trigger a space creation process; According to the second operation, a target space is created, where the target space is used to store the billing data of the e-commerce platform and the billing data of the logistics platform; In the target space, the target billing period task is created based on the first billing file and the second billing file, and the reconciliation method of the target billing period task includes reconciliation according to a preset time period.

7. The method according to claim 6, characterized in that The creating the target bill period task based on the first bill file and the second bill file includes: In the target space, the target billing period task is created based on the first billing file, the second billing file and the third billing file, wherein the third billing file includes historical difference data, which is difference data obtained by comparing the historical billing data of the e-commerce platform with the historical billing data of the logistics platform; The reconciliation processing of the first billing data and the second billing data based on the first configuration rule to obtain the reconciliation result of the target bill period task includes: Based on the first configuration rule, reconciliation processing is performed on the first billing data, the second billing data, and the historical difference data to obtain a reconciliation result of the target bill period task.

8. A reconciliation device, characterized in that: include: A receiving module, used to receive a first operation input by a user, where the first operation is used to trigger a reconciliation process for a target account period task; An acquisition module, according to the first operation, acquires first billing data and second billing data, wherein the first billing data is billing data of an e-commerce platform corresponding to the target billing period task, and the second billing data is billing data of a logistics platform corresponding to the target billing period task; A processing module is used to reconcile the first billing data and the second billing data based on a first configuration rule to obtain a reconciliation result of the target account period task, wherein the first configuration rule refers to a configuration rule for comparing specified data in the first billing data with specified data in the second billing data when performing reconciliation processing, the specified data in the first billing data is determined by a first calculation rule, the first calculation rule is a rule corresponding to the e-commerce platform, the specified data in the second billing data is determined by a second calculation rule, the second calculation rule is a rule corresponding to the logistics platform, the reconciliation result includes a first reconciliation result and / or a second reconciliation result, the first reconciliation result is the billing data corresponding to the waybill number, and the second reconciliation result is the billing data related to the fee.

9. A server comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the computer program, the method according to any one of claims 1 to 7 is implemented.

10. A readable storage medium, characterized in that: The readable storage medium stores a computer executable program or instructions, and the computer executable program or instructions are configured to execute the method according to any one of claims 1 to 7.

Images