Business system account sealing method and system and computer equipment

Abstract

The invention relates to the technical field of data processing, and provides a business system account sealing method and system and computer equipment. The method comprises the steps that a plurality of account sealing nodes are configured for each type of business receipts according to the types of the business receipts, and each account sealing node represents a specific control effect; a white list penetration mechanism is set, and if the business document contains a white list subject, penetration account sealing is allowed; and receiving a specified account sealing request instruction, searching the receipt type corresponding to the specified account sealing request instruction so as to carry out account sealing operation of the corresponding account sealing node, and not allowing to carry out operation with a specific control effect after account sealing. According to the invention, three-dimensional account sealing control of receipt types, service nodes and white lists is realized, cross-year automatic initialization account sealing strategies are supported, seamless integration of service systems is realized through a real-time query interface, the usability of software is improved, and the delivery cost is reduced.

Description

Technical Field

[0001] This invention relates to the field of data processing technology, and in particular to a method, system, and computer equipment for closing accounts in a business system. Background Technology

[0002] The statements in this section are merely background information related to the present invention and do not necessarily constitute prior art.

[0003] In corporate financial management, account closure refers to the process by which a company closes its financial accounts and stops recording related transactions during a specific period (such as the end of the accounting period or during the annual audit). This operation mainly involves freezing account funds, reconciling accounts, and solidifying financial data, aiming to ensure the accuracy and completeness of financial data. Currently, enterprise business systems face significant technical bottlenecks in account closure control: 1. Existing systems generally adopt globally unified account freezing parameters (such as full freezing of electronic ledgers), lacking differentiated control capabilities for document types (receipts, expense reports, etc.), which forces different types of business data to be frozen simultaneously, affecting business continuity.

[0004] 2. Account sealing control only stays at the system level (such as sealing the entire attendance system), and cannot implement fine-grained control over business process nodes such as "order creation-submission-approval-archiving", which leads to the risk of losing control over the modification permissions of historical data.

[0005] 3. The initialization of the account closure rules relies entirely on manual configuration, requiring the setting of account association rules item by item. This results in operational pain points such as high configuration error rate and slow response speed. The average account closure preparation time exceeds 4 hours (industry survey data).

[0006] 4. Existing technology adopts a rigid account sealing mechanism, which cannot support special scenarios that require penetrating the account sealing layer, such as financial order cancellation and audit traceability. Enterprises are forced to operate directly through the back-end database, which violates SOX compliance requirements.

[0007] These technical shortcomings increase the risk of data tampering for enterprises and prolong the month-end closing cycle, among other practical problems. There is an urgent need to achieve a multi-dimensional and configurable intelligent closing system through technological innovation. Summary of the Invention

[0008] To address the technical problems mentioned above, this invention provides a method, system, and computer equipment for closing accounts in a business system. This invention enables independent control based on document type, allows for node-level account closing control, and offers high operational efficiency.

[0009] To achieve the above objectives, the present invention adopts the following technical solution: The first aspect of the present invention provides a method for closing accounts in a business system.

[0010] A method for freezing accounts in a business system includes: Based on the business document type, configure several closing nodes for each type of business document, with each closing node representing a specific control effect; Set up a whitelist penetration mechanism to allow account blocking if a business document contains a whitelisted item. Upon receiving a specified account closure request instruction, the system locates the document type corresponding to the specified account closure request instruction to perform the account closure operation for the corresponding account closure node. After account closure, operations with specific control effects are not allowed.

[0011] Furthermore, the types of business documents include: receipts, payment slips, VAT invoices, expense reimbursement forms, material requisition forms, fund application forms, travel expense reimbursement forms, loan slips, payment failure documents, and supplementary entry documents.

[0012] Furthermore, the closing nodes include: document creation closing node, printing and approval closing node, document receipt closing node, and submission closing node.

[0013] Furthermore, a document type with a closing flag is introduced during the initialization of the closing settings.

[0014] Furthermore, the whitelist penetration mechanism includes: receiving a specified business operation, determining whether the account-sealing node has sealed the account, and if so, determining whether it contains a whitelist account. If it does, the specified business operation is allowed; if it does not, the specified business operation is rejected. If the account-sealing node has not sealed the account, the specified business operation is allowed.

