Method and corresponding device for the automated processing of bills and invoices

Abstract

The application provides an automatic processing method and corresponding device for bills and invoices. The method receives encrypted order information sent by a business travel platform through an API integration platform; after obtaining order information of different customers, corresponding contract information in the order information of different customers is extracted, and a contract account database is synchronized; the extraction bill date and the reconciliation date of any customer stored in advance are extracted; if it is detected that the extraction bill date of the customer is the current day, the bill of the customer is generated; if no abnormal bill data of the bill is found, the bill is automatically pushed to the customer on the reconciliation date; according to the contract information corresponding to the bill and the stored historical invoicing data, the invoice type of the bill and the invoice header and receiving information corresponding to the customer are determined; and after receiving the invoicing application, the invoicing process is processed. The method improves the efficiency, accuracy and customer experience of financial management.

Description

Technical Field

[0001] The present application relates to the field of financial management technology, and in particular to a method and corresponding device for automated processing of bills and invoices. Background Art

[0002] In traditional corporate financial management, billing and invoice processing is a complex and time-consuming task. Companies often have to manually manage billing with suppliers, including determining bill dates, generating bills, verifying bill details, adjusting for unusual data, and applying for and processing invoices. These processes are not only inefficient but also prone to errors, especially when dealing with multiple suppliers and a large number of transactions. Furthermore, the lack of automated tools often makes it difficult for companies to reconcile and issue invoices in a timely and accurate manner, leading to inefficient financial management. Summary of the Invention

[0003] The purpose of the embodiments of the present application is to provide a method and corresponding device for automated processing of bills and invoices to improve the efficiency, accuracy and customer experience of financial management.

[0004] In a first aspect, a method for automated processing of bills and invoices is provided, which is applied to a cost control platform in an enterprise billing system, wherein the enterprise billing system also includes a business travel platform and an API integration platform. The method may include:

[0005] The API integration platform receives encrypted order information sent by the business travel platform. The encrypted order information is encrypted using a preset encryption protocol pre-negotiated between the cost control platform and the business travel platform. The API integration platform includes data queues corresponding to multiple interfaces.

[0006] After obtaining the order information of different customers corresponding to the encrypted order information, extract the corresponding contract information in the order information of different customers and synchronize it with the contract ledger database;

[0007] For any customer, retrieve the pre-stored billing date and reconciliation date for that customer; if it is detected that the billing date for that customer is the current day, generate a bill for that customer; query the bill based on the customer's order information; if no abnormal billing data is found, automatically push the bill to the customer on the reconciliation date;

[0008] Based on the contract information corresponding to the bill and the stored historical invoicing data, the invoice type and the invoice header and receipt information corresponding to the customer are determined. The invoice header and receipt information corresponding to the customer are obtained by automatically synchronizing the invoice header and receipt information in the supplier account with the cost control platform through the API integration platform.

[0009] After receiving the encrypted invoicing application sent by the business travel platform through the API integration platform, obtain the plaintext invoicing application and process the invoicing process based on the customer's legal entity and invoice header.

[0010] In a possible implementation, the preset encryption protocol is the SSL encryption protocol or the TLS encryption protocol.

[0011] In one possible implementation, the method further includes:

[0012] If abnormal billing data is found, a bill adjustment request is sent to the staff to receive the adjusted data. The data to be adjusted and the adjusted data are managed through the message queue.

[0013] After all the data to be adjusted are adjusted, the bill adjustment application status is updated to the adjusted application status.

[0014] In one possible implementation, updating the bill adjustment application status to an adjusted application status, the method further includes:

[0015] Generate a bill adjustment log, which includes bill data before the bill adjustment, bill data after the bill adjustment, and corresponding adjustment status.

[0016] In one possible implementation, the method further includes:

[0017] The API integration platform collects reimbursement details corresponding to the consumption services of corporate employees on third-party consumption platforms in real time, generates monthly bills on the configured bill extraction day each month, and pushes the monthly bills to the corresponding corporate employees on the natural day after the bill extraction.

[0018] In one possible implementation, the method further includes:

[0019] At preset time intervals, use API contract testing tools (such as Swagger, Postman) to test the API interface of the API integration platform;

