Methods for processing invoice information, computer equipment, readable storage media and program products

Abstract

This application relates to a method, apparatus, computer equipment, readable storage medium, and program product for processing invoice information. It calculates the payment data of the paying entity for a logistics waybill based on its payment information. Based on the invoicing cycle of the paying entity, the payment data is saved to a corresponding data block. The payment data in the unified data block is then statistically analyzed to obtain the invoicing resource information of the paying entity, which is then sent to the invoicing service provider. Compared to the traditional method of processing electronic invoice information separately for each logistics waybill on each platform, this solution obtains the payment information of the logistics waybill, calculates the payment data of the paying entity based on the payment information, and integrates the payment status of waybills on different operating platforms. This data is then consolidated into a single data block according to the invoicing cycle, facilitating batch calculations to update the invoicing resource information in real time within each cycle, thereby improving the efficiency of electronic invoice information processing.

Description

Technical Field

[0001] This application relates to the field of data processing technology, and in particular to a method, apparatus, computer equipment, computer-readable storage medium, and computer program product for processing invoice information. Background Technology

[0002] With the development of e-commerce, the number of logistics waybills is gradually increasing, and the related documentation information is also growing. This large volume of documentation puts immense pressure on the servers responsible for generating documentation. Therefore, a data processing method for documentation information that can reduce server load is needed. Summary of the Invention

[0003] Therefore, it is necessary to provide a method, apparatus, computer equipment, computer-readable storage medium, and computer program product for processing invoice information that can improve processing efficiency in response to the above-mentioned technical problems.

[0004] Firstly, this application provides a method for processing bill information, the method comprising:

[0005] Obtain payment information for logistics waybills;

[0006] Based on the payment information, calculate the payment data of the payment entity corresponding to the logistics waybill;

[0007] Obtain the invoicing cycle of the payment entity and save the payment data to the data block corresponding to the invoicing cycle;

[0008] Based on the payment data in the data block, update the invoicing resource information of the payment entity within the invoicing period corresponding to the data block.

[0009] Secondly, this application provides a bill information processing apparatus, the apparatus comprising:

[0010] The acquisition module is used to obtain payment information for logistics waybills;

[0011] The calculation module is used to calculate the payment data of the payment entity corresponding to the logistics waybill based on the payment information;

[0012] The storage module is used to obtain the invoicing cycle of the payment entity and save the payment data to the data block corresponding to the invoicing cycle;

[0013] The processing module is used to update the invoicing resource information of the payment entity within the corresponding invoicing period of the data block based on the payment data in the data block.

[0014] Thirdly, this application provides a computer device, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the steps of the above-described method.

[0015] Fourthly, this application provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the steps of the above-described method.

[0016] Fifthly, this application provides a computer program product, including a computer program that, when executed by a processor, implements the steps of the above-described method.

[0017] The aforementioned method, apparatus, computer equipment, computer-readable storage medium, and computer program product for processing invoice information calculate the payment data of the payment entity corresponding to the logistics waybill based on the payment information, obtain the invoicing cycle of the payment entity, store the payment data belonging to the same invoicing cycle into the same data block, and update the invoicing resource information of the payment entity within the corresponding invoicing cycle of the data block based on the payment data in the data block. This solution obtains the payment information of the logistics waybill, calculates the payment data of the payment entity based on the payment information, and integrates the waybill payment status of the payment entity on different operating platforms. By integrating these payment data into the same data block according to the invoicing cycle, it facilitates batch calculation to update the invoicing resource information within each cycle in real time, thereby improving the efficiency of electronic invoice information processing. Attached Figure Description

[0018] To more clearly illustrate the technical solutions in the embodiments of this application or related technologies, the drawings used in the description of the embodiments of this application or related technologies will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other related drawings can be obtained based on these drawings without creative effort.

[0019] Figure 1 This is a flowchart illustrating a bill information processing method in one embodiment;

[0020] Figure 2 This is a structural block diagram of a bill information processing device in one embodiment;

[0021] Figure 3 This is an internal structural diagram of a computer device in one embodiment. Detailed Implementation

[0022] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application.

[0023] In related technologies, a small-scale database and microservice architecture are used to store and process invoice information. However, this architecture is insufficient in processing massive amounts of invoice information, resulting in low data processing efficiency.