[0015] Furthermore, after receiving the specified account closure request instruction, the process also includes: using a trained large model to extract keywords from the specified account closure request instruction, and determining the document type, account closure node, and specific control effects of the account closure node based on the keywords.

[0016] Furthermore, the business document type includes a virtual document type, which supports independent processing of virtual document types.

[0017] Furthermore, the business system's account closure method supports a refund and release mechanism.

[0018] A second aspect of the present invention provides a system for closing accounts in a business system.

[0019] A system for sealing accounts in a business system, comprising: The configuration module is configured to: configure several closing nodes for each type of business document based on the business document type, with each closing node representing a specific control effect; The settings module is configured to: set a whitelist penetration mechanism, allowing penetration and account blocking if a business document contains a whitelist item; The account closure module is configured to: receive a specified account closure request instruction, find the document type corresponding to the specified account closure request instruction, and perform the account closure operation for the corresponding account closure node. After the account is closed, operations with specific control effects are not allowed.

[0020] A third aspect of the present invention provides a computer device comprising: A processor, adapted to execute computer programs; A computer-readable storage medium storing a computer program that, when executed by a processor, implements the steps in the business system account sealing method described in the first aspect above.

[0021] Compared with the prior art, the beneficial effects of the present invention are: This invention provides a method and system for closing accounts in a business system. The method includes: configuring several closing nodes for each type of business document, with each closing node representing a specific control effect; setting a whitelist penetration mechanism, allowing closing accounts if the business document contains whitelisted items; receiving a specified closing request instruction, searching for the document type corresponding to the specified closing request instruction, and performing the closing operation at the corresponding closing node; after closing the account, operations with specific control effects are not allowed. This invention achieves closing control from three dimensions: document type, business node, and whitelist. It supports automatic initialization of closing strategies across fiscal years, achieves seamless integration with business systems through a real-time query interface, improves software usability, and reduces delivery costs.

[0022] This invention solves the business interruption problem caused by global account closure by configuring the account closure node differently according to document type (e.g., freezing only the payment node while retaining the query function for a receipt), which can greatly improve the availability of core business.

[0023] This invention refines the granularity of account sealing to process nodes such as "document creation-approval-archiving", and can be combined with the RBAC permission model to achieve precise interception of historical data modification, which can greatly reduce the risk of data tampering.

[0024] This invention uses a rule template library based on business scenarios, supports automatic matching of associated accounts and recommendation of risk rules, shortens the account closure preparation time, and reduces the configuration error rate.

[0025] The whitelist mechanism designed in this invention allows special operations such as audit tracing to penetrate the account sealing layer, and improves the compliance review pass rate by replacing the direct connection to the database in the backend with traceable audit. Attached Figure Description

[0026] The accompanying drawings, which form part of this invention, are used to provide a further understanding of the invention. The illustrative embodiments of the invention and their descriptions are used to explain the invention and do not constitute an improper limitation of the invention.

[0027] Figure 1 This is a flowchart illustrating a method for closing accounts in a business system according to an embodiment of the present invention; Figure 2 This is a schematic diagram illustrating the business document types shown in an embodiment of the present invention; Figure 3 This is a schematic diagram of the account closure settings interface shown in an embodiment of the present invention; Figure 4 This is a flowchart illustrating the whitelist penetration mechanism in an embodiment of the present invention; Figure 5 This is a structural diagram of the business system for closing accounts, as shown in an embodiment of the present invention; Figure 6 This is a structural diagram of a computer device shown in an embodiment of the present invention. Detailed Implementation

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

[0029] It should be noted that the following detailed description is illustrative and intended to provide further explanation of the invention. Unless otherwise specified, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this invention pertains.

[0030] It should be noted that the terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit the scope of exemplary embodiments according to the invention. As used herein, the singular form is intended to include the plural form as well, unless the context clearly indicates otherwise. Furthermore, it should be understood that when the terms "comprising" and / or "including" are used in this specification, they indicate the presence of features, steps, operations, devices, components, and / or combinations thereof.

