Multi-currency reconciliation data management method and device based on Charge status

Abstract

This invention provides a method and apparatus for managing multi-currency reconciliation data based on Charge status, relating to the field of payment data processing. The method includes: in response to the determination of multi-currency reconciliation users, setting a batch extension of the Charge authorization period for multiple multi-currency reconciliation users to a preset time; synchronizing the latest Charge status corresponding to the extended authorization period to the expense control management system in real time; generating a status identifier based on the Charge status through the expense control management system; in response to a reconciliation addition operation performed on a target multi-currency reconciliation user among multiple multi-currency reconciliation users, verifying the Charge status against the loan package currency corresponding to the target multi-currency reconciliation user based on the status identifier; and in response to the verification result showing that the Charge status is "Charge Closed" and the loan package currency is a foreign currency, determining that the reconciliation addition operation is an invalid operation lacking reconciliation authority and intercepting the reconciliation addition operation.

Description

Technical Field

[0001] This application relates to the field of payment data processing technology, and in particular to a method and apparatus for managing multi-currency reconciliation data based on Charge status. Background Technology

[0002] Currently, in enterprise expense control management scenarios, multi-currency reconciliation is a core function supporting cross-border business and foreign currency receipts and payments control. It enables the creation of foreign currency loan packages and reconciliation in the same currency, adapting to customers' cross-border expense reimbursement needs. However, the large number of invalid expense reports submitted for multi-currency reconciliation results in a significant amount of data modification and repair in the database, leading to high operational and maintenance resource costs. Summary of the Invention

[0003] The purpose of this invention is to provide a method and apparatus for managing multi-currency reconciliation data based on Charge status, so as to solve the technical problem that the large amount of repair data leads to high operation and maintenance resource costs.

[0004] Firstly, this application provides a method for managing multi-currency reconciliation data based on Charge status, the method comprising: In response to the determination of multi-currency reimbursement users, the authorization period of the Charge authorization for multiple multi-currency reimbursement users is extended in batches to a preset time. The latest Charge status corresponding to the extended authorization period is synchronized to the expense control management system in real time. A status identifier is generated through the expense control management system based on the Charge status. In response to the reimbursement addition operation performed for the target multi-currency reimbursement user among multiple multi-currency reimbursement users, the Charge status and the loan package currency corresponding to the target multi-currency reimbursement user are verified based on the status identifier to obtain the verification result; In response to the verification result indicating that the Charge status is closed and the currency of the loan package is a foreign currency, the verification addition operation is determined to be an invalid operation without verification authority and the verification addition operation is blocked. By comparing the user business scenarios of multiple multi-currency reconciliation users to verify functional compatibility, multi-currency management functions that are compatible with the user business scenarios of the target multi-currency reconciliation user are obtained and recommended.

[0005] In one possible implementation, after determining that the reimbursement addition operation is an invalid operation without reimbursement authority and intercepting the reimbursement addition operation in response to the verification result that the Charge status is Charge off and the currency of the loan package is a foreign currency, the implementation further includes: A prompt message is generated to intercept the cancellation and addition operation, and the prompt message and the Charge status are synchronized to the PC and APP through a distributed database to adapt to the display size and display layout of different terminals and ensure that the prompt logic and display effect are consistent across different terminals.

[0006] In one possible implementation, after determining the multi-currency redemption users and setting the batch extension of the Charge authorization period for multiple multi-currency redemption users to a preset time, the method further includes: In response to the fact that the actual time difference between the current time and the preset expiration time of the Charge authorization is less than the preset time difference, the warning information of Charge expiration and corresponding foreign currency reversal restriction is sent to the client corresponding to the multi-currency reversal user in a preset manner. In response to a change in the Charge status corresponding to the Charge authorization, the Charge status change and the corresponding reimbursement permission information are sent to the client corresponding to the multi-currency reimbursement user in a preset manner.

[0007] In one possible implementation, the method further includes: A batch investigation is conducted on the historical foreign currency loan packages generated before the Charge was closed in the Charge state. The historical foreign currency loan packages are marked with their status, and the generation time, corresponding user, and corresponding amount associated with each historical foreign currency loan package are also marked. Historical loan package ledger data is generated. Based on the historical loan package ledger data, a dedicated write-off channel is provided for the historical foreign currency loan packages, so that the historical loan packages can be written off through the dedicated write-off channel, and the ledger status corresponding to the historical loan package ledger data is automatically updated after the write-off process is completed.

[0008] In one possible implementation, after performing a batch review of historical foreign currency loan portfolios generated before the Charge was closed in the Charge state, the following is also included: Based on the number of Charge authorization changes, the number of times the reconciliation verification was blocked, the number of Charge authorization changes, the number of reconciliation verification blocking times, the reduction in invalid reimbursement forms, the reconciliation processing progress of the historical foreign currency loan packages, and the reduction in invalid reimbursement forms, the analysis is performed according to the time range to identify high-frequency blocking scenarios and user adaptation issues that exceed the preset frequency. Based on the high-frequency blocking scenarios and user adaptation issues, an optimized management strategy is generated for the multi-currency reconciliation users.

[0009] In one possible implementation, in response to the determination of multi-currency reimbursement users, the authorization period of Charge authorization for multiple multi-currency reimbursement users is extended in batches to a preset time. The latest Charge status corresponding to the extended authorization period is synchronized to the expense control management system in real time. Based on the Charge status, a status identifier is generated through the expense control management system, including: In response to the determination of multi-currency redemption users, the authorization period of the Charge authorization for multiple multi-currency redemption users is extended in batches to a preset time, generating an authorization change record of the Charge authorization and the latest Charge status corresponding to the extended authorization period; the authorization change record includes the operator, operation time, original authorization period, and new authorization period; Based on the Charge status and the authorization change record, the multi-currency redemption Charge product will be removed from the activation list to prevent new users from applying for activation. The latest Charge status corresponding to the extended authorization period will be synchronized to the expense control management system in real time, so as to perform reimbursement permission verification based on the latest Charge status; Based on the Charge status, the existing user authorization status is marked through the expense control management system. A status identifier for the Charge status is generated for each multi-currency redemption user, and the status identifier is associated with the user's foreign currency loan package data to form an association between the multi-currency redemption user, the Charge status identifier, and the user's foreign currency loan package data.

