Business travel data integrated management method and device and electronic equipment

Abstract

The invention provides a business travel data integrated management method and device and electronic equipment. The business travel data integrated management method comprises the steps of calling a preset standard interface to obtain original business travel data from different systems and preprocessing the original business travel data; preliminarily associating the preprocessed data corresponding to the same business travel order and performing multi-dimensional verification; if the multi-dimensional verification is passed, calling a preset standard interface to push associated data to a financial cloud server, so that the financial cloud server generates reimbursement receipts by using the received associated data; and acquiring operation index data of the preset standard interface in real time, and if an exception occurs, processing the exception based on a preset exception processing rule and recording exception information. According to the invention, the business travel data integrated management efficiency and accuracy can be improved.

Description

Technical Field

[0001] This invention relates to the field of data processing technology, and in particular to a business travel data integration management method, apparatus, and electronic device. Background Technology

[0002] In corporate travel and expense reimbursement management scenarios, order and invoice data generated by employee business travel are scattered across different systems (such as travel booking systems, image management systems, and financial reimbursement systems). Cross-system data integration and association are necessary to achieve closed-loop management of the entire expense reimbursement process. Currently, cross-system data interaction relies on manual operation or simple API calls, resulting in issues such as untimely data synchronization, low accuracy of association, and poor process integration, severely impacting reimbursement efficiency and financial control effectiveness. Summary of the Invention

[0003] In view of this, the purpose of the present invention is to provide a business travel data integration management method, apparatus and electronic device to alleviate the above-mentioned problems existing in the related art.

[0004] In a first aspect, embodiments of the present invention provide a business travel data integration and management method, comprising: calling a preset standard interface to obtain raw business travel data from different systems, and preprocessing the raw business travel data; wherein the raw business travel data includes raw business travel order data, raw invoice information, raw itinerary confirmation information, and raw invoice image files; initially associating the preprocessed data corresponding to the same business travel order and performing multi-dimensional verification; wherein the multi-dimensional verification includes amount verification, time verification, traveler verification, and invoice image information verification; if the multi-dimensional verification passes, calling the preset standard interface to push the associated data to a financial cloud server, so that the financial cloud server can generate reimbursement documents using the received associated data; collecting the operational indicator data of the preset standard interface in real time, and if an anomaly occurs, handling the anomaly based on preset anomaly handling rules and recording the anomaly information; wherein the anomaly includes at least one of the following: multi-dimensional verification failure, operational indicator data anomaly, and preprocessing anomaly.

[0005] Secondly, embodiments of the present invention also provide a business travel data integration and management device, comprising: a preprocessing module, used to call a preset standard interface to obtain raw business travel data from different systems and preprocess the raw business travel data; wherein the raw business travel data includes raw business travel order data, raw invoice information, raw itinerary confirmation information, and raw invoice image files; a verification module, used to initially associate the preprocessed data corresponding to the same business travel order and perform multi-dimensional verification; wherein the multi-dimensional verification includes amount verification, time verification, traveler verification, and invoice image information verification; a push module, used to call the preset standard interface to push the associated data to a financial cloud server if the multi-dimensional verification passes, so that the financial cloud server can generate reimbursement documents using the received associated data; and an anomaly handling module, used to collect the operating indicator data of the preset standard interface in real time, and if an anomaly occurs, handle the anomaly based on preset anomaly handling rules and record the anomaly information; wherein the anomaly includes at least one of the following: multi-dimensional verification failure, abnormal operating indicator data, and preprocessing anomaly.

[0006] Thirdly, embodiments of the present invention also provide an electronic device, including a processor and a memory, wherein the memory stores computer-executable instructions that can be executed by the processor, and the processor executes the computer-executable instructions to implement the business travel data integration management method described in the first aspect above.

[0007] This invention provides a business travel data integration management method, apparatus, and electronic device. The method involves calling a preset standard interface to obtain raw business travel data from different systems and performing preprocessing; initially associating the preprocessed data corresponding to the same business travel order and performing multi-dimensional verification; if the multi-dimensional verification passes, pushing the associating data to a financial cloud server via the preset standard interface, enabling the financial cloud server to generate expense reimbursement documents using the received associating data; and collecting real-time operational indicator data from the preset standard interface. If an anomaly occurs, it is handled based on preset anomaly handling rules, and anomaly information is recorded. Using this technology, seamless integration of different systems can be achieved using the preset standard interface, reducing the complexity of interfacing with different systems. The introduction of a multi-dimensional verification mechanism improves the accuracy of business travel data association. The introduction of an anomaly handling mechanism based on preset standard interface operational status monitoring and preset anomaly handling rules facilitates rapid fault location and troubleshooting by relevant personnel. Simultaneously, it ensures the consistency of cross-system data and the smoothness of business processes, reduces manual intervention costs, and thus improves the efficiency and accuracy of business travel data integration management.

[0008] Other features and advantages of the invention will be set forth in the description which follows, and will be apparent in part from the description, or may be learned by practicing the invention. The objects and other advantages of the invention are realized and obtained in accordance with the structures particularly pointed out in the description, claims and drawings.

[0009] To make the above-mentioned objects, features and advantages of the present invention more apparent and understandable, preferred embodiments are described below in detail with reference to the accompanying drawings. Attached Figure Description

[0010] To more clearly illustrate the specific embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the specific embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of the present invention. For those skilled in the art, other drawings can be obtained from these drawings without creative effort.

[0011] Figure 1 This is a flowchart illustrating a business travel data integration and management method according to an embodiment of the present invention; Figure 2 This is a diagram illustrating the architecture design of the integrated management platform in an embodiment of the present invention. Figure 3 This is a schematic diagram of the structure of a business travel data integration and management device according to an embodiment of the present invention; Figure 4 This is a schematic diagram of the structure of an electronic device according to an embodiment of the present invention. Detailed Implementation

[0012] To make the objectives, technical solutions, and advantages of the embodiments of the present invention clearer, the technical solutions of the present invention will be clearly and completely described below in conjunction with the embodiments. Obviously, the described embodiments are only some embodiments of the present invention, not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0013] Currently, in corporate travel and expense reimbursement management scenarios, cross-system data interaction relies on manual operation or simple interface calls, resulting in problems such as untimely data synchronization, low accuracy of correlation, and poor process integration, which seriously affect reimbursement efficiency and financial control effectiveness.