[0024] In one embodiment, such as Figure 1 As shown, a method for processing invoice information is provided. This embodiment illustrates the application of this method to a server. It is understood that this method can also be applied to a terminal, or to a system including a terminal and a server, and is implemented through the interaction between the terminal and the server, including the following steps S202 to S208. Wherein:

[0025] Step S202: Obtain payment information for the logistics waybill.

[0026] When users purchase or return goods on e-commerce platforms, a logistics tracking number is generated. During the processing of the tracking number, the paying entity pays the logistics fees, creating payment information. This payment information may include data items such as payment time, payment amount, tracking number initiator's identifier, paying entity's identifier, and logistics tracking number. The paying entity is a participant in the logistics tracking process and can be a consumer, e-commerce platform, logistics platform, or third-party business platform, such as a third-party business platform providing shipping insurance services.

[0027] The payer of a logistics waybill needs to pay corresponding resources for that waybill. Each participant in the logistics waybill can then obtain corresponding electronic invoices for the resources they have paid. The server can obtain the payment information from the logistics waybill, and thus determine the electronic invoice information for each party based on that payment information.

[0028] The electronic invoice information processing system may include a data processing server, a microservice architecture, a message middleware, and a relational database. The message middleware is a high-throughput distributed publish-subscribe messaging system. It has multiple topics, or message distribution nodes, for processing logistics orders with different payment statuses. The server utilizes the message middleware for asynchronous message processing, improving system response speed and processing capacity. The server can leverage a microservice architecture to achieve high availability and scalability. Furthermore, the server can achieve encrypted and secure communication through HTTPS (Hypertext Transfer Protocol Secure) combined with RSA (Rivest-Shamir-Adleman) encryption and salting technology, ensuring data transmission security. The relational database can be a distributed relational database, allowing the server to store summary results, business processing payment information, payment data, and invoicing resource information, ensuring data consistency and reliability. The payment information for the aforementioned logistics orders can be stored in different topics within the message middleware.

[0029] In one embodiment, a bill information processing method further includes: obtaining payment information of a logistics waybill, determining the payment status corresponding to the logistics waybill, and inputting the logistics waybill into a message middleware with the topic corresponding to the payment status.

[0030] In this embodiment, the server can obtain payment information for logistics waybills from multiple e-commerce platforms. Logistics waybills can have various payment statuses, including but not limited to successful payment, successful refund, and settlement. The server can obtain the payment status corresponding to the logistics waybill. For example, the server can search within a preset location corresponding to the payment status in the payment information to obtain the payment status of the logistics waybill.

[0031] Payment information for different payment statuses can be stored in different topics within the message middleware. E-commerce platforms can send payment information to these topics on the server according to the payment status of the logistics waybill. The server can then retrieve payment information for a specific payment status from the topics within the message middleware.

[0032] In one embodiment, the server can preprocess the payment information to remove payment information that does not meet the requirements. Logistics waybills with different payment statuses can reside in message middleware with different themes. The server can retrieve the original payment information corresponding to the logistics waybill from the theme corresponding to the message middleware based on the payment status of the logistics waybill. The original payment information represents unprocessed payment information. The server can retrieve duplicate payment information from the original payment information. Specifically, the server can detect whether duplicate records exist in the original payment information based on information similarity. If duplicate records are detected, duplicate payment information is determined to exist. The server can remove the duplicate payment information from the original payment information and obtain the payment information corresponding to the logistics waybill based on the original payment information after removing duplicate payment information.

[0033] Specifically, after retrieving the original payment information from the corresponding topic in the message middleware, the server can clean the original payment information on the data processing server platform to eliminate duplicate records, thereby obtaining the aforementioned payment information. This payment information represents details such as the value of resources that each participant needs to pay during the completion of the logistics order.

[0034] The payment status of the aforementioned logistics waybills can include multiple categories. Specifically, these can include payment success, refund success, and settlement. Payment success indicates that the payment information for the logistics waybill has been completed, i.e., a logistics waybill where the user has paid for the corresponding resources; refund indicates a logistics waybill where a transaction has been reversed, such as a logistics waybill where the user has retrieved the corresponding resources; settlement indicates a logistics waybill where the resources have been cleared, such as a logistics waybill where the e-commerce platform has finally acquired the resources. For different payment statuses, the server can pass the payment information from the logistics waybill into different topics in the message middleware.