[0020] If the detection result is that the interface is abnormal, the data processing and data transmission of the data queue corresponding to the abnormal interface will be stopped and an alarm message will be generated.

[0021] In a second aspect, a device for automatically processing bills and invoices is provided, which is applied to a cost control platform in an enterprise billing system, wherein the enterprise billing system also includes a business travel platform and an API integration platform. The device may include:

[0022] A receiving unit is configured to receive encrypted order information sent by the business travel platform through the API integration platform. The encrypted order information is obtained by encrypting order information of different customers using a preset encryption protocol pre-negotiated between the fee control platform and the business travel platform. The API integration platform includes data queues corresponding to multiple interfaces.

[0023] An extraction unit is configured to, after obtaining the order information of different customers corresponding to the encrypted order information, extract the corresponding contract information from the order information of different customers and synchronize it with the contract ledger database; for any customer, extract the pre-stored withdrawal billing date and reconciliation date of the customer;

[0024] A generating unit is configured to generate a bill for the customer if it is detected that the billing date for the customer is the current day; query the bill based on the customer's order information, and automatically push the bill to the customer on the reconciliation date if no abnormal billing data is found;

[0025] The determination unit is configured to determine the invoice type of the bill and the invoice header and receipt information corresponding to the customer based on the contract information corresponding to the bill and the stored historical invoicing data. The invoice header and receipt information corresponding to the customer are obtained by automatically synchronizing the invoice header and receipt information in the supplier account with the cost control platform through the API integration platform.

[0026] The acquisition unit is used to obtain the plain text invoicing application after receiving the encrypted invoicing application sent by the business travel platform through the API integration platform, and perform invoicing process processing on the invoice header, receipt information and bill content of the bill.

[0027] In a possible implementation, the preset encryption protocol is the SSL encryption protocol or the TLS encryption protocol.

[0028] In a third aspect, an electronic device is provided, the electronic device including a processor, a communication interface, a memory, and a communication bus, wherein the processor, the communication interface, and the memory communicate with each other via the communication bus;

[0029] Memory for storing computer programs;

[0030] The processor is configured to implement any of the method steps described in the first aspect when executing a program stored in the memory.

[0031] In a fourth aspect, a computer-readable storage medium is provided, wherein a computer program is stored in the computer-readable storage medium, and when the computer program is executed by a processor, any of the method steps described in the first aspect is implemented.

[0032] The automated processing method for bills and invoices provided in this application receives encrypted order information sent by the business travel platform through the API integration platform. The encrypted order information is obtained by encrypting the order information of different customers using a preset encryption protocol pre-negotiated by the cost control platform and the business travel platform; the API integration platform includes data queues corresponding to multiple interfaces; after obtaining the order information of different customers corresponding to the encrypted order information, the corresponding contract information in the order information of different customers is extracted and synchronized with the contract ledger database; for any customer, the pre-stored billing date and reconciliation date of the customer are extracted; if it is detected that the billing date of the customer is the current day, the bill for the customer is generated; based on the customer's The system then queries the bill based on the order information. If no abnormal billing data is found, the bill is automatically pushed to the customer on the reconciliation date. Based on the contract information corresponding to the bill and the stored historical invoicing data, the invoice type and the invoice header and receipt information corresponding to the customer are determined. The invoice header and receipt information corresponding to the customer are obtained by automating the data synchronization between the invoice header and receipt information in the supplier account and the expense control platform through the API integration platform. After receiving the encrypted invoicing application sent by the business travel platform through the API integration platform, the plaintext invoicing application is obtained and, based on the customer's legal entity and invoice header, the invoicing process is performed on the receipt information and the billing content of the bill. This method improves the efficiency, accuracy and customer experience of financial management. BRIEF DESCRIPTION OF THE DRAWINGS

[0033] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the following is a brief introduction to the drawings required for use in the embodiments of the present application. It should be understood that the following drawings only show certain embodiments of the present application and therefore should not be regarded as limiting the scope. For ordinary technicians in this field, other relevant drawings can be obtained based on these drawings without creative work.

[0034] Figure 1 A schematic diagram of the structure of an enterprise billing system provided in an embodiment of the present application;

[0035] Figure 2 A flowchart of a method for automated bill and invoice processing provided in an embodiment of the present application;