[0010] In one possible implementation, the response to the reimbursement addition operation performed for the target multi-currency reimbursement user among multiple multi-currency reimbursement users involves verifying the Charge status and the loan package currency corresponding to the target multi-currency reimbursement user based on the status identifier, and obtaining a verification result, including: In response to the reimbursement addition operation performed for the target multi-currency reimbursement user among multiple multi-currency reimbursement users, the system verifies whether the Charge status is Charge closed and whether the loan package currency corresponding to the target multi-currency reimbursement user is a foreign currency based on the association relationship, and obtains the verification result.

[0011] In one possible implementation, after the statement adds an operation in response to the target multi-currency reimbursement user among the multiple multi-currency reimbursement users, verifies the Charge status and the loan package currency corresponding to the target multi-currency reimbursement user based on the status identifier, and obtains the verification result, the method further includes: In response to the verification result indicating that the Charge status is Charge enabled and the loan package currency is a foreign currency, same-currency reconciliation data processing is performed based on the reconciliation addition operation and the user's foreign currency loan package data. In response to the Charge status being closed in the verification result, the selection entry for foreign currency loan packages is automatically blocked and only the local currency loan package is allowed to be selected, so as to intercept invalid operations from the source; In response to expense reports that have selected a foreign currency loan package before Charge is closed, a verification is triggered again upon submission. The verification is determined to be an invalid operation without verification authority, and the verification is blocked. A status change message for the Charge status is displayed.

[0012] Secondly, this application provides a multi-currency reconciliation data management device based on Charge status, comprising: The synchronization module is used to respond to the determination of multi-currency reimbursement users, set the batch extension of the authorization period of the Charge authorization of multiple multi-currency reimbursement users to a preset time, synchronize the latest Charge status corresponding to the extended authorization period to the expense control management system in real time, and generate a status identifier through the expense control management system based on the Charge status. The verification module is used to respond to the verification addition operation performed for the target multi-currency verification user among the multiple multi-currency verification users, and to verify the Charge status and the loan package currency corresponding to the target multi-currency verification user based on the status identifier, so as to obtain the verification result; The interception module is used to determine that the reimbursement addition operation is an invalid operation without reimbursement authority and to intercept the reimbursement addition operation in response to the verification result that the Charge status is Charge off and the currency of the loan package is foreign currency; The recommendation module is used to perform functional compatibility verification by comparing the user business scenarios of multiple multi-currency redemption users, and to obtain and recommend multi-currency management functions that are compatible with the user business scenarios of the target multi-currency redemption user.

[0013] Thirdly, this application also provides an electronic device, including a memory and a processor, wherein the memory stores a computer program that can run on the processor, and the processor executes the computer program to implement the method described in the first aspect above.

[0014] Fourthly, this application also provides a computer-readable storage medium storing computer-executable instructions that, when invoked and executed by a processor, cause the processor to perform the method described in the first aspect above.

[0015] This application brings the following beneficial effects: This application provides a method and apparatus for managing multi-currency reimbursement data based on Charge status. In response to the determination of multi-currency reimbursement users, it sets the batch extension of the Charge authorization period for multiple multi-currency reimbursement users to a preset time, and synchronizes the latest Charge status corresponding to the extended authorization period to the expense control management system in real time. A status identifier is generated through the expense control management system based on the Charge status. In response to a reimbursement addition operation performed on a target multi-currency reimbursement user among the multiple multi-currency reimbursement users, it verifies the Charge status and the loan package currency corresponding to the target multi-currency reimbursement user based on the status identifier, obtaining a verification result. In response to the verification result indicating that the Charge status is "Charge Off" and the loan package currency is a foreign currency, it confirms the reimbursement addition operation. Invalid operations lacking reimbursement authority are identified and the reimbursement addition operation is intercepted. Functional compatibility is verified by comparing the user business scenarios of multiple multi-currency reimbursement users to obtain and recommend multi-currency management functions suitable for the target multi-currency reimbursement user's corresponding user business scenario. In this solution, the Charge status and foreign currency loan package are linked for control. The Charge status and loan package currency are verified in real time. When Charge is closed, the selection of foreign currency loan packages is automatically blocked. This establishes a pre-reimbursement Charge status verification process to pre-verify the matching between the Charge status and the loan package currency, thereby identifying invalid reimbursement operations and intercepting them in advance. This optimizes the reimbursement process, reduces invalid expense reports, significantly lowers maintenance costs and business process redundancy, and ultimately achieves precise, smooth, and consistent multi-currency reimbursement process control.

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

[0017] To more clearly illustrate the technical solutions in the specific embodiments of this application or 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 this application. For those skilled in the art, other drawings can be obtained from these drawings without creative effort.

[0018] Figure 1 A flowchart illustrating the multi-currency reconciliation data management method based on Charge status provided in this application embodiment; Figure 2Another flowchart illustrating the multi-currency reconciliation data management method based on Charge status provided in this application embodiment; Figure 3 A schematic diagram of a multi-currency reconciliation data management and control device based on Charge status is provided in this application embodiment; Figure 4 A schematic diagram of the structure of an electronic device provided in an embodiment of this application is shown. Detailed Implementation

[0019] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the technical solutions of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0020] The terms "comprising" and "having," and any variations thereof, used in the embodiments of this application, are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or device that includes a series of steps or units is not limited to the steps or units listed, but may optionally include other steps or units not listed, or may optionally include other steps or units inherent to these processes, methods, products, or devices.

[0021] Currently, the multi-currency reimbursement function is activated through Charge, a feature in its limited rollout phase. After activation, customers can configure foreign currency options in loan applications and expense reports to enable borrowing and reimbursement in the original currency. However, as some customers' Charge expires and is closed, the existing system has revealed numerous management deficiencies, leading to a surge in invalid expense reports and increased costs for data recovery, making it difficult to meet the needs of refined expense control management. The existing technology suffers from the following problems: Lack of control after Charge closure leads to frequent invalid reimbursements: After the existing system's multi-currency reimbursement Charge expires and is closed, it does not restrict the selection permission of foreign currency loan packages. Users can still select foreign currency loan packages in the reimbursement form, but the reimbursement cannot be completed, resulting in a large number of invalid reimbursement forms being submitted. The development team needs to manually modify the database to repair the data, wasting operation and maintenance resources.