[0035] For example, a server can retrieve pending logistics waybills. The aforementioned payment information and settlement details can be stored within these waybills. The server can analyze the payment status to determine the subject corresponding to the payment information.

[0036] If the server detects that the payment status is successful, it can input the payment information into a first topic. The first topic can be a payment topic in the message broker. If the server detects that the payment status is successful (refund successful), it can input the payment information into a second topic. The second topic can be a refund topic in the message broker. If the server detects that the payment status is settled, it can input the payment information into a third topic. The third topic can be a settlement topic in the message broker.

[0037] Specifically, the server can receive payment result notifications from e-commerce platform logistics (i.e., the aforementioned payment information) via HTTPS service in cloud microservices, and use RSA salting encryption for secure communication to ensure the security of information transmission. RSA salting encryption refers to the technique of adding a random "salt value" to enhance security when using the RSA algorithm for encryption. Thus, by combining RSA encryption and randomization techniques, the server makes the encrypted result more difficult for attackers to crack. The server can then categorize payment information into different topics in the message middleware, such as payment, refund, and settlement, achieving information classification and processing. When processing information for a specific logistics order, the server can directly retrieve the corresponding payment information from the relevant topic and determine the payment entity for the logistics order, thereby improving information retrieval efficiency.

[0038] Step S204: Based on the above payment information, calculate the payment data of the payment entity corresponding to the logistics waybill.

[0039] The server, after obtaining payment information from the topic corresponding to the payment status in the message middleware, can determine the payment amount for each payment entity in each logistics order based on this information, thus creating individual payment data. These payment entities represent the various participants in the logistics order, such as users, e-commerce platforms, and service providers. During the execution of a logistics order, each payment entity needs to pay corresponding resources to other parties, resulting in individual payment data for each entity. The server can then retrieve the payment amount for each payment entity as its payment data.

[0040] Step S206: Obtain the invoicing cycle of the payment entity and store the payment data belonging to the same invoicing cycle into the same data block.

[0041] The aforementioned invoicing period can be the processing period for electronic invoice information corresponding to each payment entity. Within this period, the server needs to determine the electronic invoice information of the payment entity corresponding to that period. Each invoicing period corresponds one-to-one with a payment entity. When determining the electronic invoice information, the server can obtain the payment entity's invoicing period and, based on that period, save the payment data to the corresponding data block. The invoicing period can be determined based on a pre-configured invoicing period configuration table. This table includes each payment entity's identifier and corresponding invoicing period. For different invoicing periods, the server can partition and store the payment data of payment entities for different invoicing periods; for example, the server can store the payment data in the data block corresponding to the invoicing period.

[0042] Logistics waybills with different payment statuses can be processed by different topics in the message middleware, and the server can retrieve the corresponding payment information from the respective topics. The server can store payment data into data blocks corresponding to each invoicing cycle using streaming processing. The server can consume logistics waybills with the corresponding payment status from the corresponding topics and retrieve the corresponding payment data. The server can stream and store the retrieved payment data to achieve parallel storage and processing.

[0043] The server can stream and store the payment data for the aforementioned payment topics, for example, into the data block corresponding to the invoicing cycle. Based on the address endpoint of the payment data, the server determines the starting address of new payment data within the data block. The server then returns the steps of consuming the corresponding payment status of the logistics waybill from the corresponding topic to obtain the corresponding payment data, proceeding to obtain the next payment data until the server has obtained all the payment data for the logistics waybill and all payment data has been stored. At this point, the server stops retrieving data from the message queue. Thus, the server can obtain the payment information corresponding to the logistics waybill based on the stored payment data. For example, the server can combine the payment data of various resources to obtain the payment information corresponding to the logistics waybill.

[0044] Specifically, the server can consume payment results and settlement notifications (i.e., payment information) from various topics corresponding to the logistics waybills in the aforementioned message middleware, and perform streaming storage during the consumption process to ensure real-time data processing and storage. The server's consumption of payment information from the message middleware involves reading and processing messages from the topics within the message middleware. Streaming storage refers to writing data to the storage medium gradually in a streaming manner during data processing or transmission, rather than writing it all at once; it is a segmented storage technology. Therefore, the server can read payment information for logistics waybills with corresponding payment statuses from the corresponding topics based on streaming storage, and then process electronic invoice information based on this payment information, improving the efficiency of processing electronic invoice information.