[0014] Based on this, the present invention provides a business travel data integration management method, device, and electronic device, which can alleviate the above-mentioned problems existing in related technologies.

[0015] To facilitate understanding of this embodiment, a detailed description of a business travel data integration and management method disclosed in this embodiment of the invention will be provided first. (See [link to relevant documentation]). Figure 1 As shown, the method may include the following steps: Step S102: Call the preset standard interface to obtain raw business travel data from different systems, and preprocess the raw business travel data.

[0016] The original business travel data may include original business travel order data, original invoice information, original itinerary confirmation information, and original invoice image files, etc.

[0017] Step S104: Initially associate the preprocessed data corresponding to the same business travel order and perform multi-dimensional verification.

[0018] Multi-dimensional verification can include amount verification, time verification, traveler verification, and invoice image information verification.

[0019] Step S106: If the multi-dimensional verification passes, the preset standard interface is called to push the associated data to the financial cloud server so that the financial cloud server can use the received associated data to generate reimbursement documents.

[0020] Step S108: Real-time collection of operational indicator data from the preset standard interface; if an anomaly occurs, the anomaly is handled based on the preset anomaly handling rules and the anomaly information is recorded.

[0021] Anomalies can include: failure of multi-dimensional verification, abnormal operation indicator data, and preprocessing anomalies.

[0022] This invention provides a business travel data integration and management method. The method involves calling a preset standard interface to obtain raw business travel data from different systems and performing preprocessing; initially associating the preprocessed data corresponding to the same business travel order and performing multi-dimensional verification; if the multi-dimensional verification passes, pushing the associating data to a financial cloud server via the preset standard interface, enabling the financial cloud server to generate expense reimbursement documents using the received associating data; and collecting real-time operational indicator data from the preset standard interface. If an anomaly occurs, it is handled based on preset anomaly handling rules, and anomaly information is recorded. Using this technology, seamless integration of different systems can be achieved using the preset standard interface, reducing the complexity of interfacing with different systems. The introduction of a multi-dimensional verification mechanism improves the accuracy of business travel data association. The introduction of an anomaly handling mechanism based on preset standard interface operational status monitoring and preset anomaly handling rules facilitates rapid fault location and troubleshooting by relevant personnel. Simultaneously, it ensures the consistency of cross-system data and the smoothness of business processes, reduces manual intervention costs, and thus improves the efficiency and accuracy of business travel data integration and management.

[0023] For ease of understanding, the above-mentioned business travel data integration management method is illustrated below using an integrated management platform as an example.

[0024] See Figure 2 As shown, the integrated management platform can adopt a layered architecture design, which is divided into application layer, service layer, data layer and infrastructure layer from top to bottom. Each layer has independent functions and works together to ensure the scalability and stability of the system.

[0025] See Figure 2 As shown, the application layer provides users with a visual operation interface and function entry points. The application layer mainly includes modules such as system configuration management, order invoice association management, interface monitoring, log query, and permission management. The functions of each module in the application layer are as follows: A1) System Configuration Management Module: Provides a visual configuration interface, allowing administrators to configure parameters for each system interface (interface URL, request method, authentication method, timeout, etc.), data format mapping rules, associated verification rules, exception retry rules, monitoring thresholds, etc.; supports saving, editing, deleting, importing, exporting configuration parameters, as well as querying and rolling back configuration history records.

[0026] A2) Order and Invoice Association Management Module: Displays the association status and details (order information, invoice information, image information) of business travel orders and invoices; supports manual triggering of order and invoice association, editing of association relationships, and handling of association exceptions; provides query, filtering, and export functions for associated data, and supports querying by enterprise, order number, invoice number, time range, and other conditions.

[0027] A3) Interface monitoring module: Provides a visual monitoring dashboard to display key indicators such as call success rate, response time, number of calls, and number of exceptions for each interface in real time; supports filtering and viewing by interface type, enterprise, and time range; triggers alarm prompts when the interface operation indicators exceed the preset threshold.

[0028] A4) Log Management Module: Provides functions for recording, storing, and querying full-process logs, including interface call logs, data processing logs, exception logs, and operation logs; supports multi-condition combined queries (such as time range, log type, interface name, order number, operator, etc.); supports viewing and exporting log details.

[0029] A5) Access Control Module: Supports role-based access control, allowing the creation of various roles such as system administrator, operations and maintenance personnel, corporate finance personnel, and general employees; different functional permissions and data permissions can be configured for different roles to achieve fine-grained access control.

[0030] See Figure 2As shown, the service layer is the core business logic layer of the integration management platform. It encapsulates various business service components and provides services including interface interaction services, data processing services, order and invoice association services, exception handling services, and notification push services. Each service component collaborates through standardized interfaces. The services provided by the service layer are as follows: B1) Interface Interaction Service: Encapsulates the interface call logic with business travel platforms, imaging systems, financial cloud systems, and transportation construction service platforms to achieve a unified interface call entry point; supports multiple protocols such as HTTP / HTTPS and RESTful; provides functions such as interface authentication, request parameter assembly, and response data parsing; supports synchronous / asynchronous processing modes for interface calls.

[0031] B2) Data Processing Service: Responsible for standardizing the data exchanged between various systems, including data format conversion, data cleaning, data validation, and data completion; converting heterogeneous data from different systems into a unified data format for the platform according to preset data format mapping rules; completing missing necessary fields and filtering invalid data to ensure data quality.

[0032] B3) Order and Invoice Association Service: Implements the association and matching logic between business travel orders, invoices, and image files, and adopts a multi-dimensional verification mechanism to improve the accuracy of association; supports both automatic and manual association modes; responsible for the creation, updating, deletion, and storage of association relationships.

[0033] B4) Exception Handling Service: Monitors exceptions throughout the entire process, including API call exceptions, data processing exceptions, and association matching exceptions; triggers corresponding handling strategies (such as automatic retries and manual intervention prompts) based on preset exception handling rules; records exception details and generates exception logs.

[0034] B5) Notification Push Service: Generates corresponding notification information based on changes in business process status; calls the transportation construction service platform interface to push notification information to designated employees; supports multiple message types such as text messages and link messages; records message push status to ensure successful push.

[0035] See Figure 2 As shown, the data layer is responsible for data storage and management, employing a combination of multiple databases to meet the storage needs of different data types and ensure data security, reliability, and accessibility. The databases in the data layer are as follows: C1) Relational databases (such as MySQL): Store structured data, including system configuration parameters, basic order information, basic invoice information, relational data, user information, role and permission data, interface configuration data, etc.; adopt a master-slave replication architecture to improve data read performance and data security.