[0022] Insufficient functional adaptability and confusion with multi-currency corporate entities: The existing system does not clearly define the functional boundaries between multi-currency reconciliation and multi-currency corporate entities. Although both support the creation of foreign currency loan packages, the fixed document currency of multi-currency corporate entities is associated with the corporate entity's local currency, which cannot meet customers' original currency reconciliation needs. Furthermore, no scenario recommendations are provided for adaptability differences, leading to customers misusing the function.

[0023] Lack of proactive early warning and notification mechanism, resulting in delayed information delivery: The existing system does not have proactive notification settings for Charge expiration status, so customers and employees cannot know in advance that the function will be closed. There is also no clear prompt after Charge is closed, which leads to employees submitting invalid expense reports by mistake, resulting in low efficiency in information delivery.

[0024] Inconsistent prompting logic across multiple terminals leads to a poor user experience: The existing system lacks unified rules for multi-currency redemption prompts on the PC and APP sides. In some scenarios, the mobile terminal does not synchronously display the Charge status and redemption restrictions, causing cognitive biases for users when operating across terminals and affecting the control effect.

[0025] The lack of Charge status verification leads to vulnerabilities in the reimbursement process: The existing reimbursement forms have added a reimbursement step, but the correlation between the Charge status and the loan package currency is not verified. The result is only fed back after the reimbursement fails, and invalid operations are not intercepted in advance, resulting in redundant business processes and reduced reimbursement efficiency.

[0026] There is no standardized process for handling historical foreign currency loan portfolios: After Charge is closed, there is no unified processing mechanism for the generated historical foreign currency loan portfolios. There is neither a write-off channel nor a status indicator, which results in customer loan portfolios being outstanding for a long time, affecting the accuracy of financial accounting.

[0027] The function authorization management is rigid and lacks a long-term adaptation solution: The existing multi-currency reimbursement function relies on short-term Charge authorization. Customers need to reapply after the authorization expires, and there is no convenient way to extend the authorization in batches. New customers cannot activate this function, resulting in insufficient adaptability and scalability.

[0028] Based on this, the embodiments of this application provide a method and apparatus for managing multi-currency reconciliation data based on Charge status. This method can solve technical problems such as high maintenance resource costs caused by large amounts of repair data.

[0029] The embodiments of the present invention will be further described below with reference to the accompanying drawings.

[0030] Figure 1 This is a flowchart illustrating a multi-currency reconciliation data management method based on Charge status, provided as an embodiment of this application. Figure 1 As shown, the method includes: Step S110: In response to the determination of multi-currency reimbursement users, the authorization period of Charge authorization for multiple multi-currency reimbursement users is extended in batches to a preset time. The latest Charge status corresponding to the extended authorization period is synchronized to the expense control management system in real time. A status identifier is generated through the expense control management system based on the Charge status.

[0031] It's important to note that in e-commerce or payment processing (such as IBM Sterling Order Management), Charge authorization refers to the process of freezing and verifying funds for a payment request (such as a credit card). The process is as follows: after an order is generated, the system sends an authorization request to the payment gateway to verify whether the account has sufficient funds. The status is marked as follows: if the authorization is successful, the payment status changes to AUTHORIZED; if it fails (e.g., due to a mismatch in amounts), it is marked as ERROR. The revocation mechanism is that unused authorizations must be actively revoked; otherwise, additional fees may be charged. In this scenario, Charge is a verb, meaning to deduct or charge, and authorization is a prerequisite verification step.

[0032] In this step, for example, during the Charge authorization and status management phase: the administrator filters existing customers who have activated multi-currency redemption through the system backend, extends their Charge authorization to 2099 in batches, and removes the product from the market to prevent new customers from activating it; the Charge status (activated / activated) is synchronized to the expense control management system in real time, and a status identifier is generated and persistently stored.

[0033] As one possible implementation, in response to the determination of multi-currency reimbursement users, the authorization period for the Charge authorization of multiple multi-currency reimbursement users is extended in batches to a preset time. The latest Charge status corresponding to the extended authorization period is then synchronized to the expense control management system in real time. Based on the Charge status, a status identifier is generated through the expense control management system, such as... Figure 2 As shown, the specific steps may include the following: Step S210: In response to the determination of multi-currency redemption users, the authorization period of Charge authorization for multiple multi-currency redemption users is extended to a preset time in batches, and an authorization change record of Charge authorization and the latest Charge status corresponding to the extended authorization period are generated; the authorization change record includes the operator, operation time, original authorization period, and new authorization period; Step S220: Based on the Charge status and authorization change record, remove the multi-currency redemption Charge product from the activation list so that new users are prohibited from applying for activation; Step S230: After the authorization period is extended, the latest Charge status is synchronized to the expense control management system in real time so as to perform reimbursement permission verification based on the latest Charge status. Step S240: Based on the Charge status, the authorization status of existing users is marked through the expense control management system. A status identifier of Charge status is generated for each multi-currency reimbursement user, and the status identifier is associated with the user's foreign currency loan package data to form a relationship between multi-currency reimbursement users, Charge status identifiers, and user foreign currency loan package data.

[0034] For batch management of Charge authorizations, for example, existing customers' Charge authorizations can be extended to 2099 in batches, and products can be removed from the platform to prevent new customers from opening accounts, thus achieving long-term control and standardized permissions. By optimizing the function authorization management scheme, it is possible to support the batch extension of existing customers' Charge authorizations, ensuring long-term functionality availability, i.e., improving long-term usability. At the same time, removing products from the platform and standardizing the permissions for new customers balances the needs of existing customers with system control, improving system scalability.

[0035] In practical applications, the Charge status management module is the foundation for implementing multi-currency reimbursement control. For example, its core functions include batch operation authorization for Charge, real-time status synchronization, and status identifier management, supporting long-term control and precise adaptation, and improving functional usability.

[0036] For Charge authorization batch operations, batch authorization extension: Administrators can filter existing customers who have opened multi-currency reimbursement (Charge111002) through the backend and extend their authorization period to 2099 in batches, generating authorization change records (including operator, operation time, original period, and new period) to ensure long-term availability of the function; after the authorization is extended, it will be automatically synchronized to the customer's expense control account without the need for manual operation by the customer.

[0037] For product delisting control, for example, multi-currency redemption Charge products can be removed from the activation list, new customers are prohibited from applying for activation, and the authorization status of existing customers (permanent authorization / temporary authorization) can be marked to facilitate administrator classification and management.