[0045] Step S208: Based on the payment data in the above data block, update the invoicing resource information of the payment entity in the invoicing period corresponding to the above data block.

[0046] Among them, the invoicing resource information represents the invoicing resources required to issue electronic invoices. When the invoicing resources of each payment entity change during the execution of the logistics waybill, each payment entity can obtain the corresponding electronic invoices for its changed invoicing resources. The invoicing resources can be the invoicable amount or the invoicable quantity.

[0047] Each payment entity in the aforementioned logistics waybill has a corresponding invoicing cycle. The server can obtain each invoicing cycle corresponding to each payment entity. Therefore, the server can statistically analyze the payment data corresponding to each payment entity within the data block corresponding to the invoicing cycle, and determine the invoicing resource information corresponding to each payment entity. That is, for each payment entity, the server can determine the invoicing resource information corresponding to that entity within its specified invoicing cycle, based on the payment data corresponding to that payment entity in the same data block. Here, payment data represents the payment amount paid by the entity when executing the logistics waybill business. The server can determine the invoicing resource information by statistically analyzing the payment data corresponding to each payment entity in the same data block. The aforementioned execution entities can include multiple entities, and the server can separately statistically analyze the payment data in the data block corresponding to each execution entity.

[0048] After determining the payment data corresponding to each executing entity, the server can further determine invoicing resource information based on the payment data. For example, the server can calculate the payment amount in the first data block of the invoicing period corresponding to the business initiator as the first invoicing resource information. The first invoicing resource information can be the total value of payment amounts in the first data block whose payment status is "paid".

[0049] The server can calculate the payment amount corresponding to the second payment data within the second data block of the second invoicing cycle corresponding to the business recipient, and determine the second invoicing resource information corresponding to the business recipient. The second invoicing resource information can be the total value of payment amounts in the second payment data whose payment status is "paid".

[0050] The server can also statistically analyze third-party payment data within the third data block of the third invoicing cycle corresponding to the business guarantor, thereby determining the third-party invoicing resource information corresponding to the business guarantor. This third-party invoicing resource information can be the total amount of payments with a payment status of "paid" in the third payment data. Thus, based on the invoicing cycle corresponding to each payment entity, the server can statistically analyze the payment data corresponding to each payment entity within the corresponding data block, determining the invoicing resource information for each entity. The server then uses this statistically analyzed invoicing resource information to generate electronic invoice information, enabling unified batch invoicing processing of payment data from multiple platforms for payment entities, thus improving the processing efficiency of electronic invoice information.

[0051] In the aforementioned method for processing invoice information, based on the payment information, the payment data of the payment entity corresponding to the logistics waybill is calculated, the invoicing cycle of the payment entity is obtained, and payment data belonging to the same invoicing cycle is stored in the same data block. Based on the payment data in the data block, the invoicing resource information of the payment entity within the corresponding invoicing cycle of the data block is updated. Compared to the traditional method of processing electronic invoice information separately for each logistics waybill on each platform, this solution obtains the payment information of the logistics waybill, calculates the payment data of the payment entity based on the payment information, and integrates the waybill payment status of the payment entity on different operating platforms. This data is then integrated into the same data block according to the invoicing cycle, facilitating batch calculations to update the invoicing resource information within each cycle in real time, thereby improving the efficiency of electronic invoice information processing.

[0052] In one embodiment, calculating the payment data of the payment entity corresponding to the logistics waybill based on the payment information includes:

[0053] The payment status of the aforementioned payment information is obtained, and the aforementioned payment status is associated with a message distribution node; the aforementioned message distribution node is associated with a payment information processing method.

[0054] Send the above payment information to the message distribution node corresponding to the above payment status;

[0055] The payment information is obtained from the aforementioned message distribution nodes, and the payment data of the payment entity corresponding to the aforementioned logistics waybill is calculated using the payment information processing method corresponding to the aforementioned message distribution nodes.