[0036] Figure 3 A schematic diagram of the structure of an automated bill and invoice processing device provided in an embodiment of the present application;

[0037] Figure 4 A schematic diagram of the structure of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0038] The following, in conjunction with the accompanying drawings, provides a clear and complete description of the technical solutions in the embodiments of this application. Obviously, the described embodiments represent only a portion of the embodiments of this application and do not constitute a complete set of embodiments. All other embodiments derived by persons of ordinary skill in the art based on the embodiments of this application without inventive effort are intended to fall within the scope of protection of this application. Unless otherwise defined, technical or scientific terms used in this application should have the same ordinary meanings as those understood by persons of ordinary skill in the art. The terms "first," "second," and similar expressions used in this application do not denote any order, quantity, or importance; they are merely used to distinguish between different components. Terms such as "include" or "comprising" mean that the element or object preceding the term includes the elements or objects listed after the term, and their equivalents, without excluding other elements or objects. Terms such as "connect," "couple," or "connected" are not limited to physical or mechanical connections but may include electrical connections, whether direct or indirect. Terms such as "upper," "lower," "left," and "right" are used solely to indicate relative positional relationships. When the absolute position of the described objects changes, the relative positional relationships may also change accordingly.

[0039] The automated bill and invoice processing method provided in the embodiment of the present application can be applied to Figure 1 In the corporate billing system shown in Figure 1 As shown, the enterprise billing system can include: a cost control platform, a business travel platform, and an API integration platform. The cost control platform and the business travel platform transmit data via the API integration platform. The cost control platform and the business travel platform pre-negotiate a preset encryption protocol to prevent data interception or tampering during transmission. The preset encryption protocol is either SSL or TLS.

[0040] The API integration platform includes multiple interfaces, each interface corresponds to a data queue (depending on actual needs, it may include a data queue that sends data to the cost control platform and a data queue that sends data from the cost control platform, or there may be only one data queue); the cost control platform may include a contract ledger database.

[0041] The preferred embodiments of the present application are described below in conjunction with the drawings in the specification. It should be understood that the preferred embodiments described herein are only used to illustrate and explain the present application and are not used to limit the present application. In addition, the embodiments and features in the embodiments of the present application can be combined with each other if there is no conflict.

[0042] Figure 2 The following is a flow chart of a method for automatically processing bills and invoices provided in an embodiment of the present application. Figure 2 As shown, the method for applying the fee control platform in the enterprise billing system may include:

[0043] Step S210: Receive the encrypted order information sent by the business travel platform through the API integration platform.

[0044] Encrypted order information is obtained by encrypting the order information of different customers using a preset encryption protocol pre-negotiated between the cost control platform and the business travel platform. Alternatively, the application form and order information can be encrypted together to obtain encrypted order information.

[0045] The fee control platform receives encrypted order information sent by the business travel platform through the API integration platform.

[0046] Furthermore, strict data verification is implemented before and after data transmission. This includes verifying the integrity and accuracy of data before sending, and performing data verification after receiving, in order to reduce errors and omissions in data transmission and improve data quality.

[0047] In addition, the API integration platform uses standardized data formats (such as JSON and XML) for data exchange when receiving and sending data to ensure the consistency of data structure and reduce errors caused by inconsistent formats.

[0048] Step S220: After obtaining the order information of different customers corresponding to the encrypted order information, extract the corresponding contract information in the order information of different customers and synchronize the contract ledger database.

[0049] Specifically, the cost control platform uses a negotiated encryption protocol to decrypt the encrypted order information obtained to obtain order information of different customers; then, it extracts the corresponding contract information from the order information of different customers and synchronizes it with the contract ledger database. Specifically, the contract information is synchronized to the integrated management platform in the cost control platform, and then further synchronized to the contract ledger for synchronization records. It can also automatically extract the billing date and reconciliation date of the corresponding customer.

[0050] Step S230: Generate a bill for the customer based on the extracted billing date and reconciliation date of the customer.

[0051] For any customer, retrieve the pre-stored bill withdrawal date and reconciliation date of the customer;

[0052] If it is detected that the customer's bill withdrawal date is the current day, a bill for the customer will be generated.