[0038] For example, the Charge authorization status query function can be provided, which supports filtering by customer name, account, authorization period and other conditions, and displays information such as authorization status, expiration time and change records in real time, so as to facilitate efficient management by administrators.

[0039] For real-time status synchronization and identification, an exemplary status synchronization mechanism is as follows: Charge status (on / off) is synchronized in real time through the expense control platform interface, with a synchronization delay of ≤10 seconds, ensuring that reimbursement permission verification is based on the latest status; when the Charge status changes, an internal system status update is automatically triggered, synchronizing to all related modules. Status identification rules: A Charge status identifier (CHARGE_OPEN / CHARGE_CLOSED) is configured for each customer, associated with the customer's foreign currency loan package data, forming a "customer-Charge status-loan package" relationship, providing data support for reimbursement permission verification.

[0040] Step S120: In response to the reimbursement addition operation performed for the target multi-currency reimbursement user among multiple multi-currency reimbursement users, the Charge status and the loan package currency corresponding to the target multi-currency reimbursement user are verified based on the status identifier to obtain the verification result.

[0041] For example, during the pre-reimbursement verification phase, when a user fills out an expense report and clicks "Add Reimbursement," the reimbursement permission verification module verifies the Charge status and the loan package currency in real time. The reimbursement permission verification module implements linked verification of the Charge status and the loan package currency.

[0042] In one optional implementation, the above response to the reimbursement addition operation performed for the target multi-currency reimbursement user among multiple multi-currency reimbursement users, verifies the Charge status and the loan package currency corresponding to the target multi-currency reimbursement user based on the status identifier, and obtains the verification result, which may specifically include the following steps: In response to the reimbursement addition operation performed for the target multi-currency reimbursement user among multiple multi-currency reimbursement users, the system verifies whether the Charge status is Charge closed based on the association relationship, and whether the currency of the loan package corresponding to the target multi-currency reimbursement user is a foreign currency, and obtains the verification result.

[0043] In practical applications, the reimbursement permission verification module is responsible for linking Charge status and loan package information to achieve accurate verification and interception of invalid operations before reimbursement, ensuring a smooth reimbursement process and reducing invalid reimbursement forms. For the dual verification before reimbursement, for example, status and currency verification: when a user selects a loan package and clicks "Confirm" for reimbursement, the system automatically verifies two conditions: ① whether the loan package is in a foreign currency (not the local currency); ② whether the customer's multi-currency reimbursement Charge is closed.

[0044] As another optional implementation, in response to the addition operation performed for the target multi-currency reimbursement user among multiple multi-currency reimbursement users, after verifying the Charge status and the loan package currency corresponding to the target multi-currency reimbursement user based on the status identifier and obtaining the verification result, the method may further include the following steps: In response to the verification result showing that the Charge status is Charge enabled and the loan package currency is a foreign currency, the same currency reversal data processing is performed based on the reversal addition operation and the user's foreign currency loan package data. In response to the Charge status being closed in the verification result, the selection entry for the foreign currency loan package is automatically blocked and only the local currency loan package is allowed to be selected, so as to intercept invalid operations from the source; In response to expense reports that had selected a foreign currency loan package before Charge was closed, a verification was triggered again upon submission. The verification was determined to be an invalid operation for which the author did not have the authority to perform the verification, and the verification was blocked. A status change message for Charge was displayed.

[0045] For dynamic management of reimbursement permissions, the following example demonstrates the permission linkage logic: When Charge is enabled, users are allowed to select a foreign currency loan package and complete reimbursement in the same currency; when Charge is disabled, the foreign currency loan package selection entry is automatically blocked (or the foreign currency loan package is grayed out), allowing only the selection of the local currency loan package, thus intercepting invalid operations at the source. For adaptation to special scenarios: For reimbursement forms where a foreign currency loan package has been selected before Charge is disabled, verification is triggered again upon submission, intercepting the submission and indicating a status change, preventing invalid documents from circulating.

[0046] In step S130, in response to the verification result showing that the Charge status is closed and the currency of the loan package is a foreign currency, it is determined that the reimbursement addition operation is an invalid operation without reimbursement authority and the reimbursement addition operation is blocked.

[0047] In one alternative implementation, if Charge is closed and the loan package is in foreign currency, the operation is intercepted and a prompt is triggered. For example, the system automatically verifies two conditions: ① whether the loan package is in foreign currency (not the local currency); ② whether the customer's multi-currency reconciliation Charge is closed; interception and a pop-up prompt are triggered only if ① is yes and ② is no.

[0048] Step S140: By comparing the user business scenarios of multiple multi-currency reconciliation users, functional compatibility verification is performed to obtain and recommend multi-currency management functions that are compatible with the user business scenarios of the target multi-currency reconciliation user.

[0049] In this step, the functional compatibility verification module compares the customer's business scenarios and recommends suitable multi-currency management functions. For example, the functional compatibility verification module clarifies the functional boundaries between multi-currency reconciliation and multi-currency management of legal entities, realizes scenario-based function recommendations, improves functional compatibility, and avoids customer misuse.

[0050] For the functional differences, the differences are clearly marked as follows: a new functional comparison page has been added to the system to clarify the commonalities (support for creating foreign currency loan packages and same-currency reconciliation) and differences (legal entities with multiple currencies are associated with the local currency fixed document currency, and multi-currency reconciliation supports reconciliation in the original currency), and scenario examples are provided to help users understand.

[0051] For real-time compatibility verification, for example, when a user activates multi-currency related functions, the system automatically verifies the customer's business scenario (such as whether original currency resale is required, or whether a fixed currency is used for legal entities), recommends compatible functions, and if the customer's scenario does not match the selected function, it prompts the differences in the mismatch scenario and provides adjustment suggestions.

[0052] For customer scenario research and feedback, for example, for corporate entities that are not compatible with multiple currencies, the system provides a scenario research entry point to collect details of the customer's original currency reconciliation needs, providing data support for subsequent function merging and optimization, and improving function adaptability.