[0056] In this embodiment, the message distribution node can be a topic in the message middleware, and each topic corresponds to a payment status. Logistics waybill payment information has multiple payment statuses, including but not limited to payment success, refund success, and settlement. The server can obtain the payment status corresponding to the logistics waybill payment information. For example, the server can search in a preset position corresponding to the payment status in the logistics waybill payment information to obtain the corresponding payment status, and then receive the logistics waybill from the e-commerce platform via the Hypertext Transfer Protocol Service (HTTP) and input it into different topics in the message middleware according to the payment status. The message distribution node and the payment information processing method are correlated. For example, for payment information obtained from the payment success topic, the payment amount is accumulated as payment data; or, only the payment information in the settlement success topic is obtained to calculate the payment amount as payment data; or, if there is duplicate payment information in the payment success topic, the payment information obtained from the message distribution node is cleaned to delete duplicate payment information.

[0057] In this embodiment, by storing payment information according to payment status in different topics of the message middleware, the payment information can be classified and processed, which also facilitates asynchronous processing of the payment information and improves the utilization of computing resources.

[0058] In one embodiment, the aforementioned payment information is cleaned to remove duplicate payment information, thereby improving the accuracy of payment information processing.

[0059] In one embodiment, the payment amount is split according to the relationship between the payment amount in the payment information and the payment entity to obtain the payment data of the payment entity.

[0060] Specifically, after the data is cleaned, the payment information is split into three payment amounts: logistics-consumer, logistics-merchant, and logistics-insurance company, which are then used as payment data.

[0061] In one embodiment, based on the aforementioned payment information, calculating the payment data of the payment entity corresponding to the logistics waybill includes: obtaining the entity identifiers corresponding to each payment entity; querying payment information based on each entity identifier to obtain the payment values ​​corresponding to each entity identifier; and obtaining the payment data based on the payment values ​​corresponding to each entity identifier.

[0062] In this embodiment, the payment entities participating in the logistics waybill include multiple entities. These may include, for example, a business initiator, a business recipient, and a business guarantor. The business initiator can be a user purchasing goods from an e-commerce platform, i.e., the user initiates the logistics waybill; the business recipient can be the e-commerce platform; and the business guarantor can be a platform outside the user and e-commerce platform used to ensure the normal execution of the logistics waybill. Different payment entities can have different payment data. The server can obtain the entity identifiers corresponding to each payment entity, query payment information based on each entity identifier, obtain the payment values ​​corresponding to each entity identifier, and then obtain the payment data based on the payment values ​​corresponding to each entity identifier. The payment value for each payment entity can be different. The aforementioned payment entities can include various types, such as business initiators, business recipients, and guarantors.

[0063] After obtaining the aforementioned payment information, the server can retrieve the first identifier corresponding to the business initiator and determine the first payment value corresponding to the first identifier from the payment information as the first payment data. The first identifier can be the name or number of the business initiator, and the first payment data represents the value of the resources paid by the business initiator.

[0064] For the service recipient, the server can obtain the second identifier corresponding to the service recipient and determine the second payment value corresponding to the second identifier from the payment information as the second payment data. Here, the second identifier can be an identifier such as the name or number of the service recipient, and the second payment data represents the value of the resources paid for by the service recipient.

[0065] For the service provider, the server can obtain the third identifier corresponding to the service recipient and determine the third payment value corresponding to the third identifier from the payment information as the third payment data. The third identifier can be the service provider's name or number, etc., and the third payment data represents the value of the resources paid by the service provider.

[0066] In other words, after the server cleans the original payment information and removes duplicate records, it can break down the payment information into the actual payment data corresponding to the business initiator, business recipient and business guarantor of the logistics waybill. The server then partitions and stores each payment data according to the invoicing cycle. For example, the payment data corresponding to the invoicing cycle that is closer to the current time is stored first, thereby improving the efficiency and accuracy of data processing.

[0067] In this embodiment, the server can determine the payment data corresponding to each payment entity from the payment information according to the identifier of each payment entity in the logistics waybill, thereby eliminating the need for the server to separately filter the payment data of each payment entity and improving the efficiency of payment data acquisition.

[0068] In one embodiment, obtaining the invoicing cycle of a payment entity includes: querying each invoicing cycle configuration table based on the entity identifier corresponding to the payment entity; the invoicing cycle configuration table includes each entity identifier of each payment entity with the same invoicing cycle; if the entity identifier exists in the target invoicing cycle configuration table, obtaining the invoicing cycle corresponding to the payment entity based on the invoicing cycle corresponding to the target invoicing cycle configuration table.