[0031] As described in the background section, traditional business systems use global closing parameters (such as electronic ledger closing), which cannot independently control closing based on document type (such as receipts / expense reports); they lack business node-level closing, only achieving system-level overall closing (such as overall closing of attendance data), and cannot control nodes such as "document creation-submission-approval"; closing initialization relies on manual configuration, requiring manual intervention in account rules, resulting in low operational efficiency; and special business scenarios (such as financial order cancellation) cannot penetrate closing restrictions. To solve these problems, this invention proposes a method and system for closing accounts in a business system. The technical solution of this invention will be described in detail below through several embodiments.

[0032] Figure 1This is a flowchart illustrating a method for closing accounts in a business system according to an embodiment of the present invention; see also... Figure 1 Methods for freezing accounts in the business system include: Based on the business document type, configure several closing nodes for each type of business document, with each closing node representing a specific control effect; Set up a whitelist penetration mechanism to allow account blocking if a business document contains a whitelisted item. Upon receiving a specified account closure request instruction, the system locates the document type corresponding to the specified account closure request instruction to perform the account closure operation for the corresponding account closure node. After account closure, operations with specific control effects are not allowed.

[0033] This invention achieves account closure control across three dimensions: document type, business node, and whitelist. It supports automatic initialization of account closure strategies across fiscal years and enables seamless integration with business systems through a real-time query interface, thereby improving software usability and reducing delivery costs.

[0034] Figure 2 This is a schematic diagram illustrating the business document types shown in an embodiment of the present invention; see reference. Figure 2 The types of business documents include: receipts, payment slips, VAT invoices, expense reimbursement forms, material requisition forms, fund application forms, travel expense reimbursement forms, loan slips, payment failure documents, and supplementary entry documents.

[0035] Closing settings initialization refers to the process of setting or resetting the end-of-period closing (closing) rules, permissions, cut-off dates, and related control parameters for a specific accounting period in a financial management system (such as an ERP system) or accounting software. This is a crucial basic configuration to ensure that monthly, quarterly, or annual closing work can be completed in a standardized, secure, and efficient manner in subsequent accounting periods.

[0036] During system initialization, this application configures several closing nodes for each type of business document based on the business document type, with each closing node representing a specific control effect.

[0037] Figure 3 This is a schematic diagram of the account closure settings interface shown in an embodiment of the present invention; see reference. Figure 3 For example, for a receipt, you can set up a document creation and closing node, a print approval and closing node, a receipt closing node, and a submission closing node. The document creation and closing node prevents the creation of new receipts; the print approval and closing node prevents the printing of approved documents; the receipt closing node prevents receipt confirmation; and the submission closing node prevents submission for approval.

[0038] The following example illustrates the solution of this embodiment: As a leading cloud computing service provider in China, Inspur Group processes over 1.2 million payment transactions annually for a certain financial project. To address the complex payment scenarios arising from multiple business segments (server sales, cloud service subscriptions, software licensing, etc.), the Group built an intelligent closing engine within the GSCloud system. This system divides the payment invoice lifecycle into 15 status nodes, with tiered closing controls implemented at four key nodes: invoice creation, printing and approval, invoice receipt, and submission, forming a "fuse" mechanism for business-finance collaboration.

[0039] (1) Order creation and closing node: Business entry control The system automatically triggers document creation and account closure according to a set time. Due to a delay in acceptance of a provincial government cloud project, the client requested a receipt for the remaining 8.8 million yuan contract payment by the 30th. Although the sales director had given special approval via email, the system still blocked the operation and displayed a "violation of account closure policy" message. The financial shared service center activated a level-three emergency response: the risk control system automatically verified the client's historical payment records (the delinquency rate for the past 12 months was 0); compared the acceptance clauses in the contract database (a 30-day grace period clause existed); and generated a temporary document creation token (valid until 9:00 AM the following day). This mechanism reduced the "accounts period rollover" problem at the end of the quarter for the group by 76%.