[0053] For the compatibility verification logic of multi-currency reconciliation function, the functional boundaries between multi-currency reconciliation and multi-currency transactions within legal entities are clearly defined. Based on customer business scenarios, compatible functions are automatically recommended to reduce the probability of misuse. By clarifying the functional boundaries between multi-currency reconciliation and multi-currency transactions within legal entities, a compatibility verification mechanism is constructed to automatically recommend functions that match business scenarios, improving functional compatibility. The functional compatibility verification module identifies the differences between the two functions and recommends suitable scenarios, reducing the probability of customer misuse, adapting to the multi-currency management needs of different customers (such as original currency reconciliation and fixed legal entity base currency), improving functional usability, clarifying functional boundaries, and enhancing compatibility.

[0054] By linking Charge status with foreign currency loan packages for control, the system verifies the Charge status and loan package currency in real time. When Charge is closed, the selection of foreign currency loan packages is automatically disabled. In other words, by establishing a Charge status verification process before reconciliation, the system verifies the compatibility between Charge status and loan package currency in advance, intercepts invalid reconciliation operations in advance, optimizes the reconciliation process, and reduces invalid reimbursement reports by more than 90%. This avoids the need for manual data repair by R&D, significantly reduces operation and maintenance costs and business process redundancy, and ultimately achieves precise, smooth, and consistent control of the entire multi-currency reconciliation process, reducing invalid operations and operation and maintenance costs.

[0055] This application embodiment integrates a multi-currency reconciliation intelligent system encompassing "Charge status management, reconciliation permission verification, multi-terminal collaboration, proactive message notification, and historical data processing." The core idea is to build a management system based on an enterprise expense control management platform, comprising six core modules: Charge status management, reconciliation permission verification, functional compatibility verification, multi-terminal collaboration, message notification, and historical data processing. The Charge status management module enables authorization extension and real-time status synchronization; the reconciliation permission verification module links Charge status with the loan package currency to proactively intercept invalid operations; the functional compatibility verification module clarifies the boundaries of two main functions and recommends suitable scenarios; the multi-terminal collaboration module ensures consistent cross-terminal notification logic; the message notification module proactively communicates Charge status; and the historical data processing module standardizes the handling of historical loan packages. Ultimately, this achieves precise, streamlined, and consistent multi-currency reconciliation process control, reducing invalid operations and maintenance costs.

[0056] In some embodiments, after determining that the reimbursement addition operation is an invalid operation without reimbursement authority and blocking the reimbursement addition operation in response to the verification result showing that the Charge status is Charge closed and the loan package currency is a foreign currency, the method may further include the following steps: Generate prompts for intercepting and adding verification operations, and synchronize the prompts and Charge status to the PC and APP via a distributed database to adapt to the display size and layout of different terminals and ensure that the prompt logic and display effect are consistent across different terminals.

[0057] During the multi-terminal collaborative display phase, the multi-terminal collaboration module synchronizes Charge status and reimbursement restriction prompts to both the PC and APP terminals, adapting to different terminal screen sizes and display layouts to ensure consistent prompt logic and display effects on both ends. For example, the verification prompt standard is as follows: the pop-up title is uniformly "Unable to reimburse foreign currency loan package," and the text is "Multi-currency reimbursement function is not enabled, unable to reimburse foreign currency loan package, please contact the enterprise administrator," ensuring that the prompt is clear and easy to understand, guiding users to operate correctly.

[0058] For example, the multi-terminal collaboration module is responsible for unifying the multi-currency reimbursement control logic and display effects across the PC and APP platforms, adapting to different terminal operating habits, and ensuring a consistent user experience across terminals. For PC adaptation: The PC reimbursement form page uses a drawer-style reimbursement pop-up window. Foreign currency loan packages are grayed out and marked "Function not enabled, cannot be reimbursed" when Charge is closed, triggering an immediate prompt when selected. It supports filtering loan packages by currency, displaying local currency and foreign currency loan packages separately, and is compatible with mainstream browsers (Chrome, Edge, Firefox, etc.) to ensure normal verification and prompt effects. For APP adaptation: The APP uses a simple list-style display of loan packages. Foreign currency loan packages are hidden or marked with a restriction label when Charge is closed. Clicking "Add Reimbursement" triggers a pop-up prompt, with the pop-up style adapted to the mobile screen size, optimizing the touch operation experience. It supports pull-to-refresh to synchronize the latest Charge status and loan package information, ensuring data consistency with the PC platform.

[0059] For multi-terminal data synchronization: A distributed database is used to achieve real-time synchronization of Charge status, loan package information, reimbursement records, and prompt text between the PC and APP, ensuring that the control logic and display effect are consistent when the user operates on any terminal, and avoiding cross-terminal data deviation.

[0060] During the multi-terminal collaborative display phase, ensure that the Charge status, reimbursement restriction prompts, and loan package display logic are consistent between the PC and APP terminals, support real-time data synchronization across terminals, and have a synchronization delay of ≤10 seconds.

[0061] For a multi-terminal collaborative management architecture, ensure consistency in Charge status display, redemption restriction prompts, and data synchronization between the PC and APP ends, guaranteeing a unified cross-terminal experience. By constructing a unified multi-terminal prompt logic, ensure consistency in Charge status display and redemption restriction prompts between the PC and APP ends, optimizing the cross-terminal user experience. In other words, unify the multi-terminal experience and optimize operational convenience: construct a unified multi-terminal management logic and display effect, adapt to different terminal operating habits, ensure consistent information across terminals, and eliminate the need for users to adapt to differentiated operations, improving ease of use and user experience.

[0062] In some embodiments, after determining the multi-currency redemption users and setting the batch extension of the Charge authorization period for multiple multi-currency redemption users to a preset time, the method may further include the following steps: If the actual time difference between the current time and the preset expiration time of the Charge authorization is less than the preset time difference, the warning information of Charge expiration and corresponding foreign currency reversal restrictions will be sent to the client of the multi-currency reversal user in accordance with the preset method. In response to a change in the Charge status corresponding to the Charge authorization, the Charge status change and the corresponding revocation permission information are sent to the client of the multi-currency revocation user according to the preset method.

[0063] During the proactive notification phase, the notification module pushes notifications to customer administrators and employees according to preset methods for Charges that are about to expire or have been closed, clearly informing them of the status change and reimbursement restrictions. The notification module is responsible for proactively pushing notifications of Charge status changes, ensuring that information reaches target users in a timely manner, avoiding misoperations due to information delays, and improving management response efficiency.