[0036] C2) Time-series database (such as InfluxDB): Stores interface monitoring metrics data, such as interface call time, response time, call status and other time-series data; supports high-concurrency writes and fast queries, making it easy to analyze interface operation trends.

[0037] C3) Distributed file storage systems (such as MinIO): Store unstructured data, including invoice image files, system log files, configuration file export backups, etc.; support file upload, download, deletion, query and other operations; provide data redundancy backup mechanisms to ensure file security.

[0038] See Figure 2 As shown, the infrastructure layer provides basic support for system operation, including servers, network devices, operating systems, middleware, etc.; it adopts cloud server deployment, supports elastic expansion, and can dynamically adjust server resources according to changes in business volume; through load balancing equipment, it achieves uniform distribution of requests, improving the system's concurrent processing capabilities and availability.

[0039] The integrated management platform uses standardized interface interaction methods with various external systems, unifying interface protocols, authentication methods, and data formats to reduce system integration complexity and improve the stability and efficiency of interface interaction. The standardized interface interaction is implemented as follows: The integrated management platform obtains business travel order data and invoice information by calling the open interface provided by the business travel platform. The interface adopts the HTTPS protocol and RESTful style and is based on... Identity authentication is required; the business travel platform provides the following open interfaces: a1) Get token interface: Used to obtain the token required for interface calls. The interface URL (UAT environment) format is as follows: The request method used is POST; the request parameters include... (fixed to) ), , The response data is in JSON format and includes... , (Expiration time, unit: seconds) The integrated management platform periodically calls this interface to obtain... And store it in the cache, when Automatically re-acquire when it is about to expire to ensure the continuity of API calls.

[0040] a2) Invoice Information Query Interface: Used to query invoice information corresponding to business travel orders based on time or order dimensions; the interface URL (UAT environment) is in the form of... The request method is POST; the request header format is as follows: Authorization (format: ); Request parameters include: requestid (unique request identifier), companyId (company ID), queryType (query type, 1-time dimension, 2-order dimension), startDate (start time, ...). (Time must be transmitted), endDate (end time, (Timely transmission), orderNos (list of order numbers) The response data is in JSON format and includes a return code, a return message, and a data list. Each data entry in the data list contains information such as order number, order detail ID, invoice number, invoice date, invoice type, total price including tax, and image ID. The integrated management platform calls this interface to obtain order invoice information according to a preset query frequency (e.g., real-time or every 5 minutes), parses and validates the response data, extracts key information and stores it in the database. If the interface call fails, an exception handling service is triggered for retry.

[0041] a3) Get Trip Confirmation API: Used to retrieve trip confirmation information (including order details, traveler information, etc.) corresponding to business travel orders; API URL (UAT environment) format is as follows: The request method is POST; the request header format is as follows: Authorization (format: The request parameters include requestid, companyId, and orderNos (a list of order numbers). The response data is in JSON format and includes a return code, return information, and a data list. Each data item in the data list includes information such as order number, order detail ID, traveler's name, travel time, trip type, and amount. After obtaining the invoice information, the integrated management platform calls this interface to obtain the trip confirmation information so that the trip confirmation information can be used for subsequent verification of the association between the order and the invoice.

[0042] The integrated management platform obtains the viewing and download addresses of invoice image files, as well as the full structured information of the invoice, by calling the image system interface. The interface uses the HTTP protocol and is authenticated based on username and password. The image system interface is as follows: b1) Image Viewing Address Retrieval Interface: Used to retrieve the online viewing address of invoice image files based on the image ID; the interface URL (test environment) is in the form of... The request method is POST; the request parameters include useraccount (username), password (password, encrypted transmission), fileuuid (image ID), and systemcode (system code, fixed value); the response data is in JSON format and includes the return code, return information, viewing address (url), and expiration time (expireTime); after obtaining the invoice image ID, the integrated management platform calls this interface to obtain the viewing address, associates the viewing address with the invoice information and stores it for subsequent reimbursement document generation and display.

[0043] b2) Image Download Address Acquisition Interface: Used to retrieve the download address of the invoice image file based on the image ID; the interface URL (test environment) is in the form of... The request method uses POST; the request parameters are the same as those of the image retrieval address interface; the response data uses JSON format, including the return code, return information, download address (url), and expiration time (expireTime); when it is necessary to download invoice image files for archiving, the integrated management platform calls this interface to obtain the download address, and after the file is downloaded, it is stored in the distributed file system.

[0044] b3) Interface for obtaining full invoice information: Used to retrieve the full structured information of an invoice (such as buyer's name, seller's name, product name, tax rate, etc.) based on the image ID; the interface URL (test environment) is in the form of... The request method is POST; the request parameters include useraccount, password, fileuuid, systemcode, operatoruser (operator), and operatorname (operator's name); the response data is in JSON format and includes the return code, return information, a full invoice information object (including buyer information, seller information, product details, price and tax information, etc.), and verification status (whether the invoice authenticity verification has passed). The integrated management platform calls this interface to obtain the full invoice information so that it can be used for multi-dimensional verification of orders and invoices in the future. If the verification status is not passed, an exception alarm is triggered to notify relevant personnel to verify the authenticity of the invoice.

[0045] The integrated management platform pushes associated order, invoice, and image data to the financial cloud system via API calls to generate reimbursement documents. The API uses HTTPS protocol and is based on token authentication. The APIs called are as follows: c1) Obtain Financial Cloud Token Interface: Used to obtain the token required for calling the Financial Cloud system interface; the interface URL format is as follows: The request method is POST; the request parameters include appId and appSecret; the response data is in JSON format and includes token and expiresIn (expiration time); the integration management platform periodically calls this interface to obtain the token and stores it in the cache to ensure the token's validity.