[0040] (2) Printing and approval of the closing of accounts: physical media control The printing and sealing phase begins at 00:00 on the 1st of the following month. A regional business unit needs to print a "Receipt Confirmation" for a bank guarantee. The system triggers a double interception: 1) It identifies that the server order associated with the guarantee has a 2% unreleased warranty deposit (trigger clause: FINC-331); 2) It detects that the printing IP address is located overseas (compliance policy: cross-border documents require headquarters review). The Funds Management Department remotely authorizes printing through "digital fence" technology but forcibly adds: a dynamically encrypted QR code (linked to blockchain evidence) and an audit trail number (format: PRN-202507-XXX). This measure reduces the paper document invalidation rate from 5.3% to 0.7%.

[0041] (3) Acquiring and closing the account: Confirmation of cash flow During the period when the acquiring function was locked at 12:00 on the 2nd, a company received a software subscription fee of 500,000 yuan from a customer through a digital currency wallet. Although the bank statement showed that the money had been deposited, the system prohibited the "acquisition confirmation" process. The reasons included: the transaction did not match the invoice information (suspected prepayment); the digital currency wallet had not completed KYC verification. The financial robot automatically performed the following actions: temporarily deposited the funds into the "Other Payables - Pending Confirmation" account, pushed the "Funds Claim Notice" to the business side, and generated a tax warning (the tax calculation time for digital currency is pending confirmation). This process reduced the group's fund reconciliation discrepancy time to 4.8 hours.

[0042] (4) Submit the account closure node: freeze the approval process After the complete account freeze at 24:00 on the 3rd, a client of the Cloud Business Unit prepaid 6 million yuan in service fees for 2026. Although the business department had completed service delivery, the system intercepted the approval submission and executed the following: automatically splitting the amount (allocated to each month of 2026 according to the service period); generating a "Revenue Recognition Recommendation for Inter-period Periods"; and pushing it to the SEC reporting system (compliance requirements for revenue recognition of US-listed companies). This design ensured that the Group's revenue recognition complied with ASC 606, reducing annual audit adjustments by 43%.

[0043] This invention refines the granularity of account sealing to process nodes such as "document creation-approval-archiving", and can be combined with the RBAC permission model to achieve precise interception of historical data modification, which can greatly reduce the risk of data tampering.

[0044] This embodiment only describes the type of account closing node for payment receipts and the specific control effect of the account closing node. Figure 3 For payment slips, VAT invoices, expense reimbursement forms, material requisition forms, fund application forms, travel expense reimbursement forms, loan slips, payment failure documents, and supplementary documents, the above-mentioned closing node types and specific control effects of closing nodes are also applicable in this embodiment.

[0045] In other embodiments, the account sealing node and its corresponding technical effects can be customized and extended according to user needs, thereby improving the applicability of the account sealing system.

[0046] In addition, this embodiment realizes the cross-year automated initialization function of the business system's account closure strategy. When the system switches to a new accounting year, it can automatically generate the basic account closure strategy framework for that year based on preset rules, ensuring that the necessary account closure control preparations are completed before the new year's business begins, while retaining the flexibility of manual adjustment.

[0047] Specifically, the implementation process of the cross-year automatic initialization technology is as follows: Receive external input of the business year parameter to be initialized (e.g., "2025"). Parameter validation: Verify the validity of the year format (4 digits) and the rationality of the business (not exceeding the current year + 5 years); Query the main table of account closure policies in the policy database (T_ACCOUNT_CLOSE_POLICY). Perform a conditional search: WHERE YEAR_FIELD = [input year] AND STATUS = 'ACTIVE'; Return result set judgment: If a record exists, terminate the initialization process and return the message "The policy for this year already exists"; if no record exists, proceed to the automatic generation process.

[0048] The specific generation process can use default strategy generation rules, including: Full document type coverage: Iterates through all business document types registered in the system (obtained from the T_BIZ_DOC_TYPE table) and automatically generates the document type; Full node unsealing preset: Generates all sealed nodes (such as: creation, modification, deletion, posting, etc.) for each document type, and the initial status of all nodes is set to "ENABLED"; Automatically inherit the system's global whitelist subject configuration (obtained from T_WHITELIST_ACCOUNT); This embodiment can also use data persistence processing to generate a strategy master record: input the year, the current system timestamp, etc., to generate strategy detail records, such as generating multiple records according to the combination of document type and closing node.