[0069] In this embodiment, the server can pre-generate corresponding invoicing cycle configuration tables according to the invoicing cycles of each payment entity. There can be multiple invoicing cycle configuration tables, each including the entity identifiers of each payment entity with the same invoicing cycle. The server can determine invoicing resource information based on the invoicing cycle. Therefore, the server can query each invoicing cycle configuration table based on the entity identifiers corresponding to the aforementioned payment entities to determine whether the entity identifiers corresponding to the aforementioned payment entities exist in the invoicing cycle configuration tables.

[0070] If the server detects that the aforementioned subject identifier exists in the target invoicing cycle configuration table, the server can determine that the invoicing cycle of the executing subject corresponding to the aforementioned subject identifier is the invoicing cycle corresponding to the aforementioned target invoicing cycle configuration table.

[0071] In this embodiment, the server generates an invoice cycle configuration table in advance based on each entity identifier for each invoice cycle. When processing electronic invoice information, the server can quickly find the invoice cycle corresponding to the payment entity based on the invoice cycle configuration table, and then store payment data based on the invoice cycle. This facilitates rapid statistical data collection when generating electronic invoices and improves information processing efficiency.

[0072] In one embodiment, a bill information processing method further includes: sending billing resource information to the billing service provider.

[0073] Specifically, the server can initiate batch calculations on the data processing server platform to collect invoicing resource information for each payment entity based on the aforementioned invoicing cycle, thereby generating corresponding electronic invoice information using the invoicing resource information. The aforementioned invoicing resource information can also be determined in conjunction with the invoicing cycle and payment status; the server can generate electronic invoice information for invoicing resource information with already paid payment status.

[0074] In one embodiment, a bill information processing method further includes:

[0075] Get updated information on invoicing resources;

[0076] Based on the above invoicing resource information and the above invoicing resource update information, an electronic invoice is generated.

[0077] The invoicing resource update information represents the change in the invoicing resources of the paying entity after the execution of the target logistics waybill. Specifically, the target paying entity identifier, target invoicing resource information, and invoicing resource update information can be entered into a preset electronic invoice template to obtain an electronic invoice. Alternatively, if the invoicing resource update information is not greater than the target invoicing resource information, the invoicing resource update information can be entered into a preset electronic invoice template to obtain an electronic invoice.

[0078] This embodiment generates electronic invoices based on invoicing resource information and invoicing resource update information, thereby improving the automation level of electronic invoice generation for logistics waybills and thus improving the efficiency of electronic invoice generation.

[0079] In one embodiment, generating an electronic invoice based on the aforementioned invoicing resource information and the aforementioned invoicing resource update information includes:

[0080] A distributed lock is added to the above-mentioned invoicing resource information. Based on the updated invoicing resource information, resources are deducted from the above-mentioned invoicing resource information to obtain the deduction result. The distributed lock is then released. Based on the updated invoicing resource information, an electronic invoice is generated.

[0081] The invoicing resource information can be stored in a distributed database. After the distributed database determines the updated invoicing resource information based on the logistics waybill, it can add a distributed lock to the invoicing resource in the distributed database according to the updated invoicing resource information, and perform resource deduction and electronic invoice generation based on the distributed lock.

[0082] In this embodiment, resource deduction is performed on invoicing resources based on distributed locks. After successful deduction, electronic invoices are generated. This ensures that only one operation is allowed on invoicing resources at the same time during the electronic invoice generation process, thus guaranteeing the consistency of invoicing resources.

[0083] In one exemplary embodiment, the server can receive payment result notifications from e-commerce platform logistics via HTTPS service in cloud microservices, such as obtaining the aforementioned payment information. The server can use RSA salting for secure communication to ensure the security of information transmission. The server can categorize the payment result information into different topics in the message middleware according to payment, refund, settlement, etc., to achieve information classification and processing.

[0084] The server can consume payment results and settlement notifications from the e-commerce platform's logistics via the message middleware, i.e., consume the aforementioned payment information and stream it to ensure real-time data processing and storage. This allows the server to confirm the payment data.

[0085] Specifically, the server can clean payment results on the data processing server platform, eliminate duplicate records, and split the data into individual payment data corresponding to each entity in the logistics waybill, storing it in partitions according to the invoicing cycle to improve the efficiency and accuracy of data processing. The server can initiate batch calculations on the data processing server platform, determining the invoicing resource information for each entity within the corresponding data block based on the payment status of each payment data in each invoicing cycle, and utilizing big data processing technology to improve computational efficiency. The server can also push down the invoicing resource information and electronic invoice information corresponding to each entity in the logistics waybill to a relational database to ensure data consistency and queryability.