[0046] c2) Expense Reimbursement Document Push Interface: Used to push standardized order, invoice, and image data to the financial cloud system to generate expense reimbursement documents; the interface URL format is as follows: The request method is POST; the request header format is as follows: Authorization (format: The request parameters include company information (companyId, companyName), employee information (employeeId, employeeName, user4ACode), order information (orderNo, orderDate, orderAmount), invoice information (invoiceNo, invoiceDate, invoiceType, taxAmount, totalAmount), and image information (imageId, imageUrl, imageType). The response data is in JSON format and includes a return code, return information, and document internal code (DJNM, a unique identifier for expense reports generated by the financial cloud system). The integration management platform standardizes the associated data and assembles the request parameters. Then, it calls this interface to push the data to the financial cloud system, obtains the document internal code from the response data, and associates it with the order information for storage. If the push fails, an exception handling service is triggered to retry. If the retry fails after 3 attempts, an alarm message is pushed.

[0047] The integrated management platform pushes notifications to employees based on changes in business status through the transportation construction service platform interface. This interface uses the HTTPS protocol and is implemented according to the interface specifications of enterprise office communication tools (such as WeChat Work, DingTalk, etc.). The transportation construction service platform interface is as follows: d1) Access to the transportation construction service platform Interface: Used to obtain the necessary information for API calls to the transportation construction service platform. The interface URL format is as follows: The request method is GET; the request parameters include corid (enterprise ID) and corpsecret (application key); the response data is in JSON format and includes errcode (error code) and errmsg (error message). , (Expiration time); the integrated management platform periodically calls this interface to obtain it. Stored in the cache.

[0048] d2) Send Application Message Interface: Used to push text or link messages to specified employees; the interface URL format is as follows: The request method uses POST; the request parameters include touser (a list of employee IDs to receive the message), toparty (a list of department IDs to receive the message, optional), msgtype (message type, text - text message, link - link message), and text (text message content, ...). (Timely transmission), link (link to message content, The system must transmit the message, which includes the title, description, URL, and picurl. The response data is in JSON format and includes errcode, errmsg, and invaliduser (a list of invalid user IDs). When the business status changes (such as order invoice association completed, expense report generated, approval / rejection), the integration management platform generates the corresponding message content, calls this interface to push the message to the specified employee, records the message push status, and pushes an alarm message to the administrator if an invalid user ID exists.

[0049] As one possible implementation, the preprocessed data may include business travel order data, invoice information, itinerary confirmation information, and invoice image information, etc. Based on this, the above step S104 (preliminarily associating the preprocessed data corresponding to the same business travel order and performing multi-dimensional verification) may include: preliminarily associating the business travel order data, invoice information, itinerary confirmation information, and invoice image information corresponding to the same business travel order; performing amount verification, time verification, traveler verification, and invoice image information verification on the associated data respectively; if at least one of the amount verification, time verification, traveler verification, and invoice image information verification fails, then the multi-dimensional verification fails.

[0050] For example, verifying the amount of the associated data may include: comparing the order amount in the business travel order data corresponding to the same business travel order with the total amount including tax in the invoice information corresponding to the same business travel order; if the error between the order amount and the total amount including tax corresponding to the same business travel order exceeds a preset error threshold, the amount verification fails. Time verification of associated data may include: comparing the travel time in the travel order data corresponding to the same business travel order with the invoice date in the invoice information corresponding to the same business travel order; if the travel time and invoice date corresponding to the same business travel order meet preset conditions, the time verification fails; wherein meeting the preset conditions includes: the invoice date corresponding to the same business travel order is not before the travel time corresponding to the same business travel order, and / or the interval between the travel time and invoice date corresponding to the same business travel order exceeds a preset interval threshold; The process of verifying travelers on the associated data can include: comparing the traveler's name in the itinerary confirmation information corresponding to the same business travel order with the buyer's and seller's names in the invoice information corresponding to the same business travel order; if the traveler's name and the buyer's and seller's names corresponding to the same business travel order do not match, the traveler verification will fail. Verifying invoice image information on associated data can include: comparing the invoice number and invoice date in the invoice image information corresponding to the same business travel order with the invoice information corresponding to the same business travel order; if the invoice number and invoice date corresponding to the same business travel order do not match the invoice information corresponding to the same business travel order, the invoice image information verification fails.

[0051] In practical applications, the order number can be used as the basic association identifier. When the integrated management platform obtains the invoice information returned by the business travel platform, the invoice data already contains the corresponding order number. This can be used as the basic association basis to initially associate the order data and invoice data with the same order number.

[0052] Based on the basic association, the following multi-dimensional verifications are further performed to ensure the accuracy of the association: 1) Amount Verification: Compare the total order amount in the order data with the total amount including tax in the invoice data. Discrepancies between the total order amount and the total amount including tax are allowed. The error (due to rounding) will be considered if the difference between the total order amount and the total amount including tax exceeds a threshold (i.e., If the association is abnormal, it is determined to be an anomaly.

[0053] 2) Time verification: Compare the travel time in the order data with the invoice date in the invoice data. The invoice date should be after the travel time, and the time interval between the invoice date and the travel time should not exceed 30 days (this can be adjusted through system configuration). If the invoice date is not after the travel time and / or the time interval between the invoice date and the travel time exceeds the configured time interval threshold (such as 30 days), it is determined to be an abnormal association.

[0054] 3) Traveler verification: Compare the traveler's name in the itinerary confirmation data with the buyer's name (such as company name) or seller's name (such as business travel service provider name) in the invoice data to ensure that the traveler's company is consistent with the buyer's company or matches the business travel service provider. If the traveler's company is inconsistent with the buyer's company or does not match the business travel service provider, it is judged as an abnormal association.

[0055] 4) Image Information Verification: After obtaining the full information of the invoice image, compare the invoice number and invoice date in the full information with the invoice information returned by the business travel platform to determine whether the invoice number and invoice date in the full information are consistent with the invoice information returned by the business travel platform. If the invoice number and invoice date in the full information are inconsistent with the invoice information returned by the business travel platform, it is determined to be an association anomaly.

[0056] As one possible implementation, the step S108 above, which involves processing exceptions and recording exception information based on preset exception handling rules, can be carried out in different ways depending on the circumstances, as follows: (1) If the multi-dimensional verification fails, the first abnormal information is generated and recorded in the abnormal log. The step of initially associating the pre-processed data corresponding to the same business travel order and performing multi-dimensional verification is repeated at least once according to the preset cycle. When the number of times the step of initially associating the pre-processed data corresponding to the same business travel order and performing multi-dimensional verification is repeated reaches the first preset number, the first alarm information is generated and pushed to the first target terminal device.

[0057] (2) If the preprocessing is abnormal, a second abnormal information is generated and recorded in the abnormal log. The preprocessing of the original business travel data is performed at least once again according to the preset cycle. When the number of times the preprocessing of the original business travel data is performed reaches the second preset number, a second alarm information is generated and pushed to the second target terminal device.