[0049] In the account closure system, the NODE_STATUS field can be uniformly set to "0" (unsealed status), and the IS_OVERRIDABLE field can be set to "1" (allowing manual adjustment).

[0050] This embodiment can initialize the interface, for example, using a tree structure: First level: Business document types (grouped by module); Second level: Closing nodes under each document type; Status indicators: a green toggle icon indicates unsealing status, and a red toggle icon indicates closing status. The initialization interface can also include "Save Confirm" and "Manual Adjust" buttons to meet users' confirmation and custom adjustment needs.

[0051] In addition, this embodiment allows users to switch the open / closed state of any account-sealing node, and also allows setting user permissions. Users with high-level permissions have the highest permissions, while users with low-level permissions have the lowest permissions. Access control can ensure data security.

[0052] In this embodiment, the front end displays real-time status change impact prompts (e.g., "Closing this node will prohibit all users from deleting documents").

[0053] This embodiment supports generating a new version record each time it is saved, retains the modification history, and supports important adjustments that can be configured to require supervisor approval (through the WF_APPROVAL table).

[0054] After configuring the account closure node and specific control effects, this invention allows users to input account closure request commands via the front end, such as "Do not allow payment confirmation for receipts." The front end sends the request command to the back end, which uses a trained large-scale model to extract keywords from the request command. Based on these keywords, the system confirms that the document type is "receipt" and the specific control effect of the account closure node is "Do not allow payment confirmation." To ensure the accuracy of the control effect, after confirming the document type and specific control effect, user confirmation can be requested from the front end. After user confirmation, the system can further confirm, based on the specific control effect of the account closure node, that the account closure operation is being performed on the receipt closure node. The system controls the receipt closure node in the "receipt" to be set to the closed state, and the green toggle icon on the display interface switches to a red toggle icon.

