An account information processing method, device, equipment and product across financial regions
Patent Information
- Application Number
- CN202611091822.4
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2026-07-22
- Publication Date
- 2026-08-28
AI Technical Summary
[0006]本发明的目的是提供一种跨金融区域的账户信息处理方法、装置、计算机设备、计算机可读存储产品及计算机程序产品,用以解决现有传统账户信息处理系统因单一区域固化规则而无法自动适配多金融区域下账号编码格式与机构标识差异化要求,进而导致跨区域资金流转处理效率低下、存在合规风险和/或增加财务管理成本的问题
(1)本发明创造性提供了一种能够在账户建档过程中根据金融区域的差异化要求自动生成符合对应编码格式的账号编码并自动关联该区域下对应机构识别码的新方案,即先获取为多个金融区域分别配置且用于定义账号编码格式的规则参数的账号编码模型,并建立与维护金融机构与金融区域之间的多区域机构编码映射关系;响应于为目标账户建档的操作,获取目标金融区域及目标金融机构;调用对应模型中的规则参数,自动生成符合该区域编码格式的目标账号编码;从映射关系中查询获取目标机构识别码;将目标账号编码与目标机构识别码进行关联,形成账户信息元组并存储,以备在资金流转处理时按金融区域进行信息调用,如此实现了跨金融区域下账号编码与机构识别码的自动生成与关联,解决了传统系统无法自动适配多区域差异化编码格式和机构标识要求的问题,可广泛应用于全球账户统一管理平台中;
Smart Images