[0053] In some embodiments, the bill is queried based on the customer's order information;

[0054] If no abnormal billing data is found, the bill will be automatically pushed to the customer on the reconciliation date;

[0055] If abnormal billing data is found, a bill adjustment request is sent to the staff to receive the adjusted data. The data to be adjusted and the adjusted data are managed through the message queue.

[0056] After all the data to be adjusted are adjusted, the bill adjustment application status is updated to the adjusted application status.

[0057] Furthermore, a bill adjustment log is generated, which may include bill data before the bill adjustment, bill data after the bill adjustment, and corresponding adjustment status.

[0058] It is understandable that after the bill for the customer is generated, the bill can also be pushed to the customer to receive the adjustment application. Once the operation personnel confirms the adjustment application in the background, the system will update the status of the adjustment application and trigger the subsequent invoicing process.

[0059] This status change is recorded in the database for subsequent query and audit. Once confirmed, the adjustment request is automatically sent to the invoicing platform via an outbound message for review. This process is facilitated by a message queue, ensuring the timeliness and accuracy of the review request. After the review is complete, the results are fed back to the business end via the message queue. The business end, as a consumer, listens to the outbound review message, obtains the review results, and performs subsequent processing based on the results.

[0060] The fee control platform can provide a "bill adjustment log" function. By using SpEL expressions to reference parameters on the method, variables can be filled into the template to achieve dynamic operation log text content. The operation log needs to be bound to a specific business object, such as a delivery order number, so that all operation records for the business object can be queried based on the business object number. This helps to quickly track and audit the bill adjustment process. Customers can view all adjustment records. Technically, the recording of operation logs is simplified through annotations, avoiding the addition of additional logging logic to the business code, making the code more concise and focused on business logic. Custom function services can be provided to allow customers to expand the functionality of the operation log as needed, such as querying old address information.

[0061] Step S240: Determine the invoice type of the bill and the invoice header and receipt information corresponding to the customer based on the contract information corresponding to the bill and the stored historical invoicing data.

[0062] In specific implementation, based on the contract information corresponding to the bill and the stored historical invoicing data, the appropriate invoice type can be intelligently recommended or automatically matched to ensure that the invoice content is consistent with the agreed invoice content in the contract.

[0063] The invoice header and receipt information corresponding to the customer are obtained through the API integration platform to achieve automatic synchronization of data between the invoice header and receipt information in the supplier account and the expense control platform, reducing manual input errors.

[0064] It is understandable that the stored historical invoicing data and customer information of different customers (invoice header, legal entity information, bill information corresponding to historical contracts, and invoice type) can be used to train a neural network model, and an invoice type model can be trained to determine the invoice type corresponding to the corresponding bill content based on the invoice header, legal entity information, and bill content of different customers.

[0065] Step S250: After receiving the encrypted billing application sent by the business travel platform through the API integration platform, obtain the plaintext billing application, and perform billing process processing on the received information and the bill content of the bill based on the customer's legal entity and invoice header.

[0066] The invoicing application process includes:

[0067] After confirming the sub-statement, the customer can initiate an invoicing application.

[0068] The system automatically splits invoicing content according to legal entities and business lines, and provides previews to reduce manual operation errors.

[0069] The system breaks down invoicing content by legal entity and business line, and provides previews. The system supports both electronic and paper invoice issuance, adapting to the practical operating practices of different businesses.

[0070] Invoice processing and mailing, including:

[0071] After the customer confirms, the data is sent to Mall A to handle the invoicing process.

[0072] The system automatically matches train ticket stubs, reducing manual search and matching time. Other tickets are mailed to customers, and courier information is available.

[0073] Invoice entry and binding, including:

[0074] After receiving a paper invoice, customers scan it and bind it to the invoicing batch. Electronic invoice templates can be delivered via the "QR code" or "Send by Email" function, increasing the convenience of invoice delivery. In the event of a product return or invoicing error, the system supports the issuance of a negative invoice to offset the original invoice.

[0075] Through the above specific implementation plan, we can ensure the automation and onlineization of billing and invoicing processes, reduce manual operations, improve efficiency and accuracy, and enhance customer experience.