[0058] (3) If the operating indicator data is abnormal, a third alarm message is generated and pushed to the third target terminal device, while the second alarm message is displayed through the visual monitoring dashboard.

[0059] In practical applications, anomalies during the operation of the integrated management platform can be categorized into the following types: a) Interface call exceptions: including interface timeout, connection failure, return error codes, etc.; b) Data processing anomalies: including incorrect data format, missing data, and failed data validation; c) Order invoice association anomalies: including mismatched amounts, mismatched times, mismatched travelers, etc. d) System anomalies: including database connection anomalies, cache anomalies, insufficient server resources, etc.

[0060] For recoverable anomalies (such as interface timeouts or connection failures caused by network fluctuations), the following intelligent retry mechanism is designed: Administrators can set retry parameters for different anomaly types in the system configuration management module, including the number of retries (default 3), retry interval (default 1 minute for the first time, with the interval doubling for each subsequent time), and maximum retry interval (default 10 minutes). When a recoverable anomaly occurs, the system automatically triggers the retry mechanism and performs retry operations according to the preset retry parameters. When the number of retries reaches the preset limit, or the anomaly type becomes unrecoverable (such as the interface returning a permanent error code), the retries are terminated, the anomaly information is recorded, and an alarm is triggered.

[0061] The exception handling process is as follows: 1) Exception handling: Exceptions during system operation are captured through the try-catch mechanism, or exceptions are detected through the interface monitoring module.

[0062] 2) Exception Classification and Recording: Classify captured exceptions and record exception information to the exception log; the exception information includes exception time, exception type, exception details, associated order number / invoice number / interface name, etc.

[0063] 3) Automatic processing: For recoverable exceptions, a retry mechanism is triggered. For example, for exceptions that can be automatically corrected, such as data format errors, the system automatically corrects the data according to preset rules and then re-executes the relevant operations.

[0064] 4) Manual handling: For unrecoverable anomalies or anomalies that fail to be automatically handled, an alarm message is triggered to notify relevant personnel; relevant personnel can view the anomaly details through the log query module and formulate an anomaly handling plan; after the anomaly is handled, the anomaly status is marked as "resolved" in the system and the anomaly handling process is recorded.

[0065] As an example, when an association anomaly occurs (i.e., an order invoice association anomaly, including mismatched amounts, mismatched times, mismatched travelers, etc.), the system can handle it according to the following process: 1) Exception Log: Record exception information to the exception log. The exception information includes the order number, invoice number, exception type (amount mismatch, time mismatch, etc.), exception details, etc.

[0066] 2) Automatic retry association: In case of anomalies caused by data synchronization delay (such as incomplete synchronization of invoice information), the system automatically triggers a retry mechanism, retrying the association operation once every 10 minutes, with a maximum of 5 retry operations.

[0067] 3) Manual intervention: If the association anomaly persists after 5 retries, the system will push the abnormal data to the anomaly list of the order invoice association management module, triggering an alarm to notify maintenance personnel or enterprise finance personnel. Relevant personnel can view the anomaly details through the visual interface, manually adjust the association relationship or verify the data, and mark the anomaly status as "resolved" after processing.

[0068] As one possible implementation method, the above-mentioned business travel data integration and management method may further include: generating visual reports based on the collected operational indicator data, and displaying the visual reports through a visual monitoring dashboard.

[0069] Continuing from the previous example, the interface monitoring module collects real-time operational metrics for each interface (including call count, success count, failure count, call success rate, average response time, maximum response time, minimum response time, etc.); the interface monitoring method is as follows: 1) Monitoring indicator collection: embed monitoring points at the entry and exit points of each interface call to collect information such as interface call time, response time, call status (success / failure), and error code; store the collected indicator data to the time series database at regular intervals (e.g., 1 second / time).

[0070] 2) Monitoring threshold configuration: Administrators can set monitoring thresholds for each interface in the system configuration management module, such as call success rate threshold (default 95%), average response time threshold (default 3 seconds), failure count threshold (default 5 times / hour), etc.

[0071] 3) Alarm Triggering and Push: Real-time comparison of monitoring metrics with preset monitoring thresholds. When a monitoring metric exceeds its corresponding monitoring threshold (e.g., call success rate below 95%, average response time exceeding 3 seconds, or number of failures not less than 5 within 1 hour), an alarm is automatically triggered. The alarm information includes the interface name, interface URL, abnormal metric, current value, threshold, alarm time, etc. The alarm is pushed to maintenance personnel through enterprise office communication tools (such as WeChat Work, DingTalk, etc.) and is also displayed on the visual monitoring dashboard.

[0072] 4) Monitoring report generation: Supports the generation of reports on interface operation (reflecting the changing trends of interface operation indicators, such as daily, weekly, and monthly reports), and displays the reports on the visual monitoring dashboard; reports can be automatically pushed to the administrator's email or downloaded and viewed in the system.

[0073] As one possible implementation method, the above-mentioned business travel data integration and management method may further include: recording preset standard interface call logs, preprocessing logs, preliminary association logs, operation logs and exception logs respectively; wherein, the exception logs include the exception occurrence time, exception type, exception details and exception handling status; storing the preset standard interface call logs and preprocessing logs in a time-series database, and storing the preliminary association logs, operation logs and exception logs in a relational database.

[0074] Continuing from the previous example, the log management module records log data for the entire process and stores it according to log type. It supports multi-condition querying and exporting of log data. The log management method is as follows: 1) Log Classification: Log data is classified into types such as interface call logs, data processing logs, order and invoice association logs, operation logs, and exception logs. Interface call logs record the call time, request parameters, response data, call status, error messages, and call duration for each interface. Data processing logs record the data standardization process (including data format conversion, data cleaning, data validation, and data completion), including the original data, processed data, and data validation results. Order and invoice association logs record the association time, association method (automatic / manual), association result, and association exception information between orders and invoices. Operation logs record user operations within the system, including the operator, operation time, operation module, operation content, and operation result. Exception logs record all exceptions during system operation, including the exception time, exception type, exception details, and processing status.

[0075] 2) Log storage: High-frequency logs such as interface call logs and data processing logs are stored in a time-series database for quick querying, while order invoice related logs, operation logs, and exception logs are stored in a relational database. Log data is retained for 6 months to meet the needs of business verification and fault tracing.