Figure CN122656741A_ABST
Abstract
Description
Technical Field
[0001] This invention belongs to the field of computer data processing technology, and specifically relates to a method, apparatus, equipment and product for processing account information across financial regions. Background Technology
[0002] Bank accounts are the core carriers of fund transfers. Different financial management systems in different financial regions (such as different countries or regions) have different standardized requirements for account number coding formats and institutional identification codes. For example, account numbers in different regions differ in total length, segmentation rules, and check digit algorithms. Furthermore, the institutional identification codes (such as SWIFT codes and local clearing system codes) of the same financial institution also vary in different regions.
[0003] Traditional account information processing systems are typically designed for a single financial region. In such systems, account coding rules and institutional identification codes are often hard-coded or fixedly configured and embedded within the system, adapting only to the financial system management requirements of that region. When companies expand their business across national or regional borders, they need to open and manage multiple accounts for the same entity in different financial regions.
[0004] Traditional account creation systems can only generate accounts and associate institutional information based on fixed rules for a single region within the system, failing to automatically adapt to the differentiated coding formats and institutional identification standards of different financial regions. Therefore, when cross-regional fund transfers are involved, the system cannot automatically provide accurate account information matching each financial region. Operators must manually query, convert, and fill in account numbers and institutional identification codes that conform to different regional standards. This not only significantly reduces the processing efficiency of cross-regional fund transfers but also easily introduces errors through manual operation, leading to payment failures, delayed fund arrivals, and even compliance risks, while also increasing the company's financial management costs.
[0005] In summary, there is an urgent need for a new solution that can automatically generate account codes that conform to the corresponding coding format based on the differentiated requirements of financial regions during the account creation process, and automatically associate them with the corresponding institution identification codes in that region. Summary of the Invention
[0006] The purpose of this invention is to provide a method, apparatus, computer equipment, computer-readable storage product, and computer program product for processing account information across financial regions, in order to solve the problem that existing traditional account information processing systems cannot automatically adapt to the differentiated requirements of account coding formats and institutional identification in multiple financial regions due to the fixed rules of a single region, which leads to low efficiency in cross-regional fund transfer processing, compliance risks, and / or increased financial management costs.
[0007] To achieve the above objectives, the present invention adopts the following technical solution: Firstly, a method for processing account information across financial regions is provided, including: Obtain account coding models configured for multiple financial regions, wherein the account coding models contain rule parameters for defining account coding formats that conform to the management requirements of the corresponding financial regions; Establish and maintain a multi-regional institution code mapping relationship between financial institutions and financial regions, wherein the multi-regional institution code mapping relationship is used to record the institution identification code of the same financial institution in different financial regions; In response to the operation of creating a profile for the target account, the target financial region and target financial institution associated with the target account are obtained; Based on the target financial region, the rule parameters in the corresponding account coding model are invoked to automatically generate a target account code that conforms to the management requirements of the corresponding financial region. Based on the target financial institution and the target financial region, query and obtain the target institution identification code of the target financial institution in the target financial region from the multi-regional institution coding mapping relationship; The target account code is associated with the target institution identification code to form an account information tuple for the target account in the target financial region; The account information tuple is stored so that information can be retrieved based on the financial region when processing fund transfers involving the target account.
[0008] Based on the above-mentioned invention, a novel solution is provided that can automatically generate account codes conforming to the corresponding encoding formats and automatically associate them with the corresponding institutional identification codes under the same financial region during the account creation process. Specifically, the solution first obtains an account coding model with rule parameters configured for multiple financial regions to define the account coding format, and establishes and maintains a multi-regional institutional coding mapping relationship between financial institutions and financial regions. In response to the operation of creating a target account, the solution obtains the target financial region and the target financial institution; it then calls the rule parameters in the corresponding model to automatically generate a target account code conforming to the encoding format of that region; it retrieves the target institutional identification code from the mapping relationship; and finally, it associates the target account code with the target institutional identification code to form an account information tuple and stores it for information retrieval by financial region during fund transfer processing. This achieves the automatic generation and association of account codes and institutional identification codes across financial regions, solving the problem that traditional systems cannot automatically adapt to multi-regional differentiated encoding formats and institutional identification requirements. This solution can be widely applied in global unified account management platforms, facilitating practical application and promotion.
[0009] In one possible design, the rule parameters in the account coding model include the total length of the account code, the number of code segments, the financial attribute information corresponding to each code segment, the length of each code segment, and / or the check digit generation algorithm.
[0010] In one possible design, the institution identification code in the multi-regional institution coding mapping relationship includes the SWIFT code, the International Bank Account Number (IBAN), the local clearing system code, and / or the legal entity identifier within the financial jurisdiction.
[0011] In one possible design, the account information tuple includes the internal unique identifier of the target account, the label of the target financial region, the target account number, and the target institution identification code.
[0012] In one possible design, the method further includes: updating the corresponding organization identification code in the multi-region organization coding mapping relationship in response to a change operation on the target organization identification code.
[0013] In one possible design, the method further includes: In response to an instruction to expand a new financial region for the target account, the new financial region associated with the target account and the new target financial institution under the new financial region are obtained; Based on the new financial region, the rule parameters in the corresponding account coding model are invoked to automatically generate a new target account code that conforms to the management requirements of the corresponding financial region. Based on the new target financial institution and the new financial region, query and obtain the new target institution identification code of the new target financial institution in the new financial region from the multi-regional institution coding mapping relationship; The new target account code is associated with the new target institution identification code to form an account information tuple for the target account in the new financial region, and then stored.
[0014] In one possible design, the method further includes: Receive a fund transfer request involving the target account, wherein the fund transfer request includes information about the financial region where the transaction occurred; Based on the financial region information, extract the target account code and / or target institution identification code that match the financial region information from the stored account information tuple; Based on the extracted target account code and / or target institution identification code, assemble a payment message or clearing instruction that is used to respond to the fund transfer request and conforms to the financial region where the transaction occurred.
[0015] In one possible design, the method further includes: Receive a cross-financial region fund transfer request involving the target account, wherein the cross-financial region fund transfer request includes fund outflow side account, financial region information of the fund outflow location, fund inflow side account, and financial region information of the fund inflow location, and the target account is the fund outflow side account or the fund inflow side account; Based on the financial region information of the fund outflow location, extract the fund outflow account code and / or fund outflow institution identification code that match the financial region information of the fund outflow location from the stored account information tuple of the fund outflow side account to serve as the fund outflow side extraction information; Based on the financial region information of the fund inflow location, extract the fund inflow account code and / or fund inflow institution identification code that match the financial region information of the fund inflow location from the stored account information tuple of the fund inflow side account as the fund inflow extraction information; Based on the withdrawal information from the outflow side and the withdrawal information from the inflow side, a payment message or clearing instruction is assembled to respond to the cross-financial region fund transfer request and to comply with the regulations of the financial regions where the fund outflow and inflow are located, respectively.
[0016] Secondly, a cross-financial region account information processing device is provided, including a coding model acquisition unit, a mapping relationship maintenance unit, a filing operation response unit, a target coding generation unit, a target institution query unit, an information tuple forming unit, and an information tuple storage unit. The encoding model acquisition unit is used to acquire account encoding models configured for multiple financial regions respectively, wherein the account encoding model includes rule parameters for defining an account encoding format that conforms to the management requirements of the corresponding financial region; The mapping relationship maintenance unit is used to establish and maintain a multi-regional institution code mapping relationship between financial institutions and financial regions, wherein the multi-regional institution code mapping relationship is used to record the institution identification codes of the same financial institution in different financial regions. The filing operation response unit is used to respond to the operation of filing a file for a target account and obtain the target financial region and target financial institution associated with the target account; The target code generation unit is communicatively connected to the filing operation response unit and the code model acquisition unit, respectively, and is used to automatically generate a target account code that conforms to the management requirements of the corresponding financial region by calling the rule parameters in the corresponding account code model according to the target financial region. The target institution query unit is communicatively connected to the filing operation response unit and the mapping relationship maintenance unit, and is used to query and obtain the target institution identification code of the target financial institution in the target financial region from the multi-regional institution code mapping relationship according to the target financial institution and the target financial region. The information tuple forming unit is communicatively connected to the target code generation unit and the target institution query unit, respectively, and is used to associate the target account code with the target institution identification code to form the account information tuple of the target account in the target financial region; The information tuple storage unit is communicatively connected to the information tuple forming unit and is used to store the account information tuple for information retrieval based on the financial region when processing fund transfers involving the target account.
[0017] Thirdly, the present invention provides a computer device comprising a storage module, a processing module, and a transceiver module connected in sequence for communication, wherein the storage module is used to store a computer program, the transceiver module is used to send and receive messages, and the processing module is used to read the computer program and execute the cross-financial region account information processing method as described in the first aspect or any possible design in the first aspect.
[0018] Fourthly, the present invention provides a computer-readable storage product storing instructions that, when executed on a computer, perform the cross-financial region account information processing method as described in the first aspect or any possible design in the first aspect.
[0019] Fifthly, the present invention provides a computer program product, including a computer program or instructions, which, when executed by a computer, implement the cross-financial region account information processing method as described in the first aspect or any possible design in the first aspect.
[0020] The beneficial effects of the above scheme are: (1) This invention creatively provides a new solution that can automatically generate account codes that conform to the corresponding coding format and automatically associate them with the corresponding institutional identification codes in the financial region according to the differentiated requirements of the financial region during the account filing process. That is, firstly, an account coding model is obtained, which is configured for multiple financial regions and used to define the account coding format, and a multi-regional institutional coding mapping relationship is established and maintained between financial institutions and financial regions; in response to the operation of filing a target account, the target financial region and the target financial institution are obtained; the rule parameters in the corresponding model are called to automatically generate the target account code that conforms to the coding format of the region; the target institutional identification code is obtained from the mapping relationship; the target account code and the target institutional identification code are associated to form an account information tuple and stored for information retrieval by financial region during fund transfer processing. In this way, the automatic generation and association of account codes and institutional identification codes across financial regions is realized, which solves the problem that traditional systems cannot automatically adapt to the differentiated coding formats and institutional identification requirements of multiple regions. It can be widely used in global unified account management platforms. (2) By configuring account coding models containing rule parameters for multiple financial regions and establishing multi-regional institutional coding mapping relationships, the limitations of the single-region fixed rules of the traditional account system are broken, and flexible adaptation to the differentiated coding format requirements and institutional identification specifications of different financial regions is achieved. (3) By automatically calling the account code model of the corresponding region to generate the target account code during the account filing process, and automatically querying the multi-regional institution code mapping relationship to obtain the target institution identification code, the automatic generation and association of account code and institution identification code are realized, reducing the errors and mistakes that may be introduced by manual compilation and query, and improving the accuracy of account information and filing efficiency; (3) By associating the target account code with the target institution identification code to form a structured account information tuple and storing it in a unified manner, a complete pool of account and institution code information under the global system is constructed, which enables the centralized management of the differentiated information of the same account in multiple financial regions and supports flexible access as needed during fund transfers; (5) By using the configuration-driven account coding model system and mapping table data structure, when adding a new financial area, only the corresponding model and mapping relationship need to be added in the configuration layer, without modifying the core code of the system, which improves the scalability and maintainability of the system. (6) By supporting the dynamic updating of the coding mapping relationship of multi-regional institutions, the real-time accuracy of the institution identification code is ensured, avoiding the use of incorrect institution information in the flow of funds due to outdated institution information, and ensuring the compliance of cross-regional fund flow. (7) By supporting the expansion of account information tuples to new financial regions for existing accounts, the continuous accumulation and incremental management of account information in multiple regions are realized, providing flexible information support for enterprises to expand their cross-regional business. (8) By supporting the automatic extraction of matching account codes and / or institution identification codes from stored account information tuples in single-region and cross-regional fund transfer scenarios, and assembling payment messages or clearing instructions that conform to the corresponding financial region specifications, the system realizes the fully automated closed loop of account information from generation, storage to retrieval, which significantly improves the processing efficiency of cross-financial regional fund transfers, reduces the risk of payment failure and additional financial costs caused by information mismatch, and facilitates practical application and promotion. Attached Figure Description
[0021] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.
[0022] Figure 1 This is a flowchart illustrating the cross-financial region account information processing method provided in an embodiment of this application.
[0023] Figure 2 This is a schematic diagram of the structure of the cross-financial region account information processing device provided in the embodiments of this application.
[0024] Figure 3 A schematic diagram of the structure of a computer device provided in an embodiment of this application. Detailed Implementation
[0025] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the present invention will be briefly introduced below in conjunction with the accompanying drawings and descriptions of the embodiments or the prior art. Obviously, the following description of the structure of the accompanying drawings is only some embodiments of the present invention. For those skilled in the art, other embodiments can be obtained based on these embodiments without creative effort. It should be noted that the description of these embodiments is for the purpose of helping to understand the present invention, but does not constitute a limitation of the present invention.
[0026] It should be understood that although the terms "first" and "second", etc., may be used herein to describe various objects, these objects should not be limited by these terms. These terms are only used to distinguish one object from another. For example, the first object may be referred to as the second object, and similarly, the second object may be referred to as the first object, without departing from the scope of the exemplary embodiments of the invention.
[0027] It should be understood that the term "and / or" that may appear in this document is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can mean: A exists alone, B exists alone, or A and B exist simultaneously. Another example is A, B and / or C, which can mean that any one of A, B, and C or any combination thereof exists. The term " / and" that may appear in this document describes another relationship between related objects, indicating that two relationships can exist. For example, A / and B can mean: A exists alone or A and B exist simultaneously. In addition, the character " / " that may appear in this document generally indicates that the related objects before and after it are in an "or" relationship.
[0028] Example like Figure 1 As shown, the cross-financial region account information processing method provided in the first aspect of this embodiment can be executed, but is not limited to, by a computer device with certain computing resources, such as a backend server, server cluster, or cloud server deployed with a global unified account management platform. By executing the method, the computer device provides cross-financial region account information processing services to entities (such as multinational corporations, cross-border e-commerce platforms, or financial institutions) with account management needs across multiple financial regions, enabling the automatic generation, association, and storage of account codes and institution identification codes across multiple financial regions to support subsequent information retrieval by financial region.
[0029] like Figure 1 As shown, the cross-financial region account information processing method includes, but is not limited to, the following steps S1 to S7.
[0030] S1. Obtain account coding models configured for multiple financial regions respectively, wherein the account coding model includes, but is not limited to, rule parameters for defining account coding formats that conform to the management requirements of the corresponding financial regions.
[0031] In step S1, the account coding model is pre-configured and stored in a storage medium accessible to the computer device. Specifically, system administrators or operators can pre-enter rule parameters for the account coding format corresponding to each financial region (such as different countries or regions) through a configuration interface or configuration portal, based on the financial management regulations of different financial regions (such as different countries or regions), thereby forming account coding models that correspond one-to-one with each financial region. The account coding model can be stored within the computer device in a key-value pair data structure, where the financial region identifier is the key and the rule parameters are the values. The rule parameters are used to define the coding format of legal accounts under the financial region, and include, but are not limited to, the total length of the account code, the number of code segments, the financial attribute information corresponding to each code segment (such as bank code, branch code, and account serial number), the length of each code segment, and / or the check digit generation algorithm. By pre-configuring independent account coding models for multiple financial regions, the computer device can dynamically call the corresponding model when processing account filing requests for specific financial regions without modifying the core system code. This achieves flexible adaptation and scalable support for differentiated coding rules across multiple financial regions.
[0032] S2. Establish and maintain a multi-regional institutional code mapping relationship between financial institutions and financial regions, wherein the multi-regional institutional code mapping relationship is used to record the institutional identification codes of the same financial institution in different financial regions.
[0033] In step S2, the multi-regional institution code mapping relationship is pre-established and dynamically maintained in a storage medium accessible to the computer device. Specifically, since the same financial institution (such as a bank) may be assigned different institution identification codes in different financial regions (for example, the bank's SWIFT code in the United States is different from its IBAN code in the European Union), it is necessary to establish a mapping relationship between each cooperating financial institution and its corresponding institution identification code in each financial region. Within the computer device, the multi-regional institution code mapping relationship can be stored, but is not limited to, in a mapping table data structure, where the combination of the financial institution identifier and the financial region identifier serves as the key, and the institution identification code of the financial institution in that financial region serves as the value. The institution identification code is used to uniquely identify the financial institution's identity in a specific financial region during fund transfers. Specific types include, but are not limited to, SWIFT (Society for Worldwide Interbank Financial Telecommunications) codes, International Bank Account Numbers (IBANs), local clearing system codes, and / or legal entity identifiers within a financial jurisdiction. By establishing and maintaining the multi-regional institution code mapping relationship, the computer equipment can dynamically query and obtain the corresponding institution identification code based on the target financial institution and the target financial region when processing account filing or fund transfer requests, thus meeting the differentiated requirements of information flow of the same financial institution in different financial regions.
[0034] In some extended embodiments following step S2, the method further includes dynamically updating the institution identification code in the multi-regional institution code mapping relationship. Specifically, when the institution identification code of a financial institution in a specific financial region changes due to institutional restructuring, system upgrades, or regulatory requirements, the system administrator or operations personnel can initiate a change operation for the institution identification code of that financial institution in that financial region through the configuration interface or configuration interface provided by the computer device. In response to this change operation, the computer device locates the corresponding record in the multi-regional institution code mapping relationship that uses the financial institution's identifier and the financial region's identifier as a combination key, and updates the original institution identification code in that record to the new institution identification code. This dynamic update mechanism ensures that the institution identification code in the multi-regional institution code mapping relationship remains up-to-date, thereby avoiding the use of incorrect institution information in subsequent fund transfer processing due to outdated institution identification codes, and ensuring the accuracy and compliance of cross-regional fund transfers.
[0035] S3. In response to the operation of creating a profile for the target account, obtain the target financial region and target financial institution associated with the target account.
[0036] In step S3, the operation of creating a file for the target account can be initiated by the user through the account management interface provided by the computer device, for example, by the user filling in basic account information and submitting a file creation request through the new account page. The file creation request carries, or is determined by the computer device based on the file creation context, the target financial region and target financial institution associated with the target account. The target financial region indicates the financial management jurisdiction applicable to this file creation, and determines which financial region's account coding model should be used to generate the account code subsequently; the target financial institution indicates the account opening financial institution associated with this file creation, and determines which financial institution's institution identification code should be queried subsequently. It can be understood that the target financial region and target financial institution can be directly specified by the user when initiating the file creation operation, or can be automatically identified and determined by the computer device based on account attributes (such as account location or account purpose). Obtaining the target financial region and target financial institution provides the necessary location basis for calling the corresponding account coding model to generate the account code in step S4 and for querying the corresponding institution identification code in step S5.
[0037] S4. Based on the target financial region, call the rule parameters in the corresponding account coding model to automatically generate a target account code that conforms to the management requirements of the corresponding financial region.
[0038] In step S4, specifically, the computer device uses the target financial region obtained in step S3 as an index to query and call the account coding model corresponding to the target financial region from multiple stored account coding models, and then reads the rule parameters in the model. The rule parameters define the coding format requirements for legitimate accounts under the target financial region, including, for example, the total length of the account code, the number of code segments, the financial attribute information corresponding to each code segment (such as bank code, branch code, and account serial number), the length of each code segment, and the check digit generation algorithm. Based on the read rule parameters, the computer device automatically generates a target account code that conforms to the coding format requirements of the target financial region according to a preset coding generation logic (such as string concatenation, template filling, or formatting). For example, if the rule parameters of a certain financial region require the account code to consist of "4-digit bank code + 6-digit branch code + 10-digit account serial number + 2-digit check digit," then the computer device fills in the contents of each code segment sequentially according to this format, calls the corresponding check digit generation algorithm to calculate the check digit, and finally generates a complete 22-digit target account code. It is understood that account coding models corresponding to different financial regions can have different rule parameter configurations, thereby achieving automatic adaptation and generation of differentiated account coding formats for different financial regions. Through this step, the computer equipment can automatically generate account codes that conform to regional standards without human intervention, avoiding format errors and compliance risks that may be introduced by manual account creation.
[0039] S5. Based on the target financial institution and the target financial region, query and obtain the target institution identification code of the target financial institution in the target financial region from the multi-regional institution coding mapping relationship.
[0040] In step S5, specifically, the computer device uses the target financial institution and the target financial region obtained in step S3 as joint query conditions. It then queries the multi-regional institution code mapping relationship pre-established and maintained in step S2 to find records matching the combined conditions and extracts the institution identification code assigned to the target financial institution within the target financial region as the target institution identification code. It is understood that since the same financial institution may be assigned different institution identification codes in different financial regions, it is necessary to use both the financial institution identifier and the financial region identifier as joint query conditions to accurately locate the correct institution identification code of the financial institution within a specific financial region. The specific type of the target institution identification code may include, but is not limited to, SWIFT codes, International Bank Account Numbers (IBANs), Local Clearing System codes, and / or legal entity identifiers within a financial jurisdiction. In subsequent step S6, the target institution identification code will be associated with the target account code generated in step S4 to form a complete account information tuple. Furthermore, it is understood that the execution order of steps S4 and S5 can be interchanged or executed in parallel; this embodiment does not limit the order of the two.
[0041] S6. Associate the target account code with the target institution identification code to form an account information tuple for the target account in the target financial region.
[0042] In step S6, specifically, the computer device associates the target account code generated in step S4 with the target institution identification code obtained in step S5 to form an account information tuple for the target account within the target financial region. This association refers to establishing a structured data binding relationship between the target account code and the target institution identification code within the computer device, making them a complete, queryable, and retrievalable information unit. The account information tuple is a data structure describing the complete account information of the target account within a specific financial region, and it may include at least: the target account's internal unique identifier, the target financial region's label, the target account code, and the target institution identification code. By forming a dedicated account information tuple for the target account within the target financial region, precise binding between account information and the financial region is achieved. It can be understood that when the target account needs to be used in multiple financial regions, separate account information tuples can be formed for each target account in different financial regions, thereby achieving differentiated information management for the same account in different financial regions and providing a data foundation for flexibly retrieving accurate account information by region during subsequent fund transfers.
[0043] S7. Store the account information tuple for future reference when processing fund transfers involving the target account, and retrieve the information based on the financial region.
[0044] In step S7, specifically, the computer device stores the account information tuple formed in step S6 into a storage medium accessible to the computer device, such as writing it into an account information table in a database. During storage, each field in the account information tuple (such as the internal unique identifier, the target financial region label, the target account code, and the target institution identification code) is persistently saved in the form of structured data records. This allows for rapid retrieval and extraction of the corresponding account code and / or institution identification code based on the financial region during subsequent fund transfer processing involving the target account. It can be understood that when the target account has corresponding account information tuples in multiple financial regions, these tuples can be uniformly stored in a global account information pool, enabling centralized management and on-demand retrieval of the target account's differentiated account information across different financial regions. Through this step, the computer device completes a full account filing process from configuration, filing, generation, association to storage, achieving automated processing of account information across financial regions. This provides data support for flexibly extracting accurate account information by financial region during subsequent single-region or cross-regional fund transfers.
[0045] Therefore, based on the account information processing method described in steps S1 to S7 above, a new solution is provided that can automatically generate account codes conforming to the corresponding coding format and automatically associate them with the corresponding institutional identification codes under that region during the account filing process. Specifically, first, an account coding model is obtained, which is configured separately for multiple financial regions and used to define the account coding format, and a multi-regional institutional coding mapping relationship is established and maintained between financial institutions and financial regions. In response to the operation of filing a target account, the target financial region and the target financial institution are obtained; the rule parameters in the corresponding model are called to automatically generate a target account code conforming to the coding format of that region; the target institutional identification code is retrieved from the mapping relationship; and the target account code and the target institutional identification code are associated to form an account information tuple and stored for information retrieval by financial region during fund transfer processing. This achieves the automatic generation and association of account codes and institutional identification codes across financial regions, solving the problem that traditional systems cannot automatically adapt to multi-regional differentiated coding formats and institutional identification requirements. It can be widely applied in global unified account management platforms, facilitating practical application and promotion.
[0046] Based on the technical solution of the first aspect mentioned above, this embodiment also provides a possible design for how to support the expansion of account information for multiple financial regions for existing accounts, that is, the method also includes, but is not limited to, the following steps S811 to S814.
[0047] S811. In response to an instruction to expand a new financial region for the target account, obtain the new financial region associated with the target account and the new target financial institution under the new financial region.
[0048] In step S811, the instruction to expand the target account to a new financial region can be, but is not limited to, initiated by the user through the account management interface provided by the computer device. For example, when a company conducts business in a new financial region, it needs to supplement the existing target account with account information under that new region. The user can initiate the "Expand New Region" operation on the details page of the target account and specify the new financial region and the new target financial institution under that new region. The computer device responds to this instruction by obtaining the identifier of the new financial region and the identifier of the new target financial institution, providing a location basis for generating the account code under the new region in subsequent step S812 and querying the institution identification code under the new region in step S813. It can be understood that the new financial region is different from the target financial region described in step S3 above; it corresponds to an incremental region where the target account has not yet established account information tuples.
[0049] S812. Based on the new financial region, invoke the rule parameters in the corresponding account coding model to automatically generate a new target account code that conforms to the account coding format required by the management of the corresponding financial region.
[0050] In step S812, the computer device uses the new financial region obtained in step S811 as an index to query and call the account coding model corresponding to the new financial region from multiple stored account coding models, reads the rule parameters in the model, and automatically generates a new target account code that conforms to the coding format requirements of the new financial region according to the preset coding generation logic. The specific implementation of this step is similar to the aforementioned step S4, except that the financial region targeted is the new financial region, and the generated account code is the new target account code instead of the aforementioned target account code. By reusing the account coding model system configured in the aforementioned step S1, it is possible to expand to a new region without redeveloping or modifying the coding generation logic; it is only necessary to ensure that the account coding model corresponding to the new financial region has been pre-configured.
[0051] S813. Based on the new target financial institution and the new financial region, query and obtain the new target institution identification code of the new target financial institution in the new financial region from the multi-regional institution coding mapping relationship.
[0052] In step S813, the computer device uses the new target financial institution and the new financial region obtained in step S811 as joint query conditions. It queries the multi-regional institution code mapping relationship pre-established and maintained in step S2 to find records matching the combined conditions, and extracts the institution identification code assigned to the new target financial institution in the new financial region as the new target institution identification code. The specific implementation of this step is similar to the aforementioned step S5, except that the query conditions are the new target financial institution and the new financial region, and the obtained result is the new target institution identification code. Similarly, by reusing the mapping relationship system established in step S2, the corresponding institution identification code can be easily obtained when expanding to a new region.
[0053] S814. Associate the new target account code with the new target institution identification code to form an account information tuple for the target account in the new financial region, and store it.
[0054] In step S814, the computer device associates the new target account code generated in step S812 with the new target institution identification code obtained in step S813 to form an account information tuple for the target account in the new financial region, and stores this account information tuple. The specific implementation of this step is similar to steps S6 and S7. The data structure of the account information tuple can be consistent with the tuple structure described in step S6, for example, it also includes the internal unique identifier of the target account, the label of the new financial region, the new target account code, and the new target institution identification code. Since the internal unique identifier of the target account remains consistent across tuples in different financial regions, the newly formed tuple is naturally associated with the previously stored tuples through this internal unique identifier, together constituting the complete account information of the target account in the global system. By supplementing the storage of the account information tuple under the new financial region into the global account information pool, the scope of differentiated information management for the target account is extended to the new financial region, providing information retrieval support for subsequent fund flows within that region.
[0055] Based on the above possible design, the system enables the dynamic expansion of account information for target accounts in new financial regions beyond the existing filing regions, without requiring the re-execution of the complete initial filing process. By reusing the configured account coding model system and the multi-regional institution coding mapping relationship, the system can automatically generate account codes and associate institution identification codes in new regions. This allows for the continuous accumulation and centralized management of differentiated information for the same account in multiple financial regions, providing technical support for building a truly global integrated account information pool and effectively supporting the needs of enterprises for cross-regional business expansion.
[0056] Based on the technical solution of the first aspect mentioned above, this embodiment also provides a possible design two for how to support the on-demand retrieval of stored account information when funds are transferred in a single region. That is, the method also includes, but is not limited to, the following steps S821 to S823.
[0057] S821. Receive a fund transfer request involving the target account, wherein the fund transfer request includes, but is not limited to, information such as the financial region where the transaction occurred.
[0058] In step S821, the fund transfer request involving the target account can be, but is not limited to, received by the computer device from an internal payment processing system, an external clearing network, or by the user through an account operation interface. The fund transfer request can be, for example, a payment instruction, a transfer request, or a clearing and settlement instruction. The fund transfer request includes at least information about the financial region where the transaction occurred. This financial region information indicates the financial jurisdiction involved in the fund transfer, such as the financial region where the funds originate or originate. It is understood that the financial region information where the transaction occurred can be specified by the transaction initiator when submitting the request, or it can be automatically identified and determined by the computer device based on the transaction context (such as counterparty information, transaction currency, or transaction channel). Obtaining the financial region information provides a location basis for extracting account information matching that financial region from the stored account information tuple in subsequent step S822.
[0059] S822. Based on the financial region information, extract the target account code and / or target institution identification code that match the financial region information from the stored account information tuple.
[0060] In step S822, the computer device uses the financial region information of the transaction location obtained in step S821 as a query condition to retrieve and extract the target account code and / or target institution identification code that match the financial region information from the account information tuple of the target account stored in step S7. Specifically, since the account information tuple contains a tag field of the target financial region, the computer device can locate the corresponding tuple record by matching the tag with the financial region information of the transaction location, and extract the required target account code and / or target institution identification code from it. It can be understood that if the fund transfer request only requires the account code to complete the processing, the target account code is extracted; if the fund transfer request also requires an institution identification code to complete the clearing route, the target institution identification code is extracted at the same time. Through this step, the computer device automatically retrieves the correct account information from the pre-stored global account information pool based on the transaction location, without the need for manual querying and filling.
[0061] S823. Based on the extracted target account code and / or target institution identification code, assemble a payment message or clearing instruction for responding to the fund transfer request and conforming to the financial region regulations where the transaction occurred.
[0062] In step S823, the computer device assembles the target account code and / or target institution identification code extracted in step S822 into a payment message or clearing instruction to respond to the fund transfer request, according to the message format specifications or clearing interface specifications of the financial region where the transaction occurred. For example, if the transaction occurred in the United States, the extracted account code and institution identification code (such as the ABA routing number) are filled into the corresponding fields of the message according to the message format requirements of the Automated Clearing System or Federal Electronic Funds Transfer System (EFFT). Through this step, the computer device automatically completes the entire process from information extraction to message assembly, ensuring that the generated payment message or clearing instruction complies with the compliance requirements of the financial region where the transaction occurred.
[0063] Based on the aforementioned second possible design, in single-region fund transfer scenarios, the system automatically extracts the matching account code and / or institution identification code from the stored account information tuples according to the transaction location, and assembles payment messages or clearing instructions that conform to the corresponding financial region's regulations. Through the combination of the aforementioned configuration and linkage management mechanism with the account information tuples, the previously automatically generated account information is effectively applied to the actual fund transfer process, avoiding information errors and operational delays that may be introduced by manual querying and filling, improving the processing efficiency and compliance of cross-financial region fund transfers, and reducing the risk of payment failure and additional financial costs caused by inaccurate information.
[0064] Based on the technical solution of the first aspect mentioned above, this embodiment also provides a possible design three for how to support bidirectional extraction of account information on both sides when transferring funds across regions, that is, the method also includes, but is not limited to, the following steps S831 to S834.
[0065] S831. Receive a cross-financial region fund transfer request involving the target account, wherein the cross-financial region fund transfer request includes, but is not limited to, an outflow account, information on the financial region where the outflow location is located, an inflow account, and information on the financial region where the inflow location is located, and the target account is the outflow account or the inflow account, etc.
[0066] In step S831, the cross-financial region fund transfer request can, but is not limited to, be received by the computer device from an internal payment processing system, an external clearing network, or by a user through an account operation interface. Unlike the single-region fund transfer request involved in step S821, the cross-financial region fund transfer request involves two different financial regions: the financial region where the funds originate and the financial region where the funds flow into. The cross-financial region fund transfer request simultaneously indicates the outflowing account, the financial region information of the outflowing account, the inflowing account, and the financial region information of the inflowing account. The target account can be either the outflowing account or the inflowing account; that is, the target account can be either the spender or the receiver of funds. It can be understood that when the target account is the outflowing account, the inflowing account is the counterparty account; and vice versa. By obtaining the account identifiers and corresponding financial region information of the outflow and inflow sides of funds, the necessary positioning basis is provided for extracting matching account information from the account information tuples of the two sides in subsequent steps S832 and S833.
[0067] S832. Based on the financial region information of the fund outflow location, extract the fund outflow account code and / or fund outflow institution identification code that match the financial region information of the fund outflow location from the stored account information tuple of the fund outflow side account as the fund outflow side extraction information.
[0068] In step S832, the computer device uses the financial region information of the fund outflow location obtained in step S831 as a query condition to retrieve and extract the fund outflow account code and / or fund outflow institution identification code that match the financial region information from the account information tuple of the fund outflow account stored in step S7, as the fund outflow extraction information. The specific implementation of this step is similar to the aforementioned step S822, except that this step targets the fund outflow account, and the extracted account code and institution identification code match the financial region of the fund outflow location. It can be understood that the account information tuple of the fund outflow account is pre-stored through the aforementioned steps S1-S7 or steps S811-S814; therefore, the computer device can automatically locate the corresponding tuple record and extract the required information based on the financial region information of the fund outflow location without manual intervention.
[0069] S833. Based on the financial region information of the location of the funds inflow, extract the fund inflow account code and / or fund inflow institution identification code that match the financial region information of the location of the funds inflow from the stored account information tuple of the fund inflow account as the fund inflow extraction information.
[0070] In step S833, the computer device uses the financial region information of the fund inflow location obtained in step S831 as the query condition, and retrieves and extracts the fund inflow side account code and / or fund inflow side institution identification code that match the financial region information from the account information tuple of the fund inflow side account stored in step S7, as the fund inflow side extracted information. The specific implementation of this step is symmetrical to step S832, the difference being that it targets the fund inflow side account and the financial region where the fund inflow location is located. It can be understood that the execution order of steps S832 and S833 can be interchanged or executed in parallel, and this embodiment does not limit the order of the two. By extracting matching account information from both the fund outflow side and the fund inflow side according to their respective corresponding financial region information, the computer device realizes the automated acquisition of account information on both sides in the scenario of cross-financial region fund flow.
[0071] S834. Based on the outflow side extraction information and the inflow side extraction information, assemble a payment message or clearing instruction for responding to the cross-financial region fund transfer request and respectively conforming to the financial region specifications of the outflow and inflow locations.
[0072] In step S834, the computer device assembles the outflow-side extraction information extracted in step S832 and the inflow-side extraction information extracted in step S833, according to the message format specifications or clearing interface specifications involved in cross-financial regional fund transfers, to generate a payment message or clearing instruction in response to the cross-financial regional fund transfer request. Since cross-financial regional fund transfers involve two different financial jurisdictions, the assembled payment message or clearing instruction must simultaneously meet the regulatory requirements of both the outflow and inflow financial regions. For example, in a cross-border transfer from the United States to the European Union, the payment message must simultaneously include payer account information conforming to US regulations (such as the ABA routing number and corresponding account number) and payee account information conforming to EU regulations (such as the IBAN and corresponding SWIFT code). Through this step, the computer device automatically completes the bidirectional information assembly required for cross-regional fund transfers, ensuring that the generated payment message or clearing instruction complies with the compliance requirements of both the outflow and inflow financial regions.
[0073] Based on the aforementioned possible design three, in cross-financial regional fund transfer scenarios, the system automatically extracts account codes and / or institution identification codes matching the corresponding financial regions from the account information tuples of the accounts on both sides, according to the fund outflow and fund inflow locations, and assembles payment messages or clearing instructions that conform to the specifications of the two financial regions respectively. By effectively applying the aforementioned automatically generated and associated stored account information tuples to the cross-regional fund transfer process, the system achieves automatic capture and assembly of bidirectional information, avoiding errors and delays that may be introduced by manually querying and filling in the account information on both sides. This significantly improves the processing efficiency and compliance of cross-financial regional fund transfers and reduces the risk of payment failure and additional financial costs caused by information mismatch.
[0074] like Figure 2 As shown, the second aspect of this embodiment provides a virtual device for implementing the account information processing method described in the first aspect or any possible design in the first aspect, including an encoding model acquisition unit, a mapping relationship maintenance unit, a filing operation response unit, a target encoding generation unit, a target organization query unit, an information tuple forming unit, and an information tuple storage unit. The encoding model acquisition unit is used to acquire account encoding models configured for multiple financial regions respectively, wherein the account encoding model includes rule parameters for defining an account encoding format that conforms to the management requirements of the corresponding financial region; The mapping relationship maintenance unit is used to establish and maintain a multi-regional institution code mapping relationship between financial institutions and financial regions, wherein the multi-regional institution code mapping relationship is used to record the institution identification codes of the same financial institution in different financial regions. The filing operation response unit is used to respond to the operation of filing a file for a target account and obtain the target financial region and target financial institution associated with the target account; The target code generation unit is communicatively connected to the filing operation response unit and the code model acquisition unit, respectively, and is used to automatically generate a target account code that conforms to the management requirements of the corresponding financial region by calling the rule parameters in the corresponding account code model according to the target financial region. The target institution query unit is communicatively connected to the filing operation response unit and the mapping relationship maintenance unit, and is used to query and obtain the target institution identification code of the target financial institution in the target financial region from the multi-regional institution code mapping relationship according to the target financial institution and the target financial region. The information tuple forming unit is communicatively connected to the target code generation unit and the target institution query unit, respectively, and is used to associate the target account code with the target institution identification code to form the account information tuple of the target account in the target financial region; The information tuple storage unit is communicatively connected to the information tuple forming unit and is used to store the account information tuple for information retrieval based on the financial region when processing fund transfers involving the target account.
[0075] The working process, working details and technical effects of the aforementioned device provided in the second aspect of this embodiment can be found in the first aspect or any possible design of the account information processing method described in the first aspect, and will not be repeated here.
[0076] like Figure 3As shown, the third aspect of this embodiment provides a computer device for executing the account information processing method as described in the first aspect or any possible design within the first aspect. The device includes a storage module, a processing module, and a transceiver module that are sequentially and communicatively connected. The storage module stores a computer program, the transceiver module sends and receives messages, and the processing module reads the computer program and executes the account information processing method as described in the first aspect or any possible design within the first aspect. Specifically, the storage module may include, but is not limited to, random-access memory (RAM), read-only memory (ROM), flash memory, first-in-first-out (FIFO) memory, and / or first-in-last-out (FILO) memory, etc.; the processing module may, but is not limited to, use a microprocessor of the STM32F105 series. Furthermore, the computer device may also include, but is not limited to, a power supply module, a display screen, and other necessary components.
[0077] The working process, working details and technical effects of the aforementioned computer device provided in the third aspect of this embodiment can be found in the account information processing method described in the first aspect or any possible design in the first aspect, and will not be repeated here.
[0078] This fourth aspect of the embodiment provides a computer-readable storage product that stores instructions comprising the account information processing method as described in the first aspect or any possible design within the first aspect. Specifically, the computer-readable storage product stores instructions that, when executed on a computer, perform the account information processing method as described in the first aspect or any possible design within the first aspect. The computer-readable storage product refers to a data storage medium, which may include, but is not limited to, computer-readable storage media such as floppy disks, optical disks, hard disks, flash memory, USB flash drives, and / or Memory Sticks. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices.
[0079] The working process, working details and technical effects of the aforementioned computer-readable storage product provided in the fourth aspect of this embodiment can be found in the account information processing method described in the first aspect or any possible design in the first aspect, and will not be repeated here.
[0080] This fifth aspect of the embodiment provides a computer program product, including a computer program or instructions, which, when executed by a computer, implement the account information processing method as described in the first aspect or any possible design within the first aspect. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device.
[0081] Finally, it should be noted that the above description is merely a preferred embodiment of the present invention and is not intended to limit the scope of protection of the present invention. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the present invention should be included within the scope of protection of the present invention.
Claims
1. A method for processing account information across financial regions, characterized in that, include: Obtain account coding models configured for multiple financial regions, wherein the account coding models contain rule parameters for defining account coding formats that conform to the management requirements of the corresponding financial regions; Establish and maintain a multi-regional institution code mapping relationship between financial institutions and financial regions, wherein the multi-regional institution code mapping relationship is used to record the institution identification code of the same financial institution in different financial regions; In response to the operation of creating a profile for the target account, the target financial region and target financial institution associated with the target account are obtained; Based on the target financial region, the rule parameters in the corresponding account coding model are invoked to automatically generate a target account code that conforms to the management requirements of the corresponding financial region. Based on the target financial institution and the target financial region, query and obtain the target institution identification code of the target financial institution in the target financial region from the multi-regional institution coding mapping relationship; The target account code is associated with the target institution identification code to form an account information tuple for the target account in the target financial region; The account information tuple is stored so that information can be retrieved based on the financial region when processing fund transfers involving the target account.
2. The account information processing method according to claim 1, characterized in that, The rule parameters in the account coding model include the total length of the account code, the number of code segments, the financial attribute information corresponding to each code segment, the length of each code segment, and / or the check digit generation algorithm. And / or, the institution identification code in the multi-region institution coding mapping relationship includes the SWIFT code, the International Bank Account Number (IBAN), the local clearing system code, and / or the legal institution identifier within the financial jurisdiction; And / or, the account information tuple includes the internal unique identifier of the target account, the label of the target financial region, the target account number, and the target institution identification code.
3. The account information processing method according to claim 1, characterized in that, The method further includes: updating the corresponding organization identification code in the multi-region organization coding mapping relationship in response to the change operation of the target organization identification code.
4. The account information processing method according to claim 1, characterized in that, The method further includes: In response to an instruction to expand a new financial region for the target account, the new financial region associated with the target account and the new target financial institution under the new financial region are obtained; Based on the new financial region, the rule parameters in the corresponding account coding model are invoked to automatically generate a new target account code that conforms to the management requirements of the corresponding financial region. Based on the new target financial institution and the new financial region, query and obtain the new target institution identification code of the new target financial institution in the new financial region from the multi-regional institution coding mapping relationship; The new target account code is associated with the new target institution identification code to form an account information tuple for the target account in the new financial region, and then stored.
5. The account information processing method according to claim 1, characterized in that, The method further includes: Receive a fund transfer request involving the target account, wherein the fund transfer request includes information about the financial region where the transaction occurred; Based on the financial region information, extract the target account code and / or target institution identification code that match the financial region information from the stored account information tuple; Based on the extracted target account code and / or target institution identification code, assemble a payment message or clearing instruction that is used to respond to the fund transfer request and conforms to the financial region where the transaction occurred.
6. The account information processing method according to claim 1, characterized in that, The method further includes: Receive a cross-financial region fund transfer request involving the target account, wherein the cross-financial region fund transfer request includes fund outflow side account, financial region information of the fund outflow location, fund inflow side account, and financial region information of the fund inflow location, and the target account is the fund outflow side account or the fund inflow side account; Based on the financial region information of the fund outflow location, extract the fund outflow account code and / or fund outflow institution identification code that match the financial region information of the fund outflow location from the stored account information tuple of the fund outflow side account to serve as the fund outflow side extraction information; Based on the financial region information of the fund inflow location, extract the fund inflow account code and / or fund inflow institution identification code that match the financial region information of the fund inflow location from the stored account information tuple of the fund inflow side account as the fund inflow extraction information; Based on the withdrawal information from the outflow side and the withdrawal information from the inflow side, a payment message or clearing instruction is assembled to respond to the cross-financial region fund transfer request and to comply with the regulations of the financial regions where the fund outflow and inflow are located, respectively.
7. An account information processing device for cross-financial regions, characterized in that, It includes a coding model acquisition unit, a mapping relationship maintenance unit, a filing operation response unit, a target coding generation unit, a target organization query unit, an information tuple formation unit, and an information tuple storage unit; The encoding model acquisition unit is used to acquire account encoding models configured for multiple financial regions respectively, wherein the account encoding model includes rule parameters for defining an account encoding format that conforms to the management requirements of the corresponding financial region; The mapping relationship maintenance unit is used to establish and maintain a multi-regional institution code mapping relationship between financial institutions and financial regions, wherein the multi-regional institution code mapping relationship is used to record the institution identification codes of the same financial institution in different financial regions. The filing operation response unit is used to respond to the operation of filing a file for a target account and obtain the target financial region and target financial institution associated with the target account; The target code generation unit is communicatively connected to the filing operation response unit and the code model acquisition unit, respectively, and is used to automatically generate a target account code that conforms to the management requirements of the corresponding financial region by calling the rule parameters in the corresponding account code model according to the target financial region. The target institution query unit is communicatively connected to the filing operation response unit and the mapping relationship maintenance unit, and is used to query and obtain the target institution identification code of the target financial institution in the target financial region from the multi-regional institution code mapping relationship according to the target financial institution and the target financial region. The information tuple forming unit is communicatively connected to the target code generation unit and the target institution query unit, respectively, and is used to associate the target account code with the target institution identification code to form the account information tuple of the target account in the target financial region; The information tuple storage unit is communicatively connected to the information tuple forming unit and is used to store the account information tuple for information retrieval based on the financial region when processing fund transfers involving the target account.
8. A computer device, characterized in that, The device includes a storage module, a processing module, and a transceiver module that are sequentially connected in communication. The storage module is used to store computer programs, the transceiver module is used to send and receive messages, and the processing module is used to read the computer programs and execute the account information processing method as described in any one of claims 1 to 6.
9. A computer-readable storage product, characterized in that, The computer-readable storage product stores instructions that, when executed on a computer, perform the account information processing method as described in any one of claims 1 to 6.
10. A computer program product, comprising a computer program or instructions, characterized in that, When the computer program or the instructions are executed by the computer, they implement the account information processing method as described in any one of claims 1 to 6.