[0086] Specifically, the electronic invoice information processing system is configured with a microservice architecture, a consumption middleware, a data processing server, and a relational database. It can receive payment result notifications from e-commerce platforms via cloud microservices, such as retrieving the aforementioned payment information. It can also send payment information to e-commerce platforms via the cloud microservice architecture, employing RSA salting for secure communication to ensure data transmission security. The server can push payment information into different topics within the consumption middleware according to payment status. The server then utilizes the payment information from the corresponding topic in the consumption message middleware, performing streaming storage, data cleaning, and duplicate record removal. The data processing server performs data splitting, determining the payment data corresponding to each executing entity, and storing it in partitions according to the invoicing cycle. The data processing server initiates batch calculations, determining the invoicing resource information corresponding to each executing entity according to the invoicing cycle, and pushes the invoicing resource information and electronic invoice information corresponding to each executing entity in the logistics waybill down to the relational database to ensure data consistency and queryability.

[0087] Through the above embodiments, the server obtains payment information from logistics waybills, calculates payment data for the paying entity based on this information, and integrates the payment status of waybills from different operating platforms. This data is then consolidated into a single data block according to the invoicing cycle, facilitating batch calculations to update invoicing resource information in real time within each cycle, thereby improving the efficiency of electronic invoice information processing. Furthermore, the server combines a data processing server, microservice architecture, message middleware, and relational database to achieve efficient storage, cleaning, and calculation of large amounts of payment information. This enables accurate and timely calculation of payment details and user invoicing resource information from e-commerce platforms, while ensuring the security and accuracy of the electronic invoice generation process. It economically and accurately calculates large amounts of payment details and user invoicing resource information from e-commerce platforms, ensuring that various paying entities on the e-commerce platform can generate electronic invoice information through logistics platform applications or self-service generation on the e-commerce platform.

[0088] It should be understood that although the steps in the flowcharts of the above embodiments are shown sequentially according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some steps in the flowcharts of the above embodiments may include multiple steps or multiple stages. These steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these steps or stages is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the steps or stages of other steps.

[0089] Based on the same inventive concept, this application also provides a bill information processing apparatus for implementing the bill information processing method described above. The solution provided by this apparatus is similar to the implementation scheme described in the above method; therefore, the specific limitations in one or more embodiments of the bill information processing apparatus provided below can be found in the limitations of the bill information processing method described above, and will not be repeated here.

[0090] In one exemplary embodiment, such as Figure 2 As shown, a ticket information processing device is provided, including: an acquisition module 500, a calculation module 502, a storage module 504, and a processing module 506, wherein:

[0091] The acquisition module 500 is used to obtain payment information for logistics waybills.

[0092] The calculation module 502 is used to calculate the payment data of the payment entity corresponding to the logistics waybill based on the above payment information.

[0093] The storage module 504 is used to calculate the payment data of the payment entity corresponding to the logistics waybill based on the above payment information.

[0094] Processing module 506 is used to update the invoicing resource information of the payment entity in the corresponding invoicing period of the above data block based on the payment data in the above data block.

[0095] Each module in the aforementioned invoice information processing device can be implemented entirely or partially through software, hardware, or a combination thereof. These modules can be embedded in or independent of the processor in a computer device, or stored in the memory of a computer device as software, so that the processor can call and execute the operations corresponding to each module.

[0096] In one exemplary embodiment, a computer device is provided, which may be a server, and its internal structure diagram may be as follows: Figure 3As shown, this computer device includes a processor, memory, input / output (I / O) interfaces, and a communication interface. The processor, memory, and I / O interfaces are connected via a system bus, and the communication interface is also connected to the system bus via the I / O interfaces. The processor provides computational and control capabilities. The memory includes non-volatile storage media and internal memory. The non-volatile storage media stores the operating system, computer programs, and a database. The internal memory provides the environment for the operation of the operating system and computer programs stored in the non-volatile storage media. The database stores electronic ticket information. The I / O interfaces are used for exchanging information between the processor and external devices. The communication interface is used for communicating with external terminals via a network connection. When the computer program is executed by the processor, it implements a ticket information processing method.