[0076] 3) Log Query: Provides a multi-condition query interface, supporting querying logs by log type, time range, interface name, order number, invoice number, operator, etc.; query results are displayed in pages, and log details can be viewed; query results can be exported to Excel or PDF format.

[0077] As one possible implementation method, the above-mentioned business travel data integration and management method may further include: if the business status changes, generating notification information based on the change in business status and pushing the notification information to a fourth target terminal device; wherein, the business status includes the initial association status, expense report generation status, review status, etc.; if pushing the notification information to the fourth target terminal device fails, generating a fourth alarm information and pushing it to a fifth target terminal device.

[0078] Continuing from the previous example, when the business status changes (such as order invoice association completed, expense report generated, approval / rejection), the integration management platform generates the corresponding message content and calls the above-mentioned application message sending interface to push the message to the designated employee. At the same time, the message push status is recorded. If an invalid user ID exists, the above-mentioned application message sending interface is called to push alarm information to the administrator.

[0079] In practical applications, the aforementioned integrated management platform can also adopt a three-level permission control model of "role-user-permission" and combine it with the enterprise ownership dimension to achieve refined permission control and ensure data security.

[0080] Specifically, the system pre-defines the following core roles (the permissions of each role can be flexibly adjusted through system configuration): 1) System Administrator: Has full access to all system functions, including system configuration, access control, interface monitoring, log querying, etc.; can view business data of all enterprises.

[0081] 2) Operations and maintenance personnel: They have operation permissions for operations and maintenance-related functions such as interface monitoring, log querying, and exception handling; they can view the interface operation data and log data of all enterprises, but cannot modify business data.

[0082] 3) Corporate finance personnel: They have access to functions such as order and invoice association management, association exception handling, and corporate log query; they can only view business data related to their own company.

[0083] 4) Regular employees of the company: They only have the permission to view their own business travel orders, invoice information, expense reimbursement document status, and receive notification messages; they cannot perform other operations.

[0084] Following the previous example, the access control method is as follows: 1) Functional access control: Define the functional modules and operation buttons that each role can access through the permission matrix; after a user logs into the system, load the corresponding functional menu according to the user's role, and hide the functional modules and operation buttons that the user does not have permission to access.

[0085] 2) Data access control: Data access is isolated based on enterprise affiliation, and an enterprise ID field is added to the database table; when users query data, the system automatically adds enterprise ID filtering conditions to ensure that users can only query relevant data of their own enterprise; system administrators and maintenance personnel can bypass data access restrictions to perform relevant data operations through permission configuration, but the operation log will record the relevant data operations in detail.

[0086] 3) Permission verification process: When a user initiates an operation request, the system first verifies whether the user has the operation permission for that function; if so, it then verifies whether the user has the data permission to operate the corresponding data; only after both verifications pass can the operation be allowed; if the verification fails, an insufficient permission prompt is returned and the operation log is recorded.

[0087] The core idea of ​​the aforementioned business travel data integration management method is to construct an integrated architecture based on standardized interfaces between an integrated management platform and multiple systems for full-process monitoring and control. With the integrated management platform as the core hub, it achieves standardized data interaction and process connection between the business travel platform, imaging system, financial cloud system, and transportation construction service platform. This method achieves real-time synchronization of business travel order data, invoice information, itinerary confirmations, invoice image files, and financial documents (i.e., reimbursement documents) through the design of standardized interface interaction protocols and data formats. It employs a multi-dimensional data verification mechanism to accurately associate orders and invoices, establishes an interface monitoring module to monitor interface operation status in real time, and a log management module to record, store, and query logs throughout the entire process. Furthermore, it ensures data consistency through exception handling and retry mechanisms and guarantees data security through a refined access control module. Therefore, this business travel data integration management method enables automated and intelligent integrated management of the entire process of business travel order-invoice association, improving reimbursement efficiency and financial control.

[0088] The core implementation process of the above-mentioned business travel data integration and management method is as follows: (I) System initialization and configuration phase: Complete the interface configuration with the business travel platform, imaging system, financial cloud system and transportation construction service platform on the integration management platform, including configuring interface URL, request protocol, authentication parameters, data format mapping rules, etc.; configure basic parameters such as order and invoice association verification rules, permission control rules, interface monitoring thresholds, and abnormal retry rules on the integration management platform.

[0089] (II) Data Collection and Association Stage: After an employee completes a business trip, the integrated management platform calls the business travel platform interface in real time to obtain business travel order data, invoice information, and itinerary confirmation slips. It also calls the image system interface to obtain relevant information about invoice image files (including the viewing address, download address, and full invoice information of the invoice image files). Then, the business travel order data, invoice information, itinerary confirmation slip information, and invoice image information corresponding to the same business travel order are initially associated. After the associated data is verified through a multi-dimensional verification mechanism, the association and matching of business travel order data, invoice information, itinerary confirmation slip information, and invoice image information are completed to generate associated relationship data.

[0090] (III) Data Processing and Push Stage: The integrated management platform standardizes the associated data to convert it into a data format that the financial cloud system can recognize; the integrated management platform calls the financial cloud system interface in real time to push the standardized data to the financial cloud system, and the financial cloud system generates reimbursement documents; the integrated management platform calls the transportation construction service platform interface to push status notifications to employees based on changes in business status (such as order invoice association completed, reimbursement documents generated, review status updated, etc.).

[0091] (iv) Full-process monitoring and exception handling stage: The interface monitoring module monitors the call status, response time, and data return status of each system interface in real time; the log management module records the interface call log, data processing log, and exception log of the entire process; when an interface call fails or data verification fails, the exception handling module automatically triggers the retry mechanism according to preset rules. If the exception cannot be resolved, an alarm message is pushed to the operation and maintenance personnel to ensure the smooth operation of the process.

[0092] In summary, the beneficial effects of the above-mentioned business travel data integration and management methods are mainly reflected in the following aspects: (A) Achieve seamless integration of multiple systems and reduce interface complexity: Through a unified integration management platform and standardized interface interaction protocol, seamless integration of business travel order system, image management system, financial system and notification system is achieved, reducing system interface and maintenance costs.

[0093] (B) Improve the accuracy of order and invoice association and ensure the effectiveness of financial control: A multi-dimensional verification mechanism is adopted, which combines order number, amount, time, traveler, image information and other dimensions for verification. This effectively avoids data mismatch and omission problems, significantly improves the accuracy of association, and ensures the accuracy and standardization of financial audit.