[0064] For notification triggering scenarios, examples include: Expiration Warning Notification: 7 days before the Charge expires, an automatic warning notification is pushed to the customer administrator, informing them that the authorization is about to expire and its subsequent impact (such as restrictions on foreign currency remittance), reminding them to handle it promptly. Status Change Notification: After the Charge is closed or the authorization is extended, a status change notification is immediately pushed to the customer administrator and relevant employees, clarifying the current status and remittance permissions to avoid accidental operations.

[0065] Regarding notification methods and content, for example, the notification method selection supports multiple channels such as in-system notifications, WeChat / DingTalk messages, and emails. Notification methods can be selected according to customer configuration. If a push fails, it will automatically retry (up to 3 times) and log the process. Notification content specifications: The notification content includes key information such as customer name, Charge status (expired / closed / authorization extended), effective time, changes in revocation permissions, and operation instructions (e.g., contacting the administrator), ensuring users are clearly aware and can take appropriate action. Notification history tracking: Users can view notification history records, filtering by time range, notification type, and push status to understand past Charge status changes and notification activities, facilitating problem tracing and auditing.

[0066] For example, the proactive message notification phase supports Charge expiration warnings (7 days before expiration) and status change notifications, which are pushed through multiple channels such as in-system notifications, WeChat / DingTalk messages, and emails. If the push fails, it will automatically retry up to 3 times.

[0067] In this embodiment, a proactive notification mechanism is implemented across all scenarios: for scenarios such as Charge expiration and status changes, notifications are pushed through multiple channels to ensure timely information delivery and avoid accidental operations. By adding a proactive Charge status notification mechanism, expiration warnings and shutdown reminders are supported, ensuring that information reaches customers and employees in a timely manner and avoiding accidental operations. In short, proactive notification ensures timely delivery and avoids accidental operations: the multi-channel, all-scenario Charge status notification mechanism ensures that customers and employees are promptly informed of status changes and write-off restrictions, allowing them to make advance business adjustments and avoid accidental operations due to information delays, thus improving the foresight of management.

[0068] In some embodiments, the method may further include the following steps: performing batch screening of historical foreign currency loan packages generated before the Charge was closed in the Charge state; marking the status of the historical foreign currency loan packages and marking the generation time, corresponding user, and corresponding amount associated with the historical foreign currency loan packages; generating historical loan package ledger data; providing a dedicated write-off channel for the historical foreign currency loan packages based on the historical loan package ledger data, so that the historical loan packages can be written off through the dedicated write-off channel, and automatically updating the ledger status corresponding to the historical loan package ledger data after the write-off process is completed.

[0069] During the historical data processing phase, the historical data processing module conducts batch reviews of foreign currency loan packages generated before Charge closure, marks their status, and provides a compliant write-off channel to ensure the orderly disposal of historical loan packages. The historical data processing and operations module is responsible for standardizing the disposal of historical foreign currency loan packages after Charge closure, providing visualized operations and maintenance monitoring functions to support efficient management by administrators and reduce maintenance costs. This strengthens operations and maintenance management and improves system stability: a visualized operations and maintenance dashboard and anomaly alarm mechanism enable real-time monitoring of management status and rapid fault location, reducing fault troubleshooting time by more than 60%.

[0070] Regarding the handling of historical foreign currency loan packages: Batch screening and labeling: The system automatically conducts batch screening of foreign currency loan packages generated before Charge closure, labels them as "historical foreign currency loan packages," and associates information such as generation time, corresponding customer, and amount (original currency / base currency) to form a historical loan package ledger. Compliance write-off channel: A dedicated write-off channel is provided for historical foreign currency loan packages, supporting customers to complete write-offs through compliant means such as supplementing materials and adjusting write-off methods, avoiding long-term outstanding balances; the ledger status is automatically updated after write-off to ensure accurate financial accounting. The above historical data processing stage automatically conducts batch screening of foreign currency loan packages generated before Charge closure, labels their status, forms a ledger, and provides a compliant write-off channel to ensure the orderly handling of historical loan packages. In short, the historical foreign currency loan package handling system: batch screening and labeling of historical loan packages, providing a compliant write-off channel, resolving outstanding balance issues, and ensuring accurate financial accounting.

[0071] The historical foreign currency loan portfolio processing mechanism supports compliant write-off and status identification of historical loan portfolios after Charge is closed, ensuring the accuracy of financial accounting. This standardizes the handling of historical data and ensures financial accuracy: through batch screening, labeling, and compliant write-off channels for historical foreign currency loan portfolios, it resolves the issue of outstanding historical loan portfolios, ensuring the accuracy of financial accounting and improving the standardization of expense control management.

[0072] As another possible implementation, during the control execution and logging phase, the system performs reconciliation permission control based on Charge status, recording reconciliation operations, status changes, and prompt triggers in real time. It supports queries by time, user, and business document, facilitating auditing and problem tracing. For anomaly monitoring and logging, for example, it monitors in real time for Charge status synchronization anomalies, reconciliation verification failures, and notification push anomalies, triggering anomaly alarms and pushing them to operations personnel. Alarm information includes the anomaly type, details, and associated customer / document ID, facilitating rapid troubleshooting. Operation logs and anomaly logs are retained for more than 6 months, supporting multi-condition queries and exports to meet auditing requirements. Therefore, it improves the log traceability system, ensures business auditing and problem tracing, and reduces operational risks.

[0073] In some embodiments, after performing a batch review of historical foreign currency loan packages generated before the Charge was closed in the Charge state, the method may further include the following steps: Based on the number of Charge authorization changes, the number of times blocked through reconciliation verification, the number of Charge authorization changes, the number of times reconciliation verification is blocked, the reduction of invalid reimbursement forms, the reconciliation processing progress of historical foreign currency loan packages, and the reduction of invalid reimbursement forms, the analysis is carried out according to the time range to identify high-frequency blocking scenarios and user adaptation issues that exceed the preset frequency. Based on the high-frequency blocking scenarios and user adaptation issues, optimized management strategies for multi-currency reconciliation users are generated.

[0074] For example, a visual operations and maintenance dashboard can display key indicators in real time, such as the number of Charge authorization changes, the number of reimbursement verification interceptions, the reduction in invalid expense reports, and the processing progress of historical loan packages. It can also perform statistical analysis by time range (day / week / month) to identify high-frequency interception scenarios, customer compatibility issues, etc., to help administrators optimize management and control strategies.