[0097] Those skilled in the art will understand that Figure 3 The structure shown is merely a block diagram of a portion of the structure related to the present application and does not constitute a limitation on the computer device to which the present application is applied. Specific computer devices may include more or fewer components than those shown in the figure, or combine certain components, or have different component arrangements.

[0098] In one exemplary embodiment, a computer device is provided, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the above-described method for processing ticket information.

[0099] In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored, which, when executed by a processor, implements the above-described method for processing invoice information.

[0100] In one embodiment, a computer program product is provided, including a computer program that, when executed by a processor, implements the above-described invoice information processing method.

[0101] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, data stored, data displayed, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of the relevant data must comply with relevant regulations.

[0102] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium, and when executed, it can include the processes of the embodiments of the above methods. Any references to memory, databases, or other media used in the embodiments provided in this application can include at least one of non-volatile memory and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. By way of illustration and not limitation, RAM can take many forms, such as Static Random Access Memory (SRAM) or Dynamic Random Access Memory (DRAM). The databases involved in the embodiments provided in this application may include at least one type of relational database and non-relational database. Non-relational databases may include, but are not limited to, blockchain-based distributed databases. The processors involved in the embodiments provided in this application may be general-purpose processors, central processing units, graphics processing units, digital signal processors, programmable logic devices, quantum computing-based data processing logic devices, artificial intelligence (AI) processors, etc., and are not limited to these.

[0103] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this application.

[0104] The embodiments described above are merely illustrative of several implementation methods of this application, and while the descriptions are specific and detailed, they should not be construed as limiting the scope of this patent application. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of this application, and these all fall within the protection scope of this application. Therefore, the protection scope of this application should be determined by the appended claims.

Claims

1. A method for processing invoice information, characterized in that, The method includes: Obtain payment information for logistics waybills; Based on the payment information, calculate the payment data of the payment entity corresponding to the logistics waybill; Obtain the invoicing cycle of the payment entity and store payment data belonging to the same invoicing cycle into the same data block; Based on the payment data in the data block, update the invoicing resource information of the payment entity within the invoicing period corresponding to the data block.

2. The method according to claim 1, characterized in that, The step of calculating the payment data of the payment entity corresponding to the logistics waybill based on the payment information includes: The payment status of the payment information is obtained, and the payment status is associated with a message distribution node; the message distribution node is associated with a payment information processing method. Send the payment information to the message distribution node corresponding to the payment status; The payment information is obtained from the message distribution node, and the payment data of the payment subject corresponding to the logistics waybill is calculated through the payment information processing method corresponding to the message distribution node.

3. The method according to claim 2, characterized in that, After obtaining the payment information from the message distribution node, the method further includes: The payment information is cleaned to remove duplicate payment information.

4. The method according to claim 1, characterized in that, The step of calculating the payment data of the payment entity corresponding to the logistics waybill based on the payment information includes: Based on the relationship between the payment amount and the payment entity in the payment information, the payment amount is split to obtain the payment data of the payment entity.

5. The method according to claim 1, characterized in that, The process of obtaining the invoicing cycle of the payment entity includes: Based on the entity identifier corresponding to the payment entity, query the configuration table for each invoice cycle; the configuration table for each invoice cycle includes the entity identifiers of each payment entity with the same invoice cycle; If the entity identifier exists in the target invoicing cycle configuration table, the invoicing cycle corresponding to the payment entity is obtained according to the invoicing cycle corresponding to the target invoicing cycle configuration table.

6. The method according to claim 1, characterized in that, Also includes: Get updated information on invoicing resources; An electronic invoice is generated based on the invoicing resource information and the invoicing resource update information.

7. The method according to claim 6, characterized in that, The step of generating electronic invoices based on the invoicing resource information and the invoicing resource update information includes: A distributed lock is added to the invoicing resource information, and resource deduction is performed on the invoicing resource information based on the updated invoicing resource information to obtain the deduction result; Release the distributed lock; Based on the updated invoicing resource information, an electronic invoice is generated.

8. A computer device comprising a memory and a processor, wherein the memory stores a computer program, characterized in that, When the processor executes the computer program, it implements the steps of the method according to any one of claims 1 to 7.

9. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 7.

10. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 7.

Images