[0076] In some embodiments, employees can make compliant consumption on a third-party consumption platform supported by the enterprise (a one-stop platform that provides consumption services such as corporate cars, travel, catering, office procurement, etc.). The cost control platform can collect the reimbursement details corresponding to the consumption services of corporate employees on the third-party consumption platform in real time through the API integration platform, and generate a monthly bill on the configured bill extraction day each month, and push the monthly bill to the corresponding corporate employees on the natural day after the bill extraction. That is, the company directly pays and finally issues a unified invoice. The company's official consumption control is put in place in advance, and employees can avoid the advance payment, invoicing and other links in the traditional reimbursement process. It also supports both electronic invoices and paper invoices, and then automatically generates a monthly bill based on the travel date, and automatically pushes the bill to the customer on the billing date + 1 day.

[0077] In some embodiments, at preset time intervals, an API contract testing tool (such as Swagger, Postman) is used to test the API interface of the API integration platform;

[0078] If the detection result is that the interface is abnormal, the data processing and data transmission of the data queue corresponding to the abnormal interface will be stopped and an alarm message will be generated.

[0079] In some embodiments, the specific contents of the contract ledger may include: the contract signing process, the subcontract signing process, the process of generating contract content in a unified interface, and order cash flow. The ledger data involved in the specific contents of the contract ledger are all automatically written in real time by the cost control platform.

[0080] The automated bill and invoice processing method provided by this application has the following beneficial effects:

[0081] Improve efficiency: Automated bill generation and delivery reduces manual operations and improves the efficiency of financial management.

[0082] Enhanced accuracy: The system automates bill and invoice processing, reducing human errors and improving data accuracy.

[0083] Improve user experience: Online confirmation and adjustment of bill anomalies simplifies user operations and improves user experience.

[0084] Data consistency: Ensures data consistency between Mall A and the reconciliation and settlement center, improving data reliability.

[0085] Reduced communication costs: Online processing of bill exceptions and invoicing applications reduces offline communication and lowers communication costs.

[0086] Optimize invoice management: Automated invoice issuance and mailing processes reduce the workload of users' manual entry and optimize invoice management.

[0087] Corresponding to the above method, the embodiment of the present application also provides an automatic processing device for bills and invoices, such as Figure 3 As shown, the cost control platform is applied to the enterprise billing system, and the enterprise billing system also includes a business travel platform and an API integration platform. The device includes:

[0088] Receiving unit 310 is configured to receive encrypted order information sent by the business travel platform through the API integration platform. The encrypted order information is obtained by encrypting order information of different customers using a preset encryption protocol pre-negotiated between the cost control platform and the business travel platform. The API integration platform includes data queues corresponding to multiple interfaces.

[0089] Extraction unit 320 is configured to, after obtaining the order information of different customers corresponding to the encrypted order information, extract the corresponding contract information from the order information of different customers and synchronize it with the contract ledger database; for any customer, extract the pre-stored billing date and reconciliation date of the customer;

[0090] The generating unit 330 is configured to generate a bill for the customer if it is detected that the billing date for the customer is the current day; query the bill based on the customer's order information, and if no abnormal bill data is found, automatically push the bill to the customer on the reconciliation date;

[0091] Determining unit 340 is configured to determine the invoice type of the invoice and the invoice header and receipt information corresponding to the customer based on the contract information corresponding to the invoice and the stored historical invoicing data. The invoice header and receipt information corresponding to the customer are obtained by automatically synchronizing the invoice header and receipt information in the supplier account with the cost control platform through the API integration platform.

[0092] The acquisition unit 350 is used to obtain the plain text invoicing application after receiving the encrypted invoicing application sent by the business travel platform through the API integration platform, and perform invoicing process processing on the invoice header, receipt information and bill content of the bill.

[0093] The functions of the various functional units of the automated processing device for bills and invoices provided in the above-mentioned embodiments of the present application can be realized through the above-mentioned method steps. Therefore, the specific working process and beneficial effects of each unit in the automated processing device for bills and invoices provided in the embodiments of the present application will not be repeated here.

[0094] The present application also provides an electronic device, such as Figure 4 As shown, it includes a processor 410 , a communication interface 420 , a memory 430 and a communication bus 440 , wherein the processor 410 , the communication interface 420 , and the memory 430 communicate with each other via the communication bus 540 .