[0075] Figure 3 A schematic diagram of a multi-currency reconciliation data management device based on Charge status is provided. Figure 3 As shown, the multi-currency reconciliation data management device 300 based on Charge status includes: Synchronization module 301 is used to respond to the determination of multi-currency reimbursement users, set the batch extension of the authorization period of the Charge authorization of multiple multi-currency reimbursement users to a preset time, synchronize the latest Charge status corresponding to the extended authorization period to the expense control management system in real time, and generate a status identifier through the expense control management system based on the Charge status. Verification module 302 is used to respond to the verification addition operation performed for the target multi-currency verification user among the multiple multi-currency verification users, and to verify the Charge status and the loan package currency corresponding to the target multi-currency verification user based on the status identifier to obtain the verification result; The interception module 303 is used to determine that the reimbursement addition operation is an invalid operation without reimbursement authority and to intercept the reimbursement addition operation in response to the verification result that the Charge status is Charge off and the currency of the loan package is foreign currency. The recommendation module 304 is used to perform functional compatibility verification by comparing the user business scenarios of multiple multi-currency reconciliation users, and to obtain and recommend multi-currency management functions that are compatible with the user business scenarios of the target multi-currency reconciliation user.

[0076] The multi-currency reconciliation data management device based on Charge state provided in this application embodiment has the same technical features as the multi-currency reconciliation data management method based on Charge state provided in the above embodiment, so it can also solve the same technical problems and achieve the same technical effects.

[0077] An electronic device provided in this application embodiment, such as Figure 4 As shown, the electronic device 400 includes a processor 402 and a memory 401. The memory stores a computer program that can run on the processor. When the processor executes the computer program, it implements the steps of the method provided in the above embodiments.

[0078] See Figure 4 The electronic device also includes a bus 403 and a communication interface 404. The processor 402, the communication interface 404 and the memory 401 are connected via the bus 403. The processor 402 is used to execute executable modules, such as computer programs, stored in the memory 401.

[0079] The memory 401 may include high-speed random access memory (RAM) or 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 404 (which can be wired or wireless), such as the Internet, wide area network, local area network, or metropolitan area network.

[0080] Bus 403 can be an ISA bus, PCI bus, or EISA bus, etc. The bus can be divided into address bus, data bus, control bus, etc. For ease of representation, Figure 4The 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.

[0081] The memory 401 is used to store programs. After receiving an execution instruction, the processor 402 executes the program. The method executed by the apparatus defined by the process disclosed in any of the preceding embodiments of this application can be applied to the processor 402 or implemented by the processor 402.

[0082] Processor 402 may be an integrated circuit chip with signal processing capabilities. In implementation, each step of the above method can be completed by the integrated logic circuitry in the hardware of processor 402 or by instructions in software form. The processor 402 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. It can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the methods disclosed in the embodiments of this application can be directly manifested as execution by a hardware decoding processor, or execution by a combination of hardware and software modules in the decoding processor. The software module can reside in a mature storage medium in the field, such as random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, or registers. This storage medium is located in memory 401, and processor 402 reads the information from memory 401 and, in conjunction with its hardware, completes the steps of the above method.

[0083] Corresponding to the above-described method for managing multi-currency reconciliation data based on Charge state, this application also provides a computer-readable storage medium storing computer-executable instructions. When these computer-executable instructions are invoked and executed by a processor, they cause the processor to perform the steps of the above-described method for managing multi-currency reconciliation data based on Charge state.

[0084] The multi-currency reconciliation data management device based on Charge status provided in this application embodiment can be specific hardware on the device or software or firmware installed on the device. The implementation principle and technical effects of the device provided in this application embodiment are the same as those in the foregoing method embodiments. For the sake of brevity, any parts not mentioned in the device embodiment can be referred to the corresponding content in the foregoing method embodiments. Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can all be referred to the corresponding processes in the above method embodiments, and will not be repeated here.

[0085] In the embodiments provided in this application, it should be understood that the disclosed apparatus and methods can be implemented in other ways. The apparatus embodiments described above are merely illustrative. For example, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. Furthermore, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Additionally, the displayed or discussed mutual couplings, direct couplings, or communication connections may be through some communication interfaces; indirect couplings or communication connections between devices or units may be electrical, mechanical, or other forms.

[0086] For example, the flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of apparatus, methods, and computer program products according to various embodiments of this application. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions marked in the blocks may occur in a different order than those marked in the drawings. For example, two consecutive blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in a block diagram and / or flowchart, and combinations of blocks in block diagrams and / or flowcharts, can be implemented using a dedicated hardware-based system that performs the specified function or action, or using a combination of dedicated hardware and computer instructions.

[0087] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0088] In addition, the functional units in the embodiments provided in this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0089] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, 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 multi-currency reconciliation data management method based on Charge state described in various embodiments of this application. 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.

[0090] It should be noted that similar labels and letters in the following figures indicate similar items. Therefore, once an item is defined in one figure, it does not need to be further defined and explained in subsequent figures. In addition, the terms "first", "second", "third", etc. are used only to distinguish descriptions and should not be construed as indicating or implying relative importance.

[0091] Finally, it should be noted that the above-described embodiments are merely specific implementations of this application, used to illustrate the technical solutions of this application, and not to limit them. The protection scope of this application is not limited thereto. Although this application 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, or make equivalent substitutions for some of the technical features, within the scope of the technology disclosed in this application; and these modifications, changes, or substitutions do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of this application. All should be covered within the protection scope of this application. Therefore, the protection scope of this application should be determined by the protection scope of the claims.

Claims

1. A method for managing multi-currency reconciliation data based on Charge status, characterized in that, The method includes: In response to the determination of multi-currency reimbursement users, the authorization period of the Charge authorization for multiple multi-currency reimbursement users is extended in batches to a preset time. The latest Charge status corresponding to the extended authorization period is synchronized to the expense control management system in real time. A status identifier is generated through the expense control management system based on the Charge status. In response to the reimbursement addition operation performed for the target multi-currency reimbursement user among multiple multi-currency reimbursement users, the Charge status and the loan package currency corresponding to the target multi-currency reimbursement user are verified based on the status identifier to obtain the verification result; In response to the verification result indicating that the Charge status is closed and the currency of the loan package is a foreign currency, the verification addition operation is determined to be an invalid operation without verification authority and the verification addition operation is blocked. By comparing the user business scenarios of multiple multi-currency reconciliation users to verify functional compatibility, multi-currency management functions that are compatible with the user business scenarios of the target multi-currency reconciliation user are obtained and recommended.