[0094] (C) Real-time data synchronization improves business processing efficiency: Through real-time interface calls and data synchronization mechanisms, business travel orders, invoice information, itinerary confirmations, and invoice image data can be linked and pushed to the financial system in real time to generate reimbursement documents; employees can receive business status notifications in real time without waiting for data synchronization, significantly shortening the reimbursement process cycle and significantly improving business processing efficiency and user experience.

[0095] (D) Full-process monitoring and rapid fault location to ensure stable system operation: Build an interface monitoring and log management system to monitor the interface operation status in real time and record the full-process log; when a fault occurs, the root cause of the problem can be quickly located through the log, the fault investigation time is significantly shortened, and the stable operation of the integration process is ensured.

[0096] (E) Standardized anomaly handling to ensure data consistency: Establishing standardized anomaly handling processes and intelligent retry mechanisms can automatically handle most recoverable anomalies, reducing manual intervention; for unrecoverable anomalies, an alarm mechanism is used to promptly notify relevant personnel for handling, ensuring the consistency of data across multiple systems and the smoothness of business processes.

[0097] (F) Refined access control to ensure data security: Adopting a three-level access control model of "role-user-permission" and combining it with the enterprise affiliation dimension to achieve data isolation, ensuring that users of different roles and different enterprises can only access functions and data within their access scope, effectively preventing the leakage of sensitive business data and financial data, and ensuring data security.

[0098] Based on the above-described business travel data integration and management method, this invention also provides a business travel data integration and management device, see [link to device]. Figure 3 As shown, the device may include the following modules: The preprocessing module 302 is used to call a preset standard interface to obtain raw business travel data from different systems and to preprocess the raw business travel data; wherein, the raw business travel data includes raw business travel order data, raw invoice information, raw itinerary confirmation information and raw invoice image files.

[0099] The verification module 304 is used to initially associate the preprocessed data corresponding to the same business travel order and perform multi-dimensional verification; wherein, the multi-dimensional verification includes amount verification, time verification, traveler verification and invoice image information verification.

[0100] The push module 306 is used to call the preset standard interface to push the associated data to the financial cloud server if the multi-dimensional verification passes, so that the financial cloud server can use the received associated data to generate reimbursement documents.

[0101] The exception handling module 308 is used to collect the operation index data of the preset standard interface in real time. If an exception occurs, the exception is handled according to the preset exception handling rules and the exception information is recorded. The exception includes at least one of the following: multi-dimensional verification failure, abnormal operation index data, and preprocessing exception.

[0102] By adopting the aforementioned business travel data integration and management device, seamless integration of different systems can be achieved using preset standard interfaces, reducing the complexity of interfacing different systems. By introducing a multi-dimensional verification mechanism, the accuracy of business travel data association can be improved. By introducing an anomaly handling mechanism based on preset standard interface operation status monitoring and preset anomaly handling rules, relevant personnel can quickly locate and troubleshoot faults. At the same time, it ensures the consistency of cross-system data and the smoothness of business processes, reduces the cost of manual intervention, and thus improves the efficiency and accuracy of business travel data integration and management.

[0103] The business travel data integration and management device provided in this embodiment of the invention has the same implementation principle and technical effects as the aforementioned business travel data integration and management method embodiment. For the sake of brevity, any parts not mentioned in the embodiment of the business travel data integration and management device can be referred to the corresponding content in the aforementioned business travel data integration and management method embodiment.

[0104] This invention also provides an electronic device, such as... Figure 4 The diagram shows the structure of the electronic device, which includes a processor 41 and a memory 40. The memory 40 stores computer-executable instructions that can be executed by the processor 41. The processor 41 executes the computer-executable instructions to implement the aforementioned business travel data integration management method.

[0105] exist Figure 4 In the illustrated embodiment, the electronic device further includes a bus 42 and a communication interface 43, wherein the processor 41, the communication interface 43, and the memory 40 are connected via the bus 42.

[0106] The memory 40 may include high-speed random access memory (RAM) and may also include non-volatile memory, such as at least one disk storage device. Communication between this system network element and at least one other network element is achieved through at least one communication interface 43 (which can be wired or wireless), such as the Internet, wide area network, local area network, metropolitan area network, etc. The bus 42 may be an ISA (Industry Standard Architecture) bus, a PCI (Peripheral Component Interconnect) bus, or an EISA (Extended Industry Standard Architecture) bus, etc. The bus 42 can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Figure 4 The symbol is represented by a single double-headed arrow, but this does not mean that there is only one bus or one type of bus.

[0107] Processor 41 may be an integrated circuit chip with signal processing capabilities. In implementation, each step of the aforementioned business travel data integration management method can be completed through the integrated logic circuits in the hardware of processor 41 or through software instructions. Processor 41 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, or discrete hardware components. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the business travel data integration management method disclosed in this embodiment can be directly implemented by a hardware decoding processor, or implemented by a combination of hardware and software modules in the decoding processor. The software modules can reside in random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, or other mature storage media in the art. The storage medium is located in the memory. The processor 41 reads the information in the memory and, in conjunction with its hardware, completes the steps of the business travel data integration and management method of the aforementioned embodiment.

[0108] Unless otherwise specifically stated, the relative steps, numerical expressions, and values ​​of the components and steps described in these embodiments do not limit the scope of the invention.

[0109] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a processor-executable, non-volatile, computer-readable storage medium. Based on this understanding, the technical solution of this invention, essentially, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the business travel data integration management method described in the various embodiments of this invention. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0110] In the description of this invention, it should be noted that the terms "center," "upper," "lower," "left," "right," "vertical," "horizontal," "inner," and "outer," etc., indicate the orientation or positional relationship based on the orientation or positional relationship shown in the accompanying drawings. They are used only for the convenience of describing the invention and for simplifying the description, and do not indicate or imply that the device or element referred to must have a specific orientation, or be constructed and operated in a specific orientation. Therefore, they should not be construed as limitations on the invention. Furthermore, the terms "first," "second," and "third" are used for descriptive purposes only and should not be construed as indicating or implying relative importance.