[0095] Memory 430, for storing computer programs;

[0096] The processor 410 is configured to execute the program stored in the memory 430 by performing the following steps:

[0097] The API integration platform receives encrypted order information sent by the business travel platform. The encrypted order information is encrypted using a preset encryption protocol pre-negotiated between the cost control platform and the business travel platform. The API integration platform includes data queues corresponding to multiple interfaces.

[0098] After obtaining the order information of different customers corresponding to the encrypted order information, extract the corresponding contract information in the order information of different customers and synchronize it with the contract ledger database;

[0099] For any customer, retrieve the pre-stored billing date and reconciliation date for that customer; if it is detected that the billing date for that customer is the current day, generate a bill for that customer; query the bill based on the customer's order information; if no abnormal billing data is found, automatically push the bill to the customer on the reconciliation date;

[0100] Based on the contract information corresponding to the bill and the stored historical invoicing data, the invoice type and the invoice header and receipt information corresponding to the customer are determined. The invoice header and receipt information corresponding to the customer are obtained by automatically synchronizing the invoice header and receipt information in the supplier account with the cost control platform through the API integration platform.

[0101] After receiving the encrypted invoicing application sent by the business travel platform through the API integration platform, obtain the plaintext invoicing application and process the invoicing process based on the customer's legal entity and invoice header.

[0102] The communication bus mentioned above can be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus. This communication bus can be divided into address buses, data buses, and control buses. For ease of illustration, the figure uses only one thick line, but this does not mean that there is only one bus or only one type of bus.

[0103] The communication interface is used for communication between the above electronic device and other devices.

[0104] The memory may include random access memory (RAM) or non-volatile memory (NVM), such as at least one disk storage. Alternatively, the memory may be at least one storage device located away from the processor.

[0105] The above-mentioned processor can be a general-purpose processor, including a central processing unit (CPU), a network processor (NP), etc.; it can also be a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, and discrete hardware components.

[0106] The implementation methods and beneficial effects of the various components of the electronic device in the above embodiments to solve the problems can be found in Figure 2 The various steps in the embodiment shown are implemented, therefore, the specific working process and beneficial effects of the electronic device provided by the embodiment of the present application are not repeated here.

[0107] In another embodiment provided by the present application, a computer-readable storage medium is also provided, in which instructions are stored. When the computer-readable storage medium is executed on a computer, the computer executes the automated bill and invoice processing method described in any of the above embodiments.

[0108] In another embodiment provided by the present application, a computer program product comprising instructions is also provided, which, when executed on a computer, enables the computer to execute the automated bill and invoice processing method described in any one of the above embodiments.

[0109] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems, or computer program products. Therefore, the embodiments of the present application may take the form of entirely hardware embodiments, entirely software embodiments, or embodiments combining software and hardware. Furthermore, the embodiments of the present application may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to magnetic disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0110] The computer program instructions can also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer-implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart block or blocks. Figure 1 one or more flowcharts and / or blocks Figure 1 means for functionally implementing the steps listed in the flowchart block or blocks.

[0111] These computer program instructions can also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instructions which implement the function specified in the flowchart block or blocks. Figure 1 one or more flowcharts and / or blocks Figure 1 means for functionally implementing the steps listed in the flowchart block or blocks.

[0112] The computer program instructions can also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer-implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart block or blocks. Figure 1 one or more flowcharts and / or blocks Figure 1 means for functionally implementing the steps listed in the flowchart block or blocks.

[0113] While preferred embodiments of the application have been described, modifications and variations can be apparent to those skilled in the art once aware of the general underlying concepts. Therefore, it is intended that the scope of the appended claims should include all such modifications and variations.

[0114] Obviously, numerous modifications and variations of the present embodiments are possible in light of the above teachings. It is therefore to be understood that within the scope of the appended claims and their equivalents, the application can be practiced otherwise than as specifically described.

Claims