[0055] The following example illustrates this: (1) Instruction input stage The user enters "Immediately disable all receipt confirmation operations" through the front-end command window. This command contains three key elements: a timeliness flag ("immediately"), the controlled object ("receipt confirmation of receipts"). The system front-end performs preliminary syntax validation, rejects commands containing ambiguous words (such as "maybe" or "probably"), and automatically completes the standardized description of the document type (correcting the user's input "receipt" to "receipt").

[0056] (2) Semantic parsing stage After receiving the instruction, the backend large model initiates multi-level analysis: Entity recognition uses a pre-trained financial terminology model to identify that "receipt" belongs to the "accounts receivable" document category.

[0057] Intent decoding analyzes the verb phrase "prohibit...acceptance confirmation" and matches it with the "acceptance sealing node" among the four types of sealing nodes. Its control effect is to block the transition of the transaction status from "received" to "confirmed".

[0058] Context validation checks whether dynamic closing of accounts is allowed in the current accounting period.

[0059] (3) Secondary confirmation mechanism The system returns structured parsing results to the user: You are requesting: to perform [Account Closure] on [Payment Notice]; Control effect: The scope of the payment notice confirmation status will not be updated. Users need to verify their fingerprints to confirm the operation. This step simultaneously records the operator's MAC address and network topology location, and asks whether to add the user to the whitelist.

[0060] (4) Strategy Execution Phase After confirmation, the system will perform the following actions: Write a closing record to the distributed ledger, push control policies to the financial system, automatically generate a list of affected documents (including customer name, amount, and aging), and trigger associated controls: synchronously freeze the revenue recognition process of related sales contracts.

[0061] Figure 4 This is a flowchart illustrating the whitelist penetration mechanism in an embodiment of the present invention; see also Figure 4 The front end receives the specified business operation, determines whether the account closure node has closed the account, and if so, determines whether it contains the whitelisted account. If it does, the specified business operation is allowed; if not, the specified business operation is rejected. If the account closure node has not closed the account, the specified business operation is allowed.

[0062] In some embodiments, the whitelist includes: Level 1 whitelist, Level 2 whitelist, Level 3 whitelist, and Level 4 whitelist. Level 1 whitelist refers to specific business types that cannot be delayed, allowing continued operation during the account freeze period, such as: emergency expense reimbursement items, regulatory account transfer instructions, and cross-border settlement timeliness business, etc.; Level 2 whitelist includes: intra-group related transactions, government mandated payments, etc.; Level 3 whitelist includes: system-level privilege whitelist, etc.; Level 4 whitelist includes: regional special approval whitelist, etc.

[0063] This invention establishes a whitelist-based penetration mechanism, allowing for account closure through a whitelist when a business document contains such an account, thus bypassing account closure controls. While maintaining technical rigor, the dual-track design of "standard control + exception management" ensures both the rigid constraints of financial closing and a compliant channel for necessary business adjustments.

[0064] Finally, this invention achieves seamless integration with business systems through a real-time query interface. The account closure query interface specification is shown in Table 1: Table 1. Account Closure Query Interface Specifications

[0065] In this embodiment, the response logic for the account closure query interface is as follows: Figure 4 The flowchart shown is for the whitelist penetration mechanism.

[0066] This invention also supports independent processing of virtual document types (payment failure / re-entry, etc.) and a refund release mechanism to avoid business interruption.

[0067] In summary, this invention provides a three-dimensional account closure control method based on document type, business node, and whitelist, which supports automatic initialization of account closure strategies across fiscal years, achieves seamless integration with business systems through a real-time query interface, improves software usability, and reduces delivery costs.

[0068] The above combination Figure 1The method for closing accounts in a business system provided in this embodiment of the invention has been described in detail. Next, the system for closing accounts in a business system provided in this embodiment of the invention will be described in conjunction with the accompanying drawings.

[0069] Figure 5 This is a schematic diagram of the structure of the business system for closing accounts, as shown in an embodiment of the present invention. Figure 5 The system described in this invention includes: The configuration module is configured to: configure several closing nodes for each type of business document based on the business document type, with each closing node representing a specific control effect; The settings module is configured to: set a whitelist penetration mechanism, allowing penetration and account blocking if a business document contains a whitelist item; The account closure module is configured to: receive a specified account closure request instruction, find the document type corresponding to the specified account closure request instruction, and perform the account closure operation for the corresponding account closure node. After the account is closed, operations with specific control effects are not allowed.

[0070] In some embodiments, the business document types include: receipts, payment slips, VAT invoices, expense reimbursement forms, material requisition forms, fund application forms, travel expense reimbursement forms, loan slips, payment failure documents, and supplementary entry documents.

[0071] In some embodiments, the closing nodes include: a document creation closing node, a printing and approval closing node, a document receipt closing node, and a submission closing node.

[0072] In some embodiments, a document type with a closing flag is introduced during the closing settings initialization.

[0073] In some embodiments, the whitelist penetration mechanism includes: receiving a specified business operation, determining whether the account-sealing node has sealed the account, and if so, determining whether it contains a whitelist account. If it does, the specified business operation is allowed; if it does not, the specified business operation is rejected. If the account-sealing node has not sealed the account, the specified business operation is allowed.

[0074] In some embodiments, after receiving a specified account closure request instruction, the method further includes: using a trained large model to extract keywords from the specified account closure request instruction, and determining the document type, account closure node, and specific control effect of the account closure node based on the keywords.

[0075] In some embodiments, the business document type includes a virtual document type, which supports independent processing of the virtual document type.

[0076] In some embodiments, the business system's method for closing accounts supports a cancellation and release mechanism.

[0077] According to embodiments of the present invention, the system for closing accounts in a business system can correspond to executing the method described in the embodiments of the present invention, and the above and other operations and / or functions of each module of the system for closing accounts in a business system are respectively for implementing Figure 1 For the sake of brevity, the corresponding processes of each method in the code will not be elaborated here.

[0078] See Figure 6 The diagram shows the structure of a computer device, which includes a processor, a communication interface, and a computer-readable storage medium. The processor, communication interface, and computer-readable storage medium are connected via a bus or other means. The communication interface is used to receive and send data. The computer-readable storage medium can be stored in the computer device's memory. The computer-readable storage medium stores computer programs, including program instructions, and the processor executes the program instructions stored in the computer-readable storage medium. The processor (or CPU, Central Processing Unit) is the computing and control core of the computer device, adapted to implement one or more instructions, specifically adapted to load and execute one or more instructions to achieve the corresponding steps in the method embodiment of the business system's account closure.

[0079] Furthermore, this storage space also contains one or more instructions suitable for loading and execution by the processor. These instructions can be one or more computer programs (including program code). It should be noted that the computer-readable storage medium here can be high-speed RAM memory or non-volatile memory, such as at least one disk storage device; optionally, it can also be at least one computer-readable storage medium located remotely from the aforementioned processor.

[0080] In one embodiment, the computer-readable storage medium stores one or more instructions; the processor loads and executes one or more instructions stored in the computer-readable storage medium to implement the corresponding steps in the above-described method embodiment for sealing accounts in the business system.

[0081] Those skilled in the art will understand that embodiments of the present invention can be provided as methods, systems, or computer program products. Therefore, the present invention can take the form of hardware embodiments, software embodiments, or embodiments combining software and hardware aspects. Furthermore, the present invention can take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage and optical storage) containing computer-usable program code.