[0111] Finally, it should be noted that the above-described embodiments are merely specific implementations of the present invention, used to illustrate the technical solutions of the present invention, and not to limit it. The scope of protection of the present invention is not limited thereto. Although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that any person skilled in the art can still modify or easily conceive of changes to the technical solutions described in the foregoing embodiments within the technical scope disclosed in the present invention, or make equivalent substitutions for some of the technical features; and these modifications, changes, or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of the present invention, and should all be covered within the scope of protection of the present invention. Therefore, the scope of protection of the present invention should be determined by the scope of the claims.

Claims

1. A method for integrated management of business travel data, characterized in that, include: The system calls a preset standard interface to obtain raw business travel data from different systems and preprocesses the raw business travel data; wherein, the raw business travel data includes raw business travel order data, raw invoice information, raw itinerary confirmation information, and raw invoice image files; The pre-processed data corresponding to the same business travel order are initially linked and subjected to multi-dimensional verification; wherein, the multi-dimensional verification includes amount verification, time verification, traveler verification and invoice image information verification; If the multi-dimensional verification passes, the preset standard interface is called to push the associated data to the financial cloud server so that the financial cloud server can use the received associated data to generate reimbursement documents. The system collects operational metrics data from the preset standard interface in real time. If an anomaly occurs, it processes the anomaly based on preset anomaly handling rules and records the anomaly information. The anomaly includes at least one of the following: multi-dimensional verification failure, abnormal operational metrics data, and preprocessing anomaly.

2. The business travel data integration and management method according to claim 1, characterized in that, The preprocessed data includes business travel order data, invoice information, itinerary confirmation information, and invoice image information; the preprocessed data corresponding to the same business travel order are initially linked and subjected to multi-dimensional verification, including: Initially link the business travel order data, invoice information, itinerary confirmation information, and invoice image information corresponding to the same business travel order; then perform amount verification, time verification, traveler verification, and invoice image information verification on the linked data respectively; if at least one of the amount verification, time verification, traveler verification, and invoice image information verification fails, then the multi-dimensional verification fails.

3. The business travel data integration and management method according to claim 2, characterized in that, The associated data is validated for amount, including: comparing the order amount in the business travel order data corresponding to the same business travel order with the total amount including tax in the invoice information corresponding to the same business travel order; if the error between the order amount and the total amount including tax corresponding to the same business travel order exceeds the preset error threshold, the amount validation fails. Time verification is performed on the associated data, including: comparing the travel time in the travel order data corresponding to the same travel order with the invoice date in the invoice information corresponding to the same travel order; if the travel time and invoice date corresponding to the same travel order meet preset conditions, the time verification fails; wherein, meeting the preset conditions includes: the invoice date corresponding to the same travel order is not before the travel time corresponding to the same travel order, and / or, the interval between the travel time and invoice date corresponding to the same travel order exceeds a preset interval threshold; The associated data is validated for travelers, including: comparing the traveler's name in the itinerary confirmation information corresponding to the same business travel order with the buyer's and seller's names in the invoice information corresponding to the same business travel order; if the traveler's name and the buyer's and seller's names corresponding to the same business travel order do not match, the traveler validation fails. The associated data is verified by invoice image information, including: comparing the invoice number and invoice date in the invoice image information corresponding to the same business travel order with the invoice information corresponding to the same business travel order; if the invoice number and invoice date corresponding to the same business travel order do not match the invoice information corresponding to the same business travel order, the invoice image information verification fails.

4. The business travel data integration and management method according to claim 3, characterized in that, Exceptions are handled and exception information is recorded based on preset exception handling rules, including: If the multi-dimensional verification fails, a first abnormal message is generated and recorded in the abnormal log. The process of initially associating the pre-processed data corresponding to the same business travel order and performing multi-dimensional verification is repeated at least once according to a preset period. When the number of times the process of initially associating the pre-processed data corresponding to the same business travel order and performing multi-dimensional verification is repeated reaches a first preset number, a first alarm message is generated and pushed to the first target terminal device.

5. The business travel data integration and management method according to claim 4, characterized in that, The system handles exceptions and records exception information based on preset exception handling rules, and also includes: If the preprocessing is abnormal, a second abnormality message is generated and recorded in the abnormality log. The preprocessing step of the original business travel data is repeated at least once according to a preset period. When the number of times the preprocessing step of the original business travel data is repeated reaches a second preset number, a second alarm message is generated and pushed to the second target terminal device. If the operational metrics data are abnormal, a third alarm message is generated and pushed to the third target terminal device, while the second alarm message is displayed through a visual monitoring dashboard.

6. The business travel data integration and management method according to claim 5, characterized in that, Also includes: Visual reports are generated based on the collected operational metrics data and displayed on a visual monitoring dashboard.

7. The business travel data integration and management method according to claim 1, characterized in that, Also includes: Record the following logs respectively: preset standard interface call log, preprocessing log, preliminary association log, operation log, and exception log; wherein, the exception log includes the exception occurrence time, exception type, exception details, and exception handling status; Store the preset standard interface call logs and preprocessed logs in a time-series database, and store the preliminary association logs, operation logs and exception logs in a relational database.

8. The business travel data integration and management method according to claim 1, characterized in that, Also includes: If the business status changes, a notification message is generated based on the change in business status and pushed to the fourth target terminal device; wherein, the business status includes at least one of the following: preliminary association status, expense report generation status, and review status; If pushing notification information to the fourth target terminal device fails, a fourth alarm message is generated and pushed to the fifth target terminal device.

9. A business travel data integration and management device, characterized in that, include: The preprocessing module is used to call a preset standard interface to obtain raw business travel data from different systems and to preprocess the raw business travel data; wherein, the raw business travel data includes raw business travel order data, raw invoice information, raw itinerary confirmation information, and raw invoice image files; The verification module is used to initially associate the preprocessed data corresponding to the same business travel order and perform multi-dimensional verification; wherein, the multi-dimensional verification includes amount verification, time verification, traveler verification and invoice image information verification; The push module is used to call the preset standard interface to push the associated data to the financial cloud server if the multi-dimensional verification passes, so that the financial cloud server can use the received associated data to generate reimbursement documents. An exception handling module is used to collect the operation index data of the preset standard interface in real time. If an exception occurs, the exception is handled according to the preset exception handling rules and the exception information is recorded. The exception includes at least one of the following: multi-dimensional verification failure, abnormal operation index data, and preprocessing exception.

10. An electronic device, characterized in that, The method includes a processor and a memory, the memory storing computer-executable instructions that can be executed by the processor, the processor executing the computer-executable instructions to implement the business travel data integration management method according to any one of claims 1 to 8.

Images