1. A method for automated processing of bills and invoices, characterized in that: A cost control platform is applied to an enterprise billing system, wherein the enterprise billing system also includes a business travel platform and an API integration platform. The method includes: The API integration platform receives encrypted order information sent by the business travel platform. The encrypted order information is encrypted using a preset encryption protocol pre-negotiated between the cost control platform and the business travel platform. The API integration platform includes data queues corresponding to multiple interfaces. After obtaining the order information of different customers corresponding to the encrypted order information, extract the corresponding contract information in the order information of different customers and synchronize it to the contract ledger database; For any customer, retrieve the pre-stored billing date and reconciliation date for that customer; if it is detected that the billing date for that customer is the current day, generate a bill for that customer; query the bill based on the customer's order information; if no abnormal billing data is found, automatically push the bill to the customer on the reconciliation date; Based on the contract information corresponding to the bill and the stored historical invoicing data, the invoice type and the invoice header and receipt information corresponding to the customer are determined. The invoice header and receipt information corresponding to the customer are obtained by automatically synchronizing the invoice header and receipt information in the supplier account with the cost control platform through the API integration platform. After receiving the encrypted invoicing application sent by the business travel platform through the API integration platform, obtain the plaintext invoicing application and process the invoicing process based on the customer's legal entity and invoice header.

2. The method according to claim 1, wherein The default encryption protocol is SSL or TLS.

3. The method according to claim 1, wherein The method further comprises: If abnormal billing data is found, a bill adjustment request is sent to the staff to receive the adjusted data. The data to be adjusted and the adjusted data are managed through the message queue. After all the data to be adjusted are adjusted, the bill adjustment application status is updated to the adjusted application status.

4. The method according to claim 3, wherein Updating the bill adjustment application status to an adjusted application status, the method further comprising: Generate a bill adjustment log, which includes bill data before the bill adjustment, bill data after the bill adjustment, and corresponding adjustment status.

5. The method according to claim 1, wherein The method further comprises: The API integration platform collects reimbursement details corresponding to the consumption services of corporate employees on third-party consumption platforms in real time, generates monthly bills on the configured bill extraction day each month, and pushes the monthly bills to the corresponding corporate employees on the natural day after the bill extraction.

6. The method according to claim 1, wherein The method further comprises: At preset time intervals, use API contract testing tools to test the API interface of the API integration platform; If the detection result is that the interface is abnormal, the data processing and data transmission of the data queue corresponding to the detected abnormal interface will be stopped and an alarm message will be generated.

7. An automated bill and invoice processing device, characterized in that: A cost control platform used in an enterprise billing system, which also includes a business travel platform and an API integration platform, includes: A receiving unit is configured to receive encrypted order information sent by the business travel platform through the API integration platform. The encrypted order information is obtained by encrypting order information of different customers using a preset encryption protocol pre-negotiated between the fee control platform and the business travel platform. The API integration platform includes data queues corresponding to multiple interfaces. An extraction unit is configured to, after obtaining the order information of different customers corresponding to the encrypted order information, extract the corresponding contract information from the order information of different customers and synchronize it to the contract ledger database; for any customer, extract the pre-stored withdrawal billing date and reconciliation date of the customer; A generating unit is configured to generate a bill for the customer if it is detected that the billing date for the customer is the current day; query the bill based on the customer's order information, and automatically push the bill to the customer on the reconciliation date if no abnormal billing data is found; The determination unit is configured to determine the invoice type of the bill and the invoice header and receipt information corresponding to the customer based on the contract information corresponding to the bill and the stored historical invoicing data. The invoice header and receipt information corresponding to the customer are obtained by automatically synchronizing the invoice header and receipt information in the supplier account with the cost control platform through the API integration platform. The acquisition unit is used to obtain the plain text invoicing application after receiving the encrypted invoicing application sent by the business travel platform through the API integration platform, and perform invoicing process processing on the invoice header, receipt information and bill content of the bill.

8. The device according to claim 7, wherein The default encryption protocol is SSL or TLS.

9. An electronic device, characterized in that: The electronic device includes a processor, a communication interface, a memory and a communication bus, wherein the processor, the communication interface and the memory communicate with each other via the communication bus; Memory for storing computer programs; A processor, configured to implement the method according to any one of claims 1 to 6 when executing a program stored in a memory.

10. A computer-readable storage medium, characterized in that The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the method according to any one of claims 1 to 6 is implemented.

Images