[0082] This invention is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart illustrations and / or block diagrams. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0083] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0084] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0085] Those skilled in the art will understand that all or part of the processes in the above embodiments can be implemented by a computer program instructing related hardware. The program can be stored in a computer-readable storage medium, and when executed, it can include the processes of the embodiments of the above methods. The storage medium can be a magnetic disk, optical disk, read-only memory (ROM), or random access memory (RAM), etc.

[0086] The above description is merely a preferred embodiment of the present invention and is not intended to limit the invention. Various modifications and variations can be made to the present invention by those skilled in the art. 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 sealing accounts in a business system, characterized in that, include: Based on the business document type, configure several closing nodes for each type of business document, with each closing node representing a specific control effect; Set up a whitelist penetration mechanism to allow account blocking if a business document contains a whitelisted item. Upon receiving a specified account closure request instruction, the system locates the document type corresponding to the specified account closure request instruction to perform the account closure operation for the corresponding account closure node. After account closure, operations with specific control effects are not allowed.

2. The method for closing accounts in a business system according to claim 1, characterized in that, The types of business documents include: receipts, payment slips, VAT invoices, expense reimbursement forms, material requisition forms, fund application forms, travel expense reimbursement forms, loan slips, payment failure documents, and supplementary entry documents.

3. The method for closing accounts in a business system according to claim 1, characterized in that, The closing nodes include: document creation closing node, printing and approval closing node, document receipt closing node, and document submission closing node.

4. The method for closing accounts in a business system according to claim 1, characterized in that, Introduce a document type with a closing flag during the closing settings initialization.

5. The method for closing accounts in a business system according to claim 1, characterized in that, The whitelist penetration mechanism includes: receiving a specified business operation, determining whether the account-sealing node has sealed the account, and if so, determining whether it contains a whitelisted account. If it does, the specified business operation is allowed; if it does not, the specified business operation is rejected. If the account-sealing node has not sealed the account, the specified business operation is allowed.

6. The method for closing accounts in a business system according to claim 1, characterized in that, After receiving the specified account closure request instruction, the process also includes: using a trained large model to extract keywords from the specified account closure request instruction, and determining the document type, account closure node, and specific control effects of the account closure node based on the keywords.

7. The method for closing accounts in a business system according to claim 1, characterized in that, The business document types include virtual document types, and independent processing of virtual document types is supported.

8. The method for closing accounts in a business system according to claim 1, characterized in that, The business system's account closure method supports a refund and release mechanism.

9. A system for sealing accounts in a business system, characterized in that, include: The configuration module is configured to: configure several closing nodes for each type of business document based on the business document type, with each closing node representing a specific control effect; The settings module is configured to: set a whitelist penetration mechanism, allowing penetration and account blocking if a business document contains a whitelist item; The account closure module is configured to: receive a specified account closure request instruction, find the document type corresponding to the specified account closure request instruction, and perform the account closure operation for the corresponding account closure node. After the account is closed, operations with specific control effects are not allowed.

10. A computer device, characterized in that, A processor, adapted to execute computer programs; A computer-readable storage medium storing a computer program, which, when executed by the processor, implements the steps of the business system account closure method as described in any one of claims 1-8.

Images