2. The method according to claim 1, characterized in that, After determining that the charge status is "Charge Off" and the loan package currency is a foreign currency in the response to the verification result, and after intercepting the reimbursement addition operation as an invalid operation without reimbursement authority, the process further includes: A prompt message is generated to intercept the cancellation and addition operation, and the prompt message and the Charge status are synchronized to the PC and APP through a distributed database to adapt to the display size and display layout of different terminals and ensure that the prompt logic and display effect are consistent across different terminals.

3. The method according to claim 1, characterized in that, After determining the multi-currency redemption users and setting the batch extension of the Charge authorization period for multiple multi-currency redemption users to a preset time, the method further includes: In response to the fact that the actual time difference between the current time and the preset expiration time of the Charge authorization is less than the preset time difference, the warning information of Charge expiration and corresponding foreign currency reversal restriction is sent to the client corresponding to the multi-currency reversal user in a preset manner. In response to a change in the Charge status corresponding to the Charge authorization, the Charge status change and the corresponding reimbursement permission information are sent to the client corresponding to the multi-currency reimbursement user in a preset manner.

4. The method according to claim 1, characterized in that, The method further includes: A batch investigation is conducted on the historical foreign currency loan packages generated before the Charge was closed in the Charge state. The historical foreign currency loan packages are marked with their status, and the generation time, corresponding user, and corresponding amount associated with each historical foreign currency loan package are also marked. Historical loan package ledger data is generated. Based on the historical loan package ledger data, a dedicated write-off channel is provided for the historical foreign currency loan packages, so that the historical loan packages can be written off through the dedicated write-off channel, and the ledger status corresponding to the historical loan package ledger data is automatically updated after the write-off process is completed.

5. The method according to claim 4, characterized in that, After performing a batch review of historical foreign currency loan packages generated before the Charge was closed in the Charge state, the process also includes: Based on the number of Charge authorization changes, the number of times the reconciliation verification was blocked, the number of Charge authorization changes, the number of reconciliation verification blocking times, the reduction in invalid reimbursement forms, the reconciliation processing progress of the historical foreign currency loan packages, and the reduction in invalid reimbursement forms, the analysis is performed according to the time range to identify high-frequency blocking scenarios and user adaptation issues that exceed the preset frequency. Based on the high-frequency blocking scenarios and user adaptation issues, an optimized management strategy is generated for the multi-currency reconciliation users.

6. The method according to claim 1, characterized in that, In response to the determination of multi-currency redemption users, the authorization period of Charge authorization for multiple multi-currency redemption users is extended in batches to a preset time. The latest Charge status corresponding to the extended authorization period is synchronized to the expense control management system in real time. Based on the Charge status, a status identifier is generated through the expense control management system, including: In response to the determination of multi-currency redemption users, the authorization period of the Charge authorization for multiple multi-currency redemption users is extended in batches to a preset time, generating an authorization change record of the Charge authorization and the latest Charge status corresponding to the extended authorization period; the authorization change record includes the operator, operation time, original authorization period, and new authorization period; Based on the Charge status and the authorization change record, the multi-currency redemption Charge product will be removed from the activation list to prevent new users from applying for activation. The latest Charge status corresponding to the extended authorization period will be synchronized to the expense control management system in real time, so as to perform reimbursement permission verification based on the latest Charge status; Based on the Charge status, the existing user authorization status is marked through the expense control management system. A status identifier for the Charge status is generated for each multi-currency redemption user, and the status identifier is associated with the user's foreign currency loan package data to form an association between the multi-currency redemption user, the Charge status identifier, and the user's foreign currency loan package data.

7. The method according to claim 6, characterized in that, The response to the reimbursement addition operation performed for the target multi-currency reimbursement user among multiple multi-currency reimbursement users includes verifying the Charge status and the loan package currency corresponding to the target multi-currency reimbursement user based on the status identifier, and obtaining the verification result, including: In response to the reimbursement addition operation performed for the target multi-currency reimbursement user among multiple multi-currency reimbursement users, the system verifies whether the Charge status is Charge closed and whether the loan package currency corresponding to the target multi-currency reimbursement user is a foreign currency based on the association relationship, and obtains the verification result.

8. The method according to claim 6, characterized in that, In response to the reimbursement addition operation performed for the target multi-currency reimbursement user among multiple multi-currency reimbursement users, after verifying the Charge status and the loan package currency corresponding to the target multi-currency reimbursement user based on the status identifier and obtaining the verification result, the method further includes: In response to the verification result indicating that the Charge status is Charge enabled and the loan package currency is a foreign currency, same-currency reconciliation data processing is performed based on the reconciliation addition operation and the user's foreign currency loan package data. In response to the Charge status being closed in the verification result, the selection entry for foreign currency loan packages is automatically blocked and only the local currency loan package is allowed to be selected, so as to intercept invalid operations from the source; In response to expense reports that have selected a foreign currency loan package before Charge is closed, a verification is triggered again upon submission. The verification is determined to be an invalid operation without verification authority, and the verification is blocked. A status change message for the Charge status is displayed.

9. A multi-currency reconciliation data management and control device based on Charge status, characterized in that, include: The synchronization module is used to respond to the determination of multi-currency reimbursement users, set the batch extension of the authorization period of the Charge authorization of multiple multi-currency reimbursement users to a preset time, synchronize the latest Charge status corresponding to the extended authorization period to the expense control management system in real time, and generate a status identifier through the expense control management system based on the Charge status. The verification module is used to respond to the verification addition operation performed for the target multi-currency verification user among the multiple multi-currency verification users, and to verify the Charge status and the loan package currency corresponding to the target multi-currency verification user based on the status identifier, so as to obtain the verification result; The interception module is used to determine that the reimbursement addition operation is an invalid operation without reimbursement authority and to intercept the reimbursement addition operation in response to the verification result that the Charge status is Charge off and the currency of the loan package is foreign currency; The recommendation module is used to perform functional compatibility verification by comparing the user business scenarios of multiple multi-currency redemption users, and to obtain and recommend multi-currency management functions that are compatible with the user business scenarios of the target multi-currency redemption user.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer-executable instructions that, when invoked and executed by a processor, cause the processor to perform the method according to any one of claims 1 to 8.

Images